yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Android Development] spezi77:
It seems that you don't trust my words? You can check my commits to change your opinion. Ondemand in this kernel is indeed based on stratosk's work.

https://github.com/spezi77/hellspawn-N4/commits/mm-6.0?page=10

Sent from my beanstalk'd & hellspawn'd N4.
[Nexus 4 Android Development] emraz786:
it was just a confusion, I apologize for the misunderstanding. Thank you

Enviado desde mi Nexus 4 mediante Tapatalk
[Nexus 4 Android Development] Cristiano Lira:
[MENTION=5091819]spezi77[/MENTION], with thunderx governor, when a CPU core reachs highest freq it gets stuck at that freq.

Edit: it happens with others governors as well, at least with smartmax.
[Nexus 4 Android Development] colin p:
Just flashed hellspawn-N4-mm-6.0-r13-test-#2-CM-UBERTC-7.0.zip over 9.5 and so far everything seems ok. Even SuperSu doesn't puke. Good job. I'll be sure to shout if anything untoward happens.
[Nexus 4 Android Development] McLongDong:
When you say "juiced up", do you mean the phone will have better battery life or better performance?
[Nexus 4 Android Development] dragos281993:
Yes, he means better battery life without noticeable loss in the UX performance.
[Nexus 4 Android Development] spezi77:
For which hotplug?

Sent from my beanstalk'd & hellspawn'd N4.
[Nexus 4 Android Development] spezi77:
I just quoted the comments by the original author. In my understanding he refers to battery life. ;)

Sent from my beanstalk'd & hellspawn'd N4.
[Nexus 4 Android Development] Cristiano Lira:
Thunderplug, Mako, Alucard, AutoSMP, Zen and Dyn. Tested thunderx and the issue happens in every hotplug.
[Nexus 4 Android Development] spezi77:
I see, and I was also able to reproduce this behavior. Thanks for your report. I don't know if I really find the time to fix this. Maybe the best would be to remove thunderX in the next official build?! ;)
[Nexus 4 Android Development] spezi77:
I have added dyn_hotplug controls into KernelAdiutor-Mod. You can get my test build from this post..

P.S.: Today I also flashed PA + r13, and it looks very nice! :p
[Nexus 4 Android Development] dragos281993:
I tried PA too. I managed to live with it for a day. I had to flash Xposed and install Gravity box in order to give me back some features I had on PN. Then I got system ui crash which didn't go away even after dirty flashing the ROM so I ended up flashing PN again and felt whole again. LOL. Beans is rebuilding PN for maximum stability and some improvements so I'm really excited about that.

I'll flash r13 and test the new hotplug. I suspect it will be awesome considering that Stratosk made it for mako.
[Nexus 4 Android Development] dragos281993:
Nevermind. I fixed it.
[Nexus 4 Android Development] spezi77:
[MENTION=3118524]xenyz[/MENTION] I did a build with your suggested tweak. In case that you are interested in, get the cm build from here: https://www.androidfilehost.com/?fid=24459283995311372

However, if compared with the official r04, it gets a lower Antutu score. But I have doubts whether that Antutu benchmark app really works in a reliable way. It seems to me that conducting benchmarks gives different scores depending on whether the phone or Antutu or both are in a good or bad mood... :p
[Nexus 4 Android Development] Cristiano Lira:
Can you build AOSP?
[Nexus 4 Android Development] bean+:
yes, please create an AOSP build with [MENTION=4052139]xenyx[/MENTION] changes, thanks.
[Nexus 4 Android Development] spezi77:
Alright, here you go.. ;)

https://www.androidfilehost.com/?fid=24459283995311371
[Nexus 4 Android Development] bean+:
That was really fast... dirty flashed the R04 alpha-test AOSP-Version.

Just testing row(readahead 1024kB)/elementalX (with [MENTION=5091819]spezi77[/MENTION] governor defaults), 94/1512Mhz (min/max), cpu boost 1000ms, wakeup-boost enabled, GPU 400/ondemand, DT2W, FSync disabled.

Cant test GPU/simple, after a few seconds KA is on GPU/ondemand again (installation default). I am not as experienced as you guys, any suggestion/recommendation concerning the selected i/o-scheduler, cpu/gpu-governor?

