I'm brand new to HTC devices so I'm unsure if the dialer is sense or if this is a ICS dialer were dealing with. (My old phone was a Droidx, so my exp is with blur and asop 2.3 from liberty).
Either way though i seem to have come across an interesting "bug" or at least unusual behavior.
I've noticed on almost every other call, weather it's incoming or outgoing, the MOMENT you dial/answer the screen goes dark. Now i can press the power button to wake it up again and it will stay on for exactly 5 seconds before going dark again. If i flip on speaker phone the screen will stay on, however the moment i turn off speaker phone it goes dark again.
Whats really annoying is if i go back to the home screen it still goes dark after 5 seconds but now when i wake it up it's at the lock screen. If i try to unlock it the moment i touch the screen it goes dark. No matter where i touch the screen the phone is now perma locked until the call is finished.
Now like i said this happens every other call so far in the 6 times I've tested this, which i thought was really odd. The other times the screen stays on and acts completely normal no matter what i do while a call is active. Fresh reboot makes no difference. I haven't done a factory reset yet as I'm trying avoid that.
What i have done so far is unlocked the bootloader, Flashed recovery, and the root from con247's thread in the dev section. I don't think that has anything to do with it though since i noticed the screen going black during a call before i started messing with bootloaders/recovery/root. I just didn't test it as well before doing those things cuz i didn't think anything of it.
Is anyone else seeing this behavior and does anyone have any suggestions?
Void4ever
void4ever said:
I'm brand new to HTC devices so I'm unsure if the dialer is sense or if this is a ICS dialer were dealing with. (My old phone was a Droidx, so my exp is with blur and asop 2.3 from liberty).
Either way though i seem to have come across an interesting "bug" or at least unusual behavior.
I've noticed on almost every other call, weather it's incoming or outgoing, the MOMENT you dial/answer the screen goes dark. Now i can press the power button to wake it up again and it will stay on for exactly 5 seconds before going dark again. If i flip on speaker phone the screen will stay on, however the moment i turn off speaker phone it goes dark again.
Whats really annoying is if i go back to the home screen it still goes dark after 5 seconds but now when i wake it up it's at the lock screen. If i try to unlock it the moment i touch the screen it goes dark. No matter where i touch the screen the phone is now perma locked until the call is finished.
Now like i said this happens every other call so far in the 6 times I've tested this, which i thought was really odd. The other times the screen stays on and acts completely normal no matter what i do while a call is active. Fresh reboot makes no difference. I haven't done a factory reset yet as I'm trying avoid that.
What i have done so far is unlocked the bootloader, Flashed recovery, and the root from con247's thread in the dev section. I don't think that has anything to do with it though since i noticed the screen going black during a call before i started messing with bootloaders/recovery/root. I just didn't test it as well before doing those things cuz i didn't think anything of it.
Is anyone else seeing this behavior and does anyone have any suggestions?
Void4ever
Click to expand...
Click to collapse
Sounds like the proximity sensor is going wonky. You might try a factory reset and without installing anything else see if you get the same issue. Also, make sure that any programs you have installed are not affecting it for some reason.
blazingwolf said:
Sounds like the proximity sensor is going wonky. You might try a factory reset and without installing anything else see if you get the same issue. Also, make sure that any programs you have installed are not affecting it for some reason.
Click to expand...
Click to collapse
Just factory reset it, skipped setup completely and started making calls, same issue. You maybe right about the sensor though. The first call acted up like i explained. The second call the screen was staying on like i expected, but once i switched speaker phone off and then back on the screen shut off and started acting like call one again.
I just got this phone 6 hours ago i wonder how hard it will be to convince verizon there's a hardware fault. I guess i'd better unroot it and remove recovery so i can call in the morning.
Void4ever
I just wanted to make sure i understand this before i do it.
To remove the root i need to install the RUU for the phone, which i found at http://themikmik.com/showthread.php?13550-Asian-Shooter-goes-ICS-and-a-VZW-Fireball-RUU (second link i assume).
I haven't downloaded it yet, but it's an exe. Will it flash the phone via USB, or does it just extract something i can use recovery to flash with?
Once i get the root removed i just need to flash back the original recovery and i should be good to go right?
Void4ever
void4ever said:
I just wanted to make sure i understand this before i do it.
To remove the root i need to install the RUU for the phone, which i found at http://themikmik.com/showthread.php?13550-Asian-Shooter-goes-ICS-and-a-VZW-Fireball-RUU (second link i assume).
I haven't downloaded it yet, but it's an exe. Will it flash the phone via USB, or does it just extract something i can use recovery to flash with?
Once i get the root removed i just need to flash back the original recovery and i should be good to go right?
Void4ever
Click to expand...
Click to collapse
There are directions in the RUU that will explain all of the steps. You will connect your phone with the USB cable.
It shouldn't be to hard to convince them. Just show them the steps you did to reproduce the issue. Good luck.
On the phone right now and the guy is setting up overnight sat delivery to my house. We are a fairly large business account so i'm glad they are going that extra mile.
Just to note I've noticed the sensor doesn't shut off after a call is complete. In fact it stayed on last night for around 6 hours before finally turning off. I did another test this morning and once again the sensor is stuck on, so good call. Thanks so much for your help, i never would have thought sensor, it seemed like a software issue to me!
Void4ever
void4ever said:
On the phone right now and the guy is setting up overnight sat delivery to my house. We are a fairly large business account so i'm glad they are going that extra mile.
Just to note I've noticed the sensor doesn't shut off after a call is complete. In fact it stayed on last night for around 6 hours before finally turning off. I did another test this morning and once again the sensor is stuck on, so good call. Thanks so much for your help, i never would have thought sensor, it seemed like a software issue to me!
Void4ever
Click to expand...
Click to collapse
No problem. Glad you got a new one coming.
replacement came today and it works like a dream now, got custom recovery and root going! It was def a bad prox sensor on the other one. Thanks again for your help wolf!
Void4ever
Good to hear man. Enjoy that puppy.
void4ever said:
replacement came today and it works like a dream now, got custom recovery and root going! It was def a bad prox sensor on the other one. Thanks again for your help wolf!
Void4ever
Click to expand...
Click to collapse
Awesome.
Sent from my ADR6410LVW using Tapatalk 2
Related
I was installing some apps on my phone and suddenly the screen turned off. When I tried to turn it on, nothing happened. I then let the phone sit for a minute and still nothing would happen until I noticed the buttons turning on and off. I tried swiping where the unlock would be when the buttons come on and it worked. I could tell from the tactile feel. I then rebooted the phone by pressing and holding the power button and guessing where restart would be. The screen works again.
Has anyone else experienced this problem? First time for me.
hpcolombia said:
I was installing some apps on my phone and suddenly the screen turned off. When I tried to turn it on, nothing happened. I then let the phone sit for a minute and still nothing would happen until I noticed the buttons turning on and off. I tried swiping where the unlock would be when the buttons come on and it worked. I could tell from the tactile feel. I then rebooted the phone by pressing and holding the power button and guessing where restart would be. The screen works again.
Has anyone else experienced this problem? First time for me.
Click to expand...
Click to collapse
I had it happen to me once, when I first got the phone. Exactly as you described, except I had to battery pull. I was using an app called Screen Filter, so I could dim the capacitive lights. I figured it had to do with that app, so i removed it. I haven't had it happen since. I'm not sure if it was Screen Filter that caused it or not, but I haven't had it happen again since I removed it. Either that, or just a coincidence.
Happened to me once when I was messing with a root script that had a bug. Ended up clearing some of my app data too. Seems like a common "brain death" state that the phone can get into. I'm pretty sure it's software related and nothing to worry about.
Mike
it happens to me often, and I too have screen filter... but that isn't the cause of the problem (i got it to dim the buttons but it doesn't work on those yet).
I'm not sure what the problem is, but you can eventually turn the screen back on and reboot it - just keep at it. Do you have anything plugged into the headphones jacks BTW? If you do, and you try to reboot, it'll hang. It's done that to me a few times so I unplugged the headphones everytime
Started happening to me after i installed either switkey x or the amazon app, i am not sure but i think that's what caused it
SwiftKey works fine for me... try reinstalling it. Same far any other apps that cause issues, make sure the download was good and reinstall.
If the phone freezes, remember that the only ways to get a try restart is a dead battery or battery pull. Wifes phone froze and shut off, would not restart until a battery pull.
Good luck!
Sent from my phone
Happens to me too and it is really irritating.
GhettoBSD said:
it happens to me often, and I too have screen filter... but that isn't the cause of the problem (i got it to dim the buttons but it doesn't work on those yet).
I'm not sure what the problem is, but you can eventually turn the screen back on and reboot it - just keep at it. Do you have anything plugged into the headphones jacks BTW? If you do, and you try to reboot, it'll hang. It's done that to me a few times so I unplugged the headphones everytime
Click to expand...
Click to collapse
It works perfect for dimming (well turning off) the buttons, check your settings!
so i keep having the same problem even without the swiftke y installed tried to reboot and even factory reset no luck. did you find any solutions.
used to happen a lot when i had aosp roms on my old hero
Are you guys overclocked?
I am not overlooked and I exchanged to another phone.
Sent from my PG86100 using XDA App
iliapiano said:
I am not overlooked and I exchanged to another phone.
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
Damn....I may have to do that. Sprint allowed you to exchange with no hassle? It seems to happen so randomly that I don't think my Sprint Store will exchange it if they can't reproduce it.
freeza said:
Are you guys overclocked?
Click to expand...
Click to collapse
My wife was oc when hers froze
Sent from my phone
I'm overclocked but the issue @ hand is software related. When I had the OG Evo, certain kernels would cause the screen to act in the same matter stated in the op. A lot of bugs that people report would be resolved once we get perm. Root.
My ''xDU4L C0R3 SH00T3Rx'' shot you down in 3D!
SO this has happened to me and I am freaking out thinking its the aosp rom. how long did it take for the screen to light up again. it been like two hours for mine.
When I answer the phone the screen immediately shuts off, I would like to keep it from doing it right away. For instance, if I want to turn on speaker phone I have to unlock and then press speaker phone while the person is wondering who has answered lol.
Poiuyt00 said:
When I answer the phone the screen immediately shuts off, I would like to keep it from doing it right away. For instance, if I want to turn on speaker phone I have to unlock and then press speaker phone while the person is wondering who has answered lol.
Click to expand...
Click to collapse
thats odd. I know the dimming of the display has to do with the proximity sensor, do you have a screen protector on that my be slightly covering the sensor itself? I had eclipse v2.1 and 2.2 and never encounter this problem. And i just looked through the phone settings on my x2 and cant find any settings related (im currently on cm9 though) may be possible you need to reflash eclipse 2.1 =(
Mine does the same thing and I'm on 2.1. Sometimes it drives me nuts. There's nothing I've found that will help. I'm pretty sure it has something to do with the position of the phone being level or not. That's more technical than I can explain. I've done it so many times now that its really automatic to when it comes to pushing the lock/unlock.
It just hit me: I have noticed that if you unlock the phone to select the speakerphone and or dialpad, I'm pretty sure it stays on. It's just the intial unlocking that's tricky, yet forgetful.
Thanks at least I am not alone in this. It happens other times also but always involves the dialer in some way.
Hello.
When I leave my phone in sleep mode (screen locked and light off) and try to wake with On/Off button, sometimes I get a black screen with a faintly image. The touchscreen works and all the buttons, and if you click 2 times On/Off button - the image appears all ok. I tried to flash another stock ROM - all the same. Then I`ve unlocked the bootloader, rooted the phone and even did the S-off with wire trick (1.53 Hboot). Then I`ve tried 3-4 custom ROMs with 6-7 different kernels, from stock to custom, but all the same. Yes, I`ve updated the firmware file, also, but with no difference.
Well, I see that this problem is not so usual, but I couldn`t find any real solution. Did anyone have this kind of problem and solved it? Since I got this phone from another country - official warranty is out of the question, I need a DIY solution.
Any help is greatly appreciated.
THX in advance!!!
I would have to say it looks like the light for your screen is dying, I had my screen replaced once, my screen would flicker from very dark to very bright
Sent from my HTC EVO 3D X515m using xda premium
flashallthetime said:
I would have to say it looks like the light for your screen is dying, I had my screen replaced once, my screen would flicker from very dark to very bright
Sent from my HTC EVO 3D X515m using xda premium
Click to expand...
Click to collapse
hmmmm, but when I get the OK image - it doesn`t flicker or go from dark to bright, it only has trouble to "wake up from sleep mode". even when i relock the screen quickly and don`t leave it unused for 2-3 minutes, the screen works OK every time....it looks like a software problem, but still I didn`t manage to fix it with all the ROMs/kernels/firmwares I`ve flashed....
E-ducation said:
Hello.
When I leave my phone in sleep mode (screen locked and light off) and try to wake with On/Off button, sometimes I get a black screen with a faintly image. The touchscreen works and all the buttons, and if you click 2 times On/Off button - the image appears all ok. I tried to flash another stock ROM - all the same. Then I`ve unlocked the bootloader, rooted the phone and even did the S-off with wire trick (1.53 Hboot). Then I`ve tried 3-4 custom ROMs with 6-7 different kernels, from stock to custom, but all the same. Yes, I`ve updated the firmware file, also, but with no difference.
Well, I see that this problem is not so usual, but I couldn`t find any real solution. Did anyone have this kind of problem and solved it? Since I got this phone from another country - official warranty is out of the question, I need a DIY solution.
Any help is greatly appreciated.
THX in advance!!!
Click to expand...
Click to collapse
Thinking about how to troubleshoot if hardware or software. When in sleep mode, instead of using the power button, I would have the phone plugged into a computer and use the " adb reboot " command to reboot the phone without touching the phone a few times and see if it lights up correctly. The first thing you should see is the boot screen, and if it works every time, then you do have an issue with your firmware. If you don't see that boot screen first every time, then as much as it sucks, I would guess there is a hardware issue.
Good luck, but this is the easiest way I know of to help determine what the issue likely is.
Minor update here, the first thing (at least on mine) that I see is the lock screen for just a quick second or two, then it quickly goes into the boot sequence. This is important as in "sleep" the ROM is running, so if the first thing you see is the boot sequence every time, and not the lock screen, then it points more to a software problem than a hardware issue. CM9 had an issue for the epic4g where you had to turn it off and on sometimes to get the keyboard to light. They found the issue in the firmware causing it.
Just wanted to make this as accurate as possible.
Wow so I am not the only person with this problem. The EVO 3D that I have was replacement phone that was given to me from Sprint from the first EVO 3D that I had which had issues with the digitizer. I received the replacement phone this past Tuesday and it worked fine for two days. It was not rooted and I did install the ICS update. On Friday morning I took it off the charger and went to work, while in the break room the screen suddenly went black and I could not get the phone to display anything after that. The Android function buttons at the bottom will light up but the screen wont, the phone also gets hot even with it powered off.
Long story short, I took it back to the Sprint store where they ordered me yet another replacement EVO 3D. Has anyone had to go through 3 EVO 3Ds or more?
sonza said:
Thinking about how to troubleshoot if hardware or software. When in sleep mode, instead of using the power button, I would have the phone plugged into a computer and use the " adb reboot " command to reboot the phone without touching the phone a few times and see if it lights up correctly. The first thing you should see is the boot screen, and if it works every time, then you do have an issue with your firmware. If you don't see that boot screen first every time, then as much as it sucks, I would guess there is a hardware issue.
Good luck, but this is the easiest way I know of to help determine what the issue likely is.
Minor update here, the first thing (at least on mine) that I see is the lock screen for just a quick second or two, then it quickly goes into the boot sequence. This is important as in "sleep" the ROM is running, so if the first thing you see is the boot sequence every time, and not the lock screen, then it points more to a software problem than a hardware issue. CM9 had an issue for the epic4g where you had to turn it off and on sometimes to get the keyboard to light. They found the issue in the firmware causing it.
Just wanted to make this as accurate as possible.
Click to expand...
Click to collapse
Excellent thinking, I didn't think in that direction. I'll try this tomorow, since I'm not at home. My personal oppinion that it's a software problem but if I did all the above - what did I miss? If I flashed the firmware, ROM and kernel, what else is left untouched that could affect the LCD? Could anyone suggest a good kernel? Or can I downgrade the firmware, since no one had such a problem with GB?
just to inform all - I tried all soft solutions, but all the samo. finaly - I replaced the LCD and everything is OK.
THX all for help
I have had my Verizon Note 2 for about a month now, and about 2 days ago i read that the processor has Vulnerabilities and mailware problems samusing is trying to fix but about a week ago i went to use my quick glance and my direct call and it wasnt working and when someone calls me i put it up to my ear the screen goes black as it should but then its stuck at the black screen i hit all the buttons cant get to the phone call if i wanted to put it on speaker or even just check a txt message i cant do anything until that person hangs up. The only way i am able to check my txt messages and stuff while on the phone is if i dont put it up to my ear.. so i restarted phone as we all would assume this would fix it well it didnt, so then i did a Factory reset thinking that would just put it back to complete stock and fix it well turns out that didnt work. My phone has never been rooted or anything and never will be. Im running Android 4.1.1 If anyone has any idea how i can fix this it would be gladly appreciated i love the motion features. Also i did the Gyroscope calibration and it didn't make any difference, my proximity sensor is on and glowing red just doesnt work like i said.
Thanks, Stephen
Hawksfan88 said:
I have had my Verizon Note 2 for about a month now, and about 2 days ago i read that the processor has Vulnerabilities and mailware problems samusing is trying to fix but about a week ago i went to use my quick glance and my direct call and it wasnt working and when someone calls me i put it up to my ear the screen goes black as it should but then its stuck at the black screen i hit all the buttons cant get to the phone call if i wanted to put it on speaker or even just check a txt message i cant do anything until that person hangs up. The only way i am able to check my txt messages and stuff while on the phone is if i dont put it up to my ear.. so i restarted phone as we all would assume this would fix it well it didnt, so then i did a Factory reset thinking that would just put it back to complete stock and fix it well turns out that didnt work. My phone has never been rooted or anything and never will be. Im running Android 4.1.1 If anyone has any idea how i can fix this it would be gladly appreciated i love the motion features. Also i did the Gyroscope calibration and it didn't make any difference, my proximity sensor is on and glowing red just doesnt work like i said.
Thanks, Stephen
Click to expand...
Click to collapse
That exploit that you are referring to has nothing to do with your issue... And the proximity sensor does not light up as that is the LED notification light. I have this issue from time to time too and it's just that the sensor is not doing it's job properly but if you just simply hit the home button or power button real quick the screen will turn on. Other than that you may want to check some of your settings... Turn off your "motion" settings and see if that takes care of your issue then find out which one is causing the problem...
The quick glance used to work without any problems at all and i liked that, then all of a sudden one day it just decides not to work and it hasn't worked in a week now, i turned my motion off and when im in a phone call it still locked up at the phone screen i cant do anything until they hang up ive gone through the settings multiple times and nothing, i think imma go to verizon today and ***** about it
Hawksfan88 said:
The quick glance used to work without any problems at all and i liked that, then all of a sudden one day it just decides not to work and it hasn't worked in a week now, i turned my motion off and when im in a phone call it still locked up at the phone screen i cant do anything until they hang up ive gone through the settings multiple times and nothing, i think imma go to verizon today and ***** about it
Click to expand...
Click to collapse
Ya something does not sound right... Do you have a screen protector on your Note 2 that is covering the sensors?
shojus said:
Ya something does not sound right... Do you have a screen protector on your Note 2 that is covering the sensors?
Click to expand...
Click to collapse
No screen protector or anything no case either, my girlfriend yanked the battery while it was on one day idk if that has anything to do with it or not cause after that happened seemed like it didn't work
shojus said:
That exploit that you are referring to has nothing to do with your issue... And the proximity sensor does not light up as that is the LED notification light. I have this issue from time to time too and it's just that the sensor is not doing it's job properly but if you just simply hit the home button or power button real quick the screen will turn on. Other than that you may want to check some of your settings... Turn off your "motion" settings and see if that takes care of your issue then find out which one is causing the problem...
Click to expand...
Click to collapse
actually the proximity sensor DOES light up, it's a very faint red light and it's the left one of the two little holes to the _right_ of the phone speaker, the notification LED is on the left of the phone speaker. This light turns on when in a phone call to indicate that the sensor has been activated.
While making a phone call the proximity turns the screen off and keeps it off, making it difficult to toggle the screen while in calls.
This is really annoying while calling your voicemail.
Currently running unofficial CM
Thanks for your thoughts.
Full story Here:
I get to mess around with the DNA for a few days, but i'm having a proximity sensor problem,
with CM and Stock Rom, do you have the same? Or is the device I have just defective.
It's a mostly an in call problem, where the phone screen goes blank and
(lets say you're in voicemail) you can't dial your password etc.
(The Screen won't come on even with the power button until 30 seconds after the call has ended.)
Your screen should come back on right when you take it away from your face. Do you perchance have a screen protector on it?
Sent from my VIPER DNA
I have the DNA and I am experiencing the same thing, but we probably have a little bit are a different scenario. Here are the details.
My digitizer broke so I bought a new LCD/digitizer assembly (LCD broke when trying to replace just the digitizer). Prior to it breaking I had CM 10.1 installed. When I replaced the screen I started experiencing the same issue described above. As soon as I place a call the screen goes blank and does not come back on until 10-20 seconds after a phone call. Regardless of formatting/wiping/etc. this has never gone away.
I installed Venom 1.3.1 to see if the ROM had anything to do with it and now, randomly, the sensor works. Also, even if the screen does shut off when press Send, I can press the power button to bring the screen back up (i.e. 5/10 phone calls the proximity sensor will work as it should. The other times the screen will go blank and pressing the power button will turn it back on.
I reinstalled CM 10.1 this afternoon to test a fresh install (I booted into recovery wiped factory data and formated SDcard then installed CM10.1) and the screen shuts off when I press send and stays off until the call is disconnected.
Is this a proximity sensor driver issue?
I have not tried using the phone after I returned back to stock flashing the RUU method.
Thanks for any feedback.
softBrikt said:
I have the DNA and I am experiencing the same thing, but we probably have a little bit are a different scenario. Here are the details.
My digitizer broke so I bought a new LCD/digitizer assembly (LCD broke when trying to replace just the digitizer). Prior to it breaking I had CM 10.1 installed. When I replaced the screen I started experiencing the same issue described above. As soon as I place a call the screen goes blank and does not come back on until 10-20 seconds after a phone call. Regardless of formatting/wiping/etc. this has never gone away.
I installed Venom 1.3.1 to see if the ROM had anything to do with it and now, randomly, the sensor works. Also, even if the screen does shut off when press Send, I can press the power button to bring the screen back up (i.e. 5/10 phone calls the proximity sensor will work as it should. The other times the screen will go blank and pressing the power button will turn it back on.
I reinstalled CM 10.1 this afternoon to test a fresh install (I booted into recovery wiped factory data and formated SDcard then installed CM10.1) and the screen shuts off when I press send and stays off until the call is disconnected.
Is this a proximity sensor driver issue?
I have not tried using the phone after I returned back to stock flashing the RUU method.
Thanks for any feedback.
Click to expand...
Click to collapse
i believe its controlled by the kernel.
reaverclan said:
i believe its controlled by the kernel.
Click to expand...
Click to collapse
I have never been very enthusiastic about flashing different Kernels (I haven't researched enough about them to know if I can flash any kernel with any ROM). I will research that and test accordingly. Thank you. I will report back here when I have reached a conclusion or with further questions.
you should be able to flash any aosp kernel on a aosp rom and sense ona sense cept for maybe sense 5 roms that im not to sure of.
reaverclan said:
you should be able to flash any aosp kernel on a aosp rom and sense ona sense cept for maybe sense 5 roms that im not to sure of.
Click to expand...
Click to collapse
I'll do some testing and see what happens. Thank you.
Guess I should have looked in the questions and answers section first. The app i reference in my second post here should fix it for the OP. Crank the top slider up to 100 and see if the 'far' or 'near' status changes when you put your finger over the sensor. If it does then adjust it to activate when an object is very close.
http://forum.xda-developers.com/showthread.php?p=43053376#post43053376
Sweet app used it to compensate for the thickness of the otterbox defender.
Sent from my VIPER DNA