Database Info

Phonealarm switching questions?

I'm trying this program out to get my phone profiles to change automatically (silent for work and wifi/bluetooth on at other times like when plugged in etc).
I have set up details for auto switching but the behaviour now of the profiles is a bit weird at times.
When I have an automatic switchover for instance from Home to Work (silent) profiles, I'm not certain if it's actually doing it or not.
What happened this morning for instance was that I got to work at 8.40 and checked my phone and it still had the speaker icon showing normally in the taskbar as if it was still set to 100% volume, BUT, when I pressed the volume rocker to set it silent, I found the volume bar was already fully down, suggesting it had actually changed the volume setting as required and presumably switched the profile, but simply not refreshed the speaker icon on the taskbar to show that the phone was now set as silent or vibrate.
Hope that makes sense!
On top of that, whilst it seems to work well to switch both wifi and bluetooth on when required, it doesn't always seem to turn wifi off again when it should. I'm fairly sure it's not just a case of profile settings causing it just to remain on because the profile it's gone back to still uses wifi after an auto switch.
Would love to keep this program but only if I have total confidence that my phone is not going to ring when it's meant to be silent etc, and it's a little misleading at the moment with the impression it sometimes gives about whether the phone is actually silent or not.
Anyone else have these issues, and any way I can correct this?
Cheers!

if you've gone in to setting-->profiles --> and click option --> automatic switching
then you are doing it right
also realise there are option for switch on/off bluetooth/wifi/radio etc when setting up your profile
also if you can't see the PhoneAlarm taskbar on your front screen, then that would mean its not install properly and therefore not working, hope that helps

have you been to the forums @ pocketmax.net? there is tons of information there, and plenty of help for questions such as this.
I have been using phoneAlarm with no problems whatsoever for years now...
oh, and by the way, your signature does not reflect what ROM you are using -- I have noticed on the more recent Energy ROMs of mine that the taskbar is sometimes "slow" to refresh. for instance, when unplugging usb/charger the battery icon does not change from the 'lightning bolt' back to percentage until a minute or so... (this could possibly be related to volume icon as well)

Thanks for the replies
No I've not looked on their forum I must admit. Will be worth checking out though.
I'm very interested in the comments about this slow refresh with the taskbar though as I think that must be the problem.
I had noticed the same thing with the charging 'lightning'' icon but had forgotten until you mentioned it.
I've added my rom info in signature - thanks for pointing that out.
Is there any cure for this behaviour with the taskbar other than swapping Roms?
I'm quite happy really with this one, unless someone wants to recommend a rom that's radically better and doesn't have this particular issue?
Plus the fact I could potentially go through loads of other roms til this is solved, or just be trading this bug for another one.
Would love to solve it though. This app is growing on me but if I have to double check each time it swaps a profile to make sure it's done it then it defeats the purpose of having it.
I realise at least that this may not actually be the fault of the app itself though.

[Q] Missed call unlocks screen

Hi, I searched the forum but had no luck:
Completely new Nexus 5, White 16GB, and I have this issue:
When i receive and miss a call, as soon as the ringer stops the phone automatically shows the unlocked homescreen and it just stays there, instead of locking itself normally. This is really weird, and happens even if the phone is in my pocket (so it's not sensor-related like whatsapp pop-ups for example). Also not really safe i'd say. If I select another lockscreen method, it behaves normally (showing, for example, unlock pattern for a certain amount of time before turning the monitor off again.)
Anyone experiencing the same issue?

http://www.reddit.com/r/Nexus5/comments/1q04f7/nexus_5_unlocks_itself_after_a_missed_call/
This is the only other reporting I found on the web. Can anyone test this? It's really fast and easy, and I think this could be a pretty serious issue.

My phone (pin locked) doesn't do that. Phone stays locked. Is your phone kept unlocked?

jj14 said:
My phone (pin locked) doesn't do that. Phone stays locked. Is your phone kept unlocked?
Click to expand...
Click to collapse
Yes. I don't really like the pin/passcode unlock (also don't really need it). Classic slide is simple and fast enough, but it's crazy that it stays unlocked after a missed call.
Also, I noticed that it automatically enters the last application that was open the last time you locked it, creating even more concerns (last online on messaging applications, online status in facebook, ecc.)
Just imagine you boss calling you, with no luck, and founding out a second later you're online in Facebook. Just because you were ignoring your phone, while driving for example.

