yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Android Development] dragos281993:
Most probably. Other users tried on L all these kernels that have been made for M and reported problems, so my advice is to either stay with the original semaphore or install Chroma, Pure Nexus, or Beanstalk (all 6.0.1), which are very stable, and flash one of the few great kernels we have available at the moment. You won't be disappointed.
[Nexus 4 Android Development] spezi77:
You are right, I didn't intend to keep up backwards compatibility with L. Thanks for asking this question. Revival is/will be especially made for M.

Sent from my beanstalk'd & hellspawn'd N4.
[Nexus 4 Android Development] spezi77:
Sorry, I couldn't understand your specific problem.. 400Mhz GPU or CPU usage?? Could you add any log or useful information (e.g. which governor/hotplug configuration) in addition, please?

Sent from my beanstalk'd & hellspawn'd N4.
[Nexus 4 Android Development] g33k0 b3lk0w:
I alshould've been more clear. Although it really is a fast kernel and phone works fast, it drains battery just a little bit more but that is not the problem I had. Today I was traveling and surfing reddit on 2G while listening to music. Because the kernel keeps 4 cores up all the time while using my phone got very hot after 15mins and throttled the cpu tu Max 400Mhz and device really got slow. That's the problem that's occured because all 4 cores are up all the time ( in my opinion )
[Nexus 4 Android Development] spezi77:
Instead of lowering max. CPU frequency you should have rather restricted max. online CPUs to 2. This way you don't cut too much of the processing power.

It should be possible to do this by using KA mod or any other kernel tweaker.

P.s.: once I find a little time, I will add an additional cpu governor/hotplug driver that allows for better energy savings.

Sent from my beanstalk'd & hellspawn'd N4.
[Nexus 4 Android Development] g33k0 b3lk0w:
I didnt do anything, kernel done that itself, couldnt find option to limit cpu to two cores up in kernel adiutor
[Nexus 4 Android Development] spezi77:
Install the latest version from this thread:

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

Sent from my beanstalk'd & hellspawn'd N4.
[Nexus 4 Android Development] xenyz:
Try running this script or setting those settings in KA-mod.
[Nexus 4 Android Development] Alex 9:
I'm kind of new to this stuff and I'm having an issue with the CPU governors.

I'm only having OnDemand, Interactive, perfomance, powersave, conservative and userspace governors.

I'm using Kernel Adiutor-Mod, I've tried others but only get these governors.

I switched from Taurus to Quanta and now to this. What should I do?

I'm having the latest Chroma build.
[Nexus 4 Android Development] dragos281993:
So you switched between them just like that ?
[Nexus 4 Android Development] Alex 9:
I wiped Dalvik/Cache after every kernel.
[Nexus 4 Android Development] dragos281993:
I'm not surprised at all. Moving between different custom kernels involves more than just a caches wipe. The ramdisk is different from one kernel to another so flashing 1 on top of the other will just add more stuff to the ramdisk instead of emptying it before being written again. Going back to the ROM's stock kernel is ABSOLUTELY REQUIRED before moving on to another kernel and that can be achieved by simply dirty flashing the ROM.

So here's what you gave to do to safety move between custom kernels:

1. Delete the kernel manager that you're using to tweak the kernel (eg. Kernel Adiutor, Synapse, etc.) *don't worry ! You can install it after the entire flashing process is done and the phone booted up.

2. Reboot to recovery.

3. Wipe cache + dalvik cache

4. Dirty flash the ROM you love. This right here is the crucial step that assures that everything will work properly after you finished all these steps. Dirty flashing the ROM basically overrides the custom kernel, having the stock kernel installed and the ramdisk cleaned.

5. Flash the desired >custom kernel<

6. Wipe both caches again and reboot to system.

Now you can reinstall Kernel Adiutor. The reason for uninstalling it is to make sure it doesn't apply any settings and tweaks you had it set to apply after a reboot. Leaving it installed means that the app will try to apply settings you had set from another kernel, stuff that may be different and that would cause kernel panics, so it's better to uninstall it before starting anything then reinstall it after everything is done.

