yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Android Development] vedantdude:
http://xdaforums.com/showthread.php?p=69612713

[MENTION=5091819]spezi77[/MENTION]

Looks like enabling fast charge causes the problem, that actually makes charging slower with a/c source. Could somebody cross check if they have the same problem with USB fast charge?
[Nexus 4 Android Development] 2chevsky:
Just tested it on StephanMC's CM 14.1

Working fine, but music is freezing, and sysmon shows only one active core at 90% of time.

P.S. kernel adiutor mod from OP crashes if i change the governor
[Nexus 4 Android Development] gorilla p:
I changed my battery twice. After you do it once, it's really easy. Plenty of videos and instructions as well as N4 batteries with tools to replace it on eBay and amazon for like $10.

But to answer your question, I could get about 4-4.5 hrs SOT but would have to charge it nightly still.

However battery life with 6.1/7.0 is better than when I was using it with 5.1
[Nexus 4 Android Development] dcshallot:
CM14.1 is on the way, would you consider to keep up with it after the nightlies come? (Last time the kernel broke the camera)
[Nexus 4 Android Development] nARMstrong20:
Don't pressure the dev, remember most devs here only get their free time to work on this stuff. Who knows, maybe he's plugging away at fixing the camera right now.

Went from 3.5 hrs to 4 to even 5 hours SOT after changing battery. I think it also helped I switched Roms and changed primary browser. I normally use ondemand and 125 power save bias with Mako hotplug at 85% threshold and load counters turned up so it doesn't plug all cores in as easily.
[Nexus 4 Android Development] aldus12:
I'm using kernel auditor to customize kernel settings but cpu voltage doesn't stick after reboot. Do you know how to manage that? I've already tried to clean all previous settings, re-flash the kernel, re-flash the rom (nitrogen os) and the kernel but with no luck.
[Nexus 4 Android Development] zephyr79:
Try it with KA mod.
[Nexus 4 Android Development] Cristiano Lira:
Thanks but in r05 test build this issue is already gone :). But, another thing that still bothers me is the presence of input boost in the governors despite the global input boost implementation, also, I don't know if it this is the reason (probably, because it seems that it don't have an buit in input boost) but I'm getting better battery life using ondemand than conservative even with it having a smoother operation.
[Nexus 4 Android Development] spezi77:
Hey there, I am not that satisfied with battery in r05 test build. I am considering to get rid of CPU boost features at all. What are your thoughts?

Sent from my beanstalked N4.
[Nexus 4 Android Development] xenyz:
I'd like to revise my answer, as I don't think it's CPU boost causing this.

I believe it's the mpdecision service deciding to give an input boost for some reason and then crashing.

[MENTION=5091819]spezi77[/MENTION] I use a custom installer for AOSP ROMs based on Semaphore anykernel installer, do you want to use it for hellspawn? You can see it attached to this post. I've just changed it to use elementalx as default but it's basically the same. It disables mpdecision and has a 'mpdfake' binary that eats the touch boost log spam.
[Nexus 4 Android Development] Cristiano Lira:
Idk but I can say is that only with ondemand that I get a minimally decent battery life (with wakeupboost off). But read what xenyz said, it can be that 3 different input boost implementation working at the same time (global, mpdecision's and the bult in on the governors) is the cause of the high battery drain.
[Nexus 4 Android Development] jer_ying_fd:
How does elemantalx feel compared to stratosk's ondemand or other ondemand variants?
[Nexus 4 Android Development] mparmpas122321:
Thanks for the kernel! Pretty smooth. Flashed r04 over r03 and works fine! Although it seems battery drain is higher than that of cm13 kernel and benchmarks a bit lower. I am waiting for your upgrades :)
[Nexus 4 Android Development] mesaj:
I've flashed r03 with cache wipe and it didn't boot as well as r04 (with or without wipe after r03)? What I'm doing wrong here? It boot once but most of time it doesn't after rebooting
[Nexus 4 Android Development] spezi77:
Well, you could try to restore or reinstall your custom rom and then directly flash r05 over it without roundabout way via r03. *fingers-crossed*

As a last resort you could install BeanStalk ROM which has this kernel already integrated.
[Nexus 4 Android Development] spezi77:
After a while of testing various combinations, I decided to publish the final r05 w/o CPU BOOST. On one hand it feels like throwing something over board.. but on the other hand I am pretty sure that our boat is more efficient now!

