yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Android Development] bean+:
My N4 is running Chroma 03/13/2016, Installed HellSpawn R4 this morning. Strange... after clean install with wipe, the default cpu governor is ondemand. Re-installed HellSpawn R4 with wipes, again the default cpu governor was ondemand. Changed this to [MENTION=5091819]spezi77[/MENTION] recommendations (one of the previous posts): hellsactive/bfq, 94/1512 CPU frequency range, CPU boost: wake up and input boost enabled. Boost intervall: 1000ms.

Selected features via Kernel Adiutor: DT2W on, Exponential brightness on, Fsync off, GPU@200Mhz.

During the day my device was smooth, fast and rocket stable.

I heard a lot of good things about the elementalX governor for N5 (and above). Is it worth to try it with HellSpawn?

Thanks for the very good kernel, very good job!
[Nexus 4 Android Development] xenyz:
I've been trying it out the past few days and it sort of works. I think I've tracked down where it could be tweaked a bit better for the N4.

I know that hellsgod fixed the 'missing' 27 MHz GPU step, but I think it still isn't the same on the N5. If you look at the line here, it's applying a boost to GPU power level < 2.

As far as I know, power level 0 is 400 MHz, 1 is 320 MHz, 2 is 200 MHz, 3 is 128 MHz and 4 is 27 MHz (idle).

I suggest changing the line to power level 0, then it would be a more effective boost, as it would only apply when GPU is at max power.

Either that, or a lazier GPU governor which stays at or below 200 MHz more often.

[MENTION=5091819]spezi77[/MENTION] is it worth a try?
[Nexus 4 Android Development] Cristiano Lira:
I also noticed that core 1 stays at 1000 Mhz almost all the time, even without any load.
[Nexus 4 Android Development] montbazon:
At first thanks for your support!!

Actually there is something to report...

CM Versions doesn't boot for me on CM13 3/31

I tried R3 and R4. But both aren't.
[Nexus 4 Android Development] bdasmith:
Does turning the sxitch off turn on exponential brightness, or is it already enabled?

Does exponential brightness work with adaptive brightness enabled?
[Nexus 4 Android Development] Jakub_Z.:
[MENTION=3389416]bean+[/MENTION]

I also had ondemand gov and 1134mhz max freq after flashing. But I don't bother with that ;)

Kernel runs really smooth and stable, loving it so far.
[Nexus 4 Android Development] Cristiano Lira:
Can confirm CM versions aren't booting.
[Nexus 4 Android Development] Jakub_Z.:
"Normal" hellscore also had problems with bootloops on CM and dev is still developing that.

So maybe thats the point? ;)
[Nexus 4 Android Development] spezi77:
Hum, that's weird because I used r03 and r04 (CM release) in my BeanStalk rom (which is based on CM-13).

Did it work before CM13 3/31?

Did you follow the installation instructions mentioned in the OP.. Could you maybe describe your installation steps?
[Nexus 4 Android Development] montbazon:
I used unsure nightly with r03. It did work well. And I tried to update version 31.3.2016 nightly, since the r04 was released. But it didn't boot.

I just wipe my dalvik cache and flash latest Rom, I am using then flash kernel. This is my step.

---------- Post added at 13:04 ---------- Previous post was at 12:58 ----------

Hellsgod doesn't have N4. I think it's hard to fix by hellsgod.

And this kernel was working well before 31.3
[Nexus 4 Android Development] kol1124:
Install version r03 first on the stock kernel, boot and then install the newest r04. It's works I checked each nightly ?

Wysłane z mojego Nexus 4 przy użyciu Tapatalka
[Nexus 4 Android Development] spezi77:
You have a good point. I will make a build and conduct benchmark to see if there is an improvement.

I have to admit that I probably don't know too much about GPU governors. Currently I use ondemand by default. Maybe simple governor is worth a try? I have read that it will allow a more fine grained control over how the gpu scales up and down than the default ones.
[Nexus 4 Android Development] spezi77:
Ah ok. Let me explain. In r04 I decided to remove a script inside anykernel which is meant to set the default CPU gov to hellsactive in the existing ramdisk of your kernel. This trick allows dirty-flashing r04 over a previous hellspawn.

