yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] RenderBroken:
Thanks!

Yea things have been crazy busy for myself with my new job and such. Alot of cool things have been going on behind the scenes. I am trying to finish up the forever promised R22 build for CM12.x based roms. I have a new CM13.x CAF build ready to go but want to fix the annoying Sleep of Deaths that are occurring. I have an idea what it is and need to remove certain changes. Once done, I will release! Of course.

Now for N6, I am still undecided what I will do. There are already a metric crap ton of heavy hitters in the kernel world taking up real estate there. But I would still be doing my own builds anyways so I might as well as release them. Main difference there is now you have CM13 and Stock to build for. I am still learning the new 3.10 based source. Also learning how they do the new Hotplugging where all cores are left online. 100% of the time while the screen is on. My biggest desire would be to post that functionality over to the OPO but that may be way too difficult to make happen. There would have to be a ton of changes in a large number of subsystems, mostly scheduling though.
[ONE Original Android Development] NOSTALGIA:
no worries and yeah i agree. so many hitters outt here.. haha..just dnt mind them.
[ONE Original Android Development] Setting.Out:
It's not the size of the ocean, its the quality of fish... ;) Just remember to swim home to us once in a while..
[ONE Original Android Development] RenderBroken:
My goal is to further hone my kernel skills and learning. The OPO was the first, amazing Android experience I have ever had. I was so blown away by the phone and still am surprised at how well it performs. I do not plan on selling it and this way I can use it for development/testing. I am working on the last issue over the next few days and will release as soon as I believe we are good to go.

But you are totally right, I try to not just release builds that have such minor changes or updates. I like to release substantial updates. If nothing is going on I do not mind releasing a new build with minor updates that come from the main branch I build for (CM13-CAF or CM).

Thanks for the kind words! :)
[ONE Original Android Development] KnightGalahad:
Works with TWRP 3.0.0

:good:

Running geekbench to see how long I can get for max SOT
[ONE Original Android Development] iTalisman:
Guys...anybody still using CM12.1 CAF ROM's? Can you please link me up with the latest stable CM12.1 CAF kernel and the lastest test version if you have it? I am still using the AK version of Euphoria CAF and would love to pair it up with Render again but lost all the files...