So every time you decide to try another custom kernel, it's absolutely necessary to follow the steps above in order to replace the custom kernel with the stock one.
[Nexus 4 Android Development] Alex 9:
That didn't seem to work with me. Did all these steps, still only get the governors above.
[Nexus 4 Android Development] dragos281993:
It's not possible. You're doing something wrong and that's the reason you get this problem. The kernel you flash, when you start the flashing process, it writes exactly what the dev made it write. It can't flash more or less stuff than what it includes in the zip file.

So download Hellspawn kernel again in case you got a corrupt file. Then make sure you install the latest recovery on your device (twrp 3.0.2.0). Most probably, the kernels you were trying to flash didn't even finish the installation and that's why you see the same features in KA Mod. Go to "About phone" in Settings, and tell me what's written under "Kernel version".
[Nexus 4 Android Development] Alex 9:
3.4.112-hellspawn-N4-revival-marshmallow-AOSP-UBERTC-5.4

spezi@manjaro-pc #1

Tue Jun 21 20:56:17 CEST 2016
[Nexus 4 Android Development] dragos281993:
Do this and respect every step, carefully:

1. Uninstall KA Mod.

2. Open the ROM.zip with Winrar, on your computer.

3. Extract the "boot.img" file found in there (drag it out of the archive).

4. Transfer "boot.img" to your phone.

5. Reboot to recovery.

6. Flash "boot.img"

7. Flash hellspawn kernel

8. Reboot to system.

Reinstall KA Mod and check to see how things are.

Don't forget to use twrp 3.0.2.0.
[Nexus 4 Android Development] Alex 9:
Just downloaded and flashed the kernel again and it works. Seems like I had a corrupted file, but thanks anyway.
[Nexus 4 Android Development] tyler999:
need the same cpu fréquence table of hell core kernel for my undervoltage
[Nexus 4 Android Development] xenyz:
[MENTION=5091819]spezi77[/MENTION] I need some advice. I've had some free time between football matches and created a custom installer for HellSpawn, which includes all my best kernel settings as defaults, and has two unique features: shared cpufreq policy to let stock thermald and the battery saver feature work correctly, and a method to reset both mediaserver (when playing videos gets stuck) and sensors (when autorotate, adaptive brightness or GPS stops working) by double/triple pressing the power button.

