yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Android Development] Durotan:
which recommended version for fake Nexus?
[Nexus 4 Android Development] spezi77:
Fake Nexus is AOSP based and has support for CPU set, which means that HellSpawn-N4-Nougat-R04-AOSP-UBERTC-5.4-CPUSET is the one for you.
[Nexus 4 Android Development] Daandofreak:
Is my understanding right that if using Pegasus q governor i don't need any hotplug. Because this governor has also hotplugging?
[Nexus 4 Android Development] *Jonny*:
So you stop support CM version?
[Nexus 4 Android Development] spezi77:
I can no longer continue kernel development for mako on my own, also support for CM makes no sense without a proper camcorder fix or fix confirmed by users.

I feel really confused by the fact that some user mentioned that in the official CM14.1 camcorder works flawlessly while others tell the opposite. Unless this has not been clarified, I don't see a point in continuing CM support.

If CM users are interested in further support, please help us with clear and systematic test results.
[Nexus 4 Android Development] spezi77:
Yes, I share the same understanding. The governor has its own hotplugging mechanism which allows for controlling the amount of running cores depending on the current overall load.
[Nexus 4 Android Development] r4yN:
Can confirm that the camera & torch do work on the (new) official CM14.1 nightlies... :good:
[Nexus 4 Android Development] Azure Potato:
For whatever it's worth I can second that.

Clean flashed latest CM 14.1 on my Nexus 4 and camera, video and torch work perfectly fine.

Took some pictures, worked perfectly.

Took a video, worked perfectly, picture during video aswell.

Used torch on and off, worked perfectly fine.

Hope it helps.
[Nexus 4 Android Development] xenyz:
Oh no, he's... (gasp) upgraded!

Thanks for all the work on the N4, really appreciate it. Hope you get into hacking the Pixel sooner or later too.

BTW, it may be some sort of Irony that on the very last HellSpawn & Android 7.1.1, the Mako is so fast, it might as well be a Pixel :D :D ;D
[Nexus 4 Android Development] Cristiano Lira:
It doesn't turn off lhe cores for me without any hotplug activated.

Btw, sad to hear that you mako got broken. :/

Thanks for all your work on our beloved device, you did a revival on it. :) Good luck with Pixel and maybe someday we will reach each other on the other side of the xda. :)
[Nexus 4 Android Development] spezi77:
Thanks for sharing your experience. So much for the theory! :laugh:

Yes, we should definitely meet one day on the other side! ? [advert] I enjoy the new Pixel experience to the fullest! [/advert]

P.s.: it was also nice to closely collaborate with you during the development & testing phases of the revival kernel!
[Nexus 4 Android Development] vedantdude:
Can u please share your kernel settings?
[Nexus 4 Android Development] ayyub46:
So im om CM 14.1

Using Hellspawn N R03 Hotfix.

When I set Dt2w to center, apply on boot with Kernel Adiutor Mod.

And when i reboot my phone, Wake Control is back to unknown/disable.

Any idea [MENTION=5091819]spezi77[/MENTION] ?
[Nexus 4 Android Development] spezi77:
I confirm this little thingie. The problem is that the displayed text is inaccurate. The dt2w is still working, isn't it?
[Nexus 4 Android Development] spezi77:
[MENTION=2002216]jolinnard[/MENTION] I have reverted the commit that has temporarily removed the CM build. So, just in case that you would like to provide a new build for CM-14.1-users, here you go:

https://github.com/spezi77/hellspawn-N4/commit/8eb512121da588c4da79928ed2994756a90ee16e
[Nexus 4 Android Development] jolinnard:
Build done: HellSpawn-N4-Nougat-R04-CM-UBERTC-5.4.zip
[Nexus 4 Android Development] xenyz:
There is some sort of bizarre race condition happening on boot it seems. Even on Fake Nexus ROM it's a 50/50 chance the camera/torch works. The crappy workaround for now is to keep rebooting your device until the torch tile works. :D

I'll plug in via ADB and see if I can figure out wtf is going on.