Kinda desperately searching for it... :(
[ONE Original Android Development] iTalisman:
[MENTION=5438598]RenderBroken[/MENTION]....any other site where I can get a copy?

Edit: My apologies. Found it. Somehow forgot to stretch my eye at the bottom of the screen :-/
[ONE Original Android Development] siddheshvartak:
Link is not working for cm12. X
[ONE Original Android Development] RenderBroken:
Hello Ladies and Gents!

Been awhile, been busy like crazy lately for me. I just wanted to drop a line and say that I am still around, just have life to deal with first. This is a rule for me, my personal life will always come first. But, I am seeing light at the end of the tunnel and plan on kicking things back into gear. I hope everyone has been well.

Kind Regards,

Zachariah
[ONE Original Android Development] Setting.Out:
Don't go towards the light... It might be a train?.. ;)
[ONE Original Android Development] RenderBroken:
Thanks for the info! Just wanted to make sure I didn't miss anything.

I thought I seen you use the updated version I had done. Its possible the unofficial update I had done doesn't work wright for the OPO. Thanks for chiming in as always :)
[ONE Original Android Development] RenderBroken:
Well so far so good, I have had 0 reboots. Only issue I have is that the phone doesnt go to sleep now. Doesnt really make sense to me as I did not see any changes regarding sleep but there it is. . . So I may end up going with plan B. I imagine there is some cruft somewhere else in the code that doesnt allow for Load based calculations and I am not sure I can find it. Still everything will work the same, just some of the under the hood stuff that i would like would be missing :( oh well. It was worth a shot. I am trying to debug it further to see if I can catch the cause.
[ONE Original Android Development] Thunderbolt:
SOT 6h 10 min and 6% left On this kernel with gianton settings. Freaky awesome.
[ONE Original Android Development] RenderBroken:
Thanks for reporting!
[ONE Original Android Development] Thunderbolt:
You must know, that Phone have tough life with me. Tapatalk non stop, clash of clans and others. This is the best score On opo for me.
[ONE Original Android Development] RenderBroken:
Wonderful! That is the goal I am trying to reach. I want great performance but decent battery life to go with it.

So I decided to go with plan C and start over from scratch with all the scheduler commits and load based commits. I am about to flash and test. If this doesn't work I will go with plan be and JUST rework CPU-Boost to add in the new features and makes some changes to the hotplugs to use the new features.
[ONE Original Android Development] ahaq:
The new CPU boost your trying to make it efficient that's causing you the prob from going deep sleep?
[ONE Original Android Development] RenderBroken:
I am pretty certain that the problem is the scheduler changes that are needed for some of the new cpu-boost changes. I reset them and only made the absolute necessary changes. Testing seems good so far. If DS is still affected then I am going with Plan B and just making changes to CPU-Boost where DS worked fine.

EDIT: DS is still jacked :( But thats ok. Still making CPU-Boost smarter!
[ONE Original Android Development] _ASSASSIN_:
yeah.. CPU boost's default settings are far too aggressive for me to consider using really.
[ONE Original Android Development] RenderBroken:
I agree, I have been playing with different values myself and now with per cpu ability you can really adjust cpu-boost to your liking. Testing new build now. . .
[ONE Original Android Development] _ASSASSIN_:
Have you gotten slimsaber working yet? I've read that the issue is that the Slimsaber's ramdisk is different to that of CM12. Will you have a slimsaber branch or just won't bother?
[ONE Original Android Development] gianton:
Dev said that he's going to release next build with the any kernel format which will work on SlimSaber too.
[ONE Original Android Development] ahaq:
Hopefully the new changes to CPU boost help the battery efficiency
[ONE Original Android Development] RenderBroken:
I will try to have it out for R3 but not sure. If not then R4 for sure. If I am going to use it then I will need to do alot of work just to make sure when a user flashes my kernel ontop of another's, it will cleanup anything left over.

Should but not by much. Just should sleep better.
[ONE Original Android Development] ahaq:
to be honest, the kernel is all well done to the latest version, just if can solve the mic problem this will be really stable. plus you are fixing the cpu post and deep sleep, it will make it rock stable
[ONE Original Android Development] gianton:
As Euphoria 5.1 beta is out and working great, hope for a 5.1 release soon.
[ONE Original Android Development] ahaq:
Are you using stock Euphoria or put render on 5.1?
[ONE Original Android Development] gianton:
Only stock or ak v137 working on Euphoria 5.1 beta atm.
[ONE Original Android Development] ahaq:
Got it. If you have youe setup for new euphoria like you had via render
[ONE Original Android Development] RenderBroken:
Ok So really, I am going with Plan E. That is, the problem with DS was not my kernel but somehow and something was messed up in my rom install and after a clean install all is well again . . . #fml lol that is android dev work in a nutshell guys. So, I am going to go back to Plan A lmao.
[ONE Original Android Development] Bobbi lim:
[MENTION=5438598]RenderBroken[/MENTION] can you remember which version of your kernel works with COS12?
[ONE Original Android Development] RenderBroken:
Here you go bud:

https://androidfilehost.com/?fid=24421527759885488
[ONE Original Android Development] Bobbi lim:
It works? :eek:

I thought your latest R21 kernel only works with COS12.1 & CM12.1?
[ONE Original Android Development] RenderBroken:
Sorry, I didn't realize you were asking for only cm12. I am not sure but when I get on my computer I will try to look. Thanks for letting me know.
[ONE Original Android Development] Bobbi lim:
No problems! I appreciate your help :) Take your time as I'm staying on stock for now :cowboy:
[ONE Original Android Development] rajdoll:
Just to confirm again, is it working on COS12. 1 too apart from cm12. 1? Because i tried and got continuous boot loop after display of launcher screen.
[ONE Original Android Development] Bobbi lim:
I don't think its working on COS12.1 as I got a bootloop as well
[ONE Original Android Development] HFX9:
Why in R2 version is minimal cpu frequency 300mHz and in recommanded profile in synapse use smaller value?

Is it possible change this?

Odesláno z mého A0001 pomocí Tapatalk
[ONE Original Android Development] RenderBroken:
Hey, sorry, that is old. I no longer use Synapse as my main kernel app. I use Kernel Aduitor. Also, that profile was for an older version of my kernel that offered OCUC.
[ONE Original Android Development] RenderBroken:
Most likely COS12.1 is just too new compared to my CM12.1 kernel and they are just not inline anymore. May need to update it. I am not in the know here but CM is still only officially at COS12.1? not COS13? Thanks guys.
[ONE Original Android Development] nikhil18:
synapse onboot settings problem has been fixed
[ONE Original Android Development] Bobbi lim:
Official build as of this post is COS12.1.1 (with cortana integration)
[ONE Original Android Development] TLR_Sky:
Is it possible to have bluetooth rsap working with this kernel? i have a One plus One with standard (rooted) CM12.1 however they have disabled diag mode in the kernel so i am not able to enable Rsap. is this possible with this kernel to have rsap working or have diag mode working?

Thanks!

Mark.
[ONE Original Android Development] RenderBroken:
I will look into it. I have been bringing up my new Nexus 6 kernel since that is my new daily driver. Once done I will be continuing work for the OPO. I have a number of things I will be bringing to my next OPO build.
[ONE Original Android Development] TLR_Sky:
Thanks mate that's all i can ask :)

Regards,

Mark.
[ONE Original Android Development] NewHeights:
OC

Hi, i'd like to know if it's possible to overclock the cpu with this kernel, or if there's a kernel that allow this on opo with caf-cm13?

thank you:confused::confused:
[ONE Original Android Development] ahaq:
So we can estimate 5.1 support quicker?
[ONE Original Android Development] RenderBroken:
yes. Now that I can stop spinning my wheels on an issue that is not an issue.
[ONE Original Android Development] Formhault:
What was plan A again? :silly:
[ONE Original Android Development] RenderBroken:
Who knows at this point lol

It was to setup Load Based Syncs, hotplug and wakeup boost and the ability for the hotplug to suspend while screen off since there really is not a need to boost then.
[ONE Original Android Development] RenderBroken:
New Build!

This has all the new features (Look in Synapse) but does not user Anykernel so it wont work with CM12.1 or Slim Saber yet. This has some changes that had caused reboots when I first started but I believe I had fixed them by adding in some missing code for cpu-boost. Only way to tell is to have more ppl flash and report! Also Sound issues should be fixed now as problematic code has been reverted.

Let me know.

https://drive.google.com/file/d/0B-GVJKBx9-GnOUJWV3JFdFczcWc/view?usp=sharing
[ONE Original Android Development] Formhault:
Speaker gain can be lowered now, yay!

Perhaps you can enable Earpiece gain control in the future, too! :fingers-crossed:
[ONE Original Android Development] aftmkt:
I was going to suggest a clean install, but refrained from doing so.:p

Downloading now. Will test and report for bugs, if any.

FYI, with the previous test version, i ended up with 49 hours of total usage with 6 hours SOT.

That is pretty awesome in my books. Thank You.
[ONE Original Android Development] Formhault:
Doing what? :D
[ONE Original Android Development] aftmkt:
Almost everything except gaming.

For some reason, i just dislike gaming on a handheld device. :D
[ONE Original Android Development] gianton:
Working great with my setup on latest 03/29 Euphoria 5.0.2. Phonecalls over speakerphone is fixed now.

Thanks for your hard work.
[ONE Original Android Development] PsyGik:
Yeah right :p
[ONE Original Android Development] RenderBroken:
Totally true man. It just happened to be that build of euphoria. I use my phone so much that I didn't notice the abnormal drainage. I even did a clean install and the problem was still there even with ak. Using the newer build fixed the problem.

Also I am happy to report that I have had 0 reboot and have a SoT of almost 2 hours at percent left. Very happy with the results and performance. Right now with cpu boost lowered per core and hotplug boosting, now when a core is onlined it doesn't have to ramp up, now it starts out at 1ghz. This has pretty much eliminated micro lag for me while keeping the phone battery friendly. For me, when a core is hotplugged, we are saying that load is high and needs to be addressed. Why wait for the governor to ramp up to handle the spike in load. Starting the core out at 1ghz (for example), we are able to handle the spike and go offline faster when done instead of the wait to ramp up to a high enough freq to handle the load, then go back down.

Also with the per core ability we are able have these features on the cores we want! This works with any hotplug so I can set it to only boost on cores0-1 and off for the rest since those cores are normally the only ones used while browsing and such small workload. Right now the possibilities are endless and I look forward to see what users come up with.

Lastly if you have ANY reboots, please let me know and provide a log. This new code is something I spent 2 weeks working on before I released the first build and ultimately had to drop the code even though It's a huge part of my kernel vision. But I am hopeful that we are solid now. I had to reset certain files and rebuild but I am quite happy.
[ONE Original Android Development] aftmkt:
[MENTION=5438598]RenderBroken[/MENTION] Could I ask you to share your current "synapse profile" please.

Also, the latest test version is going strong as much as you would like.

Very stable and NO reboots. This looks promising.

Forgot to add: Running this on the 03/26 CM 12 nightly.
[ONE Original Android Development] RenderBroken:
I pretty much run it stock. I only change minor things like wifi scan time to 300 (like I'm always looking for free WiFi lol) enable ksm (testing for now, want to see if it helps) I enable drop caches and write back mode, lower min cpus for msm hotplug to 1 from 2 since this new cpu-boost really helps hotplugging cores with no micro lag.

That's about it. I use impulse in conjunction with cpu boost and believe I get better batterylife this way rather than disabling cpu-boost all together and running a more performance based governor. With my latest tests, they seem to backup what I am saying.

When I get back home I will push my source code for others to look at. These new changed not only make cpu-boost smarter but the scheduler too. Now it schedules keeping load per core and frequency the core is at to decide if it's up to speed to handle said load.

Last note, the hotplug I use (msm_hotplug, intelliplug, msm_mpdecision (bricked)) have their stock boost functions removed to work with this unified boost system I had reworked in the latest test build. This obviously prevents each driver from stepping on each other. Causing unneeded overhead and other minor issues.

Some more things I plan on adding:

Zram

Optimax governor.

Also if no one noticed, I added AutoSMP hotplug, this hotplug driver code is very small and efficient. This was written by the same person who created msm_mpdecision.

You guys will find that u like to try things, if they work and fit, they stay, if they are unused and redundant they will be wiped from this kernel. Maybe in R5 we will know what works and I will cull the rest. No sense in making this kernel cluttered.
[ONE Original Android Development] RenderBroken:
Also anykernel is incoming so my build should now work with all cm12 based roms. This way I don't have to build a kernel for each variant like slimsaber, cm12.1,cm12, etc.
[ONE Original Android Development] aftmkt:
Pretty much stock I see. Makes sense when the kernel is very optimized by default, such as in this case. :highfive:

Yes, totally did not notice AutoSMP, I guess no one scrolls till there. LOL. Will give it a whip in the next charge cycle:D

Liking where this Kernel is heading towards.

Many thanks to you and goodluck with everything you wish to implement.:good:
[ONE Original Android Development] störte:
Great work. Do you have plans to build an omni kernel for the 5.1 ?
[ONE Original Android Development] DerRomtester:
It is difficult because omni is using a completly different device and kernel tree. It would be alot of work. So i guess no.
[ONE Original Android Development] RenderBroken:
Not really. I would imagine that my kernel with the anykernel scripts should work but you never know. If not then I will most likely not support it.
[ONE Original Android Development] abhi08638:
I just wanna thank you for making such an awesome sounding kernel! Really can't wait to test the anykernel version :D
[ONE Original Android Development] ahaq:
Waiting patiently!!! For the cm 12.1! Legggo I'm fired up!
[ONE Original Android Development] gianton:
I got high kernel wakelock overnight in standby, on R3-T24 and Euphoria.
[ONE Original Android Development] RenderBroken:
Not sure if you are joking but I don't really see anything wrong. I may be overlooking something. Also I found that I had 0 Deep Sleep using Euphoria's last build, something was wrong with that build for me cuz it was like that after a clean flash too. The newest build doesn't have Exchange email services so I am not on it but now using AICP 3/29, I get amazing battery life.

Let me know your thoughts, I know you give good info so I am interested in what you think. Thanks!
[ONE Original Android Development] gianton:
Usually with ak kernel I loose 1-2% overnight with the same setup and ROM. Lost 7% with R3-T24 which I consider high. Top on the list of kernel wakelock is Wlan. You might have a look at it.

Other than that kernel is rock stable and very smooth. Thanks for your hard work.
[ONE Original Android Development] RenderBroken:
Ok I see. Sorry, coming from the G2, 6% per hour is awesome lol. But I will take a look and see what has changed. Thanks for the input.
[ONE Original Android Development] Formhault:
I've noticed some weird Wi-Fi dropouts. I'm connected to my neighbour's Wi-Fi (don't say I'm stealing bandwidth - it was 3 AM and we don't have data caps ANYWAY, just my router was too busy doing something else :silly: ) and every once in a while (especially when waking up the phone) I would see a toast notification going like "Connection restored : <my neighbour's Wi-Fi>".

I'm on Euphoria. Wi-Fi during phone sleep IS enabled.

Not sure what's up with that :eek:
[ONE Original Android Development] gianton:
Which Euphoria version?
[ONE Original Android Development] Formhault:
Oh, right. Latest 5.0.2 build.
[ONE Original Android Development] gianton:
No such issue here and definitely not kernel or ROM related. Must be the router playing up or smth.
[ONE Original Android Development] Nandeh:
No wakelocks here along the night in airplane mode. Using [MENTION=1546609]gianton[/MENTION] profile [MENTION=5438598]RenderBroken[/MENTION] R3 T32 and last Euphoria build 5.0.2.

Using last Slim Gapps downloaded from here:

http://104.236.22.120/index.php?device=gapps/lollipop

Thanks everyone for your work :)
[ONE Original Android Development] gianton:
You can't have any wakelock while on airplane mode. My test was with everything enabled data, WiFi and sync on.
[ONE Original Android Development] Nandeh:
I have got draining while in airplane mode in other ROMs and devices. I think this is due to unexpected wakelocks.

But not in the OPO with this combo :)
[ONE Original Android Development] clockworkstop:
Sound is fine again! Thanks.
[ONE Original Android Development] störte:
Well then i will give it a try when the anykernel is coming. Just changed to Darkos Omnibased 5.1 Rom
[ONE Original Android Development] abhi08638:
Its seems like an app was taking advantage of the location services and not letting the phone go to sleep. Try checking the alarms and seeing what woke the phone up
[ONE Original Android Development] gianton:
Nothing is keeping my device from deep sleeping. It's a kernel wakelock as with the exact same ROM and GApps on ak kernel I loose 1-2% overnight.
[ONE Original Android Development] schaggo:
Of course you have (a) wakelock(s). 1h 13m 52s awake, of which only 3m 33s can be attributed to screen on. 1h 10m are unaccounted for. Wakelocks.

