Database Develop

Run custom shell script on boot

Hi XDA Community!
I know some Custom ROMS includes shell scripts that are executed at the boot.
Now, I'm cooking one, already made the script, just searching for a way to autostart it at boot.
I'm trying to add my script to some /etc/init.d folder but in my cooked ROM there is just a system/etc folder, extracted from an update.zip without any init.d
HowTo?

[edit] Checked Cyan's ROM and I see /system/etc folder with content, and init.d is there.

Jack_R1 said:
On Cyanogen, for example, /etc is mounted to /system/etc on start.
Click to expand...
Click to collapse
Yes. In my rom, it is also mounted.
But init.d does not exists.
And I don't even know if it works that way on Android...
HowTo?

Edited my post above.

Jack_R1 said:
Edited my post above.
Click to expand...
Click to collapse
Thx for your time.
Yes I also did.
In fact, I search for the answer quite some time before posting.
I see this folder in Cyan's ROM.
But it still do not tell me how to make my script run at boot:
- do I have to create init.d?
- will my script be under names conventions (like 01xx 02xx 03xx)
- will it loads automaticaly by Android 2.2 ?

some progress:
i found etc/init* in ramdisk!
trying a few things on that and report
-------------------------------------
Sent via the XDA Tapatalk App

On CM, try putting your script in /system/bin then adding it's name to /system/etc/init.d/20userinit.
There is also an app in the market called autostart which runs a script at /data/opt/autostart.sh which you have to create. I use it because it's the first way I found to execute scripts at startup and I just stuck with it, so I've never used the CM script, but I think that's the proper place to add it.
Unfortunately, I haven't seen a way to run things at startup on froyo yet. When someone figures that one out, please report.

fubaya said:
Unfortunately, I haven't seen a way to run things at startup on froyo yet. When someone figures that one out, please report.
Click to expand...
Click to collapse
I'm trying Autostart (root), the app you told me, but it seems you also say that you found no way to do such thing on FroYo...
Do you mean autostart (the app) do NOT work on FroYo?

leonnib4 said:
I'm trying Autostart (root), the app you told me, but it seems you also say that you found no way to do such thing on FroYo...
Do you mean autostart (the app) do NOT work on FroYo?
Click to expand...
Click to collapse
Yes, autostart doesn't seem to work on Froyo. You talked about both Cyan and Froyo, which one are you using?

fubaya said:
Yes, autostart doesn't seem to work on Froyo. You talked about both Cyan and Froyo, which one are you using?
Click to expand...
Click to collapse
I said I was aware Cyan was using bootscripts, but Im using stock rooted froyo.
In fact, Im cooking one.

Found it!
In Cyanogen sources:
in boot.img
in ramdisk
init.rc
Code:
# Execute files in /etc/init.d before booting
service sysinit /system/bin/logwrapper /system/xbin/busybox run-parts /system/etc/init.d
disabled
oneshot
dsixda should include in its rom kitchen

Emulating the effect of the Autostart app
Since the Autostart does not work on Android 2.2 (Froyo),
I simulate it by the following contents in /system/etc/init.d/20autostart :
Code:
#!/system/bin/sh
/system/bin/sh /data/opt/autostart.sh >/data/opt/autostart.out 2>/data/opt/autostart.err
which not only calls /data/opt/autostart.sh at boot time, but
also dumps its stdout to /data/opt/autostart.out
and dumps its stderr to /data/opt/autostart.err
which is very helpful for debugging the commands in /data/opt/autostart.sh
Note that you need to enter recovery mode before you can write to /system/etc/init.d/

ddvo said:
Since the Autostart does not work on Android 2.2 (Froyo),
I simulate it by the following contents in /system/etc/init.d/20autostart :
Code:
#!/system/bin/sh
/system/bin/sh /data/opt/autostart.sh >/data/opt/autostart.out 2>/data/opt/autostart.err
which not only calls /data/opt/autostart.sh at boot time, but
also dumps its stdout to /data/opt/autostart.out
and dumps its stderr to /data/opt/autostart.err
which is very helpful for debugging the commands in /data/opt/autostart.sh
Note that you need to enter recovery mode before you can write to /system/etc/init.d/
Click to expand...
Click to collapse
Did you create the 20autostart folder? Are you performing this with Autostart running? I'm trying to have insmod tun.ko perform at each boot so my VPN works without having to open TerminalE and doing it at command line on the phone.

