Database Develop

screen freezes when i wake my phone

Ever since i manually updated to frf91 sometimes when i try to wake my phone my screen freezes an i can't unlock it also when i try to power my phone back on it will vibrate 7 times an it wont come on. I guts take the battery out an put it back it to get my phone to turn back on. I've never had this problem until i manually updated my phone. I did a factory reset an it helped for a while but the problems come back. Has anyone had this problem an does anyone know how i can fix this? I'd really appreciate any help i can get

Help please

Is the bootloader unlocked?

this seems to be a common issue with FRF91, although most people's phones will unfreeze after a minute or two, does your backlight turn on and off when you press the power button?

Jep4444 said:
this seems to be a common issue with FRF91, although most people's phones will unfreeze after a minute or two, does your backlight turn on and off when you press the power button?
Click to expand...
Click to collapse
whether it unfreezes after a minute or two depends on what it's doing..there have been many times where i have to pull battery...........

rensky said:
whether it unfreezes after a minute or two depends on what it's doing..there have been many times where i have to pull battery...........
Click to expand...
Click to collapse
ya i have had to as well but most of the time it wakes just fine

No my bootloader is not unlocked an yea the backlight will come on but it won't unlock. Ive never tried waitin a min to see if it fixes itself i just usually pull the battery when it happens an sometimes when i try to turn my phone back on it does the 7 vibrating thing. Like i said before it never happened until frf91

I have an app called AutoKiller installed. It tweaks the Android system's inner memory management routines. it was set to something other than default. I changed it back to default, and haven't had a problem since. if you have this installed, maybe try and switch it to default settings.

Sounds like a data issue. A factory reset only wipes user data, You must wipe in recovery to wipe rom data. Also make sure you have the correct radio for the build especially coming from lower build. If that's the issue flash radio first to support the build. Then flash the rom.
Sent from my Nexus One using XDA App

How do u wipe in recovery? Yea im a newb lol

Also if i wipe in recovery will i still be on 2.2 or will i have to update to it again?

hard reboot

since there is no battery to pull out and i switch roms a lot and do a lot of experimental modding stuff what if the phone suddenly freeze up is there a way to force it to reboot?

qzan7 said:
since there is no battery to pull out and i switch roms a lot and do a lot of experimental modding stuff what if the phone suddenly freeze up is there a way to force it to reboot?
Click to expand...
Click to collapse
just hold power until it reboots. takes a while sometimes but it will reboot

thanks it hasn't frozen up on me yet though

qzan7 said:
thanks it hasn't frozen up on me yet though
Click to expand...
Click to collapse
it will but its more of a pain in the a** than a serious issue just make sure you have plenty of battery. it seems it freezes more when my phone is plugged in so flash with your phone off charger

If it still doesn't want to turn off you can PWR+Vol for 15+ seconds. ("They" say that's like a battery pull.)

thanks guys, it did freeze on me in aroma launcher while i tried to install a new kernel. holding power button worked just fine to restart it.

[Q] New sort of N7000 brick

At least I think this is. I have recently moved from stock to Asylum's CM10.1 but did flash a known safe kernel before any wifing occurred so I do not think this is the standard EMMC bricking.
The onset of this was gradual - phone reboobed itself a couple of times (that I noticed) but this was no huge deal for me, then a few days later the screen digitizer stopped working and I had to take the battery out - from there it degenerated fairly rapidly with more reboobs, more often returning with the digitizer not functioning and finally it is at the point where it will not boot - stuck at the loading logo.
I can reboot into recovery (CWM 6.0.3.2) but can't do a lot there - fleshing a new ROM errors out saying the package is invalid or crashes (often with a brief flickering of the screen in either case).
I can run through hg42s partition scanner - if it completes it does so without report a problem otherwise it crashes, it's about 50/50 which although it seems more reliable if mains power is connected.
If I leave the phone in CWM it will eventually reboob itself after a few minutes.
I haven't seen any magic smoke escape.
I never experienced the EMMC brick so I don't know if it was progressive as this seems to be but I get the impression it was not - and I can't rule out the same sort of problem even if the original cause is different but at the moment I am unsure about the best way to progess - I will at some point pop over to Samsung's store but ideally I'd want to get to the bottom of this with the help of the community.
So any ideas? Does this sound like a corrupt partition somewhere? Thermal sensors triggering shutdowns when they shouldn't?

