yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Android Development] spezi77:
Woops, seems like I didn't pay attention. The answer is no, Voltage settings got removed without purpose.

Thanks for reporting it. [emoji6]

Sent from my beanstalk'd & hellspawn'd N4.
[Nexus 4 Android Development] bart.found:
Just flashed! No voltage control, but I can live without it till the official release! :P
[Nexus 4 Android Development] granazis:
Just posted on nexus community about new test build r13 prompting the users to see exactly your posts about first.Please if possible inform me what is the best version and ubert tc to flash on Broken 4.7 build rom?coz i always trust u following your posts.Notice that this will be my first try on this kernel.

Tnx in advance
[Nexus 4 Android Development] dragos281993:
If you want complete stability, flash "r12 tc5.3". Make sure that before flashing "hellspawn", to either dirty flash the ROM or flash the "boot.img" file found inside the ROM.zip. And before doing any of the above, uninstall the kernel manager that you're using (if you have one installed) or just wipe its data from Settings/ Apps. Only then can you reboot into recovery and do what I said above.

Cheers !
[Nexus 4 Android Development] granazis:
TNX!! for reply,all these are known.

Have a nice day friend.
[Nexus 4 Android Development] cemilplt:
If 7.0 is not stable enough? It was a very update.
[Nexus 4 Android Development] dragos281993:
Tc 7.0 is still an experimental toolchain while 5.3 is stable. While I tried 7.0, I haven't experienced any bugs but other users might put their device under a scenario that I didn't, and might end up with problems. As stable as may be, the toolchain is in an experimental stage.
[Nexus 4 Android Development] cemilplt:
Thanks for the answer.
[Nexus 4 Android Development] spezi77:
BTW, it seems that in r13 test build you cannot change CPU governor to Ondemand. Can anyone confirm?

After changing to Ondemand in KA, it immediately flips back to the previous governor. I'm sorry for that and will try to find a solution (hopefully) soon.. ;)

Sent from my beanstalk'd & hellspawn'd N4.
[Nexus 4 Android Development] cemilplt:
There is a bug report.No photo using the flash in a dark environment fails sung.r12-5.3CM https://plus.google.com/106738992948239440820/posts/beB97b69BC4
[Nexus 4 Android Development] dragos281993:
Very odd. I'm on Pure Nexus and for me the governor doesn't revert to default. I tried other governors, force closed KA Mod and the governor still remains the one I selected. So that problem is not present on the tc 5.3 AOSP version.

Edit: I got a random reboot as soon as I pressed to "send" the message before this "Edit" part.

Here's a log:http://cloud.tapatalk.com/s/5751346e5e0eb/2016-06-03_10.36.zip
[Nexus 4 Android Development] granazis:
[MENTION=5796730]dragos281993[/MENTION],Good afternoon friend,yesterday after midnight Hellspawn r12 ubert tc5.3 flashed on 4.7 Broken build and as always use to first try camera(snapdragon on Broken) in dark space on every kernel changed, there is no flash sync plus i have had a black pic only,tried also w/Footej camera w/same result,this not happen w/in rom included kernel and w/Quanta v16.My next step is to try it on another rom.

Had u ever met something like this?Its also happen w/Taurus R43.

Just informing
[Nexus 4 Android Development] dragos281993:
Very odd. Never had a problem with the camera, on any ROM or kernel.

Try the camera below. Reboot the phone first, then install this camera app and see how things go.

http://www.apkmirror.com/apk/google...mera-2-4-025-1636091-30-android-apk-download/
[Nexus 4 Android Development] granazis:
Thanking for your reply i will on latestRR iam running now on wich snapcamera also included and for this one iam interesting and inform.

Regards
[Nexus 4 Android Development] bart.found:
I can easily change the governor to Ondemand (or whichever I want).

Hellspawn r13 uber TC7 AOSP
[Nexus 4 Android Development] dragos281993:
Same here. Tc 5.3 AOSP.
[Nexus 4 Android Development] Cristiano Lira:
+1.
[Nexus 4 Android Development] granazis:
[MENTION=5796730]dragos281993[/MENTION],just flashed and tested on latest RR -> NONE camera problem,so may be on rom(Broken) depended.

