Related
Hello!
I have been asked into looking for usb host support for nook touch. The hardware appears to be pretty similar to Nook Color, so there were no troubles in that area.
The kernel used by B&N for the Nook Touch is somewhat older than .32 kernel used for Nook Color, so the patch itself required some massage. Surprisingly B&N kernel already has usb host support compiled in, so you don't even need to change anything in kernel config, just apply the patch.
Just like in Nook Color, the id pin in the usb receptacle is not connected anywhere, so a special app is needed to switch the host mode on and off. The Nook Color usbhost switcher should work: https://github.com/verygreen/Nook-Color-usbhost-switcher though I cannot compile it for eclair, so I guess that needs some more massage and help here would be appreciated.
Meanwhile you can simply switch the mode from adb, type
Code:
echo host > /sys/devices/platform/musb_hdrc/mode
to enable usb host mode and type
Code:
echo peripheral > /sys/devices/platform/musb_hdrc/mode
to disable it.
The LED at the bottom that usually indicates charging status will light up in usb host mode even if the power is not connected.
The upside is you don't need a special OTG cable and can just use gender changer on your existing nook cable if you so desire.
Now, problems
I have not tracked why yet, but self powered mode only works when you try to enable it first with external power plugged in first.
The user-friendly tool for usbhost mode switching needs to be compiled for eclair
The self-powered mode is very faint. Keeps up with my keyboard, but not even with a simple usb hub.
Battery drain is significant, though not sure what part of it is attributed to the usbhost mode and what to adb over wifi
Eclair init is buggy so input devices are unusable without a patch, see commit 6405c6953fa02d41d9f6377f4cdb947604f481c4 in google tree to sytem/core/init. I am attaching recompiled init binary that works.
Attachments: binary.zip contains:
uImage - prebuilt 1.1 kernel with the patch
uRamdisk - root ramdisk with fixed init, adb over wifi
init - just recompiled init binary for those who might need it
usbhost_patch.zip - just the patch itself in it's current form.
THANKS TO:
andrewed, who asked me to do this and also provided me with a device. He is on a quest to touchtype on e-paper with a USB physical keyboard, all described here: Project: E-Paper Tablet (typable!)
Thats just awesome, thanks!
Now the only thing missing is a good ebook composer and publisher, and it becomes symetrical.
That is awesome! How about audio and serial ports?
Thanks!
bisbal said:
That is awesome! How about audio and serial ports?
Thanks!
Click to expand...
Click to collapse
Audio will most probably require external power source. Also to make audio work there would need to be some changes to the libaudio, likely similar in nature to stuff I did for Nook Color, only for this older release of Android.
Serial ports will likely work as is as I don't think they draw too much power. The kernel support for usbserial would need to be added of course.
Possibility for Bluetooth dongle? And thus audio?
Sent from my GT-I8150 using xda premium
Thiso said:
Possibility for Bluetooth dongle? And thus audio?
Click to expand...
Click to collapse
Should be possible, but would require external power for the bt dongle I would think.
Verygreen,
As of now, what is the use? Can I put an external keyboard as it is? Does it need a driver (or something of the sort) for that? Can I put a usb stick? Audio and BT, as I can see, need an extra effort...
Anyway, thank you for your effort. I thought I'd never see something like that for the STR.
apeine said:
Verygreen,
As of now, what is the use? Can I put an external keyboard as it is? Does it need a driver (or something of the sort) for that? Can I put a usb stick? Audio and BT, as I can see, need an extra effort...
Anyway, thank you for your effort. I thought I'd never see something like that for the STR.
Click to expand...
Click to collapse
You can use keyboard and mouse as is with just the files posted, no extra drivers need. Everything else would need more work at the android side.
for some phones it is possible to buy usb to audio jack converter, e.g.
http://www.amazon.com/Headphones-Ea...6?s=electronics&ie=UTF8&qid=1327504575&sr=1-6
I don't know how much effort and changes is needed on kernel side to make it work though.
---------- Post added at 04:26 PM ---------- Previous post was at 04:21 PM ----------
Do I need to copy all three binaries? Also, could you prepare uRamdisk with adb over usb (not wifi) enabled? Thank you in advance.
cceerrtt said:
for some phones it is possible to buy usb to audio jack converter, e.g.
http://www.amazon.com/Headphones-Ea...6?s=electronics&ie=UTF8&qid=1327504575&sr=1-6
I don't know how much effort and changes is needed on kernel side to make it work though.
Click to expand...
Click to collapse
Those are not applicable, since they aren't actually connected to the USB port. On some phones, the USB "plug" is modified to connect with extra pins -- which carry audio signal.
cceerrtt said:
Do I need to copy all three binaries? Also, could you prepare uRamdisk with adb over usb (not wifi) enabled? Thank you in advance.
Click to expand...
Click to collapse
You need the kernel uImage and uRamdisk files, init is already included.
As far as adb over usb is concerned, it's a bit pointless since there is only one usb receptacle, so you can either connect with adb over usb or connect some usb device, but not both at the same time.
That's why wifi makes more sense.
verygreen said:
Should be possible, but would require external power for the bt dongle I would think.
Click to expand...
Click to collapse
BT USB dongle consumes almost same as USB mouse
http://www.tomsguide.com/us/squeezing-more-life-out-of-your-notebook,review-583-26.html
Since USB mouse is working, BT USB might be feasible as well...
verygreen said:
You need the kernel uImage and uRamdisk files, init is already included.
As far as adb over usb is concerned, it's a bit pointless since there is only one usb receptacle, so you can either connect with adb over usb or connect some usb device, but not both at the same time.
That's why wifi makes more sense.
Click to expand...
Click to collapse
My point is that you don't need wireless access point with adb over usb. It is also more secure than adb over wifi with lower power consumption. Whenewer I need adb over wifi, I can enable it using one adb command. Moreover, using both adb and keyboard attached to nook would not be very frequent scenario (at least in my case).
Thiso said:
BT USB dongle consumes almost same as USB mouse
http://www.tomsguide.com/us/squeezing-more-life-out-of-your-notebook,review-583-26.html
Since USB mouse is working, BT USB might be feasible as well...
Click to expand...
Click to collapse
I've tried a few BT dongles and they can be detected without external power, but I have yet to figure out if BT communications can be driven without external power as well.
USB Host Mode Swicth for Nook Simple Touch
Attached is a Nook Simple Touch version of verygreens USB Host Mode switching app.
Requires properly installed "su" in /system/bin
Let me know if there are problems.
Let's hope so. But I have good hopes as BT intention is to be low power communication. In the post I was referring to earlier, the power communication of BT in use was similar to USB mouse in use...
Sent from my GT-I8150 using xda premium
Would this cable work for host? I've had cables refuse to work with other devices for no apparent reason before, and I don't really want to order something that won't work.
http://www.amazon.com/female-Micro-male-Cable-Adapter/dp/B005GI2VMG/ref=pd_vtp_e_77
TorimuNooter
I'll try to get this included in my TorimuNooter root! Maybe version 0.5 I'm working on 0.4 right now and I can't include your USB host support because it's not yet complete, but I will try to implement it as soon as I can.
Good work!
@Googie2149: Any standard USB cable will work as well as any other.
The ID pin on the micro USB connector on the Nook is not going anywhere so a special OTG cable is not required.
I loaded in the new uImage and uRamdisk and things act more consistently, but I still can't get a keyboard to work.
Neither of the two utilities out there seem to work correctly for me. I do have su installed. I have had more success with simple commands
Code:
echo host > /sys/devices/platform/musb_hdrc/mode
echo peripheral > /sys/devices/platform/musb_hdrc/mode
cat /sys/devices/platform/musb_hdrc/mode
One thing is clear; the Nook adheres to the USB standard for supplying power, that is, it supplies it for 100 millisecs and if the peripheral signals back correctly it continues to supply it. Issuing a host command cause the red LED to flash for about a 1/10 of a second. Supplying power on the red wire is not necessary for host communication.
My setup has a powered hub and a cable with the red lead not carried through. I can issue a host command but it never seems to communicate. The status reads back "a_wait_vrise".
Does anybody have any insight into the FSM to say what is going on?
Hi
Can someone answer if USB OTG is supported on the One V
using stock kernel and ROM?
Regards
max
EDIT: After some searching I found that "official" it is not suported
What surprises me is that in the kernel configuration of the stock
kernel all options are set that I would assume to allow OTG
e.g. there is something like
...
CONFIG_USB_MSM_OTG:
Enable this to support the USB OTG transceiver on MSM chips
...
Would be nice if someone could enable this for One V. This kernel project is enabling OTG for One X http://forum.xda-developers.com/showthread.php?t=1640532
Otg only works in bootloader....
Sent from my HTC One V using XDA
Hy
Actually we are talking here about USB-Host support and not USB-OTG
regards
max
maxwen said:
Hy
Actually we are talking here about USB-Host support and not USB-OTG
regards
max
Click to expand...
Click to collapse
Isn't it the same?
USB On-The-Go, often abbreviated USB OTG, is a specification that allows USB devices such as digital audio players or mobile phones to act as a host allowing a USB flash drive, mouse, or keyboard to be attached and also connecting USB peripherals directly for communication purposes among them.
http://en.wikipedia.org/wiki/USB_On-The-Go
Hi
hlavicka82 said:
Isn't it the same?
Click to expand...
Click to collapse
USB-OTG also means that you dont necessarily need a powered hub to use it AFAIK
And USB-OTG means that "both sides" can act as a client or a host
From your link above
...
USB OTG defines two roles of devices: OTG A-device and OTG B-device. This terminology defines which side supplies power to the link, and which is initially the host. The OTG A-device is a power supplier, and an OTG B-device is a power consumer. The default link configuration is that A-device act as USB Host and B-device is a USB peripheral. The host and peripheral modes may be exchanged later by using HNP. Because every OTG controller supports both roles, they are often called "Dual-Role" controllers rather than "OTG controllers"
...
Whereas USB-Host means that the android device is always the host
Since the HTC is not providing power on its USB port you always
need to use a powered usb hub in this case.
I am pretty sure that we can have USB-Host on the V since other devices
using exactly the same chipset can do it. But I still need to do some investigation
regards
max
Hi Guys
See attached screenshot and notice the "mouse pointer"
So it means we will have USB host support!
Actually not much was "missing" the guys at HTC just
"forgot" to register the usb host driver on init
At the moment the "mode" musst be switched manually
between "host" and "peripheral" which means e.g. charger a.s.o
The automatic switch based on using a OTG cable is not working
or I have the wrong cable
SO I was able to connect a active hub with a mouse and it works
Next thing will be a usb storage device
I will still need some more time to finalize this.
This will then continue in the Titanium-KISS kernel thread
regards
max
Lol why do you have an app for screen shots?
Sent from my GT-P7500 using xda app-developers app
Hi
Just a short update
-OTG cable detect working
that means switching between host and peripheral (normal) mode works
automatically. No need for a script anymore
-USB keyboard tested and works
-USB storage is still killing me
regards
max
Hi
Update:
http://forum.xda-developers.com/showthread.php?goto=newpost&t=1794497
Regards
max
Hi
Just found a nice other xda thread about USB host
http://forum.xda-developers.com/showthread.php?t=1820375
Info there applies nearly 1:1 to KISS kernel
regards
max
Hey...i am on stock rom and kernel..can uab otg work for me..if yes then tell me the setup...
Sent from my HTC One V using Tapatalk 2
I also wan to use otg on my one v.
Sent from mah Htc one V.
My buddy gave me what I assume to ba a cheap OTG cable and when I Try to use a mouse to scroll on screen it's no bueno.....any suggestions or maybe phone doesn't support it? Kernel issue though doubtful? Thanks to ANY responses
You have power source support???.....cuz One v doesn't support power to USB otg.....
Sent from my HTC One V using xda premium
handryg555 said:
You have power source support???.....cuz One v doesn't support power to USB otg.....
Sent from my HTC One V using xda premium
Click to expand...
Click to collapse
Thanks I didn't know this........ thought I was crazy or just a cheap otg cable.......
The right kernal for otg to work
if i wanted to use custom kernal that supports the use of otg and exacting how to flash-install the virgin moble cdma primo c..and what r the dangers of doing this..and is there a easier way to do all this.? i'm only after the use of OTG for some games..
aaronrw said:
Thanks I didn't know this........ thought I was crazy or just a cheap otg cable.......
Click to expand...
Click to collapse
Dude there's always thanks button.....
Sent from my HTC One V using xda premium
handryg555 said:
Dude there's always thanks button.....
Sent from my HTC One V using xda premium
Click to expand...
Click to collapse
All out for the day I guess. Seriously:what:
sentfromybrain
I'm trying to get USB Host mode working on my CDMA HTC One V (PrimoC) too. I've read that the GSM version of the HTC One V (PrimoU) supports USB Host Mode with the Titanium-KISS kernel, but unfortunately there is not a CDMA version of that kernel. I'm trying the SuperSick kernel on my PrimoC but haven't had any luck with USB Host Mode yet.
The first thing to do is make sure you have the right cable setup. From what I've researched, you need a setup like in this thread:
http://forum.xda-developers.com/showthread.php?t=1820375
The USB Y cable approach sounds likeliest to work. They have two USB Type A male connectors (the type that plugs into a computer USB port) on one end and either a USB Type A female connector or a USB Type B/Mini-B male connector on the other end. These sometimes come with external USB hard drives that need more power than one USB port can provide. You plug the main Type A male connector into your USB OTG adapter and plug the second Type A male connector into a power source like the charger that comes with the HTC One V. You connect the other end of the cable to your device (mouse / keyboard / hub / etc). As far as I know, the power pins on all the connectors on such a cable are all connected together (+ to +, - to -) so that power flows from your external power source into the phone and your connected device.
There is also mention of using USB hubs that are externally powered. Supposedly some of these also supply power back to the phone, which I'm guessing is necessary but I'm not sure. None of the powered hubs I have seem to power the source USB connection, and actually have an internal diode that probably prevents this from being possible without modification.
Of course, you still need to have a kernel with USB Host Mode support.
Apparently there is a subtle terminology difference between "USB OTG" and "USB Host Mode", mainly with regards to the fact that the HTC One V doesn't output power to the USB power pins as far as I know. See:
http://forum.xda-developers.com/showthread.php?t=1771135
lanigera said:
Supposedly some of these also supply power back to the phone, which I'm guessing is necessary but I'm not sure.
Click to expand...
Click to collapse
If you have such a hub it will make the y-cable unneccessary
to allow charging of your HOV while using USB host mode
To make USB devices work you also need to load the required
kernel modules e.g. HID, mass storage, ....
Depends on the kernel creator if it includes those into the kernel or
as separate modules
For my PrimoU kernels you will find here http://forum.xda-developers.com/showpost.php?p=28599248&postcount=2
some scripts that will load the required kernel modules.
You MUST do this before attaching the USB host cable
maxwen said:
For my PrimoU kernels you will find here http://forum.xda-developers.com/showpost.php?p=28599248&postcount=2
some scripts that will load the required kernel modules.
You MUST do this before attaching the USB host cable
Click to expand...
Click to collapse
I'm starting to wish I had bought a PrimoU instead of a PrimoC so I could just use your kernel.
I looked at your USB scripts, and I think something may be slightly different / missing in the kernel I am using (latest SickKernel) which prevents them from working for me.
I mounted /sys/kernel/debug/ and it seems I have some an msm_otg driver loaded, but there is no "/sys/kernel/debug/msm_otg/mode" control file, just two other control files.
There is a read/write "/sys/kernel/debug/msm_otg/aca" which says "disabled" that I can set to "enabled". But, I still get an empty "/sys/bus/usb/devices/" directory when I plug in my hub.
There is also a read-only "/sys/kernel/debug/msm_otg/chg_type" that says "USB_SDP_CHARGER" when my hub is plugged in and "INVALID_CHARGER" when nothing is attached.
The usbhid.ko, usb-storage.ko, and hid-topseed.ko kernel modules (which I assume depend on msm_otg working) are nowhere to be found, so I'm guessing their functionality is either built into the kernel or not included yet.
I'm tempted to try compiling & modifying the kernel source myself, but I can't until I upgrade my computer.
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.
As the thread title states, I want to find out if the Wileyfox Swift support USB OTG? I have tried attaching a USB flash drive via the cable that used to work with my One Plus One that I had, but it does not respond when connected to the Wileyfox Swift. Any ideas? Thanks for any help!
Ill test it in 15 mins and get back to you.
I think I might have used OTG via TWRP recovery, but don't know about the ROM
Thanx for checking this. It would be great if there's a way to get this to work but I also wouldn't be surprised if the phone cannot support OTG.
It doesn't look like it is configured for OTG. It might be changeable via a custom kernel going by Chainfire's USB Host app.
I did not try the 'fix' in the second app as I don't have a current backup.
It might also not work because you have a wrong OTG cable since many microUSB cables won't work with the Swift
You might want to try using externally powered usb hub or Y shaped OTG cable to power the flash drive. I don't have any at the moment to try. Most likely it will turn out that the microUSB on the phone doesn't have the wiring to provide power (as it was for Nexus S but can be used if powered externally).
Maybe anybody can make OTG support in kernel and it will work with Y cable like on Nexus4?
r25txe said:
I did not try the 'fix' in the second app as I don't have a current backup.
Click to expand...
Click to collapse
seems like the 'fix' don't work...
h t t p : / / imgur.com/pY0zWOr
http://forum.xda-developers.com/showpost.php?p=65353312&postcount=84
cac2s said:
http://forum.xda-developers.com/showpost.php?p=65353312&postcount=84
Click to expand...
Click to collapse
Thanks for the update. As I stated in the beginning, I am not surprised that Wileyfox Swift doesn't support USB OTG. It's still a good phone despite this omission.
While the kernel that comes with it does not support USB-OTG, it is not impossible that a kernel with support could be built. The APIs are there, they just need instructions to call them.
I'm not too fussed about it, if it had no portable SD card support I would be annoyed, but having the card allows much of the usage cases of USB-OTG.