[MENTION=5091819]spezi77[/MENTION], what was the configuration for your Antutu tests?
[Nexus 4 Android Development] spezi77:
In alpha-test build you should use CPU: elementalx. 94/1512Mhz.

In general my defaults are.

GPU: ondemand.

I/O: bfq. Read ahead: 1024k.

Fsync: off.

P.s.: don't mind Simple GPU gov. It doesn't work either in UKM. I guess that it has an issue.

Sent from my beanstalked N4.
[Nexus 4 Android Development] xenyz:
Nice, I'm running it now and it works exactly as it should. Checking with Trepn profiler shows it working as intended, and it also shows that the GPU hangs around 320 MHz a lot, which is why it didn't work well before.

It could be worth trying the simple GPU governor. If it can get the GPU to 128 or 27 MHz when idle, it could be worth reverting the tweak, but for now it's fine.

However, one thing I noticed could be a real problem. I came from r03, and Android System (system_server) CPU usage was really low, usually lower than Android OS (kernel) on battery stats. This is similar to hells-Core b88. On r04 alpha, system_server usage is way up, similar to stock kernel. If I have it right, it must be something in the Dmitry patch set that is causing system_server to hog the CPU.

It could be worth breaking the patch set out into multiple alpha tests to find what is causing it. If you want a place to start, check these messages I'm seeing in dmesg

[ 6551.540972] cpufreq_stats_platform_cpu_power_read_tables asked for too many values (wanted 15 have 12)
[ 6551.542987] cpufreq_stats_platform_cpu_power_read_tables asked for too many values (wanted 15 have 12)

I think hellsgod actually already commited Dmitrys patches, reverted them, and finally picked which were necessary for mako, if you check the commit history around b84 or b85. They may not even be necessary at all, but I can't be sure.
[Nexus 4 Android Development] spezi77:
Thanks for your prompt feedback, it feels like we are doing a real development thread now :D

About Dmitrys patches: I have discovered a few error messages related to uid-cputime, and after applying the patches it was gone. However, maybe it added some overhead, and probably can be safely reverted as we didn't face any major issues in r03 and lower.

Alright, I plan to deliver more alpha-test builds:

* current alpha-test build with fully reverted Dmitrys patches

* current alpha-test build with partial revert of Dmitrys patches (keep partial-resume framework and deduce wakeup reasons, USB/MIDI update, IPV6 update)

* Add working simple GPU gov and revert gpu boost tweak in elementalx

Anything else?

Stay tuned..
[Nexus 4 Android Development] spezi77:
[MENTION=3118524]xenyz[/MENTION] [MENTION=3389416]bean+[/MENTION] [MENTION=5694024]elbotty[/MENTION] [MENTION=4057901]kol1124[/MENTION] [MENTION=3413850]mischler[/MENTION] [MENTION=4973320]str3tch72[/MENTION]

here we go.. I decided to start with the following builds:

01: current alpha-test build with fully reverted Dmitrys patches

** hellspawn-N4-mm-6.0-r04-alpha-test-aosp-01.zip

** hellspawn-N4-mm-6.0-r04-alpha-test-cm-01.zip

02: current alpha-test build with partial revert of Dmitrys patches (keep partial-resume framework and deduce wakeup reasons, USB/MIDI update, IPV6 update)

** hellspawn-N4-mm-6.0-r04-alpha-test-aosp-02.zip

** hellspawn-N4-mm-6.0-r04-alpha-test-cm-02.zip
[Nexus 4 Android Development] kol1124:
Great to see that! Of course I'll be test it bro ?

Keep it up! [MENTION=5091819]spezi77[/MENTION]

Wysłane z mojego Nexus 4 przy użyciu Tapatalka
[Nexus 4 Android Development] spezi77:
[MENTION=3118524]xenyz[/MENTION] [MENTION=3389416]bean+[/MENTION] [MENTION=5694024]elbotty[/MENTION] [MENTION=4057901]kol1124[/MENTION] [MENTION=3413850]mischler[/MENTION] [MENTION=4973320]str3tch72[/MENTION]

