yashsingh1/xdaforums huggingface dataset:
[OnePlus 2 Android Development] magnamentis:
funny that, i was just pondering over the themes as possible culprit while it does not happen on the rom version from march 18th

currently i'm trying out all combos 18th-ROM+All kernels from v2.4+ up to v2.8 currently i'm on 18th-ROM+v2.6 working well but don't like the 2 big cores always on, hence have to try v2.7 on 18th rom again which before broke dt2w for me.

thing is dt2w is a must, big clusters off is a must, themes is an absolute must because i'll never go with whit-UI and Exodus has a issues with alert icons in the status bar not showing properly in addition to the fact that it's the only rom where FlatStyle Xposed Module does not fully work, in short, there is a statbar issue. other roms i can read in the thread are currently not at their best as well.

what i do now is to make nandroids from each combo until something brakes, hope that v2.7 kernel will work with 18th rom because the issue with themes and telephony started only with 24th-Rom and i only got fully aware of it with v2.8 kernel but that was perhaps only a coincidence.

i'll go through it all now and will report back as soon as i have a final result but if the themes are not compatible with latest cm commits i have to wait until the themers wil fix it. i've seen RRs in other ROMs as well hence it can be expected that it will be fixed from either side.

one thing seems obvious, it's not a kernel issue but my dt2w did't work on the 18th-ROM+v2.8 kernel combo. no i try to come from the down side up, means from lower versions updating to higher versions again, hoping that i'll end up at least with 18th-ROM and v2.8 Kernel because that one was very much to my liking :) let's see.

was a whole book i know but it's quiet here and i'm sure you like to exchange various finds :)
[OnePlus 2 Android Development] ollimi1:
Sure. The more the better!

Yesterday I noticed the reboot problems with incoming calls for the first time and was able to fix by simple reflashing the new modem / firmware.

With dt2w I have no problems using the latest 03/24 Temasek release and v2.8 kernel. It seems there are more than one culprit and it will be a hard piece of work to solve all!!
[OnePlus 2 Android Development] magnamentis:
[MENTION=535343]all[/MENTION]

ok guys the following is the case:

a) it's not the kernel, it's the roms but not just one, several of the lates CM13 based roms have the same issue

b) one could as well say it' the themes, but since the rom is newer tend to say that CM broke themes hence we have to wait for themes to be updated

possible workarounds:

use roms older than 24th, i tried 18th of march with those older roms themes work and hence no reboots but this kernel would be not fully compatible because

it will brake dt2w, perhaps more, didn't try every setting, for me is enough that dt2w does not work, hence this kernel does not work 100% on <19th CM13 ROMs

perhaps <24th-ROMs but did not try a rom for each date, hence <19th is 100% sure that this kernel v2.8 brakes dt2w and perhaps/probably more like s2w.

so to have everything working with >18th-ROMS but certainly with >24th-CM-ROMs+Kernel-v2.8 one would have to forfait most if not all CM-Themes.

that's no option for me because i can't have white-UI, it's a basic condition, hence i reverted back to ROM-Temasek's from March 18th and Kernel

Benschholds v2.6 that combo works flawlessly, only downside i found is that to cores of the big cluster are always on, don't like it but it's for me

the smallest price to pay.

Most probably as it seems is that one of the commits between March 19th and March 24th broke CMTE (CM-Theme-Engine) and themes cause

the random reboots upon incoming call and eventually on other occasions.

so either you stay on latest rom with latest kernel without theme or you revert back to older rom as mentioned above and older kernel as and for reasons

mentioned above and therefore can keep you themes and have a fully working phone. probably at the price of a bit of battery consumption with

2 big cores always on.

there would be many more possibilities, combos and so on to mention but that would be too long to read, hence i hope the general situation was explained here

good enough.

EDIT: Benschholds Kernel v2.7 is less sophisticated than v2.8 but as well brakes dt2w on same roms like v2.8 hence i did not mention v2.7 much

use either v2.8 on later than 24th Roms without themes or v2.6 on <19th roms with all working but a less sophisticated but ok working kernel.

sorry for the double post but it concerns both, rom and kernel, due to the combo of things working and/or braking, depending and not everyone with the kernel is on temasek

and not everyone on temasek uses this kernel, hence it needed to be posted in both places IMO. i changed the wording very sligthly but mostly it's and identical post
[OnePlus 2 Android Development] ollimi1:
Yeah!