I guess that I should have mentioned this in the OP. I will update now the installation instructions.

Thanks for your feedback, highly appreciated! :good:
[Nexus 4 Android Development] Cristiano Lira:
r04-CM doesn't boot on Exodus, just r03.
[Nexus 4 Android Development] spezi77:
And you already tried to dirty-flash r04 over r03?
[Nexus 4 Android Development] Cristiano Lira:
Tried just now, it worked. Thanks!
[Nexus 4 Android Development] kanishkad:
This one, the one about PowerHAL:
[Nexus 4 Android Development] spezi77:
Afaik, this one is ROM specific. I don't know how to fix on kernel level. I have removed it in the device tree, which I use to compile my BS ROM.

Could you point out to me a kernel which does not produce this error msg?

Sent from my beanstalk'd & hellspawn'd N4.
[Nexus 4 Android Development] jer_ying_fd:
If I remember correctly, mirage kernel fixed this.
[Nexus 4 Android Development] kanishkad:
Taurus also I think, but I'm not certain. Can't test at the moment ?
[Nexus 4 Android Development] txuki2005:
[MENTION=5091819]spezi77[/MENTION] check my anykernel to fix "power-hal" log.
[Nexus 4 Android Development] stormPremier:
Arf, i'm trying but can't find it, even with the search engine :eek:
[Nexus 4 Android Development] spezi77:
Woops, my mistake. I meant the BS ROM thread. Get it from here: http://xdaforums.com/showthread.php?p=66845893

Sent from my beanstalk'd & hellspawn'd N4.
[Nexus 4 Android Development] .stendeck:
Just as a small reminder: I really would like to test r11 but it doesn't seem to work alongside with SuperSU (at least on Fake Nexus ROM). Is there anything I can do to run both? Is it a ROM related issue? But why isn't there any problem with r9.5?
[Nexus 4 Android Development] jer_ying_fd:
Can confirm
[Nexus 4 Android Development] kanishkad:
Should be ROM related. Working fine here on Resurrection Remix.
[Nexus 4 Android Development] kanishkad:
[MENTION=5091819]spezi77[/MENTION] Reporting another issue..

The phone gets stuck on the Google logo when rebooting sometimes. Almost all the time it reboots to the Google logo at least 2 times & sometimes 3. Rarely, it never proceeds to boot the ROM. However, switching off and powering it back up has a less chance of getting stuck forever. Even then, it boots to the Google logo at least 2 times. Haven't faced this with any other kernels. Anyone else can confirm this?
[Nexus 4 Android Development] dragos281993:
How did you move between kernels ?
[Nexus 4 Android Development] kanishkad:
Flashed the stock kernel & then flashed HellSpawn, then rebooted. This problem is not introduced with the latest update. It was there when I first started using this kernel.

Were you able to reproduce it? :o
[Nexus 4 Android Development] dragos281993:
Nope.
[Nexus 4 Android Development] kanishkad:
Flashed Taurus just now to confirm and it boots properly. Strange :confused:
[Nexus 4 Android Development] dragos281993:
Try doing a cache + dalvik cache wipe, just in case.
[Nexus 4 Android Development] kanishkad:
I'm planning to clean flash with the next ROM update. Thank you for your response :)
[Nexus 4 Android Development] spezi77:
Which is your base ROM?

Sent from my beanstalk'd & hellspawn'd N4.
[Nexus 4 Android Development] Cristiano Lira:
I have the same problem, sometimes it gets stuck on Google logo and I have to press vol down + power to power off then power on. Another thing, I think r11 final build introduced a issue with the phone doesn't dozing well, with "Idle" consuming 4% or more battery, in Quanta v16 I think it's the same but with the stock kernel of the rom I use (DU) the phone is dozing well and with r11 test build 2 also. It could be the commits from Quanta, what you think, [MENTION=5091819]spezi77[/MENTION], you noticed this too?
[Nexus 4 Android Development] kanishkad:
Resurrection Remix
[Nexus 4 Android Development] TheArt.:
Same here
[Nexus 4 Android Development] spezi77:
If this should reoccur, please immediately boot into recovery and save the last_kmsg for me.