What should I do, where should it go?
[Nexus 4 Android Development] spezi77:
You could check Ziddey's script which has been adopted by quite a few devs for making their anykernel based installer: https://github.com/spezi77/anykernel_msm/blob/mako-6.0/tmp/anykernel/modrd.sh
[Nexus 4 Android Development] Ahmed Kassem:
I have 2 problems, I can't set SELinux to permissive. And also vibration sensitivity can't set on boot and stuck at 71% and I must change it everytime.
[Nexus 4 Android Development] spezi77:
Which ROM and which kernel tweaker app? Did you clean cache/dalvik-cache?
[Nexus 4 Android Development] xenyz:
If I post it on XDA, may I include your kernel zImage?
[Nexus 4 Android Development] Ahmed Kassem:
PureNexus ROM, Kernel Auditor and yes I did clean cache/dalvik.
[Nexus 4 Android Development] spezi77:
I am not against in the case that you declare it as a mod and give proper credits. ;)
[Nexus 4 Android Development] spezi77:
You could try my new revival kernel. It has per default selinux set to permissive.
[Nexus 4 Android Development] jewshawn2:
delete
[Nexus 4 Android Development] TA123:
So what is the difference between HellSpawn and Revival?
[Nexus 4 Android Development] TheArt.:
Just go back a little and you will find the answer:
[Nexus 4 Android Development] zephyr79:
Revival is basically Semaphore Kernel (its dev doesn't have a mako anymore so Hellspawn dev made an update for Marshmallow)
[Nexus 4 Android Development] Ahmed Kassem:
May that be included in HellSpawn in the next version?
[Nexus 4 Android Development] xenyz:
Hi spezi77, I finished it up and posted it to reddit to get some feedback before putting it on XDA.
[Nexus 4 Android Development] spezi77:
It looks really interesting. :svetius: Are you sure that mdpfake service is working as expected?

Edit: I've been asking because I can still find PowerHAL errors in the logcat.

E.g.:

E PowerHAL: sync_thread: failed to send: No such file or directory
[Nexus 4 Android Development] spezi77:
Hey [MENTION=3118524]xenyz[/MENTION]

I think that you have forgotten to add a command for starting mpdfake service. E.g.:

start mpdfake

However, as stated in my previous comment, I have tried this, but it still didn't absorb (all of) the PowerHAL errors.
[Nexus 4 Android Development] spezi77:
First off, could you test it? Please check if it works in Revival.
[Nexus 4 Android Development] xenyz:
Yeah, in AOSP at least when you put a service in init.rc you don't have to explicitly call start service, it just runs on boot unless it has keyword disabled

I'll keep an eye out for the PowerHAL messages, but 10 mins of logcat | grep PowerHAL haven't showed anything yet on my device.

BTW, I've got another trick for the installer mod - I moved my dalvik-cache to cache partition and got an extra 0.5 GB free space on my mako :) Just testing it a few more days, might try filling it up completely to see how Android acts when it's out of space for it, but so far so good.

Oh, and I also might have found a fix for the GPS not working after some time. I have to figure how to do some stuff from the command line to automate it though.
[Nexus 4 Android Development] ihendraX:
Lost root

Hi all,

I have one (big) problem, on my Nexus 4 with latest ParanoidAndroid 6.0.1, when I flash AOSP r13 tc 5.4 ot tc 7, I lose root access.

When try to root it again over ADB, it says it's already rooted.

With other kernel (hells core) it works fine.

I tried everything, flash just kernel, kernel + supersu.zip, with or without cache wipe, downloaded from different sources, etc...

I really want to give this kernel a try, but I run out of ideas. :rolleyes:
[Nexus 4 Android Development] spezi77:
I used to have PA 6.0.1 on my n4 and will try to make a reproduction of the issue you mentioned. However, reading about loosing root gives me a deja vu feeling. Have you checked all posts in this thread? I believe that someone has discovered a workaround (slightly different sequence of flashing kernel and SuperSU)..
[Nexus 4 Android Development] math.rangel:
So... I had the same thing when I tried PA 6.0.1 + Hellspawn (9.5). Tried a lot of things and the only thing that worked was: flashing rom zip, flash root, flash Hellspawn and then boot. That was the only solution, but it did work out.

Used the rom for a week I guess, stable, good battery, but I got into a bootloop (just rebooted the device) and couldn't get out of it. Flashed the rom over it and it didn't solve. Lost a few things, such as WhatsApp messages. Only thing I could do was flash another rom, in this case, PureNexus, and still on it. Really love P.A since Jelly Bean times, but can't take this risk again
[Nexus 4 Android Development] Dav1_d:
Please, please, please could you keep selinux in enforcing mode; if anyone wants to set it to permissive, it can be done through the 'Kernel aduitor mod' or through installing the 'Selinuxmodechanger' app, both of which can be found here on XDA.

This kernel has really impressed me with its speed, smoothness and stability.. Keep up the good work.
[Nexus 4 Android Development] TA123:
I've got a problem with music stuttering. I have not changed anything in the CPU section.
[Nexus 4 Android Development] spezi77:
Does it stutter when screen is off?
[Nexus 4 Android Development] TA123:
Yes, especially when the phone hooks up with Wi-Fi or there is a notification. I have upped the off screen frequency to 1350 MHz but it still happens.
[Nexus 4 Android Development] spezi77:
Try interactive governor instead. As a last resort, you could try to increase the min CPU frequency from 384Mhz to a higher value.
[Nexus 4 Android Development] dragos281993:
I had this problem while listening to music with Viper4Android's sound processing on. The fix is to have "ondemand" set as governor, minimum 2 cores online while the screen is turned off (or all the time), and if this doesn't completely fix the static noise, stutters, etc., which it should, then increasing the minimum CPU frequency to 486MHz, will definitely fix it.
[Nexus 4 Android Development] shawnbrennan55:
Make sure you have more than one core active when the screen is off.
[Nexus 4 Android Development] gorilla p:
Yeah, when listening to music, I had to 2 cores online max when screen is off and max freq 1248 (or close to that) You can limit those cores a bit so as to preserve battery life.
[Nexus 4 Android Development] spezi77:
Hey people,

Here we go again. R14 appears to be the fastest option since hellspawn has been ever created. My AnTuTu score is unbelievably high: >37.000 points!

View attachment 3807377

Check post #2 for change log.

Enjoy! ;)
[Nexus 4 Android Development] cemilplt:
https://plus.google.com/112559686997337277076/posts/BUxxrhB6haW[emoji7] [emoji7]

