Hello,
Based off of Harsh 3.0.41 github
Changelog:
Version 0830 (MMDD)
OC/UV - 1.375GHz
Adjusted frequencies/voltages, if you have any suggestions...feel free to provide feedback...
Code:
750-250/800-438/850-625/900-813/950-1000/1035-1125/1120-1250/1205-1375
SetCPU users: I noticed that it kept the second core active...after I uninstalled, all was good Antutu CPU master is good alternative
Version 0821 (MMDD)
Commented out ZRAM and Morfics tweaks by way of 95vrooom in /system/etc/init.d (you may edit it to re-enable them if you wish)
EASY METHOD! - Will work for Temasek Kang – (cm7kang-G2x-133), CM 7.2 Stable (cm-7.2.0-p999), Eaglesblood 2.3.7 (EGB 02-13-12), HFP V2.2 (hellfirephoenixV2.2) and ROMs that have the GB vold.fstab that matches
ALL OTHER ROMs CANNOT use this version...for now...
Version 0820 (MMDD)
Linux 3.0.41
Compiled with Code Sourcery (CS) and Linaro (LIN) toolchains, choose your poison...
OC/UV - 1.4GHz p @ airnique23)
V(R) I/O Scheduler set as default (can be changed)
Includes ZRAM and Morfics tweaks by way of 95vrooom in /system/etc/init.d
Installation:
Recommended
CM 7.2 Stable...
CWM 5.0.2.0 (REQUIRED)
EASY METHOD
Will work for Temasek Kang – (cm7kang-G2x-133), CM 7.2 Stable (cm-7.2.0-p999), Eaglesblood 2.3.7 (EGB 02-13-12), HFP V2.2+ (hellfirephoenixV2.2 & 2.3) and ROMs that have the GB vold.fstab that matches
1. MAKE A BACKUP FIRST!!! Especially the internal memory (Not responsible for any mishaps :victory
2. Choose which one you want to download/install, CS or LIN version, (please provide feedback) just compiled with a different toolchain
3. Boot into CWM
4. Clear cache/dalvik cache
5. Install
6. Reboot (will take awhile to boot...be patient)
ALTERNATIVE (ALT) METHOD
1. MAKE A BACKUP FIRST!!! Especially the internal memory (Not responsible for any mishaps :victory
2. Choose which one you want to download/install, CS or LIN version, (please provide feedback) just compiled with a different toolchain
3. Please check /system/etc/vold.fstab and your internal sdcard (emmc) has an 8 instead of a 9 (change to 8 if its a 9 and make sure vold.fstab permissions are rw-r--r-- after saving)
4. Boot into CWM
5. Clear cache/dalvik cache
6. Install
7. Reboot (will take awhile to boot...be patient)
Known bugs:
Reboot/Reboot recovery work 90% of time. (same as Harsh's)
Button Panel LED backlights cannot be turned off (will cause phone to lag...BAD...still looking into it)
Wifi Calling app may get an Invalid Sim error after first installing the kernel (if you use it)...a restart fixes this
Titanium Backup might freeze when you run it after you flash this, go to the Applications > Force stop and clear data...should be good to go...it may affect other applications that reference partitions FYI...
Have slow GPS locks? try this
Important!
Be mindful when you OC/UV, all our phones are different, experiment to find your phones optimal setting...
Don't like the kernel?
Complete Steps 4 and 5, and reinstall your ROM you are using to avoid any issues...
What's the different between Code Sourcery and Linaro?
Code Sourcery and Linaro
Lagging after installing?
You probably already have a ROM or an app that runs tweaks...delete 95vrooom and reboot...may have to clear dalvik and cache and fix permissions if your are experiencing data drops...(thanks nycelitemaster & BigDog!)
Just be aware if you have disabled the LED button backlights...you will experience serious lagging...
Received "Damaged SD Card" message or stuck in recovery?
You will have to NVFlash back to stock...then NVFlash CWM 5.0.2.0...then you can restore your backup or reinstall your ROM...(thanks hypemanisus!)
I don't wanna NVFlash 5.0.2.0, what can I do?
CWM 5.0.2.8 will break recovery...I have not tested the other recoveries like CWM touch or TWRP...be warned...you MAY need to perform the "Damaged SD Card" steps...
Why do I have to edit the vold.fstab file? I never had this issue with ICS
ICS vold.fstab already has the 8...
Code:
#######################
## Regular device mount
##
## Format: dev_mount
## label - Label for the volume
## mount_point - Where the volume will be mounted
## part - Partition # (1 based), or 'auto' for first usable partition.
## - List of sysfs paths to source devices
######################
dev_mount sdcard /mnt/sdcard auto /devices/platform/tegra-sdhci.2/mmc_host/mmc1
dev_mount emmc /mnt/emmc 8 /devices/platform/tegra-sdhci.3/mmc_host/mmc2
GB vold.fstab has a 9...
Code:
#######################
## Regular device mount
##
## Format: dev_mount
## label - Label for the volume
## mount_point - Where the volume will be mounted
## part - Partition # (1 based), or 'auto' for first usable partition.
## - List of sysfs paths to source devices
######################
dev_mount sdcard /mnt/sdcard auto /devices/platform/tegra-sdhci.2/mmc_host/mmc1
dev_mount emmc /mnt/emmc 9 /devices/platform/tegra-sdhci.3/mmc_host/mmc2
Compared to recovery.fstab...for GB and ICS...they're the same...
Code:
# mount pointfstypedevice[device2] fstype2
/recoveryemmc/dev/block/mmcblk0p5
/bootemmc/dev/block/mmcblk0p5
/cacheext4/dev/block/mmcblk0p2
/dataext4/dev/block/mmcblk0p7
/sdcardvfat/dev/block/mmcblk1p1
/emmcvfat/dev/block/mmcblk0p8
/systemext4/dev/block/mmcblk0p1
Still having issues?
Provide the ROM you are using and what the issue is...and a log if possible...
Credits:
Harsh (for allowing me to share)
TeamDouche
nycelitemaster (for testing...thanks sir!)
Everyone else who made 3.0 possible...
djvoleur said:
Hello,
Based off of Harsh 3.0.41 github
Changelog:
Version 0820 (MMDD)
Linux 3.0.41
Compiled with Code Sourcery (CS) and Linaro (LIN) toolchains, choose your poison...
OC/UV - 1.4GHz p @ airnique23)
V(R) I/O Scheduler set as default (can be changed)
Includes ZRAM and Morfics tweaks by way of 95vrooom in /system/etc/init.d (If you are experiencing lags, try deleting 95vrooom and reboot)
Installation:
Recommended but not required
CM 7.2 Stable
CWM 5.0.20
(If you are having an issue with the kernel, please provide what ROM and CWM version or other recovery version you are using)
1. MAKE A BACKUP FIRST!!! (Not responsible for any mishaps :victory
2. Choose which one you want to download/install, CS or LIN version, (please provide feedback) just compiled with a different toolchain
3. Please check /system/etc/vold.fstab and your internal sdcard (emmc) has an 8 instead of a 9 (change to 8 if its a 9 and make sure vold.fstab permissions are rw-r--r-- after saving), especially if this is your first time otherwise you will have to NVFlash back to stock...
4. Boot into CWM
5. Clear cache/dalvik cache
6. Install
7. Reboot (will take awhile to boot...be patient)
Known bugs:
Reboot/Reboot recovery work 90% of time. (same as Harsh's)
Button Panel LED backlights cannot be turned off (will cause phone to lag...BAD...still looking into it)
Wifi Calling app may get an Invalid Sim error (if you use it)...a restart fixes this
Titanium Backup might freeze when you run it after you flash this, go to the Applications > Force stop and clear data...should be good to go...it may affect other applications that reference partitions FYI...
Have slow GPS locks? try this
Important!
Be mindful when you OC/UV, all our phones are different, experiment to find your phones optimal setting...
Don't like the kernel?
Complete Steps 4 and 5, and reinstall your ROM you are using to avoid any issues...
Credits:
Harsh (for allowing me to share)
TeamDouche
nyelitemaster (for testing...thanks sir!)
Everyone else who made 3.0 possible...
Click to expand...
Click to collapse
Thanks, will try linaro build and report back with results.
*linaro working like a champ
Sent from my LG-P999 using xda app-developers app
HFP v2.2 and system boots fine. When it comes up I get a damaged SD Card message which is in fact untrue. Rebooted, cleared dalvik and cache, rebooted again all with no change. Flashed back the the backup I made prior to flashing this kernel and all is well.
Darkseider said:
HFP v2.2 and system boots fine. When it comes up I get a damaged SD Card message which is in fact untrue. Rebooted, cleared dalvik and cache, rebooted again all with no change. Flashed back the the backup I made prior to flashing this kernel and all is well.
Click to expand...
Click to collapse
This happens when you don't complete step 3...
I did that and it still showed Damaged SD card. Was able to restore from backup and all is well. Dunno maybe dumb luck?
Darkseider said:
I did that and it still showed Damaged SD card. Was able to restore from backup and all is well. Dunno maybe dumb luck?
Click to expand...
Click to collapse
What recovery are you using?
Sent from my LG-P999 using Tapatalk 2
Oh sh t.... will be trying it out...ty harsh and dj
Sent from my LG-P999 using xda app-developers app
Using linaro
Sent via G2X-SINGH-UI
nycelitemaster said:
Using linaro
Sent via G2X-SINGH-UI
Click to expand...
Click to collapse
Hehe
Sent from my LG-P999 using Tapatalk 2
I wanna try this out, but I hate the LED notifications
Sent from my LG-P999 using xda premium
Tried CS version, changed void.fstab (permissions verified), wiped dalvic and cache. Froze at boot screen of the ROM, pulled battery. It did it again. Flashed faux's current kernel, booted fine. Harsh's kernels don't seem to like me anyway. Oh well.
Sent from my Android powered coffee coaster.
sleepingturtle said:
Tried CS version, changed void.fstab (permissions verified), wiped dalvic and cache. Froze at boot screen of the ROM, pulled battery. It did it again. Flashed faux's current kernel, booted fine. Harsh's kernels don't seem to like me anyway. Oh well.
Sent from my Android powered coffee coaster.
Click to expand...
Click to collapse
What recovery do you have?
FatalityBoyZahy said:
I wanna try this out, but I hate the LED notifications
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
You can turn off the LED notifications...it's just when the phone is on...or there's a response to the screen...or when the screen shuts off...that i'm still looking into
djvoleur said:
What recovery are you using?
Sent from my LG-P999 using Tapatalk 2
Click to expand...
Click to collapse
CWM 5.0.2.8
Darkseider said:
I did that and it still showed Damaged SD card. Was able to restore from backup and all is well. Dunno maybe dumb luck?
Click to expand...
Click to collapse
Just unmount and mount it back from settings the message disappears
Sent from my -P999 using xda app-developers app
djvoleur said:
Hello,
Based off of Harsh 3.0.41 github
Changelog:
Version 0820 (MMDD)
Linux 3.0.41
Compiled with Code Sourcery (CS) and Linaro (LIN) toolchains, choose your poison...
OC/UV - 1.4GHz p @ airnique23)
V(R) I/O Scheduler set as default (can be changed)
Includes ZRAM and Morfics tweaks by way of 95vrooom in /system/etc/init.d (If you are experiencing lags, try deleting 95vrooom and reboot)
Installation:
Recommended but not required
CM 7.2 Stable
CWM 5.0.20
(If you are having an issue with the kernel AFTER installing, please provide what ROM and CWM version or other recovery version you are using)
1. MAKE A BACKUP FIRST!!! (Not responsible for any mishaps :victory
2. Choose which one you want to download/install, CS or LIN version, (please provide feedback) just compiled with a different toolchain
3. Please check /system/etc/vold.fstab and your internal sdcard (emmc) has an 8 instead of a 9 (change to 8 if its a 9 and make sure vold.fstab permissions are rw-r--r-- after saving), especially if this is your first time otherwise you will have to NVFlash back to stock...
4. Boot into CWM
5. Clear cache/dalvik cache
6. Install
7. Reboot (will take awhile to boot...be patient)
Known bugs:
Reboot/Reboot recovery work 90% of time. (same as Harsh's)
Button Panel LED backlights cannot be turned off (will cause phone to lag...BAD...still looking into it)
Wifi Calling app may get an Invalid Sim error (if you use it)...a restart fixes this
Titanium Backup might freeze when you run it after you flash this, go to the Applications > Force stop and clear data...should be good to go...it may affect other applications that reference partitions FYI...
Have slow GPS locks? try this
Important!
Be mindful when you OC/UV, all our phones are different, experiment to find your phones optimal setting...
Don't like the kernel?
Complete Steps 4 and 5, and reinstall your ROM you are using to avoid any issues...
Credits:
Harsh (for allowing me to share)
TeamDouche
nyelitemaster (for testing...thanks sir!)
Everyone else who made 3.0 possible...
Click to expand...
Click to collapse
SWEEET!!!!! :victory:
Thanks a million
Just flashed the Linaro version. So far, so good.
I have been running it hard through back-to-back benchmarking tools (Nenamark2, Antutu, Quadrant) trying to get the phone hot and unstable. No instability to report yet! My phone even seems to be staying cooler (and using less battery) than it would at 1400Mhz on Faux 052 stable. Gonna run this config for at least 2 days more before reporting back. Thanks mucho to Harsh and dj. Awesome job on the kernel and the dedication to this thread djvoleur!!!
Is it my imagination, or are landscape/portrait transitions faster than with other kernels? (I don't mean the smoothness of the animation, but the delay between when the device is rotated and the start of the screen transition)
Temasek build 130
CWM 5.0.2.0
Darkseider said:
CWM 5.0.2.8
Click to expand...
Click to collapse
I have no problems with Temasek Rom and CWM 5.0.2.0
5.0.2.0
Tried the Linaro build. Booted fine. I'll play with this for a few days.
I guess the CS build doesn't like me.
Sent from my Android powered coffee coaster.
5.0.2.8 is a port from the P990...I have a feeling that the ported version used the P990 recovery.fstab
Code:
# mount pointfstypedevice[device2] fstype2
/recoveryemmc/dev/block/mmcblk0p7
/bootemmc/dev/block/mmcblk0p5
/cacheext4/dev/block/mmcblk0p2 NULL ext3
/dataext4/dev/block/mmcblk0p8 NULL ext3
/sdcardvfat/dev/block/mmcblk1p1 /dev/block/mmcblk1
/emmcvfat/dev/block/mmcblk0p[B]9[/B]
/systemext4/dev/block/mmcblk0p1 NULL ext3
Once the vold.fstab is changed to 8 for the emmc, it would make the internal emmc not mount on boot, hence the Damaged SD Card message...that's my assumption...
So be weary of 5.0.2.8...and it looks like if you reboot into recovery you will need to NVFlash
Related
data2whatever v0.2
UPDATE: For the new test version of v0.3 and v0.4 look at the end of the post.
Features:
- Supports: Ext2, Ext3, Ext4 (and if kernel supports it: ) btrfs, ReiserFS
- Supports loop device as optional addon (as siberes data2sd)
- Flashable zip for many app2sd ROMs (no long setup required)
- It does a e2fsck (disk check) on every boot and creates a logfile on the sdcard (/sdcard/e2fscklog.txt)
- looks nice if you do a logcat on boot
- no "settings lost on reboot" bug like in my old or siberes script
- changes the scheduler for the sd-card and internal to noop for better performance on sd.
- Nandroid Backup of EXT2/3/4 external with AmonRa 2.0.0.1 or any clockwork recovery.
- Removes the common app2sd scripts on its own
Requirements
- A second partition (same as app2sd - Min 512 mb - 1024mb is highly recommended - max 2048 MB or there will be issues with market) in any format (as long as the kernel supports - ext2/3/4 support is default in most kernels - Ext4 or ReiserFS is recommended).
- An app2sd or non app2sd ROM (data2sd versions wont work) (this SHOULD work with most or at least many ROMs . Roms that are confirmed to work can be found in the post below. Please report to me it it works or not so i can update this thread. If it doesn't work i try to make it compatible asap. )
Installation
1.) Full wipe (at least needed on first installation)
2.) Flash the app2sd Version of the ROM of your choice
3.) DONT REBOOT
4.) If you rebooted then start over at 1.)
5.) flash the attached "data2whatever.zip"
6.) now reboot
ADDITIONAL INFO: Even without "life on the edge" you should watch the first 4 "don't"s of "life on the edge". The normal script use the same disk safety methods as NTFS on Windows or EXT4 on linux. But as you know you shouldnt just switch off the computer because there can still be issues in very rare cases. Reboots with tools like "snqs power menu" is the same as a batterypull (or pulling the ac plug on PC) and this isn't good in general (and this also applies for using it with app2sd). If you want to go to recovery just make a normal shutdown and switch the phone on with "volume down" button pressed.
Optional life-on-the-edge add on
EDIT: Life on the edge causes reboots. Don't use it for now.
This patch has the same effect as sibere's and ownhere's script (loop device - the way ownhere does in v4 doesnt work though). Other than those scripts it this addon doesnt need any repartitioning or other setup (like FAT or a third partition) and can simply be installed or removed with a flashable zip. All you need for this is a normal ext 2/3/4 partition (as above ^^). Ext4 is recommended for this (as above) since it is the fastest of those 3. This patch is more risky than normal ext3/4 considering the possibility of data loss. If you want to use this add-on you should watch the following (this also applys to ownheres and sibere script and is NOT more risky than their scripts):
- DON'T use the reboot of snq's powermenu (or any other reboot app)
- DON'T use anything in the "ROM Manager" that makes it reboot.
- DON'T do adb reboot / abd reboot recovery / adb reboot bootloader
- DON'T pull the battery while the phone is on (this should be obvious)
- DON'T remove the "sync" mount options for the Quadrant "boost" (this is a fake boost anyway)
All of this is like a powerloss for the sd-card and has a high change of data corruption.
From my test with this i give you an estimate what can happen if a powerloss occurs or any of the 5 points above happen:
- 50% general chance of corruption that will be autofixed on boot (not a problem)
- 10% chance of forcecloses after reboot of some apps (this can be fixed by deleting the app data or restoring it with titanium (or other) backup)
- REALLY tiny chance (didnt happen for me in over 40 "simulated" powerlosses) that partition gets corrupted (needs complete repartitioning of the microSD so all data on it will be gone then)
As long as you watch the 5 points above and as long as you don't drop the phone and the battery jumps out this will be safe.
Installation of the addon:
- Flash the "life-on-the-edge.zip" any time after you installed "data2whatever".
Installation of the addon:
- Flash the "life-on-the-edge-UNPATCH.zip" any time after you installed "data2whatever" and the addon. (this will revert back to the normal script)
Personal remark: While this is a improvement over normal ext4 it is not the "holy-grale" of a data2sd lag fix. I'm not using this myself and use a ReiserFS as second partition instead which is more safe and completly feels the same as a "loop" device considering performance.
Further Plans
- Changes for the mount options of the internal YAFFS2 Partition to optimize the speed of the "dalvik-cache" (have to look into YAFFS2 what can be done)
- Make Roms that doesn't work yet compatible to this
Thanks:
- cyanogen who made app2sd+ in the first place.
- sibere and ownhere who started all the data2sd.
- supercurio and Unhelpful of SGS' Voodoolagfix (#Project-Voodoo on freenode) for their helpfull script tipps.
- Coutts99 and Neophyte for their Kernels.
- woti23 for all those test's in this thread.
- All devs of XDA in generall for all this nice stuff that is done here
UPDATE: Test version of v0.3 and v0.4:
BOTH NEED A FULL WIPE BEFORE INSTALLED FOR THE FIRST TIME.
Please make a logcat of the first boot. This can help me to find possible issues.
This version now checks if your second partition is aligned and if not it will ERASE it and recreate it aligned. You will find more info about alignment later here (in the meantime you can google "ssd alignment" to get some info).
WARNING: THIS WILL ERASE THE SD-EXT PARTITION IF IT IS NOT ALIGNED. On top of that there is a little risk that it messes up the partition table. Although i made a lot of test with this and added busybox to assure compatibility there could still issues with it. If something should go wrong in recreating the partition you may have to REPARTITION the COMPLETE Sd-card. So make a BACKUP OF ALL YOUR DATA ON THE SD before you test this .
Additional info: Don't let yourself get confused by the many deleting messages on install. The update script tries to erase:
- busybox (newest version gets installed afterwards)
- 4 different versions of app2sd scripts
- dalvikcache2cache script
- the 3 binaries included (e2fsck, tune2fs, mkfs.ext4)
- 3 possible symlinks for the binaries
- mtab file
Everything that is erased gets either installed afterwards (busybox, etc ...) or isn't needed (app2sd scripts).
Please post the alignment log if you testet this. This log can be found on the sdcard ( /sdcard/sd-ext-alignment-log.txt).
==================================================================================
changelog
0.4d test release
- If the partitions gets aligned it will be formated with ext3 now instead of ext4 so it works with ROMs without ext4 kernel support.
0.4c test release
-fixed a rare issue that could happen on alignment if a partition has set the bootflag.
v0.4b test release
- fixed and Oxygen 2.0 RC4 related issue:
- renamed the "99complete" to "991complete" to prevent similiar issues on other AOSP ROMs that use individual properties.
v0.4 test release
- dalvik cache is now left internal. This should spread i/o and thus speed things up a bit.
- change scheduler to "deadline" if the kernel supports it
- changed logging: One file (data2whateverlog.txt on sdcard) for alignement and fsck with more info (thx moebius83)
- In case there is a swap partition (mmcblck0p3) this will also get aligned.
v0.3 test release
- this version will now recreate your sd-ext partition if it is not aligned (format: ext4)
- fixed the mtab error that could cause issues in some cases
- added busybox v1.17.2 to assure compatibility.
- added support for swap partition (if kernel supports it and partition 3 exists)
- removing more stuff on install (to make sure there are no old symlinks)
0.2e
-fixed an issue caused by the s-off fix.
0.2d
-fixed the cm6 fix
v0.2c
-fixed a bug that made this only work with S-OFF. (i totally forgot that system can't be mounted rw as default )
v0.2b
- fixed a typo of the last fix . This could have caused issues on leedroid. (thanks woti)
- added the patch for CM6 (thanks iinga)
v0.2
- fixed a syntax error making the script not working at all
- fixed a bug that would have occured on leedroid if it would have worked ^^
------------------------------------------
data2whatever v0.1 (dec 23.)
-completly rewrote of the data2ext script
Confirmed to work with:
- LeeDroid 2.3b A2SD (life-on-the-edge may not work)
- MIUI 0.12.18 R3
- Gingerbread Oxygen RC2
- Ginger Villain ROM
- CM6
- MidianUI r2e
- Desire stock (with init.d support enabled through ramdisk - more info)
Don't work yet:
(about HD roms in general. They will be the ones with most issues because they use external space for system stuff because of the size of the HD Rom - ill still try to make my script work with them)
- robocik's Z v06
- ReflexTSenseHD 1.5
nice work man
im using miui currently and it hass 04apps2sd instead
is this the same thing?
Very nice work.... and it kinda confirmed what i've been thinking all the time about it. Ppl thinks it speeds up your phone! Still this is of very good use if u want alot of space for apps
Rastaman-FB said:
nice work man
im using miui currently and it hass 04apps2sd instead
is this the same thing?
Click to expand...
Click to collapse
Check my 2nd post. I just edited it.
I love you.
But still the best way is to integrate it w/ ROM
where is the download link
ghmail2 said:
where is the download link
Click to expand...
Click to collapse
This
10char
Rafa91 said:
This
10char
Click to expand...
Click to collapse
a joke?
ghmail2 said:
where is the download link
Click to expand...
Click to collapse
+1
10char
Go here ->http://forum.xda-developers.com/showpost.php?p=9697369&postcount=7229
but i don't know if it's RCMixHD specific.
+1
Is it a joke or not?
ghmail2 said:
where is the download link
Click to expand...
Click to collapse
D'oh .... sry ... when i finished the post i went eating ... i had the fealing i should have checked it again
just wait omg ...
anko184 said:
Go here ->http://forum.xda-developers.com/showpost.php?p=9697369&postcount=7229
but i don't know if it's RCMixHD specific.
Click to expand...
Click to collapse
This one also works. All 3 Roms i posted use the same script
So generally, it should work on any rom with CM6/AOSP based A2SD script? Mkay...
ghmail2 said:
a joke?
Click to expand...
Click to collapse
It wasn't there before xD
Didn't get to experimenting with btrfs today, will test it tomorrow
Sent from my HTC Desire using XDA App
@melethron great work man, but I will remain to my opinion that data2sd(ext) is bad for so many reasons. But it is good to have choices.
But nevertheless your work is apreciated
Hi, having small issue here, trying to install this on the baadnwz rc2 hd rom, following all the steps, when i finally restart and everything boots up as it should, it freezes on the white htc screen before it asks you to select your network provider and force closes.
Anyone have a solution?
This thread is reserve for nightly build of CyanogenMod Rom for HTC Desire
CyanogenMod is a free, community built distribution of Android 2.3 (Gingerbread) which greatly extends the capabilities of your phone.
Code:
** These CyanogenMod builds are highly experimental and unsupported.
**
** Please refrain from submitting bug reports for any issues
** you may encounter while running one of these builds.
**
** Submitting bug reports on nightly builds is the leading
** cause of male impotence.
What are Nightly build? Auto compiled build of the latest CyanogenMod source from github. This version change each night and aren't officialy supported.
If you find bugs/issues you can/must discuss here (do not submit nightlies bug on CyanogenMod issue tracker).
Warning : Not for new user, flash this build only if you know what you are doing !!!
INSTRUCTIONS:
- First time flashing CM 7 to your Desire (or coming from another ROM)?
1. Root your device and install Clockwork Recovery.
2. Do a Nandroid backup!
3. WIPE (wipe data/factory reset + wipe cache partition)
4. Install the ROM
5. Optionally install the Google Addon
- Upgrading from earlier CM7?
1. Do a Nandroid Backup!
2. Install the ROM (your Google apps will be backed up automatically)
There are no Google Apps bundled with CM ROMs, because Google asked Cyanogen to remove copyrighted apps, after flashing rom don't forget to flash Google Addon package if you want it.
Latest version: http://download.cyanogenmod.com/?device=bravo
before flash is recommended to check the md5sum
CyanogenMod Enhancement:
ChangeLog / Twitter
Device specific ChangeLog by igor.tonky
Please visit the CyanogenMod Wiki for step-by-step installation walkthroughs and tons of other useful information.
Thank you to EVERYONE involved in helping with testing, coding, debugging and documenting! Enjoy!
cm7 is in a development stage and for the first installation i recommend to:
1) install rom
2) reboot, skip setup wizard and setup your access point
3) reboot recovery and install gapps
4) start and follow setup wizard, when requested select desired gapps to be downloaded from market
Battery drain issue:
Set wifi sleep policy to never
settings -> wireless & networks -> wifi settings
press menu -> advanced and set wifi sleep policy to Never
press menu -> save
RIL issue:
Switching RIL is cause of know network problem:
* Unable to make a network scan
* Data connection die on asleep (only for some carrier)
CM7 HBOOT by Alpharev | xda thread
Change partition table size 130/5/302 (system/cache/size)
Require nightly #18 or newer
Upgrade instruction:
1) Nandroid backup in recovery.
2) Verify the MD5SUM of the file you downloaded against the one in the table.
3) Flash HBOOT with your phone in fastboot mode (Back+POWER) -> 'fastboot flash hboot bravo_alphaspl-cm7.img'
4) 'fastboot reboot-bootloader'
5) 'fastboot erase cache'
6) Boot recovery, wipe everything, advanced restore system & data, install CM7 again (same version or a newer one).
Legacy App2SD Addon:
CyanogenMod do not officially support a2sd, i'm working on it because desire (not only) desperatly need it (cutted down Firerat script)
Bootloop free: bind mount do not cause bootloop
Zero Maintenance: no maintenance required after ROM update
Other a2sd can be used, this is just the easiest way: use recovery to partition your SD then install cm7_legacy_a2sd_rX-signed.zip
By default only App will be moved on SD
Optionally Cache and Data can be moved to SD, but is not recommended (guide)
Require GB Nightly #7 or newer
It's recommended to set the install location to "Internal" under Settings -> CyanogenMod -> Application Settings -> Install location
Before install check if /sd-ext is mounted, "quick system info" under A2SD Storage should report Total and Free space, if it report "information not available" format sd-ext from recovery.
r3: improved installation process (i hope)
r2: added data2sd and cache2sd as options
r1: first release
General App2SD Q&A:
Q: A2SD is recommended?
A: Internal storage perform better than SD, install A2SD only when low disk space warning happen
Q: How to check if is working?
A: run:
adb shell
df -h | grep /dev/block/mmcblk0p2
output should be
Code:
Filesystem Size Used Available Use% Mounted on
/dev/block/mmcblk0p2 751.9M 146.9M 566.8M 21% /sd-ext
/dev/block/mmcblk0p2 751.9M 146.9M 566.8M 21% /data/app
/dev/block/mmcblk0p2 751.9M 146.9M 566.8M 21% /data/app-private
Q: I have installed a2sd addon but now i get low space warning again, why?
A: by default a2sd addon move only app, this is fine for most user but some user with more application have to move also cache and/or data.
Cache2SD can be enabled with
adb shell
/sd-ext/userinit.d/10cache2sdext-binds enable
Data2SD
adb shell
/sd-ext/userinit.d/11data2sdext-binds enable
reboot when prompted
HBOOT
All alpharev's hboot are compatible except the oxygen version
CM7 version is recommended ~270MB for app (stock 110MB, N1 195MB)
HowTo
Perform automatic backups of files in /system/ while (re-)flashing CyanogenMod
useful link
http://goo-inside.me/google-apps/
md5:
18ef81c567398a93183aff65a41a1565 cm7_legacy_a2sd_r3-signed.zip
murdock's semi official nightly replacement drugs
update 31.05.2011: buildbot is down due to hdd crash. might take a few more days to return - so here is an interims nightly for you:
mirror1: cm_bravo_full_teamdesire-20110601-1925.zip size: 84M (88037737 bytes)
mirror2: cm_bravo_full_teamdesire-20110601-1925.zip md5sum: 38591bab5df5d8f57e714f7888567bdb
Kali- said:
CyanogenMod is a free, community built distribution of Android 2.3 (Froyo) which greatly extends the capabilities of your phone.
Click to expand...
Click to collapse
You mean Gingerbread not Froyo - pedantic I know!
Great work though by the way - excellent ROM!
sykomaniac said:
You mean Gingerbread not Froyo - pedantic I know!
Great wrok though by the way excellent ROM!
Click to expand...
Click to collapse
C&P fail
10 char
andQlimax said:
I was waiting for this thread lol
Any Radio / RIL recommended?
Click to expand...
Click to collapse
no
any 5.x should work
Nice looking forward to follow this thread
Well I am not superseeding the Great Kali's saying about A2sd but Dark Tremors App2SD works ok with CM7. Just installed it onto CM7. Working great on my CM7.
Niiiceee, great work team !
rover.prince said:
Well I am not superseeding the Great Kali's saying about A2sd but Dark Tremors App2SD works ok with CM7. Just installed it onto CM7. Working great on my CM7.
Click to expand...
Click to collapse
Never tested but for what i know DT need to be flash after any update and is not bootloop free
Thank's for report
before someone ask
Oxygen HBOOT do not work, system is too small (cm7 require other 20mb)
we are working with alpharev for a CM7 specific partition layout but there are some thing concerning the /cache shrinking that requires to be developed and tested
not sure if this is a market issue or titanium backup but my apps don't appear as installed on the market after a restore. btw is the sd-ext issue fixed in cwm? read from the cwm thread of some people having issues about sd-ext not being backed up.
Kali- said:
we are working with alpharev for a CM7 specific partition layout but there are some thing concerning the /cache shrinking that requires to be developed and tested
Click to expand...
Click to collapse
Great, looking forward to it! I'm using the N1 Layout atm and it my cache is under 50MB
Code:
Filesystem Size Used Available Use% Mounted on
/dev/block/mtdblock4 95.0M 48.4M 46.6M 51% /cache
I guess a bit above 50 would be good?
btw, what would happen if the cache is full? Would it just get really slow?
MrDevil said:
btw is the sd-ext issue fixed in cwm? read from the cwm thread of some people having issues about sd-ext not being backed up.
Click to expand...
Click to collapse
just tested and the one i posted do not backup/restore sd-ext
i will post a working one later, i just noticed that my patch is still under review
Kali- said:
Never tested but for what i know DT need to be flash after any update and is not bootloop free
Thank's for report
Click to expand...
Click to collapse
I am using it personally, I have done the installation what I did.
1. Installed CM7.
2. Installed G.Apps
3. Started Phone, Installed All Apps
4. Restored Some Apps via Titanium Backup ==>Ended Up via Low Storage
5. Installed DT
6. Executed CacheSD
7. Phone Rebooted (Took Some Time to Boot)
Voilla I am happy.
cTrox said:
Great, looking forward to it! I'm using the N1 Layout atm and it my cache is under 50MB
Code:
Filesystem Size Used Available Use% Mounted on
/dev/block/mtdblock4 95.0M 48.4M 46.6M 51% /cache
I guess a bit above 50 would be good?
btw, what would happen if the cache is full? Would it just get really slow?
Click to expand...
Click to collapse
we are working for something like 5MB or less
the problem is about download and market.
for sure tmp file are stored on cache and if file size is bigger then free space download fail, not sure if there are other issue
rover.prince said:
Voilla I am happy.
Click to expand...
Click to collapse
this is the most important thing
Kali- said:
this is the most important thing
Click to expand...
Click to collapse
Kali I Love U and CM Team. Great Work with all thumbs UP.
Kali- said:
just tested and the one i posted do not backup/restore sd-ext
i will post a working one later, i just noticed that my patch is still under review
Click to expand...
Click to collapse
thanks for the info. looking forward to a rc.
will try to reflash later and restore apps with mybackup and see if it's a market or titanium issue.
How long will it take before CM7 is released in stable mod?
I'm getting tired of using Oxygen 2.0 and its bugs
This project is now discontinued and will recieve no further updates nor support.
First of all, thanks petter (https://github.com/havlenapetr), Czech Samsung Galaxy developer, for idea and source codes.
What do I mean?
You have one ROM in internal memory as usual, and another one in folder on SD card ext partition. You can easily switch between them - just move rom from ext partition to some backup folder.
See guide in second post
How is it done?
Lets look on how android boots - its (roughly) like that:
1. Bootloader - forks between recovery, fastboot and normal boot
2. Linux kernel - Unpacks its initrd, loads drivers and many more things, not important now
3. Init - kernel runs this program, which mounts android partitions, sets correct permissions to files, starts services, and in the end, starts android itself
4. Android - Dunno much about it yet, anyway not important now
So, what we need to do is mount something else than internal memory in init. Init parses & runs simple scripts, which makes it simpler to mount sdcard folders.
We need to add mknod and bind mounting to init binary. Unfortunately, we dont have sources of init modified by LG (that thing is three(!) times larger than init compiled from AOSP, what the hell is in there?!). That is solved by running modified init, which parses "preinit.rc" with mounts and then runs LG init.
Commit: https://github.com/Tasssadar/init/commit/aa3604ca90f5ef9b688fdc2e3cc865aa29a54809
preinit.rc: https://github.com/Tasssadar/init/blob/b4e701e8bc4831fadbefa64be48300139dcc2023/ramdisk/preinit.rc
This would be all, if original LG init would not remount /system and /data from internal memory. Also, nearly every ROM has different init.rc, and wont boot without it.
To solve this, I created "import_boot" command in init, which copies *.rc files and LG init from ramdisk(well, its only folder with these files extracted from ramdisk for now) on sdcard ext partition. This command also puts comments out every line with mount /data, /system or /cache in init.rc file, so LG init wont remount them.
Commit: https://github.com/Tasssadar/init/commit/dc3fa50d65d1221a4fb819d8ee616765ee043e83, https://github.com/Tasssadar/init/commit/f7bc141b1e4b7d214e49d4bb005c71237231436c and https://github.com/Tasssadar/init/commit/1cde6b6a093d4ac1f961e610c5229605bc517b52
Format of ROM on ext partition:
All files from paritions in internal memory copied to sd ext partition with preserved owners and permissions(!).
So, when I copy data, I do "cp -r -p /data/* /sd-ext/multirom/rom/data/" (I suggest to run this via adb shell while in recovery).
Currently, I mount /system, /data and /cache from sdcard. If one or more of these folders does not exist, its equivalent from internal memory is used.
It would be nice to have *.img files from nandroid backups instead of this, but as far as I know, they cant be just mounted.
As for *.rc files, I put them into /sd-ext/multirom/rom/boot folder. I would like to just copy boot.img and extract files in init, but I did not find way to extract it when I have hardly STL usable in init. I'd like to use kernel's internal decompressor, but I dont know how.
Limitations
- Both ROMs must be compatible with one kernel - kernel is already loaded in init
- ROMs must be for same baseband, obviously
- Kernel modules(wifi, for example) of both ROMs must be compatible with one kernel. That can be easily solved by copying modules from one ROM to another, though.
- It will be slower than internal memory.
Integration with recovery
Definitely possible & usefull. This is integration in my modified AmonRa recovery: https://github.com/Tasssadar/Amon-R...mmit/bd0232f7379993c296b0223973b81e8c55dc3ee2
Security risk
/system on sdcard can't be mounted read-only - I'd have to mount whole sdcard read-only. This is possible security hole, but you cant do much without root anyway, because of permissions. And if you have root, it does not matter if its read-only or not.
Conclusion
So, it is possible to have dual-boot. You can use it to develop ROMs(you can directly edit data in /data and /system), as backup ROM when you are testing something in internal memory which does not boot, and you need to call someone or when our devices will be so old that bad blocks in internal memory wont allow us to boot
But, as you can see, It is not something that average user could do, at least not yet. Maybe I could modify recovery to do everything for the user (copy data from /system, /data and /cache, extract *.rc files from boot) and create some flashable ZIPs which would modify the init.
But there are some problems - some ROMs may not be compatible with this and there are multiple recoveries out there, but theres not single one which is only for our phone - both AmonRa and ClockworkMod are developed for wide range of devices. Yes, both of them can be modified, but I doubt they creators would accept such inflexible and device-specific thing.
What do you think, is it worth it?
Tested ROMs (first one is in internal memory, second one is on SDcard)
Working:
Megatron and stock v10a ROM - stock rom is slow
Megatron and devoid #froyo-final - like ten times faster than stock xD
LightRom(2.2.2) and devoid #froyo-final (and vice versa)
Megatron and Megatron - both ROMs can have a2sd
Megatron and Mik's CM7 6.5.8 - since v2
Gingerbread 2.3.4 from Optimus Net and CM7 6.6.1 (thx eduardogouveia for testing)
Stock 2.2.2 and CM7 6.5.8 (thx eduardogouveia for testing) - if you have ext4 partition, you need custom kernel for stock ROM.
.void 2.3.4 and stock V20B (thx diazneoones for testing)
CM7 6.5.8 and .void 2.3.4 (thx diazneoones for testing)
CM7 nightlies and Lupohirp's СM9 (thx aquapp for testing)
Not working
None found yet, but when CM7 is on sdcard, it looses root. Trying to figure out why. - fixed in v10
PS: I hope I explained it correctly, not exactly good at this. Do not fear to ask, if you don't understand something.
OK, here goes guide for average user. This is still highly experimental feature, keep that in mind. Backup, backup backups and backup them to PC, read whole guide first, I am not responsible for your bricked phone etc.
GUIDE:1. Requirements
Ext4/Ext2/Ext3 partition on SDcard big enough to hold all files from /system and /data, which is from 170mb to 400mb (depends on ROM and apps installed), so I think 512mb partition is minimum (if its 90% or so free).
Modified recovery. Only AmonRa and CWM version is available at this time, TeamWin is coming "soon". You can find flashable zip at the bottom of this post, flash it before you proceed to next move. If something goes wrong, you can restore your recovery with zips from here.
Kernel with ext2/3/4 support, which is basically every but stock
Both ROMs you wanna use must be compatible with same kernel. See Limitations in previous post
2. MultiROM instalation
- Via MultiROM Mgr application
I recommend you do nandroid backup before installing via this app.
Download MultiROM Manager (link at the bottom of this), tap to "Tap to install via this app" and wait. As simple as that. Mgr will also install recovery for you (It will ask you which one, you can select AmonRa, CWM and none). App can check & install update, too.- Via recovery
Just download multirom.zip at the bottom of the post, make nandroid backup and flash it. Your current ROM will be the one in internal memory, we will setup the one on the SDCard in next move.
Now, try to reboot the phone (boot will take little longer, because it has to mount ext partition). If it boots up correctly, then its OK - your ROM is supported. If not, then restore your nandroid backup and post your ROM name here, maybe I'll try to make it working.
3. Setup ROM on the sdcard
Make nandroid backup (I am not kidding, you will need this one), flash ROM which you wanna to have on SDcard, do the first boot (because it will create dalvik-cache, and you dont wanna do that when its already on sdcard) and reboot to recovery again.
Go to "MultiROM options" menu and select "Create from current ROM". It will do everything for you (it takes time, though). ROM on the sdcard is placed in /sd-ext/multirom/rom/, backups are in /sd-ext/multirom/backup/.
Restore nandroid backup from beggining of this step and reboot. Wait until Boot manager shows up, and select SDcard as boot location. ROM from sdcard should boot. If your ROM from internal memory boots or if its stuck, something got wrong and you should restore from backup.
4. MultiROM recovery menu description
Active/deactive state is for recovery only, you can boot ROMs from backup in boot manager - that means its N-times boot rather than dual-boot.
When not active(boot from internal memory):
Activate (move from backup) - when you already have backup, this will move it to active folder (fast).
Activate (copy from backup) - same as above, but it copies it instead of moving
Create from current ROM - pretty self-explanatory
Create from ZIP file - see http://forum.xda-developers.com/showthread.php?p=22194117#post22194117
When active(boot from sdcard):
Deactivate (move to backup) - Moves current ROM to backup folder, so next boot will be from internal memory
Backup - Creates backup of current ROM
Erase current ROM - Deletes current rom, next boot will be from internal memory
Copy modules from int mem - Copies modules from ROM in internal memory to SDcard. Try this if WiFi does not work in SDcard ROM.
Flash ZIP - flash ZIP file to ROM on SD card, for example gapps.
5. Config file:
It is recommended to use Multirom Manager(see bottom of this post) to change config file.
File itself is placed on sdcard and its name is multirom.txt. Description of its contents is in this post(post is updated if something changes): http://forum.xda-developers.com/showthread.php?p=20045183#post20045183
6. Key bindings:
Since v11, you also can control MultiROM via touchscreen.
Anywhere: Hold Power button to shut down the phone
While on main screen:
VolUp/Down - list between actions
Menu - Confirm action
Back - Reboot to recovery
Power button - Sleep mode
While playing tetris
VolUp - return to main screen
VolDown - pause
Menu - move the piece to left
Home - hard-drop
Back - rotate piece
Search - move the piece to right
FAQ:Q: It is slow!
A: Its sdcard. It just is slower than nand memory.
Q: It does not work with my ROM
A: Post your ROM combination here, maybe I'll see to it.
Q: When do I need to reflash?
A: When you flash new ROM or do something which rewrites boot partition. Most (if not all) kernels are using Koush's AnyKernel, so they should not cause any problems.
Changelog & Download:(Always flash newest version)
Uninstaller: http://www.mediafire.com/?3eco51f2t0at77o (info here)
Changelog AND DOWNLOAD LINKS have moved to github: http://tasssadar.github.com/multirom/
Recoveries
AmonRa - based on 3.06: http://www.mediafire.com/?ld9g81igvze7na0 (9th March 2012 21:57)
AmonRa - based on 2.2.1: http://www.multiupload.com/7Y5HHNEPOT (20th October 2011 22:29)
CWM: http://www.mediafire.com/?6rfw0qbrddzq5d8 (9th March 2012 21:57)
TWRP: http://www.mediafire.com/download.php?o8kphxmfk9l01tl (21st October 2012 23:49)
MultiROM Manager app
http://forum.xda-developers.com/showthread.php?p=20610052#post20610052
(Always use newest version)
v24 - http://www.mediafire.com/download.php?1xy52tamzepibrx (TWRP support)
v21 - http://www.mediafire.com/?u9c3bmfbtf57dtm (Add charger settings)
v18 - http://www.mediafire.com/?g1lpsp66jc1cb1b (Add boot location settings)
v17 - http://www.mediafire.com/?l1li51sseaisz5j (Add brightness setting)
v15 - http://www.multiupload.com/B65WPFMFXP (Show & reset tetris high score)
v14 - http://www.multiupload.com/FWB5UBSMO1 (Updater now also check for app update, some minor fixes)
v13 - http://www.multiupload.com/NYYBX9CAFD (Update translations, add support for optimus V - http://forum.xda-developers.com/showthread.php?p=20657898#post20657898)
v11 - http://www.multiupload.com/1L3294ZAU7 (Fix mount issues on some roms, add menu to main screen, add link to xda)
v10 - http://www.multiupload.com/B3AVSFKDOW (Create /sd-ext/multirom folder on install)
v9 - http://www.multiupload.com/WW7TUNP7RY (read http://forum.xda-developers.com/showthread.php?p=20624306#post20624306)
v8 - http://www.multiupload.com/6OD7RQ74OE
v7 - http://www.multiupload.com/DJKMUGIVJ0
Something like this have the Xperia series. Maybe u find something u can use there.
Sent from my LG-P500 using XDA App
so this means we can test roms without replace current ??
Yes. Is my english so bad or you just don't read what I wrote?
Tasssadar said:
Yes. Is my english so bad or you just don't read what I wrote?
Click to expand...
Click to collapse
For the last time,you're speaking english perfectly p)
how to install your zip of amonra recovery i try but the recovery says that the zip dont have updatescript so it gives error....
i dont understand how to do this but ii´m searching this for a long time,if you can make a more frindley all user guide it will be very cool thankyou and hope you could doot....
*sigh* once again, this is [dev] thread, this is not something you can flash, at least not yet. You would know that, if you'd read whole post.
eduardogouveia said:
how to install your zip of amonra recovery i try but the recovery says that the zip dont have updatescript so it gives error....
i dont understand how to do this but ii´m searching this for a long time,if you can make a more frindley all user guide it will be very cool thankyou and hope you could doot....
Click to expand...
Click to collapse
[dev] means this is not something ordinary. Don't know what it is, don't mess with it.
Tasssadar said:
*sigh* once again, this is [dev] thread, this is not something you can flash, at least not yet. You would know that, if you'd read whole post.
Click to expand...
Click to collapse
Don't worry, you'll get more "hao cán i flush this into ma phones?" questions, good luck.
sounds like fun
thanks for bringing it for optimus one
but i have one question for you
I think in future kernel changing will also possible
because if we can flash kernel then we can make it to change
right?
Tasssadar said:
Yes. Is my english so bad or you just don't read what I wrote?
Click to expand...
Click to collapse
Maybe you just helped us with boot manager app
Sent from my LG-P500 using xda premium
I read the post but since the download you have is of a amonra recovery modified by you,i thougt that was a regular zip and only then make by abd the tutorial,thats why hi also ask a more friendly use because i now its not for averager use no need to get obset however im still happy hi was searching for that so hi dont mind waiting you make it more simple... sorry if that ofend you or franco lol we have to learn and its very hard now how to develop without having the proper nowledge like you all devs have and hi respect every dev even of he just make a simple app,by the way just dont send me to school lol where could i learn the bases to umderstand how to program java and then develop im asking this because all books hi find rekire previous nowleged of some progaming could some dev. Pointing me somewhere where i could learn and please dont be rude im just asking because i just dont love i want and hi will learn...
And baking to the thread what you find for me is one of the best and most important for our phones thanks a lot now just wainting a day everybody could use your work thank you
Sent from my LG-P500 using XDA Premium App
So your main question is: "Is it worth it?"
I would say, "Hell yeah it is!" but then again I do not have the know-how to pull something like this off.
If you decide to go ahead with it, I wish you the best of luck =P
I just modified Koush's AnyKernel so that it can modify ramdisk's content, so it is possible to install it with .zip file via recovery. I will add some modified version of CWM & AmonRA, create some walkthrough video and write some guide soon(c).
By the way, that kernel which is in devoid #froyo-final cant mount ext4 partition in init, dunno why, I'll look into it after raid.
EDIT: wtf, it just works now, and I did nothing Oo
EDIT2: Changes commited, now It can installed/controlled only by flashable ZIPs and recovery(well, only my modified AmonRa recovery for now). I'll do the rest soon, but I dont know when - maybe tomorrow (oh my, it is today actually already), maybe next month.
Flashable zips and guide added, see first and second post.
keep going I wanted something like this waiting when it can boot stock<froyo> and cm7....
thanx
gingerbread test
well i try with V20C,2.3.4 port(both with a2sd)and didnt woork after flash multiromv1.zip,when reobooting always return to recovery,so in recovery i go to multirom options and says no multirom folder so i start to think a2sd imcompatibelity,so i grab 2.3.3 V20G without changes oficial as lg give us but the results where the same no a2sd problem....
well later i will flash oldbaseband and try one of your combinations but i think its not compatible with gingerbread.....
I think I found it - on GB, there is "on fs" trigger in init.rc, which has only mounts in there, but I need to comment them out - all of them, so "on fs" trigger is empty, and init parser cant handle that. Will update soon.
Ok i will remain in new baseband to try when you update your exclente work...
Sent from my LG-P500 using XDA Premium App
v2 released, I have tested it with CM7 6.5.8, problem with stock GB should be the same as with CM7.
Features :
- Wifi and accelerometer should works fine for XW ROM owner
- Faster speed based on better code generation (will work on OC in next release)
- Voodoo sound and super user will be automatically dropped upon restart, so that even you have deleted them by accident, the kernel will always get them back for you
- Does automatically install busybox in /system/bin, so that you can start messing with bash script '
- Lifespan tweak (avoid frequent read / write to disk) and network tweak via sysctl.conf (since ver 1.2c)
- Performance tweak and battery life tweak as well via default.prop (since ver 1.3). To understand what I have done, check below for the copy default.prop with explanation.
- Automatically adds bravia engine to the system (since ver 1.3a) (there was a bug in ver 1.3 that makes bravia engine didn't work)
- Added 3 IO scheduler at the moment, sio, bfq and vr. SIO is selected by kernel by default. (You may override it with your init.d script) (since ver 1.3a)
- Automatically zipalign and perform database optimization with sqlite3 (thanks to ius in CM dev team to provide his statically linked binary) (since ver 1.3a)
- Perform a load of IO improvement when booting the device (since ver 1.3a)
Since too many people *****ed about the error while the kernel is running safe on my phone, I decided to make this kernel into dev release now. And may become private one in the future.
btw, if you want to use this kernel, please remove all those SetCPU or blahblahblah program for setting CPU frequency. Because setting CPU frequency simply doesn't work on my kernel (only 1.0Ghz max). And my kernel only works best with stock ROM, please let me know if you have any problem. In you have found any force close problem, and the problem persists after you have wiped the dalvik cache in CWM, that means you /data partition is doomed as having corruption made by the heat generated from other OC'ed kernels, and stop complaining about it in my thread. Just stick to the original kernel if you do not want the speed boost caused by dalvik int:jit mode. (The reason that I need to wipe dalvik-cache during installation)
For ROM developer :
- If you want to write something to /proc/sys/blah/blah/blah, you no longer need to use echo to input value to there. You just need to place a sysctl.cfg under /etc and then call 'sysctl -p' in the init.d script. Look below for an example of sysctl.cfg.
Credits goes to supercurio for his voodoo sound patch, xlm13x for testing, ius @ CM dev team for providing statically linked sqlite3 binary, utkanos for providing guide in make CWM, Turl for providing a guideline for making BroadConfig.mk (for the errata patch ), each IO scheduler author for their kind support for Linux community.
Change log in version 1.3a :
- Makes bravia engine works again
- Removed the problematic prop from default.prop so that the camera recording works again
- Added 3 IO schedulers : sio, bfq, vr (automatically select sio on all mmcblk partition by default)
- Sqlite3 and zipalign optimization upon boot
- Deleted the part for wiping dalvik-cache and cache on every boot (so this will do less damage to disk as well as faster boot speed)
(btw if you experience any force close, please boot to CWM and select 'Advanced' -> 'Wipe dalvik-cache'.)
- Since this build, there will be 2 versions because there is a IO optimization performed on /efs that may brick your device. Please always use CWM to flash both as I have finally made a backup script in the updater that automatically back up your /efs upon installation
- Since this build, the way to flash the kernel via odin is deprecated and un-recommended since it does not backup your /efs folder upon installation
- Since this build, service iq and user stats data will get disabled and no longer get sent to any user stat server
- Finally it is a stable release
Differences between dangerous build and normal build : dangerous build means it modify the mount option of /efs to disable ext4 journalism to gain IO performance which could compromise the integrity of the /efs partition (which means your phone can be bricked), normal build means that it doesn't do anything for disable ext4 journalism on /efs.
However the dangerous build should be safe if you flash it via my CWM flashable zip because it does automatically backup your /efs upon installation (and allow you to restore later). Just backup the efs_backup.img in the internal sdcard or external sdcard and you are good to go. (I have made the backup on both sdcard, and even if you install my kernel multiple time via CWM, the oldest version of efs partition is still be saved because the script does not overwrite the efs_backup.img by itself. If efs_backup.img exists, efs.img is created instead.) But it does really take you time when you need to restore the efs partition. (You have to repack it for flashing in odin or flashing via CWM, will make a guide for it later) If you really afraid of using the dangerous build, use safe build instead.
Change log in version 1.3 :
- Added bravia engine
- Moved those apk files aways from /sbin to /tmp
- More tweaks made via default.prop now
- Fixed a typo in the post init script that made init.d script stops working and stops dropping su and other stuff into the system automatically
btw since ver 1.3, the boot time will take longer as the system has to wipe and re-generate the dalvik cache everytime it boots. This is due to I have set the dalvik vm mode to int:jit and the dalvik cache has to be wiped. But don't worry, it will still boot.
Change log in version 1.2c2 :
- Major update that fixed the 'accident' (was too busying in development, sry)
- Added more useful binary into /sbin for normal boot condition and /system/bin, such as tune2fs and makee2fs
- A minor update in the post-init script that drops voodoo sound only when the string 'org.projectvoodoo.controlapp' in not found in /system/app package list (instead of totally matching the string)
Change log in version 1.2c1 (minor update that can ensure that voodoo sound is automatically installed + an accident :x ) :
- Automatically installs voodoo sound without any problem (If you find that voodoo sound is *****ing about mod developer is lame, just restart once and everything should work)
- Accidentally rolled out a development ramdisk for CWM in this release
Change log in version 1.2c (all the changes are made in ramdisk only, no kernel improvement yet) :
- Supports init.d script initialization now (Credit goes to ardatdat for original post-init.sh method)
- Using busybox instead of the crappy samsung stock toolbox binary (should be more useful if you use adbd for debug frequently) which has following 2 benefits
- Using busybox binary could also increase the performance as all the binaries are compiled with optimization (I am not totally sure about this at the moment, but it seems like the OS works faster now)
- A fully functional working bash script in /system/bin
- Network speed tweak by increasing memory buffer size for network connection (via sysctl.cfg placed in the root directory of the ramdisk)
- Has enabled many config that can avoid frequent read write to the NAND (disk) to further expand the lifespan of your device
Change log in version 1.2b :
- Added voodoo support to stock XW kernel
- Added CWM 5.0.2.8
- Modification on makefile that generates optimized code for our device
To-do list (for next major version release) :
- Add OC capability
- Installing busybox on boot.img by default <----- finished
- Add a version number in the build number <----- finished as well
Timeline :
Phase 1 : Boost performance and network speed boost by using the property I have set via default.prop and sysctl.conf (so it will work on any rom if the ROM developer doesn't override them, work best for stock ROM) <- finished, made in ver 1.3
Phase 2 : Removing those sysctl setting from the init script so that no duplicate entry is made in the ramdisk
Phase 3 : Enabling overclock in the kernel (yes 1200mhz by default but no longer 1000mhz) <----- will be the ver 1.4
Phase 4 : Patch out CWM to support backup to external sd, as well as supporting installing zip from external sd
Phase 5 : Properly adding zipalign to the kernel such that files will get zipalign-ed by default
Phase 6 : Add IO scheduler <---- Finished by half, still lots of scheduler can be added
Phase 7 : Allow the user to set CPU frequency for different CPU separately
Phase 8 : Investigate the wifi disconnect problem
Credit goes to supercurio for his old voodoo sound kernel patches made on Galaxy tab 10.1, which I have ported to this device using cherry pick method.
Kernel rev 1.3a download link (for odin) (Safe version) (without messing with /efs) (totally un-recommended as you need to wipe dalvik cache for using my kernel, CWM version does it automatically) :
http://www.mediafire.com/?206q94b2f25ouh4
Kernel rev 1.3a download link which can be flashed with CWM (Safe version) (Without messing with /efs) :
http://www.mediafire.com/?fcpea3c8an3k325
Kernel rev 1.3a download link (for odin) (Dangerous version) (totally un-recommended as you need to wipe dalvik cache for using my kernel, CWM version does it automatically) :
http://www.mediafire.com/?vapkb382fyaj6nu
Kernel rev 1.3a download link which can be flashed with CWM (Dangerous version) :
http://www.mediafire.com/?1ii2sdz1qode012
To install it (without CWM from stock firmware) :
1. Download the zip file from here and unpack it : http://www.mediafire.com/?cf6ah2cfzvcko
2. Download odin 1.8.5 from the sticky post
3. Flash the extracted .tar.md5 file with odin (just place it in PDA tab and press start after your phone has got into download mode and connected to your PC)
4. Then follow the guide below
To install it (with CWM from version other than 1.2c1) (recommended way) :
1. Download the CWM flashable zip file and then put it on your phone internal SD card (external sd card is not supported for installation at the moment, will get it supported in next build)
2. Start the phone in recovery mode with 3 buttons combo (Press the power button, and after the phone started, immediately press the volume up + home button)
2.1 If the phone is switched on, just power off it
2.2 After the phone powered off, press power button to switch it on again, after the boot logo is shown, immediately press Volume up + home button. CWM recovery mode will be shown.
3. Install the package via CWM (Install zip from sdcard)
Then reboot and restart the system twice to make sure that voodoo sound library is properly dropped.
Warning : If you are trying to update from Ultimate kernel ver 1.2c1, follow the following guide instead. I know this may be painful for you, however I am here to help you to fix the problem that I accidentally introduced in ver 1.2c1 without getting download counter increased. I apologize for any inconvenience caused. In general, if adbd is enabled on a device and if dd binary is presented, you can always use the following method to flash a kernel / CWM.
Guide post : http://forum.xda-developers.com/showpost.php?p=25893081&postcount=102
To recover (uninstall my kernel) (for any errors) :
1. First open up this folder : http://www.mediafire.com/?cf6ah2cfzvcko
2. Select the target that you want (they are all flashable via CWM) :
ardatdat kernel v1.7b1 CWM -> means ardatdat kernel v1.7b1 with stock recovery ZCLA1 image (these are the images that used by ardatdat kernel by default)
ardatdat kernel v1.7b2 CWM -> means ardatdat kernel v1.7b2 with stock recovery XWLA4 image (these are the images that used by ardatdat kernel by default)
stock boot and CWM 5.0.2.8 (XWLA4) -> means stock kernel XWLA4 but with my CWM
stock boot and CWM 5.0.2.8 (ZCLA1) -> means stock kernel ZCLA1 but with my CWM
Stock boot and recovery (XWLA4) CWM -> means stock kernel and recovery image (DO NOT select this unless you want no CWM recovery and revert to default)
Stock boot and recovery (ZCLA1) CWM -> means stock kernel and recovery image (DO NOT select this unless you want no CWM recovery and revert to default)
3. Boot your phone in CWM recovery mode, select 'mounts and storage' -> 'mount USB device', copy the downloaded file to the internal sd that mounted to your PC
4. Then just flash it via CWM (Install zip from sdcard)
5. Wipe dalvik cache and cache via CWM menu
6. Reboot
And since ver 1.2c1, you no longer need to install superuser, su binary and voodoo sound seperatedly on your own now.
The full src code change can be viewed here : https://github.com/UnknownzD/I9103_XW_Kernel/commits/master
The ramdisk folder for boot.img can be viewed here : https://github.com/UnknownzD/I9103_XW_Kernel_boot_initramfs
The ramdisk folder for recovery.img can be viewed here : https://github.com/UnknownzD/I9103_XW_Recovery_initramfs
Example of sysctl.cfg
https://github.com/UnknownzD/I9103_XW_Kernel_boot_initramfs/blob/master/sysctl.conf
Copy of default.prop (ver 1.3a) :
https://github.com/UnknownzD/I9103_XW_Kernel_boot_initramfs/blob/master/default.prop
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
btw I hope that the same patch can be made to I9103_CHN_Kernel very soon. I have too much things to do atm, still a ROM and 3 exams to be finished atm.
hey thanks a lot for this but we'd like it more if it was a CWM flashable zip as the odin one increases the custom counter and we all do not have the USB jig... Can you help us with that if it's not much of a problem ?
sagarwadhwa1 said:
hey thanks a lot for this but we'd like it more if it was a CWM flashable zip as the odin one increases the custom counter and we all do not have the USB jig... Can you help us with that if it's not much of a problem ?
Click to expand...
Click to collapse
Definitely, I will make one asap. So it will also flash superuser, su and voodoo sound @ once.
btw, I have already found a bug in voodoo sound. So I hope it can be patched in next build.
You can create it on your own.
follow these steps.
1. Download ardatdat's 1.7 kernel zip.
2. Download the Ultimate Kernel for XW.
3. Now unpack ardatdat's zip and Ultimate Kernel zip.
4. Replace Boot.ing of ardatdat's with ultimate kernel Boot.ing.
5. now zip it again.
Now you are ready to flash the Ultimate Kernel with CWM.
guys, is it possible to do so would have created backup on a removable flash drive?
Okay I have made a CWM flashable zip now. Check first post for more info.
UnknownzD said:
Okay I have made a CWM flashable zip now. Check first post for more info.
Click to expand...
Click to collapse
put the package cwm + core, cwm and does backup on a removable memory stick, and, in principle, not bad!
Thanks for the wonderful kernel. It makes my phone with titanium ROM silly smooth and voodoo really rocks. For some reason I find the bass effect in ultimate better than ardatdat kernel.
Sent from my GT-I9103 using Tapatalk
Flashed the new kernel. Smooth no issues as of now.thank you
Sent from my GT-I9103 using XDA
Amazing sound performance with your voodoo enabled kernel.. Thank you UnknowzD...!! you rock..
i had checked this rom
but it giving error while updating zip from recovery
Thank you for your hard work and efforts for our Device.
is it possible to flash CWM 5.0.2.8 with CWM or can you please make it a separate file which we can flash from ODIN because if we flash this with kernel the Custom Count will be increased, as many of us are not having USB JIG it will be more help full for all of us.
mj.vikram said:
Thank you for your hard work and efforts for our Device.
is it possible to flash CWM 5.0.2.8 with CWM or can you please make it a separate file which we can flash from ODIN because if we flash this with kernel the Custom Count will be increased, as many of us are not having USB JIG it will be more help full for all of us.
Click to expand...
Click to collapse
Yes it is possible, coz I have made my recovery image seperate from the boot.img and actually you can use my recovery image with ardatdat kernel as well.
Sent from my GT-I9103 using XDA
mj.vikram said:
Thank you for your hard work and efforts for our Device.
is it possible to flash CWM 5.0.2.8 with CWM or can you please make it a separate file which we can flash from ODIN because if we flash this with kernel the Custom Count will be increased, as many of us are not having USB JIG it will be more help full for all of us.
Click to expand...
Click to collapse
The Cwm zip package includes the CWM 5.0.2.8.
emanoj.i9103 said:
The Cwm zip package includes the CWM 5.0.2.8.
Click to expand...
Click to collapse
Thank you i haven't checked it, flashed it now ....
I'm getting a problem with the CWM Recovery.
Whenever i try to backup my system, it starts to backup perfect and when it reaches backing up data, data of external sd, it stops saying error in backing up data of external sd... It think it's because it's backing up in the internal sd which runs out of space...
Can you fix CWM to not back up data in internal SD and to not backup the external sd card ??
sagarwadhwa1 said:
I'm getting a problem with the CWM Recovery.
Whenever i try to backup my system, it starts to backup perfect and when it reaches backing up data, data of external sd, it stops saying error in backing up data of external sd... It think it's because it's backing up in the internal sd which runs out of space...
Can you fix CWM to not back up data in internal SD and to not backup the external sd card ??
Click to expand...
Click to collapse
I am also having the same problem, its trying to take all the data which is present in External SD and dumping it to internal SD and giving error, may be because of insufficient space..
So can you please change the Back up location to External SD and not to take the back up of External SD card please.
azhar.munshi said:
i had checked this rom
but it giving error while updating zip from recovery
Click to expand...
Click to collapse
I have the same problem ( I installed Kernel package with voodoo via CWM.
Just flashed 2.3.6 and first thing I did was install cwm and ur kernel. One word.. AWESOME dude. Really too good improvement in sound. Its almost equal to my clip+.. Bass is too good even with my pl-11.. Thanks a lot
Sent from my GT-I9103 using XDA
mj.vikram said:
I am also having the same problem, its trying to take all the data which is present in External SD and dumping it to internal SD and giving error, may be because of insufficient space..
So can you please change the Back up location to External SD and not to take the back up of External SD card please.
Click to expand...
Click to collapse
sagarwadhwa1 said:
I'm getting a problem with the CWM Recovery.
Whenever i try to backup my system, it starts to backup perfect and when it reaches backing up data, data of external sd, it stops saying error in backing up data of external sd... It think it's because it's backing up in the internal sd which runs out of space...
Can you fix CWM to not back up data in internal SD and to not backup the external sd card ??
Click to expand...
Click to collapse
Minns said:
I have the same problem ( I installed Kernel package with voodoo via CWM.
Click to expand...
Click to collapse
Okay I will try to fix the problem tonight. Thank you for reporting the problem. In addition, I will roll out another build tonight that supports init.d script as well as installing busybox in /system partition (yes latest hacked busybox src that compiled from CM repo that gives you a much better bash shell than the original one @ /system/bin/sh. And no more crappy toolbox binary as well if they can be replaced from the one in busybox). In addition, it will also supports sysctl in the system partition so all the ROM developer do not need to use the echo '0' > /proc/sys/blah/blah/blah any more. You will just need to ship 2 files to change those values, a sysctl.conf and a init script that invokes sysctl.
brb in 2 hrs, I have to go now as having dinner with my gf.
******************* INFO&CREDITS *******************
I know i've been away from this forum for a lot of time (mostly my Nexus 5 fault ) but when i've seen that F2FS it's now possible on this device i decided to create an easier way to create&use this filesystem,so average users can try it and decide.The best part of XDA is that everyone can contribute in the best way he/she can.
Anyway all credit goes to: samsung (for the f2fs) , Alex Page <[email protected]>, @_that @Dees_Troy (TeamWin ), @dasunsrule32 (cyanogenmod), @Hundsbuah and to everyone who contributed to make this device better.Thank You all!
******************* About F2FS *******************
F2FS (Flash-Friendly File System) is a flash file system created by Kim Jaegeuk (Hangul: 김재극) at Samsung for the Linux operating system kernel.
The motive for F2FS was to build a file system that from the start takes into account the characteristics of NAND flash memory-based storage devices (such as solid-state disks, eMMC, and SD cards), which are widely used in computer systems ranging from mobile devices to servers.
Samsung chose a log-structured file system approach, which it adapted to newer forms of storage. F2FS also remedies some known issues of the older log structured file systems, such as the snowball effect of wandering trees and high cleaning overhead. Because a NAND-based storage device shows different characteristics according to its internal geometry or flash memory management scheme (such as the Flash Translation Layer or FTL), Samsung also added various parameters not only for configuring on-disk layout, but also for selecting allocation and cleaning algorithms. (source Wikipedia )
******************* WARNING *******************
* Please be aware that F2FS is still experimental and DATA LOSS or other issue may occur.
* You agree to use this MOD on you own risk and i don't take any responsability if you encounter any issue or if your personal data is lost
******************* Requirements *******************
Your tf700t device must be Unlocked
An external MicroSD card or a PC (for backup/restore )
A brain
******************* Preinstalling steps *******************
Backup of your personal data to an external card or PC (photo,music,ringtones,etc)
Create a backup from recovery and store it in a safe place (external sdcard or PC)
Download twrp_f2fs from the Download Section (second post )
Download a kernel from the Download Section (second post) - _that and Hundsbuah are for stock based roms only ; CM11 is for Cyanogenmod based.
Download your favorite rom
******************* Install Steps *******************
1) Install twrp_f2fs recovery using one of the methods bellow
Fastboot method
Code:
fastboot -i 0x0B05 flash recovery twrp_f2fs.blob
fastboot -i 0x0B05 reboot
Terminal/ADB
Save twrp_f2fs.blob to the root of your /sdcard directly (internal memory only).
Launch terminal emulator or connect to your computer and open an adb shell, then type the following:
Code:
su
dd if=/sdcard/twrp_f2fs.blob of=/dev/block/mmcblk0p4
and reboot your device
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
2) Reboot to recovery (if the recovery was installed you will see the 4 linux penguins after pressing the RCK button)
3) Enter the WIPE menu and select Format DATA ( warning all your personal data will be lost )
4) Wait until the format is complete then reboot to recovery again (if previous step was succefull your DATA partition is now F2FS )
5) Wipe Cache (Wipe Menu --> Advanced --> select only Cache partition and go)
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
6) ROM installation ( you can choose several methods to get your system back and running)
a) if you already have a System installed you can skip to step 7)
b) install your favorite ROM from external sdcard and Reboot to Recovery
c) restore your previous backup from an external sdcard (select only SYSTEM and DATA partitions) and Reboot to Recovery
7) Install one of the F2FS kernels (based on the ROM you have) and REBOOT SYSTEM
Remember that everytime you install a new ROM you have to Reboot to Recovery and install an F2FS kernel.
That's it,the system should boot with an F2FS data partition,start playing with it. :good: :laugh:
******************* Rom2SD_F2FS *******************
NOTE:
In order to use Rom2SD you need to have a running and rooted stock-based ROM with busybox and a kernel with preinit support (_that and hundbuah kernels are one of them
Also make sure there are no residual folders&files from an old Data2SD/Rom2SD setup ( basically delete the /boot folder in /system if there is one)
Partitioning your MicroSD -- > You can find a good tutorial (thx @sbdags) here
**** Install steps ****
Download all the files from Rom2SD section in the Download page ( post #2) and save them on MicroSD
Download a Kernel from the Download page ( choose the correct one depending on your favorite ROM base) and save it to MicroSD
Boot your device in Recovery
Install Rom2SD_F2fs.zip
Install Rom2SD1.zip
Go to Mount option and make sure Data partition is unchecked ,if not,uncheck it and press Home icon to go back to the Main menu (don't press back)
Go to Wipe and press Format Data (this will format your external data partition to F2FS) - if is failing check the Mount option again
Install your favorite ROM (don't reboot)
Install an F2FS Kernel (don't reboot)
Install Rom2SD2.zip
Reboot and enjoy Rom2SD_F2FS
**** Tips ****
If you have a Backup for the Rom installed on external then you can restore your data and avoid the waste of time needed to configure everything again
Boot to Recovery
Install Rom2SD1.zip
Go to Restore and select the desired backup and check only Data
Swipe to restore and then reboot to system
******************* Back2EXT4 Script *******************
Description: This script will help you format the Data partition to EXT4 without the need to change the recovery.
Instructions:
**** Internal Data ***
Download Format Data to EXT4.zip from the download section and save it to MicroSD
Reboot to Recovery
Install Format Data to EXT4.zip --> Warning,your personal data will be lost
Now your data (mmcblk0p8) partition it's EXT4 but you can still use twrp_f2fs
**** External Data (Rom2SD/Data2SD setup) ***
Download Format Data to EXT4.zip from the download section and save it to MicroSD
Download Rom2SD1.zip from the download section and save it to MicroSD
Reboot to Recovery
Install Rom2SD1.zip
Install Format Data to EXT4.zip --> Warning,your personal data will be lost
Now your data (mmcblk1p2) partition it's EXT4 but you can still use twrp_f2fs
*********************************************************************************************************************************************************************************************************************
Note: As you can see there are several ways to get your system up and running after your Data partition was formated with F2FS.Also based on my tests you can use an "old" EXT4 backup to restore on F2FS and should work viceversa too.
I will also update this thread with info on how to go back to EXT4 without changing the recovery,and also i will try to modify the Data2SD/Rom2SD scripts and make them F2FS compatible.
And btw,please kick that THANKs button
Downloads
********************************************************* Downloads *********************************************************
++++++++ Kernels ++++++++
That_F2FS.zip --> MD5 Sum: 1165247d099f5dbd5f5a4d4a848ff186
Kernel_F2FS_Hund_v3.4.5 --> MD5 Sum: 888e71f5fade857ed7a062dc08b36d77
CM11_Kernel_F2FS.zip --> MD5 Sum: e9772d2b8a63a009d0499c43fb93a6db
Build by @sbdags F2FS kernels
++++++++ Recovery ++++++++
twrp_f2fs.blob --> MD5 Sum: 4391cdfac9bf9660f52b8b0081543ea0
++++++++ Rom2SD_F2FS++++++++
Rom2SD_F2fs.zip -- > MD5 Sum: f5629e4fc9c40cbb7590152001de8179
Rom2SD1.zip -- > MD5 Sum: f6a6b0e5f0260078782a86c2e60c664e
Rom2SD2.zip -- > MD5 Sum: e82008368cb8ee663a70e63c6cb10040
++++++++ Back2EXT4 Script ++++++++
Format Data to EXT4.zip -- > MD5 Sum: 7ddbbbbe5d7e3c546c46ab8c185b4a70
********************************************************* Sources *********************************************************
Recovery - build from the official sources available in Omnirom 4.4 tree (android_bootable_recovery)with @that kernel (kernel source ).
Hundsbuah kernel - original kernel from here + modified ramdisk
_that kernel - original kernel from here + modified ramdisk
CM11 kernel - Source + Patch
Pretoriano80 said:
Reboot to recovery (if the recovery was installed you will see the 4 linux penguins after pressing the RCK button)
Click to expand...
Click to collapse
Even if you hadn't told me before, I could guess which kernel your recovery is using.
Thanks for making this package available to all users!
A warning to all potential users of f2fs: There is still no program to repair a corrupted filesystem - fsck.f2fs can only detect corruption but not fix it. Don't store anything important on f2fs.
Do you run into any issue with this f2fs so far?
LetMeKnow said:
Do you run into any issue with this f2fs so far?
Click to expand...
Click to collapse
Nope, no issue so far. At some point i was afraid that internal storage will die on me with all the formatting, installing and erasing i've did during F2FS tests, but still no issues.
Sent from my Nexus 5
Thank you for the new recovery with f2fs support.
I'm running latest crombikk with your own cm kernel and the system is running smoothly. Androbench shows that the random write speed gets doubled.
However, my system is not completely stable. Sometimes it freezes without rebooting, specially trying to copy very large files. And sometimes the internal storage gets unmounted. I suppose it's kernel related.
Are you planning to give the option to format also /system and /cache on f2fs? Or you think it's not worth it?
deadlocked007 said:
So does this zips the full internal storage or just the data part with apps and stuff?
Sent from my HTCONE using Tapatalk
Click to expand...
Click to collapse
Internal storage will be completely wiped,so /data/media too.
ariadnejro said:
Thank you for the new recovery with f2fs support.
I'm running latest crombikk with your own cm kernel and the system is running smoothly. Androbench shows that the random write speed gets doubled.
However, my system is not completely stable. Sometimes it freezes without rebooting, specially trying to copy very large files. And sometimes the internal storage gets unmounted. I suppose it's kernel related.
Are you planning to give the option to format also /system and /cache on f2fs? Or you think it's not worth it?
Click to expand...
Click to collapse
Didn't experienced issues so far but i 'm using CromiX here.
F2FS it's useful mostly for random write (or writing operations in general) ,there's no point using it for /system or /cache imo.
Sent from my Nexus 5 using Tapatalk
I assume twrp_f2fs is compatible with the current .10 bootloader and all the current roms: CROMi-X 5.4, CROMBi-KK and CM 11?
Sent from my K00C using Tapatalk
berndblb said:
I assume twrp_f2fs is compatible with the current .10 bootloader and all the current roms: CROMi-X 5.4, CROMBi-KK and CM 11?
Sent from my K00C using Tapatalk
Click to expand...
Click to collapse
twrp_f2fs it's based on official TWRP 2.7.0 and it should work fine with latest bootloader and all ROMs.
Basically i tested all those roms mentioned in your post and are working fine.
Sent from my Nexus 5
Seems to work well! I'm on the 3-19 build of CM11. Had really major IO issues with the device, nothing would make it even remotely usable, even on the performance CPU profile in both the cpu govenor and the asus cpu changer. It was always slow and laggy, it would not handle multiple things well, you basically had to single task. However, flashing this, doing my usual modifications, and it's making this baby fly again. I can open multiple apps and actually navigate without too much lag. Not sure if it's a placebo effect, but so far, it seems great, I'm able to install multiple things at once. I'll see how long this lasts (Wiping the SD can have some beneficial effects too) and I'll try to give an update later, it usually slows down after a few weeks. But this could be "settling" still, it's a fresh flash, even so, I'm happy it's usable again!
Hey is there any method available yet for this to work with rom2sd? Just imagining F2FS, rom2d, cromix 5.4 and hunds ET
yew123 said:
Hey is there any method available yet for this to work with rom2sd? Just imagining F2FS, rom2d, cromix 5.4 and hunds ET
Click to expand...
Click to collapse
In theory it should work like any ROM2SD installation:
* install rom2sd1 to switch the device nodes to the external card
* format data to f2fs
* install your ROM and a kernel with f2fs-enabled fstab in the ramdisk, don't reboot
* install rom2sd2 to move the ramdisk files to the external /system and modify mount points
Disclaimer: Not tested, there may be issues with the CROMI-X installer trying to be too clever, ...
_that said:
In theory it should work like any ROM2SD installation:
* install rom2sd1 to switch the device nodes to the external card
* format data to f2fs
* install your ROM and a kernel with f2fs-enabled fstab in the ramdisk, don't reboot
* install rom2sd2 to move the ramdisk files to the external /system and modify mount points
Disclaimer: Not tested, there may be issues with the CROMI-X installer trying to be too clever, ...
Click to expand...
Click to collapse
Well as long as you only do the data partition it should be OK. I'll look into f2fs support this week.
_that said:
In theory it should work like any ROM2SD installation:
* install rom2sd1 to switch the device nodes to the external card
* format data to f2fs
* install your ROM and a kernel with f2fs-enabled fstab in the ramdisk, don't reboot
* install rom2sd2 to move the ramdisk files to the external /system and modify mount points
Disclaimer: Not tested, there may be issues with the CROMI-X installer trying to be too clever, ...
Click to expand...
Click to collapse
Thanks @_that, when i've got some free time i'll give it a go
CM10 kernel?
Have a request for you, guys. Can someone make f2fs kernel for CM10?
Because I really don't want update my TF700 to 4.4, and stock-based roms isn't my choice...
I made 2 kernels for CM11 for data2sd setup with f2fs (sorry I know not CM10). But here they are if anyone wants to test them.
_thatv9 cm11 data2sd f2fs
DOWNLOAD
md5 sum : 8c340aca96c50ed734b0c903b80d8312
Hunds 3.4.5 cm11 data2sd f2fs
DOWNLOAD
md5 sum : 92cbf93223c07410758feb9921694353
sbdags said:
I made 2 kernels for CM11 for data2sd setup with f2fs (sorry I know not CM10). But here they are if anyone wants to test them.
_thatv9 cm11 data2sd f2fs
DOWNLOAD
md5 sum : 8c340aca96c50ed734b0c903b80d8312
Hunds 3.4.5 cm11 data2sd f2fs
DOWNLOAD
md5 sum : 92cbf93223c07410758feb9921694353
Click to expand...
Click to collapse
These Kernels will work on all CM based roms not just cromi-kk?
Sent from my SPH-L710 using Tapatalk
Frostbiter said:
These Kernels will work on all CM based roms not just cromi-kk?
Sent from my SPH-L710 using Tapatalk
Click to expand...
Click to collapse
Should do.
delete please
sbdags said:
Should do.
Click to expand...
Click to collapse
I end up with encryption unsucessful error on boot using the _that/sbdags kernel then reboots and twrp runs an open recovery script, reformatting cache with the mk_ext4 (IIRC), then same error on boot.
The CM kernel runs smoothly for me, but cannot get the touchscreen to respond from a deep sleep. The screen will turn on / off with power button press, but unable to get past the reboot screen or slide to wake screen because there isn't a response with touch. Fully charged the screen reads 'connect your charger' and will not connect to adb so I could not get a log for you.