yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] andip71:
No, I cannot myself. Maybe the master of zzmoove [MENTION=3279788]ZaneZam[/MENTION] can shed some light.

But just realized... even with the stress test app I was not able to produce enough load to load all cores completely on 2880 with interactive. Interesting.... :)

But seems this is due to thermal throttling coming in, phone is already quite warm...

Andi
[ONE Original Android Development] Arise:
Ok, I will test more, but I think the issue is from the kernel maybe, not from governor itself, because the other governors that can scale up at max act in the same way (2 cores at 2880 and 2 cores at 2457MHz).

Anyway, again, awesome work and awesome kernel, I also cloned your github repo, I will take some look at this maybe I will be able to understand something. :)
[ONE Original Android Development] sui81:
[MENTION=254166]Lord[/MENTION]

Any Chance to get a Boeffla CM11 Version ?

BTW: Danke im vor raus...
[ONE Original Android Development] andip71:
Well, not planned as I stated, as I cannot test it.

But I already built an unofficial version of the kernel for genuine CM. And a test user confirmed it seems to work fine.

However, if I decide to give it out, I will provide no support for it as I cannot check things myself. If you are interested in giving this test build a try, just PM me.

Andi
[ONE Original Android Development] andip71:
Sure, let me know if you find something :)

It is the very first version, as I stated, I expect things to come up to be fixed and fine tuned. Everything else would be... "strange" :)

Question... how is that behaving with other kernels? AK, Franco etc.? Different?

With stock there is no OC possible, so no need to ask :D

Andi
[ONE Original Android Development] Arise:
Haven't tested exactly latest franco and AK kernel because I didn't had the time to do that.

But tested franco 22 and AK gold 50 and there was no overclocking, they had only the default 2457MHz stock. They had more or less governors (some were removed, some added) but no OC options, only UV.
[ONE Original Android Development] ZaneZam:
well we all (including me *g*) have to watch closely and have to learn how governors (respectively scaling) behave on this device. what I can say for sure is that hotplugging is out of scope for all the governors as this is made now by Qualcomms mpdecision service so we can completely exclude all "core stories" here! this mpdecision is closed source so we never will know when and what it does exactly but as andi said I think it's also responsible for the not fully scaled up cores as it makes also thermal throttling and cpu boost (if I'm not wrong) ;) I did some testing with native Hotplugging of zzmoove and here it would behave like zzmoove behaves on other devices including switching cores off BUT unfortunately it leads to crashes due to excessive hotplugging (or maybe because of switching off core 4?) . honestly I think hotplugging build in the governor is history on newer devices and will never come back. so the conclusion is now that this whole behaving is normal on opo. ;)

that's my actual knowledge about this for me new platform so corrections appreciated if I talked BS :)
[ONE Original Android Development] NickosD:
Testing right now :D
[ONE Original Android Development] NickosD:
So........ Great performance with 38r. I got always <40k using ak. Keep up.

For some reason the settings at gpu tab are not editable....
[ONE Original Android Development] andip71:
Yes, performance looking good.

And again yes: GPU tab is not editable as nothing on GPU side is implemented in the kernel.

This app is a generic app for all my kernels, on S3 and Galasy Tab 10.1, the GPU tab has functionality. On OnePlus kernel not. And this is what the red message should tell you :)

Same goes for many other options in Boeffla-Config. Some are not possible to be implemented there, some make no sense as the OnePlus has it already by default.

Thanks

Andi
[ONE Original Android Development] NickosD:
I guess it's the same for the equalizer? Only the volume on l&r and speaker I can edit there.
[ONE Original Android Development] andip71:
Absolutely. This is even stated in the feature list of the OP.

Get me technical documentation to the WDC9320 audio hub, and I can check what else all can be done :)

It is not available freely unfortunately.

Andi
[ONE Original Android Development] NickosD:
I own the donate version ^^
[ONE Original Android Development] andip71:
Yes... and? What do you want to tell us exactly?

Thanks

Andi
[ONE Original Android Development] NickosD:
I thought it was gonna be a donate thing only, now I got where the "freely" was going.
[ONE Original Android Development] andip71:
No no. The donation version of my app is only for people that want to support my work and as such get some nice little comfort functions activated.

But also the normal (non-donation) version always is enough to configure my kernel completely.

