Related
Can someone be so kind as to tell me how I edit the file to enable Compache?
Here is the code on the compache.sh file:
Code:
#/system/xbin/insmod /system/lib/modules/lzo_decompress.ko
#/system/xbin/insmod /system/lib/modules/lzo_compress.ko
#/system/xbin/insmod /system/lib/modules/xvmalloc.ko
#/system/xbin/insmod /system/lib/modules/ramzswap.ko disksize_kb=131072
#/system/xbin/swapon /dev/block/ramzswap0
#echo "10" > /proc/sys/vm/swappiness
Also, do I need to repartition my SD card in order for it to work?
Thanks!
Edit:
Would just commenting the lines suffice? Or is that different for linux code? Not used to it >.>;
Edit #2:
Damn, just found the guide for enabling compache. I'll try to delete the thread... or a mod can do it please!
Thanks!
I managed to get init.d working on the EE03 leak but it broke logcat, I switched to the no-op scheduler and it seems to be quite a bit more responsive =p
I wish I could post how I did it but xda thinks a file path is an outside link and wont let me submit it...
Is this useful at all? I don't know much about android but I'm a linux nerd by profession
chairface said:
I managed to get init.d working on the EE03 leak but it broke logcat, I switched to the no-op scheduler and it seems to be quite a bit more responsive =p
I wish I could post how I did it but xda thinks a file path is an outside link and wont let me submit it...
Is this useful at all? I don't know much about android but I'm a linux nerd by profession
Click to expand...
Click to collapse
Makes sense that noop i/o would be more responsive as it's designed for flash memory devices. Init.d is supported by default in cm7 and it's always handy to have it around for keeping things out of the original init.<device>.rc without having to recompile initramfs.
All you need is 10 posts and you'll be able to post whatever you need.
You can also use the 'CODE' tags to paste paths, etc.
init.d was enabled via the initramfs in the kernel. Scrips go in /system/etc/init.d - and have on every ROM with initscripts enabled.
Thanks for the tip on the scheduler - feel free to play around with the other settings. Have a look at the tweaks thread for some possibilities.
k0nane said:
init.d was enabled via the initramfs in the kernel. Scrips go in /system/etc/init.d - and have on every ROM with initscripts enabled.
Thanks for the tip on the scheduler - feel free to play around with the other settings. Have a look at the tweaks thread for some possibilities.
Click to expand...
Click to collapse
/system/bin/sh can't parse if [ <x> ] statements...
the block in twilightzone.sh that says
<code>
if [ -d /etc/init.d ]
then
run-parts /etc/init.d
fi
</code>
should be changed to
<code>
/sbin/busybox [ -d /etc/init.d ] && /sbin/busybox run-parts /etc/init.d
</code>
thanks for all your hard work man
also the updater-script has to set everything in /etc/init.d to 755 - it doesn't in ee03
I wasn't aware init.d support was there until after I wrote the script.
oh haha
I changed /system/bin/sh to point to busybox... the only thing it seems to break is logcat =\
before I did this nothing in /etc/init.d worked, if I did
/sbin/twilightzone.sh
it wouldn't run /etc/init.d but if I did busybox sh /sbin/twilightzone.sh it did
I probably broke a lot of other stuff doing this too but it's working well so far.
while I have someone knowledgeable here, is it possible to extract/repack the zImage? I'm assuming either ACS did that or used an older 2.2 kernel
ICS's VPN doesn't work on my U8800. Is it a bug that hasn't been fixed on Aurora ICS? Anybody has the same problem? Is there a solution for it?
VPN in U8800 Aurora does not work
dmzsdx said:
ICS's VPN doesn't work on my U8800. Is it a bug that hasn't been fixed on Aurora ICS? Anybody has the same problem? Is there a solution for it?
Click to expand...
Click to collapse
I have the same problem. Test Aurora 1.12a, 2.02 and 2.04. I allways do all wipes (cache, data, dalvik). PPTP VPN does not work for mee.
Same here, That renders Onavo Extend unusable. From what i gathered so far, it seems to be a kernel issue and not a rom issue. As users from all kinds of phones report the same behaviour on their ICS roms and so far the only way around is a proper kernel.
ArbiterGR said:
Same here, That renders Onavo Extend unusable. From what i gathered so far, it seems to be a kernel issue and not a rom issue. As users from all kinds of phones report the same behaviour on their ICS roms and so far the only way around is a proper kernel.
Click to expand...
Click to collapse
What about Openvpn?
try kernel 3.08.
flesh it,and try again.for 10....
Try with the new kernel for ics, you can find it on my signature.
Regards
Sent from my U8800 using xda premium
Solution of PPTP VPN problem on custom ICS ROMs
I use Aurora 2.11a now. I have two major problems:
- PPTP VPN not works
- SIP VoIP (only Linphone Video works, but quality not good, other program eg CSipSimple does not work - make/receive calls but voice is not transfered)
I found why PPTP VPN does not work.
I use logcat and found that mtpd can't create PPPoX socket. I found many people has this problem with ICS custom ROMs.
This problem is caused by missing protocol support in kernel.
I compiled and loaded kernel modules (load in terminal by insmod). PPTP VPN connects now withou problems.
Needed kernel modules:
insmod slhc.ko
insmod ppp_generic.ko
insmod pppox.ko
insmod pppopns.ko
I made test without encryption. I suppose that for encrypted PPTP connection more modules will be needed. Eg ppp_mppe.ko for MPPE encryption or ppp_deflate.ko for deflate compression. I will make some tests later.
I suggest add needed modules (with auto modprobe support) to the rom. But I can't put results of my tests to developer posts. I have not made 10 helpful posts.
Please send my solution to DZO.
More tests PPTP VPN in Aurora 2.11a (ICS ROM)
I made more tests:
1. And confirm that for connection to Linux poptop PPTP server (via WiFI) without compression and ancryption this kernel modules are needed: slhc.ko, ppp_generic.ko, pppox.ko, pppopns.ko
2. I also succesfully connect to Microsoft ISA server with MPPE encryption activated. As I suppose in previous post, in this case ppp_mppe.ko module is needed too.
I use mobile phone for work. Not working connection to company ISA VPN PPTP server was major problem for me in Aurora. Now I can connect. Wow. (I have only one big problem with Aurora now - SIP VoIP.)
I did not test PPTP with deflate and bsd compressions (I suppose ppp_deflate.ko and bsd_comp.ko will be needed). I also not tested l2tp and ipsec configurations. (I don't have prepared VPN servers for this.)
There is two ways now. Staticaly compile all code to the kernel or compile kernel modules.
I prefer to add kernel modules to rom. And this modules will be loaded to RAM automaticaly when user needs it (user use VPN, eg as wlan driver module is loaded only when WiFI is used).
DZO, please can you add this to Aurora ROM.
Tests deflate and BSD compression in PPTP VPN in Aurora 2.11a (ICS ROM)
I changed configuration of my Linux poptop PPTP server and test deflate and BSD compresion. Both is working with Aurora ROM. This additional modules are needed ppp_deflate.ko and bsd_comp.ko for this.
I still not tested l2tp and ipsec configurations. (I don't have prepared VPN servers for this.)
Autoloading kernel modules
>There is two ways now. Staticaly compile all code to the kernel or compile kernel modules.
>I prefer to add kernel modules to rom. And this modules will be loaded to RAM automaticaly when user needs it (user use VPN, eg as wlan driver module is loaded only when WiFI is used).
Kernel can load modules automaticaly. Kernel calls "modprobe" for this. But in Aurora and probably in other roms is not corectly configured path to "modprobe" in kernel.
In Aurora kernel is default path "/sbin/modprobe". But "/system/xbin/modprobe" is right.
If you set correct path to "modprobe" in kernel than modules ppp_mppe.ko, ppp_deflate.ko, bsd_comp.ko will be automaticaly loaded to ram when needed. (You have to copy this modules to /system/lib/modules ofcourse). No need to compile thist code staticaly to kernel.
Set correct path to modprobe may be done in startup scripts by:
echo /system/xbin/modprobe > /proc/sys/kernel/modprobe
JaRo1 said:
>There is two ways now. Staticaly compile all code to the kernel or compile kernel modules.
>I prefer to add kernel modules to rom. And this modules will be loaded to RAM automaticaly when user needs it (user use VPN, eg as wlan driver module is loaded only when WiFI is used).
Kernel can load modules automaticaly. Kernel calls "modprobe" for this. But in Aurora and probably in other roms is not corectly configured path to "modprobe" in kernel.
In Aurora kernel is default path "/sbin/modprobe". But "/system/xbin/modprobe" is right.
If you set correct path to "modprobe" in kernel than modules ppp_mppe.ko, ppp_deflate.ko, bsd_comp.ko will be automaticaly loaded to ram when needed. (You have to copy this modules to /system/lib/modules ofcourse). No need to compile thist code staticaly to kernel.
Set correct path to modprobe may be done in startup scripts by:
echo /system/xbin/modprobe > /proc/sys/kernel/modprobe
Click to expand...
Click to collapse
You should let DZO know about this
Strange, all those modules are built into the kernel already:
Code:
[email protected]:/proc # gzip -d < config.gz | grep PPP
CONFIG_PPP=y
CONFIG_PPP_MULTILINK=y
CONFIG_PPP_FILTER=y
CONFIG_PPP_ASYNC=y
CONFIG_PPP_SYNC_TTY=y
CONFIG_PPP_DEFLATE=y
CONFIG_PPP_BSDCOMP=y
CONFIG_PPP_MPPE=y
CONFIG_PPPOE=y
CONFIG_PPPOLAC=y
CONFIG_PPPOPNS=y
[email protected]:/proc # gzip -d < config.gz | grep BSD
# CONFIG_BSD_PROCESS_ACCT is not set
CONFIG_PPP_BSDCOMP=y
# CONFIG_BSD_DISKLABEL is not set
[email protected]:/proc # gzip -d < config.gz | grep SLHC
CONFIG_SLHC=y
[email protected]:/proc #
I wonder why they aren't being used. I'll look into it.
dzo said:
Strange, all those modules are built into the kernel already:
Code:
[email protected]:/proc # gzip -d < config.gz | grep PPP
CONFIG_PPP=y
CONFIG_PPP_MULTILINK=y
CONFIG_PPP_FILTER=y
CONFIG_PPP_ASYNC=y
CONFIG_PPP_SYNC_TTY=y
CONFIG_PPP_DEFLATE=y
CONFIG_PPP_BSDCOMP=y
CONFIG_PPP_MPPE=y
CONFIG_PPPOE=y
CONFIG_PPPOLAC=y
CONFIG_PPPOPNS=y
[email protected]:/proc # gzip -d < config.gz | grep BSD
# CONFIG_BSD_PROCESS_ACCT is not set
CONFIG_PPP_BSDCOMP=y
# CONFIG_BSD_DISKLABEL is not set
[email protected]:/proc # gzip -d < config.gz | grep SLHC
CONFIG_SLHC=y
[email protected]:/proc #
I wonder why they aren't being used. I'll look into it.
Click to expand...
Click to collapse
yay! my hero !
dzo said:
Strange, all those modules are built into the kernel already:
Code:
[email protected]:/proc # gzip -d < config.gz | grep PPP
CONFIG_PPP=y
CONFIG_PPP_MULTILINK=y
CONFIG_PPP_FILTER=y
CONFIG_PPP_ASYNC=y
CONFIG_PPP_SYNC_TTY=y
CONFIG_PPP_DEFLATE=y
CONFIG_PPP_BSDCOMP=y
CONFIG_PPP_MPPE=y
CONFIG_PPPOE=y
CONFIG_PPPOLAC=y
CONFIG_PPPOPNS=y
[email protected]:/proc # gzip -d < config.gz | grep BSD
# CONFIG_BSD_PROCESS_ACCT is not set
CONFIG_PPP_BSDCOMP=y
# CONFIG_BSD_DISKLABEL is not set
[email protected]:/proc # gzip -d < config.gz | grep SLHC
CONFIG_SLHC=y
[email protected]:/proc #
I wonder why they aren't being used. I'll look into it.
Click to expand...
Click to collapse
Hello DZO.
Yes I see. After my post "http://forum.xda-developers.com/showpost.php?p=25872580&postcount=7" you staticaly build needed modules to kernel. Thank you.
I never wrote that staticaly linked modules are not used. I didn't test your kernel with staticaly linked modules. But this is one solution. This is simple solution. All code compile staticaly and create one superbig kernel with all drivers compiled in.
I prefer another solution. Create smaller kernel and many modules with working autoloading. If user use pptp then modules will be automaticaly loaded to ram. If user don't use pptp than modules are not loaded to ram. The same we can do with tun/tap driver - create module tun.ko. (Is staticaly linked now.)
I am working on second solution. I am using your older binary kernel (without staticaly linked modules for PPTP VPN). And I compiled needed modules from your kernel sources (from git). And made tests.
Now I have working kernel modules autoloading. If user use PPTP then kernel automaticaly loads all needed modules.
I made this:
1. I added to directory "/system/lib/modules" needed modules:
bsd_comp.ko, ppp_deflate.ko, ppp_generic.ko, ppp_mppe.ko, pppopns.ko, pppox.ko, slhc.ko
2. I Set correct path to modprobe in kernel:
echo /system/xbin/modprobe > /proc/sys/kernel/modprobe
3. I generate files with information about modules and copy to directory "/system/lib/modules":
modules.alias, modules.dep, modules.dep.bb, modules.symbols
I don't know which solution is better for Aurora ROM.
- Compile one big kernel with all code is simple and does not depend on modprobe (autoloading modules support) functionality. May be more reliable solution.
- Compile code as modules probably has advantage for users who don't use this code (eg do not use VPN). Probably in this case kernel use less RAM. But I don't compare this two solutions (kernel whith staticaly linken code and without). So I don't have concrete numbers.
For DZO:
I attached archive with files (modules and info). May be helpful for you. May be not. Its on you what solution you choose. Please add to starting script this in anycase: echo /system/xbin/modprobe > /proc/sys/kernel/modprobe
Once again I thank you for your work.
hi,
Can you explain the procedure how to load with insmod file ppp_mppe.ko in to my device. I copied in the folder /system/lib/modules/ file ppp_mppe.ko that you sent. I get the message "Exec format error" when trying to load command: insmod /system/lib/modules/ppp_mppe.ko in terminal. My device is a Samsung GT-P5100 with ICS 4.0.4
Dzo,
Have you made any progress with this one? Just wondering if there is a solution for us?
Thanks for the time and effort!!
so did you get PPTP vpn working?
with ample googling this thread seems to be closest to having a working PPTP vpn.
(other than a german thread from 2010: http://www.android-hilfe.de/motorola-milestone/20823-endlich-pptp-vpn-root.html
i'm on cm7.2 - in dire need of working PPTP - it seems that this is an android-wide problem, though i did have it working on my previous phone, also on cm7.2.
so where are we with this? and if loading add'l modules gets it working, could you please hold my hand a bit through the process - i'm a noob and it seems a bit complicated this stuff here.
JaRo1 said:
2. I Set correct path to modprobe in kernel:
echo /system/xbin/modprobe > /proc/sys/kernel/modprobe
Click to expand...
Click to collapse
Sorry ı've same promblem and ı need help. I cant understand second step.please exlplain it me?
I wait your help.
Hello everybody,
I thought that ICS was a little bit slow on my SGS+ so I tried to tweak it.
This is when I came across the option compcache in the settings -> performance menu.
Only I found this option isn't w orking yet in arco's alpha 3 build, or isn't working anymore.
Either way I found out that zram0 is present on the device, so I created a little script with which you can set-up Zram.
Just put it somewhere you can browse to with Terminal Emulator.
Also make sure it's permissions are set to rwx-r-x-r-x.
After you set the permissions right, just execute with: ./zram start
Or if you want to stop the swapping again just give in ./zram stop
This is the code for the script:
#!/system/bin/sh
#
# Zram manager
# koudumrulez{at}gmail.com (PsychoGame)
case "$1" in
start)
echo 3 > /proc/sys/vm/drop_caches
echo 30 > /proc/sys/vm/swappiness
# get the amount of memory in the machine
mem_total_kb=$(grep MemTotal /proc/meminfo | grep -E -o '[[:digit:]]+')
mem_total=$((0,25 * mem_total_kb * 1024))
# initialize the devices
echo $((mem_total)) > /sys/block/zram0/disksize
# Creating swap filesystem
mkswap /dev/block/zram0
# Switch the swap on
swapon /dev/block/zram0
;;
stop)
# Switching off swap
swapoff /dev/block/zram0
;;
*)
echo "Usage: $0 {start|stop}"
esac
exit 0
You can just call the file zram, and then copy it on you're device for example you're SD.
I only used this script on ALPHA3 build. Maybe it works on others as well, but that's at you're own responsibility.
Greetings Psycho Game
Here I'am again.
There's been a little error from my side.
If you put this file on you're SD-Card you can't set the permissions right.
What I did was putting the file in /system/bin, so the full path would be /system/bin/zram.
I did this with ES File Manager, but you're free to use whatever file manager you like.
After this make sure the permissions are set to rwx-r-x-r-x in the file manager, or in the terminal you can do a "chmod 755 /system/bin/zram" without quotes.
The zram is now useable through executing the command: "/system/bin/zram start or stop".
You can also choose to mount the zram automatically with booting.
In this case you have to make a file called userinit.sh in the folder "/data/local/"
This file needs the following content:
#!/system/bin/sh
/system/bin/zram start
I also set the permissions of this file to 755 with "chmod 755 /data/local/userinit.sh" but I'm not sure if this is neccesary. Anyway it works.
Hopefully somebody can use this script as well. If you do, please leave a comment. Also if you have questions feel free to ask. I will keep an eye on this post.
And the question if this will work on Alpha 4, yes it does.
Greetings,
Psycho Game
Hi Psycho,
thanks for your effort.
I also saw that zRam is indeed not working on the latest Alpha 6 (i use the Galxy W / i8150 Build).
I had a look at your script and some other sources and enabled zRam on my deivce for testing purposes.
My conclucsion so far is, that there seems so be some major problem of interference with an other memory management policy.
Independent from the Size and Swapiness configuration - there is something going wrong hier i think
I watched the systems memory stats through proc/meminfo and free. Once the system is out of fresh memory, it begins swapping. zRam swap then getfs filled up quickly. Now the system gets extremely slow, i also had two restarts (likely in cause of some kernel panics from acute memory problems).
Will be difficult to track down the problem, my guessings so far:
- Interference with LMK, as it only indirectly knows about zRam
- Some kind of io block size might have been set to a bad value for the zram device
- CPU-load through compression simply much to high (unlikely, but have not checked it yet)
.. and plenty other possibilites
ATM, its definitely only a huge decrease in performance for me. What was your experience?
From the technical specs, i guess zRam should behave much better, so i really guess theres going something wrong.
Guess i found a possible reason for the bad performance.
I will write more details when i have the time to.
Just tried the above script on CM9 (build 0814) for Galaxy Exhibit 4G (a sister phone of Galaxy W as I understand it). I ran the script in the Terminal. Initially the performance became very bad after a period of time (especially after opened many apps). It almost looked like zRam made it worse once it got used for some storage amount. However, after I changed mem_total_kb from MemTotal to MemFree, and removed 0,15 for mem_total, the horrible slow down seemed to disappeared (even after I opened 5 apps at the same time).
any further refinements of this script?
Hello, all!
I have recently built a tool that allows users to more efficiently create and run scripts on boot.
These can be python scripts if you have python installed to your system (No, SL4A won't work. At least, not without some work). Usually though, they are bash or sh scripts.
They can be used to do various things, such as fix permissions every reboot, or things such as record a log of the time of every time you boot up your device, or other cool things.
I am currently looking into getting python packed into a flashable zip (lots of more fun with python scripts like showing a toast notification on boot).
To use bse's scripts executing feature, you must place the script you wish to execute under /system/etc/startup. You don't need to worry about chmodding it, there is an init script that does that already. For reference purposes, I recommend you read the contents of that init script (it's in /system/etc/startup).
To clarify, anyone who wants to build an automated installer for this, distribute some scripts, or distribute any modification to be, you have my full permission as long as you provide a link to this thread.
DOWNLOAD
https://docs.google.com/file/d/0ByulRvn_lJmbbnRfMG82Mm9Pb3c/edit?usp=docslist_api
INSTALLATION
- Just flash the zip file in the recovery of your choice
If you have any questions, feel free to ask. I'm sorry, this was written when I was tired (Not the program, the post)
Sent from my Nexus 7 using Tapatalk
FAQ:
What does "bse" stand for?
If you were to run bse alone, you would see that it stands for "Boot Script Executer".
Is BSE open-sourced?
Almost. I lost the source code and I'm in the process of re-creating it from scratch.
Where is the open source repo?
It's at https://github.com/boot-script-executer. PM me with your Github email if you wish to contribute to BSE development or submit your bse scripts. (please tell me which one)
Sent from my Nexus 7 using Tapatalk
Can we have a github source of all the scripts so we can execute in the Roms and execute it in the android source
nice idea
how about adding in a log wrapper to forward all output to the logcat
note: this is untested, but it should work
Code:
function logger() {
# args:
# $1 = message - the message you want to show
# $2 = priority - optional, defaults to i. the priority you want to give the log message
export LOG="/system/bin/log"
tag="BSE_LOGGER"
message=${1}
priority="i"
if [[ $2 ]]
then
options="vdiwe"
if test "${options#*$2}" == "$options"
then
$LOG -p "e" -t "$tag" "invalid priority level: $2"
else
priority=$2
fi
fi
$LOG -p "$priority" -t "$tag" "$message"
}
examples:
Code:
logger "this is a random message"
# I/BSE_LOGGER(15836): this is a random message
logger "another random message" d
# D/BSE_LOGGER(17393): another random message
logger "this message should give an error" t
# E/BSE_LOGGER(17395): invalid priority level: t
# I/BSE_LOGGER(17396): this message should give an error
This is freaking awesome r3. Good job bro.
*Starts slow clapping. Waiting for other people to join in.* ☺
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
cybojenix said:
nice idea
how about adding in a log wrapper to forward all output to the logcat
note: this is untested, but it should work
Code:
function logger() {
# args:
# $1 = message - the message you want to show
# $2 = priority - optional, defaults to i. the priority you want to give the log message
export LOG="/system/bin/log"
tag="BSE_LOGGER"
message=${1}
priority="i"
if [[ $2 ]]
then
options="vdiwe"
if test "${options#*$2}" == "$options"
then
$LOG -p "e" -t "$tag" "invalid priority level: $2"
else
priority=$2
fi
fi
$LOG -p "$priority" -t "$tag" "$message"
}
Click to expand...
Click to collapse
i like the thought of this!
this is realy cool,great idea and work,thanx man.
Sorry if this sounds like a stupid question, but what's the difference between using init.d and your tool or even using script manager to run scripts at boot?
Sent from my GT-P7500 using Tapatalk
Hehe. Funny story about this. All of its source code (There wasn't too much... Don't worry) was on my trusty (not really) old Kindle Fire HD, which I managed to brick. I will have to re-write the source (Again, I didn't really lose that much) and I'll make everything open-sourced (see 2nd post if you want to help contribute).
cybojenix said:
nice idea ...
Click to expand...
Click to collapse
Thanks... I will try to see if I can implement that. If I have no sucess, you could try for yourself once I get everything re-written.
eushaun99 said:
Sorry if this sounds like a stupid question, but what's the difference between using init.d and your tool or even using script manager to run scripts at boot?
Sent from my GT-P7500 using Tapatalk
Click to expand...
Click to collapse
init.d triggered through the rom not the kernel, and it supports python scripts aswell
ricky310711 said:
init.d triggered through the rom not the kernel, and it supports python scripts aswell
Click to expand...
Click to collapse
Hi
I didn't understand this answer...
This solution also relies on init.d. Apart from python interpreting, what's the thing that makes it more robust aganist init.d scripts?
If a Rom (it's kernel) does not or only via 3rd part apps supports init.d, there could be problems the same.
Publiuss said:
Hi
I didn't understand this answer...
This solution also relies on init.d. Apart from python interpreting, what's the thing that makes it more robust aganist init.d scripts?
If a Rom (it's kernel) does not or only via 3rd part apps supports init.d, there could be problems the same.
Click to expand...
Click to collapse
what do you mean?
this doesnt rely on init.d, it is init.d.
this makes your device run init.d scripts WITHOUT the need to modify the kernel unlike some previous methods... but the scripts are called from /system/etc/startup/
the python script support is a featured currently in progress(from what i read)
ricky310711 said:
what do you mean?
this doesnt rely on init.d, it is init.d.
this makes your device run init.d scripts WITHOUT the need to modify the kernel unlike some previous methods... but the scripts are called from /system/etc/startup/
the python script support is a featured currently in progress(from what i read)
Click to expand...
Click to collapse
It does rely on init.d to call the "bse" binary, but I'm looking for an alternative method.
Sent from my Nexus 7 using Tapatalk
ricky310711 said:
what do you mean?
this doesnt rely on init.d, it is init.d.
this makes your device run init.d scripts WITHOUT the need to modify the kernel unlike some previous methods... but the scripts are called from /system/etc/startup/
the python script support is a featured currently in progress(from what i read)
Click to expand...
Click to collapse
Mhhh...
I'm not so expert, but I saw some metods using /etc/install_recovery.sh to call (another script that calls) run-parts to execute all /etc/init.d scripts, don't know if it's a way to make init.d work despite kernel not supporting it...
This one uses init.d itself to call bse executable so... well if init.d is no way supported it won't work?
Publiuss said:
Mhhh...
I'm not so expert, but I saw some metods using /etc/install_recovery.sh to call (another script that calls) run-parts to execute all /etc/init.d scripts, don't know if it's a way to make init.d work despite kernel not supporting it...
This one uses init.d itself to call bse executable so... well if init.d is no way supported it won't work?
Click to expand...
Click to collapse
justarchi has an init.d method where he calls the scripts from debuggerd!
The link is broken ... can upload? please!
Can anyone give me the download link of this tool