yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Android Development] jer_ying_fd:
Do you think there are any differences in speed between revival and hellspawn? I'm torn between the 2 :P
[Nexus 4 Android Development] spezi77:
To be honest, hellspawn is a monster and it performs "faster" when you are only judging by looking at AnTuTu scores, but in a daily usage scenario you don't really notice that there is a big difference.

With "revival" I intended to start a new kernel base which offers a very good speed, but with less experimental features, and in principle paying more attention to stability and battery life.

However, you decide which horse to ride. :cowboy:
[Nexus 4 Android Development] jer_ying_fd:
Is it kernel adiutor bug or kernel problem when thermald won't stick, leading to no thermal solution being used? Same happens for sound control as well

Edit: Tested with synapse, looks like it's a problem with kernel adiutor
[Nexus 4 Android Development] espionage724:
Is there any benefit to having SELinux on permissive instead of enforced, and would there be any issues with enforcing it with this kernel?
[Nexus 4 Android Development] Vasya4:
Can this kernel be flashed directly over hellspawn with cache/Dalvik wiped or the stock kernel must be flashed first?

Thanks!
[Nexus 4 Android Development] dragos281993:
Nope. They have very different bases and flashing one on top if the other will no doubt result in all sorts of problems, that if the phone boots up in the first place.

So if you want to flash a new custom kernel while you already use a different one, you MUST either:

1. dirty flash the ROM before flashing the desired kernel

OR

2. extract the "boot.img" file (which is basically the ROM's stock kernel) which you can find inside the ROM's zip file that you're using, flash it in recovery, and only after that will you move on and flash the desired custom kernel.

NEVER flash 2 different kernels on top of each other.
[Nexus 4 Android Development] tom0769:
Maybe flash the boot.img before flashing the custom kernel;)

Sorry don't wanted to be a smartass:D
[Nexus 4 Android Development] dragos281993:
Of course, I forgot to type in "and flash it" after saying to extract the boot.img.
[Nexus 4 Android Development] spezi77:
r04 test build

Hey there,

I am looking for brave guys to test my latest r04.

Changes:

From Franco's release for Hammerhead:

- WiFi driver: improved battery life, performance & security updates

- cpufreq: interactive: set timer_rate to 60ms on screen off (previously 50ms)

- cfq-iosched: improvements

From Franco's release for Flo (thanks zaclimon):

- Performance improvements

- Faster boot up

Downloads:

https://www.dropbox.com/sh/uzbva5ugswzqpnb/AABxGZBNi8mUVw0B8SC5FUZ_a?dl=0
[Nexus 4 Android Development] dragos281993:
I flashed it right after you posted it. I've had no problems all day until a few minutes ago. I was trying to check some posts in Tapatalk, it loaded pretty slow because of my network "situation" and then the phone simply froze and force-rebooted by itself. I did -100mV UV just for the sake of it and also changed the I/O scheduler to cfq. These are the only things I changed.

Other than this , I haven't noticed any strange behaviour. I'll see if the UV caused the panic by using the stock voltages.

https://drive.google.com/file/d/0B6SsZ9qokxalMGd3UW1JTXE4ZEE/view?usp=drivesdk
[Nexus 4 Android Development] espionage724:
Would BeanStalk work with either of those kernels or did it need a specific one? Noticed in the other kernel threads BS had its own version separate from AOSP and CM.

I'd be interested in trying it on BeanStalk.
[Nexus 4 Android Development] spezi77:
BeanStalk will work by using the CM build of Revival Kernel.
[Nexus 4 Android Development] iskandar1023:
With r03 i got a kind of performance degradation if i don't reboot for a day (even better, a couple of hours)

But with r04, the performance degradation is reduced, boot time is reduced too. Will test it for a couple of days again.

Thank you!
[Nexus 4 Android Development] ironvane:
The r4 is really faster, battery friendly and stable on aosp rom for 3 days test. But i have noticed a few degradation on wifi. Good job for this better kernel als the r3
[Nexus 4 Android Development] spezi77:
Thanks for reporting back. Could you please explain more precisely what means few degradation on wifi?
[Nexus 4 Android Development] dragos281993:
After a few days, it seems that wifi has been nkt as consistent as before. Sometimes, while having data on at the same, wifi simply lost signal leaving me with unloaded webpages, etc. Now I'm on Quanta v18 to see if the same behaviour is there and only 1 "wifi hiccup" occurred here too. For now, everything is back to normal, after turning mobile data off. I'll see if I encounter more "hiccups" in the following days. I'm getting ready to flash Revival back for further testing. Also, I had some video playback problems in the Youtube app, which consisted of image freezes in the middle of the video. I set readahead size to 128kb to fix the issue, which still occurred from time to time.
[Nexus 4 Android Development] ironvane:
The wifi constantly clinched and web pages stop load sometimes for no reason. I also noticed more battery consumption when turned on als on the r3
[Nexus 4 Android Development] hassantalal11:
It works on slim rom 6.0.1?
[Nexus 4 Android Development] spezi77:
Possible. Please make a test and let us know. ;)
[Nexus 4 Android Development] hassantalal11:
All working on slim6 without any problems :good:
[Nexus 4 Android Development] justmix4:
Today I had two restarts while surfing the internet and playing games, not too long, just 20-30 minutes.

