Root [Kernel][OC] cdz Kernel for the ZTE Source

cooldudezach · Dec 12, 2013

This kernel is built from the stock kernel sources, with some modifications from me/rbheromax originally added for the ZTE Awe. The devices are quite similar, so the kernel was easy to port over (hopefully!).

CONSIDER THIS A BETA IMAGE UNTIL IT IS CONFIRMED TO WORK. I DO NOT OWN THIS DEVICE, I JUST BUILT THE KERNEL. I TAKE NO RESPONSIBILITY FOR WHAT YOU DO TO YOUR DEVICE.

What's new in this kernel:
12/12/2013

CPU Overclock to 1.944 GHz
Additional CPU governors
- SmartassV2
- Badass
- Wheatley
- Asswax
Additional I/O Schedulers
- sio
- zen
Additional Filesystem support
- Exfat
- F2FS

Planned Features:

GPU Overclock

Source Code:

Download Links

Installation

Install zip in CWM

or

Extract the boot.img, use dd to write to boot partition

Code:

dd if=/dev/zero of=/dev/block/mmcblk0p15
dd if=/sdcard/boot.img of=/dev/block/mmcblk0p15

Thanks

rbheromax for starting the kernel mod and helping me figure out what little I know now.
junkie2100 for his assistance with cm porting
dragongart6505(dragonhart6505!) & zeruth for testing

Krsmqn · Dec 12, 2013

Awesome work! Thanks for this.

A few questions:

Isn't mmcblk0p16 our recovery?

ZTE Source (n9511) Rooted W/CWM Recovery! - Page 6 - xda-developers

And will the kernel allow for swap?

Your install instructions, do both?

Code:

Installation
Install zip in CWM
Extract the boot.img, use dd to write to boot partition

If the answer to the last question is yes, then after we install the zip via cwm, where will the boot.img be located?

Thanks.

cooldudezach · Dec 12, 2013

Krsmqn said:
Awesome work! Thanks for this.

A few questions:

Isn't mmcblk0p16 our recovery?

ZTE Source (n9511) Rooted W/CWM Recovery! - Page 6 - xda-developers

And will the kernel allow for swap?

Your install instructions, do both?

Code:

Installation Install zip in CWM Extract the boot.img, use dd to write to boot partition

If the answer to the last question is yes, then after we install the zip via cwm, where will the boot.img be located?

Thanks.

Fixed, thanks. I wrote that thinking recovery, but this is obviously not the recovery. -_-

The instructions are either or, made that more obvious.

As for swap, I think that's enabled by default in the stock kernel, as it wasn't touched when adding mods:
"
[*] Support for paging of anonymous memory (swap)"

Krsmqn · Dec 12, 2013

Well then I can now tell you that it does work.

Bugs:

only one found so far. No wifi... it's grayed out and if you can get it to turn on it just stalls at "turning wifi on" ...

But overall it is snappy. I'll have to restore because... well... I can't live without wifi

Nice work. I hope it can be fixed.

cooldudezach · Dec 12, 2013

Krsmqn said:
Well then I can now tell you that it does work.

Bugs:

only one found so far. No wifi... it's grayed out and if you can get it to turn on it just stalls at "turning wifi on" ...

But overall it is snappy. I'll have to restore because... well... I can't live without wifi

Nice work. I hope it can be fixed.

Thats good to know. The kernel I built for the warp4g is also wifi-less. However, the awe is not wifi-less, so more research for me.

cooldudezach · Dec 13, 2013

Krsmqn said:
Well then I can now tell you that it does work.

Bugs:

only one found so far. No wifi... it's grayed out and if you can get it to turn on it just stalls at "turning wifi on" ...

But overall it is snappy. I'll have to restore because... well... I can't live without wifi

Nice work. I hope it can be fixed.

Try this one. It probably won't have the wifi fixed, but it might. I'm not sure.

Dev-Host - cdz-hera-kernel.zip - The Ultimate Free File Hosting / File Sharing Service

junkie2100 · Dec 13, 2013

