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!
I have a samsung galaxy tab 2 7inch that is rooted and running a cyanogenmod 11(i think) nightly. So here's the story:
I was looking on google for a way to shut down my tablet through adb and came across "adb shell halt". After typing this, the screen immediately turned off and would not turn back on. After google searching I only found one person with the same problem. Looking into the "halt" command a bit more, I've learned that apparently it forcefully shuts down the Zygote which causes the Android system to forcefully close everything without giving anything a chance to save. Apparently the only thing left active is the Linux kernel, or at least that's what I've read. It's said that a battery pull can fix this, however I've repeatedly removed the battery, waited 15 minutes (and once overnight) and put the battery back in, only to constantly have the same result; it simply won't turn on, or at least show any signs that it is on. I've seen people saying that "adb shell start" will restart it, but I can't reconnect it to adb, I've tried several times. The only other thing I have seen is to mod the board and solder a chip to test pads that will allow me to communicate with the Linux kernel, but I'm hoping that there is another thing I can try first. If anyone can help me, I would REALLY appreciate it.
the100guy said:
I have a samsung galaxy tab 2 7inch that is rooted and running a cyanogenmod 11(i think) nightly. So here's the story:
I was looking on google for a way to shut down my tablet through adb and came across "adb shell halt". After typing this, the screen immediately turned off and would not turn back on. After google searching I only found one person with the same problem. Looking into the "halt" command a bit more, I've learned that apparently it forcefully shuts down the Zygote which causes the Android system to forcefully close everything without giving anything a chance to save. Apparently the only thing left active is the Linux kernel, or at least that's what I've read. It's said that a battery pull can fix this, however I've repeatedly removed the battery, waited 15 minutes (and once overnight) and put the battery back in, only to constantly have the same result; it simply won't turn on, or at least show any signs that it is on. I've seen people saying that "adb shell start" will restart it, but I can't reconnect it to adb, I've tried several times. The only other thing I have seen is to mod the board and solder a chip to test pads that will allow me to communicate with the Linux kernel, but I'm hoping that there is another thing I can try first. If anyone can help me, I would REALLY appreciate it.
Click to expand...
Click to collapse
Can you get into recovery or download mode? can you get your device to connected to pc via adb? if none of these, then that's the only way my friend.
Seems like i have same problem.I also had cyanogenmod11 runing for like 3-4 months before it simply...died 2 days ago.It does not respond to any charger/usb/ car charger/ battery pull. Even tried to power the motherboard on without any daughterboard connected.Still dead.
It's a P3110 (wifi).Any suggestions?Thanks alot, i can and i'm willing to try anything that does not include desoldering/soldering chips.Thanks alot
I've had my Oneplus One since the beginning of 2015, up until now it's been honestly fantastic, with very few issues whatsoever, certainly nothing that has bothered me at any rate. That's up until last night;
My phone was lying on my desk next to me with the screen on updating some applications whilst I was writing on my computer - suddenly, it starts to vibrate, one continuous long note, I naturally picked it up and looked at it, at which point the phone turn itself off in my hand. That was unfortunately the last I ever saw of my phone alive. This happened at about 6PM yesterday evening, since then I've tried everything within my power to get it to work. I can't access the bootloader, in order to get to fastboot (which would allow me to fix all my issues by enabling me to refresh the device), nor can I access my recovery. The phone turns on and displays nothing, it vibrates, but that's it.
The phone was running the latest COS13.1.1 update (X1) which I had flashed the day before, it was running the stock kernel for the ROM, the ROM was however rooted.
I know a fair amount about android, I also know a fair amount about the OPO, to me, I think something about the LOGO partition has gone wrong. The LOHO partition being responsible for the images shown in the bootloader, fastboot, splash screen etc.... I'm just not sure how that would have happened.
Either way, I don't know what to do, the one doesn't register to my computer in fastboot or adb , so both those routes seem closed. I primarily use a Mac for my work, I'm yet to try plugging the phone into a PC.
I've submitted a ticket to OP, and have spoken to an adviser who moved my case to a 'specialist', but I'm yet to hear back on that one.
Any help would be massively useful, because I need this phone for my work, and just general communication.
Thanks for reading,
Ben
Here, try this http://http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732
Hello, not sure if this is the right thread to be posting this on but here goes...I am trying to root my phone mainly because I want to open up more resources, get rid of certain programs, try out new rooms and I'm interested in development. But another more pressing reason now is because I believe my phone has been hacked. It, along with the last few phones I've had (I've been changing phones to run from whatever is happening.) changes security settings on it's own, goes through batteries way to quickly and uses data when it shouldn't be. Certain options in settings have been grayed out and others keep getting switched back from where I put them. I absolutely cannot run adb because I cannot get my computer to recognize them. I can't run adb over WiFi either. I've tried different computers, operating systems and everything I know to do. I've spent weeks (literally weeks) trying different suggestions from different websites and tutorials and nothing works. I've used Windows, Linux and OSX. I even payed one click root to do it and they couldn't either. I've been looking at what logs and other info I can get from apps but it's limited info because I don't have root. I have read some manifest docs and even though I'm a noob they just don't sound right and certain apps permissions are way out there. I've checked call logs through two carriers, T-Mobile and now Verizon and both indicate that my phone is sending back to back texts and making phone calls that I didn't make. And I mean a lot of them. I've even made it a point to leave my phone at home all day and not use it and my call logs have still indicated usage. I really need some help...I don't know what to do at this point, I feel defeated, angry and frustrated. I believe that it has something to do with firebase and possibly my ex-wife. About a year ago I found an .apk file in her Google drive called ( truthspy.apk ). I did some research and it wasn't good. This was like 5 phones ago and she hasn't had physical access to my last few phones. I'm not sure what's going on but I know for a fact something is going on and Im respectfully requesting someone's help. Is there something that I can do like invoke a log or bug report or go somewhere and take a screen shot to someone something that they would be able to look at and tell if it wasn't right or that something was going on?
Thanks.
Sent from my Nexus 6P using Tapatalk