I'm curious what is the purpose of preload partition in our devices if we installed CyanogenMod ROM?
We have plenty space on preload, because CM doesn't use any preload partition. Can we repartition it and combine it with system partition? Or why don't we make symlink of our system/app on cyanogenmod to preload partition? isn't it linkable??
If there a devs who would volunteer to make an aosp ROM with using the preload partition, I think we could save lot of space on our system partition.
I'm to lazy to make all of the symlink of CM system/apps to preload. Make me lazier because I don't know is CM system/app linkable (though theoritically its linkable).
it is good to use preload as swap partition
Related
Perhaps I don't understand the purpose of sd-ext/4ext/a2sd etc [I'm sure this is the case!]
I'm running the Aurora v3 rom - basically a sense2.1 with an ext partition. I cannot understand why I've 128mb free in /data after installing pretty much all my apps yet I'm getting insufficient storage errors; I can't install anything despite having a lot of /data free- it seems if my sd-ext if nearly full I can't use my /data?
1. The rom's files flash to /system, and a few to /data. As it's large, we partition the sd card with a 4ext part of say 342mb for overspill of the system/data files.
2. If we change the hboot (to cm7) such that the /system is smaller - overflowing into sd-ext - we get a larger /data partition for apps on the internal memory. (I've done this for for Oxygen/Redux roms and had over 340mb /data with no sd-ext.) Thus alpharev say's we'd get 287mb /data.
3. This rom installs apps to /sd-ext, and/or /data[?]; in Android's App usage I'm reporting 152mb used, 135mb free (the 287mb /data?); and 128mb free storage.
4. 4ext recovery reports 1.7mb free of 342mb for sd-ext - it's full. Which makes sense if apps install to /sd-ext, but why not fill the internal /data first? adb shell df -h gives:
Code:
Filesystem Size Used Available Use% Mounted on
/dev/block/mtdblock4 5.0M 796.0K 4.2M 16% /cache
/dev/block/mmcblk0p1 7.1G 4.5G 2.6G 63% /sdcard
/dev/block/mtdblock5 287.6M 159.3M 128.3M 55% /data
/dev/block/mmcblk0p2 331.3M 329.6M 1.7M 99% /sd-ext
/dev/block/mtdblock3 145.0M 122.8M 22.2M 85% /system
5. To me this means /data has 128mb free for apps; sd-ext is full with system files and apps - seeming to me that apps take space up on both /data and /sd-ext, duplicating space usage. Obviously I'm wrong on this but that's how I see my space disappearing lol Yet I cannot install any apps as I've insufficient storage.
6. Clearly I'm misunderstanding things after installing just 150mb apps and thinking I'd have 287mb of apps /data, not just /sd-ext: why shrink hboot's /system to make a large /data if the apps go to sd-ext?
7. I've not moved dalvik cache to sd as I thought I'd not need to given the seemingly large /data, and it's free amount. Clearly I can do so but why isn't my /data space available?
Sorry for long post and sounding dumb, I'm really trying not to be!
These Roms use sdext for both Rom and part of the apps and possibly dalvik too. Traditionally it would just be apps and maybe dalvik.
With these bigger roms, you need bigger ext to get the same. Yes when ext is full, you can't install anything. Maybe you need a bigger ext partition
Sent from my HTC Desire using XDA App
Thanks for the reply.
That's what I thought - I just cannot understand why I cannot use the free /data though; what's the point of changing to the CM7 hboot when your /data is limited to that of the sd-ext? Isn't it doubling up on storage use by apps, placing them in sd-ext and /data, and when one is full you can't utilise the other?
Sorry for sounding stupid, it just makes no sense to me.
btw I checked out your dGB, looks great. I do love miinimalist roms but also prize my Sense-720p'd camera!
No its not doubling up. The point is that /data/app and /data/dalvik-cache are symlinked to /sd-ext/app and /sd-ext/dalvik-cache.
However, /data/data where the libs, preferences and databases are, remain on /data/data
So when you install an .apk, it installs the app to /sd-ext/app, the dalvik is created on /sd-ext/dalvik-cache and the libs & db's etc will install to /data/data
If sd-ext is full, there is no where for the apk to go.
Thanks for clearing that up for me, I feel kinda stupid - I just couldn't get my head around it: why the nand wasn't being used for apk placement but I see they are split up and components spread over the combined sd-ext and /data. Thanks!
No probs. Not seen you on AF for a while?
OT
Android Forum? = xda? I've been offline a lot recently as this Indian Summer has made for some prime ultrarunning weather, but also takes a ton of time (by definition) although I've been rocking Redux/Aurora roms recently. Just been perusing the Desire forum today and there's been a ton of awesome rom progress since my last visit. I remember your help and work on Redux/thread/pm, great stuff. Still a beginner but it's very interesting learning this stuff, just also takes a lot of time for a non programmer!
Of potential note, 'found' a bug in gnu parted trying to partition out a 512mb 4ext sd-ext via 4EXTRecovery (madmaxx82 located it, I merely experienced it!) Always feels good to in a tiny way contribute
like the title says, I want an EXT4 partition from my system, wich is needed to install mods.
im currently running cyanogenmod 7.2 rc1 rooted, clockworkmod installed.
to install the script, I need an EXT4 system partition. I know how to do this on my SD card, but how to do this on your system?
thanks
You find the tutorial in this thread:
http://forum.xda-developers.com/showthread.php?t=1397120
But you need a card reader, you can't format to ext4 with usb cable.
LegoGabi: he's talking about the internal memory.
IIRC the CM7 install script did the formatting for you.
Starting from RFS partitions, either:
-Install a ROM with CWM that includes the reformatting utilities in its zip along with the required commands in the script.
-Use an appropriate ext4 CWM recovery and use the format functions in there.
-You could also make your own script, there's a few out there for other devices that could be adapted...
Oh, i thought he wants to make app2sd work.
I think cyanogen are already EXT4, so you don't need to convert it anymore
Cyanogenmods for Gio are in EXT4.
It formats internal partitions during installation.
Sent from my GT-S5660
Is this possible with the HOX.. given the size of the system partition and the free space available with some roms, could help to free up.space on the internal storage (data) partition.
Is there a script available ?
Titanium Backup can do something like this if you're rooted.
That only does system dalvik, integrates into Rom, recreating odex files..
I'm talking about creating a script so all dalvik is stored on a system partition.
Symlnked or hard linked,..
ie rather that data/dalvik-cache
Have it as system/dalvik-cache
I had a script for my DHD that moved the dalvik to the cache partition, I suggested the system partition with the HOX because of its has so much free space that would be more than adequate to store it..
I might have a look at this script later tonight if I still have it, and see if I can modify it, to work on the HOX for the system partition..
Figured it out..
I have added a patch to the Sense version of the ncx-217_v4_1 Kernel that stores the Dalvik Cache on the System Partition, therefore freeing up some space on the internal storage..
The System Partition is set as Rewriteable on boot to allow this to work..
I know some people say for security reasons System Partition should be left as Read Only.. But then my argument against that is why go to the trouble to root the device in the first place then. ?
Before installing this makes sure you have wiped the Dalvik Cache in recovery..
to install..
Code:
fastboot flash boot ncx_217_v4_1_SENSE_D2S.img
fastboot erase cache
The modules for this kernel don't require to be re-flashed if you have done prior to this already... But I did anyway just to be on the safe side..
Bare in mind if you flash any other kernel after this.. your Dalvik cache will go back to the stock setting, so if you do not have enough space on your Data partition you could run into problems..
To get around this you could always unpack the new kernel, add the patch to the 'init.rc' file then re pack..
For information on how to unpack and repack Boot.img files refer to this thread HERE
For information on how to apply the patch, read the article HERE
Hi
Im new on XDA and I have problem
I have war with HTC about updating Desire Z to android ICS or JB
HTC said the cant update 2.3.3 to 4.0 because you will lost your data
So I have idea how to protect data while istalling update to new android, but Im N00b and cant write program that will protect /data from wipe.
Possibilities:
1 Copy /data partition to sdcard as ./data
Then format /data /system /boot /cache /dalvik-cache etc
Copy system files to /system and /data
Restore /data from sdcard
Add /data , /system files
2 Dump /data to data.img/data.zip to your sdcard
Then format /data /system /boot /cache /dalvik-cache etc
Copy system files to /system and /data
Restore /data from sdcard
Add /data , /system files
3 Format /system , dump /data to .img or .zip , copy to ./system
Then format all partitions (EXCEPT /system)
Restore /data from /system/data.img
Add /data files from new ROM
Format /system
Add /system files
Im a programming N00b, so can You tell me:
1. Is it possible?
2. Can You write this script for any ICS Sense 4 (or 5) ROM? (HTC Desire Z)
Sorry for my English. Im a Polack from Poland
I installed Flinny's Andromadus CM10.1 over my previous CM7 installation I had been using for years, it worked perfectly fine with no data loss really. Quite a few of the settings transferred over surprisingly. HTC isn't interested in updating 3 year old devices let alone your carrier, your warranties are up and you own the phone by now. You're on your own and it's now the community's job to support it which is slowly petering out.
Go root and flash
Hi,
I switched very soon to Custom ROMs and had a long list of ROMs on my DZ from the Virtuous ROMs to Andromadus and slimBean. I'm now back to Andromadus Mimicry which is a Android 4.0.4 ROM (I tried Slimbean but it has no car mode, go for it when this doesn't bother you, it's 4.2).
Please keep in mind that the DZ is a rather old device and slow compared to the actual ones. HTC wants its Sense on Android which significantly slows the DZ down. So I went for more custom ROMs and have come Sense feeling eith the Apex Launcher. The only thing I really miss is the Sense contacts app that aggregates different addresses of a user (Exchange/Xing/LinkedIn/Facebook/Twitter) into one single contact. I didn't find a replacement for that.
Re. data: Which unique data do you have on the phone? Most of my data sits on the SD card and that is not affected when you flash a new ROM. All the calendar/contact/mail data can be re-synced from Google or Exchange or whatever you use. Use Titanium Backup and make Backups with Clockworkmod and you're perfectly fine. I tried out a ROM last evening and was back to my old ROM and up again in a hour. A Nandroid backup keeps the complete state of the phone so it's easy to roll back.
Apart from this (and some waiting moments here and there) a DZ with a Custom ROM is absolutely useable. I'm a 48 year old freelancer who uses the phone for work so I need a reliable phone and a keyboard for Emailing - and I've got that now.
Have fun and use all the Howtos to root and flash your phone
Cheers, Ralf
FotelPL said:
Hi
Im new on XDA and I have problem
I have war with HTC about updating Desire Z to android ICS or JB
HTC said the cant update 2.3.3 to 4.0 because you will lost your data
So I have idea how to protect data while istalling update to new android, but Im N00b and cant write program that will protect /data from wipe.
Possibilities:
1 Copy /data partition to sdcard as ./data
Then format /data /system /boot /cache /dalvik-cache etc
Copy system files to /system and /data
Restore /data from sdcard
Add /data , /system files
2 Dump /data to data.img/data.zip to your sdcard
Then format /data /system /boot /cache /dalvik-cache etc
Copy system files to /system and /data
Restore /data from sdcard
Add /data , /system files
3 Format /system , dump /data to .img or .zip , copy to ./system
Then format all partitions (EXCEPT /system)
Restore /data from /system/data.img
Add /data files from new ROM
Format /system
Add /system files
Im a programming N00b, so can You tell me:
1. Is it possible?
2. Can You write this script for any ICS Sense 4 (or 5) ROM? (HTC Desire Z)
Sorry for my English. Im a Polack from Poland
Click to expand...
Click to collapse
What kind of data is it that you really want to save?
Contacts, Call Logs and SMS can be easily saved by apps available on the Play Store. Super Backup, SMS Backup + for example. Your contacts get synced to Gmail so you don't really need to save those.
If you are worried about application data, get an app like Titanium Backup Pro, root your phone and back the whole lot up. All the app settings and data gets backed up to your SD card.
Do a Nandroid backup in any case. You can restore stuff from that too. Wipe, flash new ROM and restore everything from Titanium one by one. Is there anything else specifically that you don't want to lose?
War with HTC
Yeah, I know
By "Data" I mean whole /data partition (contacts, apps, appdata etc.)
My friends have root on their DZ's, but they dont want to backup everything before installation of new ROM, and install everything again on new ROM (ex. Migration from GB to ICS/JB)
I think its really annoying
FotelPL said:
Hi
Im new on XDA and I have problem
I have war with HTC about updating Desire Z to android ICS or JB
HTC said the cant update 2.3.3 to 4.0 because you will lost your data
So I have idea how to protect data while istalling update to new android, but Im N00b and cant write program that will protect /data from wipe.
Possibilities:
1 Copy /data partition to sdcard as ./data
Then format /data /system /boot /cache /dalvik-cache etc
Copy system files to /system and /data
Restore /data from sdcard
Add /data , /system files
2 Dump /data to data.img/data.zip to your sdcard
Then format /data /system /boot /cache /dalvik-cache etc
Copy system files to /system and /data
Restore /data from sdcard
Add /data , /system files
3 Format /system , dump /data to .img or .zip , copy to ./system
Then format all partitions (EXCEPT /system)
Restore /data from /system/data.img
Add /data files from new ROM
Format /system
Add /system files
Im a programming N00b, so can You tell me:
1. Is it possible?
2. Can You write this script for any ICS Sense 4 (or 5) ROM? (HTC Desire Z)
Sorry for my English. Im a Polack from Poland
Click to expand...
Click to collapse
You have no choice but to loose data such as Games etc... BUT you can backup your contacts, appoitmnets (Calendar) and messages by using
SMS Backup+ for your messages and call logs and even MMS
Sync your phone with google to backup contacts and calendar remonders (I know you know how to do that )
War with HTC
I know how to do that, but AppData backup dont exist, sms too but contacts are incolmpete (In Google backup, of course)
FotelPL said:
I know how to do that, but AppData backup dont exist, sms too but contacts are incolmpete (In Google backup, of course)
Click to expand...
Click to collapse
There are many ways to back up app data, many ways to back up contacts, really I can't think of what you can't back up completely
Google completely backs up contacts so long as its synced to gmail
And to answer the op this is a standard song and dance that OEMs give when they don't want to continue developing for an old device, there are many ways they could solve the app loss issue, even if they didn't they could but a build on their website you have to download as an RUU with disclaimers and not an ota. This way they could keep both groups of users happy
Unfortunately they don't find it t be in their best interest supporting old devices, one of many reasons xda and other sites exist
Sent from my Nexus 4 using Tapatalk 2
I wanted to install p. vs z 2 but it has 168 MB. And our Desire 151MB system partitionn :crying:
Of cause i have an ext partition. There are 754 free Mb of 1,41 GB. (quick system info)
But my intern memory just have 33,44MB of 151 free.
So on the ext i could install it 4 times but the store first download to intern. Is there a way to install? Maybe if someone uploads the apk and i flash it in the recovery directly to ext4?
An other question. When i startet my phone there where just 5,6MB free. When moves the a2sd script things to the partition and when moves it it back?
HandyBesitzer said:
I wanted to install p. vs z 2 but it has 168 MB. And our Desire 151MB system partitionn :crying:
Of cause i have an ext partition. There are 754 free Mb of 1,41 GB. (quick system info)
But my intern memory just have 33,44MB of 151 free.
Click to expand...
Click to collapse
Your /data partition is 151MB, not your /system partition. Your /system partition is 250MB as you are on stock hboot.
So on the ext i could install it 4 times but the store first download to intern. Is there a way to install? Maybe if someone uploads the apk and i flash it in the recovery directly to ext4?
Click to expand...
Click to collapse
When installing apps, as far as I know it doesn't actually install it to internal (/data), and then move it to ext4. It should install it directly to ext4.
However, depending on the ROM, it needs to see the available space on the internal. The apk is then tricked to your ext4 partition.
One way to install it which might work (not tried it)
- Find and download the apk
- Copy and paste it to your /sd-ext partition using a file browser
- Change file permissions to match your other apps
- Reboot
An other question. When i startet my phone there where just 5,6MB free. When moves the a2sd script things to the partition and when moves it it back?
Click to expand...
Click to collapse
What ROM are you using, and are you using the built in A2SD script or something else? Any A2SD script should move apps (and maybe dalvik cache) automatically to your ext4 partition. I does not move it to internal and back to ext4.
It looks like your memory usage is not very efficient. You may benefit from changing hboot if your ROM /system size is a lot smaller than 250MB. Your dalvik cache might also be on internal, when you could move it to sd-ext where there is plenty of free space.
eddiehk6 said:
Your /data partition is 151MB, not your /system partition. Your /system partition is 250MB as you are on stock hboot.
When installing apps, as far as I know it doesn't actually install it to internal (/data), and then move it to ext4. It should install it directly to ext4.
However, depending on the ROM, it needs to see the available space on the internal. The apk is then tricked to your ext4 partition.
One way to install it which might work (not tried it)
- Find and download the apk
- Copy and paste it to your /sd-ext partition using a file browser
- Change file permissions to match your other apps
- Reboot
What ROM are you using, and are you using the built in A2SD script or something else? Any A2SD script should move apps (and maybe dalvik cache) automatically to your ext4 partition. I does not move it to internal and back to ext4.
It looks like your memory usage is not very efficient. You may benefit from changing hboot if your ROM /system size is a lot smaller than 250MB. Your dalvik cache might also be on internal, when you could move it to sd-ext where there is plenty of free space.
Click to expand...
Click to collapse
i'm using RSK Sattelite ROM.
but if the apps are installed to ext how comes that the data sometimes has about 10MB free and after i installed an update there are 15MB free??
HandyBesitzer said:
i'm using RSK Sattelite ROM.
but if the apps are installed to ext how comes that the data sometimes has about 10MB free and after i installed an update there are 15MB free??
Click to expand...
Click to collapse
It depends a bit on how your script works. Reading the ROM OP it has some sort of "a2sdx" built it, I'm not familiar with exactly how it works. You need to understand this script first before wondering about anything internal memory related.
Think about it logically though...the script is meant to move things to the ext. That's its purpose. Generally they move at least the whole app apk to ext.
So
- If you have an app installed, it should already be on the ext.
- When you update the app, it will overwrite the existing apk on ext.
- There are other things along with an app such as app libs, app data and dalvik cache, which may be on internal or ext depending on the script. These can change on app updates as well.
Have a look at an app like 'DiskUsage', use it to browse your /data partition. See what's using the space. Often you may have some stray /system apps on /data, and you need to move them back to /system.