Alright I've updated my thread where I post an alternative kernel installer for HellSpawn. It's set exactly how I use it, obviously.
[Nexus 4 Android Development] ayyub46:
Still working but i must set manually from KA-Mod
[Nexus 4 Android Development] *Jonny*:
Why your kernel based on kernel 3.4.112 when latest is 3.4.113? I installed r04 for CM - work fine at this moment :D Thank you for your support!
[Nexus 4 Android Development] moriel5:
I wish we could wrest control from Qualcomm over the kernel sources, so that we could have kernel 4.9 (which just came out today).
[Nexus 4 Android Development] spezi77:
Guys, you should get yourself a LG Nexus 5: https://www.phoronix.com/scan.php?page=news_item&px=Linux-4.9-ARM-Pull
[Nexus 4 Android Development] moriel5:
I am speechless.

I VANT A NEXUS 5, TO REPLACE ZE ONE ZAT VAS STOLEN FROM ME A FEW YEARS AGO!

Thanks for the info!

Sorry about the outburst, the enthusiast in me is extremely jubilant at these news.
[Nexus 4 Android Development] fr3quency:
We need an answer to the site's comment:

"On the Nexus 5: Does that mean that Android (mainly alternate Android distros) could run now (and forever) on the latest kernel?"

Sent from my Nexus 4
[Nexus 4 Android Development] xenyz:
Probably not, there is just too much proprietary stuff compiled in to have everything work. It likely means you can run a (headless) Linux distribution on the N5 with Linux 4.9 if the networking hardware is up.

Although if video and touch drivers are made, I guess you could boot Android and skip all the rest of the hardware (RIL, sensors, GPS, etc) and it'd still be useful.
[Nexus 4 Android Development] moriel5:
As far as I know, the latest kernel to work at all with Android is the latest 4.4.x LTS kernel, but I could be wrong.
[Nexus 4 Android Development] xenyz:
[MENTION=5091819]spezi77[/MENTION] I just now noticed rq_stats are back in HellSpawn because of the alucard hotplug. I'm now running my mako on mpdecision and ondemand and it's actually working better than the in-kernel hotplug drivers! No idea about power consumption yet but I now realize the importance of looking at the run queue instead of CPU usage with all the multithreaded Android apps these days. Something to keep in mind if you start your kernel dev on the Pixel...

I may take a closer look at alucard hotplug though.
[Nexus 4 Android Development] spezi77:
Great finding, thanks for sharing it with me.

BTW, I have set mpdecision and interactive as default in my N4E ROM. And I remember that my mako (R.I.P.) was getting a wonderful battery life by running the basic kernel setup. Here is the kernel source (just in case that someone is interested): https://github.com/nexus4ever/android_kernel_lge_mako

And as far as I can recall it, the significant battery savings started around that time when I cherry-picked the "mpdecision: yes_sleep" commit from flo's device tree (credits nardholio):

https://github.com/nexus4ever/andro...mmit/eeac41bf9f4d00b068ec23383e4a19912b7c4afa

I hope that it will become useful in the further developments for the Nexus 4. ;)
[Nexus 4 Android Development] xenyz:
Hmm that is interesting, but it just may be a badly named option, as it seems no sleep means yes sleep?

service mpdecision /system/bin/mpdecision --no_sleep --avg_comp

12-14 16:38:53.902 23319 23319 I MP-Decision: MPDecision server starting
12-14 16:38:53.908 23319 23319 I MP-Decision: OPTION ENABLED: Control sleep modes
12-14 16:38:53.908 23319 23319 I MP-Decision: OPTION ENABLED: Adjusting average

Damn proprietary binaries.
[Nexus 4 Android Development] jolinnard:
[MENTION=5091819]spezi77[/MENTION] I've uploaded kernels to a new AFH account. Please, add it as a mirror in the OP: https://www.androidfilehost.com/?w=files&flid=136250
[Nexus 4 Android Development] klaust58:
Hello,

where can i find the "Kernel Adiutor Mod" for this kernel?