Further alpha builds with Simple GPU governor arrived. I decided not to mix the full/partial reversion of Dmitry patches into this one., which means that those builds still contain the full set of Dmitry patches.

01: Added Simple gov and kept GPU boost at level 0:

** hellspawn-N4-mm-6.0-r04-alpha-test-aosp-simple-gpu.zip

** hellspawn-N4-mm-6.0-r04-alpha-test-cm-simple-gpu.zip

02: Added Simple gov and reverted GPU boost at level 0:

** hellspawn-N4-mm-6.0-r04-alpha-test-aosp-simple-gpu-revert-boost.zip

** hellspawn-N4-mm-6.0-r04-alpha-test-cm-simple-gpu-revert-boost.zip

Happy testing.. :good:
[Nexus 4 Android Development] spezi77:
You are welcome, bro. Nice to see that you are interested in it, as well. :good:

@ everyone: Take your time, we should not be in a rush while testing, in order to obtain proper test results.
[Nexus 4 Android Development] jacomail95:
Finally a new kernel for our glorious mako, i'll be more than happy to test it, thanks dear spezi77 :D:thumbup:

Inviato dal mio Nexus 4 con Tapatalk 2
[Nexus 4 Android Development] Cristiano Lira:
I'm seeing a problem with frequency handling. I don't know if it's just with the conservative governor but the mininum frequency of core 2 is setting itself for 1026 Mhz after a while and I have to set the CPU minimum frequency to 384 then again to 94 MHz to get it back to normal, but it all start again just after a few minutes.

Edit: it occurs with the others governors as well.
[Nexus 4 Android Development] filjusz:
Check if You have touch boost enabled bro ?
[Nexus 4 Android Development] Cristiano Lira:
I don't need to touch the screen to it happen and, by the way, input boost frequency from all cores is set to 384 MHz. Even if I disable it for all cores it remains the same.
[Nexus 4 Android Development] str3tch72:
Nice to have alot of versions to test! #FlashoholicAlert :D will test asap!

Wysłane z mojego Nexus 4 przy użyciu Tapatalka
[Nexus 4 Android Development] Aphex33:
Thanks for your work! Remember you from the Desire forums.
[Nexus 4 Android Development] Cristiano Lira:
[MENTION=5091819]spezi77[/MENTION], anything?
[Nexus 4 Android Development] spezi77:
First off, thanks for reporting your observation. I had a quick look into the cpu-boost feature, and I think that I lost one "deadlock fix" along the way. I added this back: https://github.com/spezi77/hellspawn-N4/commit/577c85d9873200bcee16051c49af00995608637f

That's all I could do this evening. I only managed to did a quick test, and I seemed to me that this bizarre issue is gone. *fingers-crossed* Please conduct further test on your end, and let me know..

Cheers! ;)

New test builds:

** hellspawn-N4-mm-6.0-r04-aosp-test-cpuboost-fix.zip

** hellspawn-N4-mm-6.0-r04-cm-test-cpuboost-fix.zip
[Nexus 4 Android Development] mubaidr:
Using this kernel and ka-mod, voltage settings does not seem to stick. BTW I have two profiles both undet-volted.
[Nexus 4 Android Development] mathorv:
Great work stable again

chroma_mako-2016-06-09

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

with xposed 0.85 and loads of modules. Only v12 had issues with black screen. This is no longer a problem.
[Nexus 4 Android Development] ivanich:
There is something wrong with ondemand governor in r13-test2, it won't stick at 384 Mhz, most of the time it runs at higher freqs.

Отправлено с моего Nexus 4 через Tapatalk
[Nexus 4 Android Development] emraz786:
I'm using on demand in r13 test 2 and I have no problems, in fact the frequency used is 384 mhz more

Enviado desde mi Nexus 4 mediante Tapatalk

---------- Post added at 10:13 PM ---------- Previous post was at 10:12 PM ----------