has anyone tried the wlan module from the awe? that might fix it maybe the modules just incompatable

rbheromax · Dec 13, 2013

this is REALLY odd...no wifi no 2 others but awe has wifi. i wonder if its because they have diff wifi chips and we just compiled the wrong one in???

cooldudezach · Dec 13, 2013

rbheromax said:
this is REALLY odd...no wifi no 2 others but awe has wifi. i wonder if its because they have diff wifi chips and we just compiled the wrong one in???

I'm trying to get source code for the others from ZTE, they're giving me the go around. Go figure. How would we find out what wifi chips they have?

rbheromax · Dec 13, 2013

um....dmesg from stock kernel maybe?
or check out the config file

Krsmqn · Dec 13, 2013

You can find the stock image as well as a complete backup of the stock ROM over @ xda http://forum.xda-developers.com/showthread.php?t=2520309

cooldudezach · Dec 13, 2013

rbheromax said:
um....dmesg from stock kernel maybe?
or check out the config file

Well, here's the dmesg wifi-relevant snippits from the awe:

Code:

<4>[12-13 19:23:53.661] [0][787: Thread-54]wlan: module license 'Proprietary' taints kernel.
<4>[12-13 19:23:53.661] [0][787: Thread-54]Disabling lock debugging due to kernel taint
<6>[12-13 19:23:53.691] [0][787: Thread-54]wlan: loading driver v3.2.1.73
<6>[12-13 19:23:53.721] [0][787: Thread-54]DefaultCountry is US
<4>[12-13  19:23:53.731] [0][787: Thread-54]Read form mac file - wifiaddr:<snip> get wifi mac successfully! 
<4>[12-13  19:23:53.731] [0][787: Thread-54]Read form p2p mac file - wifiaddr:<snip> get wifi p2p successfully! 
<4>[12-13 19:23:53.731] [0][787: Thread-54]wifi mac: <snip>
<3>[12-13 19:23:53.831] [1][755: sh]hcismd_set_enable 0
<6>[12-13 19:23:53.831] Bluetooth: opening HCI-SMD channel :APPS_RIVA_BT_ACL
<6>[12-13 19:23:53.831] Bluetooth: opening HCI-SMD channel :APPS_RIVA_BT_CMD
<6>[12-13 19:23:53.831] [0][16: kworker/0:1]Bluetooth: HCI device registration is starting0x30  0xF3 0x1D 0xE1 0x1F 0xF8
<6>[12-13 19:23:53.921] [1][683: er.ServerThread]acc_open
<6>[12-13 19:23:53.921] [1][683: er.ServerThread]acc_release
<6>[12-13 19:23:53.951] [0][787: Thread-54]wlan: WCNSS WLAN version 1.3.1.2
<6>[12-13 19:23:53.951] [0][787: Thread-54]wlan: WCNSS software version 120172
<6>[12-13 19:23:53.951] [0][787: Thread-54]wlan: WCNSS hardware version WCN v2.0 RadioPhy vIris_TSMC_2.0 with 48MHz XO
<2>[12-13 19:23:53.951] [0][799: MC_Thread]wlan: [0:799:F :CTL] Begin WDI Update Scan Parameters New Style Params
<3>[12-13 19:23:53.951] [0][799: MC_Thread]wlan: [0:799:E :CTL] End Update Scan Parameters New Style
<6>[12-13 19:23:53.982] [1][787: Thread-54]wlan: driver loaded
<2>[12-13 19:23:53.982] [0][799: MC_Thread]wlan: [0:799:F :CTL] Begin WDI Update Scan Parameters New Style Params
<3>[12-13 19:23:53.982] [0][799: MC_Thread]wlan: [0:799:E :CTL] End Update Scan Parameters New Style
<3>[12-13  19:23:54.082] [0][820: wpa_supplicant]wlan: [820:E :SME] PMC: STA not  associated with an AP with single active session. BMPS cannot be entered
<3>[12-13 19:23:54.082] [0][820: wpa_supplicant]
<6>[12-13 19:23:54.082] [0][820: wpa_supplicant]ADDRCONF(NETDEV_UP): p2p0: link is not ready
<3>[12-13  19:23:54.232] [1][820: wpa_supplicant]wlan: [820:E :SME] PMC: STA not  associated with an AP with single active session. BMPS cannot be entered
<3>[12-13 19:23:54.232] [1][820: wpa_supplicant]
<6>[12-13 19:23:54.232] [1][820: wpa_supplicant]ADDRCONF(NETDEV_UP): wlan0: link is not ready
<4>[12-13 19:23:54.282] [1][683: er.ServerThread]vib-zte pm8xxx_vib_enable(0ms)
<4>[12-13 19:23:54.282] [0][824: Thread-69]vib-zte pm8xxx_vib_enable(1ms)
<4>[12-13 19:23:54.292] [1][683: er.ServerThread]vib-zte pm8xxx_vib_enable(0ms)
<2>[12-13 19:23:54.342] [1][624: Binder_1][taos]light on while prox off
<2>[12-13 19:23:54.342] [0][624: Binder_1][taos]TAOS_IOCTL_ALS_ON,lux=0
<4>[12-13  19:23:54.342] [1][9: kworker/1:0]led_mpp_set : button-backlight  1(1-5MA, 2-10MA, 3-15MA, 4-20MA, 5-25MA, 6-30MA, 7-35MA, 8-40MA)
<2>[12-13 19:23:54.362] [0][799: MC_Thread]wlan: [0:799:F :CTL] Begin WDI Update Scan Parameters New Style Params
<3>[12-13 19:23:54.362] [0][799: MC_Thread]wlan: [0:799:E :CTL] End Update Scan Parameters New Style
<3>[12-13 19:23:54.502] [0][16: kworker/0:1]TAOS: lux_timep->saturation=8100 hi=41 lo=25
<4>[12-13 19:23:55.293] [0][931: netd]netd used greatest stack depth: 4968 bytes left
<2>[12-13 19:23:56.234] [0][799: MC_Thread]wlan: [0:799:F :CTL] Begin WDI Update Scan Parameters New Style Params
<3>[12-13 19:23:56.234] [0][799: MC_Thread]wlan: [0:799:E :CTL] End Update Scan Parameters New Style
<3>[12-13 19:23:56.384] [0][799: MC_Thread]wlan: [799:E :PE ] __limProcessAddBAReq: 1417: ADDBAREQ NUMBUFF 40  
<3>[12-13 19:23:56.384] [0][799: MC_Thread]
<6>[12-13 19:23:56.394] [0][799: MC_Thread]wlan: connected to 00:7f:28:01:73:c0
<6>[12-13 19:23:56.394] [0][16: kworker/0:1]ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
<3>[12-13 19:23:56.414] [0][820: wpa_supplicant]wlan: [820:E :SME] sme_FTUpdateKey: Unhandled state=0
<3>[12-13 19:23:56.414] [0][820: wpa_supplicant]
<3>[12-13 19:23:56.414] [0][820: wpa_supplicant]wlan: [820:E :SME] sme_FTUpdateKey: Unhandled state=0
<3>[12-13 19:23:56.414] [0][820: wpa_supplicant]
<3>[12-13 19:23:56.905] [0][799: MC_Thread]wlan: [799:E :PE ] __limProcessAddBAReq: 1417: ADDBAREQ NUMBUFF 40  
<3>[12-13 19:23:56.905] [0][799: MC_Thread]