---------- Post added at 03:35 AM ---------- Previous post was at 03:32 AM ----------

Thank you verry much!Yay.....
[Nexus 4 Android Development] tvisforme:
A question - which is the correct version of Kernel Adiutor to use? I'm currently using the stable (ie non-beta) version from the Play Store, but from reading this thread it appears that KA doesn't control everything in this kernel. There was a KA-Mod linked by Spezi77 in this thread back in mid-June, but there are also links to a separate version (v14) in the Revival kernel thread. Would it be possible to put a link to the recommended version of KA-Mod at the top of this discussion?
[Nexus 4 Android Development] TheArt.:
Use the v14 one and you'll be OK
[Nexus 4 Android Development] ivanich:
After 2 days of using r14 I've found that mcm and dyn hotplug comparing to autosmp just stupidly keeps at least 2 cores online even if it set to min 1 core, this is with msm limiter disabled. Ondemand governor still refused to stay at 384 Mhz as in previous release, so interactive governor is the best choice for me for now I believe because no "improvements" has been applied to it.
[Nexus 4 Android Development] xenyz:
[MENTION=5091819]spezi77[/MENTION] I tried out r14 and unfortunately had both a reboot and a SoD :/

Of course, it's impossible to tell if the SoD was related to r14, but I've been using r13 since release with no SoD or reboots.
[Nexus 4 Android Development] spezi77:
Hmm, sorry to hear about that. I'd better change the title of r14 release to "testing".

About "interactive" CPU governor:

In r14 this "interactive" has been completely rebased. I took over the version from chaos kernel, see here: https://github.com/spezi77/hellspawn-N4/commits/mm-6.0-dev?page=2.

How is/was r13 working for you?
[Nexus 4 Android Development] spezi77:
It's a pity to hear about it. I have run r14 only for 2-3 days without any issues before I switched back to revival. If you don't mind, could you stay a little longer with r14 to see what exactly is causing it? From your kmsg have seen that you were probably using dt2w feature right before a kernel panic occurred.
[Nexus 4 Android Development] ivanich:
Interactive was good in r13 and I have no issues so far with it in r14. Also I've realized that issue with ondemand is also present in taurus 45 kernel however you both used the same code so it's not surprising.

Отправлено с моего Nexus 4 через Tapatalk
[Nexus 4 Android Development] spezi77:
Yeah, to be honest I think that both of us, txuki with his taurus and myself with hellspawn, we went a little too far beyond at improving things. When I realized that, I decided to start with a new kernel base, which ended up in [advertisement] my new "N4-revival" kernel project. [/advertisement]

:silly:
[Nexus 4 Android Development] xenyz:
I think it was detecting presses while in my pocket, I wasn't actually using the phone when it rebooted. I found out some time later that it did. I'll have a close look at the changes from r13 to see if I can spot something.
[Nexus 4 Android Development] spezi77:
I don't know, it is just a guess.. it could be caused by smpboot changes.
[Nexus 4 Android Development] ivanich:
Yeah, I run into the same situation multiple times with device I've maintained, however I stopped adding new experimental code to kernel.

