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.
CM7 on the atrix appears to heat up rather quickly. Is this due to the Kernel but faux123 has mentioned (slave processor not able to be under clocked yet)? Has anyone else solved the heating issues? I've seen a bunch of posts on this, but i could never find a straight answer. Sorry if i missed it.
Undervolting seemed to fix that problem for me. I I also run at 1000 mhz rather than 1100.
sent from my Atrix via XDA premium
I actually felt less heat with CM7. Just make sure you have the kernel that came with CM7 not faux's 1.3 GHz one. Also, if you still feel it gets warm, try setting profiles in SetCPU. And if that doesn't work, read about undervolting and then try it if you're up for it.
plus one for the less heat, at first i had more but that was when i just flashed it and was charging + putting everything back on.
cm7 after boot up with same apps gives me 560mb ram, Alien #4 like 360. Blur takes alot out of the phone, also they have the fingure print scanner working and will hopefully be out next update of cm7
this phone on cm7 not being overclocked is like alien on steroids. mine boots up in like 5 seconds TOP i cant say much about the battery as Atnt in my town the last 2 days have been screwed up. cant get service for the life of me 3g dropped calls instantly. i just found out forcing it to egde everything works, but i think they finally fixed it tho.
Undervolting helps with the heat.
Sent from my CM860
So i have a verizon fascinate and am currently running cm7. (first tried the stable release but niw a nightly). Im eeally liking cm, but since i got it my battery life is garbage. Basically the drain seems to come from either the android os sercice or cell standby. Whenever i leave my phone inactive for a while, when i wake it up the battery has dropped a lot and tge phone is very warm. I have been modding this phone for a while, but im no android programmer. Purely based on the forum searchi. G ive done on the issue, it seemsblike cm7 has an issue with my modem or radio.
Extra info: my 3g/2g signals seem fine (always 0% time without signal). Wifi connectivity seems fine. Im also running glitch's kernal altho the problem has persisted with and without it (i did do a kernel cleaning first). I used the "go from anything to jb vanilla" guide cuz i was having issues switching to mtd at first (sry dont have a link rite now but it was on xda) . I get occassional force closes, but not really a problem. When i did a titanium back up, the very first time i flashed cm7 i Did restore system settings, but i did not do that every time since then. Ive done a fresh flash of the stable mod around 3 times trying different stuff, but this one is niggtly as i said, and each has had this issue.
If looked around a lot, and wgile this seems common, no one has posted a consistent solution or explanation to the problem, so thats what im looking for.
Sent from my SCH-I500 using XDA App
Hellomello13 said:
So i have a verizon fascinate and am currently running cm7. (first tried the stable release but niw a nightly). Im eeally liking cm, but since i got it my battery life is garbage. Basically the drain seems to come from either the android os sercice or cell standby. Whenever i leave my phone inactive for a while, when i wake it up the battery has dropped a lot and tge phone is very warm. I have been modding this phone for a while, but im no android programmer. Purely based on the forum searchi. G ive done on the issue, it seemsblike cm7 has an issue with my modem or radio.
Extra info: my 3g/2g signals seem fine (always 0% time without signal). Wifi connectivity seems fine. Im also running glitch's kernal altho the problem has persisted with and without it (i did do a kernel cleaning first). I used the "go from anything to jb vanilla" guide cuz i was having issues switching to mtd at first (sry dont have a link rite now but it was on xda) . I get occassional force closes, but not really a problem. When i did a titanium back up, the very first time i flashed cm7 i Did restore system settings, but i did not do that every time since then. Ive done a fresh flash of the stable mod around 3 times trying different stuff, but this one is niggtly as i said, and each has had this issue.
If looked around a lot, and wgile this seems common, no one has posted a consistent solution or explanation to the problem, so thats what im looking for.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
You could flash jt's vanilla gb rom. That has good battery life.
Sent from my SCH-I500 using XDA App
Plus do you have an overclock?
Sent from my SCH-I500 using XDA App
I have had the standby battery drain on every CM7 version and Kernel tried so far including 7.1 stable,7.0 nightlies,JT's Vanilla,and PoolParty. It's even worse if I shut phone down and don't plug in. It will drop 50 to 75% overnight with phone not on?
Has done it with undervolting,overclocking,and voltage control not even installed. This is first time I have seen others having similiar issues.
I think this is a known issue for all MTD roms on the fascinate, if I'm not mistaken.
Sent from my SCH-I500 using xda premium
TheBDub said:
I think this is a known issue for all MTD roms on the fascinate, if I'm not mistaken.
Sent from my SCH-I500 using xda premium
Click to expand...
Click to collapse
I lose only 5% to 10% overnight on CM7 never really notice how much on MIUI cause I never ran it long enough. I guess every phone would behave differently for MTD's or maybe you have an app or mulitple ones that refreshes frequently(Fancy Widget comes to mind).
Well that really sucks, because i do enjoy cm7. But this also means if i go back to a touchwiz configuration like stock dl09 i shouldnt have these issues right?
But before that, has anyone who had these issues tried anything (ie kernels or maybe standby mode power conservation setting, etc... ) that have at least noticeably improved your battery life? Right now mines pretty unbearable (im talking 8hrs while on but totally inactive), but if i can get it up a little i might b able to manage.
Sent from my SCH-I500 using XDA App
I am also experiencing poor battery life. I just flashed 7.1.0 yesterday and absolutely love it. Was using com rom for a few months, but a friend said to try out cwm 7. I used to get about 6 - 8 hours of Pandora while at work and today I only got about 4 before my phone shut off. I'm going to try completely killing battery and charge with phone off tonight an see if it's any better tomorrow.
Any other suggestions? I'm not a noob when it comes to custom roms and flashing (I used to flash the **** out of my G1) but there may have been something I over looked when switching to cwm7. I wiped everything a few times before flashing including battery stats and dalvic.
My battery life is actually really good. Running latest nighty, undervolted -75 across the board,stock kernel, and no overclocking.
Just can't figure why I lose 50-75% of battery overnight when phone is shut down and not charging?
I have the same issue with CM7.1, turning phone of at 80% battery at night to find it at 25% at morning
Is there knows solution?
Hi everybody,
I'm trying to understand how to fix this problem that's affecting me since I have this device.
I've got it in my hands in the end of November, and I've quickly unlocked and rooted it to install CM7. I don't like motoblur, so I didn't use it until I had CM7 on it. After few hours of happiness, I suddenly started experiencing freezes with black screens (I had to remove battery to unlock it) and auto-reboots.
I've wiped, fastboot-wiped, re-flashed, many times but nothing.
Tried different Roms such as redpill hybrid and dark side...same!
Googling around out there I've found hundreds of users with these two bad issues, and after hours of reading, and observing my own Atrix I've figured out what follows:
There are mainly two different issues. Although they are often considered the same, I think they are separate and I have both:
GPU issue: after playing a game or any app that "stresses" the GPU I have my Atrix not waking up after screen-lock. Black screen but if you call it is up and running somewhere in the background. it appears death, and I have to remove the battery to wake it up again. Device heating at rear-bottom.
RADIO issue: when the signal isn't that good and it changes often spot it reboots all alone.
trying to understand if it is hardware related (not an issue, but maybe small differences in the hardware of different phones) yesterday I went back to stock froyo.
Since then everything seems to work properly. Incompatibility of some ROMs with my device?
I want to stay on stock for some days to a deep test, after that, I will search for a good stock gingerbread firmware to flash.
I hope to find a solution, 'cause since I don't have CM on my device I don't feel it really mine .
Sorry for my English, hope to have made myself clear.
Thanks.
What kernel are you using? Some phones can't handle a high overclock. As for a gb rom I suggest darkside.
Sent from my MB860 using XDA App
Standard kernel @ 1Ghz. I've tried Faux's kernel @1.3 and 1.4, but I did it trying to solve the issue.
After good stock froyo and stock gingerbread experiences, I'm now happily running Aura deblurred.
Thank you, now I'll stay with Aura until CM9...
If you are experiencing the same issue look here: http://forum.xda-developers.com/showthread.php?p=21277632#post21277632
Sent from my MB860 using XDA App
I've only had this happen a few times and was wondering if anyone had this happen to them also. I'm rooted and run custom roms, it doesn't seem to be rom or kernel dependent.
For example, I had my phone on since noon and haven't really used it since then except a few times to check the time. I just pulled my phone out of my pocket and hit the power button... nothing. I held it down and it started to boot up. When this happens the battery is never dead (it was at 68% with the ext. battery this time), it just wants to turn itself off. It seems to happen when the phone is "sleeping", it's never done it when I'm actively using the phone so it's not an overheating issue.
It's not really annoying since it doesn't happen often, it just confuses me.
brando56894 said:
I've only had this happen a few times and was wondering if anyone had this happen to them also. I'm rooted and run custom roms, it doesn't seem to be rom or kernel dependent.
For example, I had my phone on since noon and haven't really used it since then except a few times to check the time. I just pulled my phone out of my pocket and hit the power button... nothing. I held it down and it started to boot up. When this happens the battery is never dead (it was at 68% with the ext. battery this time), it just wants to turn itself off. It seems to happen when the phone is "sleeping", it's never done it when I'm actively using the phone so it's not an overheating issue.
It's not really annoying since it doesn't happen often, it just confuses me.
Click to expand...
Click to collapse
still you might want to check the rom and kernel just in case, either re-flash or change.
if the problem still happens, use your warranty and get a new phone.
what rom, kernel, and recovery are you using?
I actually just happened earlier again. Got a text from a friend that she was here, so I went down and let her in, came back up and went to check my phone a few minutes later and it was off. WTF.
I'm currently using Nils newest business sense with the OC'd ICS kernel and the latest Amon Ra recovery. This used to happen on GB also so it's not a rom/kernel problem IMO.
It happens so sporadically (except for tonight apparently) that it's maybe happened 5 times since I got it on release day.
Maybe I have the governor in cpu master set too low? I have it at the lowest of 384 MHz, I've always wondered this: whats the difference between conservative and powersave?
did it happen while you were on stock GB or on a custom rom and kernel? maybe try relocking and running stock for a while and see what happens?
I honestly don't remember, it's been too long lol. It's not worth it to go back to stock and relock considering I like ICS too much.
brando56894 said:
I actually just happened earlier again.
I'm currently using the OC'd ICS kernel
Click to expand...
Click to collapse
that's the issue right there, run the stock kernel at stock speeds.
How could it be the ICS kernel when it's happened on GB also?
Which OC? I've read that the 1.8 causes random stuff like this, but 1.7 doesn't.
Sent from my ADR6425LVW using Tapatalk 2 Beta-5
3.0.16-g4a9c8a3 SebastianFM #1 is what the kernel info says
The zip name is Overclocked_kernel_v1.20_1836_MHz_by_sebastianFM.zip
Not all phones can handle overclocking.
Mine is stable about 98% of the time, it may actually be the extended battery that is causing the issue.
brando56894 said:
Mine is stable about 98% of the time, it may actually be the extended battery that is causing the issue.
Click to expand...
Click to collapse
9x out of 10 random reboots are from either undervolting too low or overclocking too high.
I went back to the stock kernel since it seemed to be a little choppy with the oc'd kernel. That may have been the problem after all.
Sent from my Transformer TF101 using Tapatalk