Just an info plus to all.

Regards
[Nexus 4 Android Development] kol1124:
Ok, so the newest test build works really good. No crash, no lags, battery seems to be better than last build or maybe it's cause fresh flashing anyway.. Thanks for sharing and I'll report if anything happen ? Peace!

Wysłane z mojego Nexus 4 przy użyciu Tapatalka
[Nexus 4 Android Development] spezi77:
Hey there, I am pretty sure that this bug is not a kernel related issue, but exists in your ROM.

I have fixed it a few weeks ago in my Beanstalk ROM. Tell the dev of your ROM to add this commit into their device tree:

https://github.com/spezi77/android_device_lge_mako/commit/8a5b13afbd68456d5bb0bf17e7b6f42612e6e1a3

Sent from my beanstalk'd & hellspawn'd N4.
[Nexus 4 Android Development] spezi77:
Thanks very much for your feedback, guys! I just realized that I have forgotten to clean cache & dalvik after flashing the new kernel. Now it works, and in this moment I feel like a bloody n00b.. [emoji15]

Sent from my beanstalk'd & hellspawn'd N4.
[Nexus 4 Android Development] dragos281993:
Ha ha ! It happens to the best people too sometimes.
[Nexus 4 Android Development] bart.found:
I never clean cache and dalvik after I flash a kernel, unless things start to become weird! :P

Does this affect Google Camera too? In 2.4+ versions flash doesn't sync with shutter.. so I never update!
[Nexus 4 Android Development] spezi77:
It will affect any camera app because this change is applied in the OS / hardware interface. I hope this answers your question.[emoji14]

Sent from my beanstalk'd & hellspawn'd N4.
[Nexus 4 Android Development] granazis:
[MENTION=5091819]spezi77[/MENTION],as posted to [MENTION=5796730]dragos281993[/MENTION] and and answered by me "may be on rom depended" and confirmed by him some posts above yours, can u please explain why not happen w/in rom included kernel(a cm based dt2w included plus........) and Quanta v16?

Tnx in advance
[Nexus 4 Android Development] spezi77:
Sorry, I can't explain it.. firstly, I would have to consult my Oracle. [emoji16]

Sent from my beanstalk'd & hellspawn'd N4.
[Nexus 4 Android Development] granazis:
I will always remember this answer,tnx a lot sir!
[Nexus 4 Android Development] Daandofreak:
I am using kernel adiutor, under wake lock settings i found some wake lock toggles. They all are on by default, means wake lock prevention is off? Or on? Can't understand. I don't want wake locks so should I leave these settings or turn all toggles to left?
[Nexus 4 Android Development] dragos281993:
When an option is unchecked, that's means it's disabled. Checking the options, turn them on. So, by default, all those options are on.
[Nexus 4 Android Development] Daandofreak:
But for 2nd option it is written that I have to disable it to prevent from this wake lock. Means I have to disable it, or not?
[Nexus 4 Android Development] dragos281993:
The text is a bit off. Keep the option activated/checked so the "wakelock blocker" can prevent the wakelock.
[Nexus 4 Android Development] Daandofreak:
It's really complicated. Dev is writing other suggestions.
[Nexus 4 Android Development] dragos281993:
If the dev says that, then you definitely must follow his suggestion. As I suspected, there was a translation mistake which is very confusing and can be misinterpreted. But we got a precise answer on how things are.
[Nexus 4 Android Development] spezi77:
The behavior is the same for all wake lock knobs, it is NOT specific for the second option. When the knob is ON (default) your phone does not block the wake lock.

Thanks for your screenshot. I will ask the dev of KA-mod to improve the descriptions of the other knobs accordingly.

Sent from my beanstalk'd & hellspawn'd N4.
[Nexus 4 Android Development] Daandofreak:
Thx for replying, ur kernel is great. I will disable all these wakelocks. I was always thinking they are already off �������� I hope there is no difference between kernel adiutor mod and original kernel adiutor regarding wakelocks settings.
[Nexus 4 Android Development] Daandofreak:
Now this means all wakelocks are off now?
[Nexus 4 Android Development] DarkPhoenix7878:
Love this kernel,it makes my n4 feel fresh again!
[Nexus 4 Android Development] spezi77:
This means that all wakelocks are getting blocked by kernel (knob off). ON means that the kernel allows the Wakelocks.

