yashsingh1/xdaforums huggingface dataset:
[HD2 Android NAND Development] Sneakyghost:
If you refer to the \System partition by saying "ROM Partition" you cannot reduce its size further by removing unwanted apps, as the apps are not in \system.

Do it like this:

1: open the ROM.zip with 7zip as usual

2: remove whatever you deem safe to remove from the directory \system

3: check the second column in 7zip (Size). It will tell you the System Size in total bytes (unpacked).

4: use your calculator and devide that figure (9 digits) by 1024x1024 (1048576) to gain the System Size in MegaByte.

5: add +20 Megabyte to that size. Now you know your ROM Partition size.

So, according to my 7Zip, the themed ROM has a default System Size of 146746014 bytes. devided by 1048576 it reads 139,94 Megabytes, read: 140 Megabytes. Add 20 will make it 160 Megabytes. So, to my understanding, the recommended 172 are still to big and just there to make it easier for the people (some find it a hard thing to repartition their NAND).

The default stock values read like this: 146505140 / 1048576 = 139,72 or 140 Megabytes. not a big difference.

From the System, the only thing safely removable are the sounds unfortunately. With everything else you will start to mess with things badly. If you really need more to remove, ask Dan what you can take out without damaging the functionality. I have had a close look at it and i don't see much more than the sounds to remove.

The Apps get installed on the SD-EXT anyhow on Dan's design. What you see on NAND is just Hard Links or SymLinks or in Windows you would know it as Junctions.

[EDIT]

Something isn't right in my explanation as i just noticed all the media is in \parts1 and not in \system! Dan, could you please correct my post here as i want to add that information to the FAQ page? i remember, the sounds used to be in system, right? and how to correctly calculate the System Partition size? Do we need to add the size of \parts1?
[HD2 Android NAND Development] zxf3000:
thank you:)
[HD2 Android NAND Development] sandymac:
Marcus, I always delete audio files and have been using partition 7/152/7 since 3.4 build. Unfortunately, you are not going to release much more space re the partition size by removing unwanted apps as they are all moved to sd-ext, anyway, with just a pointer left in main memory. You will, however, reduce the dalvik size each time you remove an app. So your real option is to use Titanium to remove as many apps as you wish then use either Stephan's DalvikMover or Total Commander to check the size of the Dalvik. Also use Total Commander to check which programs within Dalvik are the largest and see if you can delete these. :D

One thing for everyone to bear in mind is that when you update installed apps to the latest version via the market then your available memory will reduce significantly as it would appear these are not moved to sd-ext. Not sure what Dan would need to do to make this happen. :mad:

Edit: I see Sneaky beat me to it with some useful info. :D
[HD2 Android NAND Development] brush2:
Hey Sneakyghost :)

how are you?

Damn - right after typing my stupid stuff about Marcus's partition sizes, i saw your post :D

Marcus - forget about my stuff - the master arrived :)

Yours,

Stephan
[HD2 Android NAND Development] Sneakyghost:
No what i wrote is most likely bull**** too.

The Media is located in \Parts1 and if i am not totally mistaken, that directory contains everything that goes to SD-EXT. So it is a part of \System but it is the part located on the SD-EXt. Thus it does not influence your available RAM space if you remove stuff from there. In fact, transfering Media from SD-EXT to FAT Partition like Sandy did would be pretty pointless if my theory is right (Sorry Sandy :D )

And the reason Sandymac can run on 152 is not because he removed media, but because the real system size is just 140 and with 152 he's got about 12 megs free space which might just be about ok for the ROM to work....

The Media Files, excluding UI sounds, are just 12,9 Megabyte unpacked anyway, so not too much space to be gained anyhow, even if it did influence the NAND space.

WE actually need Dan to clear things up as he knows how he had built this ROM and i dont find the scripts that setup the ROM where it says what goes where. I also don't feel like digging deeper into the matter as i actually want to work on my car now as long as the sun is shining outside...

Have a good day guys and maybe dan can clear up the mess here.
[HD2 Android NAND Development] brush2:
DalvikMover

Hi all,

right now i have a sum of 43 test results of DalvikMover v1.1x beta.

42 results are positive; 1 result is negative for some reason and this will be checked of course.

For this reason, i declare DalvikMover_1.11_beta to final release.

You can download TBDdalvikMover_v1_11_beta.apk and you can use it as "temporary final release",

since there will be no difference to DalvikMover v1.12 final release.

