Develop Bugs

[TESTING]LCD panel improvements

Hey ho fellas ,
I was working on adding power management + initialisation/de-initialisation sequence for rhodium´s lcd panel. Till now rhodium´s panel was always on ( initialised ) in deep-sleep aswell those meaning that the display was never de-initialised and was consuming more battery then normal.
I would like that all of you users that are willing to help to test the kernel ( zImage+modules + latest commits included ) and give some feedback.
Test the power on/off sequence, leave it sleeping for ~30mins and unlock it,...then give me here some feedback on your lcd panel behaviour.
zImage + modules ( mediafire or attachment ):
http://www.mediafire.com/?ny18wpc3z8utxrf
Prerequisites:
- Backup your data.img if you have some valuable data on it ( anyway it should not affect it )
- Delete pm_sleep cmd from your startup.txt

What do you mean by this?
Till now rhodium´s panel was always on ( initialised ) in deep-sleep aswell those meaning that the display was never de-initialised and was consuming more battery then normal.
Click to expand...
Click to collapse
Do you mean that although the display is off, the panel is still on? Or am I getting this the wrong way? If you could explain this to me then I am willing to test

Lennyz1988 said:
What do you mean by this?
Do you mean that although the display is off, the panel is still on? Or am I getting this the wrong way? If you could explain this to me then I am willing to test
Click to expand...
Click to collapse
yeah im curious as well because the only time the lcd is on even when the screen should be sleeping is when its in autobacklight in wm.

lilchicano said:
yeah im curious as well because the only time the lcd is on even when the screen should be sleeping is when its in autobacklight in wm.
Click to expand...
Click to collapse
I think that even though it looks like the screen is turned off it still draws power, so this should eliminate that issue allowing better battery life

Yea the way it was explained to me (by the OP on IRC) is that you can't really tell necessairly that the panel isn't being properly de-initialized... I questioned that at first as well.
I played with the new zImage, seems pretty smooth. Had a few hiccups on wakeup, but nothing crazy. Test it out guys, let the OP know how it worked!!

uub11 said:
I think that even though it looks like the screen is turned off it still draws power, so this should eliminate that issue allowing better battery life
Click to expand...
Click to collapse
Yeah, its a little bit hard to explain, but its like you said.
arrrghhh said:
Yea the way it was explained to me (by the OP on IRC) is that you can't really tell necessairly that the panel isn't being properly de-initialized... I questioned that at first as well.
I played with the new zImage, seems pretty smooth. Had a few hiccups on wakeup, but nothing crazy. Test it out guys, let the OP know how it worked!!
Click to expand...
Click to collapse
Yeah, test it out and post your feedback

ReWind402 said:
Yeah, its a little bit hard to explain, but its like you said.
Yeah, test it out and post your feedback
Click to expand...
Click to collapse
I'm at work and can't download off mediafire can anyone either upload here or on rapidshare.

uub11 said:
I'm at work and can't download off mediafire can anyone either upload here or on rapidshare.
Click to expand...
Click to collapse
I uploaded it here on xda, check the 1st post.

uub11 said:
I'm at work and can't download off mediafire can anyone either upload here or on rapidshare.
Click to expand...
Click to collapse
Ha, responded a little late. I removed it...

Does it matter for the testing if you use pm sleep 2 or 1? Just curious. Testing now

Lennyz1988 said:
Does it matter for the testing if you use pm sleep 2 or 1? Just curious. Testing now
Click to expand...
Click to collapse
It would better that pm_sleep has the default value.

Will give this a try as I go about my day today. I don't OC and use pm_sleep=1 yet still get terrible battery life (b/c I'm a power-user, on e-mail constantly). Any positive change will be wonderful We'll see how it goes.

My findings:
- Device does not go into standby, but I used sleep 2, maybe that is the cause.
- The Led keeps blinkin red. (never seen that before on android)
- The device reboots itself.
and a really negative effect is that I lost all my settings... My launcher pro settings, setcpu, whatsapp...

