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
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.
Hi!
Does anyone know how to connect a controller to the OP3? I tried Bluetooth/sixaxis and OTG.
Bluetooth: Can connect to it but wont work in emulators or games.
Sixasis: Wont find the controller
OTG: Light DS4 controller is orange (So it is connected) but won't work in supported games or emulators.
OS: OxygenOS 3.1.2
I tried support but they just say it is not supported. USB controller support is native in Android OS, right? See OnePlus forum where we discuss the problem at hand. Maybe someone here knows a solution. Support OP says it is not supported on OP3. As far as I know it worked on OP1 and OP2.
I really want to play Pokemon en OoT!
annetimdegraaf said:
Hi!
Does anyone know how to connect a controller to the OP3? I tried Bluetooth/sixaxis and OTG.
Bluetooth: Can connect to it but wont work in emulators or games.
Sixasis: Wont find the controller
OTG: Light DS4 controller is orange (So it is connected) but won't work in supported games or emulators.
OS: OxygenOS 3.1.2
I tried support but they just say it is not supported. USB controller support is native in Android OS, right? See OnePlus forum where we discuss the problem at hand. Maybe someone here knows a solution. Support OP says it is not supported on OP3. As far as I know it worked on OP1 and OP2.
I really want to play Pokemon en OoT!
Click to expand...
Click to collapse
Which bluetooth controller do you have? I have the Moga Pocket and it does work, though it took some fiddling around with different apps and then adjusting settings in the emulators.
Prozart said:
Which bluetooth controller do you have? I have the Moga Pocket and it does work, though it took some fiddling around with different apps and then adjusting settings in the emulators.
Click to expand...
Click to collapse
I connected my Playstation 4 Controller through USB.
annetimdegraaf said:
Hi!
Does anyone know how to connect a controller to the OP3? I tried Bluetooth/sixaxis and OTG.
Bluetooth: Can connect to it but wont work in emulators or games.
Sixasis: Wont find the controller
OTG: Light DS4 controller is orange (So it is connected) but won't work in supported games or emulators.
OS: OxygenOS 3.1.2
I tried support but they just say it is not supported. USB controller support is native in Android OS, right? See OnePlus forum where we discuss the problem at hand. Maybe someone here knows a solution. Support OP says it is not supported on OP3. As far as I know it worked on OP1 and OP2.
I really want to play Pokemon en OoT!
Click to expand...
Click to collapse
Have u enabled otg in the settings?
cyraxx84 said:
Have u enabled otg in the settings?
Click to expand...
Click to collapse
Yes, I enabled it. Hoped that would do the trick. No luck there
I'm having the same issue connecting my DS4 controller. It connects to the sixaxis app properly, but the nothing responds to my inputs. I am using oxygen 3.1.3. I'm guessing a different rom will probably fix the issue, but then I'd lose dash charging. Is there any work around? I was considering buying an otg cable later today, but wont since OP has had no luck with it.
nigerson said:
I'm having the same issue connecting my DS4 controller. It connects to the sixaxis app properly, but the nothing responds to my inputs. I am using oxygen 3.1.3. I'm guessing a different rom will probably fix the issue, but then I'd lose dash charging. Is there any work around? I was considering buying an otg cable later today, but wont since OP has had no luck with it.
Click to expand...
Click to collapse
Hi, Thank got i'm not alone! Next step in the process. Installed BlissPop ROM and that made it only worse. There is no way to enable OTG on CM13. So I thought, lets restore my back-up. Now my security pattern is not recognized . Let's hope the already second running restore will work.
Anyone got another plan?
annetimdegraaf said:
Hi, Thank got i'm not alone! Next step in the process. Installed BlissPop ROM and that made it only worse. There is no way to enable OTG on CM13. So I thought, lets restore my back-up. Now my security pattern is not recognized . Let's hope the already second running restore will work.
Anyone got another plan?
Click to expand...
Click to collapse
I tried contacting OnePlus support. Their response was that the OP3 is a very sensitive device and is very sensitive to input and is not designed to work with a PS4. I don't even know where they got PS4 since I didn't even mention that I was using a DS4 with my OP3.
I'm interested in using my phone as a OTG portable test monitor by allowing the USB-C Port to be an HDMI Input.
I've found several videos online showing how to make this happen.
HackADay Link
Youtube Link
In short the steps are - Have USB debugging on. Have A USB HDMI capture card. Use a USB capture App. Hook it all up, input signal. open the app.
I Used this capture card (Capture Card Link) and the "USB Camera" App.
(App LINK)
I got it working properly on my old Moto Z2 Force (Android 9).
However to my surprise, it doesn't work at all using the same setup on both my Rooted SM-N9750 N10+ (android 11) and my Stock SM-G960U1 S9 (Android 10) Samsung phones...
Anyone have an idea on how to get this to work on Samsung devices?
Did New android versions/ Samsung do something to make it not work properly (DEX)?
Hope we can figure this out! Either way though, it might work on your old phone.
Edit:
-I managed to get it to work on my note10+ by switching the video source (Nintendo Switch) and messing with the apps resolution settings.