Related
Hi Guys,
I'm new here, but have been following and reading these forums for quite some time now. Great Stuff!
anyhow, my problem, recently purchased a HTC P3600i PRO. Put a custom ROM on it, seemed to be running great over the last few weeks, but my problem is this. Now and then my phone pda will lock up and I'm forced to reset it. What happens is, I am still unsure as to why this happens, but lately it's started freezing up, and when I click on my start button, it shows my menu, and then when I click programs, it shows as "empty" when I know there's nothing empty, it's filled with stuff, randomly this happens to my settings window as well. Basically stuff randomly dissapears from my start menu, shortly after, 5 to 10 seconds, it locks up. The next thing I do or click on after seeing things disappearing from my menu, it freezes. I then have to do a soft reset, and after doing a soft reset, it's as if it's done a hard reset and wants me to re-configure the time, click on all 4 corners, etc.. I use have to use SPB Backup to do a full restore of my phone/settings/contacts/software etc..
Can anyone help?
Also, just to update.. I restored my phone with a backup today, and it seems to be running well again for some strange reason. Is it because it's overheating? getting hot or what? I'm not sure what it's doing. Please help
Figured it out
My backlight whilst on battery was set to brightest. figured it was overheating as it felt warm too.. I turned it right down to 3 bars from lowest, and it's fine now
Guess it my screen and battery were getting quite hot and the CPU was overheating. All resolved.
I got a HTC p3600 for about 10 months. i used to have the backlight set to minimum.
now i update my rom and it got crashes so often, almost every day, and I need soft restart the device all the time when get crash.
The worse, sometime my display picture just broken + crash, and I need more than once to restart the pda. When I restart the device sometime the display just turn black color moving from top to bottom, or sometime with colourfull dots on screen, and the device does not want to be restart.
In that case i take the battery to turn off the device.
Sometimes i need to wait some minutes until i can restart normally the system.
It usually crashes when it is connected to the computer via usb (charging the battery) and i need to use it. (i check and it is very hot)
Also, when i use wifi it tends to crash (very hot too)
Since i upgrade the rom my backlight settings are set higher...i reduce the backlight, to reduce heat and test the system stability, but i really think it is crashing due to overheating.
i have had my atrix for 4 days now and its locked up 3 times were i had to take the battery out to restart it anyone else have this problem anyone no how to fix it or should i return it for a new one
kga943 said:
i have had my atrix for 4 days now and its locked up 3 times were i had to take the battery out to restart it anyone else have this problem anyone no how to fix it or should i return it for a new one
Click to expand...
Click to collapse
Did you install any applications from the market? Is your phone freezing while a certain application is open or does it freeze even on the homescreen? If you have a lot of applications installed try to deinstall and look if it becomes better. If not try a factory reset. If it still freezes than return it for a new one.
Would you mind saying what you were doing when it locks up?
If it's during Music, it doesn't actually lock up, it just shows a black screen for about half a minute. Everything still functions, it just doesn't show.
Two times trying to answer a call the screen would not unlock nothing would work I had to take the battery out and just todayit was sitting on my desk and it would not turn on when I tried to use it
The green message light was on very dim and I had to take the battery out
Sent from my MB860 using XDA App
I have a feeling there is a bad batch of units out there.
Try factory reset and see if it continues to lock up, if it does, return it for another.
kga943 said:
Two times trying to answer a call the screen would not unlock nothing would work I had to take the battery out and just todayit was sitting on my desk and it would not turn on when I tried to use it
The green message light was on very dim and I had to take the battery out
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Sounds like a broken phone. Try a factory reset (if you return it they anyway ask if you did that) and if that won't help get a new one....
kga943 said:
Two times trying to answer a call the screen would not unlock nothing would work I had to take the battery out and just todayit was sitting on my desk and it would not turn on when I tried to use it
The green message light was on very dim and I had to take the battery out
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Same thing happened to me yesterday, the light was very dim green and the phone did not respond until I pulled the battery. It hasn't happened again.
I've already had to replace my Atrix for another issue. Right now my confidence in this phone is not very high, but it is brand new. Lots of issues will probably pop up and be fixed via software updates- at least I hope thats the case.
It really feels like all the issues people are having with this phone are software related. Maybe motorolla will just cave and give us gingerbread with no blur
I've had the same problem while playing music...over the past 3 days after about 30 minutes of tunes it'll lock up and after another 5 reset itself...i've done the reset after the second and it still does it...i'm bout to take it back and exchange it...i expect glitches but damn.
Motorola Atrix (stock)
AT&T Fuze (Energy.RAPHAEL.21916.Sense2.5.Cookie.2.0.sencity)
I have had the issue happen 2 me twice in 3 days, the last time was when adding the note widget to screen. It was not completely locked up just the touch screen, i could press the power off button but the touch screen would not let me shutdown
something you might want to try if a factory reset doesn't work would be a reinstall from the recovery menu.
power your phone off
hold the down volume key and the power button
release the power button once the phone begins to boot
keep holding the down volume button until you see "fastboot" at the top of the screen
now be careful, the down volume button navigates through the boot options and the up volume selects one
so press the down volume button until you come across "android recovery"
once you see it press the up volume button to select it
once you get to the screen with the exclamation mark tap the bottom right of the touchscreen, this should pop up the recovery menu
select wipe data/factory reset
let the phone do it's thing
good luck
I've seen this resolve some audio codec issues that were causing the phone's mic to not work, dunno if it'll work for your issue but it can't hurt to try.
best of luck
bl4ck0ut
I have found a fix for my lockup issue. If the screen is on and lockup (no touch screen) press the power button 2, turns off the display and turns it back on and everything continues to work fine.
mrlinux11 said:
I have found a fix for my lockup issue. If the screen is on and lockup (no touch screen) press the power button 2, turns off the display and turns it back on and everything continues to work fine.
Click to expand...
Click to collapse
I have the same problem (screen randomly locks up once or twice a day, buttons dead) and have found the above "solution" to work perfectly, also. The problem however is that pressing the power button twice and unlocking the phone is not exactly elegant especially if the screen locks while you are trying to answer an incoming call.
I changed my battery settings to "performance mode" as I read somewhere that that might help. I will let you know if that seems to resolve the issue.
Changing battery setting doesn't seem to do anything. I still get my share of frozen/locked up screens a few times a day. Still have not figured out how to replicate the behavior. It really does seem random.
I've been suffering from this as well, I'm going to try to exchange my phone and see if that helps.
Exchanged my phone today. So far I haven't seen any locked/frozen screen issues. I am relieved. Maybe there are just a few bad units out there.
Also for what it is worth ... the lady at AT&T told me that taking out the battery while the phone is on would fix it. Since I never figured out how to replicate the behavior I couldn't verify that her suggestion would indeed actually fix the problem and demanded an exchange anyways.
atrix does lock up and have glitches
lock up glitch:
While in standby (screen black), it locks up. You obviously don't know when exactly it happens as it's lying around in standby. When you press the powerbutton to wake it up, nothing happens. You can try what you want, long press, several presses, just dead phone. As if the battery losts juice, but 2 times it happened and the battery was above 50%.
Tired to connect the charger while in that lock-up state. Nothing happens The notification light remains black as well.
The 2nd time this happened to me, I had the idea to call myself and see if just the powerbutton has a glitch and the phone is actually running just remaining in standby with a black screen. But nope, the phone didn't ring or wake up.
Only way to recover is to take the battery out.
I didn't mess with my phone and was very careful in which apps I installed. The only ones I have are very populoar 4+star apps:
extended controls
easy profiles
the other apps are most of the time not even running:
photoaf, vignette, imdb, nytimes, fb, skype, pandora, screen filter, droid light, prozoom5x camera
No games at all installed...
The 2nd glitch that happened to me a couple of times is that the finger print sensor is not working: It doesn't display any message as in " did not verify, too short, ..." it's just dead, the only way to get in is to punch in the number code.
This is typically fixed after switching the phone off fully.
Of course skype also doesn't work on my atrix (well known mic issue)
It happened to me as well. I had installed some apps but when it froze it had been off (the screen that is) so it was sitting then when I tried to open it by pressing the power button the green light came on but it would not wake. I removed the battery, replaced it then it did the same thing again (including the green light). I removed and installed the battery once more then it was fine. It must have been something in the backround but not sure as to what that was. Hasnt happened again though.
pedroosan said:
lock up glitch:
While in standby (screen black), it locks up. You obviously don't know when exactly it happens as it's lying around in standby. When you press the powerbutton to wake it up, nothing happens. You can try what you want, long press, several presses, just dead phone. As if the battery losts juice, but 2 times it happened and the battery was above 50%.
Tired to connect the charger while in that lock-up state. Nothing happens The notification light remains black as well.
The 2nd time this happened to me, I had the idea to call myself and see if just the powerbutton has a glitch and the phone is actually running just remaining in standby with a black screen. But nope, the phone didn't ring or wake up.
Only way to recover is to take the battery out.
I didn't mess with my phone and was very careful in which apps I installed. The only ones I have are very populoar 4+star apps:
extended controls
easy profiles
the other apps are most of the time not even running:
photoaf, vignette, imdb, nytimes, fb, skype, pandora, screen filter, droid light, prozoom5x camera
No games at all installed...
The 2nd glitch that happened to me a couple of times is that the finger print sensor is not working: It doesn't display any message as in " did not verify, too short, ..." it's just dead, the only way to get in is to punch in the number code.
This is typically fixed after switching the phone off fully.
Of course skype also doesn't work on my atrix (well known mic issue)
Click to expand...
Click to collapse
strange, skype worked for me... oh well.
did you ever find a solution for the lockup issue, have the same thing, very frustrating but not as frequent as you thankfully.
My Atrix started to freeze up when I undervolted the CPU using SetCPU and I would have to pull the battery out and restart it. I increased the voltage settings and it hasn't locked up since, so if you have undervolted your CPU and your phone is locking up, you should increase the voltages.
As mentioned above, im having problems with my DHD. It mostly vibrates when im pushing it into my pocket. But no always. Also sometimes when it's already few minutes in my pocket.
When i check it i can only see blank screen, so it's really strange what causes phone to vibrate.
Any ideas?
Sent from my Desire HD using XDA App
Mine does this too, does it more if I catch the volume buttons as I put it in my pocket. All with the screen off. I can sometimes get it to do it if I mess with the volume buttons then go to unlock the screen. The phone freezes for a second, then vibrates and unlocks. Occasionally it has rebooted after doing this. No idea why.
No idea but mine started to do it last night too, I shut it down, removed and replaced the battery then restarted it and its been fine since.
Sent from my Desire HD
Disscussion is on in another thread also...
If it vibrates that means the volume up and down button has been pressed, so bug report is getting created. It will be stored in the bugreport folder in the sdcard. Once the report is done it will viberate once again...It might look a rendom viberate...
If it restarts that means power button and voulme up and down has been pressed...(It happens sometime while taking out or putting the phone into pocket).....
Hope this help....
Thanks for realy fast replys. I checked error folder and it is really full of errors.
So in time my phone case will stretch and problems will be gone.
BTW, could you please provide link to related topic?
Sent from my Desire HD using XDA App
some disscussion is here....
http://forum.xda-developers.com/showthread.php?t=863885
Also for the reboot some disscussion has been done on nightly thread of CM7.
Hi All
This problem happens to be quite frequently when using my xperia play. The problem consists of the phone itself basically freezing with the screen going blank and the buttons go unresponsive.
This problem usually occurs if I have to force close a program or there is a long download in the background. When I key lock the phone after a force close or the phone key locks itself during a long download this issue occurs.
Just to let you guys know, the phone itself is actually still on but the screen is blank and off. It still gives msg alert tones, it still rings when someone calls and it even clicks when the phone is unlocked but I cannot attend to these things as the phone is unresponsive.
My only solution at this point in time is removing the battery and putting it back in to reboot the phone. I have also tried to repair the phone using PC companion and also re-flashing the ROM with no resolution.
If anyone is having any similar experiences or if anyone knows of any fixes please let me and others know.
Thanks Guys and Girls
Are you running a custom kernel at lowest clock speed? (122mhz afaik) and/or are you undervolting it? Do you have a profile in setcpu for screen off, with lower clockspeed or/and undervolting?
If yes that might be the problem and then try to run it at 256 mhz normal voltage and see how that goes.
Regards Dousan...
I've had similar problems ever since I got this phone, happens randomly, just slows down and screen takes a while to go back on. I've never had to pull the battery cause of it, is like the phone is doing a lot of stuff or a lot of apps are running so it slows down and won't perform done tasks like turning on the screen
Sent from my R800i using XDA App
Me too
came across the same problem on all roms. try changing cpu governer. read at rootzwiki that smartass can cause those issues.
Not sure how to describe this other than sometimes the phone just doesn't turn on.
It's very odd, and I can't always recreate it, but sometimes I can.
Occasionally, if I get a notification and the screen comes on then after 10 seconds it will time out and turn off automatically (this is normal). At this point, if I press the power button to turn the screen back on within 5 minutes of it turning off then it doesn't come back on. The back and menu buttons light up, and the volume works, I can even answer a call with the home key and the phone works. The screen just doesn't come on.
If I press the button 4 or 5 times in a row, it eventually wakes up. Sometimes, I have to hold the power button to cause the power menu to come up, that will sometimes wake up the screen. This makes me think there is some system process hanging causing the screen not to display until it unfreezes, but I can't tell what that is.
This happens to me at least once a day and I can't figure it out.
I'm on android 4.4.2 with SHOstock-i v5.0 with MDL baseband.
I did some research, there are threads where other people were talking about almost the exact same issue, but a different rom and a different phone. Does this mean it's a hardware failure issue or some specific setting/app causing it? This is driving me crazy.
What I have tried:
Reflashing the ROM
Flashing ROM with full wipe
Throttling CPU (since disabled)
Alternative Kernel (although no one else is complaining of this issue)
Uninstalling random apps to see if it goes away (hard for me to run without any apps)
Have you tried the new 6.1? I'm running it and it is very smooth. I had similar issues on the att version of Shostock. I can't say whether the full wipe or the new rom fixed my issue, but it is running smoothly now.
You could also try running Greenify.
Sent from my SAMSUNG-SGH-I337 using Tapatalk
XGhozt said:
Not sure how to describe this other than sometimes the phone just doesn't turn on.
It's very odd, and I can't always recreate it, but sometimes I can.
Occasionally, if I get a notification and the screen comes on then after 10 seconds it will time out and turn off automatically (this is normal). At this point, if I press the power button to turn the screen back on within 5 minutes of it turning off then it doesn't come back on. The back and menu buttons light up, and the volume works, I can even answer a call with the home key and the phone works. The screen just doesn't come on.
If I press the button 4 or 5 times in a row, it eventually wakes up. Sometimes, I have to hold the power button to cause the power menu to come up, that will sometimes wake up the screen. This makes me think there is some system process hanging causing the screen not to display until it unfreezes, but I can't tell what that is.
This happens to me at least once a day and I can't figure it out.
I'm on android 4.4.2 with SHOstock-i v5.0 with MDL baseband.
I did some research, there are threads where other people were talking about almost the exact same issue, but a different rom and a different phone. Does this mean it's a hardware failure issue or some specific setting/app causing it? This is driving me crazy.
What I have tried:
Reflashing the ROM
Flashing ROM with full wipe
Throttling CPU (since disabled)
Alternative Kernel (although no one else is complaining of this issue)
Uninstalling random apps to see if it goes away (hard for me to run without any apps)
Click to expand...
Click to collapse
Not familiar with your rom but I know any rom I have tried where idle speed is set to 182 I find the occasional freeze then pushing too many buttons causes a reboot. The rom I am using now has the min set to 384 MHz and that seems to work very well, not one wake up issue or reboot. Depends if your kernel has a tweaker tool or not. Currently using googy-max kernel which comes with a tweaker.... you would need to research if it is compatible with your rom though..... this kernel set on battery profile gives me currently 1 day 20 hrs.... screen on time 2 hrs... battery left... 44% pretty good I'd say....
Gage_Hero said:
Not familiar with your rom but I know any rom I have tried where idle speed is set to 182 I find the occasional freeze then pushing too many buttons causes a reboot. The rom I am using now has the min set to 384 MHz and that seems to work very well, not one wake up issue or reboot. Depends if your kernel has a tweaker tool or not. Currently using googy-max kernel which comes with a tweaker.... you would need to research if it is compatible with your rom though..... this kernel set on battery profile gives me currently 1 day 20 hrs.... screen on time 2 hrs... battery left... 44% pretty good I'd say....
Click to expand...
Click to collapse
I don't think I can change the clock speed with my kernel. I will try that but I'm not sure that's the issue since the phone appears to be functioning even when the screen is stuck off. You might be on the something, if I press too many buttons that's usually how I can cause it to reboot/crash.
Try using cpu spy to see what the minimum clock setting is. Shostock 6.1 appears to be 384
Sent from my SAMSUNG-SGH-I337 using Tapatalk
Red_81 said:
Try using cpu spy to see what the minimum clock setting is. Shostock 6.1 appears to be 384
Sent from my SAMSUNG-SGH-I337 using Tapatalk
Click to expand...
Click to collapse
Yes, I am on v5.0 and it's set to 384. The issue might not be the clock speed.
This ROM doesn't have support for manually changing the clockspeed anyway.
Any other ideas?
I noticed we both had 32gb. Maybe the tolerances on the chip are not quite as good as the 16gb. I did play with cpu settings because waze would cause my phone to really heat up.
Sent from my SAMSUNG-SGH-I337 using Tapatalk
I have since changed to a different kernel and I have not had the issue yet (~13 hours running).
I can only assume this is a bug with the kernel until I have the issue again. My attempts to recreate it on the new kernel have failed.
XGhozt said:
Not sure how to describe this other than sometimes the phone just doesn't turn on.
It's very odd, and I can't always recreate it, but sometimes I can.
Occasionally, if I get a notification and the screen comes on then after 10 seconds it will time out and turn off automatically (this is normal). At this point, if I press the power button to turn the screen back on within 5 minutes of it turning off then it doesn't come back on. The back and menu buttons light up, and the volume works, I can even answer a call with the home key and the phone works. The screen just doesn't come on.
If I press the button 4 or 5 times in a row, it eventually wakes up. Sometimes, I have to hold the power button to cause the power menu to come up, that will sometimes wake up the screen. This makes me think there is some system process hanging causing the screen not to display until it unfreezes, but I can't tell what that is.
This happens to me at least once a day and I can't figure it out.
I'm on android 4.4.2 with SHOstock-i v5.0 with MDL baseband.
I did some research, there are threads where other people were talking about almost the exact same issue, but a different rom and a different phone. Does this mean it's a hardware failure issue or some specific setting/app causing it? This is driving me crazy.
What I have tried:
Reflashing the ROM
Flashing ROM with full wipe
Throttling CPU (since disabled)
Alternative Kernel (although no one else is complaining of this issue)
Uninstalling random apps to see if it goes away (hard for me to run without any apps)
Click to expand...
Click to collapse
I haven't experienced this with my GS4. But with my GS2 I had this problem and it seemed to happen with custom Kernels and with the min set to 182. I seen someone else mention this too .. The fact I haven't seen this yet is probably because I cant underclock being my bootloader is locked and I cant flash a custom kernel..Have you tried a different scheduler . It seemed to be worse on my gs2 when I had it set to NOOP. Hope you get this figured out because I know how frustrating it is to have as a problem..My Gs2 almost turned into a 70 mph fastball into a brick wall numerous times EDIT .. My fault I didn't see your post about it being set to 384 already
spirodave said:
I haven't experienced this with my GS4. But with my GS2 I had this problem and it seemed to happen with custom Kernels and with the min set to 182. I seen someone else mention this too .. The fact I haven't seen this yet is probably because I cant underclock being my bootloader is locked and I cant flash a custom kernel..Have you tried a different scheduler . It seemed to be worse on my gs2 when I had it set to NOOP. Hope you get this figured out because I know how frustrating it is to have as a problem..My Gs2 almost turned into a 70 mph fastball into a brick wall numerous times EDIT .. My fault I didn't see your post about it being set to 384 already
Click to expand...
Click to collapse
This might be related, but I'm not sure. The new kernel I'm on is actually set to 189Mhz - 1998Mhz and I have yet to have the issue happen again.
XGhozt said:
This might be related, but I'm not sure. The new kernel I'm on is actually set to 189Mhz - 1998Mhz and I have yet to have the issue happen again.
Click to expand...
Click to collapse
Right on .. Sounds like a kernel issue to me also ..I ran into the problem more often when I was playing music with the screen off .. Mind you that was on my tmobile gs2..It seemed to me that when any button was pressed to turn the screen on It was like it wasn't scaling through freqs enough to power on.. Hopefully your issue is resolved ... Now I know if I run into this issue in the future ill know its kernel related
I just wanted to follow up here. I noticed the issue happen again but this time it was right after I made a change. I'm using GO TaskManager EX and there is a setting in here to "Clear when turn on screen" and "Clear when turn off screen". When either of these are enabled then it causes the device to take an extra 15 seconds to wake and/or it doesn't wake at all.
Still not 100% sure if this was the original issue, but I thought I would post it in case anyone else is using this as well. Especially since it caused a similar behavior.
Major face-palm moment.