yashsingh1/xdaforums huggingface dataset:
[Android Auto General] vvveith:
Not quite ready for Prime time.

As is typical for Google, they launched AA before the developers were all on board or even ready for the change. As of right now, the only media choice you have when using AA is Google play music and for me, that's a rarely used application. Even though they said it would support other media apps. So, as seems to be my experience with the nexus 6 and lollipop, it just seems rushed and unfinished. We are their paying beta testers.

I don't use the AA program right now either for it's lack of options. Sad, it kind of looked like a great solution to hands free driving if it worked as advertised. You can't even ask it to read a text when one comes in even though you can ask it to reply to one. You have to touch the notification on the screen for it to read it to you. They say they would like everyone to use voice commands to do everything to make it safer on the road but yet left the messaging application like that! Talk about overlooking the obvious and most used feature on most peoples phones: Texting. Silly Google.
[Android Auto General] Skynx72:
With Android Auto I can use Google Play Music, Spotify and TuneIn Radio (Pro). One issue I've had with my Moto X 2014 is that if I Navigate and play Google Music it will sometimes freeze. I then just unplug the phone and plug it back in and it works. There are definitely some bugs with it. Sometimes when I use the voice commands it freezes too and can get the whole unit stuck in Voice mode. I then have to unplug the phone and plug it back in...
[Android Auto General] earsmccoy:
No problems here.

I installed my 4100 and haven't had any issues. I read that some people are only able to use Google Play Music, which is my app of choice, but I also use Iheart Radio, and Pocket Casts, all of them work great with Android Auto. The only problem so far is what is what vvveith said, you have to tap on the message notification otherwise it wont read your message by asking google now. The Sync system it my five year old Ford Fusion can read my unread messages. Besides that everything works great. I am really hoping that more apps find its way to it. Netflix when the car is in park would be great during my lunch hour but I would imagine the liability is something that would keep it from ever happening.
[Android Auto General] tgcid2040:
The following links might be of help to someone :)

List of phones with known issues:

https://support.google.com/androidauto/#6200174

Genreral Android Auto support:

https://support.google.com/androidauto/

List of compatible Android Auto apps:

https://play.google.com/store/apps/collection/promotion_3001303_android_auto_all
[Android Auto General] killa2009:
So how are you guys plugged up to the radio? Mhl cable, extension usb cable, or direct USB to radio then phone?
[Android Auto General] mikereidis:
Rushed and unfinished, yes.

I think Google was forced into releasing the AA app after Pioneer starting selling HUs earlier than expected.

I am not surprised that there are limited choices for AA compatible apps now.

Selling/making money from apps is a VERY tough business. Businesses do not want to spend developer time on things until there is good evidence that it will make them more money. (Then they will want it yesterday, LOL.)

How many companies are "raking in the money" with smartwatch apps ? Android/Google TV apps ? Chrome ?

I started adding AA capabilities to my own media app (Spirit FM radio). It works, more or less but then I saw that there is still a lot of work to do. I'd have to add stuff for AA, yet retain the old methods for Kitkat and earlier and make them work together. Uggh... Google has a habit of deprecating old APIs needed on Android versions most people are still using, and bringing out new APIs that take a bunch of work to create and test. Reminds me of Microsoft over the decades; they have an advantage over app competitors due to secret APIs, or having access to new APIs long before their competition can use them. Same concept: Control the OS and have a major advantage with the apps.

Add to this the fact that AA compatible apps MUST be approved by Google, which can take at least a few weeks, and during which time an existing app on Play is frozen.

Note that AA apps can't show advertising. Given that most people do not want to pay a cent for apps, that destroys one of the main app moneymakers: ads. In app purchases ? Not while we're driving... I will guess that some app devs will turn to "next generation" paid apps with AA compatibility.

Also, AA forces an app to use Googles' UI, though with some small-ish customizations possible. I'm personally OK with that; I'm happy to leave UI to Google. But many app sellers want to BRAND their app for marketing reasons.

Also, I think that Google's apps will always have advantages and other media app makers are competing with Google.

Something like AA has been wanted by many of us for a LONG time.

But as the issues are slowly resolved, I think AA will become very popular. And it seems many people who have seen both AA and Apple Car Play think that AA is much better.

