Database Develop

[Q] About the ~200 line Linux kernel patch that does wonders

Hello, guys!
I guess most of you know about this "magic patch" that significantly boosts Linux speed. It's going to be merged in the 2.6.38 branch and it's shipping with Ubuntu Natty too. But this kernel patch can be applied to a previous kernel as well, just rebuilding it with this 224 magical lines of code.
What I wanted to know is if it's possibile to rebuild our kernels with this patch, if it is already, or if it's possibile but won't have significant boosts on Android devices.
You may read more about this on Phoronix. On the 2nd page there are video demos for lazy ones!

This has been discussed here twice &found not to help because we dont use harddisk.
Sent from my GT-I9000 using XDA App

was it "proven" or "theorized" ?

You can look it up here in dev. Search
Sent from my GT-I9000 using XDA App

ragin said:
This has been discussed here twice &found not to help because we dont use harddisk.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Thank you, but can you please link the thread with this discussion? I can't seem to find it. Also, this patch regards CPU, not hard disks.

this patch will be officially introduced in the 2.6.38 kernel..
also, this kernel will have about 50% more speed increase, due to the 200 lines patch and another issue resolved after it .. in general the upcoming kernel will be blazingly fast !!
there is a script that tries to do the same as the patch for earlier kernels. which I use on my Ubuntu laptop, and yes major performance increase !!
I tried to apply it to my previous phone (HTC Hero), but didn't work. I also asked Cyanogen on his twitter, but didn't care to give me an answer..
finally I gave up, and decided to wait for the next Android version that will have the 2.6.38 in the future..

MaXo64 said:
this patch will be officially introduced in the 2.6.38 kernel..
also, this kernel will have about 50% more speed increase, due to the 200 lines patch and another issue resolved after it .. in general the upcoming kernel will be blazingly fast !!
there is a script that tries to do the same as the patch for earlier kernels. which I use on my Ubuntu laptop, and yes major performance increase !!
I tried to apply it to my previous phone (HTC Hero), but didn't work. I also asked Cyanogen on his twitter, but didn't care to give me an answer..
finally I gave up, and decided to wait for the next Android version that will have the 2.6.38 in the future..
Click to expand...
Click to collapse
I'm using that script too on Maverick! I don't think there should be a significant increase in responsiveness if you apply it on high-end systems, but our SGS might benefit from it (as my old dual core system).
You say it didn't work on your Hero, but were there any errors in dmesg or you didn't find any significant change in speed?

thunderteaser said:
I'm using that script too on Maverick! I don't think there should be a significant increase in responsiveness if you apply it on high-end systems, but our SGS might benefit from it (as my old dual core system).
You say it didn't work on your Hero, but were there any errors in dmesg or you didn't find any significant change in speed?
Click to expand...
Click to collapse
dmesg should no difference. the script just showed a lot of errors.
I tried the "non-Ubuntu" version as described in Webupd8, but still similar errors.
I guess Android place the kernel differently from Linux desktops.

I might be mistaken, but SO kernel uses its. And haven't really noticed any difference with or without it.

MaXo64 said:
this patch will be officially introduced in the 2.6.38 kernel..
also, this kernel will have about 50% more speed increase, due to the 200 lines patch and another issue resolved after it .. in general the upcoming kernel will be blazingly fast !!
there is a script that tries to do the same as the patch for earlier kernels. which I use on my Ubuntu laptop, and yes major performance increase !!
I tried to apply it to my previous phone (HTC Hero), but didn't work. I also asked Cyanogen on his twitter, but didn't care to give me an answer..
finally I gave up, and decided to wait for the next Android version that will have the 2.6.38 in the future..
Click to expand...
Click to collapse
please don't spread incorrect facts:
* the "automated per tty task groups" (or autogroup) patch - by using cgroups (in CFS - the cpu scheduler) and thus isolating several taks from each other, giving them dedicated slices of cpu power - allows the system to be more responsive under load if there is a kind of cpu hog (task producing much load)
* the speed increase is due to Nick Piggin's VFS changes and Andrea Arcangeli & Mel Gorman's Transparent Hugepages (THP) support (and of course lots of other changes)
dupel said:
I might be mistaken, but SO kernel uses its. And haven't really noticed any difference with or without it.
Click to expand...
Click to collapse
that's correct: - "sched patch : automated per tty task groups (system more smooth and responsive) (v3(since 4_3) and v4(since 4_4))"
so you tried SO kernel with the patch applied and once reverted ?
but - yeah, I got you: I'm myself running a heavy patched 2.6.37 kernel with transparent hugepages, CFS autogroup, etc. enabled - and it certainly can play off its advantage most noticably during heavy system load

