Develop Bugs

Android Device Manager - Ring function does not work properly

I have Google Apps and am trying to ring my device remotely while its set to vibrate. It rings once at full volume then stops (its supposed to ring for five minutes at full volume). If I call my phone it makes a quick chirp and then goes into silent mode from vibrate (its supposed to stay at full volume). Can someone please test theirs?

hytekjosh said:
I have Google Apps and am trying to ring my device remotely while its set to vibrate. It rings once at full volume then stops (its supposed to ring for five minutes at full volume). If I call my phone it makes a quick chirp and then goes into silent mode from vibrate (its supposed to stay at full volume). Can someone please test theirs?
Click to expand...
Click to collapse
Works fine for me.

In working with Google, the resolution was:
Paid Google Apps should use: https://www.google.com/apps/mydevices
Regular Android Consumers: https://www.google.com/android/devicemanager
Using the Google Apps link all the functionality works great.

It did the same thing for me. One ring at full volume, then fell back to silent.
The Google ID i have tied to this phone is my personal one, so I can only use the "Regular Android Customers"

Working fine here.

My wife uses the HTC One on T-Mobile, and we see this behavior on her phone as well. I don't remember my One on Verizon having this issue, but in fairness I never tried it until after I flashed CM 10.2. Anyway, it's not specific to the Verizon edition. Whether that's comforting or not, I can't say.

Anthrax79 said:
It did the same thing for me. One ring at full volume, then fell back to silent.
The Google ID i have tied to this phone is my personal one, so I can only use the "Regular Android Customers"
Click to expand...
Click to collapse
Same here. One ring only.

Old thread but the same for me.
Rings once.

steven_1214 said:
Old thread but the same for me.
Rings once.
Click to expand...
Click to collapse
Same here. Rings once, then unable to trigger again. Not sure what the retry threshold is supposed to be.

Just tested it with my Note3 and it does the same, rings only once no matter if the phone is set to vibrate or not. Although it seems to track it fine even though I'm indoors.
But I already had the chance to put this to good use a few weeks ago to find my father's S3. He called one evening upset and said he thinks he lost his phone on the golf course somewhere. I started to get mad at myself for not having installed one of the tracker apps on his phone. It was already near dark and we have heavy dew that would have ruined the phone overnight. So I called Verizon and asked if there was anything we could do. The rep asked if he had a Google account setup on the phone and whether or not GPS was on. I said yes to both and he instructed me how to login at Google.com and track the phone with Android Device Manager. It worked perfect. It pin-pointed the phone of the golf course and my father and I went to retrieve it. It was really dark by then and I was using my phone, signed into his Google account, to see the map. We went to where the map indicated the phone was but still didn't see it even with flashlights. So I clicked the ring option and we heard his ringtone clearly in the quiet darkness. It was less than 10 feet from where we were looking and it was lying face down it thick grass. Had it not been for the ringer, we may have overlooked it and just assumed the mapped location wasn't very accurate.
So that story had a happy ending and at least the ring option worked on the S3, but it still only rings once on my Note3. And when I immediately click the ring option a second time it doesn't ring at all. If I wait 30secs to a minute and try it again, it will ring but only once. My father had a song ringtone on his S3 and I just have one of the default ringtones on my Note3. Wonder if that makes a difference? Will have to test it sometime.
Also I'm curious to see if the device tracker will work well with GPS turned off? The rep asked me if GPS was turned on, and I knew my father gets good battery life and just leaves his GPS, Bluetooth, and WiFi on. I was so excited to see it track the phone that I forgot to ask if it would work with the GPS turned off. The battery on the Note3 also lasts about 2 days even with GPS and Wifi on, so I'm planning on leaving GPS on just in case.

So, with a Galaxy Note 5, just updated to Marshmallow 6.0.1, I can't get it to ring at all (didn't try with 5.1.1).

0x6A7232 said:
So, with a Galaxy Note 5, just updated to Marshmallow 6.0.1, I can't get it to ring at all (didn't try with 5.1.1).
Click to expand...
Click to collapse
Is Android device manager allowed as a device manager under settings->security ?
Sent from my XT1575 using Tapatalk

dottat said:
Is Android device manager allowed as a device manager under settings->security ?
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
Yes it is.

