[KERNEL][SEP.30][AOSP]Bricked-Kernel|2.6.39.4|v0.7|Sweep2Wake|mpdecision|PowerHA L

Search This thread
By:
Advanced…
show-p1984

show-p1984

Inactive Recognized Developer
Jul 30, 2011
3,700
11,805



Bricked-Kernel One X (endeavoru) AOSP (CM10/etc)

The first 100% stable kernel for the HTC One X (endeavoru)
(thx HTC for the screwed source btw, fixed it ^^)
Replaced NVIDIA's strange hotplug manager with my own: tegra_mpdecision
​

Features:

Based upon HTC source
Fixed all stability issues from the HTC source
Fixed all section mismatches
Various other fixes
Sweep2wake
tegra_mpdecision, which completely replaces nvidias hotplug manager (better battery life + performance)
extensive sysfs interface for mpdecision with all the tuneables you want
modified ondemand governor for tegra3 & mpdecision (this is the only recommended governor atm)
fixed sound playback while screen is off
fixed bluetooth toggle with gps active
GPU OC (484Mhz)
Variant free CPU OC for all phones (51 - 1600Mhz)
added init.tegra.post_boot.sh support
Compiled with gcc4.7
fixed max cpufreq resets throughout the kernel
all cores now use the max freq (before: only in singlecore, otherwise -100Mhz)
Undervolting (faux123)
Check the changelog for the rest :)
​

Changelog @ bricked.de​

What is sweep2wake?


How to install?


!!!!IMPORTANT!!!!​
Flash through recovery. But:
Since the htcdev unlock prevents us from flashing the boot partition from recovery, the installer will ONLY INSTALL THE MODULES & disable the HTC screenshot! (needed as a fixup for sweep2wake, use the AOSP screenshot pwr+vol.down instead)
_YOU_ will need to flash the boot.img within the zip (folder: kernel) yourself! (extract it to your desktop so you can use the commands given to you here)
I can't stress enough how important this is. _YOU_ will need to flash it.

How to do that (full guide, if you use the reboot option given to you by the installer you will only need steps 1 & 4-7)
1. Install HTC drivers (how to do that is explained a hundred times all over the web)
2. Reboot
3. in the boot animation, connect your phone to your computer and do:
adb reboot-bootloader
4. You should now see "FASTBOOT USB", if that is the case:
fastboot flash boot %USERPROFILE%\Desktop\boot.img
5. fastboot reboot
6. check with: adb shell uname -a if it says bricked.
7. enjoy ;)

ofc these steps can also be done before the installer is executed from recovery. Just be sure to complete both.

​

Where to complain about errors/bugs?

Please use the Issuetracker for bugs/errors/feature wishes!
Issuetracker @ https://code.google.com/p/bricked/issues/entry
showp1984@googlemail.com
IRC Chat: Freenode IRC #bricked
​

Download:

No Guarantees! If it kills your grandmother or your device, I am NOT responsible! If you understand this:
(If you download, please hit Thanks below my post! Thank you!)

>>> DOWNLOAD <<<
​




Source:



​
 
Last edited:
  • Like
Reactions: eboye, Miha_149, Authorise and 64 others
show-p1984

show-p1984

Inactive Recognized Developer
Jul 30, 2011
3,700
11,805
Battery life
onexbattlife.png


Performance:
onex1500antutu2.png
 
Last edited:
  • Like
Reactions: gregneal, TToivanen, hoanbeck and 16 others
show-p1984

show-p1984

Inactive Recognized Developer
Jul 30, 2011
3,700
11,805
Knowledge base:
(under construction)

tegra_mpdecision manual:
coming soon(tm)


Why only clock with 1.4 Ghz max?
That's not a fix, just a point of opinion. I provide stock or close-to-stock kernel settings in regards to UV/Clocks. Usually I don't take HTC's 'stock' but the manufacturer of the component. In this case the soc, so NVIDIA.
Our stock-phone is clocked with 1.5Ghz single core and 1.4Ghz multicore (as soon as the 2nd core comes up). Usually, whatever you do, you will instantly trigger the second core to come up, if even only for a short time. This would effectively limit the cpu clock speed to 1.4Ghz for that time.
Since I overwrote the clock reduce, our phone will clock with the set max at all times. Which, in this case, is overclocking.
So I just reduced the clock back to it's "stock" setting and please trust me that you won't notice the difference to stock in Benchmarks, UI performance, or anywhere else. Not only because it is only 100Mhz on ONE CORE, but also because that core seldom runs alone and therefore can only use the 1.5Ghz for a very short time.

