Related
i want to install http://forum.xda-developers.com/showthread.php?t=1004740
i follow all the instruction but i cant get it to work on my phone..how to get it to work?..i use http://forum.xda-developers.com/showthread.php?t=964223 this rom..
please help..i really want this feature..
try manual installation, or you haven´t already activate gesture - try again
already try manual instruction...how to activate gesture?
edit:i cant understand the manual instruction..can you help me..heres the hw_config.sh file..
please help me out..
Remount /system as rw
- Copy the attached x8gesture.ko below to /system/lib/modules
- Change hw_config.sh in your /system/etc, add this code at the beginning
insmod /system/lib/modules/x8gesture.ko #dx: add gestures
use RE
downloaded the gesture x8gesture-v004.zip and installed it,
downloaded update-floyo15-2011-03-26-rel-signed.zip and installed it,
checked all the relevant files (hw_config.sh- it had the necessary code in that file and the x8gesture.ko was in /system/lib/modules)
but it still didnt work. Am i missing something? i have baseband XXX015 and im using floyo. help?
dmcb123 said:
downloaded the gesture x8gesture-v004.zip and installed it,
downloaded update-floyo15-2011-03-26-rel-signed.zip and installed it,
checked all the relevant files (hw_config.sh- it had the necessary code in that file and the x8gesture.ko was in /system/lib/modules)
but it still didnt work. Am i missing something? i have baseband XXX015 and im using floyo. help?
Click to expand...
Click to collapse
Just read instructions again.. begin at the top.. maybe you missed something in the process.. ex. typo error.. because system work on me..
http://forum.xda-developers.com/showthread.php?t=1004740
I just re-read through the instructions and I have done it all correctly. I backed up a friends floyo (he has dualtouch) and restored it onto my phone and it still doesn't work
Sent from my X8 using XDA App
This happened to me too, using minicm rc1, Elelinux v3 and Nexus-x8 v2 also no luck to get it.
Minicm RC1 - using update-minicm2-2011-04-13-signed.zip (9.44 KB) after update,
no dualtouch, loose OC.
check with hw_config.sh, the code is at the bottom.
# dx: our modded touchscreen driver
insmod /system/lib/modules/x8gesture.ko
Install again 3 custom rom - minicm rc1, Elelinux v3 and Nexus-x8 v2
with factory reset
Manual Installation for the dualtouch and oc
I had added the code at the beginning
# dx: our modded touchscreen driver
insmod /system/lib/modules/x8gesture.ko
insmod /system/lib/modules/x8oc.ko # x8 overclock
As a result, Im only get the OC.
Edit: I had baseband 015, and i did adb shell command check also
adb shell
dmesg | grep X8Gesture
It returned a same output in the command prompt.
I had try with Multitouch Visualiser 2, always showing 1 touch
Add insmod line to the top of /system/bin/chargemon. I did that and it's working.
hi blagus, you mean add
insmod /system/lib/modules/x8gesture.ko at top of the line /system/bin/chargemon,
and how about the insmod /system/lib/modules/x8gesture.ko at the hw_config.sh,
leave it there or delete the command line?
lookingpost said:
hi blagus, you mean add
insmod /system/lib/modules/x8gesture.ko at top of the line /system/bin/chargemon,
and how about the insmod /system/lib/modules/x8gesture.ko at the hw_config.sh,
leave it there or delete the command line?
Click to expand...
Click to collapse
Remove insmod from hw_config and put it as the second line in chargemon.
In my case, chargemon looks like this:
Code:
#!/system/recovery/sh
insmod .../x8gesture.ko
insmod .../x8oc.ko
[...and so on...]
I think this is better method that hw_config because chargemon is the first thing executing on boot.
Hi blagus, my chargemon is start like this
#!/system/bin/busybox sh
/system/bin/charger
cat /dev/input/event 1 > /dev/keycheck&
sleep 3
Kill -9 $!
.... and so on ...
So i need to add like this ...
#!/system/bin/busybox sh
insmod /system/lib/modules/x8gesture.ko
insmod /system/lib/modules/x8oc.ko
/system/bin/charger
cat /dev/input/event 1 > /dev/keycheck&
sleep 3
Kill -9 $!
Edit: after test with Mr. Blagus method..the result still the same
OC worked but multitouch failed (I think is my hardware problem)
This didn't work for me either
Sent from my X8 using XDA App
I doubt that it's HW problem... I suggest you to flash baseband 015 again to make sure you have latest kernel.
blagus said:
I doubt that it's HW problem... I suggest you to flash baseband 015 again to make sure you have latest kernel.
Click to expand...
Click to collapse
this didnt work either :\ beginning to think it may well be a hw problem but i really dont understand how that could possibly be
No, it shouldn't be HW problem. When did you buy your phone?
ya..didnt work for me either, Im from malaysia, i also dont understand why will become like this..Now, only OC worked for me but i satisfied what i had now, actually the multitouch not very important for me, just curious to know what happened
About the phone last christmas
Sent from my X8 using XDA App
*I bought the phone last christmas
Sent from my X8 using XDA App
cool ill try it
dmcb123 said:
*I bought the phone last christmas
Sent from my X8 using XDA App
Click to expand...
Click to collapse
Me too, so it CAN'T be HW problem due to new revision... it's somewhere else.
First, chmod x8gesture to 777 (chmod 777 /path-to/x8gesture.ko)
If that fails...
Reflash stock FW (you can get it in my Mediafire folder), root, install xRecovery, then flash custom ROM, copy modules to /system/lib/modules and put insmod lines to chargemon.
blagus said:
Me too, so it CAN'T be HW problem due to new revision... it's somewhere else.
First, chmod x8gesture to 777 (chmod 777 /path-to/x8gesture.ko)
If that fails...
Reflash stock FW (you can get it in my Mediafire folder), root, install xRecovery, then flash custom ROM, copy modules to /system/lib/modules and put insmod lines to chargemon.
Click to expand...
Click to collapse
I had tried before using Root Explorer, tick all at the permission on x8gesture.ko, but dont know this step will be same as your method..will try later on. (Now im using minicm rc2,best rom atm only compass not work)
Edit: after chmod 777 - x8gesture.ko (rwxrwxrwx)
As a result - multitouch didint work, i lost root again (this is 2nd time, first time install floyo theme), now restore back RC2
Dont really want to go back to stock fw, ill wait a while for an update and then see about going back. Thanks anyway really appreciatedappreciated
Sent from my X8 using XDA App
To Blagus,
Reflash stock FW (From your Mediafire folder) and the Build 2.1.1.A.0.6 provided by mohakrastogi, is it the same method?
Let's cut the crap. Seems like somebody on a Chinese forum figured out the way to apply the mod to MM2. I just translate it into English.
1. Download the attachment and unzip milestone2_more.ko to the root of sd
2. mount /system/ r/w
3. copy milestone2_more.ko to /system/lib/modules/
4. open terminal emulator
5. input the following command
su
chmod 644 /system/lib/modules/milestone2_more.ko
insmod /system/lib/modules/milestone2_more.ko touch_num=6
(the guy said if you choose a number greater than 6 the system will crash)
now you should get a 6-point-multitouch
original thread: http://bbs.gfan.com/android-1997547-1-1.html
Thank you soooooooo much! )))
Works but MT is still buggy...
oh my god.. thank you, it works.
5 is more than enough
OMG!! You made my day!
Sent from my A953 using XDA Premium App
Is this permanent? Or it'll go away when we reboot?
Sent from my A953 using XDA App
It will go away when you reboot, but its not a big deal to use the command again
Sent from my A953 using XDA Premium App
Just make a init.d script to load it up when the system boots and you won't have to worry about it again..
Just did this, but I think i wrote it wrong. Please correct me
I created a blank file and wrote inside it:
insmod /system/lib/modules/multitouchfix.ko (I replaced the name)
And saved the file as 99multitouchfix inside /system/etc/init.d/
I also fixed permissions for both files
Sent from my A953
Is it working Aragorn?
Thank you. I'll try it when I get home!
inheme said:
Is it working Aragorn?
Click to expand...
Click to collapse
Nope. The module works, but not the init.d script
you can use autostart from Market
AragornPE said:
Nope. The module works, but not the init.d script
Click to expand...
Click to collapse
Try this script:
Code:
#!/system/bin/sh
# Load 5 finger multitouch module
insmod /system/lib/modules/defy_more.ko
Also note that the first touch after reboot is delayed.
dangpzanco said:
Try this script:
Code:
#!/system/bin/sh
# Load 5 finger multitouch module
insmod /system/lib/modules/defy_more.ko
Also note that the first touch after reboot is delayed.
Click to expand...
Click to collapse
I'll try that as soon as my M2 wakes up, long day for it today =P
Actually,the patch is developed by korean , the XDA thread is http://forum.xda-developers.com/showthread.php?t=1162327
Autoload after reboot: copy install-recovery.sh to /system/etc and set rwxr-xr-x .
If you wanna change the touch point limit , open install-recovery.sh with text editor , change the number that follows "touch_num=". The range is 1~10.
My own test shows more than 6 touch points will NOT lead to system crash , but make it back to 2 points...orz. Since the same patch on D2/D2G/DEFY enable up to 10 points, why
m2 cound not
Ah, forgot to say , the autoload patch is ported from http://bbs.gfan.com/android-1997547-1-1.html
Neither autostart or init.d script worked. Going to try the install recovery
Sent from my A953
Install recovery didn't work either
Maybe I'm doing something wrong?
Sent from my A953
AragornPE said:
Neither autostart or init.d script worked. Going to try the install recovery
Sent from my A953
Click to expand...
Click to collapse
Did you set the permission properly，both milestone2_more.ko and install.sh.
All works fine, both the milestone2_more.ko and the install recovery, no problem at all, have 4 MT points now
Hi all. If anyone is willing to help please assist me, im currently trying to upload cm 7 Morrison files for our beloved Ruth devices. I still haven't figured out how the 2nd init injector works yet.
For all charm users we can always branch the files and delete the MOTO.ROTATOR line for your devices.
If you have time, patients and sh¡t loads of guts please help or add links for me to checkout.
EVEYTHING IS APPRECIATED! :fistbump:
DEV Device: MB511 (deodexed)
Current System: MT27i xICS
Long Live: V9 Ferrari Rom
code.google.com/p/motorola-flipout-files
Ok if anyone know of any other motorola developers please let me know.
DEV Device: MB511 (deodexed)
Current System: MT27i xICS
Long Live: V9 Ferrari Rom
code.google.com/p/motorola-flipout-files
ruth(MB511) sensors in init.mapphone30_umts.rc
# sensor interface
chown compass compass /dev/lis331dlh --> not found
chmod 660 /dev/lis331dlh
chown compass compass /dev/kxtf9 --> found
chmod 660 /dev/kxtf9
chown compass compass /dev/akm8973 --> not found
chmod 660 /dev/akm8973
chown compass compass /dev/sfh7743 --> found
chmod 660 /dev/sfh7743
chown compass compass /dev/akm8973_dev --> found
chmod 660 /dev/akm8973_dev
chown compass compass /dev/akm8973_aot --> found
chmod 660 /dev/akm8973_aot
chown compass compass /dev/airc --> not found
chmod 660 /dev/airc
so ruth(MB511) sensors should be /dev/kxtf9, /dev/sfh7743,/dev/akm8973_dev, /dev/akm8973_aot
but Morrison sensors in libsensors/nusensors.h
#define AKM_DEVICE_NAME "/dev/akm8973_aot"
#define ACCEL_MODE_NAME "/sys/class/i2c-adapter/i2c-0/0-0018/mode"
#define CM_DEVICE_NAME "/dev/proximity"
#define LS_DEVICE_NAME "/dev"
#define LIS_DEVICE_NAME "/dev/lis331dlh"
I think porting Morrison maybe less suitable for ruth
Thanks phc, and yes I know its a long shot, I still haven't gotten to the lib files, let alone hardware. But morrison IS the closest port for us. All the other devices are to advanced for the device. Do a compare between the two, ram is almost identical, chips are close, gpu aswell. Only thing that isnt is screen size. Thanks for the lost, it will come in handy later.
DEV Device: MB511 (deodexed)
Current System: MT27i xICS
Long Live: V9 Ferrari Rom
code.google.com/p/motorola-flipout-files
Hi,
I used jordan-common and MagicDevTeam's MB508([h t t p s : / / github.com/MagicDevTeam) files,
and compiled eclair AOSP to check different files than create ruth device files.
My ROM VERSION:
RUTEM_U3_01.14.16_DEBLUR_SIGNED_USARUTH15ND0RTINT056.0R_PDS000_USARUTHEHKTWEMARA_P011_A010_HWp3_1FF.sbf
My ruth configure files: ruthconfigureforcm7.zip(h t t p s : / / docs.google.com/file/d/0BxgqJrVwRKJqQUlWTWI3SURGU1U/edit)
https://github.com/phchshow/android_device_motorola_ruth
My unstable update file:v0.1.5.zip(h t t p s : / / docs.google.com/file/d/0BxgqJrVwRKJqaXNzRVJDSU95Slk/edit)
V0.5.0.zip
can work:
battd[2013/03/14]
bluetooth
half work:
audio->media codec can't use.
[2013/03/19]solved some media codec running problem, but video recorder codec still has problem (even use low quality).
[2013/03/23]only mp3 and jpg codec is ok, orthers codec has problem, unknow how to solved...
sensors.
fmradio->FMRadioService.apk can't use, but can purchase "Spirit FM Radio Unlocked" to use.[2013/03/15]
camera->[2013/03/18]replace to use MB508's libcamera.so and libcameraservice.so. can take a picture, but media codec has some problem, so can't photograph.
wifi->[2013/03/23]dhcp has problem, but use command to execute is ok.
use mb508's bootmenu/2nd-init/init, solve setprop question, now wifi is OK.
but no softap beacuse can't compile tiap_drv.ko with 2.6.29 kernel.
ril->[2013/03/25]can call, but no sound, seems like audio codec problem.
not work:
battd->log say INIT BATTD SOCKET SERVER: failed. unknow how to solve. update[2013/03/14]:chmod cpcap permission
camera->used mb508's camera library, log say "mapped at 0x4103c000, not at 0xa7900000" can not load library
used ruth camera library, log say CAMERA HAL not support. unknow how to solve.
radio. unknow how to solve.
wifi->when process step 2, /system/bin/wlan_loader -f /system/etc/wifi/fw_wlan1271.bin -i /system/etc/wifi/tiwlan.ini -e /pds/wifi/nvs_map.bin
failed. [2013/03/16]get new question Failed to start supplicant daemon.unknow to solve.
[2013/03/23]gps->Failed to enable location provider
forget test:
fmradio, gps
phchshow said:
Hi,
I used jordan-common and MagicDevTeam's MB508([h t t p s : / / github.com/MagicDevTeam) files,
and compiled eclair AOSP to check different files than create ruth device files.
My ROM VERSION:
RUTEM_U3_01.14.16_DEBLUR_SIGNED_USARUTH15ND0RTINT056.0R_PDS000_USARUTHEHKTWEMARA_P011_A010_HWp3_1FF.sbf
My ruth configure files: ruthconfigureforcm7.zip(h t t p s : / / docs.google.com/file/d/0BxgqJrVwRKJqQUlWTWI3SURGU1U/edit)
My unstable update file:v0.1.5.zip(h t t p s : / / docs.google.com/file/d/0BxgqJrVwRKJqaXNzRVJDSU95Slk/edit)
can work:bluetooth
halt work:
audio->media codes can't use.
sensors.
not work:
battd->log say INIT BATTD SOCKET SERVER: failed. unknow how to solve.
camera->used mb508's camera library, log say "mapped at 0x4103c000, not at 0xa7900000" can not load library
used ruth camera library, log say CAMERA HAL not support. unknow how to solve.
radio. unknow how to solve.
wifi->when process step 2, /system/bin/wlan_loader -f /system/etc/wifi/fw_wlan1271.bin -i /system/etc/wifi/tiwlan.ini -e /pds/wifi/nvs_map.bin
failed. unknow to solve.
forget test:
fmradio, gps
Click to expand...
Click to collapse
How are you flashing the update.zip files, my phone doesnt seem to respond to any of the changes.
hsr0 said:
How are you flashing the update.zip files, my phone doesnt seem to respond to any of the changes.
Click to expand...
Click to collapse
you can use charm Big Bootstrapped Recovery Update to update.
or use bootmenu to update.
update:
if you want use bootmenu,
you can unzip my update zip (v0.1.5.zip).
WARNING: if step fails, may be need reinstall the system. BE CAREFUL.
1. remount system (root)
mount -o remount,rw / /system
2. push bootmenu files
adb push v0.1.5/system/bin/bootmenu /system/bin/
adb push v0.1.5/system/bootmenu /system/bootmenu
3. chmod files permisson (root)
chmod 0755 /system/bin/bootmenu
chmod 0755 /system/bootmenu/binary/*
chmod 0755 /system/bootmenu/script/*
chmod 0755 /system/bootmenu/recovery/sbin/*
4. change mot_boot_mode(original motorola file) (root)
mv /system/bin/mot_boot_mode /system/bin/mot_boot_mode.bin
5. edit mot_boot_mode (root) update(2013/02/08)
/system/bootmenu/binary/busybox vi /system/bin/mot_boot_mode
#!/system/bin/sh
export PATH=/system/bin:$PATH
/system/bin/bootmenu
mot_boot_mode.bin
6. chmod mot_boot_mode permission (root)
chmod 0755 /system/bin/mot_boot_mode
7. reboot and click click click(loop) "vol down" key until show bootmenu screen
Can you post just the bootmenu files?
I have already tried your steps twice but soft bricked the phone.
hsr0 said:
Can you post just the bootmenu files?
I have already tried your steps twice but soft bricked the phone.
Click to expand...
Click to collapse
OK. I re-installed system. And write script name mkbootmenu.sh
unzip bootmenuDIR.zip
adb push bootmenuDIR/bootmenu /sdcard/bootmenu
adb push bootmenuDIR/mkbootmenu.sh /sdcard
in phone side:
$su
#sh /sdcard/mkbootmenu.sh
#reboot
when MOTO LOGO click click click (loop) "VOL - " (VOL DOWN) until show bootmenu screen
NOTICE: only new system or never changed mot_boot_mode can run this script .
thank you very much, it worked!
However I still do not know why it did not run when I executed it although I did a fresh install with RSD lite.
Maybe because I used windows to create mot_boot_mode file, maybe some character issues occured.
but once again thank you!
Will check it in the morning, so far i've modded most of the make files for CM9 and my only worry is the framework.apk but so far so good :thumbup:
Almost forgot! The 2nd init and a modified boot kernel will be the biggest problems.
DEV Device: MB511 (deodexed)
Current System: MT27i xICS
Long Live: V9 Ferrari Rom
code.google.com/p/motorola-flipout-files
https://github.com/plageran/ruth
Good job, man
My Flipout is waiting for a stable CM
ruth device cpu and gpu
As far as I know, flipout and charm have OMAP 3410 CPU inside, this CPU DOESN'T include GPU. Others like OMAP 3430 in Milestone 1 does include Imagination PowerVR SGX535 GPU.
Please check this location on your device with a root explorer app:
/system/lib/egl/
and in there you will find your gpu drivers, also most phones do have gpu's although it only helps the device a little bit.
I know my device has atleast 3 .so files in there and I think thats android drivers. I must just figure out if it should be recompiled for newer versions of android.
xinbada007 said:
As far as I know, flipout and charm have OMAP 3410 CPU inside, this CPU DOESN'T include GPU. Others like OMAP 3430 in Milestone 1 does include Imagination PowerVR SGX535 GPU.
Click to expand...
Click to collapse
Hijack
How did you manage to get the hijack working? I've been struggling my butt off to get the 2nd-init working:highfive:
phchshow said:
you can use charm Big Bootstrapped Recovery Update to update.
or use bootmenu to update.
update:
if you want use bootmenu,
you can unzip my update zip (v0.1.5.zip).
WARNING: if step fails, may be need reinstall the system. BE CAREFUL.
1. remount system (root)
mount -o remount,rw / /system
2. push bootmenu files
adb push v0.1.5/system/bin/bootmenu /system/bin/
adb push v0.1.5/system/bootmenu /system/bootmenu
3. chmod files permisson (root)
chmod 0755 /system/bin/bootmenu
chmod 0755 /system/bootmenu/binary/*
chmod 0755 /system/bootmenu/script/*
chmod 0755 /system/bootmenu/recovery/sbin/*
4. change mot_boot_mode(original motorola file) (root)
mv /system/bin/mot_boot_mode /system/bin/mot_boot_mode.bin
"5. edit mot_boot_mode (root)
vi /system/bin/mot_boot_mode "
#!/system/bin/sh
export PATH=/system/bin:$PATH
/system/bin/bootmenu
mot_boot_mode.bin
6. chmod mot_boot_mode permission (root)
chmod 0755 /system/bin/mot_boot_mode
7. reboot and click click click(loop) "vol down" key until show bootmenu screen
Click to expand...
Click to collapse
plageran said:
How did you manage to get the hijack working? I've been struggling my butt off to get the 2nd-init working:highfive:
Click to expand...
Click to collapse
He basically rewrote the boot script, so while booting up, it opens the bootmenu script and only then does it do a regular boot..
The normal 2nd init installer don't invoke the boot script in the same way I guess and hence it doesn't work.
Well now since bootmenu works, its like a torchlight in an otherwise dark tunnel.
Another point I want to make is that the flipout cm7 update given is in a bootloop. probably I need to change the files for basil (charm).
I think bootloop is audio device (libaudio.so) error. Maybe like when I use MB508's libcamera.so the message log show "mapped at .... " can't load library.
So should be use charm's libaudio.so to recompile CM7 sources. But maybe make some error, like media codec can't use.
hsr0 said:
He basically rewrote the boot script, so while booting up, it opens the bootmenu script and only then does it do a regular boot..
The normal 2nd init installer don't invoke the boot script in the same way I guess and hence it doesn't work.
Well now since bootmenu works, its like a torchlight in an otherwise dark tunnel.
Another point I want to make is that the flipout cm7 update given is in a bootloop. probably I need to change the files for basil (charm).
Click to expand...
Click to collapse
---------- Post added at 10:55 PM ---------- Previous post was at 10:34 PM ----------
The 5 step should be
"/system/bootmenu/binary/busybox vi /system/bin/mot_boot_mode", I forgot no install busybox no vi.
Defy use logwrapper to hijack, but flipout can't.
I think flipout processed init have not execute logwrapper, let we can't hijack logwrapper.
But mot_boot_mode executed.
So I rename mot_boot_mode to mot_boot_mode.bin and write new script name mot_boot_mode. Make bootmenu can execute.
And modify init.mapphone30_umts.rc
"exec /system/bin/mot_boot_mode" to "exec /system/bin/mot_boot_mode.bin", make 2nd-init can success execute init files.
In My uploaded bootmenuDIR.zip, the 2nd-init directory is modify for eclair to use.
You can modify eclair init files to test 2ndinit.
plageran said:
How did you manage to get the hijack working? I've been struggling my butt off to get the 2nd-init working:highfive:
Click to expand...
Click to collapse
What I've learned so far is that most motorola's have the hijacked kernel from the original device, I'm not sure up to what level of Android os this works but if you dig deep enough. Its all almost the same to stock.
I hope you don't mind me using your scripts for my rom, this changed things big time.
Now to get my build machine up and running and to finish my LIB list for CM
edit: has anyone figured out the fingerprint system yet? I haven't found anything about it yet, whether it's generated or copied over.
phchshow said:
I think bootloop is audio device (libaudio.so) error. Maybe like when I use MB508's libcamera.so the message log show "mapped at .... " can't load library.
So should be use charm's libaudio.so to recompile CM7 sources. But maybe make some error, like media codec can't use.
---------- Post added at 10:55 PM ---------- Previous post was at 10:34 PM ----------
The 5 step should be
"/system/bootmenu/binary/busybox vi /system/bin/mot_boot_mode", I forgot no install busybox no vi.
Defy use logwrapper to hijack, but flipout can't.
I think flipout processed init have not execute logwrapper, let we can't hijack logwrapper.
But mot_boot_mode executed.
So I rename mot_boot_mode to mot_boot_mode.bin and write new script name mot_boot_mode. Make bootmenu can execute.
And modify init.mapphone30_umts.rc
"exec /system/bin/mot_boot_mode" to "exec /system/bin/mot_boot_mode.bin", make 2nd-init can success execute init files.
In My uploaded bootmenuDIR.zip, the 2nd-init directory is modify for eclair to use.
You can modify eclair init files to test 2ndinit.
Click to expand...
Click to collapse
hey dude, r you guys still working on flip/charm? any progress to share?
xinbada007 said:
hey dude, r you guys still working on flip/charm? any progress to share?
Click to expand...
Click to collapse
keep an eye on our github pages, i can only update monthly due to cost's. Still need to get and build my build machine lol!
What is init.d ?
Init.d is a feature which allows you to run brunch of scripts at boot . Thats really useful while you want to set values which reset at boot or run/do any thing at every boot or install tweaks , engines and....
There are some ways to add this feature to you rom but always best way is to add init.d support directly by your kernel . I want to help you to do this
Requirements
1- Ability to unpack boot.img & ramdisk
2- Some basic linux shell knowloedge
3- Having Busybox located in /system/bin/busybox at your rom
Step 1: Making kernel ready
1- Unpack kernel then ramdisk
2- Open Init.rc with a text editor
3- Add this codes at the end , before the paragraph which there is "stop bootanim" command in it :
Code:
service sysinit /system/bin/sysinit
oneshot
4- Save , Exit and repack ramdisk and boot.img
Step 2 : Making Rom Ready !
1- Open /system/bin/sysinit
2- Add this codes :
Code:
#!/system/bin/sh
export PATH=${PATH}:/system/bin:/system/xbin
chmod 777 /system/etc/init.d/*
logwrapper busybox run-parts /system/etc/init.d/
3- Set permissions of sysinit to 777 or 755 ( rwxrwxr-x | rwxrwxrwx )
4- Make a directory at system/etc and name it init.d
Now you have init.d support !
Reserved for future changes !
Pls tell me about this '' init'' on my supersu dialog box...
It's my first time to see this and I don't know what is this for?
Is this harmful? Or very important not to loose it...
Educate me... I really don't know what is is for...
... What? why? how?
Thanks much!
Sent from my GT-I9300 using XDA Premium HD app
'' Init '' or '' init.d''
Pls differentiate....
What is this for?
Sent from my GT-I9300 using XDA Premium HD app
leio rusher said:
'' Init '' or '' init.d''
Pls differentiate....
What is this for?
Sent from my GT-I9300 using XDA Premium HD app
Click to expand...
Click to collapse
leio rusher said:
Pls tell me about this '' init'' on my supersu dialog box...
It's my first time to see this and I don't know what is this for?
Is this harmful? Or very important not to loose it...
Educate me... I really don't know what is is for...
... What? why? how?
Thanks much!
Sent from my GT-I9300 using XDA Premium HD app
Click to expand...
Click to collapse
Read in the op what is init.d section...
Inviato dal mio GT-I9070 con Tapatalk 2