Connect to phone via "adb shell", then type:

cat /proc/last_kmsg > /sdcard/last_kmsg.txt
[Nexus 4 Android Development] spezi77:
Hum, do you mean that it doesn't reach deep sleep state. Do you have shorter battery life, now?

Could you please go back to v9.5 and let me know if the issue is not therein?
[Nexus 4 Android Development] kanishkad:
I will :) I also can confirm the battery life degradation. Last night it was at about 30% & I found the battery completely drained and the phone switched off in the morning. Thought it was my battery.
[Nexus 4 Android Development] Cristiano Lira:
It does deep sleep but the problem is that it takes too much time to enter on this state and also the phone is awake when screen is off way more time than before. For example, when I fully charge then unplug the charger and don't wake up the screen for like 5 minutes when I wake the screen it's already in 98%. Everything is fine with r9.5 here.
[Nexus 4 Android Development] spezi77:
Fixed in r12. Enjoy! :D

Furthermore, added power efficient workqueues (enabled per default). This can be controlled in KernelAdiutor (Schedule workqueues on awake CPUs to save power).

View attachment 3758728
[Nexus 4 Android Development] Cristiano Lira:
You are fast! Thank you, spezi, you are awesome.

---------- Post added at 11:06 AM ---------- Previous post was at 10:32 AM ----------

Got a sod after waking the phone from sleep. First I wasn't able to unlock my phone (touchscreen didn't respond) then after the screen went off again it won't wake up anymore then it auto-rebooted. I took a last_kmsg but don't know if anything went into it.

last_kmsg: http://pastebin.com/tuC32MXu

Edit: k, after cleaning up KA data and rebooting so it won't apply any setting at boot I didn't get any more sod. Congrats, spezi77, this build is pretty solid and you have put very nice commits on it. (y)
[Nexus 4 Android Development] spezi77:
You are also fast! Thanks for your prompt feedback, highly appreciated! ;)

Phew, I am relieved to hear that you got no more SoDs. Btw, the last kmsg is not about hellspawn kernel. It says: Linux version 3.4.0-Bricked-TWRP-Edition..

Sent from my beanstalk'd & hellspawn'd N4.
[Nexus 4 Android Development] :
how do I install the kernel?
[Nexus 4 Android Development] Mrcactuseater:
Are you joking?
[Nexus 4 Android Development] tom0769:
1st: choose the right kernel (aosp, cm) for your rom

2nd: if you already flashed a custom kernel, dirty flash your current rom. If not, skip this step.

3rd: simply flash the kernel in recovery.

If you do not unterstand the procedure, just learn some basics before flashing anything.
[Nexus 4 Android Development] spezi77:
You were posting in the wrong thread, I guess. ;)

I added quite a few things from Mirage kernel. Those patches were for increased performance, stability and battery life (e.g. add NEON optimized SHA1, SHA256, and SHA512 crypto code, added system wide power_efficient workqueues, added msm memutils, removed many unnecessary options, removed PMEM completely, deactivate unnecessary debug logging, Linux 3.4.x patches).

I did a benchmark with Antutu and r12 has received appr. 1.500 points more than r11 (using autosmp/hellsactive)

Are you on r12?
[Nexus 4 Android Development] Cristiano Lira:
Yes, it's from r9.5 I guess. It occured again: I just woke up the screen and wasn't able to unlock the screen as before then the phone won't wake up anymore after screen went off, and auto-rebooted after a while. last_kmsg was not saved.
[Nexus 4 Android Development] mathorv:
ROM:Chroma 05/04/2016

Kernel: hellspawn-N4-mm-6.0-r12-AOSP-UBER-TC7.0.zip

Flashing results in black screen after rom boot animation.

Wiping cache/dalvik doesn't help. Screen goes black at the point there should be app updating screen.

Going back to 9.5utc7 immediately fixes the problem

Should there be reinstallation of ROM due to huge changes or r12utc5.3 is stable?

Kernel r9.5utc7 is very stable and battery efficient.

