Develop Bugs

any font's for the arc?

I wanna change the font on the arc, is there any, please provide pics.

got many available here
i personally used zegoe and sometimes ubuntu
use "font changer" app to switch to your desired font

Rycon33 said:
got many available here
i personally used zegoe and sometimes ubuntu
use "font changer" app to switch to your desired font
Click to expand...
Click to collapse
thank you, I downloaded it, too many files along with ttf file, what to do?

if you use the "font changer" app, there will be a folder in your sdcard named ".fontchanger", you just put the 2 files there(e.g. Zegoe.ttf and Zegoe-Bold.ttf), then once you open the actual fontchanger app it will be there as one of the choices, just click it then apply and reboot
alternatively, you can just use root explorer to overwrite the 2 files in /system/fonts:
- first, rename your desired font to DroidSans.ttf(for regular) and DroidSans-Bold.ttf(for the bold)
- put the 2 files in system/fonts overwriting the original files then set permissions to rw-r-r then reboot
*those two files are all you need, the normal and the bold .ttf

Rycon33 said:
if you use the "font changer" app, there will be a folder in your sdcard named ".fontchanger", you just put the 2 files there(e.g. Zegoe.ttf and Zegoe-Bold.ttf), then once you open the actual fontchanger app it will be there as one of the choices, just click it then apply and reboot
alternatively, you can just use root explorer to overwrite the 2 files in /system/fonts:
- first, rename your desired font to DroidSans.ttf(for regular) and DroidSans-Bold.ttf(for the bold)
- put the 2 files in system/fonts overwriting the original files then set permissions to rw-r-r then reboot
*those two files are all you need, the normal and the bold .ttf
Click to expand...
Click to collapse
thank you
I couldn't find the fonts you have, Zegoe & Ubunto.

see attached file which is originally from that thread also

[Q] DoCoMo Status Bar v4 & Task Switcher/Does this work on ZL?

Has someone already tested this Mod on the Xperia ZL?
http://forum.xda-developers.com/showthread.php?t=2202383

Yes it works !!!!!
Yes I installed it, tested it and can confirm it works on the Sony Xperia ZL.
First I rooted the phone using this method:
http://forum.xda-developers.com/showthread.php?t=2186368
Then I download the files to computer then to my SD Card/external storage on smartphone.
Back up all necessary file from system/app such systemui.apk, systemui.odex, taskswitcher.apk, settings.apk and settings.odex files to my sd card/external storage in case it went wrong.
Deleted the systemui.odex and settings.odex files.
Copy on files at a time for example the systemui.apk file to the system folder then changed the permission to rw-r--r-- then delete and move the the systemui.apk file to the system/app folder. I did the same for teh other files as well.
Finally reboot the smartphone and voila it should work.

Darkfunnyguy said:
Yes I installed it, tested it and can confirm it works on the Sony Xperia ZL.
First I rooted the phone using this method:
http://forum.xda-developers.com/showthread.php?t=2186368
Then I download the files to computer then to my SD Card/external storage on smartphone.
Back up all necessary file from system/app such systemui.apk, systemui.odex, taskswitcher.apk, settings.apk and settings.odex files to my sd card/external storage in case it went wrong.
Deleted the systemui.odex and settings.odex files.
Copy on files at a time for example the systemui.apk file to the system folder then changed the permission to rw-r--r-- then delete and move the the systemui.apk file to the system/app folder. I did the same for teh other files as well.
Finally reboot the smartphone and voila it should work.
Click to expand...
Click to collapse
Thank you for your explanations, because I also have the problem.
I have some questions:
1. I did not use this method to root, which for me is more complicated. Is that my problem may be here?
2. What recovery are you using?
3. can you detail me this because I do not understand:
"Copy on files at a time for example the systemui.apk file to the system folder then changed the permission to rw-r--r-- then delete and move the the systemui.apk file to the system/app folder. I did the same for teh other files as well.
In the topic, asked to remove only two files."
Thank you to you for your help