You are definitely right, we need some new hotplug drivers which are fully compatible to big/LITTLE and hmp true octa core architecture.

Only handle both cluster as two quadcores is not enough because of his hmp feature.

It is time OnePlus finally delivers the promised update for Q1, so that kernel developers like AK would maybe decide to work again with our device.

Hopefully! He had something mentioned before he changed the device to N6p angler!

Attention: off topic!

The devil in me wants to freeze in my thanks meter, (hohohohohohhhahawwwuurgg!)
[OnePlus 2 Android Development] magnamentis:
you know, yesterday was my birthday and nobody called me LOL thanks god there is email and messaging but interestingly today i got two calls coming through and both told me they tried all day yesterday and it was just ringing without response. when i got the calls today i was

updating EXODUS Rom so i had even less thoughts about my phone not working, very bad luck though. Exodus uses layers themes

so it did not matter, while i have other issues with that rom, can't use it right now.

thanks again for mentioning the themes because i would not have just believed my own find. i've just seen in the logs some users had posted that there was a huge bunch of font colors, many lines in a row and i thought that's a strange thing but am simply not good enough (not good at all) in reading logs, except if there is an app name followed by "fatal error" LOL that even i understand haha... it's just rarely the case :(

good night

---------- Post added at 01:03 AM ---------- Previous post was at 12:44 AM ----------

did you read the book? "Und sein zahl war 666"? the red one with black letters? very interested. there were so many canditates but all gone by now, hence we will have to watch out further LOL
[OnePlus 2 Android Development] ollimi1:
Haha, congratulations afterwards! :highfive:

In my case the caller was routed to the mailbox, after he heard 2 times the ringtone, but on my side no ringtones resounded I got only the reboot!

Ps. Danke für die Anregung. Mal sehen ob ich's irgendwo finde..
[OnePlus 2 Android Development] Methroix:
Since the dissappearance of Core Control I'm using MSM Performance. Right now I'm running at 4:2 (LITTLE:big).

For Governor I've lately been using Impulse as it is very fast at ramping both up and down, but I've just now changed back to Interactive.

Although Interactive has had no impact on MSM Performance hotplug; the Maximum Cores value is still the number of cores that will always be online.

Maybe I've misunderstood the function of hotplugging?

I thought this function was to make sure only the cores actually needed were powered up.

I've noticed that by default MSM Performance is set to -1:-1, which afaik means MSM Performance is disabled, which also results in 4:2 cores online.

With Core Control out of the picture, exactly what is then controlling the cores?

This is pretty much my conclusion as well; MSM Hotplug and MSM MPDesicion Hotplug are engineered towards single cluster CPU's and, from what I can see, cannot handle load between two (or more) clusters.
[OnePlus 2 Android Development] shantam3108:
As far as I know Andi in his kernel separated the function of the a53 and a57. The A57 cores were waked only when needed and didn't remain on. It treated a53 and a57 as different clusters
[OnePlus 2 Android Development] AANISH:
My wifi isn't working
[OnePlus 2 Android Development] urgali:
most useful post ever
[OnePlus 2 Android Development] magnamentis:
yep it is because it gave such a good example how not to post and for us to pinpoint it LOL hahha...

BTW my light switch doesn't switch, the rest is non of anyone's business :D
[OnePlus 2 Android Development] benschhold:
Kernel Update 2.9

Update Kernel

removed msm and bricked hotplug

replaced with Intelliplug and Thunderplug

code cleanup

gpu optimization

backlight dimmer

IMPORTAND:

i didnt had time to port all features from Thunderplug to KernelAdiutor, use Thunderzap Control from play store in between.

But i will implement ASAP cause this hotplug is optimized for octo core and works really nice
[OnePlus 2 Android Development] chintu1234:
In v2.9 kernel auditor seems to get installed but there is no way to launch it. There is no icon whatsoever in any launcher i try but if i look in system app remover it is there. Weird.
[OnePlus 2 Android Development] magnamentis:
you can use a shortcut instead of a launcher icon, would look like below, i attached the sidebar with the app shortcut which i'm really using but also included a set up just made for you to demonstrate how it looks on desktop, i will delete it from there again
[OnePlus 2 Android Development] tremendouz:
OT:

Didnt need your support yet, but I read most of the posts.

Awesome!
[OnePlus 2 Android Development] nuwan32:
I'm having the same problem and tried this, but doesnt work. freq just shoots back up to 1344.
[OnePlus 2 Android Development] Hackpb:
Try Disable touch boost...
[OnePlus 2 Android Development] iaa85:
It's okay use anothers gov's then interactive with these hotplugs?