Chroma 7/7/16 with Revival r03.

Tap Tap
[Nexus 4 Android Development] spezi77:
Could you try to make a reproduction while your device is being connected via USB/ADB to your computer. Please record a logcat and ideally a last_kmesg as well. Only these pieces of information will possibly allow me to detect issues and hopefully identify a solution.
[Nexus 4 Android Development] justmix4:
Sure, on Tuesday I give you everything because this time I do not have access to the original cable N4.

I tried to do it manually according to the instructions in this topic:

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

But without success.

Tap Tap
[Nexus 4 Android Development] spezi77:
Try this one: http://xdaforums.com/showthread.php?t=1378491
[Nexus 4 Android Development] ted mosby021:
please tell me what kernel is best for stock 5.1.1

i want better battery life
[Nexus 4 Android Development] justmix4:
I did this using the application SysLog. The way the cmd does not work, when I type the command cmd responds "Access Denied."

The amount of text exceeds the limit Pastebin and xda attachment. That is why I pasted logcats on nopaste.

Logcat:

https://nopaste.me/view/344bfaeb

last_kmesg:

http://pastebin.com/gJe1f37f

Restart I had a few days ago, and these logs do not contain logs from the day when it happened.

Is such a thing should be done on freshly immediately after an unplanned reboot?

\\\\\

Another reboot a few minutes ago.

Logcat:

https://nopaste.me/view/4e0886fd

last_kmesg:

http://pastebin.com/KVBxPGJS

My kernel setings:

- CPU max.1350Mhz min.384MHz, governor interactive

- CPU voltage -80 (After rebooting the value changed to +10)

- CPU Hotplug Dyn_Plug

- I/O Scheduler cfq

- DT2W

These are not normal restarts. I mean, it is boot animation, but I do not have to enter the PIN code.
[Nexus 4 Android Development] spezi77:
I have looked into your logs. There was no kernel error. Most likely the reboots you have observed are caused by your ROM/apps/Gapps. I have seen a few errors there, but there is nothing kernel related.

Recommendations:

- Remove FB App

- Don't undervolt the CPU
[Nexus 4 Android Development] spezi77:
R05 released incl. the most stable commits from r04 test build. See OP for changelog.

Enjoy! :D
[Nexus 4 Android Development] spezi77:
Stockdemand in combination with AutoSMP is my recommendation for you if you want to keep your phone away from the charger.

Stockdemand tumbles to the lowest CPU frequency possible while in IDLE mode.
[Nexus 4 Android Development] Cristiano Lira:
Smoother than ever.
[Nexus 4 Android Development] TheArt.:
Can confirm. I didn't expected such a big difference between r4 and r5, but it is really fast and smooth now, it seems that I'm using performance governor but I'm not! Ondemand a bit UC and UV with default hotplug.

Thank you [MENTION=942874]spezy77[/MENTION]
[Nexus 4 Android Development] iskandar1023:
thanks for the update!

if you don't mind maybe you want to add this script for removing touchboost logspam

#!/sbin/sh
#

#remove the binaries as they are no longer needed. (kernel handled)
if [ -e /system/bin/mpdecision ] ; then
busybox mv /system/bin/mpdecision /system/bin/mpdecision_bck
fi
if [ -e /system/bin/thermald ] ; then
busybox mv /system/bin/thermald /system/bin/thermald_bck
fi
if [ -e /system/lib/hw/power.msm8960.so ] ; then
busybox mv /system/lib/hw/power.msm8960.so /system/lib/hw/power.msm8960.so_bck
fi
if [ -e /system/lib/hw/power.mako.so ] ; then
busybox mv /system/lib/hw/power.mako.so /system/lib/hw/power.mako.so_bck
fi

return $?

