Related
ok so to try and not sound redundant ( prob not gonna happen) i had the cm7 release running perfectly no issues ... then i decided to install faux's OC UV kernel which was great ... everything was speedy and working fine up until last night where my phone froze and i had to pull the battery ... after once booted up everytime id try and turn on wifi it wouldnt and i would just recieve a message that says error ... tried rebooting , wiping and reflashing .. tried flashing royals new GB rom exactly the way the instructions said too ... still nothing ... anybody know what might be causing this issue ... ive tried 3 diff roms with different kernels and still no wifi ... could this be hardware ????
bump.
Ive tried wiping everything including /system and davlik and still cant get the wifi to work ... i was told that i might have a bad module so i pushed on from the kernel i was currently using and still nothing ... anybody have any type of advice ?
bump .... im willing to donate !
try this:
extract the bcm4329.ko from the kernel zip file (module and kernel version MUST MATCH) and somehow copy it to /system/lib/modules (via adb/root explorer, etc etc)
then use terminal emulator and type the following code exactly as shown:
Code:
su
cd /system/lib/modules
chmod 644 *
chown 0.0 *
reboot... and see if it works...
faux123 said:
try this:
extract the bcm4329.ko from the kernel zip file (module and kernel version MUST MATCH) and somehow copy it to /system/lib/modules (via adb/root explorer, etc etc)
then use terminal emulator and type the following code exactly as shown:
Code:
su
cd /system/lib/modules
chmod 644 *
chown 0.0 *
reboot... and see if it works...
Click to expand...
Click to collapse
Faux my name is neidlinger and I get assfucked by you and other homos.
faux123 said:
try this:
extract the bcm4329.ko from the kernel zip file (module and kernel version MUST MATCH) and somehow copy it to /system/lib/modules (via adb/root explorer, etc etc)
then use terminal emulator and type the following code exactly as shown:
Code:
su
cd /system/lib/modules
chmod 644 *
chown 0.0 *
reboot... and see if it works...
Click to expand...
Click to collapse
Nice to get help from the master himself
Sent from my HTC Glaciee using XDA Premium App
Double post by mistake. my bad
faux123 said:
try this:
extract the bcm4329.ko from the kernel zip file (module and kernel version MUST MATCH) and somehow copy it to /system/lib/modules (via adb/root explorer, etc etc)
then use terminal emulator and type the following code exactly as shown:
Code:
su
cd /system/lib/modules
chmod 644 *
chown 0.0 *
reboot... and see if it works...
Click to expand...
Click to collapse
Sigh ... no luck. I used your GB kernel with the Royal Ginger 1.6 rom ... rafyvitto thinks it might be my hardware so i was prob gonna have somebody take a look at it sometime this week .. what a bad one !
For what ever reason if i am at home, i have to use static ip address to get on my router, no other devices on the network have this issue, including my old phone. its probably not related to your problem but worth trying.
[via XDA premium]
I'm pleased to tell everyone Bluetooth finally works!!! I can't take any credit other than putting together the instructions to get it working and digging all over the interwebs so have a look below!!!!!!!:
Also note, this may work on other Linux setups using the Transformer and possibly other devices using similar instructions and files.
OP for Tubutnu by x3maniac
1. Go to this site and download the gz file. This contains a few missing files we need and it's compile for ARMHF. http://forum.xda-developers.com/showthread.php?t=1476835
2. Extract the contents of the gz to /usr/sbin
3. Go to this site. Copy the code in the box and make a new file called bsp-tf101. Save the file to /etc/init.d. http://forum.xda-developers.com/showpost.php?p=21388706&postcount=1456
4. In Android (or mount the Android file system if it isn't already) copy the file /data/misc/bluetooth/bcm4329.hcd to /lib/firmware. If the file with CAPITAL letters exists like this already in /lib/firmware: BCM4329.hcd you are to delete it or CUT it from that directory (many XDA posts say to get rid of that file. We want to use the lower case file.
5. In Android (or mount the Android file system if it isn't already) copy the file /data/misc/bluetooth/mac.txt to /lib/firmware/brcm.
6. Now, edit /etc/init.d/bsp-tf101. Go to the line that starts with /usr/sbin/brcm_patchram_plus and REMOVE --bd_addr and whatever MAC address is in the file. We are doing this because when you run the service, the MAC will be read from /lib/firmware/brcm/mac.txt.
7. In terminal type "service bsp-tf101 start" NO QUOTES.
8. After the terminal says Done Setting Line Discipline, open your Bluetooth Manager application from Preferences in Lubuntu.
9. Happy scanning and pairing! I successfully connected my GS3 and saw other devices nearby.
Addendum for Bluetooth in Raring
1. Create a file called "tfbatch" or whatever name you want, it does not matter. Save it in your home directory for the moment. Edit your file with nano /home/username/tfbatch with the following lines in it below.
#! /bin/shrfkill unblock 0/usr/sbin/brcm_patchram_plus --enable_hci --baudrate 3000000 --patchram /lib/firmware/bcm4329.hcd /dev/ttyHS2chmod /dev/nv* /dev/tegra_*exit
2. Now copy "tfbatch" or whatever you named it to /usr/bin. You can do (without quotes) "cp /home/username/tfbatch /usr/bin"
3. sudo nano /etc/rc.local
4. Type tfbatch in this file before the line that says exit 0. I'm not sure if you need a space in between tfbatch and exit 0 but put one there just in case.
5. If you haven't done so already, from terminal do the following for these files:
sudo chmod 777 /usr/bin/tfbatchsudo chmod 777 /lib/firmware/bcm4329.hcdsudo chmod 777 /usr/sbin/brcm_patchram_plussudo chmod 777 /usr/sbin/brcm_patchram_plus.c
6. Please note, I understand the security risks of 777 for these files but if you are worried then you must choose something different. Maybe 644 but I don't know for sure. We are doing 777 for some files becacuse of permission denied errors. If you find a better method I'll update my post.
7. Reboot and Profit. (I was perfectly able to use PAN for Bluetooth tethering without installing anything extra using Raring and GNOME-CORE. However, I did not get Bluetooth headsets to work yet so if someone else wants to help out then that's great too.
Hi!
First of all thank you, that worked perfectly for me.
I just had to chmod bcm4329.hcd and brcm_patchram_plus's files.
For those who have the same "problem" just type this once you placed all the files in good folders.
Code:
sudo chmod 777 /lib/firmware/bcm4329.hcd
Code:
sudo chmod 777 /etc/init.d/bsp-tf101
And do the same for all files you extracted from brcm.tar.gz
Not sure if chmod all of these files is useful but that's what I've done and it worked.
Hope it'll help.
147keul said:
Hi!
First of all thank you, that worked perfectly for me.
I just had to chmod bcm4329.hcd and brcm_patchram_plus's files.
For those who have the same "problem" just type this once you placed all the files in good folders.
Code:
sudo chmod 777 /lib/firmware/bcm4329.hcd
Code:
sudo chmod 777 /etc/init.d/bsp-tf101
And do the same for all files you extracted from brcm.tar.gz
Not sure if chmod all of these files is useful but that's what I've done and it worked.
Hope it'll help.
Click to expand...
Click to collapse
I have been problems getting this to work on Raring 13.04 build from X3. Are you using Raring by chance or one of the other versions by X3?
I've not been using yet Raring method, I used the one click method with 2.6.36 kernel.
Gonna take a look in a few with raring, I'll tell you if I manage to make it work.
147keul said:
I've not been using yet Raring method, I used the one click method with 2.6.36 kernel.
Gonna take a look in a few with raring, I'll tell you if I manage to make it work.
Click to expand...
Click to collapse
I got it to work a little bit ago and tethering for Bluetooth internet. Good call with chmod it worked like a champ. Thanks!
When using your Bluetooth tethering, you can also use Conky to display the IP address. You can edit the file by sudo nano /etc/conky/conky.conf. Go to the line that is displaying ${addr wlan0}. Copy that whole line below and replace wlan0 with bnep0. Bnep0 is the adapter interface that has the BT tether IP address.
Has anyone seen this? Ubuntu Developer Preview for Galaxy Nexus, Nexus 4 Arrives Feb. 21
"Our platform supports a wide range of screen sizes and resolutions. Developers who have experience bringing up phone environments will find it relatively easy to port Ubuntu to current handsets"
"For developers, contributors and partners, there is now a coherent experience that warrants attention. The cleanest, most stylish mobile interface around."
Click to expand...
Click to collapse
I don't have the files starting from step 4 (folder is empty). I'm guessing it's because I installed another ROM (EOS JB MR1 4.2 from http://forum.xda-developers.com/showthread.php?t=2063406). Would anyone happen to know where else I can obtain the files needed starting from step 4? Thanks!
Treizy said:
I don't have the files starting from step 4 (folder is empty). I'm guessing it's because I installed another ROM (EOS JB MR1 4.2 from http://forum.xda-developers.com/showthread.php?t=2063406). Would anyone happen to know where else I can obtain the files needed starting from step 4? Thanks!
Click to expand...
Click to collapse
Search android from terminal:
Find / | grep bcm4329.hcd
If you get nothing I'll try to upload later.
TomTcom said:
Search android from terminal:
Find / | grep bcm4329.hcd
If you get nothing I'll try to upload later.
Click to expand...
Click to collapse
Thanks! Found that file in /system/etc/firmware.
I wasn't able to find the mac.txt file but I know my bluetooth mac address. Is that the only thing that I need to include in that file?
Treizy said:
Thanks! Found that file in /system/etc/firmware.
I wasn't able to find the mac.txt file but I know my bluetooth mac address. Is that the only thing that I need to include in that file?
Click to expand...
Click to collapse
Yes, that's the only thing you need to put in. Strange you can't find needed files in right places, have you tried with a "root explorer"? Try to download it, and normally you should find mac.txt.
Trying this again with the raring build and still running into problems.
When I try to start the service, i get the following error:
Code:
$ sudo service bsp-tf101 start
* Starting Bluetooth Support Deamon...
* Setting correct permissions on nvtegra device nodes...
/etc/init.d/bsp-tf101: 23: /etc/init.d/bsp-tf101: /usr/sbin/brcm_patchram_plus: Permission denied
I did run the following commands before hand:
sudo apt-get install rfkill (I didn't have this installed before and it was giving an error)
sudo chmod 777 /lib/firmware/bcm4329.hcd
sudo chmod 777 /etc/init.d/bsp-tf101
sudo chmod -R 777 /usr/sbin/brcm_patchram_plus
Any idea why it still says permission denied?
Thanks!
Treizy said:
Trying this again with the raring build and still running into problems.
When I try to start the service, i get the following error:
Code:
$ sudo service bsp-tf101 start
* Starting Bluetooth Support Deamon...
* Setting correct permissions on nvtegra device nodes...
/etc/init.d/bsp-tf101: 23: /etc/init.d/bsp-tf101: /usr/sbin/brcm_patchram_plus: Permission denied
I did run the following commands before hand:
sudo apt-get install rfkill (I didn't have this installed before and it was giving an error)
sudo chmod 777 /lib/firmware/bcm4329.hcd
sudo chmod 777 /etc/init.d/bsp-tf101
sudo chmod -R 777 /usr/sbin/brcm_patchram_plus
Any idea why it still says permission denied?
Thanks!
Click to expand...
Click to collapse
Try also chmod 777 the brcm_patchram_plus.c file as well.
Also, I need to update my guide. I don't run it as a service but rather a batch file launched from rc.local so everything is executed as root. I'll have to update the guide to include Raring. So that could be part of the problem as well.
TomTcom said:
Try also chmod 777 the brcm_patchram_plus.c file as well.
Also, I need to update my guide. I don't run it as a service but rather a batch file launched from rc.local so everything is executed as root. I'll have to update the guide to include Raring. So that could be part of the problem as well.
Click to expand...
Click to collapse
So if I add these commands to the rc.local file in /etc it should work?
Code:
sudo chmod 777 /lib/firmware/bcm4329.hcd
sudo chmod 777 /etc/init.d/bsp-tf101
sudo chmod -R 777 /usr/sbin/brcm_patchram_plus
sudo service bsp-tf101 start
Or do I need to do something else?
Treizy said:
So if I add these commands to the rc.local file in /etc it should work?
Code:
sudo chmod 777 /lib/firmware/bcm4329.hcd
sudo chmod 777 /etc/init.d/bsp-tf101
sudo chmod -R 777 /usr/sbin/brcm_patchram_plus
sudo service bsp-tf101 start
Or do I need to do something else?
Click to expand...
Click to collapse
No don't do that. I'll try and post what you need to do later tonight.
Treizy said:
So if I add these commands to the rc.local file in /etc it should work?
Code:
sudo chmod 777 /lib/firmware/bcm4329.hcd
sudo chmod 777 /etc/init.d/bsp-tf101
sudo chmod -R 777 /usr/sbin/brcm_patchram_plus
sudo service bsp-tf101 start
Or do I need to do something else?
Click to expand...
Click to collapse
I have updated my guide. See the OP for the Addendum for Raring installation. The file you create will be ran before the GUI loads with root permissions from rc.local.
Let me know if this worked.
TomTcom said:
I have updated my guide. See the OP for the Addendum for Raring installation. The file you create will be ran before the GUI loads with root permissions from rc.local.
Let me know if this worked.
Click to expand...
Click to collapse
Nope
When I try to turn bluetooth on, nothing happens. It will switch back to off when i close the settings popup.
Treizy said:
Nope
When I try to turn bluetooth on, nothing happens. It will switch back to off when i close the settings popup.
Click to expand...
Click to collapse
Hmmm...if you followed the guide you shouldn't have to turn it on. The batch is executed on boot from RC.local. Try and give me some more details.
TomTcom said:
Hmmm...if you followed the guide you shouldn't have to turn it on. The batch is executed on boot from RC.local. Try and give me some more details.
Click to expand...
Click to collapse
Maybe I messed up. For step 1, the files you are asking us to download are the ones in post #10 correct (brcm.tar.gz)? Also, I don't have this mac.txt file anywhere so I created my own and just put my mac address in it (hopefully the correct one). Lastly, i dont have this file for this step:
sudo chmod 777 /usr/sbin/brcm_patchram_plus.c
but instead i have it in this location:
/usr/sbin/brcm_patchram_plus/brcm_patchram_plus.c
Treizy said:
Maybe I messed up. For step 1, the files you are asking us to download are the ones in post #10 correct (brcm.tar.gz)? Also, I don't have this mac.txt file anywhere so I created my own and just put my mac address in it (hopefully the correct one). Lastly, i dont have this file for this step:
sudo chmod 777 /usr/sbin/brcm_patchram_plus.c
but instead i have it in this location:
/usr/sbin/brcm_patchram_plus/brcm_patchram_plus.c
Click to expand...
Click to collapse
I think you might have files in the wrong location, there should be no brcm_patchram_plus directory. Try to extract the zip again and make sure they are all in /usr/sbin only.
If you didn't have mac.txt from Android, you can just make it like you did and make sure it is in /lib/firmware/brcm.
Everything was good until I started messing with the 4.4 roms. Now no matter what I do. Full Wipe, Factory Image restore, try different Roms/Kernels, etc, my MAC Address will reset after every reboot. This is an issues as I use Mac Filtering on my router. Any Ideas?
The same is happening to me and I can't find a way to fix it!
It sucks because my main connection (my University wifi) doesn't let me connect if I have a different MAC Address.
I'm using this app to change my MAC (temporarily) https://play.google.com/store/apps/details?id=com.jworksbr.macspoofer
You need root to make it works.
Anyway, I'm still trying to find a way to get my original MAC address back.
joaocadide said:
The same is happening to me and I can't find a way to fix it!
It sucks because my main connection (my University wifi) doesn't let me connect if I have a different MAC Address.
I'm using this app to change my MAC (temporarily) https://play.google.com/store/apps/details?id=com.jworksbr.macspoofer
You need root to make it works.
Anyway, I'm still trying to find a way to get my original MAC address back.
Click to expand...
Click to collapse
I ended up using http://forum.xda-developers.com/showthread.php?t=2347060
For mac address:
- In /persist directory create wifi directory. In the new directory create a file named .macaddr (don't miss the dot!)
Edit the file and put 12 random hex numbers in it (0-9, A-F), save.
- Set execute and read permissions for everybody on /persist/wifi directory and change owner of .macaddr to wifi:wifi and permission to 660 (read/write for owner and group and nothing else).
In command line:
Code:
chown root:root /persist/wifi
chmod 755 /persist/wifi
chown wifi:wifi /persist/wifi/.macaddr
chmod 660 /persist/wifi/.macaddr
- run /system/bin/conn_init program. Can be run in root explorer(choose Linux Script Handler when you open it), or in adb shell:
Code:
su
/system/bin/conn_init
Then reboot and check if the changes got applied in settings
I cant get my original one back but at least I have a static MAC.
..
chainup said:
For me it's only the last 6 numbers/letters that keep changing on reboot. For both Wifi and Bluetooth. Is it the same for you guys?
Click to expand...
Click to collapse
Yeah first are always 11:22:33
Thank you, bandit97!
It's working fine now! =D
bandit97 said:
I ended up using http://forum.xda-developers.com/showthread.php?t=2347060
For mac address:
- In /persist directory create wifi directory. In the new directory create a file named .macaddr (don't miss the dot!)
Edit the file and put 12 random hex numbers in it (0-9, A-F), save.
- Set execute and read permissions for everybody on /persist/wifi directory and change owner of .macaddr to wifi:wifi and permission to 660 (read/write for owner and group and nothing else).
In command line:
Code:
chown root:root /persist/wifi
chmod 755 /persist/wifi
chown wifi:wifi /persist/wifi/.macaddr
chmod 660 /persist/wifi/.macaddr
- run /system/bin/conn_init program. Can be run in root explorer(choose Linux Script Handler when you open it), or in adb shell:
Code:
su
/system/bin/conn_init
Then reboot and check if the changes got applied in settings
I cant get my original one back but at least I have a static MAC.
Click to expand...
Click to collapse
i came from your link too but this didn't work for me
anyone know why?
Hi. This has been driving me crazy! My Nexus 4 also gets a new Mac address on each reboot. My local WiFi hotspot thinks i am a new customer every time I visit (as it uses Mac address filtering) which is frustrating. I got onto Google about it but they said i should return the phone to the retailer (didn't get it on the Play store). I tried reverting the phone to Android 4.3, resetting etc but nothing works. I the phone was fine at first so I can only assume it is a hardware fault. Does anyone have any more incite into this or a solution?
Could someone explain how I run the commands in an adb shell? I'm familiar with adb and android toolkit etc. Many thanks! PS. I tried it using root explorer and it did not work
Sent from my Nexus 4 using xda app-developers app
Where is /persist directory?
bandit97 said:
I ended up using http://forum.xda-developers.com/showthread.php?t=2347060
For mac address:
- In /persist directory create wifi directory. In the new directory create a file named .macaddr (don't miss the dot!)
Edit the file and put 12 random hex numbers in it (0-9, A-F), save.
- Set execute and read permissions for everybody on /persist/wifi directory and change owner of .macaddr to wifi:wifi and permission to 660 (read/write for owner and group and nothing else).
In command line:
Code:
chown root:root /persist/wifi
chmod 755 /persist/wifi
chown wifi:wifi /persist/wifi/.macaddr
chmod 660 /persist/wifi/.macaddr
- run /system/bin/conn_init program. Can be run in root explorer(choose Linux Script Handler when you open it), or in adb shell:
Code:
su
/system/bin/conn_init
Then reboot and check if the changes got applied in settings
I cant get my original one back but at least I have a static MAC.
Click to expand...
Click to collapse
Where is the /persist directory found? Does this work on unrooted phones? I have the Chinese S5 phone which changed Mac address every time I reboot or turn off and on the wifi. This has me logging in to my router to add a new mac every time.
You DO need to be rooted
ayonbaxter said:
Where is the /persist directory found? Does this work on unrooted phones? I have the Chinese S5 phone which changed Mac address every time I reboot or turn off and on the wifi. This has me logging in to my router to add a new mac every time.
Click to expand...
Click to collapse
Hello, you need not only root access, but a file manager capable of mounting read-write permissions, like ES File Explorer (free on Google Play).
If you have a Terminal Emulator, this will help. If not, find one on the Play Store. My favorite is from developer Jack Palevich, found here.
Otherwise, you won't see the directory on a stock file manager, especially if you're NOT rooted. Although I am on CM 10.2, this has plagued me as well when I was running CM11.
Good luck!
furboom1240 said:
Hello, you need not only root access, but a file manager capable of mounting read-write permissions, like ES File Explorer (free on ).
If you have a Terminal Emulator, this will help. If not, find one on the Play Store. My favorite is from developer Jack Palevich, found .
Otherwise, you won't see the directory on a stock file manager, especially if you're NOT rooted. Although I am on CM 10.2, this has plagued me as well when I was running CM11.
Good luck!
Click to expand...
Click to collapse
i have the same problem, i cant find the /persist directory. i installed ES file exloprer but on / there is no /persist folder only these folders:
acct, cache, config, custom, d, data , dev, etc, mnt, proc ,protect_f,protect_s, root, sbchk, sbin, sdcard, sys,system, vendor
can i create a persist folder or do i have a bigger problem with my system?
Lack of Details
tommy0014 said:
i have the same problem, i cant find the /persist directory. i installed ES file exloprer but on / there is no /persist folder only these folders:
acct, cache, config, custom, d, data , dev, etc, mnt, proc ,protect_f,protect_s, root, sbchk, sbin, sdcard, sys,system, vendor
can i create a persist folder or do i have a bigger problem with my system?
Click to expand...
Click to collapse
First of all, do you have Superuser-managed root access? In order for me to assist, you need to answer that. The /persist directory should certainly exist, as it was so on all devices I own, rooted or not. When browsing the filesystem, please be careful what you mess with. Even with root access, you must exercise judgment in what you modify.
As always, Root Responsibly.
Stay custom, my friends...
Hello,
I have SM-N9005 variant and recently I updated to the latest android 4.4.2 leaked version with Odin, and then rooted with CF-Auto-Root.
After that, I lost the permission to write to external sdcard.
I searched and found this: http://forum.xda-developers.com/showthread.php?p=49603814
I backed up /system/etc/permissions/platform.xml and then I followed the instructions there.
After restart, a lot of app stopping messages showed and I had no access to file system or network anymore.
I used adb shell to restore the original platform.xml but it didn't helped in any way.
It seems that all mounts and networks are working, but none of the applications has permission to use any of them.
How do I resolve this, without wiping all my data?
Thank you!
You need to set the correct permissions on the .xml after you overwrite it back into the /system Off the top of my head I can't think what they are (just out of bed and got to work so still sleepy!)
radicalisto said:
You need to set the correct permissions on the .xml after you overwrite it back into the /system Off the top of my head I can't think what they are (just out of bed and got to work so still sleepy!)
Click to expand...
Click to collapse
I tried 644 and 777 but the problem persists.
rw-r-r which is 644 - read wrong
or chmod 666 -- forgive my lack of memory, it has been a long time since I have used chmod commands, few years since my glFTPD / site modding days.
radicalisto said:
rw-r-r which is 644 - read wrong
or chmod 666 -- forgive my lack of memory, it has been a long time since I have used chmod commands, few years since my glFTPD / site modding days.
Click to expand...
Click to collapse
The problem still persist
DxCK said:
The problem still persist
Click to expand...
Click to collapse
i dont know if it helps in your situation but did you try the "fix permissions" from a custom recovery like twrp?
there are also scripts you can execute in a terminal, the knoxout script linked in my sig for example has a permission fixer included.
A.N.Droid said:
i dont know if it helps in your situation but did you try the "fix permissions" from a custom recovery like twrp?
there are also scripts you can execute in a terminal, the knoxout script linked in my sig for example has a permission fixer included.
Click to expand...
Click to collapse
Thank you.
When i run this, no matter what are the parameters, for example: sh kn0x0ut.sh kn0x0ut
it says:
ERROR: Unknown parameter ""
Removing all temp folder /data/media/kn0x0ut_temp...
DxCK said:
Thank you.
When i run this, no matter what are the parameters, for example: sh kn0x0ut.sh kn0x0ut
it says:
ERROR: Unknown parameter ""
Removing all temp folder /data/media/kn0x0ut_temp...
Click to expand...
Click to collapse
just type sh kn0x0ut.sh to get all commands.
if you dont get this working, you can do it from twrp (i think cwm too)if you have it.
tap on "advanced" and then on "fix permissions".
Hi Folks!
I created a QWERTZ keylayout for the Logitech K830.
This works on every FireTV, every firmware and every android device IF YOU HAVE ROOT
DOWNLOAD
See Attachments
INSTALL
1. mount system Read-Write
2. copy Vendor_046d_Product_c52b.kl to /system/usr/keylayout
3. chmod 644 /system/usr/keylayout/Vendor_046d_Product_c52b.kl
4. if needed chown 0:0 /system/usr/keylayout/Vendor_046d_Product_c52b.kl
4. copy Vendor_046d_Product_c52b.kcm to /system/usr/keychars
5. chmod 644 /system/usr/keychars/Vendor_046d_Product_c52b.kcm
5. if needed chown 0:0 /system/usr/keychars/Vendor_046d_Product_c52b.kcm
6. reboot
NOTE
This Layout basically applies for the Logitech Unified Receiver so this keylayout will work for every keyboard using the Unified Receiver as for example the K400 from Logitech .
All the magic happens in the key character map and the layout file is just a cleaned generic one with two tweaked buttons. And because i use a cleaned keylayout file some buttons on other keyboards might be wrong or even missing.
If this is the case delete the layout file (Vendor_046d_Product_c52b.kl), reboot and try again. Most things should work now.
You can also use the tool "evtest" to debug the layout file if you wish to.
HINT
If you have a other keyboard and know the Vendor and Product ID you can rename the key character map / keylayout accordingly to get QWERTZ layout.
You could even use the kcm file as Generic.kcm and so on. I haven't done it this way because i just didn't want to.
Works great with my K400.
Thanks for the info.
Hi and thank you very much! The attached files seem to be missing, can somebody please reupload them?
Thanks,
Nico
@niggonet Reuploaded attachement in first post
WheelchairArtist said:
@niggonet Reuploaded attachement in first post
Click to expand...
Click to collapse
You are the man! My hero!
Been looking for this option since months!
Here are some 'ready to copy and paste' instructions (just replace the PATH_TO_FILE):
Bash:
adb push "C:\[PATH_TO_FILE]\Vendor_046d_Product_c52b.kcm" /sdcard/Vendor_046d_Product_c52b.kcm
adb push "C:\[PATH_TO_FILE]\Vendor_046d_Product_c52b.kl" /sdcard/Vendor_046d_Product_c52b.kl
adb shell
su
mount -o rw,remount /system
mv /sdcard/Vendor_046d_Product_c52b.kcm /system/usr/keychars/Vendor_046d_Product_c52b.kcm
mv /sdcard/Vendor_046d_Product_c52b.kl /system/usr/keylayout/Vendor_046d_Product_c52b.kl
chmod 644 /system/usr/keychars/Vendor_046d_Product_c52b.kcm
chown 0:0 /system/usr/keychars/Vendor_046d_Product_c52b.kcm
chmod 644 /system/usr/keylayout/Vendor_046d_Product_c52b.kl
chown 0:0 /system/usr/keylayout/Vendor_046d_Product_c52b.kl
reboot
Second block is not neccessary when using ADB over TWRP.
Thank you - much appreciated,
Nico