yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Android Development] DingoDingo:
Just wiped cache and dalvik cache, still the same, the moment I go off the Misc Controls tab in KAMOD and return to Misc Controls, Fsync is disabled.

Just for info, I am on latest Pure Nexus and flashed PN boot.img prior install your kernel.

Hope you will manage to fix it, will stay for a while with your kernel for sure. Maybe forever, who knows[emoji2]
[Nexus 4 Android Development] tvisforme:
Spezi, I'm happy to report that I now have both SuperSU and HS 13 (w/UBERTC-7.0) coexisting on my N4. What is odd is how it ended up working. As noted above, I have repeatedly tried flashing SuperSU and HS 12/13 without success. Out of curiosity, I flashed the v13 UBERTC-5.4 CM13 version and found that it worked with SuperSU. I then went back and reflashed everything (ROM/SuperSU/kernel/Gapps) with the v13 UBERTC-7.0 kernel and it worked properly.

Is it possible that there is a slight difference in the two installers (5.4 and 7.0) in how they set up the ROM?
[Nexus 4 Android Development] Kaan_:
I just copied v13 zimage into the 9.5 zip and flashed that, selinux issue remains.
[Nexus 4 Android Development] bean+:
Installed hellspawn r13 tc7 aosp yesterday, wiped dalvic/cache before and after hellspawn installation. I am on the latest pure nexus aosp rom. I do not have any problems with supersu 2.74. I use my phone for business and private purpuses almost the whole day, never observed a sod with this kernel. And I am using hellspawn since it appeared on xda. For me, hellspawn seems to be rocket stable, it is the best kernel for my n4 i ever had. I am running autosmp/pegasusq, which make my phone really fast and responsive. I use KA to switch kernel options.

Some time ago i thought about to buy a n5x because my n4 was laggy (money is not the problem). But due to hellspawn i will keep my old n4. I really love this kernel with all the options it provides. Thanks so much to [MENTION=5091819]spezi77[/MENTION] for this fantastic job, Danke!
[Nexus 4 Android Development] pratamaaudi:
hey [MENTION=5091819]spezi77[/MENTION] your kernel is the best

but it wasn't work on version 12 and above

so i stuck at version 11

i dont know what happened but it just wont pass the bootanimation if i user version 12 and above

thanks bro

nexus 4

nitrogen os

hellspawn r11
[Nexus 4 Android Development] spezi77:
Could you take a last_kmsg? Simply turn off your phone when it got stuck and then immediately reboot into recovery. Therein please use "ADB shell" and then "cat /proc/last_kmsg > /sdcard/last_kmsg.txt".

Questions? Read this guide: xdaforums.com/showthread.php?t=1520508

Sent from my beanstalk'd & hellspawn'd N4.
[Nexus 4 Android Development] pratamaaudi:
sorry [MENTION=5091819]spezi77[/MENTION]

i can't get the last_ksmg

but i can get Dmesg

i will try again

EDIT : i got it on second run

please check it :)
[Nexus 4 Android Development] bart.found:
Hi [MENTION=5091819]spezi77[/MENTION], I'm on paranoid Android right now... and I'm also having some troubles with SuperSU.. I'll describe the behavior.

1) Flash ROM, boot to system, flash SuperSU, reboot (root works), flash hellspawn -> root broken, flash SuperSU again -> stock kernel restored

2) flash ROM, flash hellspawn, reboot, flash SuperSU, reboot everything works

3) trying to update to r13 official breaks root, flashing SuperSU again restored the previous hellspawn version....

I'm here to test if you need to investigate this issue...

Have a nice day
[Nexus 4 Android Development] snacs:
Try this:

1) Boot into recovery and mount system

2) Full wype (factory reset, cache + dalvik + system)

3) Reboot into recovery

4) Flash Rom + gapps + supersu + whatever you want

5) Boot system

6) Reboot into recovery

7) Wype cache + dalvik

