Develop Bugs

[Q] phone freezes when idleing

I have I really annoying problem, when I use sense roms (only sense, not AOSP) my phone freezes almost instantly when going to sleep.
This results in the phone not ringing when people call me, and first receiving texts after i reboot the phone.
And the only way to reboot it, is to remove the battery.
If anyone knows what is causing this, please let me know how to fix it, this problem have made me miss many really important calls.
Thanks in advance

i had the same problem with official 2.2 sense rom (don't know with 2.3, i switched yesterday) , but only when i was on a place with bad network.. In big town like Paris no problem, but when i moved to smallest town with bad network i experienced same freeze...
When you hit a button only the button backlight turn on?

Exactly, only the button backlight comes on.
But I have fine reception at my location
Thanks for the reply

KasperHermansen said:
Exactly, only the button backlight comes on.
But I have fine reception at my location
Thanks for the reply
Click to expand...
Click to collapse
Did you use setcpu?
Usually it happen when you use setcpu and you make screen off profile 128 mhz.
Sent from my HTC Desire using XDA Premium App

Not anymore, because I had the same idea that that could be the problem, but it still freezes
Thanks for the reply

Today it has frozen 4 times.
And every time with massive battery drains, about 15% in a short period of time.

[Q] Device becomes unresponsive after several minutes of use.

Hello,
I have an HTC Desire HD running Android 2.3.3. The device isn't rooted and I've never rooted it before.
I've checked on this site, and I've scoured Google all day but I haven't managed to find anything that matches my problem specifically, as explained below.
In the last couple of days I have been having a bizarre problem where after several minutes of normal use the phone becomes completely unresponsive or very laggy (to the point where it is unusable). This occurs whether I am using apps or simply looking at the home-screen.
The only thing that's responsive is the screen lock button, this works as normal. However when I then try to unlock the screen, the phone is still unresponsive and I'm unable to unlock it.
The only fix I've found (if you can call it a fix) is to leave the phone alone for a several minutes. If I do this I can once again unlock the screen as normal and continue using the phone, however after a few minutes of use it locks up again! This has been happening since last night now and I've found no way to break this cycle.
I did a hard reset to see if this solved the problem but it had no effect. The phone will boot as normal, and after a few minutes of normal use it will become unresponsive again.
I've also booted my phone without the SD card in just in case anything on this was causing the problem, still no improvement.
Has anyone else experienced a similar issue who could provide some insight as to what might be causing this issue? Any help you can provide would be greatly appreciated.
At first I thought this might have been a software issue, but as it persisted after the reset I'm beginning to think this might not be the case.
Thanks,
KaRsKiN

The problem is coming from the magnetometer. I have the same issue, please check this thread: http://forum.xda-developers.com/showthread.php?t=1394264
The only workaround I found is to disable screen rotation and do a couple of restarts (not switch off). Of course, no compass in the end, but at least I can use the phone.

KaRsKiN said:
Hello,
I have an HTC Desire HD running Android 2.3.3. The device isn't rooted and I've never rooted it before.
I've checked on this site, and I've scoured Google all day but I haven't managed to find anything that matches my problem specifically, as explained below.
In the last couple of days I have been having a bizarre problem where after several minutes of normal use the phone becomes completely unresponsive or very laggy (to the point where it is unusable). This occurs whether I am using apps or simply looking at the home-screen.
The only thing that's responsive is the screen lock button, this works as normal. However when I then try to unlock the screen, the phone is still unresponsive and I'm unable to unlock it.
The only fix I've found (if you can call it a fix) is to leave the phone alone for a several minutes. If I do this I can once again unlock the screen as normal and continue using the phone, however after a few minutes of use it locks up again! This has been happening since last night now and I've found no way to break this cycle.
I did a hard reset to see if this solved the problem but it had no effect. The phone will boot as normal, and after a few minutes of normal use it will become unresponsive again.
I've also booted my phone without the SD card in just in case anything on this was causing the problem, still no improvement.
Has anyone else experienced a similar issue who could provide some insight as to what might be causing this issue? Any help you can provide would be greatly appreciated.
At first I thought this might have been a software issue, but as it persisted after the reset I'm beginning to think this might not be the case.
Thanks,
KaRsKiN
Click to expand...
Click to collapse
It is possible that your battery could be failing. See if att has one they will let you exchange.
If its not the battery then it could be a hardware issue. Just send it in for warranty if that is the case. You should still be covered as the phone is not yet a year old.
Sent from my Inspire 4G using xda premium

Gizmoe said:
It is possible that your battery could be failing. See if att has one they will let you exchange.
Click to expand...
Click to collapse
How should this be connected to the battery...?
Anyway, I think that it is a software issue rather than a hardware one. Maybe something is running in the background, using 100% of the cpu. You could try CPUNotify for realtime cpu monitoring.
If that doesn't work, you should try the magnetometer way. Maybe it's a new issue. Never heard about it though
I do what i want, because I can.

Flussen said:
How should this be connected to the battery...?
Anyway, I think that it is a software issue rather than a hardware one. Maybe something is running in the background, using 100% of the cpu. You could try CPUNotify for realtime cpu monitoring.
If that doesn't work, you should try the magnetometer way. Maybe it's a new issue. Never heard about it though
I do what i want, because I can.
Click to expand...
Click to collapse
I'm not going to explain in detail about the relationship of voltages and CPU usage. The battery being bad can and has caused these exact issues. Just like if a power supply is failing it can cause a blue screen in windows. In android the phone rebooting itself or freezing is the equivalent to a blue screen. Since they have never rooted and are on a stock rom there is nothing except a hardware problem that would cause this. If the battery is not the culprit then one of the many components in the phone can cause freezes and reboots if it is failing. Android os does not allow a single task to take over the CPU. This is not a windows os. So like I said, just use your warranty and get it fixed. Stock phones should not be presenting this behavior, you would have to root it to cause these kind of problems.
Sent from my Inspire 4G using xda premium

Gizmoe said:
I'm not going to explain in detail about the relationship of voltages and CPU usage. The battery being bad can and has caused these exact issues. Just like if a power supply is failing it can cause a blue screen in windows. In android the phone rebooting itself or freezing is the equivalent to a blue screen. Since they have never rooted and are on a stock rom there is nothing except a hardware problem that would cause this. If the battery is not the culprit then one of the many components in the phone can cause freezes and reboots if it is failing. Android os does not allow a single task to take over the CPU. This is not a windows os. So like I said, just use your warranty and get it fixed. Stock phones should not be presenting this behavior, you would have to root it to cause these kind of problems.
Sent from my Inspire 4G using xda premium
Click to expand...
Click to collapse
Thanks for your help! My dad has the same device as me so I'll try swapping out the battery to see if this solves the problem. If not I'll try calling HTC to arrange a repair.

Any news? Was it the battery issue?

[Q] Screen does not wake up or system randomly freezes

I recently installed the new RunnyRom 6.0 ROM, so it is my current ROM. With the previous version, at random intervals, my phone would either freeze after doing some simple task such as turning on the mobile network or just at random. At other times, the phone would not respond after the screen goes blank.
I am at my wits end and might end up throwing my phone at a wall. I've tried increasing the minimum CPU speed to no avail and other remedies from googling.
Must I buy a new phone? (my warranty is up btw, so I can't send it away back to HTC or the store I bought it from)

Before you say you are at your wits end, have you even tried flashing an entirely different rom to see if the issue presents itself again?
via xda app

Or a faster sd-card !

do you have ext on your sdcard and some kind of app2ext script?

Something like this?
It's a combination of sd card, sd-ext scripts running on it and bad reception. For me, the only ROM that doesn't have this problem is RSK v6.

stankyou said:
Before you say you are at your wits end, have you even tried flashing an entirely different rom to see if the issue presents itself again?
via xda app
Click to expand...
Click to collapse
I have, that's the reason I went from CM7 to Oxygen and back to Sense.
MarcelHofs said:
Or a faster sd-card !
Click to expand...
Click to collapse
I think this could be the problem, but I'll need to buy another card today to see. As for some reason my current card keeps getting errors when I connect it to my pc.
.tnm said:
do you have ext on your sdcard and some kind of app2ext script?
Click to expand...
Click to collapse
I believe RunnyRom v6 has that.
Ronok said:
Something like this?
It's a combination of sd card, sd-ext scripts running on it and bad reception. For me, the only ROM that doesn't have this problem is RSK v6.
Click to expand...
Click to collapse
I will try to switch back to CM7/Oxygen and see if the problems persist with the same frequency.

Go back to CM7 than Oxygen to test. Oxygen uses a script if an ext partition is detected. You wanna try and see if your phone will work well without any ext partition and CM7 doesn't support it out of the box.
Or if you can't help not having ext partition because of your apps, how about you format your sd card, repartition and start fresh.
via xda app

So as I did a full wipe and reinstalled CM7, lo and behold, the phone freezes on me in the 4ext recovery screen. Wiped again and tried to reinstall RunnyRom, same thing.

Seems like hardware issue if you get freezes even on recovery. You can flash a stock rom as a last verification but since you don't have warranty you might as well consider it as a reason to get a new phone.
There's the HTC One series or if you can still wait a bit longer, Galaxy S III is about to make a debut this May.

stankyou said:
Seems like hardware issue if you get freezes even on recovery. You can flash a stock rom as a last verification but since you don't have warranty you might as well consider it as a reason to get a new phone.
There's the HTC One series or if you can still wait a bit longer, Galaxy S III is about to make a debut this May.
Click to expand...
Click to collapse
I think I will need to settle for something a bit cheaper.
However, I have noticed that if my mobile network is on, most times it will freeze my phone if I use any app that uses internet such as Whatsapp, facebook or Google+. Not sure if that might be relevant. (I am on a CM7 ROM and it still freezes so it is most definitely a hardware problem I would agree with).

I had a similar problem with my HTC Desire. I was on the road a lot and noticed that when I came near certain areas, my phone froze. I think it was because of a bad radio or something like this.
Does it happen when you are in airplane mode?
I flashed the new CM9 and the problem stopped.
Alternatively, it didn't happen with the sandvold-ICS.
Have you tried flashing with a new SD-Card?

ravach0l said:
I had a similar problem with my HTC Desire. I was on the road a lot and noticed that when I came near certain areas, my phone froze. I think it was because of a bad radio or something like this.
Does it happen when you are in airplane mode?
I flashed the new CM9 and the problem stopped.
Alternatively, it didn't happen with the sandvold-ICS.
Have you tried flashing with a new SD-Card?
Click to expand...
Click to collapse
Never tried it with airplane mode on. There's less freezing with MildWild 4.4 but occasionally it will freeze.

I had this issue once with ics and drewis kernel, on tiamat no problems at all

From using Mildwild 4.4 I've realized that when my phone rings, the ringtone will not play and if I answer it as soon as the call ends the screen will not wake up. If I ignore the call and open any application, the phone will freeze. In both cases I will need to remove the battery.

Sometime fixing permissions from recovery sorts out freezing issues
Sent from my HTC Desire using xda premium

jmcclue said:
Sometime fixing permissions from recovery sorts out freezing issues
Sent from my HTC Desire using xda premium
Click to expand...
Click to collapse
Tried that too. No major change.

same exact problem, i'm running runnymede AIO, phone freezes often, especially when i'm at home where signal is not good.
i've got the feeling is mainly related to whatsapp, but it's just a feeling.
phone usually freezes when i wake it up from standby, the lockscreen ring does not respond.
it never freezes when in airplane mode.
i think i'll try a different phone part, then a different rom, it's a pity since this one performs really well for my needs.
sorry for my english, if i fix this i'll post here, cheers.

jeremypps said:
same exact problem, i'm running runnymede AIO, phone freezes often, especially when i'm at home where signal is not good.
i've got the feeling is mainly related to whatsapp, but it's just a feeling.
phone usually freezes when i wake it up from standby, the lockscreen ring does not respond.
it never freezes when in airplane mode.
i think i'll try a different phone part, then a different rom, it's a pity since this one performs really well for my needs.
sorry for my english, if i fix this i'll post here, cheers.
Click to expand...
Click to collapse
I think my problem was mainly the sd card as it deleted all of my photos and then randomly stopped reading in my phone.
I switched sd cards and ROMs and so far no freezes.

NovaStark said:
I think my problem was mainly the sd card as it deleted all of my photos and then randomly stopped reading in my phone.
I switched sd cards and ROMs and so far no freezes.
Click to expand...
Click to collapse
well, might be, but i'd find strange, mine is a brand new samsung class 6.
but i'll give it a try when i can.

Touch panel trouble

Noticed something strange for the first time , screen is laggy and not responsive while charging the phone , I think it maybe is the kernel as its the first time to notice this , It happened after flashing franco-r6 kernel and iam using insert coin 6.3.1 Rom
Is this normal ?
Sent from my HTC One X using XDA

You flashed a ROM, You're not stock therefore you need to consult the dev of that Rom about the issue.

To be fair, I had this issue on stock.. so it probably isn't a problem with the ROM

Nit3m4re said:
To be fair, I had this issue on stock.. so it probably isn't a problem with the ROM
Click to expand...
Click to collapse
Is it still present ? What did u do about it ?
Sent from my HTC One X using XDA

Nit3m4re said:
To be fair, I had this issue on stock.. so it probably isn't a problem with the ROM
Click to expand...
Click to collapse
Yep I get this issue at times as well. Especially when I've left it to charge for a while and try to perform a pattern unlock. Happens about twice a week or so. Screen returns to normal after 10 seconds or so. Weird.

+1 this happens on stock roms all the time. it's intermittent, and often can be temporarily fixed by switching the screen off then on again.

I'm about to send my phone in for repair because of this problem. I actually have a dead patch on the screen which is intermittent. If I go to Developer Options > Pointer Location, and then trace my finger around the screen, I can see the patch where it's not picking up the input. Also sometimes the phone behaves erratically and can become completely unresponsive and flicks back and forth between home screens. Turning the screen off and then on again fixes it temporarily.

[Q] Galaxy Nexus Sleep of Death

Problem: Cannot turn on the screen by pressing the power button sometimes. The screen is black or very dim, I cannot tell. One can see nothing on the screen, and it doesn’t accept any touch input, either. The phone still rings if there’s an incoming call. If this happens, the following several presses (about 10 - 20) on the power button will probably lead to a reboot. The “screen auto-rotate” and the proximity sensor may fail after the reboot, but will recover after a manual reboot.
Frequency: Fewer with higher Rom version. About once per day for 4.3.
Other description:
 The problem frequently happens when I just take the phone outside my house/office, and seldom happens when the phone just stays somewhere.
 The problem seems to be irrelevant to the remaining battery capacity or the uptime, but it never happens when charging.
 The problem seems to be irrelevant to the Apps installed.
 The problem seldom happens in the first 3-4 days after flashing a Rom, but happens more and more frequently as time goes by. My guess is some cache is stuffed by some trash, which causes the problem. The phone may be fine as long as the trash can be cleaned up on a regular basis.
 I manually reboot my phone at most every two days.
Solutions tried, but don’t work
 Flashing official ROMs 4.0.4, 4.1.1, 4.1.2, 4.2.2 and 4.3 following the procedure “adb reboot bootloader; fastboot oem unlock; flash-all; fastboot oem lock”, without google wallet, not rooted.
 Turning off the auto-brightness control, as suggested by some post on the Internet.

Does it look like it goes to standby normally or does the screen show gibberish and then turns off?
Sent from my Galaxy Nexus using XDA Free mobile app

Thymo said:
Does it look like it goes to standby normally or does the screen show gibberish and then turns off?
Sent from my Galaxy Nexus using XDA Free mobile app
Click to expand...
Click to collapse
Thank you very much.
I think it's standing-by normally even through the screen is black (or very dim, I cannot tell), since it rings if there's an incoming call. I can see nothing from the screen, and I don't think the screen accepts any touch input, either.
Does this answer your question? Thank you.

Bobby_yan said:
Thank you very much.
I think it's standing-by normally even through the screen is black (or very dim, I cannot tell), since it rings if there's an incoming call. I can see nothing from the screen, and I don't think the screen accepts any touch input, either.
Does this answer your question? Thank you.
Click to expand...
Click to collapse
Thanks.
Was just asking if you had gibberish yes or no. In that case i've got a different issue than you (Suspecting f*cked GPU).
Have you tried a different ROM/Kernel combination maybe it's related to that.

Thymo said:
Thanks.
Was just asking if you had gibberish yes or no. In that case i've got a different issue than you (Suspecting f*cked GPU).
Have you tried a different ROM/Kernel combination maybe it's related to that.
Click to expand...
Click to collapse
No.
No, I just tried the official ROMs. Any suggestion?

Perhaps it's just busy in the background and running low on RAM. Give LagFix a try. Sorry can't link atm as I am on mobile...

eKeith said:
Perhaps it's just busy in the background and running low on RAM. Give LagFix a try. Sorry can't link atm as I am on mobile...
Click to expand...
Click to collapse
Thanks a lot. I'm trying it.

Bobby_yan said:
Thanks a lot. I'm trying it.
Click to expand...
Click to collapse
LagFix does NOT help in my case. Any other suggestions? Thanks.

I've also had this blank screen with calls still ring issue for as long as I can remember, nearly 2.5 yrs.
I've always suspected it's my ROM and so I'd try out another ROM'S, BUT no other ROM works like how I'd like, so I always come back to my ROM.
It doesn't happen every single day, but it does happen very often.
I've tried using apps that auto reboot daily, but eventually this blank screen issue will return.
Unfortunately I can't seem to find any solution, so I just put up with it, it's like the 1 only flaw with my ROM.
&
Not to be at all rude, but I'm really glad op has had this issue from testing other versions of Android, cause then at least I know I don't need to give up my great tablet mode ROM.
LOL

I think I've finally found a work around for this screen of death.
Using Exposed, download/install this module/extension:
Disable Proximity
http://repo.xposed.info/module/com.mrchandler.disableprox
It does exactly what it's name is and ever since then I've not once had to remove my GN battery to work again because the screen went completely dead.

NVM
Screen still goes dead.
Anyone find an actual fix to this?

isajoo,
I had pretty much the same problems with my Galaxy Nexus running CyanogenMod 11 M12.
It got better by doing the following :
Blowing dry air in the earpiece… though the proximity sensor is clearly beside it. Can't do any harm though, I guess.
Settings/Applications/All/menu/Reset applications preferences (or whatever that's called in english) : that seemed to do a lot of good to my phone ! However, it's a very unsatisfactory answer on a technical point of view, as I still don't know WHAT was precisely needed. It's a "magic wand" solution for which I can't give an explanation.
Not specifically related, but greatly helped my phone in the responsiveness area : Trimmer (fstrim) (https://play.google.com/store/apps/details?id=com.fifthelement.trimmer), an updated version of LagFix that you may already know
Hope that helped !
(I wanted to try http://www.androidlegend.com/how-to-perform-proximity-sensor-calibration-on-any-samsung-phone/ as well, but apparently, /sys/class/sensors/proximity_sensor/prox_cal does not exist on my phone…)