Develop Bugs

[Q] Dialer Sensor Usage

I've seen a similar post to this way back in the day when I first rooted my phone, but since then have been unable to relocate said post, so I'll just post here as I've noticed this to be a constant problem, perhaps GB related.
Days where I don't make any phone calls I get decent battery life, about 1% every 2 hours and that's listening to music. But god forbid I have to make a phone call because then Dialer remains on consuming my sensor in spare parts. I've disabled just about everything in call settings related to sensors and even tried turning my BT on as I read it might fix it, no dice. The only way to fix atm is to restart or perform a hot reboot.
Anybody else experiencing this or have found a fix? Currently running Decks 1.3d and thinking of going back to a Sense rom cuz I never dealt with this crap before I tried AOSP, even though I love and prefer AOSP over Sense.

Naturesretard said:
I've seen a similar post to this way back in the day when I first rooted my phone, but since then have been unable to relocate said post, so I'll just post here as I've noticed this to be a constant problem, perhaps GB related.
Days where I don't make any phone calls I get decent battery life, about 1% every 2 hours and that's listening to music. But god forbid I have to make a phone call because then Dialer remains on consuming my sensor in spare parts. I've disabled just about everything in call settings related to sensors and even tried turning my BT on as I read it might fix it, no dice. The only way to fix atm is to restart or perform a hot reboot.
Anybody else experiencing this or have found a fix? Currently running Decks 1.3d and thinking of going back to a Sense rom cuz I never dealt with this crap before I tried AOSP, even though I love and prefer AOSP over Sense.
Click to expand...
Click to collapse
I would look for the topic about wake lock, there is a possible fix in there if I remember right. Also could try to reflash decks, I've never had a problem.
Sent from my PC36100 using xda premium

I agree with the guy above me, you should check the thread of whatever ROM your using as well, and for a quick fix you could always just push the Power/Screen Lock button

http://forum.xda-developers.com/showthread.php?p=14814224
Sent from my PC36100 using xda premium

[Q] Screen goes black, and wont turn back on again during calls..

I recently changed my mini-jack and my speaker on the HTC Desire.. Now I got a new problem during calls, my screen goes black as usual during calls. But when I try to make it responsive again - it wont act.. Only way to fix it, is to restart my phone.. I read something about the sensor, but never found a way to fix it..
How can I fix this problem?
Best regards,
DanVazz

Your proximity sensor is broken, likewise is mine. In some ROMs (CM7 definitely), you can wake the phone with power.

i've the same problem, but it's cause of a bug of my current rom(nikez ics). i solved with a cpu governor change, form ondemand to conservative.

DanVazz said:
I recently changed my mini-jack and my speaker on the HTC Desire.. Now I got a new problem during calls, my screen goes black as usual during calls. But when I try to make it responsive again - it wont act.. Only way to fix it, is to restart my phone.. I read something about the sensor, but never found a way to fix it..
How can I fix this problem?
Best regards,
DanVazz
Click to expand...
Click to collapse
did you not miss a piece of rubber going ot top of proximity sensor?
(my own experience)

kotag82 said:
did you not miss a piece of rubber going ot top of proximity sensor?
(my own experience)
Click to expand...
Click to collapse
I dont think so.. Did u manage to fix yours?

Yes that was my problem I found it under my desk, since everything works fine
Sent from my HTC Sensation Z710e using XDA Premium App

kotag82 said:
Yes that was my problem I found it under my desk, since everything works fine
Sent from my HTC Sensation Z710e using XDA Premium App
Click to expand...
Click to collapse
How did the rubber "thing" look like?

http://dl.dropbox.com/u/71463016/DSC00158-small.jpg

Thank you so much!
This worked for me! Seems like I didn't get it with the package I bought.
Once again thank you so much kotag82!
Best regards,
DanVazz

glad to hear that, enjoy

Hmm maybe that's why mine's broken.
EDIT: Nope, it was there.

Proximity Sensor Issue?

When i place a call and put the phone to my ear and then pull back away the screen does not "wake". It stays de-activated, no matter what i do. Eventually the only thing to do is to hold the power button down long enough for the phone to reboot.
Stock ROM, no root.
Thanks for any help anyone can offer.

WTF
I tested by laying the phone flat on a surface, placed a call, and then put my hand over the proximity sensor. The screen turned black as it should. When I removed my hand it did not come back on. Again, the only solution is to reboot the phone. So, the proximity sensor is not working correctly. Is this a known issue and is there a way to fix?

BUMP!
I'm in the self test module and am running the "sensors" test. I'm not sure when this ends if it ends at all or what values that proximity sensor field should have.
Anybody? Bueller?

Apparently Q&A isn't the place to post this? This is dissapointing coming from the E4GT forums which were super responsive.

Cool yer jets. It's only been a few hours. What ROM? Rooted? Any other mods that might affect it?

dkmdlb said:
Cool yer jets. It's only been a few hours. What ROM? Rooted? Any other mods that might affect it?
Click to expand...
Click to collapse
LOL
I said no root stock ROM
Anyway, I turned off the proximity sensor, verified that it was off, then turned it back on. It works now. Bizarre.
Sorry to get pissy.

oregondave said:
LOL
I said no root stock ROM
Anyway, I turned off the proximity sensor, verified that it was off, then turned it back on. It works now. Bizarre.
Sorry to get pissy.
Click to expand...
Click to collapse
Where is the sensor setting?
Edit. Found it.
Sent from my SGH-T999 using Tapatalk 2

