Related
This thread is for my personal kernel patches that I use to patch the main android kernel source to be able to build a working kernel for 32A Magic/Sapphire devices. Various people have chipped in during the development of this, please see the old thread for details.
The old dev thread is located here: http://forum.xda-developers.com/showthread.php?t=548061
Who is this for?
Anyone that builds kernels for HTC 32A Magic/Sapphire devices and has experience patching, configuring and building kernels for the ARM architecture. This thread is not intended as a guide for beginners.
Please do not ask how to build a kernel or how to configure a kernel.
Why?
It is true that HTC have released their kernel sources here, but one would have to use this exact source and would be unable to simply build a patch to make a 2.6.29 kernel due to the numerous differences in the HTC kernel source. One could not also just rely on pulling a new kernel snapshot from the main GIT tree. This patch intends to patch the kernel from the main msm branch with as little changes as possible.
What do you need?
Get the latest snapshot here (currently c7f8bcecb06b937c45dd0e342450a3218b286b8d.tgz)
Do not try and patch HTC's Kernel Source.
Notes:
For the time being, this patch works properly for both 2.6.27 and the 2.6.29 branch.
You will not be able to build kernels for 32B devices after you use this patch. Please keep a separate copy of your kernel for 32B devices.
[NEW] Built a 2.6.29 kernel from cyanogens /proc/config.gz, everything seems to be working fine.
The Files:
Kernel Patch 2.6.27 TT V3
Example Kernel:
32A Cyanogen 2.6.29 (v4.0.4 - stable version, updated 8/28) with wlan.ko - ONLY FOR USE WITH 4.0.4 CYANOGEN ROM (Cyanogen contains extra modules on his ROM for this kernel)
There seems to be a bug in 4.0.4 ROM where wifi tethering is not working. I have reverted back to 4.0.3 with the above kernel and all is working fine including tethering.
32A Cyanogen 2.6.29 (v4.1.1) with wlan.ko - ONLY FOR USE WITH 4.1.1 CYANOGEN ROM (Built from cyanogen github w 4.0.4 config)
Multi-touch is working in the browser.
32A Cyanogen 2.6.29 (v4.1.5) with wlan.ko - ONLY FOR USE WITH 4.1.5 CYANOGEN ROM (Built from cyanogen github w/4.1.5 config)
Cyanogen says he will be changing the scheduler to BFS soon.
32A Cyanogen 2.6.29 (v4.1.6) with wlan.ko - ONLY FOR USE WITH 4.1.6 CYANOGEN ROM (Built from cyanogen github w/4.1.6 config)
Includes BFS scheduler. Wow, browser flies.
32A Cyanogen 2.6.29 (v4.1.7) with wlan.ko - ONLY FOR USE WITH 4.1.7 CYANOGEN ROM (Built from cyanogen github w/4.1.7 config)
Haven't really tested this completely but seems fine.
32A Cyanogen 2.6.29 (v4.1.8) with wlan.ko - ONLY FOR USE WITH 4.1.8 CYANOGEN ROM (Built from cyanogen github w/4.1.8 config)
Camera working, Camcorder not working.
32A Cyanogen 2.6.29 (v4.1.9.2) with wlan.ko - ONLY FOR USE WITH 4.1.9.2 CYANOGEN ROM (Built from cyanogen github w/4.1.9.2 config)
Everything appears to be working properly
32A Cyanogen 2.6.29 (v4.1.11.1) with wlan.ko - ONLY FOR USE WITH 4.1.11.1 CYANOGEN ROM (Built from cyanogen github w/4.1.11.1 config)
Everything appears fine.
ROM boot images:
V2.1 eViL hero 2.9.5x (2.6.29, BFS, SLUB) 32A only (apply as update) - THIS IS EXPERIMENTAL. Any bugs, let me know.
Bluetooth,Wlan,Gps - working. (Not sure about headset but bluetooth turns on)
Graphic intensive apps - Working (Armadillo roll works, Gears gets 60fps)
Camera working this time
eViL hero 2.9.9 (2.6.29, SLUB, Anticipatory) 32A only (apply as update)
Seems to work properly!
Hero Volume Fix:
Hero Volume Fix (tested on eViL Hero) (Do a backup first and then test) -- Apply as update
Disclaimer:
These patches are experimental and should not be used for mission critical operations without extensive testing. I nor anyone else, will be held responsible for the use of these patches. If any damage or loss is experienced due to these patches, these are at your own risk. You will not be reimbursed by anyone for any amount what-so-ever.
Changelog:
V3
Added comments to changed values - may help to find errors in the future.
Changed Makefile.boot back to V1 to be the same as official HTC Source - (initrd_phys-y := 0x19A00000)
Changed EBI_SIZE to the same size as the HTC released kernel source.
Changed VMALLOC to the same size as the HTC released kernel source.
V2
Changed Makefile.boot - changed to initrd_phys-y := 0x1A200000 (credit to rayman84)
Great work. Looking forward to this.
I will have to learn how to compile a kernel now.
Tigertael..in the prevous thread u said..
Bluetooth and led working..
* SDCard
* Memory - (All memory)
* Camera - (Special thanks to zinx @ Freenode!)
* GPU1 - (Pretty sure this is right)
* ADSP - (Pretty sure this is right)
* MDP - (Untested)
* LED's - working fine.
* GPS -working fine.
* Bluetooth - working fine.
* WLAN - Working 100%
Click to expand...
Click to collapse
Does this mean if a Hero Cooker use this kernel then Bluetooth and Led Problem will be fix?
lesjaw said:
Tigertael..in the prevous thread u said..
Bluetooth and led working..
Does this mean if a Hero Cooker use this kernel then Bluetooth and Led Problem will be fix?
Click to expand...
Click to collapse
Unfortunately no. That was running on a stock ROM, not a Hero ROM.
The problem with Hero is the binaries that it was built upon was meant purely for the Hero. It's not known currently if you can correct this with a kernel, although I suspect you might be able to but only with the Hero sources for the kernel.
Even then it's a mission.
lesjaw said:
Tigertael..in the prevous thread u said..
Bluetooth and led working..
Does this mean if a Hero Cooker use this kernel then Bluetooth and Led Problem will be fix?
Click to expand...
Click to collapse
This means that bluetooth and the leds work correctly with a cupcake based rom. The Hero roms still have issues which will probably only be resolved when (if) the Hero source is released.
What in Cyanogen's kernel is working?
If multitouch is finally working, I love you
WaterMan! said:
What in Cyanogen's kernel is working?
If multitouch is finally working, I love you
Click to expand...
Click to collapse
I didn't even know Cyanogen had multitouch capable apps in his ROM.
If he does, he might've had to use kernel patches of his own and if this is so, he hasn't shared them with me.
Name display
How it s possible to add a caller name display in the rom as we know fido and rogers support this option thanks
roriii said:
How it s possible to add a caller name display in the rom as we know fido and rogers support this option thanks
Click to expand...
Click to collapse
This is a paid carrier feature, nothing to do with the ROM.
Clinton
TigerTael said:
I didn't even know Cyanogen had multitouch capable apps in his ROM.
If he does, he might've had to use kernel patches of his own and if this is so, he hasn't shared them with me.
Click to expand...
Click to collapse
I think the multitoch is more from some Android changes than kernel's , I read somewhere that The Kernel has already multitouch enabled, I fyou recall, it worked fine with Hero ROMs and stock kernel for Magic.
shwan_3 said:
I think the multitoch is more from some Android changes than kernel's , I read somewhere that The Kernel has already multitouch enabled, I fyou recall, it worked fine with Hero ROMs and stock kernel for Magic.
Click to expand...
Click to collapse
I do recall and I'm inclined to agree with you.
TigerTael said:
I do recall and I'm inclined to agree with you.
Click to expand...
Click to collapse
I can't say that my stock Magic (Vodacom) had multitouch enabled... It is enabled in Hero roms but that is in someway due to the HTC closed-source framework. The Magic (and Dream) kernels had no specific way of interpreting multitouch data without a kernel hack or modified dalvikvm).
http://lukehutch.wordpress.com/2009/01/25/get-multi-touch-support-on-your-t-mobile-g1-today/
Not only does the framework/kernel have to support multitouch, but the applications too.
That's true
Hi, I'm using your kernel 2.6.29 (from Cyanogen) in the bcook's porting of Cyanogen 4.0.4 (http://forum.xda-developers.com/showthread.php?t=544854). It works great but I don't understand why the multitouch doesn't work. It requires support by both the applications and kernel: the Cyanogen's browser package has multitouch (all the Dream and Magic 32B people use it) and your kernel should inherit it.
How did you compile it? Did you use, as base, the original kernel by Cyanogen from his git repository? Did you use his config file?
Thanks.
Actually, multi-touch IS working on the new kernel I built for 4.1.1
TigerTael said:
Actually, multi-touch IS working on the new kernel I built for 4.1.1
Click to expand...
Click to collapse
Do you mean that it is not working with the browser package in 4.0.4 or that you rebuild/fixed the kernel just for 4.1.1?
Can you provide a kernel for Cyanogen 4.0.4 (stable) with a working multitouch? I would keep my phone on the stable releases of Cyanogen. Thanks.
You can use the 4.1.1 kernel with 4.0.4 and multi-touch should work fine as well as all your other features. HOWEVER, please note that I could not get tether working in 4.0.4 or 4.1.1.
I am using 4.0.3 with 4.1.1 kernel, tether works, etc.
I'm using the new kernel from 4.1.1 in my Cyanogen 4.0.4 (I don't care about tethering): multitouch works well in the browser. Do you know if in Cyanogen there are other applications that support multitouch? Gallery don't.
The next step is to unify the kernel with the official one by Cyanogen (with some kind of board recognition on the boot phase) so we can just use the same official image.
Thanks to all!
For Sapphire EBI1/32A users
All credits goes to Wesgarner and the people who his works based on.. (cyanogen etc.)
Original Thread: http://forum.xda-developers.com/showthread.php?t=592466
Now, the real stuffs-
EBI1 CFS Kernel (01/01/10): Here
EBI1 BFS Kernel (02/01/10): Here
Instructions
Nandroid BACKUP!
Wipe/Clear
Install WG Build Y R1 (thread link above)
Install EBI1 Port (link above)
Boot and wait~
Enjoy, folks!
Thanks your work
downloading the rom now.....great and thanks , mate!!
arctu said:
For Sapphire EBI1/32A users
All credits goes to Wesgarner and the people who his works based on.. (cyanogen etc.)
Original Thread: http://forum.xda-developers.com/showthread.php?t=592466
Now, the real stuffs-
EBI1 CFS Kernel (01/01/10): Here
EBI1 BFS Kernel (02/01/10): Here
Instructions
Nandroid BACKUP!
Wipe/Clear
Install WG Build Y R1 (thread link above)
Install EBI1 Port (link above)
Boot and wait~
Enjoy, folks!
Click to expand...
Click to collapse
Good work man, I'll try it!!
imho, it's one of the featured smoothest rom besides CM. try it with BFS kernel.
Hmm.. there seems to be little interest in this rom port. I'll discontinue the port if people don't want it.
Thanks a lot for the hard work. Will try it out mate
no many issues so far, everything seems to work well.
arctu said:
Hmm.. there seems to be little interest in this rom port. I'll discontinue the port if people don't want it.
Click to expand...
Click to collapse
Thank you. this is just what I was looking for. I was using bcrook's CM port in earlier versions and was doing ok(only some FCs in the first boot).
and since build Y I can't user bcrook's port with app2sd and swap..maybe something to do with the new kernel.
I did post in that thread if there is a 32A port prior the release, but guess too many people are just too excited for the new release and overlooked my post..anyway
please don't discontinue it, I am sure many people will like to run WG build on their 32A Sapphire.
just wondering, I saw your other thread MAGIC Port, can we use that with ANY dream/32B ROM? and more importantly, is is stable? (I saw an big red ALPHA..)
if so, can we also use that with WG-Build?
so you can take a rest now, then?
arctu said:
Hmm.. there seems to be little interest in this rom port. I'll discontinue the port if people don't want it.
Click to expand...
Click to collapse
Thanks for porting, this rom seems sexy. Lol. Aniwae, pls continue! Since it would be great to have this rom widely used on 32A radios.
@haozheng91
MAGIC Port is stable actually.
But no, for WG Build and few other roms, even though it ports properly, it doesn't do a full port. For Cyanogen Mod, WG Build Y, Enomether etc. they use custom kernels. When you use my magic port, well, it does work, but it's not using the intended kernel which the ROM creator compiled.
But anyway, your problem was you're using CM Port over WG Build Y.. that's incorrect because of the different ramdisk (the rom init script). Hence the A2SD failed.
---
the rom is stable so far for me. i'm loving it and the smoothness.
so far, no FC. though, BFS does drain battery.
What's the difference between CFS & BFS?
multitouch
wipe
flash WG-Build Y.R1 - CFS with RAM Hack
flash wgbuildy_ebi1_signed.zip - CFS kernel
everything is going well, but multitouch doesnt work ...
BFS: http://en.wikipedia.org/wiki/Brain_Fuck_Scheduler
Naturally, smoother UI but drains a little more battery.
@coltcha:
CFS somehow doesn't work. Try BFS. I'll recompile the kernel once wesgarner release another version.
Does this ROM include the radio image that will brick a 32A magic?
BFS drains more battery.. that's good to know.
if Cyanogen Mod and WG Build use different kernel, then what are some ROMs we can use your magic port? Cyanogen Mod is one of the most popular ROMs there..
what about any of the Eclair ROMs?
I have heard that BFS is supposed to be a little faster..but WG recommands CFS as BFS is not as stable or something.. as for the battery, I always have to recharge everyday, so can't really tell the difference between different ROM or kernel...
hikki2000 said:
Does this ROM include the radio image that will brick a 32A magic?
Click to expand...
Click to collapse
it doesnt.
@haozheng91
like i said, it'll work on any 32B roms.
it's just not a full port for cases of roms with custom kernel. so... if you go on to the dream forums, if the ROM dev say he compiled his own kernel... you will just not benefit from the custom kernel enhancement. that's all.
though, most of the time, the custom kernel isn't much of a benefit as they're usually just variants of existing kernels with different build configs. you'll also see that most devs tend to us CM kernel... especially eugene eclair roms and some senseui roms.
arctu said:
it doesnt.
Click to expand...
Click to collapse
So it is safe for me to flash the ROM and then apply your port file, with my current SPL and Radio? Thanks.
yes. it should be. but then again, flash at your own risk, i or the rom dev aren't responsible if you brick your phone.
arctu said:
Hmm.. there seems to be little interest in this rom port. I'll discontinue the port if people don't want it.
Click to expand...
Click to collapse
No No, buddy, please keep up your good work, we are glad to see the diversities.
superFroyo v2.8.2 guys please port these rom for 32a device
we hope they will and i believe they will
Did you bother asking the developer?
gonna take some time for this to happen lol
Binary100100 said:
Did you bother asking the developer?
Click to expand...
Click to collapse
I asked one giant_rider is testing with some kernel function of this rom. But I wish some developer patches (as bcrook) created a patch for old radios
flash the Rom
flash port
davidcal said:
flash the Rom
flash port
Click to expand...
Click to collapse
work ??????
fonsigno said:
work ??????
Click to expand...
Click to collapse
Perfectly well
Well I don't think anybody should do any special port for any G1/32B roms.
I you wish to flash any of the roms in g1 section, the only thing you need to do is flash one of pershoot/bcrook/dumfuq 32A kernels on top of it and it will work just fine. Just make sure you flash the correct kernel version according to the rom base CM version.
In my opinion there is not a significant benefit to porting SuperFroyo since we now have other Froyo roms (without sense ui) that....
(1) Run on 32a 3.22 and 6.35 radios
(2) Have JIT working
(3) Have overclock kernels available up to ~700+ MHz
(4) Have Spareparts, CyanogenMod Settings and SetCPU for tweaking rom performance
These roms can now easily get 4.0-5.0 in Linpack and are stable.
Out of curiousity, I ported SuperFroyo a few days ago. The performance tweaks in SupSetup were not capatible with the .32 Sanpei kernel that was available for the 32a 6.35 radio at the time I did the port. We recently have the .34 kernel for the 32a 6.35 radio (thanks to carz12 and Switch33). I will update the ported SuperFroyo with the .34 kernel for the 32a 6.35 radio tonight or tomorrow hopefully. I don't think the result will be better than the other Froyo roms we have now, but I am happy to post a link if people want it.
thank you brother giant_rider for your hard work to give us the happiness
thanks you again giant
giant_rider said:
In my opinion there is not a significant benefit to porting SuperFroyo since we now have other Froyo roms (without sense ui) that....
(1) Run on 32a 3.22 and 6.35 radios
(2) Have JIT working
(3) Have overclock kernels available up to ~700+ MHz
(4) Have Spareparts, CyanogenMod Settings and SetCPU for tweaking rom performance
These roms can now easily get 4.0-5.0 in Linpack and are stable.
Out of curiousity, I ported SuperFroyo a few days ago. The performance tweaks in SupSetup were not capatible with the .32 Sanpei kernel that was available for the 32a 6.35 radio at the time I did the port. We recently have the .34 kernel for the 32a 6.35 radio (thanks to carz12 and Switch33). I will update the ported SuperFroyo with the .34 kernel for the 32a 6.35 radio tonight or tomorrow hopefully. I don't think the result will be better than the other Froyo roms we have now, but I am happy to post a link if people want it.
Click to expand...
Click to collapse
Hey giant_rider, I want link.
Thanks
giant please post the link
Here is a link to a ported SuperFroyo rom.
It is running Sanpei's .32 kernel for 32a 6.35 radio.
Some of the features in SupSetup are not enabled because they are not compatible with the kernel the way it is set up.
http://rapidshare.com/files/408904656/SuperFroyo2.4_32a_NR_v0.2.zip.html
I have been unable to get this rom to boot properly using the carz / switch .34 kernel. You can try flashing that kernel over this rom from recovery if you like. I think all of the settings in SupSetup could be enabled with the .34 kernel.
I am still sceptical whether this rom will be any better than the ones we have for 32a 6.35 or 3.22.
For a fast lite rom, I suggest you try flashing Switch's Fusebox Froyo, then install SetCPU and up the max CPU to 652 or 691 MHz. I did this tonight and got linpack of 4.6 and my phone is stable.
giant_rider,
Thanks
I was wondering if any of the kernels in the development section are re-based when a new Linux kernel comes out?
I've noticed that in all the HTC Forums that kernel threads will list what version of the Linux kernel they were based on but not here in the Nexus S forums. Why not?
What kernel version does it say on your Settings->About Phone screen?
Uh.. the threads here do mention them. Not sure about all of them but Netarchy does
- Kernel base 2.6.35.11 (as of 1.2.3)
Click to expand...
Click to collapse
And honestly.. I can really care less about the kernel base numbers. They're just numbers, I care about performance and speed.
zephiK said:
And honestly.. I can really care less about the kernel base numbers. They're just numbers, I care about performance and speed.
Click to expand...
Click to collapse
The newest kernal has the best speed (2.6.38)
mazodude said:
The newest kernal has the best speed (2.6.38)
Click to expand...
Click to collapse
And where's the source of that "kernal" (it's kernel) proving that its the best speed on the Nexus S? I'm not saying a kernel for another device because thats irrelevant. That's like saying Windows 7 SP1 is faster than Windows 7 SP0 on two different machines with different specifications.
zephiK said:
Uh.. the threads here do mention them. Not sure about all of them but Netarchy does
And honestly.. I can really care less about the kernel base numbers. They're just numbers, I care about performance and speed.
Click to expand...
Click to collapse
Thank you very much for letting me know your kernel version. I checked that thread and I did find it listed. I'm just trying to understand why the Nexus S doesn't have their kernels based on the latest Linux version when the HTC phones seem to.
But there not just numbers it's improvements to the base code. That can improve performance among other things.
mazodude said:
The newest kernal has the best speed (2.6.38)
Click to expand...
Click to collapse
2.6.38 hasn't made it to an android phone as far as I know.
Here is why he is say it's the best speed. It has a big change that should improve performance across the board.
http://www.linuxfordevices.com/c/a/News/Galbraith-Linux-kernel-scheduling-patch/
Here are the kernels I saw on the first 4 pages of development.
Honity - No mention in main post
Voodoo kernel from Supercurio - No mention in main post
Netarchy - 2.6.35.11
Trinity - No mention in main post
I don't own an Nexus S so I can't look for myself. I just wonder why there is no mention. When I see the kernel version tracked by other phones.
Here are some examples from other forums.
[Kernel] [.37.4] intersectRaven's Kernel
[KERNEL][AOSP] - Savaged-Zen [2.6.37.4
[Kernel] LeeDrOiD v2.2.8
[Kernel] 2.6.32.33
Click to expand...
Click to collapse
Is the Nexus S locked on a specific kernel version?
Are the developers not re-basing the kernels?
Hmm interesting point, i too am curious
in nexus one i used intersecraven 6.37.x kernels, i dont think the nexus one was based on the 6.37 when it came out the first time it had 6.32 kernels
Well the Nexus S official kernel version is 2.6.35.7. It's easy to merge the minor patches, but a major version jump to to .38 would require a lot of manual fixing of the kernel source code.
Changing major bases would require a lot of porting work, as many of the drivers required by the nexus s are not in the standard kernel by default.
It will probably be done eventually.
netarchy said:
Changing major bases would require a lot of porting work, as many of the drivers required by the nexus s are not in the standard kernel by default.
It will probably be done eventually.
Click to expand...
Click to collapse
Thank you for your reply. So just to confirm there are no technical limitations (lack of drivers/files/etc..) that prevent someone from re-basing their kernel versions for the Nexus S?
Hello guys n gals,
This is T-Mobile G2X version of my Harsh Kernel for O2X based on 3.0.y sources.
It share same tweaks and changelog with its international brother O2X.
This is my FIRST kernel based on sources of wkpark and vadonka.
This kernel is compiled by me, and comes with more added patches by me.
If you like it hit THANKS button.
Click to expand...
Click to collapse
All credits goes to:
armcee (CM7 & CM9 GOD of LG devices)
CM Team (You guys rock)
wkpark (ported kernel 3.0.26 to our devices)
vadonka (various kernel tweaks and awesome sources)
pastime (helping at various stages, and awesome fixes)
Owain (Biggest motivation for compiling 100 times a day)
and to everybody else who participated in making this possible.
Harsh Kernel P999:
Code:
Build from 3.0.37 sources.
Compiled using tweaked CodeSourcery arm Toolchain.
Better battery.
Default SIO scheduler.
Working Data Usage ICS.
Working Data Usage Limit.
Fixed USB tethering(windows).
And many tweaks.
Changelog:
Build 0510 Stock & OC
Updated Linux version 3.0.44 now.
Stock & OC version both uploaded to goo.im.
linux version 3.0.43 and 3.0.44 brings lots of changes (150+ commits hope good)
Still works for both JB and ICS both.
build 0509 Stock & OC
Compile zram as module (Thanks Benee)
Fix zram for dual core
build 0309 Stock
Linux Version 3.0.42
JellyBean[Heckfest] supported (thanks Benee)
build 0208 Stock & OC
Linux Version 3.0.39
Reverted various fixes which were implemented in 1907
Compiled with linaro toolchain on OS X
build 1907 NO-OC
Linux Version 3.0.37
Improves SIO scheduler for flash storage.
Added V(R) I/O Scheduler. (select if from AnTuTu CPU Master)
other various fixes (thanks to vork[benee] and faux123)
build 1006 Stock & OC
Linux Version 3.0.34
Patches from NVIDIA for cpu control (power saving)
Lowmemory killer from linux 3.4 ported by vork (thanks benee)
build 0306 Stock
Some patches from Benee (vork)
And tegra OTG try update.
build 2205 Stock
Linux Version 3.0.32
Re-enabled ext3 ability (fix unsupported file system problem)
Increased XZ compression usage.
build 1505 Stock & OC
Added Force Fast Charging patch by Chad Froebel
Lots of tegra related v21 source drop fixes, thanks to faux123
New wifi code change, from v21 sources
As usual few kernel config changes (still have to find minimum config )
build 0805 Stock & OC
Linux Version 3.0.31
Battery heat protection (thanks wkpark)
And few more kernel config changes
build 0405 Stock & OC
v21y battery driver (thanks vadonka)
too many kernel config changes (100s of changes)
pmem size reduced (let me know 4 mb change can make difference or not)
build 2804 No-OC
Linux 3.0.30 sources
First attempt for CpuSpy to work
build 2704 Stock & OC
rmcc's tegra_odm_touch: More ICS-compatibility
Catalin Marinas: Kmemleak patches
build 2504 - NO-OC
Updated to Linux 3.0.29
Scheduler Tweak
Scheduler multi-core support
build 2204
OC Version of Build 1904
build 1904
ZRAM compression changed from LZO to Google's SNAPPY (~2x faster)
ZRAM disksize set to 64mb
SNAPPY KERNEL
build 1504 - OC
Build from kernel sources 3.0.28
USB Mass Storage support for both SD Cards (ROM required to make it work)
XZ Compression, so even smaller size of zips.
OC Enabled upto 1.4 GHz
zram enabled and allocated
And many small changer that are not stated here.
build 1104
Lower TouchLED Brightness
Kernel refresh, compiled with new toolchain
build 0604
SD Card IO speed fixed (thanks again wkpark)
Nothing much, just some cosmetic fixes in code
build 0504
Using AnyKernel by koush (easy flash for all ICS roms.)
Added Voodoo again
Fajarep BL values (better battery)
build ReBorn 0304
upgraded Linux kernel source version 3.0.27
various MMC tweak and safepoints
pastime .config fix for support voltage unit in uV
build ReBorn 0204-1
fixed WiFi not turning on
WiFi was not loading up before, NOW FIXED
build ReBorn 0204
ReBorn: used clean wkpark's sources
added patches handpicked (new branch).
removed voodoo sound.
better bettery & speed
build 3003
proper suspend (wkpark original work)
build 2903
latest wkpark's merge fixes (thanks)
pastime1971's fixes
build 2703-1
latest wkpark's fixes he posted. (thanks again)
Fixed reboot issue
build 2703
some more kernel config changes.
pastime kernel pull fix.
build 2503-3
some kernel config changes.
spica1234 call quality improvement patch
Compiled with more hard flags, faster compilation.
build-2503
Updated to kernel 3.0.26 (thanks vadonka)
Added Simple I/O scheduler as default
and few kernel config tweaks
build-2403-4
Removed Kernel Debugs (further cleaning)
implemented hard float in order to reduce compile time
added ramdisk tweaks
build-2403-2
Implemented cache (first try to improve performance)
improved gps (source wkpark)
build-2403-1
Fixed Internal Storage problems(thanks to wkpark)
few compiling fixes, cleaner build.
build-2303
Initial sources.
Added usb tethering
Fixed Data Usage and Limit
Added Voodoo Sound
Selfcompiled linaro toolchain​
Understanding build number:
build-ddmm-n
where dd=date, mm=month & n=compile number [start from 0/none]
Known bugs:
No HW Acceleration (Nvidia and LG at fault)
Reboot/Reboot recovery work 90% of time.
Download OC 0510 Link: Goo.im
Download NO-OC 0510 Link: Goo.im
My PIZZA suppliers (Donators, thanks a lot)
Owain van Brakel
Warren (djvoleur)
Gregory Martinson
Vu Phan
John(aragorn7)
sourcecode
Looks great!
Sent from my LG-P999 using XDA
zoppp said:
Looks great!
Sent from my LG-P999 using XDA
Click to expand...
Click to collapse
Thanks you. If you are on CM9 unofficial nightly, you can try it. I am out of thanks per day
Installed. Will test drive today.
Sent from my G2x running AOKP ICS Build 28
Is it overclocked?
Sent from my LG-P999 using xda premium
flak0 said:
Is it overclocked?
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
No, its not overclocked.
Its on stock, will add overclock patch later, but defualt will always be stock.
Just for clarification: if hardware acceleration isn't yet included, what advantages are there to install this kernel over, say, faux's? Thanks.
GenghisKhan67 said:
Just for clarification: if hardware acceleration isn't yet included, what advantages are there to install this kernel over, say, faux's? Thanks.
Click to expand...
Click to collapse
Actually this is completely different kernel than faux kernel.
This kernel is not based on CM sources, it is based on kernel version 3.0.26, one of the latest in linux-3.0.y. If you guys know, Samsung Galaxy Nexus uses, kernel 3.0.8 in stock, this is kernel 3.0.26.
Faux kernel is based on CM sources linux-2.6.xx.x .
And there are no advantages as such, but deep sleep is finally working perfectly in kernel 3.0.y versions. So maybe better battery.
Working great on AOKP..... Battery seems a little bit better.
Sent from my LG-P999 using xda premium
the stock CM9 kernel has no HW accel, right? if so, i need this kernel for the voodoo, as stock CM9 doesn't have it.
joeyxl said:
the stock CM9 kernel has no HW accel, right? if so, i need this kernel for the voodoo, as stock CM9 doesn't have it.
Click to expand...
Click to collapse
True, stock CM9 do not have HW, neither do this kernel. And tegra2 devices will not have HW accel until Nvidia releases sources, or LG/T-Mobile release office ICS Rom.
Yes this kernel do have voodoo sound.
Appreciate your work. Thank you.
If you could please, in a timely fashion, provide the source to your changes and place it in the OP before the GPL police find out.
Thanks again!
Will there be a CM7 version of this kernel at all?
overground said:
Appreciate your work. Thank you.
If you could please, in a timely fashion, provide the source to your changes and place it in the OP before the GPL police find out.
Thanks again!
Click to expand...
Click to collapse
its already in its main thread in O2x, added it here too.
thendless said:
Will there be a CM7 version of this kernel at all?
Click to expand...
Click to collapse
No, not planned at the moment.
Nice!!! You work fast
Edit: Starting to like SIO, antutu benchmarks went up.
Sent from my LG-P999 using xda premium
Been following this project for awhile on other threads. I've been very impressed with this work. I've been curious about something, though, and didn't want to post this question in one of the main development threads.
What is the feasibility of upgrading the kernel to 3.1,3.2, or 3.3 series? For all I know it's completely impossible as I'm sure they had a reason to use 3.0 as the base for the project. I do find it interesting, though, that 3.3 comes with "android support" (not that I really know what that means either ).
MWBehr said:
Been following this project for awhile on other threads. I've been very impressed with this work. I've been curious about something, though, and didn't want to post this question in one of the main development threads.
What is the feasibility of upgrading the kernel to 3.1,3.2, or 3.3 series? For all I know it's completely impossible as I'm sure they had a reason to use 3.0 as the base for the project. I do find it interesting, though, that 3.3 comes with "android support" (not that I really know what that means either ).
Click to expand...
Click to collapse
yeah they have stated that next version will come with android support, it would not be 3.3, but would be 3.4. With more android related patches.
Guys even 3.0.y was a difficult task to port to tegra2, as no source, all thanks to wkpark and his awesome talents. I think your question can be better answered by him.
But code in 3.0.y to 3.1/3.2 has changed a lot, so would be very difficult to port, specially without any other android manufacturers not having 3.1/3.2 as base make it near impossible.
Harsh said:
yeah they have stated that next version will come with android support, it would not be 3.3, but would be 3.4. With more android related patches.
Guys even 3.0.y was a difficult task to port to tegra2, as no source, all thanks to wkpark and his awesome talents. I think your question can be better answered by him.
But code in 3.0.y to 3.1/3.2 has changed a lot, so would be very difficult to port, specially without any other android manufacturers not having 3.1/3.2 as base make it near impossible.
Click to expand...
Click to collapse
Thanks for the quick response. Ya, I was just curious more about if it was a possibility. If it takes a year or more, then that's what it takes. I have complete respect for the difficulties in porting something that's never been ported before.
so far so good...tks dev
Well...I can say this gets about 500 points higher on Quadrant 2.0 than Faux SV kernel. I didn't think it was fair to compare it to the OC version.