Database Info

[ROM] Official 2.2 (HTC 2.09 and 2.10): busybox, A2SD+, TUN, EXT4, Undervolt, SYSRW

Hi all
I decided to give you an update for the apparently much-used 2.09 ROM
This is fully rooted, kept completely stock with the following small mods,
mostly for powersaving and ease-of-use.
The following additions were made:
- Busybox + Latest su and SuperUser.apk.
- Still has A2SD+, a bit cleaner implementation this time. (Fully depends on whether or not you create an EXT partition, which can be EXT2/3 or 4.)
- OpenVPN and TUN
- Wifi module edited to make sure it never goes into standby.
- Symlinked /data/local/bootanimation.zip for easy bootanimation replacements.
- Cpufreq_interactive governor as default. This is slightly better than ondemand.
- Default undervolting by 75mV-100mV -> Major powersaving.
- UnionFS-FUSE overlay filesystem for /system. This makes /system writeable, and therefore allows you to use stuff like MetaMorph.
Thanks to tgreer for hosting my stuff!
Make sure you pick the correct radio to go with these two ROMs. It's a bad idea to use an older ROM with a newer radio, or vice-versa, seeing as these ROMs have updated RILs.
*updated* HTC 2.10 ROM
32.44.00.32U_5.09.05.30_2 radio (recommended for 2.10 - new RIL)
Older HTC 2.09 ROM
32.43.00.32U_5.09.00.20 radio (recommended for 2.09)

is this de-odexed?

lol that was fast mate cheers will flash to ther halfs phone when she gets back lol

Santa, is that you????

Nekromantik said:
is this de-odexed?
Click to expand...
Click to collapse
Not atm.
It is kept close to stock. Custom ROMs later on will be deodexed, based on this.

Great job mate. No fuss. Straight in there.

surprised...

Nekromantik said:
is this de-odexed?
Click to expand...
Click to collapse
Most probably not I guess (since the OTA also is odexed). But f*ck that, dex files just waste space on your data partition anyway.

excellent misdirection...a majority of us were following 42turkeys little run around and here you were waiting for us.

How about some credit's in the OP to the right people.

nice nice nice downloading now

That's fantastic.

Can anyone OC this Rom pls

YAY
Awesome mate!
Will take the plunge as soon as my DL is finished.
You've added exactly the bits I need (especially the OpenVPN).

Anyone tested this yet?

Fantastic up thanks
Anyone tried it yet lol

Thanks a ton m8.... will try this one instead of the few others posted

Dlding now but speed down to 100kb/s, gone tast asap.
EDIT: thnx for adding the app2sd busybox and vpn settings ;-)

and now the whole thing without f**** SENSE please ...

Can't seem to install this. It only says (Bad)

[ROM] [20/08] Pre-rooted Stock Gingerbread (3.14.405.1) [Optional Mods]