Phone goes into Do Not Disturb mode on its own

I'm having issues, my phone goes into "Do Not Disturb" mode on it's own. I think it has something to do with the Android wear connection to my watch. I've reset the watch and checked to make sure it isn't set to turn on that mode. But still at random times my phone goes quiet. Curious to hear if anyone has had the same issue or a cure. Thanks!

yes i have the same issue with pixel xl & Huawei watch 🤔
Sent from my Pixel XL using XDA-Developers mobile app

I have the same issue as well. It also happens on calls.

It's a new feature in 7.1.1

You have to disable the automatic rules that are created in settings. I just deleted all the premade ones in there and my issue went away.

sassmk2 said:
You have to disable the automatic rules that are created in settings. I just deleted all the premade ones in there and my issue went away.
Click to expand...
Click to collapse
I have an Android Wear watch and have the same problem. Are you saying the deleting the built-in Weekend, Weeknight, and Event rules fixed it for you?

JimSmith94 said:
I have an Android Wear watch and have the same problem. Are you saying the deleting the built-in Weekend, Weeknight, and Event rules fixed it for you?
Click to expand...
Click to collapse
Yes, Fixed it for me

sassmk2 said:
Yes, Fixed it for me
Click to expand...
Click to collapse
Thanks, I just deleted mine, so we'll see if it helps me.

JimSmith94 said:
Thanks, I just deleted mine, so we'll see if it helps me.
Click to expand...
Click to collapse
I have done this too and my phone goes into DnD mode when I make or take phone calls. It becomes an issue when I get off the phone about 50% of the time it stays in DnD mode and I have to manually turn DnD mode off. Anyone found a work around for this yet?

I posted this to fix it. Its a hidden menu https://forum.xda-developers.com/pixel-xl/how-to/how-to-off-disturb-section-using-volume-t3598695

Has anyone solved this? My Pixel XL keeps turning DND on when I've manually turned it off. I do not use a smart watch or any other accessory. And I have already deleted the single Automatic Rule which I programmed (my phone didn't come with any pre-installed rules). I'm a doctor and keep missing super-important phone calls because my phone isn't ringing. (It's sitting in a cradle on my desk, charging -- so I know I'm not accidentally hitting the volume down button.)
Thanks!
Fitz

itfitz01 said:
Has anyone solved this? My Pixel XL keeps turning DND on when I've manually turned it off. I do not use a smart watch or any other accessory. And I have already deleted the single Automatic Rule which I programmed (my phone didn't come with any pre-installed rules). I'm a doctor and keep missing super-important phone calls because my phone isn't ringing. (It's sitting in a cradle on my desk, charging -- so I know I'm not accidentally hitting the volume down button.)
Thanks!
Fitz
Click to expand...
Click to collapse
The only sure fire way, if you're sure it's not an app you installed or setting you set, is to factory reset including wiping system OR flashing stock via fastboot. I mean technically if you had the time and you didn't wanna do all that you could boot the phone into safe mode, then wait and see if it does the same thing. If it doesn't , you know it's an app you have installed.

Proximity Sensor fail!

I'm on my second Pixel 3 XL after an RMA for distorted bottom speaker.
I'm now noticing that the proximity sensor is stopping working when you bring the phone to your ear in a phone call and thus, leaving the screen visible and active.
A restart does fix this but only for about a day!
Has anyone else noticed this issue?
I didn't notice this on the unit that I sent back!
Thanks.

Do you have a screen protector covering the proximity sensor? It may not be working correctly if it's covered.
Is it only during calls or all the time? A few other people have posted about prox issues with the smaller Pixel 3, here's one thread:
https://forum.xda-developers.com/pixel-3/help/proximity-sensor-keeos-display-off-t3864055
Seems it can be fixed by cleaning the area around the sensor if you don't have a screen protector.

fury683 said:
Do you have a screen protector covering the proximity sensor? It may not be working correctly if it's covered.
Is it only during calls or all the time? A few other people have posted about prox issues with the smaller Pixel 3, here's one thread:
https://forum.xda-developers.com/pixel-3/help/proximity-sensor-keeos-display-off-t3864055
Seems it can be fixed by cleaning the area around the sensor if you don't have a screen protector.
Click to expand...
Click to collapse
Thanks for the suggestions.
No screen protector fitted or anything obscuring the sensor.
Next time it happens, I'll check to see if it might need cleaning.
One theory I have, is that this phone has been upgraded with the November patch and maybe there's something in there that has caused this issue.
Has anyone else noticed this after the Nov update?
Thanks.