interesting, try to catch the evnts in the logs, use elixer/logcat/android tuner for that.

Check the battery dude.
I had similar problesm due to bad battery.
Phone was closing itslef. And before it closesi thescreen was turning crazy
Then no boot at all....

ardicli2000 said:
Check the battery dude.
I had similar problesm due to bad battery.
Click to expand...
Click to collapse
Thanks. Did your problems occur even if the phone was on mains power? Does the battery have enough 'smart' features to affect the phone even if it is not required for powering the device?

JolyonS said:
Thanks. Did your problems occur even if the phone was on mains power? Does the battery have enough 'smart' features to affect the phone even if it is not required for powering the device?
Click to expand...
Click to collapse
I was outside when faced such a big problem. It was happening before like reboobs and stucks on logo. But after i took out the battery for 15 min I was able to boot the phone.
However, eventually, one day phone got stuck with a flickering screen and then it never booted. Tired nandroid restore. Did not help. Changed kernels etc. It was no good either. Then I changed battery. Did not work again Then made a factory reset. It worked. Using it without any problem now. But even at that time I was able to see my files in the phone via Qadb. This could be your case as well.
Try changing battery if it is older than 9 months. Make a full pit fresh Stock install.
Then Reboot. I hope t will work

JolyonS said:
At least I think this is. I have recently moved from stock to Asylum's CM10.1 but did flash a known safe kernel before any wifing occurred so I do not think this is the standard EMMC bricking.
The onset of this was gradual - phone reboobed itself a couple of times (that I noticed) but this was no huge deal for me, then a few days later the screen digitizer stopped working and I had to take the battery out - from there it degenerated fairly rapidly with more reboobs, more often returning with the digitizer not functioning and finally it is at the point where it will not boot - stuck at the loading logo.
I can reboot into recovery (CWM 6.0.3.2) but can't do a lot there - fleshing a new ROM errors out saying the package is invalid or crashes (often with a brief flickering of the screen in either case).
I can run through hg42s partition scanner - if it completes it does so without report a problem otherwise it crashes, it's about 50/50 which although it seems more reliable if mains power is connected.
If I leave the phone in CWM it will eventually reboob itself after a few minutes.
I haven't seen any magic smoke escape.
I never experienced the EMMC brick so I don't know if it was progressive as this seems to be but I get the impression it was not - and I can't rule out the same sort of problem even if the original cause is different but at the moment I am unsure about the best way to progess - I will at some point pop over to Samsung's store but ideally I'd want to get to the bottom of this with the help of the community.
So any ideas? Does this sound like a corrupt partition somewhere? Thermal sensors triggering shutdowns when they shouldn't?
Click to expand...
Click to collapse
Me too, i have some problem.

delete-

ardicli2000 said:
if it is older than 9 months.
Click to expand...
Click to collapse
Yup. This was indeed the problem - new battery in and after a few repeats of the same behaviour it kicked into life and has been fine since.
Thank heavens for replaceable batteries.

JolyonS said:
Yup. This was indeed the problem - new battery in and after a few repeats of the same behaviour it kicked into life and has been fine since.
Thank heavens for replaceable batteries.
Click to expand...
Click to collapse
Glad to hear that problem is solved

Battery at 100% after every reboot