Thanks!
[Nexus 4 Android Development] spezi77:
In the download section of the OP.
[Nexus 4 Android Development] klaust58:
Oh sh**, thanks. I had tomaten auf den augen :cowboy:
[Nexus 4 Android Development] spezi77:
[IMG="tomaten auf den augen"]http://images04.oe24.at/brugger_tomaten_132760a.jpg/bigStory/259.364[/IMG]
[Nexus 4 Android Development] ayyub46:
No, dt2w isn't working after reboot.
[Nexus 4 Android Development] Pac-Man:
What? Could you repeat the question?
[Nexus 4 Android Development] moriel5:
He means to ask what is the battery life on CM14.1, and how long is the screen on time on CM14.1 with the Hellscore kernel.
[Nexus 4 Android Development] dcshallot:
What's the changelog of R04 for cm nougat? You just updated for AOSP.
[Nexus 4 Android Development] Hankmg5:
Have you guys noticed any performance issues with the hells Active governor and autosmp because my device freezes more often than when using the interactive and mp decision preset
[Nexus 4 Android Development] spezi77:
Same as for AOSP.
[Nexus 4 Android Development] Pac-Man:
Did someone tried this kernel with 20161217 build of NitrogenOS? :)
[Nexus 4 Android Development] moriel5:
I am using it as my daily driver, in accordance to the battery and performance concious tips handed around here, while CPU is downclocked to 1.2GHz, GPU is clocked at 400MHz, and utilizing BFQ.

Extremely smooth, battery life is between 3-4 hours SOT (although I suspect that I have a faulty battery, despite the fact that it is showing up as "healthy", since I only get between 1-2 hours SOT on the Nitrogen OS kernel, with Wi-Fi on, without GAPPS, while someone in the Nitrogen OS thread gets between 3-4 hours SOT on the Nitrogen OS kernel, with WiFi on, and GAPPS installed), with WiFi on.
[Nexus 4 Android Development] Pac-Man:
And... What is the difference between normal and CPUSET? :)
[Nexus 4 Android Development] murali0007:
Working fine on RR 7.1.1 ðŸ‘ðŸ™‚
[Nexus 4 Android Development] fr3quency:
I don't really know but I tried both versions with the same things of course and I couldn't be more angry in my life with a kernel. I don't know what this ***** is, but it better stay away from my phone. [emoji14] I lagged like there was no tomorrow (OK I'm exaggerating but it really is slower compared to the normal version)

Sent from my Nexus 4
[Nexus 4 Android Development] jer_ying_fd:
It's meant to be used ONLY with fake nexus rom, because it is the only rom with the modifications to use CPUSET properly. As a result, using it with another rom will result in one core being used only.
[Nexus 4 Android Development] spezi77:
Hum, your comment seems not to be very positive. Please always remember the forum Netiquette!

According to the changelog in this thread the developer has mentioned in R02:

* Added a new build variant for Fake nexus ROM (incl. cpuset feature) as requested by [MENTION=3118524]xenyz[/MENTION]

Please read the provided information before installation and before shouting at the world!

Thanks for your understanding.. :good:
[Nexus 4 Android Development] fr3quency:
Whaaaaat??

1) I didn't mean anything mean/ill (I love your kernel)with this comment... But I can now.

2) I know what ROM I have to use it on

3) I was using fake Nexus

4) cpuset is the worst thing that can happen to a kernel - slower than a grandma trying to cross the road. Of course the post wouldn't be "positive" for something that slows your phone down.

How is this for netiquette?

Sent from my Nexus 4
[Nexus 4 Android Development] Pac-Man:
I didn't see when I readed the changelog, so it's my bad. Thank you both of you for clarifying for what it was CPUSET :)
[Nexus 4 Android Development] spezi77:
Thanks for your feedback! Great that we have sorted things out. I will soon add some information about this point to the FAQ section on page 1, and I hope that people will discover it.. :fingers-crossed:
[Nexus 4 Android Development] bean+:
Whoever is interested... I am using latest Fake Nexus ROM by [MENTION=6117313]ganachoco[/MENTION] w/ Pixel modifications (SystemUI from N5) and HellSpawn-N4-Nougat-R04-AOSP-UBERTC-5.4-CPUSET from [MENTION=5091819]spezi77[/MENTION]. Did some kernel-tuning with [MENTION=5091819]spezi77[/MENTION]'s KAmod... (tuned Mako hotplug, elementalX, Simple GPU, ROW, LaptopMode, etc.).

Can't remember when i had the last SOD..., have an uptime of 106h at the moment (but only because I rebooted my N4 manually at that time). The combination of Fake Nexus 7.1.1 and Hellspawn R04 seems to be very stable (at least for me).