Auf Deutsch: AUS bedeutet, dass die Wakelocks Kernel-seitig verhindert werden. AN bedeutet, dass die Wakelocks zulässig sind (Standard).

Sent from my beanstalk'd & hellspawn'd N4.
[Nexus 4 Android Development] Daandofreak:
Danke, es ist echt verwirrend. Hab jetzt alles nach links gedreht.
[Nexus 4 Android Development] spezi77:
You can use this app to test the effect of the wakelock options: WakeLock Detektor - Zeigt Anwendungen an, die Ihr Gerät aktiv halten: https://play.google.com/store/apps/details?id=com.uzumapps.wakelockdetector

Sent from my beanstalk'd & hellspawn'd N4.
[Nexus 4 Android Development] ivanich:
Got reboot when played a game, last kmsg attached. Cm13… kernel r13 test http://cloud.tapatalk.com/s/57533ff2f20c9/last_kmsg.txt
[Nexus 4 Android Development] colin p:
After reading nearly through 71 pages (skipped a couple though) I installed "hellspawn-N4-mm-6.0-r12-CM-UBER-TC7.0.zip" and set the CPU hotplug to Alucard and CPU governor to Smartmax to see how battery life works out. Certainly a lot more settings than the stock CM 13 kernel. Thanks muchly for this, as I intend to keep my N4 for as long as I can.
[Nexus 4 Android Development] spezi77:
Do you have changed CPU governor to elementalX?

Sent from my beanstalk'd & hellspawn'd N4.
[Nexus 4 Android Development] cemilplt:
https://plus.google.com/112559686997337277076/posts/dWoryJRTrZK---oldest known facts here leave here Replaced by a new Truise "Hellspawn Kernel" Thanks (Spezi 77)
[Nexus 4 Android Development] spezi77:
The URL brings a

404.*That’s an error. [emoji12]

Edit: Here is a working link: https://plus.google.com/112559686997337277076/posts/dWoryJRTrZK

And please don't forget to leave a vote for your favorite kernel! ;)

BTW; Just to inform you: elementalX is no longer stable in r13-test-build. I have already taken notice of it and took a last kmsg.

Sent from my beanstalk'd & hellspawn'd N4.
[Nexus 4 Android Development] spezi77:
Hellspawn users, right after giving your vote in the G+ thread, I would like to ask you to also participate in the newly started poll in this thread. ;)

I intend to evaluate your feedback and eventually consider the results to purify the CPU options in one of the next builds.. Any questions? No? That's perfect, then please gimme your vote! :D
[Nexus 4 Android Development] cemilplt:
The survey continues the boss.
[Nexus 4 Android Development] Daandofreak:
I am trying zen decision and smartmax combination now. Wow, really very fast and I am having not same battery saving like with Alucard and smart max but speed is really awesome.
[Nexus 4 Android Development] spezi77:
Spoiler:

Out of my experience the best battery saving/performance combo is AutoSMP/smartmax.

Sent from my beanstalk'd & hellspawn'd N4.
[Nexus 4 Android Development] Daandofreak:
Under screen settings there is this Exponentiellen thing. I changed the value and it was darker then usual but best at night. Is this the standard screen setting or when it is enabled?
[Nexus 4 Android Development] spezi77:
You must be talking about the Exponential brightness feature (introduced by Statosk). It allows you to make the screen go so dim, that you can't hardly use it anymore. And I think that it is turned off by default. When you turn the knob OFF, your screen will have a very low brightness. Be very cautious when doing this -- especially during daylight! You may need to increase the min brightness value for better results.
[Nexus 4 Android Development] Cristiano Lira:
R12 AOSP-ubertc5.3.

ROM Pure Nexus with DU UnicornBlood kernel latest build.