On r11utc7 there was battery drain. 3%/hour.
[Nexus 4 Android Development] spezi77:
Thanks for your report. I will have to reproduce your scenario in a few days to see what could have went wrong.

On my BS ROM everything works like a charm.. I also don't get into the issue
[Nexus 4 Android Development] Thrikiller18:
Yes I'm using it right now. Battery life and smoothness are better than r11. Thx for anwser btw
[Nexus 4 Android Development] mathorv:
Tested:

r12utc5.3 same result black screen as r12utc7

r12utc7 after flashing rom, it also results in black screen.

PS

I use xposed v84 which can eventually be a culprit
[Nexus 4 Android Development] stormPremier:
Few ^^

I tested all since r9, and everytime i've enough "mind" data, i'm going here to tell ... everything that was already told xD

Anyway, i didn't really understand, now there is so mush governor and hotplug (talking about CPU).

I'm wondering ... I'm using intellimm, awesome, but i don't know HOW to choose hotplug since they seems all fine...

How do you choose your hotplug ?

I don't playing game so mush (except boom beach from time to time)

Listening a lot of music (through spotify btw).

Using AutoMate some times too ... this one is a battery killer :(
[Nexus 4 Android Development] spezi77:
Yes, xposed is very likely the culprit.

I just flashed Chroma, and here is no problem so far..

View attachment 3760088
[Nexus 4 Android Development] spezi77:
I have added quite a few of them for experimental purposes and to offer greater variety. Sometimes you may want to boost up your device to become fast as hell for gaming, sometimes you need an extensive battery life.

Edit: I have added some pieces of information about the different CPU governors and hotplug drivers that come along with this kernel: http://xdaforums.com/showpost.php?p=66103116&postcount=3.

Which kernel tweaker do you currently use? My personal recommendation is to use Kernel Adiutor Mod which has been further enhanced by [MENTION=4231562]Yoinx[/MENTION] .
[Nexus 4 Android Development] math.rangel:
Every since I flashed r12 I'm having the stuck on boot problems. I tried clean flashing and then flashing r9.5, and now I'm having this in all hellspawn versions
[Nexus 4 Android Development] spezi77:
I'm sorry to hear about this.

Please try these steps.

Dirty flash your ROM to revert to the original kernel. Then wipe cache/dalvik cache and flash hellspawn.

Sent from my beanstalk'd & hellspawn'd N4.
[Nexus 4 Android Development] math.rangel:
Still not working, man :/
[Nexus 4 Android Development] spezi77:
Can you do a dmesg?

ADB shell

dmesg

Sent from my beanstalk'd & hellspawn'd N4.
[Nexus 4 Android Development] stormPremier:
[MENTION=7251729]math.rangel[/MENTION] when i'm locked, i'm flashing original image from google ... then go back through all basic steps : root, install recovery, install WTFYW ... always work for me even in the worst case ^^'

Yup thanks for page, i'm on BS rom (just updated to 6.17), using your modded kernel aduitor =)

When i was asking about how choosing hotplug, i was talking about how do know which one is best for you ... For governor, just by testing them for one day or sometimes even one hour is enough ... but i don't feel big differences when changing hotplug sooooo ... Thanks for your link, that was what i expected =D
[Nexus 4 Android Development] spezi77:
For performance I use pegasusq with zen-decision or hellsactive with autoSMP. For increased battery life, I use intellimm or smartmax with alucard-hotplug.

Sent from my beanstalk'd & hellspawn'd N4.
[Nexus 4 Android Development] starkly_raving:
R12 working great on latest Chroma and Pure Nexus. For the user having issues booting into black screen I'd recommend flashing the latest factory image and rerooting ... especially if a clean flash of your ROM or a nand restore didn't work.
[Nexus 4 Android Development] str3tch72:
R12 seems to be smoothest version ever. Working good on Krexus.

Wysłane z mojego Nexus 4 przy użyciu Tapatalka
[Nexus 4 Android Development] math.rangel:
So, last night I decided to do what they said. Went to 5.1.1 official images, then flashed the recovery and finally tried the rom I'm using and Hellspawn r9.5 and I got the Google stuck logo again. I'm using Turbo ROM. Do you think it's rom-related? Quanta boots fine
[Nexus 4 Android Development] sidnoit22:
Which ROM you are using?
[Nexus 4 Android Development] jer_ying_fd:
He said he's using Turbo rom. Btw, did you manage to get root to work with Fake Nexus May builds in R12?
[Nexus 4 Android Development] ivanich:
Stuck at Google logo is common problem for this kernel from the beginning, but there is a simple workaround, just power off phone with power button and then turn it on. However it happens for me almost each time I flash ROM+this kernel.
[Nexus 4 Android Development] Cristiano Lira:
Yeah, it mostly happens after flashing anything on recovery and rebooting directly to system.
[Nexus 4 Android Development] sidnoit22:
Yes but now I have switched to BeanStalk ROM, which is better in optimizations and overall.
[Nexus 4 Android Development] Thrikiller18:
I am thinking about switching to beanstalk. Is battery life ok? Cuz cm roms have problems with battery life.
[Nexus 4 Android Development] sidnoit22:
Battery is much more good and overall experience is good, very fast! Even I don't like CM based ROM but this one is good HellsPawn and the creator of this ROM are the same guy. :cowboy:
[Nexus 4 Android Development] cemilplt:
Thanks [emoji4]
[Nexus 4 Android Development] spezi77:
You are welcome. What is your config? :eek:

Edit: I am asking because the best score I have reached has been 35.874 with Zen-Decision and PegasusQ...
[Nexus 4 Android Development] jacomail95:
R12 is a beast, really impressive, thanks [MENTION=5091819]spezi77[/MENTION], great work :thumbup:

Inviato dal mio Nexus 4 con Tapatalk 2
[Nexus 4 Android Development] cemilplt:
There has not been any tweak settings and Temasek ROM / nano gapps / hellspawn r12-5.3cm / new adreno may 2016 (mob30j)

---------- Post added at 04:11 PM ---------- Previous post was at 04:05 PM ----------

I've never done it already, unfortunately I do not know these settings???
[Nexus 4 Android Development] spezi77:
In case that you might become interested in tweaking try this awesome app: http://xdaforums.com/showthread.php?t=3333549

Sent from my beanstalk'd & hellspawn'd N4.
[Nexus 4 Android Development] cemilplt:
Pure nexus/last nano/last adreno/hellspawn r12-5.3 tweak, and without any adjustment.???

---------- Post added at 01:43 AM ---------- Previous post was at 12:54 AM ----------

??? You do not need any tweak and setting the kernel you use Hellspawn???
[Nexus 4 Android Development] spezi77:
Yes, for getting a good performance you don't have to tweak anything, but use my defaults. However, I think that by changing CPU governor to Pegasusq you can reach a higher end score.

Furthermore, if you want to increase battery life you can change hotplug/governor to Alucard/Smartmax.

P.s.: sorry, if I am repeating this info. Should add this into FAQ section..

Sent from my beanstalk'd & hellspawn'd N4.
[Nexus 4 Android Development] lolrko:
what's the difference between UBERTC-5.3 and UBERTC-7.0
[Nexus 4 Android Development] Mrcactuseater:
Even though it's on almost every page in the forum, the difference is the performance and stability of the kernel. 5.3 for stability, 7.0 for performance.

Tapatalk'd from my Twisted, Despaired Nexus 5x
[Nexus 4 Android Development] dragos281993:
Tc 5.3 is the stable toolchain used to compile the kernel, and tc 7.0 is an experimental toolchain.
[Nexus 4 Android Development] lolrko:
sorry I have just seen it
[Nexus 4 Android Development] spezi77:
Added to FAQ section ;)