Hi,
As far as i understood there is no way to know exactly is display in standby mode or not?
I did some tests for now with light sensor ON and OFF (in WM) so here we go (PM is set to 2).
With sensor turned ON in WM:
After going standby screen gone completely off, no glow from backlight in dark environment like it was in previeous kernels and here is an answer to my guess above, screen IS truly going into standby. Also I've noticed some strange behaviour, the debugging led which was intended to go green in standby, randomly (i guess) flashes in around 2 Hz frequency with amber and then stays for 3-4 secs and cycleing like this, no green at all. Returning from standby is not OK, after pressing end button screen is not turning on as expected BUT, after touching at the place where unlock or mute sliders should be screen wakes, so i can assume that after pressing end button screen is just not turning on but touch panel does. Wake on call works as before, as like as wake from HWkeyboard slide (both with 2-3 sec delay). Shutdown actually turn the phone OFF.
It seems With sensor turned OFF in WM, phone acts same way.
I was testing with Matthew's RAR - Android v2.2 Froyo: BLAZN from Aug 30, 2010

Lennyz1988 said:
My findings:
- Device does not go into standby, but I used sleep 2, maybe that is the cause.
- The Led keeps blinkin red. (never seen that before on android)
- The device reboots itself.
and a really negative effect is that I lost all my settings... My launcher pro settings, setcpu, whatsapp...
Click to expand...
Click to collapse
1. Try deleting pm_sleep from your startup.txt ( then the default value will be used - i recommend that ) or put 1
2. never seen that on android
Anyway i am really sry for the inconvenience regarding launcer pro, kernel change should not affect those kind of settings :s
solevi said:
Hi,
As far as i understood there is no way to know exactly is display in standby mode or not?
I did some tests for now with light sensor ON and OFF (in WM) so here we go (PM is set to 2).
With sensor turned ON in WM:
After going standby screen gone completely off, no glow from backlight in dark environment like it was in previeous kernels and here is an answer to my guess above, screen IS truly going into standby. Also I've noticed some strange behaviour, the debugging led which was intended to go green in standby, randomly (i guess) flashes in around 2 Hz frequency with amber and then stays for 3-4 secs and cycleing like this, no green at all. Returning from standby is not OK, after pressing end button screen is not turning on as expected BUT, after touching at the place where unlock or mute sliders should be screen wakes, so i can assume that after pressing end button screen is just not turning on but touch panel does. Wake on call works as before, as like as wake from HWkeyboard slide (both with 2-3 sec delay). Shutdown actually turn the phone OFF.
It seems With sensor turned OFF in WM, phone acts same way.
I was testing with Matthew's RAR - Android v2.2 Froyo: BLAZN from Aug 30, 2010
Click to expand...
Click to collapse
Yeah its a common problem for now we are investigating this.
So i have a confirmation that the screen is really powered off?
Anyway guys try putting 1 into pm_sleep or deleting it from startup.txt (i recommend the 2nd choice ).

I ran into an interesting problem however I did not see the previous post...
Several time it went into standby (I assume) and the screen was pitch black meaning the backlight was not on. To get it out of standby, I woul click the end button like normal. after a couple of hours I pulled the phone out of my holdster, and it was abnormally hot. I do not have an overclock and my pm sleep is set to 1. I did not press the screen to see if it would respond so maybe that is what was being mentioned in the last post. None of the buttons would bring it back to life and the LED was amber and solid, where typically it would flash with this new zimage and modules. I will try to get it back to that state and see if I can click the screen even though it is dark. One thing that worries me is the battery though. Could this be damaging to it? Even when I did have it overclocked it never reached that temperature.
Anything else I can do to help troubleshoot?
EDIT: Sorry, forgot to mention I am on a Sprint RHOD400

I'm on the RHOD400 model, no OC, pm_sleep=1
Couldn't really get it to be stable, had to switch back to WinMo for the day (and trust me, that's desperation ). Once restarted in my pocket without any interaction on my part. I would press the end key to turn on screen, and had it auto reboot at that point as well. Also got a "sleep of death" twice and had to restart. While in your kernel I didn't have notification LEDs as well (not even for power events), vs the guy above that had blinking red.
I'm sure you'll get it eventually, keep up the hard work!

Hi!
Any news? Are we gonna wait for new kernel with committed code or it development is stalled?

screen wont come back on during call

my wife has the att nitro hd, when the screen goes off during a call sometimes nothing including power button will turn it back on. Anyone know of a fix? did the ATT small update fix this?
Actually it comes back on after a long minute or two. Not very helpful if you need the dialpad or keys, etc.
I have just rooted it for her and installed CWM.
I have added a few proximity tweaks to build.prop
gsm.proximity.enable=false (rebooted twice but screen still goes off)
also used the ro.lg.proximity and the mot.lge.proximity (dont recall exact wording) both were set to a value of 5.
I'll have to take alook into the lg hidden dialer menu to see if I can disable this.
I dont like this sensor on my device either, but I have an option in settings to disable it, which makes it bearable.
thanks for the help guys.
I have noticied LG throws together some junky builds, typos, bad english/grammar. Wonky sensors etc. Incorrect kernel build ReadMe's
I thought I recall someone with another device just placing a peice of tape over the sensor. hmmm..worth a try.
cheers.

