Hi guys,
sorry because this has probably been answered somewhere but I couldn't find it ....
So here it goes: I just installed Modaco's ROM and it works perfectly. Now I would like my apps to install directly on the SD card.
What I understand is that I need to create a EXT3 partition but I don't know what the hell that means, nor how to do it.
I just put my SD card in the hero, didn't format anything ....
Dould you give a step by step guide ? On how to create that EXT3 partition, how to use A2SD afterwards ? Also, what to do with the currently installed applications ?
Thanks
Geeum
Dould you give a step by step guide ?
Click to expand...
Click to collapse
http://androidandme.com/2009/08/news/how-to-manually-partition-your-sd-card-for-android-apps2sd/
how to use A2SD afterwards?
Click to expand...
Click to collapse
Just use MoDaCo's custom ROMs. (It will do it automatically)
can app2sd work with official ROMs not rooted?
Hi guys I finally partitioned my sdcard to have an ext3 partition.
I thought A2SD was automatic but apparently applications don't go to the sdcard: my phone memory has changed after I installed an app ...
Here is what I get if I type the 'print' command on parted
Code:
(parted) print
print
print
Model: SD 00000 (sd/mmc)
Disk /dev/block/mmcblk0: 8166MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 512B 7110MB 7110MB primary fat32 lba
2 7110MB 8134MB 1024MB primary ext3
3 8134MB 8166MB 32.3MB primary linux-swap(v1)
So I DO have ext3. Then I found this post that explains how to check if A2SD is working:
Thanks! Here is my way to check if a2sd is working:
Check if the ext3 partition exists (please see androidandme.com for details):
Code:
# mount | grep mmcblk0p2
mount | grep mmcblk0p2
/dev/block/mmcblk0p2 on /system/sd type ext3 (rw,noatime,nodiratime,errors=continue,data=ordered)
Compare available/used space on mmcblk0p2:
Code:
adb shell
# df
df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 98520 0 98520 0% /dev
tmpfs 4096 0 4096 0% /sqlite_stmt_journals
/dev/block/mtdblock3 174080 153460 20620 88% /system
/dev/block/mtdblock5 169728 27240 142488 16% /data
/dev/block/mtdblock4 133120 1160 131960 1% /cache
/dev/block/mmcblk0p2 468331 11767 431579 3% /system/sd
Now install an app from the market (as suggested by fleming222) and again run "df". Compare the available (or used) space on /dev/block/mmcblk0p2 with the first "df".
Click to expand...
Click to collapse
This is what I get (I can see on the first line that my ext3 is not listed ... weird)
Code:
/ # mount | grep mmcblk0p2
mount | grep mmcblk0p2
/ # df
df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 98508 0 98508 0% /dev
/dev/block/mtdblock4 133120 1496 131624 1% /cache
HELP !
By the way I'm running MODACO's 2.6 custom ROM ...
Geeum said:
By the way I'm running MODACO's 2.6 custom ROM ...
Click to expand...
Click to collapse
The best way to do it if your not too good with the adb commands is to install the AMON recovery image for Hero.
It has all the options to create the correct sd card partitions from the recovery mode, then just install your custom rom and everything should work.
You will need to format your sd card so you may want to create a backup of it. And I would suggest that you wipe the phone clean as well. Once you install the modaco rom it automatically moves all of your apps to the sd card.
The link for the recovery image is here:
http://forum.xda-developers.com/showthread.php?t=561124
You will also need Instant Root (http://neilandtheresa.co.uk/Android/), which you should install first, it is an .apk file so you will need a file manager for your phone. It should pop up with a notification "instant root was successfully" or along those lines. (If you have a problem installing Instant Root make sure Settings>Applications>Unknown Sources is checked)
You should then place the AMON recovery image onto the sdcard making sure it is not put into any folders (root).
Instant root then allows for root access with adb shell using the following 2 commands:
1) adb shell
then
2) su
the icon should change from a $ to #.
Now flash the recovery image with the following command:
flash_image recovery /sdcard/recovery-RA-HERO-v1.2.3.img
That should do it, remove the usb and battery and once you have replaced the battery boot into recovery mode.
I ran the following commands in this order from recvoery mode:
- Wipe data + cache (factory reset)
- Wipe ext partition on SD-card
- Wipe Dalvik-cache on SD-card (NOT on /data !) [email protected] ALWAYS WORK
- Partition SD-card : 500MB Ext2, 32MB Swap, remaining Fat32
- Convert ext2 to ext3
- Installed ROM
Hope this helps
Hi and thanks for your reply. I finally sorted my problem, I was typing the commands from the recovery console, and now my ext3 shows:
Code:
# mount | grep mmcblk0p2
mount | grep mmcblk0p2
/dev/block/mmcblk0p2 on /system/sd type ext3 (rw,noatime,nodiratime,errors=conti
nue,data=ordered)
I checked the space with df, and I can see it changing when installing apps.
However, so does the 'internal memory of the phone' in the settings panel; it keeps getting smaller as I install apps
Why is that ?
really want to do this but i find it all to hard and confusing
Geeum said:
I checked the space with df, and I can see it changing when installing apps.
However, so does the 'internal memory of the phone' in the settings panel; it keeps getting smaller as I install apps
Why is that ?
Click to expand...
Click to collapse
I think this is inevitable as the app uses some part of the phone memory for cache files etc (I am not 100% certain on this, just saw it written in an older post on the same topic).
I do not know if this is a coincidence but for some reason I have tried partitioning manually (the way your doing it) in the past and have recently used the AMON recovery image for partitioning instead. I notice that the recovery image tends to use less of the internal storage for each installed app, I don't know why but you could try it out yourself.
guys, i am using modaco's 2.6 rom. so if i just create partitions this custom rom will automatically install newly installed apps to the sd card. right?
but what if i already got many apps installed? will those be deleted while creating partitions?
is there any way so that i can backup the whole application folder and restore after creating partitions?
cheers
apparently if you do ext2 + swap + fat32, you can't do a Nandroid backup (it keeps giving errors). anyone got similar issues?
kazuni said:
apparently if you do ext2 + swap + fat32, you can't do a Nandroid backup (it keeps giving errors). anyone got similar issues?
Click to expand...
Click to collapse
is it so? if so then that wud be a disaster.
Hi!
I was experimenting with the data2ext script made for the Desire in following thread:
http://forum.xda-developers.com/showthread.php?t=859419
Now I managed to get it working with HTC Hero and Flykernel12a and Amon RA-s recovery v1.7.0.1 .
MAKING THIS WORKING IS A RISKY OPERATION! DO NOT START IF YOU DO NOT UNDERSTAND WHAT IS WRITTEN BELOW! I'M NOT RESPONSIBLE IF YOU DAMAGE YOUR PHONE OR YOU LOOSE YOUR DATA!
So here is what I made:
- make backup of your entire SD card, because we are going to repartition it, so all data will be lost on your SD card
- reboot to recovery and MAKE NANDROID BACKUP of your existing configuration!!! Then stay in recovery mode, and copy your NANDROID BACKUP to a safe place on your computer from the SD card!!!!! DURING THE OPERATION WE WILL ERASE THE WHOLE SD CARD!!!
- wipe your cache and dalvik-cache (only this 2, NO factory/data reset!!)
- connect to your phone with "adb shell" (while in recovery!!)
- in the shell execute following commands:
(do this only if you have active app2sd and your app/app-private/dalvik-cache directories are on the SD card EXT partition)
mount /data
rm -rf /data/app
rm - rf /data/app-private
rm - rf /data/dalvik-cache
mkdir /data/app
mkdir /data/app-private
mkdir /data/dalvik-cache
chmod 777 /data/app*
chmod 777 /data/dalvik-cache
chown 1000:1000 /data/app*
chown 1000:1000 /data/dalvik-cache
- now we will copy back the apps on the nand
mount /sd-ext
cp /sd-ext/app/* /data/app
cp /sd-ext/app-private/* /data/app-private
(no need to copy the dalvik-cache content!)
umount /sd-ext
- so now we have all our app on the nand again. next step is to put the 04data2extV4 script into the right place
umount /data
mount /system
exit
(now leaving shell to copy file)
in the command prompt execute:
adb push pathtothescript/04data2extV4 /system/etc/init.d/
adb shell
(back to shell again)
chmod 755 /system/etc/init.d/04data2extV4
chown 0:2000 /system/etc/init.d/04data2extV4
rm /system/etc/init.d/05mountsd
(remove script which mounts SD card differently)
rm /system/etc/init.d/10apps2sd
(remove script which makes app2sd)
umount /system
exit
(now leaving shell)
now we have to repartition your SD card to 2 ext and 1 fat partition. For this use the utility1 I uploaded which is modified version of the original utility in /sbin.
in command prompt:
adb push pathtoyourscript/utility1 /sbin/
adb shell
(back to shell)
chmod +x /sbin/utility1
(now execute the utility)
/sbin/utility1
choose 0 from menu: Partition SD 2 EXT 1 FAT (can set sizes)
enter the first EXT partition size (min. 3-400, I use 1300 - values are in MB)
enter second EXT partition size (min. 2-300, I use 300 - values are in MB)
the rest will be configured for the FAT32 file system
On the first EXT partition you will store the whole /data
On the second EXT partition you will store the /data/data in a loop file
Now we are hopefully ready to reboot, the rest will be managed by the 04data2extV4 script, wich creates the ext2 file systems, converts them to ext4, stets file system option such as journaling where needed, etc and copies everything from nand to ext4.
I hope this works for all. I reached Quadrant score for total system score about 455, without data2ext I had about 400. But I have a Class4 SD card. On class6 I'm sure it will be even faster.
Again, it is risky, so take care.
The boot process can be long, because at the first time it will copy the whole /data directory to the first EXT partition, the data/data directory on the 2nd partition, and will recreate the whole dalvik-cache (remember we wiped!).
Enjoy
Regards,
byr2
PS: in the RAR file you will find an FSTAB file. I removed the /sd-ext mount option from it. If you have trouble, try to replace the fstab file in /etc to this fstab file or remove the /sd-ext mount option from your fstab
Thank you for this.
Just a few questions. The EXT partitions, are they EXT 2, 3 or 4?
Are you using exactly the same script as ownhere? As in, you use exactly his method, aka the following one:
"I would like to share my Data2EXT script, a collection of data2sd(Thanks to sibere) and the advantages of ext4, you can let the phone run at peak efficiency.
I use EXT4 for whole SD 2nd partition, and create a ext2 loopback device with 1/5 size of 2nd partition.
The files in /data/app,/data/.systemapp it not updated frequently. so store them in EXT4.
In /data/data and /data/app-private, a lot of small files and sqlite database, is updated frequently. so store thenm in EXT2 loopback device.
/data/dalvik-cache is stored in phone memory /mnt/asec/mtddata for distributed IO pressure.
/data/misc, /data/system, /data/property is stored in phone memory /mnt/asec/mtddata for system settings restore(or you will lost your timezone/language settings after reboot).
use this script, I can get quandrant score:2000+, IO:4000+, my phone is smooth and quickly."
Are you running this stable? Reboots? All apps show after reboots?
Hi!
The two EXT partition is EXT4 partition. The script I provided is based on ownhere's script, wich is modified only in a few places.
For example on hero I do not have a /system/xbin/mkfs.ext4 like he had, but only a mkfs.ext2, so I have to create the EXT4 partition on a different way. Also the loopback device is set up in a different way than in the original script.
But what you quoted remains so, which means I did not modified any location of storage files, nor did modified filesystem parameters. First EXT4 ha no journaling ,second EXT4 has journaling, ext4 loop device has no journaling.
You can diff the two scripts to see the difference, but an example here:
Original part:
/system/xbin/mkfs.ext4 -b 4096 -m 0 -F -L userdata /dev/block/mmcblk0p2
/system/bin/tune2fs -o journal_data_writeback /dev/block/mmcblk0p2
/system/bin/e2fsck /dev/block/mmcblk0p2
/system/bin/tune2fs -O ^has_journal /dev/block/mmcblk0p2
Modified part:
/system/xbin/mkfs.ext2 -b 4096 -m 0 -F -L extdata /dev/block/mmcblk0p2
/system/bin/e2fsck -y -v -f /dev/block/mmcblk0p2
/system/bin/tune2fs -O extents,uninit_bg,dir_index /dev/block/mmcblk0p2
/system/bin/e2fsck -fpDC0 /dev/block/mmcblk0p2
/system/bin/tune2fs -o journal_data_writeback /dev/block/mmcblk0p2
/system/bin/e2fsck /dev/block/mmcblk0p2
/system/bin/tune2fs -O ^has_journal /dev/block/mmcblk0p2
As you can see I create an ext2 partition, check it, and with tune2fs I convert it to EXT4, check it again, and set the same parameters ownhere has set.
for loopback device I use:
$BUSYBOX losetup /dev/block/loop1 /mnt/asec/extdata/ext4
$BUSYBOX mount -t ext4 -o loop,sync,commit=3,barrier=1,nouser_xattr,errors=continue,noatime,nodiratime,nosuid,nodev /dev/block/loop1 /mnt/asec/tmpdata
the losetup is needed, because for some reason it won't mount as loop. But this way it is working.
Other parts of the script are untouched.
Regards,
byr2
"Are you running this stable? Reboots? All apps show after reboots?"
Till now everything runs OK, no reboot, all widgets, apps, settings were preserved. After reboot also everything OK. Made some phone calls, no problems so far.
Just with Class4 SD card the speed gain is not as huge as expected. The IO performance is slightly better, but not too much. I've read posts on CDMA Hero forum, where they managed to get quadrant score over 700, but I'm sure not with a Class4 SD card
But the funniest thing in settings is: Available internal phone storage: 1,17Gb
Excuse me for the noob question, but what this process basically does is make the entire phone run off of an ext4 partition on the SD card?
No, not the entry phone, just the /data directory is moved to ext4 partition (wich is accessed frequently by the OS, and where applications and application related data are stored). The kernel, firmware, etc. remains on the NAND.
I wonder what one does when flashing a new ROM =/ You have to go through this procedure every single time? What does AmonRA do when you Wipe Data/Factory Reset?
So essentially the differentiations are due to the fact that we lack a /system/xbin/mkfs.ext4 (since we only have an ext2) and you turn the first EXT4 partition into a non journaling one to fill the lack of that, if i understand correctly.
If you flash a new rom, then all this is gone, since if will overwrite the /system/etc/init.d where our data2ext script is located. So you're right, you have to do this every time you flash a new ROM. A solution would be to pack this script into the ROMs, so it would work out of the box without this hack mentioned in the first post.
The data/factory reset wont work I think, because it deletes from the nand, but since our data/settings are not on the nand but the SD, it will have no effect.
the first ext4 partition is non journaling because ownhere write the script so. You can read in his post why he choosed to do so.
The first EXT pratition where /data is stored is a EXT4 part without journaling
The second EXT partition where the loop file is stored is an EXT4 part with journaling
and the LOOP file which contains an EXT4 partition without journaling
from ownhere's post:
"EDIT:2010/12/12 update V4 script:
/data/:ext4, disable journaling
/data/data:ext4 loopfile on ext4 device, enable journaling on ext4 device, disable journaling on ext4 loopfile, for fast and stable sqlite3 access.
really smooth this time. please trying..."
This is the setup here also.
byr2
I see, the script is essentially the same, with your own critical changes to fit the Hero.
Now what i am trying to understand is what happens when you want to flash a new ROM.
Say you place the 04data2extV4 script in the new ROM's /system/etc/init.d and remove the other two scripts if they exit (05mountsd and 10apps2sd). Does this mean the partitions and this whole process won't have to be repeated?
Also when installing a new rom it is recommended you wipe data and system, if AmonRA doesn't wipe, what do we do?
Well, I've not tested to install a new rom, but let think:
- the partitions are preserved on your SD, so repartitioning is not needed.
- but as you mention all data/settings are currently on your SD, so a wipe does nothing with it, and if you simply put the 04data2extV4 script back to init.d I think it will mess things just up... but if you just delete everything off the two EXT partitions I think it will be fine
That's the only limitation i have so far as to not attempting this.
I wonder if i can mod the AmonRA Recovery to delete the content of those 2 partitions instead =/
I'm going to have a look.
Nice work!
By the way, I was thinking. Why not just make an ext partition, add a line for it in fstab and set the mountpoint for it to be /data. What would happen if I tried this?
Byr2.... just wanted to say this is first thing i read today and without coffee all I heard was
Blah blah blah dangerous blah blah blah faster blah blah risk blah blah even faster
Lmao
Once I get my head working it should prove interesting though
Thanks for this experiment
Sent from my HTC Hero using Tapatalk
ok, sitting down at pc now, drinking espresso...
this is starting to sink in
Instant benefit is huge storage space which, coupled with the method used, ought to have a general performance improvement over previous ext-based apps2sd, right? if so then removing ext-based apps2sd and using this script concept instead seems like a good plan if, for example, every rom builder switched to this concept and removed old apps2sd stuff simultaneously. Does that sound right or wrong?
if you have a fast sd card then the speed benefit should be very good, better than using ext-based "apps2sd" since it's the actual data partition on the ext card.
and I too would like to know the answer to the brief question someone already asked - what about just setting a mount point to data on the sd card and doing it that way in simple linux fashion? I'm not bothering to think this through - coffee's still kicking in - I'll leave the intelligence to you folks who are already awake.
IMHO this idea of yours is quite brilliant as a goal (well ok, it's not your idea, but you did it first on the gsm hero . The thing that slows my phone the most is reads and writes to phone memory and to my stock sd card. I can upgrade the sd card but the phone memory writes are still slow. This would improve the speed of the largest file writes when managing my apps and installing from the market which we all know brings our phones to a standstill briefly during installs and so on.
How's the performance when installing apps? does your phone still crawl for a bit at those crucial moments or is it all somewhat less of a dramatic slowdown now?
Hi All!
Well, If you do not change the ROMs frequently, it should not be a problem that ROM developers do not include this script. However till now only one ROM developers have taken care about this opportunity, I think it was Cronos. They have a modified ROM wich supports this kind of functionality.
The speed gain over app2sd comes from storing the whole data partition on a faster SD card than the internal NAND. As my tests show a class4 SD card is slightly faster than the internal NAND (not much, say about 5-10%). A class6 SD card could be much more faster. All application access the data partition to read and write settings/data. Even the Frimware stores things there, so if you have a fast SD card, overall system performance could be great.
Not to mention about stored data space. With app2sd you only store the downloaded apk-s on the EXT. With data2ext you have extra space for the application data/settings/cache wich size is determined by you and your SD card size ! (See screenshot!)
A simple fstab modification could work, however the script does do a lot of things beside copying everything to EXT. It also sets up some symlinks during every boot, so a part of the script is needed always. Also there is 2 EXT partitions, and the /data/data is stored on a 2nd EXT partition in an EXT4 loop file image So it's not that easy to simply mount it via fstab.
byr2
dkelley said:
Byr2.... just wanted to say this is first thing i read today and without coffee all I heard was
Blah blah blah dangerous blah blah blah faster blah blah risk blah blah even faster
Lmao
Click to expand...
Click to collapse
Hahaha. I've read this several times now and still all I get is what you wrote above.
I got this after all
Code:
$mount
rootfs on / type rootfs (ro)
tmpfs on /dev type tmpfs (rw,mode=755)
devpts on /dev/pts type devpts (rw,mode=600)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
none on /acct type cgroup (rw,cpuacct)
tmpfs on /mnt/asec type tmpfs (rw,mode=755,gid=1000)
none on /dev/cpuctl type cgroup (rw,cpu)
/dev/block/mtdblock3 on /system type yaffs2 (ro)
/dev/block/mtdblock4 on /cache type yaffs2 (rw,nosuid,nodev,noatime)
/dev/block/mtdblock5 on /mnt/asec/mtddata type yaffs (rw,nosuid,nodev,relatime)
/dev/block/mmcblk0p2 on /data type ext4 (rw,nosuid,nodev,noatime,nodiratime,commit=19,barrier=0,nobh,data=writeback)
/dev/block/mmcblk0p3 on /mnt/asec/extdata type ext4 (rw,nosuid,nodev,noatime,nodiratime,barrier=1,data=ordered)
/dev/block/loop1 on /data/data type ext4 (rw,sync,nosuid,nodev,noatime,nodiratime,commit=3,barrier=1,data=writeback)
/dev/block/vold/179:1 on /mnt/sdcard type vfat (rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/block/vold/179:1 on /mnt/secure/asec type vfat (rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
tmpfs on /mnt/sdcard/.android_secure type tmpfs (ro,size=0k,mode=000)
All correct?
This is mine:
Code:
rootfs on / type rootfs (ro,noatime)
tmpfs on /dev type tmpfs (rw,mode=755)
devpts on /dev/pts type devpts (rw,mode=600)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
none on /acct type cgroup (rw,cpuacct)
tmpfs on /mnt/asec type tmpfs (rw,mode=755,gid=1000)
none on /dev/cpuctl type cgroup (rw,cpu)
/dev/block/mtdblock3 on /system type yaffs2 (ro)
/dev/block/mtdblock4 on /cache type yaffs2 (rw,nosuid,nodev,noatime)
/dev/block/mtdblock5 on /mnt/asec/mtddata type yaffs (rw,nosuid,nodev,relatime)
/dev/block/mmcblk0p2 on /data type ext4 (rw,nosuid,nodev,noatime,nodiratime,commit=19,barrier=0,nobh,data=writeback)
/dev/block/mmcblk0p3 on /mnt/asec/extdata type ext4 (rw,nosuid,nodev,noatime,nodiratime,barrier=1,data=ordered)
/dev/block/loop1 on /data/data type ext4 (rw,sync,nosuid,nodev,noatime,nodiratime,commit=3,barrier=1,data=writeback)
/dev/block/vold/179:1 on /mnt/sdcard type vfat (rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0
020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/block/vold/179:1 on /mnt/secure/asec type vfat (rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_ut
ime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
tmpfs on /mnt/sdcard/.android_secure type tmpfs (ro,size=0k,mode=000)
/dev/block/dm-0 on /mnt/asec/com.qualcomm.qx.neocore-1 type vfat (ro,dirsync,nosuid,nodev,noexec,uid=1000,fmask=0222,dmask=0222,code
page=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
Seems your's almost the same...
The key is this:
Code:
/dev/block/mmcblk0p2 on /data type ext4 (rw,nosuid,nodev,noatime,nodiratime,commit=19,barrier=0,nobh,data=writeback)
/dev/block/mmcblk0p3 on /mnt/asec/extdata type ext4 (rw,nosuid,nodev,noatime,nodiratime,barrier=1,data=ordered)
/dev/block/loop1 on /data/data type ext4 (rw,sync,nosuid,nodev,noatime,nodiratime,commit=3,barrier=1,data=writeback)
How is your phone performing? Was everything OK?
byr2
Everything seems to be ok )
There is no more sticking when new apk installed. Quadrant score around 500.
I have Class 10 sd card (prooflink).
But I have had a little problem - not enough nand space to hold all of my apks, so I've decided to push most of them via adb from my laptop after Hero's reboot.
Quadrant score not so high as I expected, but anyway I'm happy =)
if you push it via ADB after reboot, than it should get to the right place
The quadrant score is affected by 3D and CPU also, but can you feel the "speed" while testing the IO? Does it run fast? How long is the DB read/write, FS read/write?
I'm happy someone else could get this thing working
byr2
Hi Guys,
Im currently running oxygen RC7 on my Htc Desire. ok im a little confused as to how i have such little space. According to wikipedia the Desire has 512mb flash memory. But according to app2sd it has a total of 185.69MB and according to settings it has 148Mb. So which is it? Now im aware that the rom takes up some space now onto the second part of my question.
I also have partitioned my SD card to 512mb with rom manager, but this doesnt explain the random sizes both A2SD and system settings are saying. Also i dont understand what i achieved by partitioning my sd card i didnt see any difference in size on the storage settings am i just looking in the wrong place.
My understanding is that app2sd moves apps to the ext3 partition created by Rom manager and the stock application manager moves apps to the fat partition. My reasoning for this is that some apps can be moved to SD by the stock application manager and the same apps cant be moved by app 2 SD
Can anyone explain this to me?
Thanks
I don't know much about Apps2SD, A2SD or what ever you call it but I will give it a go anyway and hope that I help you out a little. I don't use it as I will explain why.
The 512MB size is the total size of the internal memory. That memory is split up into 3 main partitions. /system, /data and /cache. Other things like boot, recovery and so on goes somewhere else. The rom goes onto the /system partition, the apps go to /data partition and /cache is for temporary storage like when your downloading apps from the market.
Try not to do it with Rom Manager. It is a little buggy and doesn't work well. You can use something like gparted to format and partition your SD card.
As for A2SD. I understand that you install a script for it to work properly. By default, it will move apps to the ext partition on your SD card. Please note if your using widgets and the app is on the SD card, you won't be able to use the widgets.
Here is a A2SD script by DarkTremmor. Read up on it. Hope this helps.
I prob am wrong about this but this is my understanding of A2SD. Please update me guys if I am wrong or you have better info. I still don't understand A2SD properly. I will however try it out and see how it works.
If you use A2SD (the version with the ext) widgets will work. They only won't work when on the fat partition.
hey thanks for the reply. ok so this helps me understand it a bit better thanks googlejelly. But this still doesnt explain why a2sd has a different total size then the stock application manager?
Even if you say that by default App2sd moves it to ext partition and that is the reason for the different sizes it still doesnt match up as i created a partition of 512mb and got 185.69 which is a bit far off the mark.
Most proper way to know your free memory is Console. Connect phone, type adb shell and:
Code:
# mount
/dev/block/mtdblock3 /system yaffs2 ro,relatime 0 0
/dev/block/mtdblock5 /data yaffs2 rw,nosuid,nodev,relatime 0 0
/dev/block/mtdblock4 /cache yaffs2 rw,nosuid,nodev,relatime 0 0
/dev/block/vold/179:1 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:1 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
/dev/block/dm-0 /mnt/asec/com.rovio.angrybirdsseasons-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/system - read only (s-off rules!) file system for your system files
/data and /cache rw partitions for application and data storage
next is SD-Card mount point
/mnt/secure - is hidden folders on SD-Card for storing data for native a2sd Android. You can see last line - it's Angry birds moved to SD mounted as independent partition. Don't move any apps to SD-card if you have custom a2sd+ script configured.
Code:
# df
Filesystem Size Used Free Blksize
/dev 203M 44K 203M 4096
/mnt/asec 203M 0K 203M 4096
/mnt/obb 203M 0K 203M 4096
/system 140M 126M 13M 4096
/data 272M 56M 215M 4096
/cache 25M 10M 14M 4096
/sd-ext 457M 189M 267M 1024
/mnt/sdcard 3G 2G 859M 4096
/mnt/secure/asec 3G 2G 859M 4096
Now sizes (i have custom partitions size, so your sizes will differ)
/data - where you install all apps.
/sd-ext - a2sd+ storage (on SD-Card)
And to check is a2sd word proper:
Code:
# ls -l data/
lrwxrwxrwx root root 2011-02-22 16:54 app-private -> /sd-ext/app-private
lrwxrwxrwx root root 2011-02-22 16:54 app -> /sd-ext/app
lrwxrwxrwx root root 2011-02-22 16:54 dalvik-cache -> /sd-ext/dalvik-cache
-rw-r--r-- root root 8447 2011-02-22 16:55 dta2sd.log
-rw-r--r-- root root 8447 2011-02-22 16:54 dta2sd.lg1
-rw-r--r-- root root 8576 2011-02-22 16:54 dta2sd.lg2
drwx------ system system 2011-02-22 16:55 backup
-rw-rw-rw- root root 376 2011-02-21 17:30 dtinstall.log
drwx------ system system 2011-02-21 17:32 secure
drwxrwxr-x system system 2011-02-23 15:08 system
drwxr-xr-x root root 2008-08-01 15:00 xbin
drwxr-xr-x root root 2011-02-21 17:32 local
drwxr-xr-x root root 2008-08-01 15:00 jit
drwxr-xr-x root root 2011-02-23 14:05 data
drwx------ root root 2011-02-22 16:54 property
-rw-r--r-- root root 1978 2008-08-01 15:00 changelog.txt
drwxrwx--- root root 2011-02-21 17:32 lost+found
drwxrwx--t system misc 2011-02-23 13:14 misc
drwxr-x--- root log 2011-02-21 17:32 dontpanic
you see "->" is symlink to SD-card. So any app you installed in internal memory of your phone actually goes to SD. But, there is on folder - data, which not moved to card with a2sd. Cause some restrictions or smth like this.
in /data/data/ app store their libraries etc. Now check which soft use storage:
Code:
# cd data/data
# du -shd1
3.0M ./com.adobe.reader
80.0K ./com.mhuang.overclocking
54.5K ./kz.mek.DialerOne
4.0K ./jp.r246.twiccaplugins.twitpic
17.5K ./com.anddoes.fancywidget
9.0K ./org.swiftp
.....
2.5K ./com.rerware.android.MyBackupRoot
15.0K ./ccc71.bmw
45.6M .
So total folder use 45.6MB of internal storage. all other is free for use. There another folders in data, but it not so heavy.
Stock Desire, according to alpharev, has - Bravo Sense: /system:180M /cache:40M /data:217M.
Main goal of using custom a2sd+ is that you install all apps in internal memory as your phone thinks. And all widgets work well. With stock a2sd you can't move apps with widgets to sd-card or it stop working.
crap i tried the app2sd script and it messed up my phone, now i cant install any app from the market it just starts and stops straight away. im after doing a factory reset on my phone and even restored backups.
can anyone help?
Why not to take any of existent rom with working a2sd?
thanks for the relpy (both of them) after doing a wipe via android itself, everything is back to normal now. So is it that all i have to do to get app2sd to transfer my apps to my ext3 partition on my sd is run a script (.zip file) in clockworkrecovery?
the one i tried is what messed everything up, i dont know if it was because some of my apps were on my sd (via the standard application manager) or that the script wasnt designed for the desire/the rom im running.
i have partitioned my rom correctly to ext3 so im nearly there :-(
With a2sd all apps should be installed in internal memory.
Check what show ls -l /data/ in terminal. If there is symlink to SD - everything is Ok!
THIS IS FOR DEVELOPMENT ONLY!!!! THIS IS ONLY A CONCEPt FORGETTING THE 1GB SYSTEM PARTITION.
30-Jan-13 update
Ok so using this method I now have a ported rom from the Samsung Galaxy S3 that has a 680+mb system booting on my G2. If any of you feel like helping me get it up and running PM me or you can download it from here http://sourceforge.net/projects/sgs3forg2/files/FJB4G2-orig-runtime.zip/download and see for yourself...
MAJOR EDIT: SO THE UPLOAD MUST HAVE BEEN CORRUPTED FOR THE EM1.zip. IT IS NON FUNCTIONAL. ALL CREDIT TO THE ONE I WILL PUT UP GOES TO FLINNY. I IN NO WAY DID ANYTHING TO CREATE THIS ROM JUST ALTERED THE MOUNTS TO GET THE 1GB SYSTEM PARTITION. THE FILE IS NAMED f10.zip. it is his 10.1 base.
Ok so I know its been a while but I have something I can not keep away from the community. Anyone want to get a 1GB System and 549MB Data partition??? Yes thats right we can swap the partitions. here is a link to some screen shots and another to, with the permission of nik3r, the modified Elitemod Rom. just go into recovery, format all partitions(sorry you will have to start over in order to swap the partitions, well for now that is), and flash the EM1.zip
http://www.mediafire.com/?ka8yq4hzs6upj
Ok so this all started after my wife got her new phone the samsung galaxy s3. in love with the phone and what it could do but unable to, due to financial constraints and TMobiles unwillingness to give me one for free like they did my wife, I set forth trying to find a way to port its OS to our G2. finally i have found a way, or at least now the space in which to put it. now will begin the porting phase. hence this thread, I bring you this solution to our space issue cause really is 1.3GB for G2 or 1GB for DZ partition for data really needed???
So here is what I did...
1. First I got android sdk all setup
2. Then I downloaded the android kitchen
3. Also downloaded the Elitemod Rom from nik3r's thread and set it up in the android kitchen
4. In the android kitchen I extracted the kernel and ramdisk from the boot.img
5. I editted all the init files in the BOOT-EXTRACTED/boot.img-ramdisk directory and changed the mount section of the init.rc to
# mount mtd partitions
# Mount /system rw first to give the filesystem a chance to save a checkpoint
mount yaffs2 /dev/block/mmcblk0p26 /system
mount yaffs2 /dev/block/mmcblk0p26 /system ro remount
mount yaffs2 /dev/block/mmcblk0p25 /data nosuid nodev
mount yaffs2 [email protected] /cache nosuid nodev
and the init.vision.rc mounts i also swapped
on early-fs
mkdir /system
mkdir /data 0771 system system
mkdir /cache 0770 system cache
mkdir /devlog 0700 root root
mount ext4 /dev/block/mmcblk0p26 /system wait ro barrier=1
setprop ro.crypto.tmpfs_options size=128m,mode=0771,uid=1000,gid=1000
mount ext4 /dev/block/mmcblk0p25 /data wait noatime nosuid nodev barrier=1 noauto_da_alloc
mount ext4 /dev/block/mmcblk0p27 /cache wait noatime nosuid nodev barrier=1
mount ext4 /dev/block/mmcblk0p28 /devlog wait noatime nosuid nodev barrier=1
6. now in order for it to boot right i had to get the files to go to the right place so i editted the updater-script and changed the mount for system to /dev/block/mmcblk0p26 (which as you know is the normal data partition) and the data mount to /dev/block/mmcblk0p25( normally system) now the files are going to places we want and the init files on boot remount the system on 0p26 and data on 0p25 (in reverse from normal) but it boots. so here we go lets get the life put back in this phone now we have the space.
Mad props to nik3r for his rom and permission to use it
UPDATE: For some reason the wifi got broken but to fix there is the MOD_Elitekernel zip found in the link at the top of this post that will fix that. I also put EdKeys wifi calling as well, have it running now on my phone so let me know if you find anything else.
UPDATE 2: I have put a hacked version of S Voice from the galaxy S3 in the link for the G2 *TO BE USED WITH THIS PROJECT ONLY*.
UPDATE 3: there must be some confusion with this. This is not a new rom with some timeframe to get it working. I have a fully opperational rom with no problems with apps or anything right now. This is about a mod that can be adapted to any rom or as brought up gapps which will be uploaded here tomorrow. My point is that any rom should be able to be altered this way.
So this means you're giving us Nature UX in the near future? Good luck :good: also does this open up multi booting possibilities (proper multi booting, not anything like Boot Manager)? 'Cause that'd be awesome, but would there need to be a special kernel?
WOW, Congrats man! Looking forward to this! As if the G2 will ever die! Pffft! And Kudos To nik3r for all his work towards this community!
BUT COME BACKKKKKK nik3r, we miss you!!
HTCDreamOn said:
So this means you're giving us Nature UX in the near future? Good luck :good: also does this open up multi booting possibilities (proper multi booting, not anything like Boot Manager)? 'Cause that'd be awesome, but would there need to be a special kernel?
Click to expand...
Click to collapse
working on one of those... not sure what it would take for multiboot... could look into it once my main task is done -> SGS3 to G2
So, this would allow me to install more apps and less moving apps to sd card? Noob question, but I really do not know the answer.
Sent from my HTC Vision using xda app-developers app
Less apps, lager rom, kinda like custom mtd partions for older devices. Probably would need to have an ext partition to hold apps if you need a lot... gotta say I've been waiting for something like this!
Sent from my HTC Vision using xda premium
So all roms need to be modefied in order to get this to work? I can go back to my previous rom without problems cause partitions are only mounted in different order by this rom? Just to be shure...
And multitasking wil benefit a lot of this?
Yes, the updater script just writes system to the data partition and since the init files are in the boot.img.they mount the "data" partition as /system and "system" partition as /data. Minor alterations to any rom would take advantage of this work around. And yes you can swap back and forth between a bacckup and this or any other altered rom but just remember in recovery(for now) formating system clears data and factory reset (clearing data) deletes the rom.
ineedone said:
So all roms need to be modefied in order to get this to work? I can go back to my previous rom without problems cause partitions are only mounted in different order by this rom? Just to be shure...
And multitasking wil benefit a lot of this?
Click to expand...
Click to collapse
Oke i wiped all partitions with 4ext, installed rom, rebooted, but now it hangs on bootlogo?
It does take a min to boot... remember there's no cache. What does logcat say????
ineedone said:
Oke i wiped all partitions with 4ext, installed rom, rebooted, but now it hangs on bootlogo?
Click to expand...
Click to collapse
I really mean the htc bootlogo. I can boot into recovery and when i take a look at the partition table, i see systeem is still 549 and there is a 500mb swap partition.. have no knowledge of logcat but i can try and see later tonight when I'm home.
Edit: data partition is now 549
ineedone said:
I really mean the htc bootlogo. I can boot into recovery and when i take a look at the partition table, i see systeem is still 549 and there is a 500mb swap partition.. have no knowledge of logcat but i can try and see later tonight when I'm home.
Edit: data partition is now 549
Click to expand...
Click to collapse
Did you do changes in ramdisk?
Sent from my HTC Vision using xda app-developers app
EnZl said:
Did you do changes in ramdisk?
Sent from my HTC Vision using xda app-developers app
Click to expand...
Click to collapse
as i stated in the OP... yes i did change the mounting in the init.rc and init.vision.rc in the ramdisk. once the updater script sends the info tho the partitions i needed to edit those to make it boot with it making /dev/block/mmcblk0p26(originally data) the system mount. same for data mount is now the 0p25 partition
ineedone said:
I really mean the htc bootlogo. I can boot into recovery and when i take a look at the partition table, i see systeem is still 549 and there is a 500mb swap partition.. have no knowledge of logcat but i can try and see later tonight when I'm home.
Edit: data partition is now 549
Click to expand...
Click to collapse
Oke forget this post, I had the wrong partition info, and forgot about the 500mb swap on my sd because i don't use it, sorry
This is the partition table after installing this rom:
------------------ Info -------------------
mount point | fs | size | free
system ext4 549.2MiB 539.3MiB
data ext4 1.0GiB 792.8MiB
cache ext4 295.3MiB 290.5MiB
sdcard fat32 28.7GiB 12.8GiB
sd-ext ext4 129MiB 108.9MiB
swap swap 513MiB -
Current Rom: unknown
There are some errors in the recover.log of 4ext touch recovery, which i included. Maybe someone can help me out
ineedone said:
Oke forget this post, I had the wrong partition info, and forgot about the 500mb swap on my sd because i don't use it, sorry
This is the partition table after installing this rom:
------------------ Info -------------------
mount point | fs | size | free
system ext4 549.2MiB 539.3MiB
data ext4 1.0GiB 792.8MiB
cache ext4 295.3MiB 290.5MiB
sdcard fat32 28.7GiB 12.8GiB
sd-ext ext4 129MiB 108.9MiB
swap swap 513MiB -
Current Rom: unknown
There are some errors in the recover.log of 4ext touch recovery, which i included. Maybe someone can help me out
Click to expand...
Click to collapse
you have to remember that recoveries still look to the 0p25 as system but i have a way to show you if it is installing right.
reboot into recovery
plug phone into usb and usb into computer - make sure adb works... type in a terminal or command prompt "adb shell" and hit enter
you should be in an android shell... you should see this ~ #
then type df and hit enter - this will show the partitions and how they are mounted
select to install the rom and as soon as it starts press the up arrow and hit enter (if the up arrow does not bring up the df command just type it)
do this repeatedly and you will watch as the rom is installed, the space on and which partition is what.
let me know
ok so an update I have gotten Flinny's latest 10.1 to work also but I will not put it out until/ if I get his permission to do so
[/SIZE]
OdiemanSAM said:
you have to remember that recoveries still look to the 0p25 as system but i have a way to show you if it is installing right.
reboot into recovery
plug phone into usb and usb into computer - make sure adb works... type in a terminal or command prompt "adb shell" and hit enter
you should be in an android shell... you should see this ~ #
then type df and hit enter - this will show the partitions and how they are mounted
select to install the rom and as soon as it starts press the up arrow and hit enter (if the up arrow does not bring up the df command just type it)
do this repeatedly and you will watch as the rom is installed, the space on and which partition is what
Click to expand...
Click to collapse
Here is the output:
Partitions seem to change and i lose 500MB some how
~ # df
df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 188504 32 188472 0% /dev
/dev/block/mmcblk0p27
302356 4804 297552 2% /cache
~ # df
df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 188504 32 188472 0% /dev
/dev/block/mmcblk0p27
302356 4804 297552 2% /cache
/dev/block/mmcblk0p25
1099608 18840 1080768 2% /system
/dev/block/mmcblk0p26
1099608 18840 1080768 2% /data
/dev/block/mmcblk1p2 127936 16404 111532 13% /sd-ext
/dev/block/mmcblk1p1 30102144 16812160 13289984 56% /sdcard
/dev/block/mmcblk0p26
562384 10216 552168 2% /system
~ # df
df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 188504 32 188472 0% /dev
/dev/block/mmcblk0p27
302356 4804 297552 2% /cache
/dev/block/mmcblk0p25
562384 10216 552168 2% /system
/dev/block/mmcblk0p26
562384 10216 552168 2% /data
/dev/block/mmcblk1p2 127936 16404 111532 13% /sd-ext
/dev/block/mmcblk1p1 30102144 16815296 13286848 56% /sdcard
/dev/block/mmcblk0p25
562384 10216 552168 2% /data
~ # df
also from previous recovery.log:
About to install:
EM1-1.zip
Continue install?
-- Installing: /sdcard/Download/EM1-1.zip
Finding update package...
I:Update location: /sdcard/Download/EM1-1.zip
Opening update package...
Installing update...
package_extract_file: no system/bin/backuptool.sh in package
set_perm: chown of /tmp/backuptool.sh to 0 0 failed: No such file or directory
set_perm: chmod of /tmp/backuptool.sh to 777 failed: No such file or directory
about to run program [/tmp/backuptool.sh] with 2 args
run_program: execv failed: No such file or directory
run_program: child exited with status 1
Creating filesystem with parameters:
Size: 1143992320
Block size: 4096
Blocks per group: 32768
Inodes per group: 7760
Inode size: 256
Journal blocks: 4363
Label:
Blocks: 279295
Block groups: 9
Reserved block group size: 71
Created filesystem with 11/69840 inodes and 9114/279295 blocks
warning: wipe_block_device: Discard failed
Initiating EliteMod ICS 120728
================================
Designed for HTC Desire Z/G2
Applying AOKP m6 and gapps...
minzip: Extracted file "/...........................................
.....................................................snip
minzip: Extracted file "/system/xbin/su"
package_extract_file: no system/bin/backuptool.sh in package
set_perm: chown of /tmp/backuptool.sh to 0 0 failed: No such file or directory
set_perm: chmod of /tmp/backuptool.sh to 777 failed: No such file or directory
about to run program [/tmp/backuptool.sh] with 2 args
run_program: execv failed: No such file or directory
run_program: child exited with status 1
package_extract_file: no system/bin/modelid_cfg.sh in package
set_perm: chown of /tmp/modelid_cfg.sh to 0 0 failed: No such file or directory
set_perm: chmod of /tmp/modelid_cfg.sh to 777 failed: No such file or directory
about to run program [/tmp/modelid_cfg.sh] with 2 args
run_program: execv failed: No such file or directory..............................................
.......................
minzip: Extracted file "/data/local/postsetup/undervolt.txt"
Applying EliteKernel 120728...
set_perm: chown of /system/etc/init.d/04mountsddl to 0 0 failed: No such file or directory
set_perm: chmod of /system/etc/init.d/04mountsddl to 775 failed: No such file or directory
set_perm: chown of /system/etc/init.d/11apps2sd to 0 0 failed: No such file or directory
set_perm: chmod of /system/etc/init.d/11apps2sd to 775 failed: No such file or directory
set_perm: chown of /system/etc/init.d/61swap2sd to 0 0 failed: No such file or directory
set_perm: chmod of /system/etc/init.d/61swap2sd to 775 failed: No such file or directory
set_perm: chown of /system/etc/init.d/64swapmarker to 0 0 failed: No such file or directory
set_perm: chmod of /system/etc/init.d/64swapmarker to 775 failed: No such file or directory
set_perm: chown of /system/xbin/virtuous_oc to 0 0 failed: No such file or directory
set_perm: chmod of /system/xbin/virtuous_oc to 775 failed: No such file or directory
about to run program [/sbin/busybox] with 3 args
minzip: Extracted file "/tmp/dump_image"
minzip: Extracted file "/tmp/mkbootimg"
minzip: Extracted file "/tmp/mkbootimg.sh"
Extracting Kernel files...
minzip: Extracted file "/tmp/unpackbootimg"
minzip: Extracted file "/tmp/zImage"
Installing kernel...
about to run program [/tmp/dump_image] with 3 args
about to run program [/tmp/unpackbootimg] with 3 args
BOARD_KERNEL_CMDLINE no_console_suspend=1
BOARD_KERNEL_BASE 4000000
about to run program [/tmp/mkbootimg.sh] with 1 args
minzip: Extracted file "/tmp/vision_wipe_efs"
about to run program [/tmp/vision_wipe_efs] with 1 args
Backing up partition /dev/block/mmcblk0p13 to /sdcard/part13backup-1358877146.bin ...
Backing up partition /dev/block/mmcblk0p14 to /sdcard/part14backup-1358877146.bin ...
Wiping partition /dev/block/mmcblk0p13...
Wiping partition /dev/block/mmcblk0p14...
Successfully wiped partitions 13 and 14.script result was []
EliteMod ICS installed successfully!
Credits to all the amazing devs that made this possible! Thank You!
Install from sdcard complete.
..................................................................
it also seems like only some files get written to data partition around 200mb, nothing to system...
you have dual mounts!!!! system and data are both mounted to both partitions. go into mounts windows in recovery and unmount both system and data partitions... then try again.
OdiemanSAM said:
you have dual mounts!!!! system and data are both mounted to both partitions. go into mounts windows in recovery and unmount both system and data partitions... then try again.[/QUOTE
mounted them last time because they didn't show up in fist instance :silly:
output:
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 188504 32 188472 0% /dev
/dev/block/mmcblk0p27
302356 4804 297552 2% /cache
/dev/block/mmcblk1p1 30102144 16824752 13277392 56% /sdcard
~ # df
df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 188504 32 188472 0% /dev
/dev/block/mmcblk0p27
302356 4804 297552 2% /cache
/dev/block/mmcblk1p1 30102144 16824752 13277392 56% /sdcard
/dev/block/mmcblk0p26
1099608 31892 1067716 3% /system
~ # df
df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 188504 32 188472 0% /dev
/dev/block/mmcblk0p27
302356 4804 297552 2% /cache
/dev/block/mmcblk1p1 30102144 16824752 13277392 56% /sdcard
/dev/block/mmcblk0p26
1099608 136220 963388 12% /system
~ # df
df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 188504 32 188472 0% /dev
/dev/block/mmcblk0p27
302356 4804 297552 2% /cache
/dev/block/mmcblk1p1 30102144 16824752 13277392 56% /sdcard
/dev/block/mmcblk0p26
1099608 288248 811360 26% /system
~ # df
df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 188504 32 188472 0% /dev
/dev/block/mmcblk0p27
302356 4804 297552 2% /cache
/dev/block/mmcblk1p1 30102144 16827968 13274176 56% /sdcard
/dev/block/mmcblk0p25
562384 10216 552168 2% /data
~ # dfFilesystem 1K-blocks Used Available Use% Mounted on
tmpfs 188504 32 188472 0% /dev
/dev/block/mmcblk0p27
302356 4804 297552 2% /cache
/dev/block/mmcblk1p1 30102144 16824752 13277392 56% /sdcard
~ # df
df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 188504 32 188472 0% /dev
/dev/block/mmcblk0p27
302356 4804 297552 2% /cache
/dev/block/mmcblk1p1 30102144 16824752 13277392 56% /sdcard
/dev/block/mmcblk0p26
1099608 31892 1067716 3% /system
~ # df
df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 188504 32 188472 0% /dev
/dev/block/mmcblk0p27
302356 4804 297552 2% /cache
/dev/block/mmcblk1p1 30102144 16824752 13277392 56% /sdcard
/dev/block/mmcblk0p26
1099608 136220 963388 12% /system
~ # df
df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 188504 32 188472 0% /dev
/dev/block/mmcblk0p27
302356 4804 297552 2% /cache
/dev/block/mmcblk1p1 30102144 16824752 13277392 56% /sdcard
/dev/block/mmcblk0p26
1099608 288248 811360 26% /system
~ # df
df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 188504 32 188472 0% /dev
/dev/block/mmcblk0p27
302356 4804 297552 2% /cache
/dev/block/mmcblk1p1 30102144 16827968 13274176 56% /sdcard
/dev/block/mmcblk0p25
562384 10216 552168 2% /data
~ # df
Click to expand...
Click to collapse
so is it working for you now???
UPDATED OP
Sorry , still on htc bootlogo
Only files seems to be written to data
Is there a way to view if/what data is written to the different partitions or boot ? Or do i need to install aditional gapps?