It's from hckernel, thanks!
[Nexus 4 Android Development] chaostrodamis:
What the difference between your build and David 617's build of KA_mod
[Nexus 4 Android Development] spezi77:
Mine is older now. Feel free to use the latest build by David. I push my commits to the repo which he uses to compile from.. :)
[Nexus 4 Android Development] Vasya4:
Stockdemand in conjunction with AutoSMP makes my phone freeze and reboot as soon as selected. The same happens with hellsactive regardless of hotplug type. All other governors seem to work fine.

Any idea what might cause this?

Thanks!
[Nexus 4 Android Development] ivelramona:
+1

I got same case in RR rom..
[Nexus 4 Android Development] spezi77:
Hum, that sounds like you have encountered a bizarre issue. Please try to clean the app data of KA-mod or uninstall it. Furthermore you should boot into recovery and wipe cache/dalvik-cache.

I hope that this helped you...
[Nexus 4 Android Development] Vasya4:
Tried all these, but to to no avail. Cache/dalvik have been wiped multiple times - when moved from HellSpawn to stock kernel, then to H4 Revival R03, then to R05. R03, by the way, had the same issue. It takes about 2-3 seconds for stockdemand governor to make the phone freeze while hellsactive kills it right away.

There must be something common in hellsactive and stockdemand governors that causes system to crash. The only additional thing I have installed through recovery is Xposed framework, but I don't think it would affect governors.
[Nexus 4 Android Development] spezi77:
Ah, I understand. I suspect that your ramdisk got screwd up. Try to dirty flash your current rom to restore your stock kernel /w ramdisk and then flash the kernel of your choice. Jumping between custom kernels wasn't a good idea..
[Nexus 4 Android Development] Vasya4:
But that's exactly what I did. I used to have HellSpawn kernel and, before switching to N4 Revival, flashed ROM with stock kernel while wiping cache/dalvik before and after each flash.
[Nexus 4 Android Development] spezi77:
Alright, now we are clear about this point, at least.

Please send me your init.mako.rc file. It is located in the ROM's root folder. Maybe I can find something therein. If not I could try to make a reproduction..
[Nexus 4 Android Development] Vasya4:
File attached. Please take a look. Thank you very much for your effort!
[Nexus 4 Android Development] spezi77:
Revival r06 test build arrived (focus: reduce lags and improve power-efficiency).

P.S.: I am still investigating on the issues mentioned above concerning RR rom and AutoSMP / CPU governors. Stay tuned.. ;)
[Nexus 4 Android Development] spezi77:
Good news. I am pretty sure where the issue coems from. RR ROM has an outdated version of Kernel Adiutor which has lack of support of my CPU hotplug drivers (i.e. dyn_hotplug by stratosk). At the time when you turn on one of the hotplug drivers, e.g. AutoSMP, then KA is not able to stop the dyn_hotplug (which is my default hotplug). Hence you get two hotplugs active in parallel. That's where your problem starts..

Solution: replace your KA with the KA-mod (David 617) from this thread:

http://xdaforums.com/android/apps-games/kernel-adiutor-mod-singularity-kernel-t3333549
[Nexus 4 Android Development] Vasya4:
I wish it would be that simple. This is the KA mod (V15) I've been using. I even cleared the data and reinstalled it a couple of times just to make sure. Both hellsactive and stockdemand governors crash the system regardless of the hotplug (I tried dyn_hotplug and AutoSMP and even with all hotplugs turned off). The only difference is that hellsactive does it instantly while it takes stockdemand up to a minute to make the phone freeze and reboot.
[Nexus 4 Android Development] spezi77:
Yes, you are right. I was able to make a reproduction. It seems that in CM13 and RR this problem is present. It is under investigation. Stay tuned.
[Nexus 4 Android Development] bean+:
Thanks, just installed r06! [MENTION=5091819]spezi77[/MENTION]: In your Post #3, there was a direct link to a modified apk for KernelAdiutor (some time ago), "your" apk installed w/o any problems. Now you link to the thread "Kernel Adiutor-Mod [V15] [18JUL2016]". The downloaded file "app-release.apk" of this thread can't be installed (it is not an installable file). And with the original version of KernelAdiutor I can't see all options of your kernel . Do you have an link to an actual and installable apk for the modified version of KernelAdiutor which supports all options of your revival kernel?

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

Thanks, just installed r06! [MENTION=5091819]spezi77[/MENTION]: In your Post #3, there was a direct link to a modified apk for KernelAdiutor (some time ago), "your" apk installed w/o any problems. Now you link to the thread "Kernel Adiutor-Mod [V15] [18JUL2016]". The downloaded file "app-release.apk" of this thread can't be installed (it is not an installable file). And with the original version of KernelAdiutor I can't see all options of your kernel . Do you have an link to an actual and installable apk for the modified version of KernelAdiutor which supports all options of your revival kernel?
[Nexus 4 Android Development] Vasya4:
By the way, I'm using Purity ROM, not RR. But it is also CM13-based, so it shouldn't make much difference, I guess.