Krsmqn · Dec 13, 2013

cooldudezach said:
Try this one. It probably won't have the wifi fixed, but it might. I'm not sure.

Dev-Host - cdz-hera-kernel.zip - The Ultimate Free File Hosting / File Sharing Service

Same issue.

cooldudezach · Dec 14, 2013

Krsmqn said:
Same issue.

Ok, I thought so. How about normal 3G connectivity?

Krsmqn · Dec 14, 2013

3g is fine.... Everything else is fine that I can see... Just the wifi.

Oh, ... and of course, wifi teather.

Krsmqn · Dec 16, 2013

I hope you guys are able to make this work sometime in the not so distant future. It would be nice to have a great working OC'd kernel that has working wifi. Good work so far though. I understand that it's not easy to get these things working perfectly.

cooldudezach · Dec 17, 2013

If somebody could do this, that would be great. (This was posted by junkie over in the warp 4g forum)

do me a favor people. on the awe go to terminal and insmod the wlan module. then immediately check the dmesg see if it gives you crap. then try the same on the warp or the source doesnt really matter which as its using the oc kernel

How I did it (and I'll update here if it turns out I did it wrong

)

-Make sure you can use 'adb shell' with your phone plugged in.
After you plug your phone in and type adb shell, execute these commands:
You could also type these on the phone via terminal emulator, if you wanted to.