Google has Google Maps for one, and it looks reasonably well integrated with AA. Nav and maps is essential for mobile in the car.

Cheap Chinese Head Units and HU apps for tablets will come eventually, along with AA in new cars. At this point many who were excited about AA have lost enthusiasm when told they'll need a $700+ HU, as well as a compatible phone running Lollipop.
[Android Auto General] pjosman:
USB Port 2 to the phone (Nexus 6). My USB cable was long enough that it didn't need the extender. I have the another cable connected to USB 1 with the extender and a lightning cable in case the wife wants to use her IPhone. Contrary to Pioneer's instructions, it doesn't require a specific cable.
[Android Auto General] vvveith:
Very well said sir!

Very well said sir! I like your thoughtfulness. I am one of the people that likes supporting developers if I use and like their apps. If they have a paid version, I always purchase the application. Being a musician I understand that without financial support, we parish or can't afford to do many of the things we love.

If a developer has quick responses to user feedback and corrects/helps users to understand their app, I also donate cash for their assistance. I know I am a minority. I hope as time moves forward that more people understand how important it is to pay for what they use and like. I asked Pandora if they would send me their code so I could fool around with making a version of it that would work on the AA platform but they told me, they are indeed working on one and it should be available soon.

But knowing how big Pandora has grown, their idea of soon is probably months to years away.

I'm thinking that their might be a way to tweak Google Maps to work outside of the AA platform and just stream to the HU of the car but I don't know if it would be legal or not. Thanks for your thoughtful input, we need more people like you here.
[Android Auto General] mikereidis:
:)

There are some display mirroring things, but they are "the old way".

AA is "the new way" and the way forward IMO; designed specifically for in car use.

It will take some time, but it will get done.

One of these days Google self driving cars will tell us we are 10 minutes early for work and offer to stop for a donut and an oil change. And Google will get a commision on each.
[Android Auto General] noutoo:
I have a Nexus 6 with Pure Rom and I get the message it's not compatible. Might try MeanPop. I would like to know why their is compatible issues with some roms. I think Google needs to get their stuff together. Support should be based on the app. if Lollipop is a requirement, post or limit that in the Google Play Store before a person drop 600-1200 on a radio and install just to find out, oops your phone or rom isn't supported.
[Android Auto General] rpjwalter:
Do you have the USB plugged into USB2? USB1 is for Apple Carplay. I have the 4100 and a GS4 and it works fine.
[Android Auto General] bill.in.detroitX:
New to Android Auto - not new to Android or Samsung S4

Some simple things I have learned since I got my 4100 ten days ago:

NOTE: All my comments are related to using a Samsung S4 with the 4100

1. update the security policies on your phone to get sound working in Android Auto.

2. use the charging cable that came with your S4 with Android Auto and plug it into USB2. As others have said, the cable is an important link between the hardware in the 4100 and your phone. At this early stage of development, the link does not appear to be super stable, so increase your chances of a reliable connection by using that white cable.

3. you can use USB1 - but only for USB memory devices containing music or video. I have both cables wired up in my car and I switch between the two ports as my mood at the moment requires.

4. I haven't read though the 5 pages of comments (I know, flame on, purists!) but you must update your radio to 1.03 firmware for android auto to work - if you already know that, I apologize...

More to come - too many side jobs for tonight but I will be back...

---------- Post added at 08:27 PM ---------- Previous post was at 08:11 PM ----------

I didn't see anyone answer you directly so I thought I would.

Look for my post #46 - updating the Samsung Security policies may work for you...

Bill
[Android Auto General] norm807:
Some of my observations with the 4100 and a Verizon S5

HU: firware 1.03, S5 updated to latest version and security policies

1. I mostly like the AA interface. Do not like the background, need to figure out if that is changeable

2. on my phone, android auto sometimes takes a while to start. From the time I plug the usb cable in, it can take minutes for AA app to start on the phone. It varies. I think I have found the pattern I need to use to get it start in the first 30 seconds reliably

3. I have had random slow downs on the HU. I have seen when I have clicked on play music icon, the screen stays where it is for 20 or 30 seconds then change over to play music. Seems like a lot of lag. This may be related to #2 above.