So, when some things in the app are deactivated, it is because this functionality is not (yet) implemented on kernel side. Thats all about it.

Andi
[ONE Original Android Development] pantmunu:
So far so good. Had a random reboot while using Facebook unfortunately I'm not using any log apps. If it happens again .. Will post the last kmesg thingy . battery life is great
[ONE Original Android Development] andip71:
During boot the max frequency is 2457 stock, not more.

Also if you choose to overclock, the oc frequency is applied when the user interface is already loaded (ie when the Boeffla Config notification displays in the notification bar).

Andi
[ONE Original Android Development] vikrant82:
Awesome thanks. Enjoy your vacations.

Sent from my A0001
[ONE Original Android Development] magnamentis:
latest

made a factory reset to see, no gapps, no mods, just boot and look and all was fine, then installed the kernel beta9, all was fine

so it's not the kernel, it's not the rom, it's not xposed, it's not superSU 2.19, tried as well was all fine.

but still it's something that works on beta8 but with no other kernel also not cm default kernel anymore. so for now i'm stuck on beta8 and will

wait until cm11 nightlies stop or whatever final version is out and make a hyper cleany. if it's true what i heard tomorrow will be the latest nightly which would fit in to cm history in the past upon new os releases.

thank you all for caring and as suspected quite early in the process it's a userspace issue, an app or something.
[ONE Original Android Development] andip71:
Thanks magnamentis for the feedback. Still is weird...

I did not follow so much, why is tomorrow last nightly? Are they switching to cm12 already?

Now I am really gone for holidays ☺

Andi
[ONE Original Android Development] Franc38:
Flashed beta 9 and my wifi slowness that had me flash the stock wifi firmware are gone. (That was on CM11s XNPH38R)

So now I really have a "full boeffla kernel" and it works very fine.

Enjoy your holidays, Andi!
[ONE Original Android Development] magnamentis:
heads up+

ok that sound like a night ride :)

Back OT: i was reading that cm will stop feature development of cm11 except bugfixes and security patches a per tomorrow but then it might as well be a day or 2 later. reason is that they want to publish M12 in a few days and later, during the first week of december, start with cm12 nightlies. but a) this is the plan while we don't know if the plan works out in time and then i was not in a board meeting with them so chance it hight but not 100% that it will be in fact so.

as to my problem, i spent the night to perform a clean install and go from scratch. all works well, just made a nandroid from the new configuration and will do the fine tuning tomorrow. however it was overdue obviously, just a pity that it did not last the few days so that i could have saved me that till cm12 will be out. nevertheless, as i said, it's part of the game and thus no biggy :)
[ONE Original Android Development] DjDiabolik:
Very great feature for ac value stock value if sliders is set to 0.... on next charcing i thinks i can watch what's the exact value use my 1+1. After thins i thinks i can try to set a little much value for obtain a little less time for obtain a full charcing..
[ONE Original Android Development] andip71:
Yes, just be aware with stock logic the rate used is VERY much dependent on charger and cable. It varies between 500...1200 for me using different chargers. But anyways nice to see it now.

Andi
[ONE Original Android Development] gianton:
Its 940 mA on stock charger for me.
[ONE Original Android Development] Aavion:
[MENTION=947981]Lord Boeffla[/MENTION] andi? i've monitored the charging behaviour as promised.

screen-on it requests 1.2A, average current is at around 900mA.

in idle state it requests 2A, average current is at around 1.7A.

so far my observation...

i go back to 2A fixed current as i don't have any heating problems while screen on charging, even while gaming :)

Gesendet von meinem 1+ One
[ONE Original Android Development] Roman91:
andi can you please add to the list "things to do" the possibility to off softkeys light when you press the screen, and maybe to change the intensity of the vibration of softkeys.

btw for now good holidays :)
[ONE Original Android Development] DjDiabolik:
mmm...great.. i don't use the original cable because i dislike it :) on next charging i can monitoring it........... but other member have reported the value whit screen off... how i can monitor the AC value whitout turn on the screen ? From the config app it's possibly to obtain a log file ?