Enviado desde mi Nexus 4 mediante Tapatalk
[Nexus 4 Android Development] dragos281993:
The behaviour should be due to the new hotplug. It's not a problem though. For me everything works well and the way the frequencies scale up and down gives me a good experience. Nice and smooth.
[Nexus 4 Android Development] ivanich:
I have this issue with AutoSMP hotplug and only with r13-test2, anyway hotplug is nothing to do with governor freqs, it responsible only for cores on/off logic.
[Nexus 4 Android Development] spezi77:
I compiled a new version of KA-Mod (dyn_hotplug controls: fix logic to correctly set min/max CPUs online).
[Nexus 4 Android Development] spezi77:
r13 official build just arrived.
[Nexus 4 Android Development] Gamernivek:
Running PA 6 with r13 and OTG isn't working for me. First time with the Kernel; any advice? Using a modified KAM found here to enable the setting: http://xdaforums.com/showpost.php?p=66845893&postcount=513
[Nexus 4 Android Development] txuki2005:
[MENTION=5091819]spezi77[/MENTION] check github ;)
[Nexus 4 Android Development] spezi77:
Have you installed my KernelAdiutor-Mod from two posts above? In KA go to Misc Settings and enable MSM OTG. After this it should work fine.

Sent from my beanstalk'd & hellspawn'd N4.
[Nexus 4 Android Development] Cristiano Lira:
[MENTION=5091819]spezi77[/MENTION], when switching governors using mako hotplug (don't know about others) sometimes KA freezes and when it happens the next time the phone screen goes off it immediately enters in a sod state.
[Nexus 4 Android Development] spezi77:
Thanks for finding this, I will have a look into it. First of all, we should identify where the root cause is, is it related to kernel or KA?!

Sent from my beanstalk'd & hellspawn'd N4.
[Nexus 4 Android Development] Gamernivek:
Ya, that's what I tried - no go. My OTG cable is providing power correctly to my Flash Drive, but when I plug in the phone, it bypasses the drive and just charges the phone. Order that I plug them in doesn't matter either. Wondering if it has to do with the latest PA.

Edit: Apparently order does matter. Was able to get power to the drive by plugging it in second. Still doesn't show up with Stickmount though as an available mount.

Edit 2: My bad, I installed a previous version of the mod. Latest you described also seems to have no effect.

Edit 3: I have absolutely no idea what I did, but it just started working! Maybe the 10+ resets did something. I also installed some kind of OTG diagnostic tool by Chainfire that installed some kind of patch, but it didn't have an immediate effect.
[Nexus 4 Android Development] mubaidr:
I have switched back to taurus kernel for now and voltage settings seems to be fine with this.
[Nexus 4 Android Development] xenyz:
Voltage settings work just fine, but it's probably best to leave them stock.

BTW if anyone is interested, here is my 'Semaphore mode' setting for HellSpawn :)

# governor
echo 8 > /sys/devices/system/cpu/cpufreq/ondemand/down_threshold
echo 1 > /sys/devices/system/cpu/cpufreq/ondemand/io_is_busy
echo 4 > /sys/devices/system/cpu/cpufreq/ondemand/sampling_down_factor
echo 20000 > /sys/devices/system/cpu/cpufreq/ondemand/sampling_rate
echo 55 > /sys/devices/system/cpu/cpufreq/ondemand/touch_load

#hotplug
echo 1 > /sys/module/dyn_hotplug/parameters/enabled
echo 6 > /sys/module/dyn_hotplug/parameters/down_timer_cnt
echo 75 > /sys/module/dyn_hotplug/parameters/up_threshold

#cpu
echo 25 > /sys/devices/system/cpu/cpu0/cpufreq/util_threshold
echo 30 > /sys/devices/system/cpu/cpu1/cpufreq/util_threshold
echo 35 > /sys/devices/system/cpu/cpu2/cpufreq/util_threshold
echo 40 > /sys/devices/system/cpu/cpu3/cpufreq/util_threshold
[Nexus 4 Android Development] mubaidr:
I am having issues if i use multiple profiles (gaming and power saving). I think it does make difference, phone runs a little cooler when gaming with undervolt.
[Nexus 4 Android Development] tvisforme:
Hi, I'm still having the issue where SuperSU and HS kernel don't get along. I've just tried installing with v13 and it is still either HS kernel with no root, or root with the standard cm13 kernel. I'd be happy to try the new version with the old installer, I'm just not comfortable with building it myself.
[Nexus 4 Android Development] momojuro:
Good morning,