jscsltd said:
I'm on my second Pixel 3 XL after an RMA for distorted bottom speaker.
I'm now noticing that the proximity sensor is stopping working when you bring the phone to your ear in a phone call and thus, leaving the screen visible and active.
A restart does fix this but only for about a day!
Has anyone else noticed this issue?
Click to expand...
Click to collapse
I just got the phone yesterday and am seeing the exact same behavior. It works and then it does not. Reboot temporarily fixes it.

I know there is a bug when using the pixel buds and unplugging them either before a call or during it would stop the proximity sensor from working.
a reboot was the only thing that would fix this issue for me

xweb10 said:
I just got the phone yesterday and am seeing the exact same behavior. It works and then it does not. Reboot temporarily fixes it.
Click to expand...
Click to collapse
I've RMA'd the phone that had this issue and still have the issue.
It does seem quite random. I'm hoping Dec Update will fix this along with the distorted bottom speaker.
I think that this issue is software related, as I tried using an App that shows when the proximity sensor is triggered and this seemed to work as expected.

How do I test my proximity sensor?

jscsltd said:
I've RMA'd the phone that had this issue and still have the issue.
It does seem quite random. I'm hoping Dec Update will fix this along with the distorted bottom speaker.
I think that this issue is software related, as I tried using an App that shows when the proximity sensor is triggered and this seemed to work as expected.
Click to expand...
Click to collapse
I am trying to get to the bottom of this. Do you happen to have a Samsung Gear watch? I have the S3 and removed the "phone calls" option from the Pixel Bluetooth menu and so far this issue has not occured, but I am still testing.
---------- Post added at 06:25 AM ---------- Previous post was at 06:24 AM ----------
swieder711 said:
How do I test my proximity sensor?
Click to expand...
Click to collapse
There are apps on the play store.

That's interesting regarding the Gear S3 watch.
Yes, I do have one of these watches.
I'll try what you've suggested and report back with the results.
What made you think it could be an interaction with the Gear S3?
Thanks.

jscsltd said:
That's interesting regarding the Gear S3 watch.
Yes, I do have one of these watches.
I'll try what you've suggested and report back with the results.
What made you think it could be an interaction with the Gear S3?
Thanks.
Click to expand...
Click to collapse
I have a pixel 2xl, as well. I looked at the Bluetooth setting on that phone when connected to my S3 and noticed the "phone calls" option was disabled.
I was looking at all apps that access the dialer or phone calls. Really just a guess.

xweb10 said:
I have a pixel 2xl, as well. I looked at the Bluetooth setting on that phone when connected to my S3 and noticed the "phone calls" option was disabled.
I was looking at all apps that access the dialer or phone calls. Really just a guess.
Click to expand...
Click to collapse
I see....good spot.
If I do disable this setting in Bluetooth though, will this just disable the ability to take voice calls on the watch using the internal microphone and speaker or will it as well, stop the watch from vibrating when a call comes in?

jscsltd said:
I see....good spot.
If I do disable this setting in Bluetooth though, will this just disable the ability to take voice calls on the watch using the internal microphone and speaker or will it as well, stop the watch from vibrating when a call comes in?
Click to expand...
Click to collapse
I believe it only disables the ability to take voice calls on the watch. It continues to vibrate when a call comes through.
I forgot: Also boot to Safe Mode first. I do not have a reason, but that is the path I took.

xweb10 said:
I believe it only disables the ability to take voice calls on the watch. It continues to vibrate when a call comes through.
I forgot: Also boot to Safe Mode first. I do not have a reason, but that is the path I took.
Click to expand...
Click to collapse
That's a shame that you can't take voice calls on the watch as that's a feature I do use at times.
Either, way I disabled it after more issues with the screen not blanking and will see how it goes.
I also had a new issue, where I'm in a call and could not switch to Speaker. I would choose the Speaker option but it just would not switch.
I'm wondering if you've had this same issue when you had your Gear S3 watch setup to take calls?

