Related
NOTE: No longer being developed. You may want to try tytung's kernels instead.
Click to expand...
Click to collapse
Release 8.6
This is a Kernel I built for my own purposes, and now for others, based on the current EVO kernel (as of whenever I last merged it to my branch) and changes from various sources.
Click to expand...
Click to collapse
Features
Here's what's different to the main tree (See changelog for latest changes in case I forget to update this)
Packaged to be compatible with cedesmith's new style initrd for easy installation on builds using it
CIFS support via a module
mac address patch for wifi/bt by mdebeljuh. See http://forum.xda-developers.com/showthread.php?t=819819
Built without support for ext3 and yaffs
Optimized for speed rather than size
Removed some debug features the average user isn't capable of using anyway (dmesg/logcat still work)
G-sensor workaround by mdebeljuh & jdivic (http://forum.xda-developers.com/showthread.php?p=9208297#post9208297)
Smartass governor added as default
Sysfs interface for optional under/overvolting (see http://forum.xda-developers.com/showthread.php?t=821372) (800-1350mV)
Optional overclocking (via SetCPU or similar) to 1536MHz - USE AT YOUR OWN RISK - it may damage your phone
Optional older battery driver with my patch to support the official HTC extended battery (eb version)
Click to expand...
Click to collapse
Extended battery users extra WARNING!
r8.3+ version with "eb" supports extended batteries using the old driver. r7.7+ temperature reporting for extended batteries is reasonable but NOT accurate. Please see this post for more information.
As of r8.5.3 versions without eb in the name have EXPERIMENTAL (ie it has known bugs) support for extended batteries using a patch to the new driver. More information.
Click to expand...
Click to collapse
Use this at your own risk.
How to Install the kernel
Download the latest from here:
Release r8.6 - https://dl.dropbox.com/u/11373163/Kernels/update.kernel.hastarin.16.12.2010.zip
(Overclock and Undervolt enabled but defaults to normal speeds and voltages)
Release r8.6_eb - https://dl.dropbox.com/u/11373163/Kernels/update.kernel.hastarin.eb.16.12.2010.zip
(as above but with older battery driver with extended battery support)
Undervolt 925mV - https://dl.dropbox.com/u/11373163/Kernels/update.kernel.hastarin.undervolt925mV.15.12.2010.zip
(optional update to undervolt to 925mV, edit as needed)
NOTE: It would be nice to see a few more clicks of that Thanks button folks.
Click to expand...
Click to collapse
DONATIONS
In the past I've suggested donating to your favorite charity instead of me.
But I've decided due to the amount of time this is now taking to accept some donations. I encourage you to still consider a charity first, such as:
http://www.kennedysdisease.org/
So far I've had enough donations to buy an official HTC extended battery for testing purposes. Future donations will probably be spent on beer, coffee or junk food.
Please only donate if you can spare the money. NOTE: I've all but given up getting extended battery support working with the new driver!
I also can't make any guarantees on how long I can keep investing time in the kernel so please consider any donations to be for past work done, not what I might do in the future.
Finally please note I'm building a kernel here and working on the odd bit of code. The bulk of the work is done by others:
Cotulla
Markinus
Letama
Rajko
gauner1986
and no doubt more I've missed
Donations to some of them can be made here:
http://forum.xda-developers.com/showthread.php?t=794953
Click to expand...
Click to collapse
Anyone having issues with this kernel. PLEASE before you post them here, try the following:
Make sure you reboot twice after installing so files get updated (or manually update them then reboot if your build won't auto update)
Actually reading the README.txt provided!
Reading my FAQ
If that doesn't work try a stock EVO kernel
If you still have issues with the stock EVO kernel it's nothing I've done and we may have to wait for the devs to fix it.
If that still doesn't work, then don't use any task killers, and try a clean format of your SD card.
If that still doesn't work you're out of luck.
Click to expand...
Click to collapse
Further Information
I am running Autokiller (despite it's name this is not an automatic task killer) set to Optimum.
I do recommend System Panel Lite to be able to see what processes are using your CPU. I DO NOT recommend using any automatic task killer.
I do recommend using EBL with a 3 sec timeout
Further recommendations can be found in My FAQ
Click to expand...
Click to collapse
A note on the included lights file
memin1857 said:
I talked to gauner1986 (author of the new lights file) and the filename comes from the build.prop file.
It is the ro.board.platform=xxxxxx line in the build.prop file.
xxxxx is also your lights filename. (lights.xxxxx.so)
For example my desire hd build has msm7x30
others I have seen are htcleo, default, qsd8k, ace, bravo.
So you have to rename the lights.htcleo.so that is in hastarins root\system\lib\hw folder to match your builds filename if you want it to work.
Click to expand...
Click to collapse
Old versions
Old camera driver versions for builds that haven't been updated to support the new driver yet:
Release r8.5.3_oldcam - http://www.multiupload.com/KTF4ULINT3
(as per base but with old camera driver)
Release r8.5.3_eb_oldcam - http://www.multiupload.com/X6ZTQ9S2ER
(as above but with older battery driver with extended battery support)
Click to expand...
Click to collapse
Notes:
This should work with any build that can use the EVO kernel.
Data will not work on RMNET based builds.
For anyone else complaining about no data issues make sure you installed the kernel AND modules correctly, and if you're using an older build you may need to update your WiFi firmware and/or your radio.
If it's no data over 3G also check your APN settings.
Click to expand...
Click to collapse
Changelog
Code:
[I]Release r8.6 - 16/12/2010[/I]
- Patched Wifi driver to match main tree (fixes wakeup lag when wifi is on) - Thanks Markinus
- Updated init script to update calibration data (fixes mac address not working) - Thanks OSM
- Enabled extreme overclocking and included speeds from mdeejay's kernel. USE THESE AT YOUR OWN RISK I DO NOT recommend overclocking, you will see little benefit in daily use.
[I]Release r8.5.3 - 09/12/2010[/I]
- EXPERIMENTAL support for extended battery users (NOT for daily use yet)
See http://bit.ly/eDLk0g for more information
- REMOVED initrd.gz & haret.exe (by now all recent builds are updated anyway)
- REMOVED LeTama's new PPP wrapper and aussiebum's suggested ppp options
The latest builds incorporate these changes anyway, and you can get them from
the original thread - http://bit.ly/92IBH6
- Modified package to suit cedesmiths initrd.gz - http://bit.ly/foZ1j3
- Trimmed changelog to only include recent changes
- Yet another smd_tty patch test
[I]Release r8.5.1 - 26/11/2010[/I]
- Included LeTama's patch to fix music skipping when turning the screen on
- Included root folder structure with LeTama's new PPP wrapper and aussiebum's suggested ppp options
****** WARNING ************ WARNING ************ WARNING ************ WARNING ************ WARNING ******
Includes new camera driver you may need a new camera APK and libraries, etc
HTC Desire (Sense) Camera APK - http://www.multiupload.com/0YVTSSQO79 (Thanks mdeejay)
Libraries for Desire/Nexus builds - http://www.multiupload.com/1UDF24Y28R (Thanks michyprima)
****** WARNING ************ WARNING ************ WARNING ************ WARNING ************ WARNING ******
[I]Release r8.5 - 23/11/2010[/I]
- Reverted my toolchain due to a wierd bug causing increased power drain in r8.4 after calls
- Updated smd_tty - This is still experimental but the Beta had 900+ downloads with largely positive feedback
- Changed default governor to smartass
[I]Release r8.4 - 18/11/2010[/I]
- WARNING from 8.3 still applies, see below.
- Updated my toolchain to latest CodeSourcery one
- Commit messages follow for the rest. Thanks to huanyu for finding most of the patches so I could just git cherry-pick them, and to mdeejay for pointing me to huanyu's git tree.
b02a70d Tweak smartass for better performance
260b0ba Added some extra debug info for vdd_level being set on bootup, and fixed another warning in WiFi driver.
e9c3ac0 Optimized ARM RWSEM algorithm
fea4f78 increase IDLE_TIMEOUT within kgsl_yamato_idle (kgsl_yamato.c)
f248e15 msm: kgsl: Remove support for mmap from the kgsl driver.
031a7f7 [ARM] msm: qsd8k: audio
7304611 cpufreq: interactive: Changes to interactive governor
c8cec4c cpufreq: interactive: Fix potential division by zero
c69e698 msm_kgsl: Optimize TLB flushing
9e35440 msm_kgsl: Move kgsl_sharedmem_init to module load
[I]Release r8.3 - 17/11/2010[/I]
- Added smartass governor (use SetCPU if you want to try it)
- Added sysfs interface for undervolting (see http://forum.xda-developers.com/showthread.php?t=821372)
- Added g-sensor workaround by mdebeljuh & jdivic (http://forum.xda-developers.com/showthread.php?p=9208297#post9208297)
- Merged main tree - WARNING: Includes new camera driver with auto white balance bug (but auto focus/zoom works)
[I]Release r8.2 - 11/11/2010[/I]
- Minor update to enable App2SD again (yes Angry Birds should install without unmounting SD)
- Merged main tree as usual (nothing of immediate use in there though)
[I]Release r8.1 - 07/11/2010[/I]
- Merged main tree again (light sensor changes, lowered verbosity of battery driver, etc)
- Included latest liblights to go with the light sensor changes
- Removed NFS support
- Moved CIFS support to a module
- Built with support for tunneling (GRE), may help those with VPN issues
[I]Release r8 - 30/10/2010[/I]
- MAJOR CHANGES = now closer to main tree
- Removed gauner1986s video driver tweaks (they were causing issues merging the main tree)
- DOES NOT support extended batteries due to the new ace based driver (until I can figure out a fix, best bet for eb users is to catch myself and/or Markinus on IRC over the next week or so and we may be able to test further)
- DOES NOT support Overclocking/Undervolting/AXI My testing shows they provide minimal benefit in day to day use, and tend to cause unpredictable errors that will make troubleshooting remaining issues (like data issues) harder. I may release a kernel with these things when everything is running smoothly, but until then I won't even be running one on my phone.
- Perflocked = You can't even underclock with SetCPU. My reasoning is the same as above.
- Merged main tree (updated battery driver from Desire HD kernel, plus a tweak to help prevent oom errors)
- Updated wifi.mac patch by mdebeljuh (http://forum.xda-developers.com/showthread.php?p=8828147)
- Added PPP patch from http://docs.openmoko.org/trac/ticket/2212 (no this does not fix everything with PPP)
I hope to upload to Rapidshare Links
Here u go
http://www.multiupload.com/5QIHT86TAU
[Kernel][21.09.2010][Overclocking][Undervolting][AXI]EVO base + tweaks
Click to expand...
Click to collapse
so... you come from the future?
jrdaz said:
so... you come from the future?
Click to expand...
Click to collapse
Lol in some countries (eg. Australia) it's already tuesday... So it is possible
pixine786 said:
Here u go
http://www.multiupload.com/5QIHT86TAU
Click to expand...
Click to collapse
Thanks I'd seen that but hadn't taken the time to sign up and figure it out.
MAsterokki said:
Lol in some countries (eg. Australia) it's already tuesday... So it is possible
Click to expand...
Click to collapse
Exactly, it's 36 minutes in to Tuesday here.
damn for some time I was just thinking what is he talking about... why u giving so much importance to time stamp... Let XDA server do things for you...
Life is simple... U making things complicated
Can this kernel only be used with a hd2 desire hd rom or also with other current roms?
hastarin said:
Thanks I'd seen that but hadn't taken the time to sign up and figure it out.
Click to expand...
Click to collapse
Hope u are not angry on me... I didnt even asked ur permission... Sorry Bro
TheWizzard2203 said:
Can this kernel only be used with a hd2 desire hd rom or also with other current roms?
Click to expand...
Click to collapse
ONLY HD2 Desire HD Rom (Beta 2)
TheWizzard2203 said:
Can this kernel only be used with a hd2 desire hd rom or also with other current roms?
Click to expand...
Click to collapse
I have no idea sorry. I updated the original post to indicate this.
you test this build?
or
you post this builds for other people try without securety
hastarin said:
I debated releasing an actual built version of this, rather than just the diff, but here goes...
This is a Kernel I built for my own purposes based on the current EVO kernel (as of this commit) and the diffs guaner1986 and darkstone provided in his Desire HD - Beta 2 build.
It has some minor tweaks to the code provided to enable overclocking with AXI enabled. Undervolting support was already there, from gauner1986.diff, along with audio tweaks and others. darkstones shadow writes and writecombine graphic tweaks are also included.
Use at your own risk if you know how. I won't be answering questions on this and I won't be doing another build in a hurry, I'll leave that to the core folks that really know what they're doing.
What's included:
The kernel (as Image) and needed modules
Latest haret.exe
A new initrd.gz (for use with darkstones Desire HD Beta 2 Build) with a logo.rle as created by Letama (hope he doesn't mind)
Diff of the changes made
Before people ask, and so I don't have to answer, no it is not built for extended batteries (unless the base kernel is and I didn't know about it).
NOTE: I have not tested this with other builds. Try it at your own risk. I don't understand half the code in gauner1986's patch.
Download from Megaupload:
http://www.megaupload.com/?d=Y18CPVVX
or
http://www.multiupload.com/5QIHT86TAU - thanks pixine786
Click to expand...
Click to collapse
Is this thread exclusive for Android Elites out there?
Thanks for a very informative thread for the Noobs.
What do we do with this?
Threads shared should offer support to EVERYONE. otherwise its DISCRIMINATORY.
starting a thread just to show off your skills with Android and not offering guide and help just pisses me off really
jigners said:
Is this thread exclusive for Android Elites out there?
Thanks for a very informative thread for the Noobs.
What do we do with this?
Threads shared should offer support to EVERYONE. otherwise its DISCRIMINATORY.
starting a thread just to show off your skills with Android and not offering guide and help just pisses me off really
Click to expand...
Click to collapse
Where do you see discrimination ?
There are many post on how to update a Kernel.
The dev has compile the kernel for users that don't know how to compile.
I prefer to say thanks to the user to give us the new kernel ..
Iosu
jigners said:
Is this thread exclusive for Android Elites out there?
Thanks for a very informative thread for the Noobs.
What do we do with this?
Threads shared should offer support to EVERYONE. otherwise its DISCRIMINATORY.
starting a thread just to show off your skills with Android and not offering guide and help just pisses me off really
Click to expand...
Click to collapse
If the OP had used smaller words, would that have made you feel better?
jigners said:
Is this thread exclusive for Android Elites out there?
Thanks for a very informative thread for the Noobs.
What do we do with this?
Threads shared should offer support to EVERYONE. otherwise its DISCRIMINATORY.
starting a thread just to show off your skills with Android and not offering guide and help just pisses me off really
Click to expand...
Click to collapse
And posts like yours are why I said I won't answer questions. The information is out there. I had to find it for myself, so can you.
That said, I've linked "know how" in the original post to the wiki:
http://htc-linux.org/wiki/index.php?title=Leo/UpdateKernel#Installing_latest_Linux_kernel_image_.28zImage.29
Should I try this with mattc 1.7 or is there no chance to boot it with this kernel?
Thanks for your work will test.
if OP wanted to publish something that has worked well for him
he should be willing to support the thread not warn those who
have little knowledge to stay away as he wont be answering questions
see my point? that is not in the spirit of community really now is it?
It's working fine. I don't like the first image but better than a white screen. It's overclock to 1113*** . I'll go home later to test WiFi .
Sent from my Desire HD using XDA App
This module is not for end-users. It's only valuable for kernel developers.
Intro
I wrote this module for the purpose of extracting kernel config from our running kernel 2.6.29 in my X8 (an educational purpose).
Instruction
Everyone who wants to try:
Download the module below (only for X8 with latest kernel + baseband 015)
Extract
Push to /system/lib/modules
From adb shell
Code:
insmod /system/lib/modules/x8kconfig.ko
gunzip -c /proc/config.gz > /mnt/sdcard/x8config.txt
Mount USB, open x8config.txt from your sdcard with wordpad
You will see these in some first line:
#
# Automatically generated make config: don't edit
# Linux kernel version: 2.6.29
# Tue Jan 18 23:38:24 2011
#
Click to expand...
Click to collapse
Source was pushed to github: https://github.com/doixanh/X8Features
Licence violation will be discussed later
SE is treating it's end users like s*it as we all can see....
This will pass,only we need to spread the news.
News:Sony is hiding latest open source kernel,does sony afraid or newest source can unlock bootloader.
Because of user rights when qouastion will asked we can only guess whay they will say nothing or they can go to jail.
Sent from my X8 using XDA Premium App
Why don't you take the boot.img from the latest se rom and extract it so you can get the origenal kernel ..
then build a costom one debending on it
That's insane... I've just forwarded it to Polish android board, everyone should know this.
me using your module I obtain it:
# Automatically generated make config: don't edit
# Linux kernel version: 2.6.29
# Sun Jan 30 20:24:17 2011
#
hmm, why cant we use the older kernel to unlock the bootloader?
just asking.
doixanh, are you going to contact http://gpl-violations.org/ those guys?
does the kernel tree compile with the config extracted from the device?
I think the different build dates are not really a good proof that the published archive is not the real one because they probably did multiple builds with different configs. I know that when I tried compiling kconfig support into the previous kernel/baseband it turned out to be useless and had a bunch of undefined config flags compared to the published kernel tree.
Because the configuration is newer you assume changes to source? That's pretty far fetched... Releasing updates on this big scale you don't do last minute changes to code... Gpl said release changes to code. What code is missing / changed?
Sent from my E15i using XDA Premium App
lol i posted this to SE's facebook page and it got deleted in under 5 minutes
http://www.facebook.com/sonyericsson
chewdaniel said:
lol i posted this to SE's facebook page and it got deleted in under 5 minutes
http://www.facebook.com/sonyericsson
Click to expand...
Click to collapse
what did you post? i mean the exact words.
well i said something about them abandoning us X8/10mini customers and making us stuck at 2.1 and that since they don't care about us the community will and asked them to release their code so the devs can work better
it wasn't rude or anything maybe SE just didn't like the idea of ppl developing the software for their phones
I posted this on polish sony ericsson on fb , bcause I have been blocked on english site
Sent from my Arc-X8 using Tapatalk
This is f*cking unbelievable! They were playing with us since they released 2010 products and now we see another thing.
doixanh many thanks to YOU!
They surely should be reported gpl site http://gpl-violations.org but who will do this? I don't want to be rude but YOU know what to say so why don't you do that?
Sent from my E15i using XDA Premium App
chewdaniel said:
lol i posted this to SE's facebook page and it got deleted in under 5 minutes
http://www.facebook.com/sonyericsson
Click to expand...
Click to collapse
I´ve posted similar threads there aswell and the threads got deleted.
I was starting to look at kernel stuff today for my X10 Mini Pro = and also couldn't find the latest kernel on the site.
However I downloaded the x10_x10mini_x8_eclair_2.1.A.0.390 file anyway to have a look - and according to the makefile for this it's
VERSION = 2
PATCHLEVEL = 6
SUBLEVEL = 29
EXTRAVERSION =
NAME = Temporary Tasmanian Devil
So has the kernel actually changed since this release - as this looks like a 2.6.29 to me?
cyttsp_i2c_init: Cypress TrueTouch(R) Standard Product I2C Touchscreen Driver (Built Jan 18 2011 @ 23:43:30) returned 0
got the same text too
Code:
#
# Automatically generated make config: don't edit
# Linux kernel version: 2.6.29
# Tue Jan 18 23:38:24 2011
oisteink said:
Because the configuration is newer you assume changes to source? That's pretty far fetched... Releasing updates on this big scale you don't do last minute changes to code... Gpl said release changes to code. What code is missing / changed?
Sent from my E15i using XDA Premium App
Click to expand...
Click to collapse
It's entirely far fetched, as OP is trying to correlate something that isn't the cause.
The only thing he's proven is someone typed make oldconfig or make menuconfig, there is usually no indication of source code changes in the .config, outside of new kernel config options that may be in the running kernel vs provided defconfig (did you even check? no). The fact that you didn't even mention looking at the actual kernel build timestamp in /proc/version tells me you don't really know what you're doing, it's not in the .config...
Are there any modules that exist on stock but aren't available for compilation from source? Are there any kernel modules that are exporting tainted symbols? (i.e. is /proc/sys/kernel/tainted 0?) That would rule out any use of proprietary or missing modules. Do any of the stock modules export newer versions or kmsg info that isn't in the source? I highly doubt you looked through the source this extensively.
Most production kernel development cycles I've been a part of involve a period of code freeze before the final release. Usually during this period only absolutely show-stopping bugs are fixed and things like debugging and factory/test hardware modules are removed. It is likely that this is what happens at SE.
Do you really think they put relatively untested code in the kernel during that 5 day period from source finalization and production build? Any changes, especially the security measure you speculate were put in, would require extensive testing. Judging by the contributions that SE has provided in AOSP, they test their software and hardware for compliance more than the average vendor. It's illogical to me to assume they've snuck some code in when they spend countless man-hours doing testing and QA.
This type of speculative witch-hunt makes the community look bad, not SE. You need to provide factual evidence of a license violation, not .config file changes.
WARNING: THIS METHOD CAN BE DANGEROUS. DON’T DO ANYTHING IF YOU DO NOT KNOW WHAT YOU DO.
I AM NOT RESPONSIBLE IF YOU TRANSFORM YOUR N1 INTO A BRICK
.38.8 zKernel
This kernel is based on IR+Evervolv.
Recommendation
SmartAssV2 254-1130Mhz
BUGS
test it
DOWNLOAD
.38.8 zKernel #21 :: BFS :: 2011-12-30
Remember to +(Thank) when downloading kernel
Sources #21 (will update when possible): https://github.com/zyr3x/ics-zkernel-passion
Changelog:
2012-01-12:
Include modules : сifs,tun
Enable: DMA, BFQ hierarchical scheduling support
2012-01-07:
Reconfig kernel options
enable AXI
Speed up the GPU ( Quadrent: 3D 340 -> 385; FPS ~9fps -> ~18fps ). Smoother operation CM9.
fix critical bug with bootloop(crash data)
2012-01-02:
rebase all sources on iR
2011-12-30 #21:
update video, gpu, kgsl (ir-kernel)
2011-12-28 #15:
update blk-lib
add / enable sio-iosched
enable cfs-iosched (default)
2011-12-26 #14:
add SmartAss
update CPUStats
update Ondemand
update kernel classes
2011-12-25 #11:
update CPUSET
update POSIX_TIMER
update RCUTINY
2011-12-25 #10:
added CPU governors:
Lazy
InteractiveX
Savaged-Zen
SmartAssV2
Flashing now, will report back with results!
thanks
Does this mean what I think it does?
Are we able to get HW acceleration soon?!
No. This is based off the one included in the ics Tom if I looked correctly.
Sent from my Nexus One using XDA App
zyr3x said:
.38.8 zKernel
2.6.38.8, 256-1036 (base on Evervolv-Perdo-2.1.0p2-passion)
Changelog:
2011-12-25 #11:
update CPUSET
update POSIX_TIMER
update RCUTINY
2011-12-25 #10:
added CPU governors:
Lazy
InteractiveX
Savaged-Zen
SmartAssV2
Click to expand...
Click to collapse
Thank you for sharing. Will this work with MIUI ROM?
eidros said:
Thank you for sharing. Will this work with MIUI ROM?
Click to expand...
Click to collapse
Need test. I don `t know
Where is boot.img? so i can to use with fastboot.
Battery drain on #11 seems a bit faster...a little less lag on app processing but still only problem is the lack of msm 3.0 kernal. Good improvement for the time being
Sent from my Nexus One using XDA App
Forbearance. I think we will find common effort to solve this problem
fjnty5 said:
Battery drain on #11 seems a bit faster...a little less lag on app processing but still only problem is the lack of msm 3.0 kernal. Good improvement for the time being
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
How about battery drain on #14?
---------- Post added at 05:03 PM ---------- Previous post was at 04:53 PM ----------
btw, i did one boot.img http://mup5.com/40393 (for texasice's rom)
u need extract bcm4329.ko and push by yourself.
Thanks OP
File appears to be a zip file, however when I try to install it it does not show up as a zip and I can not install. Is anyone else experiencing this?
NVM.....seems to be correct now.
Quadrant
j00m said:
How about battery drain on #14?
---------- Post added at 05:03 PM ---------- Previous post was at 04:53 PM ----------
btw, i did one boot.img http://mup5.com/40393 (for texasice's rom)
u need extract bcm4329.ko and push by yourself.
Thanks OP
Click to expand...
Click to collapse
.38.8 zKernel #14 vs Tiamat-Drews 2.1.0p3
1157 vs 1077
wait next release...
Works great, but there is one thing I miss... Could you please add SWAP support (so we can use a2sd reswap with DT A2SD?) It would be a great help!
Thanks,
Zeboo
zyr3x said:
.38.8 zKernel #14 vs Tiamat-Drews 2.1.0p3
1157 vs 1077
wait next release...
Click to expand...
Click to collapse
as default or need to use setcpu things? and what are the number? 1157 vs 1077
btw, I made boot.img & split bcm4329.ko from OP for Evervolv-Perdo-2.1.0p3-passion ROM of texasice: http://mup5.com/40767
Quadrant scores.
Sent from my Nexus One using xda premium
ctfrommn said:
Quadrant scores.
Sent from my Nexus One using xda premium
Click to expand...
Click to collapse
thanks.
j00m said:
as default or need to use setcpu things? and what are the number? 1157 vs 1077
btw, I made boot.img & split bcm4329.ko from OP for Evervolv-Perdo-2.1.0p3-passion ROM of texasice: http://mup5.com/40767
Click to expand...
Click to collapse
Max point on SmartAssV2 1036-245
zyr3x said:
Max point on SmartAssV2 1036-245
Click to expand...
Click to collapse
does i need setcpu? or u config as default!
Please give some guide for newbie as me.
I use my soft CKZTools.apk v 1.4.4 ICS Profiles )
Hi guys, a couple days ago, i spent hours sifting through pages of google searches to find the EASIEST stuff about kernel patches. This guide will be updated slowly, be patient! I welcome the help and input from the community, please feel free to pm me (to make sure i get the message ). Let me start off by saying that I will not be able to fix all the problems that you get from patching, but i have no doubt that someone in this awesome community can. So enjoy!
Patching your linux kernel!
Alright guys, i am gonna cover INCREMENTAL patches, these are fairly easy and won't take much of your time. If you plan on doing a more major update, i.e. 2.x --> 3.x, i suggest you go elsewhere because this guide WILL NOT help you.
Another important note, all 3.x updates are incrimental, you cannot skip a patch. Meaning, if i want to patch a 3.0.58 kernel to 3.0.60, i have to patch .58->.59 and then .59->.60. That took me a while to figure out which is why i brought it up early .
LETS GET STARTED!
First, get a nice kernel, one that you know compiles correctly and works, for the most part. Check the makefile, it should be in the root of the directory. Open up the makefile, in my kernel, i see this:
Code:
VERSION = 3
PATCHLEVEL = 0
SUBLEVEL = 63
Ok, it looks like we have a kernel source that's on 3.0.63. Awesome, this should be simple enough. We need 2 patches, one to go up to .64 and the next to .65.
Go HERE and download the .bz2 of what you need. In this case, i am going to download patch-3.0.63-64.bz2 and patch-3.0.64-65.bz2. You'll need to "save link as" to download the files or you can you the lftp command in terminal if you know how to use that. Anyway.
Here is where the terminal fun starts, lets unpack those files so we have the patches. CD into wherever you downloaded the files and run
Code:
bzip2 -dv insertpatchname.bz2
Obviously, you change insertpatchname to your file name. You run that for as many patches you need to do.
Good, now we have the patches. Linux loves us and made it really simple to apply those patches. All you have to do is
Code:
patch -p1 > ~/path/to/the/patch
If you did it right, give you a wall of text telling you that its patching files. NICELY DONE. If you want to confirm that the patch was sucessful, go back to you makefile, you should see that your sublevel is higher. For each additional patch, just repeat the last two steps!
As always, i can't guarantee that these patches won't break compatibility but thats when the fun starts, right?
Wow, nice, you just patched your very own kernel! In the next post, we'll learn how to do the same thing, but instead, we'll cherry-pick those commits from github. PM and Post for any comments, questions, blah, blah. As always, donations are not required but they'll be paying for a new processor to replace my 1.6ghz single core crap. Thanks are appreciated!
Reserved for Github Stuff
I want this one!
Nice, just what I was looking for! Tnx
wantowan2 said:
Nice, just what I was looking for! Tnx
Click to expand...
Click to collapse
No problem, i am happy it was helpful!
Ques:
Say I put the patch in the top of the kernel dir and I cd to the kernel dir, should this work?
Code:
patch -p1 > ~/patch-3.0.49-50
That will work as long as the patch is in ~/
Introduction:
This modification / custom kernel configuration for Pixel and Pixel XL is optimized and made with the focus on bringing several, carefully tuned behind-the-scenes enhancements & adjustments that improves overall critically needed performance, system responsivness and battery life to the highest possible level. The seed to this project can by the way be found here, for anyone that is interested of its origins.
Note: This script is not recommended to be modified or customized by the user.
The latest release can be found here.
Disclaimer:
This is presented as "what if". If this modification screws up or breaks anything for you, I am not the one to be held responsible. It's a free will to try out this kind of changes/modifications/addons/tweaks, just don't blame the inventors for eventual bad results and/or screw-ups.
Features:
Reduced battery consumption
Device specific enhancements for best possible balance between battery life & performance
Enabled, and fully configured, Boeffla generic kernel wakelock blocker
[
Disabled a lot of useless stuff at kernel level (Improves battery life as well as performance)
CPUSet improvements & optimizations
Schedtune tweaks (Improves responsivness)
Power efficiency enhancements
Wide IO block tuning (Reduces the possibility of hiccups, lags and overhead)
Possibly other miscellaneous things I've forgotten to write down here, both big and small.
Requirements/what you need for getting this script fully working:
An unlocked bootloader
Your own specific choice of kernel
Latest Magisk
Busybox for Android NDK Magisk Module by @osm0sis
Patience
Installation/How-To use & abuse:
1) Download the attached ZIP
2) Extract the script
3) Move the script to the following location;
/data/adb/service.d and give the script the following permissions (0755)
4) Reboot your phone, let Android boot to the launcher and let Magisk boot service do its crucial magic (takes a few seconds before the scripts is fully up and running around behind the scenes)
5) Enjoy!
Note: If you still are unsure how to do for making my kernel configuration / modification work & be up and running behind the scenes, then please read @Phalanx7621 phenomenal guide here or check out @Phalanx7621 in-depth video here. The installation method is the same for both the first generation as well as the second generation of Pixels!
Credits:
@nathanchance for his contributions with his Flash Kernel
@franciscofranco for all the information on which kernel wakelocks that is safe to block
@Phalanx7621 for his phenomenal how-to guide
@Lord Boeffla for his awesome generic kernel wakelock blocker
@pkgnex for inspiring me walking into this partially unknown territory from the beginning
@flar2 for his excellent EXKM application and ElementalX Kernel
@osm0sis for his Magisk Busybox module
Everyone that I've forgotten to mention here
Telegram:
If you want to try out betas / previews of my script before they are officially released, or just hangout and chat a little, then join the official Telegram group here
To-Do list:
Optimize and properly tune things even further for best possible balance between battery life, system responsivness and performance
Contributors:
@xFirefly93
Created: 2018-10-08
Last updated: 2019-01-04
Been following your thread over in the Pixel 2 XL forum, nice to have you here
Edit: sorry for stealing the first post btw hehe
EDIT: My changelog dedicated post have exceeded 30000 characters, so I have decided that the changelog will only be included in the respective update posts from now on!
So you all know how the situation is.
shagbag913 said:
Been following your thread over in the Pixel 2 XL forum, nice to have you here
Click to expand...
Click to collapse
I'll do whatever I can on the first generation Pixels for giving you guys & girls the same awesome experience.
And thanks btw.
:highfive:
Update!
v1.1 (Minor release)
- Made a few more (hopefully) battery conserving adjustments to the Sched governor.
Enjoy!
There is no .core folder inside /sbin, do we have to create it ? Edit: reboot solved. Couldn't see it.
Got it installed and I'm thinking it's working. Does the script turn off Core Control ? Just noticed it's off in Ex Kernel Manager , is this by design ?
Core control screenshot
Phalanx7621 said:
There is no .core folder inside /sbin, do we have to create it ? Edit: reboot solved. Couldn't see it.
Got it installed and I'm thinking it's working. Does the script turn off Core Control ? Just noticed it's off in Ex Kernel Manager , is this by design ?
Click to expand...
Click to collapse
Hm, I have not touched the specific tunable that is controlling Core Control.. Maybe it is disabled because of my Sched CPU governor tweak.
Phalanx7621 said:
Core control screenshot
Click to expand...
Click to collapse
xFirefly93 said:
Hm, I have not touched the specific tunable that is controlling Core Control.. Maybe it is disabled because of my Sched CPU governor tweak.
Click to expand...
Click to collapse
I can confirm that the same happens to me.
Thanks for the work!
Phalanx7621 said:
Core control screenshot
Click to expand...
Click to collapse
Old Man Dave said:
I can confirm that the same happens to me.
Thanks for the work!
Click to expand...
Click to collapse
I'll take a look into it later today.
EDIT: Oh snap, I forgot that I have disabled the Core Control tunable in my script. My bad, sorry.
Do you guys want to have it enabled or disabled btw?
xFirefly93 said:
I'll take a look into it later today.
EDIT: Oh snap, I forgot that I have disabled the Core Control tunable in my script. My bad, sorry.
Do you guys want to have it enabled or disabled btw?
Click to expand...
Click to collapse
I mean I'm only concerned with battery life. If you get better battery life with it off, I'm down with that for sure.
Phalanx7621 said:
I mean I'm only concerned with battery life. If you get better battery life with it off, I'm down with that for sure.
Click to expand...
Click to collapse
I will compare how my Marlin / Pixel XL performs with it disabled respectively enabled and see which "solution" that is giving best battery life with less performance tradeoffs, and then I will include the best overall compromise in v1.2 of my kernel configuration / script.
For anyone else interested in this, this is how I went about it:
1) Downloaded Flash Kernel from his thread over here https://forum.xda-developers.com/pixel-xl/development/marlin-flash-kernel-1-00-t3788300
2) Downloaded the latest version of this mod
3) Downloaded the Magisk module required, which you can find by searching Magisk for "busybox" and choosing the "Busybox for android NDK" version
4) Flash that Magisk module, reboot into recovery, flash the Flash kernel (no need to reflash magisk, it's automatic), reboot back into system.
5) Check to make sure Magisk is functioning properly, for me I had to reboot due to an error in the application but that may have been on my end.
6) So now you have Flash kernel and the Magisk module required to be able to properly run this script. Extract the script from the .zip file you downloaded to a folder.
7) Ok so these next steps if you aren't familiar with this stuff could be tricky, but it's actually simple it just sounds tricky. I use Mixplorer for this, I highly suggest using it, it's free and it's on XDA Labs here. https://labs.xda-developers.com/store/app/com.mixplorer But any file explorer w/ root access will do. Inside the folder you extracted the script into there are two versions, choose the Public Release version and copy that file. Navigate to root ( / ) and go to /data/media/0 and paste the file there. The reason for this is you have to change the permissions to allow it to be an executable script and this folder allows that. (there are other ways to do this, FYI but this works just fine for me) You want the permissions to be 755, so it would look like this: (see attachment) To change permissions in Mixplorer, just long press the file and hit the little i (for information) in the upper right. Then click on the permissions you want to change.
8) Now all you have to do is copy that file you just changed the permissions to and paste it into: /sbin/.core/img/.core/service.d | | Now you won't be able to SEE .core unless you have hidden files on, in Magisk it's in the upper right hand corner 3 dot menu. Click Show Hidden. After you paste the file there, reboot and congratulations, you have achieved greatness.
Phalanx7621 said:
.. FYI..
Click to expand...
Click to collapse
Thanks a lot for the in-depth guide! I added your guide to the OP both in this thread and over at my Pixel 2 (XL) thread!
:highfive:
xFirefly93 said:
Thanks a lot for the in-depth guide! I added your guide to the OP both in this thread and over at my Pixel 2 (XL) thread!
:highfive:
Click to expand...
Click to collapse
Oh ok cool, just wanted anybody else to be able to use this awesome mod too, it works wonderfully!
I miss this path on my pixel: /sbin/.core/img/.core/service.d
i'm on last LOS 16.0
moyses said:
I miss this path on my pixel: /sbin/.core/img/.core/service.d
i'm on last LOS 16.0
Click to expand...
Click to collapse
It's there.... I'm on the same rom. You need to start at root and not device storage, as well as show hidden folders
moyses said:
I miss this path on my pixel: /sbin/.core/img/.core/service.d
i'm on last LOS 16.0
Click to expand...
Click to collapse
Use X-plore file manager adn give Root permissions and in settings Show hidden files or folders something.
Update!
v1.2 (Minor release)
- Optimized Sched governor for best balance between performance & battery life
- Reverted pm_freeze_timeout to stock settings
- Raised dirty_ratio to 30
- Some minor script based clean-ups here and there
Enjoy!
xFirefly93 said:
Update!
v1.2 (Minor release)
- Optimized Sched governor for best balance between performance & battery life
- Reverted pm_freeze_timeout to stock settings
- Raised dirty_ratio to 30
- Some minor script based clean-ups here and there
Enjoy!
Click to expand...
Click to collapse
Hi, which release from Public and Maintenance we have to use. Thank you for your hard work.