Related
My phone has reboot a few times since ive purchased it, on active phone calls, twice today alone. I have a feeling its a software compatibility issue with one of my apps, but i just wanted to see if other people have experienced this, and any advice before i try a factory reset.
My phone is not rooted. It has the latest OTA update. When i first booted phone, it did a google backup
My other question was on the NFC. When i have NFC checked in the wireless area, it works great. But as soon as i turn it off, and try to turn it back on, it gives an error code. It wont turn back on until i reboot the phone, and than it checks just fine again until i turn it back off. I played with a phone at BB and it gave an occasional error when i cycled the check mark fast, but it always corrected the error eventually. This is probably another software bug, but just seeing if anybody else is experiencing this.
If i reset my phone, i will lose all my save game data correct?
My Nexus S is also resetting during phone calls, four times in a row now.
Is there any news on this issue?
http://forum.xda-developers.com/showthread.php?t=880497
I just reported rebooting issue to the Google. Please add your comments and star it, so Google will be aware of the problem and start fixing it!
http://code.google.com/p/android/issues/detail?id=13674
I exchanged the phone, and it was great for a week or so, but just tonight reboot twice during an active calls. I suspect it to be some sort of software bug, but, I'm most likely going to be exchanging it again. Works great until you need to use the phone as a phone, than it doesnt work.
Psosmith82 said:
My other question was on the NFC. When i have NFC checked in the wireless area, it works great. But as soon as i turn it off, and try to turn it back on, it gives an error code. It wont turn back on until i reboot the phone, and than it checks just fine again until i turn it back off. I played with a phone at BB and it gave an occasional error when i cycled the check mark fast, but it always corrected the error eventually. This is probably another software bug, but just seeing if anybody else is experiencing this.
Click to expand...
Click to collapse
I can recreate this problem as well, and was a major concern for me (didn't want to have a defective NFC down the line when/if it becomes common use). After speaking with some people over at Android Central, one of the editors had this to say:
"Yes, if I toggle the NFC switch enough times I will see the error notification. It still works as intended though. Looks like there is a "cool down" time on the NFC hardware, and messages to the kernel are getting picked up as errors. Either the filter needs tweaked (the filter that reports kernel messages) or the output from the NFC hardware needs "re-worded"
Makes sense to me. I wouldn't worry too much about it. However, I did create a report to bring to Google's attention, if you feel like starring it: http://code.google.com/p/android/issues/detail?id=13581
Hi, I have a g1 that has suddenly stopped working - when I start it I see the t-mobile screen and then it switches to the android screen and just stays like that and doesnt start.
It stalled while making a call and I was not able to restart it.
I have tried wiping everything from recovery console (http://forum.xda-developers.com/showthread.php?t=566669) and re-flashing my phone with my old firmware (http://forum.xda-developers.com/showthread.php?t=811620)
I don't know what's next here - can anyone please help?
some more background:
I had the phone for two years here in the US and have traveled out side of the country with it for several trips with no problems whatsoever, however, this phone I have given to my niece who doesnt live in the US.
The reason i'm saying this is that maybe the cause is a radio problem of some sort...
Let me know if you think of something coz I really don't know what do to next
Thanks,
e.
First of all, wrong section.. (Please post in Q&A)
If you had poked around and used the search feature, i'm pretty sure you can find what you are looking for
but anyhow, you need to flash another rom (via recovery) assuming you have already rooted because you somehow corrupted the system partition.
Thanks for the reply, I tried using cyanogen's mod but it didnt get me anywhere, I will try different mods but could this be a radio issue? is there a way to check that?
p.s. I did a thorough search of the forums and that's how i did all the things b4 posting but then I got stuck...
Hi, sorry I posted in the wrong section, just noticed what you mean.
Can any of the admins move this thread to q&a (or can I do it myself somehow)?
Data?
eladkatz said:
Thanks for the reply, I tried using cyanogen's mod but it didnt get me anywhere, I will try different mods but could this be a radio issue? is there a way to check that?
Click to expand...
Click to collapse
My friends phone is doing something extremely similar. He gave it to me to play with to make sure he wasn't mad, and it was actually the phone having issues.
Upon playing with it for a few hours problems started to occur. It would randomly shut off, then not want to reboot unless left sitting. It would get after the ROM screen and then shut off. I noticed that that a quick was to crash it was to start browsing the Internet over Wi-Fi. After a few pages loading and moving around the pages as they loaded the poor phone would just turn off.
Since he is using another phone in the mean time, I got his G1 without a SIM card. I was playing games on it, poking around in applications and more and the phone wouldn't turn off. I wasn't till I enabled Wi-Fi that problems started happening. I'm not sure if the Wi-Fi driver is part of the baseband unit or not but it seems that the more data the phone uses (3G or Wi-Fi) heightens its chance of turning off.
To get the phone to boot again I either have to take the battery our for a few minutes or leave it off for a while. Upon which time it will book as if nothing happens.
I also noted that every time it boots it shows an exception error related to "gapps" and you have to click force quit. His phone is running CyanogenMod 4.2. Also the Home key doesn't function, but this is software related because it can turn the screen on.
Scott
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've been on Humble 1.42 for about a month now (please don't look down on me, haven't had time to switch since the drama) and I am starting to have some issues with my phone not waking. At random moments, my screen would refuse to turn on no matter what I do. It does, however, respond to me holding down the power button for a forced power off (hard reset?) Anyhow, has anyone else experienced this at all? I had a feeling it was my xfinity mobile app because I had been getting a lot of errors from it lately even though I rarely ever use it. Should I just switch to another rom or is there any other apps known to cause issues with this rom that I should be aware of?
On a side note, I have been on this forum and obsessed with android for the past year and been doing some serious thinking about making a career change into Android development. Been doing some java tutorials on youtube over the last few months and the such and think I'm about ready to start some real android app development. I credit some of the great developers on this site and the awesome experience at Dreamforce this week as the tipping point. Any ideas on additional resources I should look into?
There are a few things that could be causing this problem(that I'm aware of)
1) You may have sideloaded a "virus" app. I attempted to sideload an app once(will never do it again after what happened..) and it completely BROKE my phone. It made apps unable to isntall, the screen would take FOREVER to wake(if it ever did wake) and plenty of other problems. I tried rebooting and got stuck in a bootloop(boot animation would never end), did a factory reset and everything force closed on me so I was forced to flash the .md5/.pit to go back to bare stock and that finally fixed it.
2) Have you flashed Fuju Tweaks? This exact same thing happened when I flashed it on Gummy2.0, worked fine on Eclipse1.3.1 and even works for a lot of people on Gummy2.0 but it wouldn't work for me.
3) Try reflashing your ROM, that's how I fixed the Fuju Tweaks problem. It might fix whatever plagued your phone.
Just let me know of anything you've done recently and I'll try and diagnose the problem(if I didn't already).
Uh-Oh, a virus maybe? Yeah, I will just reflash later on, and change some passwords while I am at it.
I don't think it was that kind of virus but it definitely screwed up my phone.
Ok, so as the title says, I'm looking to completely undo having rooted my tablet, and all the customization I did to it, but I'm having a bit of trouble.
According to multiple apps my tablet is no longer rooted, and I got the stock rom from Sammobile flashed on it, and I have the stock recovery back, but I seem to be suffering from the wifi problem that CM suffers, I know this as I can connect to my 5G wifi as well, which I'm never able to do when the tablets wifi is working correctly, and also even connected I barely have any speed, if even any.
Now I know of the wifi fix you can flash through TWRP, but as I said, no more TWRP, and I don't want to reinstall it, I want everything back to stock.
Now, I know of Wifi Fix's for other tablets, like the Galaxy S4, that you can flash on with Odin, but I can't seem to find one like that for the Note Pro 12.2. So if anyone can send me a link I'd really appreciate it.
And also, I can't remember, but did the Note Pro 12.2 ever get anything higher then Android 5.0.2? Because I try to update it, and it says because my tablet was modified I can't do so. Plus Sammobile doesn't have higher then 5.0.2 but I read somewhere that it got 5.1.1 so I really don't know, any help on that front as well would be great.
Now, you may be wondering why I want to do this, in truth I'd rather have my tablet rooted, I save so much battery life getting rid of all the bloatware. But no matter what I do, there always ends up being a problem with my tablet.
I follow all the instructions given, I do exactly what everyone else does, even having someone walk me through it step by step once, and always it goes horribly wrong.
The first time my Nova Launcher would crash constantly, and then everything else would start crashing with it. Then the second time all my videos would play stuttering and jerky, and the audio would be out of sync horribly, and nothing I did would fix it. And now most recently, even though the tablet it connected to the computer, the drivers always fail installation, and even when they are successful, I'm still unable to actually access the tablet from my pc.
I read somewhere that it may be because I disabled Media Storage, but with Media Storage I have just as many problems, it drains my battery like crazy, it causes things to load up extremely slow when accessed through the computer, if a folder has a hundred files for example, it will take almost twenty minutes for them all to load up, and you can't do anything until they do, and if you try copying something into a folder without going into it you'll just be stuck in an endless loop of copying that never ends.
But without Media Storage everything loads up just as quickly as say an SD Card, so said 100 files only takes a few seconds.
And worse thing it caused, which troubled me for a long time before I found out what caused it, at random the media storage would decide to claim 20gb's of space, saying it was all taken up, when it isn't. And it would keep happening at random times, and at random sizes. Near the end it had taken up every bit of free space I had and didn't change back even after several days which is what led me to looking up what was causing that in the first place.
So as you can see, leaving Media Storage enabled is a big no for me. So as such I'm unable to root and customize my tablet for that reason as well.
Now, before you say how weird it is that I have such trouble, and how you have no idea why it would happen, there is a very key reason, Technology HATES me. Trust me, more often then not when I try to do something that works for literally everyone else it fails for me, like say connecting an Xbox controller and getting it to work on my pc. Yeah, never works even after almost 5 hours of trying. So yeah, technology hates, maybe even dispises me.
So anyway, if you can help me fix the wifi, and the update problem if that's possible, I'd really appreciate it.
Are you able to get it connected to a PC?
There are tutorials on how to go back to complete stock if you haven't tried Knox I might search for what people have done before they take the their device back to the carrier. Many people want to un-root before they give up their old devices.