When i am back at home tonight, i will provide a final version DalvikMover v1.12.

Regards,

Stephan
[HD2 Android NAND Development] underboy2008:
Good Rom

I'm using this rom for 4 days now and its very stable for me. The only thing i noticed was the results on benchmarks... Only 1076...

The rom is very fast for a 3.5 sense rom. My feedback is very positive!

Great Work! :cool:
[HD2 Android NAND Development] sandymac:
You may be right to a degree, Sneaky, but on checking files structure, it looks like audio is on both /system and sd-ext/sys-parts/ - not sure why they are duplicated. I certainly remember Dan mentioning some time ago that the only way to reduce the size of the ROM was to move the audio files to the sd card. Perhaps Dan can clarify, as you said. Or someone can look at both /system/media and sd-ext/sys-parts/media on their phone and advise if the files are actually shown in both areas. The only files I left were in ui folder and they appear in both locations.

In any case, my comments regarding reducing the dalvik stand as this is the only way to ensure sufficient space on EU phones to have dalvik cache on internal memory.

Anyway, I'm with you Sneaky, the sun is shining here and rain due later so got to make the most of it. :D
[HD2 Android NAND Development] brush2:
Symlinks

Hi Sandy,

how are you?

I checked the "media" locations:

/system and sd-ext/sys-parts/

/system -> media is a symlink that links to /sd-ext/sys-parts -> media via symlink:

"media -> /sd-ext/sys-parts/media"

on my device, so it just looks like duplicated media in some file explorers, but it's a link.

Hopefully i am not the only one with this configuration :)

Yours,

Stephan
[HD2 Android NAND Development] marcusloosewire99:
Stephan, Sneaky & Sandy

folks you are what makes this forum great, a simple question with comprehensive responses and no sarcastic comments.

I appreciate all of your responses, every day we learn a little more!

I have just flashed 3.7 themed after removing many apps I never use. I have used a 7/152/7 partition, moved audio files (except UI) to SD-card and have just downloaded the latest Davlik mover. I'll play for the next day or two and report back.

Unfortunately tomorrow I have to go back to work for the week so I'll be limited to evening feedback only as work computers are screwed down so tight I have no hope of getting on the forum without some it security manager tearing me off a strip!

many thanks

Marcus
[HD2 Android NAND Development] brush2:
Slim Rom

Hi Marcus,

you're embarrassing me :D

I think, it's just the way, people should behave:)

Yours, Stephan
[HD2 Android NAND Development] sandymac:
Stephan and I are currently trying to figure out why nand reduces when you install updates to your apps (as I have experienced). So far, we have discovered that dalvik still retains the original apk's data which effectively bloats it. I have just tested how this could impact by deleting dalvik and rebooting. Before reboot (and with a number of updated apps), dalvik was 136.4Mb and after reboot it is 127.9Mb so something to remember when updating your apps. Incidentally, it also increased available NAND from 126Mb to 137Mb. Don't know why yet.....

So, in summary, apk updates are actually stored on sd-ext and not as I suspected on nand so apologies for that. When you update apps then dalvik will increase in size and nand will reduce (reason unknown at this time). It is therefore important to clear dalvik after all updates have been applied to maximise available memory. :D
[HD2 Android NAND Development] Sneakyghost:
OK thanks guys i think the Symlinks are what we are seing in system so Dan's comment on reducing system size by moving audio must be from the times before he had that stuff located on the EXT.

So its pointless to move it over to the FAT partition. Pity. I had already written a little article on the FAQ for it. Gonna remove it again :D

The weather looks fine from inside but its effing freezing outside so i am not gonna swap my speakers today as thats no fun with stiff fingers...

will install the themed ROM now. Fun too... jeez i gotta remember all that stuff to do before. nearly a month now since swapping over to WP7...
[HD2 Android NAND Development] Dunc001:
Sandy, can you confirm this please. Bit puzzled because the way we have cache set up is that Market should download to a temp location, install the app then delete the file downloaded from Play Store as soon as it is installed (rather than leaving a load of download.apk files in /data as it used to). Then as soon as you reboot your phone any new updates if still in internal memory should then move to sd-ext/app. Are you saying this isn't happening even after a reboot?

Edit - OK, just read your later post which confirms it is working as it should - run your updates then reboot (the a2sd script runs at boot and moves any new apks to sd-ext/app, overwriting any existing ones as it does so). I guess the temporary 'slowdown' you may experience when updating/installing apps comes from the use of the temp mount during the download/install process - we did this to make the Play Store installs cleaner by deleting the temp files right after they are finished with.