zacharias.maladroit said:
that's correct: - "sched patch : automated per tty task groups (system more smooth and responsive) (v3(since 4_3) and v4(since 4_4))"
so you tried SO kernel with the patch applied and once reverted ?
but - yeah, I got you: I'm myself running a heavy patched 2.6.37 kernel with transparent hugepages, CFS autogroup, etc. enabled - and it certainly can play off its advantage most noticably during heavy system load
Click to expand...
Click to collapse
So, please, correct my noobiness, isn't Android using TTY shells? If it's not than I understand why this patch can't be applied, but if it is, rebuilding a kernel with just 200 lines more is no big deal and we all could benefit from it. It's not very common for Android to be under heavy load but hey, it's going to be default in 2.6.38, so why not?

There is a better patch :
blog.internetnews.com/skerner/2010/11/forget-200-lines-red-hat-speed.html
But I don't know if android uses shells.

Protocamlann said:
There is a better patch :
blog.internetnews.com/skerner/2010/11/forget-200-lines-red-hat-speed.html
But I don't know if android uses shells.
Click to expand...
Click to collapse
Yes, that's exactly the script I was talking about a few posts ago. On my system running 2.6.35, I did not rebuild the kernel with the "patch of wonders" but applied this script. But as you may have read, it acts in userspace which is slightly different in Android (as far as I know it's not using the same environment variables and I don't know about any ~/.bashrc equivalents, but again correct me if I'm wrong), that's why a kernel-oriented patch would be more suitable.

* well, actually newer revisions of that patch don't make use of ttys but of the task session
so basically it seems to create separate groups for each task (or program for simplicity's sake)
(source)
I'm also not sure if current Android kernel revisions use CFS at all ("Android versus Linux?")
laststufo has the autogroup patch included in his SO Kernel but I don't know how to measure its effect ... (whether it makes any difference)
* other options to improve interactivity would be to use Lennart Poettering's bash-approach (the script), like MaXo64 already posted: link
since Android uses Bourne Shell (sh) instead of BASH the script might need to be rewritten
* if it's stable enough on the SGS - yet another option would be to use Con Kolivas BFS

thunderteaser said:
Yes, that's exactly the script I was talking about a few posts ago. On my system running 2.6.35, I did not rebuild the kernel with the "patch of wonders" but applied this script. But as you may have read, it acts in userspace which is slightly different in Android (as far as I know it's not using the same environment variables and I don't know about any ~/.bashrc equivalents, but again correct me if I'm wrong), that's why a kernel-oriented patch would be more suitable.
Click to expand...
Click to collapse
well, you could rewrite that script that it is run as a init-script (afaik in /system/init.d/ )
besides that:
there are stripped down (smaller) versions of bash 4.1* that are known to work on CM6 and the HTC Hero
so it should be a possibility to use that script on stock roms, too
if you can install busybox & root it, there also should be the possibility to install bash

