Is there anyone else having the same issue as I have? My Nexus S screen would turn off during/after a call, sometimes it would turn on when i press the power button and sometimes it would not. I am on stock Android 2.3.4 baseband I9020AUCKD1 Kerne version 2.6.36.7-ge382d80 android-build2apa28 #1 Build number GRJ22. I just got the OTA update the other day. Is this some kind of bug that comes with the update? I hope someone could shed a light on this matter. BTW I am on At&t if that helps. Thanks in advance!
Have den same problem in my phone to
Android 2.3.4
i9023
The screen turn's off when i answer a phone call.
I think it turns off when your in a call so that you don't touch the screen, it can detect you proximity , try on the middle of a call take the phone from your ear the screen should turn on.
Sent from my Nexus S using XDA App
I have the same problem... sometimes the display stays black after the call is finished. Then I have to press the power-button.
Rom: MIUI-1.8.19
Kernel: Netachy-1.3.7
I don't have a solution for this problem, but it certainly annoys me too.
It seems that the screen lock timer is still running while the call is in progress. You can verify this by trying to hit the home screen in the middle of the call and seeing the lock screen come up.
I also have this problem and can be very annoying.
This also happens sometimes when I am watching flash video content. As soon as the video finishes the display turns off. The person who said something about the idle timer continuing to count idle time sounds plausible. As soon as the app that was preventing the sleep/lock ends it sleeps immediately.
Sent from my Nexus S using Tapatalk
I think its the in pocket detection... does anyone how to update my kernel from 2.6.35.7 to 2.6.36.7?im not sure how to do?
I think you should just wait, as its going to be March real soon and we should start to see updates for the Nexus S and 4g coming up. If you really can't wait, go ahead .
mclee235 said:
I think its the in pocket detection... does anyone how to update my kernel from 2.6.35.7 to 2.6.36.7?im not sure how to do?
Click to expand...
Click to collapse
Are you rooted? Are you on a customer ROM?
If I'm not wrong, you can only update your unrooted stock ROM when you get an official update. (Somebody more experienced please confirm this)
However, once rooted and with a custom ICS ROM there is a whole list of Kernels that can be flashed and each one has the instructions on their respective pages.
dino993 said:
I think it turns off when your in a call so that you don't touch the screen, it can detect you proximity , try on the middle of a call take the phone from your ear the screen should turn on.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
you are correct
is that possible:
1. proximity sensor during the call in order to avoid your face accidentally touched the screen
2. over time to lockscreen , like 1 minute , but you spoke 2 minutes ... and then phone automatically screen off ?
I exprienced that sometime in stock GB ROM and custom GB ROM. I have yet to experience it in ICS so far. It could be that when you try to wake the screen up, the phone may actually try to wake up but at that time your phone call may take higher priority -- cpu wise, so it is busy processing your phone call instead. I'm thinking Windows processing priority and I'm a noob.. Or the proximity sensor processing got stuck.
This does actually happen sometimes on my 2.3.6 stock ROM (i9023). Never had problems with turning the screen back on afterwards, though.
Related
Hi,
I have this wierd problem with my sensation. I found out that if i have my camera on and it falls a sleep it wont unlock any more. no ring nothing.buttons glow but a solid black screen. The only way out is a battery pull.
It's with photo camera and video camera mode. no other apps suffer fom this.
I've tried other roms but nothing. I currently run ARHD 3.6.7
I found out on accident but it is realy annoying me now
Any of u with the same problem or ideas?
known issue with kernel. not sure which kernels. try keepscreen app to keep screen awake if using camera so it doesnt freeze
https://market.android.com/details?id=com.tni.KeepScreenLite&hl=en
Yeah, it's bricked kernel. Doesn't matter what version you use, it seems to keep on happening randomly.
knuddeknurft said:
Hi,
I have this wierd problem with my sensation. I found out that if i have my camera on and it falls a sleep it wont unlock any more. no ring nothing.buttons glow but a solid black screen. The only way out is a battery pull.
It's with photo camera and video camera mode. no other apps suffer fom this.
I've tried other roms but nothing. I currently run ARHD 3.6.7
I found out on accident but it is realy annoying me now
Any of u with the same problem or ideas?
Click to expand...
Click to collapse
Hi,
Go into Bricked Kernel post, there is a .zip file called, CAM-FIX.zip
Flash that, magic will happen =]
Thanks guys, I've all ready flashed an other kernel and it works all fine now.
CAM-FIX.zip on the other hand is only for sense 3.5 and I really prefer sense 3.0
The camfix patch is so the camera can even function in the first place, it does not fix this issue. Without the camfix, if you try to use the camera the screen just goes black and the phone freezes. This issue however is an intermittent one, where sometimes when you exit the camera you get the black screen and freeze. Doesn't happen all the time, but it's definitely the kernel at fault.
To the OP, if in your case it's only happening once the screen times out, you could always use tasker to make it not timeout when using that app?
StuartTheFish said:
The camfix patch is so the camera can even function in the first place, it does not fix this issue. Without the camfix, if you try to use the camera the screen just goes black and the phone freezes. This issue however is an intermittent one, where sometimes when you exit the camera you get the black screen and freeze. Doesn't happen all the time, but it's definitely the kernel at fault.
To the OP, if in your case it's only happening once the screen times out, you could always use tasker to make it not timeout when using that app?
Click to expand...
Click to collapse
You can try keep screen, it will keep phone up when camera is on
Sent from my HTC Sensation XE with Beats Audio using XDA App
Hi,
I just saw today, that there was a very weak red light just next to the proximity and light sensor. It looked like it was flickering at a very high rate!
I tried to restart the phone normally, but the light didn't disappear. After that I tried a reset by holding the power button down for 10 seconds. That made it vanish.
What the f**k was that all about???
Best regards
Casper
If you were making a phone call, the red flashing light is normal It's the proximity sensor. If you were doing nothing, it should not be seen the red light, might be faulty.
Sent from my HTC One S using XDA
Moved To Q&A
This is best in the Q&A section, as it been written as a question.
h.han said:
If you were making a phone call, the red flashing light is normal It's the proximity sensor. If you were doing nothing, it should not be seen the red light, might be faulty.
Sent from my HTC One S using XDA
Click to expand...
Click to collapse
Its The Goverment Spyin On us...Making Sure We Dont Flash Anything Or Even Root...If So It Will Say Tampered And The S.W.A.T. Team Will Come Crashin in Our Homes...
That red light is in fact the actual proximity sensor and it's in use while in a call. If you where not in a call then that was a strange occurance unless you ran some of these sensor testing apps...
Well, I wasn't in a call. I had been calling someone through the hands-free in my car on my way to work, where I discovered it about 10-15 minutes after the call was finished...
cawith said:
Well, I wasn't in a call. I had been calling someone through the hands-free in my car on my way to work, where I discovered it about 10-15 minutes after the call was finished...
Click to expand...
Click to collapse
That was an odd one... maybe it was a temporary fluke? Strnag nonetheless...
I often use face unlock. The red light turns on when the front cam turns on.
Sent from my HTC VLE_U using XDA
any tips on how to trouble shoot this? I wish I could figure out which app (if any) is causing the proximity sensor to stay lit.
I've heard it's related to an autobrightness tweak, but it appears even when tweak is not applied, across multiple roms. The only commonality between my roms is the apps I have installed.
I've tried multiple proximity sensor testing apps and, it's working.. it's just always lit up.
decalex said:
any tips on how to trouble shoot this? I wish I could figure out which app (if any) is causing the proximity sensor to stay lit.
I've heard it's related to an autobrightness tweak, but it appears even when tweak is not applied, across multiple roms. The only commonality between my roms is the apps I have installed.
I've tried multiple proximity sensor testing apps and, it's working.. it's just always lit up.
Click to expand...
Click to collapse
Same here. Have to restart to get it off again. Any help? (TrickDroid 4.3)
Anytime you make a call by any means other than handset to your ear, the proximity sensor will come on and stay lit until reboot or until you make another call via handset.
Example:
Place call> turn on speaker phone> hang up - proximity sensor will stay lit after call;
To fix do this:
Place call from handset (not using speaker phone or hands free) and hang up right away, or reboot device and light will go out.
Same seems to go for calls through hands free as well.
These guys are lying its a bomb isn't it obvious flashing red light HTC controls it if u do something they don't want u to do boom ur hands are no more why do u think the phone heats up so much its a warning don't believe me read the thread in forums about heats in the one s another reason they don't want us to remove back well see the bomb :what:
Sent from my HTC One S using xda premium
Hi All,
My One S also does this. I'm finding it a pain to have to make a call after using speakerphone to turn the proximity sensor off again. Has anyone found out what the cause of this is?
I've tried clearing cache partition with HTC support but still no fix.
Hi all, I forgot to mention that the issue on my phone only happens when the call is ended with speakerphone active. If I turn off the speakerphone before ending the call it does not happen.
Hey brothers.. I had the same problem with the proximity sensor not turning off.. Even after so many restarts resets... Finally I just opened the original task manager of the one x, and push "stop all" .. and YES!! the sensor was turned of and stopped lighting.. After that I tried calls with speaker phone or not.. No problem.. Now it is working how it has to...
Sv3TL10 said:
Hey brothers.. I had the same problem with the proximity sensor not turning off.. Even after so many restarts resets... Finally I just opened the original task manager of the one x, and push "stop all" .. and YES!! the sensor was turned of and stopped lighting.. After that I tried calls with speaker phone or not.. No problem.. Now it is working how it has to...
Click to expand...
Click to collapse
You maybe have turned off Viber doing this: http://www.boards.ie/vbulletin/showthread.php?p=80972874
Does it come back after restarting Viber?
Sometimes a restart fixes the problem.
I had the same problem. I uninstaled Viber and the light disipired.
foner81 said:
You maybe have turned off Viber doing this:
Does it come back after restarting Viber?
Click to expand...
Click to collapse
Later I realized that Viber is the reason. Yes. But now it seems that Viber is fixed after last update, and no red light when viber is turned on
Was anyone experiencing the display randomly turning on & won't dim itself off. I am using the fingerprint lock so it stays on the screen asking for the alternate password. This happens while charging & when idle. The phone stays on until you press the power button. I am testing if is something to do with the fingerprint lock, switching to pattern lock. any ideas?
I also use fingerprint unlock and have noticed that the display will randomly turn on and ask for the alternative password. I just got the phone this past Sunday (6/8) and all I've really done to it is add the fingerprint security.
what ROM are you running?
youdoofus said:
what ROM are you running?
Click to expand...
Click to collapse
Stock ROM, no changes.
I've also seen this. Usually happens to me at night for some reason. Screen turns on and when I hit the side button to turn off the screen it goes out for a few seconds then lights up again. Have to reboot to fix it.
Mine does it during the day at work quite a bit, I think it is from the home button being pushed in my pocket. It really should be associated with the light/proximity sensor as to when the button will work.
Having the same problem with both swipe and fingerprint unlock. I can understand swipe, fingerprint works better in my pocket then with my finger
Mine is constantly turning on in my pocket now. I have an otterbox commuter on it and edges are raised pretty good, doesn't seem like my leg would hit the home button but it's hard to tell
Only happens to me when connectivity state changes, or music skips for a notification
Sent from my SM-G900P using Tapatalk
I am having this problem on stock unrooted ND2 as well as RDDT. I also noticed on both that I get notification sounds with NO notifications showing up. So I have my notification sound going off a few times each hour for no reason unless I leave my phone on silent.
As far as the screen coming on randomly, I found that disabling air wake has helped a little bit. Especially overnight, I leave my phone next to my pillow (yea, I am a junkie...) and the screen would turn itself on every time I rolled over, and the screen would stay on after that until I woke up and turned it off. I know it was staying on because a couple of times I reached over the phone, screen turned on and I watched it for about 5 minutes (screen time out is set to 15 seconds) and it didn't shut off.
TL;DR Turn off air wake - Need help figuring out phantom notifications (still exist after multiple factory resets and almost no apps installed)
My issue stopped once I installed a glass screen saver. Home button is now countersunk with the 0.33 mm. Cover & review.
http://www.amazon.com/Tech-Armor-Samsung-Ballistic-Protector/dp/B00IGISUTG/ref=cm_cr_pr_product_top
http://www.amazon.com/Tech-Armor-Sa...tBy=bySubmissionDateDescending#R1R8876D8WLXE3
I installed the same one, lol. It still does it, not as often though
I was using standard pattern lock screen on stock rooted and had this issue. It was the wave to wakeup feature that was causing it. I turned it off and it went away. 3 days with no waking by itself.
I've never had that turned on.
looks like you guys turn on air wake and it's working sensetively. on the contrary, mine is numb
yueyejinghun said:
looks like you guys turn on air wake and it's working sensetively. on the contrary, mine is numb
Click to expand...
Click to collapse
It was numb for me too when it wasn't being awakened by ghosts. The other guy said he didn't have that feature on so not sure what the other issue(s) is/are.
GorillaPimp said:
It was numb for me too when it wasn't being awakened by ghosts. The other guy said he didn't have that feature on so not sure what the other issue(s) is/are.
Click to expand...
Click to collapse
air wake is a nice feature to extend the lives of home & power button, except it always makes me look like an idiot when I am waving my palm over the phone again and again.
I tried to set the mode to unlock by fingerprint and keep air wake on for a whole day, but I didn't encounter that problem. maybe it just affects some devices, maybe it's not air wake.
Anybody found a real solution for this inconvenient?!
This only happens at Lollipop... 2 months ago I updated and because this annoying issue that was draining my battery I downgraded to Kit Kat...
Last weekend I decided to give another shot to Lollipop, but the issue remains...
I tried all settings relative to screen and lock screen and nothing worked!
andreluigo said:
Anybody found a real solution for this inconvenient?!
This only happens at Lollipop... 2 months ago I updated and because this annoying issue that was draining my battery I downgraded to Kit Kat...
Last weekend I decided to give another shot to Lollipop, but the issue remains...
I tried all settings relative to screen and lock screen and nothing worked!
Click to expand...
Click to collapse
I have the same problem. My battery has been life does not even last me until the end of work. Trying a fix now that I just thought of though. This problem is incredibly frustrating at night too.
I believe its the connection optimizer. Go to Settings > More networks > Mobile networks > Connections optimizer:
Then Uncheck "Connections Optimizer"
Seems to be working so far! So hopefully this helps the rest of you!
This Fix did not work still perplexed by this problem.
After rooting and removing a lot of bloat, I got rid of it. I have no idea which app it is though. Maybe an xposed module logging screen wakes could be of assistance. But I too noticed it immediately after flashing a lollipop ROM.
I have tried every single ROM on this Forum for Moto G 2015 Osprey 1GB version. However I am having same issue on evry ROM . Often I recieve a call my screen goes blank and I am not able to answer the call . Also when dialling out my screen goes blank after pressing dial . As a result I am not able to put teh call to loud speaker or use any other in call options . Can some please help me how to fix the issue . (I know work around to use Power Button to end calls and Volume to answer calls however that doe snot suite me as I ended up answering few calls which i did not wanted while mobiel in my pocket ).
Things I have done so far
I have tried this with both a screen protectoron and now have taken screen protector off . Issue still there
I have a a backup of orignal Motoroal ROM and this issue does not happen on orignal ROM
I have installed Nano gapps to make sure I have unough RAM free issue still there
I have tried most of the ROM 7.1.1 and even 6.0.1 all ROMS including Cynogen mod+ Lineage 13 and 14, ressurection remix, AOPS . Experience, Slim, AOKP, Cosmic , AOSP extended and list goes on and on but issue is still; there
Is there any specific reason for this issue ?
Is this to do with RAM, Sensor or custom ROMS issue ?
Is teher any way to turn teh sensor off which turn screen off whiel in a call and when i take mobile near my face (I am thinking if sensor incorrectly so wanst to check if turning thsi off makes any difference )
Can anyone please help
So your proximity sensor is acting up... are you on current baseband and firmware? I would suggest flashing the latest factory image completely via fastboot, verify operation of the proximity sensor, then flash your ROM again. A backup and restore in TWRP of stock is not sufficient to update firmware.
acejavelin said:
So your proximity sensor is acting up... are you on current baseband and firmware? I would suggest flashing the latest factory image completely via fastboot, verify operation of the proximity sensor, then flash your ROM again. A backup and restore in TWRP of stock is not sufficient to update firmware.
Click to expand...
Click to collapse
Thanks acejavelin you are always helpfull. I know how to flash Stock Formware however How can I verify operation of the proximity sensor?
I have found a copy of orignal firmware under XDA thread however I am not sure whether it is up to date firmware or not . How can I confirm if this is up to date firmware ?
https://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639
Retail UK (1GB) - XT1541_OSPREY_RETGB_6.0.1_MPI24.107-55-2_cid7
Can you please help on this bit
chungomungo1 said:
Thanks acejavelin you are always helpfull. I know how to flash Stock Formware however How can I verify operation of the proximity sensor?
I have found a copy of orignal firmware under XDA thread however I am not sure whether it is up to date firmware or not . How can I confirm if this is up to date firmware ?
https://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639
Retail UK (1GB) - XT1541_OSPREY_RETGB_6.0.1_MPI24.107-55-2_cid7
Can you please help on this bit
Click to expand...
Click to collapse
Just take the newest one there... Best you can do.
As far as testing the proximity sensor, make some calls and have someone call you... You can try a sensor tester app like https://play.google.com/store/apps/details?id=com.mtorres.phonetester too
Brilliant , Thanks alot . will try that
FACING EXACTLY SAME PROBLEM ON XT1550
I have a common problem in all ROMs I'm installing . whenever I answer a call or dial a call my screen goes off as if proximity sensor is activated and doesn't turn on even when I take it away from my ear or press my power button. Screen doesn't turn on at all during call.
Phone remains fine for a day or two after I wipe cache etc from recovery but again the problem starts. This happens in all custom roms and also in rooted stock ROM. My device is XT 1055.
Kindly suggest any solution as it causes lot of inconvenience.
abhishekturumella said:
FACING EXACTLY SAME PROBLEM ON XT1550
I have a common problem in all ROMs I'm installing . whenever I answer a call or dial a call my screen goes off as if proximity sensor is activated and doesn't turn on even when I take it away from my ear or press my power button. Screen doesn't turn on at all during call.
Phone remains fine for a day or two after I wipe cache etc from recovery but again the problem starts. This happens in all custom roms and also in rooted stock ROM. My device is XT 1055.
Kindly suggest any solution as it causes lot of inconvenience.
Click to expand...
Click to collapse
There is only one fix. find where is proximity sensor, usually it is on the top near front camera . when ever screen goes blank dry your thumb and clean screen with teh thumb where proximity sensor and screen will wake up .
Also you need to keep you pockets extra clean. It is better if you can hoover inside them as most of the time I noticed there was a little dirt always on my screen when screen went blank. I am noit sure if my mobiel screen has gone very catchy to dirt after 1 year use
I intially though iut was due to custom ROMS and I have gone back to stock ROM and recieved two motorola security updated still issue is there so this is not because of the ROM .
Try this
Goto settings and search default from the search button then select phone app and set the default app.
Just saw this and thought I'd try Phone Tester. covered or uncovered, my proximity det always said Far. I tested phone by making a call and then covering it and the screen immediately went black. I would suggest that some screen protectors might interfere a bit but you've already taken that into account. Note where it is (on my xt1540 top just right of ear speaker) and make sure surface is clean. Otherwise just may be defective.
EDIT: if you feel it's "defective" You might consider replacing the screen/digitizer in hopes that that would fix it and it's not a motherboard issue.
Facing same issue
My stock rom on moto G3 2015 was working fine. Yesterday i rooted and installed tesla when this issue started. Frustrated i tried ASOP Extended and here too same issue.
It's not the issue of the sensor since Stock rom was fine till 2 days ago.
Have tried Phone notificaion settings as well.
Any updates on this or else i may have to reinstall Stock ROM
Hello All.
Anybody else have the same issue like me?
I have around 4 seconds lag during wake-up phone with double-tap. But only when phone goes to sleep with camera application opened in front.
This is strange.
If camera app is opened in front and phone goes to sleep - long wake-up with double-tap.
With power button wake-up -> phone wake-up immediately.
If phone goes to sleep with any other application opened in front (home screen, any other app) -> double-tap wake up phone immediately.
I have this issue on few last nougat versions. Today I applied Oreo update and still the same issue.
In safe-mode still the same. I have opened service ticket to HTC but I would like to know if anybody else see the same issue?
I have this issue on few last nougat versions. Today I applied Oreo update and still the same issue.
In safe-mode still the same. I have opened service ticket to HTC but I would like to know if anybody else see the same issue?[/QUOTE]
Just tried mine and seems to work fine on double tap
Hello all. Sorry for long reply time. I still have this issue. Please see attached video.
https://www.dropbox.com/s/pnawcdlo4vbvu2l/U11_DoubleTap.MOV?dl=0
see around sec. 00:22 Only DoubleTap when camera application is on top generate this issue. Other combinations wake up phone quick.
nedalnib said:
Hello all. Sorry for long reply time. I still have this issue. Please see attached video.
https://www.dropbox.com/s/pnawcdlo4vbvu2l/U11_DoubleTap.MOV?dl=0
see around sec. 00:22 Only DoubleTap when camera application is on top generate this issue. Other combinations wake up phone quick.
Click to expand...
Click to collapse
Now that I have watched the video,, mine acts the same.
That's a "normal" behavior, on android when the screen brightness needs to change this lag always appear. I develop an app to turn screen off by changing the brightness and timeout times, and happens this same lag in a various devices seems to be an android issue.
So what I did to "hde" the lag was to add a screen with some info like day, date and time.
But on your case there is no solution yet.
Strange. So, why waking up phone with fingerprint scanner or power button wakes it very quick?
Why this "issue" can be seen only when camera app is on top? [if other app is on top phone wake up every time very quick]?
This looks for me like issue in HTC software. Not "standard android behaviour"
nedalnib said:
Strange. So, why waking up phone with fingerprint scanner or power button wakes it very quick?
Why this "issue" can be seen only when camera app is on top? [if other app is on top phone wake up every time very quick]?
This looks for me like issue in HTC software. Not "standard android behaviour"
Click to expand...
Click to collapse
Because camera change the screen brightness, the problem is in changing screen brightness and not the action that you are performing.
ok, this explains question 2. But what about question 1 : "why waking up phone with fingerprint scanner or power button wakes it very quick?" ???
nedalnib said:
ok, this explains question 2. But what about question 1 : "why waking up phone with fingerprint scanner or power button wakes it very quick?" ???
Click to expand...
Click to collapse
That one I don't know for sure, but I think that can be due to the way the it turn the device.
Double tap is controlled by "lockscreen app/kernel", the power button and fingerprint it android native code and kernel, can be that but just htc knows!
Did you tried to ask then about that in twitter or via support emaill?
I just made additional test: manual brightness, full level. The same phone behaviour.
In my opinion this is something in kernel / wake-up procedure. I raised support ticket to HTC.
nedalnib said:
I just made additional test: manual brightness, full level. The same phone behaviour.
In my opinion this is something in kernel / wake-up procedure. I raised support ticket to HTC.
Click to expand...
Click to collapse
Hum, nice ideia.
Ok, let us know what they answer