8) Flash kernel

9) Wype cache + dalvik

10) Reboot and be happy.

Those steps always works for me, and I never had any problems as you and others said.
[Nexus 4 Android Development] bart.found:
[MENTION=5091819]spezi77[/MENTION]

Actually clearing dalvik+cache did the trick for me! Usually I don't do it especially after a clean flash... but if it's needed to make everything work flawlessy... I'll ever do a clear cache+dalvik since now! ;)
[Nexus 4 Android Development] spezi77:
Sorry, but the logs don't provide the needed information. Dmesg is not useful when you take it in recovery mode because it will be about the kernel being embedded into the recovery software. The 2nd kmsg does not show any errors, at least I couldn't find anything specific. Maybe next time you could wait a little longer (2-3 min) before you force restart the phone.

BTW, which kernel did you flash, aosp, bs or cm?

Sent from my beanstalk'd & hellspawn'd N4.
[Nexus 4 Android Development] ravionly431:
[MENTION=5091819]spezi77[/MENTION] would you mind providing me link to hellspawn kernel auditor? I want to enable double tap to wake/sleep.

Device Nexus 4

OS Paranoid Android 6.0.1

Kernel official r13
[Nexus 4 Android Development] Skazzy3:
Is there a way to set the vibration past 100%? TWRP Recovery has 150% for example and it feels amazing. I can't even feel it in my pocket with 100%.
[Nexus 4 Android Development] DingoDingo:
400 Mhz GPU is missing in Kernel Adiutor Mod?
[Nexus 4 Android Development] snacs:
Nope. It's because GPU overclock.
[Nexus 4 Android Development] DingoDingo:
Ok, but it is strange that I can't choose 400 Mhz but can choose 487, 320, 200 and 128.
[Nexus 4 Android Development] dragos281993:
Yes, 400MHz has been removed in the favour of 487. Just so you know, 320MHz gives you the same GPU performance as 400, and I mean absolutely identical performance. I'm playing a pretty graphical intensive game (Boom Beach) and that can get pretty intensive. The good part: I can replay a battle and check out any stutters and performance slow downs. The stutters appear in the same areas, moments, and with the same duration. On the other hand, 487 gives a slightly smoother experience, in some areas, but I checked it thoroughly and it's noticeable if you know where to look. In day to day use, you won't notice the difference between 200MHz and 487. Zaclimon made the standard GPU clock speed 200MHz just because, for the same performance level (pretty close to higher frequencies), this step makes the device run a bit mire cooler and also there's a slightly smaller impact on the battery life. You can increase the clock speed but for daily use and moderate gaming, 200MHz does fabulous. The higher freqs are for stuff that tends to go on the hardcore side.

So 320MHz is a great step intended for moderate to high gaming, 487MHz is for special occasions (lol) and 200MHz should be used for everything else. This doesn't apply specifically to gaming, but to other stuff that involves work from the GPU as well.

So don't worry about the 400MHz cause it's pretty irrelevant.
[Nexus 4 Android Development] DingoDingo:
Thanks for detailed info[emoji106]
[Nexus 4 Android Development] bart.found:
Hi [MENTION=5091819]spezi77[/MENTION] using dyn hotplug always keeps all cores online (at least for me) It doesn't matter how many cores I choose in settings...
[Nexus 4 Android Development] dragos281993:
They go off after a while. Txuki implemented this in "r44 test build" and it goes dual core mode when the interaction with the device is lower.
[Nexus 4 Android Development] spezi77:
Which ROM/ Kernel Tweaker are you using?

Yes, I can confirm that this is the same in r13. Be more patient.. [emoji16]

Sent from my beanstalk'd & hellspawn'd N4.
[Nexus 4 Android Development] dragos281993:
I like the way dyn_hotplug behaves. I have the same battery stats as with the other hotplugs and all the cores are harmoniously working together, giving me a smooth experience. I don't think it should work differently. It's great AS IS. Those that don't like the new hotplug, are free to choose a different one from the list, based on what they prefer.
[Nexus 4 Android Development] bart.found:
Paranoid Android