I would be interested in the latest researches concerning the MPDecision/Alucard (topic "run queue" vs. "CPU usage", a few posts back).

Maybe the performance, stability,... can be improved further... :D

Many thanks to [MENTION=5091819]spezi77[/MENTION] , [MENTION=3118524]xenyz[/MENTION], and [MENTION=2002216]jolinnard[/MENTION] for the kernel development & investigations

and of course [MENTION=6117313]ganachoco[/MENTION] for the ROM

---------- Post added at 01:26 PM ---------- Previous post was at 01:19 PM ----------

I forgot to mention that - fore sure - my N4 is not as fast as [MENTION=5091819]spezi77[/MENTION]'s new Pixel, but due to HellSpawn close by ;)
[Nexus 4 Android Development] *Jonny*:
Version CpuSet is very slow on nitrogenos i don't why but normal version work fine...
[Nexus 4 Android Development] spezi77:
Thanks for the kudos!

Btw, here is an AnTuTu score of my Pixel XL (stock). The scores of N4 and Pixel are actually close by, only 100000 points away from each other.. ;)
[Nexus 4 Android Development] moriel5:
CPUSET is not meant for Nitrogen OS in the first place.
[Nexus 4 Android Development] Gu$houn*:
So you're telling me, that if I get a Pixel (or probably another 7.x by default) phone, there will be those weird softkeys? Oh, hell no ...

P.

[sntfrmnxsâ´]
[Nexus 4 Android Development] fr3quency:
Looking back at the thread, I have to ask. Is there any way to enable mpdecision? I have always missed it. My tests on 4.4/5.0/5.1 always showed it was faster. I don't understand why you bundle 5-6 hotplugs and you DON'T give an option to enable mpdecision(from kernel adiutor).

Sent from my Nexus 4
[Nexus 4 Android Development] Pac-Man:
You have the option at "CPU Hotplug" on KernelAuditor's build by spezi

View attachment 3978188
[Nexus 4 Android Development] jer_ying_fd:
I thought it's disabled, or is that not the case for nougat builds?
[Nexus 4 Android Development] Pac-Man:
I assume everything that appears on KernelAuditor is ready for being used, otherwise I don't see any reason to show it...
[Nexus 4 Android Development] fr3quency:
Showing it doesn't mean it works. [emoji14] For example can you enable it, navigate inside Kernel Adiutor from hotplugs to one other category (eg Voltage), turn off the screen, return to hotplugs and check if it's turned on or off. I can see the option inside the normal Kernel Adiutor but if I navigate somewhere else, it gets unticked. [emoji14]

Sent from my Nexus 4
[Nexus 4 Android Development] fr3quency:
These days as I have more free time I'll test out some ROMs with this kernel(tried revival as well but HellSpawn offers superior power). Thus far I have only tested Fake Nexus and Pure Nexus with this kernel. Today I went back to Fake Nexus as I missed the round icons and this is my setup in Kernel Adiutor. (+busybox 1.25.1 by osm0sis)

-----CPU-----

Governor: elementalx

-----CPU Hotplug-----

AutoSMP(the default; I haven't edited anything in here)

-----GPU-----

Frequency: 487MHz

Governor: ondemand

-----Sound-----

Volume Gain: +2

-----I/O Scheduler-----

Scheduler: ROW/FIOPS

Read-ahead: 2048kB

Add Random: ON

-----Virtual Memory-----

laptop_mode: 1 (I don't know if the only values are either 0 or 1 for false/true. Or if I can input a higher number)

-----Entropy-----

Read: 1024

Write: 2048

Now the available entropy is around 60-70% instead of 5-30% with the default settings

-----Misc-----

Fsync: OFF

Gentle Fair Sleepers: OFF

Arch Power: OFF

Network: westwood

Could anyone test this setup and tell me how it fairs? it's obviously not suited for battery-friendly users. :p

Now I only miss kernel same-page merging(KSM)
[Nexus 4 Android Development] BadGuy:
Nice man, good job :)
[Nexus 4 Android Development] spezi77:
Hey-ho [MENTION=2002216]jolinnard[/MENTION] ,

I hope you are doing fine, I would kindly ask you to do a new kernel build! ;)

HellSpawn R05.