And yes, you are all just seeing symlinks regarding the audio files in two locations. Some file explorers are better at identifying these than others...
[HD2 Android NAND Development] essi_baba:
hi

please give me 4ext recovery link
[HD2 Android NAND Development] Sneakyghost:
How about going to Page 978 as recommendet on the Release posts and downloading the Recovery Package you want?

Alternatively, you may also go to my Mediafire Folder and grab it there... links in my sig...
[HD2 Android NAND Development] sandymac:
Duncan, many thanks for the clarification. Most welcome. Just to be clear, from what you say, the ROM as is can be installed with a partition of 7/152/7 or am I missing something?

Regarding dalvik cache, it looks as if you still have to reboot after updating any apps as the update is added whilst leaving the original in place.

The final conundrum, as far as I can see, is the reduction in free memory after updates. Whilst a reboot recovered some memory, possibly from temp files (see my previous post), it did not recover all as I started with over 150Mb before updating any apps. Any ideas on why this is?
[HD2 Android NAND Development] essi_baba:
thanks guy
[HD2 Android NAND Development] Dunc001:
/system as it comes in 3.6/3.7 unpacks to 139Mb IIRC so 152 is fine (although there seems to be a golden rule set way back when of adding 20Mb - no idea why as it never seems to get used unless you're flashing mods that add new libs etc). I am using 160Mb /system partition but have around 14Mb free in that at present.

Don't get confused by Dalvik Cache and the download cache I was talking about earlier. It's just the download cache that gets flushed after use. Play Store downloads a file which it then extracts and installs to data/app. Our cache setup (NOT Dalvik Cache!) is such that Store downloads this file to a temp mount (ASEC) which is then flushed as soon as it has installed. At reboot the a2sd script then moves the apk from data/app to sd-ext/app, but some apps install some unmoveable stuff to system memory AFAIK so if it's new apps you are installing it might explain the increase in size, but probably not if you are just updating already installed apps. To make sure the download cache setup is working right and not leaving artefacts behind take a look in /data or /data/data and make sure there are no download.apk files...
[HD2 Android NAND Development] sandymac:
Thanks, again, Duncan for the information. Don't worry, I understand the difference between your reference to /data and dalvik. Herewith an example of what I have found regarding memory:

Before updating Google Voice Search:

/cache = 60.5k

/data/data = 59.1Mb

/sd-ext/dalvik-cache - 127.9Mb

Internal memory = 139Mb

sd-ext = 373Mb

After updating Google Voice Search:

/cache = 2.2Mb (contains the Download.apk)

/data/data = 60Mb

/sd-ext/dalvik-cache = 130.4Mb

Internal memory = 139Mb

sd-ext = 368 Mb

After deleting all dalvik entries via TC and rebooting

/cache = 60.5k (successfully deleted download.apk)

/data/data = 56.9Mb

/sd-ext/dalvik-cache = 128.1 (successfully deleted old Voice data)

Internal memory = 142Mb (suddenly I'm getting an increase in memory each time I reboot???)

sd-ext = 371Mb

As you can see from the above, it is necessary to both clear dalvik cache and reboot after updates are made to any program otherwise the cache will not clear. Absolutely no idea why I am now suddenly seeing my free memory climbing...... :confused: This is obviously as a result of something additional in /data/data being deleted but I don't know what.

EDIT. Strange that internal memory as reported in Titanium and system settings is the same both before and after the update then increases by 3Mb after the reboot. I would have expected it to drop after the update..... :confused:
[HD2 Android NAND Development] Dunc001:
OK, I don't have my HD2 here so I'll take a look again tonight and see if I can shed any further light.
[HD2 Android NAND Development] LUZPIVER:
TO INSTALL helps 3.7 3.3 ABOVE

Hi, I have version 3.3 installed fear and fable goes, but I like to try the 3.7 fear.

As the install over:confused:

Thanks for your help and greetings;)
[HD2 Android NAND Development] brush2:
update to v3.7

Hi mate,

yes ;) - but you can do a backup of your important stuff via Titanium Backup.

For TBD ROM v3.7 you need to flash a recovery with NAND Partitions of 7/172/7 or for TmoUS phone 7/277/7 megabytes of size.

Carl1961 published an installation manual, which seems to be up to date.

