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.
I had a strange problem. I just happened to open preware just to poke around today a few minutes ago and saw the phantom kernel and got excited and uninstalled my other kernel and rebooted to install this one. All went well for the first install. then as i was browsing preware it refreshed and i saw there was a kernel update, so i hit update. after it rebooted, i cant seem to enable or disable wifi. if i uninstall the kernel its fine, but if i reinstall it, the same problem comes back its really weird. any ideas?
I am having the exact same issue. I took the same path as well upgrading F4. Hopefully WI comes out with another update to fix this.
A reboot allows you to re-enabled wifi, but this is a poor work around.
F15C will do until the bug is fixed.
That is why you wait until it goes out of beta.
sjc83 said:
That is why you wait until it goes out of beta.
Click to expand...
Click to collapse
What's the fun in that? Anywho, sucks that the kernel doesn't dig your wifi. Been running it all day at 1.8 rather stably, with battery actually doing fairly well.
sjc83 said:
That is why you wait until it goes out of beta.
Click to expand...
Click to collapse
I think you're on the wrong forum there dude. It says developers in the url - beta is where we live.
I hadn't noticed the WiFi oddity but tried it and sure enough. The prior F15 kernels had WiFi problems for me so I stopped using them. Seems that unixpsycho doesn't think much of people using WiFi.
Did you guys try the 1.8+ GHz speeds? My pad crashed at that speed - had to learn how to reboot using the hard buttons lol.
I have had mine lose WiFi 2x already and was unable to turn it back on w/o reboot
there'a an update 3.0.2-46. Did that helped?
My touchpad is completely stable using F4 at 1.8
Browsermark for me has resulted in scores around 38k with conservative governor, 54k with ondemand, and 74k with performance.
Battery drain seems to be only slightly worse than on F15c despite having both cores running at all times.
I tried the F4 Phantom recently and while it seemed promising at first, the second CPU always showed as N/A after I would wake it from sleep. I've tried uninstalling, going back to default settings, and reinstalling F4 and had these same results. I'm running warthog now and I don't experience the 'N/A' anymore and running stable so far.
Anyone else get the 'N/A' using the latest F4 Kernel (3.0.2-46)? Btw, I've been using it at 1.7Ghz.
I gave F4 a try. Also got wifi problem after a few hrs. Going back to warthog.
I don't have any problem with it. My WIFI works fine.
I upgraded from f15 this evening. Its noticeably faster on f4 with both cores running. Govnah suggests the battery is doing fine but I've lost about 5% in the last 30mins just browsing XDA... Doesn't sound quite right?
Wireless has been absolutely fine too.
edit: hour and a half later and govnah is showing 2nd core as N/A. Reinstalled but getting the same thing. Tablet seems just as fast though which is odd.
I have the same problem with F4 with all the profiles I saved, the second core says N/A. It did show the second core running when I installed it last night. I tried the 1.8, seems faster, but rebooted everytime when while loading sims social on facebook lol.
Edit: Weird thing, I did a device restart, and now the second core is showing. However, the device start didn't work this morning.
Same here. After about 30mins, my 2nd core shows as N/A. I do agree it does seem to keep its speed. Maybe its something with govnah?
I highly doubt it has anything to do with govnah. It is the kernel causing the issue. Have been running the earthly kernel and have had no issues at 1.7.
after latest update I have had NO problems
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)
(summarized below in tl;dr version)
Since my problem I need help with showed up after going back to stock + root, I thought I'd ask in general before filling up the ROM discussion in development about the problem that I found after updating to ICS (leaked).
Had an odd problem crop up on me with scrosler's CleanROM 2.2 SP1 running (will 'splain in a sec, and tl;dr sum-up at the end), so I relocked, flashed back to pre-OTA official firmware and then let the OTA run. All was good, and I was happy. I unlocked again, installed Amon Ra, reinstalled SU, and started putting in my happy-fun root required tools (Oh Titanium, I likes you so). Then, my problem reappeared.
So my problem is occasionally the touchscreen would act "wacky" at times. Specifically, while in my browser, sometimes when I tried to scroll while browsing, the display would act like I was using pinch-zoom. It acted like I was touching the top left corner of the display in portrait mode, and zoom-in/-out according to how I was moving my touch that I intended to scroll. Then I noticed that games which required multi-touch had significant problems reading constant touch on most of the top-half of the display (left half in landscape mode with the carrier name on the left). I like Age of Zombies, and while the game would start off running right, within 20-60 seconds, the movement virtual controller would rapidly turn on and off, leaving me able to fire but not move. Grand Theft Auto was unplayable, as every time I touched a direction key in driving mode, the system would lose track of my holding the gas.
Troubleshooting took a while, as I had installed a lot of apps, and made a few changes at once after everything appeared to run properly. Ultimately, the problem appears to be caused by underclocking, and I can't figure out how to kill that and lock myself at stock speed. Haven't tried an overclocking capable kernel to see if they run any better, and haven't tried checking voltages to see if bumping them on underclocks would fix it.
I have used Antutu CPU master, an old version of SetCPU, and System Tuner Pro (from 3c). I can set the min and max CPU to 1.52, and it seems to stay for a while, but eventually, the setting reverts to allowing underclocking and my touchscreen gets goofy.
tl;dr: My system, even after restoring to RUU/OTA, wants to underclock. When the CPU runs under stock speed, my touch-screen misbehaves, particularly in gaming, but also in browsing. Any help?
Thanks
Can almost definitely confirm it's just bad hardware at this point.
After running 2 days without problem other than the touch-screen issue noted above, the phone entered an persistent bootloop after I loaded Juice Defender today. Phone would reboot, come up to home screen, get a data connection, tell me how many new email and texts I had, then tell me an app (same every reboot) was not responding and reboot 2-3 seconds after I cleared the error. Even when I managed to get to market before a reboot and uninstall the last 2 apps I'd installed, the phone is still in a boot loop.
Appreciate all that took the time to read, and wanted to share that there's a pretty good reason no one could respond with a solution.
Well, it probably is bad hardware but two cardinal rules I have when working on any Rezound is NEVER restore with Titanium BU & don't use Juice Defender (and I have a paid version of it).
I have had both mess up certain phones & I do this stuff all day at work.
I only noticed the underclocking issue with the ICS roms. But, I believe it is due to the Kernels not supporting under/overclocking and scaling options yet.
AtLemacks said:
I only noticed the underclocking issue with the ICS roms. But, I believe it is due to the Kernels not supporting under/overclocking and scaling options yet.
Click to expand...
Click to collapse
I've had the same issue for a while now and nobody answered Me either. After a little research it seems we have bad digitizers. I say this because that was happening to me on gingerbread and I upgraded to ice in part to fix it.
Sent from my HTC Flyer P510e using xda premium
Me 2
aostl said:
I've had the same issue for a while now and nobody answered Me either. After a little research it seems we have bad digitizers. I say this because that was happening to me on gingerbread and I upgraded to ice in part to fix it.
Sent from my HTC Flyer P510e using xda premium
Click to expand...
Click to collapse
Okay so I have a similar problem.
I have hephappy cm9 prefinal installed just started having problems with rom. screen was acting funny so I turned on the touch point developer tool supplied with the rom. I have found that I have multiple touch points when scrolling with one finger.
So I used a apk called touch recalibrate that I got when I was on mik's cm7.
Which I have recalibrated aprox 7 times with no improvements so I set my cpu to min 600 max 600 smartassv2 this did not help either. If anyone has the answer to this problem please let me know.
Hi Guys,
Im no Genius when it comes to android, but I have done my fair share of programming before, but my SOD are killing me and a last resort is a warranty exchange as I cannot be without a phone.
So far I have been getting SOD about 5 times a day if not more, and I am one for tinkering with gadgets until i break or crash it, fix it and doing it all over again.
But anyway back on topic
I have noticed this in the build.prop
" persist.ril.mux.sleep=2 "
And so I wondered if this is causing my SOD, does anyone have any ideas regarding its uses?
Findings (as of 2155)
In my testing thus far I have changed it to "persist.ril.mux.sleep=1" using phone leaving it for an hour doing it over just for fun, And I have been SOD for 5 hours straight and haven't had any SOD or adverse battery drain
I mean this may not be the cause of the SOD for me, or anybody but I am up for trying just about anything
What is SOD?
Sent from my Motorola Atrix 4G using Tapatalk on AT&T, the company that disappoints me so much that I have to use my tapatalk signature to tell everyone
Sorry, Sleep Of Death
I have SOD here too. To me it's only happens when I turned off a data connection (3G or wifi).
I use LoadMonitor app as a workaround for a while, with success.
At now I'm using Neutrino 2.5 CM7 ROM with success too. I think it's more a blur rom problem than cm7 one.
Let us know about your progress.
So if you disable load manager you would get SOD?
I am making a script to update a few things so far no SOD for me, after a few tweaks
What settings are you using on load manager ?
Any info you can give me will help in me tracking down some of the errors and temporary fixes people are using to avoid the dreaded issue
Oh, THAT's what that was!
I forgot to turn the wifi back on a few nights ago when I said "Hey, let's watch some movies on netflix with my super-duper mirroring-abled phone!" So an hour into it, LBE Privacy warns me I'm about to max out my data, and I go turn the damn wifi back on but turned OFF the 3G.
Then last night I go to wake up my phone and the screen is "black but on", & took a couple of tries to wake it. I'm on Nottachtrix.
Harrison85 said:
So if you disable load manager you would get SOD?
I am making a script to update a few things so far no SOD for me, after a few tweaks
What settings are you using on load manager ?
Any info you can give me will help in me tracking down some of the errors and temporary fixes people are using to avoid the dreaded issue
Click to expand...
Click to collapse
I'm a bit confused here. I don't know what "load manager" is.
What a sad is I used LoadMonitor app (from market) as a workaround.
LoadMonitor just monitor taks that are running in your device. But it have an option that claims to prevent device deep sleep. So, when I checked this option my device don't get SOD.
It's a workaround, as I sad, and I don't know how LoadMonitor do that.
What is load manager?
Thanks
I had a similar issue, I installed SetCPU and set my minimum speed to ~456(faux 1.45 Kernel).
Never had the problem since.
cldot said:
I had a similar issue, I installed SetCPU and set my minimum speed to ~456(faux 1.45 Kernel).
Never had the problem since.
Click to expand...
Click to collapse
cldot do you use blur rom or cm7 one?
Thanks
My bad meant load monitor
Sent from my MB860 using xda premium
I tried some roms and the only one I hadn't random reboots was jokersax11 alpha7 (ICI), now I'm on beta 0.2.0 and had reboots.
I'm having the same problem. I've tried 3 different ROMs. I used Nottachtrix, following the directions to the letter with reboots and hard locks. Recently I flashed back to 4.5.91 (w/pudding) and I was having the same issues. I noticed that on the hard locks, my phone appeared to be warm, so I used SetCPU at 216MHz and still had hard locks and random reboots. I've not set the lowest setting at 301 and so far I haven't had any reboots, but its only been about 5 hours. But I was having them at least once every few hours.
BTW - I also noticed that I only had the freezes and hard locks when the phone was running on the battery. I rarely had problems when the phone was on the dock or USB charger, however, I did have reboots when it was on the wall charger.
Another program you can try is call 'Wake Lock' available from the marketplace. I haven't used it yet, I'm still experimenting with load monitor.
Wake lock has a few different options and has some really good review.
I confirmed that Neutrino 2.5 CM7 Rom works great without reboots.
That's a patch you need to apply to correct a battery drain problem of the original version. Notorious544d are working in a 2.6 version including that patch.
To me it's working like a charm. I'm testing for two days but, of course, everyone needs to test it in your own device.
PS: Follow this instructions to install a battery drain patch in Neutrino 2.5 (or wait for a 2.6 version):
http://forum.xda-developers.com/showpost.php?p=23179486&postcount=4258
Update 13/03/2012: Notorious544d released Neutrino ROM 2.5p with battery patch and some other things.
See you!
what patch?
marcosvafg said:
I confirmed that Neutrino 2.5 CM7 Rom works great without reboots.
That's a patch you need to apply to correct a battery drain problem of the original version. Notorious544d are working in a 2.6 version including the patch.
To me it's working like a charm. I'm testing for two days but, of course, everyone needs to test in your own device.
See you!
Click to expand...
Click to collapse
Could you point me to that patch? I can't seem to find it. Thank you
Sleep Of DEATH!!!
I was encountering that problem for a while but then I figured that something went wrong when I was flashing CM7 Beta. So I flashed Aura's ROM, and then Reflashed CM7 Beta and only experienced it once a month at most after that, Hope it helps
eNorby said:
Could you point me to that patch? I can't seem to find it. Thank you
Click to expand...
Click to collapse
Follow this instructions (or wait for a 2.6 version):
http://forum.xda-developers.com/showpost.php?p=23179486&postcount=4258
Update 13/03/2012: Notorious544d released Neutrino ROM 2.5p with battery patch and some other things.
Atrix SOD & Random reboots related to Wifi?
Does anyone know if the Atrix SOD & Random reboots are related to WiFi. I've had my wifi off all day and I've had no crashes.
I'm going to run it for a few more days without Wifi and see what happens.
I don't know about other guys, but wifi and 3G was the cause of my Atrix SOD and reboot problems.
Solved it using Neutrino Rom CM7 based.
See you!
Still working on my SOD issue, but recently, I disabled most power options, turned off wifi, rebooted and I've been running for 2 days with no crashes. After day 3, I'm going to turn wifi back on reboot and see what happens.
Update 1
After 3 days with wifi disabled, I've had no crashes, no freezes or random reboots. I'm going to enable wifi again and see what happens.
Update 2
After turning enabling my wifi and using it briefly then turning it back off, I had a random reboot later that evening.
The more I used my wifi, the more frequent my crashes became.
Interesting side note
I can enable all my radios when plugged into the desktop charger and I won't experience any crashes, however, if plugged into to the AC charger, I've had reboots and freezes.