Database Info

set Android 6.0 default USB config to MTP rather than “charging only”?

Whenever my device (Nexus 5, Android 6.0) connects via USB, the USB config always defaults to "charging only".
This is a big problem since whenever I'd like to listen mp3 connecting nexus 5 to my car stereo I have to manually set the mode to MTP.
The big annoyance is that whenever I turn off the car engine and then restart it the nexus 5 USB connection go back to "charging only" !!!
I already tried debugging mode:
Develop settings -> USB Configuration is set to MTP.
Any chance to set USB default as MTP?
Thanks

i want that too..its very anoying..

try this: http://stackoverflow.com/questions/...t-usb-config-to-mtp-rather-than-charging-only

_PeTiT_ said:
try this:
Click to expand...
Click to collapse
Sorry, this is not helping me in solving this issue.

I want this the other way around. I want it to default to Charging Only and not MTP...which it always does on my unit. This happened since the last update, before that it always defaulted to Charge Only, which was fine for me as I don't MTP often.
Annoying to me for different reasons. Point is we should be able to set a default action, and I can't for the life of me work out how to change this behaviour. In Dev Options, I can change the default behaviour, but it doesn persist or stick. As soon as I pull the USB cord, it flips back to MTP for me every time. Very annoying.
...so bumpity bump bump.

USB does not recognize my phones

I have a MTCD head unit MX (witson) with Android 5.1, my problem is that the USB port cannot recognize my phones, A note 4 with Android 6.0 (eRobot ROM) and a Samsung GT386T no rooted with stock ROM 4.4.2. The USB port works find with a usb stick, I can play music, pictures, etc. but not my phones. Both have the USB debugging enable.
When I plug a phone it is charging but nothing happens, my note 4 after a few minutes pop a windows saying that there is a problem with the connection MTP and that I need to download samsung Sync etc.
What I want to do is to use the mirror link function.
Any of you know something about this issue?
Thanks in advance for your help.

paniqueado said:
I have a MTCD head unit MX (witson) with Android 5.1, my problem is that the USB port cannot recognize my phones, A note 4 with Android 6.0 (eRobot ROM) and a Samsung GT386T no rooted with stock ROM 4.4.2. The USB port works find with a usb stick, I can play music, pictures, etc. but not my phones. Both have the USB debugging enable.
When I plug a phone it is charging but nothing happens, my note 4 after a few minutes pop a windows saying that there is a problem with the connection MTP and that I need to download samsung Sync etc.
What I want to do is to use the mirror link function.
Any of you know something about this issue?
Thanks in advance for your help.
Click to expand...
Click to collapse
I believe i read that there is a specific app that you have to run on these to do the mirror link...easy connect, maybe? Did your HU come with an instruction booklet? I was looking through mine earlier and it went over in detail how to setup mirroring through that app.

Yes, when I tried to use EasyConnected is when I saw the problem. The app waits for my phone to be connected, It says that it must be turned on USB debugging, but it is on. Then I checked in the File manager and the USB was not enable there, like if nothing is plug it. If I plug a USB memory it works fine.
I will try today to do a factory reset.
Thank you!

paniqueado said:
Yes, when I tried to use EasyConnected is when I saw the problem. The app waits for my phone to be connected, It says that it must be turned on USB debugging, but it is on. Then I checked in the File manager and the USB was not enable there, like if nothing is plug it. If I plug a USB memory it works fine.
I will try today to do a factory reset.
Thank you!
Click to expand...
Click to collapse
You ever get this solved? My easyconnected never stays connected. WiFi and USB both are garbage.
WiFi randomly disconnects.
USB also disconnects asks me to allow USB debugging every couple of minutes. The phone never remembers the headunit, so it constantly asks me again to allow connection. Must be a crap RSA fingerprint coming from the headunit.

JordanB said:
You ever get this solved? My easyconnected never stays connected. WiFi and USB both are garbage.
WiFi randomly disconnects.
USB also disconnects asks me to allow USB debugging every couple of minutes. The phone never remembers the headunit, so it constantly asks me again to allow connection. Must be a crap RSA fingerprint coming from the headunit.
Click to expand...
Click to collapse
Nope, Still does not work for me. Same symptoms as you. I already tried with 3 differents phones, factory reset and different versions of easyconnected.

