How's Android auto working with the chipset
sutty86 said:
How's Android auto working with the chipset
Click to expand...
Click to collapse
With this chipset? It works fine with my Chevy Malibu.
Sent from my Pixel 3a XL using Tapatalk
Its been a bit buggy when using the 'phone as a display for me. On a head unit it seems OK.
Works fine for me, every now and then it doesn't automatically close when I disconnect from my car (2011 Mazda 3, so using the phone as the display). 100% auto-start, 90% auto-close.
I've started using Android Auto on my phone when driving. I don't have a head unit that supports it - I'm just using the phone's screen. I haven't had problems with it except for occasionally when it won't shut down when I disconnect from the car as Seamonkey described above. But that is pretty rare.
I also found that sometimes the app would close normally, but the Do Not Disturb mode stayed on. This was extra frustrating because it usually took awhile before I noticed it. To be honest, when I first started using AA I didn't know that AA turned DND on automatically. What a dumb thing to require! I understand the idea behind it, but at least let me opt out of the setting! I ended up writing a tasker profile to turn DND off when the app is opened, and also turn DND off when the app is closed (just as a safety measure).
Related
Hey guys. I was wondering if there's an easy way to make an NFC toggle such that when the tag is within range a) happens and when it goes out of range b) happens. Essentially I want my phone to into silent mode when i place it on my nightstand and go off silent mode when i remove the phone from the night stand.
I know a "workaround" is to make the tag toggle for each swipe but if possible I'd like to not have to swipe a second time to remove silent mode.
Any ideas?
Yeah, i'm looking for the same... i'm not sure if there is such a thing.
maybe one way would be for an app maker to have a feature where the nfc will be checked say every minute to see if it's still within range. if it is, leave the setting alone. if it's out of range, it will do the 'out of range' action. shouldn't draw much battery I don't think?
I want this feature so I can put a tag in my car so when i'm in the car, it will turn on bluetooth, and when I get the phone out of it's spot, it will turn BT back off. (so it's only on while i'm in the car)
razorseal said:
Yeah, i'm looking for the same... i'm not sure if there is such a thing.
maybe one way would be for an app maker to have a feature where the nfc will be checked say every minute to see if it's still within range. if it is, leave the setting alone. if it's out of range, it will do the 'out of range' action. shouldn't draw much battery I don't think?
I want this feature so I can put a tag in my car so when i'm in the car, it will turn on bluetooth, and when I get the phone out of it's spot, it will turn BT back off. (so it's only on while i'm in the car)
Click to expand...
Click to collapse
NFC tag to turn BT on, then use Tasker to turn BT off after it looses connection to your car BT device.
Sent from my Transformer TF101 using Tapatalk 2
Fallon said:
NFC tag to turn BT on, then use Tasker to turn BT off after it looses connection to your car BT device.
Sent from my Transformer TF101 using Tapatalk 2
Click to expand...
Click to collapse
that seems like a great app, but I don't think I ever paid 7 bucks for an app lol... and i've gotten some great apps for much less. just saying...
good idea though.
Tasker is well worth its money. You can replace so many apps with it that in the end you'll end up saving loads of money
XlAfbk said:
Tasker is well worth its money. You can replace so many apps with it that in the end you'll end up saving loads of money
Click to expand...
Click to collapse
I got the 25 dollar gift card from Google when I got the nexus, so I'm gonna get it now
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
+1 don't know if it exists but would be sweet
Sent from my SAMSUNG-SGH-I747 using xda premium
I wonder what the range would be if it worked this way.
Sent from my SCH-I535 using xda app-developers app
I've used this in my car
I've faced the same problem in my car.
I've put a tag on the phone mount, when touched it enables car mode.
I've used tasker to take the phone out of car mode when my bluetooth HFP get's disconnected (when car is turned off, or I'm more than 5 m' away).
I can also do the same when the phone is unplugged from the car charger.
It's not perfect, but will work unless you turn the car of without removing the phone, and then on again (no NFC tap to re-enable the car mode).
Hope this helps someone
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.
Was using my Nexus 7 today w/ Portezo case.
Turned off WiFi to save battery and opened it up again and noticed it turned on instantly. No delay or not turning on at all. Always had issues previously but every time so far it seems to work perfectly. Only difference now is im on KRT16S.
Curious if anyone else's smart covers are working properly now since updating to kit kat.
You should add a poll option, "I don't have a smart cover"
smellyfungus said:
Was using my Nexus 7 today w/ Portezo case.
Turned off WiFi to save battery and opened it up again and noticed it turned on instantly. No delay or not turning on at all. Always had issues previously but every time so far it seems to work perfectly. Only difference now is im on KRT16S.
Curious if anyone else's smart covers are working properly now since updating to kit kat.
Click to expand...
Click to collapse
I noticed this too after putting my tablet on airplane mode for the night. When I opened the smart cover in the morning , the screen instantly turned on. Before it would only wake if Bluetooth or wifi were turned on
Sent from my Nexus 5 using Tapatalk
I've been smashing my head over this to no avail. Prior to side loading 8.1, when my phone rang the caller and swipe up/down would appear on the lock screen, now it rings, but nothing on the lock screen till I wake it with the fingerprint sensor. Did I miss something? Was this changed? I've been through the settings and still can't see anywhere that I missed. This a security feature so no one can see who's calling till you hit the sensor? Any feed back would be appreciated.
I agree surprised more are not annoyed...lol
Doublecore said:
Well it seems it's only happening when connected to Bluetooth. I hadn't noticed since I'm connected to my headset all day at work. Disconnected from Bluetooth and had my wife call me...screen popped right on. So it's another Bluetooth bug I guess.
Click to expand...
Click to collapse
I tested incoming phone calls with and without bluetooth, and came to the same result. Since it's very annoying for the screen to not turn on, I ended up making a macro with Macrodroid to turn the screen on when a call comes in. This workaround will be sufficient for me until Google fixes the bug.
I posted on this same issue last week. It's the last update to Google Phone app that broke this. I don't have the time to report it to them...so hopefully it gets fixed!
https://forum.xda-developers.com/pixel-2-xl/help/google-phone-update-bug-t3718424
*Edit- To fix(?), uninstall the phone app and it will remove the update. Should work then. Of course you won't be able to use Duo for video calling within the dialer...but I couldn't care less about that.
I just had this happen yesterday. Here is a work around with Tasker and Secure Task to wake screen on incoming call.
Import it in Profiles tab in Tasker and make sure you have Secure Task and have it configured with adb.
5150jpd said:
I've been smashing my head over this to no avail. Prior to side loading 8.1, when my phone rang the caller and swipe up/down would appear on the lock screen, now it rings, but nothing on the lock screen till I wake it with the fingerprint sensor. Did I miss something? Was this changed? I've been through the settings and still can't see anywhere that I missed. This a security feature so no one can see who's calling till you hit the sensor? Any feed back would be appreciated.
Click to expand...
Click to collapse
This may be related to the Proximity Sensor bug introduced with 8.1. Do you have a screen protector on your device? Does it cover the PS?
Nope.. No protector on phone at all.
v12xke said:
This may be related to the Proximity Sensor bug introduced with 8.1. Do you have a screen protector on your device? Does it cover the PS?
Click to expand...
Click to collapse
It started for me on the Google Phone update to version 15 on Dec. 14th. I never had this issue on 8.1 that I did the OTA sideload when I got my phone on Dec. 4.
My proximity sensor is fine. Even with always on display, AOD goes off in pocket and turns back on when I pull it out. On a phone call the screen blanks when I put it to my ear and wakes when I pull it away from my head.
Yep -- I just ran into the problem today as well. I've got 8.1.0 on my Pixel 2 XL, and I get this behavior (display not waking up for incoming call) when connected via Bluetooth -- to my car, headphones (Sennheiser PXC 550) or to my Jabra Speak 710 BT speakerphone.
I considered trying Drupe or Truecaller, but then I read that packet sniffing tests show them sending your contacts data off their servers...so I think I'll wait for a fix from Google. Really annoying. There are a couple of threads on this in Google's product forums / Pixel User Community:
https://productforums.google.com/fo...QEn6fH0OI;context-place=forum/phone-by-google
https://productforums.google.com/forum/#!topic/phone-by-google/hdmLGWSMhSM;context-place=topicsearchin/phone-by-google/category$3Adevice-performance%7Csort:relevance%7Cspell:false
So far, Google doesn't appear to be weighing in with any useful commentary. The only "fix" for now seems to be "uninstalling" the phone app (which just reverts back to the OEM installed version) and then not accepting updates to the app. But I've read that this can spin up other issues.
jonstrong said:
Yep -- I just ran into the problem today as well. I've got 8.1.0 on my Pixel 2 XL, and I get this behavior (display not waking up for incoming call) when connected via Bluetooth -- to my car, headphones (Sennheiser PXC 550) or to my Jabra Speak 710 BT speakerphone.
I considered trying Drupe or Truecaller, but then I read that packet sniffing tests show them sending your contacts data off their servers...so I think I'll wait for a fix from Google. Really annoying. There are a couple of threads on this in Google's product forums / Pixel User Community:
https://productforums.google.com/fo...QEn6fH0OI;context-place=forum/phone-by-google
https://productforums.google.com/forum/#!topic/phone-by-google/hdmLGWSMhSM;context-place=topicsearchin/phone-by-google/category$3Adevice-performance%7Csort:relevance%7Cspell:false
So far, Google doesn't appear to be weighing in with any useful commentary. The only "fix" for now seems to be "uninstalling" the phone app (which just reverts back to the OEM installed version) and then not accepting updates to the app. But I've read that this can spin up other issues.
Click to expand...
Click to collapse
Have you tried the tasker profile from post #7 by Pkt_Lnt? That fixed it for me.
JimSmith94 said:
Have you tried the tasker profile from post #7 by Pkt_Lnt? That fixed it for me.
Click to expand...
Click to collapse
Thanks. If this issue goes on much longer, I'll probably try that. Oddly enough, despite having played with custom Android ROMs and modding over the years, I never used Tasker -- concerned that having the add'l service(s) running in the background around the clock would be more of a battery drain.
I updated my phone app yesterday, and the screen lights up again upon receiving a phone call. I disabled the macro that I made in Macrodroid just to make sure.
EMcTx said:
I updated my phone app yesterday, and the screen lights up again upon receiving a phone call. I disabled the macro that I made in Macrodroid just to make sure.
Click to expand...
Click to collapse
Thanks for the info. My phone app updated too, so I'll disable the Tasker profile and see if it lights up without it for me too.
Is there a xposed module to disable the stupid proximity sensor? I'm having some issues with it. It does not wake my screen up when I pull it away from my face.
EMcTx said:
I updated my phone app yesterday, and the screen lights up again upon receiving a phone call. I disabled the macro that I made in Macrodroid just to make sure.
Click to expand...
Click to collapse
JimSmith94 said:
Thanks for the info. My phone app updated too, so I'll disable the Tasker profile and see if it lights up without it for me too.
Click to expand...
Click to collapse
Reports on G+ state it fixes the issue. I've not seen v.16 yet.
https://plus.google.com/u/0/+ArtemRussakovskii/posts/byEHovfFbMj
My last name starts with "S" too, not sure why Jim gets priority over me. I always get updates late, which is why apk mirror is bookmarked. :good:
Pkt_Lnt said:
Reports on G+ state it fixes the issue. I've not seen v.16 yet.
https://plus.google.com/u/0/+ArtemRussakovskii/posts/byEHovfFbMj
My last name starts with "S" too, not sure why Jim gets priority over me. I always get updates late, which is why apk mirror is bookmarked. :good:
Click to expand...
Click to collapse
Oops, mine was still on v15 so thanks to you, I just installed v16 from your link. See there, you're still da man! :good::highfive:
JimSmith94 said:
Oops, mine was still on v15 so thanks to you, I just installed v16 from your link. See there, you're still da man! :good::highfive:
Click to expand...
Click to collapse
I can confirm V16 fixes the phone app and resolves this issue. It's being rolled out gradually, in waves. If you don't see the update on the Play Store, you can download it from APKmirror. Start here:
https://www.apkmirror.com/apk/google-inc/google-phone/
My issue is the exact opposite..
I answer a call on my bluetooth headset while the phone is in my pocket and buttons start being pressed so I have to take the phone out to lock the screen.
Any quick fixes on this issue?
I'm late to the party, but I fixed this on a Pixel 2 XL in our household. In the system's app settings I force stopped the phone app and cleared the app cache, then I disabled the "Flip to Shhh" feature in the phone app settings. If that fix works for you, please leave a reply so we can validate.
While I love my 7T, I still missing a feature from my Pixel 4 XL phone: The auto DND mode while driving. Is it possible somehow to use e.g. Tasker to auto enable DND while driving and then after a while stopped the car (e.g. 10 mins or so) disable DND mode again? Does such a profile already exists?
Thanks
I think create a profile that triggers the DND while your phone is connected with the car's BT and disable it after putting a Wait for 10 mins. If you are familiar with Tasker then you can create this profile very easily. If this is not you meant then please let me know.
Sent from my OnePlus7T using XDA Labs
niyonsv said:
I think create a profile that triggers the DND while your phone is connected with the car's BT and disable it after putting a Wait for 10 mins. If you are familiar with Tasker then you can create this profile very easily. If this is not you meant then please let me know.
Click to expand...
Click to collapse
I don't have Bluetooth in my car, I use AirPods Pro and Bose 700 ANC.
rasmusj said:
I don't have Bluetooth in my car, I use AirPods Pro and Bose 700 ANC.
Click to expand...
Click to collapse
Oh, then my suggestion won't work. But may I know in your Pixel phone how does it trigger the DND while driving? How does it know that you are driving?
Sent from my OnePlus7T using XDA Labs
niyonsv said:
Oh, then my suggestion won't work. But may I know in your Pixel phone how does it trigger the DND while driving? How does it know that you are driving?
Click to expand...
Click to collapse
It's a part of the DND on Pixels running Android 9 and above. Recently it's become a part of the Google Play Services. You just simply add it as a DND profile and then you can set the properties.
I guess it knows when you drive above 20 km/h and when you've stopped moving for about 7-10 minutes it disables the DND driving profile if it was already disabled.
A little like it works on iOS devices. Quite simple and genious, I kind of like it. Set and forget ?
rasmusj said:
It's a part of the DND on Pixels running Android 9 and above. Recently it's become a part of the Google Play Services. You just simply add it as a DND profile and then you can set the properties.
I guess it knows when you drive above 20 km/h and when you've stopped moving for about 7-10 minutes it disables the DND driving profile if it was already disabled.
Click to expand...
Click to collapse
I think it is a Pixel only feature and that is built into it. I couldn't find it in my phone. So I think there's no way to automatically turn it on at present. Lemme check if it can be done using Tasker or any plugin.
EDIT: Yes, just read that it is a Pixel only feature.
Sent from my OnePlus7T using XDA Labs
niyonsv said:
I think it is a Pixel only feature and that is built into it. I couldn't find it in my phone. So I think there's no way to automatically turn it on at present. Lemme check if it can be done using Tasker or any plugin.
EDIT: Yes, just read that it is a Pixel only feature.
Click to expand...
Click to collapse
Darn ?* Of course it is ?* .... Oh well, thanks for trying.