Sent from my beanstalk'd & hellspawn'd N4.
[Nexus 4 Android Development] Trickster22:
Got this awesome score, hellspwan r 12, beanstalk rom latest and may adreno drivers.
[Nexus 4 Android Development] spezi77:
Unbelievable, which hotplug/governor combo do you use? :eek:

Edit: and from where did you get the may adreno drivers?
[Nexus 4 Android Development] Trickster22:
Thanks to you master. It's all unmodified from rom to kernel. Just flashed rom, restored antutu from T.B and tested it. And yes it's without gapps. I was trying to flash open gapps ( nano ) but it failed cause of space so left it there as i only wanted tontest battery life and performance. Awesome rom sir you rock even kernel is amazing it includes everything I needed to complete my n4
[Nexus 4 Android Development] dragos281993:
May Adreno drivers:

https://www.androidfilehost.com/?fid=24562946973630524
[Nexus 4 Android Development] spezi77:
You are welcome. This is indeed a proof that installing gapps has a negative impact on overall performance!
[Nexus 4 Android Development] Trickster22:
Yes looks like that's only the reason. Here is link for may drivers http://xdaforums.com/showpost.php?p=67013707&postcount=112
[Nexus 4 Android Development] spezi77:
Hey there, I am about to compile a new test build.. anyone interested? Please pm me.

