Related
Has anyone else had airplane.mode just turn on by itself during calls? its beeN happening often and also happened on my first EVO LTE that I exchanged...ill be on a call and all of a sudden it will hang up..ill look at the screen and airplane mode is activating..its drivin me nuts and is happening a lot..like everyday
firmbiz94 said:
Has anyone else had airplane.mode just turn on by itself during calls? its beeN happening often and also happened on my first EVO LTE that I exchanged...ill be on a call and all of a sudden it will hang up..ill look at the screen and airplane mode is activating..its drivin me nuts and is happening a lot..like everyday
Click to expand...
Click to collapse
Still doing it months later wtf
You don't have an app installed called more bars do you? That app automatically enters airplane mode during low signal to conserve battery.
Sent from my A500 using Tapatalk
ishh happen to me the other day.. i just turned my screen on and i watched it happen.. i was running mean rom forget what version.. i watched my radio's turn off and airplane mode turn on.. it hasnt happend again
U must have a something wrong with it or something. I have never had this happen
Sent from my EVO using xda premium
HTC One
So I'm having this problem as well, on my new HTC One... it goes into airplane mode nearly every call I have... I'll probably have to go back to my iPhone if I can't resolve the issue. As stupid as it sounds, I'm fairly confident it's my ear touching the screen that's "navigating" into settings and turning airplane mode on... if I'm 100% concentrating on not touching the phone's screen at all, I don't have the problem. But if I'm talking normally, it never fails, the call drops, I look at the phone, and I'm sitting on the settings page with airplane mode on. I honestly don't know how this doesn't happen to everyone... I *THINK* my ears are normal!? Anyone come up with a solution??
markzaa said:
So I'm having this problem as well, on my new HTC One... it goes into airplane mode nearly every call I have... I'll probably have to go back to my iPhone if I can't resolve the issue. As stupid as it sounds, I'm fairly confident it's my ear touching the screen that's "navigating" into settings and turning airplane mode on... if I'm 100% concentrating on not touching the phone's screen at all, I don't have the problem. But if I'm talking normally, it never fails, the call drops, I look at the phone, and I'm sitting on the settings page with airplane mode on. I honestly don't know how this doesn't happen to everyone... I *THINK* my ears are normal!? Anyone come up with a solution??
Click to expand...
Click to collapse
Is your proximity sensor working fine? Is it covered with a screen protector?
Check this out:
https://play.google.com/store/apps/details?id=com.tigermonster.proxfinder
Good luck!
Sent from my Evo 4G LTE
jocarog said:
Is your proximity sensor working fine? Is it covered with a screen protector?
Check this out: (link removed)
Good luck!
Sent from my Evo 4G LTE
Click to expand...
Click to collapse
Thanks... I installed the sensor app... seems to be working ok... it's showing "all or nothing" (9cm or 0cm) and seems to indicate the duration I hold the phone to my head. If I move my head around (not necessarily away from the phone) it indicates that the sensor thought I wasn't in proximity the full time... so perhaps there are brief moments the OS thinks I've pulled the phone away from my head. Maybe that algorithm needs tweaking (e.g. maybe wait 1-2 seconds of nothing in proximity before turning on screen?).
I don't have a screen protector.
markzaa said:
Thanks... I installed the sensor app... seems to be working ok... it's showing "all or nothing" (9cm or 0cm) and seems to indicate the duration I hold the phone to my head. If I move my head around (not necessarily away from the phone) it indicates that the sensor thought I wasn't in proximity the full time... so perhaps there are brief moments the OS thinks I've pulled the phone away from my head. Maybe that algorithm needs tweaking (e.g. maybe wait 1-2 seconds of nothing in proximity before turning on screen?).
I don't have a screen protector.
Click to expand...
Click to collapse
found this on the htc one forum: http://forum.xda-developers.com/showthread.php?t=2259526
I didn't read it, but it looks like you are not the only one having issues with the proximity sensor...
So I know this doesn't help much but wanted to add I'm having this issue as well. Not every call but maybe every couple of days or so. Does seem to happen when I'm using the phone, not an ear piece, and I'm moving around a lot. So might be something with the proximity sensor, though there is not quick button I could be hitting with my face to turn airplane mode on even if the screen was on. I have also noticed a lot of strange network issues where my single bounces between 4g, 3g and hsdpa often, which I've never had a phone do this much before. I can actually sit there and watch flip back and forth. So I'm really thinking the HCT One has some manufacture issues that are not being addressed. I'm about ready to send this thing in.
Does Omate Trusmart (1/8 1900) accelerometer turns off when screen is locked ? The listener doesn't work when screen is locked
I want to listen to the shake events without a partial wake lock on the screen( which drains the battery a lot). Any suggestions ?
sudhanpsg said:
Does Omate Trusmart (1/8 1900) accelerometer turns off when screen is locked ? The listener doesn't work when screen is locked
I want to listen to the shake events without a partial wake lock on the screen( which drains the battery a lot). Any suggestions ?
Click to expand...
Click to collapse
Same for the GPS, so probably the same for all sensors.
I assume a new kernel is needed for this.
LOL. It barely works even with a wake lock. That's why not a single wake app works consistently on the 1/8. I would not expect to see such a minor issue fixed anytime soon seeing it's 6 months later and the firmware is still not secured.
Lokifish Marz said:
LOL. It barely works even with a wake lock. That's why not a single wake app works consistently on the 1/8. I would not expect to see such a minor issue fixed anytime soon seeing it's 6 months later and the firmware is still not secured.
Click to expand...
Click to collapse
I hope this will be solved one day, this is really restrictive as it stands...
I use Awesome On/Off to wake mine. It seems to work more often than not, but sometimes it doesn't and I can only assume that the TS has gone into a deeper sleep. But worth a try by anyone who feels a bit self conscious suddenly shaking their arm in public. Awesome just requires you to raise your arm to a normal watch-reading position.
BenjaminM said:
I hope this will be solved one day, this is really restrictive as it stands...
Click to expand...
Click to collapse
I've discovered that the latest FW update (Onate_Truesmart_20140513.103530_v2.0) has introduce a new "Smart Mode" --> "Sport Mode", which basically turn off the back-light but keep the screen on hence, the sensors (Accelerometer, GPS, etc.) are kept alive.
I've been trying it for couple of days and it works great. It terms of battery drain, it is noticeable but remains reasonable. Anyway, if you are note recording any fitness activity, you can still change the mode after your workout.
I have an LG G Watch with 5.0.1 since a few days and I tried and sent back an identical LG G watch on 4.4W.1 a while ago and didn't experience it. Basically, I am noticing that after leaving the watch alone lying somewhere (I don't wear it at home) for some time (can't really say how long but at least an hour, I think) the display turns OFF. A single tap and it wakes up and then works "normally" until the next time...
The other G Watch with the older Wear version didn't have this behaviour so is this a feature of the latest Wear version (or possibly an LG-exclusive mod to squeeze even more battery life) or is it maybe an "issue"..?
I am saying this especially because I installed the Slumber app to automatically turn the display OFF while charging but realized that it's easier and more elegantly done by simply choosing the new "Theater mode" in Android Wear 5.0.1 and uninstalled the app. I don't know if what I am seeing is due to having installed Slumber but I really don't think so.
Does anybody know for sure what it is and how it exactly works..?
TIA
I was just about to post about this I think it's a bug though... I don't use a Slumber app or anything, I want my screen truly to be always on. But it will turn off occasionally and I don't like that!! I definitely did not have this issue on 4.4W.2
Anyone know what the problem is or how to fix it?
philessthanthree said:
I think it's a bug though... I don't use a Slumber app or anything,
Click to expand...
Click to collapse
Just to be clear, I don't use it anymore and uninstalled it just after getting the 5.0.1 update with its Theater mode. My worry was that having had it installed triggered this behaviour but since you get it without ever installing it I can put that to rest.
I want my screen truly to be always on. But it will turn off occasionally and I don't like that!! I definitely did not have this issue on 4.4W.2
Click to expand...
Click to collapse
Have you ever got it while it is on your wrist..?
Reading this I just removed my g-watch and after a few minutes I see that my screen was OFF. Never happen when I have watch on my wrist the last 2 days. Screen alaways ON and turn on with movement OFF. So yes it is a new feature of the last update 5.01.
Same here, it happened twice on the table, and once on my wrist this morning.
Must be something like the ambient mode in Moto 360 that does this. For one moment I thought I accidentally triggered the cinema mode.
I always take my watch off at work and the screen keeps turning off after 30 minutes. I did a full reset in case it was an overhang from the old version but it's still turning off.
So based on all of the above replies it seems it's a feature of the latest Android Wear. I am not calling it a bug because, except for a single reported case from our friend with the Moto 360, it seems to never happen while wearing it, so the logic appears to be "save the battery when not in use".
Just to "investigate" it some more, I am trying to time it and confirm it's 30 minutes for me too like StuBFrost says, and may you all please confirm you have Ambient turned ON (i.e. the display is always ON) and state whether you have the new Tilt to wake up setting ON (i.e. the Display lights up from its dimmed state when you tilt your wrist).
My settings are Display always ON and Tilt to wake up OFF.
It would be good to have some more reports from owners of different Wear smartwatches, to this end I posted also in the general Android Wear forum but no replies so far. I am going to update that post with our findings and see if we can understand what exactly is this behaviour we are seeing...
Actually, I think it might be a good feature to keep ON in many cases but it absolutely should be an *option*!
I have both options switched on and both work fine except for this new stupid sleep mode that quite clearly hasn't been thought out properly. Surely the theatre mode allows people to turn the display off should they need to and for everythimg else it should do what it did before and stay on.. If it doesn't get "corrected" soon, I will be rooting my watch and putting a custom ROM on it.
StuBFrost said:
I have both options switched on and both work fine except for this new stupid sleep mode that quite clearly hasn't been thought out properly. Surely the theatre mode allows people to turn the display off should they need to and for everythimg else it should do what it did before and stay on.. If it doesn't get "corrected" soon, I will be rooting my watch and putting a custom ROM on it.
Click to expand...
Click to collapse
Trying to time it, I think I can say (I am still trying to cover all of the different scenarios) that any event which normally wakes the display up to normal brightness (i.e. an incoming call) resets the countdown. BTW, I think you are right and it's 30 minutes off the wirst with no movement, no tapping on it and no event like the ones just mentioned. "Normal" incoming notifications don't seem to reset the countdown.
Like I said, I don't think it's a bad idea in and of itself (I would use it in most cases) but they should have made it an option! And, ideally, they would let us set the time after which the display turns itself off.
I use and *strongly* prefer Android instead of limited and dumbed down Windows Phone and even worse Apple's useless crap exactly because of its customizability and powerfulness...
"Funny" thing is that from further testing, this feature doesn't kick in while on the charger (which could actually be pretty useful for most people...) LOL
ADDENDUM: the kind of events which resets the countdown to this "deep sleep" state (i.e. an incoming call) also wakes the display up from "deep sleep".
I am running the LG G Watch, version 5.0.1 with accompanying Android Wear app on my phone version 1.0.5
Screen is set to ALWAYS ON.
Tilt to wake is OFF.
It happens BOTH on my wrist and off my wrist. The timing is variable from my limited observation, but I haven't tried to directly time it.
on my lg g watch too
may I ask something related? on mine, it happened to be able to stop display (full black) with a swype from bottom to the top, never been able to do it again. Anybody faced that?
Hi all,
Since Android Wear 2.0 the dock mode while charging with clock doesn't work any longer. When placing Moto on the dock it shows a black screen. When touching the screen de clock appears for a moment and vanishes after about 1.5 seconds. It appears to be a bug. Do you all have this bug or is it just me. Did anyone tried a reset of the watch? I would really like to able to fix it , cause I use that feature a lot.
Same here.
A temporary solution I have found is to enable in developer options 'stay awake while charging' now it stays on. But it is not the same. The display appears to be much brighter. probably because ambient mode (Not sure that's how its called) is not enabled.
Edit: That appears to be the fix. When turning on in settings 'always on display' it works like before. no need to enable stay awake while charging in developers settings.
Although this fixes the issue, I am somewhat disappointed because this option reduces battery life.
I noticed I should have put this question into 'troubleshoot and questions'. I am sorry for placing it here. Perhaps a moderator can place it in the right section for me?
Not a problem here.
Always on is normally activated.
Sent from my m1 note using Tapatalk
I've noticed the same behavior when I upgraded my Moto 360 to AW 2.0
For me, the clock stays on but the background is really bright whereas it used to be black before
Same thing here, background to bright. I don't think this is on purpose. They would probably get out fixed in an upcoming patch(?)
Same here.
I liked docking my watch on my bathroom counter and using it as my clock while getting ready in morning. Now it doesn't stay on and when I tap the screen I can see it for a few seconds. When it is on ....the brightness of the background is terrible.
I sure hope they fix this problem.
I have the same problem
Can't believe there is still no fix for this?
This is really annoying! I was hoping XDA had found an answer. Having always on screen on is not a solution since Moto made a bad design decision on the screen making it best to turn that option off. I assume everyone else's keep awake while charging option doesn't really solve it either because the screen turns off once the battery is full. Anyone think there's a workaround to be found in Tasker and maybe AutoInput (maybe turn always on screen on while charging, off otherwise, or even based on hours). I'm no tasker expert, so I'm not sure if that combo could work on android wear.
Sn0w0nS said:
Hi all,
Since Android Wear 2.0 the dock mode while charging with clock doesn't work any longer. When placing Moto on the dock it shows a black screen. When touching the screen de clock appears for a moment and vanishes after about 1.5 seconds. It appears to be a bug. Do you all have this bug or is it just me. Did anyone tried a reset of the watch? I would really like to able to fix it , cause I use that feature a lot.
Click to expand...
Click to collapse
I have found this to be an issue when I use a charger that is not the Motorola plug that came with the watch. If you switch to the Motorola OEM charger you'll see a lag of about one to two seconds but the clock will always come on.
sebastianraven said:
I have found this to be an issue when I use a charger that is not the Motorola plug that came with the watch. If you switch to the Motorola OEM charger you'll see a lag of about one to two seconds but the clock will always come on.
Click to expand...
Click to collapse
Not on mine. I'm using the factory charger.
vladfan said:
Not on mine. I'm using the factory charger.
Click to expand...
Click to collapse
That's so odd. I'm not having that problem at all
sebastianraven said:
I have found this to be an issue when I use a charger that is not the Motorola plug that came with the watch. If you switch to the Motorola OEM charger you'll see a lag of about one to two seconds but the clock will always come on.
Click to expand...
Click to collapse
I am using Motorola's dock charger. I am positive that the issue lies with Android Wear 2.0 and not the charger. Before wear 2.0 it worked as it should.
I think it's random with AW2.
After flashing a new rom at my mobile, I had to forget and pair again the watch to the Android wear.
From now on, the clock stays on during charging.
This was not the case before that.
Sent from my m1 note using Tapatalk
I have the very same issue (watch paired with a Nexus 4, 5.1.1). Anything I can try? Thanks!
Well, at least this is validation for me. It's been driving me insane, and I'm almost positive it's killing my battery life. I used to be able to stretch a full week on a single charge, but now it's more like a full day.
I'm sure this is what everyone else has been experiencing: there is now a setting called "Always on screen" in Android wear settings. The new behavior for this setting is a strict enforcement of this property; that is, to be either always on or auto off. This seems absurd because before Android wear 2 (not sure if the option existed or not), it seemed to work as we expected, to auto off in active wear but stay lit while docked. There should at the very least be another mode for when docked/standby vs active wear.
Something else that makes it seem buggy is that when the always on screen option is disabled, and the watch is docked and charging, the screen is still faintly lit although only a blank black and no clock. I do think this is a bug and not a feature. For anyone interested, there are also settings for other things you might not be using. I'm turning them off and pray the battery gets better.
wesswei said:
Well, at least this is validation for me. It's been driving me insane, and I'm almost positive it's killing my battery life. I used to be able to stretch a full week on a single charge, but now it's more like a full day.
I'm sure this is what everyone else has been experiencing: there is now a setting called "Always on screen" in Android wear settings. The new behavior for this setting is a strict enforcement of this property; that is, to be either always on or auto off. This seems absurd because before Android wear 2 (not sure if the option existed or not), it seemed to work as we expected, to auto off in active wear but stay lit while docked. There should at the very least be another mode for when docked/standby vs active wear.
Something else that makes it seem buggy is that when the always on screen option is disabled, and the watch is docked and charging, the screen is still faintly lit although only a blank black and no clock. I do think this is a bug and not a feature. For anyone interested, there are also settings for other things you might not be using. I'm turning them off and pray the battery gets better.
Click to expand...
Click to collapse
What r u talking about?
Always On was there since Android Wear 1.5.
And come again?
1 week use of the watch with 1 charge?
How did u manage to do that?
By turning on the watch for 2 hours every day?
Sent from my m1 note using Tapatalk
I'm pretty sure my S7e had the option to turn the screen completely off when in a pocket or face down, even when AOD was turned on. I can't find any way to do that on the S9. Even on auto brightness it stays on, very dimly. On manual brightness, it stays on at whatever brightness you've set. What's the point of having AOD use even a little bit of battery if you can't see the display at all?
Anyone found a way to shut AOD off in these circumstances?
Try Blocking Touches in the Display Options.
Goofytek said:
Try Blocking Touches in the Display Options.
Click to expand...
Click to collapse
Thanks, but that's not it. I do have that turned on. It's not that AOD turns off but comes back on because of touches. Unlike the S7, it never turns off, even in a pocket or screen down.
Is this just a rant? Cause it seems like you've answered your own question.
Actually, it does turn off completely. If you cover the proximity sensor for around 30 seconds, the AOD turns off completely.
Same as the S7, same as the S8.
meyerweb said:
Thanks, but that's not it. I do have that turned on. It's not that AOD turns off but comes back on because of touches. Unlike the S7, it never turns off, even in a pocket or screen down.
Click to expand...
Click to collapse
I've been trying to solve this as well. It seems some models have different wording in the block touches option. My tmobile device says something like prevent touches while in a dark place, pocket. I've been told the wording for that option on other models is more like disable screen in dark places, pockets. I hope it gets changed in an update.
the_scotsman said:
Actually, it does turn off completely. If you cover the proximity sensor for around 30 seconds, the AOD turns off completely.
Same as the S7, same as the S8.
Click to expand...
Click to collapse
Actually it does not. What's weird is I swear it did when I first got the phone but it seems like an update broke it or something because it no longer does it.
Really hope a future update brings it back because I haven't found any settings that enable it.
Anyone figure this out?
vintagerock said:
Actually it does not. What's weird is I swear it did when I first got the phone but it seems like an update broke it or something because it no longer does it.
Really hope a future update brings it back because I haven't found any settings that enable it.
Anyone figure this out?
Click to expand...
Click to collapse
What I've figured out is that it works 100% on my S9+.
And my wife's S9+.
And my daughter's S9+.
And my other daughter's S9+.
You may wish to review the settings on your device again.
I hope you find the missing configuration, because I can understand the frustration when something appears to not work as it should.
Having had a number of S7 phones that featured a stuck rotation-lock due to a borked accelerometer, and "glowing" screens while turned off due to bad display drivers, I would not discount the possibility that your device could be defective, if you have turned on the appropriate feature-set and the AOD still does not turn off when the proximity sensors are covered.
the_scotsman said:
Actually, it does turn off completely. If you cover the proximity sensor for around 30 seconds, the AOD turns off completely.
Same as the S7, same as the S8.
Click to expand...
Click to collapse
Nope. If I put it face down on a table or desk in a completely dark room, I can see the light from the screen reflecting off the surface. (My case lifts the screen slightly off the table.) And if I take it out of my pocket, I can see the AOD is very dim immediately after coming out, and then brightens after a split second.
afh3 said:
What I've figured out is that it works 100% on my S9+.
And my wife's S9+.
And my daughter's S9+.
And my other daughter's S9+.
You may wish to review the settings on your device again.
I hope you find the missing configuration, because I can understand the frustration when something appears to not work as it should.
Having had a number of S7 phones that featured a stuck rotation-lock due to a borked accelerometer, and "glowing" screens while turned off due to bad display drivers, I would not discount the possibility that your device could be defective, if you have turned on the appropriate feature-set and the AOD still does not turn off when the proximity sensors are covered.
Click to expand...
Click to collapse
Have you checked it in a totally dark room (say, a bathroom, at night, with the shade closed and the door closed)? Because that's when it becomes clear the screen is just very dim, not off. Also, if you set manual brightness on the AOD, instead of auto, it's very obvious that it stays on even when the phone is face down.
What do you consider the "appropriate feature set," because I've looked all through the settings and there is no setting for turning the screen off when in a pocket or face down.
meyerweb said:
Have you checked it in a totally dark room (say, a bathroom, at night, with the shade closed and the door closed)? Because that's when it becomes clear the screen is just very dim, not off. Also, if you set manual brightness on the AOD, instead of auto, it's very obvious that it stays on even when the phone is face down.
What do you consider the "appropriate feature set," because I've looked all through the settings and there is no setting for turning the screen off when in a pocket or face down.
Click to expand...
Click to collapse
I think I see where at least some of the misunderstanding is now.
What you describe is expected behavior in the dark/low-light scenario.
Note that the AOD turns off (if you've enabled "Block accidental touches" in the display settings) only if the >proximity< sensor detects that the phone is, well, in proximity to something - such as when it is face-down or in a pocket.
If not in proximity to something, what can be expected is that the illumination sensor will simply adjust the AOD brightness (if in the automatic mode) in response to the ambient light it detects - bright in bright light, and dim in low or no light. Just as you've described your experience.
Again, if your "Block accidental touches" feature is on, and the AOD isn't turning off when it is in proximity to an object (in a pocket, face-down, etc.) you may have a defect.
meyerweb said:
Have you checked it in a totally dark room (say, a bathroom, at night, with the shade closed and the door closed)? Because that's when it becomes clear the screen is just very dim, not off. Also, if you set manual brightness on the AOD, instead of auto, it's very obvious that it stays on even when the phone is face down.
What do you consider the "appropriate feature set," because I've looked all through the settings and there is no setting for turning the screen off when in a pocket or face down.
Click to expand...
Click to collapse
I don't have block accidental touches on but it does turn off when it's in my pocket or faced down. It might be just your device. It always turns off for me when it should.
chickenbb said:
I don't have block accidental touches on but it does turn off when it's in my pocket or faced down. It might be just your device. It always turns off for me when it should.
Click to expand...
Click to collapse
Interesting. I was always under the belief that the setting was required in order to assure AOD would turn off in those situations.
Turns out, it does work regardless of the state of that feature!
I still think that having that turned on just makes sense for those times when it is in a pocket, but you are correct in that it does not preclude the AOD turn-off feature.
afh3 said:
Interesting. I was always under the belief that the setting was required in order to assure AOD would turn off in those situations.
Turns out, it does work regardless of the state of that feature!
I still think that having that turned on just makes sense for those times when it is in a pocket, but you are correct in that it does not preclude the AOD turn-off feature.
Click to expand...
Click to collapse
I have that setting on but it still won't turn off AOD in my pocket. I was worried my proximity sensor was defective so I tested it but it appears to be working fine.
What model/carrier do you guys have. I have the attached branded snapdragon model. Like I said before it used to work but now it doesn't. Not sure if it coincides with an update or not
vintagerock said:
I have that setting on but it still won't turn off AOD in my pocket. I was worried my proximity sensor was defective so I tested it but it appears to be working fine.
What model/carrier do you guys have. I have the attached branded snapdragon model. Like I said before it used to work but now it doesn't. Not sure if it coincides with an update or not
Click to expand...
Click to collapse
Verizon branded S9+ [ARBG] here.
afh3 said:
Verizon branded S9+ [ARBG] here.
Click to expand...
Click to collapse
Hmm interesting.
I meant to say att branded is what I have.
vintagerock said:
Hmm interesting.
I meant to say att branded is what I have.
Click to expand...
Click to collapse
You could always factory-reset the device and see if the functionality returns.
With an SD card and a SmartSwitch backup, it's not that painful to reset the phone and get it back to (more or less) the configuration you have right now.
After a reset, I'd probably test it >before< restoring the SmartSwitch backup - just to confirm that it isn't some app that is breaking the AOD turn-off deal.
Best of luck with this.
meyerweb said:
Thanks, but that's not it. I do have that turned on. It's not that AOD turns off but comes back on because of touches. Unlike the S7, it never turns off, even in a pocket or screen down.
Click to expand...
Click to collapse
Don't know if you've figured out your issue yet but I finally figured out what was causing mine to not turn off. It was bcActions app I was using to remap bixby button.
vintagerock said:
Don't know if you've figured out your issue yet but I finally figured out what was causing mine to not turn off. It was bcActions app I was using to remap bixby button.
Click to expand...
Click to collapse
I have the exynos version. Are you sure it's the bxActions app causing it? Because I have it and the AOD still turns off for me.
chickenbb said:
I have the exynos version. Are you sure it's the bxActions app causing it? Because I have it and the AOD still turns off for me.
Click to expand...
Click to collapse
Yeah I stopped bxaactions and it instantly fixed the AOD problem. What actions do you have your button mapped to?