Edit 1: adreno idler option doesn't stick, I tried a reboot and got disable again, I am on 2.9 version.

iaa85 from Brazil with Oneplus Two
[OnePlus 2 Android Development] yuva_cool:
The cpu freqs dnt stick.. Cant change them. Tried all kernel tweak apps
[OnePlus 2 Android Development] iaa85:
Did you tried disable touchboost?

iaa85 from Brazil with Oneplus Two
[OnePlus 2 Android Development] return.of.octobot:
I can't tell you all how thrilled I am with the inclusion of an octa-ready hotplug driver. I realize Kernel Adiutor is now the defacto tuning tool for this kernel, and that UKM is no longer being updated to support new features. I'm fine with this as I primarily covert my profiles into init.d scripts but of would be nice to see UKM compatibility remain intact as a secondary option.

On another note, as I've seen some mentioning the absence of the Core Control. I can't speak for 2.9 as I've yet to install it, but as for 2.8 the module is still intact and can be re-enabled by renaming the file @ system/lib/modules/msm_core_ctl.ko_ to msm_core_ctl.ko. Just remove the underscore.
[OnePlus 2 Android Development] AndroidBeginNinja:
This kernel works on nxrom I don't know how well though I used nxrom for less than a hour. This kernel works on vanillia unicorn.(currently testing) This kernel for sure works on AOKP.
[OnePlus 2 Android Development] yuva_cool:
No I did not, but can u please give me a list of settings you would prefer on this kernel for optimization between battery and performance?! Thank you.

Pm me if possible.
[OnePlus 2 Android Development] abhishekcma:
+1 yeah preferred settings ??
[OnePlus 2 Android Development] benschhold:
3.0 is soon finished

Any wishes left?
[OnePlus 2 Android Development] Flamehell:
I m going to flash temasek rom....so i will wait a little bit,so i can also flash your new kernel....tnx buddy :D
[OnePlus 2 Android Development] magnamentis:
just came across an idea recently, how about keeping default settings as close to stock as possible so that in case anything seems out of the ordinary one can always go from there, activate and deactivate features (hotplugging etc) dunno if that's well explained without going into lengthy details, let me know if you need further elaboration.

this would allow you to play more with features without having to find out whether lastest changes caused any issues.

i'm specifically talking about battery consumption.
[OnePlus 2 Android Development] :
What about merging some features from KA Mod ( Github )?!?
[OnePlus 2 Android Development] tlxxxsracer:
Undervolt for those who want to get more battery life ;)
[OnePlus 2 Android Development] nicesoni_ash:
How about a "reset to default" settings option?
[OnePlus 2 Android Development] urgali:
Smartmax governor ?
[OnePlus 2 Android Development] Mohit31:
Option to disable hardware keys..

No option in temasek and don't know if it's kernel related

So if it is...It would be great if included

Thanks
[OnePlus 2 Android Development] nicesoni_ash:
That's a rom feature afaik, most probably CM implementation so guess you will have to wait for that.
[OnePlus 2 Android Development] Mohit31:
In stock cm if we enable onscreen Nav bar.

Hardware buttons automatically gets disabled but not on temasek.. So was wondering if it can be implemented
[OnePlus 2 Android Development] nicesoni_ash:
I was talking about the option for that. I guess it can be implemented since it was in lollipop too but [MENTION=4729623]benschhold[/MENTION] builds these roms from sources, guess their developers has to be asked not him.
[OnePlus 2 Android Development] magnamentis:
i want both so to have both is a feature and if you don't want to use HW keys simply don't use them, how can they distorb, they're invisible when time set to 0 hence don't bother while i want all nav features available. softkeys are good to have via expanded desktop as well, similar to authide of the dock on a mac (or windows pc)
[OnePlus 2 Android Development] nicesoni_ash:
Exactly. I would rather have a choice than them completely off.
[OnePlus 2 Android Development] Mohit31:
Well I prefer them completely off when I m not using it..

I don't want on screen and hardware keys doing the same thing for me..

I want my screen to be small and don't want it to be active since I don't want to use and disabling it would avoid any unintentional touch
[OnePlus 2 Android Development] benschhold:
I will think about your requests and let you know what is baked in

UV control is definitely not possible
[OnePlus 2 Android Development] magnamentis:
thanks god no UV, that would add another 100 pages with issues to the thread LOL ;)

