Develop Bugs

[Q] Answer phone

every other time my phone rings I cant answer it. The accept button just wont move?? is it just me or have anyone else had this error I have a dezire z

Do you have set CPU set to 245MHz @ screen off?

no i dont, why?

Well that could be one cause, maybe it's a bad app causing your phone to temporarily freeze? Can you slide it the other way and ignore the call?

Did you try flashing a different kernel?
Sent from my CyanogenMod powered G2.

Utorrent76 said:
Did you try flashing a different kernel?
Sent from my CyanogenMod powered G2.
Click to expand...
Click to collapse
why do you suggest this? how do you know hes using kernels? im just trying to see what your connection to the solution is -its quite a specific answer to a problem that hasnt really been examined. what rom is he on, etc before you can start talking about kernels -- so can you clarify?
accept button - do you mean the slider? if you have cmod - just activate settings to disable lock menu/trackball/ whatever --also you could try the no-lock unless you have security issues.
if no cmod -- theres apps to reduce the lockage -- that may help you get your phone calls but still doesnt fix the problem? you could try enomther's and his awesome extra ssettings app has all those options

Thanks for your help, well it is my wifes phone and it is fresh from the store, just a bunch of apps installed.
I will try some things and see if i can figure it out. And yes it is the slide button, can that be switched for a push button, Is it theme based or in the dialer?? hope you understand what i say.

jaypeg123 said:
Thanks for your help, well it is my wifes phone and it is fresh from the store, just a bunch of apps installed.
I will try some things and see if i can figure it out. And yes it is the slide button, can that be switched for a push button, Is it theme based or in the dialer?? hope you understand what i say.
Click to expand...
Click to collapse
If its a stock DESIRE Z and not a G2 then I think it's safe to assume its got sense on it and not AOSP. Did you try hard resetting it? (power down and pulling the battery for at least 30 sec) other than that id check for any OTA updates in the settings menu. OR if you're willing/know how, you can root it and run CM or virtuous. Both ROMs are excellent. If you do that and the problem persists, it could very well be a faulty unit. You have a lot of options!

I found I had problems answering calls when I had a specific make of screen protector on the phone. As soon as I took that off and went back to a previous one I'd used then it was fine again ! It's a long shot, but I thought I'd throw it in there.

Problem solved, An update did the trick, thanks for helping out my friends,

same problem , cannot answer with swipe keys
I have the same problem, which update did you use

same problem , cannot answer with swipe keys
I have the same problem, which update did you use

Phone randomly switches off. Needs battery pull.