Ukm+Synapse

I don't dislike the new hotplug, I just need to test it more! Since i didn't notice what you said! ;)

I'll report back, just in case
[Nexus 4 Android Development] snacs:
Hey [MENTION=5796730]dragos281993[/MENTION], which governor are you using?
[Nexus 4 Android Development] dragos281993:
Oh no no, I wasn't insinuating anything. It's just people usually tend to not like a hotplug where all the cores are online more often. That's why I mentioned using other hotplugs. The rest of them are the basic ones we got used to.

---------- Post added at 02:38 AM ---------- Previous post was at 02:37 AM ----------

I'm using ondemand.
[Nexus 4 Android Development] lethall1:
MD5 sum

Hi, I want to thank you for your awesome work!

And ask you if it is possible to post md5 sum of the file in first post too.

Thanks a lot!
[Nexus 4 Android Development] Jakub_Z.:
Ok guys, I know that it was asked here before billion times, but whats the best gov+i/o combo in terms of performance/battery life?

Stock settings are nice but sometimes phone is a little bit sloppy. ;)

I'm on r13 aosp, 5.4TC.
[Nexus 4 Android Development] sidnoit22:
Smartmax or Alucard and the io should be bfq
[Nexus 4 Android Development] Cristiano Lira:
[MENTION=5091819]spezi77[/MENTION], running r13 I noticed that it frequently kicks 1512MHz without high CPU load, with all governors. Can you take a look?
[Nexus 4 Android Development] spezi77:
For which hotplug driver/CPU governor is this?

Do you notice this in r12 as well?

Edit: I can't really say that I am able to observe the behaviour you described, neither in r12 nor in r13.

Could make a screen recording, so that I am able to better understand your problem.

P.S.:What I have observed is that Ondemand governor has a tendency to frequently kick in the upper frequency range even at a moderate CPU load.

Interactive seems to stay at 1134MHz with one CPU core.

Hellsactive seems to stay at 1350MHz with one CPU core.

All the other governors go down to 384MHz..

Sent from my beanstalk'd & hellspawn'd N4.
[Nexus 4 Android Development] franczez:
Hi everyone,

I have nexus 4 with stock 5.1 rom, but I want to install this rom. My question is, why instalation pack has only 5mb? How should I install it after root?
[Nexus 4 Android Development] dragos281993:
This is not a ROM, my friend. It's a kernel. It can be flashed over a 6.0.1 Marshmallow ROM. It replaces the kernel that's alrrady included in the ROM. The stock kernel that comes with the ROM is a basic one and offers pretty much no tweaking capabilities, except for some very basic ones. Custom kernels, in this case "Hellspawn kernel", offers A LOT more features, that vary from changing the CPU governors, to customizing the screen colors or CPU + GPU frequencies, I/O schedulers, hotplugs, etc. If you're new at this, please do some research first and learn what a ROM is, how can it be flashed, what you need to let you flash it, how to do it properly, and the same thing is available for kernels. The best 6.0.1 ROMs are Chroma, Pure Nexus, Beanstalk which is officiality supported by Spezzi, this kernel's developer.

So, before flashing anything, take your time learning how all these processes work and are done properly, otherwise you'll run into trouble without a doubt. Even flashing the latest version of twrp may turn out to be a pain in the rear, if you haven't done something like this before.
[Nexus 4 Android Development] Cristiano Lira:
It happens with every governor and hotplug for me, even using 2 CPUs core as minimum, looking to KA, just staring the screen, generally one core kicks 1512MHz at least once every 10-12 seconds. I'll try to record and post it here till tonight. I switched back to r12 and it happens with it as well.
[Nexus 4 Android Development] sidnoit22:
Wipe cache and dalvik cache. I might fix the problem.
[Nexus 4 Android Development] spezi77:
Alright, I have taken your challenge and went back to where I started my codebase (hells-Core-n4 b88-M). In this kernel build which is actually 100% developed by hellsgod, the observed behavior is already present. In this build I tested with mako-hotplug and Ondemand/hellsactive. I took a look at the frequencies under a low CPU load, and my observation is that it behaves exactly the same as it can be observed in r12 or in r13.