chrisrotolo said:
gsm.proximity.enable=false (rebooted twice but screen still goes off)
also used the ro.lg.proximity and the mot.lge.proximity (dont recall exact wording) both were set to a value of 5.
Click to expand...
Click to collapse
Congrats. Today, you learned that most of the "tweaks" found at XDA are utter bull****

aremcee said:
Congrats. Today, you learned that most of the "tweaks" found at XDA are utter bull****
Click to expand...
Click to collapse
What about the tweaks that aren't BS? Are they already included in your CM9 builds?

From what I can tell, pretty much the main thing that build.prop is good for is providing information about the system and software (i.e. info about the build). It's not really used much for useful configurations as far as I know.

networks tweaks actually have doubled me download speed.
I still have faith.
but can anyone answer my questions I posted in ICS SLim thread and PM'ed Andasa , no responses yet.
does ICS slim or CM9 have option to keep lcd no during call? and does it work??
what's working not working? I found changelogs but not a working/not working list for CM9.
and has anyone successfully restored a nandroid from ICS to GB without real issues?
thanks guys.

i doubt the ota fixed your issue as the issue is not one that occurs for every nitro.
I can tell you that when I make a phone call they screen stays no.
what's working not working, well, many of us are running it daily with no probs.
as you prolly know, it is a nightly build so a public list of what's working or not isn't rly part of the deal.
i've succesfully restore a nandroid from both slim and cm9 back to the stock att rom and others many many times. dozens.

thanks good enough.
I will have to give it a go.
would you recommend one or the other?
CM9 or slim?
thank you.

well, I like them both a lot. slim is just a trimmed down version of cm9 and i _think_ it does run just a bit snappier........maybe..but it's not wildly different from cm9. I usually switch back&forth throughout the day.

There's no setting in CM9 to disable the proximity sensor, although there may be a way to do it.

We just got a Nitro HD for my wife and her phone also has this issue. I have not gotten to know the phone well enough to try rooting or anything else of that nature, it's pure stock.
When she makes a call the screen turns off immediately after hitting the call button and will not wake up. When she receives a call we get a glimpse of the in-call screen with the various buttons etc but then the screen turns off. If the other party hangs up her screen turns back on, but if she calls something automated, like voicemail, she can't do anything except pull the battery to disconnect.
I've tried putting my thumb over the proximity sensor, hitting all buttons including power, and nothing makes the screen wake up or turns the phone off other than a battery pull.
The phone was running a build from last November when we first got it (V10i?) and today prompted us to update, so I did that hoping it would solve the problem. The phone is currently on V10j, but the problem persists.
Any help?

no driver said:
We just got a Nitro HD for my wife and her phone also has this issue. I have not gotten to know the phone well enough to try rooting or anything else of that nature, it's pure stock.
When she makes a call the screen turns off immediately after hitting the call button and will not wake up. When she receives a call we get a glimpse of the in-call screen with the various buttons etc but then the screen turns off. If the other party hangs up her screen turns back on, but if she calls something automated, like voicemail, she can't do anything except pull the battery to disconnect.
I've tried putting my thumb over the proximity sensor, hitting all buttons including power, and nothing makes the screen wake up or turns the phone off other than a battery pull.
The phone was running a build from last November when we first got it (V10i?) and today prompted us to update, so I did that hoping it would solve the problem. The phone is currently on V10j, but the problem persists.
Any help?
Click to expand...
Click to collapse
If you bought it from a store, get it exchanged for a new one.

actually works much faster on cm9, but therr still should be an optin to keep lcd on during call. i found some free apps that will disable hardware drivers but cant find the name of the proximity sensor driver, only that is named LGE.

Unfortunately it was given to us by a friend after my wife lost her Captivate, so taking it to a store to exchange is probably not going to work too well. As far as I can tell it was never used before we got it--the battery was still in it's own sealed pouch, the texting and driving warning was on the phone, and the phone went through the whole initial setup routine--but they didn't send us the box, I guess to cut down on mailing costs. I was hoping there was a known solution.

