Kernel Source for Crescent

[Guest Simon O]

These are the 8 part files from ZTE. tar.bz2 compressed with 7zip multipart then compressed again (WTF?) with ZIP multipart...

Single part, extracted from the silly multipart files that ZTE uploaded:

kernel-src-zte-p736v-p736e-20111125.tar.bz2 - 72.33MB MD5 1353C7D5939EB937ECF7F336F063E009

[Guest kallt_kaffe]

From a quick look it seems what is new is the board and keypad file but more comparisons needs to be done to be sure that there isn't anything more that has been updated.

For overclocking this should work:

https://github.com/T...51f3c00b4d23f2f (This one also fixes instability if VMSPLIT_3G is used)

https://github.com/T...246d07576762dc0

https://github.com/T...866dc56fd75cd87

[Guest kallt_kaffe]

Added the changed files to Toms repo: https://github.com/TomGiordano/kernel_zte_blade

[Guest Sebastian404]

just want to put this out there:

diff ouk/config tmo/config 

4c4

< # Thu Oct 20 16:38:33 2011

---

> # Thu Oct 13 01:44:01 2011

1228c1228

< CONFIG_TOUCHSCREEN_MXT224_P736V=y

---

> # CONFIG_TOUCHSCREEN_MXT224_P736V is not set[/code]

[Guest Sebastian404]

OK,

I'm not sure if I screwed up, but I could not make a boot-able kernel until I built it with android-ndk-r7...

it would build with older versions, but not boot...

[Guest kallt_kaffe]

just want to put this out there:

diff ouk/config tmo/config 

4c4

< # Thu Oct 20 16:38:33 2011

---

> # Thu Oct 13 01:44:01 2011

1228c1228

< CONFIG_TOUCHSCREEN_MXT224_P736V=y

---

> # CONFIG_TOUCHSCREEN_MXT224_P736V is not set[/code]


The default config that came with the source has this one turned on. Are you saying the tmo version needs it off to work?


Btw, since you have a working Clockwork you should be able to make an overclocking addon by enabling 

MSM_CPU_FREQ_OVERCLOCK_800 and MSM_CPU_FREQ_SET_MIN_MAX if you are using Toms repo. It works with the ZTE Skate so it should work on the Blade2 too.

[Guest Sebastian404]

The default config that came with the source has this one turned on. Are you saying the tmo version needs it off to work?

Btw, since you have a working Clockwork you should be able to make an overclocking addon by enabling

MSM_CPU_FREQ_OVERCLOCK_800 and MSM_CPU_FREQ_SET_MIN_MAX if you are using Toms repo. It works with the ZTE Skate so it should work on the Blade2 too.

I did my usual thing with the recovery kernel of turning off the stuff you don't need (its my OCD) like sound, wifi, dab, etc, etc.. and having checked the .config that option has actually disappeared from the .config, but

CONFIG_TOUCHSCREEN_MXT224=y

that's interesting, The kernel I built works on both devices tho...

[Guest hecatae]

I did my usual thing with the recovery kernel of turning off the stuff you don't need (its my OCD) like sound, wifi, dab, etc, etc.. and having checked the .config that option has actually disappeared from the .config, but

CONFIG_TOUCHSCREEN_MXT224=y

that's interesting, The kernel I built works on both devices tho...

Sebastian, I've never had to use the touchscreen when using clockwork, it's usually all button presses

[Guest Sebastian404]

Sebastian, I've never had to use the touchscreen when using clockwork, it's usually all button presses

ah, well that is something I usually turn off too, but when I did that the buttons below the screen on the Crescent didn't work so I had to leave that enabled.

[Guest Sebastian404]

Checking between the kernel config with the newer versions of the roms...

diff .config.old .config.new 

4c4

< # Thu Oct 13 01:44:01 2011

---

> # Fri Nov 18 09:52:14 2011

1391d1390

< # CONFIG_CARKIT_FEATURE is not set

[/code]

[Guest Simon O]

Checking between the kernel config with the newer versions of the roms...

diff .config.old .config.new 

4c4

< # Thu Oct 13 01:44:01 2011

---

> # Fri Nov 18 09:52:14 2011

1391d1390

< # CONFIG_CARKIT_FEATURE is not set

[/code]



lol. Nothing amazing then.

[Guest Adam Cable]

kallt_kaffe - I'm happy to test some O/C kernels if you want to have some fun.

Adam

[Guest Sebastian404]

kallt_kaffe - I'm happy to test some O/C kernels if you want to have some fun.

Adam