4. Google play music works pretty well. I am a Pandora fan, but slowly switching to google music. I do wish Pandora was a supported app

5. If I was playing google music and shut the car off, when I start it back up again and have the phone plugged in, it says unrecognized usb device.. rather annoying.. wished the 4100 could recognize that the AA hasn't started and switch to radio.
[Android Auto General] mikereidis:
1. You can get day or night modes, but I think we are stuck with the "South Park mountains" etc. unless Android Auto / Google Play Services resources are hacked. Google's lawyers don't like user changeable backgrounds that might be more distracting, like pron, LOL.

2. Verizon phones have some kind of USB app or mode that can be disabled to avoid some problems. Not sure if that's your issue.

3. If it's slow it's likely the phone's software "fault", OR you are getting mobile Internet access dropouts. Voice recognition happens over the Internet and some other components may need Net too.

5. USB reconnect is like rebooting our phones and PCs. We shouldn't HAVE to, but it's needed sometimes. It's worth trying some kind of powered or not USB hub or similar to see if it helps.
[Android Auto General] chocolatet:
Im getting very low volume when i connect to android auto and try to use the voice control also regular music is very low as well when comparing the same song going through regular bluetooth vs android auto. I have a note 4 with maximum ovrdrive. I tried a note 3 and volume was fine. Any ideas for me?
[Android Auto General] hi-phile:
Was working with my Asus Zenfone 2

I have a ZF2 ZE551ML CN region Z00A with rooted and unlocked boot loader still running on WW ASUS_Z00A-2.19.40.18_20150612 and had purchased the Pioneer NEX 4100 that already had firmware 1.03 installed. I hooked up the provided USB cable to port 2 which allows Android Auto to work as well as other Android Applications that are currently supported. I haven't deleted any stock Asus applications, and the applications update and I normally apply the application updates.

I'm not getting any OTA updates because of root and unlocked bootloader, things seem to be running fine, although I probably should update the firmware which has the Stagefright fix, but I haven't and i've disabled the auto download of MMS files in Hangouts anyway as a precaution.

But Android Auto wasn't working this morning when I got in the car and plugged in the phone. So, this was all working fine up until today when I plugged in the phone into the USB port on the Pioneer a message appears that reports "Problem connecting to Android Auto it is not available at this time. Please check your Phone for the Android Auto Application."

I haven't tried troubleshooting further because I had to drive into work.

This has been working ever since the beginning too, which is I why I was surprised and a little upset that message started appearing. I checked the version of Android Auto and Google Play Services because I thought maybe an update caused it to stop working. Google Play services is version 8.1.18 (2272748-270) Oct. 7 for x86 and Android Auto is version 1.3.089821 (2258745-release) Sept. 21 so these weren't updated and shouldn't have been a reason for this.

I have rebooted the phone, and that didn't fix the problem. Now I have just cleared the cache in these applications and will give it another attempt and report back the results.

Solution: After clearing cache and rebooting the phone now it is working again.
[Android Auto General] dryvali:
I am getting the same issue with the stock note 4. I have a moto x pure 2015 that works flawlessly, but when connected to the note 4, I have to turn the volume almost to 30+ on the HU to get acceptable levels. After a phone call, however, it will sometimes go to "normal" volume and almost deafen me because the HU volume is so high. Has anyone found a solution to this?
[Android Auto General] chocolatet:
Nope and I'm still having same issue. I'm going to try the v10 tonight
[Android Auto General] rubber guard:
anyone put one of these in an 03-06 Tahoe/Yukon/Silverado/Suburban/etc?
[Android Auto General] 2010zx6r:
I am so over trying to use android auto with my galaxy s5. It had good days where it worked for 30mins or so and then it had bad days (which was the norm) where it lasted 2mins. Tried everything from cables to firmware. Made little difference. My pioneer is the Australian version avh-x8750.

Got a iPhone 6s Plus and works a treat. No problems what so ever. Didn't want to go down this path. But too many variables with android. No guarantees with any phones working on android auto.
[Android Auto General] mikereidis:
In theory, Nexus phones running stock Android 5.1+ should be guarantee-able.

In practice, even Nexus can have issues too.