Cheers!

;)

Thanks very much to all "testers" for your time and valuable feedback! :good:
[Nexus 4 Android Development] Sharjeel.Khan:
works like charm with latest dirty unicorn rom. very good work.

much appreciated.
[Nexus 4 Android Development] karan.sorathia:
which version to use for DU v10.1 Mako Hellspawn aosp-TC4.9.zip or aosp-TC5.3.zip ???
[Nexus 4 Android Development] Mrcactuseater:
Whichever you want, they are both great.

Tapatalk'd from my Twisted, Yank'd Nexus 5
[Nexus 4 Android Development] hash87:
I've just flashed newest version and it seems to work great. However 2nd core still seems to randomly get stuck [MENTION=5214376]1026[/MENTION]MHz.
[Nexus 4 Android Development] rodries:
I have the same issue

Maybe is because I'm using ukm, I'll check it setting the min freq. In kernel auditor
[Nexus 4 Android Development] spezi77:
Hum, could you please flash r02 to check whether you are also able to reproduce it?

Sent from my beanstalked N4.
[Nexus 4 Android Development] hash87:
Yesterday i was at r02 and i've had similar issue - core 1 or core 2 was sometimes getting stuck @ 1350MHz (as far as i can remember). Now it's 1026MHz and only core 2.

BTW I use kernel adiutor.
[Nexus 4 Android Development] Jakub_Z.:
EDIT:

Can I dirty flash r05-aosp-UBER-TC5.3 build over r04?
[Nexus 4 Android Development] spezi77:
Yep! [emoji51]

Sent from my beanstalked N4.
[Nexus 4 Android Development] rodries:
Using ondemand governor and Mako Hotplug Control

I've changed CPU Max Frequency to 810MHz and sync_freq to 918000 to check if that values are related to the change of CPU Min Frequency to 1026MHz but after a while the CPU Min Frequency is set to 1026MHz
[Nexus 4 Android Development] Cristiano Lira:
I got that too after clean flashing then I noticed that both MPDecision and Mako hotplug were and after I turned off MPdecision and reset minimun CPU frequency to 384 MHz the issue was gone. A thing I noticed too related to KA is that sometimes you have to turn off the screen to get the changes applied. Another thing that I want to say is that, although this kernel is really great, I think it's lacking a good battery friendly governor, that somehow the battery performance could be better. What you think, spezi77?
[Nexus 4 Android Development] aldus12:
Works great! Thank you!
[Nexus 4 Android Development] dcshallot:
I just installed cm14.1 experimental version of 1126. Camera works normally, dt2w normal too. Thanks a lot!
[Nexus 4 Android Development] Bhavish784:
Hi Spezi77. Thanks for the awesome kernel! i've tried this new KA mod but still only getting the 'enable/disable' option for the dt2w,.. any help how to make it full screen dt2w please? i used the hellspawn-N4-mm-6.0-r18-CM-UBERTC-5.4.
[Nexus 4 Android Development] vedantdude:
Flash UKM and use synapse
[Nexus 4 Android Development] Bhavish784:
Hi. thanks for the advice. just did that. flashed UKM and synapse (from this thread: http://xdaforums.com/android/software/zip-synapse-script-universal-kernel-t2736986). in synapse i can see the full screen dt2w option but i cannot apply it. only centre option works..
[Nexus 4 Android Development] Gu$houn*:
AFAIK that's because of the implemented dt2w's method, stratosk developed his method as it's activated from the screen centre and if there is no changes in the original code, it's just like stratosk made it.

P.

[sntfrmnxs⁴]
[Nexus 4 Android Development] Ra1d3R:
thank you so much man full screen dt2w working now :)
[Nexus 4 Android Development] Has_anDroid:
synapse work amazing :D
[Nexus 4 Android Development] spezi77:
You are welcome!

No, you should use my KA Mod to get full access to dt2w features.
[Nexus 4 Android Development] *Jonny*:
Hi guys why i can not change selinux status? Please i need help, i try selinux changer but also do not work :/
[Nexus 4 Android Development] Anthonius:
someone can say me, which kernel I use in nitrogen os 7.1, I need help #spezi77.