zacharias.maladroit said:
* well, actually newer revisions of that patch don't make use of ttys but of the task session
so basically it seems to create separate groups for each task (or program for simplicity's sake)
(source)
I'm also not sure if current Android kernel revisions use CFS at all ("Android versus Linux?")
laststufo has the autogroup patch included in his SO Kernel but I don't know how to measure its effect ... (whether it makes any difference)
* other options to improve interactivity would be to use Lennart Poettering's bash-approach (the script), like MaXo64 already posted: link
since Android uses Bourne Shell (sh) instead of BASH the script might need to be rewritten
* if it's stable enough on the SGS - yet another option would be to use Con Kolivas BFS
Click to expand...
Click to collapse
It seems you're very well informed, so thanks for the infos you're posting!
I'm not a coder, though, so I hope a kernel developer could pick this up and go for BFS. You said laststufo already implemented this patch in his kernel, so that's really good! We should just find a way of testing its effectiveness.
zacharias.maladroit said:
well, you could rewrite that script that it is run as a init-script (afaik in /system/init.d/ )
besides that:
there are stripped down (smaller) versions of bash 4.1* that are known to work on CM6 and the HTC Hero
so it should be a possibility to use that script on stock roms, too
if you can install busybox & root it, there also should be the possibility to install bash
Click to expand...
Click to collapse
Yes, I've also seen bash shipping with some ROMs, so it's definitely possibile, though as I said before, I'm no coder...

thunderteaser said:
It seems you're very well informed, so thanks for the infos you're posting!
I'm not a coder, though, so I hope a kernel developer could pick this up and go for BFS. You said laststufo already implemented this patch in his kernel, so that's really good! We should just find a way of testing its effectiveness.
Click to expand...
Click to collapse
I'm a kernel-dev for linux-kernels so I got to know & learned to cherish them
just stumbled over a thread in the Epic 4G forum
for reference: [Q] [REQ] Galbraith Patch worked into kernals?

zacharias.maladroit said:
I'm a kernel-dev for linux-kernels so I got to know & learned to cherish them
Click to expand...
Click to collapse
You really are? That's great! So why don't you join laststufo to try maximizing the impact of his implemented "patch of wonders"? As I try to keep up with your techical chatting it seems I really can't do more than asking you to help!
zacharias.maladroit said:
just stumbled over a thread in the Epic 4G forum
for reference: [Q] [REQ] Galbraith Patch worked into kernals?
Click to expand...
Click to collapse
Uhm, so it seems BFS isn't stable on our hardware, pretty bad.

[krn.modules] intellidemand governor for Arc / Arc S stock Kernel (ICS)

Upon request from fellow member ascariz on the smartassV2 governor, I've compiled intellidemand module for Arc 4.0.3 stock kernel.
Since the firmware I use is the Arc S one (ICS 4.0.3) - I believe this module will also work for Arc S.
To fully configure / install the module, please check this page for a similar module I did for X10 back in the days - page.
Some things are different, but if you want to hand customize all possible parameters after phone starts up, the path to check is
Code:
/sys/devices/system/cpu/cpu0/cpufreq
Download:
Use it at your own risk!
cpufreq_intellidemand_arc_ics.zip
Enjoy!

Awesome. Not trying to be greedy but can we have BoostedAssV2 too ? xD

viulian said:
Upon request from fellow member ascariz on the smartassV2 governor, I've compiled intellidemand module for Arc 4.0.3 stock kernel.
Since the firmware I use is the Arc S one (ICS 4.0.3) - I believe this module will also work for Arc S.
To fully configure / install the module, please check this page for a similar module I did for X10 back in the days - page.
Some things are different, but if you want to hand customize all possible parameters after phone starts up, the path to check is
Code:
/sys/devices/system/cpu/cpu0/cpufreq
Download:
Use it at your own risk!
cpufreq_intellidemand_arc_ics.zip
Enjoy!
Click to expand...
Click to collapse
OMG. you really do it?! tq mate!

After a day of testing, I'm switching back to smartassV2.
With smartassV2:
a) the time in state shows me about 16-17% at 1Ghz, and the others at 122MHz. Intermediate frequences are rarely used.
b) battery was about 40% at the end of the day with my usage (4 email accounts doing sync at 15 minutes - I'm not using push, but k9 connects) - also half of the day in an area where 3G signal is weak and phone swiches back and forth.
With intellidemand:
a) the time in state is 6% for 1GHz which might look better in comparison with smartassV2.
BUT:
b) the phone is sluggish and you can feel it needs a bit of time (1 second ?) to pick up speed, UI animations are choppy.
c) it does make use of the intermediate frequencies - but battery was about 20% when I got home, identical usage as previous day with smartassV2.
In both cases, screen was always kept at 25%.
Now my conclusion is that:
a) intermediate (but high) frequencies have similar battery usage as maximum frequency.
b) spending more time in an intermediate frequency makes things slower to finish and thus, based on point a) drains battery more.
Also, the code of intellidemand is more complex (.ko size is +20Kb more) as opposed to smartassV2 - and thus I guess it also takes more time (energy) to compute the correct frequency. In itself, a complex algorithm to compute the next state takes its toll.
smartassV2 does perform better with my usage pattern - and I'm curious why this governor is claimed to be advanced I mean algorithmically it surely is, but phone is more sluggish + more battery drain (not significant, but about 20% in my basic, 1 day test).
I will focus my attention on other *ass governors

flashable intellidemand. auto load on startup. all credit to viulian.

ascariz said:
flashable intellidemand. auto load on startup. all credit to viulian.
Click to expand...
Click to collapse
Can you make a flashable smartassv2 too ?

Dark Fable said:
Can you make a flashable smartassv2 too ?
Click to expand...
Click to collapse
errr...im not a module compiler like viulian. honestly, i dunno. but to make it autoload on boot & flashable, yes, as long as i have that .ko file.