So, what are your suggestions now?

Sent from my beanstalk'd & hellspawn'd N4.
[Nexus 4 Android Development] dragos281993:
I'm currently using Taurus and Txuki has pretty much the same hotplugs and governors as Hellspawn. There's no erratic frequency behaviour with any of the hotplugs or governor and certainly no frequency increase avove the maximum freq preset. When I used Hellspawn r13, the same behaviour, no out of the ordinary behaviour, so everything was stable. I flashed it over a clean system after a complete clean installation of *everything. I don't think my phone is more special than the others so my bet is that this has to do with "residue" from previous installations, even if people may have dirty flashed the ROM or boot.img. I can't think of anything else.
[Nexus 4 Android Development] xenyz:
The proper way to test this using KA is by going to the frequency table tab, menu, reset timers, and wait a reasonable amount of time. Swipe down to refresh the table and see how long it really was at max freq.

When you are looking at the CPU tab, your device is far from idle, having to update the CPU status once or twice a second. It also picks the highest freq from the last sample, no matter how long it was there for.
[Nexus 4 Android Development] Cristiano Lira:
[MENTION=5091819]spezi77[/MENTION], [MENTION=5796730]dragos281993[/MENTION], [MENTION=3118524]xenyz[/MENTION], ok guys, after further testing I came to conclusion that it happens with TaUrUs also but does not with Semaphore (I used a build for M from SAOSP dev). With Hells, after 10 minutes in freq tab after had reset it the CPU stayed at 1512MHz 3% of the time, what I think cause a big impact in battery performance overall, (result which was the same with TaUrUs r44) where in semaphore (looking through the cpu tab), using conservative, the freqs didn't pass 594MHz even at 86% load in that core - while just staring the phone, and running with the minimum number of cores online configured during all the time (2). I think semaphore is a good kernel base but till now I had never noticed that it's GPU freq doesn't go bellow 200MHz even while in idle and this can be the reason I could never pass much 5h SOT with it, now I'm curious what could we get with GPU freq properly scalling down to 27MHz and with governors like Smartmax in it.

One last thing: that 405MHz step could benefit us?
[Nexus 4 Android Development] Cristiano Lira:
[MENTION=5091819]spezi77[/MENTION], also got a last_kmsg after that bug of KA freezing and then the next time screen goes off phone enter in sod and I think this time it have more info. KA freezed when I tried to switch to conservative and after the screen went off the phone entered in sod and rebooted after a while, couldn't get the last kmsg after the phone booted because it freezed so I had to manually reboot but got it right after this manual reboot.

last_kmsg: http://pastebin.com/Dzd7Peri

Edit: happened one more time after the manual boot, still was using conservative since the switch to apply the settings on boot on KA was on - so could it have something to do with conservative governors, like it only happens swithing to or from it? Will investigate this further. --Edit 2: it seems like it - started to swicth governors like crazy but the issue only happened when swichting to conservative (this time from interactive to conservative).-- This time I got the last_kmsg right after the sod entered, by the recovery.

last_kmsg: http://pastebin.com/pYspUiPH
[Nexus 4 Android Development] spezi77:
According to your last kmsg there were no errors detected, no crash or kernel panic occured. Your phone just entered a SOD. Sorry, in other words there is no useful information about a kernel error that I could potentially look into. :/

