This thread started off as a mod request because I thought it was my proximity sensor causing the issue. After further investigation I'm completely stumped as, disabling my proximity sensor didn't work (or the disable wasn't effective, not sure). Highly modified original post to make the thread relevant to the direction that its going.
Issue details - screen will not stay on while in call unless enabling speakerphone mode. After call initiates, screen promptly turns off. Pressing power key wakes the screen up but the second a finger is touched ANYWHERE on the screen it turns off again forcing one to wait for the call to disconnect itself or pull the battery to hard reset the device (whichever comes first). The issue seems to be somewhat inconsistent, as some calls I get more responsiveness out of the screen than others. It DOES seem to be software related as this issue is very, very specific. It only happens while a call is active. The screen and standby functions work 100% of the time otherwise.
Facts:
-issue was not present before obtaining s off and upgrading to ICS
-issue is present when doing a clean install of the Rom (energy, though I'm inclined to think its not Rom related for obvious reasons)
-issue persisted even when restoring an old back up of a gingerbread state from days prior to obtaining s off and flashing ics.
I know I'm not the only one experiencing this issue. I've spoken with several others who are having the same problem. Hoping an xda elite on here might be able to figure out what might be causing this to happen. Any help would be greatly appreciated.
----------------------------
(Original post) -
My proximity sensor is on the fritz and making it impossible to multitask anything while on a call (so much to the point where sometimes I can't even hang up and have to pull my battery). It's killing the screen the second I touch the screen anywhere while on a call.
Can someone tell me how to, or would someone even be able to put something together that'd allow me to disable my proximity sensor entirely? I don't really need it anyways since I can just manually hit standby before I hold my phone up to my ear. Any help anyone could provide would be greatly appreciated =)
Sent from my HTC_Amaze_4G using xda premium
Too tricky? No one? I know I'm not the only one encountering issues with their proximity sensor freaking out while on a call.
I guess ill just have to live with the inability to do anything on my phone while on a call unless I activate the speaker. Not the end of the world.
But if anyone can write a script/throw something together that'd turn it off you could save ne a lot of trouble and help others that are having this issue as well. Nbd ::shrugs::
Sent from my HTC_Amaze_4G using xda premium
would a piece of tape work? just tape it over the sensor.
No cuz then itd just stay off. The problem is that the screen won't stay on while in a call. If I touch the screen anywhere while on a call the screen shuts off immediately. =( very annoying. Can't even hang up sometimes.
Sent from my HTC_Amaze_4G using xda premium
Should work even though it's a different device, but haven't tried myself so no guarantees
How to/Solution to disable proximity sensor incall
Just a quick search found that
I tried to find the file in sys/class/optical-sensors/proximity .... But I didn't know which of the other files needed to be edited.
Wait....I sent this with Tapatalk?
Nativedude said:
Should work even though it's a different device, but haven't tried myself so no guarantees
How to/Solution to disable proximity sensor incall
Just a quick search found that
Click to expand...
Click to collapse
Totally worked. My proximity sensor seems to be off but oddly the screen still won't stay on while in call unless I have speakerphone enabled lol.
I figured it HAS to be related to the proximity sensor cuz the screen shuts off the instant my finger touches it... But apparently the problem is related to something else entirely. Thanks though =)
Just a slightly annoying glitch I can live with. Guess I'm gonna have to lol
Sent from my HTC_Amaze_4G using xda premium
AndroidAutobot said:
Totally worked. My proximity sensor seems to be off but oddly the screen still won't stay on while in call unless I have speakerphone enabled lol.
I figured it HAS to be related to the proximity sensor cuz the screen shuts off the instant my finger touches it... But apparently the problem is related to something else entirely. Thanks though =)
Just a slightly annoying glitch I can live with. Guess I'm gonna have to lol
Sent from my HTC_Amaze_4G using xda premium
Click to expand...
Click to collapse
Totally reflash your rom, leak, whatever.. that bug sounds like something didn't take fully on initial setup. Can't hurt to try. I say this because it sounds VERY similar to the problem I had with my Vibrant.. and many of the issues I keep reading people having make me think that the install methods aren't perfect and fool proof.
If you're on the leak you'd have to make a nandroid, but if on a rom that doesn't wipe data partition you can just wipe the system and reinstall- or worse case restore a nandroid of data partition.
Silentbtdeadly said:
Totally reflash your rom, leak, whatever.. that bug sounds like something didn't take fully on initial setup. Can't hurt to try. I say this because it sounds VERY similar to the problem I had with my Vibrant.. and many of the issues I keep reading people having make me think that the install methods aren't perfect and fool proof.
If you're on the leak you'd have to make a nandroid, but if on a rom that doesn't wipe data partition you can just wipe the system and reinstall- or worse case restore a nandroid of data partition.
Click to expand...
Click to collapse
Yeah. That was my first suspicion. Sadly it persisted even when I restored a backup of when I was running nrg's gingerbread Rom. Think it might be some kind of weird hardware failure since it persists no matter what I do (clean install from scratch with everything wiped/cleared).
Nit a huge deal. If j ever have to look something up while on a call all I gotta do is throw the speaker on which is normally do in that situation anyways he he. Just bothersome when there's an issue you haven't been able to fix no matter what you've tried ya know? =)
Sent from my HTC_Amaze_4G using xda premium
AndroidAutobot said:
No cuz then itd just stay off. The problem is that the screen won't stay on while in a call. If I touch the screen anywhere while on a call the screen shuts off immediately. =( very annoying. Can't even hang up sometimes.
Sent from my HTC_Amaze_4G using xda premium
Click to expand...
Click to collapse
I have the same issue, I thought it was just my phone. It's such an annoying issue, can't even hang up half the time. I love the phone but that one issue is really irking me. I never had this issue til I updated to ICS.
Sent from my HTC_Amaze_4G using xda premium
Headshots4life said:
I have the same issue, I thought it was just my phone. It's such an annoying issue, can't even hang up half the time. I love the phone but that one issue is really irking me. I never had this issue til I updated to ICS.
Sent from my HTC_Amaze_4G using xda premium
Click to expand...
Click to collapse
That's the really strange thing of it is that I never had the issue till I flashed ICS as well, but then the issue persisted when I restored an old gingerbread backup. Hopefully someone might see this that might have a better understanding and be able to figure out what's causing this to happen. =L. I'll change the subject of the thread to hopefully draw attention to it.
Question for you (let's compare) are you s off? And what Rom are you currently running? I'm inclined to think its not Rom related since the issue persists even when restoring a nandroid back up from days before I ever obtained s off and flashed ics. It'd be nice to confirm this is happening on Roms other than energy. Don't feel like going through all the steps to flash revolutionary or any of the other ics roms at this moment just to confirm what I already suspect.
Sent from my HTC_Amaze_4G using xda premium
Related
Hi all,
I am trying to figure out why my scanner is not operating. It was operating and suddenly stopped, wondering if it has to do with custom roms etc... I have tried to restore backups, factory reset phone, and tried recalibrating my prints. The scanner registers swipes when I have not touched it, and says swipe too short while trying to setup scanner password lockpad. so I want to know the software path in order to eliminate the possibly that its a software malfunction. I have read a few articles about the hardware being the issue but want to be sure its not something I may have mixed up.
Thanks in advance for any useful and/or helpful posts.
Sent from my MB860 using XDA App
Anyone?? Anything? Also after I reboot I swipe about 10-20 times before it registers one swipe, saying swipe too short.
Sent from my MB860 using XDA App
Or better yet will Motorola repair it if the bootloader is unlocked.
Sent from my MB860 using XDA App
been here before. I am not sure if the root cause is the scanner has gone buggy on you (hardware not software related) but what I ended up doing to fix it was getting a new fingerprint scanner and swapping them out ($20+20 min to do the swap - might take you a bit longer)
I originally it was from the power button being misaligned (if I opened it up and adjusted, it would work for a period of time).
the x factor here was that it could have just been misaligned with the cover as i bought a new one but did not end up actually using it.) so that could be a possible fix as well.
the alternative? send it in to moto and wait for them to repair. Should be covered under warranty but who knows, haven't heard stories about people sending in their devices with a hardware problem with an unlocked bootloader to moto.
Will my warranty cover it, I know it's been void by unlocking the bootloader, but the scanner doesn't seem to me a piece of hardware that is altered by rooting. I have talked to Motorola ( forgot to mention the bootloader )and they say it is covered by warranty and want me to fill out a ticket etc. And send in for repair
Sent from my MB860 using XDA App
Have you tried pulling the battery for a minute? Not just powering off, but actually pulling out the battery. It's known to fix some issues with FP scanner.
Robert Havens said:
Have you tried pulling the battery for a minute? Not just powering off, but actually pulling out the battery. It's known to fix some issues with FP scanner.
Click to expand...
Click to collapse
Just tried that. Booted back up and had 5 ghost swipes ( I didn't touch the scanner, but it said swipe too short and vibrated ). Also tried swiping after and no response. I'm leaning towards hardware malfunction.
Sent from my MB860 using XDA App
I feel something diffrent
I had finger print reader problem so offen ... I have to restart my phone all time...
But I notice that it many time happens after i come back from swimming and even i wash my hands and not dry it proparlly I always have problem with finger print sensor.... While I upgrade to new firmware... and Taking care about my wet fingers... i dont swip if my finger is wet...and I dont remember I ever had issue after that...
Please try wiping the sensor with isopropyl alcohol (rubbing alcohol).
Let it dry completely.
then test again.
Dave__C said:
Please try wiping the sensor with isopropyl alcohol (rubbing alcohol).
Let it dry completely.
then test again.
Click to expand...
Click to collapse
I will try that cause it is kinda oiled up, but that doesn't explain the ghost swipes.
Sent from my MB860 using XDA App
Are you stock our ruining a specific ROM?
Phoneguy589 said:
Are you stock our ruining a specific ROM?
Click to expand...
Click to collapse
I am on alien v4 with theme
Sent from my MB860 using XDA App
i have this exact same problem
I had some issues with Alien as well. I'm not sure if its from some of the debloat removed or what..but I installed Aura ROM with full Blur..and my fingerprint scanner has never worked better. It hasn't missed ONE swipe. On froyo I sometimes had to swipe twice to unlock..but this one is mint. Give it a try and then you at least know if its hardware it software. Just be sure to do a good clean wipe (fastboot) before install.
Rickroller said:
I had some issues with Alien as well. I'm not sure if its from some of the debloat removed or what..but I installed Aura ROM with full Blur..and my fingerprint scanner has never worked better. It hasn't missed ONE swipe. On froyo I sometimes had to swipe twice to unlock..but this one is mint. Give it a try and then you at least know if its hardware it software. Just be sure to do a good clean wipe (fastboot) before install.
Click to expand...
Click to collapse
Installed aura.. problems persisted.
Edit: any new ideas?
My overclocked alien atrix
My problem was not software related, Motorola has repaired my phone, the fps hardware was to blame. Solved.
Hi
I recently bought Amaze. Pretty awesome! I was all happy and clicking lots of pictures and stuff after which I decided to root because of the battery problem. Never mind that all good. But yesterday I randomly opened up the G-Sensor settings in display and I noticed some lag in the movements of those bubbles, I was confused and I knew this isn't how those bubbles move. I downloaded AndroSensor to check if everythings alright. But it wasn't I think there is some problem with my Accelerometer and Gyroscope :l those number besides the Accelerometer and Gyroscope keep on changing even if the phone is kept on the ground without any motion. If someone has experienced this or has a solution to it please help. I really don't want to ruin my experience with this phone.
Sent from my HTC_Amaze_4G using xda premium
Seriously no one? :O
Sent from my HTC_Amaze_4G using xda premium
I would just say get it exchanged man. I haven't had any issues along those lines and rooting shouldn't have any effect on those sensors =/
I also got probably a similar problem with the accelerometer. The phone began rotating the pictures as well as application windows absolutely wrong, unexpectedly and may say randomly.. and it isn't rooted yet..
P.S. I decided to go for the factory reset..
Now re-installing and re-setting all my operational environment
Anyhow the G sensor seems to resume its duly performance.. ))
jauhien said:
I also got probably a similar problem with the accelerometer. The phone began rotating the pictures as well as application windows absolutely wrong, unexpectedly and may say randomly.. and it isn't rooted yet..
P.S. I decided to go for the factory reset..
Now re-installing and re-setting all my operational environment
Anyhow the G sensor seems to resume its duly performance.. ))
Click to expand...
Click to collapse
Try and get AndroSenser from Market and let me know if the accelerometer values keep on changing even if the phone is kept on a surface with no movements.
Sent from my HTC_Amaze_4G using xda premium
Well my Amaze also has a prob with the g-sensor. it doesnt work at all there is no auto rotation , nothing. i have just had the phone for 2 days now. any solutions?
Try removing the battery and let sit for about a half hour. I had the same issue and this worked for me. Good luck.
the-other-gordo said:
Try removing the battery and let sit for about a half hour. I had the same issue and this worked for me. Good luck.
Click to expand...
Click to collapse
didnt work for me what should i do ? my other sensors are also not working
Got the same issue, at this point it doesn't work at all yet if I flash a rom with out a full wipe it'll work again until I restart. That being the case it feels like a driver issue to me... I'm not sure if anyone has a tool that will allow me to flash the proper drivers?
gunjan_25 said:
didnt work for me what should i do ? my other sensors are also not working
Click to expand...
Click to collapse
Call HTC as far as i know the phone hasnt even been out a year yet which means they should all still be under warranty. Htc sent me a new back, a battery and charger for things i made up so i could have back ups should anything go wrong. All sent for free and they dont even ask for the bad parts back. Their customer service is great. Unless you like messing with stuffvif a factory reset dosent fix it. Get a new one. & to the guy with the? About the accelerometer numbers they always dance around a little even when set down flat. As long as the phone rotates correctly and maybe get a game that uses it and az long as everything functions your good dont freak out because the numbers dont hold completely still.
My S3 is fully working. Only the issue is power goes off automatically some time later if it is not used and left.
Does anyone help me to fix this issue?
Galaxy S3 Turns Off (Fully Off) Overnight or When Unused
Having exactly the same problem.
When my Galaxy S3 is left for a while (more than half an hour or so it seems) I find it is not in idle mode, but has fully turned itself off.
The question is, whether this is due to a crash, or intentional (which would be a terrible feature if you wanted to receive a call overnight.)
Does anyone have any idea what could be causing it? - The first S3 I had developed screen issues and exhibited similar problems, turning itself off. But it turned out that one was faulty - the screen was corrupted after a while and it would not turn back on.
So, is there a feature we can turn off which does this that we can turn off? Or is it simply a flaw, and if so is there a way to trace it with say, logs or something else?
Any help gratefully appreciated.
No problems here. Running rooted stock rom and stock kernel. Maybe you've downloaded some faulty app thats screwing your phone.
Sent from my GT-I9300 using xda premium
Faulty Apps?
knuckle03 said:
No problems here. Running rooted stock rom and stock kernel. Maybe you've downloaded some faulty app thats screwing your phone.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Hmm... Perhaps, but if an app can cause your phone to shut off entirely without user input?... surely that's an O/S security issue
Well, I've seen a few other people with the same issue, I suppose I could try a factory reset and try for a few days without any extra apps. (Arg! The pain of no apps!)
Widgets could be a culpret I suppose. Still, turning off entirely? Seems a bit odd.
Anyone have any more ideas?
Experienced same thing when i was still new to android. Phone just reboot itself and sometimes it lights up itself with out touching it. Then i read somewhere that it could be some app causing it so i did a fresh start. Wiped up everything and install a stock rom thru odin. From then i always read user reviews and its permissions when downloading apps and when i find the permissions fishy il pass on it.
Sent from my GT-I9300 using xda premium
Hi,
I have a really strange problem, that I was unable to find among other people.
So, this is how it started:
I had some old official Froyo firmware with Voodoo lagfix and Voodoo Sound on it. One day I've noticed that it now takes like 5-10 seconds after you press a power button for screen to turn on. It started to annoy me and I decided to update to latest official firmware. After I did, the problem I mentioned disappeared. But somehow now I've got much bigger problem...
Anytime when i'm trying to make or accept a call phone freezes. Black screen and battery icon is all that is visible. However, call itself proceed and you can talk, but the only way to finish it is to remove battery (3G calls still works fine, btw)
I've tried all possible firmwares from oldest ones to ICS... tried all cleanup options from recover menu, stll nothing's changed.
I'll be very grateful if you guys can suggest me anything.
Thanks
Just a thought but make sure bluetooth is off, see if that helps
Read it on XDA a while ago.
Hope this helps
Taysider said:
Just a thought but make sure bluetooth is off, see if that helps
Read it on XDA a while ago.
Hope this helps
Click to expand...
Click to collapse
Thanks for advice, but bluetooth is disabled by default after firmware updates...
EvilJay said:
Thanks for advice, but bluetooth is disabled by default after firmware updates...
Click to expand...
Click to collapse
seems like an old thread but have you managed to solve it somehow? cuz im havin the same issue? and have you ever had it wet or some kind?
o-w-a said:
seems like an old thread but have you managed to solve it somehow? cuz im havin the same issue? and have you ever had it wet or some kind?
Click to expand...
Click to collapse
yep, it was water. not that I dropped it in there or something, but guys from service center told me that there was corroded track on circuit board. that's why proximity sensor wasn't working, so phone use to freeze each time OS tried to initialize the sensor
Sometimes when i press the power button on the side of my phone my phone will not fire up. I see the screen really vague. I need to press the button sometimes more them 10 times in order to get my phone working. It looks like the backlite is not working good. It is starting to piss me off.
Anyone else experiencing the same kind of problem?
No BackLite
rickxbox said:
Sometimes when i press the power button on the side of my phone my phone will not fire up. I see the screen really vague. I need to press the button sometimes more them 10 times in order to get my phone working. It looks like the backlite is not working good. It is starting to piss me off.
Anyone else experiencing the same kind of problem?
Click to expand...
Click to collapse
Hey,
Sorry to say I don't know the answer to your question, but there is one thing I'd like to share with you. Samsung OLED displays don't have backlite. So it can't be broken either. Good luck finding a solution!
Stock rom = sent it back
Flash stock, if still not working, triangle away, Send it back..
Sent from my GT-I9300 using xda premium
I can sent it back but i dont want to miss my phone for some weeks if i can fix it myself. Then i have to go back to my S1
So you want a defective phone? Even if you fix it, you still have a defective phone. Get it sent back to the store or Samsung.. Surely you can live without it for the benefit of the time it comes to sell the device.
Sent from my GT-I9300 using xda premium
Are you sure you are on the most current official ROM? (This would be, starting today, Jellybean in a few countries)
Some old offical ROM's sometimes had the issue and it was annodying as hell. I have not seen it since switching to leaked Jellybean builds.
As the previous poster already said; there is no backlight so you should not be able to see anything. Maybe your eyes are playing tticks on you or you got some app such as ScreenFilter to act up.