themcfly said:
Yes. I don't really like the pin/passcode unlock (also don't really need it). Classic slide is simple and fast enough, but it's crazy that it stays unlocked after a missed call.
Also, I noticed that it automatically enters the last application that was open the last time you locked it, creating even more concerns (last online on messaging applications, online status in facebook, ecc.)
Just imagine you boss calling you, with no luck, and founding out a second later you're online in Facebook. Just because you were ignoring your phone, while driving for example.
Click to expand...
Click to collapse
I agree - that should not be the expected behavior

nexus5 32gb here, exactly the same behavior.. I had to enable a pin/password unlock method because every missed call would unlock my phone, even in my pocket..

I have the same issue.
Maybe it is because of the app Light Flow Lite ?

mr_smith1 said:
I have the same issue.
Maybe it is because of the app Light Flow Lite ?
Click to expand...
Click to collapse
I thought this as well, but then I tried it on my friends N5 and had the same behavior, without light flow. I think many of us actually discovered this trying notifications in Light Flow (i bought the pro version) but it's not related to that.
kowloon12 said:
nexus5 32gb here, exactly the same behavior.. I had to enable a pin/password unlock method because every missed call would unlock my phone, even in my pocket..
Click to expand...
Click to collapse
Me too, but I hate it because I can't swipe down from the top to quickly see my notification without unlocking the device first.
Let me know if you guys have any advice on this issue, also report it in this thread to keep it bumped and see if anyone is reporting any solution.

themcfly said:
Me too, but I hate it because I can't swipe down from the top to quickly see my notification without unlocking the device first.
Click to expand...
Click to collapse
exactly this, it was so useful to just throw a glance to the notifications to decide if open them or simply clean them away

Yes same here, this looks to be a bug surely?
Sent from my Nexus 5 using xda app-developers app

OK thanks,
I reported the problem on google discussion (I copy/paste our first topic because you explained the problem very well ^^).
the URL:
"https://productforums.google.com/forum/#!category-topic/nexus/nexus-5/KML5nWW9q6o"

mr_smith1 said:
OK thanks,
I reported the problem on google discussion (I copy/paste our first topic because you explained the problem very well ^^).
the URL:
"https://productforums.google.com/forum/#!category-topic/nexus/nexus-5/KML5nWW9q6o"
Click to expand...
Click to collapse
Nice one, I have posted in that discussion as well. Hopefully we will get a response.

Others have the same problem, do you know how to report a problem to google ?

I just tried it on my phone, called from my desk number, missed call. It did open the phone all the way, but the screen turned back off in 5 seconds, per my settings.
My phones is currently stock, have not rooted or unlocked the bootloader yet. Only UI modification apps are Widgetzoid and Dashclock, I wanted to stay stock for a bit.
Sorry, that you are having issues. Unfortunately sometimes the easiest way to figure out what is causing the problems is to do a factory reset, and re-dowload your apps one by one, to see what is causing the problem.

Ok, but a several people have the same issue ...
Anyway, I think I will tri not to miss a call whenever the phone is in my pocket !

Zandeer said:
I just tried it on my phone, called from my desk number, missed call. It did open the phone all the way, but the screen turned back off in 5 seconds, per my settings.
Click to expand...
Click to collapse
I don't like setting the screen timeout so short, many thimes i just place the phone on my desk while messaging and I want the screen to stay on, for at least 2 minutes.
And when I lock my phone to keep it in my pocket, it's supposed to stay locked and ignore any unintended touches as soon as i slide to unlock, which was originally introduced to prevent an unlock by accident. Yes, I could lower my screen timeout to 5 seconds, but that does not solve the problem because still unintended touches can occur in that time frame.

