This module will disable system write protection on the stock HTC One kernel.
To make /system writeable, you must install the module and then remount /system as rw.
For example:
insmod /system/lib/modules/wp_mod.ko
mount -o remount,rw /system
You can make an init.d script to load it, or add it to the boot.img. Either way will work, but it's important that this is loaded at boot, as attempting to make changes to /system and then installing this module could corrupt the partition.
This is mainly for devs, who are free to incorporate it into their ROMs.
Unless you are an advanced user, I would wait for it to be included in your favourite ROM.
A credit and a link here so people can thank me in the OP would be much appreciated
Download:
wp_mod.ko
Source code: wp_mod.c
Awesome mate... Thanks a lot
Thanks!
Quick question, do we need to install the module manually first before I create the init script?
wp_mod.ko for 3.4.10-gddcfb8c kernel version
wow ... new version from this mod ... thx :highfive:
ok ... installed wp_mod.ko to system/lib/modules ... make a new boot.img ... restart ... modified a file in system ... restart ... but changed file back original
ok ... next try ... i found the mod is kernel depends ... hexedit the mod to my kernel version ... installed ... modified a file ... restart ... and it works now, the file is well modified
thx @flar2
attached my modified wp_mod.ko only for 3.4.10-gddcfb8c kernel-version
use the attached with cwm-recovery, its only the modified wp_mod.ko file
The module should be placed somewhere on your /system partition, because that is what is mounted early in the boot process.
Kernel modules are usually located in /system/lib/modules/ but you can put it anywhere on /system
Then you can load it with an init script using the commands I posted above. Or you can put those commands in init.rc in the boot.img. Obviously the command has to be modified to reflect the location where you copied wp_mod.ko
You have to make sure that the boot.img is set to run init.d scripts, this is also done in init.rc.
Isotopes said:
wow ... new version from this mod ... thx :highfive:
ok ... installed wp_mod.ko to system/lib/modules ... make a new boot.img ... restart ... modified a file in system ... restart ... but changed file back original
ok ... next try ... i found the mod is kernel depends ... hexedit the mod to my kernel version ... installed ... modified a file ... restart ... and it works now, the file is well modified
Click to expand...
Click to collapse
Yes, it will only load if the version info matches.
If people don't know what that means, check your kernel:
uname -a
And make sure the module has the same string:
modinfo wp_mod.ko
You can change it with a hex editor as above, make sure you only change the characters of the version string and nothing else.
Good job mate
torxx said:
Good job mate
Click to expand...
Click to collapse
Really good job can you do the same file for the kernel? Thanks in advance
wp_mod.ko for 3.4.10-g87f8d97 kernel version
nikotine81 said:
Really good job can you do the same file for the kernel? Thanks in advance
Click to expand...
Click to collapse
and now, here the wp_mod.ko for 3.4.10-g87f8d97 kernel version
use the attached with cwm-recovery, its only the modified wp_mod.ko file
Isotopes said:
and now, here the wp_mod.ko for 3.4.10-g87f8d97 kernel version
use the attached with cwm-recovery, its only the modified wp_mod.ko file
Click to expand...
Click to collapse
Thanks i will test
Isotopes said:
and now, here the wp_mod.ko for 3.4.10-g87f8d97 kernel version
use the attached with cwm-recovery, its only the modified wp_mod.ko file
Click to expand...
Click to collapse
Works fine
Thanks
Nekromantik said:
Works fine
Thanks
Click to expand...
Click to collapse
fine is the wrong word, works perfect :good::good::good:
Hi! Just wanted to add additional info. Since the kernel source is out now you could also disable write protection by changing the line in
arch/arm/configs/m7_defconfig
Click to expand...
Click to collapse
from
CONFIG_MMC_MUST_PREVENT_WP_VIOLATION=y
Click to expand...
Click to collapse
to
# CONFIG_MMC_MUST_PREVENT_WP_VIOLATION is not set
Click to expand...
Click to collapse
referencing file
arch/arm/mach-msm/emmc_partitions.c
Click to expand...
Click to collapse
code
Code:
#ifdef CONFIG_MMC_MUST_PREVENT_WP_VIOLATION
if (!strncmp(ptn->name, "system", 6))
mmc_blk_set_wp_prevention_partno((int) ptn->offset);
#endif
on
Code:
void mmc_blk_set_wp_prevention_partno(int partno)
{
sprintf(wp_prevention_partno, "mmcblk0p%d", partno);
pr_info("%s: set wp_prevention_partno to %s\n", __func__, wp_prevention_partno);
}
EXPORT_SYMBOL(mmc_blk_set_wp_prevention_partno);
from
drivers/mmc/card/block.c
Click to expand...
Click to collapse
Works great thank you
Sent from my HTC One using xda app-developers app
Riyal said:
Hi! Just wanted to add additional info. Since the kernel source is out now you could also disable write protection by changing the line in
from
to
referencing file
code
Code:
#ifdef CONFIG_MMC_MUST_PREVENT_WP_VIOLATION
if (!strncmp(ptn->name, "system", 6))
mmc_blk_set_wp_prevention_partno((int) ptn->offset);
#endif
on
Code:
void mmc_blk_set_wp_prevention_partno(int partno)
{
sprintf(wp_prevention_partno, "mmcblk0p%d", partno);
pr_info("%s: set wp_prevention_partno to %s\n", __func__, wp_prevention_partno);
}
EXPORT_SYMBOL(mmc_blk_set_wp_prevention_partno);
from
Click to expand...
Click to collapse
Thank you, I discovered this months ago: http://forum.xda-developers.com/showthread.php?t=2059411. The reason for disabling it via a module is so people can continue to use the stock kernel. There are already custom kernels for this phone, but not everyone wants a custom kernel.
flar2 said:
Thank you, I discovered this months ago: http://forum.xda-developers.com/showthread.php?t=2059411. The reason for disabling it via a module is so people can continue to use the stock kernel. There are already custom kernels for this phone, but not everyone wants a custom kernel.
Click to expand...
Click to collapse
Only custom kernel is one from you at the moment.
Have to wait for more devs now.
The base version for the source code seems to be a older base, does that make a difference?
Nekromantik said:
Only custom kernel is one from you at the moment.
Have to wait for more devs now.
The base version for the source code seems to be a older base, does that make a difference?
Click to expand...
Click to collapse
It depends on what they changed.
I thought a couple custom kernels were posted in the trick droid thread?
flar2 said:
It depends on what they changed.
I thought a couple custom kernels were posted in the trick droid thread?
Click to expand...
Click to collapse
Only saw one other one but that did not work as it had issues with calls.
flar2 said:
Thank you, I discovered this months ago: http://forum.xda-developers.com/showthread.php?t=2059411. The reason for disabling it via a module is so people can continue to use the stock kernel. There are already custom kernels for this phone, but not everyone wants a custom kernel.
Click to expand...
Click to collapse
Nice! Never had a One X phone so wasn't aware of your mods :fingers-crossed:
If you're feeling adventurous here's a kernel to try:
http://goo.im/devs/flar2/One/Bulletproof-m7-0.1.zip
I don't have this device, so I couldn't test it. It might not work.
If the installer doesn't work, take the boot.img out of the zip and flash it in fastboot.
If the kernel won't boot, please send me /proc/last_kmsg. I might have to make some adjustments to the boot.img.
Don't install this unless you want to help me out with log files, etc.
Related
This can make filenames with special characters to be shown correctly when using cifs.
The module was extracted from the kernel in this post.
The script I wrote would load modules by insmod. You can select which modules to load on boot by editing the config file located at /data/init.insmod.conf.
The config file will be re-generated after delete / data wipe.
The attached file is also hosted here
Hi man
I traid to boot this on a CM6.1 RC2 but it give an error in the load what I have to do to boot it
Czaro said:
Hi man
I traid to boot this on a CM6.1 RC2 but it give an error in the load what I have to do to boot it
Click to expand...
Click to collapse
I cant understand you completely, but please try the new zip I've just uploaded.
chrisanddarla
I installed cm6 and lost the market. Can anyone tell me if it is possible to get it back and if so how? Thanks
chrisanddarla said:
I installed cm6 and lost the market. Can anyone tell me if it is possible to get it back and if so how? Thanks
Click to expand...
Click to collapse
With cm6, you must also install the GAPPS add on for Google apps.
http://android.d3xt3r01.tk/cyanogen/gapps/gapps-mdpi-20101020-signed.zip
I dont have this phone,try at your own risk!
as the title says,this mod will enable u to easily customize bootscreen !
I Have Attached The Custom Booting.zip File
Which Contain 2 files
1) bootanimation
2) samsungani
NOTE : Files Should Be Executable
ie. Permission should be rwxr_xr_x (r=read, w=write, x= executable)
These Two Files Have to be copied to /system/bin With Root Explorer Or Any Thing Like That
The Next File I am Attaching Is sanim.zip
sanim.zip file must be copied To /system/media
delete /system/media/shutdown.qmg /system/media/bootanimation.qmg and /system/media/bootanimationloop.qmg.
The sanim contains the PNG files Which Can be edited As your will
Downloads
Custom Booting
Sanim.zip
Credits:vivekkalady
I put all files where you said and changed permissions accordingly, the phone boots alright, but after the samsung- and the following galaxy s plus gt....-screens
there is just a black screen till boot is complete.
Aurellion said:
I put all files where you said and changed permissions accordingly, the phone boots alright, but after the samsung- and the following galaxy s plus gt....-screens
there is just a black screen till boot is complete.
Click to expand...
Click to collapse
really strange............will see if anything can be done
r u sure u didint forget sanim.zip?
Aurellion said:
I put all files where you said and changed permissions accordingly, the phone boots alright, but after the samsung- and the following galaxy s plus gt....-screens
there is just a black screen till boot is complete.
Click to expand...
Click to collapse
exactly the same for me..
@sakindia123: I tried a custom boot animation (renamed to sanim.zip) which didn't work. But I also tried the original sanim.zip which also doesn't seem to work
sakindia123 said:
really strange............will see if anything can be done
r u sure u didint forget sanim.zip?
Click to expand...
Click to collapse
Yeah, just double checked everything, doesn't work
Aurellion said:
Yeah, just double checked everything, doesn't work
Click to expand...
Click to collapse
what is the samsungani doing in your version (I know what it's doing but I wanna have an answer for your system ).
manveru0 said:
what is the samsungani doing in your version (I know what it's doing but I wanna have an answer for your system ).
Click to expand...
Click to collapse
I'm not sure what you mean, so I uploaded my samsungani:
https://rapidshare.com/files/3183414437/samsungani
Aurellion said:
I'm not sure what you mean, so I uploaded my samsungani:
https://rapidshare.com/files/3183414437/samsungani
Click to expand...
Click to collapse
ooops, sorry my mistake. My question was for Sakindia. I was wondering because he obviously didn't change the init.rc which would trigger the bootanimation binary.
EDIT: Nevermind. Found it out by looking at the files. The samsungani Sakindia uploaded does trigger the bootanimation binary, so no need to do it in the init.rc
manveru0 said:
ooops, sorry my mistake. My question was for Sakindia. I was wondering because he obviously didn't change the init.rc which would trigger the bootanimation binary.
EDIT: Nevermind. Found it out by looking at the files. The samsungani Sakindia uploaded does trigger the bootanimation binary, so no need to do it in the init.rc
Click to expand...
Click to collapse
yup,that's y ramdisk wasnt needed
can u investigate the matter manveru0?
sakindia123 said:
yup,that's y ramdisk wasnt needed
can u investigate the matter manveru0?
Click to expand...
Click to collapse
well I've tested my own version of it (but with modded init.rc) and I was facing the same issue as the other users did with your version. Where did you get the bootanimation binary from? I think that binary may cause the issue. Anyway I have to take a deeper look at what happens when starting the bootanimation.
The question....is it can be use now?
GT-I9001 Adrenaline Shot v13 - powered by Instanet free edition : )
pyronia said:
The question....is it can be use now?
GT-I9001 Adrenaline Shot v13 - powered by Instanet free edition : )
Click to expand...
Click to collapse
No it's not unfortunately
broodplank1337 said:
No it's not unfortunately
Click to expand...
Click to collapse
delete /system/media/shutdown.qmg /system/media/bootanimation.qmg and /system/media/bootanimationloop.qmg. It should work afterwards. See also the latest FeaMod Release as the FeaCore kernel now supports bootanimation.zip (I've changed the init.rc and took a different bootanimation binary):
http://www.mediafire.com/?38j6nnnztki7wdj
manveru0 said:
delete /system/media/shutdown.qmg /system/media/bootanimation.qmg and /system/media/bootanimationloop.qmg. It should work afterwards. See also the latest FeaMod Release as the FeaCore kernel now supports bootanimation.zip (I've changed the init.rc and took a different bootanimation binary):
http://www.mediafire.com/?38j6nnnztki7wdj
Click to expand...
Click to collapse
Sounds great! Gonna try it now
Edit: Works! Good work! Finally someone who managed it to make a custom boot ani for i9001
broodplank1337 said:
Sounds great! Gonna try it now
Edit: Works! Good work! Finally someone who managed it to make a custom boot ani for i9001
Click to expand...
Click to collapse
u can pickup any existing one.......sample is attached
sakindia123 said:
u can pickup any existing one.......sample is attached
Click to expand...
Click to collapse
What file do I replace for a new one? because i can't find any bootanimation in /system/media
broodplank1337 said:
What file do I replace for a new one? because i can't find any bootanimation in /system/media
Click to expand...
Click to collapse
u dont have to replace...just add it there
sakindia123 said:
u dont have to replace...just add it there
Click to expand...
Click to collapse
Tried placing it there and set permissions but without success.
Do i need to use ADB Push for this?
broodplank1337 said:
Tried placing it there and set permissions but without success.
Do i need to use ADB Push for this?
Click to expand...
Click to collapse
no need................did u delete specified files?
sakindia123 said:
no need................did u delete specified files?
Click to expand...
Click to collapse
Totally works now, i used the kernel posted here, didn't work with that but it works with 1.3.1 feamod (and the 2 files in system/bin ofc)
thnx a bunch guys
I know some people have had a need to take apart a the boot.img file that mtd roms use, and I have been curious myself, so I wrote a bash script to do the job. The format of these files is as follows:
Code:
[
zImage[
kernel,
initramfs,
???
],
header (512 bytes),
boot,
recovery,
]
This script will split out the zImage, boot, recovery, and the initramfs from inside the zimage. These are all in gzipped cpio format. All three of those will be extracted into separate folders.
Instructions for use:
IMPORTANT: run this as root so permissions are preserved
Code:
tar -xf extract_boot.tar.bz2
./extract_boot.sh -b boot.img -o output_dir
Download link:
extract_boot.tar.bz2 - 1 KB
Thanks:
supercurio: Used some of his code from kernel_repack_utils to learn how to extract the zImage.
How to rebuild:
There is a script in the EpicCM repos that can rebuild a boot.img from the zImage, boot.cpio.gz, and recovery.cpio.gz.
Link: mkshbootimg.py
Thank you. I've been looking for this.
Sent from my SPH-D700 using Tapatalk
What am I doing wrong? I've tried extracting both cm7 and stock mtd kernels using this tool on android using terminal emulator. They both say syntax error.
Sent from my SPH-D700 using Tapatalk
xboxfanj said:
What am I doing wrong? I've tried extracting both cm7 and stock mtd kernels using this tool on android using terminal emulator. They both say syntax error.
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
This is meant for Linux. Something like Fedora or Ubuntu. Its a bash script, so it may still work on a phone it you run it in bash, but I doubt it.
Sent from my SPH-D700 using xda premium
Also, I think our boot.img's are a little weird.
sent from my always aosp epic
While you were figuring this out, I was getting this ready......
https://github.com/nubecoder/create_boot.img
Kernel devs should easily be able to make some use of it.
=]
nubecoder said:
While you were figuring this out, I was getting this ready......
https://github.com/nubecoder/create_boot.img
Kernel devs should easily be able to make some use of it.
=]
Click to expand...
Click to collapse
Oh you sneaky....
sent from my always aosp epic
zman0900 said:
I know some people have had a need to take apart a the boot.img file that mtd roms use, and I have been curious myself, so I wrote a bash script to do the job. The format of these files is as follows:
Code:
[
zImage[
kernel,
initramfs,
???
],
header (512 bytes),
boot,
recovery,
]
This script will split out the zImage, boot, recovery, and the initramfs from inside the zimage. These are all in gzipped cpio format. All three of those will be extracted into separate folders.
Instructions for use:
IMPORTANT: run this as root so permissions are preserved
Code:
tar -xf extract_boot.tar.bz2
./extract_boot.sh -b boot.img -o output_dir
Download link:
extract_boot.tar.bz2 - 1 KB
Thanks:
supercurio: Used some of his code from kernel_repack_utils to learn how to extract the zImage.
How to rebuild:
There is a script in the EpicCM repos that can rebuild a boot.img from the zImage, boot.cpio.gz, and recovery.cpio.gz.
Link: mkshbootimg.py
Click to expand...
Click to collapse
okay so...
extracting = CHECK
repacking = wtf???
how are you supposed to use the code from github? i dont see a way to download it so u can use as an executable text file and copying and pasting code into the teminal doesnt work.... how do i use it?
roddygonzo17 said:
okay so...
extracting = CHECK
repacking = wtf???
how are you supposed to use the code from github? i dont see a way to download it so u can use as an executable text file and copying and pasting code into the teminal doesnt work.... how do i use it?
Click to expand...
Click to collapse
Click the raw link in the upper right. That will give you plain text. You might want to check out what nubecoder did above, it could be easier to use.
Sent from my SPH-D700 using xda premium
nubecoder said:
While you were figuring this out, I was getting this ready......
https://github.com/nubecoder/create_boot.img
Kernel devs should easily be able to make some use of it.
=]
Click to expand...
Click to collapse
Nice! I've been working on a kernel and set up a similar build system for it in my github.
Some questions: how does mkbootfs work? It seems tovtake the place of cpio -o -c. Does it automatically set up the correct file permissions and ownership? If not, how are these being set? Last, is there source somewhere?
Sent from my SPH-D700 using xda premium
So do u have to make a zimage first and then make that a boot.img? I am so confused.
Sent from my SPH-D700 using Tapatalk
xboxfanj said:
So do u have to make a zimage first and then make that a boot.img? I am so confused.
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
Yep.
sent from my always aosp epic
So then where's the zimage maker?
Sent from my SPH-D700 using Tapatalk
xboxfanj said:
So then where's the zimage maker?
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
You compile it yourself..
sent from my always aosp epic
nubecoder said:
While you were figuring this out, I was getting this ready......
https://github.com/nubecoder/create_boot.img
Kernel devs should easily be able to make some use of it.
=]
Click to expand...
Click to collapse
This worked after a few fixes. The script references files without the ./ prefix in several places. This caused errors for me. I'm completely sure why, but I think it's because of my shell configuration change I had to make to install the codesourcery ARM toolchain.
After fixing it, it created the boot.img jsut fine, but the resulting image was too large to flash - around 7.6MB. Either the recovery or initramfs (I'm sorry I don't remember which one right now) you supplied is much larger than the one I was using and caused the increased size.
toadlife said:
This worked after a few fixes. The script references files without the ./ prefix in several places. This caused errors for me. I'm completely sure why, but I think it's because of my shell configuration change I had to make to install the codesourcery ARM toolchain.
After fixing it, it created the boot.img jsut fine, but the resulting image was too large to flash - around 7.6MB. Either the recovery or initramfs (I'm sorry I don't remember which one right now) you supplied is much larger than the one I was using and caused the increased size.
Click to expand...
Click to collapse
I think there's a lot of unnecessary parts in that initramfs, like the res folder and binaries in sbin. I think those should only be in the recovery. Check out my working initramfs in my github https://github.com/zman0900/android_kernel_epic4g_gb_mtd/tree/master/initramfs_mtd
So do the zimages inside the boot.img not have an intramfs? And if that's the case, I can probably just use the zimage that I got when I unpacked the cm7 kernel also when I repack, right? I'm updating intramfs and I know its in boot.img, but idk about zimage. Thanks.
Sent from my SPH-D700 using Tapatalk
xboxfanj said:
So do the zimages inside the boot.img not have an intramfs? And if that's the case, I can probably just use the zimage that I got when I unpacked the cm7 kernel also when I repack, right? I'm updating intramfs and I know its in boot.img, but idk about zimage. Thanks.
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
The zImage from cm7 won't work for a tw rom!
The zImage does have an initramfs. Mtd uses a two stage boot. So the zImage contains the kernel and a small first stage initramfs. The phone loads the zImage and starts the kernel, which then runs init in the first stage. That loads the second stage initramfs from the boot.img and executes its init, which mounts filesystems and handles the rest of the boot.
Sent from my SPH-D700 using xda premium
zman0900 said:
The zImage from cm7 won't work for a tw rom!
The zImage does have an initramfs. Mtd uses a two stage boot. So the zImage contains the kernel and a small first stage initramfs. The phone loads the zImage and starts the kernel, which then runs init in the first stage. That loads the second stage initramfs from the boot.img and executes its init, which mounts filesystems and handles the rest of the boot.
Sent from my SPH-D700 using xda premium
Click to expand...
Click to collapse
LOL. I know TW and CM7 kernels aren't compatible. Thank you very much for all the information though.
Umm...the zImage for tw WILL work for cm...its just the initramfs that changes, iirc
sent from my touchwiz 4.5-ed epic
Hi everyone! First of all, sorry for my english.
My question is very simple. I am going to flash Aero Kernel into my Moto G xt1034.
In case something goes wrong or i want to go back to stock kernel, does reflash the rom via fastboot replaces the kernel? I mean, Aero Kernel is ereased and replaced by the stock kernel?
Thank you very much in advance!
Yep, boot.img is your kernel, so you need to flash that at least. But, I think aero is replacing your kernel modules too (eg the WiFi driver), so you need to flash the system image too. Or backup the original modules from the /system/lib/modules directory.
Rhyn said:
Yep, boot.img is your kernel, so you need to flash that at least. But, I think aero is replacing your kernel modules too (eg the WiFi driver), so you need to flash the system image too. Or backup the original modules from the /system/lib/modules directory.
Click to expand...
Click to collapse
Thank you. Does flashing stock Rom replaces those modules ?
neucoas said:
Thank you. Does flashing stock Rom replaces those modules ?
Click to expand...
Click to collapse
If you mean by flashing is fastboot flash etc, then yes. The system.sparesechunk.0-3 files contains your full system partition including the kernel modules. But if you do a cwm backup from your stock system partition before flashing aero and flash that back, that will work too.
Edit: if you just do a backup from /system/lib/modules directory, you should include /system/lib/hw/power.msm8226.so too, hence aero installer also deletes that too.
Usually if you uncertain what a flashable zip do, you can always examine the META-INF/com/google/android/updater-script file. Thats the installer, you can open it with a simple text editor. Usually not too hard to understand, its quite a simple language.
Rhyn said:
If you mean by flashing is fastboot flash etc, then yes. The system.sparesechunk.0-3 files contains your full system partition including the kernel modules. But if you do a cwm backup from your stock system partition before flashing aero and flash that back, that will work too.
Edit: if you just do a backup from /system/lib/modules directory, you should include /system/lib/hw/power.msm8226.so too, hence aero installer also deletes that too.
Usually if you uncertain what a flashable zip do, you can always examine the META-INF/com/google/android/updater-script file. Thats the installer, you can open it with a simple text editor. Usually not too hard to understand, its quite a simple language.
Click to expand...
Click to collapse
Thank you very much! :victory:
Hello guys. I found this annoying bug on CyanogenMod 12.1 based ROM, that the swipe feature on AOSP keyboard does not work. So I have made a flashable zip of few hundred KBs that allows you to use Swipe. You can flash it over any ROM (might work on older versions of android too) and it won't require any kind of wipe.
Requirements
Root
Custom Recovery
SwipeFix.zip - 464.4KiB
Do not mirror please.
How to use the mod?
Boot into custom recovery
Flash the zip
Reboot into system
profit
If you want to use the mod, give proper credits
Hey MZO
Thanks
IRRITATING bug indeed, I cannot believe this is not corrected in a nightly! (what is the actual solution please?)
I can report it works on the latest trltexx (SM-N910F, Note 4)
Thanks
beng
BenG7 said:
Hey MZO
Thanks
IRRITATING bug indeed, I cannot believe this is not corrected in a nightly! (what is the actual solution please?)
I can report it works on the latest trltexx (SM-N910F, Note 4)
Thanks
beng
Click to expand...
Click to collapse
Yeah, the actual solution is a missing library actually. It's not built in CM or any custom ROM, I'd include the lib in my builds tho.
Sent from my FIND7 using XDA Free mobile app
Thanks again MZO
What is the missing lib then, libjn_latinime.so?
I looked into it, and I read at some point that it had been renamed to libjn_latinimegoogle.so...
thanks
beng
2 Years later still Keyboard Swipe Problem
It's over 2 years now and this problem still appears.
I'm using an otherwise great custom ROM but the AOSP keyboard Gesture/Swipe function isn't working although it's shown.
I tried flashing this zip solution with TWRP 3.0 but the flash failed. Any ideas how to get this working? Should this zip solution still work?
Laugh2 said:
It's over 2 years now and this problem still appears.
I'm using an otherwise great custom ROM but the AOSP keyboard Gesture/Swipe function isn't working although it's shown.
I tried flashing this zip solution with TWRP 3.0 but the flash failed. Any ideas how to get this working? Should this zip solution still work?
Click to expand...
Click to collapse
Hi
I use the script but with lib64. And I can swype :good:
You have to create a lib64 folder and put the last version of the file. (Open a ROM file or gapps and take the last one)
And you have to edit the updater-script with lib64 folder.
musklor said:
Hi
I use the script but with lib64. And I can swype :good:
You have to create a lib64 folder and put the last version of the file. (Open a ROM file or gapps and take the last one)
And you have to edit the updater-script with lib64 folder.
Click to expand...
Click to collapse
Would the binary file still work? I am asking because it is 32 bit executable: ELF 32-bit LSB executable, ARM, EABI5 version 1 (SYSV), statically linked, stripped but I am not sure how to get it for arm64. (I have a S7 btw, and the absence of swipe-typing is a big issue.)
aarem said:
Would the binary file still work? I am asking because it is 32 bit executable: ELF 32-bit LSB executable, ARM, EABI5 version 1 (SYSV), statically linked, stripped but I am not sure how to get it for arm64. (I have a S7 btw, and the absence of swipe-typing is a big issue.)
Click to expand...
Click to collapse
You can use nanodroid with twrp