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
Related
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.
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.
About three months ago my Pixel 2 (purchased new from Google) began having an issue where it becomes unresponsive or extraordinarily delayed on responding. It almost always happens when I'm waking the phone up from being locked. When it happens, the phone will eventually unlock but everything reacts several seconds after contact (power button, taps, swipes). A reboot or power down fixes the problem, but is always necessary.
I switched to Project Fi around that time and thought it had something to do with the switching between CDMA and GSM (Sprint/US Cellular vs T-Moble) towers, but I've switched to T-Mobile (a solely GSM provider) since and the problem persists.
I am running Android Pie (stock). My bootloader is unlocked and I do have Magisk installed. No TWRP. I don't have any obvious troublemakers installed (like Xposed, for example) and only a few apps that even use root (Cerberus, Adaway, and Nova Launcher).
I have heard about the Pixel 2 XL having a hardware issue that results in unresponsiveness and that ultimately requires sending in the device for a replacement. Is this the same thing?
Any advice would be much appreciated. If it would be helpful, I can produce logs, but I'll have to wait until it happens again to offer logs that might contain clear indications of what might be happening.
- Computerslayer
computerslayer said:
About three months ago my Pixel 2 (purchased new from Google) began having an issue where it becomes unresponsive or extraordinarily delayed on responding. It almost always happens when I'm waking the phone up from being locked. When it happens, the phone will eventually unlock but everything reacts several seconds after contact (power button, taps, swipes). A reboot or power down fixes the problem, but is always necessary.
I switched to Project Fi around that time and thought it had something to do with the switching between CDMA and GSM (Sprint/US Cellular vs T-Moble) towers, but I've switched to T-Mobile (a solely GSM provider) since and the problem persists.
I am running Android Pie (stock). My bootloader is unlocked and I do have Magisk installed. No TWRP. I don't have any obvious troublemakers installed (like Xposed, for example) and only a few apps that even use root (Cerberus, Adaway, and Nova Launcher).
I have heard about the Pixel 2 XL having a hardware issue that results in unresponsiveness and that ultimately requires sending in the device for a replacement. Is this the same thing?
Any advice would be much appreciated. If it would be helpful, I can produce logs, but I'll have to wait until it happens again to offer logs that might contain clear indications of what might be happening.
- Computerslayer
Click to expand...
Click to collapse
Do you have the navbar hidden by any chance
crixley said:
Do you have the navbar hidden by any chance
Click to expand...
Click to collapse
Well, I have Nova set up to hide the dock unless I swipe up (or down) on it. I can't seem to find a setting about hiding the navbar. Where should I be looking to check?
computerslayer said:
Well, I have Nova set up to hide the dock unless I swipe up (or down) on it. I can't seem to find a setting about hiding the navbar. Where should I be looking to check?
Click to expand...
Click to collapse
Did you install any apps to hide your navigation bar? Is it always visible? Immersive mode apps for example
crixley said:
Did you install any apps to hide your navigation bar? Is it always visible? Immersive mode apps for example
Click to expand...
Click to collapse
We're talking about the back button and the new pill gesture button, right? If so, then no I haven't installed anything to hide those: they are always visible.
Well, after 24 hours, I had the issue resurface. Unfortunately, the logging app I was using (matlog) froze up with the phone and produced a blank text file. While rebooting restored normal function of the phone, I can't produce a log as a result.
It occurs to me that while I am not disabling the navbar, I do use a function of the Cerberus anti-theft app to disable the notification bar while locked. Could this be the source of my issue? If so, is there any way to confirm this?
In the meantime, I've disabled that function and will see if the lock-up occurs again.
I'm curious where you were going with the question about the navbar. Could you tell me more about what you were thinking it might have been?
I went ahead and disabled the 'block status bar' function of the Cerberus app and the problem has not resurfaced in over two days (it was occurring several times daily). Although I can't definitively prove it, I think the culprit was the app.
Thanks for the time and assistance!
computerslayer said:
I went ahead and disabled the 'block status bar' function of the Cerberus app and the problem has not resurfaced in over two days (it was occurring several times daily). Although I can't definitively prove it, I think the culprit was the app.
Thanks for the time and assistance!
Click to expand...
Click to collapse
Sorry I didn't get back to you I read this a while back and totally thought I responded. Yeah anything that hides the status bar or navbar from the system UI at all times is known to cause wake issues. On my essential phone it would require me to restart it to actually get the screen to come back on. It's called the deep sleep of death or something haha
crixley said:
Sorry I didn't get back to you I read this a while back and totally thought I responded. Yeah anything that hides the status bar or navbar from the system UI at all times is known to cause wake issues. On my essential phone it would require me to restart it to actually get the screen to come back on. It's called the deep sleep of death or something haha
Click to expand...
Click to collapse
Hello Crixley,
No worries at all - I'm always grateful when anyone responds around here because I know that we're all balancing regular life and our hobby time!
I'm relieved to hear that it is a known issue, though I'm going to miss the functionality! I wish Google would build some kind of equivalent security measure so that the network state can't be changed while the phone is locked. I'm guessing that this issue is exactly why they haven't gotten to it (yet?).
Thanks for your time & support, both here with my issue and across the forums.
Peace,
Computerslayer
computerslayer said:
Hello Crixley,
No worries at all - I'm always grateful when anyone responds around here because I know that we're all balancing regular life and our hobby time!
I'm relieved to hear that it is a known issue, though I'm going to miss the functionality! I wish Google would build some kind of equivalent security measure so that the network state can't be changed while the phone is locked. I'm guessing that this issue is exactly why they haven't gotten to it (yet?).
Thanks for your time & support, both here with my issue and across the forums.
Peace,
Computerslayer
Click to expand...
Click to collapse
I'm glad to hear it's fixed for you!
I try to help as much possible, I remember how good it was to have people help me when I needed it and sometimes I need a hand as well.
Well, as the title says, everytime I pick up my phone I feel a little vibration (and no, I don't have the "smart alert" thing turned on). I tried not to be worried about it but I can't not notice it. Any ideas?
TonyGzl92 said:
Well, as the title says, everytime I pick up my phone I feel a little vibration (and no, I don't have the "smart alert" thing turned on). I tried not to be worried about it but I can't not notice it. Any ideas?
Click to expand...
Click to collapse
I get this too if I have missed calls. I turned off the settings in phone app and it still does it.
TonyGzl92 said:
Well, as the title says, everytime I pick up my phone I feel a little vibration (and no, I don't have the "smart alert" thing turned on). I tried not to be worried about it but I can't not notice it. Any ideas?
Click to expand...
Click to collapse
So i switched off smart alert and it stopped doing it for me.
borijess said:
I get this too if I have missed calls. I turned off the settings in phone app and it still does it.
Click to expand...
Click to collapse
May be you guys should try turning off the setting and restart, if that doesnt solve the problem go to recovery mode and clear cache. Let us know if any of that works.
On a side note: I have been facing weird ass issues with this phone just today my phone wont go to mute by using volume key while receiving a call. Like someone calls you and your phone is ringing, you just want to silence the ringtone you can use volume key (Press once), Flip the phone or put your palm over it (If you have the settings on). I tried multiple restarts and switched on and off the settings many times. It was fixed when i restarted my phone to download mode (This happened by mistake i wanted to go to recovery) anyhow that fixed it.
warriorvibhu said:
So i switched off smart alert and it stopped doing it for me.
May be you guys should try turning off the setting and restart, if that doesnt solve the problem go to recovery mode and clear cache. Let us know if any of that works.
On a side note: I have been facing weird ass issues with this phone just today my phone wont go to mute by using volume key while receiving a call. Like someone calls you and your phone is ringing, you just want to silence the ringtone you can use volume key (Press once), Flip the phone or put your palm over it (If you have the settings on). I tried multiple restarts and switched on and off the settings many times. It was fixed when i restarted my phone to download mode (This happened by mistake i wanted to go to recovery) anyhow that fixed it.
Click to expand...
Click to collapse
^^ This, it's the "Smart Alert" setting, to inform you you have an unread notification waiting
*Detection* said:
^^ This, it's the "Smart Alert" setting, to inform you you have an unread notification waiting
Click to expand...
Click to collapse
But I have that setting turned off.
TonyGzl92 said:
But I have that setting turned off.
Click to expand...
Click to collapse
Did you follow the steps i suggested ?
Also try clearing system cache in the boot menu.
If that doesn't get it, modify the appropriate notification setting, lol.
That can be a daunting task but sort of fun because you can streamline your notification settings as you do so.
*Detection* said:
^^ This, it's the "Smart Alert" setting, to inform you you have an unread notification waiting
Click to expand...
Click to collapse
warriorvibhu said:
Did you follow the steps i suggested ?
Click to expand...
Click to collapse
Yeah, I've done that
blackhawk said:
Also try clearing system cache in the boot menu.
If that doesn't get it, modify the appropriate notification setting, lol.
That can be a daunting task but sort of fun because you can streamline your notification settings as you do so.
Click to expand...
Click to collapse
What do you mean about the appropriate notification setting?
TonyGzl92 said:
Yeah, I've done that
What do you mean about the appropriate notification setting?
Click to expand...
Click to collapse
That's the trick.
Figuring out which app is responsible.
blackhawk said:
That's the trick.
Figuring out which app is responsible.
Click to expand...
Click to collapse
There are apps that log notifications so you can just check the log and quickly determine what is causing the notification even if nothing is showing on-screen
*Detection* said:
There are apps that log notifications so you can just check the log and quickly determine what is causing the notification even if nothing is showing on-screen
Click to expand...
Click to collapse
If they catch it. Consider which sensors and operation triggers it, cause and effect, to narrow it down.
Playing with Android is fun... Android witch hunts are how you really learn about Android's gooey layer tricks.
Google searches on older Notes and parallel Samsung models can turn up answers many times.
This model is too recent; so not near as much online troubleshooting info. Google searches encompass threads on this forum as well so it can be a good way to find the needle in the Android stack. Do not time limit searches.
On my 10+ with it's baffling bt poor audio I found the answer with something written about the N9.
Many of these issues are long standing.
Samsung finally fixed the bt settings issue in a Wearables update. That took years.
Only persistence is omnipotent...
I figured that out by chance..
It's the edge-compass app
Just delete it from edge apps and it'll go away.. cheers
blackhawk said:
That's the trick.
Figuring out which app is responsible.
Click to expand...
Click to collapse
*Detection* said:
There are apps that log notifications so you can just check the log and quickly determine what is causing the notification even if nothing is showing on-screen
Click to expand...
Click to collapse
samialhout said:
I figured that out by chance..
It's the edge-compass app
Just delete it from edge apps and it'll go away.. cheers
Click to expand...
Click to collapse
Well, I've checked all that and nothing, I don't even have the compass edge panel. But I think I'm able to replicate the issue, it mostly happens when my phone is face down on a surface and I pick it up and turn it to me, I don't have a case on it yet and I'm starting to think that it might have something to do with the edge screen but so far no luck
Use good lock. It has a module to detect vibrations and tell you what they are
Nice catch
TheMadScientist said:
Nice catch
Click to expand...
Click to collapse
Yeah, I installed it yesterday. But no vibrations are registered there so honestly I don't even know what to think now.
On the other hand when I switched from my note 10 plus I used smart switch, and now I'm thinking I should do a fresh start on my n20U.
*Detection* said:
There are apps that log notifications so you can just check the log and quickly determine what is causing the notification even if nothing is showing on-screen
Click to expand...
Click to collapse
Exactly check if you have Notistar from good lock switched on. That cache might need clearing.
I just go with it lol. I'm nutz. I'll feel my **** vibrate in my pocket when its sitting on the table. So I don't pay much mind to phantom vibrations. ???
TheMadScientist said:
I just go with it lol. I'm nutz. I'll feel my **** vibrate in my pocket when its sitting on the table. So I don't pay much mind to phantom vibrations. ?
Click to expand...
Click to collapse
It does suck some battery life though. It's one of the features I disable on my 10+ mostly because I find it annoying.
It's cool though how much you can customize notification behavior; one of the biggest reasons to go with Samsung is customization.
I play around with Settings a lot.. never crashed a load doing it. It's just occasionally gets time consuming to sort it out.
I need some advice on troubleshooting this one.
Brand new P7P, turned on Tap to Wake and "Always show time and info" on the lockscreen. It only ever works after a reboot *before* I log in the first time. Once I log in,that's it,screen is black when I lock it and it won't tap to wake.
I've removed the screen protector in case it was messing with the proximity sensor. I ran the phone in safemode and both *do* work in safemode,so I suspect it's an app on startup causing this.
What I need help with is how can I whittle down the culprit without removing all the apps one by one? Is there an app that will allow me to stop apps starting up at boot time and add them one by one?
dunetails said:
I need some advice on troubleshooting this one.
Brand new P7P, turned on Tap to Wake and "Always show time and info" on the lockscreen. It only ever works after a reboot *before* I log in the first time. Once I log in,that's it,screen is black when I lock it and it won't tap to wake.
I've removed the screen protector in case it was messing with the proximity sensor. I ran the phone in safemode and both *do* work in safemode,so I suspect it's an app on startup causing this.
What I need help with is how can I whittle down the culprit without removing all the apps one by one? Is there an app that will allow me to stop apps starting up at boot time and add them one by one?
Click to expand...
Click to collapse
@zetsumeikuro wait,I don't get what's so funny?
Mine works on every part of my lock screen.
Any chance you're using lift to wake? Besides that, I have everything else on the same as you.
Edit: Just reread your post. Do you have a lot of apps? You could force stop every single one of them and test to see what happens to be sure that it's an app.
Curiousn00b said:
Mine works on every part of my lock screen.
Any chance you're using lift to wake? Besides that, I have everything else on the same as you.
Edit: Just reread your post. Do you have a lot of apps? You could force stop every single one of them and test to see what happens to be sure that it's an app.
Click to expand...
Click to collapse
Yeah I have quite a few,but I think I'd rather try this first than start uninstalling and reinstalling the lot.
Not fixed,but getting somewhere. This is related to Bluetooth in some way.
If I turn off Bluetooth and reboot the phone,AOD works. I unlock the phone,it still works.
If I turn on Bluetooth AOD immediately breaks again until I turn off Bluetooth AND reboot.
I thought it might be my fitness band so disconnected and uninstalled the app, but the problem persisted. I have no other devices permanently using Bluetooth, so I'm starting to think this is a Bluetooth bug rather than a specific app now
dunetails said:
Not fixed,but getting somewhere. This is related to Bluetooth in some way.
If I turn off Bluetooth and reboot the phone,AOD works. I unlock the phone,it still works.
If I turn on Bluetooth AOD immediately breaks again until I turn off Bluetooth AND reboot.
I thought it might be my fitness band so disconnected and uninstalled the app, but the problem persisted. I have no other devices permanently using Bluetooth, so I'm starting to think this is a Bluetooth bug rather than a specific app now
Click to expand...
Click to collapse
If the fitness band allows you to take pictures remotely, it is possible that it recognizes it as a keyboard and that this interferes due to some bugs
PaulBW said:
If the fitness band allows you to take pictures remotely, it is possible that it recognizes it as a keyboard and that this interferes due to some bugs
Click to expand...
Click to collapse
Good point. This is why I tried to uninstall the app and disconnect the fitness band entirely,just to rule it out. Unfortunately,even once uninstalled,after a reboot with BT off AOD worked,but the moment I turned BT on AOD broke.
I can't think of any other apps using the BT at the moment but having a think. Will post more info if/when I get it.
Finally figured it out thanks to the hint by LaNy_6. This *is* down to Android Auto, but it’s not immediately obvious how or why.
To fix I went to Settings > Apps
Select See All Apps
From the top right overflow menu select Show System
Scroll Down to Android System
Select Notifications
Ensure Car Mode is selected
When I did this, I saw LaNy_6’s screenshot for the Android System notification that says “Driving App is running – tap to exit driving app” in my notification shade.
After doing this, AOD/tap to wake/lift to wake all suddenly work as expected.
Please note that upon rebooting the Driving App notification shows again and you have to tap it to go away. Again,no idea why.
I have no idea why, but I’m guessing every reboot the phone was put in to driving mode. I have never connected it to a car, there’s no reason for this to happen, but because I didn’t see the notification it never got exited from it seems. There’s no other indicators that it’s in driving mode, the phone works as normal other than the AOD problem.