Really sorry for this off-topic but can someone share for me Hellspawn's (or any other kernel like Taurus) CFQ I/O scheduler's tunables (slice_async value, fifo_expire ect..) ? I need them for my personal usage. :)

Thanks in advance !
[Nexus 4 Android Development] spezi77:
Thanks very much for sharing this. :good: I have taken over your settings as new defaults. See https://github.com/spezi77/hellspawn-N4/commit/357281afa662ba05bac2eebf4c66e55c66fa33ea

Only one remark.

echo 1 > /sys/module/dyn_hotplug/parameters/enabled

Afaik, the value pair is Y/N and not 0/1 as in your example. At least that is how it is implemented at the moment in KA-Mod App. I don't know whether both variants are supported, but 0/1 has never worked for me in r13 (official build).

Edit: I did a few tests and it seems that you can use both variants for turning on/off dyn_hotplug. In case someone is interested:

root@:/ # echo 1 > /sys/module/dyn_hotplug/parameters/enabled

root@:/ # cat /sys/module/dyn_hotplug/parameters/enabled

Y

root@:/ # echo N > /sys/module/dyn_hotplug/parameters/enabled

root@:/ # cat /sys/module/dyn_hotplug/parameters/enabled

N

root@:/ # echo 0 > /sys/module/dyn_hotplug/parameters/enabled

root@:/ # cat /sys/module/dyn_hotplug/parameters/enabled

N

root@:/ # echo 1 > /sys/module/dyn_hotplug/parameters/enabled

root@:/ # cat /sys/module/dyn_hotplug/parameters/enabled

Y

root@:/ # echo 0 > /sys/module/dyn_hotplug/parameters/enabled

root@:/ # cat /sys/module/dyn_hotplug/parameters/enabled

N

root@:/ # echo Y > /sys/module/dyn_hotplug/parameters/enabled

root@:/ # cat /sys/module/dyn_hotplug/parameters/enabled

Y
[Nexus 4 Android Development] spezi77:
Good to know. Maybe KA-Mod has a little bug, so that the OTG setting didn't stick. Or maybe you rebooted your phone and that did it?! Who knows.. ;)
[Nexus 4 Android Development] colin p:
I haven't had any issues yet with r13 and SuperSu. As a matter of fact the only problem I have had was r12, all the others have worked. So whatever was causing the problem for me, seems to have been resolved. I don't imagine that it is a universal issue, as more people would have mentioned it, so it must be something peculiar to your set up that would require more investigation.

However, you said that you don't have root without SuperSu? You do realize that CM has a very capable native superuser that needs to be turned on in "developer options" correct?

Also, CM13 has a history of problems with SuperSU and the CyanogenMod Forums are filled with people not being able to get the binaries installed.

You could try the suggestion in post #732 "Could you do me a favor and copy the kernel zImage from r12 into the installer of r9.5? That would be very interesting.. " Seems easy enough, I know I would have gone that route if I was still having problems with SuperSu. I hope you figure it out, it would very interesting to find out what the resolution would be.
[Nexus 4 Android Development] spezi77:
Just in case that you would like to know what has been the resolution: https://github.com/spezi77/anykernel_msm/commit/638ee759d404b619ded8d2ba024b4370765b5960
[Nexus 4 Android Development] DingoDingo:
[MENTION=5091819]spezi77[/MENTION] I am long time Quanta user but when I saw that you included Semaphore ondemand gov and Dyn_Plug hotplug, I was very happy to try your kernel.

Everything is well except that Fsync is always dissabled, no matter if I enable it, as soon as I get out of Kernel Adiutor Mod (Build 12, both kernels r13 with UBERTC 5.4 and 7.0), Fsync is disabled. Is it a bug or it is mean to be like that? I always had Fsync enabled to avoid data loss.

Thanks for great kernel.
[Nexus 4 Android Development] Kaan_:
I can confirm the supersu issue, exactly the same problem as before. The supersu app complains about missing su binary.
[Nexus 4 Android Development] tvisforme:
Hello, thanks for the reply. With respect to the setup, it is pretty much a standard process. Flash CM13, then SuperSU, the HS kernel and finally OpenGapps. Wipe cache and Dalvik, reboot. This has worked for several years on this device, through CM11, CM12.1 and more recently CM13. It has only been recently - specifically, post-HS9.5 - that the problem has surfaced. Moreover, installing HS9.5 still works properly, hence my question about 12.