Compare to other method to rooting I looked this is by far the easiest to root without unlocking the bootloader as well. It only takes a minutes or two.
Sorry I have not used any recovery as of yet apart from android software such as backup pro or backup and restore.
When you downloaded the files from here in Zip or WinRAR format I used I extract the three files systemui.apk, taskswitcher.apk and settings.apk to your computer/laptop then connect up your Xperia ZL to the computer/laptop then copy or move these files to your Xperia ZL on your sd card.
You need to download something like android app like file manager and make sure the settings on file manager is set to root.
Now I used the file manager copy the systemui.apk to the system folder then I press on systemui.apk to press option for permission to change the permission with the with the first column all boxes ticked for read and second column only the top for owner is ticked for write, all other boxes including the third column for execute is left unticked.
Now I move the systemui.apk file to the system/app folder replacing the current systemui.apk. I used the same method for settings.apk and taskswitcher.apk files. Once you done that reboot your smartphone.

Darkfunnyguy said:
Compare to other method to rooting I looked this is by far the easiest to root without unlocking the bootloader as well. It only takes a minutes or two.
Sorry I have not used any recovery as of yet apart from android software such as backup pro or backup and restore.
When you downloaded the files from here in Zip or WinRAR format I used I extract the three files systemui.apk, taskswitcher.apk and settings.apk to your computer/laptop then connect up your Xperia ZL to the computer/laptop then copy or move these files to your Xperia ZL on your sd card.
You need to download something like android app like file manager and make sure the settings on file manager is set to root.
Now I used the file manager copy the systemui.apk to the system folder then I press on systemui.apk to press option for permission to change the permission with the with the first column all boxes ticked for read and second column only the top for owner is ticked for write, all other boxes including the third column for execute is left unticked.
Now I move the systemui.apk file to the system/app folder replacing the current systemui.apk. I used the same method for settings.apk and taskswitcher.apk files. Once you done that reboot your smartphone.
Click to expand...
Click to collapse
Thanks.
Yes, I do that and it's ok.
Look at : http://forum.xda-developers.com/showpost.php?p=40569989&postcount=443

[Guide]How to add custom language in localized device