One thing I've seen with AA is that it's pretty much designed to crash when a non-perfect packet arrives.

IMO that's a bad way to write software. But it may have the business reason of favoring Google's officially blessed HU OEMs in the so called "Open Automotive Alliance". (Open ONLY to Tier 1 OEMs who pay Google for the privilege.)
[Android Auto General] aergern:
You folks might want to upgrade to 1.05 which was released on 12/16/2015. It's changelog has lots of AA patches in it. I have an 8100NEX that I use with a Nexus 6P (stock but rooted) running 6.0.1 and it works perfectly except it doesn't like to mark SMS as read so I have to listen to the whole conversation until I disconnect the phone, mark the thread as read and reconnect. As far as AA crashing with any Nexus or any phone is probably not true since my head unit has been used with my N5, N6 and 6P along with phones that a few friends wanted to try. My commute is varies from 45 minutes to 90 minutes depending on the weather and it never crashes ... I push the crap out of AA with music, maps and alerts coming in from work via SMS.

If you are using a 3rd party ROM this could be the issue. Also, update to 1.05 and see if that does anything.
[Android Auto General] 2010zx6r:
It wasn't my rom. Tried stock and custom. Made no difference. Latest firmware at the time was used.

I'm not bothering with AA. Have gone Apple instead and no dramas at all.
[Android Auto General] aergern:
Based on the fact that my wife's '16 Accord has Carplay and AA available AND the stock deck also runs Android 4.2.2 .... the no drama is delusional. She has issues and little bits that give her no end of fits with Carplay. I however have no issues with my Nex8100 and Nexus 6P. I do believe it's all in how one uses these two technologies and what one expects from them. iOS/Carplay isn't perfect and neither is Android/AA.

If the iPhone and Carplay work for you with what you expect ... grand! And enjoy. :good:
[Android Auto General] malimal:
I have had many issue with AA and samsung phones. I have used both a S6 and Note 5 and the issues are the same. Sometimes the music and phone screen don't want to show. Sometimes it just doesn't load. Have been testing with a Nexus 5x and it seems to be smooth so far.
[Android Auto General] 2010zx6r:
Just my head unit replaced. It had a couple of intermittent problems. It would sometimes take a couple of minutes to turn on after starting the car. Then when turning off the car the screen would go back to home position from tilted. It would beep a few times then nothing.

Let's see how new one goes.
[Android Auto General] iLoki:
I have the same issue with my Note 4... this just started recently though. I had absolutely no issues with volume until an OTA broke all audio in AA.. After giving up searching for a solution to that problem, I factory reset my device and audio works again, but it is very, very quiet compared to standard bluetooth audio or the FM radio levels. My 4100NEX is on FW version 1.05 btw.

I haven't had any luck with this, and while annoying, it isn't unbearable. Would be great if anybody has any ideas that may help bring the volume levels back up to 'normal'.
[Android Auto General] rubber guard:
Question. Is firmware v1.5(0) the newest or is it 1.53?

I see both v1.5(0) and v1.53 on their site, and my HU shows v1.5(0)

Tia
[Android Auto General] cranbiz:
1.053 is the latest firmware. That's what's on my unit and matches the web download.
[Android Auto General] recepo1:
Yea 1.053 is latest firmware
[Android Auto General] ktrotter11:
My note 4 started acting up after a factory reset, but update to marshmallow fixed the issue...
[Fire TV Themes and Apps] phillip.r:
Hey guys, new to the forum.... sideloaded the Settings.apk last night and was able to pair a motorolla BT mouse no problem. Used it all last night.

Came home today and the Fire TV was frozen, so I reset it, now the mouse isn't connecting.

When I go into the Settings app, it still shows it in the list but it doesn't say 'Connected' under the name like it does for the Fire remote.

Clicking on it in the list does nothing. I wish there was some way to tell it to forget that device but I'm not seeing any way.

I've tried uninstalling the Settings.apk but when I reinstall, the mouse is still listed as a device that has already been recognized.

I've checked the mouse batteries, and even took it upstairs and paired it with my computer to make sure it still worked.

