Related
My phone decides to reboot and or power off randomly and for no apparent reason. It's just sitting on my desk. Anyone else experience this issue?
Guess i'll try a reflash if this continues.
yep
+1
Not very often but very annoying if you use your phone as alarm clock.
I honestly haven't experienced either with my SGS. I can sympathise though as my Milestone used to do both way too often (hence swapping for the SGS).
It hasn't happened to me.. It might be running a software or hardware watchdog to reboot automatically when the system panics. Ensure you are using a stock rom, otherwise, it may even be faulty hardware
Would happen several times a day on my Motorola Milestone so I sent it back and got the SGS. Totally rock solid. Only time it reboots is when I want it to. Maybe you have a rogue app?
you guys have any changes to the CPU speed whatsoever, task killers and all? i once used SetCPU and it sort of sent me into a random spree of reboots and such.
i remember rebooting, scanning 10gb of media, auto-reboot... repeat 4 times. lol.
Well it hasnt happened since yesterday. I will flash to froyo today just in case it was software related
Sent from my GT-I9000 using XDA App
dakine said:
My phone decides to reboot and or power off randomly and for no apparent reason. It's just sitting on my desk. Anyone else experience this issue?
Guess i'll try a reflash if this continues.
Click to expand...
Click to collapse
did you see the topic on the DEV forum about Resetting the battery status?
seems like the phone (not the battery) keeps a wrong battery status if you flashed it a few times
so even when you still have battery, the phone "thinks" it rans out of juice and it does that thing you mentioned
AllGamer said:
did you see the topic on the DEV forum about Resetting the battery status?
seems like the phone (not the battery) keeps a wrong battery status if you flashed it a few times
so even when you still have battery, the phone "thinks" it rans out of juice and it does that thing you mentioned
Click to expand...
Click to collapse
Link would be helpful, because I can't find that topic.
WOW, old thread that got dug up, for me it was just a software issue. I flashed many roms since and haven't had it happen again. I never reset my battery stats but I think clockwork mod recovery has an option to do that so most of the custom roms make that easy.
I also had random reboots and power-offs, on average once every 2 weeks, running on stock-firmware JF3. Problems did not go away when I manually upgraded to JM2. Problems stopped when I upgraded to Froyo...
So does EVERYONE has this problem? Is it a software problem?
I'm running on CM7 RC1 with Netarchy 1.2.4, reboots quite frequently, and it's annoying. Just had another odd bug, phone froze and wouldn't turn on and vibrated non stop for 30 seconds. Phone is buggy when ending a call, it freezes a lot at that point too, anyone else having these problems?
I called today the customer service of my carrier "oi" and I spent kinda 30 minutes talking, trying to solve a problem.
When I saw, my phone was in a bootloop with the cyanogenmod boot and I was continuing to talk, without any interrumption.
The only difference was thet the phone was hot!
Running at 1.4 with the last netarchy kernel my max was 38!!! (low)
Random reboots are a S/W problem, Google is aware of the issue and will be pushing out an update that fixes the problem.
there is nothing your carriers can do about the issue
slowz3r said:
Random reboots are a S/W problem, Google is aware of the issue and will be pushing out an update that fixes the problem.
there is nothing your carriers can do about the issue
Click to expand...
Click to collapse
I hope so!
Serious_Beans said:
So does EVERYONE has this problem? Is it a software problem?
I'm running on CM7 RC1 with Netarchy 1.2.4, reboots quite frequently, and it's annoying. Just had another odd bug, phone froze and wouldn't turn on and vibrated non stop for 30 seconds. Phone is buggy when ending a call, it freezes a lot at that point too, anyone else having these problems?
Click to expand...
Click to collapse
Just a couple of questions. Are you using a frequency changer app example, setcpu cpu tuner? Do you have the set on boot checked for main profile? I have found if the set on boot is check to have random reboots on calls. I uncheck and no longer have the reboots on calls. That was the only time I ever had the reboots happen. Just a question and something to check in your settings.
Serious_Beans said:
So does EVERYONE has this problem? Is it a software problem?
I'm running on CM7 RC1 with Netarchy 1.2.4, reboots quite frequently, and it's annoying. Just had another odd bug, phone froze and wouldn't turn on and vibrated non stop for 30 seconds. Phone is buggy when ending a call, it freezes a lot at that point too, anyone else having these problems?
Click to expand...
Click to collapse
Your running netarchy 1.2.4 which is still in its test phase. That's where your issue is. If you switch to a more stable one then you should be fine
Sent from my Nexus S using XDA App
No random reboots here, got it on the 3rd. Phone runs smooth as silk. I'm on stock 2.3.2. Out of all the phones I've owned this has been the most stable.
Could my phone possibly be from a different batch? I'm not experiencing any of the issues alot of other people are besides 100% init process, which I solved with keeping USB debugging on.
Sent from my Nexus S using XDA App
ruben8448 said:
Your running netarchy 1.2.4 which is still in its test phase. That's where your issue is. If you switch to a more stable one then you should be fine
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
I don't think it's the kernel, even stock users have the reboot problems.
I don't have any such problem on Cyanogenmod 7 rc1...
iKitsunee said:
I don't think it's the kernel, even stock users have the reboot problems.
Click to expand...
Click to collapse
We get random reboots from time to time but with the freezing and all the other issues it sounds like the kernel. I tried that kernel and I had the same issues. I just switched to 1.2.2 and I was good to go
Sent from my Nexus S using XDA App
ruben8448 said:
We get random reboots from time to time but with the freezing and all the other issues it sounds like the kernel. I tried that kernel and I had the same issues. I just switched to 1.2.2 and I was good to go
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Ah, I'm actually using that kernel as well, hasn't happened to me but I suppose it might vary from phone to phone.
jerrycycle said:
Just a couple of questions. Are you using a frequency changer app example, setcpu cpu tuner? Do you have the set on boot checked for main profile? I have found if the set on boot is check to have random reboots on calls. I uncheck and no longer have the reboots on calls. That was the only time I ever had the reboots happen. Just a question and something to check in your settings.
Click to expand...
Click to collapse
I have it set on boot,but I'm running at stock speeds. I am not overclocking and still having these problems. I'm going to try a bunch of other roms and kernels and see what my results are, it COULD be the phone it self, but I doubt it.
And thanks everyone for all the responses.
Serious_Beans said:
I have it set on boot,but I'm running at stock speeds. I am not overclocking and still having these problems. I'm going to try a bunch of other roms and kernels and see what my results are, it COULD be the phone it self, but I doubt it.
And thanks everyone for all the responses.
Click to expand...
Click to collapse
The kernel is set to default at stock setting so no need to have it set on boot. It isn't going to overclock unless you raise the cpu past 1g
google have already said that the problem its just s/w and they are going to fix it with an update and it's not the new 2.3.3! Hope it don't take much longer!!
Sent from my Nexus S using XDA App
There is a stock kernel for cm7 out that has all the voodoo engagement and ext 4 hack
I've had random reboots and it only happens to me when I'm using bluetooth.
Sent from my Nexus S using XDA App
its been over one month now and i never had such problem with mine..its running smoothly both with stock and cm7..
I experienced my first random reboot today. Installed clocksync and was fine. Today I loaded the app... screen was blank then saw the boot animation.
Sent from my Nexus S
I experienced 2 reboots in a row trying to retrieve a service from my mobile operator. I got so frustrated ´cause the mobile operator service takes too long,
the last time I looked, elapsed 7 minutes, few minutes later, reboot...
Became afraid to call again from the nexus, not trusting anymore
wifi on, sync on, bluetooth off, gps off, it was charging with the regular charger, factory rom and kernel, not rooted, launcher pro
I also have random reboots. it's strange though, it goes to the boot animation for some time, looks like the phone reboots, then all the apps and launcher is reloaded, but if you check the phone boot time under settings -> about, the uptime is not reset.
can you guys confirm that your boot times are also no reset during the randon reboots oft he known google android software issue for nexus s?
thanks,
Does anyone have a logcat from their dead transformer, during/around the time when it died?
Has anyone noticed any trends in when it happens? I saw something about 82% battery but I think that's just a coincidence.
Please post here so we can get to the bottom of this.
Jcarrz1
I think this is dev, unless it's a hardware issue. But hopefully we'll be able to discern that.
I have had multiple sleep of death issues after rooting. When I flashed back to the stock Blob, they stopped. Every time I root to Blob V5 (I am on the most recent firmware), they come back. I tried MoDaCo's Rom - they still occurred. Trying Prime's Rom now - so far it's working without any sleep of deaths.
I was on MoDaCo's Hr4 for a few days and never had a sleep of death. Since installing Prime 1.2 I've had 3 or 4.
Since we've had completely opposite experiences I think we can safely rule out that this issue is ROM related.
I've used both those roms and never had a sleep of death. But I also used the root method without the v5 blob, just the standard GingerbreakBB.
I've had one sleep of death incident, using unrooted stock Transformer configuration.
mine case: downgrade back to 8.2.2.6 using SD method (EP101_SDUPDATE.zip) then Gigerbreakbb then the BLOBV5 => lots of SOD issue.
May be we must update to the latest 8.2.3.9 before break using gingerbreakbb and install BLOBV5?
BR
Blob 5 is made to work with 8.2.3.9... It will most definitely have issues with the old firmware.
I am beginning to think the issue is with one of my apps and its settings. When I am rooted, I use Titanium Backup to restore my data and maybe the reason for the SOD is because something in an application isn't playing nice with Honeycomb... Obviously when I am not rooted, I cannot restore the settings and thus no SOD.
I just flashed back to root with Blob V5. Going to see if there are any SOD issues before installing apps... Will probably install one by one to try to see if I can find the problem - A PITA, but I really want the SOD to stop.
Had it with latest asus Update, no root and 40% brightness + wifi sleeps while screen is off. Lockscreen was enabled.
Sent from my Nexus One using Tapatalk
Edit:
Had another one after changing wifi sleep policy. I think it is wifi related.
The-Nazgul said:
Had it with latest asus Update, no root and 40% brightness + wifi sleeps while screen is off. Lockscreen was enabled.
Sent from my Nexus One using Tapatalk
Edit:
Had another one after changing wifi sleep policy. I think it is wifi related.
Click to expand...
Click to collapse
Other threads are pointing to the WiFi scanning be enabled. I have flashed back to MoDaCo Hr4 (because it was more stable for me than Prime 1.2) and also disabled WiFi notifications and will report back if/when I get a SOD.
Unrooted, getting about one or two of these a day depending...... seems to happen more if I've left it sleeping for an hour or more.
Putzy said:
Unrooted, getting about one or two of these a day depending...... seems to happen more if I've left it sleeping for an hour or more.
Click to expand...
Click to collapse
this could relate to wifi scanning as well. were you connected, and what are your current settings?
Thanks for participating everyone, so far there isn't a conclusive answer.
However, could someone install log collector from the market, and leave it there until the BlackSOD happens, and then upload the file? that would be super awesome. preferably someone who gets them all the time. if the last thing in the logcat is consistently wifi-related, then we're on to something.
is there any firmware version on which NOBODY has EVER had a BlackSOD? This could be worth looking in to as well.
Well, I rerooted and have installed about 80% of my apps. So far no SOD. I have a few more apps to install and I usually freeze some of the unwanted apps. Will post an update later. Also, I read on other forums that fancy widget caused issues like this on other tablets. I had been using beautiful widgets I wonder if the way that tries to access wifi causes issues.
The apps I have yet to install are:
Watchdog lite, beautiful widgets, adfree android
Sent from my Transformer TF101 using Tapatalk
Just had one while wifi was disabled! I guess that makes it less likely that wifi causes the problem.
Next time I will upload a logfile!
Sent from my Nexus One using Tapatalk
I've had 2 so far, both with Hr4 and blob v5. Battery has been at different levels, so I think thats a coincidence.
Has anyone tested on a 100% Factory reset device (either with a custom or stock ROM?) That should help rule out any apps which may cause the problem.
FWIW, never had this issue (have run Stock, HR1 -> HR4 & Prime V1.2)
so far no SOD after a clean tstart
Had a SOD this morning on Hr4 so I will run Log Collector today and hope to catch another. I'm assuming that Log Collector is continually writing to my Gmail draft so it should be there after the full reboot? Doesn't seem like it will let me mirror logcat to a file on sdcard...
sent from a device using an app
I realize this isn't the least bit helpful, but after having several SoD issues, and trying all the fixes (and then undoing them), I haven't had the issue for a week now. Mine would do it sporadically -- it would happen once in a day, and then 3 times in a day -- and the only thing I've left changed is disabling the lock screen, but I think that's just coincidence. This will be a hard one for Asus to nail down.
Hopefully someone produces a helpful log for Asus, I'm sure some non-XDA people may think they have a dead tablet rather than one they have to force power down and reboot.
had my firs SOD today.
running prime 1.2 US. battery at 96%. wifi on.
spuniun said:
Had a SOD this morning on Hr4 so I will run Log Collector today and hope to catch another. I'm assuming that Log Collector is continually writing to my Gmail draft so it should be there after the full reboot? Doesn't seem like it will let me mirror logcat to a file on sdcard
Click to expand...
Click to collapse
So it does not seem that this app will work because it only collects logs in real-time, does not store them for later analyzing. What else can I use other than leaving adb logcat running?
sent from a device using an app
I have done countless searches and tried everything I possibly could to find a solution to my problem and nothing has worked.
When running any 4.4 rom, and I have tried pretty much all of them, I have this wifi issue. The problem is that if I have wifi turned on the phone starts randomly rebooting approximately every 15-20 minutes when the screen is off. I have tried every setting, upgraded and reset my router(dd-wrt) with different settings and a static ip, and tried different apps that are supposed to help with wifi issues.
This does not happen on stock roms and I have zero issues with any other devices on my network. The very limited amount of info any where that I have found with a similar problem all lead to dead ends. This happens regardless of being a fresh install with no apps installed besides gapps. I really just can not think of anything else to try. Please help me with my G2, I really want to like this phone. :crying:
From the complete lack of info I am able to find on this it would seem to be quite a rare problem. But if anyone has any suggestions for me I would really appreciate it.
No suggestions at all?
Mine is doing this too, however not as frequently. Are you using a proxy app? And do you have auto-wifi disconnect on?
It has nothing to do with the router. I'm 99.9% sure it's either a rogue app or a bad install.
greydelta38 said:
Mine is doing this too, however not as frequently. Are you using a proxy app? And do you have auto-wifi disconnect on?
It has nothing to do with the router. I'm 99.9% sure it's either a rogue app or a bad install.
Click to expand...
Click to collapse
No I'm not using any proxy apps or disconnect. It's not an app or bad install as far as I know. Like I have said this has happened with every install of any 4.4 rom that I have tried. Including, PA, CM and Mahdi. When installing any rom I always do a full wipe, cache, data, dalvik and system. Even without out installing anything besides gapps it happens. So I think I can rule out a rogue app or a bad install.
I have reinstalled countless times and it always pops up. On occasion there has been instances where the problem does not start for several hours after a fresh install but invariably the issue does come up and the reboots start again every 15-20 minutes when the screen is off.
I mentioned the router because, although rare, they can cause issues with connecting devices. Most of the problems that I have read about is usually the other way around though. The router crashing with certain devices connecting to them. But I have had zero issues with my router and any other devices but still thinking it could be possible.
I have a 4.2 rom(Energy) installed currently with no issues whatsoever. It is only KItKat that seems to be a problem. I just have no idea what it could be.
What model is your g2 and kernel? The only thing I can think of is you are changing sleep tweaks on the kernel and causing it to sod when in deep sleep. Are you undervolting?
greydelta38 said:
What model is your g2 and kernel? The only thing I can think of is you are changing sleep tweaks on the kernel and causing it to sod when in deep sleep. Are you undervolting?
Click to expand...
Click to collapse
It's the d801. Every kernel on every rom. I have tried using kernels as is or using Trickster to undervolt, overvolt, you name it, I've tried it.
Any other suggestions?
Project X-Ray said:
Any other suggestions?
Click to expand...
Click to collapse
Make a backup and wipe everything, and boot up into a totally clean rom WITHOUT installing Gapps for it. Then see if it keeps happening. I'm searching around and not really finding anything on this issue. Mine hasn't been doing it since I flashed the new AOSB build
greydelta38 said:
Make a backup and wipe everything, and boot up into a totally clean rom WITHOUT installing Gapps for it. Then see if it keeps happening. I'm searching around and not really finding anything on this issue. Mine hasn't been doing it since I flashed the new AOSB build
Click to expand...
Click to collapse
Well I took your advice. I wiped everything and did a fresh install, latest PA without gapps.The only thing that I have done is connected it to my wifi. I let it go for about 3 hours and had no reboots. So I installed Banks Core gapps. Again, I let it sit for 3 hours. No reboots. All the while it has been plugged in and charging. As I write this, I just unplugged it from the charger and within 2 minutes had my first reboot. We'll see if they continue.
So now, I wiped and reinstalled PA without gapps. I did not install anything else at all. Turned on wifi and started getting at least 2 reboots per hour without even using the phone at all. When I turned off the wifi it has been running for 10 hours now without any reboots at all. I am at a complete loss as to what could be the problem. Is there anything I can do?
Project X-Ray said:
So now, I wiped and reinstalled PA without gapps. I did not install anything else at all. Turned on wifi and started getting at least 2 reboots per hour without even using the phone at all. When I turned off the wifi it has been running for 10 hours now without any reboots at all. I am at a complete loss as to what could be the problem. Is there anything I can do?
Click to expand...
Click to collapse
I hate to say it, but I'm at a loss too. Best course of action I can see is for you to return to stock, email LG, and ask for a replacement for a defective device.
Since 20140415 nightly update (installed via CMupdater) I'm experiencing the Phone Problem. The translated German text would be
"there was a problem with your phone's modem, the device needs to be rebooted..."
I've had those before, but to a small extend. Now it's more like: it takes around 30 Minutes from reboot until the "Problem" reappears.
I'm sorry, I cannot post to the dev-thread, yet. If any logs are needed, I'd update back to 20140415 or 20140416 (where this also happened) and try to grab'em.
EDIT: it might be important information: I've come from the "full" nightly "11-20140407-NIGHTLY_mb526", then used cmUpdater on the 14th, the 15th and the 16th April (so: the last three days), at least that are the files present in my /sdcard/cmupdater folder. The problem has appeared yesterday.
Question: if I do incrementals, will I have to update every day?
oops - it seems not to be the ROM I guess
As I didn't have those problems with 20140407, I downgraded to that version. Seems it didn't have an effect - just about half an hour after downgrade, I had the "Problem", again.
I'll reboot once and if the "Problem" reappears at the same rate, I'll do a full-wipe reinstall.
St0fF said:
As I didn't have those problems with 20140407, I downgraded to that version. Seems it didn't have an effect - just about half an hour after downgrade, I had the "Problem", again.
I'll reboot once and if the "Problem" reappears at the same rate, I'll do a full-wipe reinstall.
Click to expand...
Click to collapse
It is a hardware problem of the Defy, it will go away with time.
hotdog125 said:
It is a hardware problem of the Defy, it will go away with time.
Click to expand...
Click to collapse
I'm having this since 3 days and I'm barely reachable because of that - what are the experiences, how long may it take until this goes away?
St0fF said:
I'm having this since 3 days and I'm barely reachable because of that - what are the experiences, how long may it take until this goes away?
Click to expand...
Click to collapse
For me, the system stabilises after 36 hrs of uptime.
Defy / temporary failure
hotdog125 said:
For me, the system stabilises after 36 hrs of uptime.
Click to expand...
Click to collapse
That sounds really weird! After it stabilizes - when does the problem return? Any idea what caused this effect?
mklmkl said:
That sounds really weird! After it stabilizes - when does the problem return? Any idea what caused this effect?
Click to expand...
Click to collapse
It doesn't return. Hence I said the system stabilizes.
Sent from my Nexus 7 using Tapatalk
Try to flash new modem.Latest or just different.Try BasesbandSwitcher .I Had simillar problems with CM10 and I dont know how exactly i solved it - flashing,switching,trying...Some says that CM ROMs dont change the modem because it have no modem in CM ROMs.
That's the infamous RIL bug. Try disabling and re-enabling location. Doesn't make much sense, but fixed it for me.
propov said:
Try to flash new modem.Latest or just different.Try BasesbandSwitcher .I Had simillar problems with CM10 and I dont know how exactly i solved it - flashing,switching,trying...Some says that CM ROMs dont change the modem because it have no modem in CM ROMs.
Click to expand...
Click to collapse
That's what fixed it for me: I reflashed to factory, then installed cm10/cm11 freshly.
dau_ said:
That's the infamous RIL bug. Try disabling and re-enabling location. Doesn't make much sense, but fixed it for me.
Click to expand...
Click to collapse
Thanks for that information - I'll try to remember next time I get banged by this.
Another search result
[email protected],
i just thought about perhaps creating another thread that may be made sticky, collecting all possible reasons, explanations and most likely workarounds for the RIL Bug - and I found this answer:
http://forum.xda-developers.com/showpost.php?p=50830467&postcount=5
It says undervolting might be a factor. My Defy is undervolted. So I'll try to figure out some less extreme settings, as RIL just reappeared on my phone.
P.S.: I couldn't find that post originally, as at that time I wasn't aware of the bug's name - searching for "RIL bug" in fact returns a lot of results.
St0fF said:
That's what fixed it for me: I reflashed to factory, then installed cm10/cm11 freshly.
Click to expand...
Click to collapse
that's the only thing which helped me too. many rom's worked okay for me and had no RIL reboots ever, but when i've tried to use them again instead of newer ones i tried - i got constant reboots. reflashed to factory and no more ril's again.