Ok, I downloaded two proximity sensor test apps today, but neither showed any activity. On my Captivate I get different readings with Proximity Sensor Finder (market link), but on the Nitro it is stuck at 3cm and it doesn't register anything no matter where I put my hand over the phone.
Can someone whose phone works right try installing this app and make sure that it picks up different readings on this device? OP, if you are still having issues, can you also try this app and see if it is static for you?
Thanks.

Took off the screen protector that they installed at the AT&T store and now the proximity sensor works just fine. OP, do you have a screen protector on your device?

we had an awfully thick one from att. we have since changed it to a super thin one. screen off is not a real problem on cm9, however i feel all devices should have the option to disable proximity sensor/keep lcd on during calls.

It's worth trying to use the warranty on the phone. Even though you dont have the original sales reciept, the phone has been released for less than a year, so no matter when you bought it, it is still within it's year long guaranteed warranty window.
Finished reading the thread, I suppose this post is now irrelevent

Get Smart Stay functionality on HOX

Now you can enjoy SGS3 Smart Stay funcionality in HOX too. Download ISeeyou app from Play Store to get the feature.
razzil.com/get-smart-stay-feature-any-android-phone.html

Works perfect . Whether it drains battery.
Sent from my HTC One X using Tapatalk 2

Thanks. It works, now just have to monitor on the battery life.
Btw, would like to ask on the notification icon, is it possible to set it to show only when the "smart stay function" is activated during looking at screen?

Nothing happens on my one!!!!

shtipu1111 said:
Nothing happens on my one!!!!
Click to expand...
Click to collapse
Haha. You have to stare really really hard at the front camera. I kid
What's your screen off time? If you set it to the lowest for the screen to turn off after 15 sec, it might not work since the free version of the app detects your face every 20sec by default.
Get the paid version and you can set face detect time and scan time
it works quite well I must say
Transformer: Tablet in Disguise

shtipu1111 said:
Nothing happens on my one!!!!
Click to expand...
Click to collapse
As @samuelong87 mention buy Premium version so that you can customize the time. It works perfectly at my side.

Smart Stay would be a nice feature to have but I would like to think that the app would somehow drain lots of battery.. abusing the front camera every half a minute or so would somehow have an impact I'm sure.
I wonder if the S3 would have enhanced battery life if they disabled the Smart Stay option.

alvtminghui said:
Smart Stay would be a nice feature to have but I would like to think that the app would somehow drain lots of battery.. abusing the front camera every half a minute or so would somehow have an impact I'm sure.
I wonder if the S3 would have enhanced battery life if they disabled the Smart Stay option.
Click to expand...
Click to collapse
i am wonder the same thing.
but i just purchased it and i will test
this is not interfering in any way to the auto brightness settings in in display as far as i can see.
it would be more than interesting to have an option to auto power off display after no face detecting (with customizable timing of course)
regards

Oh got it..thnx

andreipga85 said:
i am wonder the same thing.
but i just purchased it and i will test
this is not interfering in any way to the auto brightness settings in in display as far as i can see.
it would be more than interesting to have an option to auto power off display after no face detecting (with customizable timing of course)
regards
Click to expand...
Click to collapse
Well, first impression on this app is that it's not really battery friendly, but it does what it is supposed to do very well. Maybe next releases will be better from this point of view.
Regards
Sent from my HTC One X using XDA

Well, seems i will use it just from time to time
But is indeed an app that does well what is meant to do.
Regrads!
Sent from my HTC One X using XDA

Sorry for double or triple posting. Tapatalk is fc when uploadin photos.
Regards
Sent from my HTC One X using XDA

This app appears not working when device is on horizontal position

It works here when I'm switching to landscape mode, maybe you're blocking the front camera with your finger a little bit ?
Sent from my HOX

Now HTC One X is the best phone. This was the only feature missing

ISeeYou Causing Issues On My HOX
I have the HOX International. I used this app, and though it's a great concept, I was left largely dissatisfied by it.
While it works as advertised, I'm peeved with a couple of issues:
1) It blocks BOTH the front and back cameras. Try accessing the camera app while the service is ON and you only get a black screen.
2) It seems to hog battery occasionally (although this happens rarely).
3) I had the service to autostart, and received the shock of my life when around 1 hour into my day, I found that the rear camera was heating up. This might be a direct consequence of point 1 above.
I am on Stock and have the latest firmware update.
I don't know if any of you are facing these issues, but I've uninstalled the app ever since I started facing it.
Just a friendly heads up!

