Bug Reporting
- You always have to flash the kernel accompanying every build.
- Always follow rule #1
- Don't file bugs mentioning "Wifi is not working". Wifi is always tested and working before the release, except if I state that it's broken. If it's not working for you, you didn't follow rules #1 & #2.
If you have issues with the builds, you can report them in the bug tracker so we can look at them and possibly fix them. If you don't report something in the bug tracker and simply post it here in xda, we won't fix it for sure. There are hundreds of posts and it's not easy to keep track of them.
- First check if there isn't a similar issue in the bug tracker
- Don't report issues if you are not using the kernel that was provided with the ROM.
- Don't report issues for any other version than the latest test release.
- Don't report issues if you haven't followed the exact order of installation steps.
- Don't report issues if you have flashed any mod or use any script.
- Don't report issues if you don't have the needed logs.
HTCLEGACY is a work in progress. Looking at the wrong things cost precious time.
If you create a new issue, always include:
- Android version
- The release date
- A detailed description of the problem
- The device name
- Log files (not zipped and available to read live without downloading them)
Any issue that does not include the above info will be set to invalid and closed without further notice.
- PC with adb installed or
- Market apps that collect the logs (see below) or
- Terminal emulator app
Additionally to report battery problems
- Install BetterBatteryStats (BBS) from here
- Android log:
adb logcat -dor use an app like CatLog - Last kernel log:
adb shell su -c 'cat /proc/last_kmsg'(see also the remark below) - Current kernel log:
adb shell su -c 'dmesg'or use an app like dmesgLog - Radio log:
adb logcat -b radio - All-in-one solution, via opensource app, which support Kernel logs (dmsg), Last kernel log (last_kmsg) and Android log (Logcat) SysLog app
- Battery usage: BetterBatteryStats: Menu > Dump to File
- Paste the logs on pastebin or a similar service, like gist. If the logs are provided as a zip file or can't be viewed live on the internet, the bug report will be closed as invalid.
- Create/update an issue on the bug tracker and provide the link to the pasted log
If you had a kernel crash (reboot), try to capture the log in recovery before starting Android again: adb shell cat /proc/last_kmsg
If you have network issues, you need to provide the radio log along with the android log
If you want to get the logs on your device, open a terminal, type the su command and:
- Android log:
logcat -d >/sdcard/logcat.txt - Last kernel log:
cat /proc/last_kmsg >/sdcard/last_kmsg.txt - Current kernel log:
dmesg >/sdcard/dmsg.txt