Does anyone know how to get this feature to work on the LG G3. I had it working on my GS5, Nexus 5 and Moto X. I've gone into the settings in Google Now, checked all the check-marks and did the voice training but for the life of me it will not respond if the screen is locked.
That only works from the lockscreen while the phone is plugged into a charging device. It's a limitation implemented by Google.
I just tried it with my own G3, while plugged in, and it worked just fine.
That's really bizarre and downright stupid. I used it all the time in the car on my Samsung phones.
ranphi said:
That only works from the lockscreen while the phone is plugged into a charging device. It's a limitation implemented by Google.
I just tried it with my own G3, while plugged in, and it worked just fine.
Click to expand...
Click to collapse
will_8907 said:
That's really bizarre and downright stupid. I used it all the time in the car on my Samsung phones.
Click to expand...
Click to collapse
Consensus on why they did it that way is that it was to prevent battery life from getting eaten up. The Moto X has a dedicated chip for it's own "always listening" service to help prevent the battery from draining rapidly with the service being enabled, so it's in a unique situation in this particular matter.
It will work as long add the screen is on. I.E. the phone can be locked but the screen needs to be on, unless its being used via Bluetooth as others have mentioned.
Sent from my LG-D850 using XDA Premium 4 mobile app
What's with Bluetooth chewing up the battery? If Bluetooth is on for Android Wear, it will basically always be the top battery user. I don't think this is related to my watch because I see the same issue on my Nexus 9 running 6.0.1.
I'd like to keep it on for my smart watch but this is starting to drive be nuts. Anybody know of a fix?
Sent from my Nexus 5X using Tapatalk
I am having a similar problem, it seems as if I have BT on but not even connected to anything it is the top battery user.
Crazy Chuckster said:
I am having a similar problem, it seems as if I have BT on but not even connected to anything it is the top battery user.
Click to expand...
Click to collapse
Also noticed this the past day or so. Completely prevents doze as well.
Same problem. 5X. Worked fine until 6.01 update
So I got a few days with my Pixel 2 I dont get too bad blue shift I don't think it's that annoying colors are different that Samsung Screens supposedly because they are using sRGB Color space, as you can see on my photos which are not so clear in person it looks a little bit more the screen burn of the nav bar yes it's there but so faintly and since it's basically always there I don't know how can this be bad, I really hope they get a setting for a more colorful display
maxrdlf95 said:
So I got a few days with my Pixel 2 I dont get too bad blue shift I don't think it's that annoying colors are different that Samsung Screens supposedly because they are using sRGB Color space, as you can see on my photos which are not so clear in person it looks a little bit more the screen burn of the nav bar yes it's there but so faintly and since it's basically always there I don't know how can this be bad, I really hope they get a setting for a more colorful display
Click to expand...
Click to collapse
If its the navbar that has burn in, most see it as non issue. People with ocd complain about it.
What has annoyed me I don't know if it's Android 8.1 but bluetooth audio is a pain I noticed that bluetooth also with galaxy s8+ wasn't so good when connected to car but with pixel 2 even with a close speaker is broken
maxrdlf95 said:
What has annoyed me I don't know if it's Android 8.1 but bluetooth audio is a pain I noticed that bluetooth also with galaxy s8+ wasn't so good when connected to car but with pixel 2 even with a close speaker is broken
Click to expand...
Click to collapse
So it doesn't work at all? I know 8.0 BT to my car is fine on my 6p, it seems less finiky to connect than what it did on 7.1. But that was only on initial set up.
Supposed to get my pixel today
with the car If I move it a little far it stutters some times with the speaker is totally broken is a UE Megaboom
maxrdlf95 said:
with the car If I move it a little far it stutters some times with the speaker is totally broken is a UE Megaboom
Click to expand...
Click to collapse
I'll check it out myself once I get my device in hand and set up, then report back.
I'll admit I haven't been following the xl2 section as much ad I do with most phones I've owned, but I don't know that I've seen other posts about the same type of BT issue.
Have you tried bluetooth audio with other devices other than a car. Does it work with an AVR (Audio/Video Receiver) or a bluetooth speaker. Does it have the same behaviour across bluetooth devices?
Something interesting I noticed yesterday...I was packing up my old pixel XL to send to Google for trade in .
Look at at screen burn in on the bottom of screen .
Sent from my Pixel 2 XL using XDA Premium HD app
This one's huge for me and might warrant a return. My 3 XL when I plug into my Fiesta and Android Auto comes on switches from Charging to Charging Slowly, and I maintain or lose charge over the course of my trip. My 2 XL and first-gen could gain charge no problem. Wasn't Rapid, but was plenty fast.
Anyone else seeing this? This is a huge problem for me. I rely on my car to top off my phone during drives and if this can't happen anymore it kills AA for me.
Edit: There's a thread on Google's own Android Auto forums regarding this issue (apparently for people who actually have USB-C in their vehicles, the problem is ironically worse), and best yet, it has an actual Google engineer interacting and collecting data. Please report your experience here with full details, make/model of car, phone, OS and Play Services versions, etc: https://productforums.google.com/forum/#!topic/android-auto/1NmG3ojHX_k;context-place=mydiscussions
Also, user bigdave79 helpfully reported here that if you plug in your phone, let Android Auto open, and without unplugging go into USB Preferences and toggle from USB Controlled by "This Device" to "Connected Device" it will switch itself right back, but charging speed will return to expectations. While still not a fix, this helps further suggest this is truly a software bug and not a hardware or software feature/decision.
TurboFool said:
This one's huge for me and might warrant a return. My 3 XL when I plug into my Fiesta and Android Auto comes on switches from Charging to Charging Slowly, and I maintain or lose charge over the course of my trip. My 2 XL and first-gen could gain charge no problem. Wasn't Rapid, but was plenty fast.
Anyone else seeing this? This is a huge problem for me. I rely on my car to top off my phone during drives and if this can't happen anymore it kills AA for me.
Click to expand...
Click to collapse
If I'm not mistaken it probably depends on your car. My 2018 Civic can't fast charge because Android Auto run through one specific USB spot. If I used a fast charge car adapter it would but then lose AA
I'm well aware. To reiterate, BOTH previous Pixels had NO trouble with my car. This is specific to the 3 XL.
I'm not having this issue in my car. Using the same USB C car charger I used on my 2XL.
TurboFool said:
I'm well aware. To reiterate, BOTH previous Pixels had NO trouble with my car. This is specific to the 3 XL.
Click to expand...
Click to collapse
I recently purchased a quick charge charger for my car. It worked great with a Note 9, S8+, and a Razer phone. My Pixel 3 XL however, charges slowly. It is kind of annoying.
I think you're all missing the Android Auto part of this. Not a car charger. The USB port built into the car to allow it to connect to Android Auto.
glad i am not the only one who is having this issue.... it charged my s8+ fast but it shows slow charging with pixel 3 xl =\
Well, this is annoying. Same thing on my 3 XL, "Slowing Charging".
Plugged the 2 XL back in- charging normally. Ford Explorer.
Let's hope it is some stupid $hit related to this-
https://www.xda-developers.com/google-pixel-fast-charging-android-pie-fix/
The time frame and Oct release seem to match the build date in the 3 XL I have, so maybe the build of PIE is not synced to the OTA release and the next OTA will fix it? Wishful thinking I suppose..
Google support was worse than useless on this, asking questions in circles and misunderstanding me. That said, thanks to someone on Reddit and my own thinking, I tried enabling USB Debugging. After a reboot of the phone it resolved the issue. AA starts up faster, as well.
TurboFool said:
Google support was worse than useless on this, asking questions in circles and misunderstanding me. That said, thanks to someone on Reddit and my own thinking, I tried enabling USB Debugging. After a reboot of the phone it resolved the issue. AA starts up faster, as well.
Click to expand...
Click to collapse
Thank you for posting, never would have thought about that.
So the problem actually returned, but was resolved again with another reboot. This is very odd. Combined with the severe memory leaks, I have to reboot this phone more than I'm used to.
TurboFool said:
So the problem actually returned, but was resolved again with another reboot. This is very odd. Combined with the severe memory leaks, I have to reboot this phone more than I'm used to.
Click to expand...
Click to collapse
How do you tell what it is charging at now? I can see it on the main screen if the screen is powered off (ambient) and Android Auto isn't running.
The battery dialog screen used to say, maybe I'm in the wrong spot?
d j a said:
How do you tell what it is charging at now? I can see it on the main screen if the screen is powered off (ambient) and Android Auto isn't running.
The battery dialog screen used to say, maybe I'm in the wrong spot?
Click to expand...
Click to collapse
Turn the screen off and back on to look at the ambient screen text at the bottom.
TurboFool said:
Turn the screen off and back on to look at the ambient screen text at the bottom.
Click to expand...
Click to collapse
So all you did was enable USB Debugging through the developer options and your pixel 3 now charges at a similar speed as the Pixel 2 when connected in the car using Android Auto?
I was so hopeful and tried it out this morning but no luck at all. I even rebooted the phone 3 times and still receiving the "Slowly charging" dialog and the phone gained 2% in an hour.
Mastaking said:
So all you did was enable USB Debugging through the developer options and your pixel 3 now charges at a similar speed as the Pixel 2 when connected in the car using Android Auto?
I was so hopeful and tried it out this morning but no luck at all. I even rebooted the phone 3 times and still receiving the "Slowly charging" dialog and the phone gained 2% in an hour.
Click to expand...
Click to collapse
Correct. Could be a 3 versus 3 XL thing, I don't know. But yes, enabled that function, restarted, and it immediately stayed on Charging. It later returns to the bad behavior, so I basically have to restart my phone every time I enter the car.
I'm seeing the same thing. I have had developer options enabled since first day and have never seen it show rapid charging. Even with the original charger I am seeing charging slow. Since the Pixel 3 is on Sept build it is most likely the same issue as the pixel. Hopefully this will be fixed in the next update.
I too am experiencing issues with AA and a Pixel 3 XL.
1) 2014 Cadillac CTS V-Sport Premium with Cue. The phone connects and AA works just fine; however the phone shows "charging slowly".
2) 2000 Dodge Dakota R/T with a Pioneer AVH-2300NEX; latest firmware version 8.35. The phone will not establish a connection to the head unit via USB, and battery indicator flashes between charging and not charging.
I still have my Pixel 2 XL, which performs flawlessly in the CTS. Same cable, same port. The P2 XL reports "charging", and gains a charge when AA is in use.
In the Dakota, the P2 XL also performs flawlessly since the 8.35 firmware update. Again, same cable, same port. Just like the in the CTS, the P2 XL reports "charging" and gains a charge while AA is in use.
It is to be noted that developer mode is enabled on both phones, and USB debugging is "on" (both phones). I have tried the whole restart thing; to no avail.
I've initiated a return process. Since Google's unable to offer any indication of this problem being known to them or a solution being planned, I can't go forward like this. I like this phone quite a bit, but its experience isn't so dramatically better from my 2 XL as to justify putting up with a problem with no expected solution. I'll keep my eye on updates and see if any indicate this issue has been seen and fixed and maybe consider a repurchase then. Otherwise I'll hold out for the 4.
TurboFool said:
I've initiated a return process. Since Google's unable to offer any indication of this problem being known to them or a solution being planned, I can't go forward like this. I like this phone quite a bit, but its experience isn't so dramatically better from my 2 XL as to justify putting up with a problem with no expected solution. I'll keep my eye on updates and see if any indicate this issue has been seen and fixed and maybe consider a repurchase then. Otherwise I'll hold out for the 4.
Click to expand...
Click to collapse
Mine went to FedEx today. Sadly, I love the phone but already got an RA for it prior to the return window expiring. I am not confident that Google will fix the issue in a timely manner; or even acknowledge there is one. For $1000, I am not willing to go backwards in functionality. If I see proof the issue is resolved, then like you; I may decide to repurchase. If not, the P2 XL still has another year of warranty and 2 years of support.
SmoovC said:
For $1000, I am not willing to go backwards in functionality. If I see proof the issue is resolved, then like you; I may decide to repurchase. If not, the P2 XL still has another year of warrany and 2 years of support.
Click to expand...
Click to collapse
Exactly that. I spent a lot of money on a phone to replace a very good phone. There should be no regressions for that price.
Oh well, my 2 XL was fantastic, truly. I'll probably need a few days to readjust to the screen and a month or two to wait for most of the new features to filter back to it, and I'll be fine until next year.
I've had the Galaxy Watch since March and have played around a lot with faces for it that supposedly show both the Watch and the Phone battery strength. I had many of these on my Moto360 Gen2 watch that I replaced with this Galaxy watch. The Moto faces I used would keep updated with battery strength throughout the day. Every watch face I've tried with the Galaxy tells me I've got 100% most of the day. Occasionally it'll update and show where it's gone from 100%, down to something else, ex. 87%, 56%, etc, without showing any other decreases in between those. Some days, I go all day long with the watch showing I'm at 100%, even though the phone is lower.
I have a Galaxy Note8 and decided to go Galaxy Watch, thinking they would actually be more compatible. It seems like I had better interoperability with the Android Watch than I do with this Tizan based watch, even though it's all part of the same ecosystem by Samsung.
Does anyone out there know of a watch face, Paid or Free, that accurately represents Phone battery strength?
Thanks
John
All in One! by Shuisky works for me with my Pixel 3XL.
Thanks. I have that one, and for some reason, the Phone battery indicator goes away when I install it on my watch. I can see it when I first bring that face up and select it for the watch. But, then after it initializes on my watch, the phone indicator goes away and only shows the watch battery. That's what seems to happen with all the watch faces.
newkydawg said:
All in One! by Shuisky works for me with my Pixel 3XL.
Click to expand...
Click to collapse
I have bought All in One, but the mobile battery indicator stops updating after some 15 minutes, (mobile is the Note 10+)
EDIT: this is the fix https://bit.ly/2kJODkm
SpideRMaN-17 said:
I have bought All in One, but the mobile battery indicator stops updating after some 15 minutes, (mobile is the Note 10+)
EDIT: this is the fix https://bit.ly/2kJODkm
Click to expand...
Click to collapse
Thanks. I just went through and found a couple of things that needed to be unchecked. I'll see how that runs through now and if it fixes things.
I appreciate the info.
John