I am one of the many who have been experiencing the random reboots. I have seen talk about it, but have not seen anyone really looking into why this is happening. Some people claim it happens only when docked, or when SD card is in etc. Yet others post that they still get the reboots without doing those things either.
I have been monitoring my reboot problem very closely. I have yet to determine the cause other than it only happens when the device is put into sleep mode manually or automatically, and I am looking for some help from some of the DEV's around here.
When our TF's do this reboot, it is a system crash. When this happens, a ROMDUMP file is placed on the internal "sd card".
These can be viewed with a simple txt editor, like windows notepad. I myself can not read the code and understand what info it is revealing to me. According to an Asus tech on the phone this file can tell you what went wrong and made the device reboot. However the buggers won't tell you crap over the phone and want me to send the device in with the ROMDUMP files.
When I try and read the files, I do see one thing in common, in 99% of them, right near the end of the file, or the very last line before the crash, this line is present,
Kernel panic - not syncing: Fatal exception in interrupt
<2>[ 162.985309] CPU1: stopping
If our reboot issue is kernal based, which would indicate it's a firmware issue;
I was thinking one of the talented DEV's around here could fix us up.
Hell maybe even just a reflash of the current firmware would fix the issue.
Anyway, if a DEV around here want to or willing to look into this, I have some ROM dumpfiles they can look at, just send me a PM.
For reference,
I have a B60K modle
Stock 3.1
GPS 1.3.1
Wifi 5.1.42
BluT 6.17
Kernal 2.6.36.3-00001-gf377a2b [email protected] #1
Build HMJ37.US_epad-8.4.4.5.2-20110603
Thanks.
I don't have any more dumps recently, deleted them so I can't pull up and see what mine said to give you, but wanted to just say I was having these multiple times a day every day and it started once I bought an AData 16GB SDCard for the dock. Then I ended up removing that card and bought a MicroSD 16GB card instead and it has quit doing the random reboots, so definitely seemed to be something with my SDCard in the dock.
Post your whole log here (as .txt or .zip) and I will look at it.
I've had these once or twice but have always deleted the file.
The Kernel Panic is the kernel's way of telling you that something unrecoverable has happened and the integrity of the whole OS is in question. Think of a kernel panic like a BSOD on Windows.
I've never seen that specific one before, but a quick Google search indicates it may be a problem with I/O operations - like bad RAM or a bad SD card.
sassafras
Thanks for the response. I have included 4 RAMDUMP files. I find these 4 special because they all happened in quick succession. Four separate reboots all within 8 mins of each other without any interaction of the device myself. I never touched the device, I just sat there and staring at the device rebooting 4 times in 8 mins. On the final reboot the device never came back on. AT this point I picked up the device and had to hold the power button down for over 10 seconds for the device to come back on to an Asus splash screen. This was mins after I did a fresh factory reset via the OS options internally then a hard reset using the hardware buttons.
...It's a bug alright...
It doesn't seem to be caused by the same problem though, just that the watchdog program invokes a kernel panic and reboots. Weird. I'll backtrace it later and see what's up.
sassafras
went a whole day without a reboot. I did have an odd lock up/freeze at the lock screen where i couldnt unlock the device or get it to rotate the screen. It was locked up tight. Held hte power button down for 20 secs before it shut down. Rebooted, no new RAMdump created. No issues since.
sassafras_, Did you have any luck reading those ramdumps?
I did - sort of.
They're all related to the watchdog program assuming it's soft locked up. Which it may very well have been, but since you weren't using the device at the time, it's hard to know for sure.
The function's that were called immediately prior to the fault were different, which to me indicates that it's just buggy software. Honestly, without doing a backtrace I wouldn't know, but I can't without a system.map from around the time of the lockup. I'm going to assume it's just buggy code from 3.1 and wait and see if the 3.2 release lowers the rate of these. If not, then maybe I'll do some more digging.
sassafras
sassafras_ said:
I did - sort of.
They're all related to the watchdog program assuming it's soft locked up. Which it may very well have been, but since you weren't using the device at the time, it's hard to know for sure.
The function's that were called immediately prior to the fault were different, which to me indicates that it's just buggy software. Honestly, without doing a backtrace I wouldn't know, but I can't without a system.map from around the time of the lockup. I'm going to assume it's just buggy code from 3.1 and wait and see if the 3.2 release lowers the rate of these. If not, then maybe I'll do some more digging.
sassafras
Click to expand...
Click to collapse
Is there any progress on this issue? I bougth a brand new tf and during day random reboots maybe 50 times. And that romdumps are appeared on my internal storage. I dont have external sd by the way. Im stuck.
Hi.
Im having a same problem with my Transformer. Its a week old B60 and its reboots probably 50 times a day and give me log files.
Also im using Honeycomb 3.2
I really want to find out what is going on
i guess its a hardware issue or something.
i'm going to give back my TF today and take back a new one.
if i get same errors, i'll let you know.
I posted a workaround that helps immensely for rooted tablets somewhere around here. I can't find it tonight, but it's in one of the other 'random reboot' threads.
sassafras
sassafras_ -
Did you ever find anything with this issue? I am on my second TF and it is exhibiting the same random reboot while sleeping issue as the first. I know you have a post on another thread indicating how to tell the kernel to ignore "oops" conditions - have you received any feedback on how that is working? I assume this requires root access, I haven't yet rooted my device.
I have collected a few ramdump log files, but as of now only one out of 6 shows a kernel panic. I am new to Android, and I am trying to make sense of the dump logs. It appears that these dumps are maintained in a ring buffer, so the last entries are usually somewhere in the middle, is that correct? All of them also have some garbage at the end, but I assume that is just another effect of the ring buffer strategy.
Like I said, I am new to Android, but I am a long time embedded and real-time programmer, and pretty handy in Linux. It seems to me that the log files aren't providing enough information, but I'm not sure how to debug kernel/system crashes in Android. If anyone could point me in the right direction of where I should look next to get more information on these crashes, perhaps we could get to the bottom of this problem.
From what I can tell via the logs, when the TF is sleeping, it wakes up from time to time for various reasons, then suspends when it is done. It looks like it is during this wake/suspend cycle that something occasionally goes wrong and causes the tablet to reboot.
I am hoping that this is a software/firmware issue (or a hardware issue that can be worked-around with software), because I really like the TF platform and this issue makes keeping apps like IM or email running while it the device sleeps kinda iffy.
Any help from the awesome experts here at XDA would be greatly appreciated, and I look forward to learning more of the gory details and inner workings of Android.
I have had the same issues. Configuring the kernel to ignore oops only helped a bit. The tf would still freeze in standby eventually (once a day or so). My supplier (i.e. not Asus) replaced it and my new tf (a SBK v2 one, unfortunately) has not rebooted once in 2+ weeks. So my guess is that it was a hardware issue (memory, something not coming out of backup mode properly, ...?). Not sure if one could work-around it in software.
Now, this was probably not very helpful but I thought I'd share my experience here. And possibly my tf suffered from an entirely different defect, although the symptoms were the same (ramdump logs from random reboots in standby, independent from wifi on/off, sync on/off, and lots of other settings I tried).
flipflipflip -
Thanks for your reply! I was hoping that it wasn't a hardware issue, and since I got two in a row with the identical problem I was thinking that maybe a software fix could get around it. After reading about your experience, I went ahead and returned it and ordered another one from a different source. Hopefully the third time's a charm!
I'm keeping my fingers crossed that this one is not an SBK v2, but I'll be happy just to have one without sleep-apnea!
This did give me a chance to load up ADB and poke around a bit under the hood of the last one, so if nothing else it is a learning experience. Hopefully I will have something to contribute to the community once I get my hands on a working device.
I know it's been a while (had a big work-related headache), but just wanted to post and let people know that I finally received a TF101 (B50!!) that seems to be working just fine - so I guess it was just a combination of bad luck and a hardware issue after all.
The only issue I have now is that sometimes when it is sleeping, it loses its internet connection (it still seems to be connected to the AP) - but I think I can work around that.
Cheers!
I am glad to see there are at least four other folks about sufficiently embarassed to lead with their apology. Enough pleasantries:
I am capable enough to root my device but am careful enough apparently to avoid triggering inadvertent boot sequences, to wit: I have certainly dropped my Verizon-flavored S in bootloader a few times and with patience I was able to return to a normal boot sequence with no harm/no foul.
Today I forced my imac to serve up its wireless connection to my device via bluetooth (because I accept the fact I need Verizon's signal strength but I refuse to relinquish even one more dollar to them than I absolutely must so I loaded down with Google voice, etc. and EVEN THOUGH I OWN THE PHONE of course I cannot go prepaid and have a 4G connecetion),... I know, stream-of-consciousness is annoying but I am only trying to create a little background).
SO, my otherwise find rooted S, soon after but NOT immediately following my ham-handed creation of the imac connection share via bluetooth it went into the following boot sequence:
1.BOOTLOADER
2. bootloader "ends" and it begins to "charge" based on iconography
3. user grows impatient and, since it always worked before, tries to manually force a normal boot
4. Google icon appears, Stylized X icon appears, home screen appears for an instant and then the display immediately reverts to the X
5. Repeat 4 ad infinitum.
I recognize the fact that I really am not qualified to be a part of this discussion, but, I am self-taught and making sincere effort and my experience is that pros recognize that and will offer a quick work of advice.
My thanks to anybody that took the time to read this post, good evening from Georgia.
1. It's certainly not dumb to ask a question
2. Could you give some more info on you device, like which rom you're running and with which kernel? And maybe what recovery you've got installed?
Me Gusta!
First time poster, I apologize if this post is a mess.
I recently dropped my Droid Charge down a flight of stairs. The phone itself still seems to work - I can boot it up, it plays all the proper sounds, and my 7pm alarm even went off today (hadn't had it on to test that before), but the screen is completely dead.
I've already upgraded to a Galaxy Note 3. I had a backup with SMS Backup & Restore from April; same for my Checkbook app - these are the two apps I'm most concerned about. I'd like to get the additional data since April 22.
My Charge is rooted, though I got a lot of walkthrough to do it - I also did the root over two years ago.
I have these links in the chatlog with the friend who helped me root, if that helps at all:
http://forums.androidcentral.com/dr...charge-windows-drivers-w-direct-download.html
http://www.mediafire.com/?yn37uc4z3cx3bl6
http://rootzwiki.com/topic/10515-odinall-in-oneep4d-gingerbread-236-w-cwrimo-kernelrooted/
http://forum.xda-developers.com/showthread.php?t=1172182
Problem: USB debugging was turned off when I dropped the phone. I didn't know any better until I'd already broken the screen. I've tried MoboRobo, MyPhoneExplorer, and Samsung Kies, and nobody sees the phone. It beeps when plugged in, and with Kies the hard keys light up about ten-twenty seconds later, but that's the furthest I've gotten.
I'm willing to boot to recovery and use adb/command prompt/whatever, but I can only find these instructions for other phones, and I'm worried that if I use the wrong phone's menu instructions I'll end up wiping it instead of booting to recovery. I'm also not too clear on if ADB is a different build for different phones... this is my first time doing this.
I don't have a mini-HDMI cable but if that's the better solution I'll get my hands on one.
Any help is appreciated, thank you!
Hey there forums.
I've been an active browser of XDA but never really created an account but I've done so to have assistance with a particular situation with my device.
So the other week, i had spent 150 dollars on a Sony Xperia XA F3115 from Vodafone, Australia and it turns out that the bootloader was locked because of Vodafone and i wasn't going to pay 50 dollars to unlock it. I alternated and browsed the internet (Mostly XDA but other sources aswell) to figure out if there were any methods of bypassing this, whether it be easy or not - I was willing to try anything that seemed like it had a chance to work, without a 100% failure rate. Reading responses to particular methods, i was drawn into one method of just reflashing the stock firmware onto the device and then rooting, flashing and doing everything from there (as the device was no longer locked by Vodafone at that point).
I have completed this task as of this morning, and the device booted successfully. As soon as i unlocked my device, i had received the general android setup window but half way through, i got spammed with "Name has stopped responding" countless times to the point where the phone was literally unusable, it would just pop up again right after closing it - So i decided to restart the device. This was probably a big mistake, it booted fine but it said "Android is updating" and had the whole "Applications updating 100 out of 255" stuff happening. Then it booted to the lock screen, which i had previously setup before i flashed the device which didn't really surprise me too much.
Then it rebooted. Now every single time i boot the device, it reboots to the "Optimizing apps blah out of blah" and then will reboot upon the notification bar popping up, but no lock screen. I decided that my best cause of action was to download another firmware and try that one instead, but I'm unable to boot my device into bootloader mode as it's impossible to happen. I turn off my device, plug it in and hold the volume down button but it refuses to work anymore.
Now that the situation has been explained, I'd really like your help to see if i can have this resolved. I'm baffled as to why Vodafone even locked it to begin with, since the phone was prepaid and had nothing to do with any sort of plans - nor was it even available as a plan. I don't have the money to buy a new phone, and they have already denied me a refund. I need this phone for work and the mistakes i made were stupid - Please, i need assistance. You're all hopefully more tech savvy than i am in the field of mobile phones.
Over the past 1 year I have purchased a total of 7 Samsung Galaxy A32 5G. One for myself (Development) and one each for my children and wife. They were (are) decent devices for the price. I’m a licensed Android Developer (among a-lot of certs and licenses) and I have tried everything. I explain this so we can skip the basic concepts.
One night one of my device wouldn’t charge properly (no water damage) I turned it off to see if it charges correctly while off.
Instead the device enters a boot loop. I noticed an error on the bottom. Seems like it said “Kernel Dump” or “KDump” but the message was too fast to read. I even attempted taking video and pausing it on that frame but it was so quick it’s blurry. I was able to read it a bit better though and It does look like it says Kernel Dump (kdump) though. I can boot into Download Mode , I cannot boot into recovery or Fastboot however. I have tried many options (Kies , Odin) and while Odin is absolutely 100% completing successfully with no issues the device continues to go into a boot loop and show this Kernal dump. . I know Linux in general has a Kdump which creates a log when the Kernal crashes. Naturally I can’t think of a way to see that log. Is there something I’m missing? Is there a solution that works?
Thank anyone for any suggestions.
Innovatorsww said:
Over the past 1 year I have purchased a total of 7 Samsung Galaxy A32 5G. One for myself (Development) and one each for my children and wife. They were (are) decent devices for the price. I’m a licensed Android Developer (among a-lot of certs and licenses) and I have tried everything. I explain this so we can skip the basic concepts.
One night one of my device wouldn’t charge properly (no water damage) I turned it off to see if it charges correctly while off.
Instead the device enters a boot loop. I noticed an error on the bottom. Seems like it said “Kernel Dump” or “KDump” but the message was too fast to read. I even attempted taking video and pausing it on that frame but it was so quick it’s blurry. I was able to read it a bit better though and It does look like it says Kernel Dump (kdump) though. I can boot into Download Mode , I cannot boot into recovery or Fastboot however. I have tried many options (Kies , Odin) and while Odin is absolutely 100% completing successfully with no issues the device continues to go into a boot loop and show this Kernal dump. . I know Linux in general has a Kdump which creates a log when the Kernal crashes. Naturally I can’t think of a way to see that log. Is there something I’m missing? Is there a solution that works?
Thank anyone for any suggestions.
Click to expand...
Click to collapse
Have you tried booting in to safe-mofe or adb booting an image, a/b slots, etc. Make sure clear data (sucks)
Not much help, I'm sure you've covered all this, and well, the basics. Good luck
I had the same issue with my A32 5G and i found a solution to this. Plug the phone in and make sure it is charging and then power it on and set it aside and let it go into the boot loop. (plugging it in is to ensure it wont die) Eventually, after a few hours, the boot loop will stop and the phone will open android recovery and allow you to facotry reset the phone. After the reset it should boot again. Not sure what the exact cause of this is but this is what worked for me. Good luck!