let's see what we get, i'm confident it will be good, thanks
[OnePlus 2 Android Development] return.of.octobot:
Undervolting is just one of those things, as with many tunable parameters, that should be left alone by those that don't fully comprehend the functionality, risks vs. reward. Unfortunately those same individuals tend to have a shoot first ask questions after you've broken something mentality. UVing can be of potential benefit, but only when applied in moderation. Otherwise, it can easily end up doing more harm then good and you'd never know it because you didn't know what you were doing to begin with.

Those are the same people who drop in with posts like "what setting for best battery life and performance?" Is it not a little more rewarding to develop an understanding of what works best for you? I'm all for the sharing of knowledge and experiences, but before you allow yourself to be spoonfed a set of parameters it would behoove you to wrap your head around why you're doing what you're doing, and how it all fits together rather than taking someone else's word on what's in your "best" interest.

This was absolutely NOT directed at anyone in particular, just tossing my two pennies.
[OnePlus 2 Android Development] Hellgamer007:
Haven't been able to find any other requests for this - but would it be possible to change how the screen brightness works? to get adaptive display working better? the brightness slider only does very little change on my phone, and its quite blinding :/ I'm guessing it doesn't have to do with the brightness too much, also to do with screen saturation?

sorry if this post is redundant! and thanks for the great work so far! :D
[OnePlus 2 Android Development] benschhold:
you mean backlight dimmer? thats allready build in
[OnePlus 2 Android Development] Hellgamer007:
I Saw your previous thread about it being added to the kernel, and I am running v2.9 so I do have it, but using the brightness slider doesnt seem to be change the brightness much, im not sure why. There is a difference, but not a major one
[OnePlus 2 Android Development] arch_geek:
Try changing the brightness with Lux Auto Brightness app from Google Play. If the screen brigntness changes normally as it should, then it might be a ROM issue.
[OnePlus 2 Android Development] Hellgamer007:
Thanks, this helped. I realise the issue isnt actually due to the kernel but the way grarak's rom handles brightness - if adaptive brightness is set, it seems it doesnt allow changing the brightness by large amounts using the brightness slider . My bad, nothing to do with the kernel after all.

Thanks for your time! :D :eek::victory:
[OnePlus 2 Android Development] arch_geek:
Happy to help!:D
[OnePlus 2 Android Development] urgali:
You don't have enabled it, probably.

To do so, open kernel adiutor and go to screen tab then scroll down until brightness dimmer
[OnePlus 2 Android Development] benschhold:
Kernel V3.0

Kernel v3.0

All settings for Thunderplug now in KernelAdiutor

[*]Added Governors:

* Smartmax

* Bioshock

* Blu-Active

* Intelliactive

* Hyper

* lionheart

* Pegasusq

Changed from Intelliplug to Thunderplug as default HP

[*]I have tweaked TP Hotplug settings, stock kernel configuration should bring a good comprimise between performance and battery consuming.
[OnePlus 2 Android Development] Flamehell:
Today you are better than Santa Claus :D Tnx a lot!!
[OnePlus 2 Android Development] MrMajestic:
Dayumm if only your kernel had support for new OOS 3.0..

I'm tempted to go back to CM13 just because of the awesome new update.
[OnePlus 2 Android Development] benschhold:
Ay before i forget it

someone wanted a reset to default button

just turn off all enable on boot tabs and reboot, no need for a button
[OnePlus 2 Android Development] ollimi1:
...and if it's done, go to profile section and create a profile with stock kernel settings to reset your settings in future a bit faster!:D
[OnePlus 2 Android Development] return.of.octobot:
Damn we're really moving on up over here. The inclusion of smartmax is a welcome one indeed, consider my interest piqued. I'm curious if it's been optimized for our SOC. Last I heard Maxwen was stating that he had no plans to support newer Linux kernel iterations.

Welp, guess there's only one way to find out. Flash and see how it behaves. I know we've already got darkness, which I'm much appreciative of and is presumably a more refined nightmare. With that said, I've always kind of preferred nightmare due to it's configurability.. that's a word, I'm sure of it.
[OnePlus 2 Android Development] Flamehell:
Amazing kernel.....works great!!!:)
[OnePlus 2 Android Development] Hackpb:
Anyone having problem defining the max frequency for the little and big core? For example when defining another max frequency it doesn't stay... Other then that amazing kernel...
[OnePlus 2 Android Development] umair9001:
Even have an issue with the big core's max frequency being set and the governor.. Always keeps going back to interactive after reboot..already reset kernel auditor by disabling set on boot..still the issue persists..
[OnePlus 2 Android Development] hunter_bruhh:
I need the code for the kexec hardboot patch to give to Lord boeffla so he can implement in his test kernel for me to test. Can you email me a reply please? hbashton13@gmail.com