Which I can use in Nitrógeno OS 7.1

Nougat release:

HellSpawn-N4-Nougat-R03-AOSP-UBERTC-5.4-CPUSET

HellSpawn-N4-Nougat-R03-AOSP-UBERTC-5.4

HellSpawn-N4-Nougat-R03-CM-UBERTC-5.4
[Nexus 4 Android Development] Vlad87do:
spezi77, please update your kernel for CM14.1 :o
[Nexus 4 Android Development] dcshallot:
I'm using it. Camera works. But sometimes cm bug reporter crash, I'm not sure if cause by kernel.
[Nexus 4 Android Development] moriel5:
The second one.
[Nexus 4 Android Development] Emandroid:
What is cpuset??
[Nexus 4 Android Development] klaust58:
oops...deleted, wrong thread :(
[Nexus 4 Android Development] spezi77:
It is only supposed to work with fake_nexus.
[Nexus 4 Android Development] Vlad87do:
camera is not working for me, and some other bugs
[Nexus 4 Android Development] dcshallot:
I did the clean install. If you have time, you can try.
[Nexus 4 Android Development] hastthou:
Which android nougat rom is fully compatible with this kernel?
[Nexus 4 Android Development] zephyr79:
Nexus4ever, PN & Nitrogen have all worked fine for me when I've tested them.
[Nexus 4 Android Development] moriel5:
Current battery level & approximation of time left.

This was done after I had underclocked the kernel to 1.3GHz, with screen off frequency at 1.0GHz.

HellSpawn kernel R03, NitrogenOS (Nov 11), with Greenify running.
[Nexus 4 Android Development] :
This kernel works well on CM 14.1 NIGHTLY ?
[Nexus 4 Android Development] dcshallot:
I'm using it. I think it's ok.
[Nexus 4 Android Development] tom0013:
where can i enable dt2w? i used kernel auditor original and mod also. :(

I did it!!!! Just flash kernel again and enjoy :). Now all run normally. Thanks [MENTION=5091819]spezi77[/MENTION]
[Nexus 4 Android Development] *Jonny*:
Best kernel for cm 13 but on nougat is very slow and unstable, he need update...
[Nexus 4 Android Development] xenyz:
Quick Hellspawn tips you can try, with the official installer:

- change hotplug to mako_hotplug

- change CPU governor to ondemand

- change ondemand sampling rate to 10000, io busy to 1, down threshold to 10

- change GPU max freq to 400/487 MHz

- change iosched to BFQ

- use -CPUSET version on Fake Nexus

It's not slow nor unstable for me on 7.1 with the above mods.

Edit: ondemand sampling_rate_min is set to 20000, [MENTION=5091819]spezi77[/MENTION] when did that change? :D
[Nexus 4 Android Development] dcshallot:
cm14.1 nightly 1130.

Governor hellsactive

Hotplug mako-hotplug

Sometimes I play local music using google music player, and I find that when the network switch from 3G↔WiFi, the player lag much.
[Nexus 4 Android Development] r4yN:
Running stephanmc's CyanogenMod 14.1 11-27 build with HellSpawn R03 hotfix CM

Smooth, Stable & Good Battery Life, but unfortunately R03 broke the Camera & Flashlight :crying:

(Haven't tried the official Nightlies yet, but since it's kernel-related it probably won't make a difference)

Any chance you could update the CM-version, spezi? :fingers-crossed:

(I really hate stubbing my toe in the dark :laugh:)
[Nexus 4 Android Development] spezi77:
Here it was changed, according to the "semaphore" settings you have posted here: http://xdaforums.com/showpost.php?p=67293446&postcount=796

:o
[Nexus 4 Android Development] spezi77:
I tried to find a solution a few days ago, but there is a big gap in the code base between CM bloated kernel and AOSP kernel. The end of the story is that, no, unfortunately there is no hellspawn kernel with camcorder/torch fix available for CM 14.x ROMs.
[Nexus 4 Android Development] xenyz:
Ha. Well I guess sampling_rate should be changed in init scripts instead of MICRO_FREQUENCY_MIN_SAMPLE_RATE, as that sets the floor that the sampling rate cannot go below. If you feel like it please set it back to 10000, the reasonable minimum :)

BTW, Hellspawn has seemed to fight back the SoDs I was having on 'stock' 7.1 and I don't want to jinx anything since I have a good uptime. Anyone else have the same experience?
[Nexus 4 Android Development] :
very quickly discharged battery CM 14.1 :(
[Nexus 4 Android Development] spezi77:
You should use settings for battery savings. Just search, it has been explained in many places in this thread.
[Nexus 4 Android Development] Mc AGV:
Camera don't work on cm14, please fix it ?

It's excellent, but, the camera don't work on Cm14
[Nexus 4 Android Development] r4yN:
Spezi already commented on the issue (it's just 4 posts above your very own), unfortunately it doesn't look like he is going to (be able to) fix it :crying:
[Nexus 4 Android Development] spezi77:
Absolutely right, thanks for pointing this out! ;)

Always remember, first read a few pages back and also don't be afraid of using the search function to scan the thread for possible answers. Only if you have a new topic, create a post. :good:

BTW, I just made a new test build (AOSP). Could someone give it a shot?

AOSP std. version: https://www.dropbox.com/s/ezbj4ud7zq9c9ih/HellSpawn-N4-Nougat-R04-AOSP-UBERTC-5.4.zip?dl=0

AOSP CPUset version: https://www.dropbox.com/s/26gl1p2d5arrmjz/HellSpawn-N4-Nougat-R04-AOSP-UBERTC-5.4-CPUSET.zip?dl=0

What's new?

* cpufreq: ondemand: MICRO_FREQUENCY_MIN_SAMPLE_RATE to 10K (return to a more sane default value)

* merged latest updates from security bulletin

* USB: msm_otg: Fix a bug in charger detection procedure

* USB: msm_otg: Fix host mode suspend bug

P.s.: USB OTG fixes added [MENTION=7562629]hasanben35[/MENTION]
[Nexus 4 Android Development] Has_anDroid:
thanks spezi77
[Nexus 4 Android Development] spezi77:
Thanks for the logs. Need some time for investigation.. stay tuned.
[Nexus 4 Android Development] Has_anDroid:
7.1.1 not work ?
[Nexus 4 Android Development] spezi77:
R03 works.
[Nexus 4 Android Development] spezi77:
Another test build (AOSP), same download links. Please let me know if it boots!

AOSP std. version: https://www.dropbox.com/s/ezbj4ud7zq9c9ih/HellSpawn-N4-Nougat-R04-AOSP-UBERTC-5.4.zip?dl=0

AOSP CPUset version: https://www.dropbox.com/s/26gl1p2d5arrmjz/HellSpawn-N4-Nougat-R04-AOSP-UBERTC-5.4-CPUSET.zip?dl=0
[Nexus 4 Android Development] VegetaSSJ5:
How I know what revision I need to flash? (r13 or r18. I'm running the last snapshot of cyanogen 13.0)
[Nexus 4 Android Development] Has_anDroid:
yes r03 works :D not works r04 sorry
[Nexus 4 Android Development] Azure Potato:
Okay, using Nitrogen OS and used the std version of your r04 kernel.

It definetly boots up to the setup screen however there is no picture once it does. I can lock and unlock the screen and could even hit the get started button (remembered where it is, the touch sounds help alot). So apparently something about the display.

Also, did all of this with a clean flash from scratch.
[Nexus 4 Android Development] spezi77:
Thanks for the detailed report. I hope that it will allow me to locate the bug.
[Nexus 4 Android Development] spezi77:
Release 18 is the right one for you. My change log (see 2nd post) says "CM compatible". Enjoy :D
[Nexus 4 Android Development] Azure Potato:
No problem, I hope it helps you too :cowboy:
[Nexus 4 Android Development] dcshallot:
It's strange that I'm using official CM14.1 and the camera is fine.
[Nexus 4 Android Development] jolinnard:
I've compiled a personal build. First I've build latest UBER 5.x. Then removed latest commit in n-7.x branch (b65d3c2b677752b95ee16a233e6cc1e1fef9ea88) and reverted aa9d4d4ed3cf3ec7089744fa44440420d1d1dd31. My phone boots and screen seems OK. Makes sense?
[Nexus 4 Android Development] spezi77:
Thanks very much for finding the "faulty" commit. I will later have a closer look and recompile it.
[Nexus 4 Android Development] ItaroyaN:
which version should I download for the latest Nitrogen ROM?
[Nexus 4 Android Development] fr3quency:
Any chance for some compiled .zip? [emoji14]

Sent from my Nexus 4
[Nexus 4 Android Development] r4yN:
Which CM14.1 build (one of the new December builds, I assume?) & which hellspawn kernel (R03-hotfix?) are you using, if I may ask?

I'm still on StephanMc's old build (due to gapps problems), maybe there have been some (kernel-related) changes in the official nightlies? :fingers-crossed:
[Nexus 4 Android Development] dcshallot:
I don't use his build any more, and it's a clean install. You can just try the latest version.
[Nexus 4 Android Development] spezi77:
At the moment R03 (AOSP).
[Nexus 4 Android Development] spezi77:
Yes, try to download from theses links in appr. 20 minutes:

AOSP std. version: https://www.dropbox.com/s/ezbj4ud7zq9c9ih/HellSpawn-N4-Nougat-R04-AOSP-UBERTC-5.4.zip?dl=0

AOSP CPUset version: https://www.dropbox.com/s/26gl1p2d5arrmjz/HellSpawn-N4-Nougat-R04-AOSP-UBERTC-5.4-CPUSET.zip?dl=0
[Nexus 4 Android Development] spezi77:
Hum, by looking into the reverted commit it makes no sense. So, you did it like this? https://github.com/spezi77/hellspawn-N4/commits/n-7.x
[Nexus 4 Android Development] Durotan:
Tested HellSpawn-N4-Nougat-R04-AOSP-UBERTC-5.4. on Fake nexus rom for Nexus 4. [Dec/06/2016] and i have a black screen on boot (but I have heard the startup sound).

I have done all cache wipe
[Nexus 4 Android Development] Azure Potato:
Tested the updated AOSP std. version R04 with Nitrogen OS again and still the same problem. Clean flash from scratch again.

Boots up to the setup screen, digitizer works as I click around and hear the touch sounds at the spots where the buttons should be.

Can lock and unlock the screen and the lcd still turns on but no picture, just black(as black as the lcd on the nexus gets xD).
[Nexus 4 Android Development] jolinnard:
Yes... That's why I asked yesterday if that commit could cause it... Let me try to build it without that reverted commit... I remember that something like this happened some time ago, and finally it was an issue with my toolchain...

Edit:

I can confirm that R04 build without "reverts" works fine. You should check your toolchain... maybe problem is there.

My setup:

- Build UBER with: UBER/scripts/arm-eabi-5.x

- Build with a local tree in this point:

$ git log
commit ce4694247a1d109814e6e9adcbf3cccf07785202
Author: spezi77 <spezi77@gmx.com>
Date: Tue Dec 6 22:02:26 2016 +0100

Bump up to R04.

Signed-off-by: spezi77 <spezi77@gmx.com>

commit 18b0e17b83c9b9c1bc302aeaf572cae2fdb7d967
Author: Pavankumar Kondeti <pkondeti@codeaurora.org>
Date: Wed Mar 9 21:15:42 2016 +0800

USB: msm_otg: Fix a bug in charger detection procedure
USB PHY is put into non-driving mode and pull-down resistors on DP
and DM are disabled before starting the charger detection. The
PHY is put into driving mode at the end of the charger detection
without enabling the pull-down resistors. Due to this DP is
pulled high when a dedicated charger is connected. USB controller
is not allowing PHY suspend if line state is non-zero when charger
is connected. Enable pull-down resistors at the end of charger
detection to resolve this issue.

Signed-off-by: spezi77 <spezi77@gmx.com>

commit 48b06901ced8bca665aec75464f5bace1b119a4b
Author: Sujeet Kumar <ksujeet@codeaurora.org>
Date: Wed Mar 9 21:13:50 2016 +0800

USB: msm_otg: Fix host mode suspend bug
Capturing BSV bit before ID test msm_otg_set_vbus_state()
is leading to return suspend call without entering
USB into LPM. In host mode since there is no need for
BSV check, clear the BSV bit so that USB suspend can
go through.

This happens when a target enters host mode with no devices
attached, USB OTG will never enter LPM, as the BSV bit will
always be set.

Signed-off-by: spezi77 <spezi77@gmx.com>

I've attached my zImage (compressed in gzip to be allowed by xda) if you want to compare.
[Nexus 4 Android Development] spezi77:
Just did a build with the commits you suggested, but it didn't work out. Maybe you can do another build and share it here?

And I have to tell you that I am currently not able to do any quality checks. I am now without my mako.

My new device is Pixel XL. Not a faked one. :laugh:
[Nexus 4 Android Development] jolinnard:
Yeah, I've attached zImage in my last post... I'm running it right now.
[Nexus 4 Android Development] spezi77:
Well, I didn't change the toolchain. I still have UBER TC 5.x, the one I used for all the previous builds.

However, it should no longer matter to me as I no longer have a N4. I guess that this has been a sign. A sign to quit development for mako.. time to say goodbye! :angel:
[Nexus 4 Android Development] jolinnard:
Sorry to hear that. Many thanks for all your work!
[Nexus 4 Android Development] spezi77:
After 4 years of being a reliable phone, my mako got a serious hw related defect! :/

It was a funny time here in the mako dev forums., we will maybe meet again on the other side of the forum (Pixel XL)..

[MENTION=2002216]jolinnard[/MENTION], are you interested in continuing the HellSpawn legacy, seriously? ;)
[Nexus 4 Android Development] jolinnard:
Wow, I can build kernels for mako, test patches and new "stuff"... but I never could do the same as you with the code, too much for me. But, I can help you to keep HellSpawn legacy up-to-date if you merge security patches, etc... :) build is not a problem for me... But sources are yours ;)
[Nexus 4 Android Development] ItaroyaN:
really sad ):
[Nexus 4 Android Development] spezi77:
Well, that sounds better than nothing. ;)