Please use this documentation to install it - but with NAND Partition size of 7/172/7 or for TmoUS phone 7/277/7 megabytes.

After flashing v3.7 you can restore all stuff you saved before.

Please don't forget anything - Bookmarks, Emails, SMS, MMS, not even the sync stuff like Contacts and Calendar! :)

You will not regret it! :)

Regards, Stephan
[HD2 Android NAND Development] alex.odell.2011:
V3.7 has double the battery life of V3.6 here :)
[HD2 Android NAND Development] LUZPIVER:
Thanks.
[HD2 Android NAND Development] brush2:
Battery life

:eek: Was v3.6 so bad?

LOL- Hi Alex,

i think it wasn't that bad :D

But - we never had a better one than v3.7:)

Yours, Stephan
[HD2 Android NAND Development] johnnyvb78:
TBD dalvikmover

Hello,

i'm using dalvikmover now for a day or 2 and it works until now perfect.

I repartitiond my HD2 to 7/147/7 and i have 2.29 MB free in system rom and about 32 apps installed. it gives me 51.8 MB free space, acording to titanium backup....

i'm happy with this setup now.

:):)
[HD2 Android NAND Development] zulwik:
How kernel it is better ? Now i have marc 1,8.
[HD2 Android NAND Development] brush2:
Thanks

Hi mate,

good to hear you are fine with it.

If you have suggestions - please hit me :D

Regards, Stephan
[HD2 Android NAND Development] alex.odell.2011:
I'm using Marc's 2.0,

I have got 11 Hours, Medium/Heavy Use :)

On V3.6 I got only 6 hours at same use :)
[HD2 Android NAND Development] zulwik:
Nice thanx Mate ;)
[HD2 Android NAND Development] brush2:
marc 2.0

Hi zulwik,

i am using mark 2.0 and i am really fine with it :)

Regards, Stephan
[HD2 Android NAND Development] alex.odell.2011:
Press the button ;)
[HD2 Android NAND Development] johnnyvb78:
I updated the kernel to 2.0 and in tweaks/Rosie I turned to full 2d scroll.

I clocked the phone to min. 96mhz and max. 1305mhz in interactivex.

Maybe it helps for others.

Verstuurd van mijn HTC Sensation XL with Beats Audio X315e met Tapatalk
[HD2 Android NAND Development] gecata:
96mhz is not good for our phones. Snapdragon processor cannot scale correct from speed below 245mhz. If speed is set below - firs jump to 245 and then to another selected speed. You get a risk of freeze.
[HD2 Android NAND Development] Sneakyghost:
G'day all.

Have now setup the Themed ROM EU on 7/160/7.

Report:

+ Fast and responsive, mostly bug free

+ ADB connection improved A LOT! Suddenly i can actually use Droid Explorer. Not sure if it is to do with the ROM though. Might also be Changes in my PC as i have cleaned out my Windows recently.

- Gmail themed and unthemed both onboard. Had to take out the unthemed prior to flashing.

- Some Apps outdated: Maps (6.5.0), SoundHound (2.9.7), Titanium Backup (4.9.0.2), Adobe Flash and Adobe Reader, SDBooster (1.5.4), Google VoiceSearch (2.1.4), Google QuickSearchBox (1.3.3.247963) and Google PlayStore (3.5.16) are all outdated in the default App-Package. Some only updated after ROM release, no biggy.

- Crypted's GPS Fix not integrated by default. Am a little disappointed as that Fix has really proven its value. I recommend using it. Can be found on his thread and also put into \Sytem\etc before flashing.

I extracted and mirrored the most important Apps on my MediaFire folder if anyone wants to integrate them prior to flashing. Saves some updating later.

This morning on my way to work i noticed there is one major advantage over WP7 on this ROM: the Sound output is far superior to the Sound of WP7. I just fitted my car with a new Amp, new Bass-box and Speakers. Testing that setup with Android-Players is much more satisfying than with that bad Zune-Sound.
[HD2 Android NAND Development] jasroop:
fileswap doesnt work..it shows invalid id..
[HD2 Android NAND Development] brush2:
What means fileswap?

Hi mate,

what do you mean exactly with "fileswap"?

Sharing files via Bluetooth?

Please be more precise.

Greetings, brush2
[HD2 Android NAND Development] sandymac:
What he means, Stephan, is that the site fileswap.com has problems so can't download.... ;)
[HD2 Android NAND Development] brush2:
stupid

Hi Sandy,