themcfly said:
I don't like setting the screen timeout so short, many thimes i just place the phone on my desk while messaging and I want the screen to stay on, for at least 2 minutes.
And when I lock my phone to keep it in my pocket, it's supposed to stay locked and ignore any unintended touches as soon as i slide to unlock, which was originally introduced to prevent an unlock by accident. Yes, I could lower my screen timeout to 5 seconds, but that does not solve the problem because still unintended touches can occur in that time frame.
Click to expand...
Click to collapse
I wasn't sing o set your screen lock time to what I have it set at, I was just saying that it did re-lock. However, you are right, IMO it should not completely unlock the screen when the phone is ringing.
Though I have never not had a passcode on my phone, so not sure if that is how it always behaves. Was just trying to test and be helpful.

I sent a message to the google team, let's wait and see.
here is a link to see the bug :"http://www.youtube.com/watch?v=SSTq8Xhe6Kc&"

Zandeer said:
I wasn't sing o set your screen lock time to what I have it set at, I was just saying that it did re-lock. However, you are right, IMO it should not completely unlock the screen when the phone is ringing.
Though I have never not had a passcode on my phone, so not sure if that is how it always behaves. Was just trying to test and be helpful.
Click to expand...
Click to collapse
Thanks for testing, I was wondering if this could have been related to root / unlocked bootloader somehow but you have confirmed this is not the case as it happens on a totally stock phone.

good catch there. same issue here.
at least a Google employee has responded to the topic created HERE. Maybe that will expedite then pushing out an update ASAP.

Need advice for solving persistent glitch

Hello everyone,
It has been a while since I ventured through this forum, but it seems that y'all may be my only hope.
I've been suffering through this glitch/stutter that, when scrolling, the phone registers my finger as taps everywhere my finger slides. All I simply need to do it remove my finger from the phone and I can continue scrolling like normal. It is super annoying and I cannot find out what causes it, it just seems random. It never happened on any of my Nexus phones in the past.
Now, here's a list of things I've tried in order to fix it:
- Safe mode
- Factory Reset (Restore from Google account)
- Factory Reset (New Device option)
- RMA'd through Google support and received a new pixel and the problem persists (even after going through the steps above on the new device)
Here is a short video of the glitch while it is happening.
https://goo.gl/photos/GysQXd82MexVkk836
(Hopefully that link works)
Note: the glitch will not stop until I take my finger off the phone, you can tell when it is happening when I scroll over the share button and it registers as a tap.
If you guys have any suggestions, I'm ready to try anything at this point. I don't want to go through Google support because I know they'll send me yet another Pixel (I've already talked to them again and that was their solution, I told them I'll try a few more things) and I feel like that is a waste. I'm almost 100% positive that this is a software glitch, not hardware.
Thanks!

Was that the Reddit app or a browser window? I'll try to reproduce if you can tell me exactly what you were running. I do not have that behavior in the XDA app as I try it right now.

Jaxidian said:
Was that the Reddit app or a browser window? I'll try to reproduce if you can tell me exactly what you were running. I do not have that behavior in the XDA app as I try it right now.
Click to expand...
Click to collapse
Hey thanks for the response. I've gotten the glitch to happen all over. The Reddit app as you saw in the video, the chrome app, even scrolling through the list of apps in the stock pixel launcher. So I'm really not sure how to have you replicate the problem.
I'm thinking it is because certain settings in the settings app since Safe Mode disabled all third party apps when I tried that. I have night light enabled to turn on at dusk, I have ambient display off, auto brightness off, etc. Nothing too out of the ordinary.
I thought it may have been because I have location settings on high accuracy and when the phone pings for location maybe it bogs down the rest of my phone at that certain time but there's no way I can try and replicate that. It's a long shot anyway.

