Related
I have been having my phone shut off for no reason at least 5 times a day. Even when phone is in sleep mode. When I wake my phone I have the bamf toolkit in my notification bar that says unclean shutdown settings not applied, that's how I know it keeps rebooting while in sleep mode. Only reason I haven't made the jump to 1.7 is because I like the extras that are made for 1.6.3. I didn't wanna try and flash 1.7 and then apply 1.6.3 mods. Running stock kernel that came with Rom. It didn't used to do anything like this when I first installed it. It seems like it's getting worse over time. Anybody else having the same problem or similar? Any ideas or thoughts would be helpful. I'm actually thinking about putting GB back on. I just wish I knew what the odds of me ending up with a expensive brick were before i put it back on.
I had the same problem. Flashing the second radio on the radio thread finally solved the problem for me.
Turns out this is obviously an issue with my phone, and not the new kernels I have been using. All though it has only happened with Fserve's franco.Kernel.v19.3-gbs.v15 and franco.Kernel |.v19.4| 2.6.32.46. But the problem is the same between both of them, happens less often with v19.4. But rather than bother the kernel developers I will put a general post here. I'm sure that they already have their hands full, and I don't think it's a kernel issue anymore.
The issue:
My lockscreen keeps burning the image into my LCD when I put the screen to sleep. Always is the last image it was at when I shut it off, and it takes around 3-4 hours after flashing a kernel to start with the issue.
It's basically the same type of thing that happens if you leave a computer monitor on at the same screen for day or so, the image stays on the screen for a while because it has burned itself into the monitor.
I cannot take a Logcat as it is disabled in the franco kernel I am currently running. Current specs are in my signature.
Essentially I am trying to track down the cause of this issue, as it seems to happen across different setups, no matter the LCD sleep settings I set, and doesn't go away with lower overclock settings. But when I flash my phone back to OEM specs with KDZ updater it does not produce the problem at all.
It has to be software related because if it was my hardware, It would produce the same result when KDZ updated.
Anyone have this issue at any point? Any suggestions on how to fix it?
I'm not sure how much use it'll be to you, but if it's actually a kernel issue, and not just an android problem, this might be useful:
instead of logcat you can use dmesg.
in a terminal app or adb shell:
Code:
dmesg > /sdcard/dmesg.txt
if the /sdcard path isn't appropriate for your device, replace it with something accurate.
bigsupersquid said:
I'm not sure how much use it'll be to you, but if it's actually a kernel issue, and not just an android problem, this might be useful:
instead of logcat you can use dmesg.
in a terminal app or adb shell:
Code:
dmesg > /sdcard/dmesg.txt
if the /sdcard path isn't appropriate for your device, replace it with something accurate.
Click to expand...
Click to collapse
No luck, not supported in this kernel. I return the message
Code:
dmesg > /sdcard/dmesg.txt
klogctl: Function not implemented
Just returns an empty dmesg.txt file.
gahhh, i'm sorry. thought that'd work for sure.
maybe adb bugreport?
FOUND IT!!
Turns out the screen off animation in CM7 was the cause of my issues. For whatever reason, with the screen off animation disabled my screen no longer burns any images into the LCD. I have been burn free for 2 days now.
Weird. Oh well
EDIT: **** me it's back again, what the hell? This is truly a noggin scratcher of a problem here...
I have the bugreport:
Download the bugreport(report.txt)
Compiled through Terminal Emulator v1.0.29 and taken 5 min after screen burn was noticed.
Currently running franco.Kernel v19.3 CFS to see if the problem goes away, as I ran this kernel for a week with absolutely no issues.
Update: Logcat is working on v19.3 CFS version so I was able to take a look at what the phone was doing. Turns out the screen state is set to 0 when I turn it off, and it runs all the screen state off commands properly. But, with logcat not working on v19.4 CFS I am not able to compare notes. Going to look through the bugreports I have and see if there are any differences.
Aha! I have found something that might be of some help. In the battery history section of the bugreport, v19.3 does a Kernel wake_lock when turning the screen on and off, while v19.4 is doing just a wake_lock. They may be versions of the same thing, but maybe the difference in the process is what's causing my problems? I ran v19.3 for around 6 hours today and I had no issues with screen burning.
Well, after 8 hours of 19.3 CFS I still am facing the same screen burning problem. Nothing seems to be making the problem go away. My next step is going to KDZ flash my phone back to stock and run it like that for a day. If the problem persists I am taking it in to be serviced because it is definetly a hardware problem.
Update:
Day One of running stock V10V firmware, and no screen burning occurring at all. Going to keep it running like this for the rest of the week to see if anything will pop up. Maybe CM7 went on a fritz? I dunno, I'm no closer to finding the source, but it's looking like software right now.
Been running stock V10V software for more than a week, no symptoms of any type of screen burning. Definitely software related, I am going to begin flashing again tomorrow and see if anything turns up. Will report back if I find the issue again, as for whatever reason this could have just been an anomaly I have found in the custom ROM's and kernels.
On another note, It'll be nice to have this phone running fast again
Okay, approximately 4 hours into CM7 with francokernel v19.4 BFS, I am experiencing the same LCD Screen burning issue. Nothing is making it go away in any settings. Going to try void forever and see if anything changes.
Download Bugreport HERE(log1.txt)
Shofire91 said:
Been running stock V10V software for more than a week, no symptoms of any type of screen burning. Definitely software related, I am going to begin flashing again tomorrow and see if anything turns up. Will report back if I find the issue again, as for whatever reason this could have just been an anomaly I have found in the custom ROM's and kernels.
On another note, It'll be nice to have this phone running fast again
Click to expand...
Click to collapse
How does that happen? If the screen is not on, how could an image be burned onto it? Or is it not 'physically' burned on?
dancom96 said:
How does that happen? If the screen is not on, how could an image be burned onto it? Or is it not 'physically' burned on?
Click to expand...
Click to collapse
Not too sure, it's almost like the backlight LED turns off, leaving the lockscreen image there to burn into the LCD. Or maybe just a programming anomoly?
Either way, 2 hours into void forever's rom I am getting the problem once again (argh!!).
It only seems to do this with a custom ROM, the v10v firmware ran without any LCD issues whatsoever. Now why would it do that? I ran V10V rooted and clockworkmod recovery and no LCD issues. Only with a custom ROM.
Download the bugreport here(log2.txt)
MIUI-Gen71 v0.666 Suicidal Edition
This is apparently the answer to my problems. Since it is based off of CM7.1 6.6.1 it is not producing the LCD issue that I have been having with CM7.1 6.5.7.
Been running this ROM for about a day now. No lockscreen burning issues so far. Cross my fingers and hopefully the issue is gone.
Makes sense since the other roms I've tried were based off of 6.5.7. Could have been a CM7 issue in the first place.
Shofire91 said:
MIUI-Gen71 v0.666 Suicidal Edition
This is apparently the answer to my problems. Since it is based off of CM7.1 6.6.1 it is not producing the LCD issue that I have been having with CM7.1 6.5.7.
Been running this ROM for about a day now. No lockscreen burning issues so far. Cross my fingers and hopefully the issue is gone.
Makes sense since the other roms I've tried were based off of 6.5.7. Could have been a CM7 issue in the first place.
Click to expand...
Click to collapse
i dont know it it is cm7 6.5.7 issue cuz i never experienced ur problem with this rom or rom based on 6.5.7
I'm working on the assumption that my problem is just an anomoly that I have come across. Searches returned nothing, and I was able to run 6.5.7 without a single issue for weeks, across different kernels. It just came out of nowhere, maybe it will still turn up in 6.6.1, but at this point only time will tell.
This thread is essentially a record of my findings over time to help anyone who has had this issue(there are a few, but not many) figure out where to turn on fixing the problem.
Took a bugreport in 6.6.1 MIUI just for anyone to look through and see if any differences turn up. I have yet to find something that points to the cause.
Download the bugreport(log3.txt)
UPDATE:
3 days in and nothing so far, seems to have been a problem in CM7 6.5.7. Haven't had a single bug since.
Im also experiencing the lcd burn issue on cm7 6.5.7 with goldleaf kernel... doesnt happen on other kernels tho. Ive had this issue before with stock froyo when i got my phone. Since goldenleaf or whatever is based on stock kernel then i think it must be the kernels fault...
Wierd, I had the same trouble as soon as I tried fserve's kernel as well. Mind you it was 19.3 gbs v15 where it all began for me. But yet it went away when I flashed the phone back to stock with KDZ updater, but still came back after reflashing CM7 6.5.7 with franco's 19.4 kernel, and any other kernel after that, even the stock CM7 one. Even any ROM I used that is 6.5.7 based caused the problem to come back. CM7 6.6.1 seems to be the only answer for me at this point. Not sure what is causing the problem but it seems to be based from fserve's modded kernels, but yet it only manifests itself on a few number of devices. Is your O1 a P500 or a P500h?
Mine is p500. I flashed v18b2 now. Gonna give it a couple of hours and see if the problem still exsists.
Sent from my LG-P500 using xda premium
ert69 said:
Mine is p500. I flashed v18b2 now. Gonna give it a couple of hours and see if the problem still exsists.
Sent from my LG-P500 using xda premium
Click to expand...
Click to collapse
Let me know how it turns out.
Shofire91 said:
Let me know how it turns out.
Click to expand...
Click to collapse
Nope. Still can see my lockscreen. I think it might be the roms fault as some have stated before. Plus, that kernel drained my batt like crazy so I went back to goldenleaf.
Sent from my LG-P500 using xda premium
Were you not having the same trouble with goldleaf as well? It has to be the ROM because I am running the setup in my signature since Sunday. No issues at all. Something about 6.5.7 and fserve's kernel don't seem to mix for certain phones. I wonder what the difference is that causes it? I wish I knew more about Unix and Java so I could figure it out. Any developers out there with a little free time?
Sent from my LG-P500h using XDA App
I am surprised that I can't find a lot of people talking about CM7 nightly builds running on the Verizon Fascinate. Anyone out there running a recent nightly? I have already rooted my phone, and am thinking about flashing a nightly, but I want to make sure it's pretty stable first.
How are your experiences?
It's fairly stable. The volume in calls used to be really low but that was recently fixed.
The only major problem that I encounter is that Wifi and Data don't work when they say they're working. All you have to do is switch in and out of Airplane mode once or twice and it should work, but it might get frustrating for some people.
I'm using build 67 with no issues. Loving It.
Sent from my SCH-I500 using XDA App
I've been using the nightlies for quite some time now. As stated, they did have problems, they've pretty much all been rectified - I'm pretty damn picky when it comes to bugs with a phone I use daily, and I have no issues, everything seems to work fine.
Only problem, not sure when this was introduced because I got lazy in updating the nightlies, but somewhere between nightly 35 and when I updated to nightly 68 this morning somebody bundled this "LED Notification Wannabe" crap and I can't figure out how to turn it off - some sources say you can't.
Basically when you get an e-mail or text (every 5 minutes for me), your soft keys stay lit up solid until you view it. Haven't found out how to disable it, not even in the CM7 settings. It's annoying as all hell because it basically means my soft keys are lit up all day.
Though yeah, aside from that, in any of the nightlies I've used pre-36, I haven't had any issues - I mean yeah, I had the volume problem and the SD card wipe, etc., but all of that stuff was rectified a long time ago. Bug free, very stable nightlies...but don't count on it I guess?
Syndacate said:
Only problem, not sure when this was introduced because I got lazy in updating the nightlies, but somewhere between nightly 35 and when I updated to nightly 68 this morning somebody bundled this "LED Notification Wannabe" crap and I can't figure out how to turn it off - some sources say you can't.
Basically when you get an e-mail or text (every 5 minutes for me), your soft keys stay lit up solid until you view it. Haven't found out how to disable it, not even in the CM7 settings. It's annoying as all hell because it basically means my soft keys are lit up all day.
Click to expand...
Click to collapse
Sigh*
Go to Settings > Profiles > Default
In the Application groups select each of the groups and click on "Lights mode" set it to OFF. To apply the changes you need to select a different profile and go back to the one you modified (Default in this case)
m0r0n3s said:
Sigh*
Go to Settings > Profiles > Default
In the Application groups select each of the groups and click on "Lights mode" set it to OFF. To apply the changes you need to select a different profile and go back to the one you modified (Default in this case)
Click to expand...
Click to collapse
Ah, okay, most of the other how-tos for this are deprecated (ie. LED disable in places that no-longer exist in CM7 settings, but I also found this, but to no avail for me. I didn't know I had to change profiles at the end. Thanks, I'll try that now, god I hate that so much .
my personal experience with CM7 on the Fascinate: it's half-baked.
phantom ring problem, where the phone continues to ring after you pick it up to speak to someone.
data stops working and you have to cycle airplane mode to have it work again
battery life sucks
GPS takes 10 minutes to hone in on your location.
I just installed powerwashed GB last week and all these issues are GONE. I have to put up with Sense UI now, but it's a price well worth paying to get rid of constant bugs.
I'll give CM7 another shot when they have a good stable mod.
I'm really happy with the all of the newer builds. In the past (back in the days of build 35) I had lots of bootloop issues and freezeups. Pretty much everything is resolved now.
I don't think I could NOT have a CM7 nightly on my phone haha. You should really check them out.
Even if you hate it just restore your backup!
CM7 used to be very sensitive to low signal areas; the data connection would disconnect and not recover. The only solution then was to try airplane mode and if that didn't work pull the battery.
Has this been fixed?
AuroEdge said:
CM7 used to be very sensitive to low signal areas; the data connection would disconnect and not recover. The only solution then was to try airplane mode and if that didn't work pull the battery.
Has this been fixed?
Click to expand...
Click to collapse
For me i'm going to say no, not really. My house is in a low signal area and though its improved I still have to do airplane mode from time to time. Different radios made little difference, though ED05 is slightly better than EC09
Sent from my SCH-I500 using XDA Premium App
For those with data issues try this? I haven't had a problem since.
Obviously replacing Miui with CM7.
OhioYJ said:
For those with data issues try this? I haven't had a problem since.
Obviously replacing Miui with CM7.
Click to expand...
Click to collapse
I did see jt and andmer on twitter talking about this data issue. So it makes sense that there might be a fix for it in MIUI. Where do I find jt's kernels at?
AuroEdge said:
I did see jt and andmer on twitter talking about this data issue. So it makes sense that there might be a fix for it in MIUI. Where do I find jt's kernels at?
Click to expand...
Click to collapse
It could just be Miui, I haven't tried any other roms since I got it working, so it might not work in VGB or CM7. I prefer Miui so once I got it working, I've just left it alone.
I got JTs Kernel from a link he posted on his Twitter account, on the 12th obviously.
AuroEdge said:
CM7 used to be very sensitive to low signal areas; the data connection would disconnect and not recover. The only solution then was to try airplane mode and if that didn't work pull the battery.
Has this been fixed?
Click to expand...
Click to collapse
Arg, I have this problem - maybe had, I haven't been in a long signal area for awhile.
Doesn't matter though, NOBODY around here or on IRC believed me about the issue, they all just said to re-key the phone by switching phones on VZW to fix that problem.
I'm glad to see people have seen the problem outside of just me.
I haven't tried it lately, b/c there's tons of coverage in my area, but in the earlier builds I definitely had that problem when there's barely any coverage (about 105db signal) for a long time, no wifi on, 3G just cuts and never turns back on.
Never thought I'd be happy to see somebody have an issue, but now I am.
But hey, everybody thought I was lying then so maybe it's not an issue at all? Who knows...
EDIT:
The problem was also shown on VGB and PP.
Running the latest CM7 nightly with Glitch kernel. It flies; rarely have stability issues.
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)
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.