Kind regards,

Hunter
[OnePlus 2 Android Development] return.of.octobot:
Word. I'm getting some real nice results using a smartmax/ darkness combo with a conservative thunderplug. This kernel has allowed for some of the most effective 810 management I've seen since the OP2 came into being.

I got mine shortly after launch and put it on the self for quite awhile in favor of my OPO due to how stagnant development for it was. Between this kernel and full device functionality finally being achievable in custom ROMs, it's gotten me to blow the dust off for DD usage and I'll be damned if I'm not actually enjoying myself. I can't say it enough, keep up the good work! I'll likely share my parameters after some further tests and refinements, likely in the form of init.d and screenshots in lieu of Synapse profiles as I know many of you have moved on to KA.
[OnePlus 2 Android Development] shantam3108:
Cpu frequencies doesn't stick on smartmax governor even without reboot
[OnePlus 2 Android Development] danielhariri:
how you manage the BIG.little frequency? i just disable touch boost and all.. and it still there

however.. i must say this kernel is total badass...

Edit-

I manage to find and edit init.d script to put cpu frequency way i wanted... But it wont work.. My code is wrong somehow
[OnePlus 2 Android Development] benschhold:
i just found out how to handle the shutting down of big cores on low battery :good:
[OnePlus 2 Android Development] mido25:
By turning off bcl battery driver?
[OnePlus 2 Android Development] benschhold:
no, by adjusting the right variable, im looking into now if we can change this on the air
[OnePlus 2 Android Development] nexus_vl:
This is how it should be.

Can't find lead to big cores tho.

Don't forget to set permissions 0755 / rwxr-xr-x

Maybe also a good idea to activate "emulate initial.d"
[OnePlus 2 Android Development] benschhold:
cpu0 = little cores

cpu4 = big cores
[OnePlus 2 Android Development] nexus_vl:
I still can't find it, sorry...
[OnePlus 2 Android Development] :
If all big cores are shut down, the govenor settings are deleted. And if one core came back online, the standard settings are loaded.
[OnePlus 2 Android Development] benschhold:
I DID IT :D

​
[OnePlus 2 Android Development] magnamentis:
great job :good:
[OnePlus 2 Android Development] danielhariri:
I try the init.d script... But the thing is.. It just dont stick same like adjusting the KA... Maybe bcos script only perform on boot only.. It seem tht theres no workaround yet for this one

+1 the setting revert back when core is offline.. This BIG.little architecture really hard to understand.. It is really amazing you could get thus far :good: :good: :good:

Edit-

suggestion.. Maybe many other wont agree with me

Disable OC while we find some workaround for frequency problem

Again.. Its just suggestion.. I wont mind delete it later on
[OnePlus 2 Android Development] nicesoni_ash:
[MENTION=4729623]benschhold[/MENTION]

Can you set default settings of both big and small cores to their default values 15** something rather than 20** something? If someone wants to overclock them, they can. [emoji4]

Also I need some more time before reporting about that test build. Still waiting for some tests. Thanks.
[OnePlus 2 Android Development] shantam3108:
Pretty nice with v3.0
[OnePlus 2 Android Development] benschhold:
im having a hard time finding the culprit for big cores frequency reverting after cluster shutdown

this stops me from releasing 3.1

if someone knows in which version this didnt happen this would help me
[OnePlus 2 Android Development] FAB1150:
Seen the new changes, has someone some profiles for this v3.0? :p
[OnePlus 2 Android Development] oediv:
Thanks for the latest update

Also Updates temasek

It's really stable and my battery is very good

I was just came Home after 13 hours without wifi! Only LTE

lost 8% over night

Thanks :)

Everything stock by the way

Only using greenify, amplify and appops
[OnePlus 2 Android Development] danielhariri:
Hard limit.. Yes this is it...

I think this would work.. Workaround before 3.1 release... Ty
[OnePlus 2 Android Development] return.of.octobot:
Glad I could help, chances are it's only necessary to define frequencies for cores 0 and 4, but I don't know that. I've always taken the better safe than sorry approach.

Sent from my intoxicated ONE A2005