Database Info

[Q] [HELP] OTG not working on my Note 10.1

Hello,
I have the N8010 version with stock samsung XSA firmware and I bought a OTG cable last week and it does not work.
I am rooted. I tried to attach mice and keyboards and other devices like a pen drive but it does not work. when i connect the otg cable by it self, it shows the USB connector attached notification but it goes away in few seconds. Usb Host Controller (https://play.google.com/store/apps/details?id=hu.sztupy.android.usbhostcontroller) app does not show any device connect. I have tried connecting devices with USB debugging enabled and also it being disabled.
I also flashed cm10 and it does not show anything at all when I connect the OTG cable. I dont think there is a issue with the cable. Please help me out here. Devs, please make a kernel like the SiyahKernel (for SGS2 and SGS3)
:crying:
:crying:
:crying:
:crying:
:crying:
:crying:

hiruna said:
Hello,
I have the N8010 version with stock samsung XSA firmware and I bought a OTG cable last week and it does not work.
I am rooted. I tried to attach mice and keyboards and other devices like a pen drive but it does not work. when i connect the otg cable by it self, it shows the USB connector attached notification but it goes away in few seconds. Usb Host Controller (https://play.google.com/store/apps/details?id=hu.sztupy.android.usbhostcontroller) app does not show any device connect. I have tried connecting devices with USB debugging enabled and also it being disabled.
I also flashed cm10 and it does not show anything at all when I connect the OTG cable. I dont think there is a issue with the cable. Please help me out here. Devs, please make a kernel like the SiyahKernel (for SGS2 and SGS3)
:crying:
:crying:
:crying:
:crying:
:crying:
:crying:
Click to expand...
Click to collapse
Otg cable works with my stock N8010 WALI6 Rom from sammobile. Am also rooted.
Sent from my GT-N8010 using Tapatalk 2

Depends on the Adaptor but check if it has a small switch on it. I have one that switches from memory card reader to usb adaptor as it has both...
Might be of help to you but might not...

Sounds like a faulty adapter to me. The icon should stay when it is plugged in.

Otg cable works with my stock N8010 WALI6 Rom from sammobile. Am also rooted.
Click to expand...
Click to collapse
mine doesnt work...

Depends on the Adaptor but check if it has a small switch on it. I have one that switches from memory card reader to usb adaptor as it has both...
Might be of help to you but might not...
Click to expand...
Click to collapse
mine is just a cable.. heres the link where i bought it : http://www.ebay.com.au/itm/USB-OTG-...AU_MobilePhoneAccessories&hash=item4abbcc741a
thats the exact cable on the image that i have

Sounds like a faulty adapter to me. The icon should stay when it is plugged in.
Click to expand...
Click to collapse
ye thats what i thought, but then again how come it gives power to my usb hub (the light on usb hub lights up as it shud) but it dsnt show on the n8010 ... should I try to return as a faulty cable ?

otg works fine
got the cheapast OTG from amazon and works fine ... tested with stock n custom roms

Get the original Samsung otg adapter, it works the best.

true that
mdalacu said:
Get the original Samsung otg adapter, it works the best.
Click to expand...
Click to collapse
about time i buy a original OTG cable

I'm having an issue with OTG as well, and am wondering if anyone has experienced similar issues:
I purchased 2 different OTG connectors from eBay
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I received them today, and decided to give them a try. Plugging the OTG connector in displays the message "USB connector connected", and in the case of the Card Reader+Hub turns the power light on on the hub. However, in both cases no matter what I plug into the OTG connector (mouse, keyboard, thumbdrive, SD card) my Note 10.1 mounts the connected device, and then immediately dismounts it, and continues doing so in an endless loop.
I've tried rebooting the Note (several times), plugging the OTG connector in and then the USB device, plugging the USB device into the OTG connector and then attaching that to the Note, disabling/enabling USB Debugging. Nothing has worked so far.
I haven't come across this issue being reported elsewhere, and I do find it odd that this would occur with two different OTG connectors in exactly the same fashion.
I am running Team Union ROM on an N8010, so it's possible it could be that. But otherwise I'm not sure.

Have the same cardreader + hub OTG adaptor, works fine with memory card and flashdrives, won't work with a HDD as it requires external power and haven't tried a mouse or keyboard.
I'm using Dr Akrims JB rom....

Has anyone with the standard 4.1.1 (German leak) firmware had success with any adapters? I almost bought one and then read about issues, so I'm hesitant to buy something if it won't work. Thank you!

Fixed the issue :d
Hey guys,
sorry for this late reply, been busy
BUT,
After posting the thread, i decided to crack open the 30 pin connector (correct me if im wrong) and see if anythings wrong. so found that it was cheaply built and a wire was not soldered. i didnt return it, instead bought a new one with a card reader and one usb port. bought 2 of them just in case. both works, its great
thank you all for participating
P.S check out my facebook page @ https://www.facebook.com/pages/Samsung-Galaxy-Note-101/126675490838688 and like.

Sixaxis Controller Ironic problem...

Hello, When I have my PS3 controller plugged into my phone, when I try to pair it with sixaxis I get "No controller found - please connect it via USB cable" I even click the pair button with my Ps3 controller and still get the same message.

bloodhawk758 said:
Hello, When I have my PS3 controller plugged into my phone, when I try to pair it with sixaxis I get "No controller found - please connect it via USB cable" I even click the pair button with my Ps3 controller and still get the same message.
Click to expand...
Click to collapse
Why don't you pair it using the windows tool as you are supposed to?

CtrlAltDelIrl said:
Why don't you pair it using the windows tool as you are supposed to?
Click to expand...
Click to collapse
I did, but then I get "listening for controllers..." my guess is that my chipset may not be supported, (New MTK 6592)
I get "Pairing request" when I try connect it dircetly with bluetooth, however it wants me to enter a PIN code, 4 digits, I've tried 0000 and 1234. When I enter the PIN nothing happens, controller continues blinking.

How can we help you with this little info? Seriously!!
Either write down ALL the steps you've done or just don't bother asking for help here!

CtrlAltDelIrl said:
Why don't you pair it using the windows tool as you are supposed to?
Click to expand...
Click to collapse
CtrlAltDelIrl said:
How can we help you with this little info? Seriously!!
Either write down ALL the steps you've done or just don't bother asking for help here!
Click to expand...
Click to collapse
No need to be rude, I've written down everything I've tried now.
First of all, I'm trying to get my ps3 controller working on my phone, the phone is a Jiake V8 with a MTK6592 chipset with bluetooth and android 4.2.2.
The controller works as intended with the USB cable in. And shows up in USB Host Controller as a ps3 controller.
The first thing I was I paired my ps3 controller with the Sixaxis Pair Tool for windows, I've tried the same with MotionJoy.
Next I ran Sixaxis Controller on my android and started searching for controllers, I got to the part were it says "Listening for controllers"
The ps3 controller just flashes without any results.
Next thing I did was trying to pair the controller via Sixaxis controller on Android, I connected the controller in the OTG port, runs as intended, I can browse the menus and play games with it while it's in USB. So in Sixaxis controller I hit "Pair" with the controller in the usb port, and it tells me "No controller found - please connect it via USB cable".
Third thing I did was trying to connect it directly to bluetooth, I then again paired the controller just in case, started Bluetooth on the phone and started the controller, the phone finds it, and it ask me for a PIN code, I do not have any codes but they usally are 0000 or 1234 so I tried both of them, when I enter the PIN code nothing happens, the controller continues blinking.

I'm not trying to be rude honestly. It's just so frustrating when people assume we are mind-readers by supplying virtually no info.
I'd scan through this page and see if you've missed something.
Maybe you got a typo in the MAC address?

CtrlAltDelIrl said:
I'm not trying to be rude honestly. It's just so frustrating when people assume we are mind-readers by supplying virtually no info.
I'd scan through this page and see if you've missed something.
Maybe you got a typo in the MAC address?
Click to expand...
Click to collapse
From what I've read in This topic I think that the MTK 6592 chip isn't supported as for now.
I'm pretty sure I got the right MAC adress, I've tried resetting bluetooth settings without luck.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

I'm not convinced it has anything to do with the chipset at all. Maybe your kernel doesn't have the sixaxis drivers?
---------- Post added at 03:57 AM ---------- Previous post was at 03:53 AM ----------
Is your phone rooted?

CtrlAltDelIrl said:
I'm not convinced it has anything to do with the chipset at all. Maybe your kernel doesn't have the sixaxis drivers?
---------- Post added at 03:57 AM ---------- Previous post was at 03:53 AM ----------
Is your phone rooted?
Click to expand...
Click to collapse
hmm... Could be the kernel. Problem is that I got close to no knowledge about kernels, is it easy to flash one that got support for it? : /
The phone is fairly new so there's really no roms/kernels as I know.
Oh, forgot to say my phone is rooted.

bloodhawk758 said:
hmm... Could be the kernel. Problem is that I got close to no knowledge about kernels, is it easy to flash one that got support for it? : /
The phone is fairly new so there's really no roms/kernels as I know.
Oh, forgot to say my phone is rooted.
Click to expand...
Click to collapse
Ah bummer! Was hoping you weren't rooted! Can you try a mate's XBox360 controller or Wiimote? At least that would let you know if it's a driver issue.
Good luck

CtrlAltDelIrl said:
Ah bummer! Was hoping you weren't rooted! Can you try a mate's XBox360 controller or Wiimote? At least that would let you know if it's a driver issue.
Good luck
Click to expand...
Click to collapse
Now I've tried the app called Wiimote Controller. I click "Init and connect" and then the search button on my Wii mote, wait 5 seconds and then it shows a error message for less than a second and closes the app. ( crashing )
The error message I get is:
Initializing...
Searching...
Found 1 wiimote(s)
Connecting.
An error occour Last error: Adress family not supported by protocol
When I try to connect it directly via bluetooth it wants me to enter a PIN code which shouldn't be required.
On their FAQ site it says that with the protocol error the device might not be supported.
: (
I do not have access to an Xbox Controller.
EDIT: http://android.ccpcreations.com/wc-compatibility Says 4.2.2 don't support wiimote controller D:

dont worry man i have the same problem too. my chipset is mt8692 also.. rooted lenovo a536. and im sure bluetooth address is correct. because everytime i try to connect the controller directly to phone bluetooth the phone detects it and requesting to input pin to controller. but sixaxis wont connect to controller. and also i tried to connect it in my galaxy duos and it paired running good. so i think the problem is our phones are not supported. i think.

Pioneer AVH-4000 NEX connecting with App Radio and ARUnchained

Okay, so instead of hijacking the ARUnchained app I decided to create a troubleshooting thread for fellow Pioneer 4000NEX owners to get their phones to connect with basic App Radio and ARUnchained.
In your replies please try to include the following of your phone
Model Number:
OS Version:
Kernel:
Type of MHL cable used & WHERE you purchased it ( I think this is a big issue as well that I have read on many forums lots of bogus connectors)
My setup is the following and these are my Phone specs:
Galaxy Nexus (Roger Canada)
Android Version 4.3.1
Cyanogen mod 10.2.1-maguro
Kernel - 3.0.101 Franco Kernel Knightly
Here is my Car Start Up Procedure.
I make sure BlueTooth is on my Nexus.
I start ARUnchained
Turn my car on and make sure the BT is connected for phone calls.
I plug in my MHL Cable (MonoPrice MHL adapter)
I hit the Home button to go to the layout to bring up which source you want to choose and I make sure i see the HDMI lit up
I can see that my apps button on the touch screen is available
I got into the apps with mirroring automatically.
I hit back or exit button on my touch screen of the deck to exit out of appradio and it goes to mirroring.
This worked for 2 days but all off a sudden I am getting the Red X and the pointy finger. For No reason. So now when I leave work I will try rebooting my phone and trying that again.
I don't think this phone has KNOX.

Please Help!!
Dharmaboy75 said:
Okay, so instead of hijacking the ARUnchained app I decided to create a troubleshooting thread for fellow Pioneer 4000NEX owners to get their phones to connect with basic App Radio and ARUnchained.
In your replies please try to include the following of your phone
Model Number:
OS Version:
Kernel:
Type of MHL cable used & WHERE you purchased it ( I think this is a big issue as well that I have read on many forums lots of bogus connectors)
My setup is the following and these are my Phone specs:
Galaxy Nexus (Roger Canada)
Android Version 4.3.1
Cyanogen mod 10.2.1-maguro
Kernel - 3.0.101 Franco Kernel Knightly
Here is my Car Start Up Procedure.
I make sure BlueTooth is on my Nexus.
I start ARUnchained
Turn my car on and make sure the BT is connected for phone calls.
I plug in my MHL Cable (MonoPrice MHL adapter)
I hit the Home button to go to the layout to bring up which source you want to choose and I make sure i see the HDMI lit up
I can see that my apps button on the touch screen is available
I got into the apps with mirroring automatically.
I hit back or exit button on my touch screen of the deck to exit out of appradio and it goes to mirroring.
This worked for 2 days but all off a sudden I am getting the Red X and the pointy finger. For No reason. So now when I leave work I will try rebooting my phone and trying that again.
I don't think this phone has KNOX.
Click to expand...
Click to collapse
Did you ever find a solution to the problem?
I am running...
Model Number: SPH-L900 (galaxy note 2)
OS Version: 4.4.2
Kernel: 3.0.31-1561791
Cable>> CableMatters MHL converter from Amazon (Thinking this could be the main problem)
The only mods done to this stock note 2 from Sprint are: rooted and disabled KNOX. I initially had a bt connectivity problem, where after running aru and attempting to connect it would just show disconnected after about 10 seconds.
I somehow got this solved after multiple reboots and permission fixes through rom manager. I was also having the same problem you are having now with aru giving me the proverbial finger. The fix permission and reboots also solved this problem.
The problem I am having now, is the touch functionality is not working on my HU. The bt stays connected, rotation works, and everything mirrors smooth, but I have to use my actual phone. It let me calibrate the screen during the initial setup, but when I double tap mode the only thing that changes is the toolbar to the left goes away. Touching the display on HDMI mode only activates the HUs normal functionality (down arrow in top left corner to change input, etc.)
Have you or anyone else had this problem? Do you have any ideas on what might be causing this? I've been at this for some time now an getting pretty damn frustrated.
Thanks in advance!

weavedirch said:
Did you ever find a solution to the problem?
I am running...
Model Number: SPH-L900 (galaxy note 2)
OS Version: 4.4.2
Kernel: 3.0.31-1561791
Cable>> CableMatters MHL converter from Amazon (Thinking this could be the main problem)
The only mods done to this stock note 2 from Sprint are: rooted and disabled KNOX. I initially had a bt connectivity problem, where after running aru and attempting to connect it would just show disconnected after about 10 seconds.
I somehow got this solved after multiple reboots and permission fixes through rom manager. I was also having the same problem you are having now with aru giving me the proverbial finger. The fix permission and reboots also solved this problem.
The problem I am having now, is the touch functionality is not working on my HU. The bt stays connected, rotation works, and everything mirrors smooth, but I have to use my actual phone. It let me calibrate the screen during the initial setup, but when I double tap mode the only thing that changes is the toolbar to the left goes away. Touching the display on HDMI mode only activates the HUs normal functionality (down arrow in top left corner to change input, etc.)
Have you or anyone else had this problem? Do you have any ideas on what might be causing this? I've been at this for some time now an getting pretty damn frustrated.
Thanks in advance!
Click to expand...
Click to collapse
Huzzah I figured it out!!
Okay here is the issue. My phone already had AppUnchained running in the background in a sleep function. See that little icon next to my phone missed called? Thats the BT function waiting in AppRadio. This means that as I hooked up my phone. AppRadioUnchaine was already running.
Notice how my functions on the right side are greyed out? That's when you get the Red Finger of X.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Here is my Screen Mirroring but look.....Greyed out menu on the left Meaning again Red Finger of X
Here it is running in the background on my phone as well..in the background
Here is what I did :-
I put it in Hibernate using Greenify.
Then I fire up ARU and hit the Home Button and looky here, My HDMI is lit up and my APPS is hilighted now meaning it can run Apps off the phone
I Hit Apps in the Head Unit and volia No Red Finger and I know that because the Left menus is now available.
I exit the App on the HU touchscreen. And Voila full touch screen controlling my phone. You know you will NOT get the Red Finger of X because the Left Menu is now touchable.
Any question ask away. But I think this is the issue. APU not closing properly. Seems that the HU Likes it only on a fresh new instance of ARUnchained. otherwise Red Finger of X. Remember , You might have to unplug your phone a couple of times for ARUnchained to start up and detect it. It's something to do with the MHL Cables.

I forgot to mention on this unit that you have to set the function of AV Input to OFF, or else you will get a side menu on the left (even with screen mirrored) every time you attempt to touch the screen. Also Clicking on the HDMI just tells the HU "Go Show me whats being displayed" and every time you go to touch it, you will get a AV input overlay which is useless.
You have to get it to be in Apps mode for your touch and screen mirroring to work.

I've found that all you need to do to get the touch working... is plug in your phone first and THEN connect your bluetooth. Then touch works fine every time. You don't need to keep restarting ARU.
Also, anyone know a way to get rid of the left side menu so the phone mirroring and touch is full screen?

Touch Problems
Thank you for all the tips; your the man Dharmaboy75!!! I'll mess with it tonight after I get off work and post an update later. I'll also try anujpuri85s method and report back on what worked. Thanks again guys!!

anujpuri85 said:
I've found that all you need to do to get the touch working... is plug in your phone first and THEN connect your bluetooth. Then touch works fine every time. You don't need to keep restarting ARU.
Also, anyone know a way to get rid of the left side menu so the phone mirroring and touch is full screen?
Click to expand...
Click to collapse
I tried this and had no luck. The 4000NEX starts to demand a BT or HDMI Source. When I say HDMI source it goes a mirrored screen in with an AV output overlay which is not available to touch control.
I retried my method this morning, Made sure ARU is in Hibernated states. Hooked up my phone to the deck via BT and then plugged in my phone to the MHL cable.
I hit the home button, then went to the Apps touch button on the HU and voila full mirroring with touch control and no Red Finger of X.
This could be something to do with my Nexus (2011 Model) and this deck but it is confirmed working with these steps.

Can anyone recommend a ROM for a note3 ATT?

john94si said:
Can anyone recommend a ROM for a note3 ATT?
Click to expand...
Click to collapse
I have a Note 2, Installed the Jedi ROM last night, Mirroring and functions work great with genuine Samsung MHL cable. Flawless.
I would lean towards getting a Jedi ROM working on your phone.

john94si said:
Can anyone recommend a ROM for a note3 ATT?
Click to expand...
Click to collapse
you will need to do this as well
http://www.droidviews.com/disable-knox-security-service-on-samsung-galaxy-devices/

Damn Chromecast is not compatible with both my Nexus and Note2. So looks like my cable method is my only choice

Well I am using a OnePlus One now. I was able to use Chromecast (connecting to my OnePlus via WIFI Hotspot) and was able to mirror my image . I am able to get touch working etc but the only issue now is the image is too big on my 4000NEX. Anyone have an idea?

Greyed out HDMI
I have the Avh 4000nex. Everything works well with the system. The only problem I'm having is that the HDMI sign is greyed out whenever I plug in a HDMI cable. I've tried 4 different HDMI cables all high speed but it won't connect with my phone at all. I have the Galaxy Note 2. I do have a pioneer bypass installed but it works fine. What can be the problem?

Hi all,
Today my AVH-4000NEX got installed and I came across this thread. I need a advise.
My understanding is that I need to buy one of those bypass cables to be able to use MirrorLink while driving?
Also, other then original Samsung MHL adapter (ET-H10FAUWESTA) I will need usb cable (kind that is not only for charging) ?
Just want to get the list of things I will need in order to get it to work.
TIA

Kooljazz. I'd talk to the installation guys. This doesn't sound right. What are you plugging in on your side of the cable? mhl?
Sent from my A0001 using Tapatalk

JohnnyBeGood113 said:
Hi all,
Today my AVH-4000NEX got installed and I came across this thread. I need a advise.
My understanding is that I need to buy one of those bypass cables to be able to use MirrorLink while driving?
Also, other then original Samsung MHL adapter (ET-H10FAUWESTA) I will need usb cable (kind that is not only for charging) ?
Just want to get the list of things I will need in order to get it to work.
TIA
Click to expand...
Click to collapse
Yup. Mhl needs USB power.
Sent from my A0001 using Tapatalk

Dharmaboy75 said:
Kooljazz. I'd talk to the installation guys. This doesn't sound right. What are you plugging in on your side of the cable? mhl?
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
I have a MHL and a Samsung AllShare cast hooked up. I called a pioneer rep and they were saying that it doesn't work because phone is running 4.4 kitkat. The head unit only works for 4.3. I also successfully rooted my phone ad it still doesn't work.

I used the Jedi X Rom so that I could use the Franco kernel. It allows the phone go to permissive SE Linux. Stock is okay but fire me a PM to test this later. Last I used my Note 2, I had it working perfectly with Franco kernel and Jedi X Rom. Stock Note 2 Rom is very locked down. Pioneer are dumbasses and will never firmware this to work. They want you to buy a new deck.
Sent from my A0001 using Tapatalk

I got it to work here's what I had to do http://forum.xda-developers.com/showpost.php?p=56168695&postcount=7427
Sent from my SCH-I545 using Tapatalk

I have an HTC one with HTC mhl adapter. What settings should be used in the head unit? I got to input settings, smart phone, and then I choose "other" in place of iPhone. Below is an option for USB, HDMI or BT Wireless. Should I set it to USB or HDMI? Also, should I be selecting the "aha" source or "HDMI" source? HDMI source just shows my screen on the unit with no control. I have latest at unchained and root. Thanks in advance.

USB Audio

Hi all,
Just brought a Pixel 32gb coming from the 6P. With the 6p, I'm able to use USB-audio to my cars radio no problem. However, with my pixel - it doesn't want to work. Upon connection, it cycles through the USB modes (Charging, PTP and Audio Source,) which interrupts the connection process. With the 6P, it's a constant 'audio source' USB mode.
I should mention, that the times I've got it working, I've had to wait for the connection to time out, and cause my radio to throw up an 'Android error' (unable to connect.) Then I simply went into developer options and selected 'audio source' as the default method. When this worked, I wasn't able to use the radio buttons (pause / play and seek.)
Nexus 6P - 7.1 dev preview
Pixel - 7.1
Radio: Kenwood KDC200UB.
Thoughts anyone?
Thanks in advance,
Chicken

It doesn't sound like your head unit is demanding "USB audio" and I don't believe it should.. It sounds like your 6P is connecting as a hard drive and you're able to use the head unit to control the tracks. This is how pretty much all after market head units work, I don't believe there are any head units that act like a USB DAC (straight thru USB audio controlled solely by the phone with an analog/digital output).
In my case with my DEH4800BT, my Pixel automatically mounts as storage and the head unit reads the music content and is able to play/pause/skip directly from it. This should be what happens in your case, I had to play with mine a few times in order to get it to work.
Edit: I'm going to play with the OTG adapter and a male/male USB cable to see how my head unit connects. Just as an experiment.

I can assure you, my 6p is not acting as a hard drive due to the radio not supporting MTP. It's a Kenwood KDC200UB. It's using USB-passthrough, and yes, the radio does support it and many others do too.
You may search the radio google, and you'd find a feature called 'hand mode.' This allows Google play etc to pass audio.

You are right, I should have done the research. However your head unit is using AOA and not USB audio in the traditional sense, it's allowing the head unit to be a human interface device and not (just) a DAC .
Your Kenwood head unit technically requires the use of the Kenwood Music Play app however my pioneer also states it needs an app but I don't use one. I did have to cycle my device into midi mode once before it worked you could give that a try or maybe your head unit needs a software update? Are you using the cable that came with the Pixel?
Thank you tho, I never would have fully understood AOA if you hadn't suggested that I look it up.

Last firmware update was last year, the nexus 6p wasn't on the supported device.
It did try to connect to an accessory, which I thought was strange

mine did too the first time, which is why i shuffled thru the usb modes. When i was reading about AOA i found out that its now depreciated, so there wont be anymore updates for it.

k.s.deviate said:
mine did too the first time, which is why i shuffled thru the usb modes. When i was reading about AOA i found out that its now depreciated, so there wont be anymore updates for it.
Click to expand...
Click to collapse
I'm sure AOA2 is still being worked upon, no?

Just an update: popped into a car audio Centre, and tried roughly 40 headunits. Didn't work on any of them. I'm almost positive this is a 7.1 issue

I believe you need to change the way it connects to your USB port in the car. I changed it from charging to reading files. Pull down the notification bar and click on the USB notification to select how it connects to the car. Worked for me.

pixel-painter said:
I believe you need to change the way it connects to your USB port in the car. I changed it from charging to reading files. Pull down the notification bar and click on the USB notification to select how it connects to the car. Worked for me.
Click to expand...
Click to collapse
I'm guessing your using MTP connection, which does work. However, after trying 2 pixels, and a Pixel XL - as well as having someone in America try with a similar head unit - it's definitely a pixel bug / issue.
To reiterate, MTP works fine - but using Audio out VIA USB does NOT

Suicidal Chicken said:
I'm guessing your using MTP connection, which does work. However, after trying 2 pixels, and a Pixel XL - as well as having someone in America try with a similar head unit - it's definitely a pixel bug / issue.
To reiterate, MTP works fine - but using Audio out VIA USB does NOT
Click to expand...
Click to collapse
While I understand what you mean by MPT, you might be confusing some people since it isn't listed as such on my phone and probably for others too. It is listed as "Transfer files" as in my screenshot below. Perhaps it is a brand specific issue related to proprietary software, or a mod or app installed. I bought mine directly from Google and have never had this issue once File transfer is selected, but my pixel seems to default to "Charge this device" every time even if I change the settings.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

pixel-painter said:
While I understand what you mean by MPT, you might be confusing some people since it isn't listed as such on my phone and probably for others too. It is listed as "Transfer files" as in my screenshot below. Perhaps it is a brand specific issue related to proprietary software, or a mod or app installed. I bought mine directly from Google and have never had this issue once File transfer is selected, but my pixel seems to default to "Charge this device" every time even if I change the settings.
Click to expand...
Click to collapse
My phones not rooted, it's stock. Your image is relating to MTP / file transfer. My issue is related to Audio Out via USB using the AOA (Android Open Accessory) protocol.

Suicidal Chicken said:
My phones not rooted, it's stock. Your image is relating to MTP / file transfer. My issue is related to Audio Out via USB using the AOA (Android Open Accessory) protocol.
Click to expand...
Click to collapse
What is the drawback of starting using the method that works and stopping using the method that doesn't work?
A moment of nostalgic want for the old days?
If AOA is depreciated, 7.1 has forgotten it so it is not technically a bug but unsupported.
I get it is annoying if you're losing features to use the current working method of MTP / file transfer. Is that the case?
If AOA is depreciated, you may need to adapt to continue.
Sent from my sailfish using XDA Labs

nednednerb said:
What is the drawback of starting using the method that works and stopping using the method that doesn't work?
A moment of nostalgic want for the old days?
If AOA is depreciated, 7.1 has forgotten it so it is not technically a bug but unsupported.
I get it is annoying if you're losing features to use the current working method of MTP / file transfer. Is that the case?
If AOA is depreciated, you may need to adapt to continue.
Click to expand...
Click to collapse
It works on the 6p with 7.1 Dev preview.
Google's guidelines for nougat were that devices MUST be compatible with AOA. It's a bug.

Having this issue too and it sucks. I had a Nexus 5 and a Pioneer MVH-X380BT and it sounded great with the usb cable. Now with my Pixel my deck says error-19 every time I plug it in. I've tried going into the dev settings and changing the usb configuration and the app SoundAbout and it didn't make a difference. It was a pretty big difference in sound quality on the Nexus 5 between usb and bt and it's lame that the Pixel doesn't have the same audio support.
It would be amazing if Google backported aoa or someone made a mod to add it. That would be worth rootingng my phone for.

I also tried to connect my phone through USB, but it's not successful. Why google didn't provide an easy solution for such a long time?

I have a Pixel 2 and cannot get Audio out of phone to AOA device.
https://source.android.com/compatibility/android-cdd.pdf
In documentation it reads:
SHOULD NOT implement AOAv2 audio documented in the Android Open Accessory
Protocol 2.0 documentation. AOAv2 audio is deprecated as of Android version 8.0
(API
level 26). (page 102)
WHY must you do this Google!!!! :crying::crying::crying:

Zlink v. 4.0.8

I can't get wireless android auto working on my PX6 MAX 10.
I have the Bluetooth connected to my phone and my phone connected to the head unit's hotspot but nothing happens.
Works over wired though...

Not mtcb

marchnz said:
Not mtcb
Click to expand...
Click to collapse
Can you please explain a little bit more? It's an HA MCU so MTCD/MTCE (running MTCE HA 3.67 right now).
What does the MTC'b' MCU have over the MTC'e'?

ruinertt said:
Can you please explain a little bit more? It's an HA MCU so MTCD/MTCE (running MTCE HA 3.67 right now).
What does the MTC'b' MCU have over the MTC'e'?
Click to expand...
Click to collapse
Originally posted in mtcb forum, I requested mod move to MTCD forum.

marchnz said:
Originally posted in mtcb forum, I requested mod move to MTCD forum.
Click to expand...
Click to collapse
Understood.
With that said, has anyone gotten wireless Android Auto to work with this version (it shows as an option)? Is it even possible without the 5Ghz antenna on the unit?

ruinertt said:
Understood.
With that said, has anyone gotten wireless Android Auto to work with this version (it shows as an option)? Is it even possible without the 5Ghz antenna on the unit?
Click to expand...
Click to collapse
Did u find an answer ? Or a solution ?

Taha429 said:
Did u find an answer ? Or a solution ?
Click to expand...
Click to collapse
Yeah, it works just fine with the newer zlink app versions. Both Android Auto and Carplay wireless work perfect.

ruinertt said:
Yeah, it works just fine with the newer zlink app versions. Both Android Auto and Carplay wireless work perfect.
Click to expand...
Click to collapse
Even though your head unit doesn't have 5 GHZ ? What version is that cuz i bought mine with zlink avctivated and it says it the latest update.

Taha429 said:
Even though your head unit doesn't have 5 GHZ ? What version is that cuz i bought mine with zlink avctivated and it says it the latest update.
Click to expand...
Click to collapse
Yes, even with just the 2.4Ghz antenna. I run something like 4.0.23, but it's been working since 4.0.17 I think? It goes back to last year for sure. Just upgrade the Android OS and MCU and it will come with a ZLINK app update as well. https://www.dasaita.com/community/forum/topic/36770/firmwares

ruinertt said:
Yes, even with just the 2.4Ghz antenna. I run something like 4.0.23, but it's been working since 4.0.17 I think? It goes back to last year for sure. Just upgrade the Android OS and MCU and it will come with a ZLINK app update as well. https://www.dasaita.com/community/forum/topic/36770/firmwares
Click to expand...
Click to collapse
I think its android 10. how to update it ?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Taha429 said:
I think its android 10. how to update it ?
View attachment 5467881View attachment 5467883
Click to expand...
Click to collapse
Your version of Zlink should work for wireless AA and Carplay. No need to update Android 10 just to update Zlink.

ruinertt said:
Your version of Zlink should work for wireless AA and Carplay. No need to update Android 10 just to update Zlink.
Click to expand...
Click to collapse
I have to root my device to update zlink ? It should be working when i connect my phone to the car wirelessly it say android auto connected please continue on your car but zlink keeps on saying waiting untill i plug it with usb

Taha429 said:
I have to root my device to update zlink ? It should be working when i connect my phone to the car wirelessly it say android auto connected please continue on your car but zlink keeps on saying waiting untill i plug it with usb
Click to expand...
Click to collapse
No, no need for root. Also, you can only typically update ZLINK when you update Android using Dasaita's update packages. You can't find Zlink outside of the Dasaita package, typically. Either way, your version is sufficient enough to run AA wireless.
I forget how I did it exactly, but you need to connect your phone (via USB) to your car and start Android Auto. Make sure that you are connected to your head unit via Bluetooth. Then, go into the Android Auto settings and click the toggle to connect Wirelessly. What the app will do is create a hotspot on your head unit and your phone will connect to that hotspot. Actually, connect it via USB, get it running, then disconnect the USB while the car is one and AA is running. That might launch the wireless connectivity as well.
Here is a video on it (although I don't remember having to do all of that):
Here is a link the the MCU firmware and Android update:
Firmwares | Dasaita
Warm Notice： If your system is working well, please do not upgrade it !!!Because the upgrade is risky, it might lead to CRASH, BLACK SCREEN, OR SYSTEM ERROR; Unless there is a major bug in the car system, it unable to be used normally. At this time, you can choose to upgrade the system to...
www.dasaita.com

ruinertt said:
No, no need for root. Also, you can only typically update ZLINK when you update Android using Dasaita's update packages. You can't find Zlink outside of the Dasaita package, typically. Either way, your version is sufficient enough to run AA wireless.
I forget how I did it exactly, but you need to connect your phone (via USB) to your car and start Android Auto. Make sure that you are connected to your head unit via Bluetooth. Then, go into the Android Auto settings and click the toggle to connect Wirelessly. What the app will do is create a hotspot on your head unit and your phone will connect to that hotspot. Actually, connect it via USB, get it running, then disconnect the USB while the car is one and AA is running. That might launch the wireless connectivity as well.
Here is a video on it (although I don't remember having to do all of that):
Here is a link the the MCU firmware and Android update:
Firmwares | Dasaita
Warm Notice： If your system is working well, please do not upgrade it !!!Because the upgrade is risky, it might lead to CRASH, BLACK SCREEN, OR SYSTEM ERROR; Unless there is a major bug in the car system, it unable to be used normally. At this time, you can choose to upgrade the system to...
www.dasaita.com
Click to expand...
Click to collapse
I just updated my firmware using the dasaita public firmware since my hu is not dasaita and zlink got updated and literally once i connected to the bluetooth wireless AA worked since i already had everything done on my phone but like the theme and apps layout are so bad its all white with the application only do i need to install a theme or a mod and i didn't update my mcu. btw i don't know the maker of my hu I think its a chinese company under the name SK VISION. Thanks alot for your help