You are ofc free to clock it back to 1.5Ghz again. Please note that this counts as overclocking and the same rules as undervolting apply to it.


 
Last edited:
  • Like
Reactions: gregneal, TToivanen, ra38 and 10 others
ptr_hamilton

ptr_hamilton

Senior Member
Aug 1, 2010
1,320
583
Woooow! Coming from neo's v7 which is stable, pretty fast and is supposed to have good battery also (as far as I experienced with former versions) .

But I have NEVER seen a HOX kernel that has so many 51mhz cpu times w/o lags.
This kernel is pure awesomeness, really a new feeling how cold a HOX can be and i bet the battery life will be outstanding :D

Good to have you back mate
Cheers Pete
 
  • Like
Reactions: show-p1984
show-p1984

show-p1984

Inactive Recognized Developer
Jul 30, 2011
3,700
11,805
ptr_hamilton said:
Woooow! Coming from neo's v7 which is stable, pretty fast and is supposed to have good battery also (as far as I experienced with former versions) .

But I have NEVER seen a HOX kernel that has so many 51mhz cpu times w/o lags.
This kernel is pure awesomeness, really a new feeling how cold a HOX can be and i bet the battery life will be outstanding :D

Good to have you back mate
Cheers Pete
Click to expand...
Click to collapse

Well here is the magic wand I used:
https://github.com/showp1984/bricked-endeavoru/blob/exp/arch/arm/mach-tegra/tegra_mpdecision.c
 
  • Like
Reactions: aman360elite, hassan89, r0cafella and 1 other person
Laurentius26

Laurentius26

Inactive Recognized Developer
Nov 22, 2005
7,970
1,151
@show-p1984,

Earlier tonight I flashed repacked Bricked_onex_v0.3 for CyanogenMod 10 Nightlies - 4.1.1 by TeamNDVRu.
@First impression all is working perfect; wifi, bluetooth, compass, gps and the rom flies, no delays in end call it's just wonderful. :D

Going to update asap LoL, thanks for your hard work. :)
 
You must log in or register to reply here.

Similar threads

mike1986.
[ROM] Android Revolution HD 33.1 | High Quality & Performance | Sense 5 | 4.18.401.3
Replies
50K
Views
9M
C
cmaz
show-p1984
[KERNEL][SEP.30]Bricked-Kernel|2.6.39.4|v0.7|Sweep2Wake|mpdecision|stickyf req
Replies
2K
Views
339K
frankcck
frankcck
X
  • Poll