Skillfulshoe said:
Hey thanks for the response. I've gotten the glitch to happen all over. The Reddit app as you saw in the video, the chrome app, even scrolling through the list of apps in the stock pixel launcher. So I'm really not sure how to have you replicate the problem.
I'm thinking it is because certain settings in the settings app since Safe Mode disabled all third party apps when I tried that. I have night light enabled to turn on at dusk, I have ambient display off, auto brightness off, etc. Nothing too out of the ordinary.
I thought it may have been because I have location settings on high accuracy and when the phone pings for location maybe it bogs down the rest of my phone at that certain time but there's no way I can try and replicate that. It's a long shot anyway.
Click to expand...
Click to collapse
I just tried reproducing this by going to the app drawer and scrolling up and down while being sure my finger passed over both the home and app switcher buttons a good 50 or so times. The ONLY time the nav bar buttons were triggered were if my finger completely left the screen and went into the bezel - clearly that's not your problem. So I don't think I can reproduce the glitch.
If you think this is caused by your specific set of settings configured, you can always rule that out quickly with a factory reset. Just do a factory reset, set things up quickly, go ahead and login with your Gmail account so you can download some apps but do NOT change any non-basic settings. For example, go ahead and setup WiFi but do NOT change any display, input, or accessibility settings (especially the last thing there - the accessibility settings are often glitchy themselves). One setup, install a bunch more Google apps then try to reproduce the behavior again in the app drawer. If the behavior continues, then you may have a bad touchscreen sensor!
One last thing: Any chance you have really dry fingertips? Dry skin could always be your problem here!

Jaxidian said:
I just tried reproducing this by going to the app drawer and scrolling up and down while being sure my finger passed over both the home and app switcher buttons a good 50 or so times. The ONLY time the nav bar buttons were triggered were if my finger completely left the screen and went into the bezel - clearly that's not your problem. So I don't think I can reproduce the glitch.
If you think this is caused by your specific set of settings configured, you can always rule that out quickly with a factory reset. Just do a factory reset, set things up quickly, go ahead and login with your Gmail account so you can download some apps but do NOT change any non-basic settings. For example, go ahead and setup WiFi but do NOT change any display, input, or accessibility settings (especially the last thing there - the accessibility settings are often glitchy themselves). One setup, install a bunch more Google apps then try to reproduce the behavior again in the app drawer. If the behavior continues, then you may have a bad touchscreen sensor!
One last thing: Any chance you have really dry fingertips? Dry skin could always be your problem here!
Click to expand...
Click to collapse
I guess I'll try a factory reset and not mess with the settings although that kind of defeats the purpose of using this phone the way I want lol.
I'm not sure if this is caused by a bad touchscreen sensor because I've had the problem on two separate Pixel phones so far. Or maybe I just got super unlucky with two faulty phones.
I don't think my fingers are too dry. If all else fails, I'll try moisturizing them I guess. I've never had this problem on all my other phones though, but I guess you never know.
Thanks for the help.

Skillfulshoe said:
I guess I'll try a factory reset and not mess with the settings although that kind of defeats the purpose of using this phone the way I want lol.
Click to expand...
Click to collapse
I recently had a similar situation (different bad behavior) when helping my mother-in-law with a vision disability. Atrociously unacceptable performance, multiple phones. Turned out the triple-tap-to-zoom feature in the accessibility options was the culprit and disabling that one checkbox made all the difference.
I'm not necessarily suggesting you must use defaults forever, but if this is a setting of yours, let's first prove that it's a setting before going through the long process of finding out WHICH setting it is. Does that make sense? If we reset settings to defaults and it continues, no need to spend all that time - you've got a broker phone. If that does fix it, no need to return the phone, it's a buggy setting - let's find it to see if you can live without it one way or another. It may be a major deal breaker out it may be something you really don't care much about.

I think I get that issue now and again, usually whilst scrolling in chrome. I decided it was due to holding a finger on the screen just long enough (before starting to scroll) to register the press as a "select text" event.

Jaxidian said:
I recently had a similar situation (different bad behavior) when helping my mother-in-law with a vision disability. Atrociously unacceptable performance, multiple phones. Turned out the triple-tap-to-zoom feature in the accessibility options was the culprit and disabling that one checkbox made all the difference.
I'm not necessarily suggesting you must use defaults forever, but if this is a setting of yours, let's first prove that it's a setting before going through the long process of finding out WHICH setting it is. Does that make sense? If we reset settings to defaults and it continues, no need to spend all that time - you've got a broker phone. If that does fix it, no need to return the phone, it's a buggy setting - let's find it to see if you can live without it one way or another. It may be a major deal breaker out it may be something you really don't care much about.
Click to expand...
Click to collapse
Yeah I totally understand what you're saying. I just have gotten frustrated with this. I know it isn't a big deal honestly.

