Hi all, I'm running Cyanogenmod 6.5.7 and in the last couple weeks I've picked up my phone only to find it was off, not sleeping. It still has plenty of charge left (I can't remember when my phone last went below 50%), and it boots back up without a problem. You wouldn't know there was anything wrong except for the fact that it sometimes turns off on its own.
My first problem is that I don't know where to look to see what could be the trouble. It's running ADWLauncher EX. Beyond that and the OS I don't know what could be relevant. I switched to CM7 last month, up to then I'd been running GingerLOL and I never had this issue.
Any help or advice is appreciated.
The devs would say do a full format and flash and see if it still happens.
Sent from my LG-P500 using XDA App
if you want to know what is happening install logcat from market and check for errors..
i used it to know why mms wont downlaoad and logcat showed that mms ip is wrong and changed it and it works
Oneiros42 said:
Hi all, I'm running Cyanogenmod 6.5.7 and in the last couple weeks I've picked up my phone only to find it was off, not sleeping. It still has plenty of charge left (I can't remember when my phone last went below 50%), and it boots back up without a problem. You wouldn't know there was anything wrong except for the fact that it sometimes turns off on its own.
My first problem is that I don't know where to look to see what could be the trouble. It's running ADWLauncher EX. Beyond that and the OS I don't know what could be relevant. I switched to CM7 last month, up to then I'd been running GingerLOL and I never had this issue.
Any help or advice is appreciated.
Click to expand...
Click to collapse
Try tuning down your overclock frequency... if you have overclocked it... it sometimes happens cuz of that... if you havent overclocked then theres some other problem...
Sent from my LG-P500 using xda premium
samrox144 said:
if you want to know what is happening install logcat from market and check for errors..
i used it to know why mms wont downlaoad and logcat showed that mms ip is wrong and changed it and it works
Click to expand...
Click to collapse
I've done that, but does logcat hold on to recent logs automatically, or do I have to turn on "save to sd card"?
I think I might be having this same issue. I left my phone on and plugged in to charge not even for a half hour or less then I came back to it later and pressed the power button to try to turn it back on but it wouldn't turn on. Then I pressed and held it a second and it wouldn't turn on. I unplugged the battery then plugged it back in then it powered up fine. I seem to be having this issue every once in awhile and I am not quite certain why it is doing this. Also it seems like it has an issue with charging on my computer. I plug it and it the computer is telling me that it can be connected to a higher speed port which makes no since as I have 2 usb 2.0 ports and 1 usb sata port. But basically I plug it in with a full charge and it has no problem keeping it charged but when it ends up going down to at least 50% the charge just keep deceasing and never charges. I just hope that I can make it stop this as it is getting quite annoying maybe it is just the battery or something but I can't see how as it isn't even 6 months old.
I've tried using Logcat but unless you set it to save the log every few seconds it doesn't help. If there's an error it doesn't get caught by Logcat because whatever it does, it turns off the whole phone.
What are you overclocked to?
I'm not, unless CM7 comes already set to overclock. I don't play games on my phone so not much point overclocking for me.
Oneiros42 said:
I'm not, unless CM7 comes already set to overclock. I don't play games on my phone so not much point overclocking for me.
Click to expand...
Click to collapse
Well then. I don't know. Have you tried reflashing the ROM?
Not yet. I was hoping Mik's CM7 6.6.1 would have been declared stable by now, but I guess I'll have to settle for 6.5.8.
Quick off-topic question: ADW Launcher always comes to a grinding halt immediately after a reboot, to the point it gives the force-close option window. Is that because there are widgets installed to the partition on the sdcard, thanks to app2sd? I checked under applications and it says they're installed to the phone, but I thought I heard that app2sd (I'm using Darktremor's, as suggested by Mik) effectively takes the option out of your hands, making it moot. If that's the case, how do I delete the partition, since I'll be doing a full wipe and reinstall when I flash the ROM again.
I don't play games 2
Dammit! Yesterday I did a complete wipe (return to factory, wipe dalvik), reformatted the sd card, and updated the ROM to 6.5.8 and it just shut down on its own again. I even saw it happen... while it was sleeping, I saw the buttons light up and blink once or twice, then it shut off. The screen stayed off.
I did a clean install and haven't touched the clock settings. I reinstalled my apps of course, but I don't have anything that runs constantly in the background that I'm aware of. I installed ADW Launcher EX, I don't know if that matters.
Does this mean it could have a physical fault somewhere? I'd really hate to have to go through the hassle of reloading the LG stock ROM and unrooting it (that's possible, right) to send it in for repair.
I had the same problem with gingerbread and the related roms.
But my problems were about the overclock frequencies. I used the italian rom GingerLoL 1.5.2 and I set the frequencies in this mode: 320-729 smartass v2. No more problems.
I don't know why I hadn't this problem with Froyo's rom...
I'm tempted to fiddle with the clock settings now that I know just reflashing the rom doesn't help. It seems by default CM7 is set to 245-600mhz, with the "smartass" governor. I figure I might as well bump the low end to 320, but where's the "v2" version of smartass you mention? It's not in the list.
I have exactly the same issue! Tried 3 different firmwares, 3 different roms and different kernels too, but it seems to reboot by itself and also really slow sometimes to scroll. Can't solve this... maybe some hardware troubles? some new defected cpu ? I sent this phone 1 month ago in warranty and they changed me the logic board, then when i got it back, it started to have this trouble. Before this, never had this trouble.
Oneiros42 said:
Hi all, I'm running Cyanogenmod 6.5.7 and in the last couple weeks I've picked up my phone only to find it was off, not sleeping. It still has plenty of charge left (I can't remember when my phone last went below 50%), and it boots back up without a problem. You wouldn't know there was anything wrong except for the fact that it sometimes turns off on its own.
My first problem is that I don't know where to look to see what could be the trouble. It's running ADWLauncher EX. Beyond that and the OS I don't know what could be relevant. I switched to CM7 last month, up to then I'd been running GingerLOL and I never had this issue.
Any help or advice is appreciated.
Click to expand...
Click to collapse
Make a full wipe and don't let your phone with low internal memory, it worked for me and i was having the same issue
FPChaim said:
Make a full wipe and don't let your phone with low internal memory, it worked for me and i was having the same issue
Click to expand...
Click to collapse
I have done a full wipe, but I don't understand your other suggestion. I'm using Darktremor's Apps2SD, so I'm pretty sure I'm not running low on ACTUAL internal memory.
As per my last comment, I bumped the low end of the governor to 320mhz and there was no trouble until two days ago when it turned off on its own again, making it the longest it went without the spontaneous shutdown. However, it then broke its record for SHORTEST time because it shutdown again five hours later.
Can anyone thing of anything else, or should I start looking for my warranty info?
Oneiros42 said:
I have done a full wipe, but I don't understand your other suggestion. I'm using Darktremor's Apps2SD, so I'm pretty sure I'm not running low on ACTUAL internal memory.
As per my last comment, I bumped the low end of the governor to 320mhz and there was no trouble until two days ago when it turned off on its own again, making it the longest it went without the spontaneous shutdown. However, it then broke its record for SHORTEST time because it shutdown again five hours later.
Can anyone thing of anything else, or should I start looking for my warranty info?
Click to expand...
Click to collapse
I'm my case the phone boots and when it load all the aplications it reboots... but one time i quickly go to setting>applications>manage applications and there has less than 1 mb... so i think it was building something like caches... I wiped everything and my phone worked as usually... but i installed a lot of things again and it keeps rebooting and rebooting... i wiped everything again and installed just few things, leaving my phone to have high internal memory... it worked!(actually i have 42 mbs of free space and it never happened again)
Related
OK, so I'm on GSB 3.4 (though this issue began with 3.3), and I'm having a problem with my phone rebooting (screen cuts off after about a second, and the phone immediately reboots to the skateboard screen) at the following times:
1. Whenever I attempt to wake the phone from sleep.
2. Whenever I hang up a phone call.
3. Whenever I get a phone call while the phone is asleep.
4. Whenever I plug the phone in to charge while the phone is asleep (be it a wall socket or PC) [see below].
These problems only occur when the phone is NOT plugged into a charging source; the problem appears to be nonexistent in this scenario. But as soon as I unplug, all 4 become auto-crash scenarios.
I tried going back to GSB 3.2, but no dice. I then resorted to the stock-ish XTRsense ROM, which fixed the issue, but going back to Froyo just was too big a downgrade for me.
Throughout this process, I full-wiped multiple times, hoping to track the issue to an app or setting, but even before restoring anything through TBU (I think I may have just let the phone go to sleep at the "Touch the Android" initial setup screen once), the problem persisted, eliminating apps, settings, or CM7 CPU modifications as possible culprits.
I've continued to play with CM7 CPU settings even up till now, but I'm not getting much of anywhere. I've now resorted to the "Caffeine" app, which just never lets the phone go to sleep, and I just turn the brightness down or activate the "Desk Clock" mode in the default Clock app to save battery.
HELP?
Have you tried Tazz's ROM or CondemnedSoul's ROM, just to see what happens with those? CS's ROM uses ADW as the default launcher (not sure about Tazz's) - perhaps it's something with LauncherPro?
Had this happen once
Sent from my Aosp Gin-Tazz using XDA App
My phones use to freeze on the unlock screen, it happened in multiple roms. i switched back to the "ondemand" governor and it hasn't happened since. not sure if it the same issue but it might help.
My last name is also Schultz ....
Sent from my Aosp-Gin-Tazz using XDA Premium App
Guys, just thought I throw out the idea that it might an overclocking (i.e., hardware) issue?
I see that the Conap's CFS kernel that GSB 3.4 uses is max clocked at 604 MHz, but maybe that's too high for your particular phone?
I also think that schultzmd's comment about the ondemand governor helping might point to the clock stepping to a higher speed when coming out of sleep (and being related to clock speed). Maybe try running the phone at a lower speed just to see if its better behaved might prove instructive.
Just a thought...
Cheers!
scary alien said:
Guys, just thought I throw out the idea that it might an overclocking (i.e., hardware) issue?
I see that the Conap's CFS kernel that GSB 3.4 uses is max clocked at 604 MHz, but maybe that's too high for your particular phone?
I also think that schultzmd's comment about the ondemand governor helping might point to the clock stepping to a higher speed when coming out of sleep (and being related to clock speed). Maybe try running the phone at a lower speed just to see if its better behaved might prove instructive.
Just a thought...
Cheers!
Click to expand...
Click to collapse
Sounds familiar: http://forum.xda-developers.com/showpost.php?p=14016867&postcount=5186
I'll try the changing the max, but I know I've tried as low as 604 max (19 min) with the problem persisting, and as high as 710 or 768 before GSB 3.3 (when the problem started) with no major issues. And I had already been using Ondemand when the problem started, having stopped using Smartass when I thought it slowing the performance down a bit. Any other governors I should try?
And does the overclocking issue not apply when a phone is charging?
doogald said:
Sounds familiar: http://forum.xda-developers.com/showpost.php?p=14016867&postcount=5186
Click to expand...
Click to collapse
lol, doogald...I had no idea .
I should know better than to come in to any thread you've already weighed-in on and know that you've already exhausted all the possibilities.
I'll leave the Op to your very capable hands.
Cheers and thanks for keeping an eye out here on XDA and over at AF too (and probably six or seven other sites ).
natemup said:
And does the overclocking issue not apply when a phone is charging?
Click to expand...
Click to collapse
Well, you are introducing some extra heat into the equation while charging, which might be enough to tip the balance against you if it is indeed an overclock issue.
scary alien said:
lol, doogald...I had no idea .
I should know better than to come in to any thread you've already weighed-in on and know that you've already exhausted all the possibilities.
I'll leave the Op to your very capable hands.
Cheers and thanks for keeping an eye out here on XDA and over at AF too (and probably six or seven other sites ).
Click to expand...
Click to collapse
You would have only seen that if you had seen the post in the GSB thread, of course.
I am still going to suggest trying Tazz or Condemned. From what the OP says, he should be able to see that it's having the same issue pretty quickly.
But, just to rule out the OC issue, you could try setting the max to stock 528 and see if it still happens.
doogald said:
You would have only seen that if you had seen the post in the GSB thread, of course.
Click to expand...
Click to collapse
lol...that post was on the 519th page of (currently) 530 pages! (I read the first page, does that count? )
Still crashing on 528 max / 19 min...
natemup said:
Still crashing on 528 max / 19 min...
Click to expand...
Click to collapse
How about on Tazz or Condemned? And, 19.2 is too slow for a minimum for this kernel. 245 should be the minimum.
scary alien said:
Well, you are introducing some extra heat into the equation while charging, which might be enough to tip the balance against you if it is indeed an overclock issue.
Click to expand...
Click to collapse
I was inquiring as to why the issue DOESN'T happen when I'm charging. I'm not sure if that's what you were saying, but I have no issues while the phone is charging; it's weird, because CM7's CPU governor doesn't allow profiles for "screen-off", "charging", or anything like that. It just seems to make my problem more random and untraceable. It literally is happening on EVERY CPU setting, even 480 max (which to me, is just pointless to actually use)
I've full-wiped so many times in the last few days, I'm wary to just try a different Gingerbread ROM when GSB is (was, for me) so stable and full-featured. I'm trying my darnedest to just stick it out and charge-charge-charge to avoid the issue.
One more thing: if, right after the phone reboots itself, I unlock it before the screen goes off and manually put it to sleep and quickly wake it back up, the issue usually doesn't occur (and I can keep doing this, putting it to sleep and waking it back up again, with no issue). But if I unlock it and let it sit and reach the screen timeout itself (or never unlock it after it reboots, then let it sit for a while), the problem reoccurs.
natemup said:
I've full-wiped so many times in the last few days, I'm wary to just try a different Gingerbread ROM when GSB is (was, for me) so stable and full-featured. I'm trying my darnedest to just stick it out and charge-charge-charge to avoid the issue.
Click to expand...
Click to collapse
I have used both GSB and Condemned and you will not be missing anything. I stopped using GSB because I could not get market updates to stick reliably. I do not have that issue at all with Condemned.
Right now the only issue with the latest Condemned is apparently a GPS issue, so I would go with V6 or V7 rather than V8 for now until CondemnedSoul gets an update. Or, if you don't navigate, go ahead with V8. It's just fine.
You're obviously having a stability issue with GSB now, so you have nothing to lose but about 45 minutes of time and a Nandroid Restore to go back to GSB if you don't like it.
So, I had a minor issue that was fixed by switching to a different ROM. It's worth a try.
I wish you luck finding a solution.
natemup said:
I was inquiring as to why the issue DOESN'T happen when I'm charging. I'm not sure if that's what you were saying, but I have no issues while the phone is charging; it's weird, because CM7's CPU governor doesn't allow profiles for "screen-off", "charging", or anything like that. It just seems to make my problem more random and untraceable. It literally is happening on EVERY CPU setting, even 480 max (which to me, is just pointless to actually use)
Click to expand...
Click to collapse
Nate,
Sorry about that ...I was confused from where you asked in post #8 about whether or not overclocking was in effect while charging (it can/could be, depending on the overclocking monitor/govenor I suppose) and I had lost that point from your original post.
I would say take doogald's advice and switch to at least some other ROM since that would help indicate if it is indeed a software issue or a hardware issue. Its sounding like its not clock-speed related given the things you've already tried. If you've still got issues on other ROMs, that would tend to point to some hardware issue (our Erii are getting a little long in the tooth at this point, after all).
You could even flash back to stock and see if the phone is still stable there since you can always re-root and re-restore your Nandroid backups.
Good luck...I hope you figure something out.
Problem is alive and well on Condemned GB. *sigh*
XTRsense was fine and flawless, but going back to Froyo after months on gingerbread was just too depressing for me...
Sent from my ERIS using XDA App
I'm going to make one more suggestion - not sure if you have tried this yet, but try flashing GSB from a full wipe. When you go through the setup, DO NOT LOG IN TO YOUR GOOGLE ACCOUNT. After the launcher starts, go into the market, let it log you in to your Google account then, and then install all of your apps and change all of your settings from scratch.
When you log in with your Google account when installing a CM ROM, it tries to restore your apps and settings from your last CM ROM install. It may be that you have some weird setting or app that is causing this that you just keep reinstalling when you flash the ROM and log in with your account.
If you've already tried this, then try running xtrSENSE or xtrROM instead. They are both excellent ROMs and clearly your phone likes them better.
[edit] Oh, and try leaving your min at 245 MHz for a while. See if that helps your phone run better. It should, and it should have the exact same battery life as 19.2, as nonsensical as that sounds.
It is literally happening as soon as I boot the phone after a fresh GB install. I four-corner the Android setup screen, let the screen time out, and boom I'm screwed.
im wondering if it is the speed scripts? i am using eclipse 1.1 now so im going to see if that fixes it. but i have been getting the freeze when unlocking the phone, and sometimes randomly when im using the phone the screen goes 100% unresponsive...the buttons work, but nothing else...then after about a min or two it comes back..VERY annoying...
Do u reboot or clear system caches on a regular /daily basis? This may help.
Sounds like things are getting clogged up. I used to have that problem a while ago before I started rebooting once a day. Usually when I wake up and sometimes twice a day. It is healthy for an android phone to be rebooted once a day. Just plain works better.
oh this has happend right after a SBF or a reinstall of an OS, so there was not even a day on it. it happened this morning once when i unlocked the phone BUT i had that speedy script installed, i resotored from a back up before i installed that scrpit so im going to see if it happens again....i hope it is not hardware related..
dvigue said:
oh this has happend right after a SBF or a reinstall of an OS, so there was not even a day on it. it happened this morning once when i unlocked the phone BUT i had that speedy script installed, i resotored from a back up before i installed that scrpit so im going to see if it happens again....i hope it is not hardware related..
Click to expand...
Click to collapse
I hope it isn't also.
It has only happened to me in the past like I said. It's been a long time tho((knock on wood))
I have also been running the speedy script v6 . I only made one change and that was deleting the 3gturbo entries in the one script. And I haven't had this problem yet at all. Been running for two and half days now.
has this also happened on 2.3.3? i was wondering if it was a 2.3.4 issue?
Sounds like something clogging your memory. When I start fruit ninja my x2 screen goes unresponsive for up to 20 seconds I assume its just memory management during game startup. Are you using a task killer to maximize free ram? This will cause background apps that you may have killed to restart if they are called upon. That would cause the phone to bog down temporarily
Sent from my DROID X2 using XDA App
nope no task killers at all. i noticed using system panel i was at only 77 mb using eclipse...
My phone doesnt freeze but it does randomly reboot no matter what rom, script, length of use before a restart, or whatever.
booked said:
My phone doesnt freeze but it does randomly reboot no matter what rom, script, length of use before a restart, or whatever.
Click to expand...
Click to collapse
I guess I got pretty lucky with not getting reboots.
Even before I rooted and rom'd up I think I MAY have had one random reboot. I guess I just got lucky. Basically the only major problem I have had that others have os the music skipping I used to encounter lag occasionally but since I started my daily reboot routine lag is pretty null on most occasions.
dvigue said:
im wondering if it is the speed scripts? i am using eclipse 1.1 now so im going to see if that fixes it. but i have been getting the freeze when unlocking the phone, and sometimes randomly when im using the phone the screen goes 100% unresponsive...the buttons work, but nothing else...then after about a min or two it comes back..VERY annoying...
Click to expand...
Click to collapse
I wonder the same been using eclipse straight up except for setting the min to 216 instead of 312 never had any issues period . Might be worth getting rid of speed scripts and see if that is the issue.
2.3.4 was made pretty much to fix the lockups and reboots. It might be something with your backups. I know I just used a backup a couple days ago after giving up on upgrading to 2.3.4 and until today when I finally upgraded to 2.3.4 it was slow, laggy and unresponsive. Mind you before that last nandroid, it was working amazingly.
Okay so I'm not 100% sure if this is a sure fix, but it seems to have worked for myself and my wife. We both were getting random reboots like crazy and it was getting very annoying. I remembered back in my windows mobile TP2 days that a lot of stuff gets stored on the SD card after constant flashing and tweaks. So in order to get a proper flash u normally would have to reformat ur SD card, wipe, wipe, wipe, and then flash ur ROM. That is exactly what I did with my phone as well as my wife's phone. I formatted our SD cards after backing everything up of course. I backed it up on an external harddrive, formatted, put everything back, formatted the phone with a super wipe zip I found somewhere in the development forum, installed a custom stock Rom I have been tweaking and then booted up my phone and have not had a single random reboot since. So as the title says, it is a possible fix. If u try it then please post so that other users can know if it is actually stopping the reboots or if It's just a placebo effect. Thanks and I hope I've helped someone who is extremely frustrated as I was with their 500 dollar phone randomly rebooting.
Sent from my Beastly EVO.. And did I mention it has 3D?
I fixed mine with a buisness card as a shim for the battery lol
atistang said:
I fixed mine with a buisness card as a shim for the battery lol
Click to expand...
Click to collapse
Yeah my battery wasn't loose at all. My phone would also sometimes freeze up and when I rebooted it would just be a black screen. I had to pull the battery to get it working again. I tried the auto brightness fix bit my screen would go black sometimes and rebooting did not fix. I actually had to pull the battery out.
Sent from my Beastly EVO.. And did I mention it has 3D?
See, the problem with my phone is not random reboots, but hard freezes--with custom kernels..only custom kernels. My actual ROM software is very stable.
Now, if someone can figure out why that happens, I will give them $100.
freeza said:
See, the problem with my phone is not random reboots, but hard freezes--with custom kernels..only custom kernels. My actual ROM software is very stable.
Now, if someone can figure out why that happens, I will give them $100.
Click to expand...
Click to collapse
Truth. I've never had random reboots and the only reboots I've done were solely manual because of these hardlocks from custom kernels.
If only my phone played nicely with kernels...
freeza said:
See, the problem with my phone is not random reboots, but hard freezes--with custom kernels..only custom kernels. My actual ROM software is very stable.
Now, if someone can figure out why that happens, I will give them $100.
Click to expand...
Click to collapse
Since we never had this issue with the 4G you think it could just be a borked kernel source from HTC and we are missing some valuable info in it? Or the dual core aspect of it being ours r diff than others being asynchronous, is very touchy to code and adjustments we woulda made on single cores?
Any other of the MSM8660 handsets experiencing this with their custom kernels or is it just ours? If just ours be worth looking at their stable kernel modes source to see difference n what they might be doing differently??
Sent from my PG86100 using XDA App
sgt. slaughter said:
Since we never had this issue with the 4G you think it could just be a borked kernel source from HTC and we are missing some valuable info in it? Or the dual core aspect of it being ours r diff than others being asynchronous, is very touchy to code and adjustments we woulda made on single cores?
Any other of the MSM8660 handsets experiencing this with their custom kernels or is it just ours? If just ours be worth looking at their stable kernel modes source to see difference n what they might be doing differently??
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
I'm leaning more towards HTC's screwed up source. As this problem wasn't present in their 2.3.3 source, at least with netarchy's kernel. There weren't nearly as many kernels to choose from but still.
I've heard a few people say the source was either incomplete or messed up somehow. We can only hope that HTC releases an updated software version with a new kernel so that they're obligated to release the source as well, and this time hopefully it will be complete.
atistang said:
I fixed mine with a buisness card as a shim for the battery lol
Click to expand...
Click to collapse
I used a gum wrapper for mine
Sent from my PG86100 using xda premium
I'm having strange issues as well. My phone will sometimes lockup while using it and then it displays the bootanimation and gets stuck on it and I have to battery pull. And it's actually done it once so far while I was sleeping. ROM is stock but I just decided to finally update it to 2.3.4 so I flashed dastin1015's "[ROM][Sense 3.0][2.3.4][Nov. 3, 2011] Stock 2.08.651.3 Deodexed w/ Hotspot and Beats" over it and rolled. Before I flashed, I nandroid'd, Titanium'd, and My Backup Pro'd. I then booted into TWRP and flashed and rolled. I didn't clean reset before or after because I was worried about losing texts and whatnot. That seemed to go well so I flashed chad.goodman's mildAnthraX and also updated my PRI. And keep in mind I haven't touched the clock settings or voltage. Any ideas? I was considering flashing stock kernel and seeing if that fixes it. If not, then I imagine I will have to do what I least want to and clean reset my phone. Will the logcat help identity the problem here?
Lucentio said:
I'm having strange issues as well. My phone will sometimes lockup while using it and then it displays the bootanimation and gets stuck on it and I have to battery pull. And it's actually done it once so far while I was sleeping. ROM is stock but I just decided to finally update it to 2.3.4 so I flashed dastin1015's "[ROM][Sense 3.0][2.3.4][Nov. 3, 2011] Stock 2.08.651.3 Deodexed w/ Hotspot and Beats" over it and rolled. Before I flashed, I nandroid'd, Titanium'd, and My Backup Pro'd. I then booted into TWRP and flashed and rolled. I didn't clean reset before or after because I was worried about losing texts and whatnot. That seemed to go well so I flashed chad.goodman's mildAnthraX and also updated my PRI. And keep in mind I haven't touched the clock settings or voltage. Any ideas? I was considering flashing stock kernel and seeing if that fixes it. If not, then I imagine I will have to do what I least want to and clean reset my phone. Will the logcat help identity the problem here?
Click to expand...
Click to collapse
Ur on the exact setup as I am. Kernel and ROM. Stock kernel still did exactly what u mentioned above as well. After formatting my SD card I have yet to have it happen. It's been about 8 days since I formatted. After reading the posts I don't think formatting my SD card is a fix, but I too am leaning towards HTC kernel being messed up. I think sooner or later my phone is going to do it. My phone was doing exactly as u stated. Booting into the splash screen and not going past it. On some occasions my phone would either freeze up or just go black. The hard buttons would light up but not my screen. Hope this gets figured out soon.
Sent from my Beastly EVO.. And did I mention it has 3D?
Mine resets between the hours of 71-80 of being on
I'm having the same problem and I do not know how to solve it! I am so close to selling my Evo 3D and going to the SG II.
I have ran CleanRom and currently running Fresh. I have tried Mwalts kernel, Bcblends kernel, and stock kernel from Fresh stock. No matter what I tried, my phone ALWAYS resets between the hours of 71-80 of being on.
The reset happens only when I try to turn on the phone. It turns on, off really quick, then I hit the power button again, the lock screen comes on, then the phone resets. It is getting really annoying as I love having stability and this phone isn't stable at all.
Any ideas? I have exhausted everything I know. I'm running the exact same programs as I have on the Evo 4G and since it is resetting at the same hours always at the same time on different ROMS/Kernels, I'm pretty sure its not app issue. I also tried changing between the 3 radios and no change there. The only other option now is to do a fresh install of Fresh and use it stock and see what happens.
Rytt
Try setting min cpu freq to something other than 192000, I use 384000 sleep and 482000 wake. I used to have a reboots and freezes but saw that advice somewhere and gave it a shot. Presto no more issues. Battery life is no worse for wear either. Not saying this will work but worth a try.
3VO Sent
ifly4vamerica said:
Try setting min cpu freq to something other than 192000, I use 384000 sleep and 482000 wake. I used to have a reboots and freezes but saw that advice somewhere and gave it a shot. Presto no more issues. Battery life is no worse for wear either. Not saying this will work but worth a try.
3VO Sent
Click to expand...
Click to collapse
already try that
no luck it still keep rebooting while screen off
freeza said:
See, the problem with my phone is not random reboots, but hard freezes--with custom kernels..only custom kernels. My actual ROM software is very stable.
Now, if someone can figure out why that happens, I will give them $100.
Click to expand...
Click to collapse
my cdma-sense kernels having issues????
RLS9 and RLS14 should be 100% stable - and not based off of htc source
(on pre 2.17 based roms)
i think freeza gave rls9 his seal of approval for stability.. if memory serves correctly
...on my phone i use (not my test phone) im @ 242 hours uptime on rls14 and warm 3.5 r116
...no im not trolling, just looking for feedback
chad.goodman said:
my cdma-sense kernels having issues????
RLS9 and RLS14 should be 100% stable - and not based off of htc source
(on pre 2.17 based roms)
i think freeza gave rls9 his seal of approval for stability.. if memory serves correctly
...on my phone i use (not my test phone) im @ 242 hours uptime on rls14 and warm 3.5 r116
...no im not trolling, just looking for feedback
Click to expand...
Click to collapse
He said that before you found the magic fix I'm pretty sure. Notice that was back from November. Lol
Sent from my PG86100 using xda premium
Huge Thanks
thank you so much for sharing your information my evo 3d was rebooting about every 30 min and i have just been dealing with it because i had took my evo4g into the sprint store because it was rebooting aboutevery 5-10min so they looked at it and couldnt figure it out so the gave me the evo3d for free and i put the sdcard that was in my evo 4g into my evo3d without having any idea that it was the sdcard causing all of my problems so the same thing started to happen to my new evo 3d started off about every day and eventually started to reboot every 30min and i just decided that all htc devices were like this so i have been dealing with it but today i said enough is enough and looked online and saw this thread and wiped my sdcard and sure enough no reboots yet its been about 3 hours so i think its fixed
i cant thank you enough i think it got corrupt from all of the flashing i was doing
son of a ***** right as i was about to hit post the mother ****er rebooted so its not my sdcard after all should i take it in to sprint what do you think ahhh i should have never posted anything it was going so well FML!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
ps hboot 1.4 is the **** no more going to the computer to flash a rom stupid hboot 1.5
I've sometimes had trouble running custom kernels (reboots and strange behaviors) that were fixed when running the stock kernel. But, the stock kernel leaves a lot to be desired in overall performance, so I continue to kernel hop. But, from my lurking on the different ROM forums, it seems that stock is the way to go for stability at the sacrifice of performance.
I had problems with evo rebooting and that in a loop. Very annoying. For that i've changed several roms just to find out that it could probably be because of widgetsoid.
At first the rebooting after some time of use, 1-2 days. And if flashing a different kernel than the one with rom. I was going mad, the last reboot or series of constant reboot after the evo has turned itself on, has occured after i set the brightness to lowest value, it was late so i wanted a darker screen. Interesting it when i set lowest value in system or via leedroid tweaks in widgetsoid widget popup - value im at 12 %. Maybe i got the restarts because i went below 12? Since my brightness im above 12 in widgetsoid and minimal in system, my evo didn't reboot a single time.
Currently i'm at shawn3d rom. Later i'll try some other kernel and rom again and see if the reboots occured.
U get random reboots while using any brightness widget with custom roms. I've narrowed my 3d threshold for the reboots to be anything less than 5%.
No reboots if kept at or above 5% for me...
Sent from my PG86100 using Tapatalk 2
i have had success after formatting system/data/cache to ext4 in the ext4 recovery, i had random reboots and lockups while using twrp and not formatting to ext4, (in all honesty i doubt the twrp was too blame)
I'm posting this here because I hope some devs might be able to get a handle on the problem. I think it has something to do with the launcher.
Since I upgraded my phone to a 2.3.4 ROM, I've had constant problems with its randomly rebooting, or occasionally just freezing. (I say "rebooting", but it always gets stuck in a boot loop, and so it might as well be frozen.) The first ROM was Synergy, but I've had the same trouble on Warm, and with three or four different kernels (OC'ed and not OC'ed) on each of those ROM's. In some configurations it's better, and in some it's worse, but I've nearly always had the reboots happen at least once a day. Sometimes it happens while charging, sometimes while it's not; sometimes it happens while I'm touching it, and sometimes when I haven't touched it in hours (kind of annoying when it's my alarm clock--I missed a meeting last week). There's not a lot of consistency in when it happens, though I should say, for the record, that I've been using Launcher Pro the whole time.
Obviously, I'm not the only one with this problem: for some, like me, it started with 2.3.4 (including, in many cases, the stock OTA); for others, it started when the phone was first released; while for others, it's never happened at all. The fact that some people haven't experienced it at all may mean hardware has something to do with it, and I even read one account of a guy who took five different phones back to Sprint for replacements before finding one that worked right.
After searching high and low, I found a thread on the Sprint Community forums that suggested editing the data.prop file to keep the launcher in memory constantly (Look here and scroll down to post #9.). I tried this a couple of days ago, and it hasn't fixed the problem, but it did dramatically reduce it: I went from rebooting every two hours to rebooting once or twice a day.
I've noticed one other interesting thing: a couple of months ago, I started playing Godville, and I've been propping the phone up next to me and letting it idle with the screen on (while on USB), so that I can glance over every once in a while to see if anything is happening in the game. I've noticed that, every few minutes, the home screen wallpaper briefly replaces the app I have open; it happens so fast that I can't tell for sure if the whole launcher is coming up, but I suspect it is. I wonder if this constant yanking of the launcher into the foreground might be the source of the instability.
my mind is like..... blowwwwn
---------- Post added at 01:37 AM ---------- Previous post was at 01:28 AM ----------
no but on a serious note man... many people have had problems with reboots since the launch of the 3D, which was 2.3.3 based. I doubt that was the issue (launcher, your update, your games... gnomes...)
i would say flash the RPM PGIMG86423million update whatever that number is for the bootloader update.zip, and see if that rids you from the reboots.
for me, i fixed my reboots by getting a new SD card... i had the same issue when i first got my 3D late in july. Did it both on 2.3.3 base, and 2.3.4... it occurred to me one day that a bad disk would cause system reboots... and not being able to change out the one built into the phone... i opted for the SD card because it was cheap and i wanted a better one anyways. reboots went away immediately.
it also never occurred to me initially that my SD had been bad for a long time... not just when i had my 3D.. on my previous phone (samsung moment with froyo), whenever i would move apps to the SD card, i would always get some kind of error message. trying to move them a couple times would always successfully move the app(s) to the SD card.. i figured this was a problem with the rom i was on (speaking of my samsung moment)...
then when i transferred my card to my 3D, same problem, along with the reboots, and a light clicked on in my brain and said "***k-tard, your SD card is bad. derp."
haven't had a single reboot since then. i even wonder if the paramount number of people having reboot issues on the 3D was due to HTC possibly shipping them with defective SD cards...
just something to mix around in your brain for a bit...
Yeah, I considered the SD card as a problem, but the reboots happen even when the SD card is mounted as a USB drive. Also, a bad SD card wouldn't explain why keeping the launcher in memory dramatically reduces the problem.
I'll be giving it a try.
Just a side note. I've been using the stock kernel lately and havn't had a single reeboot. I'm on synergy rom and since he put back in the stock kernel w/ no OC I've had no issues.
I may try that, but it would be sad to not to able to OC a rooted phone. I'm starting to wonder if it's a bad internal flash drive, though.
You should try a stock ROM to see if that solves your issue if that's doesn't work maybe you have defective phone
Sent from my PG86100 using xda premium
All my problems went away when I used Senseless ROM. I think the kernel in the ROM is stock. It's been over two weeks since my phone has frozen on me and no more random reboots.
Only stable kernels are tiamat and stock. All the others cause bootloops thanks to tryin to remove ciq
Sent from my PG86100 using Tapatalk
I'm having the same reboot issues. I've noticed a few things:
1. Doesn't matter what sd card or how new, my phone reboots unexpectedly
2. Phone ONLY reboots RIGHT when the screen times out. Only on Android 2.3.4 w/ sense! It does not matter what kernel. Whatever I do, all reboots are directly related to sense on 2.3.4.
3. The only solution I have found is to deactivate the screen time out or gut HTC proprietary sense from the ROM.
P.s. I DO NOT have problemswith any ota based off 2.3.3
bloodrain954 said:
Only stable kernels are tiamat and stock. All the others cause bootloops thanks to tryin to remove ciq
Click to expand...
Click to collapse
Tiamat isn't stable for me.
MTKnife said:
Tiamat isn't stable for me.
Click to expand...
Click to collapse
Nor for me. It causes daily hard lockups that require a battery pull on my phone. Tiamat exhibited this on multiple ROMs for me.
I think trying a largely stock rom is a must as a start to tracing your problem. So is incremental additions of apps, tweaks, etc. Basic debugging and defect isolation stuff.
bloodrain954 said:
Only stable kernels are tiamat and stock. All the others cause bootloops thanks to tryin to remove ciq
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
What about bcblend by mwalt? Senseless rom has been using that for quite some time and I haven't had any issues. When it was switched to tiamat for a short time (2.5 & 2.6, i believe) I had problems with lockups and reboots. Reboots would occur when the screen timed out every once in a while.
Just curious OP - have you tried the phone on a newly installed rom without installing any side apps for a day or so and seeing if you have any problems? Back on my old nexus S 4g i had issues with a particular battery app that would give similar problems to what you are experiencing.
Tiamat has not been stable for me either. I tried many different rom and kernel combos and am still having the issue. I noticed it is mostly happeneing when the phone is plugged in. but it also happens sometimes when im on a call. So there has to be more than one issue one being the proximity sensor and i cant figure out the other ive hset charging profiles to 384max and 198 min and other low clock speeds to see if it would help. Also set a temp profile to underclock when its over 38.0 celsius. Right now im running olympus trinity xe titan i ran it for a few days with mild anthrax and it only froze/rebooted a few times a day. I tried the anthrax kernel and it rebooted twice the first half hour so i flashed tiamat last night. Im trying to give it time to settle in but it just rebooted again when i plugged into pc. I bought my phone used and rooted before i even activated it so i dont know if this is something kernel/rom related. I started another thread a few days ago about this and the few responses i got were people running stock romand kernel not rooted. So i guess all we can hope for is the devs to figure it out or sprint to give us an ota that fixes it since im starting to belive its a hardware issue.
If you're on titan freezas is recommended.
Sent from my PG86100
I saw a few people talking about that but I thought they were talking about for when he released Hades. I'm gonna find the dl link now thanks.
Sent from my PG86100 using XDA App
Cabe24i said:
Just curious OP - have you tried the phone on a newly installed rom without installing any side apps for a day or so and seeing if you have any problems? Back on my old nexus S 4g i had issues with a particular battery app that would give similar problems to what you are experiencing.
Click to expand...
Click to collapse
Not for that long a period, no--unfortunately, I haven't been in a position where I could give up most of the use of my phone for that long. Once I have grades submitted next Monday, I can probably do more methodical testing.
I'm still freaked out by the way the launcher pops up every few minutes, though--has anyone else ever seen anything like that?
Questions or Problems Should Not Be Posted in the Development Forum
Please Post in the Correct Forums
Moving to General
One of my favorite rom and kernel combo's is infected eternity with anthrax but random reboots are common for me with any sense based rom. I run MIUI with whatever aosp kernel and everything is flawless. Other than experimenting with kernels to find battery life, MIUI is the most stable rom I have used so far and is my new daily driver!
Sent from my HTC EVO 3D using xda premium
My evo also reboots and i havent rooted my phone at all. I did get a new SD card and that reduced the amounts of reboots i get! . Although, i still get a few every week.
hope sprint/person finds a fix for this soon.
Mine did it stock / rooted stock and viper ROM I an on fresh and so far smooth as butter ... Stock rooted was awful every time it would time out bam reboot
Sent from my PG86100 using XDA App
Hi all,
I'm wondering if anyone can help me....I'm getting kind of desperate here! Basically my Atrix keeps randomly rebooting or getting stuck with the screen off (requiring a batter pull) . This happens about 10-20 times a day (my Atrix is far too unreliable right now to use as a daily). This seems to ONLY happen when on network (ie 2g/3g/hspa) and doesn't seem to happen on wifi. I can leave it on all night and day at home on wifi happily with no trouble but as soon as I go to work and leave it on network, the trouble starts. Its weird cause if the phone is doing something with the screen off (playing and streaming music over Bluetooth for example) it won't have any problems. Its only once I leave it at rest on the network that it turns into the most unreliable handset ever.
At first I thought it may be the neutrino rom I was running but I've since been using jokersax's amazing ics builds and the same problem persists. I did a full clean (format /data & /system plus cache and factory wipe ) and loaded on the latest beta build this morning, left it clean with zero apps except google (and xda!) and within an hour of getting to work the problem came back.
I am fully boot loader and network unlocked.
Please, if anyone has any idea I would be really grateful. I am tearing my hair out!
Sent from my MB860 using XDA App
It is happening with me too, but, I dont realize it on happen on mobile data connection
Since i flashed beta 0.1.0 2d of Jokersax's ICS and come out of home
Today, for 5 times I have to pull battery out of Atrix
Why not try a more stable ROM first and see if you get reboots.You do realize some phones just cannot handle unstable roms like the cm9 builds even though they are great for some ppl it just doesn't workout also maybe you are using an oc kernel that your phone cannot handle.I would check both things first.
Try some a bit more stable.
cm7 ba2ft
wetdream
darkside
gingermod
If you get the same with those then maybe fastboot wipe and stuff like that so you can clear everything out
EDIT: flash a radio too
sk8trix said:
Why not try a more stable ROM first and see if you get reboots.You do realize some phones just cannot handle unstable roms like the cm9 builds even though they are great for some ppl it just doesn't workout also maybe you are using an oc kernel that your phone cannot handle.I would check both things first.
Try some a bit more stable.
cm7 ba2ft
wetdream
darkside
gingermod
If you get the same with those then maybe fastboot wipe and stuff like that so you can clear everything out
EDIT: flash a radio too
Click to expand...
Click to collapse
Hey,
Thanks, I'm going to try Gingerblur tonight... I had ruled that out as I have used darkside/gingerblur before and apart from the occasional reboot they were OK. The reboot was OK really, I know its a known issue with this model even with unrooted handsets, as long as its occasional and clean boots back to system again it doesn't really matter as I don't pin lock my sim (currently my problems are either a reboot every three minutes as soon as I switch the screen off... or, more commonly, the dead screen, needing that battery pull) .
I *suspect* that it may be the radio, but really need some solid advice on this because a couple of years ago I completely bricked my G1 by flashing the wrong radio and vowed never to touch radios again if I didn't have to....I am naturally very hesitant about radio flashing from that episode. Can anyone give me some decent advice on which radios i should be looking at for an unlocked ( but formerly Orange UK) Atrix? One very nervous owner here!
The other weird thing is that is perfectly fine when on a power source.
Sent from my MB860 using XDA App
markdjj said:
Hey,
Thanks, I'm going to try Gingerblur tonight... I had ruled that out as I have used darkside/gingerblur before and apart from the occasional reboot they were OK. The reboot was OK really, I know its a known issue with this model even with unrooted handsets, as long as its occasional and clean boots back to system again it doesn't really matter as I don't pin lock my sim (currently my problems are either a reboot every three minutes as soon as I switch the screen off... or, more commonly, the dead screen, needing that battery pull) .
I *suspect* that it may be the radio, but really need some solid advice on this because a couple of years ago I completely bricked my G1 by flashing the wrong radio and vowed never to touch radios again if I didn't have to....I am naturally very hesitant about radio flashing from that episode. Can anyone give me some decent advice on which radios i should be looking at for an unlocked ( but formerly Orange UK) Atrix? One very nervous owner here!
The other weird thing is that is perfectly fine when on a power source.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Hang on, I'm not making sense here, maybe it is these advanced ROMs, I was just surprised that neutrino (a cm7 based rom) also produced these reboot problems. Anyway, any advice on radios would be appreciated
Sent from my MB860 using XDA App
As long as you flash atrix radios only you should be okay. I flashed just about every applicable radio on my brother's captivate and never bricked it.
I agree with you and previous posters, it sounds like a radio issue for sure.
Sent from my MB860 using XDA App
I have the same problem with my Atrix running cm7 ba2ft. Sometimes it does not respond when you try to unlock, and I need to take out the battery to turn it on again. I bought the phone couple of weeks ago.
another thing to look at would be the battery my friend had similar problems with his nexus and tryed Roms and radios I bought him a new battery as a joke and the joke ended up on me cause he hasn't had the problem since let me know if this helped you aswell
Sent from my ics+darkside multiboot mb860 using xda premium
Same problem here. Very aggravating.
I am having the same problem. And I am 100% stock with no mods. I just installed OTA 2.3.6 so I am waiting to see if that helped.
Yeah, I'm really worried this is a hardware problem - I've been quiet these past couple of days testing the brand new GB radio and when that still had errors i then also tried the European one - the problem still persists. I have now downloaded every Atrix radio under the sun now so may try a few more...
This is quite frustrating as a) I really want to enjoy ICS as it really is a step up from previous versions of Android and b) I no longer have the option of selling this in its current state.
I'm also going to try a new battery as WikidClown suggested above, can't harm....I can pick up one on Amazon for less than a tenner.
One thing is for sure, I don't think I will be buying Moto hardware again!
ChrisSkeeles said:
I am having the same problem. And I am 100% stock with no mods. I just installed OTA 2.3.6 so I am waiting to see if that helped.
Click to expand...
Click to collapse
OK, so does anyone have any ideas? I have tested it using a load radios...and still nothing, it still randomly reboots. This is possibly the most unreliable handset I have ever owned
Sent from my MB860 using XDA App
Have you tried fastboot wipe? Maybe format internal SD and start fresh. Haven't had this issue just trying to help.
Sent from my MB860 using Tapatalk
jp2132 said:
Have you tried fastboot wipe? Maybe format internal SD and start fresh. Haven't had this issue just trying to help.
Sent from my MB860 using Tapatalk
Click to expand...
Click to collapse
I have formatted /system and /data etc between ROM changes, how would I do a fastboot wipe? I'm willing to try anything at this point!
Sent from my MB860 using XDA App
Actually, scratch that, I know exactly how to do that...except I can't boot into fastboot. Is this indicative of something wrong? Will I have to go back to SBF?
markdjj said:
I have formatted /system and /data etc between ROM changes, how would I do a fastboot wipe? I'm willing to try anything at this point!
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
i baught my atrix used. everything was stock. still had multiple reboots and battery pulls daily. on cm9 they seem to happen less. and the battery pull only happened once. but i know the issue must still be there. might try my wifes battery. her atrix has rebooted maybe 5 times ever. 3 since this last official update (she is still lock stock and 2 smoking barrels)
OK, trying a new battery is my last hope...I did a fastboot wipe this morning and for an hour and a half it was all going so well...but then the reboot happened.
I'm getting a bit fed up with this pos hardware...I can't even sell this thing in this state.
Sent from my MB860 using XDA App
Anyone have any other experiences? I have confirmed that it isn't the battery...I bought a new batter and within 45 minutes it has rebooted once and done the screen off thing where it needs a battery pull. Complete crap.
One thing to note is that it does seem to get very warm on the back, although the internals ( behind the battery) don't seem so bad. Is there any way to keep the temp down aside from underclocking? All my roms have always been under clocked so I know that doesn't make any difference.
The other thing I might try is to use something like Noled so the phone isn't completely idle. Might drain the battery a bit unnecessarily though....why couldn't Moto have put in an amoled screen?
Anyway, will report back once I've tried it.
Sent from my MB860 using XDA App
I used to get tons of random reboots and then I was told to get the app called "Wake My Android Pro". Settings -> Test Activity -> Auto Startup, and Stop Activity checked. Weird settings, I know, technically with stop activity checked it doesn't do anything, but ever since then I don't experience random reboots. This was a few months ago when I was on just CM7. I've always installed this app when I get a new rom and I've tried Neutrino, Darkside, Alien, Aura, CM7, Wet Dream, and currently on joker's CM9 beta 1 build and RARELY experience random reboots. It went from once an hour to once a month now. I'm also on the .36p radio if that helps.
SoupySauce said:
I used to get tons of random reboots and then I was told to get the app called "Wake My Android Pro". Settings -> Test Activity -> Auto Startup, and Stop Activity checked. Weird settings, I know, technically with stop activity checked it doesn't do anything, but ever since then I don't experience random reboots. This was a few months ago when I was on just CM7. I've always installed this app when I get a new rom and I've tried Neutrino, Darkside, Alien, Aura, CM7, Wet Dream, and currently on joker's CM9 beta 1 build and RARELY experience random reboots. It went from once an hour to once a month now. I'm also on the .36p radio if that helps.
Click to expand...
Click to collapse
Cheers, have downloaded and will report back. The most annoying thing about troubleshooting a problem like this is that there is no immediate 'it worked or 'it didn't work' ....it's just a waiting game! Thanks a lot though, really hope it does work (and thanks for replying, was starting to feel like I was answering threads to myself!). I have .36 radio installed already (I think, will check...it's the Brazilian one isn't it?) .
Just to check then...you have all the check boxes in wake my android ticked?
Sent from my MB860 using XDA App