Settings: smartmax with ioisbusy set 1 and ramp up during boost set to 0 (should this be made default?), -80 UV, mako hotplug, gpu governor set to ondemand and max freq of 200MHz, noop IO scheduler and vibration power at 45%. [MENTION=5091819]spezi77[/MENTION], I think the mako hotplug + smartmax is the best combo cuz it leaves always at least 2 cores on but I will check it with AutoSMP. What number of min cores online do you use?
[Nexus 4 Android Development] Mrcactuseater:
What kernel did you use sorry?

Tapatalk'd from my Twisted, Despaired Nexus 5x
[Nexus 4 Android Development] Cristiano Lira:
HellSpawn r12-AOSP-ubertc5.3, as I said in the post. I also use the brightness set to minimum and adaptive.
[Nexus 4 Android Development] Mrcactuseater:
You also said you were using the UnicornBlood one, so I'm just clarifying.

Tapatalk'd from my Twisted, Yank'd Nexus 5
[Nexus 4 Android Development] Cristiano Lira:
I was saying the ROM build I am using that is from Narasimha Kasibhotla which he posts on his G+ profile. I think his builds are the best regarding battery, specially the last one that comes with new adreno drivers.
[Nexus 4 Android Development] Mrcactuseater:
You said you were using PureNexus ROM and UnicornBlood. You mentioned Hellspawn above that but no matter, I'm glad your battery is good comrade.

Tapatalk'd from my Twisted, Yank'd Nexus 5
[Nexus 4 Android Development] spezi77:
AutoSMP also allows you to set min. CPUs online to a custom value.

For performance I use 2 cores online -- for battery 1 core online.
[Nexus 4 Android Development] math.rangel:
hey, could you ask the KA dev to add the DT2W power key suspend for our mako? It's a really useful feature. I use Kernel Adiutor and also Quanta Tweaks just to check this option
[Nexus 4 Android Development] cemilplt:
The New Emperor
[Nexus 4 Android Development] spezi77:
Hey there! Yes, I could try to get this done. First off, I need to get from you the sysfs path for this feature. It should look similar like this:

/sys/module/qpnp_power_on/parameters/pwrkey_suspend
[Nexus 4 Android Development] spezi77:
Unbelievable.. hell yeah! :D:D:D
[Nexus 4 Android Development] tvisforme:
Hi, I've run into a bit of an issue with this kernel and SuperSU. I've typically been flashing CM13, the HS kernel (CM UBERTC 7.0 version), then SuperSU (currently 2.74 beta) and GApps. This has worked for quite a long time now. Today, in updating to the latest CM13 nightly (from a late May version) I also updated HS from 9.5 to 12. Unfortunately, that is when an issue arose, despite all flashed items registering as successful in recovery. Flashing the kernel, then SuperSU, leads to a successful boot, root access with su, but the stock CM13 kernel (ie no HS kernel). Reversing the order (flashing SuperSU and HS12) also boots, but gives me the HS kernel and no root access. I've tried numerous methods to try to resolve this, including wiping /system, installing SuperSU, booting, returning to recovery and flashing the kernel, etc. I've just gone back and redone the flash with HS 9.5 and things are working properly again. Is there anything that has changed between 9.5 and 12 that might affect SuperSU and the boot image?

Thanks in advance for any insight you can provide.
[Nexus 4 Android Development] math.rangel:
Well, in the terminal I used this one: echo 1 >sys/devices/virtual/input/lge_touch/dt_wake_pwr_disable

Don't know if that's what you want but it's the only thing I know
[Nexus 4 Android Development] spezi77:
Thanks for your detailed report. I remember that in the installer for r12 I have introduced a cleaner script. Maybe that's causing the issue with SuperSU.

Could you do me a favor and copy the kernel zImage from r12 into the installer of r9.5? That would be very interesting.. ;)

Sent from my beanstalk'd & hellspawn'd N4.
[Nexus 4 Android Development] Kaan_:
I've talked about two of my issues, supersu and selinux, in your beanstalk thread. Both of those were resolved by installing quanta kernel. I was able to install supersu and be able to temporarily disable selinux. Apps I mentioned worked properly too.
[Nexus 4 Android Development] colin p:
I have the same issue as tvisforme with CM 13 (June 7 2016 build), SuperSu (2.67) and HellSpawn (R12 TC5.3). I can only have SuperSu or HellSpawn installed, not both. However, since this is the first time I've tried a custom kernel, I have no point of reference.
[Nexus 4 Android Development] spezi77:
Alright, let me remove that cleaner script in my next kernel build. I would be glad if you are willing to test it..

