I'm trying to build CM10 for my Samsung Galaxy Reverb. It's compiling fine, giving ADB fine, but not actually booting.
Here's the results of logcat:
http://pastebin.com/gWh4UkEU
And dmesg:
http://pastebin.com/LnjVgcnG
Any help would be appreciated!
Related
After rooting my SG2, Logcat will keep on crashing whenever I try to connect my device with Eclipse.
Anybody else experience this? It worked fine before rooting.
Hi everyone:
I am attempting to boot AOSP 4.0.4 (r1) for the Galaxy Tab 10.1 wifi (GT-P7510). I have merged pershoot's CM9 3.1.10 kernel and been able to get through a few errors noticed in last_kmsg. However, I'm trying to figure out why servicemanager is now crashing and can't seem to get a hold of a logcat. I must be doing something stupidly simple incorrectly...have searched high and low and every example I have seen of someone complaining of a servicemanager crash with the same output has a logcat to provide.
Basically what's happening is I try to boot, see the Samsung Galaxy Tab logo, it sits for about 20 seconds and then auto-reboots back into recovery after the 4th servicemanager crash.
I edited the init.rc to increase loglevel to 8 which is showing me more detail, but not enough. I've attached my last_kmsg, init.rc and init.p3.rc to this thread in a zip file.
Here's what I'm doing to try and pull logcat:
1) Boot into recovery, wipe my device, install my rom/kernel + gapps
2) Run "adb logcat -v long > logcat.txt". I get the obvious "-waiting for device-" message
3) Attach device to computer
4) Reboot device and wait
When the device goes back into recovery after the failed boot, I check the output file and it's empty. What dumb thing am I forgetting? Or is it legit that the system is just not getting far enough into the boot sequence to start adbd?
Thanks all very much in advance for any assistance you can provide.
Never mind, worked it out on my own.
Sent from my Infamous Tab.
I've been experiencing random freezes, at least one daily, which force me to hold power to restart the phone. The phone otherwise appears to operate just fine. I finally figured out the SDK system and got an error-filtered logcat. I have no idea how to interpret whats going wrong, and before I pin a logcat in the wrong dev forum, how can I determine the relevant causes of the errors recorded?
adb logcat *:E
cm 10.1.3
ajk 4.8
ucmd8 modem
4.1.2 bootloader
-Cyril
Today I build my first (working) android rom based on CM.
When booted up the process com.android.phone keeps on crashing every second or something, I tried to use adb logcat but it keeps waiting for a device.
In the windows device manager I don't see a new device and when connecting over the network I get an error: protocol fault (status read)
Any suggestions at what it could be?
The rom that is currently running has been continued from where it errored out, I am rebuilding it now.
I will keep you up-to-date
Thanks,
Tim
Hi everybody. When I use custom rom in my phone I'm getting random reboots. I have managed to get logs and last_kmsg for this problem but I am unable to find the ptoblem and solution. From logs I can see that something 8s messed with RIL.
Any help to know and fix this problem will be highly appreciated..
I have attached the log and last_kmsg only thr name is kmsg but it is actually last_kmsg.