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

[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.

Problem with receiving calls?

Hello all,
Recently I've been having problems with my phone in that sometimes whenever I get a call, I'd hear 2 seconds of my ringtone play and then it would cut off and then vibrate.
At other times, the same thing would happen, except the entire phone would just freeze and continuously vibrate (one long vibration no pauses).
Now if I restart my phone, I can receive calls normally but the problem returns after the phone is on for a long time.
The only thing I've recently done differently is that I installed a new 32GB mirco sd card. Any solution for it?
(Also, I am running Cm7.0.3)

NovaStark said:
Hello all,
Recently I've been having problems with my phone in that sometimes whenever I get a call, I'd hear 2 seconds of my ringtone play and then it would cut off and then vibrate.
At other times, the same thing would happen, except the entire phone would just freeze and continuously vibrate (one long vibration no pauses).
Now if I restart my phone, I can receive calls normally but the problem returns after the phone is on for a long time.
The only thing I've recently done differently is that I installed a new 32GB mirco sd card. Any solution for it?
(Also, I am running Cm7.0.3)
Click to expand...
Click to collapse
Any chance you use set cpu ( or something similar) and underclock ur phone too much when in sleep ??

vashishtuday said:
Any chance you use set cpu ( or something similar) and underclock ur phone too much when in sleep ??
Click to expand...
Click to collapse
Nope, didn't do anything with the CPU settings.
Also sometimes, I might press the power button and the screen will not come on but the menu button and home button will light up though.

try different ROM

Hey
even i had the same issue with CM7 , i think as Nova said try a diff rom
give oxygen a try maybe

vashishtuday said:
Hey
even i had the same issue with CM7 , i think as Nova said try a diff rom
give oxygen a try maybe
Click to expand...
Click to collapse
It seems I will have to do that then.
Is flashing from Cm7 to oxygen just to wipe Davlik, battery stats and cache and then flash with the oxygen zip? Or do more things have to be done?
(The last time I flashed to Cm7 was a few months ago)

I have similar problems as the thread starter.. I'm using MildWild 4.0 based on oxygen. When I get a call, it plays ringtone less than a second, also vibrating stops. So it doesn't cut the call, only ringtone and vibrating stops. Does anyone know fix for this?
The problem got fixed when I unistalled K9 mail program..

[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…)

Fingerprint scanner randomly not working

I'm just trying to narrow down why randomly the fingerprint scanner does not wake the phone. It might happen once a day or not for a couple of days, but it seems to always come back. Not a huge deal since the power button will always work, but it is disconcerting when it happens. I'm not using any power widget or lock program although I do use Nova Launcher Pro. Does this happen to anyone else and if so have you narrowed it down?

Mine always wakes my phone, although every now and then it doesn't recognize my print. However, I believe it's because of how my finger lays on the sensor so I think it's user error in my case.
I've registered 4 prints, 2 from each index finger and all in different positions on the sensor to get the least reading errors.
Are you saying that you get no vibration as in it doesn't even register at times therefore you HAVE to use the power button to wake it?
I use nova pro too.

jbdan said:
Mine always wakes my phone, although every now and then it doesn't recognize my print. However, I believe it's because of how my finger lays on the sensor so I think it's user error in my case.
I've registered 4 prints, 2 from each index finger and all in different positions on the sensor to get the least reading errors.
Are you saying that you get no vibration as in it doesn't even register at times therefore you HAVE to use the power button to wake it?
I use nova pro too.
Click to expand...
Click to collapse
Yes exactly, no vibration. I've had it where it vibrates and doesn't unlock because my fingers are slightly wet or something. This is like it doesn't even know my finger is on the sensor. Power button unlocks and then it works again. Last time I said ok I'm not unlocking with the power button I'm gonna get this to work. Nope, had to power button it on after a minute or so of trying. As I said, it's not that big a deal and only happens once in a while. Glad it's not Nova though. Kernel dev said it's not the kernel , I'm using Elemental X. I might try going back to the stock kernel just to test it out. Problem is that I can't reproduce it.

bobby janow said:
Yes exactly, no vibration. I've had it where it vibrates and doesn't unlock because my fingers are slightly wet or something. This is like it doesn't even know my finger is on the sensor. Power button unlocks and then it works again. Last time I said ok I'm not unlocking with the power button I'm gonna get this to work. Nope, had to power button it on after a minute or so of trying. As I said, it's not that big a deal and only happens once in a while. Glad it's not Nova though. Kernel dev said it's not the kernel , I'm using Elemental X. I might try going back to the stock kernel just to test it out. Problem is that I can't reproduce it.
Click to expand...
Click to collapse
I get this occasionally when charging but that occurred on stock everything, can't say I've noticed it in any other capacity. Are you using smart lock or an app to lock your screen?
Edit: I should read your post before replying, disregard my app question. Still asking about smart lock though.
Sent from my Nexus 5X using Tapatalk

bobby janow said:
Yes exactly, no vibration. I've had it where it vibrates and doesn't unlock because my fingers are slightly wet or something. This is like it doesn't even know my finger is on the sensor. Power button unlocks and then it works again. Last time I said ok I'm not unlocking with the power button I'm gonna get this to work. Nope, had to power button it on after a minute or so of trying. As I said, it's not that big a deal and only happens once in a while. Glad it's not Nova though. Kernel dev said it's not the kernel , I'm using Elemental X. I might try going back to the stock kernel just to test it out. Problem is that I can't reproduce it.
Click to expand...
Click to collapse
And I meant to include the "big" question in my original reply. Big being "what mods are you using"
Best way to trial and error issues as you well know? I'd test it on all stock (for a day or 2) and see what that gets you then you can narrow down to if it's the kernel or not. I'm not a kernel dev, but an educated guess would point to that imo

SlimSnoopOS said:
I get this occasionally when charging but that occurred on stock everything, can't say I've noticed it in any other capacity. Are you using smart lock or an app to lock your screen?
Edit: I should read your post before replying, disregard my app question. Still asking about smart lock though.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Smart lock, yes. Well smart unlock isn't it? I have a couple of BT unlock devices, Mi Band and car BT radio but that's it.

jbdan said:
And I meant to include the "big" question in my original reply. Big being "what mods are you using"
Best way to trial and error issues as you well know? I'd test it on all stock (for a day or 2) and see what that gets you then you can narrow down to if it's the kernel or not. I'm not a kernel dev, but an educated guess would point to that imo
Click to expand...
Click to collapse
No mods.. well let me rephrase that. I have a bunch of programs running naturally, but the only "mod" I have is Cataclysm and systemless root along with Elemental X kernel. Cataclysm is considered a mod these days as it's just an overlay on stock 6.01. I know I'd have to go full stock to test for a few days but I'm so so trying to avoid that as I'm sure you know. Thanks for all the input guys, I know this can't just be me right? Hey wait a sec.. I do have a BT smart band unlock running. I'm going to take that off and see if that makes a difference. Maybe that is interfering with the fingerprint requirement.
Edit..nope not it. Gonna run stock kernel next.

The exact same thing is happening to me. Same symptoms but I am on fully stock. I'm also using nova pro. Been searching around for an answer but haven't found anything.

tofuwrice said:
The exact same thing is happening to me. Same symptoms but I am on fully stock. I'm also using nova pro. Been searching around for an answer but haven't found anything.
Click to expand...
Click to collapse
Too many people on Nova Pro for it to be an undocumented issue. I know it's been said that it is not the kernel, however, yesterday morning I flashed this one http://forum.xda-developers.com/nexus-5x/orig-development/jolla-kernelbullhead-t3271530 and I've not had the issue since. I usually have it at least once / day and none so far. That doesn't mean it's not going to happen in 5 minutes though. I went with stock kernel values if you're rooted and feel like giving it a try.

I was having this issue randomly when running custom hotplugging. Currently no issues with default cpu hotplug settings and ElementalX.

For me I have a case on my 5x. There are two cutouts - one for fingerprint sensor and one for camera. They're both about the same size. Every once in awhile I find myself reaching for the camera instead of the fingerprint sensor. When I first got the phone I thought my fingerprint wasn't working at times. Turns out I was just putting my finger on the camera instead of the fingerprint sensor. Any chance this is what's going on?

jgummeson said:
For me I have a case on my 5x. There are two cutouts - one for fingerprint sensor and one for camera. They're both about the same size. Every once in awhile I find myself reaching for the camera instead of the fingerprint sensor. When I first got the phone I thought my fingerprint wasn't working at times. Turns out I was just putting my finger on the camera instead of the fingerprint sensor. Any chance this is what's going on?
Click to expand...
Click to collapse
Don't make me question my own sanity! hehe. I did the same thing at the outset but quickly realized my error. This is not what happens here, however. I even put it back in my pocket once to make sure it wasn't some aberration. It just wouldn't recognize there was even a finger there. Almost thought the phone had shut down but power button got it working again. Haven't had the issue in well over a day now with this kernel but I'm not sure that's what it is.

bobby janow said:
Don't make me question my own sanity! hehe. I did the same thing at the outset but quickly realized my error. This is not what happens here, however. I even put it back in my pocket once to make sure it wasn't some aberration. It just wouldn't recognize there was even a finger there. Almost thought the phone had shut down but power button got it working again. Haven't had the issue in well over a day now with this kernel but I'm not sure that's what it is.
Click to expand...
Click to collapse
This has happened to me twice. Both times while charging. Has not happened any other time. (stock everything/not rooted)

morenoa48 said:
This has happened to me twice. Both times while charging. Has not happened any other time. (stock everything/not rooted)
Click to expand...
Click to collapse
Happened to me not charging, rooted with custom kernel. So it's across the board hit or miss. I have a feeling it will be fixed in an update or OTA. Not a deal breaker just odd is all. Oh well, if we didn't have a power button it would be major.

After 3 years of usage my Nexus 5X fingerprint scanner stopped working at all and i can't do anything about it apparently. The issues started when i sent the phone to LG to fix the bootloop