argetlam1 said:
I have the HOX International. I used this app, and though it's a great concept, I was left largely dissatisfied by it.
While it works as advertised, I'm peeved with a couple of issues:
1) It blocks BOTH the front and back cameras. Try accessing the camera app while the service is ON and you only get a black screen.
2) It seems to hog battery occasionally (although this happens rarely).
3) I had the service to autostart, and received the shock of my life when around 1 hour into my day, I found that the rear camera was heating up. This might be a direct consequence of point 1 above.
I am on Stock and have the latest firmware update.
I don't know if any of you are facing these issues, but I've uninstalled the app ever since I started facing it.
Just a friendly heads up!
Click to expand...
Click to collapse
The camera works well here! But, when I launched it from lock screen, it was blank. After unlocking properly with the secure path I use, both front and back cameras worked! (Newest wwe firmware.)
BUT: it DOES brake Face Unlock! I already sent a bug report e-mail to the dev

Used to work ok,then stoped without reason and I got blank screen with stock and other camera app(FV 5 and ics+).Unistalled it,but still had to reboot phone to get camera working properly.Installed it again,it works now,stock camera is working as well as FV5,with ics + , it gets FC sometimes...very nice idea,needs some polishing.

argetlam1 said:
I have the HOX International. I used this app, and though it's a great concept, I was left largely dissatisfied by it.
While it works as advertised, I'm peeved with a couple of issues:
1) It blocks BOTH the front and back cameras. Try accessing the camera app while the service is ON and you only get a black screen.
2) It seems to hog battery occasionally (although this happens rarely).
3) I had the service to autostart, and received the shock of my life when around 1 hour into my day, I found that the rear camera was heating up. This might be a direct consequence of point 1 above.
I am on Stock and have the latest firmware update.
I don't know if any of you are facing these issues, but I've uninstalled the app ever since I started facing it.
Just a friendly heads up!
Click to expand...
Click to collapse
I had haven't any problem as you wrote.
And also battery brain is normal from the moment front camera open for checking every 20". But no something special.
Anyway I think we dont need so match this future. At smartphones screen is so small, so when you read anything you need to scroll down. It's meaning if you touch the screen will continue to stay wakeup. I would like to have something like that in my iPad.

I can't get this working

Weird Issue with screen

I have something weird happening ,when auto-brightness is enabled or the phone screen is dimming down right before it goes to sleep a grey transparent looking screen flickers and sometimes sticks until i touch the screen to wake the phone back up and bring it back to whatever brightness setting i had it on . Im probably gonna do a warranty exchange when i get home i just wonder if this has happened to anyone else

tigerz0202 said:
I have something weird happening ,when auto-brightness is enabled or the phone screen is dimming down right before it goes to sleep a grey transparent looking screen flickers and sometimes sticks until i touch the screen to wake the phone back up and bring it back to whatever brightness setting i had it on . Im probably gonna do a warranty exchange when i get home i just wonder if this has happened to anyone else
Click to expand...
Click to collapse
Haven't seen that happen on mine over the two weeks I've had it.

tigerz0202 said:
I have something weird happening ,when auto-brightness is enabled or the phone screen is dimming down right before it goes to sleep a grey transparent looking screen flickers and sometimes sticks until i touch the screen to wake the phone back up and bring it back to whatever brightness setting i had it on . Im probably gonna do a warranty exchange when i get home i just wonder if this has happened to anyone else
Click to expand...
Click to collapse
I think I know what you are talking about. It's got to do with "Auto adjust screen tone" in Setting -> Display. For whatever the reason, transition between high brightness level and auto adjust screen tone isn't quite smooth. This happens all 3 of my Note 2 and S3. It's annoying as hell...
Let me know if that fix the flickering issue.

I have the same problem and every so often when useing the s pen the hole phone goes nuts, screen flipping by at a fast rate of speed and it is go from dim to bright to dim really fast too.
I have restart the phone and works for a few days and it comes right back.

Mike was it exposed to moisture? How long did you have the brighter note apk on there also?
Sent from the highly modded JDevil Note 2

zen0s said:
I think I know what you are talking about. It's got to do with "Auto adjust screen tone" in Setting -> Display. For whatever the reason, transition between high brightness level and auto adjust screen tone isn't quite smooth. This happens all 3 of my Note 2 and S3. It's annoying as hell...
Let me know if that fix the flickering issue.
Click to expand...
Click to collapse
I just checked the box in the settings gonna mess with it for a while see if it happens again.
Edit:
Hmm ran some tests with that feature enabled and so far so good .Gonna play with it for a couple days thanks for the tip