For those familiar with my pre-rooted stock Froyo ROM, this is the first release of HTC's official HTC Desire Gingerbread ROM. As before, the base ROM is entirely stock, but with the following minimal changes:
Added root (including busybox)
Superuser App - 2.3.6.3 (ChainsDD)
init.d support
This ROM requires a full wipe to install. There is no option here - the ROM will automatically wipe your phone's storage (excluding the sdcard). Therefore it's highly recommended to do a back up before installing.
The ROM does not include the radio, but you should install this at the same time you install the ROM, if you don't have this version already. The radio supplied with HTC's release is 5.17.05.23 and this is provided below.
3.14.405.1 INIT.D ROM
Download 3.14.405.1 Stock ROM (1.0-test)
md5: de99e70682971b183ed65abc6e2fc62d
Download 5.17.05.23 Radio
md5: 738a94c891a6a10082c8bf9f5c4884ba
OPTIONS
Below are some mods to this ROM (more will follow). They are purely optional, and of course take you further away from the stock ROM. Remember that all of these mods are designed to work with this ROM specifically, and not others.
UPDATE APPS (1.0) - updated || 03/08
This will update your system Google apps to the latest market versions: Maps 5.8.0, Gmail 2.3.5.
POWERSAVING MODULES - updated || 10/08
This reduces your battery usage by slightly undervolting, and by forcing the CPU down to 245MHz when the screen is off (it will also fall to 245MHz when idle). Additionally, when battery capacity falls below 30%, the maximum speed will be 800MHz, less than 20% it will be 700MHz and less than 10% it will be limited to 380MHz. When your phone is connected to a charger, it will boost performance a bit when the screen is on, and the speed will not be limited.
A2SD (1.0) - updated || 05/08
With this mod your apps will be saved to the sdcard instead of internal storage. Gingerbread includes enhanced support for moving apps to your sdcard, but not all can be moved, and so this isn't sufficient for everybody. If you need more space, this will help. For this to work you need your sdcard formatted with two partitions, the first a regular FAT partition for general use, the second an ext2/ext3 partition exclusively for A2SD. If you install the mod without a second partition A2SD will not be activated, but it will automatically start up if you create the partition later on your next boot.
MINOR TWEAKS & EXT4 (2.0) - updated || 20/08
This mod will install the default boot animation to the data area, where you can replace it with a custom one if you want to. It also allows hosts modification (you can use the AdFree Android app - do not use the symlink option in it). You will need to re-apply this mod if you do a full wipe. 2.0: Add ext4 support.
REMOVE BOOTSOUND (1.0) - updated || 04/08
Disables the sound on boot up.
INSTALLATION
Your phone must be rooted with custom recovery to install this ROM. There are plenty of guides on how to do this simple procedure. The recommended steps for installation are as follows:
Back up your contacts, apps and text messages to your sdcard; reboot the phone into custom recovery; perform a full backup in recovery; install the radio (select 'install zip from sdcard'); install the ROM; reboot.
After you update the radio the phone will reboot a couple of times, this is normal. The first regular boot may take a little longer than usual.

FAQ
Q. I have installed the official HTC developer Gingerbread update. Can I install this?
A. The preview of the new version of Alpharev (Revolutionary) should be able to help you with this.
Q. Do I need to install this radio?
A. No, but it's highly recommended.
Q. Does this support 720p?
A. Yes. It supports everything that the official ROM supports.
Q. My wifi disconnects occasionally - I had no problem in froyo.
A. This is a problem with the official ROM. It cuts the wifi connection if the signal falls low and switches to your data connection. There will be an optional mod to revert this soon.
Q. Can I use this with Alpharev?
A. Yes. But your system partition must be 250mb.

Hi Teppic,
I'm still using your froyo rom. Thank you very much, runs very smoothly. I didn't use the a2sd+ you included there but i need more room now.
How much space is left to install apps after installing this rom?
Will you include a powersaving modpack?
If you add some form of apps to sd will you give us the option of keeping dalvik cache on the internal memory? (If I have read correctly, this gives least lag)

j5m said:
Hi Teppic,
I'm still using your froyo rom. Thank you very much, runs very smoothly. I didn't use the a2sd+ you included there but i need more room now.
How much space is left to install apps after installing this rom?
Will you include a powersaving modpack?
If you add some form of apps to sd will you give us the option of keeping dalvik cache on the internal memory? (If I have read correctly, this gives least lag)
Click to expand...
Click to collapse
I think there's about 120mb free on a clean installation. Remember that in Gingerbread the official apps to sd function is better than in Froyo, and might be enough.
I need to spend more time to get other mods sorted out, but I thought it would be best to get the base rom out immediately.

altough I'm an AOSP fan this seems an excelent choice to go stock.
tks

Thanks for this, I was a big fan of your Froyo rom!
Looking forward to A2SD support.

Thanks a lot teppic74 for this ROM.
I'm using your Froyo ROM since months and will use this Gingerbread ROM as soon as the powersaving modpack will be available.
One mod that could be very useful is DATA2SD : [DEV][DATA2SD] More space (and more I/O) for your Desire (Updated/EXT4/Flashable ZIP). I'm using it with success on your Froyo rom.

Thanks for this release!
Only reason I'm on Sense is due to the lack of an aosp rom supporting 720p recording on the Desire, and this makes it nice knowing I don't have to get locked in with the new hboot etc.
Thanks!

i heard this rom just for development testing and not every day use, what thing are laggy/buggy in this rom thanks. i heard battery is terrible...