It could be even related to a weakness in the process of changing the tuneables via KA.
[Nexus 4 Android Development] xenyz:
[MENTION=5091819]spezi77[/MENTION] - I'm not sure if it's your kernel, the new 5.4 tool chain, [MENTION=3750240]stratosk[/MENTION]'s ondemand + dyn_hotplug, Fake Nexus (stock) ROM, the new Google Play Services, or Xposed, but it's been 10 days since Jun 10 (r13 test 2 + r13) and no SoDs on my N4. Congrats on the best, most stable kernel for mako!
[Nexus 4 Android Development] spezi77:
Really nice to read about this.. It's just a little magic. ;)

BTW, three days ago I heard the bad news about stratosk has broken his n4. :(

See here: http://xdaforums.com/nexus-4/orig-d...e-n4-2-2-2-t2232898/post67346361#post67346361

This inspired me to do stratosk the honour, and port over his work to marshmallow. Of course, I will try to keep the initial release as close as possible to stock in order to keep up the original semaphore feeling.

Anyone interested in testing this kernel?
[Nexus 4 Android Development] Cristiano Lira:
[MENTION=5091819]spezi77[/MENTION], I am. :)
[Nexus 4 Android Development] spezi77:
Alright, then here we go! :D

Test builds:

hellspawn-N4-revival-marshmallow-stock-AOSP-UBERTC-5.4.zip

hellspawn-N4-revival-marshmallow-stock-CM-UBERTC-5.4.zip

Just fyi:

These are only compiled with UBERTC 5.x and I decided for the purpose of simplicity to combine the BeanStalk with the CM variant into one build.
[Nexus 4 Android Development] Thrikiller18:
Are these builds compiled from semaphore sources? I am looking for a kernel close to stock on these days. If the anwser is yes, thanks for keeping up the legend.
[Nexus 4 Android Development] spezi77:
Yes, compiled from semaphore sources based on latest version 3.4.1 (lollipop branch). You can check my changes on github: https://github.com/spezi77/kernel_msm

I don't know yet, but I should probably create a new thread soon (once a public/stable build is ready) in order to not confuse the new kernel (codename: revival) with this one. :silly:
[Nexus 4 Android Development] Cristiano Lira:
Thanks for this, [MENTION=5091819]spezi77[/MENTION]! Working like a charm here. Will you include the governors and hotplugs from HS and voltage control on future builds?
[Nexus 4 Android Development] jacomail95:
Just a little suggestion for your kernel, [MENTION=5091819]spezi77[/MENTION]. If you take a look here

http://xdaforums.com/showthread.php?t=2700597

This is an old kernel installed using an Aroma Installer, by choicing the preferences like voltage, or various controls. I don't know precisely how it worked, i think it modified the zImage directly with scripts, but at least consider using it, when you release the kernels with different UberTCs or features. Thanks for your time :)

Inviato dal mio Nexus 4 con Tapatalk 2
[Nexus 4 Android Development] dragos281993:
I don't mean to intrude, but why would someone need to select to have only some features during the flashing process through an Aroma installer ? I can't see the reason. Isn't it better to not tweak the sections that you don't want changed ?
[Nexus 4 Android Development] nereis:
not saying I find it necessary, but its useful when choosing max gpu scaling freq 487 replaces 400mhz and stuff like that. Back in the day when grouper used tegra chip with low power core, in order to oc there can was a additional step, which could be setup as 475,666,700mhz...etc not possible to tune unless setup in ramdisk.
[Nexus 4 Android Development] jacomail95:
Well, it can be useful when there are experimental features or new code added to the kernel, or different toolchains, when other people wants to stick with stability. Personally i'm a guy who loves exp features, mine is only an idea, but [MENTION=5091819]spezi77[/MENTION] will know how to manage it, if he decides so

Inviato dal mio Nexus 4 con Tapatalk 2
[Nexus 4 Android Development] g33k0 b3lk0w:
I've flashed your test build AOSP version. Ton od things missing since last o e I've used (R08) but will keep on rocking it even without UV and governors
[Nexus 4 Android Development] spezi77:
Hey there,