I seem to have USB connection working now with only one "allow USB Debugging?" popup, only when I first connect.
What I did was turn wifi off on the headunit. I am not sure why it worked, but I just wanted to turn everything not needed off, and see if the headunit would stop disconnecting all the time. So far so good. I can probably live with one annoying popup, instead of one every few minutes.
Of course you have to keep the screen on the phone on, and the battery in the phone will deplete faster than the headunit charges it, but still an improvement. I had a 30 minute drive today, and the USB never disconnected!

paniqueado said:
Nope, Still does not work for me. Same symptoms as you. I already tried with 3 differents phones, factory reset and different versions of easyconnected.
Click to expand...
Click to collapse
paniqueado, try the da_anton ROM. I just installed it and easyconnect finally works as it should. I just plug in my phone to the USB and it fires right up! One prompt if any on the head unit, and NO disconnects whatsoever.

Android Auto

Hi,
Did somebody try to use an android auto function? My car (Peugeot 308SW 2018) and the phone not connecting with latest (8.1.0) android version. I tried to enable an USB debugging (as workaround recommendation), but nothing changed...
Have you other idea or working solution?
thx!

rawen69 said:
Hi,
Did somebody try to use an android auto function? My car (Peugeot 308SW 2018) and the phone not connecting with latest (8.1.0) android version. I tried to enable an USB debugging (as workaround recommendation), but nothing changed...
Have you other idea or working solution?
thx!
Click to expand...
Click to collapse
Yes, it works perfectly in my mid 2017 Kia Cee'd SW. Check if you have android auto enabled(i have the option to disable it and the apple car play). Also, the usb cable is working properly when connecting to a pc?

At the car side is enabled, at phone side i didnt found any additional options...
The best result was the android auto icon at phone appears and disappears continously with 2-3 different cables.
Is it possible the car head unit firmware not compatible with N7P latest SW version?

rawen69 said:
At the car side is enabled, at phone side i didnt found any additional options...
The best result was the android auto icon at phone appears and disappears continously with 2-3 different cables.
Is it possible the car head unit firmware not compatible with N7P latest SW version?
Click to expand...
Click to collapse
Doubt it. The car is from this year, it seems unlikely(to me) that the firmware wasn't up to date.
Stupid question, you have the android auto app installed on the phone right? Android has a Car Mode but to use android auto you need to install the app 1st(https://play.google.com/store/apps/details?id=com.google.android.projection.gearhead&hl=en). If the link says that you have no compatible device, download the latest version from here(https://www.apkmirror.com/apk/google-inc/android-auto/)
For almost a year I thought my head-unit wasn't up to date as the android auto would freeze, the app would say that the head-unit wasn't up to date, waze would display random artefacts, etc.
Now with the N7p it is butter smooth, no funky stuff and way more responsive that when I was trying to use it with my Redmi 4 Prime(same cable but with a micro-b to usb c adapter)...

No issues with AA in Seat Ateca 2018.
Everything works like a charm.
For phonecalls, you need to select default sim first, otherwise the call hangs on a sim selection prompt on the phone.

I write to nokia support and they send:
- clear the bluetooth cache
- do a soft reset
after this steps working fine...

what is Bluetooth cache?

Tequila.CZ said:
what is Bluetooth cache?
Click to expand...
Click to collapse
You found here, how to clear: http://support.hereplus.me/hc/en-us/articles/115003497328-Clearing-your-Bluetooth-Cache-Android-/

Do you install android auto app on your smartphone ? some lands doesn't have android auto on the play store, so you need to download manually on apk mirror web site (arm64 version)
A good quality cable is also needed.

I'm having similar issues.
This phone won't work in both my VW cars.
If I clear all settings it works fine.
I get to my destination, unplug and then when I head out on my next trip it doesn't. Just a blank screen on the head unit and the phone has the green screen saying launch Android Auto on the head unit.
Tried the BT cache clearing as above. Will try a factory reset of the phone shortly too otherwise wait for pie and if still no go then sell the phone which I will miss
Though can't work without Android Auto now

It is definitely problem with Nokia 7 plus. In my car it connect and after few minutes black screen and solution is only disconnect and connect again.

matonka007 said:
It is definitely problem with Nokia 7 plus. In my car it connect and after few minutes black screen and solution is only disconnect and connect again.
Click to expand...
Click to collapse
I've found the bluetooth with my N7P poor anyway. This is my second one and the same as the first.
All HMD will do is send you a list of the bluetooth protocols they support.
So you may need to change your car ?

My 7+ works perfectly now.
Enable USB debugging and disable the extreme power saving settings.

Getting Android Auto to automatically connect to car headunit

Each time I get into my car and connect my OnePlus 6 via USB, I have to change the USB connection type on the phone to MTP in order for Android Auto to connect. Once I change the setting and it connects, Android Auto runs well and stays connected until I turn off my car. Without changing the USB setting, the phone will stay in charging mode and Android Auto does not connect.
My car is a 2016 Honda Accord EX and I am using an OEM cable. The phone is rooted, developer options are enabled, and USB debugging is off. When I go into the developer options and try to change the default USB connection mode to something other than charging, the setting change doesn't seem to take.
Is there a way to automatically use MTP mode when I connect the phone to my car? Or something else I can do to get it connected without having to change a setting on my phone each time I get in my car?

I would clear data, force stop, and reinstall Android Auto. I use it every day and have no problems at all. Connects automatically.
My HTC M9 had no end of problems with AA. Would not connect half time time unless I replugged it in, and the voice-to-text function was buggy as hell. My OP6 is smooth as silk.

Thanks. I tried that and even deleted the phone from my car. It didn't work. I had to change the mode to mpt to get it to do the initial connection. Same for reconnecting. Doh!

Do you use Tasker? I wrote a task that will automatically change the setting to MTP. It requires the Tasker plugin - AutoInput as well.

I do have tasker. How do I set it up to do that? Thanks.

theman22 said:
I do have tasker. How do I set it up to do that? Thanks.
Click to expand...
Click to collapse
So I actually created two different profiles/tasks.
1) Detects when USB power is plugged and then opens developer settings and scrolls automatically to usb configuration and makes the change. This profile/task requires the plugin AutoInput.
2) Uses AutoNotification to detect when there is a notification in your tray stating that the device is being charged. Then it will use AutoInput again to click on the notification and change it to 'USB for file transfer'.
I only attached #1. Import it into to Tasker and see if that works. If not, I can add the second option.

theman22 said:
Each time I get into my car and connect my OnePlus 6 via USB, I have to change the USB connection type on the phone to MTP in order for Android Auto to connect. Once I change the setting and it connects, Android Auto runs well and stays connected until I turn off my car. Without changing the USB setting, the phone will stay in charging mode and Android Auto does not connect.
My car is a 2016 Honda Accord EX and I am using an OEM cable. The phone is rooted, developer options are enabled, and USB debugging is off. When I go into the developer options and try to change the default USB connection mode to something other than charging, the setting change doesn't seem to take.
Is there a way to automatically use MTP mode when I connect the phone to my car? Or something else I can do to get it connected without having to change a setting on my phone each time I get in my car?
Click to expand...
Click to collapse
God, it's annoying. It happens in all the modern androids. My S8+ 5T and now my OP6

My OP6 has no issues connecting to my Pioneer AVH-2330NEX. Just plug it in and AA starts right up. Bluetooth is pretty reliable as well, which is how I connect most of the time.

It usually takes a minute or 2 for my AA to come up on my screen (2017 Charger). Once it's connected, it runs super smooth. But I wish it was a little more responsive once I plug in the cable. Now I have to wait for it to come up before I can launch any app (Maps, Spotify, etc)
I"m going to see if the MTP method makes it connect "faster". If so, I'll look into building a Tasker Profile as well like @azsl1326

azsl1326 said:
So I actually created two different profiles/tasks.
1) Detects when USB power is plugged and then opens developer settings and scrolls automatically to usb configuration and makes the change. This profile/task requires the plugin AutoInput.
2) Uses AutoNotification to detect when there is a notification in your tray stating that the device is being charged. Then it will use AutoInput again to click on the notification and change it to 'USB for file transfer'.
I only attached #1. Import it into to Tasker and see if that works. If not, I can add the second option.
Click to expand...
Click to collapse
This is really close. I had to add one more scroll down step in the developer menu and change the mode to MIDI. It doesn't work 100% though. If the developer options menu is already open, it reopens wherever it was and sometimes the scroll down goes too far... Perhaps there is a more stable way to do this?
Attached is my modified tasker profile.

theman22 said:
This is really close. I had to add one more scroll down step in the developer menu and change the mode to MIDI. It doesn't work 100% though. If the developer options menu is already open, it reopens wherever it was and sometimes the scroll down goes too far... Perhaps there is a more stable way to do this?
Attached is my modified tasker profile.
Click to expand...
Click to collapse
I have another profile that uses AutoNotifications to detect when there is a notification in the tray regarding USB charging. It will then use AutoInput to select this option from the notification tray and change it to 'Transfer files'. I can post that here if you are interested. It does require two paid plugins.
You could add a task to clear recents before running the AndroidAuto task - that way it should ensure that Developers Option screen is no longer active.

azsl1326 said:
I have another profile that uses AutoNotifications to detect when there is a notification in the tray regarding USB charging. It will then use AutoInput to select this option from the notification tray and change it to 'Transfer files'. I can post that here if you are interested. It does require two paid plugins.
Click to expand...
Click to collapse
If it works reliably, I'm interested.

theman22 said:
If it works reliably, I'm interested.
Click to expand...
Click to collapse
Here you go. I think both of these Auto plugins have free trials, so you should be able to try it before you buy it.

Disabling USB debugging has helped me

theman22 said:
Each time I get into my car and connect my OnePlus 6 via USB, I have to change the USB connection type on the phone to MTP in order for Android Auto to connect. Once I change the setting and it connects, Android Auto runs well and stays connected until I turn off my car. Without changing the USB setting, the phone will stay in charging mode and Android Auto does not connect.
My car is a 2016 Honda Accord EX and I am using an OEM cable. The phone is rooted, developer options are enabled, and USB debugging is off. When I go into the developer options and try to change the default USB connection mode to something other than charging, the setting change doesn't seem to take.
Is there a way to automatically use MTP mode when I connect the phone to my car? Or something else I can do to get it connected without having to change a setting on my phone each time I get in my car?
Click to expand...
Click to collapse
I replied to you in the other thread, OnePlus 6 and Android Auto
But to fix your issue, this MIGHT be the solution for you specifically. Setup an appointment with your local Honda dealer, and ask to get Technical Service Bulletin 16-059 installed.
This fixed my issue for my '16 Accord when AA wasn't working at all with my PH-1

Or you can just simply choose this option to mtp as default on USB connection. It's in developer settings.

Berlifan said:
Disabling USB debugging has helped me
Click to expand...
Click to collapse
I have read about this and disabled USB debugging. It does sound like it works for some users but it didn't make a difference for me, unfortunately...
surface13 said:
I replied to you in the other thread, OnePlus 6 and Android Auto
But to fix your issue, this MIGHT be the solution for you specifically. Setup an appointment with your local Honda dealer, and ask to get Technical Service Bulletin 16-059 installed.
This fixed my issue for my '16 Accord when AA wasn't working at all with my PH-1
Click to expand...
Click to collapse
I will go ahead and do this. Thank you for the suggestion!
Joyarup said:
Or you can just simply choose this option to mtp as default on USB connection. It's in developer settings.
Click to expand...
Click to collapse
I've tried this as well. The setting does not seem to stick. It sometimes works the next time I plug my phone into my car but the 2nd time I plug my phone in, the default in developer settings is back to USB.

azsl1326 said:
Here you go. I think both of these Auto plugins have free trials, so you should be able to try it before you buy it.
Click to expand...
Click to collapse
This did not work when I tried it today. I'm guessing there is some difference on my phone that would require the setting to be tweaked. I'll look into this.

theman22 said:
I have read about this and disabled USB debugging. It does sound like it works for some users but it didn't make a difference for me, unfortunately...
I will go ahead and do this. Thank you for the suggestion!
I've tried this as well. The setting does not seem to stick. It sometimes works the next time I plug my phone into my car but the 2nd time I plug my phone in, the default in developer settings is back to USB.
Click to expand...
Click to collapse
Didn't know that..

I had the same issue with a VW Passat 2016, and the solution was to enable USB debugging, and after that everything is working ok.
Unfortunately I'm facing another issue. If I'm initiating a call with the phone connected to AA, usually by voice command, the sound is routed randomly on the headset, speaker and sometime to Bluetooth.
Every time I have to set manually from phone app in AA on the car screen to route the sound to Bluetooth, and this is annoying. . Do you experience this issue as well?
Thanks!

Pixel3 not visible to PC (USB Transfer mode)

I am using my USB to USB-C Cable form my Nexus 5X, which works flawlessly with that one.
With the Pixel, however, I don't get it showing up in Transfer mode (as a drive).
When using PTP mode it becomes visible, but of course only showing picture folders.
Cable works 100% fine as far as I know, also with the Tool-All-In-One etc.
Any idea how enable USB-Transfers from PC to Pixel3?

fronten said:
I am using my USB to USB-C Cable form my Nexus 5X, which works flawlessly with that one.
With the Pixel, however, I don't get it showing up in Transfer mode (as a drive).
When using PTP mode it becomes visible, but of course only showing picture folders.
Cable works 100% fine as far as I know, also with the Tool-All-In-One etc.
Any idea how enable USB-Transfers from PC to Pixel3?
Click to expand...
Click to collapse
When the pixel3 is connected did you look in the settings to see what USB mode is selected? You might need to change the mode to File Transfer. Also you have to unlock the phone after connecting it before it shows up. I'm not near a computer so I can't give the exact details.
EDIT: When the phone is connected go to Settings/Connected Devices/USB. Then in the section "Use USB for" make sure File Transfer is selected.

Thank you for the reply.
There's a "Yes" to all of that: USB mode is "Transfer Files", set directly via Setting but also checked on unlocked screen.
PC explorer shows Pixel3 in PTP mode (images folders only), which vanishes completely when switching to file transfer mode.
With Pixel 3 we are able to change which device controls USB connection, - i can't change this for this connection, it stays in "This device" (P3), "other device" (does this mean PC?) fails and reverts to "this device".
Is this a setting relevant only for Phone-to-Phone connections?

My Pixel 3 is doing this now with Android Auto after I got the February update. I can't change USB mode and Android Auto only launches on my phone instead of my car head unit. If I try to manually change the the USB mode to anything other than charging it immediately resets like nothing happened. If I change the control type to "other device" it reverts to "this device" and grays out the option.
I have tried a few cables, two different cars, and enabling USB Debugging but nothing helps. I think Google did this and we might have to wait on a fix.

As a follow-up, I've seen some people with this issue fix it by getting a USB C cable that is 65 ohm, or getting a USB 3.1 SS+ cable. I have one on order and will update when I receive it.

zeropants said:
As a follow-up, I've seen some people with this issue fix it by getting a USB C cable that is 65 ohm, or getting a USB 3.1 SS+ cable. I have one on order and will update when I receive it.
Click to expand...
Click to collapse
Thank you!
So this is a confirmation that this indeed is a bug needing some fix?
I did a quick look around and couldn't really find such a cable - what would I search for specifically?
I did not get confidently lucky with 65 ohm, USB 3.1 or SS+ terms..
(Also, i am quite sour about Google not including an USBCtoA connector.)

fronten said:
Thank you!
So this is a confirmation that this indeed is a bug needing some fix?
I did a quick look around and couldn't really find such a cable - what would I search for specifically?
I did not get confidently lucky with 65 ohm, USB 3.1 or SS+ terms..
(Also, i am quite sour about Google not including an USBCtoA connector.)
Click to expand...
Click to collapse
From my view it's a bug, but I don't have much to confirm with, just personal experience. I'm going to re-check Apple Carplay too to make sure it's not a vehicle fault.

Another failure.
So far I've tried 4 cables, including a USB-C 3.1 cable. I've tried 2 different cars with Android Auto support. No combination has enabled AA on the cars head unit.
I plugged my Pixel 3 into a laptop work USB 3 support and it connected to file transfer.
As a follow up, my wife's iPhone XR connects to Car Play almost instantly.

I found out my issue is specifically with Android Auto, and I have since fixed it. I had to remove all system updates to Android Auto and let it update and setup from scratch.

I finally managed to get my Pixel 3 recognized for file transfer.
Device manager showed a problem with the Portable Device - MTP device (yellow attention sign). I tried to update that driver, failing, even with the one from google directly .
However, i got the hint that missing system update (Windows) might be the culprit.
So I checked, installed the 2 it showed, and .. .. Pixel 3 showed up in device and file manager.