ascariz said:
errr...im not a module compiler like viulian. honestly, i dunno. but to make it autoload on boot & flashable, yes, as long as i have that .ko file.
Click to expand...
Click to collapse
The .ko was already made by viulian, here ya go.

Dark Fable said:
The .ko was already made by viulian, here ya go.
Click to expand...
Click to collapse
this is intellidemand and smartassv2 modules that you can load in 2 way.
1) for those who use stock kernel that not support init.d, use script manager to load MODULELOADER script at start up. after flash, browse at system/etc/init.d folder and you will find the script.
2) for those who use kernel with init.d supported (e.g. Cobrato kernel), do nothing. just flash it and you ready to go.

ascariz said:
this is intellidemand and smartassv2 modules that you can load in 2 way.
1) for those who use stock kernel that not support init.d, use script manager to load MODULELOADER script at start up. after flash, browse at system/etc/init.d folder and you will find the script.
2) for those who use kernel with init.d supported (e.g. Cobrato kernel), do nothing. just flash it and you ready to go.
Click to expand...
Click to collapse
Doesn't work man. :/ The new governors aren't showing up in No Frills CPU..using Cobrato's kernel.

First you must use the stock kernel from Sony's official 4.0.3 release for Arc S (even if having the Arc).
Any other kernel will not work ... (or very slim chances to work).
Second, please check using Module Loader app (but only activate the boot time loading of the module after you are sure the things work).

viulian said:
First you must use the stock kernel from Sony's official 4.0.3 release for Arc S (even if having the Arc).
Any other kernel will not work ... (or very slim chances to work).
Second, please check using Module Loader app (but only activate the boot time loading of the module after you are sure the things work).
Click to expand...
Click to collapse
I have the ARC S lol, and Cobrato's kernel is Stock 4.0.3 kernel with init.d support.
http://forum.xda-developers.com/showthread.php?t=1591279
Hmm...I thought you didnt have to use module loader for the flashable zips ? :/ Because the module loader shows 'Starting modules...' in the middle of any game (Like Temple Run) and it begins to lag horribly, this pisses my friends off. I want to show them how great a phone Arc/S is. :/