Ah... on config app you can add a function to Reset the 1+1 to recovery ??? For example on "Reset App" inside preferences you can also add a choice for restart 1+1 in Recovery... this is also usefull when you want to update whit newest kernel. Whit this addiction you can "Reset APP" and restart directly on recovery for flash the new zip, now when you reset app the 1+1 it's automatically resetted.... and on next start you need to restart all over again to back on recovery but if it's present a choice on config app i can use the reset app and directly goes to recovery....
[ONE Original Android Development] magnamentis:
you would need a amperemeter / voltmeter which you would have to loop in between the power source and the consumer. all software based numbers on consumer side are not accurate and mostly not really "realtime"

there are threads about this specific topic, i bought such a device because i had discharge on charger on my bike and without going into lenghty details here, the results were very enlightenting and frustrating as far as cables are concerned. huge differences and i mean up to 400%.

by the way i also don't use the stock (orange flat) cable because it's not flexible enough for my liking but i can tell you it's by far the best cable i ever had and in the process of solving my discharge on charger problem on the bike i purchased douzens of cables and at least one douzen of chargers. so this is a proven fact if people would know ( believe ) everyone would buy a amperemeter just not to be cheated by vendors like that.

EDIT: BTW the up to 400% differences was among so called "quality cables" since i was searching for the best i can get i did not go for best price (cheap) but for the mentioned, the worse the results were. ok there was one criteria which had to met which reduced the choice a bit, i need a 90 degree angle on micro usb side so that i can still open the "glove compartment on top of my gastank were remotes for garage and realestate entry doors are stored next to other little goodies :) otherwise i could not open it to more than a slit.
[ONE Original Android Development] Aavion:
for the cable-thing an amperemeter makes sense.. but to observe charging behaviour, a simple battery monitor app helps a lot :)

Gesendet von meinem 1+ One
[ONE Original Android Development] P1nGu1n_:
Tested the battery the charging speed myself. With the screen off it charges at a rate of 1900 mA on average, with the screen on it charges at 900 mA on average. I used both the original charger and usb-cable.
[ONE Original Android Development] magnamentis:
with the term: "helps a lot" you stay on the save side haha.... but the reason why i had to buy an amperemeter after months of trying was that

none of the apps was accurate and real time enough. you only know that if you compare app-readings with amperemeter readings unfortunately so

you can believe me or not, no proof possible without making a video and that's too much work for me sorry :)

but at least the apps can tell you a good average of % per hour readings which already give good hint, but if you wanna test 10 cables you don't wanna ( not even able ) to maintain the same consumption conditions up for several hours just to get a mid-long-term reading with a certain value
[ONE Original Android Development] DjDiabolik:
Yeah.... i know but whit an amperemeter / voltmeter i can obtain the exactly value......... but i don't need the exact value in this case :)

We can see an approximate value by config app right ?? Whit beta 8 the ac value has been setted to 1500 by default... now at 0 the 1+1 using the stock value and i can really know the value reported by config app and after that i can choose the better value for my needs... i explain:

Before to flash this fantastic kernel i ever using the stock kernel... whit this my 1+1 needs about 3 hours for pass from 10% to 100%........ whit 2.0 beta 8 whit value fixed at 1500mA the same charging as been completed in about 2hours.

Whit this beta 9 i can check by app the approximative value using by stock kernel.. and after that i can choose my self the best value i thinks..... example:

If I notice that the value used is around 900mA i can set the value on config app at 1200mA for obtain a little more speed charging....... but i'm not sure if the 900mA it's the value used by 1+1 because i have a different usb cable (payed 5€ at one shopping center... same length but it's not flat like the original) but now i can approximately find it like this newest feature.....

I'm not sure you can understand this my theory.... i know my it's a bad english :)
[ONE Original Android Development] magnamentis:
sure

no problem, i get your point which is a valid way to see things, you know as a swiss guy with 3/4 german roots i'm more on the accuracy side LOL which is often good and sometimes a P.I.T.A. depends :) however this time i needed it because i drive around 30'000km per year on that bike and music over BT, navy over bluetooth and display always on, often 2 navis google for the bigger picture and sygic for turn by turn and POIs. so there was no way but to find out which combo would charge and not discharge on the ride.
[ONE Original Android Development] Aavion:
sorry, had posted in the wrong thread initially :D

[MENTION=947981]Lord Boeffla[/MENTION]

Gesendet von meinem 1+ One
[ONE Original Android Development] Aavion:
nvm! beta9 works flawlessly with 44S :)

Gesendet von meinem 1+ One
[ONE Original Android Development] andip71:
You are using SuperSu, right?

