[Gen9 Android Development] trevd:
The missing and the bad!

Right I'm Back

Where was I - I'll cover what's missing.

Clearly the other side, I.e the system partition. For my tests I been "jaffing" on a 4.0.25 rom, I basically dump the full system into a ext4 img.

I also copied the /etc directory normally found on the root of archos rom to the /system/etc. the dropped the *.ko files into /system/lib/modules.

/system/etc/ is symlinked into /etc at boottime so I makes sense to add the recovery.fstab into the /system/etc/ directory.

the Wpa_supplicant binary I think need a rebuild as I read that it does auto mounting/detection of the wlan12xx_sdio.ko at runtime and Is a path that you specify at compile. Although the lazy would just symlink /system/lib/modules/wl12xx_sdio.ko to /etc/modules/wl12xx_sdio.ko and see if that cures what ale's yeah.

The Recovery needs a recoveryUI building for It I think It was lost in the archos_tablet tree while switching branches to ICS on my sources. So I use 4.0.25 as a test rom. I see If I can implement basic flash today, I'll be keeping my clothes on and only recovery will be doing the flashing LOL :laugh:

Also on trevd's Android Porting Saturday Fun List is, Investing using yaffs instead of ext4, I may not be possible to loop mount it with a larger than I wish to carry out code hack, If that is the case the ext4 it will be. I may also look at adding suppoort for the fastboot protocol, The PandaBoard I believe has a userland fatsboot server which maybe worth a kang..

I've marked zygote surfaceflinger and mediaserver as critcial, too many failure on them should dump you into recovery.

Something I'm going to suggest to the modding folks at large. [RANT] It would probably save a couple of hundred new threads from 13 year old kids who post ****e about there new phone that the parents had bought then, is now broken and bootlooping and how they're in sooo much trouble. If I see many more of those thread I'm think going to Metasploit a remote shell and run dmesg and logcat for them... Admittedly we all have to learn sometime But I don't ever recall learning anything on XDA by writing. [/RANT] But I digress. Along similar lines however a live boot animation which tells you what part of the boot process it's on would be a nice touch and from a quick look, It looks pretty easy to do as the bootanimation binary is display jpgs. Not a massive Issue the make the JPG's on the fly.

So , That leaves the The Bad in the Attached Ramdisk above

Like I Mentioned. Recovery UI Has Stopped Functioning

I've Only tested with the A101S

The Init.*.rc need attention. I tore out alot of the WIFI and bluethooth stuff to rework it especially re a101s.

I'm sure the more.... But that'll do for now, I may welll take the test rom up to JellyBean, at least CM10. Because other than the camera on some powervr stuff, it is pretty stable... The powervr stuff Is now solvable as should the Camera issue ( Hoping!!! ) no that my understanding is create an the omapzoom. is the place to start repo.

As I the custom, I might start a team.... of 1...:laugh: TeamJFMIW! which is the short version of Team Just ****ing Make it Work! A well used rallying call throughout my professional career and more so on those special chruch times!!