I tried this and is great work indeed. Congratulations.
Froyo also rocks compared to Eclair.
1) I havent been able to remount the /system filesystem rw nor with Root Explorer, commandline or ADB. Somebody said on the Internet something about using a boot.img with "ro secure = 0".
As in many tablets, the /system partition is a cramfs system partition, which means that it is a read-only partition. Some phones have ext2/ext3 partitions. They can be made read-wrtiable. Himself created a rom for the V1 (NOT for the v2) that does have an ext3 read-writable partition. I already worked quite long a derivations of that for the V2, but so far unsuccessful. By now I also question the necessesity of havin a read-writable /system. I have already tried an ext3 image but it becomes more than twice as big, also for the upgrade.img that needs to be on the tablet to reflash it to factory defaults.
2) Is my personal opinion the actual image comes loaded with too many apps which makes the tablet slow. I would say a less crowded image would suit a better tablet and from there anybody should just install what they would like.
Yes and No. First of all
the google set of applications HAS to be part of the system rom on these tablets. They can only be installed as system applications. Which means that they either need a rw /system (as in 1), or they need to be added beforehand inside the rom.
Next to that a couple of applications are delivered by Rockchip (for these tablets) and/or by Archos. There is no use in stripping the tablet.Secondly:
The amount of applications doesn't make the tablet slow. The amount of aplications that get started automatically makes the tablet slow. Android sets an event after succesful boot/inititalization. Android checks the applications that "want to be triggered" by this event. It's those $%*@#
programmers that want their applications started on tablet startup.
And there is a second event that can be used to restart an application that is no longer in memory. (After being killed for example as I don't want it to run.) This event is actually for system libraries and programs. Some [email protected]
programmers even use that second event to have their applications started again.
As you see I get a bit emotional about the programming habits of some programmers.