Ok, if it has the same version number then it will load the modules ok (as well as having the same binary kernel image).
I think the OS kills Module Loader to regain some memory, then starts it back when memory level gets better (kills it when game / heavy app starts, then as memory becomes available, it starts it back). But Module Loader has a bug and when started also loads the modules
Another solution is to use Script Manager ( http://www.androidsoftware.us/Applications/Script-Manager.html ) to run a script at boot (a small script that just do the insmod).
Hope it helps...

viulian said:
Ok, if it has the same version number then it will load the modules ok (as well as having the same binary kernel image).
I think the OS kills Module Loader to regain some memory, then starts it back when memory level gets better (kills it when game / heavy app starts, then as memory becomes available, it starts it back). But Module Loader has a bug and when started also loads the modules
Another solution is to use Script Manager ( http://www.androidsoftware.us/Applications/Script-Manager.html ) to run a script at boot (a small script that just do the insmod).
Hope it helps...
Click to expand...
Click to collapse
Thank you for your quick response. [: I know about script manager, can you please provide me with the script to use with it for the modules and a how to ? If not too much trouble that is.
Nvm, got it, thanks.

Dark Fable said:
Doesn't work man. :/ The new governors aren't showing up in No Frills CPU..using Cobrato's kernel.
Click to expand...
Click to collapse
err...it should work man..i used JJ hybrid rom, and the modules shows up in the rom control..maybe you should try app other than no frills..

[MOD] MultiROM (sharing kernel)

I found the bug with not isolating kernel in additional roms after posting multirom here. Unfortunately I havent solved it yet. I decided to not delele this project because the rest of this works. This is useful who want to have similar rom in on tab. For example to test apps. Sorry for inconvience.
this is beta release. for p900 only.
I'll write full instruction later. For full description see http://forum.xda-developers.com/showthread.php?t=2011403
I'm not sure that everything is stable, so I dont publish source code. I dont want to distribute buggy sources. thanks for understanding.
for stock firmware only. for now. use stock frimware as primary. you can flash cm as additional.
Installation:
1. https://yadi.sk/d/RVXpEgc6c4GKo - this is modded recovery. flash via odin
2. https://yadi.sk/d/CHl8wTYYc4GMZ - patched kernel. (patched my 1.3 pro kernel)
https://yadi.sk/d/D2riVhEgc4GPP - multirom main program
flash through modded recovery patched kernel and multirom.
uninstallation:
https://yadi.sk/d/jc4uxZeCc4GRb - flash this uninstaller through recovery, then flash original twrp
known issues:
- 1920x1200 resolution in twrp
- in List Roms installed roms dont shown
- in multirom boot menu touchscreen downt work. use buttons (vol-,vol+,power)
multirom apk from play store doesnt support this release.

reserved

more reserved

bonuzzz said:
this is beta release. for p900 only.
I'll wrote full instruction later. For full description see http://forum.xda-developers.com/showthread.php?t=2011403
I'm not sure that everything is stable, so I dont publish source code. I dont want to distribute buggy sources. thanks for understanding.
Click to expand...
Click to collapse
I saw earlier that you had plans for this, but I didn't expect it to happen this quickly.
Anyway, great initiative.

WOW
@bonuzzz,
nice to see you here. Actually I bought this high end class tablet because of its specifations and over standarts. Still is the most powerful tablet in market.. But somehow it always lacked development and support of developers. Recently maybe the price is dropped so it started make owners smile little bit.
I was almost giong to change it, but still there is no powerful alternate..
I would like to be a tester of multiboot. because I would love to see ubuntu desktop in this tablet.
Thank you!

m_carleone82 said:
@bonuzzz,
nice to see you here. Actually I bought this high end class tablet because of its specifations and over standarts. Still is the most powerful tablet in market.. But somehow it always lacked development and support of developers. Recently maybe the price is dropped so it started make owners smile little bit.
I was almost giong to change it, but still there is no powerful alternate..
I would like to be a tester of multiboot. because I would love to see ubuntu desktop in this tablet.
Thank you!
Click to expand...
Click to collapse
it's not so difficult to run ubuntu desktop here, but it wiil be very big problem with drivers. I thought about ubuntu, but now I'm not going to have a deal with it. I advice you to look linux deploy

Great job
bonuzzz said:
it's not so difficult to run ubuntu desktop here, but it wiil be very big problem with drivers.
Click to expand...
Click to collapse
Here are some drivers for the GPU. I will look into it.
http://malideveloper.arm.com/develop-for-mali/features/mali-t6xx-gpu-user-space-drivers/

ESmazter said:
Great job
Here are some drivers for the GPU. I will look into it.
http://malideveloper.arm.com/develop-for-mali/features/mali-t6xx-gpu-user-space-drivers/
Click to expand...
Click to collapse
If you could get it working it would be great.

arcadia2uk said:
If you could get it working it would be great.
Click to expand...
Click to collapse
I'm currently having a lot of work with multirom, so I think I'll not have time to deal with ubuntu

bonuzzz said:
I'm currently having a lot of work with multirom, so I think I'll not have time to deal with ubuntu
Click to expand...
Click to collapse
My appreciation was actually meant for ESmazter saying: I will look into it

oops, i haven't noticed esmazter's phrase

I found the bug with not isolating kernel in additional roms after posting multirom here. Unfortunately I havent solved it yet. I decided to not delele this project because the rest of this works. This is useful who want to have similar rom in on tab. For example to test apps.

bonuzzz said:
I found the bug with not isolating kernel in additional roms after posting multirom here. Unfortunately I havent solved it yet. I decided to not delele this project because the rest of this works. This is useful who want to have similar rom in on tab. For example to test apps.
Click to expand...
Click to collapse
I was still hoping to get the minor issues resolved, notably the issue with Rom's installer are not shown in the installed ROM's section.

Any possibility of porting this to Galaxy Note 10.1 (2014)? The hardware is almost exactly identical. Really like your work, keep it up!

hhairplane said:
Any possibility of porting this to Galaxy Note 10.1 (2014)? The hardware is almost exactly identical. Really like your work, keep it up!
Click to expand...
Click to collapse
I dont have any plans to port to other devices. It doesnt fully working and I dont have any progress with it...

Do you mean the first (pre multirom install ) flashed rom kernal is the only kernal that boots regardless of the chosen rom, is multirom a separate bootloder that is chainloaded by the original bootloader? Does multirom have a config file describing the various kernals with different filenames if so can it be manually edited? Does multirom mount emulated system partition images or are their actual multiple prexisting system partions in the mbr that multirom can choose from ? What would quilify as similar roms, stock and omni are they similar enouph ?

brock28 said:
Do you mean the first (pre multirom install ) flashed rom kernal is the only kernal that boots regardless of the chosen rom, is multirom a separate bootloder that is chainloaded by the original bootloader? Does multirom have a config file describing the various kernals with different filenames if so can it be manually edited? Does multirom mount emulated system partition images or are their actual multiple prexisting system partions in the mbr that multirom can choose from ? What would quilify as similar roms, stock and omni are they similar enouph ?
Click to expand...
Click to collapse
I dont recommend to use this multirom because it has the bug with sharing kernel. So you need to use similar roms as primary and as additional. I dont have an idea how to solve it at this moment.

TheDreamer Kernel Only 64bit

Warning: Use this on you Own Risk
Features:
S2W D2W
Stereo Call Record
GPU Tweak
NO Write Protection for System Partition
AWB LCD Custom Color for .Rec 709 Profile
Few little Code Changes
How to:
Load boot.img into fastboot folder
run this command:
"fastboot boot thedreamer-Desire510-64bit.img"
When the Device Boot UP and is Stable
Flash the boot.img with:
"Fastboot flash boot thedreamer-Desire510-64bit.img​
Download:
http://forum.xda-developers.com/devdb/project/?id=8179#downloads
Source:
GitHub
I Give no Support i make this Kernels Only for me and post it for other 64bit MSM8919 User to Use.
I Integrate only my Wishes
XDA:DevDB Information
TheDreamer, Kernel for the HTC Desire 510
Contributors
Thestealth2, thestealth2, RBHeromax
Source Code: https://github.com/thestealth131205/HTC_Desire_510_64bit
Kernel Special Features:
Version Information
Status: Stable
Stable Release Date: 2015-02-10
Created 2015-02-10
Last Updated 2015-02-10

I'd love to try it. Is there a link to download it please?

Burtrum57 said:
I'd love to try it. Is there a link to download it please?
Click to expand...
Click to collapse
thanks for the source it coould prove useful in compiling a custom rom for the 64bit i may have to re sync the cm11 repo and give it a shot..
could you also provide a link to the boot.img so we dont have compile the kernel lol.. cheers..

excuse me if i sound stupid,but what is "AWB LCD Custom Color for .Rec 709 Profile" actually? is it actual modified screen colors or is it just the custom kcal driver?

Kcal driver. For Rec. 709 Calibration. My display is calibrated with a Colorimeter.
Download is in First Post
Sent from my HTC Desire 510 using XDA Free mobile app

Thestealth2 said:
Kcal driver. For Rec. 709 Calibration. My display is calibrated with a Colorimeter.
Download is in First Post
Sent from my HTC Desire 510 using XDA Free mobile app
Click to expand...
Click to collapse
do you remember which file you modified for the calibration? i would like to apply it to my kernel,i dont wanna bug you :silly:

See source and merge with youre source

Thestealth2 said:
See source and merge with youre source
Click to expand...
Click to collapse
i build for the 32bit,i cant merge a 3.10 kernel with a 3.4 one :silly:

I write you next days a pn. Have no time at the moment.
You can push a 64 bit stock kernel to git an the push my source than can you see all changes. ?

Just a question...
Exactly which toolchain you use to compile??

I'm about ready to flash your kernel - thestealth131205 I'll update after i get my flash on.

Thestealth2 said:
Features:
NO Write Protection for System Partition
AWB LCD Custom Color for .Rec 709 Profile
Few little Code Changes
Download:
http://www.dhm-server.de/thedreamer-Desire510-64bit.img
Source:
GitHub
Click to expand...
Click to collapse
Thank you for your kernel, have been using it for a month (on my EU) and it works very well!
However, could you make some progress please...
As it is seen on this forum your work is the only one for 64bit. So, could you consider some suggestions?
Namely in their 32 verisons of modded kernels developpers write here about improving screen touch responsiveness and removing HTC's backdoor "debugging" access... How about it?

download link unavailable

See first Post

RE: THEDREAMER 64 bit
Thestealth2 said:
See first Post
Click to expand...
Click to collapse
Last I touched base/read with you and RBHEROMAX, if I understood correctly, you were going to be changing something so I've been trying to remain patient and wanted to inquire about this. I picked up a Samsung Galaxy S5 Sport (sprint) all stock to entertain myself with. LOL. I have the utmost respect for you and Rbheromax, I'd like to thank you again for your dedication and time put into this project and the respect and patience you give to everyone that asks you questions on any level. You are very special individuals giving the gift of knowledge to all that seek it.
All that came together to make the 64 bit HTC Desire 510 project. All that came to the rescue to make THEDREAMER possible. You are pioneers and not afraid of a challenge. I don't know if you have any sort of recognition for everyone that takes the time and puts fourth the effort to share the GIFT OF KNOWLEDGE. If not, I'd like to declare Tuesday, March 31, 2015 programmers appreciation day! And you both deserve the GOLDEN THUMBS UP AWARD just because I appreciate your patience, and you caring enough to share knowledge with individuals that otherwise wouldn't have the opportunity to delve into this field.
THANK YOU!
Hopefully I'm not breaking any rules by speaking up. But I. Believe it's time for some recognition with a simple shout out saying THANKS, YOU MADE A DIFFERENCE IN MY LIFE.
paying it forward....
:highfive:

Should the kernel name be "3.10.28-g36bd0f8-dirty (root @ speedstarlap)" after installing?
I'm trying to enable S2W and can't seem to get it working, was wondering if the kernel installed right, or if there were other versions - you said you have MSM8919, whereas my 510 shows up as MSM8916- a typo or actually different chips? (if possible, could you please tell me how to enable S2W if the kernel installed right?)
@edit - Managed to get it... "working" - if I lock the screen and swipe to right and left near the menu buttons within 2-3 seconds from locking, it works. otherwise it doesn't. D2W is fully dead though. I'll poke around it a bit more and see if I can get it to work properly...

Hi, which gcc are u using? and how to compile the dt.img?
I compiled a kernel for D820, only with stock dt.img could bootup. It boots into bootloader if I use the dt.img which I compiled from stock kernel source.
could u help me?

Kernel works great and great improvement in speeds! Thanks

I've a problem. Sometimes the touchscreen doesn't react after waking up my phone. But the volume up and down and the power button work.
Can this be because of the kernel? I don't know. Please help.

Lonely_Boz said:
I've a problem. Sometimes the touchscreen doesn't react after waking up my phone. But the volume up and down and the power button work.
Can this be because of the kernel? I don't know. Please help.
Click to expand...
Click to collapse
I have the exact same problem I have to restart my device for screen to be back in action

[EOL][MOD] BlackenedMod v3.1 (Pixel 3 / Pixel 3 XL)

Introduction:
Hello everyone!
The idea to this 'project' did blossom after having an conversation with @pkgnex in the past about the general idea of creating something else that follows what he started with his PK's Tuning Script for Pixel 2 (XL) but with a twist, mainly as a complement to his own thread that you can find here, but also with a completely different vision and focus on what the script itself should achieve (and deliver) for kind of results for myself and for all of you personally, of course, that wants to try it out and use it as a "daily driver".
Shortly explained.
These scripts is created with the goal of improving both battery life and performance on our Pixel 3 (XL) devices, and after a whole range of configurations and various set-ups, I've come up with something that, in my eyes, is worth sharing with all of you so that you can try it out yourself and judge on your own, with constructive feedback on what can be improved or added in future releases - if desired. My philosophy is, and will always be, this:
If something can be improved or altered in a positive way so the average user can feel and see a difference, then go for it. Non stop.
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.
Note: These scripts is not recommended to be modified or customized by the user.
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
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 these scripts fully working:
An unlocked bootloader
Your own specific choice of kernel
Latest possible version of Magisk
Busybox for Android NDK Magisk Module by @osm0sis
Patience
Installation/How-To use & abuse:
1) Download the attached ZIP
2) Extract the scripts
3) Move the scripts to the following location;
/data/adb/service.d and give it the following & needed file permissions (0775)
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 all generations of released Pixels!
Credits:
@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.
@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: 2019-01-06
Last updated: 2019-10-25

