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
Related
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'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!
Good day all
I bought this device from a seller of eBay (from USA), I am in South Africa
I had to network unlock this device, and it all ran perfect, no issues whatsoever
Recently I have noticed my device doing random reboots, once every day(literally), it will reboot when I take it off from charging or when I press pwer button to wake up. After reboot, it will show the Glowing Samsung Logo, and just stay there continueously.
To fix this, I need to do a factory reset, or just clear the Data partition then it works fine again.
This happens at random, so every day I need to reinstall all the apps, it is such a pain, and obviously something is wrong...
Device: Samsung Galaxy Note LTE (i717)
ROM: Blackstar Blackjelly 4.1.2
Baseband: I717 UCMD3
Recovery: TWRP (latest v.)
Just for the record, ,it all started happening recently, the first time it happened, I was browsing 9gag using the app, then my device rebooted in my hand while scrolling, agter going to recovery, my sdcard and internal sdcard has been formated, and all internal partitions has been formated to....
I have no idea what is causing this but I am pretty sure it is not the rom, since I have had this rom for a while now...
What kernel do you use, and can you take a logcat?
(To take a logcat, enable ADB, plug in your device to your computer, and run adb logcat from the Android SDK. You can grab that here: http://developer.android.com/sdk/index.html?hl=sk )
BachMinuetInG said:
What kernel do you use, and can you take a logcat?
(To take a logcat, enable ADB, plug in your device to your computer, and run adb logcat from the Android SDK. You can grab that here: http://developer.android.com/sdk/index.html?hl=sk )
Click to expand...
Click to collapse
after running the logcat with "
Code:
adb logcat > logcat.txt
" for just more than 2 hours, i stopped it...it is 1250kb, see attached, it is compresssed in a zip file
p.s. Im quite positive it shouldnt take that long
any help would really help!!!
Hey guys,
I was wondering what kind of logging the Verizon Samsung Galaxy S4 does and how can I access it.
I found some logs once; but I can't seem to get back to the the menu. Only the recovery menu button combo {down volume, home, power}
Also I could not figure out how to copy those logs off the device.
Really want to have the ability to get to those logs even if the device is crapping out. Any one have any ideas?
Verizon Samsng S4 on Android 5.0.1 (LRX22C)
some back story:
I have Maas360 and a Kiosk policy applied to about 70 devices. Some have been getting stuck in a loop; phone restarts for no reason, stays up for about a minute than reboot.
So I figured I had pushed out a bad policy. I made a new policy minus the changes that correlated to the reboot loops and things seemed to be ok.
Since the phone wouldn't stay on the network long enough to grab the command to remove the bad policy, I wiped the phones with Samsung Kies firmware updater.
But now some of the phones I wiped are back to the reboot loop. Maas360 wasn't a whole lot of help, but since it doesn't stay on long enough i doubt they have any logs either.
thanks guys
cefalu said:
Hey guys,
I was wondering what kind of logging the Verizon Samsung Galaxy S4 does and how can I access it.
I found some logs once; but I can't seem to get back to the the menu. Only the recovery menu button combo {down volume, home, power}
Also I could not figure out how to copy those logs off the device.
Really want to have the ability to get to those logs even if the device is crapping out. Any one have any ideas?
Verizon Samsng S4 on Android 5.0.1 (LRX22C)
some back story:
I have Maas360 and a Kiosk policy applied to about 70 devices. Some have been getting stuck in a loop; phone restarts for no reason, stays up for about a minute than reboot.
So I figured I had pushed out a bad policy. I made a new policy minus the changes that correlated to the reboot loops and things seemed to be ok.
Since the phone wouldn't stay on the network long enough to grab the command to remove the bad policy, I wiped the phones with Samsung Kies firmware updater.
But now some of the phones I wiped are back to the reboot loop. Maas360 wasn't a whole lot of help, but since it doesn't stay on long enough i doubt they have any logs either.
thanks guys
Click to expand...
Click to collapse
"Adb logcat" is definetely what you are looking for:
http://developer.android.com/tools/help/logcat.html
http://forum.xda-developers.com/showthread.php?t=1726238
It is basically kernel output.
Ciuffy's SM-G900F CM 12.1 spirit hath marked this way.
Ciuffy said:
"Adb logcat" is definetely what you are looking for:
http://developer.android.com/tools/help/logcat.html
http://forum.xda-developers.com/showthread.php?t=1726238
It is basically kernel output.
Ciuffy's SM-G900F CM 12.1 spirit hath marked this way.
Click to expand...
Click to collapse
TY DUDE!
I was moving in that direction, installed odin, android studio, but I can not seem to get adb to connect.
i get this message
adb server is out of date. killing
* daemon started successfully
error: device not found
Going t do some more reading on the links you posted I am sure the answer is there.
cefalu said:
TY DUDE!
I was moving in that direction, installed odin, android studio, but I can not seem to get adb to connect.
i get this message
adb server is out of date. killing
* daemon started successfully
error: device not found
Going t do some more reading on the links you posted I am sure the answer is there.
Click to expand...
Click to collapse
Try this:
http://forum.xda-developers.com/showthread.php?t=567955
If you are on Ubuntu, you can get the latest version with
Apt-get install android-tools-adb.
That works with my S5.
Ciuffy's SM-G900F CM 12.1 spirit hath marked this way.
i occasionally get no sound after a rom flash. sometimes wiping data and other stuff will help it. but after a reboot, or turned off to charge then boot up, sound is gone. the ouput on logcat is logcat output "setVolumeIndexForAttributes failed to set curve" amongst other outputs. "command failed for android_media_audiosystem."
it also did this on stock. i rooted to run a logcat to find out th e issues.
any ideas?