Let's make a new official release, based on the working R04 kernel on your end.

You need to create a few folders in your environment.

On my system I created the following structure:

1. anykernel installer

~/android/Kernel/anykernel_msm/

2. hellspawn kernel

~/android/Kernel/hellspawn-N4/

3. output folders (one folder to keep a local copy and one folder to automatically share the builds via dropbox)

~/android/Kernel/Releases/hellspawn-N4/

~/Dropbox/Kernel-Betas/hellspawn-N4/

That's it, now let's move on to checkout the repos.

First, let's clone the anykernel installer.

https://github.com/spezi77/anykernel_msm -b n-7.0-hellspawn

Second, let's clone the hellspawn kernel.

https://github.com/spezi77/hellspawn-N4 -b n-7.x

Now, assuming that you have a proper toolchain in place (and edited build.sh to have the correct folder paths) you can run my build script like this:

. build.sh

Then choose the 3rd option (batch-build)

Any questions?
[Nexus 4 Android Development] jolinnard:
Done. Adapted to my own paths, but did a batch build without issues. Kernel boots fine.

So, are you sure that this commit is needed?

commit ba7bbae483f3c146039b8478a740a687eac96912
Author: spezi77 <spezi77@gmx.com>
Date: Fri Dec 9 18:28:46 2016 +0100