Note: The changelogs have been strictly moved to the release posts.

Thank you for this, I will give it a try. I was hoping someone would come up with a script that we can use to automate whatever we want at the kernel level. I feel like this could make the stock kernel much better as far as battery life and performance. I know you said use whatever kernel, but Do you recommend using the stock kernel for this?

freebee269 said:
Thank you for this, I will give it a try. I was hoping someone would come up with a script that we can use to automate whatever we want at the kernel level. I feel like this could make the stock kernel much better as far as battery life and performance. I know you said use whatever kernel, but Do you recommend using the stock kernel for this?
Click to expand...
Click to collapse
Of course. BlackenedMod is universal across the whole Pixel 3 (XL) line-up, so it will work more than perfect with stock kernel, if that is what you are using!
:highfive:

On 2xl there was a file wich showed that mod works. How about 3 xl?

I remember on the pixel 2 XL there would be a file formed internal storage that showed that the script was working. That doesn't seem to happen on this device?

xFirefly93 said:
Of course. BlackenedMod is universal across the whole Pixel 3 (XL) line-up, so it will work more than perfect with stock kernel, if that is what you are using!
:highfive:
Click to expand...
Click to collapse
i was using proton kernel. so i went back to stock kernel through fastboot. upon booting the white google splash screen popped for about 1 sec then my phone rebooted and i got the your device is corrupt screen. i then rebooted to bootloader and loaded twrp img file. i then rooted the stock kernel with magisk. after that i still got the your device is corrupt message but i was able to continue after that and it booted up fine. so looks like you dont want to do this on stock kernel that is not rooted. heh.
it looks like my phone keeps saying my device is corrupted. i've restarted 2 times and both times it says that and you cant get past that screen unless you hit continue. any ideas how to get this to work without the phone doing that?