Code:

su
dmesg > /sdcard/dmesg1.txt
insmod /system/lib/modules/wlan.ko
dmesg > /sdcard/dmesg2.txt

Zip those two files up, and if you could pm them to me, that would be great!

It would be great if you could do it with both the oc kernel and the normal kernel.

This should help identify the issue with wifi.

Krsmqn · Dec 17, 2013

I'll do that within the next few days. :thumbup:

Krsmqn · Dec 17, 2013

OK... here is what I got.

https://www.dropbox.com/s/otqyrvtzrhodnsu/Dmesg.zip

Both zips are in there. You'll see. But the OC kernel didn't go well... see the screenshot. Hope this helps.

Krsmqn · Dec 17, 2013

My bad... jpg only?
...

Picture isn't showing up.. So here is a db link to it. https://www.dropbox.com/s/lf0doo24vfkgh2i/Screenshot_2013-12-17-01-37-58.png

Hmm... seems that the app is giving me issues....

junkie2100 · Dec 17, 2013

looks to me like an incompatable module... when you do it on a warp 4g with stock kernel it says failed (file exists) which id assume means its already been loaded...

Krsmqn · Dec 17, 2013

Are you referring to the picture or the Dmesg texts?

junkie2100 · Dec 17, 2013

picture. didnt look at dmesg but im gonna guess it says something about a symbol mismatch

cooldudezach · Dec 17, 2013

junkie2100 said:
picture. didnt look at dmesg but im gonna guess it says something about a symbol mismatch

bingo.

<4>[12-17 09:37:47.960] [0][5497: insmod]wlan: disagrees about version of symbol cfg80211_new_sta
<4>[12-17 09:37:47.960] [0][5497: insmod]wlan: Unknown symbol cfg80211_new_sta (err -22)
<4>[12-17 09:37:47.960] [0][5497: insmod]wlan: disagrees about version of symbol wiphy_new
<4>[12-17 09:37:47.960] [0][5497: insmod]wlan: Unknown symbol wiphy_new (err -22)

So, er, what do I need to do? Google isn't being very friendly tonight. On that note, I should probably get my IRC set up again

junkie2100 · Dec 18, 2013

basically its a problem with a value that is supposes to be set to the aame thing in the kernel as it is in the module. and its not matching up

Root [Kernel][OC] cdz Kernel for the ZTE Source

Android Enthusiast

Member

Android Enthusiast

Member

Android Enthusiast

Android Enthusiast

Android Expert

Android Expert

Android Enthusiast

Android Expert

Member

Android Enthusiast

Member

Android Enthusiast

Member

Member

Android Enthusiast

Member

Member

Attachments

Member

Attachments

Android Expert

Member

Android Expert

Android Enthusiast

Android Expert

BEST TECH IN 2023

Smartphones

Best Android Phones

Upcoming

Best iPhones

Upcoming

Tablets

Best Tablets

Upcoming

Laptops

Best Laptops

Upcoming

Televisions

Best TVs

Upcoming

Game Consoles

Best Game Consoles

Upcoming

Wearables

Best Wearables

Upcoming

Smart Home

Smart Home Tech

Upcoming

Similar threads