gadgetgaz said:
I think I get that issue now and again, usually whilst scrolling in chrome. I decided it was due to holding a finger on the screen just long enough (before starting to scroll) to register the press as a "select text" event.
Click to expand...
Click to collapse
Yeah that could be what causes it. Maybe it is just the way we are scrolling and how Google has calibrated the screen touch sensors.

Possible Fix
So I went into accessibility settings and changed the duration you need to hold your finger down to do a long press to medium (from the default as short). It seems that may have fixed it. I haven't experienced the glitch since I've done that change.
Here's to hoping that did indeed fix the issue.
Thanks everyone.

Anyone else experiencing dropped tap inputs?

On my pixel 2 tap inputs occasionally don't register, I've had it happen in the android system menu, the android back/home buttons, chrome, etc. Is anyone else experiencing this?
My phone's basically on stock default settings, nothing unusual running. Not sure if it's only tap inputs getting dropped or the whole system locking up temporarily. Turning on "Show taps" in Developer options I can see there's no visual effect when a missed tap occurs.

Yes, this is me too exactly. Same thing with the dev option too. Not sure if I should wait for 8.1 or if it's hardware and RMA it. Frustrating because I like this phone.

I noticed this on my phone, clicking around in the settings and on the back and home buttons. I then did a factory reset (because of a separate issue where the location icon was always displaying in the notification area, even when not in use). After that the issue seems to have gone away. So it would seem to be software issue. I suggest trying a factory reset (though beware that this wipes everything on your device).
P.S. nonexistent, I'm impressed that you joined the XDA forums in Dec 2010 and never posted a comment until now. Of course, you might need to change your screen name to "existent," now that you're out in the open.

I have definitely noticed this as well, happy to know it wasn't just me

cb474 said:
I noticed this on my phone, clicking around in the settings and on the back and home buttons. I then did a factory reset (because of a separate issue where the location icon was always displaying in the notification area, even when not in use). After that the issue seems to have gone away. So it would seem to be software issue. I suggest trying a factory reset (though beware that this wipes everything on your device).
P.S. nonexistent, I'm impressed that you joined the XDA forums in Dec 2010 and never posted a comment until now. Of course, you might need to change your screen name to "existent," now that you're out in the open.
Click to expand...
Click to collapse
I tried a reset but the issue still showed up. In fact it happened twice on the first time setup stuff afterwards. I called Google and we went through the motions and reset it from recovery mode but it was still there when I was testing it the next couple hours. Anyway, we're doing the RMA thing. I'll let you guys know how it works out when I get my new phone.

Got my replacement and the problem still exists. It even happens just a couple screens into the initial setup after a factory reset from recovery mode.

I find that it occurs when I'm in a small room with the heat turned up. The sensitivity of the touch screen seems to depend a lot on moisture. If I keep my fingers moist (or wear a touch sensitive glove) it works a heck of a lot better.

ritzack said:
Got my replacement and the problem still exists. It even happens just a couple screens into the initial setup after a factory reset from recovery mode.
Click to expand...
Click to collapse
That's good and bad news I guess, hopefully just needs a software update. I have a replacement coming Monday, but I kind of expect no improvement and that this is just a common thing that a lot of people aren't noticing

I noticed that for a while in Google Play Books, in which I tap the screen frequently to turn pages. I tried a factory reset, which didn't help. I tried running in safe mode and testing on Maps and still had a problem, although less frequently (a higher percentage of taps worked). Then it started to work better. We'll see if that lasts.
I tried flicking as opposed to tapping and flicking always works.
I'd suggest posting on the Pixel product forum or calling support, so that Google becomes more aware of the issue. There are some threads on the subject on reddit and the product forum.

Out of interest are you noticing it any particular parts of the screen?
I've noticed it a few times but it's been on areas of the screen near the edges.
I assumed it was some sort of palm rejection thing going on it the background with it thinking I'm accidently mashing the display.

