Related
I have searched here, and only (for the g-tab) found answers that point to apps to disable the unlock bar. I would like to turn it off. Permanently.
On my Eken M001, there was a setting in scriptcmd to toggle the "slide to unlock" bar. Of course, using it required re-flashing the rom.
Is there a way to accomplish the same thing here, with the same effect?
I am using TnT lite 5. Oh and BTW, Roebeet: you are awesome. Please never stop doing that voodoo you do.
Dan
why?
just curious as to why you would want it disabled
This may not be what you're looking for, which I'm guessing is just bypassing the lock screen entirely, but WidgetLocker (not free) allows you to use a press of the back key to unlock -- you can determine how long the press needs to be. Does a lot more than that actually, but since the custom sliders it uses don't seem to work well with a tab, I use the back key to unlock on mine.
I use switch pro. Comes with a bunch of toggles including this.
Via TT
Os Money said:
just curious as to why you would want it disabled
Click to expand...
Click to collapse
Because I put my tab down often, and pick it up often, and past experience has told me I dislike 'needing' to unlock it. With my Eken, the choice to 'slide to unlock' or not was mine without using an app, or the resources it consumes.
I'll look for switch pro. Widgetlocker has been a major resource hog on my phone, so I'm not likely to go that way.
But, as I said, if there is a hack/mod, I'd prefer that.
"No Lock" app does this
I've been using Screen Off and Lock forever to lock my phone using the swipe-up-from-home-nav-button (instead of the default Google Now).
After updating to Lolipop, I started using my Moto 360 as a trusted device and enabled a PIN lock on my phone. When I lock the phone with the power button and my Moto 360 connected, no PIN screen appears when I turn the screen back on.
However, if I lock the phone using the app Screen Off and Lock, the PIN screen always comes on when I go to turn the screen back on. This defeats the whole purpose/convenience of the trusted device bypassing the PIN. Anyone know how to fix this? Or know of an app that will work better?
It hasn't been updated since January so I imagine its just an incompatibility
ragnarokx said:
I've been using Screen Off and Lock forever to lock my phone using the swipe-up-from-home-nav-button (instead of the default Google Now).
After updating to Lolipop, I started using my Moto 360 as a trusted device and enabled a PIN lock on my phone. When I lock the phone with the power button and my Moto 360 connected, no PIN screen appears when I turn the screen back on.
However, if I lock the phone using the app Screen Off and Lock, the PIN screen always comes on when I go to turn the screen back on. This defeats the whole purpose/convenience of the trusted device bypassing the PIN. Anyone know how to fix this? Or know of an app that will work better?
Click to expand...
Click to collapse
I'm on stock rooted Lollipop and I'm running into a similar issue, but with face unlock instead of trusted device.
I have double-tap on Nova Launcher set to system lock using Tasker, and when I lock my phone using that, face unlock doesn't activate, and won't until I put in my PIN password and then re-lock using the power button.
chronostorm said:
I'm on stock rooted Lollipop and I'm running into a similar issue, but with face unlock instead of trusted device.
I have double-tap on Nova Launcher set to system lock using Tasker, and when I lock my phone using that, face unlock doesn't activate, and won't until I put in my PIN password and then re-lock using the power button.
Click to expand...
Click to collapse
I also tried locking my phone using Greenify instead of Screen Off & Lock, sam result. Perhaps there is a way to implement locking the phone that won't trigger the PIN to unlock? Or - and I hope this isn't the case - maybe there is no way to do this in 5.0?
ragnarokx said:
I also tried locking my phone using Greenify instead of Screen Off & Lock, sam result. Perhaps there is a way to implement locking the phone that won't trigger the PIN to unlock? Or - and I hope this isn't the case - maybe there is no way to do this in 5.0?
Click to expand...
Click to collapse
I tried messing around with screen timeout in Tasker, but it doesn't let me set it to 0 seconds (for obvious reasons, I guess haha), since I noticed that letting my screen time out seems to work just fine for triggering face unlock. The lowest I can set it to is 7 seconds though, if I remember right, which is a bit too high for a screen off function.
ragnarokx said:
I've been using Screen Off and Lock forever to lock my phone using the swipe-up-from-home-nav-button (instead of the default Google Now).
After updating to Lolipop, I started using my Moto 360 as a trusted device and enabled a PIN lock on my phone. When I lock the phone with the power button and my Moto 360 connected, no PIN screen appears when I turn the screen back on.
However, if I lock the phone using the app Screen Off and Lock, the PIN screen always comes on when I go to turn the screen back on. This defeats the whole purpose/convenience of the trusted device bypassing the PIN. Anyone know how to fix this? Or know of an app that will work better?
Click to expand...
Click to collapse
Have the same issue, wait for developer to fix it.
Sent from my Nexus 5 using Tapatalk
Not sure this will be "fixed". All apps that are stating to lock the phone will actually do so, whether trusted devices are enabled or not. They act the same way as if you are on the lockscreen with the lock disabled by a trusted device and then press the lock symbol at the bottom, this also locks the device. This has been a problem forever, apps just work differently than the hardware power button.
As a fix you can try the following: Use another app to completely disable the lockscreen or keyguard (whatever your prefer) when a trusted device is connected instead of using the android built in feature.
If you are like me and want to use the new trusted devices feature of lollipop you can use Tasker as a workaround. Create a tasker task with the command "run shell --> input keyevent 26". This also requires root. Then you can use the app Home Button Launcher to set a shortcut to run the new task when swiping up. This is what I'm using and it works without any problem! I hope I could help.
spiderflash said:
Not sure this will be "fixed". All apps that are stating to lock the phone will actually do so, whether trusted devices are enabled or not. They act the same way as if you are on the lockscreen with the lock disabled by a trusted device and then press the lock symbol at the bottom, this also locks the device. This has been a problem forever, apps just work differently than the hardware power button.
As a fix you can try the following: Use another app to completely disable the lockscreen or keyguard (whatever your prefer) when a trusted device is connected instead of using the android built in feature.
If you are like me and want to use the new trusted devices feature of lollipop you can use Tasker as a workaround. Create a tasker task with the command "run shell --> input keyevent 26". This also requires root. Then you can use the app Home Button Launcher to set a shortcut to run the new task when swiping up. This is what I'm using and it works without any problem! I hope I could help.
Click to expand...
Click to collapse
I attached a pic of trying to do what you said in Tasker. When I run the task, nothing happens.
ragnarokx said:
I attached a pic of trying to do what you said in Tasker. When I run the task, nothing happens.
Click to expand...
Click to collapse
Have you installed the latest superSU beta? The previous versions had problems with the new security features introduced by lollipop. If you're not using this latest version my solution won't work.
spiderflash said:
Have you installed the latest superSU beta? The previous versions had problems with the new security features introduced by lollipop. If you're not using this latest version my solution won't work.
Click to expand...
Click to collapse
It worked! SuperSU beta did the trick.
Also, I didn't need a separate app to make a Home key shortcut, I just made a profile: Event -> UI -> Assistance Request -> add the Task with input keyevent 26.
Thanks!
Nothing against Screen Off and Lock as it's just doing what it's designed to do (and Lock after all) but this is a useful work around, thanks.
ragnarokx said:
It worked! SuperSU beta did the trick.
Also, I didn't need a separate app to make a Home key shortcut, I just made a profile: Event -> UI -> Assistance Request -> add the Task with input keyevent 26.
Thanks!
Click to expand...
Click to collapse
Oh yeah I forgot about that. First I tried it that way, but for some reason it didn't work, so thats why I use an external app But I'm glad it works for you!
spiderflash said:
Not sure this will be "fixed". All apps that are stating to lock the phone will actually do so, whether trusted devices are enabled or not. They act the same way as if you are on the lockscreen with the lock disabled by a trusted device and then press the lock symbol at the bottom, this also locks the device. This has been a problem forever, apps just work differently than the hardware power button.
As a fix you can try the following: Use another app to completely disable the lockscreen or keyguard (whatever your prefer) when a trusted device is connected instead of using the android built in feature.
If you are like me and want to use the new trusted devices feature of lollipop you can use Tasker as a workaround. Create a tasker task with the command "run shell --> input keyevent 26". This also requires root. Then you can use the app Home Button Launcher to set a shortcut to run the new task when swiping up. This is what I'm using and it works without any problem! I hope I could help.
Click to expand...
Click to collapse
Thanks you guys. Now I feel more at home with Lollipop with my old habit. I couldn't stand that smart lock was disabled when I used other screen off apps (then again those haven't gotten an update for a while too).
ragnarokx said:
It worked! SuperSU beta did the trick.
Also, I didn't need a separate app to make a Home key shortcut, I just made a profile: Event -> UI -> Assistance Request -> add the Task with input keyevent 26.
Thanks!
Click to expand...
Click to collapse
Yeah, there is no update yet from screen lock app developer regarding this issue ..
guess i have to use tasker trick ..
nsg86 said:
Yeah, there is no update yet from screen lock app developer regarding this issue ..
guess i have to use tasker trick ..
Click to expand...
Click to collapse
There probably won't be. The app is called "... And Lock". Technically, it's doing what its supposed to.
spiderflash said:
Not sure this will be "fixed". All apps that are stating to lock the phone will actually do so, whether trusted devices are enabled or not. They act the same way as if you are on the lockscreen with the lock disabled by a trusted device and then press the lock symbol at the bottom, this also locks the device. This has been a problem forever, apps just work differently than the hardware power button.
As a fix you can try the following: Use another app to completely disable the lockscreen or keyguard (whatever your prefer) when a trusted device is connected instead of using the android built in feature.
If you are like me and want to use the new trusted devices feature of lollipop you can use Tasker as a workaround. Create a tasker task with the command "run shell --> input keyevent 26". This also requires root. Then you can use the app Home Button Launcher to set a shortcut to run the new task when swiping up. This is what I'm using and it works without any problem! I hope I could help.
Click to expand...
Click to collapse
Was searching for a solution and i found this thread! Thanks a lot!
So no hope for people like me who don't use trusted devices/places but use trusted face? Because I think even tasker can't do that with trusted face unlock.
Also looking for a solution to this with trusted faces on lollipop.
Edit: If you're interested, you can follow the defect here: https://code.google.com/p/android/issues/detail?id=79735
Based on this thread:
http://forum.xda-developers.com/lg-v10/help/knock-to-wake-t3239674
So far it's only a confirmed suspicion, but it's already happened to several people including myself. Accessing the hidden menu may break the knock on feature, even without doing any modification in it.
Possible Solutions:
-Hard Reset (100% working)
-Deleting Finger Prints (I've only seen this working on 1 person in another thread)
Please report if this has happened to you and if you've done something else to solve the issue. Thanks!
I go in the hidden menu a couple times a day to change RAT selection and have only had one issue. So I wouldn't say it's a 100% the hidden menu
Sent from my LG-H901 using Tapatalk
Nope, doesn't break it. Been in the hidden menu to access Engineering Mode a bunch of times already and knock-on works fine.
Went in there to unlock the APN fields. Knock-on works fine.
Sent from my LG-H901 using XDA Free mobile app
Guys, it only breaks, as I stated in another thread, if you open the IMS Settings (which causes a crash) in the hidden settings menu. It is 100% reproducible, but *ONLY* that setting causes the issue.
toastido said:
Guys, it only breaks, as I stated in another thread, if you open the IMS Settings (which causes a crash) in the hidden settings menu. It is 100% reproducible, but *ONLY* that setting causes the issue.
Click to expand...
Click to collapse
Nope that didn't break it either
@baymon - Funny how everyone notices this until you post a PSA about it then everyone has to try to rebuke it.
If it "breaks" (turns knock on, off) you can use the anycut type app from the play store and make a shortcut to the hidden menu knock on option to toggle it back on or off if you so chose (I turned mine off so it would stop turning on in my pocket).
toastido said:
@baymon - Funny how everyone notices this until you post a PSA about it then everyone has to try to rebuke it.
Click to expand...
Click to collapse
Obviously we need more data on this issue, there could be other variables in play as well but that's why we're raising the awareness of the knock on issue.
@toastido haha it's all good.
LancerV said:
I go in the hidden menu a couple times a day to change RAT selection and have only had one issue. So I wouldn't say it's a 100% the hidden menu
Sent from my LG-H901 using Tapatalk
Click to expand...
Click to collapse
How do you get into the hidden menu? Tried quickshortcutcreator but can't find it.
sentry07 said:
How do you get into the hidden menu? Tried quickshortcutcreator but can't find it.
Click to expand...
Click to collapse
Dial 277634#*#
I'm anxiously awaiting everyone now saying their knock on is broken ?
Didnt break mine! Thanks for the info to get into hidden menu though
nope mine still works but i do have issues with the screen in calls but thats it. but but was that way when i got it.
i think your hidden menu theory is good but my knock doesnt work but it stopped after i did a rest because the apn got messed up and it wouldnt let me add a new one. so i found this out this problem seams random as hell and if i turn knock pattern on to unlock the phone the knock works to turn the screen on but not off. i also noticed my second screen doesnt have the flash light on it when off anymore. so i will be doing a reset tomorrow unless anyone knows how to get the secound screen apps back when the screen is off. i think those apps are related to the tap on
It did break mine. Went to menu and hit apn unlock. No crash or anything. I noticed it not working immediatly. Knock code does still work.
I had the issue also, then did a reset. But I want to add to the issue that it didn't only effect knock on, but the touchscreen didn't register anything altogether when screen off. Meaning, the second screen can swipe when screen off to show the quick toggles, it did not work during that time.
joachim123 said:
I had the issue also, then did a reset. But I want to add to the issue that it didn't only effect knock on, but the touchscreen didn't register anything altogether when screen off. Meaning, the second screen can swipe when screen off to show the quick toggles, it did not work during that time.
Click to expand...
Click to collapse
mines the same no quick toggles
Mines the same no quick toggles but i found the answer with out rest on another post. i figured it out that its just something crashing the hidden menu doesnt matter what even force closing causes this problem. which is what i did seeing that the first time i used it nothing happened but the second time when the problem happened i cleared all apps and it stopped working. i'm guessing they disable it if something crashes it.
the knock on actually just gets turned off. Here's the quote for the answer make sure both knock on settings are on and it works instantly so no reboot needed.
-LBT- said:
Get yourself Quick Shortcut Maker, launch it, change the search type to 'Normal', search for 'Knock On', click on 'Settings', then on 'Try'. On the next screen, switch Knock On back and forth and see if that works.
Click to expand...
Click to collapse
clockcycle said:
If it "breaks" (turns knock on, off) you can use the anycut type app from the play store and make a shortcut to the hidden menu knock on option to toggle it back on or off if you so chose (I turned mine off so it would stop turning on in my pocket).
Click to expand...
Click to collapse
you are a genius and life saver!!! thank you.
hidden menu did break it, confirmed.
Hi guys.
I'm one of those who do not have lockscreens in my phones.
Also, I love the double tap to unlock feature. Been using it on my G2, G3, OnePlus3T.
This feature on the Pixel only works if you have a lockscreen. This is more like a "double tap to lockscreen" rather than "double tap to wake".
Is there a way around this?
Now I know there are apps that do this, but they are not managed by the kernel, are unstable and drain more batt than they should. I'm hoping a dev can look into this
Cheers!
MasK said:
Hi guys.
I'm one of those who do not have lockscreens in my phones.
Also, I love the double tap to unlock feature. Been using it on my G2, G3, OnePlus3T.
This feature on the Pixel only works if you have a lockscreen. This is more like a "double tap to lockscreen" rather than "double tap to wake".
Is there a way around this?
Now I know there are apps that do this, but they are not managed by the kernel, are unstable and drain more batt than they should. I'm hoping a dev can look into this [emoji14]
Cheers!
Click to expand...
Click to collapse
I agree with every single thing you wrote. I don't like to lock my phones either, but like to have the raise-to-wake feature. I happen to like Gravity Screen, but as you found, it does eat battery to set it up the exact way I want (use motion instead of proximity). So this is what I do. Establish a lock method so tap-to-wake or raise-to-wake works. Then turn around and create smart lock situations to bypass that lock. For example, I establish smart lock by locations, and by Bluetooth connections. Since I always wear a smart watch of some kind, it leaves my phones unlocked, but tap-to-wake still works.
I tried to get the double tap only to work as well but I failed. I don’t need to lock my phone either. Coming from BB10 where all I had to do was swipe up to unlock my phone man that was great. A slight swipe would show the lock screen a full swipe gesture would unlock the phone. None of this involves touching the power button I am simply talking about picking the phone up and swiping without hitting the power. BB10 was awesome it really was great but I think the lack of apps didn’t allow it to shine.
The finger print to unlock is pretty quick and easy but if your phone is position in a way that your not going to unlock it with your finger you have to use a pin or pattern to unlock.
quangtran1 said:
I agree with every single thing you wrote. I don't like to lock my phones either, but like to have the raise-to-wake feature. I happen to like Gravity Screen, but as you found, it does eat battery to set it up the exact way I want (use motion instead of proximity). So this is what I do. Establish a lock method so tap-to-wake or raise-to-wake works. Then turn around and create smart lock situations to bypass that lock. For example, I establish smart lock by locations, and by Bluetooth connections. Since I always wear a smart watch of some kind, it leaves my phones unlocked, but tap-to-wake still works.
Click to expand...
Click to collapse
Thanks for you replies, guys.
I didn't find the trusted devices method that reliable for some reason. I do have a smartwatch I use for work, but not for leisure, so I will not have a consistent experience unlocking the device. Also, this only work if it's secure (other than swipe).
So in order to use the T2W feature, you might as well have at least a simple swipe lockscreen.
Also, I tried something else last night. Elemental X kernel. It has T2W built in and works pretty alright. It is more sensitive (original implementations require you to tap with a little force) and 2 gentle touches is all that's required to unlock. Does not consume a lot of battery.
I may check out Gravity screen as well, to prevent accidental unlocks when it is upside-down (in my pocket) and that should do it.
And yea, I was also trying out Tasker, automating "swipe up" when I wake up the device. Didn't go too well. In case you guys wanna tinker with it, lemme know if you get it to work
MasK said:
Thanks for you replies, guys.
I didn't find the trusted devices method that reliable for some reason. I do have a smartwatch I use for work, but not for leisure, so I will not have a consistent experience unlocking the device. Also, this only work if it's secure (other than swipe).
So in order to use the T2W feature, you might as well have at least a simple swipe lockscreen.
Also, I tried something else last night. Elemental X kernel. It has T2W built in and works pretty alright. It is more sensitive (original implementations require you to tap with a little force) and 2 gentle touches is all that's required to unlock. Does not consume a lot of battery.
I may check out Gravity screen as well, to prevent accidental unlocks when it is upside-down (in my pocket) and that should do it.
And yea, I was also trying out Tasker, automating "swipe up" when I wake up the device. Didn't go too well. In case you guys wanna tinker with it, lemme know if you get it to work
Click to expand...
Click to collapse
The really nice thing about Gravity Screen is that it puts you back where you left it, not the lock screen.
MasK said:
Thanks for you replies, guys.
I didn't find the trusted devices method that reliable for some reason. I do have a smartwatch I use for work, but not for leisure, so I will not have a consistent experience unlocking the device. Also, this only work if it's secure (other than swipe).
So in order to use the T2W feature, you might as well have at least a simple swipe lockscreen.
Also, I tried something else last night. Elemental X kernel. It has T2W built in and works pretty alright. It is more sensitive (original implementations require you to tap with a little force) and 2 gentle touches is all that's required to unlock. Does not consume a lot of battery.
I may check out Gravity screen as well, to prevent accidental unlocks when it is upside-down (in my pocket) and that should do it.
And yea, I was also trying out Tasker, automating "swipe up" when I wake up the device. Didn't go too well. In case you guys wanna tinker with it, lemme know if you get it to work
Click to expand...
Click to collapse
I would be interested in implementing a Tasker profile to do this. I'll let you know if I get anything good.
I finally turned it off. Fingerprint scanner doesn't work even though the scroll up and down still does so I'll live.
Not sure if it would work, but what if you disabled double tap in the rom, disable lock screen in the rom and flash Elemental kernel and enable double tap with it?
Sent from my Pixel using Tapatalk
joshw0000 said:
Not sure if it would work, but what if you disabled double tap in the rom, disable lock screen in the rom and flash Elemental kernel and enable double tap with it?
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
Instead of flashing that kernel, flar2 also created a stand-alone app called Wake Gestures to accomplish just that. The app can be downloaded from his signature line.
quangtran1 said:
Instead of flashing that kernel, flar2 also created a stand-alone app called Wake Gestures to accomplish just that. The app can be downloaded from his signature line.
Click to expand...
Click to collapse
I'm not familiar with the app. Does it drain battery like some of the others that people have mentioned in this thread. I really like Elemental in that I can also enable sweep2sleep. I've actually been using the stock DT2W and Elemental just for the sleep function.
I keep my phone propped on my desk at work and can quickly lock and unlock it as needed.
Sent from my Pixel using Tapatalk
joshw0000 said:
I'm not familiar with the app. Does it drain battery like some of the others that people have mentioned in this thread. I really like Elemental in that I can also enable sweep2sleep. I've actually been using the stock DT2W and Elemental just for the sleep function.
I keep my phone propped on my desk at work and can quickly lock and unlock it as needed.
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
The app is created by flar2, the creator of ElementalX, so I don't believe it would be any different than his kernel. I use it and I do not experience drain. One additional feature the app has is the extra protection of accidental pocket turn-ons.
Maybe it's a common issue but I haven't found any info when searching about it.
I have a P11 Pro, and since I got it, I have always been having the same issue with the tablet waking up on its own quite often, randomly, or even sometime refusing to go back to sleep.
I disabled any setting that might waking it up (tap to wake, move to wake...), and disabled several apps, but it changes nothing.
It's especially annoying since when I don't use a screen lock, with the 5 minutes stay on time I set, it keeps waking and empty the battery quite fast.
Using a screen lock reduce the issue as the tablet goes back to sleep quickly, but still doesn't solve the problem. And I don't want to use screen lock when I use the tablet at home.
Does any you know that issue, or how to fix it?
Thanks in advance!
Do you have a keyboard attached or some Bluetooth devices like mice?
Does it have a built in sensor for lid close and open when used with the original keyboardcover? That might be causing the issue then.
Did you try a factory reset?
Is the latest system update installed?
hashtowent said:
Do you have a keyboard attached or some Bluetooth devices like mice?
Does it have a built in sensor for lid close and open when used with the original keyboardcover? That might be causing the issue then.
Did you try a factory reset?
Is the latest system update installed?
Click to expand...
Click to collapse
Nothing connected.
Yeah the lid has a sensor, but it does it even when I remove the cover completely or when I leave it closed and not moving.
Yes I did several factory reset, update of the firmware, and yes I'm on the latest one.
As far I can understand, a process on the tab itself is waking up the tab randomly, I just can't put my finger on which app/function does it.
Stremon said:
Nothing connected.
Yeah the lid has a sensor, but it does it even when I remove the cover completely or when I leave it closed and not moving.
Yes I did several factory reset, update of the firmware, and yes I'm on the latest one.
As far I can understand, a process on the tab itself is waking up the tab randomly, I just can't put my finger on which app/function does it.
Click to expand...
Click to collapse
Look for battery usage details it should tell, after having show system services ensbled
hashtowent said:
Look for battery usage details it should tell, after having show system services ensbled
Click to expand...
Click to collapse
Nothing visible there either, the app that keeps waking up the tab isn't necessarily taking any battery.
I didn't mention as it is very visible from my profile, but I'm not a beginner with android, very far from it, if I'm asking here it's because I already tried all the obvious things
I am asking if anybody has the same issue and/or was able to fix it. If not, I guess it's just my unit.
You might try this
The command like this:
adb shell dumpsys batterystats --checkin
provides a statistic for wakeups, including the reasons.
Mine wakes up. Can't figure out why either but then I'm not by any means an Android ace. I turn the screen off then after some period of time it'll turn back on. Nothing in the notifications bar the screen just turns back on for no apparent reason. So yes, it is happening to someone else but no answer as to why.
hashtowent said:
Do you have a keyboard attached or some Bluetooth devices like mice?
Does it have a built in sensor for lid close and open when used with the original keyboardcover? That might be causing the issue then.
Did you try a factory reset?
Is the latest system update installed?
Click to expand...
Click to collapse
I'm sad to say that you were right, the magnetic cover was at least partially to blame for the wake events. That's a huge bummer, since I guess there is no way to fix the issue
I had this issue.
I said that notifications must not wake up the tablet and it did not appear anymore.
I know there was no notification, but it worked for me.
(in fact, sometimes, I had the impression that a notification appeared for a very short time)
LeNouveau said:
I had this issue.
I said that notifications must not wake up the tablet and it did not appear anymore.
I know there was no notification, but it worked for me.
(in fact, sometimes, I had the impression that a notification appeared for a very short time)
Click to expand...
Click to collapse
Interesting, I'll try that too, thanks
I have the plus not the pro but check if near to wake up is on under the AI Experience Center in settings.
hungmung said:
I have the plus not the pro but check if near to wake up is on under the AI Experience Center in settings.
Click to expand...
Click to collapse
Everything is disabled there.
But I am quite convinced it comes from the smartcover, as since I enterily removed it, I don't have the issues anymore and the battery lasts weeks (with light usage) instead of 2 days like before.
Issue is that there is no way to disable the smart cover magnet...
Stremon said:
Everything is disabled there.
But I am quite convinced it comes from the smartcover, as since I enterily removed it, I don't have the issues anymore and the battery lasts weeks (with light usage) instead of 2 days like before.
Issue is that there is no way to disable the smart cover magnet...
Click to expand...
Click to collapse
That is probably it. I just thought I'd offer I had similar happen and had accidentally turned that on so it was turning on every time anything moved near it.
hungmung said:
That is probably it. I just thought I'd offer I had similar happen and had accidentally turned that on so it was turning on every time anything moved near it.
Click to expand...
Click to collapse
Thanks, that indeed makes sense.
And I really wish it was just that.
I'll try again with the smart cover to see if I can do anything about it.
It's the official magnetic cover so it's a huge bummer that it causes issues...
Stremon said:
Interesting, I'll try that too, thanks
Click to expand...
Click to collapse
Hi, I was looking for a solution to the waking up of the screen. In the ¨AI Experience Center¨ there is an option called ¨automatically screen light-up¨. I turned this off, because it said that if sensor detects a face, the screen lights up, and also "other" objects can trigger this screen light up. I suppose the cover is detected while closed. Other object in the range of 0.5m can also trigger this light up. Also deactivated the notifications icons in the status bar, if not doing this, it continues to light up the screen in my P11.
Mine does the same thing...just sitting there and all of a sudden the screen lights up.
Solution:
Settings -> Display -> Lock Screen -> When to show
Turn "new notification" off