Related
im wondering if it is the speed scripts? i am using eclipse 1.1 now so im going to see if that fixes it. but i have been getting the freeze when unlocking the phone, and sometimes randomly when im using the phone the screen goes 100% unresponsive...the buttons work, but nothing else...then after about a min or two it comes back..VERY annoying...
Do u reboot or clear system caches on a regular /daily basis? This may help.
Sounds like things are getting clogged up. I used to have that problem a while ago before I started rebooting once a day. Usually when I wake up and sometimes twice a day. It is healthy for an android phone to be rebooted once a day. Just plain works better.
oh this has happend right after a SBF or a reinstall of an OS, so there was not even a day on it. it happened this morning once when i unlocked the phone BUT i had that speedy script installed, i resotored from a back up before i installed that scrpit so im going to see if it happens again....i hope it is not hardware related..
dvigue said:
oh this has happend right after a SBF or a reinstall of an OS, so there was not even a day on it. it happened this morning once when i unlocked the phone BUT i had that speedy script installed, i resotored from a back up before i installed that scrpit so im going to see if it happens again....i hope it is not hardware related..
Click to expand...
Click to collapse
I hope it isn't also.
It has only happened to me in the past like I said. It's been a long time tho((knock on wood))
I have also been running the speedy script v6 . I only made one change and that was deleting the 3gturbo entries in the one script. And I haven't had this problem yet at all. Been running for two and half days now.
has this also happened on 2.3.3? i was wondering if it was a 2.3.4 issue?
Sounds like something clogging your memory. When I start fruit ninja my x2 screen goes unresponsive for up to 20 seconds I assume its just memory management during game startup. Are you using a task killer to maximize free ram? This will cause background apps that you may have killed to restart if they are called upon. That would cause the phone to bog down temporarily
Sent from my DROID X2 using XDA App
nope no task killers at all. i noticed using system panel i was at only 77 mb using eclipse...
My phone doesnt freeze but it does randomly reboot no matter what rom, script, length of use before a restart, or whatever.
booked said:
My phone doesnt freeze but it does randomly reboot no matter what rom, script, length of use before a restart, or whatever.
Click to expand...
Click to collapse
I guess I got pretty lucky with not getting reboots.
Even before I rooted and rom'd up I think I MAY have had one random reboot. I guess I just got lucky. Basically the only major problem I have had that others have os the music skipping I used to encounter lag occasionally but since I started my daily reboot routine lag is pretty null on most occasions.
dvigue said:
im wondering if it is the speed scripts? i am using eclipse 1.1 now so im going to see if that fixes it. but i have been getting the freeze when unlocking the phone, and sometimes randomly when im using the phone the screen goes 100% unresponsive...the buttons work, but nothing else...then after about a min or two it comes back..VERY annoying...
Click to expand...
Click to collapse
I wonder the same been using eclipse straight up except for setting the min to 216 instead of 312 never had any issues period . Might be worth getting rid of speed scripts and see if that is the issue.
2.3.4 was made pretty much to fix the lockups and reboots. It might be something with your backups. I know I just used a backup a couple days ago after giving up on upgrading to 2.3.4 and until today when I finally upgraded to 2.3.4 it was slow, laggy and unresponsive. Mind you before that last nandroid, it was working amazingly.
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)
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
Hey guys. I have had my EVO LTE since it was released last year and all of a sudden this past week the phone gets really hot and then will reboot itself. It does this sometimes when I am playing a game and sometimes even when I am not doing anything. The phone also seems to die faster than it used to. Is maybe the battery going in it? Any thing I should try?
I have not done any changes to the phone in months. I am still running MeanRom 6.5.2 and stock kernel.
sharky17 said:
Hey guys. I have had my EVO LTE since it was released last year and all of a sudden this past week the phone gets really hot and then will reboot itself. It does this sometimes when I am playing a game and sometimes even when I am not doing anything. The phone also seems to die faster than it used to. Is maybe the battery going in it? Any thing I should try?
I have not done any changes to the phone in months. I am still running MeanRom 6.5.2 and stock kernel.
Click to expand...
Click to collapse
I recently had the same problem. It would overheat constantly, especially when playing a game, and if you charged the phone and tried to use it at the same time, it would only overheat faster. I got my phone when it first came out as well. The tech made up something about a short in the power button, but they did end up replacing the phone for me. You'll have to go back to complete stock of course before bringing it into the sprint store. If you need any assistance getting your phone backed up or back to stock, shoot me a message.
Thanks for the info! Yeah I know I will bring i have to put it back to stock before bringing it in. I'm good with doing all that.
sharky17 said:
Thanks for the info! Yeah I know I will bring i have to put it back to stock before bringing it in. I'm good with doing all that.
Click to expand...
Click to collapse
If you do any overclocking, that may be the issue. Try to set it to a much lower value. The processor in this phone runs at an approved max. of 1.5GHz. Try to throttle it back to 1.0GHz and see what that gets you. I know the meanROM has a few versions that automatically overclock and that may be the issue as well. If you don't overclock,(speed up the natural CPU clock) then I would bring it back to Sprint. It seems like it may be a manufacturer's defect.
Hope that helped,
Chris C.
chris674 said:
If you do any overclocking, that may be the issue. Try to set it to a much lower value. The processor in this phone runs at an approved max. of 1.5GHz. Try to throttle it back to 1.0GHz and see what that gets you. I know the meanROM has a few versions that automatically overclock and that may be the issue as well. If you don't overclock,(speed up the natural CPU clock) then I would bring it back to Sprint. It seems like it may be a manufacturer's defect.
Hope that helped,
Chris C.
Click to expand...
Click to collapse
It is set at 1.3GHz but as I have said I haven't changed anything in months on it. Do you still think I should change it? I will plan to do some backups this weekend so I can return to stock for Sprint to look at.
sharky17 said:
It is set at 1.3GHz but as I have said I haven't changed anything in months on it. Do you still think I should change it? I will plan to do some backups this weekend so I can return to stock for Sprint to look at.
Click to expand...
Click to collapse
When I first noticed the heat problems, my phone was on MeanBean 3.09 and underclocked. I tried underclocking it more, I even tried removing the case to see if it would cool off. I decided to flash it all back to stock and see if that was the problem, and the phone still overheated on stock. Out of curiosity, have you dropped the phone or damaged it in any way?
DXtremz said:
When I first noticed the heat problems, my phone was on MeanBean 3.09 and underclocked. I tried underclocking it more, I even tried removing the case to see if it would cool off. I decided to flash it all back to stock and see if that was the problem, and the phone still overheated on stock. Out of curiosity, have you dropped the phone or damaged it in any way?
Click to expand...
Click to collapse
I would flash with the stock Rom and bring it back to Sprint. If u guys underclocked it and it still overheats, then I would think it is a manufacturer's defect. It doesn't make sense that the phone will still overheat with the cpu being underclocked.
Chris
im rooted n upgraded from 128 fw. I gets random reboots. Any fix this issue?
When does the reboots happen? When you do something specific, like playing heavy 3D games? Maybe overheating causes phone to restart. Have you checked temps of CPU?
ExtaSpace said:
When does the reboots happen? When you do something specific, like playing heavy 3D games? Maybe overheating causes phone to restart. Have you checked temps of CPU?
Click to expand...
Click to collapse
totaly random
Is that the latest firmware available for your model?
I've experience random reboots as well after I flashed the pre-rooted TWRP with .167 system and kernel. I've also noticed that the phone reboots frequently when downloading apps in Google Play.
i had rr yesterday (always when phone goes to deepsleep) and solved with a factory reset, then installed one by one mods checking there are no reboots
Doing a clean install/flash, wiping dalvik cache, and bumping max cpu clock speed to 1.459 GHz and min to 400 GHz seem to fix the random reboots on my .167. I haven't had a rr for a week now.
Edit:
I was a doing a little more browsing and I think I found the solution over in the general forums. It sounds quite promising and seems like it's stood the test of time (which is 4 days that's been recorded) I'm in the middle of trying this method and I'll get back to you guys in a few days if it actually works.
Find the method here - http://forum.xda-developers.com/m4-aqua/general/guide-fixing-random-gplay-app-install-t3338362
Good luck
Original Post:
I've even had problems with random reboots on the stock 26.1.A.1.112 Commercial & Journalist version with nothing but being rooted. So i don't think it has to do with programs.
In my honest opinion the problem seems more to do with the stock roms having a problem with root on a bootloader locked m4 aqua.
The only thing that I know can almost certainly cause a reboot is updating apps on the play store. I'll usually have at least 1 reboot during that.
I've been fortunate enough this time around only receiving a reboot about once per day which is manageable for me but it's still an underlying issue.
Any new insights into this would be great. Maybe we can collaborate.
Likewise. Although i can sometimes get about 2 days without rebooting. But i do notice that the reboots are usually when updating apps,(though not always) or randomly when battery is fully or almost fully charged.
Currently on 3.111 rooted, xposed installed.
dagger1 said:
Likewise. Although i can sometimes get about 2 days without rebooting. But i do notice that the reboots are usually when updating apps,(though not always) or randomly when battery is fully or almost fully charged.
Currently on 3.111 rooted, xposed installed.
Click to expand...
Click to collapse
Dude, try this! I've been running from a fresh install to having over 6-7GB of apps installed and my phones been on for hours now with no reboots.
http://forum.xda-developers.com/m4-aqua/general/guide-fixing-random-gplay-app-install-t3338362
Thanks man. Bit of a hassle though. I might try it though when i have more time.
dagger1 said:
Thanks man. Bit of a hassle though. I might try it though when i have more time.
Click to expand...
Click to collapse
That's awesome. You won't regret it. I gave up on having root awhile ago because of the reboots and I'm so happy that this fix works. It feels so freeing!
If you need any help when you do go for it, feel free to message me.
Good luck!
mobbid said:
Doing a clean install/flash, wiping dalvik cache, and bumping max cpu clock speed to 1.459 GHz and min to 400 GHz seem to fix the random reboots on my .167. I haven't had a rr for a week now.
Click to expand...
Click to collapse
How do you bump the cpu clock speed?