Hi,
I am using a HTC One, rooted, running Android Revolution HD 12.1.
I have a huge problem regarding my battery. Whenever I reboot the phone, the battery display will go up to 100% and stay there until the battery dies (no matter how much battery was left before).
I have already tried refreshing the ROM, wiping everything, wiping the battery stats. No solution. The interesting aspect is that the recovery also shows 100% after a reboot.
Any ideas?

Is the battery life shorter than usual or do you seem to get normal battery life out of it? I ask because I had similar issues with my N4 and the cause was the battery itself was bad. However, my battery life was dismal and went downhill very fast. By the time I replaced the battery, I was only getting about an hour of life before the phone would die with no warning. If you still get normal battery life, you may have a different problem.

No, the battery itself seems to be fine. When I read the battery details with an app, I also see regular voltage levels.
No idea why this is happening...

Did you install any status bar mods that may have modified the status bar or battery icon?

You have to reset eh battery logic on the phone. In order to do this, hold ALL OF THE BUTTONS (power+vol up + vol down) for 2 minutes. The phone will reboot and the problem should be fixed

xeron72548 said:
You have to reset eh battery logic on the phone. In order to do this, hold ALL OF THE BUTTONS (power+vol up + vol down) for 2 minutes. The phone will reboot and the problem should be fixed
Click to expand...
Click to collapse
Hi, Thank you for the hint - this one sounds promising. However, I can't get it to work. I'm either doing it wrong or it isn't working for me.
When I hold all three buttons the phone will begin to cycle through reboots as long as I hold them (always showing the htc splash screen for a few seconds, then rebooting again). I have tried both, holding the buttons when the phone is up and running as well as powered off. Still no luck.
Any further hints?
Best regards,
Becksman

Becksman said:
Hi, Thank you for the hint - this one sounds promising. However, I can't get it to work. I'm either doing it wrong or it isn't working for me.
When I hold all three buttons the phone will begin to cycle through reboots as long as I hold them (always showing the htc splash screen for a few seconds, then rebooting again). I have tried both, holding the buttons when the phone is up and running as well as powered off. Still no luck.
Any further hints?
Best regards,
Becksman
Click to expand...
Click to collapse
This is the e-mail I got from HTC when I had the same issue as you. If this does not help, then you have to do warranty:
From: HTC ([email protected])
Sent: Sat 7/27/13 5:09 PM
\
Thank you for contacting HTC Technical Support Center!
We completely understand how important it is to have a phone that functions properly; we will do our best to provide a solution.
In regards on the issue you are experiencing with your phone not being able to work properly. I will provide the following steps for you to perform on your phone.
Recalibrate the battery/charging logic with the following steps:
•Charge the device for at least 10 minutes
•With the device truly OFF, push in and hold volume up and volume down AND power button, for 2 minutes.
•Let go. Device will fire right up, and battery/charging logic are re-calibrated.
I kindly ask you to please perform the steps provided and let me know if they helped.
Do not hesitate in replying back to this email for further assistance; I will be more than happy to assist you.
Thank you for your continuous support of our products and services. Should you require further assistance, please do not hesitate to contact us through http://www.htc.com/us/support/email/ or call us at 1-866-449-8358 from 8AM to 1AM ET, 7 days a week.
Have an amazing weekend!
Let me know if I have successfully answered your question, please click here to complete this.
To send a reply to this message, please click here.
Sincerely,
Natalia
HTC

Thank you very much!
Have you performed the steps with the charger connected or without?
Did your phone constantly circle through reboots while you held the buttons for 2 minutes?
And finally: Did it solve the problem?
Thanks again for your effort!

Today I reset everything and put the phone back to stock. Unfortunately, the problem still persists. I therefore contacted HTC and filed a support request.
If anyone should have any further suggestions, I'd be happy to hear about them. Otherwise I assume I'll have to send the phone in.
Gesendet von meinem HTC One mit Tapatalk 4

phone turns off by itself