Sent from my beanstalk'd & hellspawn'd N4.
[Nexus 4 Android Development] spezi77:
It works. I just added it with help of yoinx into KA-mod. :D

Would you like to get a test build? Then tell me which KA app do you have.. standalone or built-in?

Sent from my beanstalk'd & hellspawn'd N4.
[Nexus 4 Android Development] colin p:
Absolutely, send away.
[Nexus 4 Android Development] bart.found:
Hi [MENTION=5091819]spezi77[/MENTION], just had a random reboot... here's a log for you

Hellspawn r13 Uber tc7

http://hastebin.com/wacovufoca.vhdl
[Nexus 4 Android Development] tvisforme:
I can test as well, if you like.
[Nexus 4 Android Development] snacs:
Hi [MENTION=5091819]spezi77[/MENTION], why you don't try dyn_hotplug (Stratosk) or intelliplug (faux123). The implementation from Stratosk is awesome. :D
[Nexus 4 Android Development] spezi77:
I know intelliplug and have tested it in this kernel. But unfortunately it slowed down things.

About dyn_hotplug: well, we could give it a shot in an upcoming test build although I I intend to take a lean approach and plan to get rid of too many options.

Sent from my beanstalk'd & hellspawn'd N4.
[Nexus 4 Android Development] pevire:
Hello, yesterday I flashed this kernel to have dt2w and I've noticed that after a time, Whatsapp doesn't receive the message until I activate the phone.

What parameter should I change to avoid that?

Thanks in advance.

Finally, tired of loosing my whatsapp notifications I uninstalled and reinstalled the app and it worked.
[Nexus 4 Android Development] math.rangel:
Amazing! Thanks, man. Yeah, I would love to get a test build. I'm using the standalone app
[Nexus 4 Android Development] spezi77:
Here you go.. ;)
[Nexus 4 Android Development] spezi77:
I had a chance today to merge dyn_hotplug by Stratosk into this kernel. See here: https://github.com/spezi77/hellspawn-N4/commits/mm-6.0-STAGING-dyn

But the KA-mod app is currently lacking support for it. I have asked the developer if he could offer his help to implement it...
[Nexus 4 Android Development] xenyz:
Isn't alucard hotplug almost the same as dyn_hotplug, with a few extra tweaks?

And you're getting rid of elementalx, one of the best battery friendly CPU governors?

Release #13 is cursed :) :) :)
[Nexus 4 Android Development] snacs:
Wow you are fast hehehe. It works with synapse, maybe... I can try a CM version with Synapse if you are interested.

I think so no, because alucard was designed first for Galaxy S4 (different SoC), and Stratosk worked on dyn_hotplug exclusive for our N4. Alucard is good for battery life, but sometimes there's a lag, freeze... Personally, dyn_hotplug + ondemand (Stratosk) were the best combination I used in a kernel (KK/LP days).
[Nexus 4 Android Development] xenyz:
I stand corrected, sorry I was thinking of blu_plug hotplug.
[Nexus 4 Android Development] snacs:
So excited

Sorry posting it in this thread... but the combo of one of the best kernel I have used and this legendary ROM :fingers-crossed:
[Nexus 4 Android Development] str3tch72:
Hi guys, I have one question. Anybody using Paranoid 6.0 with this kernel? Is it compatible? Best regards.
[Nexus 4 Android Development] dragos281993:
I'll try PA in around an hour. I'll let you know if it works. But it should work. Don't see why not. It's AOSP Marshmallow after all.
[Nexus 4 Android Development] Thrikiller18:
It works and it is smooth and fast as hell. try this rom guys. don't think and just flash it
[Nexus 4 Android Development] spezi77:
No worries, I am also excited about AOSPA. I used to have the PA Kitkat & Lollipop build on my old school device, HTC Desire. [emoji16]

