I've been messing around with swaps and noticed that the
swapon method is not implemented...
I hear that cyanogenmod6 uses some sort of special swap method...
Have I disabled that by messing around?
Hackmodford said:
I've been messing around with swaps and noticed that the
swapon method is not implemented...
I hear that cyanogenmod6 uses some sort of special swap method...
Have I disabled that by messing around?
Click to expand...
Click to collapse
I am currently using nightly 9/10 with the Kernel (Darchstar #2). As far as I know Compcache is enable and working. Is this what you are talking about?
I think hes talking about ramzswap. I don't think its enabled by default, but you can flash the newest stable uncapped kernel by decad3nce and then push the ramzswap.ko module to your /system/lib/module folder and it will work.
Also your SDcard must have a swap partion.
soo...
download both the kernel and the ramzswap.
unzip the ramzswap.ko
put the flashable kernel.zip on the root of your sdcard and put the ramzswap.ko in c:\ on your pc
reboot into recovery
flash the kernel
then type:
adb shell
mount -a
exit
adb push c:\ramzswap.ko /system/lib/modules/ramzswap.ko
adb shell reboot recovery
once booted type this to be sure its working...
adb shell
free
if it shows the swap partion having some of the space used swap is working =)
http://forum.xda-developers.com/showthread.php?t=756774
get the 9/11/2010 (#13) stable kernel and the option ramzswap module.
urushiol said:
I think hes talking about ramzswap. I don't think its enabled by default, but you can flash the newest stable uncapped kernel by decad3nce and then push the ramzswap.ko module to your /system/lib/module folder and it will work.
Also your SDcard must have a swap partion.
soo...
download both the kernel and the ramzswap.
unzip the ramzswap.ko
put the flashable kernel.zip on the root of your sdcard and put the ramzswap.ko in c:\ on your pc
reboot into recovery
flash the kernel
then type:
adb shell
mount -a
exit
adb push c:\ramzswap.ko /system/lib/modules/ramzswap.ko
adb shell reboot recovery
once booted type this to be sure its working...
adb shell
free
if it shows the swap partion having some of the space used swap is working =)
http://forum.xda-developers.com/showthread.php?t=756774
get the 9/11/2010 (#13) stable kernel and the option ramzswap module.
Click to expand...
Click to collapse
I believed Darch committed on 9/2 .. I am using Darch default kernel on 9/10 and it's working
roadster92 said:
I believed Darch committed on 9/2 .. I am using Darch default kernel on 9/10 and it's working
Click to expand...
Click to collapse
Ah! I hadn't been using the stock kernel when trying the nightlies. Good to know its working in the stock kernel.
That makes things easier indeed!
sorry it has only korean readme and init files
you will need to remove /system/persistent and /sdcard/OpenRecovery folders before install and backup copy init files on /
install is so easy
first root your phone and and connect the usb cable
second copy the files and folders on rar/sdcard and rar/pc_installer/sdcard
third run the batch files(preinstall->main) on rar/pc_installer/pc
last make 'ramdisk' folder on /system/etc and copy init files before install
i think you will need to reboot twice success to run
special thanks for hounjin modding 2nd-init binary
you will can download
modules for it (also you can install it use clockworkmod) from http://dateno1.egloos.com/category/%EB%A1%AC%ED%82%A4%EC%B9%9C%20for%20motoroi
this is example files
you can only the phone root/unroot even 2.2.1
you can also use 2nd-init or boot script and etc (i think make and use module for it is very easy)
also it support ext3 if you copy jbd.ko and ext3.ko on /system/lib/modules
dateno1 said:
special thanks for hounjin modding 2nd-init binary
Click to expand...
Click to collapse
fyi - 2nd-init from milestone works fine too its a generic app for milestone kernels
Newb alert here
What does it do?
it's some modded
Dexter_nlb said:
fyi - 2nd-init from milestone works fine too its a generic app for milestone kernels
Click to expand...
Click to collapse
it support setting file and etc
and i edit script and somethings (it for xt720 mixpack )
i use it for skaf, dlna, overclock script, boot sound, etc
also clockworkmod zip file format is very good (it will make easy install/uninstall some app or function)
my rom havn't almost bundle software and i make install pack so if user want something easy install/uninstall that
and i think it only way to root/unroot on phone for 2.2.1
dateno1 said:
it support setting file and etc
and i edit script and somethings (it for xt720 mixpack )
i use it for skaf, dlna, overclock script, boot sound, etc
Click to expand...
Click to collapse
ok i think you misunderstood, or you mean some different app, 2nd-init is to call init.rc once again and kernel reloads its init process files. so the script you refer to must be added after you run 2nd-init, that is not a mod of 2nd-init, but the rom itself, right?
dateno1 said:
also clockworkmod zip file format is very good (it will make easy install/uninstall some app or function)
Click to expand...
Click to collapse
again you mean running clockworkmod from 2nd-init? running the update.zip zip structure is not a clockworkmod standard, but used since android 1.5 on Hero
or you mean something else?
i run clockworkmod from 2nd-init and leave the rest to CWM and its functions, i dont do custom scripts, when its part of cwm.
i edit init script using 2nd-init
so if you have OpenRecovery folder on sdcard it will goto openrecovery edited (it has clockworkmod run menu) and if you not it will edited menu (it can run clockworkmod from system partition)
but i don't know when i use this way why clockworkmod can't format or overwriting boot partition
i make it for rom's modules (every xt720 can run it) (it has 2nd-init&2 bootscript runner and install pack function, backup phone (also ext3 and froyo's sd secure) (if you want you will change everything exclude kernel, lbl,mbm)
clockworkmod's zip format is old type but it can copy, delete, move, symlink etc
so user want to change or add or remove something from phone, it will do that for few second (everyone can making use some packs for phone) (and it's very easy)
i want to everyone install it for phone and many people making pack (it will every one can have own's customized rom )
sorry for poor english
i success make pack every defalt apps on phone (install/uninstall)
even i make app2ext3 pack if you before parted ext3 partition on sdcard (just install and boot, install and boot, install) (1th install modules and etc and 2nd insert boot script for move and symlink and 3nd remove 2nd's boot script)
i think it will can more easy to using phone
even in korean rooted phone can connect bank's app (it has root check)
this is install guide
http://dateno1.egloos.com/59550
korean and some english and many screenshot
I've flashed Dharam's Stock Performance ROM. It has Fugumod kernel (etc/init.d support) and ZiplAlign, RamHack, etc...
But when I wanted to find the ZipAlign's log file I haven't found anything. There is a line in the zipalign script:
"LOG_FILE=/data/zipalign.log"
So it supposed to be "somewhere" a "zipalign.log" file. But there is no any zipalign.log, so there is no zipaligning at startup, so you can put any script in the folder "etc/init.d", it won't do anything... Right?
Or how can I check that the init.d scripts worked or not? And if the zipalign script didn't do anything, how I can get it work?
SRQ642 said:
I've flashed Dharam's Stock Performance ROM. It has Fugumod kernel (etc/init.d support) and ZiplAlign, RamHack, etc...
But when I wanted to find the ZipAlign's log file I haven't found anything. There is a line in the zipalign script:
"LOG_FILE=/data/zipalign.log"
So it supposed to be "somewhere" a "zipalign.log" file. But there is no any zipalign.log, so there is no zipaligning at startup, so you can put any script in the folder "etc/init.d", it won't do anything... Right?
Or how can I check that the init.d scripts worked or not? And if the zipalign script didn't do anything, how I can get it work?
Click to expand...
Click to collapse
its wrkin for me with fugumod ultra & 2.4beta... I use dis for underclocking cpu at d start up & prevent freezing..
Sent from my GT-I5800 using Tapatalk
I've figured out that the scripts have to be named like S* (e.g., S01_myscript, S02_zipalign)...
"------ Note for startups scripts
- Put your script in /system/etc/init.d
- Scripts with Filename starting with E* (earlystartup scripts) are executed before script with filename starting with S* (users scripts)
- Scripts are executed before playlogo and after init.rc"
from http://forum.xda-developers.com/showthread.php?t=997367
Can someone please tell me how to enable JIT in JPS? I'm on stock JPS because of stability, but i think JIT will boost performance quite a bit in daily use. I see dharamg3 and kyrillos have done it in their ROMs, so can I do it and how to?
Check here.
See the second post in that link. It an easier way.
Thanks, I didn't know that this also works with jps. It says unable to push, it doesn't have permission... How do i know if it worked?
ka'cipeder said:
Thanks, I didn't know that this also works with jps. It says unable to push, it doesn't have permission... How do i know if it worked?
Click to expand...
Click to collapse
Mount as r/w first. And then push. Type following in terminal.
su
mount -o remount,rw /dev/block/stl9 /system
exit
And then push.
Or you can copy paste the same using root explorer alos.
I never had luck with those command lines and adb and stuff, but im quite familiar with root explorer, ill just push it that way.
EDIT: i was trying to download quadrant to see if it worked and now i can't instal any app from the market it say package file is invalid, tried reboot, clear market data, nothing worked
Fixed it by enabling trough adb
You can follow the link as stated above : http://forum.xda-developers.com/showthread.php?t=1026870
Steps I followed that worked for me.
1. (see 2nd post in the link above, download the zip file and unzip it) I Used root explorer to copy the files from the files folder to respective lib and bin folder in system.
2. Connected my phone through USB and using CMD i browsed to the folder JIT for example D:/JIT
3. run enable_jit.cmd (It will automatically do everything for you)
Your phone will restart and you are done
-----------Regards and God bless------------------------
Umang Sagar
Samsung Galaxy 3 I5801 (highly underrated Cellphone)
Android 2.2 Build no : Froyo.XXJPS
Baseband Version: I5800XXJP4
Kernel: G3Mod Ultimate 1.3.4 (most stable OC Kernel)
SetCPU : 200 Mhz to 1200 Mhz, (Governor - On Demand)
8 GB Class 4 SD Card
Used Lagfix for I5801 (post lagfix internal Memory 1.2 Gb)
Quadrant Score : 710+
No Heating, No Lags, No freezes anymore
Edit: bootloop, partitions are not mounting.
nagato.fm said:
I'm trying to port an X5PRO rom to regular X5 and facing an issue of unworking wi-fi and USB mass-storage. All data I have: it's all right with IMEI, wi-fi and bluetoth MAC's are missing, serial number is missing, wi-fi toggle in settings is inactive (I mean it can't be turned on and if I try to turn it on directly from wi-fi settings it says "an error occured" and goes inactive again), when I'm connecting my phone to computer and trying to turn on storage I get message of dismounting SD card and the storage stays turned off.
I've already tried to change the kernel (this ROM is running 3.0.8 PRO kernel and I've used Dzo's v5.0u17 kernel) and it haven't fixed my problems. Changing of /system/libs/hw/ to the Aurora's resulted in non-bootable rom.
Have you any ideas of how to solve it? Or is there any threads about x5pro to non-pro porting I could miss? (I've tried to google anything about problems with my port and about porting from U8800PRO and found... nothing)
Click to expand...
Click to collapse
I have no ideal to give you because i'm not a DEV, but in the whole 4rum, you can easy find out the solution to help you.
http://forum.xda-developers.com/showthread.php?t=1941239
Those so called tutorials are pretty much useless, they will help you get the base on, but no more.
So, since U8800+ has a different Wi-Fi, you should first replace /system/lib/libhardware_legacy.so, /system/bin/wpa_supplicant with the dzo ones. Then copy over the /system/lib/modules directory, it contains Wi-Fi modules needed.
If it does not work out, try to modify the init.huawei.rc or init.rc and replace service wpa_supplicant and related configs with dzo ones. Note that you will have to modify boot.img, because it contains the init files. So use a boot.img unpacker, modify it, then repack it again.
Try to get me the logs too .
Blefish said:
Those so called tutorials are pretty much useless, they will help you get the base on, but no more.
So, since U8800+ has a different Wi-Fi, you should first replace /system/lib/libhardware_legacy.so, /system/bin/wpa_supplicant with the dzo ones. Then copy over the /system/lib/modules directory, it contains Wi-Fi modules needed.
If it does not work out, try to modify the init.huawei.rc or init.rc and replace service wpa_supplicant and related configs with dzo ones. Note that you will have to modify boot.img, because it contains the init files. So use a boot.img unpacker, modify it, then repack it again.
Try to get me the logs too .
Click to expand...
Click to collapse
The problem is that I've changed the kernel using abootimg package in Ubuntu because none of the scripts for unpacking/repacking boot.img found on this forum worked for me, also I couldn't unpack ramdisk so I think I can't modify init.rc at this moment. I'll try to get some logs and do all that you've mentioned.
Also there is another problem: no mobile network at all. When I turn on the phone the indicator goes gray and nothing seems working (can't phone someone and etc.). When trying to change mobile operator via settings I get a VERY strange menu asking me for PIN code (I actually don't have one - I've disabled it years ago).
Also I need to ask for some tutorials or knowledge bases about how android works and how core parts of android work (I mean EVERYTHING I can get) because I actually don't know ANYTHING about android and there's no noob-friendly tutorials or FAQ's over the internet. I've checked xda-university and it didn't helped either.
Anyway thanks for your help, Blefish!
After following your instructions system hangs on boot. When first flashed it started to "updating android:setting applications..." and then it rebooted. Then it said "updating... 1 of 1" and another reboot. Seems like framework-res isn't starting because it hangs on bootanimation and hardware buttons lights are constantly flashing. Installing SDK now, will try to get some logs.
Try to do it step-by-step so first replace one thing, reboot, then try another. That will help us understand what makes the phone hang.
For modifying kernel or init.rc I attatched boot.img unpacker-repacker with README, check it out. I am not sure if you need a Linux box for it, but I use that tool and it works well.
MIUI-XJ (my ROM) is a ported u800pro ROM. But it is a gingerbread ROM.
First of all,you need change all init files in /system. You can found this files in system/etc (example;init.qcom.wifi.sh).And I think the mass stroage problem causing by init.qcom.usb.rc (It can found in boot.img) but I'm not sure.
You should change gralloc files for a better GPU performance. It can found in systen/lib/hw. I think You don't need change other hw files.
u8800 needs system/bin/netd - system/lib/modules/*(anything in this folder) - system/bin/wpa_supplicant - system/lib/liboem_rapi.so - system/lib/libreference-ril.so - system/lib/libhardware_legacy.so - system/etc/init.qcom.wifi.sh - system/etc/firmware/wlan/*(anything in this folder) for turn on WiFi
and also u8800 needs system/etc/init.qcom.bt.sh - system/bin/hci_qcomm_init - system/bin/qmuxd (I'm not sure about this file) - system/bin/sdptool - system/bin/hciattach for turn on BT
And also,you need change init.rc and init.huawei.rc files in boot.img for turn on WiFi and BT.
forumber2 said:
MIUI-XJ (my ROM) is a ported u800pro ROM. But it is a gingerbread ROM.
First of all,you need change all init files in /system. You can found this files in system/etc (example;init.qcom.wifi.sh).And I think the mass stroage problem causing by init.qcom.usb.rc (It can found in boot.img) but I'm not sure.
You should change gralloc files for a better GPU performance. It can found in systen/lib/hw. I think You don't need change other hw files.
u8800 needs system/bin/netd - system/lib/modules/*(anything in this folder) - system/bin/wpa_supplicant - system/lib/liboem_rapi.so - system/lib/libreference-ril.so - system/lib/libhardware_legacy.so - system/etc/init.qcom.wifi.sh - system/etc/firmware/wlan/*(anything in this folder) for turn on WiFi
and also u8800 needs system/etc/init.qcom.bt.sh - system/bin/hci_qcomm_init - system/bin/qmuxd (I'm not sure about this file) - system/bin/sdptool - system/bin/hciattach for turn on BT
And also,you need change init.rc and init.huawei.rc files in boot.img for turn on WiFi and BT.
Click to expand...
Click to collapse
Thanks a lot! Will try it all now!
Okey, now it's a bootloop on splash screen.
Edit: a bootloop was caused by some error in boot.img repack. Will try to repack it again now.
How to enable ADB when booting? On Aurora I could get kernel messages via ADB using adb shell cat /proc/kmsg. And now I really miss this feature.
Okey, great news! Wi-fi turned on, but the phone will fastreboot if I turn it off (framework crash I think) and wont turn on again until a full reboot. Also it isn't really working: no networks found.
No changes at all except Aurora kernel + setprop persist.sys.wifimac mac_param in terminal. After that wi-fi turned on, but even with that prop I have no wi-fi mac.
From that I understand all my problems are from some RIL or hardware libs that don't load or load with mistakes. So I need to know what exactly it can be and what libs are for what. Also I think it can be because of unedited init.rc's in ramdisk so I need to know what to edit in them. I've tried to look through them but I don't understand anything in it.
nagato.fm said:
Okey, great news! Wi-fi turned on, but the phone will fastreboot if I turn it off (framework crash I think) and wont turn on again until a full reboot. Also it isn't really working: no networks found.
No changes at all except Aurora kernel + setprop persist.sys.wifimac mac_param in terminal. After that wi-fi turned on, but even with that prop I have no wi-fi mac.
From that I understand all my problems are from some RIL or hardware libs that don't load or load with mistakes. So I need to know what exactly it can be and what libs are for what. Also I think it can be because of unedited init.rc's in ramdisk so I need to know what to edit in them. I've tried to look through them but I don't understand anything in it.
Click to expand...
Click to collapse
Which ROM are you fixing? Isn't CM10?
Nope, it's some desire z jb rom.
Code:
[email protected]:~# adb shell dmesg
- exec '/system/bin/sh' failed: No such file or directory (2) -
That's what I'm getting now. Already tried to fix this issue with some methods from google, no results. Even tried to adb-push bash from 4pda to system/bin and make symlinks, no results. Phone is in bootloop. Any ideas?
P.S.: sh is actually in both xbin and bin, so the problem is somewhere in the boot.img, right?
Have tried all kind of sorcery, still bootloops and exec '/system/bin/sh' failed: No such file or directory (2). Don't know why this is happening. Either /system mounts on boot in some wrong poing or init.rc is completely messed up. But I've checked everything connected to mounting partitions in all init files (except binaries) and gained nothing. I really need some explanation of what are these files for and what they do and what they MUST do.
If someone can give me answers or advices, please, do it now. Because all my ideas are over and I simply don't know now what to do.
EDIT: with aurora boot.img (no changes at all) results are the same except the message in terminal is now "/system/bin/sh: no such tool"
The system/bin/sh error is caused by not mounting /system properly. Check the init.rc files, it could also be in init.emmc.rc if it's a CM rom.
Find out where the on emmc-fs trigger is; if you can't find it, add it into one of the init.rc files.
Code:
on emmc-fs
# mount mmc partitions
wait /dev/block/mmcblk0p12
mount ext4 /dev/block/mmcblk0p12 /system rw barrier=1
wait /dev/block/mmcblk0p13
exec /system/bin/e2fsck -p /dev/block/mmcblk0p13
mount ext4 /dev/block/mmcblk0p13 /data nosuid nodev barrier=1 noauto_da_alloc
mount ext4 /dev/block/mmcblk0p6 /cache nosuid nodev barrier=1
Not sure that I am following this thread properly. I am just starting out with android devel in Fedora. Have you recompiled the WLAN module?
eyeconic said:
Not sure that I am following this thread properly. I am just starting out with android devel in Fedora. Have you recompiled the WLAN module?
Click to expand...
Click to collapse
Nope, I have no proper skills for that, sorry.
I still need some information
Mostly completely rewrote init. files and still no results.
According to this: (http://forum.xda-developers.com/showpost.php?p=30458679&postcount=1)
The Android Boot Process
Bootloader – In HD2’s case, Magldr or cLK – loads the kernel based on how you have configured the phone.
Kernel – The kernel (zImage) is loaded into RAM along with an initial ramdisk (initrd.gz), which initializes various devices (IO, memory, GPU, etc.), interrupts, and mounts the root file system (/). After this, the first user-space process called init is started.
Init – this is a binary file that is contained within the initrd.gz. The init binary processes init.rc and init..rc , along with other .rc files that are called by these two .rc files. Some of the key functions (from this thread’s perspective) in the order of their initialization/ execution are:
The init process follows the instructions in the init.rc and init.xyz.rc files and creates empty directories including /data. It then mounts the storage devices (partitions in the internal NAND (MTD)) to these empty directories. The NAND partition for system is mounted to /system, followed by the partitions specified for data, cache, etc. The directories for dalvik-cache (/data/dalvik-cache) are also created by the init process after mounting the specified device to /data.
The init process then starts various services including adb, service manager, Volume Daemon (vold) for media like SD Card (FAT partition). Most importantly, the zygote service which initiates the Dalivk-Cache is loaded in this sequence.
As we all know, Android is based on Linux. The boot sequence described above is common for all Linux machines – until the zygote stage. Core Android file like core, framework, services, IME, policy, etc. are executed from the Dalvik-Cache and hence Initialization of the Dalvik Cache is pretty much where Android comes into the picture
The sysinit/ run-parts part, which runs scripts from the /system/etc/init.d later the Zygote stage. No matter how this is done, Android has already started loading by the time the boot process comes to executing scripts in /system/etc/init.d
Click to expand...
Click to collapse
Click to expand...
Click to collapse
the error is in mounting nand partitions, but how can it past to starting adb when it fails on mounting system partitions? I don't understand this.