connexion2005 said:
Did you create the 20autostart folder?
Click to expand...
Click to collapse
20autostart is a shell script file, not a folder. All scripts in the directory /etc/init.d are executed on boot in alphanumerical order.
connexion2005 said:
Are you performing this with Autostart running?
Click to expand...
Click to collapse
Autostart is non-functional at least on my HTC Desire with rooted 2.2 (Froyo); you can uninstall it, while the method I explained above is guaranteed to work.

ddvo said:
Since the Autostart does not work on Android 2.2 (Froyo),
I simulate it by the following contents in /system/etc/init.d/20autostart :
Code:
#!/system/bin/sh
/system/bin/sh /data/opt/autostart.sh >/data/opt/autostart.out 2>/data/opt/autostart.err
which not only calls /data/opt/autostart.sh at boot time, but
also dumps its stdout to /data/opt/autostart.out
and dumps its stderr to /data/opt/autostart.err
which is very helpful for debugging the commands in /data/opt/autostart.sh
Note that you need to enter recovery mode before you can write to /system/etc/init.d/
Click to expand...
Click to collapse
I've tried it but it doesn't work for me.
there is a rcS file which seems to run everything in the init.d folder
i made a file "20autostart" file containing the script you posted.
I didn't have an "opt" folder in "/data", created one.
Created "autostart.sh, containing "swapon /data/swap256"(script works with gscript).
But it isn't run and no autostart.out or .err file is created after reboot. Seems like it isn't run at all..
There is an "sh" file in the "/bin" folder so it should be able to call that function.
I have no experience what so ever with this but i've done all the steps necessary.
Never mind, created an other solution!

Hi NRG, I just checked again with my system, and there it still works.
Maybe because it's a specific custom ROM version of Android 2.2?
Mine is called "Eight Minutes to Eight O´Clock A.M." from android.modaco.com/content/htc-desire-desire-modaco-com/312051/oclock-custom-rom/
Maybe you used the wrong shell path: /bin/sh instead of /system/bin/sh.
Which other solution have you found meanwhile?

Tasker can run things at boot if anyone needs another way to do it. You can run shell commands with Tasker and the Locale Execute Plugin.

/data/local/tmp
Hi, you are looking for - /data/local
chmod 755

Hey Folks, mybe one of you can give me a hint.
I extracted the boot.img saved before with oneclick-recovery for zte v9 light using mytools from another post (unpack-bootimg.pl etc) and everything worked. i am using Ubuntu Linux on my pc. After i added the quoted lines i repacked it, using the repack script from that mytools and flashed it using
Code:
flash_image boot /sdcard/boot.img
reboot
Well- thats what bricked my phone. Dont worry, got the official zte flashing tool, a clean android 2.2 and unbricked it after a few days of worrying... But what am i making wrong to get the init.d contents get executed on boot?
leonnib4 said:
Found it!
In Cyanogen sources:
in boot.img
in ramdisk
init.rc
Code:
# Execute files in /etc/init.d before booting
service sysinit /system/bin/logwrapper /system/xbin/busybox run-parts /system/etc/init.d
disabled
oneshot
dsixda should include in its rom kitchen
Click to expand...
Click to collapse

[Q] Porting Meego to the Tab, some Android noob questions before I start

