dmesg logs

[imnuts]

It's been posted that if you're having issues, getting the contents of dmesg can help the devs. In the chance that the system won't boot up, this can be harder to do. So, I found the instructions for getting the info and changed them a little bit. If you add the following command to froyo.user.conf in the custom shell commands section (at the bottom) it will save the dmesg data for you, though it only captures it during boot.

dmesg >> /sdcard/andboot/logs/dmesg_`date +%Y%m%d%k%M`.log

This will save the log on your sd card in the andboot/logs folder (should create it if it doesn't exist). It also time stamps the filename so that it won't put a bunch of dmesg logs together and also doesn't overwrite what is already there.

[natemcnutty]

Originally Posted by imnuts

It's been posted that if you're having issues, getting the contents of dmesg can help the devs. In the chance that the system won't boot up, this can be harder to do. So, I found the instructions for getting the info and changed them a little bit. If you add the following command to froyo.user.conf in the custom shell commands section (at the bottom) it will save the dmesg data for you, though it only captures it during boot.

dmesg >> /sdcard/andboot/logs/dmesg_`date +%Y%m%d%k%M`.log

This will save the log on your sd card in the andboot/logs folder (should create it if it doesn't exist). It also time stamps the filename so that it won't put a bunch of dmesg logs together and also doesn't overwrite what is already there.

Also, you can create a text file named earlyharetlog.txt in the same folder as haret.exe, and you will get a new file named haretlog.txt that has all commands executed by haret during startup. This can gather some information that dmesg misses.