Can't use USB in car - Google Pixel XL Questions & Answers

I had the Nexus 6P (with Android 7) and plugging it into the USB worked with my 2011 Camaro (it is not Android Auto, the Head-unit basically will see the phone as a USB Storage device, mount it, index the files, and I could then use my car's controls to search, change tracks, etc).
I broke my phone and turn it in on warranty, and end up getting the Pixel XL as replacement, and upgrade it to Android 8.
Now when I plug it into my car, I get a "No supported media found" message on my car's display. I have tried with and without USB Debugging, going into the the developer options and changing the "Select USB Configuration" to MTP, Audio Source and still the same. I would also have this issue with Samsung phones, and could never get them to work.
I am not sure if this is an issue with Pixel's, or with the Android 8 update, since my Nexus 6P with Android 7 worked fine

you need to use the otg adapter that came with it

So I have to get a standard USB-USB cable to connect the adapter to my car?
I thought this adapter added functionality, so my phone can mount drives, not the other way around? Doesn't make since that something that has worked so well on the past 3 phones (except for Samsung for whatever reason) now no longer works without another piece of hardware. Not what I would call progress

So I ordered another cable and am using my OTG adapter, and it still does not work.

Related

Possible to get midi input to our phones? [YES]

Is there a way to get midi input recognized on our phones? On my pc I use the rock band 3 keytar connected via a midi to usb adapter and I can do midi playback.
Is there a way to do this on our phones via an otg cable?
EDIT: got it done! check my post below.
Sent from my SPH-L900 using xda premium
Re: Possible to get midi input to our phones?
Seems like I found qhat I needed. Will try it tonight and report.
https://play.google.com/store/apps/details?id=com.als.grandpiano.pro
Sent from my SPH-L900 using xda premium
it works beautifully and way easier than I expected.
connected my otg cable and the phone said usb connector connected (since when is this a thing!?), plugged in the midi-usb adapter to the otg cable and right away it prompted me to open with the software I linked above and another midi software I had installed.
and bam, it was working. I messed around a bit to find the better settings for my keytar, but this thing works. over Bluetooth and with the headphone plug. there's a little bit of lag over Bluetooth but for my uses I wanted it straight to the speaker so i'm using the stereo cable. now I don't need a pc to get sound out of the keytar.
mark this as one more day i'm amazed at what my phone can do.
by the way, it functions as a synth using the software I mentioned above, so I can play harpsichord, organ, piano, etc. and the sound keeps on playing even with the screen off.
happy camper = me.
Max_Pain said:
it works beautifully and way easier than I expected.
connected my otg cable and the phone said usb connector connected (since when is this a thing!?), plugged in the midi-usb adapter to the otg cable and right away it prompted me to open with the software I linked above and another midi software I had installed.
Click to expand...
Click to collapse
Looks like you had some luck... Wondering if you can help me?
I am trying to make my Android, Huawei p20 Pro, accept a MIDI signal via USB too.
I have an OTG adapter, and have tested 2 OTG adapters and 2 cords.
All work into my PC (even via an USB type-C to standard USB adaptor )
The issue seems to be that I cannot select the USB in type to be MIDI.
I have also experienced that on another Samsung Galaxy S10
I have tried opening developer settings and changing the setting "Disable USB Audio Routing" ON as per https://help.joytunes.com/en/articles/2636638-troubleshoot-midi-on-your-android-device
I have tried using it with 3 apps that accept MIDI.
Simple Piano by Joy Tunes, FlowKey and USB MIDI Monitor
Any ideas?
Environment
Huawei p20 Pro
Model: CLT-L29
Build: 9.1.0.381 (C782E11R1P11)
EMUI v: 9.1.0
Android v: 9
Similar Posts
https://forum.xda-developers.com/mi-pad-4/help/problem-recognizing-midi-device-t3877082
https://forum.xda-developers.com/oneplus-x/help/midi-usb-mode-paranoid-rom-t3430141

[Q] Logitech Unifying Receiver not working on Nexus 7 (2013)/OTG Cable Question

I'm trying to connect the unifying receiver to my Nexus 7 (2013) with an OTG cable, but it doesn't work.
USB diagnostics app by Chainfire says the kernel detects it, but the Android API doesn't (not sure what that is). All other USB devices I have tried seem to be working.
I think I read of other people having the same problem. I was wondering if this was a problem with the 2013 Nexus 7 in general. If so, is there a fix? or will there be one?
Also, I was playing with my tablet and OTG cable; I was wondering if anyone else has USB devices "sleeping" when the tablet is put to sleep.
I noticed when I plug the cable in the tablet while it is awake, and then plug in a USB device, the USB device will work fine until I put the tablet to sleep. After I put the tablet to sleep, the USB device would power off, and after waking the tablet back up, the device would remain off and unresponsive.
The workaround I found was to plug in the cable while the tablet was asleep, and then waking up the tablet before plugging in USB device. I would then be able to put the tablet to sleep with the USB device remaining powered (while it's asleep and) when it's awakened.
Sorry if this was confusing.
Thanks!
I've got a working OTG fix that does not require root after much messing about!
Go to settings and disable security lock screen then select English US as the language.
Insert OTG cable and start Nexus Media Importer.
Reboot.
Nexus Media Importer should now pop up as usual and OTG should now be working.
Change language back but do not reboot as you will have to repeat these steps.
Same problem..
I have tried nexus media importer or custom kernel, ETC.. however, the problem is occurred again.
Everytime, kernel has error like..
Code:
logitech-djreceiver 0003:046D:C52B.0018 : claimed by neither input, hiddev nor hidraw
logitech-djreceiver 0003:046D:C52B.0018 : logi_dj_probe:hid_hw_start returned error
Is there anyone uses unifying on Nexus 7 2013? :crying:
Same issue with the receiver
My Unifying receiver works on my SGS 3, but it doesn't seem to work with my nexus 7 :'(
Lurkin_Lurker said:
I'm trying to connect the unifying receiver to my Nexus 7 (2013) with an OTG cable, but it doesn't work.
USB diagnostics app by Chainfire says the kernel detects it, but the Android API doesn't (not sure what that is). All other USB devices I have tried seem to be working.
I think I read of other people having the same problem. I was wondering if this was a problem with the 2013 Nexus 7 in general. If so, is there a fix? or will there be one?
Also, I was playing with my tablet and OTG cable; I was wondering if anyone else has USB devices "sleeping" when the tablet is put to sleep.
I noticed when I plug the cable in the tablet while it is awake, and then plug in a USB device, the USB device will work fine until I put the tablet to sleep. After I put the tablet to sleep, the USB device would power off, and after waking the tablet back up, the device would remain off and unresponsive.
The workaround I found was to plug in the cable while the tablet was asleep, and then waking up the tablet before plugging in USB device. I would then be able to put the tablet to sleep with the USB device remaining powered (while it's asleep and) when it's awakened.
Sorry if this was confusing.
Thanks!
Click to expand...
Click to collapse
Any News in this area? I Bought my Nexus 7 to use it during class (as a studytool ofc) . But without having my external keyboard it isn't of much use
I've been having trouble getting my Logitech K750 keyboard to work on the nexus 7 (stock ROM, only rooted). Does anyone know if the Logitech Unifying Receiver is supported on this product? It works perfectly fine on my Galaxy Note N7000 running CM10.2
I can get other USB devices to work on the Nexus using the same OTG cable, for example Logitech MX Revolution wireless mouse, Xbox 360 controller and USB flash drives.
Same problem
I have the same issue with a stock/non-rooted Nexus 7 (2013) and my Logitech unifying receiver. Sadly all I can really say is what did and didn't work.
Does work:
OTG adapter from monoprice.com
Trendnet Powered USB 2.0 Hub (TU2-700)
Microsoft Wireless Mouse 5000
Every USB flash drive I've tried has worked via the 'Nexus Media Importer' app (FAT/FAT32 devices). Even multiple plugged-in flash drives connected simultaneously via the USB hub works just fine.
Custom built USB 2.0 External Hard Drive (using a Nexstar enclosure and Western Digital 320GB hard drive; powered off USB hub)
Apple iPhone 4s (iOS 7) - The tablet called the phone a MTP device and viewed the media (pics) through the built-in Gallery app importer
Does NOT work:
Logitech unifying receivers - Specifically, I tried with the K360, K400 and K750 keyboards and a M510 mouse
USB 2.0 10/100 Ethernet Adapter from monoprice.com (no apparent model # but it's their PID#: 9468)
USB 2.0 Logitech C910 Webcam
USB Logitech Headset G330 ...I was just curious
So far compatibility seems arbitrary. I would have thought the Nexus 7 (2013) would have better compatibility with Logitech, a maker of Google TV's, versus Microsoft or even Apple but that has not been the case. If this is a bug, it's a big one considering the popularity of Logitech devices. Sadly, I personally don't even have a keyboard that will work.
Any more details about this problem? Surely this must be a driver issue, since I don't see any other reason why the unifying receiver would refuse to work on the new Nexus 7. As stated above by others, it works perfectly fine on other devices, including the stock rom running TF101 transformer tablet.
I'm running CM nightlies on my Nexus 7 and was really surprised to see that it doesn't work with my unifying kb & mouse
---------- Post added at 01:34 PM ---------- Previous post was at 01:14 PM ----------
Just tested with a different USB tester app - the receiver is obviously recognised. The OS can see it, and gets the device/vendor ID, and the device name... but no mouse cursor
http://i.imgur.com/moYVDet.png
http://i.imgur.com/OjFGzaw.png
Tested it with an older Logitech mouse that I have (doesn't use Unifying receiver), and that worked just fine..
http://i.imgur.com/aHdk6Qv.png
http://i.imgur.com/Z8qhoFr.png
But I need the new unifying one to work, mostly for the keyboard.
This issue is discussed here: http://forum.xda-developers.com/showthread.php?t=2233849
I'm also having trouble with this. My K400, which would be awesome for tablets, isn't able to work, for it uses a Logitech unifying receiver. It seems it's a simple fix within the kernel. I've tried flashing many different kernels for this device, yet none have added support for it. The device works well on my Galaxy S4, if that means anything.
We'll need to get ahold of one of the developers and hope they're willing to add in the necessary stuff to their kernel if we want to fix this.
Could it be that a current Nexus 7 dev has to integrate some of the patches listed in some of the roms posted here: http://forum.xda-developers.com/showthread.php?t=2233849 ?
mohitrocks said:
Could it be that a current Nexus 7 dev has to integrate some of the patches listed in some of the roms posted here: http://forum.xda-developers.com/showthread.php?t=2233849 ?
Click to expand...
Click to collapse
How can we ask them that?
Anyone found any update news on this issue:?
Marty
I can't help with the unifying remote but the sleep of the USB drive drive me nuts too I was recommended this app and it worked perfectly
https://play.google.com/store/apps/details?id=com.MI.otglock
Sent from my HTC One X using Tapatalk now Free
The Logitech Wireless Touch Keyboard K400r works with its unifying receiver and OTG cable plugged into the original Nexus 7:
Android version 4.3
Build number JWR66Y
Kernel version 3.1.10-g1e8b3d8
But the above set up does not work with the 2013 version of the Nexus 7:
Android version 4.3
Build number JSS15R
Kernel version 3.4.0-g9e52a21
Bump
Solution Anyone?
Can't believe that none of the N7 developers are using a logitech device! !
I got a K400. Works fine with my nexus 5. Not with the nexus 7 2013
need an updated or custom kernel
It looks like we'll need an updated kernel, which has some extra CONFIG switches activated, per these threads:
http://forum.xda-developers.com/showthread.php?t=2233849#2
Has anyone had success with a custom kernel or rom that includes the kernel drivers for the Logitech unifying receiver?
It would be nice to have a minimally changed kernel that included support just for these new drivers:
http://androidforums.com/nexus-7-gen2-2013-all-things-root/770430-otg-cables-usb-logitech-k400r-wireless-keyboard-track-pad-area.html#post6153020
Updates?
Hey all
Was just trying out the Unifying Receiver today and was surprised and disappointed that it didn't work at all.
Has anyone managed to get it working since the last post?
P
no
After my last post, I contacted Google support. They said that they could not help, and Logitech would have to fix it. I tried to talk technical about kernel config switches, and I begged to talk to someone who understood what I was saying, but I basically was told they did not have resources to troubleshoot every possible accessory.
I contacted Logitech, and they said that Google was right. They claimed responsibility and stated they did not support Nexus 7 (2013). It would not work.
Bottom line: This accessory will only ever work in a custom ROM, if it works then.
If anyone has any luck with this accessory on a custom ROM or in any other setup, please let us know.
Earlier posts say it is recognized by the OS, but not Android API.
Then, all it needs should be the files to tell Android it is a mouse and keyboard, right? Seems like the only issueis our device didn't have it in its device list.
What file to mod, what line(s) to mod?
Has anyone found a fix for this? I just bought a Google Nexus 7 2013 - 32GB and am trying to use the unifying receiver with an OTG cable (Logitech devices are the K800 keyboard and Experience MX mouse). The unifying receiver works fine on my galaxy S5 but no luck on my nexus 7. I am currently unrooted running stock lollipop 5.0.2. I am prepared to unlock bootloader, root, and install custom kernel if necessary.
Any info to get the Logitech unifying receiver working on my Nexus 7 would be greatly appreciated.

Can't connect to a PC

Hello everybody
I got no problems in the past with the N4 and the N7 2013, but here, I'm unable to connect the N5X to my pc.
I tried to reinstall drivers (LG or google ones), but unsuccessful.
Windows 10 can't use it (error 43), and disconnect it by itself (i tried to force the drivers i want it to use, but unsuccessful).
For information, when I connect the phone, i didn't get the notification menu where you can choose which connection you want to use (charge, MTP, etc...).
I also tried debugging mode on and off. The same ****.
I suspect my USB C/A adapter . It's a cheap thing I bought on amazon for 3.99€.
Is it possible? Should I buy a cable? (i would prefer an adapter I can have on myself everyday in my wallet to be able to use with all friends cables).
Thanks.
It is that:
http://www.amazon.fr/gp/product/B01781ORKC?psc=1&redirect=true&ref_=oh_aui_detailpage_o00_s00
Well, it's just the adapter, i use it with the official cable. I will check that, thanks.
fruity101079 said:
Hello everybody
I got no problems in the past with the N4 and the N7 2013, but here, I'm unable to connect the N5X to my pc.
I tried to reinstall drivers (LG or google ones), but unsuccessful.
Windows 10 can't use it (error 43), and disconnect it by itself (i tried to force the drivers i want it to use, but unsuccessful).
For information, when I connect the phone, i didn't get the notification menu where you can choose which connection you want to use (charge, MTP, etc...).
I also tried debugging mode on and off. The same ****.
I suspect my USB C/A adapter . It's a cheap thing I bought on amazon for 3.99€.
Is it possible? Should I buy a cable? (i would prefer an adapter I can have on myself everyday in my wallet to be able to use with all friends cables).
Thanks.
It is that:
http://www.amazon.fr/gp/product/B01781ORKC?psc=1&redirect=true&ref_=oh_aui_detailpage_o00_s00
Click to expand...
Click to collapse
Adapters have known issues with working.
You need to get a usb C/A cable.
Make sure you shop around and don't get a cheap one.
It needs to meet USB C specs our you will burn out your phone and/or comp usb ports.
Yeah thanks, i just bought another adaptater (i prefer) recommanded by Benson
Thanks everyone.

PC does not recongnize the Tablet

since more than 6 months the PC or Laptop doesn't recognize the P605, I tried to change the microusb port, tried different USB ports, PCs with no luck.
When I'm connecting the tablet to PC the tablet will charge but nothing appear in the device manager, no detection at all.
appreciate your help guys solving it, I bought Tab S3 but I still like the old fellow more
No detection, so the thing's completely inert when plugged in?
When I plugged in my Note to my 3.0 USB laptop, out comes 'Device not recognised' in the taskbar, and that's it. However, it all works well when I plug it to a computer with USB 2.0 running XP/7. A brief search shows something about incompatible default/microsoft's driver with old(er) devices on USB 3.0.
As you've mentioned several attempts above including a hardware change, I believe the problem lies with software somewhere.
I have the same problem and get an "error 43" message. My Note 5 works fine when plugged in. I must have damaged the port upon changing the battery. I wanted to upgrade to 6.0 but looks like I'm out of luck....unless I can update via update.zip on my P600

S20 Plus connection stability with USB 3.0 specifically

Ok this is driving me nuts so I gotta ask...I have a S20 Plus 5G (Verizon) and have a brand new custom-built computer with a ridiculous amount of USB 3.0, 3.1 ports. I have to tether my phone to my PC for internet so I use the USB-C to USB-C cable that came with the phone to connect to the single USB-C port on the computer. I also use said connection for Samsung DEX (not simultaneously, would if I could lol).
With this specific setup, I don't have any issues at all, but I know for a fact that it's not a 3.0 connection because of the cable (the "Device can perform faster when connected to USB 3.0" message confirms as much). The cable is obviously the limiting factor holding it back from 3.0 so I tried replacing it in the setup with various (both USB-C to USB-C and USB-C to USB-A) 3.0 cables and sure enough, I get the correct "connected through USB 3.0" message under my device's name in the devices menu.
However, no matter which 3.0 cable I try or which 3.0+ port I plug it into, I always run into the issue of the device randomly disconnecting/reconnecting every so often. I get the whole disconnected/reconnected sound deal and the "select what happens with this device" Autoplay message. I've tried turning off Autoplay, turning off the USB notification message option, going into device manager/registry and ensuring that every single thing related to the USB ports has the power conservation option turned of, etc.
One major thing is that when I created a USB 3.0 "certified" connection with my mom's slightly older custom-build computer, it seemingly had no problems holding the connection, so it appears as though it's something on my computer specifically that's causing it. I just frankly have no idea what that thing could be at this point. Any ideas?
lolDayus said:
Ok this is driving me nuts so I gotta ask...I have a S20 Plus 5G (Verizon) and have a brand new custom-built computer with a ridiculous amount of USB 3.0, 3.1 ports. I have to tether my phone to my PC for internet so I use the USB-C to USB-C cable that came with the phone to connect to the single USB-C port on the computer. I also use said connection for Samsung DEX (not simultaneously, would if I could lol).
With this specific setup, I don't have any issues at all, but I know for a fact that it's not a 3.0 connection because of the cable (the "Device can perform faster when connected to USB 3.0" message confirms as much). The cable is obviously the limiting factor holding it back from 3.0 so I tried replacing it in the setup with various (both USB-C to USB-C and USB-C to USB-A) 3.0 cables and sure enough, I get the correct "connected through USB 3.0" message under my device's name in the devices menu.
However, no matter which 3.0 cable I try or which 3.0+ port I plug it into, I always run into the issue of the device randomly disconnecting/reconnecting every so often. I get the whole disconnected/reconnected sound deal and the "select what happens with this device" Autoplay message. I've tried turning off Autoplay, turning off the USB notification message option, going into device manager/registry and ensuring that every single thing related to the USB ports has the power conservation option turned of, etc.
One major thing is that when I created a USB 3.0 "certified" connection with my mom's slightly older custom-build computer, it seemingly had no problems holding the connection, so it appears as though it's something on my computer specifically that's causing it. I just frankly have no idea what that thing could be at this point. Any ideas?
Click to expand...
Click to collapse
I have not understood your intention.
Why do you have to connect the phone via USB cable to your computer?
If you have internet via mobile data on your phone and want to share it with the computer, you can tether via mobile hotspot of your phone. Just connect the computer via wifi to your phone's hotspot.
And your device should be able to use Dex wirelessly. I read about it in one of the latest Android 11 OneUI 3.1 changelog.

Categories

Resources