[HD2 Android SD Development] copenhagen:
When implementing the operand «data_size =*» will be able to specify a size for your Data.Img.......

>>how are you going to type or select which size you want when your pre bootanimation? not only that .. but there is no terminal output to the screen how would it prompt you to choose?

Ask the other operand «resize_data =*» and available data.img changes such as 512Mb or 1Gb, Android will do it. Later you can introduce the operands to change the existing size ....

>>http://xdaforums.com/showthread.php?t=737826

1a. In terminal type:

dd if=/dev/zero bs=1M count=XXX > /sdcard/datanew.img #(create a new XXX=MB)

OR

1b. (make existing one bigger) copy your current data.img to the root of your sdcard before you boot android. call it /sdcard/datanew.img. boot android

in terminal:

dd if=/dev/zero bs=1M count=XXX >> /sdcard/datanew.img #(append to existing ie: you made ur first data.img too small)

2. e2fsck -f /sdcard/datanew.img

3. resize2fs /sdcard/datanew.img

4. e2fsck -f /sdcard/datanew.img

shutdown and move your datanew.img to /sdcard/Android/data.img

done and done.

lcd_res = 240: change the existing value of the density of the screen. This operand allows you to change the density of the screen, making only one change to Txt, need not be tormented by the user to change build.prop. Add to Txt an operand, rebooted and got the density you want. Naturally check the minimum and maximum limit can be implemented.

>>just edit your /system/build.prop and reboot

conn_type = ppp: type of network protocol. There will not explain, not all value is needed, so ....

>>what does this mean? trust me... nothing is going to happen with the ppp implimentation on this build. unless its done by cedesmith or someone who can out skill his ril implimentation

gps_zone = eu: GPS device to find the zone. In assemblies, which contain the string set eu (or europe, usa ....). I think it is clear why ....

>>edit your /system/etc/gps.conf to whatever you want it to be

In StartUp.Txt can implement any of the operands for use by individual android. They only need to add it to write scripts and test them. It all rests with the creator.

>>who is busy enough as is. you dont need me to do all those things above... you can do them already.

But I think that this way the initial configuration of Android is much more efficient and smarter than ask the user to copy something somewhere to the desired value to one specific user, such as the density of the screen.

>>we do this out of shear convenience. perhaps we can just stop and force the people that like 240 to edit the build prop.. ask them what they think about that.... again.. just edit the build.prop its no different then editing a startup.txt .. you still have to edit a file regardless.

I don't want to seem negative so please don't take my comments as such.. its just that in order to accommodate your request - that's an awful lot of coding that needs to be done.. changes to the kernel.. etc.. when right now .. most of that stuff can be done on an individual basis.. i mean.. i wrote this guide for you .. and in that time i relearned how to create data.imgs etc... so this shouldn't really be an issue for anyone really.. just a little research.. anyways.. those are MY thoughts. on all this. My plate is hefty as is... and now there are three builds - 2 require testing etc and a public launch... so.. bad timing perhaps for this wish list.