This is my development based on Takaaki's initrd, during I develop my build at http://forum.xda-developers.com/showthread.php?t=913597, I spent a lot of time to enhance the data2sd and ext4, after studying almost all the popular methods: App2SD, Data2SD, Data2ext, Data2whatever, I develop this:
Features:
1. Support both data 2 data.img or ext4.
2. Support SquareFS.
3. Auto-format the 2nd partition with block size of 4096.
4. Utilize the Nand data partition to improve the performance.
5. Switch the PPP/RMNET.
6. Config the gps_zone
7. Support the update without re-flash. (you can fully customize your build based on this feature)
8. Backup the ext4 to data.img (implement in future)
9. Restore the data.img to ext4 (implement in future).
To enable external data.img
1. create '.data' folde under sdcard (/sdcard/.data).
2. create 'config.txt' under '.data' directory.
3. copy old data.img to '.data' directory, otherwise a new data.img will be created.
4. boot into Android.
Config.txt for data2SD.
data_img=1
data_ext=0
sd_boost=1
nand_data=0
Click to expand...
Click to collapse
To enable ext4
1. create '.data' folde under sdcard (/sdcard/.data).
2. create 'config.txt' under '.data' directory.
3. Config.txt for data2SD.
data_img=0
data_ext=1
sd_boost=0
nand_data=0
format_ext4=0
Click to expand...
Click to collapse
For first installation, it is always good to set the format_ext4=1 to format your ext4 partition with proper block size, after 1st boot, change it back to 0.
To config PPP/RMNET and GPS_ZONE
ppp_mode=1 will enable the ppp, set to 0 will use rmnet.
gps_zone='your country code', - country code, us, fr, jp, etc
To update/customize your build
1. Create a folder /DLZUPDATE under your sdcard.
2. put your app's apk under AndroidApps in /DLZUPDATE, that apps will be automatically installed into your data partition.
3. put your kernel file or other under root in /DLZUPDATE, all the files under root will be copied to your build, if your want to upgrade your kernel, just put zImage in /DLZUPDATE/root/system, and module files under /DLZUPDATE/root/system/lib/modules. etc.
Download
View attachment 492146
Install
1. extract the zip to a folder on your pc
2. backup your existing initrd.gz using adb
3. In "command prompt" env, run install.
4. your existing initrd.gz will be backup at the same folder named backup.initrd.gz.
5. if your have problem to boot into the system, just try: adb push backup.initrd.gz /system/initrd.gz. (even system can not be booted into the launcher or sense, in some point of time, the adb still can function, so just keep trying.)
Caution: if your build current use app2sd, you have to disable it before using this, rename the init.local.rc under etc to init.local.rc.bak, remove the 00start, 04apps2sd from /system/etc/init.d.
If your build uses boot partition, you should change the installation script to push the initrd.gz to replace the existing one wherever it is.
Thanks to
- ownhere (he is the expert of the ext4 or other file systems, and developed the data2ext.)
- melethron (the author of data2whatever)
- Takaaki (the author of data2sd)
- Cedesmith (He is guru of initrd )
Donation
I do not work for money, but it is always nice to know people really like my work and encourage me carrying on.
Please could you provide also information in case that NAND rom already use EXT4 for data2ext4 (like AF403 DesireHD stock based 1.0a)?
Good stuff.. thank you!
I am trying your NAND ROM now....
Good knowledge ... keep up cool stuff
i already use ur nand rom
If you don't want to look into the code to find out the difference, then, how about just try 1st.
totalcmdext said:
Please could you provide also information in case that NAND rom already use EXT4 for data2ext4 (like AF403 DesireHD stock based 1.0a)?
Click to expand...
Click to collapse
Sent from my DL DesireZ v2.5 using XDA App
Ok, i've managed to understand the concept of data2ext, and when on initial setup everything gets what i expect, i've 1 GB (depends on ext partition size) of free memory space, but i get an horrible performance even if formated with your tool, i guess it's SD performance/quality because i can't run any ext build published here where most of users claim to get good performance. So i try data2sd but instead of the 512MB (img size created with this) of memory i get only the 80MB of the free nand internal ram. What is stored on this img file ? only settings ? On 20 applications i use only 4 are movable to sd, so after my initial setup (and of course with good performance) i get a lot of memory low warnings.
Thanks
Looks like the data2sd was not enforced, what's your configuration in config.txt?
jpl69 said:
Ok, i've managed to understand the concept of data2ext, and when on initial setup everything gets what i expect, i've 1 GB (depends on ext partition size) of free memory space, but i get an horrible performance even if formated with your tool, i guess it's SD performance/quality because i can't run any ext build published here where most of users claim to get good performance. So i try data2sd but instead of the 512MB (img size created with this) of memory i get only the 80MB of the free nand internal ram. What is stored on this img file ? only settings ? On 20 applications i use only 4 are movable to sd, so after my initial setup (and of course with good performance) i get a lot of memory low warnings.
Thanks
Click to expand...
Click to collapse
Sent from my DL DesireZ v2.5 using XDA App
This is good and detail steps http://forum.xda-developers.com/showpost.php?p=10666187&postcount=341 on how to config, better than mine
Sent from my DL DesireZ v2.5 using XDA App
If i understand this, this is only change existing inird with modified initrd?
I'm sorry but with all this flash/unflash install/uninstall download configure i've lost my config, but i'm sure data_img=1 and data_ext=0
(just a note gps_zone=pt should configure gps to be used here in Portugal right ?)
If you say that it should work i'm going further with my tests and post here results because i don't want to flame this thread.
Update:
I've a stock 8GB class 4 card swaped with 4GB class 2, results on nand/ext4:
Initial setup (with format ext4) 1/2 time, second boot 1 minute and everything runing muuuch smother and faster so or i've got a malfunction card (?) (and i've read someone complaining about a 16GB class 10) or lowest class gets more speed (?)
Update2:
The diference is really amazing, i've got a completly functional android now with this card.
You should mention on your threads that if you get bad results on initial setup forget about that nand, return to SD builds or get other card.
Can you please post your card type please ?
how long does it take to format the ext4?
Hi,
I am trying to setup this new initrd, i put the format ext4 parameter in the config file and start my HD2.
wondering how long will it take to format my 1G ext4 partition?
thanks!
data.img Question
3. copy old data.img to '.data' directory, otherwise a new data.img will be created. ... Can I somehow set how big will the data.img be ?
Default will be 512M, you can config it by data_size.
BoneMo said:
3. copy old data.img to '.data' directory, otherwise a new data.img will be created. ... Can I somehow set how big will the data.img be ?
Click to expand...
Click to collapse
Sent from my DL DesireZ v2.5 using XDA App
Looks promising
This new initrd and file management seems well thought through and very promising.
In other builds I experienced that there can be a huge performance difference between the different file management choices (full NAND > adsd > ads2+ > data2ext > data2sd). It's good to see that you got into this subject and tried to find an optimal solution which can be configured by other chefs.
I assume that you implemented all this in your own DL DesireZ v2.5 build? If I find time I'm certainly gonna give it a try!
Keep up the good work!
works with AF403 DesireHD stock based 1.0a
there are a lot of discussions on my nand build about mixing using all the parameters, some got the performance improved a lot, some got things worse, your can refer to that to config your build for the best performance.
Dear, i got this error message...
D:\a>install
back your initrd...
remote object '/system/initrd' does not exist
replace your initrd...
1442 KB/s (0 bytes in 1523605.001s)
failed to copy 'mkfs.ext4' to '/system/xbin/mkfs.ext4': No space left on device
1263 KB/s (0 bytes in 303212.000s)
1410 KB/s (0 bytes in 428664.000s)
Unable to chmod /system/xbin/mkfs.ext4: No such file or directory
Unable to chmod /system/xbin/e2fsck: No such file or directory
Press any key to continue . . .
please help... I am using Gauner1986 build
Looks like the system in Gauner1986 build is read only or have the boot partition, or really occupied all the space? anyway, your existing build should be unchanged.
you can try adb shell ls /system, or adb shell ls /boot, whether there is an initrd.gz under it, then, manually push all the necessary files.
rasumia said:
Dear, i got this error message...
D:\a>install
back your initrd...
remote object '/system/initrd' does not exist
replace your initrd...
1442 KB/s (0 bytes in 1523605.001s)
failed to copy 'mkfs.ext4' to '/system/xbin/mkfs.ext4': No space left on device
1263 KB/s (0 bytes in 303212.000s)
1410 KB/s (0 bytes in 428664.000s)
Unable to chmod /system/xbin/mkfs.ext4: No such file or directory
Unable to chmod /system/xbin/e2fsck: No such file or directory
Press any key to continue . . .
please help... I am using Gauner1986 build
Click to expand...
Click to collapse
dandiest said:
Default will be 512M, you can config it by data_size.
Sent from my DL DesireZ v2.5 using XDA App
Click to expand...
Click to collapse
So you mean data_size= ... (512,1024,2048)
This is in cofig.txt?
jan-willem3 said:
So you mean data_size= ... (512,1024,2048)
This is in cofig.txt?
Click to expand...
Click to collapse
Yes, but please don't use 2048.
Related
**** EXT4 for DATA (SD) install on second post *****
I've been slowly working on our Kaiser Kernel hoping to get extra life from it. Here are the changes I made so far.
1. Updated to the latest initrd and made a few changed in the init file
2. Changed the default I/O scheduler to noop.
3. Added block data integrity support and v4 support
4. Updated the latest yaffs2 filesupport up to changes dated 1/14/2011
5. Added PM module for Qualcomm 7500 chip
Will try to add BFQ I/O scheduler and see how the performance is compared to noop.
1/29/11 ** UPDATED KERNEL for better YAFFS2 best suited for Kaiser Samsung Memory chip **
Here is the nbh. This is type2 screen and keyboard1.
Will release my latest changes and update to git (need help on this one) when stable.
Please reinstall ROM and wipe data after flashing the kernel. The changes in yaffs2 code might cause issues. You can restore your data from BACKUP after installing the ROM.
************ TO FORCE CHECKPOINT IN DATA PARTITION PLEASE DO THIS IN TERMINAL *******************
su
echo 6 > /sys/module/yaffs/parameters/yaffs_auto_checkpoint
sync
This will change auto checkpointing to 2 and create a checkpoint.
This is just temporary, the checkpoint is deleted in reboot so the commands have to be done before every reboot.
One solution is to use Gscript.apk and type the commands in Gscripts. Execute via Gscript before reboot
**** To verify if you have checkpoint in Data Partition Please do in Terminal ******
To verify if you have yaffs2 checkpoint in the data partition Type the following in terminal
su
cat /proc/yaffs
Scroll down to Device 2 "userdata"
scroll down and look for "blocks_in_checkpt" should be 1 or 2 (not 0, if it is zero then you have no checkpoint in data partition)
Update 2/7/2011
******************EXT4 FILESYSTEM FOR SD INSTALL***************
Because of bad blocks on my Kaiser, I have to give all NAND partition to install on system while installing data on SD with EXT4 filesystem. Here are the requirements:
1. An SD card with at least class 4
2. A way to partition and format your SD with FAT/ext2/Ext4 (ext2 should be as small as possible), I use Ubuntu for this.
3. Kernel with ext4 support (this will format your whole NAND partition to use system and use EXT4 on SD for Data)
Instructions:
1. FORMAT SD (I use Ubuntu DiskUtil) with FAT/ext2/EXT4, on my 8GB SD I use 7gb for FAT/8mb for ext2/1gb for EXT4 but it's your call. The most important part is that you only give the second partition (ext2) the least amount of size.
2. Download the KAISIMG.zip, extract and you will get a file KAISIMG.NBH
3. use Atools to edit accordingly with your Kaiser's screen type and keyboard (NBH is using screen 2 and keyboard 1)
4. Flash the KAISIMG.NBH
HERE IS WHERE IT GETS TRICKY!!! PLEASE FOLLOW THESE INSTRUCTIONS CAREFULLY!!!!
a. PRESS CENTER D PAD to enter ANDROID Installer
b. Choose (*) Sys on NAND
Choose (*) Data on SDCard Partition
c. Scroll Down to Install System and choose it
d. This will wipe your Existing system! Are you sure CHOOSE (YES)
e. Would you like to clear data too (Suggested) CHOOSE (NO) ***DO NOT CLEAR DATA OR THIS WILL CHANGE YOUR THIRD PARTITION TO EXT2 and will not work.
That's it. After installation reboot and you have an optimized ext4 on your SD for data. The mount options for ext4 in this kernel are:
data=writeback, barrier=0, nobh, noauto_da_alloc
Will use barrier=1 for better data security on next release, just enjoying the speed of barrier=0 for now
clemsyn said:
Will try to update our 2.6.25 kernel too if I get some space for my hard drive.
Click to expand...
Click to collapse
Yes, Clemsyn If it's not a big problem please update 2.6.25 too. Thank you.
updates kernel 2.6.25
clemsyn said:
Will try to update our 2.6.25 kernel too if I get some space for my hard drive.
Click to expand...
Click to collapse
This would be nice. Thank you
mt1976 said:
This would be nice. Thank you
Click to expand...
Click to collapse
It would take awhile though since I have to remove my 2.6.32 kernel to put 2.6.25 since I'm limited in space. Donations for a laptop HD would be appreciated
UPDATE:
1. I think one of the reasons of data failure is that YAFFS refuses to write a checkpoint for our data partition. It writes it in the system partition with no issues. The new yaffs2 (updated 1-27-11 which I will update shortly) allows forcing checkpoint so I'll try that one and see if I can create a checkpoint on our data partition.
Finally got a checkpoint in my userdata partition...instructions posted on first post, no update on yaffs needed
clemsyn said:
It would take awhile though since I have to remove my 2.6.32 kernel to put 2.6.25 since I'm limited in space. Donations for a laptop HD would be appreciated
UPDATE:
1. I think one of the reasons of data failure is that YAFFS refuses to write a checkpoint for our data partition. It writes it in the system partition with no issues. The new yaffs2 (updated 1-27-11 which I will update shortly) allows forcing checkpoint so I'll try that one and see if I can create a checkpoint on our data partition.
Click to expand...
Click to collapse
I have a 20 GB Sata laptop drive I could get to you. Used to be in a 360 and then broke the enclosure open for a hdd when the one in my laptop died. Drive works just fine, just small lol
aceoyame said:
I have a 20 GB Sata laptop drive I could get to you. Used to be in a 360 and then broke the enclosure open for a hdd when the one in my laptop died. Drive works just fine, just small lol
Click to expand...
Click to collapse
Sorry about your phone. I was hoping you could test out my new kernel. ANyways, I think yaffs2 was having issues creating a checkpoint on the data partition since yaffs was only creating a checkpoint on proper unmount (which was not done in our kaiser). The latest yaffs can make us force a checkpoint by simply typing the command in the first post and typing "Sync" on terminal automatically creates a checkpoint in data partition. I'm currently testing it now and seeing how it goes.
BTW, I'll take that donation re:HD since I can use it as an external HD and put the 2.6.25 kernel there and improve it (that is if wife permits).
clemsyn said:
Sorry about your phone. I was hoping you could test out my new kernel. ANyways, I think yaffs2 was having issues creating a checkpoint on the data partition since yaffs was only creating a checkpoint on proper unmount (which was not done in our kaiser). The latest yaffs can make us force a checkpoint by simply typing the command in the first post and typing "Sync" on terminal automatically creates a checkpoint in data partition. I'm currently testing it now and seeing how it goes.
BTW, I'll take that donation re:HD since I can use it as an external HD and put the 2.6.25 kernel there and improve it (that is if wife permits).
Click to expand...
Click to collapse
lol she's really not that strict, she just thinks my development for our devices is a waste of time. Just PM me where to send it and ill get it out to you.
aceoyame said:
lol she's really not that strict, she just thinks my development for our devices is a waste of time. Just PM me where to send it and ill get it out to you.
Click to expand...
Click to collapse
Agreed, that's what my wife thinks too I'll PM you my location
BTW, please make sure that the location of yaffs_auto_checkpoint is in /sys/module/yaffs/parameters (some ROM might have it on modules).
UPDATE:
Checkpointing is working great for me so far. Command on first post has to be executed in every reboot to create a checkpoint so typing the commands in first post before rebooting will create a checkpoint and save data partition (me thinks).
You can install Gscript and run the script before reboot
To verify if you have yaffs2 checkpoint in the data partition Type the following in terminal
su
cat /proc/yaffs
Scroll down to Device 2 "userdata"
blocks_in_checkpt should be 1 or 2 (not 0, if it is zero then you have no checkpoint in data partition)
Can anyone help adding this to the shutdown script?
I've done 5 restarts, 2 battery pulls and 2 resets, made sure data partition was checkpointed before doing so....So far data partition has been OK with no FC's or errors, no lost apps with 18mb's left in data partition The thing that surprises me is that Phone Storage size hardly changes in size in every reboots so it's good news I have a feeling we finally nailed down this data corruption issue, but only time can tell since I will shift to prolong use before doing any restarts...
I have sent a PM to scooter hoping he can help me with a shutdown script so we won't need a Gscript. So far, Gscript is doing it for me. Upong reboot, I run the script and make sure I have a checkpoint in data partiion
clemsyn said:
sent a PM to scooter hoping he can help me with a shutdown script so we won't need a Gscript. So far, Gscript is doing it for me. Upong reboot, I run the script and make sure I have a checkpoint in data partiion
Click to expand...
Click to collapse
I've got it working in a script, i have it in a script which is run on startup and then again on a successful shutdown. I'll upload a couple of updates in a bit
EDIT: I have attached 2 updates to the post, one is for cyanogenMod based builds and the other is for all other builds such as fresh froyo etc.
Clemsyn, i have the latest yaffs source compiled into the kernel, i will commit it to git in a bit. With the latest yaffs a checkpoint is created every time sync is executed which makes scripts easier!
scooter1556 said:
I've got it working in a script, i have it in a script which is run on startup and then again on a successful shutdown. I'll upload a couple of updates in a bit
EDIT: I have attached 2 updates to the post, one is for cyanogenMod based builds and the other is for all other builds such as fresh froyo etc.
Clemsyn, i have the latest yaffs source compiled into the kernel, i will commit it to git in a bit. With the latest yaffs a checkpoint is created every time sync is executed which makes scripts easier!
Click to expand...
Click to collapse
I downloaded the CM update, and it didn't enable the checkpoint, still had to enable it manually through terminal.
Testing the kernel right now however, and so far liking it.
scooter1556 said:
I've got it working in a script, i have it in a script which is run on startup and then again on a successful shutdown. I'll upload a couple of updates in a bit
EDIT: I have attached 2 updates to the post, one is for cyanogenMod based builds and the other is for all other builds such as fresh froyo etc.
Clemsyn, i have the latest yaffs source compiled into the kernel, i will commit it to git in a bit. With the latest yaffs a checkpoint is created every time sync is executed which makes scripts easier!
Click to expand...
Click to collapse
Thanks scooter, I'll try it out. I got stuck on a fake vsync and can't get out of it that I was unable to create a checkpoint and upon reboot without a checkpoint, everything was messed up. This is perfect, getting a checkpoint on startup and another in shutdown Thanks a lot.
Krazy-Killa said:
I downloaded the CM update, and it didn't enable the checkpoint, still had to enable it manually through terminal.
Testing the kernel right now however, and so far liking it.
Click to expand...
Click to collapse
That's weird! So it didn't make a checkpoint on startup? I'm running the same script and init.rc and it works fine. I did push the file with adb though, did you fix permissions after updating?
scooter1556 said:
That's weird! So it didn't make a checkpoint on startup? I'm running the same script and init.rc and it works fine. I did push the file with adb though, did you fix permissions after updating?
Click to expand...
Click to collapse
Ooooooh.... Probably not, lol. I'll do that, and edit this post with my results.
*EDIT* Ok, I feel stupid. I still had an old androidupdate.tgz file in my sdcard andboot folder, and the boot menu used it instead of the correct .tar file... Hm, that explained why my Market stopped working, lmao.
Krazy-Killa said:
Ooooooh.... Probably not, lol. I'll do that, and edit this post with my results.
*EDIT* Ok, I feel stupid. I still had an old androidupdate.tgz file in my sdcard andboot folder, and the boot menu used it instead of the correct .tar file... Hm, that explained why my Market stopped working, lmao.
Click to expand...
Click to collapse
lol, rookie error
OK, it works on boot up since I get a checkpoint 1 every boot not sure about shutdown but if scooter says it works, I bet you it works in shutdown too
Scoot, I'm going to try to do a git diff and post it here so all the changes I've made in the config will be there.
Even with that little debacle, I had 0 corruption of data, or missing apps in my /data partition, and had to reboot 4-5 times, each time I used GScript to execute the command manually before shutdown.
And camera still works. ^.^
Krazy-Killa said:
Even with that little debacle, I had 0 corruption of data, or missing apps in my /data partition, and had to reboot 4-5 times, each time I used GScript to execute the command manually before shutdown.
And camera still works. ^.^
Click to expand...
Click to collapse
That's great news and if my memory serves me right, you easily have data corruption in shutdowns and reboot. IMO, scooter's script is the best option we have for this issue and you don't have to remember to use gscript (especially from an old person like me with slight dementia Anyways, I'll continue on with my testing with this script. If it is still working after a few days, I'll try to add Namespace support, CIFFS, PPOE in our kernel.
BTW, here is my git diff and .config file. Please put it up in GIT. Thanks.
Hey all,
Wanted to post CM7 here for everyone to enjoy.
Neopeek has been working hard to get this build up and running, he's been doing great work!
Neopeek's Original Post - if you wish to see Neopeek's original post about the CM7 topic.
Also, since now I am using his new ClockWordMod method - CWM Recovery thread
As is stated in the title, this is mainly for devs/testers. Lots of things are broken, and there will be frequent updates.
There are two methods to using this build:
1) ClockWorkMod (requires 3 separate ext2 partitions)
2) Loop'd system.ext2 image (like XDAndroid) [In progress]
The benefit of #1 is a dedicated system/data partition, and *partial* USB mass storage support.
The benefit of #2 is, it's easier .
I still have to work to get #2 up, but I wanted to post #1 ASAP. Lots of work to flesh out the post to, be patient!
I've been holding off on releasing this CWM version of CM7, because I'm still having a lot of bugs with it. Still needs quite a bit of work, but it's getting late for me tonight - I am going to release it, let me know if you guys make improvements, I'd love to incorporate them!
Main issues seem to be related to my durn CDMA device. Need to break into some logs to see what's goin on, it may be a little while! I think GSM folk will be fine. Let me know!
Downloads
Download #1
How-to
Method #1 (ClockWorkMod)
****WARNING****
If you setup dedicated partitions using this method, normal XDAndroid builds will think that you want to use dedicated partitions. I had to modify the init to get it to work correctly (I basically broke the partition detection in the init). It's not pretty, but I don't know of a better way to resolve that issue - let me know what ideas you guys have!
Setup:
You will need to create three (3) ext2 partitions on your SD card. This is not extremely simple, but by no means impossible .
If you're using Windows, I like the Mini Partition Tool. If you're in Linux, I usually use gparted.
This takes a little bit of planning - but in total, I would say you need a minimum of 450mb of space for all three ext2 partitions. So work out how much free space is left (if you want a bigger data partiton, or system partition account for it!) and make that the first partition - FAT32. Make sure all the partitions are "primary", not "logical"! See the partition layout below:
1 - FAT32 Primary (remainder of card)
2 - ext2 Primary (at least 150mb, system partition)
3 - ext2 Primary (at least 250mb, data partition - I wouldn't go over 1gb here)
4 - ext2 Primary (at least 50mb, cache partition)
Don't worry about putting anything in these ext2 partitions, everything is populated by Android and CWM. The FAT32 partition is used to kick off Android, while system, data and cache are all ext2 partitions. Reason for this is, hopefully if things go haywire we can blast out cache, not data . Also, it should be easier to update using this method than previously.
Extract the file. Look at the folder it created (npkboot). Copy the entire npkboot folder to the root of your SD (for now this is required - the init assumes there's a /sdcard/npkboot/tmp folder). There will also be an update.zip, in this case update-cm-7.0.0-neopeek.zip. Put this at the root of your SD card (this makes finding it in the menu much easier!)
Copy the appropriate startup.txt from the STARTUPS folder.
Find haret.exe in th npkboot folder. Run it, and watch the boot process carefully! It will ask you to hold the vol down button to enter recovery, and you have 10 seconds to do so.
Assuming you manage to do this correctly (I had some trouble at first ) you should see an icon like a hat. Wait for the menu.
Buttons:
End key - back (back button seems to do this as well...)
Send key - enter
Vol up - up
Vol down - down (menu button seems to do this as well...)
If this is the first install, go to "install zip from sdcard". Then "choose zip from sdcard" This will install the system image to the system partition from the update.zip.
If you need to wipe the data partition, you can do that under "mounts and storage". You shouldn't need to do this unless you're going from gb -> froyo or visa-versa. Froyo -> froyo should 'just work', as always YMMV.
There are A LOT of options in replimenu. The only ones I have used are install, format /data, /system or /cache and Reboot. According to Neopeek, there are several things that should not be used:
Neopeek said:
* Don't use "factory wipe" in CWM (you have been warned )
* Don't use "format sdcard" unless you know what you do (you have been warned )
* Don't use "partition sdcard" unless you know what you do (you have been warned )
Click to expand...
Click to collapse
Once you've installed Android, go back to the main menu and "reboot system now" There are some bugs, for example "reboot recovery" and "power off" all just reboot the phone to WinMo.
Boot haret again, but this time don't hold the vol down to enter recovery - boot as normal!
#2: Much simpler method, similar to XDAndroid builds.
Extract the file to your desktop. Go into the CM7 folder, look for the STARTUPS folder - grab the appropriate startup.txt, move it to where haret.exe is.
Copy everything in the CM7 folder to the root of your SD card - if you want to run it from a folder, create a rel_path=CM7 statement in your startup.txt after the set cmdline (if you want a different folder, change the CM7.)
Grab the ts-calibration file attached to this post (for RHOD), or go to this post for a list of ts-calib's. You can also create your own on boot, but may have to revert to an older kernel to do so.
Run haret.exe!
****Not Working****
CDMA seems broken - still! I did some testing with hyc's RIL and it's still busted, so there's something in the system image messing with it - Airplane mode was checked, and I could not uncheck it.
In addition, phone.apk seems like a forceclosefest. Neopeek did point this out in his original thread...
Mobile data - broken (Fixed soon)
Wifi - broken (Fixed soon)
System needs optimization for RHOD - was originally build with DIAM in mind - so it's a little slow.
Failed wakes seem pretty bad - sometimes it is quite difficult to wake the phone.
Boot animation seems to be not present - I'm looking into fixing it, probably graphics libs if anything that's broke it.
Dev Content
This new method should be great for anyone who wants to make their own updates - you can easily peek into the system image and make changes at will, then just install the new system image! You can even rolll updates instead of an entire system image if you wish.
The script language in ClockWorkMod is called "Edify", see this thread to learn about the syntax. This is related to the META-INF folder you see in the update zip.
There's a few differences in the rootfs', the main being the init. There's also some additional files it looks like neopeek added for Recovery specifically.
This is amazing work. Props to all involved.
Does anyone have any feedback on this build?
arrrghhh said:
Long story short, you need a ext2 partition and a fat32 partition - ext2 needs to be between 400-600mb, fat32 can just take the remainder of the card's space.
Click to expand...
Click to collapse
Is there a reason for the 600mb upper limit? If I use 1 gb, will it cause problems or will it not use it and just waste card space?
PM message
Arrrgh,
Disregard the PM I sent you.
I read the instruction and like you said, its not simple. So I will wait until you upload the easy to run load.
Thanks
Ltilt2 said:
Arrrgh,
Disregard the PM I sent you.
I read the instruction and like you said, its not simple. So I will wait until you upload the easy to run load.
Thanks
Click to expand...
Click to collapse
Sorry, I need access to a Linux box to do the 'easy' build... I will when I get home tonight from work, promise .
vinceweis said:
Is there a reason for the 600mb upper limit? If I use 1 gb, will it cause problems or will it not use it and just waste card space?
Click to expand...
Click to collapse
You can make it as big as you want I guess... I'm not sure how neopeek sets up the data partition to be honest, I'd have to ask him.
Edit - in lieu of the post below, I adjusted the first post to say it needs to be at least 400mb .
vinceweis said:
Is there a reason for the 600mb upper limit? If I use 1 gb, will it cause problems or will it not use it and just waste card space?
Click to expand...
Click to collapse
I have 700 mb and is working well,you can use as much as you want
Ltilt2 said:
Arrrgh,
Disregard the PM I sent you.
I read the instruction and like you said, its not simple. So I will wait until you upload the easy to run load.
Thanks
Click to expand...
Click to collapse
Is easy just use mini tool partition wizard,delete the main partition on the sd-card
and do two,one fat32 primary and one ext2 primary,then extract the archive and put the proper startups in npkinstall and in root
from the phone run install.exe
and after the reboot use haret.exe
I wonder if CDMA data is working with this...that is my biggest issue with GB right now...
HELICOPTER88 said:
I have 700 mb and is working well,you can use as much as you want
Is easy just use mini tool partition wizard,delete the main partition on the sd-card
and do two,one fat32 primary and one ext2 primary,then extract the archive and put the proper startups in npkinstall and in root
from the phone run install.exe
and after the reboot use haret.exe
Click to expand...
Click to collapse
yeah easy for you to say, that sounds complicated.
I will wait for the other one.
Do you know the ETA?
i have
- downloaded the file cm7new.tar.gz
- made primary fat32 and ext2 partitions
- extracted the file cm7new.tar.gz to the root of the fat32 partition
- got a lot of linux folders
but i am missing
- npkinstall folder
- startup.txt
- install.exe
- haret.exe
- startup folder
Where are these files?
Tippfehler said:
i have
- downloaded the file cm7new.tar.gz
- made primary fat32 and ext2 partitions
- extracted the file cm7new.tar.gz to the root of the fat32 partition
- got a lot of linux folders
but i am missing
- npkinstall folder
- startup.txt
- install.exe
- haret.exe
- startup folder
Where are these files?
Click to expand...
Click to collapse
Still need to upload, sorry!
Tippfehler said:
i have
- downloaded the file cm7new.tar.gz
- made primary fat32 and ext2 partitions
- extracted the file cm7new.tar.gz to the root of the fat32 partition
- got a lot of linux folders
but i am missing
- npkinstall folder
- startup.txt
- install.exe
- haret.exe
- startup folder
Where are these files?
Click to expand...
Click to collapse
I was looking at that too when extracted the files and didn't see what you are also missing.
Sorry about the confusion guys, I probably shouldn't have put the download link up before I was done .
I just fixed it, so #1 is good to go! I'll get #2 up later, thanks.
Another noob question, but the rootfs, kernels, oc, etc from the xdandroid builds will work the same on these?
(...solved...)
it's necessary create a swap partition?
What works in this build?
fishingmedic said:
Another noob question, but the rootfs, kernels, oc, etc from the xdandroid builds will work the same on these?
Click to expand...
Click to collapse
The rootfs is more or less collapsed in these.
Kernels are straight from XDAndroid repo.
OC is the same, startup.txt is fairly similar .
Quincux said:
it's necessary create a swap partition?
What works in this build?
Click to expand...
Click to collapse
Swap is not necessary.
Most things that work in XDAndroid work in here. Lots of other things are broken here tho .
Okay, downloaded and installed without problems.
First impressions:
Absolutely great build in terms of response!
No delays in menus, etc.
Also, this looks like the first build that may have little or no clock delay, so no need for clocksync !!! (to be confirmed since I did not use it very long, die to issues below)
However...
1) No WIFI
2) No Mobile data (2G/3G)
3) camera not working (could be just blackstone)
- maybe other issues, decided to wait for more feedback before continuing, without market access there's little point...
Device: Blackstone
Kernel: extensive testing with provided one (1276), later switched to 1277, to fix audiostuttering, no wifi or mobile data in either...
As a reference, used many NeoPeek / XDAndroid builds, generally got WIFI/Mobile data working until now...
Love to hear if someone else (blackstone?) got WIFI/2G/3G working...
Oh, well, as I understood, this was an early "developer" release, still plenty of room for improvements!
Cheers,
Robbert
FroyoB Hercules V4 Final
This ROM is based on tiad8 new rom - thanks tiad8.
Changes:
changed back to old fonts!!!
add new launcher 2.3.3.
add new market.
changed phone - thanks to cytown from XDA.
changed theme.
some bug-fixing...
What works:
* SuperUser
* WiFi
* GPS
* 3G Network
* GPS
* Phone (new)
* SMS
* Good Battery Life
* camera
* camcorder
* new market
* youtube
How to install:
A. Download:
V1: http://www.multiupload.com/ZSOG83Q1K7
V2: http://froyob.blogspot.com/2011/07/froyob-hercules-v2-final-release.html
V3: http://froyob.blogspot.com/2011/07/froyob-hercules-v3-first-beta-release.html
V4: http://froyob.blogspot.com/2011/07/froyob-hercules-v4-final_18.html
B. Before install :
1. Format your SDCARD make 4 Partition with recommended size:
1st partition: FAT32 (sdcard / Rest)
2nd partition: EXT2 (system / 300MB )
3rd partition: EXT2 (data / 300MB)
4th partition: EXT2 (cache / 300MB)
Be sure make all 4 partition primary
2. extract and copy folder npkboot to root of sdcard and put in kernel that you like (I use kernel 1295 on my Raphael and it very good).
3. copy FroyoB_Hercules.zip in to root of sdcard.
C. Install:
1. run Haret, and wait when it will be asked to press "Volume Down" shortly (!!important!! shortly) to launch
ClockworkMod Recovery or any other key to usually continue booting into Android.
Press volume Down and wait for menu Recovery.
2. In menu recovery choose "install zip from sd-card" choose zip from sdcard and select "FroyoB_Hercules_V2_final.zip"
Confirm installation . after installation finish, Confirm installation then back to main menu (press ok key) and
choose: reboot system now.
3. Run HARET again and boot into Android.
when you report a bug please do it in this format:
1. my device is:
2. I'm using kernel:
3. I'm using Ver:
4. What CWM Ver:
5. the problem is:
thanks
Nebarkay
anyone tested this?
im coming from HD2, and wondering why you need all the 4 diffrent partitions? which program do you recommend to do this?
can you post any screenshots? would like to see before i go ahead an try
loni90 said:
anyone tested this?
im coming from HD2, and wondering why you need all the 4 diffrent partitions? which program do you recommend to do this?
can you post any screenshots? would like to see before i go ahead an try
Click to expand...
Click to collapse
The four partitions are laid out..
"1st partition: FAT32 (sdcard / Rest)
2nd partition: EXT2 (system / 300MB )
3rd partition: EXT2 (data / 300MB)
4th partition: EXT2 (cache / 300MB)"
However, cache is not necessary - especially not 300mb. I think neopeek recommended 50mb, but I don't think it's necessary at all.
Other builds in this section of the forum require only one FAT32 partition. This is because the data & system are just loop mounted.
For creating partitions I recommend this:
MiniTool Partition Wizard Home Edition
http://www.partitionwizard.com/free-partition-manager.html
it's free and very useful
loni90 said:
anyone tested this?
im coming from HD2, and wondering why you need all the 4 diffrent partitions? which program do you recommend to do this?
can you post any screenshots? would like to see before i go ahead an try
Click to expand...
Click to collapse
EASEUS Partition Master Home Edition for Windows is the fastest tool I've used. Haven't had any problems.
You need the partitions on your SD card because this ROM is in CWM format and will install to those EXT2 partitions (/system, /data, /cache). The order must be:
1. FAT32 (FAT32)
2. /system (EXT2)
3. /data (EXT2)
4. /cache (EXT2)
BE SURE TO REMOVE THE "/" WHEN NAMING THE PARTITIONS!! (I.E. "system", not "/system")
maff1989 said:
EASEUS Partition Master Home Edition for Windows is the fastest tool I've used. Haven't had any problems.
You need the partitions on your SD card because this ROM is in CWM format and will install to those EXT2 partitions (/system, /data, /cache). The order must be:
1. FAT32 (FAT32)
2. /system (EXT2)
3. /data (EXT2)
4. /cache (EXT2)
BE SURE TO REMOVE THE "/" WHEN NAMING THE PARTITIONS!! (I.E. "system", not "/system")
Click to expand...
Click to collapse
EASEUS is fantastic, I forgot it did ext2 as well. I use it to resize NTFS partitions all the time!
Can anyone confirm it working on Sprint TP2? and what does and does not work?
Thanks guys!
I installed on a Sprint TP2 last night but haven't really had a chance to drive it full throttle. Did try turning on BT unsucessfully. Getting longer life than FRX06 so far. Usually I have to charge before my 8 hour shift is done. Today I was able to go 11 hours with moderate use and still had 68% showing on the meter when I had a reboot to windows while trying to update an app. We'll see how it goes the next few days now that all of my apps are installed thanks to TB.
i keep on getting an issue with no signal. I did all the steps successfully but when it loads i get no signal. and then on reboot i get signal. I rebooted once again and now i have no signal what so ever. am i missing a step?
been using this for a couple of days...
device: at&t tilt 2
kernel: wistilt2
testing period: 3 days
battery: one full day... charge all night
signal... weak at times
system speed: awefully slow... worse then looped
3d: not terrible not great.. to be expected
conclusion: not for me.. too slow.. spotty signal... not the best battery life.. have seen better...
ok, now i know.
but i want to fix android to my lil´brothers TP2, and wondering what ROM i should use? which one is the most stable, and complete - and closest to stock? any good HTC sense roms?
loni90 said:
ok, now i know.
but i want to fix android to my lil´brothers TP2, and wondering what ROM i should use? which one is the most stable, and complete - and closest to stock? any good HTC sense roms?
Click to expand...
Click to collapse
Closest to stock and Sense do not go together. Sense is an abomination, horrid UI for Android. I don't get why it made WinMo so great but Android so horrid.
I recommend FRX06 myself, 07 is going to be out soon (promise!)
loni90 said:
ok, now i know.
but i want to fix android to my lil´brothers TP2, and wondering what ROM i should use? which one is the most stable, and complete - and closest to stock? any good HTC sense roms?
Click to expand...
Click to collapse
i have a really nice version of gingerbread that i am modifying... i will send you a zip if you want to try...
Trekfan422991 said:
i have a really nice version of gingerbread that i am modifying... i will send you a zip if you want to try...
Click to expand...
Click to collapse
I would very much love to give ur gingerbread build a try, so if u could please send me a zip as well. Thanks
villa15 said:
I would very much love to give ur gingerbread build a try, so if u could please send me a zip as well. Thanks
Click to expand...
Click to collapse
Actually I'm having one small problem... the android marketplace is only displaying like a few hundred apps...
I need to do some more research to find out why... so if you want me to fix it first or there are quite a few alternative marketplaces u can install... one I use on it right now is called--- 1 mobile market...
If you don't care I will send u the zip to try... it has gapps...
Just pm your email address
sooo, been testing this for a few days on my Rhod100... and have to say it pretty much sucks...
signal drops to 0 quite often, i get random reboots when trying to call someone / in call / when hanging up, apps that use the inet connection force close when i lose data connectivity (meebo, xda, gmail), the font is _horrible_ (yes i know, fontchanger is included, but it doesnt work the way one would expect it to)
to sum it up, it's like a F1 car without a steering wheel.. fast, fun for the first minute, but completely useless
going back to FRX06 looped and finally deleting NP from my favs
edit : forgot to mention the new audio code isnt integrated, so you cant use the new .39 kernel, but thats just the icing on the ****cake
Trekfan422991 said:
i have a really nice version of gingerbread that i am modifying... i will send you a zip if you want to try...
Click to expand...
Click to collapse
I would like to get it too. Thanks!
thanks for this rom
but when I started haret.exe file and press Run botton, I saw this message:
that default.txt doesn't found
what's problem?
bahaa87 said:
thanks for this rom
but when I started haret.exe file and press Run botton, I saw this message:
that default.txt doesn't found
what's problem?
Click to expand...
Click to collapse
You have to choose your startup.txt according to your device,there should be a folder called startup,check inside for your device and copy it where there's haret.exe
Thank you I tried the ROM on 1 / 7 is good and where some of the problems
I will work on this
CYANOGEN MOD BETA 1 FEATURES
Phone
WiFi
GPS (first time slow, next time very fast)
Data connections (GPRS)
Sensors (all)
2D/3D
MP4/3GP movie play (camera hardware button doesn't work yet)
Camera in photo (up to 5MP) and movie recording mode (we are working on new driver)
Bluetooth
ADB/UMS
Autobrightness
it's already rooted
Note1: There is a new parameter to startup.txt (vmalloc=256M), so if You are installing it manually also read README.
Note2: To change clock color go to SpicaGen Mod settings in settings menu.
FROYO BETA 3 FEATURES
-Phone
-WiFi
-GPS (because of another way of loading phone is a bit slower now)
-Data connections (GPRS)
-Sensors (all)
-2D/3D
-MP4/3GP movie play (camera hardware button doesn't work yet)
-Camera in photo (up to 5MP) and movie recording mode (it's still not 480p, but works)
-Bluetooth
-ADB/UMS
-Autobrightness
-It's already rooted
Note1: There is a bug when calling via BT or speaker, when screen goes off, only way to turn it on is finish call.
FROYO BETA 2 FEATURES
- Android 2.2 Froyo compiled from sources with some O2 optimizatios
- Phone
- WiFi
- GPS
- Data connections (GPRS)
- Sensors (all)
- 2D/3D
- MP4/3GP movie play (camera hardware button doesn't work yet)
- Camera in photo (up to 5MP) and movie recording mode (it's still not 480p, but works)
- ADB/UMS
- it's already rooted
LATEST NEWS & DEVELOPMENT
30.11.2011: CyanogenMod beta 1, update 1. Headset detection (3,5mm jack) update + today's kernel update (incomming call screen appearing fix) in one package. Download here.
30.11.2011: Kernel update. Kernel update contains incomming call screen appearing fix. Now it's instant. Download here.
28.11.2011: CyanogenMod beta 1. Introducing CM beta 1 (based on SpicagenMod 4 from voku). It's very fast, has IMEI working on beta2 phone image, has JIT enabled, I/O speed is increased. For both Americas there is an update script in case of phone not working.
16.11.2011: Froyo beta3, update 1 fix. Update contains kernel which fixes App2SD problem. Download here.
07.11.2011: Froyo beta3, update 1. Update contains following: sensors lib fixes, charging battery fixes, compass calibration caused discharging even when connected to usb, memory bug fix, reserved memory change (GUI should be smoother now), WiFi should connect now faster. Remember to reboot after update, because modules changed. Download here.
18.10.2011: Froyo beta3. Introducing working Bluetooth, autobrightness, phone working for all (IMEI is ok now, signal is much better), boot logo, , some other fixes like: proximity bug when calling, WiFi should obtain DNS addresses and sleep well now, reserved memory for 3D is increased - it should not cause white squares - result is less memory for system, that's why additional swap partition is created and used. Download:
Automatic install package - full install package for external SD. Experimental (not tested, but should work) install for Internal Storage - before using read included README file and make backup. Automatic installer requires 1160MB of SD space.
Beta2 to beta3 update - update from official beta2 (SD card install only).
20.09.2011: Automatic installer is ready for download. Check main site. Quick howto is available inside archive. It assumes that Your My Storage wasn't touched (so it is mmcblk1p5). You have to use 2GB SD card or bigger. If You already have two partitions eg. from first beta installer (vfat and ext2/3/4), it should only format ext2/3/4 partition and install android. Otherwise it will try to shrink existing fat32 and create new one with ext4.
17.09.2011: Froyo beta2 is ready for download (please check project site for link)! It contains new kernel (2.6.32.9) and many bugs fixed (ie. You don't need call light anymore).
MANUALS & GUIDES (BETA 2)
Note1: Pink screen at boot
It's normal because of no logo compiled in. If it's too long (longer than 30s) tap the screen. If this not helps, You probably set wrong partition in startup.txt.
Note2: WiFi
- There is a bug with WiFi. If it's on and phone go sleep, after wake there is a chance it would not work again. Only fix is to reboot. We suggest to turn off WiFi before suspending phone.
- Sometimes phone cannot connect to router (it connects, but no DNS addresses). Workaround: in build.prop uncomment following entries:
Code:
#net.dns1=8.8.4.4
#net.dns2=8.8.8.8
to:
Code:
net.dns1=8.8.4.4
net.dns2=8.8.8.8
Note3: Black screen after call
There is a bug in a phone call. When call is finished, screen stays black. Workaround is to swipe through proximity sensor
Note4: Automatic installer
Requires:
- untouched My Storage with automatic installer content
- ext4.tar.gz from manual install package
- at least 2GB SD card (class 6 at least will be enough) with one FAT32 partition or with 2 partitions (FAT32 + ext2/3/4)
Note 5: Manual install
Example: if You have two partitions on SD card (first vfat, second ext4) You should set in startup.txt following: root=/dev/mmcblk0p2. Full file example for this (do not change anything other, only root device):
Code:
Set ramsize 180*1024*1024
Set mtype 1626
Set ramaddr 0x50000000
Set kernelcrc 1
Set CMDLINE "rootdelay=2 root=/dev/mmcblk0p2 init=/init console=ttySAC2,115200"
setbitp 0x7F008808 5 1
pfw 0x7f005800 4 0x3
pfw 0x7f005804 4 0x805
pfw 0x7f005808 4 0x7
pfw 0x7f00580c 4 0x0
pfw 0x7f005828 4 0x11
pfw 0x7f00582c 4 0x80
boot
Note 6: Internal Storage Installation
If You want install on My Storage (Internal Storage):
mmcblk1p5 - by default is My Storage partition (this partition is mounted by default by Android as /storage)
mmcblk1p6 - by default is hidden partition
You have to resize mmcblk1p5, then create mmcblk1p7 (this will be root device in startup.txt) and format it with ext4.
Just a question: install android needs a hardreset my current WM settings?
I asked that because I have a lot of configurations at now (SPB Mobile Shell, Pocket Breeze, Pocket Weather etc.) and I really don't want to lose them or need to do all again.
Thanks.
hiroshi.rio said:
Just a question: install android needs a hardreset my current WM settings?
I asked that because I have a lot of configurations at now (SPB Mobile Shell, Pocket Breeze, Pocket Weather etc.) and I really don't want to lose them or need to do all again.
Thanks.
Click to expand...
Click to collapse
no need to hard reset,android has nothinf to do with wm except running haret ,Theoretically
no need to hard reset,android has nothinf to do with wm except running haret ,Theoretically
Click to expand...
Click to collapse
Thanks for your answer.
I'm a little affraid because I read here (http://forum.xda-developers.com/showthread.php?t=1066313) that I need to create a partition at 'My Storage'. So I think this operation will automatically hardreset my device.
the installation is the same as the beta 1??
Is the Zimage missing???
not anymore. zimage is up.
i m sorry. Where can find the updates? 2011-09-17
no link
There is no link.
Where can we find the package?
Modaco thread.
http://www.modaco.com/topic/346446-froyo-beta-2-for-omnia-2/
Project Download Page
http://o2droid.phj.hu/index_en.php
lalinde89 said:
the installation is the same as the beta 1??
Click to expand...
Click to collapse
Currently you'll have to do it manually, with Ubuntu.
damn. when i tried to partition the 2GB My Storage into 1000mb FAT32 and remaining 959mb ext4 (in ubuntu), i got an error when applying in gparted.
And now, all 2GB appears unallocated, and ubuntu cant mount anything. So im stuck. Tried creating a partition under Disk Utility, but it just hangs and doesn't do anything. At the same time, using windows 7, im stuck with 1000mb of FAT32 and 959mb that appears unallocated. Cant do anything to extend or delete the partitions (using disk management). All options are greyed out.
So now winmo can only effectively recognise 1GB of My storage. I effectively reduced my storage in half.
Anyone know what to do?
l3ong91 said:
Currently you'll have to do it manually, with Ubuntu.
Click to expand...
Click to collapse
I have extracted the ext4.tar to my ext4 partition on omnia 2 (i8000 8gb) as i always do.
Copied the startup and zimage to my root and changed the startup to reflect my partition. This works perfectly for beta 1
But all i got with beta 2 was a pink screen, so i waited for 10 minutes and nothing...
So i downloaded the debug zimage to see what's going on.
I can see it's "jumping to kernel" and then a cursor is blinking for a few seconds and then the screen goes all black.
Any idea what's going wrong?
exactly the same problem than fran_nic....
i'll tell you if i find a solution....
vpnair said:
damn. when i tried to partition the 2GB My Storage into 1000mb FAT32 and remaining 959mb ext4 (in ubuntu), i got an error when applying in gparted.
And now, all 2GB appears unallocated, and ubuntu cant mount anything. So im stuck. Tried creating a partition under Disk Utility, but it just hangs and doesn't do anything. At the same time, using windows 7, im stuck with 1000mb of FAT32 and 959mb that appears unallocated. Cant do anything to extend or delete the partitions (using disk management). All options are greyed out.
So now winmo can only effectively recognise 1GB of My storage. I effectively reduced my storage in half.
Anyone know what to do?
Click to expand...
Click to collapse
If gparted is not working for you, then try to re-format or delete all the existing partition on your My Storage using Minitool PArtition Wizard (Do it on Windows instead of Ubuntu).
---------- Post added at 07:46 PM ---------- Previous post was at 07:43 PM ----------
fran_nic said:
I have extracted the ext4.tar to my ext4 partition on omnia 2 (i8000 8gb) as i always do.
Copied the startup and zimage to my root and changed the startup to reflect my partition. This works perfectly for beta 1
But all i got with beta 2 was a pink screen, so i waited for 10 minutes and nothing...
So i downloaded the debug zimage to see what's going on.
I can see it's "jumping to kernel" and then a cursor is blinking for a few seconds and then the screen goes all black.
Any idea what's going wrong?
Click to expand...
Click to collapse
Did you do the extracting in Ubuntu? And did you set the destination to the correct partition?
First boot it will took some times for the pink screen to disappear, for me it's around 1-2 minutes, before the shiny Android logo pops out.
ok i have found a solution.
re-format sd card with g-parted under ubuntu.
-unmount device
- completly erased partitions.
- create new partition in fat32 in primary mode 7go
- create new parttion in ext4 in extended mode 1go
- extract . tar files in ext partition.
my first install was a 2go ext4 parttion , it seems to be the pb, i've read somewhere that if ext 4 partitions are more than 1.5 go = troubles.
hope i have help you....
l3ong91 said:
If gparted is now working for you, then try to re-format or delete all the existing partition on your My Storage using Minitool PArtition Wizard (Do it on Windows instead of Ubuntu).
---------- Post added at 07:46 PM ---------- Previous post was at 07:43 PM ----------
Did you do the extracting in Ubuntu? And did you set the destination to the correct partition?
First boot it will took some times for the pink screen to disappear, for me it's around 1-2 minutes, before the shiny Android logo pops out.
Click to expand...
Click to collapse
Yes i did the extracting in ubuntu. I checked my previous startup to be sure i had the correct partition cause it always worked.
fran_nic said:
Yes i did the extracting in ubuntu. I checked my previous startup to be sure i had the correct partition cause it always worked.
Click to expand...
Click to collapse
Then make sure you set to the correct partition in the startup.txt, coz for this 2nd version of beta is different from the froyo beta 1.
For your reference:
mmcblk(X)p(Y)
For (X): Root of partition
mmcblk0: SD Card (If you want to extract the ext4.tar.gz to SD Card)
mmcblk1: My Storage (If you want to extract the ext4.tar.gz to My Storage)
For (Y): Specific partition number
You need to find out what is the partition number of the newly created partition.
ie. if it's 2, then it will be mmcblk(X)p2
In this beta, it's normally p5,p6 or p7.
Hope this helps you understand better and good luck.
Thanks for your advise l3ong91.
Problem was... windows would see My Storage while ubuntu would not. Minitool was able to resize my partition so i could use all of it. BUT still ubuntu would not recognise. After a lot of work, i found the problem was in my micro usb cable. It was faulty. So i replaced that and voila! ubuntu mounted My Storage. I was then able to create the partitions. Unpack the ext4, set startup.txt to My Storage (mine was mmcblk1p2 after following youtubeguide by JerryTech11).... Then had to redownload zImage (as i download my version early on and it was 2.2mb while the current link is to 2.4mb). And android is now running! Hoping battery lasts a day with moderate use. If so my omnia 2 is once again my favourite device.
l3ong91 said:
Then make sure you set to the correct partition in the startup.txt, coz for this 2nd version of beta is different from the froyo beta 1.
For your reference:
mmcblk(X)p(Y)
For (X): Root of partition
mmcblk0: SD Card (If you want to extract the ext4.tar.gz to SD Card)
mmcblk1: My Storage (If you want to extract the ext4.tar.gz to My Storage)
For (Y): Specific partition number
You need to find out what is the partition number of the newly created partition.
ie. if it's 2, then it will be mmcblk(X)p2
In this beta, it's normally p5,p6 or p7.
Hope this helps you understand better and good luck.
Click to expand...
Click to collapse
Thanks for your reply.In beta 1 mystorage was seen as mmcblk0.
That was my problem.
I changed it to 1 and it boots perfectly.
Thank you very much for helping me out here.
What is Swap?
Linux divides its physical RAM (random access memory) into chucks of memory called pages. Swapping is the process whereby a page of memory is copied to the preconfigured space on the hard disk, called swap space, to free up that page of memory. The combined sizes of the physical memory and the swap space is the amount of virtual memory available.
Swapping is necessary for two important reasons. First, when the system requires more memory than is physically available, the kernel swaps out less used pages and gives memory to the current application (process) that needs the memory immediately. Second, a significant number of the pages used by an application during its startup phase may only be used for initialization and then never used again. The system can swap out those pages and free the memory for other applications or even for the disk cache.
However, swapping does have a downside. Compared to memory, disks are very slow. Memory speeds can be measured in nanoseconds, while disks are measured in milliseconds, so accessing the disk can be tens of thousands times slower than accessing physical memory. The more swapping that occurs, the slower your system will be. Sometimes excessive swapping or thrashing occurs where a page is swapped out and then very soon swapped in and then swapped out again and so on. In such situations the system is struggling to find free memory and keep applications running at the same time. In this case only adding more RAM will help.
Linux has two forms of swap space: the swap partition and the swap file. The swap partition is an independent section of the hard disk used solely for swapping; no other files can reside there. The swap file is a special file in the filesystem that resides amongst your system and data files.
I want that on my Phone, how to do that?
Okay, here goes the real story. Since Android is Linux, that would be possible.
What is needed:
- Fast (Class 10) Micro-SD Card, if you dont have class 10, class 4 would be great too..
- CWM or Partitioning software
- Root (of course )
- Terminal Emulator app
- Kernel with swap and init.d support (for example our CM7, 9, 10 and 10.1 ROM)
- Root Exploring app (for example Root Browser or Root Explorer)
Steps:
1. Partition your SD Card, Ask Google how to do that. Make new Swap partition, or you want SD-ext too..
2. Open Terminal Emulator, do:
Code:
su
fdisk -l dev/block/mmcblk0
3. You'll see something like this:
Code:
/dev/block/mmcblk0p3 1861 1924 514080 82 Linux swap
4. Do the following code, change with your exact swap partition:
Code:
su
swapon /dev/block/mmcblk0p3
*change 3 with yours
5. Now you can check your swap partition by doing:
Code:
free
Now we create the script to do that automatically at boot
1. Open Root exploring apps, head to /system/etc/init.d
2. Make a new file, named 05swap
3. Edit that file, copy this up:
Code:
#!/system/bin/sh
echo Swap enabled
swapon -a
4. Save it and change the permission to :
V V V
V V V
V V V
*tick all the boxes (rwxrwxrwx)
5. Now head to /system/etc and create new file named fstab
6. Open it and enter this:
Code:
/dev/block/mmcblk0p3 swap swap
*remember, change the 3 with yours
Now we set the swappiness value
*the normal value is 60, but you can change to what number you want (max 100). Higher may help to improve overall performance, while setting it to lower may increase interactivity and overall stability.
1. Do this on Terminal Emulator
Code:
su
echo vm.swappiness=60 >> /system/etc/sysctl.conf
2. Reboot and you're done.
Thanks to:
- Linux.com (for the swap definitions)
- Segnale007 (for the swap how to)
First! :laugh: No just kidding. Great guide! Maybe you should cover the Swapper 2, it does it without any second partition.
X-zone said:
First! :laugh: No just kidding. Great guide! Maybe you should cover the Swapper 2, it does it without any second partition.
Click to expand...
Click to collapse
Swapper2 doesn't working fine on my phone lol
I get a error on your first step
"fdisk: can't open 'dev/block/mmcblk0': No such file or directory"
EvilKing009 said:
I get a error on your first step
"fdisk: can't open 'dev/block/mmcblk0': No such file or directory"
Click to expand...
Click to collapse
u need to partition ur sdcard first
simple and exlcellent
Thank you very much for this. :good:
AngSanley said:
u need to partition ur sdcard first
Click to expand...
Click to collapse
EvilKing009 said:
I get a error on your first step
"fdisk: can't open 'dev/block/mmcblk0': No such file or directory"
Click to expand...
Click to collapse
Is because the command does not use system path, it assumes you're in '/'.
Just use
fdisk -l /dev/block/mmcblk0
Sent from my GT-S5660 using xda app-developers app
AngSanley said:
Now we set the swappiness value
*the normal value is 60, but you can change to what number you want (max 100). Higher may help to improve overall performance, while setting it to lower may increase interactivity and overall stability.
1. Do this on Terminal Emulator
Code:
su
echo vm.swappiness=60 >> /system/etc/sysctl.conf
Click to expand...
Click to collapse
I can't find this file! I am in JellyBean 4.2.2, maybe its different file?
/system/etc/sysctl.conf
blazzer12 said:
I can't find this file! I am in JellyBean 4.2.2, maybe its different file?
/system/etc/sysctl.conf
Click to expand...
Click to collapse
Create it, new file
Btw i say do it in the terminal emulator, its easier
Sent from my GT-S5660 using xda premium
Can Plead
Please provide a zip file
To install the Recovery
Thank
$ su
#
# fdisk -l dev/block/mmcblk0
Disk dev/block/mmcblk0: 7948 MB, 7948206080 bytes
4 heads, 16 sectors/track, 242560 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Device Boot Start End Blocks Id System
dev/block/mmcblk0p1 129 195840 6262784 b Win95 FAT32
Partition 1 does not end on cylinder boundary
dev/block/mmcblk0p2 195841 228608 1048576 83 Linux
Partition 2 does not end on cylinder boundary
dev/block/mmcblk0p3 228609 242464 443392 82 Linux swap
Partition 3 does not end on cylinder boundary
# free
total used free shared buffers
Mem: 285732 277168 8564 0 2584
-/+ buffers: 274584 11148
Swap: 443388 63756 379632
# swapon /dev/block/mmcblk0p3
swapon: /dev/block/mmcblk0p3: Device or resource busy
# free
total used free shared buffers
Mem: 285732 279088 6644 0 2592
-/+ buffers: 276496 9236
Swap: 443388 63240 380148
# swapon /dev/block/mmcblk0p3
swapon: /dev/block/mmcblk0p3: Device or resource busy
#
What is wrong? Is swap partition already on? I'm on M'rage rom.
Sent from my GT-S5660 using xda app-developers app
Excellent work man! :good:
It works perfect, but you should make flashable zip file for this work
i made flashable zip but at the moment dont have phone.. is this ok?View attachment swap.zip
doctor-who said:
i made flashable zip but at the moment dont have phone.. is this ok?View attachment 2880098
Click to expand...
Click to collapse
Anyone that tried this that can confirm if it works?
thanks
i am using Joyos 2. 3. 7. (Android)rom and this is what i get flashing the swam.zip...
E:error in storage/sdcard0/swap.zip
(status 0)
installation aborted
also adding the command su
echo vm.swappiness=60 >> /system/etc/sysctl.conf
cannot create /system/etc/sysctl.conf read-only file system
#
even after adding the files etc/sysctl.conf (with the aromat zip file manager) with read wright permission
i am using
Joyos 2. 3. 7. (Android)rom
Sent from my GT-S5660 using XDA Free mobile app
devrieshh said:
Joyos 2. 3. 7. (Android)
Sent from my GT-S5660 using XDA Free mobile app
Click to expand...
Click to collapse
WIll the flashable zip work with this rom?
p.s. - ANy change you can suggest another way for increasing the internal memory of the Gio?
Not yet,
See the result with flashing It,
E:error in storage/sdcard0/swap.zip
(status 0)
installation aborted
this happend also with the mmb. 7.2 rom
perhaps those roms havent- Kernel with swap and init.d support
things you can do,make an extra ext4 partition so you can put apps on it with special appstomemorycard programms see forum somewere
Sent from my GT-5660 using XDA Free mobile app
devrieshh said:
Not yet,
See the result with flashing It,
E:error in storage/sdcard0/swap.zip
(status 0)
installation aborted
this happend also with the mmb. 7.2 rom
perhaps those roms havent- Kernel with swap and init.d support
things you can do,make an extra ext4 partition so you can put apps on it with special appstomemorycard programms see forum somewere
Sent from my GT-5660 using XDA Free mobile app
Click to expand...
Click to collapse
thanks for the help and will try that solution. found a thread here with some interesting tips, so I'll have a go from there.
do everything manualy and will work... but i didnt felt some better ezxeprience with swap on my devixe with class 10 sd card... just read/write became decreased after few days using swap