Any ideas on how I can get it back?
[Nexus 6 Q&A, Help & Troubleshooting] treIII:
Is there any way to download an ota and put it in the correct place using root explorer or equivalent and install it through the stock recovery? Also where can a person get the stock recovery for 5.1 47E? I've googled it but can't find stock recoveries. Thanks

Sent from my Nexus 6 using Xparent Blue Tapatalk 2
[Nexus 6 Q&A, Help & Troubleshooting] flamingtiger:
I am not sure about the ota being on your phone, I recommend just side loading it which IMHO is the best way to install an OTA after root. To do this you would need a pc ofc and use wugfresh's toolkit.

The stock recovery comes in the zip you download from https://developers.google.com/android/nexus/images

Look inside the zip inside of this zip
[Nexus 6 Q&A, Help & Troubleshooting] danarama:
If you have root explorer then you have root which causes ota to fail. Factory images is your best bet. Or Rooted ROM.zip
[Nexus 6 Q&A, Help & Troubleshooting] johnny grep:
I'm currently on Bell Mobility & HD Voice (non-VoLTE) calling has been around for a while now. It works on iPhones & Samsung devices, but not on my Nexus 6. Do I need to change something in build.prop to get it to work? Any ideas?

Before anyone says VoLTE is required, that's simply not true - I've had that feature for years on my iPhone 5, and yes, I know what AMR-WB sounds like.
[Nexus 6 Q&A, Help & Troubleshooting] DebianDog:
I'm curious how you can get a non LTE network to make LTE calls. It doesn't make sense to me.

On verizon you have to enable it at the carrier AND on your phone

Sent from my Google N6 on VZ
[Nexus 6 Q&A, Help & Troubleshooting] johnny grep:
As I've said before, I am not talking about LTE/VoLTE calls. I'm talking about HD Voice on HSPA+ which is available on Bell Mobility & TELUS Mobility.
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] BEDickey:
So I was watching a YouTube video about how to increase my (already insane) battery life. One of the suggestions was to set your mobile network settings to the correct setting for your region, so the Droid was not looking for all of them, which I did. Now I am completely unable to access those settings again. "Mobile Networks" is greyed out completely. Any ideas on what happened and/or how to fox this? Thanks! I'm on Verizon, northeast USofA.
[Xperia Z3 Tablet Compact Q&A, Help & Troubleshooti] zgmfx20:
I tried using the app "Ampere" from Play Store to test the cable EC-21 on Z3TC. (cable I pulled out from a magnetic charging dock of Z1)

With measurements around -120 to -150 mA while not charging, the tests with 10 seconds are:

1) Charging through EC-21, the current drawn by the tab is around 1520 mA

2) Charging through factory USB cable, the current drawn by the tab is around 1130 mA

Note that the tab is brand new. The output of the charger is 1500.

Is the EC-21 cable faulty? Is it not recommended to use this?

TIA. :)
[Xperia Z3 Compact Q&A, Help & Troubleshooting] MavZ3c:
I often call conference call lines where you have to enter an access number to get in. To add a wait to a number I simply ad a ";" (semicolon) where I want the wait to be. A number could look like this: 1-866-345-2350;23456678#. A window pops up at the wait and asks me if I want to send the following numbers, the ones after the ":". Normally when I hit "Ok" the numbers are sent. Not so on this Kitkat z3 compact. Nothing happens when I hit "call" so I am not getting into the conference. I am able to enter the numbers manually, but since I do this a lot it's really cumbersome having to do it.

When i contacted sony support this was their reply "As I was able to verify, this function was confirmed and doesn't seem to be available on our new devices. We apologize for the inconvenience this may cause you. However, I'll make sure to note your feedback regarding this matter so that perhaps it's added again in a future update."

Let me know if any one here use this Pause(;) or Wait(,) feature while call and found any alternate method to use the same on Z3c. If there is no alternatives it would be a deal breaker and i have to return the phone for some other with this feature working android device.
[Xperia Z3 Compact Q&A, Help & Troubleshooting] contrem:
Have you tried using a comma instead? That's what I use.
[Xperia Z3 Compact Q&A, Help & Troubleshooting] MavZ3c:
I have tried comma and semi colon and did not work. Which version of android is currently on your Z3c and please provide detailed steps on how its working for you. Provided a example nos with comma would help.

Thanks