1. Are you ready for the Galaxy S20? Here is everything we know so far!

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

Discussion in 'Android Devices' started by cooldudezach, Dec 12, 2013.

  1. cooldudezach

    cooldudezach Android Enthusiast
    Thread Starter

    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 (Text):
    1. dd if=/dev/zero of=/dev/block/mmcblk0p15
    2. 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
     


    strykerhandy, rbheromax and Krsmqn like this.

    1. Download the Forums for Android™ app!


      Download

       
  2. Krsmqn

    Krsmqn Member

    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 (Text):
    1. Installation
    2. Install zip in CWM
    3. 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.
     
    strykerhandy and cooldudezach like this.
  3. cooldudezach

    cooldudezach Android Enthusiast
    Thread Starter

    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)"
     
    strykerhandy and Krsmqn like this.
  4. Krsmqn

    Krsmqn Member

    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.
     
    strykerhandy likes this.
  5. cooldudezach

    cooldudezach Android Enthusiast
    Thread Starter

    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.
     
    strykerhandy and Krsmqn like this.
  6. cooldudezach

    cooldudezach Android Enthusiast
    Thread Starter

    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
     
    strykerhandy and Krsmqn like this.
  7. junkie2100

    junkie2100 Android Expert

    has anyone tried the wlan module from the awe? that might fix it maybe the modules just incompatable
     
    strykerhandy and Krsmqn like this.
  8. rbheromax

    rbheromax Android Expert

    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???
     
    strykerhandy and Krsmqn like this.
  9. cooldudezach

    cooldudezach Android Enthusiast
    Thread Starter

    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?
     
    strykerhandy and Krsmqn like this.
  10. rbheromax

    rbheromax Android Expert

    um....dmesg from stock kernel maybe?
    or check out the config file
     
    strykerhandy likes this.
  11. Krsmqn

    Krsmqn Member

    strykerhandy likes this.
  12. cooldudezach

    cooldudezach Android Enthusiast
    Thread Starter

    Well, here's the dmesg wifi-relevant snippits from the awe:
    Code (Text):
    1. <4>[12-13 19:23:53.661] [0][787: Thread-54]wlan: module license 'Proprietary' taints kernel.
    2. <4>[12-13 19:23:53.661] [0][787: Thread-54]Disabling lock debugging due to kernel taint
    3. <6>[12-13 19:23:53.691] [0][787: Thread-54]wlan: loading driver v3.2.1.73
    4. <6>[12-13 19:23:53.721] [0][787: Thread-54]DefaultCountry is US
    5. <4>[12-13  19:23:53.731] [0][787: Thread-54]Read form mac file - wifiaddr:<snip> get wifi mac successfully!
    6. <4>[12-13  19:23:53.731] [0][787: Thread-54]Read form p2p mac file - wifiaddr:<snip> get wifi p2p successfully!
    7. <4>[12-13 19:23:53.731] [0][787: Thread-54]wifi mac: <snip>
    8. <3>[12-13 19:23:53.831] [1][755: sh]hcismd_set_enable 0
    9. <6>[12-13 19:23:53.831] Bluetooth: opening HCI-SMD channel :APPS_RIVA_BT_ACL
    10. <6>[12-13 19:23:53.831] Bluetooth: opening HCI-SMD channel :APPS_RIVA_BT_CMD
    11. <6>[12-13 19:23:53.831] [0][16: kworker/0:1]Bluetooth: HCI device registration is starting0x30  0xF3 0x1D 0xE1 0x1F 0xF8
    12. <6>[12-13 19:23:53.921] [1][683: er.ServerThread]acc_open
    13. <6>[12-13 19:23:53.921] [1][683: er.ServerThread]acc_release
    14. <6>[12-13 19:23:53.951] [0][787: Thread-54]wlan: WCNSS WLAN version 1.3.1.2
    15. <6>[12-13 19:23:53.951] [0][787: Thread-54]wlan: WCNSS software version 120172
    16. <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
    17. <2>[12-13 19:23:53.951] [0][799: MC_Thread]wlan: [0:799:F :CTL] Begin WDI Update Scan Parameters New Style Params
    18. <3>[12-13 19:23:53.951] [0][799: MC_Thread]wlan: [0:799:E :CTL] End Update Scan Parameters New Style
    19. <6>[12-13 19:23:53.982] [1][787: Thread-54]wlan: driver loaded
    20. <2>[12-13 19:23:53.982] [0][799: MC_Thread]wlan: [0:799:F :CTL] Begin WDI Update Scan Parameters New Style Params
    21. <3>[12-13 19:23:53.982] [0][799: MC_Thread]wlan: [0:799:E :CTL] End Update Scan Parameters New Style
    22. <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
    23. <3>[12-13 19:23:54.082] [0][820: wpa_supplicant]
    24. <6>[12-13 19:23:54.082] [0][820: wpa_supplicant]ADDRCONF(NETDEV_UP): p2p0: link is not ready
    25. <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
    26. <3>[12-13 19:23:54.232] [1][820: wpa_supplicant]
    27. <6>[12-13 19:23:54.232] [1][820: wpa_supplicant]ADDRCONF(NETDEV_UP): wlan0: link is not ready
    28. <4>[12-13 19:23:54.282] [1][683: er.ServerThread]vib-zte pm8xxx_vib_enable(0ms)
    29. <4>[12-13 19:23:54.282] [0][824: Thread-69]vib-zte pm8xxx_vib_enable(1ms)
    30. <4>[12-13 19:23:54.292] [1][683: er.ServerThread]vib-zte pm8xxx_vib_enable(0ms)
    31. <2>[12-13 19:23:54.342] [1][624: Binder_1][taos]light on while prox off
    32. <2>[12-13 19:23:54.342] [0][624: Binder_1][taos]TAOS_IOCTL_ALS_ON,lux=0
    33. <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)
    34. <2>[12-13 19:23:54.362] [0][799: MC_Thread]wlan: [0:799:F :CTL] Begin WDI Update Scan Parameters New Style Params
    35. <3>[12-13 19:23:54.362] [0][799: MC_Thread]wlan: [0:799:E :CTL] End Update Scan Parameters New Style
    36. <3>[12-13 19:23:54.502] [0][16: kworker/0:1]TAOS: lux_timep->saturation=8100 hi=41 lo=25
    37. <4>[12-13 19:23:55.293] [0][931: netd]netd used greatest stack depth: 4968 bytes left
    38. <2>[12-13 19:23:56.234] [0][799: MC_Thread]wlan: [0:799:F :CTL] Begin WDI Update Scan Parameters New Style Params
    39. <3>[12-13 19:23:56.234] [0][799: MC_Thread]wlan: [0:799:E :CTL] End Update Scan Parameters New Style
    40. <3>[12-13 19:23:56.384] [0][799: MC_Thread]wlan: [799:E :PE ] __limProcessAddBAReq: 1417: ADDBAREQ NUMBUFF 40  
    41. <3>[12-13 19:23:56.384] [0][799: MC_Thread]
    42. <6>[12-13 19:23:56.394] [0][799: MC_Thread]wlan: connected to 00:7f:28:01:73:c0
    43. <6>[12-13 19:23:56.394] [0][16: kworker/0:1]ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
    44. <3>[12-13 19:23:56.414] [0][820: wpa_supplicant]wlan: [820:E :SME] sme_FTUpdateKey: Unhandled state=0
    45. <3>[12-13 19:23:56.414] [0][820: wpa_supplicant]
    46. <3>[12-13 19:23:56.414] [0][820: wpa_supplicant]wlan: [820:E :SME] sme_FTUpdateKey: Unhandled state=0
    47. <3>[12-13 19:23:56.414] [0][820: wpa_supplicant]
    48. <3>[12-13 19:23:56.905] [0][799: MC_Thread]wlan: [799:E :PE ] __limProcessAddBAReq: 1417: ADDBAREQ NUMBUFF 40  
    49. <3>[12-13 19:23:56.905] [0][799: MC_Thread]
     
    strykerhandy likes this.
  13. Krsmqn

    Krsmqn Member

    strykerhandy likes this.
  14. cooldudezach

    cooldudezach Android Enthusiast
    Thread Starter

    Ok, I thought so. How about normal 3G connectivity?
     
    strykerhandy likes this.
  15. Krsmqn

    Krsmqn Member

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

    Oh, ... and of course, wifi teather.
     
    strykerhandy likes this.
  16. Krsmqn

    Krsmqn Member

    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.
     
  17. cooldudezach

    cooldudezach Android Enthusiast
    Thread Starter

    If somebody could do this, that would be great. (This was posted by junkie over in the warp 4g forum)
    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 (Text):
    1. su
    2. dmesg > /sdcard/dmesg1.txt
    3. insmod /system/lib/modules/wlan.ko
    4. dmesg > /sdcard/dmesg2.txt
    5.  
    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 likes this.
  18. Krsmqn

    Krsmqn Member

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

    Krsmqn Member

    Attached Files:

  20. Krsmqn

    Krsmqn Member

    Attached Files:

  21. junkie2100

    junkie2100 Android Expert

    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...
     
  22. Krsmqn

    Krsmqn Member

    Are you referring to the picture or the Dmesg texts?
     
  23. junkie2100

    junkie2100 Android Expert

    picture. didnt look at dmesg but im gonna guess it says something about a symbol mismatch
     
    Krsmqn likes this.
  24. cooldudezach

    cooldudezach Android Enthusiast
    Thread Starter

    bingo.
    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 :p
     
    Krsmqn likes this.
  25. junkie2100

    junkie2100 Android Expert

    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
     

ZTE Source Forum

Features and specs are not yet known.

unknown
Release Date
0
Reviews
Loading...

Share This Page

Loading...