Revert "HID: core: prevent out-of-bound readings"

This reverts commit aa9d4d4ed3cf3ec7089744fa44440420d1d1dd31.

Signed-off-by: spezi77 <spezi77@gmx.com>

You can find result files here:

HellSpawn-N4-Nougat-R04-AOSP-UBERTC-5.4.zip

HellSpawn-N4-Nougat-R04-AOSP-UBERTC-5.4-CPUSET.zip
[Nexus 4 Android Development] spezi77:
No it isn't needed, I will remove it again. So, it seems that there is a problem which is not in the source code, but in my build environment/toolchain setup that is causing the issue. Holy c...! :silly:
[Nexus 4 Android Development] jolinnard:
Ok. I'll sync again and build when you're done.
[Nexus 4 Android Development] spezi77:
Done.

P.s.: Congrats on the new build, I will put the links into the OP. I will add you now as contributor. I think that this will allow you too to edit the OP. Or you could start a new thread.
[Nexus 4 Android Development] jolinnard:
Ok. You're welcome.
[Nexus 4 Android Development] spezi77:
So, about the links you posted above, can I safely put them into the OP? Or will they be different with the new build?
[Nexus 4 Android Development] jolinnard:
I will replace that zips with the final build, so you can put them in the OP.

Edit: Final build is up!