NOT FIXED
So after a reboot the proximity sensor does not work on calls again. I turned it off and then back on and still no luck. I didn't actually make a call, but obviously I shouldn't have to do this every time i reboot the phone, so clearly there is an issue. It appears to be software since I got it to work once.
Any ideas? Thanks.

oregondave said:
So after a reboot the proximity sensor does not work on calls again. I turned it off and then back on and still no luck. I didn't actually make a call, but obviously I shouldn't have to do this every time i reboot the phone, so clearly there is an issue. It appears to be software since I got it to work once.
Any ideas? Thanks.
Click to expand...
Click to collapse
Your getting screen of death.. man thats so ****ty..
Uh, you can try this.. Settings - Accessibility - Call answering/ending - power button ends calls ?

aklyrical said:
Your getting screen of death.. man thats so ****ty..
Uh, you can try this.. Settings - Accessibility - Call answering/ending - power button ends calls ?
Click to expand...
Click to collapse
? Uh No. Thanks?

After insalling a new screen my phone acted the same. I opened it up again and found a tiny piece of plastic form the old screen inside the proximity sensor hole.
I know your problem is not this, just wanted to share

gberger42 said:
After insalling a new screen my phone acted the same. I opened it up again and found a tiny piece of plastic form the old screen inside the proximity sensor hole.
I know your problem is not this, just wanted to share
Click to expand...
Click to collapse
hmmm interesting. I think this is likely a software issue on mine. it would be dumb to have to return it since i'm confident there's a way to fix it.

oregondave said:
hmmm interesting. I think this is likely a software issue on mine. it would be dumb to have to return it since i'm confident there's a way to fix it.
Click to expand...
Click to collapse
That solution wasn't very good aha, what I would suggest you root your phone without tripping the flash counter and install a custom rom to see if the issue still exists, if yes you should return the phone.

aklyrical said:
That solution wasn't very good aha, what I would suggest you root your phone without tripping the flash counter and install a custom rom to see if the issue still exists, if yes you should return the phone.
Click to expand...
Click to collapse
thanks well it's brand new and it may be hardware related so i'd rather just get a fresh device then sweat dealing with root yet. this is why i waited to root it. I appreciate your effort though .

aklyrical said:
That solution wasn't very good aha, what I would suggest you root your phone without tripping the flash counter and install a custom rom to see if the issue still exists, if yes you should return the phone.
Click to expand...
Click to collapse
Plus I don't think just rooting it is a sound fix strategy.
Nobody has anything on this huh?
BTW, Wirefly sucks...

Have you already done a master reset?
sent from my SGS3... the envy of all many friends!

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

Wake up delay

Anyone else experiencing a really long delay when you try to wake your phone up? About 70% of the time when I wake my phone up to just use my phone, it has a bad delay. Most of the time it will take around 7 - 10 seconds for the screen to turn on.
I am stock and un-rooted. I have gone into the stock recovery and cleared the cache partition a couple of times, but that doesn't help. I am really hoping for S-off soon. I'm hoping that a custom rom can fix it.

I'm also experiencing this same problem, drives me insane. I'm hoping that maybe the forthcoming 5.1 update will address that issue.

I've never experienced this. I'm stock still. Kinda sounds like a runway app causing the problem.

Never saw this on launch os or 5.1. Have you tried running it without apps for a while?

Last night I disabled instagram. It seemed to fix the problem so far. I don't use it much anyway. My battery stat still shows it as number 2 on the list. I just uninstalled it. Maybe it will fix some issues.

I have this too...but I'd say only about 30 percent of the time. I use the double tap to wake aout it certainly does not all the time.

Mine does it sometimes. I don't know if it's a delay because I push the power button again and it comes on. Another thing that drives me up the wall is that the screen doesn't wake up after taking the phone away from my ear during a call sometimes. I'll have to push the power button to turn the screen on.
Sent from my HTC6535LVW using Tapatalk

Evocm7 said:
Mine does it sometimes. I don't know if it's a delay because I push the power button again and it comes on. Another thing that drives me up the wall is that the screen doesn't wake up after taking the phone away from my ear during a call sometimes. I'll have to push the power button to turn the screen on.
Sent from my HTC6535LVW using Tapatalk
Click to expand...
Click to collapse
This sounds like either a case problem, or proximity sensor.
You can test the sensor in htc advantage app.

andybones said:
This sounds like either a case problem, or proximity sensor.
You can test the sensor in htc advantage app.
Click to expand...
Click to collapse
I just tried it, it passed the tests a few times. I have a spigen neo hybrid so it doesn't come even close to the sensor. Who knows.
Sent from my HTC6535LVW using Tapatalk

Mine doesn't wake up after a call sometimes. It just started doing the delay thing again. I wonder if it has anything to do with memory leak on 5.0? I may disable a couple games I downloaded this week and see if that fixes it.

andybones said:
This sounds like either a case problem, or proximity sensor.
You can test the sensor in htc advantage app.
Click to expand...
Click to collapse
Andybones, maybe I'm being a little dense but the htc advantage app? what or where can I find this? Thanks, Howie

meandg5 said:
Andybones, maybe I'm being a little dense but the htc advantage app? what or where can I find this? Thanks, Howie
Click to expand...
Click to collapse
Playstore search app: HTC Help.

andybones said:
Playstore search app: HTC Help.
Click to expand...
Click to collapse
Thank you sir!
Sent from my HTC6535LVW using XDA Free mobile app