Hello.
In this tutorial, I will try to explain how to add some language(s) in your phone when it's not implemented by the vendor (localized ROM).
I will not cover how to change the keyboard language (or layout) as there are a lot of free keyboards in the market with a lot of localizations. (In my case I need azerty French keyboard that is not implemented in my ROM).
I did it with KitKat (4.4.2) but should be ok with almost any version.
It's for Samsung devices, I really don't know if it's work with others brands try it !
I'm pretty sure that only the 1st phase should maybe not work in other brands, The last 3 phases should be OK with any brand.
I'm French and living in Japan, I recently bought a Samsung Galaxy S4 who is restricted by Japanese vendor (DOCOMO) to only English, Japanese & Korean languages.
I've read a lot of things before I could translate the OS (French in my case) , and I could'nt find any good tutorial. Some people say you can't, some say you have to recompile your ROM , etc...
First, you could install something like "applocal2" for add your language in already translated apps, but of course, it will not work for the non-already translated apps (usually system apps).
As I'm new here (look at my join date ), I coudn't post link, so google for them !
What you need :
In your device :
Your device must be rooted.
Root Browser or equivalent.
USB debugging turned on.
In your PC :
A Rom for your device with the language you want inside in the same version of Android. (Find it in sammobile.com site for Samsung devices).
sgs2toext4.jar. (Transform the system.img.ext4 from the extracted ROM to a readable format for the next tool)
ext2explorer. (Extract the files from the system.img.ext4)
Virtuous Ten Studio. (Don't have to present it !! The must have tool !!)
7zip or equivalent.
What you have to know :
This is always dangerous to play with system files ! I'm not responsible if you broke your device !!
Always do a backup of the file you will modify ! I suggest you copy them on your PC and you keep them in the original folder with a modified name, as this you could maybe try to restore them via ADB if something is wrong.
You don't have to bother with the signature mode when recompiling system (only) apk (any of them are ok). But you should copy the "META-INF" folder & "AndroidManifest.xml" file from the original apk to the newly repacked apk. (First erase them from the newly created apk inside 7zip, then open the original apk with 7zip and copy and paste to the new apk).
When copying new apk from PC to device, first copy them in the /system/ folder, then change permission to 644 (rw-r--r--) before finally moving them to the original folder.
How it's work :
The principe, as you should understand, is to extract both your apks and the apks from the dowloaded ROM, copy the ressources in your language from it to your apks and then rebuild them.
In our case (at least mine ) these apks are in the folders :
/system/app/
/system/framework/
/system/priv-app/
Ok, here we GO !
1st phase : extract the files from the downloaded ROM with the language you want.
Extract the ROM (.zip) with 7zip, and then extract again the resulting file (.tar.md5) with 7zip (you should have an error : don't care of it).
Open sgs2toext4.jar and past in it the file system.img.ext4. Wait it take time. It will produce a new file named : system.img.ext4.img
Open ext2explorer and choose open the previously created file. Then right click on it and save. Create a new folder (I named it sys), and press ok. Wait it take time.
You now should have the /system/ directory extracted inside the sys directory with the apks who have your language in them.
2nd phase : Find the apks you need to modify. This is actually the most harder part !
There are a lot of apks in the 3 directories I say earlier. You don't have to translate all of them.
The 1st one you should change is /system/framework/framework-res.apk or /system/priv-app/SystemUI.apk. One of them (don't remember wich one ) give you the option of your language in the settings.
Launch VTS (Virtual Ten Studio) and click New Solution
Choose the file you want to open, then Import.
Project-Type must be Apk-Project.
Choose a Solution Name (for example Original_name_of_apk or Translated_name_of_apk), then Click Next.
Should be Basic Theming. Click Next.
Click Next.
What I did is to open some of them one by one to see if there are localized languages in it.
Here a non-exhaustive list of what I found :
Some of them are the overlay by Samsung (TouchWizz), and some of them are Japanese version of app.
Try to find yours (for example JContacts.apk could be SecContacts_OSup.apk in the downloaded ROM) by opening both versions and comparing the file /res/values/strings.xml.
/system/framework/twframework-res.apk
/system/framework/framework-res.apk
/system/priv-app/SystemUI.apk
/system/priv-app/Keyguard.apk
/system/priv-app/Jcontacts.apk
/system/priv-app/SecLauncher3.apk
/system/priv-app/SecPhone_JPN.apk
/system/priv-app/SecSafetyAssurance.apk
/system/priv-app/SecSettings.apk
/system/app/AccessControl.apk
/system/app/AssistantMenu.apk
/system/app/EasySettings.apk
/system/app/MultiWindowTrayService.apk
/system/app/SViewCoverService.apk
3rd phase : Copy the language from one apk to another.
Now you have found some apk to "translate", we must copy the /res/ folders we want from the decompiled apk of the ROM who contain your language to your original apk.
Look in the /res/ folder in VTS and find the differents languages : they are /res/value-xx/ but you could have in some case /res/raw-xx & /res/xml-xx.
Anyway,
Copy from the folder created by VTS all the directories who have the language you want (in Windows Seven it's : \Documents\Virtuous Ten Studio\Projects\Translated_name_of_apk\name_of_apk\Data\res) and copy them to the VTS directory of your original apk ( \Documents\Virtuous Ten Studio\Projects\Original_name_of_apk\name_of_apk\Data\res).
In VTS, reopen or reload the original solution.
Click Build all in the top tab Home. Wait it finish.
Very important : As said before, open your original apk and the newly created apk ( \Documents\Virtuous Ten Studio\Projects\Original_name_of_apk\name_of_apk\Binary) with 7zip, and replace META-INF folder & AndroidManifest.xml file from the original one to the new one. This will sign your apk.
4th phase : Replace the original apk whith the new one.
Copy the new apk on your device, and copy it in the /system/ folder.
Very important :Change permissions to 644 (rw-r--r--) with Root Browser in the device, and then move it to the original folder remplacing the original one.
That's it, wait few minutes and play with your device to see if there are no problems and then reboot, go settings, change language and see the changes !
I suggest you reboot after each change you made in case something goes wrong.
Notes :
In some case I had errors when decompiling apk. I had resolved that by remplacing the version of ApkTool in VTS by the last one (C:\Program Files (x86)\Virtuous Ten Studio\External\ApkTool) version apktool_2.0.0rc3.jar. Then remove the other 2.0.0 jar file.
In some case I couln't build the new apk because of errors in some layout files. I didn't manage to resolve that as the both ROM I have (mine and downloaded one) have the same issue.
If something goes wrong (but it shouldn't be), for example lot of messages "error xxx should close" just when you replace the apk before rebooting try to lanch an adb shell and to retrieve the original apk you had saved in the original dir by erasing the new one and rename the saved one. In some devices you have first to remount the system partion in rw as it's read only.
EDIT :
I had a bug with 1 file I modified : SecMms.apk
I'd tried it and it was working fine, but after I receive message, it crash always.
After some testing, I got it working by using the old version of APKTOOL (1.5.2) for decompiling it.

How to add new fonts to fire os 4.6.3?

So, I needed to add a new font to my fire phone so that I can view my native language.
Thinking fire os 4.6.3 is just a customization on android KitKat(4.4.4) I went ahead and tried to add my fonts (Noto Sans Sinhala) to /system/fonts directory. But It was a read only sqfs partition. So I unmounted it and copied it's contents to a actual /system/fonts directory. Then I added a new font family with my fonts in /system/etc/fallback_fonts.xml and rebooted which is the trick for JB and later roms. Nothing happened! Still no native language.
Then I tried replacing a default android font I normally don't use(Noto Sans Thai). Still not working. So I changed Droid Sans Fallback font, which is the oldest trick to get new glyphs. Nope, still not working.
After fiddling around a little, I found a fontconfig cache in /system/etc/fonts along with fontconfig configuration files!! Something I haven't seen in any other android roms. Finally, I came to the conclusion that I might have to rebuild the fontconfig cache.
Dose anyone know how to trigger a fontconfig cache rebuild? or some other way around it?

So, as It turns out, Adding fonts to the fire phone is even easier than the rest of the KK devices. Just copy your fonts to /system/fonts and delete /system/etc/fonts/cachedir/[longname].cache-3 reboot and you are done

madushan1000, how did you umount /mnt/sqfs? I tried un-mounting via file manager with root privilege and wouldn't let me un-mount. I'm trying to replace a default android font (droidfallback.ttf) and keep getting permission denied even though I have root. Your help is appreciated.

You don't have to unmount it. Just delete the fonts sqfs image and extract it's content to /system/fonts and reboot. FYI you might have to remove some "system" app to do this. There is not enough space left on the system partition.

madushan1000,
Care to tell detail instruction? Thank you so much.
Rgds,
Kaung

Hi madushan1000,
This is what I did and still not OK. (Need to restore previous version as Font are lost)
1. Copy Fonts to Sdcard
2. Delete /system/sqfs/container.sqfs
3. mkdir fonts folder under /system
4. Copy back fonts to /system/fonts
Please help me advise. Thank you so much in advance..

Hi @kaungmyataung, I'm going to answer your PM here:
Well, madushan1000 and I had the same approach to the "problem", but I deleted only the container and copied the fonts folder to the usual path.
madushan1000 went even further with his custom XML test.
It seems you did everything right: deleted the container, copied the fonts in the correct folder...
I assume, I checked / set the permissions for the "fonts" folder to 755 and that's all I did.
Oh... and I only deleted unwanted fonts, I didn't add new ones.

Bingo Bronson said:
Hi @kaungmyataung, I'm going to answer your PM here:
Well, madushan1000 and I had the same approach to the "problem", but I deleted only the container and copied the fonts folder to the usual path.
madushan1000 went even further with his custom XML test.
It seems you did everything right: deleted the container, copied the fonts in the correct folder...
I assume, I checked / set the permissions for the "fonts" folder to 755 and that's all I did.
Oh... and I only deleted unwanted fonts, I didn't add new ones.
Click to expand...
Click to collapse
Thank you soooooo much, Bingo. Below of your reply save my life. Now All good.
-----I assume, I checked / set the permissions for the "fonts" folder to 755 and that's all I did.------

Can someone help me i cant copy my font in /system/fonts Please help...

xaamaa said:
Can someone help me i cant copy my font in /system/fonts Please help...
Click to expand...
Click to collapse
You can't copy fonts because it's not a real folder, just a mounted container (read only). Follow Madushan's lead:
madushan1000 said:
locate the sqfs image ('./system/sqfs/container.sqfs') and extract its content to './system/fonts'
you can create the 'fonts' folder manually, just be sure to set permission to 0755 for the folder and 0644 for the font files
FYI: you might have to remove some "system" apps / files to do this. There is not enough space left on the system partition
Easiest way to gain enough free space is to delete the language files for Ivona TTS ('./system/tts/ivona')
One folder for each language, for example "eng.usa.nina_1418201400000". Folders can be deleted if you don't use Ivona TTS.
Click to expand...
Click to collapse
Or you can just delete the sqfs file, create the 'fonts' folder and use this flashable zip via Safestrap / TWRP.
I deleted the CN and JP fonts*, etc. so it's less than 20 MB compared to over a 100 MB from the default sqfs container and you wouldn't be forced to delete system files in order to make enough room.
*Deleted fonts:
STKai
STYuanMedium
TBGothic_213
TBMincho_213
TsukuMinPr5
MYingHeiSMedium
STBShusong
STYuanMedium
MTChineseSurrogates
MHeiM-Big5HKSCS_E
Code2000
DroidNaskh
DroidSansEthiopic
DroidSansHebrew
NotoSansThai
NotoSansThaiUI
DroidSansArmenian
DroidSansGeorgian
NotoSansDevanagari
NotoSansTamil
NotoSansMalayalam
NotoSansBengali
NotoSansTelugu
NotoSansKannada
NotoSansKhmer
NotoSansLao
NanumGothic
Padauk-book
NotoSansSymbols
NotoColorEmoji
MTLmr3m
After creating the real 'fonts' folder, you can spam your phone with iFont.

Bingo Bronson said:
You can't copy fonts because it's not a real folder, just a mounted container (read only). Follow Madushan's lead:
Or you can just delete the sqfs file, create the 'fonts' folder and use this flashable zip via Safestrap / TWRP.
I deleted the CN and JP fonts*, etc. so it's less than 20 MB compared to over a 100 MB from the default sqfs container and you wouldn't be forced to delete system files in order to make enough room.
*Deleted fonts:
STKai
STYuanMedium
TBGothic_213
TBMincho_213
TsukuMinPr5
MYingHeiSMedium
STBShusong
STYuanMedium
MTChineseSurrogates
MHeiM-Big5HKSCS_E
Code2000
DroidNaskh
DroidSansEthiopic
DroidSansHebrew
NotoSansThai
NotoSansThaiUI
DroidSansArmenian
DroidSansGeorgian
NotoSansDevanagari
NotoSansTamil
NotoSansMalayalam
NotoSansBengali
NotoSansTelugu
NotoSansKannada
NotoSansKhmer
NotoSansLao
NanumGothic
Padauk-book
NotoSansSymbols
NotoColorEmoji
MTLmr3m
After creating the real 'fonts' folder, you can spam your phone with iFont.
Click to expand...
Click to collapse
locate the sqfs image ('./system/sqfs/container.sqfs') and extract its content to './system/fonts'
you can create the 'fonts' folder manually, just be sure to set permission to 0755 for the folder and 0644 for the font files
How can i Extract container.sqfs content to /system/fonts..
Where i can create a font folder i mean in which directory...

kaungmyataung said:
Hi madushan1000,
This is what I did and still not OK. (Need to restore previous version as Font are lost)
1. Copy Fonts to Sdcard
2. Delete /system/sqfs/container.sqfs
3. mkdir fonts folder under /system
4. Copy back fonts to /system/fonts
Please help me advise. Thank you so much in advance..
Click to expand...
Click to collapse
@kaungmyataung
@madushan1000
I deleted /system/sqfs/container.sqfs and then tried to copy the fonts to /system/fonts since it rejected for "unmounted folder" even being root user, I dont remember the exact error message but I just rebooted the Kindle Fire HD 3rd gen, now it bricked Boot loop, no matter factory reset at the boot recovery, it simply stays at the boot loop, any suggestion to at least recover it?

[HowTo] Install AOSP Keyboard w/ Long Press Alternates

Hey all,
I'm a HUGE fan of the true stock AOSP keyboard with the long-press alternates on every key. However, it is always difficult to get it installed (or find the proper files on the web, for that matter). This tutorial is NOT for the newish Google Keyboard on the Play Store - I consider that one an inferior frakking piece of shtako. But everyone is entitled to their own opinions.
Anyhow, here are two tutorials to install the AOSP Keyboard on the OnePlus X. First tutorial is for those people running OOS 2.2.0-X (i.e. the latest OTA). Second tutorial is for those people running OOS 2.2.0 (i.e. without the latest OTA - y'all have it easier than those of us who updated!)
Before you begin... I'd recommend performing a Nandroid backup through your recovery (TWRP/CWM/etc).
FIRST TUTORIAL - IF YOU'VE UPDATED TO OOS 2.2.0-X:
1. Download the attached AOSP Keyboard.zip file & extract to your SD card.
2. Go into your file manager & browse to Root/system/app. Look for the folder LatinImeGoogle.
3. Rename the LatinImeGoogle folder to something else. I used LatinImeGoogle-backup for safety reasons. Always leave yourself an out!
4. Change the LatinImeGoogle-backup folder permissions to r-r-r (really this is flexible - just use something other than what is currently assigned to the folder.)
5. Go back to where you extracted the AOSP Keyboard folder contents.
6. Copy libjni_latinime.so to system/lib/
7. Set libjni permissions to rw-r--r-- (aka 644)
8. Copy LatinIME folder to system/app/
9. Set LatinIME folder permissions to drwxr-xr-x (aka 755)
10. Open "LatinIME" folder.
11. Set LatinIME.apk permissions to rw-r--r--(aka 644)
12. Set "lib" folder permissions to drwxr-xr-x (aka 755)
13. Open "lib" folder.
14. Set "arm" folder permissions to drwxr-xr-x (aka 755)
15. Open "arm" folder. IF there is anything in the "arm" folder, delete it. (Sometimes Android will auto add libjni_latinime.so in there. Just delete it).
16. Go back to your root /system/lib/ and scroll down to libjni_latinime.so.
17. Long press on the libjni_latinime.so file. Choose "Create symlink".
18. In the Symlink location field, choose Browse. Navigate to /system/app/LatinIME/lib/arm/ and Create the symlink there.
19. Go back to your root /system/app/LatinIME/lib/arm/. You should now see a symlink "shortcut" to libjni_latinime.so. Set the shortcuts permissions to rw-r--r-- (aka 644).
20. Reboot your device.
21. Celebrate with a cookie!
SECOND TUTORIAL - IF YOU'RE RUNNING OOS 2.2.0 WITHOUT THE LATEST OTA:
1. Download the attached AOSP Keyboard.zip file & extract to your SD card.
2. Copy libjni_latinime.so to system/lib/
3. Set libjni permissions to rw-r--r-- (aka 644)
4. Copy LatinIME folder to system/app/
5. Set LatinIME folder permissions to drwxr-xr-x (aka 755)
6. Open "LatinIME" folder.
7. Set LatinIME.apk permissions to rw-r--r--(aka 644)
8. Set "lib" folder permissions to drwxr-xr-x (aka 755)
9. Open "lib" folder.
10. Set "arm" folder permissions to drwxr-xr-x (aka 755)
11. Open "arm" folder. IF there is anything in the "arm" folder, delete it. (Sometimes Android will auto add libjni_latinime.so in there. Just delete it).
12. Go back to your root /system/lib/ and scroll down to libjni_latinime.so.
13. Long press on the libjni_latinime.so file. Choose "Create symlink".
14. In the Symlink location field, choose Browse. Navigate to /system/app/LatinIME/lib/arm/ and Create the symlink there.
15. Go back to your root /system/app/LatinIME/lib/arm/. You should now see a symlink "shortcut" to libjni_latinime.so. Set the shortcuts permissions to rw-r--r-- (aka 644).
16. Reboot your device.
17. Celebrate with a brownie!
I've also tucked a txt copy of the barebones instructions into the zip file.
Feel free to ask any questions below.
Cheers,
equi

hi equi_design
thank you very much for providing a manual for aosp keyboard. i followed you instructions and everything went through apart from changing the shortcut to 644. i could not get any access in order to change permissions. nevertheless, keyboard works without any problems so far!
btw which filemanager did you use? es explorer for example does not support the creation of symlinks (i am on version 3)
best wishes,
lukas

lukas235 said:
hi equi_design
thank you very much for providing a manual for aosp keyboard. i followed you instructions and everything went through apart from changing the shortcut to 644. i could not get any access in order to change permissions. nevertheless, keyboard works without any problems so far!
btw which filemanager did you use? es explorer for example does not support the creation of symlinks (i am on version 3)
best wishes,
lukas
Click to expand...
Click to collapse
To create a symlink I used the root Explorer pro

lukas235 said:
hi equi_design
thank you very much for providing a manual for aosp keyboard. i followed you instructions and everything went through apart from changing the shortcut to 644. i could not get any access in order to change permissions. nevertheless, keyboard works without any problems so far!
btw which filemanager did you use? es explorer for example does not support the creation of symlinks (i am on version 3)
best wishes,
lukas
Click to expand...
Click to collapse
Glad it worked out in the end. I use Solid Explorer now. About a year ago, I gave up on ES since they were dropping & hidden files onto my SD card. I'd suggest looking around for another file manager if you can.
Sent from my OnePlus using XDA Labs