Sent from my beanstalk'd & hellspawn'd N4.
[Nexus 4 Android Development] str3tch72:
Yes, it's working good. :D

Wysłane z mojego Nexus 4 przy użyciu Tapatalka
[Nexus 4 Android Development] spezi77:
Ok, i will try to make a CM build for you by tomorrow...

Sent from my beanstalk'd & hellspawn'd N4.
[Nexus 4 Android Development] Thrikiller18:
[MENTION=5091819]spezi77[/MENTION] I've installed PA on my mako. but after flashing su and kernel. system shows me still the aospa kernel?

any idea?
[Nexus 4 Android Development] spezi77:
No idea. I didn't find time to flash PA yet and make a test. Could you please make a copy of your recovery.log after going through the installation steps?

Sent from my beanstalk'd & hellspawn'd N4.
[Nexus 4 Android Development] Thrikiller18:
ok I've just solved the issue.

1- I flashed su and rebooted my device

2- I flashed hellspawn r12 5.3 aosp and rebooted again.
[Nexus 4 Android Development] Cristiano Lira:
I went through this issue also yesterday. The problem is that flashing HellSpawn on top of a system-less setup will break root and when you flash SuperSU again it will reinstall the stock kernel backup it made when first installed SuperSU over it because it sees that the kernel is already patched. I got it to work installing HS r12 after SuperSU in a row, I've done this with r13 test build also but it will break root after some seconds after the ROM boots (or it worked in r12 because I tryed with the new 74 SuperSU beta?). I think if you flash HS before have ever flashed SuperSU could work too, because it won't have any backup to restore.
[Nexus 4 Android Development] TA123:
I have flashed the TC5.3 version with the latest Chroma and sound stutters occasionally when I am listening to music.

---------- Post added at 03:38 PM ---------- Previous post was at 03:36 PM ----------

Is PA that good? Never used it before.
[Nexus 4 Android Development] snacs:
One of the best ROM in XDA. The PA team was hired by OPO to develop OxygenOS for OnePlus 2 and OnePlus X. They developed a lot of nice features, like PIE, peek, halo, floating window. In Android KK they developed dynamic system bar.
[Nexus 4 Android Development] spezi77:
Uploaded r13-test-#2.

Change log:

- CPU hotplugs:

-- dyn_hotplug (Stratosk) -- currently not supported in KernelAdiutor-mod; use Synapse instead

-- thunderplug (Varun Chitre) -- compatible with dual, quad core CPUs

- CPU governors:

-- elementalX (back in town)

-- thunderX (Using smartassv2 as base, and with optimizations for ARM SoCs added on top, ThunderX does not compromise UX and is an ultimate choice to keep your phone juiced up.)

- latest upstream updates taken from msm-flo-3.4-mm-mr2

Downloads:

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

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

hellspawn-N4-mm-6.0-r13-test-#2-BS-UBERTC-5.4.zip

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

hellspawn-N4-mm-6.0-r13-test-#2-CM-UBERTC-5.4.zip

hellspawn-N4-mm-6.0-r13-test-#2-CM-UBERTC-7.0.zip
[Nexus 4 Android Development] Cristiano Lira:
Lol, Chrome and Windows Defender are saying that the file has virus (trojan).
[Nexus 4 Android Development] emraz786:
[MENTION=5091819]spezi77[/MENTION], I'm using r13 test, I put dyn hotplug but can not find in ondeman (stratosk) ondeman only single.

Enviado desde mi Nexus 4 mediante Tapatalk
[Nexus 4 Android Development] spezi77:
Hum, I cannot exactly understand what you are pointing out. Can you please post a screenshot with what you get. And then explain what you would expect?

Sent from my beanstalk'd & hellspawn'd N4.
[Nexus 4 Android Development] emraz786:
well, I hope to explain this well ... what I mean is that I thought had a special ondeman by stratosk, which was different to that brings the default kernel.

Enviado desde mi Nexus 4 mediante Tapatalk

---------- Post added at 09:01 PM ---------- Previous post was at 09:00 PM ----------

Enviado desde mi Nexus 4 mediante Tapatalk