Sent from my beanstalk'd & hellspawn'd N4.
[Nexus 4 Android Development] bart.found:
what's new?
[Nexus 4 Android Development] .stendeck:
Does it work with any ROM + SuperSU this time? <- By that, I mean specifically Fake Nexus ROM. ;)
[Nexus 4 Android Development] spezi77:
Maybe no, maybe yes.

You tell me..

Sent from my beanstalk'd & hellspawn'd N4.
[Nexus 4 Android Development] spezi77:
Increased performance especially for Ondemand governor.

Sent from my beanstalk'd & hellspawn'd N4.
[Nexus 4 Android Development] dragos281993:
Hey, buddy ! I think the best thing to do would be to have the test build posted here so more than 1 user could test it. 2, 3 people would be enough mainly because a single person can't put the phone through all the scenarios possible. While for one the test would be completely stable, the other tester might actually run into something the other didn't experience.

It's my point of view though. I'll gladly test it but I'm afraid I might not stress it enough with my usage. I'm waiting for your opinion on this one.
[Nexus 4 Android Development] spezi77:
Agreed.

Guys, here you are..
[MENTION=6262409]Mrcactuseater[/MENTION] [MENTION=4057901]kol1124[/MENTION] [MENTION=5337411]Cristiano Lira[/MENTION]

hellspawn-N4-mm-6.0-r13-test-AOSP-UBERTC-5.3.zip

hellspawn-N4-mm-6.0-r13-test-AOSP-UBERTC-7.0.zip

hellspawn-N4-mm-6.0-r13-test-BS-UBERTC-5.3.zip

hellspawn-N4-mm-6.0-r13-test-BS-UBERTC-7.0.zip

hellspawn-N4-mm-6.0-r13-test-CM-UBERTC-5.3.zip

hellspawn-N4-mm-6.0-r13-test-CM-UBERTC-7.0.zip
[Nexus 4 Android Development] dragos281993:
May I ask for a short changelog ? If there are changes in the ramdisk people might need to reflash the stock boot.img first.

Ok, I'll flash it right away. And you've posted it at the right time as well. My battery just got fully charged a few minutes ago. ?
[Nexus 4 Android Development] spezi77:
No ramdisk changes.

* cpufreq: interactive updates

* cpufreq: conservative updates

* cpufreq: ondemand updates

* etc.
[Nexus 4 Android Development] Mrcactuseater:
Neat, cheers man!

Tapatalk'd from my Twisted, Despaired Nexus 5x
[Nexus 4 Android Development] dragos281993:
The first thing I noticed, is that there's no Voltage section in KA Mod. Did you purposely remove it ? I don't mind it though. UVing is not something I usually do anyway.
[Nexus 4 Android Development] .stendeck:
I've done some tests now. Seems that the latest SuperSU (v2.74-2) fixes all previous problems with Fake Nexus ROM:

first, I've tested v13-test build with latest SuperSU: directly works

second, I tried v11 again (that previously didn't work with SuperSU ≤ 2.72) with latest SuperSU: directly works

So, at least for me: I'm happy now. :D I'm going to run v13-test build the next days.
[Nexus 4 Android Development] Cristiano Lira:
The new testbuild is from k3.18-new branch? I am suspecting this because the other time you did a testbuild for us it didn't had voltage control which is also true now. :D