HOW-TO report a bug

featured-image-bug

In this blog post, we will talk about on how to report bugs in our fork of AOSP platform and infrastructure for it which includes website, downloads, server, staticstics webpage etc.

WHAT NOT to report!

  • Bugs which are present in unofficial builds or anything that is nit downloaded from our official download server.
  • Asking about device support, unlocking bootloader, getting TWRP installed and similar queries are not encouraged.
  • Bugs on a device which has root priveleges from SuperSU, Magisk, Magisk modules or any other rooting methods that exists etc.
  • Issues which suggest feature requests.
  • Issues which suggest supporting a new device which we do not own.
  • Bugs which arise after replacing default apps.
  • Bugs in devices which occur in third party apps.
  • Bugs in devices we do not support anymore.
  • Bugs in ArrowOS experimental builds.

WHERE to report

Check if someone has already reported that bug before you create a new issue, incase you find there is already a bug report for it you can comment there with “+1” OR “I am also facing this” etc BE CREATIVE.

Issues need to be reported in our gitlab issues ORG:

Android Issues OR Infrastructure Issues

Please, report bugs in the following format:

Arrow Android:

Example:-

  • “I am facing a bug in arrow-11.0 community VANILLA edition on my Elgoog Pixel XL. Camera is not working since last update. I uploaded the logcat here www.example.com/camera-logs.txt”
  • “WiFi is not working on my OnePlus One, I use OFFICIAL arrow-11.0 GAPPS build. I have captured a logcat while trying to open WiFi and have uploaded the logs to www.example.com/opo-cyberwifi-10-12-2077.log”

Tips:

  1. You can upload logs as an attachment in gitlab issues or upload to websites like hastebin.com etc
  2. Here are some articles to help you with capturing logcats in android:
    1. https://developer.android.com/studio/command-line/logcat
    2. https://www.xda-developers.com/how-to-take-logs-in-android
  3. You MUST provide proper steps to reproduce that bug, glitch or whatever the issue you are facing, please dont report your OCD’s or perceptions as bugs.
  4. Always mention things like:
    1. ArrowOS Version: arrow-10.0, arrow-11.0, arrow-12.0… etc
    2. ArrowOS Build Type: OFFICIAL, COMMUNITY, UNOFFICIAL
    3. ArrowOS Build Variant: VANILLA, GAPPS
    4. Device Name or codename: example: Poco X3 (surya), OnePlus 6 (enchilada) etc

ArrowOS Infrastructure:

Example:

  • “Official supported device list just vanished on ArrowOS website, I cannot download anything”
  • “ArrowOS gerrit is not opening since an hour, I want to push some of my changes to it”

Please properly mention all the details you can gather, capture logcats for android bug reports after reproducing it. If you do not mention the details or if logcats are not provided such reports will be DIRECTLY ignored. Make sure all requirements are correctly fulfilled, incomplete or one sentence reporting of bugs will be ignored. Once you report the bug, please allow some time for maintainers/deveopers to look at it, dont be imaptient and expect the bugs fixed in next update. Critical bugs will be fixed on top prioriity compared to other so please be PATIENT. Last but not the least, please DO NOT SPAM the telegram chat with bugs and feature requests.

You may also like...

Leave a Reply

Your email address will not be published. Required fields are marked *