I can get the OUYA controller connected fine, but the button mappings are terribly wrong. I found a keylayout file, but the tablet doesn't seem to want to use it. I tried it with my S3 running CM 11 and it was able to use it and the mappings are fine. I'm running a rooted 10.6.A.0454 and I've done the following.
1. Copied the keylayout file Vendor_2836_Product_0001.kl to /system/usr/keylayout (verified the Vendor and Product #s are correct)
2. Set the group to root and gave it permissions 644 (like all the other .kl files)
3. Rebooted tablet
I don't know why it doesn't want to work because I've gotten that exact file to work on older builds for the tablet, as well as my S3 running CM11. Any suggestions would be appreciated. Thanks.
cain05 said:
I can get the OUYA controller connected fine, but the button mappings are terribly wrong. I found a keylayout file, but the tablet doesn't seem to want to use it. I tried it with my S3 running CM 11 and it was able to use it and the mappings are fine. I'm running a rooted 10.6.A.0454 and I've done the following.
1. Copied the keylayout file Vendor_2836_Product_0001.kl to /system/usr/keylayout (verified the Vendor and Product #s are correct)
2. Set the group to root and gave it permissions 644 (like all the other .kl files)
3. Rebooted tablet
I don't know why it doesn't want to work because I've gotten that exact file to work on older builds for the tablet, as well as my S3 running CM11. Any suggestions would be appreciated. Thanks.
Click to expand...
Click to collapse
CM11 is android 4.4.4 as far as i remember. Stock 10.6.A.0454 ROM is android 5.0.2.
So the file you are copying is from different android version, which seems to be incompatible.
You can update to CM12(.1) and copy the same file to 10.6.A.0454 firmware or update to stock 5.1.1 ROM (10.7.A.0.222).
Secondly there is SixAxis controller app which will (presumably) help you to change keyboard mapping without messing with Vendor_2836_Product... files.
So this way is less difficult, i think. But the app is paid and you need root-access to use it.
Related
I don't get it. I'm on caulkin and clems 2.2 rom and when I try to change the keyboard it warns me of possible data collection and asks if I want to proceed....but the box wont stay checked. Both slideit and swype do this. I haven't found shapewriter yet. Someone tell what I am doing wrong plz!!!! I can't stand this keyboard.
The rom you are using does not support changes in keyboard. Do this:
1) Open root explorer
2) Navigate to sdcard/data/apps
3) Long press>edit>copy the apk of the keyboard you want to use
4) Navigate in root explorer to system/data/apps
5) Mount r/w
6) Paste
7) Mount r/o
8) <<Do the same for all your other input methods you want to install>>
9) Reboot and it now works.
amusedkid said:
The rom you are using does not support changes in keyboard. Do this:
1) Open root explorer
2) Navigate to sdcard/data/apps
3) Long press>edit>copy the apk of the keyboard you want to use
4) Navigate in root explorer to system/data/apps
5) Mount r/w
6) Paste
7) Mount r/o
8) <<Do the same for all your other input methods you want to install>>
9) Reboot and it now works.
Click to expand...
Click to collapse
First, I just wanted to thank you since no one else replied! I tried to upgrade to the latest Calkulin and Clem combo but the tablet doesn't like the newer kernel so I put Pershoot's latest kernel on instead.
Robeet is apparently pulling all his ROMs and developing one called Mountain Laurel. Honestly, I don't know what a good ROM is. I want GPU acceleration so I guess that means I have to use a 2.2 ROM because Ginger doesn't accelerate. And I want NTFS access.
ANYWAAAAYyyyy..... I tried to find the apk in the sdcard/data/apps and it didn't seem to be there. I tried to move the original installer apk file (sitting in my download folder) to the folder you suggested but I'm guessing that it's not THAT apk you are telling me to move. But may be I'm wrong.
Any idea what I'm doing wrong? Besides this and not getting any EA games to work (??...they won't download additional data) I actually like the ROM I'm on.
So unless you think I should change ROMs or know what I'm doing wrong I guess I'm screwed right now.
Hey,
No problem I was equally new 2 months back and had great help from the community. Next time when you can solve probs for others do it too
I personally love Roebeet's roms so i think TNT Lite is awesome.
If the apk is not there, it is probably in data/apk_private. Btw, if you are using swype, the beta version doesnt seem to work -> i tried a month back. Not sure about slideit. I used shapewriter before on the g tab and found it incredibly ugly haha.
For swype you need a modded version:
Instructions:
1) Google this: swype v2.6.48.12226 wsvga
2) Click on first result
3) Go to post 53 and read it.
Disclaimer: i found this over the net as well.
Has anyone tried to reinstall the stock asus Keyboard app?
I know it's the "keyboard.apk".
I tried to install it via root explorer by moving it to /system/app then giving it all permissions and rebooting. But it still won't show up.
Any ideas?
The stock keyboard isn't inside Keyboard.apk; that only contains the shortcuts for the Asus dock keys. The Asus Keyboard is inside XT9IME.apk.
**Edit**
Never mind I found it on this old post. You need these files:
Needed for software keyboard:
XT9IME.apk
/system/lib/libjni_xt9input.so
/system/lib/libjni_xt9kcm.so
/system/usr/xt9
I yanked these out of the revolver rom and put them in place with root explorer.
Now I'm good to go. Thanks agentdr8.
apollostees said:
**Edit**
Never mind I found it on this old post. You need these files:
Needed for software keyboard:
XT9IME.apk
/system/lib/libjni_xt9input.so
/system/lib/libjni_xt9kcm.so
/system/usr/xt9
I yanked these out of the revolver rom and put them in place with root explorer.
Now I'm good to go. Thanks agentdr8.
Click to expand...
Click to collapse
I know this is an old post, but it's the only thread where I found someone was able to successfully install the Asus keyboard on a custom ROM. I have the files you listed, but I'm unable to copy them to the required folders. I tried with a regular file explorer as well as a root explorer. I am running CM10.1, rooted of course.
jleonard711 said:
I know this is an old post, but it's the only thread where I found someone was able to successfully install the Asus keyboard on a custom ROM. I have the files you listed, but I'm unable to copy them to the required folders. I tried with a regular file explorer as well as a root explorer. I am running CM10.1, rooted of course.
Click to expand...
Click to collapse
So I found another thread which included a file called asus_keyboard.zip which I simply needed to download and install from recovery mode, but after doing that when I select the Asus Keyboard I just keep getting the error message "Unfortunately Asus Keyboard has stopped". And it keeps popping up every 2 seconds until I disable it. Any ideas?
Here's where I found it: http://forum.xda-developers.com/showthread.php?t=1542502&highlight=keyboard
Hi there,
I upgraded my Galaxy 551 to Gingerbread 2.3.6. All went well. Unfortunately it seems to be a common side effect that the Z and Y keys (and some others) get swapped. The fix is apparently to modify the file /system/usr/keychars/sec_keypad.kcm.bin. The ideal thing is to put the old file from before the FW update back in, but of course I don't have that anymore! But the existing one can apparently be altered. If I can copy it to the SD card I can alter it in a hex editor and put it back.
So, I rooted my phone with that one click application, and that went OK too. I installed root explorer and found the file. There were also some others in the same folder I may be able to use. But, I cant make the folder R/W (pressing the button does nothing) so cant do anything with the file. I also tried Super Manager with no luck.
I am new to the phone fiddling stuff so noob level instructions would be appreciated!
Think I have it sorted. I installed superuser and then Root Explorer allowed me to select read/write. Now to try sort out this file!
OK, seems that you need to edit the file /system/usr/keylayout/sec_keypad.kl. Did that. DO'H now my keyboard doesn't work at all! Glad it saved a backup for me! Not sure what I did wrong, only edited two characters in a text file! Even the power button doesn't work. Got to pull that battery out LOL!
It seems when the file was saved it was saved with zero size. When I try to delete it to replace it with the backup it says cant delete, read only. So, not sure how I am meant to replace this and fix this problem.
Any ideas, remembering that I cant actually use any buttons on the phone!
Hi Everyone!
I'm posting this here since I don't have posting privileges in the development area.
I have converted my Korean Galaxy Tab 10.1 as explained in the development section in this thread:
http://forum.xda-developers.com/showthread.php?t=1360588&page=5
to a 7510.
Everything worked fine.
Just one tiny problem I am experiencing:
My Wifi reception has greatly decreased after the conversion.
I noticed this imediately after the conversion but hoped it would "go away" once I had rooted the Tab an installed a modded ROM.
Unfortunately this was not the case.
Does anyone of you other "converters" have any experience with this problem or am I the only one?
best regards an looking forward to your answers
Krügge
Happy new year to everyone!
Well, since noone seems to have my problem I looked into the files myself.
The wifi drivers and their configuration files are located in /etc/wifi of the system image.
I flashed the korean shw-m380w original version and did a backup using CWM. I then did the same with the original gt-p7510 version.
When I compared the filesizes I noticed differences and the content of the configuration files were different as well.
So I just replaced the contents of the european wifi folder with the contents of the korean one. I had to use a linux shell, since the file permissions need to be saved.
I copied the newly created system tar file into the CWM backup directory of the european version, adapted the the md5 hash in the same directory for the new system tar file and went into CWM and did a restore.
Worked like charm. I'm back to my old, much better, wifi reception performance.
I don't know if this is the fastest an easiest method but it worked....
best regards
kruegge99
kruegge99 said:
Happy new year to everyone!
Well, since noone seems to have my problem I looked into the files myself.
The wifi drivers and their configuration files are located in /etc/wifi of the system image.
I flashed the korean shw-m380w original version and did a backup using CWM. I then did the same with the original gt-p7510 version.
When I compared the filesizes I noticed differences and the content of the configuration files were different as well.
So I just replaced the contents of the european wifi folder with the contents of the korean one. I had to use a linux shell, since the file permissions need to be saved.
I copied the newly created system tar file into the CWM backup directory of the european version, adapted the the md5 hash in the same directory for the new system tar file and went into CWM and did a restore.
Worked like charm. I'm back to my old, much better, wifi reception performance.
I don't know if this is the fastest an easiest method but it worked....
best regards
kruegge99
Click to expand...
Click to collapse
i have same problem with you. can you please explain to me step by step how to fix the wifi like you did?
Hi Everyone!
I have done some more experimenting.
Since I wanted to install different Android Versions and different Kernels and the fact that the Kernel Drivers are always compiled to work with only one particualer Kernel, I needed to find a way to improve Wifi reception without having the korean drivers.
I acomplished this by just pasting the config file nvram_net.txt from the korean Android into the directory /system/etc/wifi.
I renamed the original file to nvram_net.txt.orig and pasted, Afterwards I adjusted the permissions to be the same as the ones of the original file and rebooted.
This has worked with every Android Version I installed so far.
I have attached a Screenshot of the directory and the nvram_net.txt file of the korean tab.
I hope I can help somone with this.
To me it seems that the korean tab has just a slightly different Wifi Hardware than the P7510.
best regards
Krügge
I've been running my xperia Z2 for a month or two now and one of the first things I did was disable the camera button, and attempt to rebind it to a different button in the .kl files within system/usr/keylayout. Initially, it worked great. I commented out the key 212 camera in a few files with a #, and added a new line.
It's been a month or so since then and I hadn't been using the camera button and all, and recently I've noticed that the kl file changed back in one of my restores to just being commented out, so the camera button is now non functional. I attempted to add a line of code to change the camera to media next like this: key 212 MEDIA_NEXT, but was getting no response after restarting my phone. I removed the line, deleted the comment on the previous line in every file that I had disabled it in, and restarted the phone. Camera is still non functional even after confirming it stayed unchecked.
After this, I attempted to copy all of the files to my SD card and mass edited every single camera key reference to media_next for the sake of testing, and the button was still disabled. I completely purged my .kl files, and uploaded notepad++ edited copies and restarted my phone. None of my buttons worked. I did a restore from my SD card backup, and nothing worked after restarting, still. I did a backup from a TWRP backup and everything is functional again... however, I'm left wondering why my .kl files might not be reading.
I apologize for the long post, but I'm trying to understand where I've went wrong. I'm on a stock bell rom(canadian) firmware 4.4.2 model D6503 build 17.1.A.2.55. I'm rooted, with only minimal modifications to the device(cydia substrate, xposed framework using rootcloak, youtube adaway, a radio modification to allow headphoneless scanning and xposed additions).
Does anyone know where I might've went wrong? My end goal is to rebind a controller's R2(simple button) controller to the R2 axis as well as button press, so if anyone has any information on rebinding a key to a maxed out axis I would appreciate information on that as well(Eg. R2 key 105 to RTrigger 1.0 + key 105).
Not sure
Perhaps copy a working existing file and try from there
I had trouble understanding your problem
Envious_Data said:
Not sure
Perhaps copy a working existing file and try from there
I had trouble understanding your problem
Click to expand...
Click to collapse
I've restored a CRM backup and the .kl files all work great, but when I attempt to modify the files they don't seem to update any system functions or buttons unless I'm just disabling the button. Even if I copy the file to another directory, break all the buttons then overwrite it with the copy and restart, the buttons stay disabled until I restore a CRM recovery.
I hope that's a little easier to read, the phone just doesn't seem to update its internal system with button definitions except to disable them, and I'm trying to figure out why.
Zarreck said:
I've restored a CRM backup and the .kl files all work great, but when I attempt to modify the files they don't seem to update any system functions or buttons unless I'm just disabling the button. Even if I copy the file to another directory, break all the buttons then overwrite it with the copy and restart, the buttons stay disabled until I restore a CRM recovery.
I hope that's a little easier to read, the phone just doesn't seem to update its internal system with button definitions except to disable them, and I'm trying to figure out why.
Click to expand...
Click to collapse
Just a thought, not pretty sure.
When you are copying files from sd-card, you should also check for correct permissions.
Your permissions must match with original files, otherwise it may create an issue.
mvv1277 said:
Just a thought, not pretty sure.
When you are copying files from sd-card, you should also check for correct permissions.
Your permissions must match with original files, otherwise it may create an issue.
Click to expand...
Click to collapse
I hadn't even thought of that, thank you, I'll try that out