[HD2 Android SD Development] satan!:
[FONT=&quot]That there was no misunderstanding, explain about Data.Img and StartUp.Txt. So let's say that we have and what you want.

Data.Img and StartUp.Txt:

Data.Img: best when it creates itself Android. Less hassle.

StartUp.Txt: at the moment, we have

[Start startup.txt]

set mtype 2524

set ramaddr 0x11800000

set ramsize 0x1e400000

set initrd_offset 0x00a00000

set KERNEL zImage

set initrd initrd.gz

set cmdline "rel_path = Android nand_boot = 0"

boot

[End startup.txt]

But this Txt convenient for the user to edit data. In other words, it is convenient and quickly set the values ​​that are required by the user for this and there he «StartUp.Txt», for example:

set cmdline "rel_path = Android data_size = 512 lcd_res = 240 conn_type = ppp gps_zone = eu nand_boot = 0"

data_size = 512: if an operand is to Txt, then Android will Data.Img given size (specified to create a 512Mb). If such a key to Txt has been set, it will create its own Android Data.Img his size (he is now in 1Gb).

Now:

Each time you launch Android checks Data.Img, if present, the Android simply passes the creation, editing Data.Img and proceeds to the next task. If Android does not find Data.Img it creates its size 1Gb.

I want to:

When implementing the operand «data_size =*» will be able to specify a size for your Data.Img. Naturally when you write a script will need to take into account the minimum and maximum. In the future it will be possible by modifying the startup code, change the size of the already established Data.Img. For example using 256Mb, needed more space (for the games ... .. etc.) 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 ....

Why: Creating Data.Img directly by Android takes away a lot of problems later use. There is no real need for third-party utilities to create and change Data.Img its size on the PC. It took a fresh and correct Data.Img, you can create it with Android and most of the size needed by the user, and not one that we have, by default.

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.

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

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 ....

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.

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. I personally like the default value of 167!

You change the value of finding the android in a folder to live. That and everything else can be done.

This is briefly described my dreams, ideas that I would like to see in this firmware.[/FONT]

[FONT=&quot]What would you say the creators?

Slowly, little by little to create a more user friendly Android smarter more logical than a wm or apple ....[/FONT]

Ps. Tried as an explanation. If something is unclear, specify.

Pss. put my log, if someone else is interesting.

later will lay out a goal-enabled sim and call-sms-if necessary