Cool & thanks! I'm also still on your Froyo A2SD... (in spite of being tempted many times by the earlier sense GB ports... I want something stable and stock-like)
I made a few home-made mods on your Froyo (install a few more apps to system, like the brilliant widgetsoid).
Anyway, as soon as your A2SD GB out, I'll try it
Sent from my HTC Desire using XDA App

kuljit55 said:
i heard this rom just for development testing and not every day use, what thing are laggy/buggy in this rom thanks. i heard battery is terrible...
Click to expand...
Click to collapse
I've been reading a lot about the HTC release. There's nothing wrong with the HTC ROM... (Other than being unrootable and irreversible). If you want to discuss the HTC ROM though, there are other threads about it.
Let's stick to teppic74's custom work here.
Sent from my HTC Desire using XDA App

Thanks for the release, mate, appreciate it!
But, really, Amend scripts?

Proz0r said:
Thanks for the release, mate, appreciate it!
But, really, Amend scripts?
Click to expand...
Click to collapse
It's what I'm used to...
(New updates will be in the newer format)

Thanks for your work always
Sent from my HTC Desire S using XDA App

I love your roms. Can this one be flashed on the data++ alpharev hboot table? Thanx

fred_be9300 said:
I've been reading a lot about the HTC release. There's nothing wrong with the HTC ROM... (Other than being unrootable and irreversible). If you want to discuss the HTC ROM though, there are other threads about it.
Let's stick to teppic74's custom work here.
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
so if i flash with this CFW can i can not root or revers even though this has been pre rooted?

wings400 said:
I love your roms. Can this one be flashed on the data++ alpharev hboot table? Thanx
Click to expand...
Click to collapse
Not a chance - the ROM takes up almost the full 250mb.

kuljit55 said:
so if i flash with this CFW can i can not root or revers even though this has been pre rooted?
Click to expand...
Click to collapse
Sorry, to clarify: it's the original GingerBread Sense ROM from HTC that, if installed using the HTC release (RUU), will be unrootable and irreversible (at the moment - with all current tools).
All custom ROMs derived from it, are pre-rooted and reversible.

Can anyone let us know hows 720p recording and playback?

mayurh said:
Can anyone let us know hows 720p recording and playback?
Click to expand...
Click to collapse
720p recording/playback works for me. That said, although tough lighting conditions, it seems *only imo, and I'm sure it;s just my eyes as doubt anything changed* it seems worse. Could just be me though.

[28th Jun][AOSP] INT2SD, a new D2EXT method (added CM 7.1 and 7.2.0.1 INT2SD-S)

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...?

[ROM] MildWild v2.9.5 Lite Final