Of course, a lot of things might be still missing.. This time I want to do things a little different. First let's add the essentials and make it run fast as hell.

Edit: Download links removed, please visit http://xdaforums.com/nexus-4/development/kernel-n4-revival-r1-t3405752
[Nexus 4 Android Development] g33k0 b3lk0w:
I don't get it, is this even newer version or? XD you should label the releases
[Nexus 4 Android Development] dragos281993:
I believe a different thread for "revival" would be essential. And my personal opinion is that revival should only have the essential stuff like just a few governors, gamma control, UV, maximum 2 hotplugs, dt2w and some other basic stuff. Hellspawn would be your "hardcore" tweakable kernel and "revival" would be the more conservative "little brother". This way you'll have 2 different kernels, 1 aimed at the users who love to tweak the hell out of their phones, and another for those who prefer basic tweaking.

But it's my personal opinion and a suggestion.

Cheers !

---------- Post added at 11:11 PM ---------- Previous post was at 11:08 PM ----------

No, it's "revival", a new kernel based on Stratosk's "semaphore kernel".
[Nexus 4 Android Development] spezi77:
[MENTION=5796730]dragos281993[/MENTION]

You have a good point. I highly appreciate your suggestions. As of now the "revival" builds are only for testing purposes. Of course, once an official release is ready, I will start to label it properly and create a new thread..

Cheers! [emoji6]

Sent from my beanstalk'd & hellspawn'd N4.
[Nexus 4 Android Development] g33k0 b3lk0w:
Thank you kind sir :D really love the test build so far even without all the things :D keep up tze good and clean work
[Nexus 4 Android Development] Cristiano Lira:
[MENTION=5091819]spezi77[/MENTION], just would like to inform that the phone freezes then reboots after trying to change governor to interactive on latest revival build. If you haven't noticed already ;).
[Nexus 4 Android Development] sidnoit22:
What you guys recommend? Because I hardly used Semaphore kernel on my Nexus 4 before, just tried it once. So HellSpawn or Revival?
[Nexus 4 Android Development] dragos281993:
1 has an impressive amount of tweaks and the other a limited one. If you like tweaking every single thing or at least to have those options there in case you want to fiddle with them at any time, then Hellspawn is your choice. If you want something that has the basic tweaking capabilities, and complete stability, then "revival" is the one want you want. It depends on what you like to tweak and what you usually don't touch in Kernel Adiutor. Based on the things you like to tweak or not, you can make your decision.
[Nexus 4 Android Development] sidnoit22:
Thank you, I will stick to HellSpawn. Will try Revival in future! :D
[Nexus 4 Android Development] g33k0 b3lk0w:
If possible add the sound tweaks that hellspawn had, my earphones are much quieter now :/
[Nexus 4 Android Development] Cristiano Lira:
I'm liking the audio more with revival. For me it's audio output is higher.
[Nexus 4 Android Development] g33k0 b3lk0w:
Another thing with Revival, I'm using 2G and reading reddit and suddenly phone crawls with 400Mhz top freq and gets very hot :/ not usable :/
[Nexus 4 Android Development] .stendeck:
Okay, to avoid any misunderstandings,… revival is not compatible with Lollipop builds, right? Is the semaphore kernel optimzied of any kind? Or is revival only a 1:1 port for marshmallow? Looking for a fast and stable kernel for latest stock ROM (5.1.1), so maybe I have to try original semaphore first.
[Nexus 4 Android Development] dragos281993:
The original semaphore kernel has specifically been optimized to work with Lollipop, as Stratosk always used L on his N4.
[Nexus 4 Android Development] .stendeck:
Yes, I know. I only was wondering if [MENTION=5091819]spezi77[/MENTION] would adopt the semaphore project (since the Nexus 4 of [MENTION=3750240]stratosk[/MENTION] is damaged) and now focuses on a more optimized version (-> "revival"). But I think that Lollipop compatibility is gone now, right?