[KERNEL][13/09/13][306|188v4][3.xx][AOSP & SENSE4][S2W][GAMING][BATTERY][UV]XM-Kernel
Replies
7K
Views
874K
kassaaam
kassaaam
faux123
[Kernel] Kitkat CM (015) Hybrid (UV/FastCharge/S2w/Intelliplug/Intelliactive)[Jun-01]
Replies
7K
Views
1M
G
Grado33
LorD ClockaN
[ROM] [24JUL] [AOKP] IceColdJelly422 - 3.8 - JellyBean 4.2.2_r1.2
Replies
17K
Views
2M
K
kyhuu007

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 67
    show-p1984
    show-p1984



    Bricked-Kernel One X (endeavoru) AOSP (CM10/etc)

    The first 100% stable kernel for the HTC One X (endeavoru)
    (thx HTC for the screwed source btw, fixed it ^^)
    Replaced NVIDIA's strange hotplug manager with my own: tegra_mpdecision
    ​

    Features:

    Based upon HTC source
    Fixed all stability issues from the HTC source
    Fixed all section mismatches
    Various other fixes
    Sweep2wake
    tegra_mpdecision, which completely replaces nvidias hotplug manager (better battery life + performance)
    extensive sysfs interface for mpdecision with all the tuneables you want
    modified ondemand governor for tegra3 & mpdecision (this is the only recommended governor atm)
    fixed sound playback while screen is off
    fixed bluetooth toggle with gps active
    GPU OC (484Mhz)
    Variant free CPU OC for all phones (51 - 1600Mhz)
    added init.tegra.post_boot.sh support
    Compiled with gcc4.7
    fixed max cpufreq resets throughout the kernel
    all cores now use the max freq (before: only in singlecore, otherwise -100Mhz)
    Undervolting (faux123)
    Check the changelog for the rest :)
    ​

    Changelog @ bricked.de​

    What is sweep2wake?


    How to install?


    !!!!IMPORTANT!!!!​
    Flash through recovery. But:
    Since the htcdev unlock prevents us from flashing the boot partition from recovery, the installer will ONLY INSTALL THE MODULES & disable the HTC screenshot! (needed as a fixup for sweep2wake, use the AOSP screenshot pwr+vol.down instead)
    _YOU_ will need to flash the boot.img within the zip (folder: kernel) yourself! (extract it to your desktop so you can use the commands given to you here)
    I can't stress enough how important this is. _YOU_ will need to flash it.

    How to do that (full guide, if you use the reboot option given to you by the installer you will only need steps 1 & 4-7)
    1. Install HTC drivers (how to do that is explained a hundred times all over the web)
    2. Reboot
    3. in the boot animation, connect your phone to your computer and do:
    adb reboot-bootloader
    4. You should now see "FASTBOOT USB", if that is the case:
    fastboot flash boot %USERPROFILE%\Desktop\boot.img
    5. fastboot reboot
    6. check with: adb shell uname -a if it says bricked.
    7. enjoy ;)

    ofc these steps can also be done before the installer is executed from recovery. Just be sure to complete both.

    ​

    Where to complain about errors/bugs?

    Please use the Issuetracker for bugs/errors/feature wishes!
    Issuetracker @ https://code.google.com/p/bricked/issues/entry
    showp1984@googlemail.com
    IRC Chat: Freenode IRC #bricked
    ​

    Download:

    No Guarantees! If it kills your grandmother or your device, I am NOT responsible! If you understand this:
    (If you download, please hit Thanks below my post! Thank you!)

    >>> DOWNLOAD <<<
    ​




    Source:



    ​
    View
    19
    show-p1984
    show-p1984
    Battery life
    onexbattlife.png


    Performance:
    onex1500antutu2.png
    View
    18
    show-p1984
    show-p1984
    drivenby said:
    You are entitled to your opinion as a paying customer....oh wait you didn't pay him a single cent D:

    and he is doing this for free ... Please don't act like an ungrateful kid and be thankful you even got the kernel in the first place.

    We don't need this types of comment here
    Click to expand...
    Click to collapse

    Considering that I made the initial source even stable (since the HTC source was just rebooting every 20 seconds with kernel panics) and that I introduced tegra_mpdecision which is to my knowledge the most accurate alternate hotplug solution actually caring about the lp core, I do see his point. [/sarcasm]

    Yes I have neglected this kernel. At first because there was nothing new to do except some useless updates you might see on other kernels (like merging linux upstream patches containing new pci device support, or power-pc stuff, or 64bit stuff which we all don't even use). Then because I needed it for KControl testing on IceCreamSandwhich.
    It will be continued. Soon. If he moves on to the One he shouldn't care eitherway :p

    I think people often underestimate that writing NEW code is actually more time consuming than doing 50 cherry picks and updating the kernel with some useless stuff. Also writing NEW code is far more fun.
    View
    17
    show-p1984
    show-p1984
    0.7 @ op.
    View
    13
    show-p1984
    show-p1984
    Knowledge base:
    (under construction)

    tegra_mpdecision manual:
    coming soon(tm)


    Why only clock with 1.4 Ghz max?
    That's not a fix, just a point of opinion. I provide stock or close-to-stock kernel settings in regards to UV/Clocks. Usually I don't take HTC's 'stock' but the manufacturer of the component. In this case the soc, so NVIDIA.
    Our stock-phone is clocked with 1.5Ghz single core and 1.4Ghz multicore (as soon as the 2nd core comes up). Usually, whatever you do, you will instantly trigger the second core to come up, if even only for a short time. This would effectively limit the cpu clock speed to 1.4Ghz for that time.
    Since I overwrote the clock reduce, our phone will clock with the set max at all times. Which, in this case, is overclocking.
    So I just reduced the clock back to it's "stock" setting and please trust me that you won't notice the difference to stock in Benchmarks, UI performance, or anywhere else. Not only because it is only 100Mhz on ONE CORE, but also because that core seldom runs alone and therefore can only use the 1.5Ghz for a very short time.

    You are ofc free to clock it back to 1.5Ghz again. Please note that this counts as overclocking and the same rules as undervolting apply to it.


    View

New posts