im just playing with such a thing... personaly I'm not a big fan of overclocking, but its work looking into I guess

[Guest kallt_kaffe]

im just playing with such a thing... personaly I'm not a big fan of overclocking, but its work looking into I guess

I've pushed the needed code to Toms github. You just need to enable it.

Enable this in the kernel config:

CONFIG_MSM_CPU_FREQ_SET_MIN_MAX=y

CONFIG_MSM_CPU_FREQ_MAX=787200

CONFIG_MSM_CPU_FREQ_MIN=245760

CONFIG_MSM_CPU_FREQ_OVERCLOCK_800=y

787.2MHz is actually what it runs when claims to run at 800MHz.

Then use SetCPU or No-Frills CPU Control to overclock it. I recommend No-Frills as it is detects unexpected reboots

For installing a new kernel without needed to create a full boot.img use one if the zip files from this thread:

Just pop in your new zImage replacing the existing one.

[Guest Sebastian404]

hmm, I might be doing it wrong, but..

using a stock kernel, SetCPU says its max speed was 800.., now having applied your patch, I cant get SetCPU to let me go about 787 as the max speed...

[Guest kallt_kaffe]

hmm, I might be doing it wrong, but..

using a stock kernel, SetCPU says its max speed was 800.., now having applied your patch, I cant get SetCPU to let me go about 787 as the max speed...

Also apply this patch: https://github.com/T...5a2e209a3a6d9ae

I added that after posting about the other patches in this thread.

Without it it will turn off the OVERCLOCK_800 option in the kernel config unless you compile for the Skate.

[Guest Sebastian404]

Also apply this patch: https://github.com/T...5a2e209a3a6d9ae

I added that after posting about the other patches in this thread.

Without it it will turn off the OVERCLOCK_800 option in the kernel config unless you compile for the Skate.

I did apply that one...

[Guest kallt_kaffe]

I did apply that one...

And MSM_CPU_FREQ_OVERCLOCK_800 is set to "y" in your .config?

What does "dmesg | grep 0.22" say after a boot. (It may not be 0.22 but on my ZTE V9 that "grep" catches the cpu frequency table)

I only use NoFrills CPU Control but SetCPU should work too. Still you may want to try NoFrills if everything else fails.

[Guest kallt_kaffe]

Here's one I compiled using Toms repo with overclocking enabled.

Completely untested as I don't have a Blade2 myself.

zte_blade2_overclockable_kernel.zip

[Guest Sebastian404]

I lost my temper with patches*, so I started again, and just added the extra speeds into acpuclock.c directly....

that seems to of fixed it...

any ideas about higher speeds to add to acpuclock.c ? :)

UPDATE:

I just noticed Wifi no longer works, I build a regular kernel from an untouched source code, and wuth the config from my device, and wifi still wont work... interesting.

* I have short attention span... oh look shiney!.......

[Guest Sebastian404]

Here's one I compiled using Toms repo with overclocking enabled.

Completely untested as I don't have a Blade2 myself.

I tried this one, and it seemed to work, and wifi is working, I'll have to have a look through you commit history to work that out...

[Guest Simon O]

The wifi lib dhd.ko expects the kernel to be version 2.6.35.7-perf+ (with the +).

The dhd.ko that is built with the kernel should work but needs some firmware files in etc renaming for some bloody reason.

Damn you ZTE!

[Guest Sebastian404]

The wifi lib dhd.ko expects the kernel to be version 2.6.35.7-perf+ (with the +).

The dhd.ko that is built with the kernel should work but needs some firmware files in etc renaming for some bloody reason.

Damn you ZTE!

ah yes, I was just looking at dmesg..

<3>[11-29 11:40:57.360000] [204: WifiService]dhd: version magic '2.6.35.7-perf+ preempt mod_unload ARMv6 ' should be '2.6.35.7-perf preempt mod_unload ARMv6 '

[/code]




and then 



[code]E/WifiHW  (  154): insmod failed! module path: /system/lib/dhd.ko, arg: firmware_path=/etc/fw_4330.bin nvram_path=/etc/nv_4330.txt iface_name=wlan0

E/WifiHW  (  154): wifi_load_driver() -

ZTE do have some VERY strange ideas about things

[Guest Simon O]

Yes. Also the dhd.ko that is built from source wants fw_4319 and fw_4329 firmware, not fw_4330 that the Blade2 uses.

I'm getting a bit of a headache already.

[Guest Simon O]

hm.. doesn't help that the kernel source doesn't even have the BCM4330 code in it..