Attend XDA's Second Annual Developer Conference, XDA:DevCon 2014!
5,807,518 Members 50,771 Now Online
XDA Developers Android and Mobile Development Forum

Shield Nvidia button Tweaks and Moga Pro HID tweaks

Tip us?
 
tridium
Old
#11  
Junior Member
Thanks Meter 0
Posts: 4
Join Date: Oct 2010
Question Not recognizing the KL files after updating image

So I have a nexus 5 and was running the factory 4.4.2 image and these KL files worked great (the moga files). After updating to the new 4.4.3 image the device doesn't seem to load them. Anyone have any ideas? It's almost as though it doesn't know those files were put there, but I copied them over from a directory in the /sdcard with root explorer and updated the permissions just like I did originally.

Only oddities I can think of is that the OTA failed (I rooted but didn't flash the team win bootloader so OTA's could still work, update did work on my wifes rooted nexus 5) for me so I had to download the factory image and flashed the update without the -w flag so that it would keep my user partition.
 
tridium
Old
#12  
Junior Member
Thanks Meter 0
Posts: 4
Join Date: Oct 2010
Quote:
Originally Posted by tridium View Post
So I have a nexus 5 and was running the factory 4.4.2 image and these KL files worked great (the moga files). After updating to the new 4.4.3 image the device doesn't seem to load them. Anyone have any ideas? It's almost as though it doesn't know those files were put there, but I copied them over from a directory in the /sdcard with root explorer and updated the permissions just like I did originally.

Only oddities I can think of is that the OTA failed (I rooted but didn't flash the team win bootloader so OTA's could still work, update did work on my wifes rooted nexus 5) for me so I had to download the factory image and flashed the update without the -w flag so that it would keep my user partition.
So after doing some more research it seems that the product code wasn't the same anymore. instead of 0dad it was 6271, so after renaming the vendor specific file to incorporate the correct product code, it worked again for me. I don't know enough about things to know why that would have changed, but before that rename it was just using the Generic.kl as it was before.

I got the code it wanted by adb shelling into the device and running a dumpsys input. One of the lines under the Moga had it's vendor and product code in it.
 
ciphray
Old
#13  
Member - OP
Thanks Meter 34
Posts: 41
Join Date: Apr 2010
Quote:
Originally Posted by tridium View Post
So after doing some more research it seems that the product code wasn't the same anymore. instead of 0dad it was 6271, so after renaming the vendor specific file to incorporate the correct product code, it worked again for me. I don't know enough about things to know why that would have changed, but before that rename it was just using the Generic.kl as it was before.

I got the code it wanted by adb shelling into the device and running a dumpsys input. One of the lines under the Moga had it's vendor and product code in it.
that's definitely interesting that the device portion would change, the triggers still work as analog? even windows gives the vendor id and device id as the 0dad one, only thing that comes to mind is maybe the newer version of android is seeing some other piece of hardware in the controller before the HID device and using that since the vendor portion isn't changing
 
tridium
Old
#14  
Junior Member
Thanks Meter 0
Posts: 4
Join Date: Oct 2010
Quote:
Originally Posted by ciphray View Post
that's definitely interesting that the device portion would change, the triggers still work as analog? even windows gives the vendor id and device id as the 0dad one, only thing that comes to mind is maybe the newer version of android is seeing some other piece of hardware in the controller before the HID device and using that since the vendor portion isn't changing
Yeah, very weird. The only thing I can think of that I've done is that I have taken the controller apart. I was trying to see if there was any way i might make some adjustments to the d-pad. But other than taking the case apart and having the board being a bit on the free side for a bit, I didn't end up doing anything to the controller. It works fine as well, so I doubt anything I did could have changed that code.
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes


Android App Review: Control Your Phone with Quick Control Panel – XDA Developer TV

Your Android smart device has many features that you … more

Play Music on Android Wear with Stellio Music Player

Android Wear smartwatchesare growing inpopularity every day. Some devices have already … more

Schedule is up for xda:devcon ’14

With xda:devcon ’14 just around the corner, and the venue close to selling out, there is a lot … more

aLogcat Returns Thanks to XDA Love

The developers of Android, that is Google, gave users several great debugging tools that can be used in … more