Guest bl1nk Posted March 11, 2011 Report Posted March 11, 2011 (edited) The kernel is based on the CM7 kernel from the new experimental branch on the official github repository for the blade. Flash the bl1nk.vX.boot.img via fastboot: fastboot flash boot bl1nk.vX.boot.imgor download the bl1nk.vX.update.zip and flash it via Clockworkmod. Tested changes in this kernel will be merged to the stable branch in the future, what means that they will be included in future nightlies. Download | Source Changelog: I'll just post the commits into the changelog... everything before and including that commit is in the versions I provide. Review commits here. v6: 31e4e44edf6a5191daa9 v5: battery and proximity sleep should be fixed v4: added the smartass cpufreq governor (thanks HCDRJacob) new v3: now based on the official experimental branch of the cm7 kernel v3: added SLQB breaks wifi. removing until we get the wifi driver build from source v2: fixed wifi v1: added BFQ and the ck2 patchset including BFS Edited March 16, 2011 by bl1nk
Guest mannas Posted March 11, 2011 Report Posted March 11, 2011 This is a kernel I just compiled, boots fine for me. I included the ck2 patchset and the BFQ IO Scheduler. Should bring more performance. :( The kernel is based on the CM7 kernel from nightly15, with the modifications t0mm13b made and some I made. Get it here and flash it via fastboot: fastboot flash boot bl1nk.bfq.ck2.v1.boot.img Only thing I noticed is, that wifi does not work (yet). I'll post an update later on. The device feels very responsive with it, hope someone tests this one too. :( I might try it out when you have wifi working keep up the good job
Guest bl1nk Posted March 11, 2011 Report Posted March 11, 2011 I might try it out when you have wifi working keep up the good job Works now, updated the post :(
Guest burstlam Posted March 11, 2011 Report Posted March 11, 2011 Thanks! test the kernel with OLED machine running RC2 much responsive. and screen scrolling improved especially with the adw launcher included.
Guest joyfun Posted March 11, 2011 Report Posted March 11, 2011 flashed v3 but wifi seems not work for me logcat /1102K, paused 4ms+10ms E/WifiService( 176): Failed to load Wi-Fi driver. D/SettingsAppWidgetProvider( 320): Call buildUpdate for widget:8 D/SettingsAppWidgetProvider( 320): buildUpdate done for widget:8 D/SettingsAppWidgetProvider( 320): Call buildUpdate for widget:8 D/SettingsAppWidgetProvider( 320): buildUpdate done for widget:8 I/TelephonyRegistry( 176): notifyServiceState: 1 home Unknown CSS not suppo rted -1 -1RoamInd: -1DefRoamInd: -1EmergOnly: false I/TelephonyRegistry( 176): notifyDataConnection: state=0 isDataConnectivityPoss ible=false reason=null interfaceName=null networkType=0 I/TelephonyRegistry( 176): notifyDataConnection: state=0 isDataConnectivityPoss ible=false reason=gprsDetached interfaceName=null networkType=0 I/TelephonyRegistry( 176): notifyServiceState: 0 home China Unicom China Unicom 46001 UMTS CSS not supported -1 -1RoamInd: -1DefRoamInd: -1EmergOnly: false I/TelephonyRegistry( 176): notifyDataConnection: state=0 isDataConnectivityPoss ible=true reason=null interfaceName=null networkType=3
Guest iconoclysm Posted March 11, 2011 Report Posted March 11, 2011 Works now, updated the post :( V3 wifi is broken for me, shows errror, but V2 is looking great. This is pretty snappy and the proximity sensor bug seems to be squashed! I was getting about 850 in quadrant bench under the regular kernel and now I'm getting 1000ish Well done sir!
Guest hedgepigdaniel Posted March 11, 2011 Report Posted March 11, 2011 (edited) I flashed v3 of your kernel today but I've found that wifi stops working (wifi sais "error" in settings and cannot turn on) EDIT: tried flashing v2 and the wifi works fine. I noticed no change in performance (tested wiht quadrant) between either v2 v3 or stock Edited March 11, 2011 by hedgepigdaniel
Guest bl1nk Posted March 11, 2011 Report Posted March 11, 2011 flashed v3 but wifi seems not work for me V3 wifi is broken for me, shows errror, but V2 is looking great. I flashed v3 of your kernel today but I've found that wifi stops working (wifi sais "error" in settings and cannot turn on) Will fix that now, also noticed that right after posting v3 here... I was too tired.
Guest gameSTICKER Posted March 11, 2011 Report Posted March 11, 2011 I included the ck2 patchset and the BFQ IO Scheduler. Should bring more performance. :( Awesome! That might be my biggest reason to switch from JJ9 to CM7, thanks :(
Guest DVDeus Posted March 11, 2011 Report Posted March 11, 2011 Hello! Is Lutea Base completely the same hardware so I can flash it the same way as SF? It has 5MP camera though. Thanks!
Guest burstlam Posted March 11, 2011 Report Posted March 11, 2011 Using V2 but the blackout issue seem appear again...
Guest bl1nk Posted March 11, 2011 Report Posted March 11, 2011 Hello! Is Lutea Base completely the same hardware so I can flash it the same way as SF? It has 5MP camera though. Thanks!I also got the BASE lutea... :( Using V2 but the blackout issue seem appear again...Thanks to wbaw.. make sure you do the following: tick "Always use proximity" in call settings.This fixes the proximity sensor issue
Guest Scoopading Posted March 11, 2011 Report Posted March 11, 2011 (edited) Giving V2 a quick check, so I thought I'd package it for flashing in ClockWorkMod :( If anyone prefers to do it that way you can get the zip file here.. File: bl1nkV2-kernel-update.zip MD5: fdf289dea54f115ac658e026dfedc749 Link: http://www.mediafire.com/?20okz2596ztqd58 Edited March 11, 2011 by Scoopading
Guest bl1nk Posted March 11, 2011 Report Posted March 11, 2011 Giving V2 a quick check, so I thought I'd package it for flashing in ClockWorkMod :( If anyone prefers to do it that way you can get the zip file here.. File: bl1nkV2-kernel-update.zip MD5: fdf289dea54f115ac658e026dfedc749 Link: http://www.mediafire.com/?20okz2596ztqd58Thanks a lot, I'll mirror it and attach it to the top post :(
Guest ivanko021 Posted March 11, 2011 Report Posted March 11, 2011 Many thanks! Both for the kernel and the Clockwork zip! Flashing now...
Guest domdom43 Posted March 11, 2011 Report Posted March 11, 2011 did you remove debugging/unnecessary logging from this kernel ?
Guest bl1nk Posted March 11, 2011 Report Posted March 11, 2011 did you remove debugging/unnecessary logging from this kernel ?I also did that, yes
Guest gsam101 Posted March 11, 2011 Report Posted March 11, 2011 How about the battery drain ? My battery dropped from 35% to 15% when i flahsed it (but i believe it's a bug :( ).
Guest bl1nk Posted March 11, 2011 Report Posted March 11, 2011 How about the battery drain ? My battery dropped from 35% to 15% when i flahsed it (but i believe it's a bug :( ).This shouldn't be because of my kernel. :(
Guest gsam101 Posted March 11, 2011 Report Posted March 11, 2011 I meant, does that kernel solve the CM7 battery problem ?
Guest bl1nk Posted March 11, 2011 Report Posted March 11, 2011 I meant, does that kernel solve the CM7 battery problem ?No, why should it? :(
Guest Lew247 Posted March 11, 2011 Report Posted March 11, 2011 I included the ck2 patchset and the BFQ IO Scheduler. Should bring more performance. The kernel is based on the CM7 kernel from nightly15, with the modifications t0mm13b made and some I made. What exactly does this Kernel do? and what benefits are there to it? as in what is this ck2 patch and BFQ thing? What modifications t0mm13b made did you include and what ones did you make?
Guest ivanko021 Posted March 11, 2011 Report Posted March 11, 2011 I tried to flash the zipped package via Clockwork but proximity sensor didn't work at all. Then I flashed the boot.img through Terminal Emulator following THIS guide and unfortunately the fix works occasionally on my OLED San Francisco with CM Nightly 15 Both times I've ticked the "Always use proximity" option in Call settings Sorry.
Guest surfatwork Posted March 11, 2011 Report Posted March 11, 2011 (edited) flashed this (v2) via clockwork, which worked just fine. proximity sensor working fine with "Always Use Proximity" ticked. responsive enough -i cant say if it is faster or slower than other ROMs. havent seen anything out of the ordinary with the battery. thanks, bl1nk. Edited March 11, 2011 by surfatwork
Guest burstlam Posted March 11, 2011 Report Posted March 11, 2011 (edited) I also got the BASE lutea... :( Thanks to wbaw.. make sure you do the following: tick "Always use proximity" in call settings.This fixes the proximity sensor issue sure I did tick it and wipe the cache and dalvik cache also. but it didn't work. now I am using the one release yesterday by css771 including . it works. Edited March 11, 2011 by burstlam
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now