omg, where are the next bushes, so i can hide myself :o

Yours, Stephan
[HD2 Android NAND Development] prolexus:
LOL !
[HD2 Android NAND Development] typongtv:
I like 3.7 very much....battery performance is great and the Rom is stable so far .... great build Team.
[HD2 Android NAND Development] GtaSpider:
nothing much to say. i allways used HTC Sense Roms, but one day i decided to switch to miui because of performance (complelty lag-free, Sense ROMS (3.0+) allways had a little lag). Yesterday i decided to switch back to Sense and used this rom. WOW. Its very fast and stable (no problems so far), complelty lagfree and beautyfull - thanks a lot TBD!

greetz,

Spider
[HD2 Android NAND Development] alex.odell.2011:
I have an issue with using the stock wired head set, I am usable to make a call the other person cannot hear me?!?
[HD2 Android NAND Development] bernardstef:
Hi everyone,

Thanks Dansta for this 3.7 rom ! Right now, I used to have 50% of battery left, and my phone have 75% now, whith 3g always on... Amazing ! and it's really fast too !

Well, I don't know if someone noticed that, but I have a wifi issue, it seems that channels 12 and 13 are locked. Not a serious problem, I can change channels, but maybe it would be easy to fix, by modifiying a file ?

Thanks again everyone for this amazing rom, and sorry about my spelling :o
[HD2 Android NAND Development] SagaPer:
The stock wired headset works on my phone.
[HD2 Android NAND Development] mentalityx:
To update my ROM can I just go into 4EXT wipe cache, dalvik and battery info, then flash 3.7 or do I need to do the whole wipe and redo my partition?? Thanks
[HD2 Android NAND Development] Sneakyghost:
You can try but the Setup will wipe System and Data anyhow, to avoid that you'd have to edit the updater-script i think. Ask Dunc001 about it or Dan. They understand such advanced techniques. :D

You will still lose everything as far as i know. And an update is not recommended either. Some have tried that already but i'd suggest to refrain from doing that.

Of course, you are a free human being and can do whatever you like ;)
[HD2 Android NAND Development] mentalityx:
Thanks

That sucks. Was hoping to make this easier. Took me a month to figure out how to do the partition and feel comfortable doing it. Now I cant remember how to do it.:D
[HD2 Android NAND Development] Sneakyghost:
It took me long to learn too some time a ago. Just see it as an exercise- you'll appreciate the new chance to flash :D

Gesendet von meinem HTC Sensation XL with Beats Audio X315e mit Tapatalk
[HD2 Android NAND Development] mentalityx:
I luv this ROM already. I have v3.6. It's quick, and very stable. The only thing that doesn't work is wifi tether. Maybe when I have a few hours I'll update my phone. Probably I might wait for a few updates and do it. Luv updating though.
[HD2 Android NAND Development] brush2:
update

Hi mentalityx,

i tried this 3-4 days before.

I modified the updater script, removed for example certain format command lines and some more stuff.

After flashing of course my "user apps" were gone but all settings like launcher icons there.

But it didn't behave like a clean flash from scratch. Of course there also were some outdated stuff, since nothing was deleted before.

When i flashed v3.7 from scratch, there was a noticable difference in comparsion to the update mothod.

So if you ask me, i would suggest to do it from scratch.

Regards, Stephan
[HD2 Android NAND Development] sandymac:
If I understand you correctly, your question was if you could avoid having to redo your partition every time you reflash a ROM. Assuming that the partition is the correct size for 3.7 and it hasn't changed for some time then the answer is that you don't have to do this. Although I personally would suggest that you re-partition to 7/147/7 to gain as much free memory as possible.

For clarity, the following is what I do when re-flashing a ROM:

1. Create a backup in CWM of your current ROM (just in case you wish to revert back).

2. Backup all apps and data using Titanium Backup

3. Boot into CWM and select "wipe data/factory reset". This will effectively wipe your cache and sd-ext (Dan's install will also wipe and reformat the sd-ext). No need to wipe dalvik cache as it resides on the sd-ext and will automatically be wiped (unless, of course, you have used DalvikMover to place it on the NAND - in this case, you will have to delete dalvik cache via CWM).

4. Install the ROM

5. Once the installation is complete, you can then recover your apps and data via Titanium

I know a lot of people swear by using Task29 and then re-creating the partition but quite honestly this is generally never needed (I have been flashing ROMs for years and never had to do this).

Hope the above helps. :D