Отправлено с моего Nexus 4 через Tapatalk
[Nexus 4 Android Development] xenyz:
[MENTION=5091819]spezi77[/MENTION] I've also noticed that msm-limiter doesn't work for screen off freq. Check with Trepn Profiler.

Perhaps give us a build of r13 with just the July security patches? It was working well enough :D
[Nexus 4 Android Development] spezi77:
Yeah, ok. That could probably be an option for the next build. Until then please be patient.. ;)
[Nexus 4 Android Development] cemilplt:
phone will not turn on the stand-by state, rarely display (r14-5.4-7.0) pure nexus!

---------- Post added at 07:42 AM ---------- Previous post was at 07:41 AM ----------

I'm using now back r13.
[Nexus 4 Android Development] jewshawn2:
I'm using the last PureNexus rom (MM) with HellSpawn-N4 r13-AOSP-TC5.4 and r14-AOSP-TC7.0. Has anyone noticed the phone doesn't go into doze anymore?

I had a much longer post but rather than drop the bomb. I'd ask a question first.
[Nexus 4 Android Development] Hyflex:
Doesn't appear to work on latest Chroma, it messes up all of the OS for some reason, loses wifi, lose access to settings (via dropdown notification bar), loses actual notifications and a bunch of other things.
[Nexus 4 Android Development] spezi77:
Thanks very much for mentioning this. That's interesting. I have uploaded a new build of r14 with only minimal changes. Could you give this version a try? https://www.dropbox.com/sh/c6i0d2t2kl6a9sj/AADXBcdwFjJWv4EnunxmImbya?dl=0

However, as you say that "deep sleep state" issue appears to be already present in r13. I'd say that in this case the problem has not been introduced by the experimental enhancements in my r14 test build (i.e. msm-limiter, cpu-boost.).

Edit: BTW, you have to make sure that you unplug your phone. If it remains on charger, then of course it won't enter into deep sleep!
[Nexus 4 Android Development] spezi77:
To my surprise r14 is even faster without msm-limiter and msm_hotplug. I switched to dyn_hotplug (2 cores min.) and interactive CPU governor and got this crazy score.

View attachment 3814297
[Nexus 4 Android Development] jer_ying_fd:
Hi, I encountered a problem with rooting. The typical routine is flashing rom, supersu, then kernel, if I'm not wrong. However, after booting up, even though the SuperSU app is installed, the app says there is no binary installed. I'm using fake nexus rom and it used to work on revival kernel. Any help is appreciated, thx!
[Nexus 4 Android Development] spezi77:
Please browse a few pages back to find the proper sequence of flashing with SuperSU.
[Nexus 4 Android Development] jolinnard:
Have installed your Kernel Adiutor Mod and tried these settings (running your latest R14 with doze patches)... All seems even better than before (still running hellsactive). I'm really glad to have this phone and see there's people working hard for it. Thanks.
[Nexus 4 Android Development] Cristiano Lira:
R14 with doze patches? Where can I get it? :p
[Nexus 4 Android Development] jolinnard:
http://xdaforums.com/showpost.php?p=67767789&postcount=951
[Nexus 4 Android Development] Cristiano Lira:
I thought you had made a build yourself with some doze commits on it :p. I am already using that one but thanks anyway. :)
[Nexus 4 Android Development] klaust58:
Sorry....which of this files with the new version should I use with a CM based ROM? I only see very short filenames....

Gesendet von meinem Nexus 7 mit Tapatalk
[Nexus 4 Android Development] Mrcactuseater:
The one that has CM in the name.

Tapatalk'd from my Twisted, Yank'd Nexus 5
[Nexus 4 Android Development] klaust58:
Shure....if I would see long filenames..... ;)

I will try it at my PC later.