blaze9090 said:
On 2xl there was a file wich showed that mod works. How about 3 xl?
Click to expand...
Click to collapse
Gordietm said:
I remember on the pixel 2 XL there would be a file formed internal storage that showed that the script was working. That doesn't seem to happen on this device?
Click to expand...
Click to collapse
For now, you have to manually create a folder in your internal storage named "logs" (without quotes) because of some security kind of thing that Google have addee which prevents "automatically" created folders to even be made at all.
Otherwise the specific output log, that tells you if the script could execute or not, won't be generated because of a non-existing path / folder.
I will though look around for a possible workaround and see if it can be added directly within the BlackenedMod script for maximal flexibility directly on-the-fly.

freebee269 said:
i was using proton kernel. so i went back to stock kernel through fastboot. upon booting the white google splash screen popped for about 1 sec then my phone rebooted and i got the your device is corrupt screen. i then rebooted to bootloader and loaded twrp img file. i then rooted the stock kernel with magisk. after that i still got the your device is corrupt message but i was able to continue after that and it booted up fine. so looks like you dont want to do this on stock kernel that is not rooted. heh.
Click to expand...
Click to collapse
You need Magisk (=root) and the Busybox Magisk module for even being able to use BlackenedMod.

Installed in Pixel 3 with Botleggers and Proton V10, at the moment everything is perfect, thanks for the work! I will report results!
Enviado desde mi Pixel 3 mediante Tapatalk

