Progress update and INT2SD implementation request form!
With holidays starting, and more free time on my hands, I've decided to revive this project. Having my hard drive fail on me recently, and losing the request log, it has become obvious that I need a new system of handling requests, and it is here. If you have requested a ROM before, please send a request again, via this form.
Please submit all further requests via this form!
---
This is the INT2SD thread for AOSP ROMs and their developers and users.
INT2SD thread for Sense ROMs
-
This is INT2SD, a new method of achieving D2EXT. It is meant for developers who wish to implement this functionality in their ROMs, since, due to the nature of the method, there is no way of making a flashable .zip which would be universal and work on most ROMs (yet?).
What differs this method from the old ways is that it uses no symlinks whatsoever.
INT2SD mounts an SD ext partition directly to /data, and this requires making changes to the boot.img, hence why universal flashable zips are not an option. The real userdata partition is mounted on /realdata and used for the e2fsck log.
Sorry for the link downtime, there were some critical bugs which I did not have time to fix. Therefore I took my time and added symlink checks, fixed fsck and more.
INT2SD-S - "Speed" (default as of 29th Jun)
Main characteristics:
/data on SD ext, /data/data on internal
/data/data limited to 280 MB (probably enough for more than 100 user apps)
noticeably faster on slower cards
for use with CM7r2 HBOOT
Description:
The new "speed" flavour mounts ext to /data and userdata to /data/data, achieving great speed while still retaining excellent storage capabilities. It's used with the CM7r2 HBOOT. This is now the default flavour, offering great speed while still being able to hold a hefty amount of apps.
INT2SD-M - "Mass" (discontinued)
Main characteristics:
/data on SD ext
number of apps is only limited by ext size
requires a faster card
for use with fatsys HBOOT
Description:
The classic "mass" flavour mounts ext to /data, thus eliminating the need for the mtd5 userdata partition. It has proven to be slow even on some of the faster cards. Due to INT2SD-S being able to hold a very high number of applications, and still being much faster, this flavour is discontinued.
FAQ
For users: How to get this in your favorite ROM
For ROM developers: How to get this implemented in your ROM
Please fill out this form.
Cross-device implementations
For now, no. You may submit requests, but I won't be able to fulfill them for a while. I have quite a lot of real life work on my plate, not to mention a list of Desire ROMs I have to tend to. After that's done, I'll be happy to try blind-porting it to whichever device you wish, but my priority are Desire ROMs, primarily because it's a lot easier to implement INT2SD into ROMs for a phone I already have.
Universal update zips
Also, no. Each ROM is different, and due to the nature of INT2SD, it is simply not possible to make a one-for-all universal update zip. Every ROM requires tending to its peculiarities, especially Sense ROMs, and I would rather not take the change of trying to make one and end up with a flashable bootloop zip.
Why don't you just publish instructions on how to implement INT2SD for devs to use?
Proz0r said:
You can take a look at the modified ROM and you will find 3 new files in /system/etc, dalchk, fsck and sleep. These files are executed by init.rc because of my modifications to it. You can also decompile the boot.img and use a tool such as diff or diffuse (a GUI for diff) and check the differences between it and the unmodified init.rc from Alex's standard, D2EXT ROM. However, his ROM required another init.d script to move weather animations to /data, and modifications to the updater-script to flash everything that would normally be flashed to /data, to be flashed to /sd-ext. Sounds simple enough, right? Well, it's actually not quite as simple. When I have first implemented INT2SD to CyanogenMod 7, all I had to do was edit a few lines and add those three scripts. There was not a single ROM (and there are a few unreleased ones which I've worked on) to which I could apply a "standard" procedure. Each ROM required further modifications on its own and being the one who devised INT2SD, I know what I should look out for in order to avoid catastrophical bugs. ROM developers do not. This is why I do NOT offer support for "homemade" INT2SD implementations. Every ROM has its own peculiarities that need tending to and INT2SD implementations need to be very flexible to allow the ROM to work in conjunction with it. Sure, everything could go great, but INT2SD is extremely easy to implement horribly wrong and have huge bugs and even unbootable systems, and without knowing what the dev did to put it in their ROM, it is next to impossible for me to troubleshoot and fix. It would probably end up with me having to implement it myself either way in most cases and having angry developers and possibly users on my hands being pissed at me for doing a bad job and releasing a ****ty product, when the problem was just a typo in init.rc. That's why I have not nor will I release instructions for devs on how to implement it themselves.
Click to expand...
Click to collapse
Instructions:
Pick your ROM featuring INT2SD, download it and flash it. You only need 1 ext2/3/4 partition. Due to /data/data being on the SD, a high-class card is recommended. Due to Gingerbread AOSP ROMs generally being pretty small, there's still quite a lot of unused space left on /realdata, to which I plan symlinking the /data/data directory so that INT2SD plays nice with lower-class cards too.
Remember to flash Google Apps, available here, if you opt for CyanogenMod.
All zips are signed for your convenience.
Flashing other kernels on top of these ROMs should work, though it hasn't been tested. If you try it, please let me know how it went.
EDIT: Seems there are people spreading false information on how this should be installed due to their own misunderstanding of my post. While I thought the instructions are simple enough, it seems they are too simple and do not describe the process. So, let me clear this up once and for all:
THE ROMS HERE ARE FULL ROMS THAT ALREADY HAVE INT2SD IN THEM.
THESE ARE NOT ADD-ON ZIPS.
Meaning, if you wish to use CM7 with INT2SD, just download CM7 from here. It is actually full CM7, along with INT2SD. So, the process is as follows:
Make a backup of all your apps
Download the full CyanogenMod 7 Stable ROM with INT2SD here
Do a full wipe
Flash it
Flash gapps
Restore your apps
Download:
Thanks to Ante0 for hosting the files!
INT2SD implemented in:
CyanogenMod 7.1.0 Stable INT2SD-M (Download)
CyanogenMod 7.1.0 Stable INT2SD-S (Download)
CyanogenMod 7.2.0.1 Stable INT2SD-S (Download)
GingerVillain 3.3 INT2SD-M (Thread | Download)
GingerVillain 3.3 INT2SD-S (Thread | Download)
Google Apps (not included in CyanogenMod)
It's compatible with Titanium Backup, here's how TB sees it:
{
"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"
}
Current bugs:
-
Credits (alphabetically):
Alex-V - providing me with the first Sense ROM to implement INT2SD in
brabo, GShellz admin - huge help with bash scripts implemented in the ROMs
CM - a base ROM for implementing the method in
Droidzone - suggestions, help with HBOOTs
Hacre - massive assistance as well, kicking me to try and realise the main idea and for coming up with names "INT2SD" and "fatsys"
JieeHD - help with compiling/decompiling the boot.img files and his excellent guides on FYA
Pulser_g2 - massive assistance, ideas on the reboot bug and hosting
Richard Trip - making GingerVillain which now has a version featuring INT2SD
snq- - pointing out a huge typo and saving me multiple hours of pointless work
ubuntubhoy - a kick in the arse I needed
... and everyone else in the #villainrom IRC channel for help and mental support! Thank you all, and everyone I forgot to mention (PM!).
Disclamer: I'm not responsible if something goes wrong and wreaks havoc upon you, your phone, your card, any part of your phone, your friends, your family, your close or distant relatives and/or your pet, but I will gladly provide assistance if it does.
Changelog:
v2.0.1
Small bugfix
v2.0
Dalvik cache is now by default on /realdata (the actual userdata partition) EDIT: Nope, not a good idea, thanks Droidzone!
Fixed fsck
Implemented lots of failsafes and small fixes
v1.0
First stable version
One version for ext2, ext3 and ext4 partitions
Implemented e2fsck (cheers Hacre!)
Reboot bug fixed (cheers Pulser!)
Real data partition is now mounted on /realdata (used only for e2fsck log)
v0.1
First beta version
Sretno!
nice work, I will try it !
This is very nice in theory and I hope devs notice your initiative. Just one question though, if ext is mounted as a /data partition, what happens to the real /data partition then? Is it merged with the ext or something else? Don't see an explanation in the first post. Thanks mate and keep up the good work. With no symlinks this could be somewhat of a speed booster for our roms for people that use higher class sd cards.
Cheers rayiskon and TomWan!
PlayPetepp, nothing happens, it simply isn't used, or even mounted. I wish I could merge it with the ext partition, but due to several issues this isn't possible.
Can /data then be mounted as /sdext? Just so there's no losses.
It can, but I intentionally avoided doing that so there was no confusion among users. Besides, I don't see what it could be used for anyway.
I could do a special version which does that, though
PlayPetepp said:
This is very nice in theory and I hope devs notice your initiative. Just one question though, if ext is mounted as a /data partition, what happens to the real /data partition then? Is it merged with the ext or something else? Don't see an explanation in the first post. Thanks mate and keep up the good work. With no symlinks this could be somewhat of a speed booster for our roms for people that use higher class sd cards.
Click to expand...
Click to collapse
Proz0r said:
Cheers rayiskon and TomWan!
PlayPetepp, nothing happens, it simply isn't used, or even mounted. I wish I could merge it with the ext partition, but due to several issues this isn't possible.
Click to expand...
Click to collapse
PlayPetepp said:
Can /data then be mounted as /sdext? Just so there's no losses.
Click to expand...
Click to collapse
Proz0r said:
It can, but I intentionally avoided doing that so there was no confusion among users. Besides, I don't see what it could be used for anyway.
I could do a special version which does that, though
Click to expand...
Click to collapse
you can change the hboot and make system partition bigger and data smaller..so you dont need to symlink system apps or libs....
Symlinking system apps or libs? There's no need of doing that in the first place
Proz0r said:
It can, but I intentionally avoided doing that so there was no confusion among users. Besides, I don't see what it could be used for anyway.
I could do a special version which does that, though
Click to expand...
Click to collapse
Devs would probably find a use for it since it's additional space on the phone. Imagine having all your apps and other stuff like boot/downanimation on /data and only dalvik, and I mean only dalvik, on /sdext (using your partitioning method ofcourse). That's my understanding of it so far.
-. typewrited .-
Alex-V said:
you can change the hboot and make system partition bigger and data smaller..so you dont need to symlink system apps or libs....
Click to expand...
Click to collapse
That's one of the uses I also had in mind. Could lead to a better responce of the rom in general.
-. typewrited .-
Proz0r said:
Symlinking system apps or libs? There's no need of doing that in the first place
Click to expand...
Click to collapse
I guess he was thinking of bypassing symlinking alltogether. Just like you.
-. typewrited .-
Yeah, I think putting just Dalvik on the real userdata partition could be done, that's a great idea, thanks!
Ah, you mean for the Sense ROMs which symlink stuff to the sd-ext! Yeah, the /system partition could be enlarged, even to the point where userdata is only a few megabytes in size since it doesn't even get mounted as is. I'll leave those things to someone else though, since I'm not great editing partition tables
PlayPetepp said:
That's one of the uses I also had in mind. Could lead to a better responce of the rom in general.
-. typewrited .-
Click to expand...
Click to collapse
PlayPetepp said:
I guess he was thinking of bypassing symlinking alltogether. Just like you.
-. typewrited .-
Click to expand...
Click to collapse
Proz0r said:
Yeah, I think putting just Dalvik on the real userdata partition could be done, that's a great idea, thanks!
Ah, you mean for the Sense ROMs which symlink stuff to the sd-ext! Yeah, the /system partition could be enlarged, even to the point where userdata is only a few megabytes in size since it doesn't even get mounted as is. I'll leave those things to someone else though, since I'm not great editing partition tables
Click to expand...
Click to collapse
Thats what i make since a half year or so...withthe 387mb system hboot and take the sd-ext with data2xxxx scripts as data partition.... lol to make the system faster without symlinks...
using nands data partition (internal) for dalvik is a bad idea...because it can be that you cant install apps but you still have free sd-ext because of data is full with dalvik because of internal
instead its better to move dalvik to sd-ext and use a odexed rom...so the dalvik (odex) from system apps and framework is internal...and only third party apps dalvik is extern...
this make system fly also whith data2xxxx scripts
anyway...good idea...i will try the script also
with kind regards
Alex-V said:
instead its better to move dalvik to sd-ext and use a odexed rom...so the dalvik (odex) from system apps and framework is internal...and only third party apps dalvik is extern...
this make system fly also whith data2xxxx scripts
Click to expand...
Click to collapse
PlayPetepp is one of the supporters of the odexed roms idea, i remember he mentioned it a while ago through pm i am too in a way, although it makes it a lil harder to customize stuff, i don't feel like using smali and baksmali everytime i want to do a battery mod or stuff like that despite it's advantages regarding speed.
nways, i think this script can be very helpful for future plans.
This is my idea for deodexed roms: /system as it is (cm7r2 hboot preferably), ext mounted as /data and data as /sdext. Now, all apps and other rom stuff that can't go to /system go to /data and only dalvik goes to /sdext. That way, there's still enough space for all apps and for dalvik because, let's face it, you'll hardly fill up 287mb with just dalvik. I have like 100+ apps on my phone and after moving dalvik to ext I got 160mb more space on /data so that's the size of dalvik.
Odexed roms are different but actually the same could be applied. Since /data gets bigger we can still use /sdext as a place for dalvik since it will be occupied with only installed apps dalvik and no framework/system dalvik (since it's odexed and everything goes to either /system or /data). Then free space would be evened out with apps going to /data where some odexed apps are stored. The only downside would be symlinking but there would be no need to change hboots. Am I making any sense here?
rayiskon said:
PlayPetepp is one of the supporters of the odexed roms idea, i remember he mentioned it a while ago through pm i am too in a way, although it makes it a lil harder to customize stuff, i don't feel like using smali and baksmali everytime i want to do a battery mod or stuff like that despite it's advantages regarding speed.
nways, i think this script can be very helpful for future plans.
Click to expand...
Click to collapse
i dont say anything bad...i know that he is a good man ..lol..i only say that this way of rom..speed things..is the way i do for around a half year..but he or michael..never ask me...maybe for tips or soo..
you dont need to deodex if you want change battery or so...first: UOT have a odex support...second: framework-res.apk and com htc resources apk is never odexed (also not in original htc roms
PlayPetepp said:
This is my idea for deodexed roms: /system as it is (cm7r2 hboot preferably), ext mounted as /data and data as /sdext. Now, all apps and other rom stuff that can't go to /system go to /data and only dalvik goes to /sdext. That way, there's still enough space for all apps and for dalvik because, let's face it, you'll hardly fill up 287mb with just dalvik. I have like 100+ apps on my phone and after moving dalvik to ext I got 160mb more space on /data so that's the size of dalvik.
Odexed roms are different but actually the same could be applied. Since /data gets bigger we can still use /sdext as a place for dalvik since it will be occupied with only installed apps dalvik and no framework/system dalvik (since it's odexed and everything goes to either /system or /data). Then free space would be evened out with apps going to /data where some odexed apps are stored. The only downside would be symlinking but there would be no need to change hboots. Am I making any sense here?
Click to expand...
Click to collapse
i was full with dalvik on data (internal) in the past...with older data2ext and whatever scripts...and also other people (i had the same thinking as you...once a day a person say..he cant install apps but he have free memory...it was a full data partition because of dalvik)...
but idea is nice...anyway dalvik is on sd-ext if i understand it right..so no limit of 2xx mb..or..?
yes symlink some files and you dont change hboot...but if you use data2xxx scripts with dalvik to sd-ext you dont need the data partition because sd-ext is data...so you can make the system partition bigger and dont need symlinks...so rom will be faster...mmmhh but this is maybe only my personal feeling...?!?
with kind regards...Alex
@Alex-V & other People here:
Hi guys,
I'm from the Nexus One forum, and I'm looking for a better script for my HyperSense ROM, based on the AceSMod007-v41 by michael.
I was trying to understand how can I modify my ROM having only dalvik-cache into an sd-ext folder... I have succesfully transferred all the stuff into /system with a modified HBOOT and so I have only a /data folder with some apps.
Obviously /data partition will have only around 70mb remaining for apps. So it's a must that I can transfer dalvik-cache to sd-ext.
How can I do?
Thanks!
Iperzampem0 said:
@Alex-V & other People here:
Hi guys,
I'm from the Nexus One forum, and I'm looking for a better script for my HyperSense ROM, based on the AceSMod007-v41 by michael.
I was trying to understand how can I modify my ROM having only dalvik-cache into an sd-ext folder... I have succesfully transferred all the stuff into /system with a modified HBOOT and so I have only a /data folder with some apps.
Obviously /data partition will have only around 70mb remaining for apps. So it's a must that I can transfer dalvik-cache to sd-ext.
How can I do?
Thanks!
Click to expand...
Click to collapse
what script you use at the moment...?
Related
Introducing...
Darktremor Apps2SD 2.7.5.3 Beta 04
Date of Release: January 29, 2011
Download Current Version
Instructions - Change Log - Commands - ROM List - Developer's Guide
Darktremor Apps2SD Fan Page ----
Darktremor Apps2SD Development Group
Are you installing Darktremor Apps2SD on your phone? Here are the instructions to help you: Facebook
Are you a developer wanting to include Darktremor Apps2SD in your latest ROM? Here is the Developer Guide: Facebook
Click to expand...
Click to collapse
Update on Beta 4
It seems I'm getting mixed results with these betas. I'm not sure why this is occurring, some people have been able to get this working right while others have had a hard time with it.
Currently, I'm rebuilding the entire program. This takes a while because I have to figure out how to pack all these options into the program but make it small enough to where it will run correctly.
I will say that some of the beta features are coming back out...one of them is the search for a partition code. I suspect that code may be leading me into issues with certain platforms, so I'm going back to the 2.7.5.2 method of mounting (mmcblk0p2 or mmcblk1p2).
Also, parts of the code will use Busybox Ash (the only code that won't will be starta2sd, which will still use Bash for the time being). The startup code will definitely use Busybox Ash.
Until then, here are the links to the the last two betas and the last official release:
Version 2.7.5.3 Beta 04 - http://www.darktremor.info/files/a2sd/dtapps2sd-2.7.5.3-beta04-signed.zip
Version 2.7.5.3 Beta 03 - http://www.darktremor.info/files/a2sd/dtapps2sd-2.7.5.3-beta03-signed.zip
Version 2.7.5.2-1 - http://www.darktremor.info/files/a2sd/dtapps2sd-2.7.5.2-1-signed.zip
And, if you want past versions, you can view the repository: ftp://dtuser:[email protected] (ignore the smiley face...that's XDA doing that.)
Click to expand...
Click to collapse
Beta 04 took longer than I expected to release. I have done major changes to the code:
1. New commands: convert-ext4 - This will convert your EXT3 partition into EXT4. Just a friendly reminder on this command: Not every rom supports EXT4, so it is possible to go into a boot loop if you switch roms. Use with caution.
2. Reworked convert-ext3 (convert-ext4 gets similar code)...now a flag file is set before the reboot (no conversion is done before the reboot). At load time, the conversion is performed. This takes longer in the reboot process and you may think your phone has locked up...wait about five minutes before doing anything with the phone.
3. Repair is rebuilt...now it uses existing commands to repair the setup (reinstall, remove, cachesd, cachepart, nocache, datasd, nodata). Definitely shrinks the code.
4. Added fix_permissions program to the package. This may help with Superuser issues when using the datasd feature. It is used in reinstall, remove, datasd and nodata.
5. a2sd install is back!!! Both a2sd install and a2sd reinstall do the exact same thing.
6. Dalvik heap code has been shrunk and now creates a file called dalvikheap. Actually, the code has been doing this all along (since about 2.7.5.2, I think), but I never put the code in to use the file.
7. Low Memory Killer code has also been shrunk and uses a file caled dtset_lowmem to set the low memory killer parameter.
8. Replaced Busybox PS function with Toolbox PS. The issue with Busybox PS is that it gives a false reading when I look for android.process.acore (which is the main program when the GUI starts up). If that is present, the program thinks you are trying to run Darktremor without any command line parameters. This was because Busybox would report the process was there when, in reality, it wasn't (validated this when my phone was boot looping.) Toolbox's PS reports the correct setting. This should fix the bootlooping issues some people are experiencing.
9. New commands: usedtbusybox and usedefaultbusybox - these commands may help in diagnosing issues that is may be related to the native Busybox on your rom. a2sd usedtbusybox will use the Busybox that is packaged with Darktremor. a2sd usedefaultbusybox will turn back on the scan behavior of the program introduced in Beta 03.
10. Support for Darktremor Apps2SD version 2.7 and earlier has been discontinued. To upgrade correctly from one of those versions, use version 2.7.5.3 Beta 03b or earlier.
11. Finally fixed stalled boot issues (or at least my tests with several roms says so.)
See the change log for additional details.
You will notice that if the program runs repair and finds a problem, it will correct the issue and reboot. You will see a second reboot when the dalvik-cache clears (this is to fix timing issues with CyanogenMod...I can't control that startup as well as I can other roms). This only happens if repair is ran or you flash a new rom (as repair will realign all data). If you are upgrading from a previous version of Darktremor, you should not see the reboots.
Click to expand...
Click to collapse
This is Darktremor Apps2SD, a multipurpose program that primarily allows a user to execute applications created for the Android OS on their Secure Digital card (with the proper setup...more on that later). But, Darktremor Apps2SD is all about stability. The goal is to be able for all users of the Android OS to be able to take advantage of a method to run their applications from a secure digital card.
But just because the Darktremor Apps2SD is all about stability, doesn't mean it isn't packed with features:
- Move applications (both free and paid) to the Secure Digital card.
- Move Dalvik Cache to run either from your Secure Digital card or from your cache partition and clears the cache on demand.
- Boot Loop Protection: prevents the phone from boot looping in the event the SD card could not be mounted.
- Dalvik JIT for faster performance on Roms which support it.
- User selectable sizes for the Dalvik heap sizes, allowing a user to freely optimize their system.
- Activate a swap partition on your SD card and sets how often the swap partition is utilized.
- Automatically fixes configuration issues.
- Users can check the free space on their SD card and check the installation to make sure all is setup correctly.
- Runs ZipAlign on demand...this makes your programs load faster.
- Built in help system for easy reference of commands.
- All features can also be reversed without repartitioning your Secure Digital card.
- New logging features assists in troubleshooting issues.
- Commands to set the Low Memory Killer feature at boot time. Great for those people who are the "set it and forget it" type.
- And more...
Darktremor Apps2SD is not the same as Froyo Apps2SD. Froyo Apps2SD creates a secure folder on the FAT32 section of your SD card (this is the section that you see when you mount your phone to your computer) and stores the programs there. This is nice as you don't have to do anything special with the phone, but it isn't backwards compatible with older versions of Android (Cupcake, Donut, Eclair) and, because of the way Froyo works, older programs not designed for Froyo will automatically stay on your internal storage (unless you install a program that forces the move to your SD card).
Darktremor Apps2SD takes a different approach. Based on the original CyanogenMod works, Darktremor Apps2SD uses symbolic linking to force Android into moving your applications to the SD card. Because Android will not allow anything to be ran from the FAT32 partition on your SD card (and, in Froyo, it will only allow you to run programs from a special folder), Darktremor utilizes filesystems called EXT2, EXT3 and EXT4. Each one of these filesystems is native to Linux (the operating system running Android), which allows you to run programs from them (same as, say, a computer running Ubuntu). This method is completely compatible with all versions of Android, including Froyo. In fact, you can run both the Darktremor Apps2SD and Froyo Apps2SD at the same time.
Check out the list of Roms that either have Darktremor Apps2SD installed or are compatible with Darktremor Apps2SD. Click on the link labeled ROM List at the top of this message.
Darktremor Apps2SD Installation Instructions
For the list of people that helped me test this on the various roms that use or can use Darktremor Apps2SD and the changelog: http://forum.xda-developers.com/showpost.php?p=7034326&postcount=3
Click to expand...
Click to collapse
The installation instructions can be found here: http://forum.xda-developers.com/showpost.php?p=7021325&postcount=2
Click to expand...
Click to collapse
If you want a list of commands for Apps2SD, type a2sd help.
Reserved...
Is there any chance we may have the option to store text messages on the SD card using a system similar to Apps2SD?
That would probably be dependent on the program you use. I was experimenting on moving the /data/data folder to the SD card. Unfortunately, I wasn't successful with it retaining settings during the move.
I did take out the code that forces /data/data to stay on the data partition, so if you want to move the /data/data folder to, say, /system/sd/data, you can.
I have the option in Darktremor A2SD 2.7.5 Alpha (based on 2.7 Update 1. The current code is based on 2.7 Update 3r1), I will put it in again if you wish to experiment with it (though I will leave it undocumented until it is proven successful).
`
Jykinturah said:
Is there any chance we may have the option to store text messages on the SD card using a system similar to Apps2SD?
Click to expand...
Click to collapse
tkirton said:
That would probably be dependent on the program you use. I was experimenting on moving the /data/data folder to the SD card. Unfortunately, I wasn't successful with it retaining settings during the move.
I did take out the code that forces /data/data to stay on the data partition, so if you want to move the /data/data folder to, say, /system/sd/data, you can.
I have the option in Darktremor A2SD 2.7.5 Alpha (based on 2.7 Update 1. The current code is based on 2.7 Update 3r1), I will put it in again if you wish to experiment with it (though I will leave it undocumented until it is proven successful).
Click to expand...
Click to collapse
To be honest, I am quite new with Android development. I think I will look at some documentation and such before I begin experimenting. Maybe I should do an adb pull of /data/data and look at the stuff there.
If you don't mind, I may request for it later.
Sure. Not a problem.
Jykinturah said:
To be honest, I am quite new with Android development. I think I will look at some documentation and such before I begin experimenting. Maybe I should do an adb pull of /data/data and look at the stuff there.
If you don't mind, I may request for it later.
Click to expand...
Click to collapse
Hi, what is he best heap size to use?
Also, can I use apps2sd on the updated 1.47 rooted ROM based on the OTA simply by flashing?
Normally on the Hero (the one I use), the heap size is 16mb (a2sd smallheap). DamageControl uses a heap size of 24mb (a2sd largeheap), which seems to make dalvik-cache runs faster. I included a 32mb heap setting (a2sd jumboheap) that I thought would be perfect for the added memory of the Evo.
Honestly, I'm not sure which one is better. I personally can't tell the difference between them. I would experiment between them and see...but I'm not sure you'll get a noticeable difference unless you clear your dalvik-cache.
As for running Apps2SD on the updated 1.47 rooted rom...if it is a stock rom, it won't run. This is because the stock rom by itself does not have the necessary components to launch any version of Apps2SD (CyanogenMod, Darktremor, DamageControl). Myself and another developer injected the Apps2SD functions in our stock rom and released it (it was just a stock rom...no other modifications was done). So, someone would have to inject the Apps2SD functions into the stock rom.
freeza said:
Hi, what is he best heap size to use?
Also, can I use apps2sd on the updated 1.47 rooted ROM based on the OTA simply by flashing?
Click to expand...
Click to collapse
Partition Size
Just received my 16G (C6) SD card and was wondering if anyone had recommendations for initial sizing of the partitions? Originally did a 50/50 split, but second guessing myself.
I have 4GB, but that's a bit excessive. Try around 1-2GB for the ext and, depending if you want a swap partition, 32MB for swap. All the rest goes to FAT32.
dpilcher said:
Just received my 16G (C6) SD card and was wondering if anyone had recommendations for initial sizing of the partitions? Originally did a 50/50 split, but second guessing myself.
Click to expand...
Click to collapse
Preview Fix 2 is out...more corrections to JIT (seems this one is hard to get my hands on).
tkirton said:
I have 4GB, but that's a bit excessive. Try around 1-2GB for the ext and, depending if you want a swap partition, 32MB for swap. All the rest goes to FAT32.
Click to expand...
Click to collapse
Thanks for the feedback. I moved to 3G, but will probably take that down to 1.5 (or almost 3 times the phone's internal system memory correct?) Don't think I will enable a swap, even though it's a C6 with protection elements on the card, don't want continual rw.
I have swap on mine and I don't see any ill effects.
But you have an Evo, which has twice the memory of the Hero. You probably would benefit without a swap file.
dpilcher said:
Thanks for the feedback. I moved to 3G, but will probably take that down to 1.5 (or almost 3 times the phone's internal system memory correct?) Don't think I will enable a swap, even though it's a C6 with protection elements on the card, don't want continual rw.
Click to expand...
Click to collapse
Guide to add Apps2SD to roms
I have added a guide on my main thread that shows you how to add Apps2SD support in roms that don't have it.
http://forum.xda-developers.com/showthread.php?t=715116
Bump...Preview Fix 4 is out (yes, I skipped PF3...Desire users got that one).
I'm trying to get apps2SD to work with the DC ROM and I'm not seeing this partition selection. When I click on partition, a menu opens up that says a lot about mount and unmount. Also says something about format boot, system, data,cache, sd card, sd-ext. Any help would be appreciated!
tkirton said:
I have swap on mine and I don't see any ill effects.
But you have an Evo, which has twice the memory of the Hero. You probably would benefit without a swap file.
Click to expand...
Click to collapse
I know this is probley a stupid question but whats the benefit of this?speed? And if so, is it a big differnence? Thanks
Are you trying to get Darktremor Apps2SD to work or the one already included with DamageControl.
If it is Darktremor, the GUI setup in DamageControl is not compatible. You need to use the commands via Terminal or adb shell. Type a2sd help for a list of commands and a description of what they do.
pastert33 said:
I'm trying to get apps2SD to work with the DC ROM and I'm not seeing this partition selection. When I click on partition, a menu opens up that says a lot about mount and unmount. Also says something about format boot, system, data,cache, sd card, sd-ext. Any help would be appreciated!
Click to expand...
Click to collapse
The only benefit is that it will allow programs to stay in memory longer. It is a little faster, but not significant.
Most people don't even bother putting a swap partition.
Using a program like Autokiller, which adjusts the values of the built-in auto termination routine, would benefit you far better than swap.
brownmc77 said:
I know this is probley a stupid question but whats the benefit of this?speed? And if so, is it a big differnence? Thanks
Click to expand...
Click to collapse
SleekSense-1.0 Officially Stable
Caution this rom uses a new format unlike any other rom. Which means it requires a ext partition. If you do not have one it will not boot and/or install. To see how to do one read the install section.
SleekSense has took a new approach. Instead of being themed like before. It is now has very little themeing. This is was done to keep the sense look more. Though it does have some themeing (Check the screenshots). SleekSense is built from the uscc froyo ruu with features you will love. On stock sense you have something around 100mb free. With this rom you will have 240mb free on boot. This doesn't seem like a lot but it also supports darktremors apps2sd+. Which means take angry birds for exmample is like 10mb. Around 8mb of it will be installed to the ext partition with 2mb on the internal memory. If so some how manage to run out of memory dalvik cache can be moved to the sd card. Though by default this wasn't done. The main reason is it slows the rom down to a crawl if on the stock card. If on a higher class card it can be enabled.
This also packs things not in any other rom. For a short list of what this has over any other sense rom here we go. Supports undervolting, powersave govenor, conservative govenor, cfq scheduler, ram optimization tweaks, perflock disabler, zipalign on boot, screen state scaling, reboot options, bloatware removed and numerous other things. Check below screenshot for a full feature list.
Any way on to the screenshots:
{
"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"
}
Things Removed:
Uscc boot animation and boot sound.
Stock bookmarks & homepage (Homepage is defaulted to google)
Toneroom
My Contacts Backup
CityId
Some different languages out of the frameworks (English is fully supported)
Unused images and codes out of the frameworks
Basically debloated but all the features of sense is still there (From the widgets to the live wallpapers)
What is Done/Added:
Dodexed entire rom to allow themeing
Optipnd'd almost the whole rom
Framework optimizations
Prerooted
Init.d support
Busybox
Nano
Bash
Apps people may not use or updates moved to data (AdobFlashplayer, AdobeReader, Facebook, OiFileManager, Gmail, Maps, Myspace, QuickOffice, Street, YourNavigator and Youtube)
Darktremors apps2sd+ with dalvik to sd-ext on boot disabled
Able to be undervolted now (Uses almost the exact voltages of my vork kernel)
More govenors now (PowerSave & Interactive)
Default scheduler changed to Cfq
Perflock on boot disabled
ZipAlign on boot (First boot will be sort of slow as it checks and zipaligns apk's. From then on it remembers what ones were done and only zip aligns ones that have been installed)
Screenstate scaling of cpu to save battery life
Backlight Settings tweaked along with backlight on buttons tweaked (Little bit dimmer to & backlights on buttons do not stay on unless on the lowest screen setting saving battery life)
Build prop tweaks to conserve battery and increase speed
Ram optimizations to futher more conserve battery and increase speed (Do not run a task killer it will only mess it up. Multitasking should greatly be increased.)
Custom boot animation (Though it likes to run on the bit fast side and booting not always fast)
0-100 percent battery mod
G4 sense themed icons for the status bar
Transparency enabled overall (For ones unaware froyo/sense does not have transparency enabled on certain system files. So this was enabled)
Transparent pull down with a little tweaking
Location Icon on taskbar is no longer there for no reason.
Popups themed to match sense overall colors and a few icons.
5 row app drawer with transparent background
Apps that require updates moved to data
All system apps moved to ext partition (This allows of live wallpapers and wallpapers to be kept with out hurting for space)
Some other things were also moved to ext. For a explanation on why this was done. Check the why dalvik was left internal with no data2sd.
Market cache for downloads mounted to ram upon downloading and installing. Once installed is is automatically deleted. Which means the only sense rom with 100% working cmtd.
Cmtd setup and fully working.
Before I forget reboot options (Reboot, Reboot to recovery & a few more)
Probably forgetting some stuff also. Once I remember I will update.
Why the rom was done like it was with no data2sd or dalvik moved:
Ok the rom was done like it was for a few reasons. One was for increased memory. Two was for speed. Three was for no dead sd cards. Followed by 4 was to help battery life. With that said we go to data2sd. Data2sd works by moving the data partition to a a sd-ext partition. There is a few different versions. Real data2sd kills cards quick due to reads and writes. Kali's data2sd is a knock off of darktremors apps2sd+. It moves the data/app and data/app-private to sdext. Same thing as darktremors apps2sd+. Darktremor's apps2sd packs more features from zip align, memory tweaking and other things. This should not cause lag like claimed. What will is enabling dalvik-cache to ext. Kali's doesn't support this. So kali's data2sd or darktremors apps2sd+ with out dalvik moved will not be that hard on a card at all.
Now with dalvik moved in darktremor's it causes lag and major read and writes to the sd card. Due to it moves system dalvik. Anytime you open a app or do something it reads and writes to the sd card. This causes battery drain and bottlenecks also. So what I did was a better alternative, since dalvik moved frees up space but causes lag. I left dalvik internal, moving system apps and a few other things to ext partitions. Then creating blind mounts. This allowed me not to remove anything like before or enable dalvik. Yet give the same free space 240mb to be exact. So you get the speed and space. Best of both worlds right?
The other thing is with anything sd-ext. Sd cards have a number of limited reads and writes. Some fail sooner and later. It just depends on the card. With that said the process done is very easy on the sd card.
Files to download:
SleekSense-1.0 Stable Click Here
Install instructions:
1. You need to have cwm 3 or above to install this. For working recoverys that will work with this rom check here Click Here Once you have that proceed.
2. Follow this step if you don't have a ext partition setup (If previously using apps2sd or data2sd you should have one. So please skip to step 3.)
First you need to back up your card sd card. This means mount your sd card on your computer, creating a folder. Then copying the contents of the sd card to the folder. Once this is done reboot phone into recovery. Once you do that go to advanced>partition sd-card. Pick you sizes for your partitions. I use 1024m/0m. Once that is done reboot your phone.
3. So once booted back into your rom. Copy the files you backup back over. The open the SleekSense-1.0.zip. Extract the contents to the root of the card. This means the sleeksense folder should be in the main directory. Along with the mtdpart text file in the root. If you had one before please replace it. Once done reboot to recovery again.
4. Go to Install zip from sd card>choose zip from sd card>SleekSense>SleekSense-recovery. Once installed go to Advanced>Reboot Recovery. Once recovery reboots it would be a good idea to do wipe data/factory reset. After the wipe is complete proceed below.
5. Go to Install zip from sd card>choose zip from sd card>SleekSense>SleekSense-SleekSense-Rc1. Once it installs and prompts you to reboot. Do reboot system now with in recovery. Now it will take a bit to boot the first time. The htc screen will stay on for about a min to two. Then you will see a android boot animation. It will also stay on this for awhile. Don't worry if it isn't booting right away. Now if 10mins have passed and you still are in the ui. Then redo the above steps for flashing the rom. No need to reformat the card. Just make sure you do a full wipe.
6. If it booted in the ui. Follow the setup wizard and you are good to go.
For any problems you encounter, have a question or anything else. Please post them at the following link: Click Here or post in the thread here. If I don't get to your post in a day you can pm me on here and ask me to check.
Credits:
Darktremor for his apps2sd
dsixda for use of his kitchen
The maker of apktool
Boot animation & some icons pulled from uot kitchen
It doesn't work mate...It doesnt boot
gkaipale said:
It doesn't work mate...It doesnt boot
Click to expand...
Click to collapse
Do you have a cdma desire?
Sent from my HTC Desire using XDA Premium App
You are right...I missed it...No, is there any other than CDMA?
I have visited your site, good work, i rarely see CDMA posts, more of them are GSM and i missed it. Thanks anyway.
Yea this is only for the cdma desire. Was there something you wanted possibly I could help you out with?
No, i just wanted a new rom and this one looked good.
Will this work without ext3? I have my card partitioned already for Dtapps2sd since that's what I know how to use lol. Second question is do we have a custom kernel yet?
Sent from my desire with SWYPE sorry bout the spelling
Hello, I was wondering what the easiest way to put a ext3 partition on my sd card is? Is that all I need to do before installing this ROM and it will auto recognize the ext3 partition or am I thinking wrong here?
Wait till later today as I am doing some changes on my forum so links will probably be down. I also fixed everything but a few of the icons that aren't themed.
I removed the modules as they don't work. The ones in the other rom doesn't either just a heads up on that. I am uploading the rc2 as I type but the links won't be up till later today.
As for the ext partition backup the contents of your card and do it from recovery following the instructions in my guide at the link. I don't recommend installing if you have a ext partition that you don't want to wipe. As if you don't wipe it. It will cause force closes.
You can make a backup of your partition say if you are using data2sd with cm7. Then wipe it as the partition will work with the rom. I plan to upload a non apps2sd and play with the data2sd scripts and upload one of those also. As for the custom kernel htc hasn't released the source though one may be built from mixing the cdma desire eclair with the cdma froyo kernel. Though I don't think it is worth the time to play with it. Not for me any way.
As running two sites doing a cm6,cm7 and froyo rom for the desire. Then roms for the mesmerize I don't honestly have enough free time.
2fast4u88 said:
Wait till later today as I am doing some changes on my forum so links will probably be down. I also fixed everything but a few of the icons that aren't themed.
I removed the modules as they don't work. The ones in the other rom doesn't either just a heads up on that. I am uploading the rc2 as I type but the links won't be up till later today.
As for the ext partition backup the contents of your card and do it from recovery following the instructions in my guide at the link. I don't recommend installing if you have a ext partition that you don't want to wipe. As if you don't wipe it. It will cause force closes.
You can make a backup of your partition say if you are using data2sd with cm7. Then wipe it as the partition will work with the rom. I plan to upload a non apps2sd and play with the data2sd scripts and upload one of those also. As for the custom kernel htc hasn't released the source though one may be built from mixing the cdma desire eclair with the cdma froyo kernel. Though I don't think it is worth the time to play with it. Not for me any way.
As running two sites doing a cm6,cm7 and froyo rom for the desire. Then roms for the mesmerize I don't honestly have enough free time.
Click to expand...
Click to collapse
Well as you know we have very little and your contribution is greatly appreciated. If I can get the mms and provider right (can't remember how on a sence rom) this is gonna be my new rom.but I can do a full wipe and I think I have a ext3 for darktremor already so it should work the same. About to give it a shot lol.
Sent from my desire with SWYPE sorry bout the spelling
Ok I've gotten a few reports on the version of darktremors apps2sd making a partition on the card with out wiping the card if one isn't found. I can't verify this at the moment due to have limited access to the girls desire since I switched to the mesmerize.
Also this will work with the green or orange cwm. Unlike the other sense rom for cdma here that was done in htc kitchen on a older version where it just boot loops on green but works on orange. The ext3 partition is fine in both for myself also.
I also added the new release to the first post if on the first rc-1 you can download the zip I am going to post of just the rom. Do a wipe and flash it. No need to redo the cmtd stuff.
Edit: Added link to just zip in guide and added link in guide for different colored markets.
Why will nothing else boot up after i flashed this rom? not even backups.. The only thing that will get past boot animation is this rom and a backup of this rom.. everything else gets stuck on boot loop.. did a full wipe but nothing works.. gonna try CM7 see if that works.. if not im stumped
Nevermind.. figured it out.. duhhh lol
It was because cmtd wasn't it? Glad you got it.
2fast4u88 said:
It was because cmtd wasn't it? Glad you got it.
Click to expand...
Click to collapse
Yea it was cuz of 1st zip that you flash.. wasnt aware you would have to use the other zip to undo it.. lol I only flashed back to my backup cuz i was having market problems cuz of my connection due to weather cuz alot of other peeps are have problems with theirs too.. only thing i can think of.. wish these roms would come with a file manager like Cyanogen does so you can install apk.s from sdcard incase of market or connection problems
Is there a way to change the battery and data connection icons? Ive tried using UOT Kitchen but it wont get past boot.
freak69ize said:
Is there a way to change the battery and data connection icons? Ive tried using UOT Kitchen but it wont get past boot.
Click to expand...
Click to collapse
If the rom is deodexed you can open the zip look in framework-res and put the icons in you want and also in drawable-mdpi (might be named a different drawable, I can't remember for the desire but when you look threw the folder it still be obvious if it's right or not) then flash it. Our you can make a metamorph file or make your own flashable zip with the files. Whatever is easiest for you. But it must be deodexed and not odex. Not sure what this rom is. Lol.
Btw I seen your question in the last post we spoke in but for some reason it wouldn't let me respond and I just forgot after that lol. Sorry
Sent from my PB99400 using Tapatalk
leadfoot9281 said:
If the rom is deodexed you can open the zip look in framework-res and put the icons in you want and also in drawable-mdpi (might be named a different drawable, I can't remember for the desire but when you look threw the folder it still be obvious if it's right or not) then flash it. Our you can make a metamorph file or make your own flashable zip with the files. Whatever is easiest for you. But it must be deodexed and not odex. Not sure what this rom is. Lol.
Btw I seen your question in the last post we spoke in but for some reason it wouldn't let me respond and I just forgot after that lol. Sorry
Sent from my PB99400 using Tapatalk
Click to expand...
Click to collapse
It must be deodexed cuz its already themed.. I jus wanna change the battery and a few other things.. heres a pic
freak69ize said:
It must be deodexed cuz its already themed.. I jus wanna change the battery and a few other things.. heres a pic
Click to expand...
Click to collapse
I sent you a pm, I'm out for the night but if work permits I can try and do that tomorrow night but at the latest can work on it this weekend.
Just remind me cuz I will forget lol
Sent from my PB99400 using Tapatalk
Heres the zip i made in kitchen.. and thanks again
View attachment UOT-04-26-06-30-1.zip
Data connection icons ( i didnt make these.. credit to the owner )
View attachment solidarrows.zip
{
"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"
}
After I have tried a lot of ROMs for the HTC Desire, and each one of them was perfect in another way, there was one kind of ROM I couldn't find: a ROM which is as small as possible, with Sense, and Gingerbread, and as clean as possible.
First of all: I am not an experienced developer, such as LeeDroid, or Coolexe (by the way, thanks a lot guys, loved your ROMs, and used each one of them without any issues, so kudos for your hard work!).
I'm just a 15-year old boy, who wanted to create a ROM which is as small as possible, but keeping Sense. If you have things to say like 'Loser, why would I flash this ROM, there are dozens of other ROMs', don't say anything at all.
However, if you have tips, questions, or think you can help me with this ROM, don't hesitate, and feel free to post!
About this ROM:
-Based on Gingerbread RUU from HTC for HTC Desire (Bravo)
-Bananacakes awesome new kernel (0.4), build by Sibere (0.4a), running on 1GHz, OC'able to 1.2.
-Su + Superuser + Busybox included
-Optional A2SD
-Removed a lot of stuff, resulting this ROM to be less than 120MB in size!
-Kept Sense, but some apps are removed (such as Stocks, Footprints, and Facebook, which you can download from the market anyway)
-Works on Stock HBOOT, and it should also work on Data++ or Bravo Sense (please post your experience with these 2 HBOOTs)
So, if you are looking for a lightweight version of Sense and Gingerbread, this is the ROM you're looking for. It may contain bugs, and I can not be held responsible for any damage. If you tell me about the bugs, I could try to fix them, but don't think I'm an expert with Android development, but I'll see what I can do.
To do:
-TrackballWake
-Perhaps create a special update.zip for some popular apps (filemanager, terminal, DSPManager)
-Fix the bootanimation (just a black screen at the moment, trying to find out how to fix it), the ROM boots just fine though
Removed:
-Apps you can install from the market (Facebook, Gmail, Flash, Flickr)
-Apps which have better alternatives (HTC Twitter)
-Apps which bugs a lot of users, even when they're not being used (HTC Stocks)
-Apps I simply don't like or use (Friendstream, Footprints)
-Apps of which I can't even come up with a reason why they would be installed by default (Polaris Office, if I'm right about the name)
-Live wallpapers which are pretty useless in my opinion (Smoke Wallpaper, Music Visualizations)
-HTC Sense Live Wallpaper, and the normal wallpaper is replaced
-Almost all ringtone/notification sounds, except for one in each category (the default ones)
Without further ado, here are the downloads:
Click here for the Non-A2SD build (version 1.5)
HBOOTs with 5MB cache won't work! Stock HBOOT or Bravo Sense HBOOTs will work fine, since they have a bigger cache (thanks Ronijs19!) For cMTD users: /system is 163MB in this build.
Click here for the A2SD build (version 1.5)
After you have installed the A2SD build, download a terminal emulator from the market and execute the following commands:
su
a2sd cachesd
Click to expand...
Click to collapse
Your apps and the Dalvik Cache will be stored on EXT from now on.
Changelog:
1.5
-Updated kernel to 0.5 by Bananacakes
-Restored original framework (= original skin)
-Restored fonts (Ubuntu fonts took more space...)
1.4
New build of Bananacakes kernel, by Sibere, running on 1GHz, OC'able to 1,2.
Bootanimation is either ANDROID now, or still a black screen, bit confused about that due to a lot of builds..
New font, Ubuntu.
Also removed alarm and notifications tones except the default ones.
1.3
-Removed LiveWallpapers (every LWP except HTC Sense)
-Removed Mode10Wallpapers (the HTC Sense LWP)
-Replaced dock (used the one from the Slate theme for Sense 2.1)
-Replaced the default Sense wallpaper for a custom one
-ROMs will be uploaded onto our own server from now on, which means: no waiting, and direct links (thanks DonUber!)
1.2
-Removed FriendStream (Twitter and Facebook were removed anyway, so Friendstream was unusable)
-Removed all ringtones except for 1 (saved about 2MB)
-Swapped the ucsh00d_c.ttf font for DroidSans.ttf, saving about 3.5MB
-Swapped the gcsh00d-hkscs.ttf font for DroidSans.ttf, saving about 1MB
-Removed some images in /media/resources, saved about 500KB, since the images are never used in Android anyway, AFAIK
-Modified updater-script with some ui_prints to inform about the progress
-Bananacakes new kernel (0.4) implemented
-Two versions from now on: with A2SD, and without A2SD. In the version without A2SD, you can insert any A2SD script you would like (both versions have init.d support). Recommended HBOOTs are Stock or Data++ or Bravo Sense. I have only tested Stock though, so if you use another HBOOT, please post your results.
1.1
-Init.d Script Support
-A2SD (Darktremor Script) installed by default, should be working
Click to expand...
Click to collapse
Thanks to:
-DonUber, a good friend IRL, who always gives me tips and ideas for improving the ROM, thanks a lot mate!
-Koush, for his Anykernel Updater!
-Bananacakes, for his awesome kernel!
-Ronijs19, for tips and testing different HBOOTs.
-You, and every other user who uses this ROM!
Enjoy, and don't hesitate to ask questions or report bugs!
If you like my ROM, and you don't have a DropBox account yet, consider creating one by using my referral link, giving both of us an additional 250MB: Click here!
This is the theme that is being used in Flux 1.3 and higher. If you download Flux 1.2, you won't have this skin!
Thx dude, gonna try it.
Which base did you use? Stock Sense GB Rom?
(what? I'm the first one? Yupiiiii)
Yes, this ROM is based on the RUU, released by HTC on HTCdev.com. It is an official Gingerbread, which was a bit slimmed down by HTC, and I removed even more bloatware.
EDIT: I'm trying another way to get A2SD working, give me half an hour
EDIT2: A2SD working, get 1.1 now from the first post! Wipe recommended.
Chaosz-X said:
Yes, this ROM is based on the RUU, released by HTC on HTCdev.com. It is an official Gingerbread, which was a bit slimmed down by HTC, and I removed even more bloatware.
EDIT: I'm trying another way to get A2SD working, give me half an hour
EDIT2: A2SD working, get 1.1 now from the first post! Wipe recommended.
Click to expand...
Click to collapse
Nice, i have removed friend stream widget (hate it).
If more people want to see other widgets/apps removed, I could make a list, and also remove that apps if there are enough people who would like to remove it. Aside from that, I'll also make a script soon which allows you to remove even more apps.
Thanks for your response!
Hello.
Always nice to see both new developers in here, and continued ROM development for the Desire.
May I ask, are there any benefits to this ROM for someone like me who hasn't S-Off'd and just has the stock partition?
Chaosz-X said:
If more people want to see other widgets/apps removed, I could make a list, and also remove that apps if there are enough people who would like to remove it. Aside from that, I'll also make a script soon which allows you to remove even more apps.
Thanks for your response!
Click to expand...
Click to collapse
Dude, can you upload some screen-shots of this ROM? how about performance and battery consumption?
williamj1 said:
Hello.
Always nice to see both new developers in here, and continued ROM development for the Desire.
May I ask, are there any benefits to this ROM for someone like me who hasn't S-Off'd and just has the stock partition?
Click to expand...
Click to collapse
If you don't have S-OFF, this ROM is perfect for you, if you want your phone to be as clean as possible, and need space for apps. This ROM uses A2SD by default, and in combination with a 512MB/1024MB EXT-partition, you don't have to worry anymore about the space for apps (a Desire without A2SD has only 137MB on NAND for apps).
Aside from that, this ROM is smaller than an original one. The GingerBread RUU by HTC was already slimmed down, and was 150MB. I removed even more bloatware, or unnecessary apps (such as HTC Stocks, which keeps running and bugs a lot of users), resulting in a ROM which is only 120MB. Even CyanogenMod is 90MB, so this ROM is really lightweight, since it has only approx. 30MB difference with an AOSP ROM.
In other words: no tweaks and modifications, just a ROM meant to be as stable and fast as possible, and without the bunch of apps most of the users won't use anyway, or they have alternative apps.
kmaq said:
Dude, can you upload some screen-shots of this ROM? how about performance and battery consumption?
Click to expand...
Click to collapse
The skin is the same as a normal Sense ROM for the Desire (so it's just as the stock ROM). The performance is really good, I haven't noticed any lag or anything like that yet, and it is running pretty stable until now.
I'll post tomorrow evening about the battery consumption, as the most recent build I made was about 2 hours ago, so I couldn't really test it yet.
I will make a skin though, and I hope to finish it in about a week.
Ok thanks....
So after boot and A2SD+ initiates, how much memory would I have free?
After you have installed the ROM, and have an EXT-partition, all your apps which you install will be placed on the EXT-partition. This means the available space is the same as the size of the EXT-partition.
My Desire said I had 80MB free after a flash, because the Dalvik Cache is still on the NAND of the phone. I also moved that to the EXT by installing a Terminal Emulator, and executing the commands:
su
a2sd cachesd
Click to expand...
Click to collapse
After which your phone will reboot. No matter how much apps you install now, your phone will always say you have 137MB available, because everything is being stored on the EXT-partition on your SD-card.
To use A2SD:
Boot in recovery, and partition your SD-card with an EXT-partition (512MB or 1024MB should be enough). Keep in mind partitioning removes all your data and formats your SD-card. Then copy the ROM ZIP to the root of the SD by using the USB Storage Function in recovery, and install it by using recovery. Then reboot, and A2SD will be enabled and your phone will boot in less than 5 minutes (only the first time, after the first boot it will startup much faster). During boot you'll get a black screen, it is completely normal. To use the EXT-partition for Dalvik Cache also, use the 2 commands I mentioned earlier in this post, and you should be ready
Chaosz-X said:
After you have installed the ROM, and have an EXT-partition, all your apps which you install will be placed on the EXT-partition. This means the available space is the same as the size of the EXT-partition.
My Desire said I had 80MB free after a flash, because the Dalvik Cache is still on the NAND of the phone. I also moved that to the EXT by installing a Terminal Emulator, and executing the commands:
After which your phone will reboot. No matter how much apps you install now, your phone will always say you have 137MB available, because everything is being stored on the EXT-partition on your SD-card.
To use A2SD:
Boot in recovery, and partition your SD-card with an EXT-partition (512MB or 1024MB should be enough). Keep in mind partitioning removes all your data and formats your SD-card. Then copy the ROM ZIP to the root of the SD by using the USB Storage Function in recovery, and install it by using recovery. Then reboot, and A2SD will be enabled and your phone will boot in less than 5 minutes (only the first time, after the first boot it will startup much faster). During boot you'll get a black screen, it is completely normal. To use the EXT-partition for Dalvik Cache also, use the 2 commands I mentioned earlier in this post, and you should be ready
Click to expand...
Click to collapse
I appreciate the efforts, but I am actually very experienced in that sense. I know perfectly well the A2SD commands and how it works All I wanted to know was the 137mb figure
PS: It isn't correct to say "No matter how much apps you install now, your phone will always say you have 137MB available". The memory will still go down even with A2SD+ installed and davlik cache to sd. It just doesn't go down as much.
Hi Chaos,
Why not just use a2sd script from Oxygen rom? I'm using it on all roms including CM7, MIUI. Leaving dalvik cache on nand with cm7r2 hboot. Much smaller then dt version.
Is your rom deodexed or odexed?
Some proposals:
-add new kernel from bananacakes (modified original GB Sense kernel, sources also available in post).
-Please add trackpad2wake also.
And kind request, what is removed or what is left inside?
Thanks!
Sent from my HTC Desire
williamj1 said:
I appreciate the efforts, but I am actually very experienced in that sense. I know perfectly well the A2SD commands and how it works All I wanted to know was the 137mb figure
PS: It isn't correct to say "No matter how much apps you install now, your phone will always say you have 137MB available". The memory will still go down even with A2SD+ installed and davlik cache to sd. It just doesn't go down as much.
Click to expand...
Click to collapse
You're right, it does go down, but since your apps, the dalvik cache and the cache are being stored on the EXT-partition, the NAND is almost untouched by apps I think. Not sure though, I don't know a lot about the A2SD scripts.
vr5411 said:
Hi Chaos,
Why not just use a2sd script from Oxygen rom? I'm using it on all roms including CM7, MIUI. Leaving dalvik cache on nand with cm7r2 hboot. Much smaller then dt version.
Is your rom deodexed or odexed?
Some proposals:
-add new kernel from bananacakes (modified original GB Sense kernel, sources also available in post).
-Please add trackpad2wake also.
And kind request, what is removed or what is left inside?
Thanks!
Sent from my HTC Desire
Click to expand...
Click to collapse
Removed:
-Apps you can install from the market (Facebook, Gmail, Flash)
-Apps which have better alternatives (HTC Twitter)
-Apps which bugs a lot of users, even when they're not being used (HTC Stocks)
-Apps of which I can't even come up with a reason why they would be installed by default (Polaris Office, if I'm right about the name)
-Live wallpapers which are pretty useless in my opinion (Smoke Wallpaper, Music Visualizations)
Trackpad2Wake is a function I also used a lot myself, so I will implement it soon
The new kernel by Bananacakes: if I see positive results by other users, and people like it, I will build it in.
And the ROM is deodexed
About the Oxygen A2SD script: I'll see what I can do, and maybe implement a feature to choose the desired script for A2SD.
Thanks a lot for your interest guys, I really appreciate it!
your rom is a perfect! dsp manger?
I'll see how much space it takes, and I'll either make a flashable ZIP to install it automatically, or if there are lots of people interested in it, I'll implement it in the ROM itself
Chaosz-X said:
You're right, it does go down, but since your apps, the dalvik cache and the cache are being stored on the EXT-partition, the NAND is almost untouched by apps I think. Not sure though, I don't know a lot about the A2SD scripts.
Thanks a lot for your interest guys, I really appreciate it!
Click to expand...
Click to collapse
You are very welcome. I will be sure to try this at some point in the next few days, thanks
Just one thing.... if you are really wanting to attract people in and get them downloading, I'm certain having a screenshot would help with that. And maybe update the OP with some of the information like the above ^, about what is removed etc etc.
Good luck Thanks
iltore said:
your rom is a perfect! dsp manger?
Click to expand...
Click to collapse
I don't think its implemented in the ROM itself, but now its possible just to install the CM7 mod as an apk file.....
(attached)
I have some work to do for school, which should be finished in about 15 minutes, and then I'll update the OP and add screenshots of the current interface.
In about 1 week I'll release an update with a really nice skin (in my opinion), and I think that will make the ROM a bit more unique
williamj1 said:
you are very welcome. I will be sure to try this at some point in the next few days, thanks
just one thing.... If you are really wanting to attract people in and get them downloading, i'm certain having a screenshot would help with that. And maybe update the op with some of the information like the above ^, about what is removed etc etc.
Good luck thanks
i don't think its implemented in the rom itself, but now its possible just to install the cm7 mod as an apk file.....
(attached)
Click to expand...
Click to collapse
everything works thanks thanks thanks to both!
Chaosz-X said:
N/A
Click to expand...
Click to collapse
Feel free to stick the APK of the DSP manager I attached in the OP if you wish ?
Progress update and INT2SD implementation request form!
With holidays starting, and more free time on my hands, I've decided to revive this project. Having my hard drive fail on me recently, and losing the request log, it has become obvious that I need a new system of handling requests, and it is here. If you have requested a ROM before, please send a request again, via this form.
Please submit all further requests via this form!
---
This is the INT2SD thread for Sense ROMs and their developers and users.
INT2SD thread for AOSP ROMs
What is INT2SD?
INT2SD doesn't use symlinks. It mounts ext partition on your SD to /data, thus eliminating the need for the mtd5 userdata partition. This makes the mtd5 userdata partition unneeded. It is used in conjunction with the fatsys HBOOT (more info later on), allowing most of the vital parts of a ROM to stay on the system partition without the need to symlink half of it to the SD due to memory shortage.
For now, there is only one ROM here, but more will come! If you wish to see INT2SD in your favorite ROM or in your own ROM, please post here!
INT2SD-S - "Speed" (default as of 29th Jun)
Main characteristics:
/data on SD ext, /data/data on internal
/data/data limited to 280 MB (probably enough for more than 100 user apps)
noticeably faster on slower cards
for use with CM7r2 HBOOT
Description:
The new "speed" flavour mounts ext to /data and userdata to /data/data, achieving great speed while still retaining excellent storage capabilities. It's used with the CM7r2 HBOOT. This is now the default flavour, offering great speed while still being able to hold a hefty amount of apps.
INT2SD-M - "Mass" (discontinued)
Main characteristics:
/data on SD ext
number of apps is only limited by ext size
requires a faster card
for use with fatsys HBOOT
Description:
The classic "mass" flavour mounts ext to /data, thus eliminating the need for the mtd5 userdata partition. It has proven to be slow even on some of the faster cards. Due to INT2SD-S being able to hold a very high number of applications, and still being much faster, this flavour is discontinued.
FAQ
For users: How to get this in your favorite ROM
For ROM developers: How to get this implemented in your ROM
Please fill out this form.
Cross-device implementations
For now, no. You may submit requests, but I won't be able to fulfill them for a while. I have quite a lot of real life work on my plate, not to mention a list of Desire ROMs I have to tend to. After that's done, I'll be happy to try blind-porting it to whichever device you wish, but my priority are Desire ROMs, primarily because it's a lot easier to implement INT2SD into ROMs for a phone I already have.
Universal update zips
Also, no. Each ROM is different, and due to the nature of INT2SD, it is simply not possible to make a one-for-all universal update zip. Every ROM requires tending to its peculiarities, especially Sense ROMs, and I would rather not take the change of trying to make one and end up with a flashable bootloop zip.
Why don't you just publish instructions on how to implement INT2SD for devs to use?
Proz0r said:
You can take a look at the modified ROM and you will find 3 new files in /system/etc, dalchk, fsck and sleep. These files are executed by init.rc because of my modifications to it. You can also decompile the boot.img and use a tool such as diff or diffuse (a GUI for diff) and check the differences between it and the unmodified init.rc from Alex's standard, D2EXT ROM. However, his ROM required another init.d script to move weather animations to /data, and modifications to the updater-script to flash everything that would normally be flashed to /data, to be flashed to /sd-ext. Sounds simple enough, right? Well, it's actually not quite as simple. When I have first implemented INT2SD to CyanogenMod 7, all I had to do was edit a few lines and add those three scripts. There was not a single ROM (and there are a few unreleased ones which I've worked on) to which I could apply a "standard" procedure. Each ROM required further modifications on its own and being the one who devised INT2SD, I know what I should look out for in order to avoid catastrophical bugs. ROM developers do not. This is why I do NOT offer support for "homemade" INT2SD implementations. Every ROM has its own peculiarities that need tending to and INT2SD implementations need to be very flexible to allow the ROM to work in conjunction with it. Sure, everything could go great, but INT2SD is extremely easy to implement horribly wrong and have huge bugs and even unbootable systems, and without knowing what the dev did to put it in their ROM, it is next to impossible for me to troubleshoot and fix. It would probably end up with me having to implement it myself either way in most cases and having angry developers and possibly users on my hands being pissed at me for doing a bad job and releasing a ****ty product, when the problem was just a typo in init.rc. That's why I have not nor will I release instructions for devs on how to implement it themselves.
Click to expand...
Click to collapse
Before you download!
Although it is for the best part bug free, INT2SD is still a fairly fresh project so I'm looking for as much input as I can get to fix possible bugs I haven't yet uncovered. If you try a ROM featuring INT2SD, please be sure to comment in this thread on your experience, even if it works great or doesn't work at all. If you wish to further support the project, there is a donate button in my signature. Although a nice sign of support and appreciation, donations are not obligatory!
Due to /data/data being on the SD, a high-class card is recommended.
Another thing is the HBOOT, fatsys. You must flash it before flashing any of the INT2SD Sense ROMs.
fatsys HBOOT
bravo_alphaspl-fatsys.img
MD5: 2272c1cb06f8eb743aa1c0ad4c3fa36b
PB99IMG-fatsys.zip
MD5: 4d6b2e74c241361237df047bfed5ff08
INT2SD Sense ROMs require a special HBOOT, fatsys. This special HBOOT has 427 MB dedicated for /system, 5 MB for /cache and 5 MB for /data and there is probably no ROM without INT2SD that would work on it properly. It was made so that the largest part of Desire's internal memory can be used for quick access to vital system files by storing them in /system instead of symlinking them to /sd-ext, therefore slowing the entire system down. There is still plenty of space for your apps if you make a large enough SD ext partition, since SD ext gets mounted to /data and the real, 5 MB mtd5 userdata partition goes unused. So, /data on SD ext, huge /system and no symlinks! Before flashing a Sense INT2SD ROM, make sure you have flashed the fatsys HBOOT!
Download
Thanks to Ante0 for hosting the files!
INT2SD implemented in:
Alex-V1.8 GB Sense HD INT2SD-M fatsys (Thread | Download)
Alex-V1.8 GB Sense HD INT2SD-S CM7r2 (Thread | Download in a minute)
Runnymede AIO 6.1.1 Beta (Thread)
Current bugs:
-
To do list for the next version:
-
Credits (alphabetically):
Alex-V - providing me with the first Sense ROM to implement INT2SD in
Ante0 - providing proper hosting for the zips
brabo, GShellz admin - huge help with bash scripts implemented in the ROMs
CM - a base ROM for implementing the method in
Droidzone - suggestions, help with HBOOTs
Hacre - massive assistance as well, kicking me to try and realise the main idea and for coming up with names "INT2SD" and "fatsys"
JieeHD - help with compiling/decompiling the boot.img files and his excellent guides on FYA
Pulser_g2 - massive assistance, ideas on the reboot bug and hosting
Richard Trip - making GingerVillain which now has a version featuring INT2SD
snq- - pointing out a huge typo and saving me multiple hours of pointless work
ubuntubhoy - a kick in the arse I needed
... and everyone else in the #villainrom IRC channel for help and mental support! Thank you all, and everyone I forgot to mention (PM!).
Disclamer: I'm not responsible if something goes wrong and wreaks havoc upon you, your phone, your card, any part of your phone, your friends, your family, your close or distant relatives and/or your pet, but I will gladly provide assistance if it does.
I'm not a dev at all, but I think this tool can help you: a too for making coustoms hboot by _thalamus
http://thalamus-hacking.blogspot.com/2011/07/custom-hbootsupdate.html
I have been using for months without any problem
Well, if you manage to learn how to reverse engineer and manipulate hboot, do share.. You might want to ask thalamus. I read that he'd done it.
Edit: Ah blackhawk_LA has already posted that.
@blackhawk_LA, is there an open source version of this tool?
blackhawk_LA said:
I'm not a dev at all, but I think this tool can help you: a too for making coustoms hboot by _thalamus
http://thalamus-hacking.blogspot.com/2011/07/custom-hbootsupdate.html
I have been using for months without any problem
Click to expand...
Click to collapse
Awesome, thanks! Wish there was a Linux version of it, luckily, I have Windows in dual-boot so I'll whip something up in a minute!
Droidzone said:
Well, if you manage to learn how to reverse engineer and manipulate hboot, do share.. You might want to ask thalamus. I read that he'd done it.
Edit: Ah blackhawk_LA has already posted that.
@blackhawk_LA, is there an open source version of this tool?
Click to expand...
Click to collapse
Yeah, I'm interested in how this works too.
Droidzone said:
@blackhawk_LA, is there an open source version of this tool?
Click to expand...
Click to collapse
I don't know, I just found that tool and start using it, I can't do anything more
@blackhawk_LA
Have you ever had any issues with the application? It's making a very important part of the system and if any errors would occur, it would be a catastrophe, which is why I am a bit apprehensive towards this program.
Make HBOOTS with it which have the same sizes as the HBOOTs from Alpharev, compare MD5, if they match, it's probably safe. Then you should be good to go to make a custom HBOOT with it
Never had any issue, I have used it very carefully to make at least 10 different custom hboots, and my phone is still alive
More statistics are needed to say it's completely safe but I think thalamus did a perfect job
I can say the program is very safe... have a dozen of custom hboots with it... no problem at all.
And looking forward to your INT2SD for sense..
here you go..
http://www.multiupload.com/N0B1RHYFPW
I'm very interested too!!! Thanks and keep up the awesome work!
When it'll be available I'll try it into my rom.
msandeep said:
here you go..
http://www.multiupload.com/N0B1RHYFPW
Click to expand...
Click to collapse
Thanks man, have you tested it?
You're not telling me everyone is too afraid to flash it, so everyone hopes someone else tries it to take the risk... -.-
Proz0r said:
Thanks man, have you tested it?
Click to expand...
Click to collapse
yes...its the one i use in my roms...and 40mb real data is really good to add apps like maps (that can updated) to the rom
with kind regards
Chaosz-X said:
You're not telling me everyone is too afraid to flash it, so everyone hopes someone else tries it to take the risk... -.-
Click to expand...
Click to collapse
I need my phone for the next couple of days and therefore cannot try it myself.
Alex-V said:
yes...its the one i use in my roms...and 40mb real data is really good to add apps like maps (that can updated) to the rom
with kind regards
Click to expand...
Click to collapse
Nice. Should real data be reduced to 5 MB or be left at 40 MB then, in INT2SD? Since it won't be needed for symlinks with it, I only see the point in having the 5 MB for the fsck log.
Word of advice.. Before flashing new hboot, use the alpharev downgrader. Otherwise you're screwed if the hboot turns out to be a corrupt file
Sent from my HTC Desire using Tapatalk
Thanks man, could you briefly describe what would happen if I would flash a corrupted HBOOT with and without flashing the downgrader prior?
Proz0r said:
Thanks man, could you briefly describe what would happen if I would flash a corrupted HBOOT with and without flashing the downgrader prior?
Click to expand...
Click to collapse
Well, AFAIK the HBOOT is also the white screen you get when you press Vol Down+Power, and it probably also involves the bootprocess normally, so I would say: broken HBOOT = a very nice brick.
Though I don't know what the downgrader is..
Yup, I know about that, I'm wondering about the downgrader too.
Proz0r said:
Yup, I know about that, I'm wondering about the downgrader too.
Click to expand...
Click to collapse
I'm always use the hboot-downgrade whenever I change hboot no matter whether the previous hboot is a lock hboot or an unlock hboot. It is always best to unlock the hboot before flashing a new one to be on a safe side.
Here is hboot with 427mb/system, 5mb/cache & 5mb/data as you mentioned here
Proz0r said:
Now, we need a volunteer to make the said zero-data HBOOT for 5 MB for /cache, 5 MB for /data and the rest for /system.
Click to expand...
Click to collapse
I tested the hboot by flashing it to my phone.. no problem to go to recovery, no problem to boot to bootloader. but I don't have any ROM which can fit a 5mb data partition to test. The lowest I ever go is 30mb/data.
Note: to change to another hboot.. use the hboot_downgrade first as this is a lock hboot.
Edit : Manage to squeeze the ROM to fit a 5mb/data ... so confirm the hboot works.
conclusion first: it was possible.
i searched for custom mtd info for chacha on google, and i found some info in chinese suggested it was possible to apply custom mtd on chacha.
http://wenku.baidu.com/view/b029ab6027d3240c8447ef67.html
i don't speak chinese, but google translation helped. i used Mikevhl's recovery (http://forum.xda-developers.com/attachment.php?attachmentid=749943&d=1318622558), and also FR-Custom-MTD-v1.5.6-boot.zip (http://115.com/file/aqvgn30z#) and FR-Custom-MTD-v1.5.6-recovery.zip (http://115.com/file/aqvgnzmc#) as the chinese instruction said although i don't know where these files came from (maybe somewhere here?)
the procedure itself was the same as desire (bravo) or any other devices, and after the process, i got;
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 214004 32 213972 0% /dev
/dev/block/mtdblock4 5120 1624 3496 32% /cache
/dev/block/mtdblock3 153600 150292 3308 98% /system
/dev/block/mtdblock5 307200 2560 304640 1% /data
yay!!
unfortunately, adlx.xda's v5.0.2.8 didn't work with these patches... sorry, if this info is already around here.
p.s. as usual, this patch automatically mounts /cache to /sd-ext when /cache partition is smaller than 20mb. however, /cache/download won't be created automatically which means vending.apk (market) fails to start. when you set /cache less than 20mb, you'd need create sd-ext partition on your sd card and either add init.d script to create /cache/download ot do it manually.
Interesting, but sorry I don't read chinese :-(. I understand it's for changing the default partition layout on the Chacha.
Isn't it easier to use App2SD?
What are the patches? Do you why it doesn't work with my CWM build (maybe we can improve it so it work).
adlx.xda said:
Interesting, but sorry I don't read chinese :-(. I understand it's for changing the default partition layout on the Chacha.
Isn't it easier to use App2SD?
What are the patches? Do you why it doesn't work with my CWM build (maybe we can improve it so it work).
Click to expand...
Click to collapse
hi adlx.xda,
i don't read chinese, either;-)
it is sure easier for most people to use app2sd or data2sd, but i prefer to keep everything in the internal memory because it is possible if you change the partitions and don't install millions of apps. it is kinda a surprise to me that you didn't know about custom mtd...
anyway, the patches were originally created for htc desire, and adopted to other htc devices with low internal memory capacity like chacha/wildfire/etc.
http://forum.xda-developers.com/showthread.php?t=806321
there were two patches in the package; one for recovery partition and the other for boot partition. the recovery patch allows you to burn a custom rom according to the designated partition info. the boot patch allows you to change the boot image so that the device recognize the new partition info on boot.
when i use your recovery and the recovery patch together to burn a custom rom, chacha does not boot. i guess the patch does not modify something in your recovery correctly. on the other hand, this patch correctly modifies Mikevhl's old recovery. it is strange the patch can be used for the latest recovery for htc desire...
thx for your attention.
qt
could also be the repackaging of the kernel if it's patched. I tried for weeks unsuccessfully to unpackage and repackage a kernel for the status/chacha and had no luck. I was wanting to do some clocking tweaks.
bedwa said:
could also be the repackaging of the kernel if it's patched. I tried for weeks unsuccessfully to unpackage and repackage a kernel for the status/chacha and had no luck. I was wanting to do some clocking tweaks.
Click to expand...
Click to collapse
How do you try to unpack/repack? I wonder why it would fail.
I'll have to look at my setup on my netbook and get back to you. May be a few days. :-\ Kinda swamped ATM.
My Tab makes calls Yo! GT-P6800
i do read chinese, i saw this fews mths back but i dont have time for it... you will left with 24x~26xmb of free space.
I just wanted to update and say that I replied to this thread:
http://forum.xda-developers.com/showthread.php?p=35367602#post35367602
Basically, I'm wondering if the CustomMTD patches might be more compatible with a newer version of CWM compiled for our phone. I built a copy of 6.0.1.5, which mostly works, so if someone wants to give it a try, please do.
I managed to see custom partitions from CWM (not with the patches, but manually altering the recovery). 312MB /system and ~120MB /data (as an example just to try)
Apparently no problem with /system, but /data is not "working":
It appears as Read Only (it shouldn't actually event mount after moving/resizing it). Also not only it mounts, but it appears as 100%full, and won't allow me to do anything. I can't reformat it, remount rw,... I don't know why to be honest.
Now that I think about it, I should check dmesg.
dead links
it looks like all the links are dead.
here are the files you need.
qtotter said:
it looks like all the links are dead.
here are the files you need.
Click to expand...
Click to collapse
I managed to have it working, but I posted on another thread: http://forum.xda-developers.com/showpost.php?p=38029256&postcount=9
adlx.xda said:
I managed to have it working, but I posted on another thread: http://forum.xda-developers.com/showpost.php?p=38029256&postcount=9
Click to expand...
Click to collapse
so what files do we need, and what exactly do we do with them? I'd love to do the same as what you got working.
kronflux said:
so what files do we need, and what exactly do we do with them? I'd love to do the same as what you got working.
Click to expand...
Click to collapse
IIRC I used no files/patch,... It was more a matter of doing the partition table right. I took some notes and made an excel spreadsheet to help me with the conversions.
I'm on holiday starting today, I probably won't be able to review my notes and write anything related to this this month. Ping me again in Septembre so I review my notes and write a post about it .
kronflux said:
so what files do we need, and what exactly do we do with them? I'd love to do the same as what you got working.
Click to expand...
Click to collapse
it came from this thread originally http://forum.xda-developers.com/showpost.php?p=8578368&postcount=1, and it is very common among HTC Desire users.
it is quite easy to change partition sizes, and all the files you need are the three files that i uploaded.
recovery_chacha.img: Mike's old recovery that is compatible with this method. Don't use other recoveries!!
FR-Custom-MTD-v1.5.6-recovery.zip: This will patch recovery so that it can handle new partition sizes.
FR-Custom-MTD-v1.5.6-boot.zip: This will patch boot (kernel) in NAND so that the system can handle new partition sizes.
Procedure for ChaCha:
Make sure your phone is S-OFFed
**Make a backup in recovery first**
Place FR-Custom-MTD-v1.5.6-recovery.zip & FR-Custom-MTD-v1.5.6-boot.zip on SD card
Create mtdpartmap.txt on SD card with size of system & cache like "mtd 125 5". For example, I wanted to use ajeevlal's cm10.1 with Japanese IME and other system apps built in /system, I needed 330MB on /system and only 5MB on /cache (because I didn't need large /cache to use int2ext+.) So, my mtdpartmap.txt was "mtd 330 5". if you want to do this by shell command, it's gonna be like: echo "mtd 330 5" > /sdcard/mtdpartmap.txt
Flash Mike's old recovery above in fastboot like "fastboot flash recovery recovery_chacha.img"
Reboot into recovery
Wipe system, data, and cache
Flash FR-Custom-MTD-v1.5.6-recovery.zip, this patches recovery to use the new partition sizes
Reboot into recovery
Wipe system, data, and cache again just in case
Flash ROM, or restore from backup, and it will be flashed to NAND based on new partition sizes
Prior to rebooting, flash FR-Custom-MTD-v1.5.6-boot.zip, this patches boot (kernel) in NAND to load with the new partition sizes.
Reboot
unless you change mtdpartmap.txt on SD card, you don't need to repeat 1 - 8 every time. once you have decided your favorite partition sizes, you can start from 9. also, if your backup includes a patched boot image already, you can even skip 12 as well.
if you do this with any other newer recoveries, your phone simply does NOT boot. Mike's old recovery cannot backup sd-ext partition, but you can always do it manually like "dd if=/dev/block/mmcblk0p2 of=/sdcard/ext-bkup.img bs=4096" or something anyway.
kronflux's recovery
by the way, i tried your CWM 6.0.1.5 Built From Adlx http://forum.xda-developers.com/showthread.php?t=1989839, but it does not patch boot correctly. so the phone won't boot.
as i repeatedly keep saying, you need mike's old recovery to do this. i have tried so many recoveries, and this old one is the ONLY that is compatible with these patches.
qtotter said:
by the way, i tried your CWM 6.0.1.5 Built From Adlx http://forum.xda-developers.com/showthread.php?t=1989839, but it does not patch boot correctly. so the phone won't boot.
as i repeatedly keep saying, you need mike's old recovery to do this. i have tried so many recoveries, and this old one is the ONLY that is compatible with these patches.
Click to expand...
Click to collapse
it's also too large to fit in the recovery partition properly I believe. would be great if we could come up with a partitioning table that has enough space for it, as well as a little more space for app/rom storage.
so what are you saying, that we need this other recovery to actually do the partitioning? or that only that recovery will work on a custom partition table?
Adlx was just saying above, he doesn't think he used any custom files or patches. naturally we'll see in september what he has to say about it.
I did it with my recovery, not Mike's, and it worked, but again, I did it manually.
Sent from my Galaxy S4 running CarbonRom "Adlx Edition"
kronflux said:
so what are you saying, that we need this other recovery to actually do the partitioning? or that only that recovery will work on a custom partition table?
Click to expand...
Click to collapse
basically, this process patches recovery and boot to rewrite the partition table. Only Mike's old recovery can do both correctly.
talking about other recoveries, the reason why the phone doesn't boot is either recovery patch failure or boot patch failure. because i know Mike's one works and am not a recovery dev, i didn't even try to find which part is not working.
however, you can easily check it by switching the recovery between patching recovery and patching boot. i guess the former part is not working correctly because the latter part is rather straight forward and simple.
i just don't understand what you want, actually. changing the partition sizes or learning the mechanism of changing partition table??
qtotter said:
i just don't understand what you want, actually. changing the partition sizes or learning the mechanism of changing partition table??
Click to expand...
Click to collapse
Essentially, changing the sizes of partitions to accommodate a larger recovery image(so that my CWM6 could be flashed and work properly), as well as add more space to the system partition so that we don't have to worry about flashing lite versions of Gapps, or slimming down roms so that they fit.
kronflux said:
Essentially, changing the sizes of partitions to accommodate a larger recovery image(so that my CWM6 could be flashed and work properly), as well as add more space to the system partition so that we don't have to worry about flashing lite versions of Gapps, or slimming down roms so that they fit.
Click to expand...
Click to collapse
i have already explained how to do it above... now, my /system is 330 MB, and /cache is 5MB to cooperate with ajeevlal's cm10.1, full gapps, additional system apps and int2ext+. i am quite happy with my chacha setting not worrying about free space of /data, and battery lasts almost forever during sleep.
well, it is such a simple procedure, but i don't need to promote it to other people myself. i simply wanted to share the info that i learned over one year ago with people who want to make /system smaller for stock rom or make /system larger for cm10 and above.