Yes, the root option was already enabled in developer options.

Thanks again, I did see that post as part of my initial inquiry. However, having poked around in the kernel file I did not feel confident in modifying a core part of the process.

---------- Post added at 09:57 AM ---------- Previous post was at 09:54 AM ----------

Thank you, I looked through the commit. I am currently reflashing the ROM, kernel and SuperSU with a wipe of /system to see if that helps.
[Nexus 4 Android Development] spezi77:
Reading through the posts by other users, I come to the conclusion that the problems with SuperSU is neither a problem in this kernel nor in the installation script. From now on I will ignore this topic..[emoji14]

Sent from my beanstalk'd & hellspawn'd N4.
[Nexus 4 Android Development] colin p:
Ah, I just noticed that too, fsync gets disabled after closing/ opening KAMOD
[Nexus 4 Android Development] Kaan_:
Ok, I'll just use other kernels. No harm.
[Nexus 4 Android Development] spezi77:
You are welcome! [emoji16]

I must admit that it is a bug. Furthermore there is a weakness in the installation script which is responsible for making the changes to the ramdisk.

I have already spend some time to improve the initial fsync setting, so it should be resolved in the next build.

Are you sure that you didn't forget to turn on "apply at startup" in KA? That would be the perfect workaround to get fsync enabled

And if that is still not working, then I recommend to wipe cache/dalvik-cache. Sometimes the process of dirty flashing can cause unwanted and bizarre side effects..

Sent from my beanstalk'd & hellspawn'd N4.
[Nexus 4 Android Development] tvisforme:
Spezi, I'm sorry to hear that. I would be more than happy to test the v13 kernel in the v9.5 package, I'm just not comfortable with assembling it correctly and cannot afford to inadvertently muck up my phone right now. All I know is that the v9.5 and earlier installations work with SuperSU every time I do it, whereas the v12 (and now v13) do not. Again, I would be happy to test what you suggested earlier.

Edit: I've just finished testing again. Installing HS12 or 13 after installing SuperSU interferes with SuperSU. Installing SuperSU after HS12 or 13 removes HS in favour of the default CM13 kernel. Using HS9.5, things install properly.
[Nexus 4 Android Development] Kaan_:
I need to also mention that selinux still can't be disabled either. This is without flashing supersu on your beanstalk rom. Here is the command output

"setenforce: Couldn't set enforcing status to '0': Invalid argument"

This command works with cm 13 and quanta kernel.

As for why I need it disabled(temporarily) is for override dns app and viper4android.
[Nexus 4 Android Development] snacs:
Hi [MENTION=5091819]spezi77[/MENTION], nice work man, very happy with #13.

In stable version you commited this settings from xenyz or you will commit it in next versions?
[Nexus 4 Android Development] spezi77:
I'm sorry for not being everyone's darling. I am just deving and building this kernel for my private purposes. I am primarily testing it on my BS ROM (which uses CM's built-in root) and on AOSPA ROM (flashing SuperSU without any issues).

I wasn't able to reproduce that SuperSU issue in r13.. If r9.5 is the only version which runs fine on your end, then you are probably better off to stay with it for now.. I can only find a fix, if someone provided me with an exact problem analysis which helps to identify the root cause.

I hope you got my idea and didn't get upset or get my comment in a wrong sense.. English isn't my mother tongue.

Sent from my beanstalk'd & hellspawn'd N4.
[Nexus 4 Android Development] spezi77:
It will become the new default settings in r14.

Sent from my beanstalk'd & hellspawn'd N4.
[Nexus 4 Android Development] tvisforme:
Don't worry, I did not see anything that would warrant getting upset. I'm most appreciative of your efforts in creating and maintaining this kernel. Again, I would happily test v13 (CM/7.0) for you and report the results if you or someone could package it in the 9.5 format. If you need more information to diagnose the issue, I can provide that, just tell me what to look for or what logs you might need. I've described the symptoms on this end as best I can.