jeremyandroid said:
Mike was it exposed to moisture? How long did you have the brighter note apk on there also?
Sent from the highly modded JDevil Note 2
Click to expand...
Click to collapse
No moisture exposure and its definitely a hardware issue im sure of ,don't think the app has anything to do with it

tigerz0202 said:
No moisture exposure and its definitely a hardware issue im sure of ,don't think the app has anything to do with it
Click to expand...
Click to collapse
May be the user of the phone messing with the settings in terminal when he don't know how to like me
Sent from the highly modded JDevil Note 2

jeremyandroid said:
May be the user of the phone messing with the settings in terminal when he don't know how to like me
Sent from the highly modded JDevil Note 2
Click to expand...
Click to collapse
probably not

I had the same issue. Its not a hardware issue or app or anything . You have to odin back stock . I won't go into detail but there is something stuck on your partition from a kernel it sounds to me that can only be removed by going back stock . That's a know issue with the note 2 with kernels. If you flashed a kernel that's why .

AOD not turning off when phone is in my pocket or when face down

As the title indicates.* Always On Display now never goes off even when it is in my pocket or phone face is down at night.* AOD used to turn off as expected and believe this broke after the September security update.*
AOD remaining on when the phone is in pockets or face down is resulting in increase of battery use. I have unlocked Note 10+ on T-Mobile.
I posted this on Samsung support as well. Can you guys check and confirm if you are seeing the same issue?
Sent from my SM-N975U1 using Tapatalk

I've mentioned on another forum that I'm having this issue as well. I have the Note10+ T-Mobile with the September update. When I first got my phone before the September update, my phone's AOD used to turn off when I close my flip case. I checked this when I first got my phone because I was reading forums and people were saying it didn't work. Then after the September update, I noticed that the AOD will not turn off anymore when I close my flip case or even face down. Now it will just dim when the case is closed but never turn off.
Thanks for posting this on the Samsung forum as well. I hope they get back to you and give us an update to fix this issue.

Mine also is not working. I'm using tap-to-turn-on right now, and prefer it, but just chiming in here.

As a temporary solution you guys could set it to "show on tap", that's how I set mine from the beginning, so AOD is off unless you tap on it, or set it active during certain hours. If it was working and no more, probably bug in the update, what else is new, yawn.

Pinan said:
Mine also is not working. I'm using tap-to-turn-on right now, and prefer it, but just chiming in here.
Click to expand...
Click to collapse
pete4k said:
As a temporary solution you guys could set it to "show on tap", that's how I set mine from the beginning, so AOD is off unless you tap on it, or set it active during certain hours. If it was working and no more, probably bug in the update, what else is new, yawn.
Click to expand...
Click to collapse
Kind of disappointing. Pay $1,100 for a phone to only be forced to use it half ass LOL.
Sent from my SM-N975U1 using Tapatalk

Lepa79 said:
Kind of disappointing. Pay $1,100 for a phone to only be forced to use it half ass LOL.
Click to expand...
Click to collapse
This is not likely to ever change. Every new (rushed to market) device has issues. They'll fix it. I actually prefer the tap-on method now.
It is what it is.

If my phone is inside my pocket, I need to take it out and hold in my hand, same at night when sleeping, phone is laying down on night table, I need to pick it up to see the screen. If tapping the screen to activate AOD, when holding the phone in your hand is such a problem, I really would hate to see the drama, when real problems appear, like when you get a message or miss call and there is no notification light etc. LOL.

It's actually worse than just AOD not turning off because after the Sep update the proximity sensor doesn't work except when making a phone call. If I get a text message or email and my phone is in my pocket then the phone display turns on. At a minimum it's bad because the device wastes power turning on in the pocket, but depending what's on the screen it can also inadvertently clear notifications, open apps make a call all by accident. Needs a fix from Samsung ASAP.

sansnil said:
It's actually worse than just AOD not turning off because after the Sep update the proximity sensor doesn't work except when making a phone call. If I get a text message or email and my phone is in my pocket then the phone display turns on. At a minimum it's bad because the device wastes power turning on in the pocket, but depending what's on the screen it can also inadvertently clear notifications, open apps make a call all by accident. Needs a fix from Samsung ASAP.
Click to expand...
Click to collapse
It makes sense the problem is with the sensor post the security update since AOD depends on the sensor to turn off in pockets and when face down. Really crappy this gotten broken [emoji17]
Sent from my SM-N975U1 using Tapatalk