jscsltd said:
That's a shame that you can't take voice calls on the watch as that's a feature I do use at times.
Either, way I disabled it after more issues with the screen not blanking and will see how it goes.
I also had a new issue, where I'm in a call and could not switch to Speaker. I would choose the Speaker option but it just would not switch.
I'm wondering if you've had this same issue when you had your Gear S3 watch setup to take calls?
Click to expand...
Click to collapse
I am able to switch to speaker but I never have my S3 set to take calls. I have not gone full on Michael Knight yet.
BTW My proximity problems are gone. Must be the Bluetooth S3 issue.

I've had to RMA mine due to the bottom speaker crackling. I purchased from carphonewarehouse in the uk so have had to to a standard replacement. Does anyone know if they will send the replacement out before receiving the faulty one? They did this last year with the 2xl. It's not due to get back to them until next Thursday so hoping I won't have to wait too long.

baginz10 said:
I've had to RMA mine due to the bottom speaker crackling. I purchased from carphonewarehouse in the uk so have had to to a standard replacement. Does anyone know if they will send the replacement out before receiving the faulty one? They did this last year with the 2xl. It's not due to get back to them until next Thursday so hoping I won't have to wait too long.
Click to expand...
Click to collapse
I've had my pixel 3 XL replaced twice due to distorted bottom speaker by Carphone Warehouse Business.
They will deliver a replacement and then collect your faulty unit a few days later, in order to allow you to transfer your data to the new unit.

xweb10 said:
I am able to switch to speaker but I never have my S3 set to take calls. I have not gone full on Michael Knight yet.
BTW My proximity problems are gone. Must be the Bluetooth S3 issue.
Click to expand...
Click to collapse
I've switched off the ability to take calls on the S3 and can now switch to phone speaker with ease.
I'm hoping I can re-enable the S3 capability when an update by either Google or Samsung fixes the issue.

jscsltd said:
I've had my pixel 3 XL replaced twice due to distorted bottom speaker by Carphone Warehouse Business.
They will deliver a replacement and then collect your faulty unit a few days later, in order to allow you to transfer your data to the new unit.
Click to expand...
Click to collapse
Sorry I wasn't clear I've done an RMA with google so just wanted to see if anyone else had done the same even though they didn't purchase direct from them. Last year with the 2XL they would send the new one out once the faulty device was sent at the post office, they must have known from the tracking. This time it's via UPS and is going straight to Poland! Not due to arrive until the 4th. If a replacement doesn't get sent out tomorrow or Monday looks like I'll be waiting a while. I even noticed screen burn in when resetting it. Changed to Samsung displays and still burn in from the nav bar just like last year. I wish I'd gone back to carphonewarehouse now to get a replacement!

Wow, I never would have thought of the Samsung gear watch interfering. I have the newest one (the one after the s3) and had the same issue with the screen staying awake while on a call. It was the one thing I really didn't like about the phone. Seems like the symptoms are the same Pixel 3xl, verizon, Samsung Galaxy watch and a restart fixes the issue for a while. I just tried what you suggested. Thank you very much for posting your idea.

I've been dealing with a similar issue, but not exactly,
My screen turns off when I hold the phone against my ear, but the display still seems "active".
My cheek is still bringing the notification area down, toggling my quick settings or even going into the settings app (if my phone was unlocked while I answered a call).
It's been super constant and annoying because one time my flashlight was toggled in an elevator, which was a bit awkward.
Another time my clock app opened and changed my alarm time and then turned it off entirely.
Luckily I could feel the vibration so I knew something was going on but this is a really strange issue.
I have already setup a RMA since the phone has a speaker distortion problem as well, so we'll see what happens once the new device arrives.

Proximity sensor/pocket dial protection

I have been using my 3a xl for a couple weeks and very happy overall with the speed and performance. I am having one issue trying to overcome that's very disappointing. I do a lot of of walking with my phone in my pocket. When ever I get a call or notification while my phone is in any of my pockets it will either answer it or because it's moving around it will go thru the menus etc. Even if I don't pull my phone out it will always do this. The pocket dial/proximity programming is not good. If you test the prox sensor by covering it up you can open, unlock, make calls etc. with it covered. I am coming from a LeMax 2 and never ever had a single problem with that phone. It had a setting in there and wouldn't allow you to accidently open, unlock, do anything if the sensor was covered. Does anyone have any workarounds for this or insight. I should be able to carry it in my pocket without it doing this. Thanks for any input.