* Linux 3.4.113

* Switch toolchain to uber/arm-eabi-6.x (more details: https://github.com/spezi77/hellspawn-N4/commit/cb8fdbffe23c6f5ea12a951563ba15b6cc23629b)

Furthermore, it would be possible to restore mpdecision functionality by using a dedicated branch of my installer-script: https://github.com/spezi77/anykernel_msm/commits/n-7.x-mpdecision-yes

I mention this because someone has recently wondered whether this would be possible. Notice: In order to use mpdecision, you have to go back to a ROM which still has an original mpdecison binary in its place, and the install hellspawn with such a modified installer script.

Cheers!

;)
[Nexus 4 Android Development] jolinnard:
I will try tomorrow. I don't have my build machine online today... I have to ask somebody to turn it on :(
[Nexus 4 Android Development] Akhilesh S V:
First I wiped System, Cache, Dalvik/ART then flashed

1. Nitrogen OS

2. Super SU

3. Gapps

4. Kernel

But ended up with a boot loop

Anything missing or the order is it wrong ? :(
[Nexus 4 Android Development] spezi77:
Wrong order. Install kernel in 2nd place and then SuperSU, etc.
[Nexus 4 Android Development] pincher65:
"For the guys who want to use SuperSu instead of the SuperUser, here is the unsu zip: http://xyyx-dev.ru/nitrogen-os/Nitrogen_msm_UNROOT.zip

Flashing process: Flash ROM, gapps, unsu zip, SuperSu and reboot" yes?
[Nexus 4 Android Development] jolinnard:
Hellspawn R05 is up.

Primary links:

HellSpawn-N4-Nougat-R05-AOSP-UBERTC-6.x.zip

HellSpawn-N4-Nougat-R05-AOSP-UBERTC-6.x-CPUSET.zip

HellSpawn-N4-Nougat-R05-CM-UBERTC-6.x.zip

Mirror in AFH:

https://www.androidfilehost.com/?w=files&flid=136250

Enjoy!

PD: [MENTION=5091819]spezi77[/MENTION] check my comment https://github.com/spezi77/anykernel_msm/commit/ea0d507481fb998689ceb22e2b50145d5460a6dd
[Nexus 4 Android Development] spezi77:
Awesome, thanks very much!

And how's the new build with tc 6.x in comparison with the previous one?
[Nexus 4 Android Development] jolinnard:
Awesome! New build seems to be smoother than R04. I've used toolchain you post in github instead of my own compilation. Do you people feel the same?
[Nexus 4 Android Development] nARMstrong20:
Hey guys, does it still say R04 for anyone else on about phone? This is my second time flashing from the primary mirror (not AFH)

Same thing on AFH version. Is this just a naming error or something?
[Nexus 4 Android Development] xenyz:
Yeah it's looking good, at least Tapatalk is a bit quicker :)

Not for me...
[Nexus 4 Android Development] dragos281993:
Do this:

1. Extract the "boot.img" file found inside the "ROM.zip" that you're using

2. Place it whatever folder you want on your phone

3. Reboot to recovery

4. Go to "Install" and tap on "Install image" (bottom right"

5. Choose the "boot.img" file you extracted earlier

6. Swipe to install

7. Flash the new hellspawn kernel

You're done. Reboot to system and check to see what's the version you got.
[Nexus 4 Android Development] nARMstrong20:
I actually went and flashed the ROM zip before seeing the post. I figured I'd probably need to do that this time around. All is well now, thanks!
[Nexus 4 Android Development] dragos281993:
Flashing only the "boot.img" saves you a lot of time. When tou dirty flash the ROM, no matter what little optimization process goes at boot, there's something happening that keeps the phone at the bootanimation screen for a few minutes, while flashing only the stock kernel (boot.img), avoids that part that's no even needed for those in your situation. Keep that in mind next time you change kernels.
[Nexus 4 Android Development] moriel5:
Does this kernel have the E015 touchdriver.

Since it is claimed to bring more sensitivity to the screen (that would be great for when I use my gloves, as it senses my fingers then, whereas on my Doogee X5 Pro it senses them pretty much flawlessly).
[Nexus 4 Android Development] zeeBomb:
Why can't I change the build prop with this? Using Nexus4ever ROM too
[Nexus 4 Android Development] :
After charging the phone I have to reset it ( to run again) because if I do not it does not go into a deep of sleep.

I have somewhere I can change that passed in this mode ( deep of sleep).

I use version AOSP and Nitrogen OS N.
[Nexus 4 Android Development] str3tch72:
I have color inversion in CypherOS ROM on AOSP and CM version.
[Nexus 4 Android Development] Applesan:
me too :(
[Nexus 4 Android Development] spezi77:
Maybe [MENTION=2002216]jolinnard[/MENTION] could have a look into this?
[Nexus 4 Android Development] jolinnard:
I'm running Nitrogen, no color issues... Can you try R04?
[Nexus 4 Android Development] str3tch72:
On R04 everything working fine.
[Nexus 4 Android Development] knuxsonico:
Does this kernel support otg? Because I connect a selfie stick and does not recognize it. In other phone work.

Enviado desde mi Nexus 4 mediante Tapatalk
[Nexus 4 Android Development] spezi77:
Yes, but it needs to be turned on via Kernel tweaking app. See OP.
[Nexus 4 Android Development] spezi77:
That's weird because by looking into the code changes, there was nothing related to color profiles, etc.

Maybe something went wrong during the compilation of the CM kernel?
[Nexus 4 Android Development] jolinnard:
Could be. I'll refresh the compilations and push again.

Edit: Build done. Download from here and let me know.
[Nexus 4 Android Development] laxin:
[MENTION=2002216]jolinnard[/MENTION] colors still damned bro :D
[Nexus 4 Android Development] jolinnard:
I know... Tried CypherOS (kernel is CM based) and colors are bad. I've checked if build script make the proper changes and it seems ok. Also, I've tried to make the changes manually (to make sure), with equal result.

The changes to build CM are:

$ git revert 6277686dfe412edf695878bd354dab504bd911a4 --no-edit
$ git revert afa96f6f21d05d44aa0df138e92cd5dc404e5a36 --no-edit

I'll keep looking into it...

Edit: Found something... Can you flash this and see if it's working now?
[Nexus 4 Android Development] Trickster22:
I confirm, colors are fixed now. Thanks
[Nexus 4 Android Development] spezi77:
Here is a potential fix: https://www.dropbox.com/s/wsbmzkosols4ma1/KernelAdiutor-Mod-Test.apk?dl=0

Please leave me your feedback. ;)
[Nexus 4 Android Development] jolinnard:
[MENTION=5091819]spezi77[/MENTION] can you take a look of these patches?

https://github.com/CyanogenMod/lge-kernel-mako/commit/8f0def3d97dabefb5ac7e4d5cd3dc513b23fe0b1

https://github.com/CyanogenMod/lge-kernel-mako/commit/0bfaf36078e0f0d87c17d5f9a02bf6bc72c770ab

After applying reverts in function git_addback_cm_commits (in your build.sh script) and apply those patches colours were fine again. Maybe ROMs/CM/CAF team changed something a while ago that requires more kernel changes than before? I was comparing mdp4_overlay.c and msm_rotator.c between CM and hellspawn code and there are a few differences.

Please, take a look when you have some free time ;)

Thanks
[Nexus 4 Android Development] spezi77:
Thanks for making an analysis. They use a slightly different set of commits these dayz. I will modify the kernel source and build script accordingly, and then let you know when it's done.

Edit: done.

P.S.: If this isn't the proper solution, you may also consider to use a different TC than UBER for making the CM build. Do you remember about this?
[Nexus 4 Android Development] Has_anDroid:
lineage os 14.1 color problem fix ?
[Nexus 4 Android Development] jolinnard:
Try this testing release please.

---------- Post added at 22:43 ---------- Previous post was at 22:31 ----------

Ok... currently I'm using this TC, as you posted here: https://github.com/spezi77/hellspawn-N4/commit/cb8fdbffe23c6f5ea12a951563ba15b6cc23629b

I'm not sure if we need to change TC if applying those 2 commits from CM we can workaround the issue.

If you agree, we can wait until more people try the test release with their CM ROMs... If there are no problems, we can make it permanent.
[Nexus 4 Android Development] spezi77:
Agreed, I am curious whether someone has already tested it.. :confused: