I can't get android auto to work with oxygen os, tried a rom like freedom and no luck. I tried different modes and MTP and nothing. Anyone has this issue or knows a fix for OOS?
Turn on USB debugging in the developer settings. It works fine for me
Sent from my ONEPLUS A5000 using Tapatalk
sdmark said:
Turn on USB debugging in the developer settings. It works fine for me
Sent from my ONEPLUS A5000 using Tapatalk
Click to expand...
Click to collapse
Interesting, not working with the debugging!
matteosaeed said:
Interesting, not working with the debugging!
Click to expand...
Click to collapse
Even here it doesn't work!
Android auto works fine for me. ExperienceOS and Ford sync 3
Gesendet von meinem ONEPLUS A5000 mit Tapatalk
For me also fine with ExperienceOS and my Skoda Fabia MKIII on my MIB II
miodzicho said:
Android auto works fine for me. ExperienceOS and Ford sync 3
Gesendet von meinem ONEPLUS A5000 mit Tapatalk
Click to expand...
Click to collapse
seatibiza said:
For me also fine with ExperienceOS and my Skoda Fabia MKIII on my MIB II
Click to expand...
Click to collapse
Which cables are you guys using ?
The original from OnePlus
Gesendet von meinem ONEPLUS A5000 mit Tapatalk
BlitzWolf 2m nylon. From Amazon.
OK. Maybe someone who reads this thread can answer this.
When I installed 4.5.5 onto the OnePlus5 it made it unseen by my wife's '16 Accord. It works fine in my truck which has a Pioneer NEX8100. I had order it for her to get back into Android and I also ordered an HTC U11 for myself. U11 works fine in both vehicles. I installed 4.5.7 today and did a factory reset. It still not seen by the Accord. I'm using the same USB-C on both phones. And no, I did not turn on usb debugging ... didn't have to in my truck before or after the reset. I didn't have it on when it was running 4.5.3 and it worked in her car.
I'm kind of at my wits end. I doubt it's her car since Honda doesn't remotely upgrade things like Infotainment systems.
Any ideas?
Also working for me! Important, take the original Oneplus cable for connecting!
slg60 said:
Also working for me! Important, take the original Oneplus cable for connecting!
Click to expand...
Click to collapse
Original cable, MOS cable, Cable Matters cable, HTC U11's cable and none of them work. The '16 Honda Accord simply won't see the phone and connect to AA. Like I say ... multiple cables made no diff and those same cables work as does the phone with my Pioneer in my Nissan Frontier. I honestly have no idea why it won't see it. It worked really well from the day I bought it until 4.5.5 was pushed and then ... nada. I ever reset her stereo back to factory per instructions I found and it still won't see it. I may try again later as I can't return it because it's outside the window. She just has no patience for "screwing around with things" as she doesn't want to have to go though that each time an update drops. So for now she's continuing to use her iPhone 6 which she hates but "it works".
Try this:
Developer options > Networking > select USB configuration > midi
Stupid question: did you guys install the Android Auto app?
If yes, does it work in stand alone mode?
Yes. Of course. It's the only way AA works. It works in stand alone mode. But has issues with some head units.
Can you guys test if AA works with other phones? Generally, if the phone is recognized by the head unit (for example in MTP mode), then there is no reason for AA not to work because of the cable.
Another approach is to see if those head units give any error messages and try to look into car brand specialized forums for similar issues. My bet is on the HU.
An update of the HU could solve a lot of issues.
PS: Testing AA on head units for a living.
daniel_loft said:
Can you guys test if AA works with other phones? Generally, if the phone is recognized by the head unit (for example in MTP mode), then there is no reason for AA not to work because of the cable.
Another approach is to see if those head units give any error messages and try to look into car brand specialized forums for similar issues. My bet is on the HU.
An update of the HU could solve a lot of issues.
PS: Testing AA on head units for a living.
Click to expand...
Click to collapse
In my case ... the wife has had this car since Sept. '15 when the first '16's came out. It's worked with multiple cables and multiple phones. It's worked with the Nexus6, 6P, Note 7, S7E, LG G6 and the HTC U11 I bought a couple weeks ago. The 1+5 worked until 4.5.5 was installed then .. nope. It's worked continuously in my truck when attached to the Pioneer NEX8100 .. both before and after a factory reset. The 1+5 after 4.5.5 simply isn't seen by her Accord. I have no idea why ... I'm starting to suspect the head unit but it works with so many other phones .. even her iPhone6 and my 7+ so it's not the USB port either. I've also factory reset her head unit with the instructions on the Honda site. Nada.
As far as vehicle specific sites ... go look at the OnePlus5 forums. There are multiple reports of AA giving up the ghost for no reason after 4.5.5. :/
Related
Has anyone seen any compatibility info with the 6P and Android Auto? I am sure there should be none, but I don't know if the USB-C would make a difference. I haven't seen any Android Auto info at all for the new Nexus models.
Thx!
Doubt it would matter, USB is backwards compatible if it's micro you would just need an adapter.
PaisanNYC said:
Has anyone seen any compatibility info with the 6P and Android Auto? I am sure there should be none, but I don't know if the USB-C would make a difference. I haven't seen any Android Auto info at all for the new Nexus models.
Thx!
Click to expand...
Click to collapse
Should hopefully work like normally, I'm gonna be using the USB-C to USB-A cable that comes in box for my car for Android Auto. Hopefully it works without any issues otherwise this would be a huge over site by Google and a huge deal-breaker for me because no way I'm not driving around with Android Auto (it has completely changed my commutes.)
Badouken said:
Should hopefully work like normally, I'm gonna be using the USB-C to USB-A cable that comes in box for my car for Android Auto. Hopefully it works without any issues otherwise this would be a huge over site by Google and a huge deal-breaker for me because no way I'm not driving around with Android Auto (it has completely changed my commutes.)
Click to expand...
Click to collapse
I agree. Android Auto makes my long commute that much bearable. Now that Amazon Prime Music works with Auto too? Sweet
Badouken said:
Should hopefully work like normally, I'm gonna be using the USB-C to USB-A cable that comes in box for my car for Android Auto. Hopefully it works without any issues otherwise this would be a huge over site by Google and a huge deal-breaker for me because no way I'm not driving around with Android Auto (it has completely changed my commutes.)
Click to expand...
Click to collapse
How's it worked out so far for you? I have no issues, so far so good. Always good to hear from other AA users since there aren't too many of us out there (yet)
Mine works fine using the cable I bought from Google.
PaisanNYC said:
How's it worked out so far for you? I have no issues, so far so good. Always good to hear from other AA users since there aren't too many of us out there (yet)
Click to expand...
Click to collapse
Ive had no issues so far! Its been amazing! Ive just been using the USB-C to USB-A cable that came with the 6P. Its the perfect length for this kinda thing!
I haven't had any problem at all. That short adapter cable is the perfect size for this. I just bought another, longer cable to use at home.
midas69 said:
I haven't had any problem at all. That short adapter cable is the perfect size for this. I just bought another, longer cable to use at home.
Click to expand...
Click to collapse
Same here. I had my installer put the USB port in where the cigarette lighter plug was (I had two of these on my dash). So I bought a Brodit Proclip mount and the short USB OEM cable works great
What do you guys choose for a USB option when you plug in your device? I tried all the options and my car and AA app don't seem to recognize. Will try a new cable this afternoon.
MoNsTeReNeRgY22 said:
What do you guys choose for a USB option when you plug in your device? I tried all the options and my car and AA app don't seem to recognize. Will try a new cable this afternoon.
Click to expand...
Click to collapse
Make sure you have android debugging on. It won't work without it.
Sent from my Nexus 6P using Tapatalk
jaben2 said:
Make sure you have android debugging on. It won't work without it.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
That's not true. I'm using a USB A to C cable I ordered from Google and it works fine on a 4100NEX.
Thanks for the responses.
It ended up being a setting on my headunit that was incorrect. It was set by default to use MirrorLink and not Android Auto, switched it up and now works perfectly! :good:
Would like to reopen this discussion as I'm buying a VW Golf TSI 2016 that has a factory installed Android Auto unit. I tried it at the dealership and it was a pain to initially connect my N6P with original USB-C to USB-A cable. It did eventually work but I had to turn on debugging, remove my lock screen pattern/security (unit in the car was saying the phone was locked and it couldn't access it but it wasn't?) ... It ultimately worked but it was a pain to setup really (took over 10 minutes). And then Maps and phone worked, Google Music wouldn't had to unplug, force close Google Music and then replug and it worked ... I tried it in a 2016 Honda Civic too while shopping and fumbled around for 20+ minutes to get it to connect ; no luck. It bluetooth paired but it was like I hadn't plugged anything in the USB port.
Of note ; in both case I compared with iPhones/Car Play : plug it in and within 3 to 5 seconds, everything is setup.
I'd be curious to see if anyone here has experience with 2016 VWs and how easy (or hard) it is to get it to connect? If I have to fumble around in the settings for a few minutes everytime I get in the car, that's a major bummer. Will try again tonight before signing paperwork.
bennyboy_84 said:
Would like to reopen this discussion as I'm buying a VW Golf TSI 2016 that has a factory installed Android Auto unit. I tried it at the dealership and it was a pain to initially connect my N6P with original USB-C to USB-A cable. It did eventually work but I had to turn on debugging, remove my lock screen pattern/security (unit in the car was saying the phone was locked and it couldn't access it but it wasn't?) ... It ultimately worked but it was a pain to setup really (took over 10 minutes). And then Maps and phone worked, Google Music wouldn't had to unplug, force close Google Music and then replug and it worked ... I tried it in a 2016 Honda Civic too while shopping and fumbled around for 20+ minutes to get it to connect ; no luck. It bluetooth paired but it was like I hadn't plugged anything in the USB port.
Of note ; in both case I compared with iPhones/Car Play : plug it in and within 3 to 5 seconds, everything is setup.
I'd be curious to see if anyone here has experience with 2016 VWs and how easy (or hard) it is to get it to connect? If I have to fumble around in the settings for a few minutes everytime I get in the car, that's a major bummer. Will try again tonight before signing paperwork.
Click to expand...
Click to collapse
Sounds like an issue with VW. My Android Auto (non-VW), set up fine. And to this day, I can use Android Auto without disabling my pattern lock.
PaisanNYC said:
Sounds like an issue with VW. My Android Auto (non-VW), set up fine. And to this day, I can use Android Auto without disabling my pattern lock.
Click to expand...
Click to collapse
Ok so ended up buying the VW and Android Auto took some time to setup the first time around but nothing as painful as when I was at the dealership. So far, 98% of the time I plugged my phone in Android Auto started within 5 seconds or so. On 2 occasions it failed to launch. One time it was kind of stuck in a loop where it would connect via Bluetooth, disconnect, try to connect via USB, fail, reconnect via Bluetooth, disconnect (and start over again endlessly). I had to unplug it and restart the car for it to work but that happened only once so...
Everything works flawlessly and is well integrated with the VW infotainment system (Google Maps voice instructions will play on top of FM radio or Sirius XM and only lower the volume of whatever is playing a tadbit, I actually did not expect that (I was expecting the sound to cut completely and then come back once Google Maps is done telling me XYZ instruction)).
2016 Kia Optimia & N6P Connection Issues
Hello,
I have a new 2016 Kia Optima and I'm been fooling around with this for 2 weeks and I can't get it connected. Here's what I've done.
-tried different cables which includes the short one that was shipped with the unit
- factory reset of the device
- turned degging off and on
- uninstalled the android app
- turned wireless off and removed the connection (that's what the Kia rep told me to do)
The only thing that I get when connected it the options to choose what to do when connected via USB. I've toggle all of them and have toggled the off and on ADD new cars to android auto button till I'm blue in the face.
Right now I'm all out for suggestions. Does anyone have any idea? It will be greatly appreciated.
Thanks,
Ron
Anyone else having a problem with no notification sound when receiving a text message. I can see the message pop up on screen but I have to be looking at the screen or I will miss the message. Happens with Messenger and Hangouts. Nexus 6P is full stock with latest firmware. Head unit is a Kenwood DDX9702S with the latest firmware.
gwojo22 said:
Anyone else having a problem with no notification sound when receiving a text message. I can see the message pop up on screen but I have to be looking at the screen or I will miss the message. Happens with Messenger and Hangouts. Nexus 6P is full stock with latest firmware. Head unit is a Kenwood DDX9702S with the latest firmware.
Click to expand...
Click to collapse
Have you tried raising the 'alert' level, available at the right side of the screen when you adjust volume levels?
Solutions Etcetera said:
Have you tried raising the 'alert' level, available at the right side of the screen when you adjust volume levels?
Click to expand...
Click to collapse
I'm having the same problem. Will try that and report back.
Got a new head unit, specifically so I could use AOA 2.0 / USB DAC with my Nexus 6P. Unfortunately, it seems that my new Kenwood DPX792BH has a specific incompatibility with the Nexus 6p? I called Kenwood about this, they didn't seem to care so far... Anyway, here are all the things I have done so far:
1) Tested my Nexus 6p with AOA 2.0 on friend's year old head unit, Kenwood KDC-X599. Sound and control via USB worked as intended.
2) Installed new DPX792BH. Nexus 6p charges over both front and back ports, but both devices wont talk at all. No warnings pop-ups or errors, just charging and nothing.
3) Tested my DPX792BH with multiple other phones. Iphone, Galaxy note 5, and Nexus 5x all work fine/as intended.
4) Tested my DPX792BH with Nexus 5x (USB-C) which also works fine/as intended.
5) Tested a different Nexus 6P. It has the exact same behavior as mine.
6) I have also tried multiple cable combinations... 3 different USB-C to USB-A cables. I used a USB-C adapter to micro USB, and that didn't work either.
Edit: Tried all possible combinations of having the Kenwood app installed or not. Had no affect on phones working or not working.
So at this point I am nearly certain that this is either a Nexus 6P bug, or a Kenwood Firmware bug, but I am not sure how to proceed.
Just to be clear here, I am only interested in this head unit if it plays digital audio via USB with my Nexus 6p. I am going to return the head unit if it will not. In this case, sound over AUX or BT are not acceptable solutions... I wish the 6P had apt-x, but it doesn't.
I guess what I am asking is, has anyone seen this and found a work around, or have any ideas? Should I be submitting a bug report somewhere?
I realize that someone will probably want to see some sort of logs, but I am not sure which ones... Let me know which ones to get and I will update this post. Thanks!
Edit: The response I got to this problem from Kenwood:
Dear Valued Customer,
Thank you for contacting Kenwood USA Corporation. We value you as a Kenwood customer and appreciate the opportunity to be of assistance.
I understand you are inquiring about the DPX792BH. The Nexus 6P is not listed on the compatibility list, unfortunately we cannot guarantee functionality. The compatibility list is available online at ###########kenwood.com/cs/ce/aoa2/. I have documented the issue. Please note that we do not have information on future updates and cannot confirm when an update will be released or what it will address. We apologize for the inconvenience.
If we can be of further assistance, please let us know at [email protected] or by phone at 1-800-536-9663. Our hours of operation are Monday through Friday 9AM to 9PM, Saturday 9AM to 6PM or Sunday 10AM to 5PM.
Janet
Product Support Representative
JVCKENWOOD USA Corporation
Phone: 1-800-536-9663
Email: ###########kenwoodusa.com/Contact/
Click to expand...
Click to collapse
Final Edit: So no firmware update from Kenwood, I am running out of time to return this unit. I will be sending it back. I also wanted to add here, if anyone else is wondering, AOA 2.0 did not work with a Nexus 6P and this unit even when I installed CM13 nightly. I then tried with Android N dev preview 5, and had no love there. The OTA Android N final just hit and I have installed it. I will update here if it does work, but if it doesn't (as I expect it will not), I am sending the head unit back an I may forget to update.
Try changing the USB Mount options under storage settings on the 6p.
Sent from my Nexus 6P using XDA-Developers mobile app
blankit said:
Try changing the USB Mount options under storage settings on the 6p.
Sent from my Nexus 6P using XDA-Developers mobile app
Click to expand...
Click to collapse
+1 should work.
blankit said:
Try changing the USB Mount options under storage settings on the 6p.
Click to expand...
Click to collapse
I don't have any changeable options in here... Settings -> Storage & USB
I'm a newb, so I can post links... Imgur lRJv2eg
Did I misunderstand something?
The above video is my review, i have it working great with my ownice c200 headunit. the usb seems to register that to the iPhone that it is a CarPlay device. the CarPlay UI apparently is stored and sent from the iPhone its self to the usb dongle and then sent to the android app. the app then sends touch and audio commands back to the usb dongle and then to the iPhone.
i can send photos of the internals of the device to any one who wants and a link to the APK.
MOD EDIT: removed email address and mention of selling head units. XDA is not a place to make money!
great !!!
i can send photos of the internals of the device to any one who wants and a link to the APK.
Can you send me?
New firmware update allowing the box application to work in the background.
https://drive.google.com/drive/folders/0Bym9XrdeViekOTF1VWRoaTlkb1E?usp=sharing
First Step: updating the CAR PLAY USB DONGLE
Plug in the car play usb dongle on the PC, copy the "update.bin" file under the root of the dongle, no extra file folder and no any operation, just wait for 5 minutes, it will be quit automatically after updating, then pull off the USB dongle.
Second Step: Uninstall the old version ZBOX softare from the car audio, then intall the new one, then it will be ok to work.(With the new APK in the attachment and follow the manual)
Hey all, I made a quick video review on the usb dongle
vassandrei said:
Hey all, I made a quick video review on the usb dongle
Click to expand...
Click to collapse
I'm interested in one of these units, how can I purchase? Thanks.
URL REMOVED
[/COLOR]
vassandrei said:
Hey all, I made a quick video review on the usb dongle
Click to expand...
Click to collapse
The issue you are experiencing with the zbox having 'stage-fright' has to do with the power requirements of the zbox device. Some USB bus' don't provide enough power (or borderline) so functionality is intermittent. If you use a powered USB hub, that provides additional power to the USB ports, you'll have almost no issues.
I have connected a y USB adapter.
Has anyone tried one of these on a PX3 RK3166 head unit?
I have one but cant get it to work.
It connects to the apk but wont connect to the iphone.
Tried the update to firmware and apk, still no joy.
Not sure if i have a faulty dongle or it's a compatibility issue with these head units.
Alibaba seller suggested not enough power on head units usb?
I have the same problem with one of these.....
I have tried three android units now and I still can’t get them to work....
Android 4.4 it says its connect but the iPhone just shows as not found....
The other two are both 6.0.1 and the zbox just shows connecting all the time!
If any one has any help it would greatfully be received..
Or for that matter any software updates.....
Mine is showing apk: 2.1.0
Zbox versions: 2.1.0
Many thanks and kind regards
Mine works and I have a px3. I updated the device and installed the latest zbox app before I tried it. I would try swapping out cords and making sure they are certified by Apple. The only issue I have with mine is that it cannot be controlled from the steering wheel.
Sent from my iPhone using Tapatalk
I use a second usb-plug and a y-cable to provide sufficient power to the device.
What do you guys do with regards to phone calls? My phone is obviously paired to the head unit via Bluetooth, so whenever I get a Call, it jumps out of CarPlay/zbox to the Stock phone interface, however the phone still transmits the audio to carplay and not via Bluetooth by default.
How any of you solved that problem?
If you are using CarPlay why do you have Bluetooth paired? Every car I've been in with CarPlay diconnects the phone from Bluetooth.
Sent from my iPhone using Tapatalk
Android Auto
Is there also a solution for Android Auto on Android Head Units ?
MarciDev said:
Is there also a solution for Android Auto on Android Head Units ?
Click to expand...
Click to collapse
https://forum.xda-developers.com/ge...ndroid-4-1-headunit-reloaded-android-t3432348
I have an Eonon GA7157 running a:
CPU: Allwinner R16 1.6GHz Cortex A7 Quad-Core
RAM: SAMSUNG DDR3, 1GB
Storage: 16GB
I have tried App and Firmware 2.x and 3.x. No joy. All I get is "Connecting" when the usb dongle and app is started. It never gets passed this "Connecting..." stage. USB devices like keyboards, mice, USB Flash drives, and even video camera work fine on this headunit. The Zbox Z1 and an OTA tuner don't work for some reason.
I did some more troubleshooting and found out the following: The dongle works perfectly on my PC running Remix. I also tried it on Samsung Table A; on this one, same symptom as the head unit, so I tried using an OTG cable and what do you know, it worked perfectly.
Therefore, I have 2 possible explanations: The headhunt's USB cable needs to be hardwire as OTG or Eonon somehow has decided to block certain type of USB devices that request data asynchronously. Why? I have not clue... I wish I could disable this flag in the OS, but I have not clue where it can be done. My headunit is rooted, so it should be possible in theory.
Hello, could you post pictures of the internals? I'm very curious what's inside the lil dongle. Also: do you still have some of the dongles? haha
osxdude said:
Hello, could you post pictures of the internals? I'm very curious what's inside the lil dongle. Also: do you still have some of the dongles? haha
Click to expand...
Click to collapse
You can buy one for $75 from Aliexpress. There is a video of the internals: check this out:
https://www.youtube.com/watch?v=VnS_TP18VBk
This guy has done a few videos on the unit.
Hey, can someone help me to find the Zbox Z APK 3.0 to Download in English?
I have the 3.0 in Chinese only. And the 2.1 doesn’t work. My Firmware is 3.0
Looking at getting this for my Mondeo. As per the subject, will it support android auto with a phone plugged in via USB or will I be best off with tethering?
https://rover.ebay.com/rover/0/0/0?mpre=https://www.ebay.co.uk/ulk/itm/311981315294
Thanks.
Sent from my MHA-L29 using Tapatalk
get this aswell: https://de.aliexpress.com/item/Carl...32826755246.html?spm=a2g0s.9042311.0.0.8ULR6U and it will work as Android auto and carplay aswell.... just got mine, and it works really well on PX3 1GB headunit.
Hello y'all,
I recently discovered by accident that when I tried plugging in my PS4 controller through the USB-C port the phone was showing headphones icon in the status bar. And sure enough, the audio wasn't coming from the phone. So can anyone test this out since I don't have any USB-C headphones, but I always wanted them.
Thanks to anyone participating in this test.
Write your results here.
Audio through USB-C works at least since Android 8.1. I've USB-C mini DAC (Hidizs Sonata HD) and works perfectly. Also I tested Nobsound NS-10g USB input via USB host adapter and also works. So, isn't a new feature of 9.0 update, if you are thinking so.
I've been using fulla schiit 2, usb audio works on 8.1
xsam123 said:
Audio through USB-C works at least since Android 8.1. I've USB-C mini DAC (Hidizs Sonata HD) and works perfectly. Also I tested Nobsound NS-10g USB input via USB host adapter and also works. So, isn't a new feature of 9.0 update, if you are thinking so.
Click to expand...
Click to collapse
Actually yes, I was thinking it's new because when I tried my friends USB C headphones it didn't respond.
But thank you for clarifying me! Your response is appreciated.
xsam123 said:
Audio through USB-C works at least since Android 8.1. I've USB-C mini DAC (Hidizs Sonata HD) and works perfectly. Also I tested Nobsound NS-10g USB input via USB host adapter and also works. So, isn't a new feature of 9.0 update, if you are thinking so.
Click to expand...
Click to collapse
Does your Hidizs Sonata work also with Android Pie? I've just got Sonata II and it works only if I connect it within one minute after reboot. After that the phone ignores it and acts like nothing has been connected (but the phone is powering the dongle as I see increased draw in logcat and hear a very faint click in the headphones). So if I want to listen via Sonata, I must connect it first and reboot the phone, then it works perfectly. I tried all the available firmwares for Sonata, it does the same with all of them. With the PC or Huawei phone it works whenever I connect the dongle, so it most probably isn't faulty USB DAC, but rather something in the phone. Also I'm missing the option "Audio source" in the USB options in the phone's settings completely, if it makes any difference/sense.
_mysiak_ said:
Does your Hidizs Sonata work also with Android Pie? I've just got Sonata II and it works only if I connect it within one minute after reboot. After that the phone ignores it and acts like nothing has been connected (but the phone is powering the dongle as I see increased draw in logcat and hear a very faint click in the headphones). So if I want to listen via Sonata, I must connect it first and reboot the phone, then it works perfectly. I tried all the available firmwares for Sonata, it does the same with all of them. With the PC or Huawei phone it works whenever I connect the dongle, so it most probably isn't faulty USB DAC, but rather something in the phone. Also I'm missing the option "Audio source" in the USB options in the phone's settings completely, if it makes any difference/sense.
Click to expand...
Click to collapse
Yes, my unit works perfectly with Android Pie, stock and custom ROM. What build are you using? Maybe something is corrupt
Enviado desde mi Mi A1 mediante Tapatalk
xsam123 said:
Yes, my unit works perfectly with Android Pie, stock and custom ROM. What build are you using? Maybe something is corrupt
Click to expand...
Click to collapse
I'm no stock Android Pie, tried the adapter with February patch. Unfortunately adapter just stopped working with all of my devices (got really hot and then died completely), so can't verify with March update.
I'm going to visit an Apple store and try their USB-C - 3.5mm adapter, it is being said to be of a very high quality and is just 10USD/EUR and available locally, so I don't have to wait more than a month for delivery of another Hidizs from China.
Apple dongle behaves the same. Working when connected within ~1 minute after reboot, won't work on later (re)connection. I tried a different kernel to no avail. Would love to know why is it happening.
Edit: it happens that I'm forgetful, see explanation below
Oh my.. I'm stupid guys, I totally forgot that I configured recommended workaround "disable USB host" for 70000.USB wakelock couple of months ago. It was running one minute after boot via Tasker, no wonders I was experiencing this. Dongle works completely fine now (except of volume buttons on the Apple DAC). Sorry for stupid confusion.