You must have a detective prox sensor or something else is not working correctly with your phone. When I cover my prox sensor (with my hand or in my pocket) the screen does not come on for notifications, calls, or when I tap to wake.

When I cover prox sensor and unlock phone with fingerprint the screen comes on too. Does yours do that as well?

retrov said:
When I cover prox sensor and unlock phone with fingerprint the screen comes on too. Does yours do that as well?
Click to expand...
Click to collapse
Yes

I just tested my phone today and my screen does wake for incoming calls even when the prox sensor is covered.
This is very annoying.
It does not wake for notifications.

Very annoying for me as well. I guess it's the software program. With that sensor covered like in your pocket it shouldn't allow that to happen. Thanks for letting me know at least I know my phone isn't defective.

My wife's Moto X4 behaves the same way.
If you want, you can install Xposed and GravityBox, it has an option to use the proximity sensor when deciding to wake the decide (see attached screenshot). It will keep the screen off for incoming calls when the sensor is covered.

creeve4 said:
My wife's Moto X4 behaves the same way.
If you want, you can install Xposed and GravityBox, it has an option to use the proximity sensor when deciding to wake the decide (see attached screenshot). It will keep the screen off for incoming calls when the sensor is covered.
Click to expand...
Click to collapse
I thought Xposed wasn't available for Pie except through some unofficial closed source buggy Magisk extensions. Are you running that? I'm not sure I trust closed source on a rooted phone....

duh1 said:
I thought Xposed wasn't available for Pie except through some unofficial closed source buggy Magisk extensions. Are you running that? I'm not sure I trust closed source on a rooted phone....
Click to expand...
Click to collapse
It's all open source now. I have not experienced any bugs, it's working really well for me.
Search the magisk repo for Riru - Exposed. I use the sandhook variant. You can find links to more information in the module description.
GravityBox Pie has a thread on XDA.

retrov said:
With that sensor covered like in your pocket it shouldn't allow that to happen. Thanks for letting me know at least I know my phone isn't defective.
Click to expand...
Click to collapse
Sounds like an annoying bug to me as well.
Google / Pixel has a bug reporting system...
https://support.google.com/pixelphone/answer/6398243/
If we all submit reports, hopefully they'll take notice and the issue will be fixed in an update...

Just submitted a report on the issue. Thanks

Try the gravity screen app & see if it fixes your issues. I use it & the phone doesn't wake in my pocket for text notifications - but I'm not sure how it will respond to phone calls/notifications; it has options for proximity sensor & a "pocket sensor" feature as well.

retrov said:
Just submitted a report on the issue. Thanks
Click to expand...
Click to collapse
If we want this bug fixed in future updates, everyone should send in a report, especially with Google, squeeky wheel gets their attention...

Anyone that has a pixel 3a 3axl please submit a report on this issue.

My Pixel 3a ja behaving the same way. Coming from a OnePlus 5 with a splendid pocket mode this phone is really getting on my nerves. I love everything about this phone but the constant pocket answering is really bad. Thinking about stop using it...
I've tried every app in Play named pocket mode but nothing seems to work properly.

I've submitted feedback report a couple times hopefully everyone on here can do the same. Won't get fixed until they update on there end. That's the only bad thing I don't like about this phone so far.

Sent.
FYI - for others looking to do this, you file the report under your phone's Settings/About Phone/"Send feedback about this device"

My biggest issue isn't answering in my pocket, but when it's ringing and I pull it out of my pocket, it will see a swipe down action this rejecting the call... Happens to me at least once a day. I really hope this is fixed in Android 10 next week.

acejavelin said:
My biggest issue isn't answering in my pocket, but when it's ringing and I pull it out of my pocket, it will see a swipe down action this rejecting the call... Happens to me at least once a day. I really hope this is fixed in Android 10 next week.
Click to expand...
Click to collapse
Android 10 didn't fix this. I really hate Google right now.

I keep my current N6 phone in a wallet like case with a front cover. Do you guys think that might help?

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

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

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

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

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

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

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

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

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

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