You have NlpWakeLock 34m 59s, Network Location Provider Wakelock which was triggered 3781 times. Hinting to that also *alarm* with 2000+ counts as well as further down LocationManagerService with almost 9000 counts.

Inspecting Kernel Wakelocks, I see 3500 counts of wlan, of which 1747 did not get resolved and ran in a timeout and expired. So an app is somehow accessing the wlan module, putting a wakelock in place and not resolving it. Also qcom_rx_wakelock hints at this, 1446 wakelocks of which, and I lol'd, 1446 ended unresolved. 153 of which woke the device up.

I think network location fires every 4 minutes, not fully sure of that though. However, assuming it does fire every 4 minutes, if I take 10h times 60 minutes, add another 51 minutes I arrive at 651 minutes. 651 minutes divided by 153 fired wakelocks I get 4.26 minutes per wakelock. I might be wrong, I might not, but I believe all that happens is your device being kept awake by Nlp which tries to acquire the network location by initiating a scan on the wifi module and either failing or not, I don't know, but whatever, ultimately causing over 1h of awake time which brings down your battery percentage.
[ONE Original Android Development] MBurns2:
bootloop with slimsaber..any suggestions ? thanks
[ONE Original Android Development] Formhault:
This kernel is not compatible with SlimSaber for now.
[ONE Original Android Development] RenderBroken:
Wonderful explanation! Feel free to drop more truth bombs on this thread lol.

Correct, I am working on AnyKernel today and should have a new build for everyone! Also note guys that Formhault is a contributor to this project and that we work closely together on this project. So he is pretty much always in the know. I say this so when he seems to speak on my behalf, you know why.
[ONE Original Android Development] RenderBroken:
AnyKernel is now setup and ready to go!

Putting last touches on R3 now. Very excited for this build as I am with all my builds lol. I was able to fix a weird bug that has been plaguing me for some time now. So that's nice. I should be releasing soon.
[ONE Original Android Development] Beaster:
Loving the frequent update posts!

Awaiting for R3!

Thx
[ONE Original Android Development] DerRomtester:
How do you manage francos thermal driver and stock thermal with anykernel ramdisk?
[ONE Original Android Development] RenderBroken:
Dont have to worry about it. I set it so Franco overwrites the stock driver in the source code and remove code that is needed for the Stock driver. So you dont have to touch anything in the ramdisk for it.
[ONE Original Android Development] DerRomtester:
So i dont need to disable stock thermal inside ramdisk ?
[ONE Original Android Development] RenderBroken:
No sir. If you used the same commits I did then no.