With me it was the right edge toward the middle, as that's where you tap to turn the page in Play Books.

I get it on the back button frequently, but it happened just now in the middle of the screen when I typed the text input box to start writing this

I think this is the whole OS hanging/freezing briefly actually, not a touchscreen input issue
- Pressing the hardware unlock button can get ignored (both locking/unlocking)
- Scrolling from a quick flick + release can suddenly stop (no additional inputs)
So most likely this is a software issue, hopefully fixed in an upcoming update? It's kinda annoying

Did you change the DPI or font size? I go back to default and it seems that everything is good now.
---
update: no it happens again…

nonexistent said:
On my pixel 2 tap inputs occasionally don't register, I've had it happen in the android system menu, the android back/home buttons, chrome, etc. Is anyone else experiencing this?
My phone's basically on stock default settings, nothing unusual running. Not sure if it's only tap inputs getting dropped or the whole system locking up temporarily. Turning on "Show taps" in Developer options I can see there's no visual effect when a missed tap occurs.
Click to expand...
Click to collapse
can you be more specific? I just got Pixel 2 - black, 128GB (Canadian). I can touch and the UI responds well. But i want to test it out thoroughly..

Haven't changed the DPI or font size
LimitsX said:
can you be more specific? I just got Pixel 2 - black, 128GB (Canadian). I can touch and the UI responds well. But i want to test it out thoroughly..
Click to expand...
Click to collapse
I can trigger the system hang/"missed input" most reliably by visiting m.reddit in chrome (any thread w/ comments) and spamming tap on the [-] next to the username of any comment to collapse/expand the section. Turning on Show Taps from Developer Tools in the system menu I can see taps being ignored sometimes

Haven't changed the DPI or font size
LimitsX said:
can you be more specific? I just got Pixel 2 - black, 128GB (Canadian). I can touch and the UI responds well. But i want to test it out thoroughly..
Click to expand...
Click to collapse
I can trigger the system hang/"missed input" most reliably by visiting any m.reddit thread in chrome and spamming tap on the [-] next to the username of any comment to collapse/expand the section. Turning on Show Taps from Developer Tools in the system menu I can see taps being ignored sometimes

nonexistent said:
Haven't changed the DPI or font size
I can trigger the system hang/"missed input" most reliably by visiting m.reddit in chrome (any thread w/ comments) and spamming tap on the [-] next to the username of any comment to collapse/expand the section. Turning on Show Taps from Developer Tools in the system menu I can see taps being ignored sometimes
Click to expand...
Click to collapse
So, I replicated what you told me, 3x. I didn't miss any taps, and no system hang/missed input..
hmm

Got my replacement and it has been much better so far. Still a few dropped inputs but I think those may be false positives because I am hyperfocused on it. Pretty sure I have always had to double click occasionally on all phones at various times.

nonexistent said:
Turning on Show Taps from Developer Tools in the system menu I can see taps being ignored sometimes
Click to expand...
Click to collapse
Yeah, sometimes I see a tap register visually on the screen, but the intended action doesn't happen.
redandblack1287 said:
Got my replacement and it has been much better so far. Still a few dropped inputs but I think those may be false positives because I am hyperfocused on it. Pretty sure I have always had to double click occasionally on all phones at various times.
Click to expand...
Click to collapse
It's funny. I had the issue. Did a factory reset. Felt like it was better. But now that I'm thinking about it more I notice it a lot. So I can't tell if it's really different. Before I figured I'd made a mistake. Now I think it's the phone. Damn you phone!
Anyway, I notice that the issue tends to happen more or less randomly, at any position on the screen. Also, sometimes the same tap fails to register twice in a row, but once it's starts working all subsequent taps that come in a row work (say I'm clicking through a lot of menu items in some settings). So maybe that lends some credence to the idea that there is a system for registering the taps that is not waking up and once it does it works fine.
Perhaps related, I have my ambient display set to wake on double tap. Before the Nov update it hardly worked. Now it seems to be working reliably.

Question [J706F] P11 Pro keeps waking up for no reason.

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