SuperSu is fooling me again, while it works with internal CM superuser.

I know how to fix it, but can take a while.

I will inform you once you can re-download the builds again.

So far, fall back to previous version please.

Andi
[ONE Original Android Development] infatality:
[KERNEL] [Bacon] [CM13/COS12.1/CM12s/CM12.x/CM11s/CM11] Boeffla-Kernel (09-03...

Yup.. Supersu by chainfire 2.65. Thanks.. Will be waiting.. Take your time.

Edit.. Beta 8 works fine..
[ONE Original Android Development] andip71:
You can re-download beta9 now and try again :)

Andi
[ONE Original Android Development] infatality:
It's works now.. Thanks! [emoji1]
[ONE Original Android Development] chenrp:
"Change: Actual charge current is displayed again in Boeffla-Config, however prefixed with a tilde (~) sign to indicate it is very inaccurate"

COOL!

very nice of you to ask the users what they want.

very cool developer!
[ONE Original Android Development] Sander9847:
What is the recommended setting for System Tweaks in the miscellaneous tab in the app?

I'm using CM13 and have it set to off as of now.

Also any options recommended here?

Thanks in advance,
[ONE Original Android Development] andip71:
Keep system tweaks set to off. Typically the OPO does not need these tweaks, they were however very helpful for the s3.

Andi
[ONE Original Android Development] Sander9847:
Thank you!
[ONE Original Android Development] Rembi:
I need help.

My OPO acts on the CM 13, on the 5.0 kernel did not boot (OnePlus logo and android), again at 5.1 runs, but after rebooting the device is a mistake com.phone then the phone abruptly slows.

I went to the stock CM 12.1.

Any ideas?
[ONE Original Android Development] andip71:
Fresh install of latest cm13 nightly +latest Boeffla beta for cm13 should work just fine.

I run that combo here.

Thanks

Andi
[ONE Original Android Development] Rembi:
I have such a set.

At CM12S Boeffla 3.1 does not boot.
[ONE Original Android Development] andip71:
Mh. Too long ago, can't even remember cm12s anymore.

Why do you use such an old rom?

But I remember all was running fine that days...

So something must be wrong with your specific setup. It was a stable kernel release because it did not make any problems.

Andi
[ONE Original Android Development] Rembi:
I flash COS12.1 + 4.1 boeffla

So far, everything works. But it is strange that CM13 is not working.

Thanks
[ONE Original Android Development] 9282gkg:
Which version of boeffla kernel will work with resurrection rom?
[ONE Original Android Development] EvilPat:
Beta 9 working good Ressurrection Remix
[ONE Original Android Development] andip71:
Hi all,

maintenance update to the CM13 kernel:

Version 5.1-beta10

09.03.2016

Update: Updated with latest official CM kernel commits as of 13.03.16, 11am CET

Update: Ramdisk of official CM13.0 build of 13.03.16

Change: Cleanup of ramdisk after removing legacy files

Enjoy

Andi
[ONE Original Android Development] 9282gkg:
What values is stable for USB charge current? And for AC charge current?
[ONE Original Android Development] andip71:
1800 / 500.

But just leave them on zero to have stock behaviour.

Andi
[ONE Original Android Development] Tiz92:
I got bootloop with RR Rom of today with last boeffla kernel (beta10).
[ONE Original Android Development] andip71:
RR seems not compatible anymore for a few days already.

Andi
[ONE Original Android Development] Tiz92:
Really sad. You have by far the best custom kernel. Used it a long time back since 2012 with the S3.
[ONE Original Android Development] EvilPat:
For me beta 10 works without problems RR today. Sorry for OT
[ONE Original Android Development] Sander9847:
Boeffla beta 10 does indeed work with the 03/13 build of RR.

You just need to reboot once in between flashing the rom and kernel.
[ONE Original Android Development] andip71:
People say it works still. See above.

And even if not, blame the RR team for becoming incomparable, not the kernel that follows official cm [emoji1]

Andi
[ONE Original Android Development] Tiz92:
I blame nobody. I respect the hard work of all developers. Yes I to flash it after the Rom installation and it "works".