gaseoso said:
Installed in Pixel 3 with Botleggers and Proton V10, at the moment everything is perfect, thanks for the work! I will report results!
Enviado desde mi Pixel 3 mediante Tapatalk
Click to expand...
Click to collapse
Enjoy!

xFirefly93 said:
You need Magisk (=root) and the Busybox Magisk module for even being able to use BlackenedMod.
Click to expand...
Click to collapse
it looks like my phone keeps saying my device is corrupted. i've restarted 2 times and both times it says that and you cant get past that screen unless you hit continue. any ideas how to get this to work without the phone doing that?

freebee269 said:
it looks like my phone keeps saying my device is corrupted. i've restarted 2 times and both times it says that and you cant get past that screen unless you hit continue. any ideas how to get this to work without the phone doing that?
Click to expand...
Click to collapse
Try with clean flashing stock firmware.

*Deleted*

xFirefly93 said:
Try with clean flashing stock firmware.
Click to expand...
Click to collapse
that worked. i backed up my current system image and data in twrp. then did the flash-all.bat without -w. then went back into twrp and rooted the stock kernel. then went back into twrp and restored my backup. thanks a lot. will report back on how its gone after a couple days.

Telegram:
Not for going off-topic far too much now but..
If you want to hang out a little, try previews / betas of BlackenedMod for Pixel 3 (XL) before they are officially released or just want to meet a lot of awesome people from every possible corner of the woeld - then join the official Telegram group, fully dedicated to the P3(XL) line-up here.
:highfive:

Will you eventually have different versions for different kernels or are you keeping the mod universal for the pixel 3 XL?

Gordietm said:
Will you eventually have different versions for different kernels or are you keeping the mod universal for the pixel 3 XL?
Click to expand...
Click to collapse
I am keeping it universal with everything good / great / greater than greatest from every kernel organized in the same package and place.

so i followed instructions, got it all done, rebooted, i'm good to go? don't need to do anything just set it up and go right?

Is there a way to tell if this is working?