Hi, this happend already to me few times so I decided to put it on here.
Sometimes when I pick up my phone and try to unlock it nothing happens, fingerprint and button all the same it looks like it completely Off. Then i have to press few times a button to actually start it and it's booting. There is huge battery loss after it boot up. See image.
I am in Stock 4.0.2 no root just few standard apps installed. Nothing fancy. This happend already few times to me. I left the phone locked and when I want to unlock its dead. Also it is behaving weirdly, when I turn it off manually I just need to press longer a button and it's turning on, but here I need to press it few times to work.
Does it happen to anyone else?

terragady said:
Hi, this happend already to me few times so I decided to put it on here.
Sometimes when I pick up my phone and try to unlock it nothing happens, fingerprint and button all the same it looks like it completely Off. Then i have to press few times a button to actually start it and it's booting. There is huge battery loss after it boot up. See image.
I am in Stock 4.0.2 no root just few standard apps installed. Nothing fancy. This happend already few times to me. I left the phone locked and when I want to unlock its dead. Also it is behaving weirdly, when I turn it off manually I just need to press longer a button and it's turning on, but here I need to press it few times to work.
Does it happen to anyone else?
Click to expand...
Click to collapse
Honestly, there's not enough information to understand exactly why it's happening. You need to get a logcat in the time before the reboot; unfortunately, logcats get erased during a reboot so it might be a little tricky getting it if the reboot is seemingly random. Someone had posted this as a possible way of getting the log:
"Retrieving the logs is tricky, since the log cache gets erased on reboot. If the phone reboots even while sitting on a charger, try running adb logcat continuously (you will need Android SDK and USB drivers installed and configured on your PC.) When the phone reboots, look at the last several pages in the command prompt window for any errors or abnormalities."
Click to expand...
Click to collapse
Otherwise, it's hard for anyone to help. I'm not much help in actually figuring out the issue, but I know if you can get the log, someone else probably can help.
For more information on logcats: Logcat Tutorial

Yeah I was trying to connect it to PC but nothing, so it is turned off. I will try next time to run command when turning on, maybe there will be something but I do not see it working before it gets erased. I was hoping that anyone else is having this problem so it might be rom related. It is completely random so you can;t guess when it happens.
I had it only few times so it's not super annoying but still it is not normal behavior. In addition it is weird that battery went from 55% to 33%, just phone reboot will not drain that much... I hope there is nothing wrong with the phone itself.

terragady said:
Yeah I was trying to connect it to PC but nothing, so it is turned off. I will try next time to run command when turning on, maybe there will be something but I do not see it working before it gets erased. I was hoping that anyone else is having this problem so it might be rom related. It is completely random so you can;t guess when it happens.
I had it only few times so it's not super annoying but still it is not normal behavior. In addition it is weird that battery went from 55% to 33%, just phone reboot will not drain that much... I hope there is nothing wrong with the phone itself.
Click to expand...
Click to collapse
Check in advanced to see if schedule off is on

Nope it's off

Happened to me to on 4.0.2. Rebooted twice a day.
Solution to me was Qualcomm flash back to stock 3.5.1 and uodate from internal to 3.5.4. OTA 4.0.2.
The theard "how to unbrick".
Not one reboot until now in days.

I think I found a culprit responsible for it. It is Hill Climb 2 game which doesn't close properly sometimes and I think it causes some kind of crash in the system. Is it possible?

terragady said:
I think I found a culprit responsible for it. It is Hill Climb 2 game which doesn't close properly sometimes and I think it causes some kind of crash in the system. Is it possible?
Click to expand...
Click to collapse
It's possible. Not necessarily the reason, but it might be. Either uninstall the app or freeze it using Titanium. Greenify might also work, but that allows the app to start itself up and potentially continue the issue. See if that stops the crashes for a couple of days.

The problem is that it doesn't happen often and only when I quit the game and lock the phone immediately after that. I am not sure if that's a reason though, just guessing because it happens after this last time. I will uninstall this game anyway, it's just time eater