Hi chaps,
I've just bought a Galaxy tab with plans to port Meego to the device.
I'm new to all the Android stuff, and tbh the myriad methods for doing this/that/the other and the relative lack of explanation of what's actually being done in these various methods/tools is quite confusing (and worrying).
So, if you'll bear with me, I have a few questions which are probably quite basic.
I've rooted my Tab using SuperOneClick, no problems there, I also understand that there is a leaked flashing tool called (Multi)Odin and an open source flashing tool called Heimdall. I understand adb.
So onto the questions:
Before I start messing about, how should I backup my existing firmware image? I see people talking about taking image dumps using dd, or Odin or Heimdall. What is the preferred method? And how should one then restore the device from these backups?
Alternatively is it possible to simply download the firmware directly from Samsung (I see links to later firmware, but really I'd be happy with what I have currently - P1000XXJK5 and FROYO.XWJJ7)?
I'm assuming that the best installation method would be to replace recovery, then I can add my own kernel and have it boot a rootfs mounted on the external SD card for example. Any thoughts?
I've seen one thread about people compiling their own kernels, with panics and the like which are solved by giving the full path to the initramfs extracted from the existing image. Any clues as to why the built version doesn't work? This is not so important as I can have a look at this when I build the Samsung source.
Is anyone looking at the bootloaders? Is there any information anywhere about them (as changing the bootloader to allow selection of the kernel to be booted would make life easier)?
Thanks for your patience!

Ok, so to partly answer myself, I see www dot samfirmware dot com has links to downloads of firmware images.
I'd really prefer to generate my own image of what's currently on the device rather than trusting a download site, but I guess it's better than nothing. Does anyone know how these images were generated anyway?

lardman said:
Ok, so to partly answer myself, I see www dot samfirmware dot com has links to downloads of firmware images.
I'd really prefer to generate my own image of what's currently on the device rather than trusting a download site, but I guess it's better than nothing. Does anyone know how these images were generated anyway?
Click to expand...
Click to collapse
Samfirmware get their images direct from Samsung insiders. They are not dumps.
If you want to dump from your device search "rotobackup" here in the dev forum.
Sent from my GT-P1000 using Tapatalk

alias_neo said:
Samfirmware get their images direct from Saunaing insiders. They are not dumps.
Click to expand...
Click to collapse
Ok that's reassuring.
alias_neo said:
If you want to dump from your device search "rotobackup" here in the dev forum.
Click to expand...
Click to collapse
Great, just what I was looking for, many thanks

So some more questions:
Any limit to the size of the kernel? Presumably just the size of the partition (which after extracting the image for backup seems to be a pretty large 15.4MB)?
What do all the .rc files in the raminitfs do? They are as follows: fota.rc, init.goldfish.rc, init.rc, init.smdkc110.rc, lpm.rc, recovery.rc
The init.rc is the normal init.rc file, so that's fine. Presumably the recovery.rc file is run if the bootloader detects that recovery mode is wanted (holding down keys during boot). The init.goldfish.rc? I guess this is to do with the emulator, though why it would be in a release image I don't know.
I assume that init.smdkc110.rc is automatically run somewhere along the line, though I don't see where it's started.
Any thoughts on lpm.rc and fota.rc? Are multiple .rc files run for the normal and recovery boots?
Thanks

lpm.rc is for low power mode that displays battery charging animation
goldfish is for running the rom under qemu.
backup your rom using rotobackup. compile samsung's kernel from sources, mix up default initramfs with meego's init scripts. pack all Meego stuff into loop mounted disk image. then flash zImage to kernel and your disk image to factoryfs using heimdall. I assume you have experience hacking N8xx/N900 and Maemo or Meego?
factoryfs is around 300MB so I think it should fit Meego and it (and kernel) can be easily restored with heimdall.

Thanks for the comprehensive reply
Yes I do have experience hacking Maemo/Meego, though have never really had to fiddle with init scripts before and this is as good a reason as any to learn.
I'd actually like to dual boot, so am modifying recovery.rc to bring up the Meego system on the external SD card.
Am just fiddling about building extra kernel modules now (needs btrfs for my image for example) and modifying the recovery.rc file.

Hmm, well I was all set to go and flash my new zImage and was looking for the heimdall command line, when I saw this at the top of one of the threads in this part of the forum (http://forum.xda-developers.com/showthread.php?t=870690):
Restoring to factory after using this process (you need using stock images):
heimdall flash --kernel stockzImage --recovery stockzImage --factoryfs factoryfs.rfs
Click to expand...
Click to collapse
Which has made me worry a bit that I've missed a recovery partition with its own kernel and wrongly assumed that the same kernel is used for both recovery and normal running, just with a different .rc file to be interpreted by init.
Any thoughts?

Do we trust the partition sizes reported here: http://forum.xda-developers.com/showpost.php?p=9471190&postcount=14
They seem very small for the kernel partition. I used RotoHammer's dd method to grab the contents of the partitions as a backup, so am assuming the sizes shown above are not correct (or represent something else?)
Going back to RECOVERY and ZIMAGE partitions - the ZIMAGE partition contains a recovery.rc, the question is really whether, even if they use the same zImage in both the ZIMAGE and RECOVERY partitions, the version in the RECOVERY partition is actually booted if recovery mode is selected (by holding the up volume key, etc.)? OTOH it may be that the RECOVERY partition is either empty or unused, has anyone tested specifically to see whether recovery.rc is run from the ZIMAGE partition?

Well I think I can answer my own question there, I flashed my modified kernel (modified recovery.rc) only to the KERNEL partition, and it boots normally if I don't touch anything, and just gets stuck on the first Samsung screen if I boot in recovery mode.
So it's doing something, I just can't tell what. Not sure if any kernel messages are getting lost behind that image, or perhaps they aren't even output to the framebuffer at all. I seem to remember seeing something about disabling the splashscreen so I'll go and have a look for that. Anyone got any other suggestions?
P.S. I also note there's a flash of screen corruption as the device starts up with my new kernel, I don't remember seeing that before. Is this a usual occurance?

I see from the Nexus S port that including adbd in the image seems to be the way to go for early messages, I'll need to generate a new Meego image and have another go later on.

Interesting, I can't see that I've done anything wrong, and my extra init shell script is not started. I am trying to use the "exec" keyword in recovery.rc to start a shell script which will pass control to the Meego rootfs. At the start of my shell script I start adbd (i.e. still within the initramfs), so I should be able to tell if it has started, and it doesn't appear to do so.
Therefore I did some Googling, and I've seen that in some cases the initramfs init does not implement the "exec" keyword (http://forum.samdroid.net/f9/new-init-exec-import-implemented-3280/). This is troublesome for me as it's what I'm trying to use, but at least would explain why I don't seem to leave the init process
I couldn't see the Samsung specific source for init anywhere, has anyone found any? I'm not happy to replace it using the standard Android source as I'm guessing there's code missing which allows the bootloader to tell init how the device was started so that it knows which of the .rc files to run. Has anyone looked into this?
Thanks

Looking at the code in that link it looks pretty straightforward, just a case of parsing the kernel command line (though I might just reverse engineer the existing init first to make sure I'm not missing anything).
Would still be easier to get the actual source code from Samsung, so I've emailed their Open Source group.

lardman said:
P.S. I also note there's a flash of screen corruption as the device starts up with my new kernel, I don't remember seeing that before. Is this a usual occurance?
Click to expand...
Click to collapse
I get it with CM

Does CM use a compressed initramfs? I'm using one of those and wondering if it's something to do with the (admittedly small) extra time required to move to init.
I don't have my Tab with me here, could someone post the output of /proc/cmdline please? You'll need to be root. Thanks.

Well it's booting you'll all be glad to hear.
More details to follow, but from memory the following were required:
Custom kernel to add btrfs support (as the image I'm booting is a btrfs partition on the external SD); kernel patch to allow compile-time cmdline to be added to the end of the bootloader cmdline (to enable console=tty0); replace Android init with init script to perform some basic setup then pivot_root to the Meego partition.
Next steps are to get the Meego system running usefully (which includes getting a terminal as currently I just have a login prompt but no way of inputting anything!) and also seeing whether I can get dual booting working with an Android system standard boot and Meego replacing the recovery boot.
Poor pic, but still: http://people.bath.ac.uk/enpsgp/Tab/PICT0040.JPG

Good stuff. Thanks for keeping us informed.

After you've got the groundwork for this done, how easy would it be to get Ubuntu running?

Try google http://lmgtfy.com/?q=ubuntu+on+galaxy+tab
Sent from my GT-P1000 using XDA App

brilldoctor said:
Try google http://lmgtfy.com/?q=ubuntu+on+galaxy+tab
Sent from my GT-P1000 using XDA App
Click to expand...
Click to collapse
That's using chroot, which I don't want. I want it running natively.
Sent from my Galaxy Tab

[Q] Help!! wifi error after loading compiled franco kernel

Hi All,
This is my first thread on this forum. Please help in resolving an error that I am facing. I could compile and link successfully franco kernel after downloading the source from franco's github!!
The only problem I face is with wifi. It displays error in the wi-fi option!! This is some what similar to what we used to get in the initial version of gingerbread kernel what Franco had made earlier!! I get the same error even with the stock GB source code of LG or with paulo's kernel source!!! Strange!!!!
The wifi driver(bcm4325) seems to be same except for some tweaks to the original GB source(In the case of Franco's)!! In either case, I am getting the error. The only difference I see is that of the compiler option -Ofast(Optimization option) was used by Franco while since I updated to the latest version of gcc, I do not get the -Ofast option!! So it uses the -Os option instead!!
Error is(logcat):
D/WifiService( 1726): setWifiEnabledBlocking : Country code is COM
E/WifiService( 1726): Failed to load Wi-Fi driver.
Same compiling options were used to compile both zImage and modules?? What could be wrong here? I am not sure what could be wrong here!!! Can anybody help me on this??
Thanks in advace.

I get this on sense too
(but I replaced all that Android wifi stuff,so on Sense,its wierd )

-Os has always been ****... Other than that, unless you can somehow make the log more verbose, NFC. Can you get something more useful when you try to load the module manually with insmod?

I dont use -Ofast anymore. Did you manually add wireless.ko to lib/modules from your compiled kernel?
Sent from my u8800 using XDA Premium App

dr.notor said:
-Os has always been ****... Other than that, unless you can somehow make the log more verbose, NFC. Can you get something more useful when you try to load the module manually with insmod?
Click to expand...
Click to collapse
I tried it thro' the init.rc too. I dont any other ways to do insmod!!
But it failed even on that account!!

franciscofranco said:
I dont use -Ofast anymore. Did you manually add wireless.ko to lib/modules from your compiled kernel?
Sent from my u8800 using XDA Premium App
Click to expand...
Click to collapse
Yup franco. I copied to modules and then signed it with command:
"java -classpath testsign.jar testsign port.zip signed-port.zip"
I really can't understand why this is getting failed as the same compile options were used for both zImage and wireless.ko!! Rest all works fine except the wifi error!!! The idea i think is as long as all the executables are of same signature, then it should work fine, right?? I am confused on what could be the problem!!!

dr.notor said:
-Os has always been ****... Other than that, unless you can somehow make the log more verbose, NFC. Can you get something more useful when you try to load the module manually with insmod?
Click to expand...
Click to collapse
Today I will try with other compile options, either O1, O2.... etc.
Strange thing is that I face this problem with all other available kernels also!! Like for ex., original GB source from LG, paulo's kernel!! All of it!!

shashi_hv said:
I tried it thro' the init.rc too. I dont any other ways to do insmod!!
But it failed even on that account!!
Click to expand...
Click to collapse
Uh, I do not understand a word.
Code:
$ su
# busybox insmod /system/lib/modules/wireless.ko
What is the output of the above.

dr.notor said:
Uh, I do not understand a word.
Code:
$ su
# busybox insmod /system/lib/modules/wireless.ko
What is the output of the above.
Click to expand...
Click to collapse
Weird!!! Though I see the file being there thro' file manager, I get the error as "No such file or directory"!!
I was telling that I tried to insert this same command even in the init.rc file at the boot option!!

shashi_hv said:
Weird!!! Though I see the file being there thro' file manager, I get the error as "No such file or directory"!!
I was telling that I tried to insert this same command even in the init.rc file at the boot option!!
Click to expand...
Click to collapse
You have been already told that you need to manually add /system/lib/modules with the ones you want (such as wireless.ko or tun.ko or cifs.ko) to the ZIP you are flashing.
Flashing zImage only will not flash the modules!!!!
As for your file manager, I recommend this as a "file manager"
Code:
# ls -l /system/lib/modules
-rw-r--r-- 1 0 0 19948 Aug 1 2008 tun.ko
-rw-r--r-- 1 0 0 191854 Aug 1 2008 wireless.ko

dr.notor said:
You have been already told that you need to manually add /system/lib/modules with the ones you want (such as wireless.ko or tun.ko or cifs.ko) to the ZIP you are flashing.
Flashing zImage only will not flash the modules!!!!
As for your file manager, I recommend this as a "file manager"
Code:
# ls -l /system/lib/modules
-rw-r--r-- 1 0 0 19948 Aug 1 2008 tun.ko
-rw-r--r-- 1 0 0 191854 Aug 1 2008 wireless.ko
Click to expand...
Click to collapse
I know that notor!!!
I copied the tun.ko and wireless.ko to the appropriate folder and built the zip file which i flashed!!
The problem is very weird. I see the file wireless.ko if I browse thro' file manager. Even when i press tab in busybox, wireless.ko gets auto populated or even the ls command lists it!!
It is much more weird that if I tried to do insmode ....../tun.ko, i get the error as 'exec format error' but a 'no such file' for the wireless.ko!! Though I flashed both these of these!!

You know, go wipe the files in /system/lib/modules and flash your kernel and modules from the SAME KERNEL you have compiled.
Also, it is insmod, not insmode and generally if you are posting something, copy and paste the exact output of a command instead of telling us stories about what the output says.

Yup thats what i was thinking too.. i would wipe and try copying it once again.
Definitely i would have shown you the screen shots.. but i am not in a position to grab those and paste it here, as i am in office right now.. but the point is i understand some of linux system and familiar wirh it!!
I tried to create and flash the zip the standard way thats available on net and it did not worked!! Thats the point!! So wanted to know am i missing anything!!
Sent from my LG Optimus One P500 using XDA Premium App

Well, things like 'exec format error' clearly suggest that you flashed some weird corrupt junk...

dr.notor said:
Well, things like 'exec format error' clearly suggest that you flashed some weird corrupt junk...
Click to expand...
Click to collapse
I tried this!!!
1. su
2. rm -f /system/lib/modules/wireless.ko
3. rm -f /system/lib/modules/tun.ko
Now the files were not there in the directory. Flashed the same zip file which I used earlier and found the wireless.ko and tun.ko in the same path!!! But still the problem prevails!!
Just to confirm once again that I indeed copied the compiled wireless.ko and tun.ko and built the zip file!! No problem in that!!!
Why do not you try to do insmod of any existing file in the modules path and report what error you get?? I think even you should get the same error even in your phone too!! I tried this command on an already existing libra.ko in the same path and got the same error!!!

for a few weeks i has compiled my kernel with optimizations -O3 and got "no such device" when tried to insmod the wifi module ...
possibly the wifi module gets corrupted when the kernel is to much optimized...

andy572 said:
for a few weeks i has compiled my kernel with optimizations -O3 and got "no such device" when tried to insmod the wifi module ...
possibly the wifi module gets corrupted when the kernel is to much optimized...
Click to expand...
Click to collapse
Yeah. Just leave the thing alone. There is basically nothing you will optimize by subverting various crazy -O3 -fzomgoptimized -fflying-phone flags to kernel compile. Leave the stock CFLAGS stuff alone.

dr.notor said:
Yeah. Just leave the thing alone. There is basically nothing you will optimize by subverting various crazy -O3 -fzomgoptimized -fflying-phone flags to kernel compile. Leave the stock CFLAGS stuff alone.
Click to expand...
Click to collapse
On a different note, can anybody tell me who will load the wireless.ko and tun.ko at boot time? I mean is there any kind of scripts like the init.rc or any other *.sh scripts under /system/etc?

I tried to see in the init.qcom.wifi.sh script, but its based on the property 'wlan.driver.status'!! I dont see this property under getprop command, but added one using setprop, but no success!!!

Suggestion: restore the stock init **** and leave it alone. There is absolutely no need to mess with that to get WiFi working on any ROM. Others, like tun.ko, you need to load manually via initscript or whatever. Go fix your kernel compile and it will just work.

[Script]Swap2cache (make use of unused Memory)

i finally get it to work.
this script (if kernel support) create a swapfile on mostly unused /cache partition
-copy the script to phone
-chmod
-add it to end of hw_config.sh (or any other way of bootexecute)
have fun
inteks
update:
new version creates own loopdevice (thx to hygge)

pls guider install ??

niceee.
Does this work on rooted and locked 2.3.4 Arc ?

dubist said:
niceee.
Does this work on rooted and locked 2.3.4 Arc ?
Click to expand...
Click to collapse
sorry but you need a kernel with swap support ...

le_manhpro said:
pls guider install ??
Click to expand...
Click to collapse
the easiest way is to use i.e. rootexplorer to run the script but then you have to do it after every reboot.
maybe a good idea for testing

will it work on ray?

What's benefits we have using swap file?
Thx for answer

inteks said:
sorry but you need a kernel with swap support ...
Click to expand...
Click to collapse
So what kind of kernel, is DoomKernel support? why you dont give a sameple?

Interesting idea, I have setup swap as descriped but I had to change loop device to /dev/block/loop18 which was the only unused loop device on my mobile.
It was wierd, because all new loop devices I created was quickly reserved for the same app by the system, rather annoying. But luckily I had one unused allready available.
I will let you know how it works, how the system performance is percieved after some testing. I would think it could slow down the device, the memeory is increased but it will be on slower memory.

donghungx said:
So what kind of kernel, is DoomKernel support? why you dont give a sameple?
Click to expand...
Click to collapse
yepp, doomkernel support swap
Sent from my MT15i using Tapatalk

Hi inteks
Thanks allot for your script, it actually feels like its memory has been increased with 64MB. I have a few times experienced a slight lag when starting up memory hungry games but the homescreen no longer has to redraw when returning from the game
It is usually problematic in the Order and Chaos game to chat as the game loads the default keyboard which takes some time as it is removed from memory again as soon as you have send your message. The swap makes the keyboard stay in memory and open up instantly
I am also able to keep more applications open during normal use, I would normally have problems having mail, web and other document open at the same time.
I had to modify your script and manually create a new loop device, all loop devices from loop0 to loop38 was allready used.
# mknod -m640 /dev/block/loop50 b 7 50

hygge said:
Hi inteks
Thanks allot for your script, it actually feels like its memory has been increased with 64MB. I have a few times experienced a slight lag when starting up memory hungry games but the homescreen no longer has to redraw when returning from the game
It is usually problematic in the Order and Chaos game to chat as the game loads the default keyboard which takes some time as it is removed from memory again as soon as you have send your message. The swap makes the keyboard stay in memory and open up instantly
I am also able to keep more applications open during normal use, I would normally have problems having mail, web and other document open at the same time.
I had to modify your script and manually create a new loop device, all loop devices from loop0 to loop38 was allready used.
# mknod -m640 /dev/block/loop50 b 7 50
Click to expand...
Click to collapse
pls guider install tks

le_manhpro said:
pls guider install tks
Click to expand...
Click to collapse
Here is the script with my modifications manually creating a new loop devices. I have used loop50 as 0-38 was allready in use and it would leave some room for new loop devices.
I am using scriptmanager to either run the script manually or run it at boot.
Have marked my changes with bold
#!/system/bin/sh
if busybox [ ! -f /cache/swap/swapfile.swp ]
then
echo "Create Swapfile"
mkdir /cache/swap
busybox dd if=/dev/zero of=/cache/swap/swapfile.swp bs=1M count=64
busybox mkswap /cache/swap/swapfile.swp
busybox chmod 0600 /cache/swap/swapfile.swp
else
echo "Swapfile Exist"
fi
echo "connect loop devices"
mknod -m640 /dev/block/loop50 b 7 50
losetup /dev/block/loop50 /cache/swap/swapfile.swp
echo "use loopdev for swap"
swapon /dev/block/loop50
echo "raise swappiness 2 "
echo 90 > /proc/sys/vm/swappiness
cat /proc/sys/vm/swappiness
free

Thanks a lot for the script. What is this loop anyways?

matus201 said:
Thanks a lot for the script. What is this loop anyways?
Click to expand...
Click to collapse
It is a device driver in linux, the loop device driver is created as a block device which functions as disc device. The loop device driver are used to loop back into local imagefiles on the existing filesystem.
You then use losetup to point the loop device file towards an imagefile on the existing memory devices. In this case it is configured to point towards the new empty 64MB file that are created in the beginning of the script.
You now have a small 64MB filesystem attached that we can use as linux swap

Why not making a 128 swap file to improve even more?!
I'm a noob... So I just intested to know how it works...
Sent from my LT15i using XDA App

must this be added for your kernel to start swapping inactive applications from the RAM to the cache partition ?!
thanks man
---------- Post added at 09:30 PM ---------- Previous post was at 09:29 PM ----------
haimelf said:
Why not making a 128 swap file to improve even more?!
I'm a noob... So I just intested to know how it works...
Sent from my LT15i using XDA App
Click to expand...
Click to collapse
the cache partition is only 100mb

yes
Sent from my MT15i using Tapatalk

i heard that swap would wear the cache partition in time thus making it un-useful @ all for it's original use , i believe that cache is used for stuff like downloading apps from market !
thanks

What is "chmod" ??
Sent from my LT15i using xda premium

[DEV] Changing Splash Screen

So, I was doing some research on how you can change it and I ended up finding this in initramfs/etc/scripts/init_sde:
Code:
# Show a nice boot image
case "$PRODUCT_NAME" in
A80S)
BOOT_IMAGE=$BOOT_IMAGE_BASE-1024x768.gz
;;
A80H)
BOOT_IMAGE=$BOOT_IMAGE_BASE-1024x768.gz
;;
A101S)
BOOT_IMAGE=$BOOT_IMAGE_BASE-1280x800.gz
;;
A101H)
BOOT_IMAGE=$BOOT_IMAGE_BASE-1280x800.gz
;;
esac
$ZCAT $BOOT_IMAGE > /dev/fb0
And at the top of that file:
Code:
BOOT_IMAGE_BASE="/SDE"
Now, if we could either find those gz files and edit them or extract and link the file to the right place, we'd change it
Any ideas?

Well, first idea would be using root explorer to check, if /SDE folder exists. If not, rooting stock rom, like 4.0.5, with universal rooting tools, and check if it's visible in that rom. I mean, root the stock rom which you install with aos.

julle131 said:
Well, first idea would be using root explorer to check, if /SDE folder exists. If not, rooting stock rom, like 4.0.5, with universal rooting tools, and check if it's visible in that rom. I mean, root the stock rom which you install with aos.
Click to expand...
Click to collapse
Hi
I'll save you the trouble as you won't find an SDE directory anywhere on a rom, "SDE" is just the prefix used for the gz file, e.g SDE-1024x768.gz. The script and Image live in the archos gitorious gpl repo.The image is a bitmap so is simple to change.
Archos GPL Code is built using BuildRoot which is a popular build system for embedded devices, but it's kinda of non-standard for Android.
If you want to do anything with it you will need to run the full Build first by running "make" in the buildroot directory, then afterwards run "make sde" which will create the gzipped image files. The full build takes about an hour as you cannot pass an -j modifies to make when using buildroot . However you only need to do the full make once, Obviously if you know what you're doing you can just run the bitmap through whatever conversion process is being run, then gzip it up but for the easy life it's recommended to do the full build first.
I think the bitmap is being converted to a raw argb file, although don't quote me on that! . Once it's been converted you don't even have to gzip it really as you can replace the "zcat" call with a call to "cat" but it makes no odds either way really apart from in size
To get started have a look here [ gitorious archos-gpl-gen9 tree ], read both the readme files, then you can find the image and build script in the buildroot/packages/sde directory.
Thanks
EDIT: I'll also add that this won't change the "power on" splash, I believe that is displayed by avboot which, from what I can gather is the 3rd stage bootloader, If I recall it was possible ( although dangerous ) to change it on earlier archos devices but due to checks in the gen 9 version there is a very real risk of bricking the device. From the various threads I've read, I believe Letama and Scholbert know more about this.

Hi Quinny899!
Quinny899 said:
So, I was doing some research on how you can change it and I ended up finding this in initramfs/etc/scripts/init_sde:
Code:
# Show a nice boot image
case "$PRODUCT_NAME" in
A80S)
BOOT_IMAGE=$BOOT_IMAGE_BASE-1024x768.gz
;;
A80H)
BOOT_IMAGE=$BOOT_IMAGE_BASE-1024x768.gz
;;
A101S)
BOOT_IMAGE=$BOOT_IMAGE_BASE-1280x800.gz
;;
A101H)
BOOT_IMAGE=$BOOT_IMAGE_BASE-1280x800.gz
;;
esac
$ZCAT $BOOT_IMAGE > /dev/fb0
And at the top of that file:
Code:
BOOT_IMAGE_BASE="/SDE"
Now, if we could either find those gz files and edit them or extract and link the file to the right place, we'd change it
Any ideas?
Click to expand...
Click to collapse
I'd suggest to read this thread in the Gen8 section completely.
http://forum.xda-developers.com/showthread.php?t=1290242
AFAIK, nothing changed on the Gen9 devices.
To point it out again:
It's risky... if you mix things up in the rawfs, you'll brick your tablet... at least it will stuck in bootloader.
Someday we'll be able to recover
Anyway, please be aware of this!
By wiping the boot logo you're entering low level hacking.
trevd said:
EDIT: I'll also add that this won't change the "power on" splash, I believe that is displayed by avboot which, from what I can gather is the 3rd stage bootloader, If I recall it was possible ( although dangerous ) to change it on earlier archos devices but due to checks in the gen 9 version there is a very real risk of bricking the device. From the various threads I've read, I believe Letama and Scholbert know more about this.
Click to expand...
Click to collapse
Nothing to add here... anyway here i am
Letama wrote a tool to parse the files inside rawfs and tweak them. See the thread i pointed to in my above statement!
Best regards,
scholbert