Thanks again for your effort!
[Nexus 4 Android Development] spezi77:
Woops, in that case you should try the debug variant: https://github.com/yoinx/kernel_adiutor/raw/master/download/app/app-debug.apk (also added to post #3 now).
[Nexus 4 Android Development] TNSMANI:
I don't know why it is not installable for the other member. For me, v15 of KA Mod by David (downloaded from his thread) installs and works well.
[Nexus 4 Android Development] benyjr:
Screen color inversion

Hi Everyone,

I installed the latest version of Revival on Resurrection Rom 5.7.3 and it works, but the screen colours are inverted/negative.

Is there some way to fix this?
[Nexus 4 Android Development] dragos281993:
Yes. Download the other version of the kernel and flash it only after you will have dirty flashed the ROM, or the "boot.img" file found inside the ROM.zip). Resurrection is CAF based, meaning that it's a mix between AOSP and CM. Even if you see "based on AOSP" in the RR's OP page, you need to flash the CM version of every custom kernel you want to try. I even had an argument with the RR dev about this matter but I decided to step back.
[Nexus 4 Android Development] seba112:
Which governor will be better? hellsactive or stockdemand for battery/perfomance?
[Nexus 4 Android Development] TNSMANI:
Are you asking for battery or performance? As per the Dev, Stockdemand is good for battery alongwith AutoSMP.
[Nexus 4 Android Development] spezi77:
Btw, I have tested an interesting combination of hotplug/cpu governor for the last couple of days which gives a fluid UX and good battery life. In my phone I get appr. 24-26h of normal usage until I have to charge it.

CPU hotplug: dyn_hotplug with min. CPU cores: 1 / max. CPU cores: 2

CPU governor: Smartmax

GPU max. frequency rate: 200MHz
[Nexus 4 Android Development] shubhdeep99:
For me default setting of your kernel is best in all way...

Using over RR and no problem here...

Thanks for your work
[Nexus 4 Android Development] spezi77:
Published r07 which addresses all of the r06 test (2016-08-06) changes as well as the following:

* Security update: Fix CVE-2016-5340 (Quadrooter Vulnerability)

* Compiled with -03

* Add CPU governor: yankdemand (a more battery-friendly derivative of ondemand)

* Add GPU governor: simple (faux123)

* Updated the kernel installer script to reduce logcat spam (powerhal) and to disable mpdecision / thermald

Added a new build of KernelAdiutor-Mod which allows to select Interactive GPU governor (see 3rd post).
[Nexus 4 Android Development] justmix4:
Thank you spezi for Quadrooter security update, now I can stay with latest Chroma. Cheers!
[Nexus 4 Android Development] Cristiano Lira:
Try yankdemand on the newest build. You won't regret. ;)
[Nexus 4 Android Development] justmix4:
Spezi, today I flash revival-r07 with latest Chroma August.

But QuadRoot Scanner still shows me that my device is vulnerable to CVE-2016-5340.

So I'm safe or not? Chroma does not see this security update, but it is safe, right?
[Nexus 4 Android Development] spezi77:
That's a tricky question and a matter of how reliable those "vulnerabilities scanners" can do their job. I believe that it is safe now. However, I cannot give you a 100% guarantee.

If you like you can compare my code changes line by line with the "official" patch which they use as reference to fix CVE-2016-5340.

Patch by codeaurora:

https://source.codeaurora.org/quic/.../?id=06e51489061e5473b4e2035c79dcf7c27a6f75a6

My commit:

https://github.com/spezi77/kernel_msm/commit/9e7406d213d9b0efb85c4d58e7240cf15eec2065

Have a nice day. :cool:

P.s.: To be on the safe side, you should turn OFF the option under Settings > Security > Unknown sources > Allow installation of apps from unknown sources.

P.p.s: please also take note that the kernel patch is only one piece of the puzzle. In order to get all security updates make sure that you have installed a ROM that has been patched according to the Google security bulletin from 5th of August 2016.
[Nexus 4 Android Development] justmix4:
That will not be necessary, you are a trusted developer. ;)

I checked the settings.

Chroma 08/02

Android security patch level:

5 August 2016

So I guess there is nothing to worry about. Thanks for your reply and best regards. :)
[Nexus 4 Android Development] spezi77:
You are welcome and thanks for your kind words! :D

