Related
First I have to state: I've already searched the web and xda-developers forums. Tried all solutions found, none work.
I don't connect my HTC Touch Pro 2 to my computer (Vista 32bit) often; other than the first few days, when I was downloading a lot of softwares to my device, I don't connect them at all. But the point is I was able to connect to WMDC.
Yesterday I wanted to try out Pocket Diablo, so I had to connect my device in order to install .NET CF 2.0. But I found I can no longer sync:
- Before I connect the device, I can see WMDC's green tray icon
- After I plug in the device (using the cable from HTC), WMDC's tray icon disappeared.
- I checked Device Manager, and found "Windows Mobile Remote Adapter" cannot start, error code 10. There was no mobile device listed.
- I tried another USB port, same result. I tried uninstalling all USB hubs and root hubs, let them reinstall, reconnect device, same result.
- With device still plugged in, I uninstalled "Windows Mobile Remote Adapter" and deleted the driver too. Then I unplugged device, uninstall WMDC driver update and WMDC itself, reboot PC, download WMDC6.1 from Microsoft again, reinstall WMDC, reboot, still no tray icon, and reconnect device with same result.
- I tried the above together with giving Users group full control on the registry key "HKLM\Software\Microsoft\Windows NT\Current Version\Svchost\WindowsMobile", same result.
- If I uncheck "advanced connection" on my device, there is no "Windows Mobile Remote Adapter" in device manager, but there is a generic mobile device listed. In WMDC it still thinks there is no device connected, and I cannot access the device in Windows Explorer.
- If I connect the device as a disk (under device's USB connection settings), I can access the device through Windows Explorer.
- I even hard-reset my device, still same result.
- I tested my old O2mini, same result.
- I don't recall any big changes on my system since my last successful connection.
- I tested my HTC Touch Pro 2 in my office (Vista 32bit), and it can be connected successfully.
So it seems the problem is in my home computer; the Windows Mobile Remote Adapter (version matches WMDC6.1's version) refuses to work in all cases.
Other than taking the sync cable in my office back home tomorrow, I'm all out of ideas of what to try next.
Can anyone give me a helping hand?
Bump. Please help, I really need to solve this.
- I'm taking the cable in office home, but I highly doubt that is the reason because with the cable at home I can connect as a disk and can charge.
- I notice in office (the successful case), the remote adapter is named "Windows Mobile Remote Adapter #2". At home (the failure case) there is no #number, just "Windows Mobile Remote Adapter".
Tested and it is not the cable. Cable used to successfully sync in office has same effect at home - Windows Mobile Remote Adapter cannot start, code 10.
I tried enabling WMDC debug log, but there're none - looks like the process failed at the driver stage and WMDC is not even started.
Also, when I have the device connected with the non-functioning driver, it seems to wreck havoc on my real network driver. I often need to reconnect my network connection.
Can anyone help?
It's getting weirder and weirder...
- I reinstalled WMDC for the countless time, and suddenly I am able to connect to O2mini (which does not connect via a network adapter). O2mini shows up in WMDC (can setup a partnership) and explorer. But not HTC TP2.
- If I disable advanced connection on TP2, I can connect TP2 as a Mobile device, but there is no network adapter. WMDC detects no connection, and I cannot view TP2 in explorer.
- I tried connecting O2mini again after TP2's failure, and O2mini cannot connect too - device manager shows no problem, but in WMDC I get nothing but the red stop sign and a simple message: "Error". No entries in event viewer.
And is anyone even reading this thread?
I was having a similar deal. Sync works solid on XP at home, was working but then stopped on 2 laptops with Vista and giving me those error codes.
I did the same things as unistalling mobile center on vista to no avail.
What did work was going onto the device, Start/All Applications/ActiveSync. Then Menu/Options and delete on the laptop PC's.
Now when I sync my vista laptop to the device it shows up as an additional device. I can copy files to it, I'm not sure if it syncs any other info.
The active sync also has an option for connections where you can uncheck "same for all pc's". I didn't try that one, but it might do something.
Update the Driver?
shealine said:
I was having a similar deal. Sync works solid on XP at home, was working but then stopped on 2 laptops with Vista and giving me those error codes.
I did the same things as unistalling mobile center on vista to no avail.
What did work was going onto the device, Start/All Applications/ActiveSync. Then Menu/Options and delete on the laptop PC's.
Click to expand...
Click to collapse
You mean removing the partnerships? I already did that - I had hardreset my TP2 for nothing too.
yrreP said:
Update the Driver?
Click to expand...
Click to collapse
I tried, but Vista said I already have the latest version (6.1.6965.0). I tried uninstalling (and fill the checkbox to remove the driver) and reinstalling, no difference.
It has to be something not right on my computer's drivers.
I'm going to compare the driver files of my home and office computers and see if there are any difference...
I copied all files related to the Windows Mobile Remote Adapter home, and compared them to mine. They are all identical.
I also tried forcing Device Manager to show non-present devices (by setting two environment variables), removed the related ones and tried again. Same result.
I'm all out of ideas now.
I'm even considering moving up to Windows 7 (Ultimate 64-bit), hoping that will solve my problems.
-- but what? They leave me with a nasty bug and I consider paying them even more? Whiskey, tango, foxtrot?
Awesome, finally i found someone that has (i think) 100% my problem.
Let me ask you this, what is your computer specs? Because this happened to me after i got a new computer >.< .
Mine is
Asus p7p55d LE motherboard
i5 50?
Crucial Ballistix 2GB (2 x 1GB) 240-Pin DDR3 SDRAM DDR3 1333 (PC3 10600)
I also have a HTC Touch pro2 (verizon) but i have testing my computer with a Samsung Omnia (verizon) to confirm my problem.
Edit: BTW this is on a Windows 7, just throwing it out there so that people can be even more mind boggled
Asus P7P55D Deluxe
Intel i7-860
2 sticks of Kingston 2Gb
I got my TP2 from Fortress (Hong Kong), they added a bunch of goodies in the ROM, like the radio cab, 1% battery driver, a business card scanner, etc.
You have the same problem on Windows 7? I am going to buy W7 tomorrow, I'm going 64-bit...
If I get the same problem in W7, then well, damn... at least I can connect TP2 as a driver and write data to it. But if I need to install anything from the PC-side, I'll need to rip the cab out of the installer.
holy crap then i think i know why its not working. Maybe its because of the new chipset p55? Doesnt support the drivers? or something
bornskilled200 said:
holy crap then i think i know why its not working. Maybe its because of the new chipset p55? Doesnt support the drivers? or something
Click to expand...
Click to collapse
Definitely not.
Plus I have sync'ed successfully before, and my TP2 plus cable can still sync in office, advanced connection on. It's a software problem.
I encountered the exact same error in Windows 7.
The Windows 7 is a fresh install, Windows updated, and installed 64-bit version of WMDC.
Darn.
First, sorry for my very bad english.
I had the same problem ( Error code 10 with Microsoft Mobile Remote Adapter) with p7p55d and Windows7.
It was a trouble with my asus p7p55d.
- I updated my bios to the 0711 version (this version does not appear on AsusUpdate, i found it on www.asus.com)
- I uninstall old Windows Mobile remote adapter
- I uninstall WMDC
- reboot
- simply plug my phone and let windows update do the job. This time it was good for me...
I have the same issue with ASUS P7P55D PRO and Windows 7 Ultimate 64bit, even with BIOS 0711. I tried all the ideas, nothing helps.
The same problem for me.
Windows 7 64bit,
Gigabyte P55M-UD2 Mainboard
I report great success with this problem!
Like suggested from a previous poster, i did update my bios to 605 (this is for p7p55d LE). But i noticed one thing, the setting for Plug and Play was set to that the bios handled it. I changed to so the that OS (?) handled it instead and tried everything again.
Happy to say (after some extra problems that does not pertain to this error) i finally got it to work. Hope my experience help others.
Encountered a similar issue yesterday.
WMDC could not sync. Although when selected as a disk drive, it connects fine.
What fixed it for me was to disable this setting in the device: Settings/connections/usb to pc/enable faster data synchronization.
Exit out, no reset required.
Good luck.
I have the same problem since my new gigabyte p55-ud5
i have windows 7 Ultimate. my htc diamond work fine for one week, then it stoped sync.
i think its somthing with the memory....
i tried to change the speed on my corsair DHX 2GB from 1600Mhz to 1333 and it worked for couple of days.
then it stoped sync.
tried to add voltage in bios but no good.
updated the bios - then it only worked with memory speed 1333 or 1066.
i shutdown my computer only once in a week.
then it started again. now no matter what i do - no SYNC.
i searched for this error alot and the common hardware is:
P55 + vista/win7 + HTC.
PLEASE HELP!!!!!!!!!!!!!!!!!!!!!!!!
Firm-up!
i have a good news!
Finally i got it after firm-up the bios.
Asus p7p55d turned out to got a problem installing 'Windows ... Adapter'
http://www.asus.com/product.aspx?P_ID=RBA8CzWoopUlYRFZ&templete=2
.
Description P7P55D 1002 BIOS
1. Fix PCI-E X16 may downgrade to X1 mode
2. Improve system stability
Good Luck!
USE ANY USB KEYBOARD WITH YOUR USB OTG SUPPORTED ANDROID DEVICE!!!!
I've been experimenting with Wifi cards and the samsung galaxy sII
and realized people where having the same problem as i was having with plugging in usb keyboards.
turns out it all has to do with a vendors permission issue. if your device is not in the list, it will seen as "unknown".
As it turns out you can simply add your device and it'll work. mind you it was to be a simple input device and will have the power constraints of 100mW. But if u can compile a driver and splice in dc power.... skies the limit!
steps:
1. Android must be rooted (not going over that) and must support USB OTG (on-the-go)
2. You can either buy a USB OTG micro to female adapter on ebay for like 4 bucks. i decided to make one myself since i have lots of spare parts.
Heads up: a simple micro usb to female usb connector IS NOT THE SAME AS A USB OTG CABLE, they may look the same but the OTG cable has Pin 4 grounded to pin 5 on the micro usb side. This is how the device distinguishes aach type of cable. WARNING: IF MAKING THIS YOURSELF DO NOT CROSS BLACK AND RED, this WILL fry your PHONE.if you don't know you rway around a soldering iron, just buy one
3. Check what manufacturer your device is on this chart, if it's not there, check on the internet or plug the usb device into a linux box and run "lsusb" in the command promt and look for your device, the number will look like this:
Bus ### Device ###:ID <THIS ONE!>:<more numbers> " Company"
here's the chart: (taken from here :http://developer.android.com/guide/developing/device.html)
Code:
Company USB Vendor ID
Acer 0502
ASUS 0b05
Dell 413c
Foxconn 0489
Garmin-Asus 091E
Google 18d1
HTC 0bb4
Huawei 12d1
K-Touch 24e3
KT Tech 2116
Kyocera 0482
Lenevo 17EF
LG 1004
Motorola 22b8
NEC 0409
Nook 2080
Nvidia 0955
OTGV 2257
Pantech 10A9
Philips 0471
PMC-Sierra 04da
Qualcomm 05c6
SK Telesys 1f53
Samsung 04e8
Sharp 04dd
Sony Ericsson 0fce
Toshiba 0930
ZTE 19D2
eg my keyboard is lenovo , so code is 17EF, you get it
4. log in as root, mount system as read-writeable, Create this file: /etc/udev/rules.d/51-android.rules
if its already there, then just append the command you want after.
if you dont have root explorer or otherwise installed here is how to in bash:
Code:
su
su
mount -o remount,rw system /system
mkdir -p /etc/udev/rules.d/
cd /etc/udev/rules.d/
now in the "51-android.rules" file add this line (or more for more device support):
SUBSYSTEM=="usb_device", SYSFS{idVendor}=="<VENDOR CODE>", MODE "0666", NAME=="<VENDOR>"
my example with my lenovo keyboard:
SUBSYSTEM=="usb_device", SYSFS{idVendor}=="17EF", MODE "0666", NAME=="lenovo"
save.
5. plug in the USB OTG cable and plug in your keyboard or other device. it sould say "usb host cable" then "usb device".
on some keyboards the numlock light wont work, due to the fact of power contraints on the phone, you can add support by plicing in 5v DC in to the line (soldering needed) or you can probably jsut attach a powered usb hub
And thats IT, now you can actually type documents at a reasonable pace, without paying an arm and a leg for a supported bluetooth keyboard!!!
-td8f4
* to moderators i know i have less than 50 posts hopefully i dont get banned, i thought this was considered dev*
Wow, really nice work - I wonder if some kindly ROM devs could just bake in support for all in their ROMs?
NZtechfreak said:
Wow, really nice work - I wonder if some kindly ROM devs could just bake in support for all in their ROMs?
Click to expand...
Click to collapse
wow really good work.
just another info on the price of an BT keyboard:
http://www.amazon.de/s?ie=UTF8&search-type=ss&index=ce-de&field-keywords=CHIN FAI
40 euro are not an arm and a leg
and this i ok to type on
Indeed, you can get some BT keyboards quite cheaply. I already have one, but I'd still like full USB keyboard support (I don't always have my keyboard on me, but lots of people have USB keyboards).
I tested this on an unrooted SGS (Logitech K340 unifying keyboard) and it worked fine without having to change any settings. Just plugged it into the USB OTG adapter and then plugged the adapter into the phone. It said the device was unknown but the keyboard worked when I went to type in the apps. Mice also worked. The logitech MX Performance worked fine. A bit weird seeing a mouse pointer on the phone though.
How about keyboard remapping?
Sent from my GT-I9100 using XDA Premium App
At first I thought:
"1) plug in OTG cable, 2) plug in USB keyb., 3) use"
*lol*
No, seriously, this information is VERY usefull and might open up the way not only for keyboard (as the OP stated, "get a driver compiled and the sky is the limit".
Will definitaly bookmark this thread and when I'm done with some other tinkerings try to "get the drivers compiled"
*clicksthanks*
reply
my ultimate goal is to have a external usb wifi adapter plugged into my phone so i can use it to pentest with a Backtrack 5 chroot session.
i'm working on cross compiling the RTL8187 driver for the ARM architecture.
look here for updates
HTML:
http://forum.xda-developers.com/showthread.php?p=16333147
and @ karl999999
40 euro are not an arm and a leg
and this i ok to type on
Click to expand...
Click to collapse
i know it's not expensive, but i'd really rather use something i already have, i've got a small flexible usb keyboard which works great.
As I'm trying to add joystick support on SGSII, I tried to add an xbox 360 controller and my device was not recognized. I tried this method and added "045E" as vendor but no luck, still not recognized... Any idea ?
Thanks
alx5962 said:
As I'm trying to add joystick support on SGSII, I tried to add an xbox 360 controller and my device was not recognized. I tried this method and added "045E" as vendor but no luck, still not recognized... Any idea ?
Thanks
Click to expand...
Click to collapse
Also interested in this... Sadly I dont have the skills to compile a driver myself...
Sent from my GT-I9100 using XDA Premium App
Thanks. This is so cool and I gotta try it at home later (Tried 2 different keyboards at home before but didn't work). Hopefully you could find a way to use PS3 joystick as well.
Maybe we collect a list of device code and update it a single file. Then rom developer can incorporate it into their roms.
Don't worry about post counts. The is definitively a very good finding and development progress for S2.
alx5962 said:
As I'm trying to add joystick support on SGSII, I tried to add an xbox 360 controller and my device was not recognized. I tried this method and added "045E" as vendor but no luck, still not recognized... Any idea ?
Thanks
Click to expand...
Click to collapse
We might have more luck with generic USB gamepads. I think all we need is someone who has the required knowledge to compile joydev.ko for our kernel.
testando said:
Also interested in this... Sadly I dont have the skills to compile a driver myself...
Sent from my GT-I9100 using XDA Premium App
Click to expand...
Click to collapse
My skill is quite limited too but with some reading it's not that hard (and I can give some help too).
I am looking for support for my Plantronics USB Headset. I am able to control volume through the headset when connected to OTG, but can't route audio through them.
I believe we do need generic drivers for USB Headsets. Hope one of the elite developers can help us. I will be happy to donate 5 euros for the same
Also, my Microsoft Wireless combo (Desktop 6000 v3) do not work while my wireless mouse 1000 do work absolutely fine on the Phone.
I am also looking for NTFS Mass Storage support which seems to be currently limited to FAT32 (and possibly FAT16) only.
Prankey said:
I am looking for support for my Plantronics USB Headset. I am able to control volume through the headset when connected to OTG, but can't route audio through them.
I believe we do need generic drivers for USB Headsets. Hope one of the elite developers can help us. I will be happy to donate 5 euros for the same
Also, my Microsoft Wireless combo (Desktop 6000 v3) do not work while my wireless mouse 1000 do work absolutely fine on the Phone.
I am also looking for NTFS Mass Storage support which seems to be currently limited to FAT32 (and possibly FAT16) only.
Click to expand...
Click to collapse
There is a solution for that already. Search ntfs-3g or posts started by me.
Just tried my logitech wireless keyboard but doesn't work. May need to dig out some old wired keyboard to try later.
somebody can get the USB ID of EuroCase? i can't get it from the internet
takato23 said:
somebody can get the USB ID of EuroCase? i can't get it from the internet
Click to expand...
Click to collapse
Actually, you may found the id by S2 itself. Just install a terminal emulator and do the same lsusb command.
jackleung said:
Actually, you may found the id by S2 itself. Just install a terminal emulator and do the same lsusb command.
Click to expand...
Click to collapse
Okay i could get the usb id from eurocase (i've a keyboard+mouse 2.4ghz pack) It's 1D57. Now when i connect the recivier, says "connected a usb device". But when i try to use mouse or keyboard it get stuck on one letter. I've try with a genius keyboard also (ID 0566) and it does the same... the only device that it works is a Razer mouse (without doing a thing)
My Microsoft Wireless Mouse 1000 works perfectly fine. However my other Microsoft Wireless Desktop combo (6000 v3) doesn't.
Also, I am looking for a way to use my USB headsets. I am able to control volume through it, but can't route audio through it.
Hope one of the devs here would be generous enough to help us get our devices working
Writing a driver and firmware from scrarch is quite a bit more arguous than finding one that works with linux. Look for one.
Once I get this porting business figured out ill post a tut on porting. Maybe even a small vm of the ubuntu box, to avoid rebuilding the setup
Sent from my GT-I9100 using XDA App
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.
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.
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