[PRJ] apps2sd discussion

[SikYou]

I have used a 1.54G partition for the apps2sd. I have seen warnings about going over 2G. Has anyone tried any different sized partitions?

How much of that are you actually using? I've used 512mb in the past and have never come close to using it all.


Sent from my nonsensikal froyo

 

[pvella]

Attached is a text file with the results. Let me know if you need more info.

View attachment 758

Cannot see anything wrong in the mounts that the unit performs.

I assume that /dev/block//vold/179:17 /sdcard2 is your internal card and that /dev/block/vold/179:2 /system/sd is a second partition on your external card or is this a second partition on your internal card ?

 

[pvella]

How much of that are you actually using? I've used 512mb in the past and have never come close to using it all.


Sent from my nonsensikal froyo

Currently using about 300M and I am trying very hard to fill it

 

[daz]

isnt there already a custom boot.img that is being used to overclock? i believe it works but it disables the rear camera. I have not tested it personally but there is a thread for it on here. maybe that plus the original boot.img could be used to get apps2sd working and overclocking with the rear camera working also. and i thought we did have a working recovery but it had some ui glitches.

Hi Daz, modifying the init.rc is a lot harder than it seeems. As one needs to modify the boot image. I am looking into unpacking the boot image and making a custom boot.

ivy

Sent from my Ideos S7 using Android Tablet Forum App

 

[shanksv]

Cannot see anything wrong in the mounts that the unit performs.

I assume that /dev/block//vold/179:17 /sdcard2 is your internal card and that /dev/block/vold/179:2 /system/sd is a second partition on your external card or is this a second partition on your internal card ?

The second partition is on the internal card. So my setup is the internal 8G card has a 7G partition for data and a 1G for App2SD.



Sent from my Ideos S7 using Tapatalk

 

[ivyvisors]

shanksv,

could I get you to run the following command with both cards in:

ls /dev/block/vold/

and tell me what the output is.

~ivy

 

[shanksv]

shanksv,

could I get you to run the following command with both cards in:

ls /dev/block/vold/

and tell me what the output is.

~ivy

I wanted to see what happens if I create the partition in my external card and this works fine as expected, a reboot does not cause any issues. So I am not sure if the ls command is going to give you a good picture but here is what it says

$ ls /dev/block/vold/
ls /dev/block/vold/
179:17
179:16
179:2
179:1
179:0

So the setup now is 8G internal card formated for data, and the 16G external card formated as 15G for data and 1G for Apps2SD. If you want I can always redo my setup with apps2d in the internal card. Let me know.

 

[ivyvisors]

cool thanks for this, the trick is to find out which of these devices are which.

I think with the external card in it changes the layout a little.

can I get you to try the following command (after su ing)

mount -t ext2 /dev/block/vold/179:2 /system/sd

if that doesn't work, try:

mount -t ext2 /dev/block/vold/179:16 /system/sd

and then depending which one works run mount again for me.

~ivy

 

[shanksv]

They are all giving me a "mount: Device or resource busy", probably not what you are looking for. I tried all 0,1,2,16 and 17

But here is my current mount data

# mount
mount
rootfs / rootfs ro 0 0
tmpfs /dev tmpfs rw,mode=755 0 0
devpts /dev/pts devpts rw,mode=600 0 0
proc /proc proc rw 0 0
sysfs /sys sysfs rw 0 0
tmpfs /sqlite_stmt_journals tmpfs rw,size=4096k 0 0
/dev/block/mtdblock1 /system yaffs2 ro 0 0
/dev/block/mtdblock6 /data yaffs2 rw,nosuid,nodev 0 0
/dev/block/mtdblock5 /cache yaffs2 rw,nosuid,nodev 0 0
/dev/block//vold/179:1 /sdcard2 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,flush 0 0
/dev/block//vold/179:17 /sdcard 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,flush 0 0
/dev/block/vold/179:2 /system/sd ext2 rw,errors=continue 0 0
/dev/block/vold/179:2 /data/app ext2 rw,errors=continue 0 0
/dev/block/vold/179:2 /data/data ext2 rw,errors=continue 0 0
/dev/block/vold/179:2 /data/dalvik-cache ext2 rw,errors=continue 0 0
#

 

[ivyvisors]

Very odd.

I'm just trying to work out which device is which in /dev/block/vold, so I can tell you how to modify the scripts.

Can I get you to try the following.

busybox fdisk /dev/block/vold/179:0

then press p (and then enter) and copy the output.

press q and enter to quit.

and then

busybox fdisk /dev/block/vold/179:16

and do the same

~Ivy

 

[pbrauer]

Just wanted to give a quick thanks to all of you for your hard work on this!

 

[shanksv]

Here you go...

# busybox fdisk /dev/block/vold/179:0
busybox fdisk /dev/block/vold/179:0
The number of cylinders for this disk is set to 1936.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)
Command (m for help): p
p
Disk /dev/block/vold/179:0: 15.9 GB, 15931539456 bytes
255 heads, 63 sectors/track, 1936 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/block/vold/179:0p1 * 1 1804 14490565+ b Win95 FAT32
/dev/block/vold/179:0p2 1805 1936 1060290 83 Linux
Command (m for help): q
q
# busybox fdisk /dev/block/vold/179:16
busybox fdisk /dev/block/vold/179:16
Command (m for help): p
p
Disk /dev/block/vold/179:16: 8095 MB, 8095006720 bytes
255 heads, 63 sectors/track, 984 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/block/vold/179:16p1 * 1 984 7903915+ b Win95 FAT32

Command (m for help):

 

[ivyvisors]

Curious.

/dev/block/vold/179:0p2 1805 1936 1060290 83 Linux

is our ext2 partition. aka

/dev/block/vold/179:2

which is what my scripts are assuming.

in your /data partition, is there a file called install-recovery.log

and what's it's contents?

~ivy

 

[shanksv]

Dunno if you noticed my earlier comment, I now have the ext2 on my external SD and not the the internal card. But here are the contents of the log file.

Mon Jan 10 22:39:31 EST 2011 Starting install-recovery.sh
Mon Jan 10 22:39:31 EST 2011 Waiting SD to become ready...
rootfs / rootfs ro 0 0
tmpfs /dev tmpfs rw,mode=755 0 0
devpts /dev/pts devpts rw,mode=600 0 0
proc /proc proc rw 0 0
sysfs /sys sysfs rw 0 0
tmpfs /sqlite_stmt_journals tmpfs rw,size=4096k 0 0
/dev/block/mtdblock1 /system yaffs2 ro 0 0
/dev/block/mtdblock6 /data yaffs2 rw,nosuid,nodev 0 0
/dev/block/mtdblock5 /cache yaffs2 rw,nosuid,nodev 0 0
/dev/block//vold/179:1 /sdcard2 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,flush 0 0
/dev/block//vold/179:17 /sdcard 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,flush 0 0
/dev/block/vold/179:2 /system/sd ext2 rw,errors=continue 0 0
/dev/block/vold/179:2 /data/app ext2 rw,errors=continue 0 0
/dev/block/vold/179:2 /data/data ext2 rw,errors=continue 0 0
/dev/block/vold/179:2 /data/dalvik-cache ext2 rw,errors=continue 0 0
Mon Jan 10 22:39:41 EST 2011 Finishing install-recovery.sh

 

[ivyvisors]

Okay. I did miss that, but it appears that it is mounting everything correctly.

can you run the following command:

busybox df -h

and give me the output.

But to me it looks like it's working correctly. remember some system utilities won't report the "extra" space for data, as we're not mounting a new data partition, but bind mounting certain things to be placed in that partition.

~Ivy