Hey guys,
I'm new to the forum. I have tried running a search for this problem already and haven't found anything related.
My phone randomly switches off and requires a battery pull to be turned back on again (Yes the conventional button pressing and power button pressing etc doesn't work). I haven't had the phone switch off on me whilst using it, it usually happens when I pick up my phone to check for messages etc. and realise it's not on.
I have a Desire Z running Virtuous 1.0.2 with the Advanced kernel.
The SetCPU screen off profile is 245/691 on 'interactive'.
Anybody have any ideas as to what may be the cause?

Same thing happens to me sometimes but it usually happens when I'm charging maybe its the battery. Have you noticed any unusual drain on your battery?
Ps. I know very little about phones and what not but I know that your battery could be over charged therefore your phone does what it does. Just a bit of guess.
Sent from my HTC Vision using XDA App

This has been called "SOD" (screen of death) by some. Probably not related to CPU clocking/stepping, like the more common "screen wake issue" on Virtuous, as the symptoms are pretty different in my experience. As you already mentioned, with the CPU clocking/stepping "screen wake" issue (common on Virtuous if you use the advanced kernel), you can power on the screen with multiple pushes of the power button, or opening the keyboard. With SOD, no amount of button pushing does anything, and the phone is completely unresponsive.
Several theories abound as to the cause of SODs, but nothing conclusive, unfortunately. Likely a hardware problem, possibly combined with kernel and/or GPS.
Personally, I've found that going back to my stock shipped ROM and using the Godspeed kernel is the only combination I've tried so far (including Virtuous and CM7) that seems totally free of SODs. But your results may vary.
Any evidence of this issue when you were on the stock ROM? If not, you might consider just reverting back (easy if you made a nandroid). If the problem persists on the stock ROM, and you are still on warranty, you might consider returning your phone to stock and sending it in for repair, as this seems the surest way to solve the issue. This isn't an option for me, since I purchased mine with no warranty (unlocked and imported). Otherwise, you might try different ROM and kernel combinations to see if things improve.
I've discussed this some more on the following similar recent thread (links to additional related threads on that post):
http://forum.xda-developers.com/showpost.php?p=13002702&postcount=7

redpoint73 said:
I've discussed this some more on the following similar recent thread (links to additional related threads on that post):
http://forum.xda-developers.com/showpost.php?p=13002702&postcount=7
Click to expand...
Click to collapse
Thanks for shedding some light on this issue for me. I'll have a try doing what you suggested and see if it's any better.

pmatang said:
Thanks for shedding some light on this issue for me. I'll have a try doing what you suggested and see if it's any better.
Click to expand...
Click to collapse
Dammit, I hit the Thanks button instead of Quote. Oh well, you get a free Thanks!
BTW, feel free to Thank my post, if you found it helpful!
At least one person I've suggested a different kernel to (to try to solve this issue), did not find it helpful. But it helped in my case. And you can do a nandroid backup to make sure the change is completely and easily reversible if you don't like the result.

[Q] Sporadic Black Screen of Death, any solution?

I have the above issue with stock 4.2. Sometimes the screen goes blank (like a dark Grey back light), the phone is still on, but I can't get into it anymore. It registers touches etc, just the screen doesn't get back.
Flashed clean stock Image, factory reset and data restore.
Only battery pull helps. Happens 1 or 2 times per day in various situations (texting, browsing, whatsapp). Luckily I don't have any of the other 4.2 problems, except the missing December in Contacts. The phone is otherwise snappy as hell with 167 apps installed, recent tasks and swiping to close apps are instant.
Did anyone find a solution yet?
Sent from my Galaxy Nexus using Tapatalk 2

nomad4ever said:
I have the above issue with stock 4.2. Sometimes the screen goes blank (like a dark Grey back light), the phone is still on, but I can't get into it anymore. It registers touches etc, just the screen doesn't get back.
Flashed clean stock Image, factory reset and data restore.
Only battery pull helps. Happens 1 or 2 times per day in various situations (texting, browsing, whatsapp). Luckily I don't have any of the other 4.2 problems, except the missing December in Contacts. The phone is otherwise snappy as hell with 167 apps installed, recent tasks and swiping to close apps are instant.
Did anyone find a solution yet?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Same thing here, never had an issue with 4.1.2 but now it happens 2-3 times a day
Sent from my Galaxy Nexus using xda premium

same me..
this is really annoying..anyone tried a clean install of 4.2 to see if its get solved? im bored to wipe..

andQlimax said:
same me..
this is really annoying..anyone tried a clean install of 4.2 to see if its get solved? im bored to wipe..
Click to expand...
Click to collapse
Let me know how that works... I have been having this problem also. Screen is blank every 2 days it happens once. Ever since 4.2 update. Before that I had no issues like this.
Also un related but I've started to notice faint horizontal lines in my screen. I use auto brightness. Is this normal or return for warranty?

i can confirm this happens to me too.
4.2 stock only rooted with custom recovery.

Same here folks, It may a bug in the 4.2 builds since Sprint did not officially release 4.2 yet.

This happens on my GSM model. It's never been rooted, and only started doing this after the 4.2 OTA.
You can shut the phone down without pulling the battery. Press the power button once to lock (or just wait until it locks on its own). Press the power button again to bring up the unlock screen, unlock and then long-press the power button. A short vibration tells you when the shutdown menu is up, and the SHUT DOWN button is across from the midpoint of the volume rocker, so you can press it without seeing it. The display works fine when it's powered back up again.
I have a theory that the problem is related to another bug in the auto-brightness in 4.2. The display always goes to maximum brightness for a split second before going black. I have set my phone to manual brightness for the last day or so and have not seen the problem again (yet).

same issue here, I'll try to keep the brightness to manual to see if it works

chanchan305 said:
same issue here, I'll try to keep the brightness to manual to see if it works
Click to expand...
Click to collapse
Manual brightness didn't work for me. Everything I have read seems to lead to something wacky in source. I finally went back to 4.1.2. It hurt to go backwards,but no more issues. I'll come back when it is fixed.
By the way, I did discover that if I was at my computer when it happened, I could reboot the phone using adb.

MondoMor said:
This happens on my GSM model. It's never been rooted, and only started doing this after the 4.2 OTA.
You can shut the phone down without pulling the battery. Press the power button once to lock (or just wait until it locks on its own). Press the power button again to bring up the unlock screen, unlock and then long-press the power button. A short vibration tells you when the shutdown menu is up, and the SHUT DOWN button is across from the midpoint of the volume rocker, so you can press it without seeing it. The display works fine when it's powered back up again.
I have a theory that the problem is related to another bug in the auto-brightness in 4.2. The display always goes to maximum brightness for a split second before going black. I have set my phone to manual brightness for the last day or so and have not seen the problem again (yet).
Click to expand...
Click to collapse
bfprd0 said:
Manual brightness didn't work for me. Everything I have read seems to lead to something wacky in source. I finally went back to 4.1.2. It hurt to go backwards,but no more issues. I'll come back when it is fixed.
By the way, I did discover that if I was at my computer when it happened, I could reboot the phone using adb.
Click to expand...
Click to collapse
I experience this issue, but not that frequent. Once every 4 or 5 days, i don't know. I've managed to pull a logcat today as i was near of pc, as posted before, adb/phone is responsive, it even locks the screen normally, there was nothing useful on dmesg. I don't normally use auto-brightness, but enabled it a little while ago, although now i'm not sure if it was enabled the first time it happened. This last time, it wasn't enabled, that I'm sure.
It happened to me both when I was using XDA-app. I have almost 0 user apps installed right now, also uninstalled XDA. Reporting back in a few.

the issue is related to location services
the "bug" has been reported to google http://code.google.com/p/android/issues/detail?id=40140
for a temporary fix turn off services/apps that track you e.g. latitude

ogdobber said:
the issue is related to location services
the "bug" has been reported to google http://code.google.com/p/android/issues/detail?id=40140
for a temporary fix turn off services/apps that track you e.g. latitude
Click to expand...
Click to collapse
huh... i also don't have location services active nor gps. i never do.
and, in our case, the phone is still on, it doesn't reboot, just the screen is black. it's not the same issue.
edit: if i manage to hit it again, my next step will be unroot. full stock.

bk201doesntexist said:
huh... i also don't have location services active nor gps. i never do.
and, in our case, the phone is still on, it doesn't reboot, just the screen is black. it's not the same issue.
edit: if i manage to hit it again, my next step will be unroot. full stock.
Click to expand...
Click to collapse
ok...star this issue https://code.google.com/p/android/issues/detail?id=40019

Severe Wake-Up Lag

I've heard of the usual 2 or 3 second lag for most users. They'll try to wake up their phone with the power button, but there's about a two or three second delay. I wouldn't care at all if I had that!
My problem is far more sinister. I don't have the usual wake lag. It's dynamic and unpredictable.
Let me explain. When I first boot up my phone (or restart it) it works flawlessly. No lag—nothing. Not even the three second wake lag most people get. Then, out of nowhere (I can't pinpoint when it starts) I'll try to wake it up and... nothing! The backlight will turn on (that very dim black light) along with the soft keys. They'll turn on fine, but my display will not show up. Funny thing though, sometimes I'll tap the screen and it'll vibrate as if it was on. The only way to fix this is one of two ways: restart the phone (very annoying) or turn it on and wait. Sometimes, eventually the display will kick in but I have about a second to react before it shuts off. Then, I have to press the power button twice more to turn off the backlight and turn it back on and wait for the display to kick in. If I tap and swipe to unlock, I'm mostly in the clear. But, most of the time it takes SwiftKey about 30 seconds to respond. I'll tap and tap and nothing will be written, but after 30 seconds of spamming it'll finally start to write. Then, my phone has minor/no lag while the display is still on. But, if I let it shut off, then it starts all over again. Backlight, but no display.
Sometimes I'll be lucky: I had a three day streak of no lag at all, but then it happened. It really is random, and I have no idea what could be causing this. It wasn't always this way either.
I have this rooted and am running CarbonRom (Android 4.4)
ANY help would be appreciated. Nothing seems to fix this permanently.

Try another rom, or better yet... Try stock 4.1.2 for comparison. Install the same things on it and see. It could be certain apps slowing your phone down, or lack of ram, or your setup.
Mine is on stock 4.1.2...and I'm sometimes amazed when I do pick it up and use it, like when I'm charging my other phone, at how zippy it is. It's not way slower feeling like you'd think it would be, at all.
---------- Post added at 11:13 AM ---------- Previous post was at 11:12 AM ----------
Also a cache and dalvik wipe can often help. Especially on older devices.

This is a common issue with KK ROMs & kernels. Try a JB ROM instead.

KJ said:
Try another rom, or better yet... Try stock 4.1.2 for comparison. Install the same things on it and see. It could be certain apps slowing your phone down, or lack of ram, or your setup.
Mine is on stock 4.1.2...and I'm sometimes amazed when I do pick it up and use it, like when I'm charging my other phone, at how zippy it is. It's not way slower feeling like you'd think it would be, at all.
---------- Post added at 11:13 AM ---------- Previous post was at 11:12 AM ----------
Also a cache and dalvik wipe can often help. Especially on older devices.
Click to expand...
Click to collapse
Agreed, a dalvik cache and a cache wipe will often help. What would be the best way to update to stock 4.1.2 from stock 4.0.3? It is not showing up in ota and I can't use kies or Odin as I don't have a Windows computer. Heimdall can only seem to successfully install ICS on this phone.
Sent from my SGH-T989

You could just flash a stock 4.1.2 rom... Tho its usually best to Odin stock first , then flash things 4.1.2 and higher.
Yeah, without a pc ... Not sure what you can do. Maybe you could visit someone that has Windows pc ?
You can try just flashing a stock rom, buy good chance you'd freeze at boot up.

KJ said:
You could just flash a stock 4.1.2 rom... Tho its usually best to Odin stock first , then flash things 4.1.2 and higher.
Yeah, without a pc ... Not sure what you can do. Maybe you could visit someone that has Windows pc ?
You can try just flashing a stock rom, buy good chance you'd freeze at boot up.
Click to expand...
Click to collapse
Don't know. All I know is when I try flashing 4.1.2 in Heimdall it freezes after Android is upgrading and then boot loops. I've tried wiping data, cache, and falcon after flashing and it still didn't work. I'll probably just stock with AOSPA since it is fairly stable right now and has decent battery life.
Sent from my SGH-T989

I'm running CarbonROM + WildKernel. Currently, I have no problems with wakeup lag when tapping the power button. Though, when I recieve a call, it takes several seconds for the screen to wake. I have my kernel configured for 96Mhz when screen is off. You might try increasing the base cpu frequency and see if that helps. You might also try changing your cpu governor and see if that helps.
However, your tapping the power button twice description might be indicative of something wrong with your power button. Just a thought. These particular phones are known to have issues with the power button after time.

ayr0 said:
I'm running CarbonROM + WildKernel. Currently, I have no problems with wakeup lag when tapping the power button. Though, when I recieve a call, it takes several seconds for the screen to wake. I have my kernel configured for 96Mhz when screen is off. You might try increasing the base cpu frequency and see if that helps. You might also try changing your cpu governor and see if that helps.
However, your tapping the power button twice description might be indicative of something wrong with your power button. Just a thought. These particular phones are known to have issues with the power button after time.
Click to expand...
Click to collapse
96mhz will definitely cause some things to lag on wake. Test it tho and then compare to 300. I very much doubt you'll see any difference in battery life at all.

Thanks for all the replies, and I just may have to try a ROM that's a bit older. This phone is basically ancient history now, but it suits me well. I'll try the stock JB ROM but probably won't keep it—I do enjoy having the features many custom ROMs include.
I've also installed and ran LagFix free from Google Play, and I can say it greatly reduced the frequency of the wake lag occurring. It still happens but for the most part it turns on fine.
ayr0 said:
I'm running CarbonROM + WildKernel. Currently, I have no problems with wakeup lag when tapping the power button. Though, when I recieve a call, it takes several seconds for the screen to wake. I have my kernel configured for 96Mhz when screen is off. You might try increasing the base cpu frequency and see if that helps. You might also try changing your cpu governor and see if that helps.
However, your tapping the power button twice description might be indicative of something wrong with your power button. Just a thought. These particular phones are known to have issues with the power button after time.
Click to expand...
Click to collapse
Twice in meaning once to turn off the backlight to put it to sleep and then once more to attempt to "wake" it up again.

KJ said:
96mhz will definitely cause some things to lag on wake. Test it tho and then compare to 300. I very much doubt you'll see any difference in battery life at all.
Click to expand...
Click to collapse
You are right, I just looked at the voltage tables in my ROM and everthing below 153Mhz uses the same amount of power.
I'm going to try 153Mhz for awhile and see if that helps. Thanks for bringing that to my attention.
---------- Post added at 04:58 PM ---------- Previous post was at 04:53 PM ----------
Saturable said:
Thanks for all the replies, and I just may have to try a ROM that's a bit older. This phone is basically ancient history now, but it suits me well. I'll try the stock JB ROM but probably won't keep it—I do enjoy having the features many custom ROMs include.
I've also installed and ran LagFix free from Google Play, and I can say it greatly reduced the frequency of the wake lag occurring. It still happens but for the most part it turns on fine.
Twice in meaning once to turn off the backlight to put it to sleep and then once more to attempt to "wake" it up again.
Click to expand...
Click to collapse
How much time do you wait between button pushes. On my rom, it they are I press the button twice in immediately consecutive pushes, it does take a second or two for the phone wake. However, if I wait a second or two before pressing the power button again, wakeup is almost instantaneous. I attribute this to the fact that even though the screen is powered off, it takes a little bit of time for the phone to actually go to sleep. The phone might be lagging because it has to wait for the phone to sleep before it can wake up again.

SOLVED:black screen when press power button

sometimes when i pick up my phone and press the power button to turn it on,i find the screen is black and i can t do anything but press power and vol + to reboot.
then the phone works fine again but of course this is quite annoying to happen and it happens maybe one or two times daily
it started happening when i upgraded to 5.1.1.
in 5.0 and 4.4 phone behaved fine.
how to find what causes screen to turn black when i try to turn it on?
does somebody faced this also?
any helpful idea?

broky said:
sometimes when i pick up my phone and press the power button to turn it on,i find the screen is black and i can t do anything but press power and vol + to reboot.
then the phone works fine again but of course this is quite annoying to happen and it happens maybe one or two times daily
it started happening when i upgraded to 5.1.1.
in 5.0 and 4.4 phone behaved fine.
how to find what causes screen to turn black when i try to turn it on?
does somebody faced this also?
any helpful idea?
Click to expand...
Click to collapse
Phone stock? Rooted? Recovery? Etc... I've never experienced it, but with modded phones, cache wipe fixes these types of things often

levone1 said:
Phone stock? Rooted? Recovery? Etc... I've never experienced it, but with modded phones, cache wipe fixes these types of things often
Click to expand...
Click to collapse
sorry,did not mention.
locked bootloader,stock 5.1.1 rom rooted and recovery,xposed installed.
i need a way to track what causes this situation,maybe an adb command?

broky said:
sorry,did not mention.
locked bootloader,stock 5.1.1 rom rooted and recovery,xposed installed.
i need a way to track what causes this situation,maybe an adb command?
Click to expand...
Click to collapse
I don't know much in that realm, but I read this one time - http://forum.xda-developers.com/showthread.php?p=34960691 - looks interesting if you know what you're doing. Anyway, all I really had to offer is attempting a cache wipe, which you probably tried. Besides that, if it happens consistently, you could experiment with disabling Xposed modules one at a time, for a day or so, and see if that reveals it. I have gotten black screen before from installing incompatible modules before, but it would just boot to the black screen. I haven't had it happen only occasionally like that. My guess would definitely be somewhere with Xposed. Maybe something clashing with built-in settings, ( I don't remember what it's called, but there's something that senses when yo pick up the phone, and it wakes up automatically - that kind of thing).

levone1 said:
I don't know much in that realm, but I read this one time - http://forum.xda-developers.com/showthread.php?p=34960691 - looks interesting if you know what you're doing. Anyway, all I really had to offer is attempting a cache wipe, which you probably tried. Besides that, if it happens consistently, you could experiment with disabling Xposed modules one at a time, for a day or so, and see if that reveals it. I have gotten black screen before from installing incompatible modules before, but it would just boot to the black screen. I haven't had it happen only occasionally like that. My guess would definitely be somewhere with Xposed. Maybe something clashing with built-in settings, ( I don't remember what it's called, but there's something that senses when yo pick up the phone, and it wakes up automatically - that kind of thing).
Click to expand...
Click to collapse
thanks mate i m working on it and i ll repopt back if i solve it and how or need more help
SOLVED:after a lot of testing found out that my problem was xposed framework v74-sdk22.
from the moment i installed xposeeed v75-sdk22 everything works as it should,not a single reboot and phone is rebooting faster also and no lag as i used to have before,fingers crossed it won t show up again:good: