[Discussion] CyanogenMod 7.x for Spica build 7.4 [+ 7.9 test build]

[gerrysnaps]

Just tried this as an update on 7.3, normal kernel.
- Noticed that as with previous update, the date and time still reset to 2005 after reboot, though it remembers the timezone setting.
- Also observed all the trimmings are in blue instead of green now? I guess we've taken up the latest CM7 updates?
- Quadrant Standard Total: 718. 3D seems to have improved from my previous run.

[zhmstar0310]

The build 7.4 have a little improvements , I can see photos from high-quality video now(it is not smooth),WIFI I did't test.
But I have an question , the power can't display 100% after I flashed ahb166 sync kernel from build7.3 , it is still like that when I flashed the build 7.4(with default kernel),and I charged more than five hours. Anyone have the same question?

[ghase1]

With the newest build and kernel ahb166/333/800 i make 828 points at quadrant!

[planetek]

I made 877 points at quadrant!

[hlukas]

and how long is your battery lasting with that 877 points setting?

[hamxabajwa]

Mine. I'm on build 7.3 with sync kernel. I'm revert back to 7.3 because of camera.


Sent from my GT-I5700 using Tapatalk

[MaximiDiabolo]

I'm revert back to 7.3 because of camera.

Why did you went back? I'm on 7.4 with nowal's prev3 and have a camera.

[tom3q]

5MB won't change in near future...may be you get the kernel more than 5MB atleast 2-3 yyears from now.
why separate kernel for recovery and normal.You can just change the u-boot arguments for that(without changing the kernel).
I have done this and it works fine.(in reco mode,just mount /cache and read if reco is needed...else normal boot).
Obvoiusly,above approach means working nand and ubi driver in your u-boot for spica nand.

Hey, I know what I'm doing. All the changes have valid reasons for them.

Our kernel is already around 4.8 MB, because of embedded initramfs, which is already trimmed down. Add there CIFS driver and more utils into initramfs and you can easily get above 5 MB. (Not even saying about new CWM recovery version for CM9 which doesn't fit in our current 5 MB limit.)

All the sane platforms (basically everything except few models from Samsung) have separate kernel for recovery. The reason is very simple. Every software update updates also the kernel. If the new kernel fails to boot you are left without recovery. Another reason is that this would greatly simplify the layout of rc scripts (and remove the need for patching init to parse bootmode string in kernel command line), because original Android ones could be used with only a small additional script containing things specific to Spica (init.spica.rc).

As for OneNAND and UBI in u-boot, both are already supported (with a minor fix for S3C6410 that I added), same goes for SDHCI controller of S3C6410.

The build 7.4 have a little improvements , I can see photos from high-quality video now(it is not smooth),WIFI I did't test.
But I have an question , the power can't display 100% after I flashed ahb166 sync kernel from build7.3 , it is still like that when I flashed the build 7.4(with default kernel),and I charged more than five hours. Anyone have the same question?

I believe that it's a problem with your battery. Try to disable any wireless data connections (mobile data, WiFi, etc.) and leave it for a while with screen turned off.

Why did you went back? I'm on 7.4 with nowal's prev3 and have a camera.

Flashing novawl's update over 7.4 basically downgrades it back to 7.3, at least partially, because some files from 7.4 are replaced by old versions (kernel for sure).

[hitlin37]

[QUOTE=tom3q;191009]Hey, I know what I'm doing. All the changes have valid reasons for them.

=>Our kernel is already around 4.8 MB, because of embedded initramfs, which is already trimmed down. Add there CIFS driver and more utils into initramfs and you can easily get above 5 MB. (Not even saying about new CWM recovery version for CM9 which doesn't fit in our current 5 MB limit.)

=> All the sane platforms (basically everything except few models from Samsung) have separate kernel for recovery. The reason is very simple. Every software update updates also the kernel. If the new kernel fails to boot you are left without recovery. Another reason is that this would greatly simplify the layout of rc scripts, because original Android ones could be used with only a small additional script containing things specific to Spica.

=>As for OneNAND and UBI in u-boot, both are already supported (with a minor fix for S3C6410 that I added), same goes for SDHCI controller of S3C6410.

Ooh!..i didn't knew about embedded initramfs combined with kernel thing.Yup.You are right.....i was thinking from uImage point of view.
Also,you logic for separate kernel is right.My mistake.(I never thought about that possibility of kernel fails to boot...obviously..this can happen any time)
Can you point me to this rc script thing?

[tom3q]

Can you point me to this rc script thing?

Currently init (sources in system/core/init) is patched to load different .rc files depending on bootmode argument in kernel command line. If it detects bootmode=2 or bootmode=4 it loads init.rc and recovery.rc, otherwise it loads init.rc and init.spica.rc.

This requires init.rc to contain everything common for both boot modes (including platform specific things), init.spica.rc - specific for normal boot and recovery.rc - specific for recovery (like it is done in my initramfs-3.0 repository), so standard init.rc from Android (system/core/rootdir) cannot be used, because it doesn't contain setup exclusive for Spica and is made for normal boot only.

In normal setup, default for Android, recovery kernel has just a generic init.rc for recovery and init.whatever.rc for given platform and same goes for normal kernel, where just another variant of init.rc is included.

Also the resulting kernels are smaller, because in normal kernel the recovery doesn't have to be included and in recovery kernel some things relevant only for normal boot can be removed, like WiFi module.

Basically what's missing currently from my u-boot sources is a visual menu for users to select the kernel to boot.