And yes, now you can feel relieved again... :good:
[Nexus 4 Android Development] :
This kernel is running out very fast battery.
[Nexus 4 Android Development] colin p:
Still getting a freeze and reboot when enabling yankdemand, stockdemand or hellsactive on CM13. I use elementalx and autosmp and no issues. I'll just have to stay away from the other 3.

Using EX kernel manager.
[Nexus 4 Android Development] chaostrodamis:
Are you undervolting?
[Nexus 4 Android Development] spezi77:
It is per default aligned for performance. Please read this thread to learn things.
[Nexus 4 Android Development] colin p:
Nope not at all.
[Nexus 4 Android Development] spezi77:
In this release that issue is still present, unfortunately.
[Nexus 4 Android Development] chaostrodamis:
Does this also happen on your ROM (beanstalk) since it's CM based? I want to try yankdemand.
[Nexus 4 Android Development] spezi77:
No, in BeanStalk and AOSP ROMs it is not an issue.
[Nexus 4 Android Development] groovepeppy:
I just flashed your kernel with confidence

Flash and leave sort of user

By reading several last pages i guess ill wrote back here happy

Thanks Spezzi77

---------- Post added at 02:19 AM ---------- Previous post was at 02:17 AM ----------

I wonder why only 19 people press the good thank's button ?
[Nexus 4 Android Development] spezi77:
BTW, folks, I just realized with the help of your constant feedback and especially by the observations of [MENTION=5337411]Cristiano Lira[/MENTION] that in r05 or later some "overhead" got introduced into revival kernel which drains the battery too fast.

In order to fix this I have started to rebase this kernel. I am now testing it and I am close to releasing a lag-free and battery-friendly version of Revival Kernel. Stay tuned! :p
[Nexus 4 Android Development] TheArt.:
Awesome! As soon as you post it I'll flash it ;) Thank you for all this effort.

By the way, can someone confirm that Revival's default governor is Ondemand?
[Nexus 4 Android Development] spezi77:
r08 test (2016-08-14)

Addresses all of the r07 changes as well as the following:

* Rebased the kernel in order to leave faulty stuff behind as quite a few changes were in contradiction to battery-life and fluidness

* Added Improved framebuffer imageblit function

* Add toggle to control software CRC

* Here is a quick overview of what has been left behind: Linaro-power efficient wq, timer upstream updates and smp related updates)

N4-revival-marshmallow-r08-AOSP-UBERTC-5.4.zip

N4-revival-marshmallow-r08-CM-UBERTC-5.4.zip

fyi [MENTION=5337411]Christiano Lira[/MENTION]
[Nexus 4 Android Development] TheArt.:
Had a soft reboot, seems kernel related. What I changed from default settings: Max freq 1350, UV -75, speaker gain +3, DT2W, SELinux Enforcing. I managed to create these two logs:

(Btw OTG hack never sticks in KAmod)
[Nexus 4 Android Development] justmix4:
Try without UV.
[Nexus 4 Android Development] chaostrodamis:
I've had a couple and I didn't undervolt
[Nexus 4 Android Development] spezi77:
Assuming that you didn't turn off any wakelocks. Could you please turn off the three wlan specific wakelocks via KA to see whether this will change anything?
[Nexus 4 Android Development] TheArt.:
Done, let's see.
[Nexus 4 Android Development] TheArt.:
[MENTION=942874]spezy77[/MENTION] it happened again, this time it was a full reboot (maybe also others were full reboot) because it happened in my hands, I just launched a game (Though the fog) for a few minutes, and it rebooted. Logs attached.
[Nexus 4 Android Development] spezi77:
Hum, I have applied a patch with a potential fix for the last occurrence.

Are you interested in conducting further tests?

<test-rcu-fix REMOVED>

reason: increased speed, but too huge battery drain.
[Nexus 4 Android Development] TheArt.:
I flashed it 10h after you uploaded this test version, always with wipe dalvik and cache and clear data of KAmod. It was going fine until few hours ago as I found my phone rebooted, I was outside and I wasn't using it. Logs attached :)

Edit: I'm getting a network error uploading logcat.txt, if you need it, just tell me.
[Nexus 4 Android Development] spezi77:
Thanks, logcat isn't necessary. I hope with your logs to get closer to the root cause.

I am using the initial r08 test build since 4 days without any flaws. Are you sure that you didn't change anything about the default settings?
[Nexus 4 Android Development] TheArt.:
[MENTION=942874]spezy77[/MENTION] Yes I changed something from the default, please look at the message above. I always make those changes in every kernel I use, also since your initial Revival's release.