However when opening the boeffla app it gives me the following message: "Es scheint als würde der mpdecision Prozess nicht laufen usw... (du weißt sicher was ich meine)" Can you maybe explain me what this means. (and yes im half german).
[ONE Original Android Development] andip71:
This simply means something (a different kernel?) has removed the mpdecision executable under /system/bin.

Or renamed it...

It means the hotplugging process is broken and this needs to be fixed.

However, no idea what rr does to mpdecision as I don't use it m

So we have to rely on others t to guide you here, sorry.

Andi
[ONE Original Android Development] Tiz92:
I have flashed Andys kernel before boeffla. Maybe this caused problems. Btw al is working "normally".
[ONE Original Android Development] andip71:
What is al?

It only seems all is working, but it is not. Your cpus will not plug anymore.

This Andy-kernel for sure renamed mpdecision to something else (how I hate when kernels mess up a system completely in areas that are not their business).

You need to find the mpdecision in system/bin, rename it back and restart.

Andi
[ONE Original Android Development] Tiz92:
I did it and it worked. Very good. Thanks again my Lord :D Btw if we are already discussing I want to ask you which governor do you reccomand for fluid animations and power safing (no gaming).
[ONE Original Android Development] andip71:
I usually stick to interactive, as I need an as stable as possible phone for my daily.

Thanks

Andi
[ONE Original Android Development] infatality:
[MENTION=947981]Lord Boeffla[/MENTION] Have you considered using any kernel methods for your kernel? So you don't need to keep having updating ramdisk everytime and also it can works with any roms.

http://xdaforums.com/showthread.php?t=2670512
[ONE Original Android Development] Renosh:
Simple search would have gotten you the answer.

Also explained here

http://xdaforums.com/showpost.php?p=59565354&postcount=3723
[ONE Original Android Development] andip71:
Thanks to Renosh, you have the answer already.

Considered sometimes, but I do not like it and rather prefer to update ramdisk when required (but have much better control on what the users have finally, which eases my support).

Andi
[ONE Original Android Development] infatality:
Yup.. Totally understood what you meant.. As I did not know even when using any kernel method will still have issues.. As when I still have my Nexus 5.. Many Dev over there uses any kernel for compatibility with different roms..
[ONE Original Android Development] andip71:
It has pros and cons.

But I dislike the cons much more than the pros.

I do not like when I cannot fully control (and therefore assume) what is used as part of the kernel on the users device.

Andi
[ONE Original Android Development] suaverc118:
I found it at the top... What do I rename it? I'm also using the latest RR rom
[ONE Original Android Development] andip71:
You don't have to rename it.

It must be called mpdecision to be loaded correctly, so you are good (assuming you do not get a warning message displayed when you start Boeffla-Config).

Andi
[ONE Original Android Development] atulclassic:
[MENTION=947981]Lord Boeffla[/MENTION] which of your CM13 kernel would work with the latest CM13 snapshot build since it's based on r17 codebase and nightlies are running on r22

Just asking
[ONE Original Android Development] andip71:
I think latest beta kernel should still work. At least I would give it a try.

I cannot track back when the nightlies were still on r17 base. If you know which nightly it was, then I can look up the best matching kernel for you.

Andi
[ONE Original Android Development] atulclassic:
deleted
[ONE Original Android Development] suaverc118:
So I'm sorry about the post. I reflashed ROM and had to flash kernel separate for it to work. Before I didn't have that mpdecision file and did after I dirty flashed ROM. Some of these ROMs are finicky. You can't flash the kernel with them. I had to flash ROM, reboot, flash XP, reboot and flash kernel and reboot. I couldn't flash kernel before XP or it wouldn't boot. Not your fault, just staring my observatuons
[ONE Original Android Development] andip71:
No problem.

Just to explain:

mpdecision is the stock method for cpu core hot plugging. I am using this method, according to my "close-to-stock" objective.

Other kernel devs implement custom hotplugging logic (intelliplug, etc, whatever) and in order to have mpdecision not conflicting with their code, they just rename it when the kernel boots up or even during running the kernel installer zip (no clue where, never was interested to find that out).

That is why these kernels then leave the mpdecision binary renamed somewhere and when you flash my kernel, the app detects that something is not working and gives you the warning.

I do not really like the other kernel devs do it that way, there are much smarter ways of doing that (they could just modify the init scripts to not even launch mpdecision, change permissions, kill the process). But his is not my call in the end.

Just to give some background information.

Cheers

Andi