Edit: Ok...at PC, i see long filenames :)

Gesendet von meinem Nexus 7 mit Tapatalk
[Nexus 4 Android Development] tvisforme:
FYI I see this issue as well. Dropbox appears to only list shortened filenames in Chrome Android.
[Nexus 4 Android Development] Pac-Man:
How can I change settings of this kernel? Thank you in advance!
[Nexus 4 Android Development] spezi77:
Give KA-mod a try. They have just released v15: http://xdaforums.com/android/apps-games/kernel-adiutor-mod-singularity-kernel-t3333549/page81
[Nexus 4 Android Development] Pac-Man:
Thank you, it's time to give it a try!

Do you recommend any rom to install the kernel? I used PN, but I'm waiting for the new mantainer...
[Nexus 4 Android Development] spezi77:
Hum, well.. you could give BeanStalk a shot, which is maintained by myself. ;)
[Nexus 4 Android Development] ivanich:
New r14 have an issue with deep sleep. Compared it with taurus 46

Отправлено с моего Nexus 4 через Tapatalk
[Nexus 4 Android Development] spezi77:
Thanks for your report. I have forgotten to revert SMP related commits in this build.
[Nexus 4 Android Development] Thrikiller18:
Did you flash it over taurus? Or did you flash the ROM and then the kernel?
[Nexus 4 Android Development] ivanich:
I know how kernels should be flashed and also aware of ramdisk and boot.img repacking.

Отправлено с моего Nexus 4 через Tapatalk
[Nexus 4 Android Development] espionage724:
The 7.0 version of HellSpawn r14 (and r13) with BS 6.19 seems to have an issue where things download very slowly from Play Store. 5.4 r14 seems to be fine though. Has anyone else experienced this?
[Nexus 4 Android Development] spezi77:
r15 arrived with fixes and performance improvements

* Fix for deep sleep issue/kernel panic by making a revert of smpboot related commits

* cpufreq: interactive: set timer_rate to 60ms on screen off (previously 50ms) (thanks franco)

* Faster boot up through increased timer frequency (thanks franco)

* Set rate to 250 Hz for mako (thanks zaclimon)
[Nexus 4 Android Development] cemilplt:
Thanks boss yay!
[Nexus 4 Android Development] ivanich:
Thanks for the new release, looks like issue with deep sleep has been resolved. However screwed ondemand governor is still here.

Отправлено с моего Nexus 4 через Tapatalk
[Nexus 4 Android Development] A18415:
Hi Spezzi

You seem to be the right person and looks like that you have got a great hand on the kernel development.

Please look at my question in General Q & A " MIUI 7 Kernel Question".

Thanks in advance.

Cheers.
[Nexus 4 Android Development] cemilplt:
Thanks for the great work.Super fast and smooth as butter.[emoji1] [emoji1]
[Nexus 4 Android Development] spezi77:
I will have a closer look at it when working on next build.
[Nexus 4 Android Development] Pac-Man:
What do you mean with "screwed ondemand"?

~~

tapatalked!
[Nexus 4 Android Development] spezi77:
That's what he was referring to.
[Nexus 4 Android Development] mesaj:
I don't really like new dropbox link, on mobile it's not showing full filename and don't know which to download until I set Computer view
[Nexus 4 Android Development] dragos281993:
Damn...!!! You're doing some real work for our beloved old Nexus 4. That's amazing. Thank you for that !!!

If only the Samsung fanboys knew what it means to have a Nexus phone...
[Nexus 4 Android Development] xenyz:
I tried out the simple GPU governor test, but it doesn't work as expected. Wasn't there another GPU gov from Franco based on interactive?

I don't even know if it's worth bothering, I doubt calming the GPU frequencies would save that much energy.

(Also the simple test build with Dmitry patches caused high system_server usage, as expected.)

The above test build works the best for me, with elementalx governor and 384 MHz min freq. system_server isn't in my battery stats and my device just flies with your Beanstalk ROM.