Clarification on the poll question:
Yes = The ROM stays up
No = The ROM goes down
With the permission of MildWild I bring to you
MildWild v2.9.5 Lite Final
(based on MildWild V-2.9.5)
This is NOT a new ROM! It's only a trimmed down and fixed up version of MildWild V-2.9.5.
Change Log for Final Version:
- NEW - ZipAligned all system apks
- NEW - Automatic ZipAlign of new apks on every boot
- Fixed 720p HW encoding - works for H.264 format ONLY (see link to test file below)
- Fixed SuperCharger script - now using V6 SuperCharger update 8 with Aggressive 1 Setting
- Updated GO Launcher EX v2.77
- Updated Superuser v3.0.7
- Added HTC Stock Alarms, Notifications and Ringtones to the separate Media Package; converted all sounds to OGG Vorbis.
Fallout 3 Trailer @ 720p in H.264 - test file for HW decoding
F.A.Q.
I. Why would I want to install MildWild v2.9.5 Lite?
- It's smaller so it will fit on the Alpharev Oxygen r2 Hboot meaning that you will get a larger data partition and more space to install your applications. (Alpharev Oxygen r2 partition sizes: 100MB system, 5MB cache, 332MB data; Alpharev CM7 r2 partition sizes: 145MB system, 5MB cache, 287MB data)
- It stores apps and dalvik on sd-ext so you get even more space for your applications. On the downside, the ROM may become a bit slower.
- Alternatively, you can install the version which keeps dalvik on the internal memory.
II. So, how come MildWild v2.9.5 Lite is smaller?
- Some non vital system data and system applications have been removed from the instalation package.
III. Right, so what's missing?
- These applications have been removed:
1. GMmail (Gmail.apk) - you can install it from the Market so it will go to sd-ext instead on the internal memory, hence you get more space;
2. Google Talk (Talk2.apk) - well, you have to make some sacrifices; however, I think you can install it manually from the apk package but I haven't tried myself;
3. Google News & Weather Widget - you can find a whole range of simmilar applications on the Market; or you can probably install it from the apk package but I haven't tried;
4. Stock 3D Gallery (Gallery3D.apk - I recommend QuickPic from the Market instead; it is smaller and does the same job better;
5. Stock Music Application - there is a whole range of media players on the Market; this however will break the ability to play music through the Desk Clock Application; however, you can probably install it manually from the apk package but I haven't tried;
6. Typological Clock (TypoClock.apk) - you can most likely find something simmilar on the Market; or you can probably install it from the apk package but I haven't tried;
7. Timer Widget - you can most likely find something simmilar on the Market; or you can probably install it from the apk package but I haven't tried;
8. File Manager (FileManager.apk) - you can find a whole range of File Manager applications on the Market;
9. Compass (compass.apk) - you can find a whole range of Compass applications on the Market;
- Launcher 2 has been replaced with GO Laucher EX; it's smaller, faster and I think generally better; then again, it's a matter of taste;
- All alarms, notifications and ringtones have been removed from the installation package. Instead, you can download the media package attached (see link further down), unzip it, and place the folder as it is anywhere on the FAT32 partition of your SD card and it will work just the same. The system will automatically detect these files on the SD card.
- All PicoTTS (voice output) data files have been removed from the installation package. Instead, you can either download them from the Market or download the svox package attached (see link further down), unzip it, and place the folder as it is in the root of your FAT32 partition of your SD card and it will work just the same. The system will automatically detect these files on the SD card.
IV. So what's the point if I still want these applications?
- Whatever you install from the Market will go to sd-ext so you will have more space on the internal data partition for additional applications. If you keep the dalvik internal then the application data will stay on the internal memory but you still get some benefit as the apk still goes to the sd-ext.
- On the downside you can't get some of them on the Market and they may not install properly from the apk package so if you want to use exactly these apps then you'd better stick to the fully fledged MildWild ROM.
- However, you can download the apps package attached (see link futher down) and play with the apk files.
DISCLAIMER
ALL CREDITS go to MildWild.
I am NOT a delevoper and I have NOT developed any of the apps, bins, libs, etc. included inside the instalation file. I simply unpacked MildWild's zip file and removed/replaced a couple of things here and there, and then repacked it back. You can ask me questions but I cannot guarantee that I will be able to answer. Also, the responsability of installing the ROM and playing around with it lies 100% with YOU!
Download Links
MildWild v2.9.5 Lite Final (with dalvik on sd-ext)
MildWild v2.9.5 Lite Final (with dalvik on internal memory)
Media Package including HTC Stock Sounds - OGG Vorbis (alarms, notifications, ringtones)
Apps Package (all apks that have been revomed from the installation)
SVox Package (PicoTTS data files)

MildWild v2.9.5 based on Oxygen (The Original)
NOTE! This is the LAST and FINAL version of my modified ROM.
As you may or may not know, to concentrate on the CyanogenMod version MildWild has stopped development on the Oxygen version of this ROM for the foreseeable future (see here: http://forum.xda-developers.com/showpost.php?p=22130173&postcount=2568). As such, this is also the last update from me.
Do check out the ORIGINAL!​
MildWild v2.9.5 based on Oxygen​

Removing a launcher and replacing it with another one doesn't make it a custom ROM. This could all be put into a flashable ZIP which has to be flashed on top of a stock MildWild ROM, so that the update-script removes all the APKs. But another topic just for a modified ZIP only causes a lot of confusion.

what is the point of this ? everyone could make this.

Chaosz-X said:
Removing a launcher and replacing it with another one doesn't make it a custom ROM. This could all be put into a flashable ZIP which has to be flashed on top of a stock MildWild ROM, so that the update-script removes all the APKs. But another topic just for a modified ZIP only causes a lot of confusion.
Click to expand...
Click to collapse
Please read the description...

expler said:
what is the point of this ? everyone could make this.
Click to expand...
Click to collapse
Constructive comments would be very much appreciated...

Not a fan PERSONALLY of this "I can unzip, remove a few apps, then re-zip and post as a new rom" attitude, but it's a case of supply and demand I suppose. At least the OP has had permission from MildWild.

Screen ? ^_^

lolitz said:
Screen ? ^_^
Click to expand...
Click to collapse
Will do later on.
In any case, appart for the GO Launcher EX bits it looks exactly like MildWild - he's the BEST! (see link below)
MildWild v2.9.5 based on Oxygen

whats the point in making this a whole new thread?
it's some deleting/adding stuff to a zip file.. nothing else.
absolutely no need for this in my opinion, 'cause everyone can open a .zip file and delete stuff they don't want, and add stuff they want.
if we continue this road, we have 20 roms based on mildwild, and 20 different threads filled with the same questions over and over and over and over and over again.

horst0815 said:
whats the point in making this a whole new thread?
it's some deleting/adding stuff to a zip file.. nothing else.
absolutely no need for this in my opinion, 'cause everyone can open a .zip file and delete stuff they don't want, and add stuff they want.
if we continue this road, we have 20 roms based on mildwild, and 20 different threads filled with the same questions over and over and over and over and over again.
Click to expand...
Click to collapse
Please vote in the poll...
If people don't like it, then I'll remove it...

horst0815 said:
whats the point in making this a whole new thread?
it's some deleting/adding stuff to a zip file.. nothing else.
absolutely no need for this in my opinion, 'cause everyone can open a .zip file and delete stuff they don't want, and add stuff they want.
if we continue this road, we have 20 roms based on mildwild, and 20 different threads filled with the same questions over and over and over and over and over again.
Click to expand...
Click to collapse
whats with the hate? it saves people time of doing it themselves if they dont know what system related stuff they can remove without causing problems
it gives more space and mildwild allowed him to do it.
if you dont want it dont use it, im sure some people would be happy to use it.
as fopr putting it on the same thread? why would he hyjack an ops thread with different work. i doubt people would but it could be seen as trying to take people away from the original ops rom or some people might be confused with it being by mildwild himself as its displayed in a rom dev format..
people need to chill out, leave the complaining to the other devs if they have an issue with it and everyone else concentrates on flashing.
i dont see you complaining about the many different varients of stock roms that are modified in a kitchen using the same kernel as every other rom and called something different.
i dont see you complaining of the clones of 3.5 sense roms that have had different apps added just to call it something different.....
grow up

The ROM was great... That's very rude of you guys
He's just trying to help the people that don't know that much about ROM's.
OP, please continue what you're doing, it's great!
I'm already using your ROM

Guizzoni said:
The ROM was great... That's very rude of you guys
He's just trying to help the people that don't know that much about ROM's.
OP, please continue what you're doing, it's great!
I'm already using your ROM
Click to expand...
Click to collapse
Thanks...
Some people really put you down sometimes...

Rastaman-FB said:
whats with the hate? it saves people time of doing it themselves if they dont know what system related stuff they can remove without causing problems
it gives more space and mildwild allowed him to do it.
if you dont want it dont use it, im sure some people would be happy to use it.
as fopr putting it on the same thread? why would he hyjack an ops thread with different work. i doubt people would but it could be seen as trying to take people away from the original ops rom or some people might be confused with it being by mildwild himself as its displayed in a rom dev format..
people need to chill out, leave the complaining to the other devs if they have an issue with it and everyone else concentrates on flashing.
i dont see you complaining about the many different varients of stock roms that are modified in a kitchen using the same kernel as every other rom and called something different.
i dont see you complaining of the clones of 3.5 sense roms that have had different apps added just to call it something different.....
grow up
Click to expand...
Click to collapse
Dito!
Thank you for the support.

I voted yes. Do not delete this thread!

Oh, I do get annoyed by all the Sense ROMs too. With all that ROMs out there it's pretty hard to see the difference, so that's a mess too IMO.

Chaosz-X said:
Oh, I do get annoyed by all the Sense ROMs too. With all that ROMs out there it's pretty hard to see the difference, so that's a mess too IMO.
Click to expand...
Click to collapse
Please vote in the poll...

do3in said:
I voted yes. Do not delete this thread!
Click to expand...
Click to collapse
Do you know if we can get Android in Romanian? I would like to add it to this trimmed ROM.

I'm a little bit confused with the poll:
Do you think this trimmed ROM is useful = yes
or I should take it off = no
how to vote yes and no...? hehe
anyway good luck with the rom and thanks for sharing

[Q] PAC-Man ROM v22.3.0 ~AOSPA + AOKP + CM10.1~ - OTA updates (5/19/2013)

Alright, noob here. Since I cannot post in the PACMAN development thread (http://forum.xda-developers.com/showthread.php?t=2164406) I will put this here.
- Problems installing PACMAN ROM
- After receiving "Errors Flashing", failures, downgraded recovery to TWRP 2.3.3.0
- 2.3.3.0 displayed "Error 7"
- Searching on error 7 led me down the path of the assert checks
- updater-script assert command in PACMAN ROM package is checking for model "ville".
- My HTC One S Special edition returns "villeplus" from "adb shell getprop ro.product.device"
My understanding is that the North American S4 and the Special Edition share identical hardware, only differing in drive size (16 vs. 64GB), so I am assuming any ROM designed for the ville will work on my phone.
Assuming it will I should be able to edit the "updater-script" file, but when I extract it windows is telling me that 23 files are duplicates. I'm not sure if this is because its windows vs. Linux that I'm extracting it on?? In any case, I don't seem to be able to modify the file without adversely affecting the integrity of the archive. Also would assume replacing the file will affect the MD5 hash which I believe TWRP checks when loading the ROM?
So first off, can someone confirm that this ROM will be compatible with my phone and 2, any suggestions on modifying the updater-script file within the archive?

Update
I was able to modify the updater-script file tonight using file X-Plore and text edit, so now the script is looking for "villeplus" rather than ville. My phone is S-OFF which I read means that it does not do signature checks... however, I'm not sure if that also means it bypasses MD5 checksums - I suspect not since I'm pretty sure I saw it verifying MD5 previously. So, since I tampered with the ZIP it still may not work.
My real question now that remains is even if it will work, do I want to flash a ROM built for the ville to my villeplus. The more I read about custom ROMs the more it appears that they are extremely specific to models.
I am still extremely curious to try it... rumor has it that curiosity didn't work out so well for the cat though. :-/

merovingian_a51 said:
I was able to modify the updater-script file tonight using file X-Plore and text edit, so now the script is looking for "villeplus" rather than ville. My phone is S-OFF which I read means that it does not do signature checks... however, I'm not sure if that also means it bypasses MD5 checksums - I suspect not since I'm pretty sure I saw it verifying MD5 previously. So, since I tampered with the ZIP it still may not work.
My real question now that remains is even if it will work, do I want to flash a ROM built for the ville to my villeplus. The more I read about custom ROMs the more it appears that they are extremely specific to models.
I am still extremely curious to try it... rumor has it that curiosity didn't work out so well for the cat though. :-/
Click to expand...
Click to collapse
Unfortunately, i have to fully disappoint you.
The villeplus is having the exact same hardware as the ville. Theoretically ideal. Unfortunately, HTC decided to make it a "/data/media" device unlike its brother, the ville.
Explained: the Ville has a partition for the SDCard and its mounted with its own mountpoint, /sdcard.
The Villeplus has a partition for the SDCard too, but its mounted inside the /Data partition as /data/media. This means a lot of problems from every imaginable aspect.
I spend a week together with Torxx from ViperOneS to get Viper to run on it and we found out that a.) the Kernel needs to be adjusted and b.) some libs and etc. which is real dev work and which no dev in the OneS section has time for.
Later i spent another two weeks with Philz and mdmower trying to at least get recovery to mount the sh.it thing as USB, which turned out to be impossible at this time as it is only possible through the MTP protocoll, which no recovery supports as of yet.
Since i am a n00b myself i did not entirely understand the nature of the problem, but it seems to be very complex.
At some point i suggested to actually rewrite the partitions on the phones so they would work the same way as on the ville. I even tried myself and flashed a Ville RUU to my Villeplus (it works, doesnt break anything) but with the same effect as custom roms: my SD was then in Data/media and the internal apps memory and RAM were shifted to somewhere else with not enough space so the phone kept running out of space and crashed often. Also all system components trying to access stuff on the SD failed to find their stuff and crashed.
Since we don't actually have means to change the chip controller programming so it offers the partitions differently to the ROM we cannot go that way either (Zarboz tried to explain it to me but i failed understanding it, somehow the device pathes are put into the actual chip and not part of any RUU, so to change them one would need to have some special software tool like we could have done on the HD2 back then).
The only viable way would be to adjust ROM modules and Kernel to this structure, which won't happen as no dev has this device and there are like maybe 5 active users here.
You are out of luck my friend. Sorry. I too was full of hope and gave it up when all devs i contacted signalled that there is no benefit for them and they wouldn't waste their time basically.

Sneakyghost said:
Unfortunately, i have to fully disappoint you.
The villeplus is having the exact same hardware as the ville. Theoretically ideal. Unfortunately, HTC decided to make it a "/data/media" device unlike its brother, the ville.
Explained: the Ville has a partition for the SDCard and its mounted with its own mountpoint, /sdcard.
The Villeplus has a partition for the SDCard too, but its mounted inside the /Data partition as /data/media. This means a lot of problems from every imaginable aspect.
I spend a week together with Torxx from ViperOneS to get Viper to run on it and we found out that a.) the Kernel needs to be adjusted and b.) some libs and etc. which is real dev work and which no dev in the OneS section has time for.
Later i spent another two weeks with Philz and mdmower trying to at least get recovery to mount the sh.it thing as USB, which turned out to be impossible at this time as it is only possible through the MTP protocoll, which no recovery supports as of yet.
Since i am a n00b myself i did not entirely understand the nature of the problem, but it seems to be very complex.
At some point i suggested to actually rewrite the partitions on the phones so they would work the same way as on the ville. I even tried myself and flashed a Ville RUU to my Villeplus (it works, doesnt break anything) but with the same effect as custom roms: my SD was then in Data/media and the internal apps memory and RAM were shifted to somewhere else with not enough space so the phone kept running out of space and crashed often. Also all system components trying to access stuff on the SD failed to find their stuff and crashed.
Since we don't actually have means to change the chip controller programming so it offers the partitions differently to the ROM we cannot go that way either (Zarboz tried to explain it to me but i failed understanding it, somehow the device pathes are put into the actual chip and not part of any RUU, so to change them one would need to have some special software tool like we could have done on the HD2 back then).
The only viable way would be to adjust ROM modules and Kernel to this structure, which won't happen as no dev has this device and there are like maybe 5 active users here.
You are out of luck my friend. Sorry. I too was full of hope and gave it up when all devs i contacted signalled that there is no benefit for them and they wouldn't waste their time basically.
Click to expand...
Click to collapse
Wow, Sneakyghost, I can't thank you enough for your prompt (I just PM'd him last night folks) and very thorough response.
I'm wondering why HTC did this - thinking maybe to prevent/protect users from tampering with the device - perhaps other ROMs wouldn't run on it in a stable fashion.. or they just don't want people messing with custom ROMs. Perhaps this was a new architecture for them (wondering if the One and One X followed this same design?).
In any case, looks like I'll be sticking to looking at launchers and custom widgets. I'm actually quite happy with 4.1.1 and Sense (maybe because I'm new to Android, not sure), I mainly wanted to try experiment with custom ROMs, and learn about how all this stuff works. At least till the M4 comes out anyways..
Thanks again so much for your response, it is much appreciated and well explained.

Sneakyghost said:
... Unfortunately, HTC decided to make it a "/data/media" device unlike its brother, the ville.
Click to expand...
Click to collapse
Oh the irony, the (unreleased) 4.2 update for ville actually reformats partitions for data media. I don't think the update will ever be officially available to US users, but it is funny nonetheless.

This, my friend, is indeed ironic, if not even sad.
Considering what it means, I come to understand that porting ROM's from Ville to Villeplus would have gotten much easier then. Only that it is too late.
Torxx and I gave up due to the amount of work attached to the previous system structures, but if the Ville turns into a datamedia device with that update, many ROM devs and chefs would have to deal with it plus HTC would have done the most difficult part already anyway...
What a shame that this comes so late now and doesn't even get released probably...
mobile post