Trying to put Android 2.2 on the SmartQV7
Since Gingerbread is coming out real soon, I figured it would be a good time to try to put Froyo on the V7. Telechips Android kernel changes are apparently not open sourced (but I did find over 2 GB of documentation and BSP's), so it will have to be built on the existing 2.2.29 kernel that ships with Android 2.1. Some nice people working on their own TCC8902 based tablets are letting me piggyback on their work ("Thank You!"s to Asure and VeNoMouS at http://apad.gen-x.co.nz/ ) to port CyanogenMod 6. Here is my first attempt:
Procedure:
I started with Corvus Mod 4 for V7
I copied the system files, framework and init files over from the 2.2 release
I did not copy any libraries over
Results:
Analysis:
The kernel is loading just fine
The system dies during init phase, before it get to the Boot animation step
Hypothesis:
I think there are 2 likely causes:
1) There is a Bad init script for 2.2 : nothing I have read indicates that there is a significant difference between the init script for 2.2 vs 2.1 but there are gaps in my knowledge that could hide a bus. To be sure, I will step through the init files again (I printed off several resources to help).
2) There is a Bad library that is killing the start up process: If the libraries have changed, it could crash the system start. I will need to copy over the correct libraries from the 2.2 build. This assumes that the Kernel is similar enough to to allow the libraries to be transferred.
Diagnostic:
Plan A: Step through the init files from 2.1 for the V7 and compare it to the init files from the TCC8902 device/APad. Where there is deviation regarding hardware, defer to the SmartQ scripts. Where there is deviation regarding the framework and Zygote, defer to the APad scripts.
If this boots, we can move on to the next step: making sure that the hardware support is correct.
If not, we go to Plan B:
Plan B: Put markers in the Init.rc script to let me know when each step of the boot up is complete. This will tell me where the boot is failing, and I'll trouble shoot each or those until we get to the Home screen.
The next time I'll start with Android 2.1v3 which just came from Smart Devices this morning.
Generic Plea for Help:
So that you can play along at home, I've uploaded the V7 firmware file to Mediafire. You can use the SmartQV SDK to uncompress the files in Linux, so feel free to make and suggest changes (I ain't doing this blog to look smart!)
http://www.mediafire.com/?24pinzf3n4o4kot
Procedure:
I started with Corvus Mod 4 for V7
I copied the system files, framework and init files over from the 2.2 release
I did not copy any libraries over
Results:
- SmartQ Logo with Android showed (boot logo from initrd?)
- Progress Bar worked on First boot
- First Boot hung over 60+ minutes and eventually closed itself out after I went to sleep
- I never saw the Boot Animation on first Boot
- Subsequent boots end shortly after the kernel boots (before we get to Corvus' boot animation)
Analysis:
The kernel is loading just fine
The system dies during init phase, before it get to the Boot animation step
Hypothesis:
I think there are 2 likely causes:
1) There is a Bad init script for 2.2 : nothing I have read indicates that there is a significant difference between the init script for 2.2 vs 2.1 but there are gaps in my knowledge that could hide a bus. To be sure, I will step through the init files again (I printed off several resources to help).
2) There is a Bad library that is killing the start up process: If the libraries have changed, it could crash the system start. I will need to copy over the correct libraries from the 2.2 build. This assumes that the Kernel is similar enough to to allow the libraries to be transferred.
Diagnostic:
Plan A: Step through the init files from 2.1 for the V7 and compare it to the init files from the TCC8902 device/APad. Where there is deviation regarding hardware, defer to the SmartQ scripts. Where there is deviation regarding the framework and Zygote, defer to the APad scripts.
If this boots, we can move on to the next step: making sure that the hardware support is correct.
If not, we go to Plan B:
Plan B: Put markers in the Init.rc script to let me know when each step of the boot up is complete. This will tell me where the boot is failing, and I'll trouble shoot each or those until we get to the Home screen.
The next time I'll start with Android 2.1v3 which just came from Smart Devices this morning.
Generic Plea for Help:
So that you can play along at home, I've uploaded the V7 firmware file to Mediafire. You can use the SmartQV SDK to uncompress the files in Linux, so feel free to make and suggest changes (I ain't doing this blog to look smart!)
http://www.mediafire.com/?24pinzf3n4o4kot
Comments
Post a Comment