yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] andip71:
beta9

Hi folks,

before I disappear for a few days into holidays (yes, I will be only back end of next week, but I will read here as good as possible, just will not write that much and cannot do any development work) I want to give you a quick last beta.

2.0-beta9 for both cm11s and cm11 kernel variants.

Version 2.0-beta9

06.11.2014

Charge logic extended to allow stock charging logic to apply (to have stock charge logic, put the charge rate sliders to 0 !!!)

Note

: During first start of this kernel version, charge logic will be set to stock charge logic (by putting both sliders to 0) one time only. This is for safety reasons for users that are not confident with fix charge rates.

Note

: During first start of this kernel version, readahead buffers will be set to the new default of 1024 one time only (of course you can change this again later as you like)

Some internal cleanup and optimisations for kernel start script

Only cm11 Boeffla-Kernel: Latest CM patches included

Only cm11 Boeffla-Kernel: Ramdisk updated to version of nightly 05.11.2014

Just to explain a bit more on the charge logic changes:

If you you put the slider for AC to zero, it does not mean the device does not load anymore, but it loads applying the normal stock charge logic when an AC charger is connected.

And same goes for USB charge rate.

So if you set both sliders to 0, you will always have stock charge logic applied - whatever you connect it to.

In Boeffla-Config overview page, you will also see some more information now:

You see, as before, the charge current that is currently flowing.

Then in brackets (and this is new), you see what the charge logic requested (this is either what you configured with the sliders, or in case you set to 0 and stock logic applies, you see what stock logic thinks it should load with).

And if you see a "SL" behind the brackets, it confirms stock logic is being used for you. If not, your fixed configured rate will be used.

Last not least... I would like to remind you again, for the cm11 kernel you need at least a rom installed that is not older than 01.11.2014 !!!

If your rom is older, your wifi will not work and you have to fallback to beta7 for the time being.

Hope it is pretty much clear.

Also, as I know some people have concerns about loading their batteries too aggressively, I decided to do a hard reset of your charge settings to 0 (stock logic) one time after you installed the kernel.

This is to save people that misconfigured the settings in any way.

If you want to load faster than stock, just put your selected charge currents into Boeffla-Config again, then it will be sticky for the futuer.

Also please note, I will set also one-time your readahead buffer to 1024 (which is the new default since the previous kernel version). Also this is only done once after this new kernel is installed and you can change it afterwards.

As always - enjoy.

Ah, forgot: Very last information... beta9 is not tested as good as previous betas. And as I will be on holidays, I cannot react if I implemented new bugs. So in that case, just fall back to beta8 again please.

Cheers

Andi
[ONE Original Android Development] pinoymutt:
EDIT -- Lord Boeffla literally posted the beta as I was typing my question.

Yahoo! :D
[ONE Original Android Development] andip71:
I just pushed the kernel out... if you set both sliders to zero in Boeffla-Config, you will always use Stock charge logic and rates :)

Cheers

Andi
[ONE Original Android Development] pinoymutt:
Thanks! I just edited my above question, as I was typing it I think the same time your were writing your beta update post! :good:

Enjoy your well deserved holiday!
[ONE Original Android Development] magnamentis:
issue with colors

[MENTION=947981]Lord Boeffla[/MENTION]

display after kernel update extremely dark

cm11 _ nightly 05.10.2014 _ kernel version beta9

tried several reboots and re-installes, same result _ tried to change rom settings, same result

difference already visible on boot logo

will wait for 06th nightly perhaps there is an incompatible commit for nightlies earlier than 06th ( latest commits )

no idea, will evaluate further, just wanted to let you know in case it's something that can be solved quickly :)

nice holiday however, i'll post further findings of course
[ONE Original Android Development] andip71:
Well absolutely zero changed for display driver etc. So it is really a coincidende I would say.

I have the same bright display here as before (but ok, I am still on nightly 02.11.14 for some reasons).

Andi
[ONE Original Android Development] magnamentis:
tried 04th and 05th no diff. then went back to beta8 all is fine.

flashing cm11 6th nightly now which just finished building and keep you informed as mentioned in PM just for those following here.

thanks for taking care
[ONE Original Android Development] gianton:
Flashed beta9 on CM11s 38R, all good so far. I'll use the stock charging rate (sliders set at 0).

Thanks and have fun on your vacation.
[ONE Original Android Development] magnamentis:
flashed cm11 6th nightly _ same result, redownloaded the kernel, flashed everything again _ same result, flashed back to beta8 all is well

so i'll stay on beta8 and wait if someone else has this, cm11s users might not have it so we have to wait for more cm11 6th nightly users to report whether things are ok or not. if i'm the only one i'll gone deactivate xposed and other mods to see which part of my config is the culprit.

i'll keep you posted about my findings as usual :)

EDIT: [MENTION=947981]Lord Boeffla[/MENTION] _ deactivated Xposed entirely _ same result _ dark colors _ high contrast
[ONE Original Android Development] pinoymutt:
Flashed beta 9 on CM11s and no issues with colors here, so it may be something specifically in recent CM11 nightlies...
[ONE Original Android Development] andip71:
No clue, honestly.

Would like to see comments from other cm11 kernel users, if they have strange colours as well.

For me, all is fine.

And another test user reported also everything to be fine.

Andi
[ONE Original Android Development] magnamentis:
yup

thanks for reporting, we suspected that already, after i have uninstalled xposed i'm a bit lost for now but keep digging. the lord did not have to problem and as far as i know he has 2 ONEs for each kernel version. for now i'll wait for others to report whether they're fine or not but it's already weird since i can flash any rom version after 03rd nightly and with beta8 all works as usual and with beta9 i get the same result.

again, albeit i mentioned it already, already the boot image is darker so it starts immediately on the beginning of the boot process. let's see, no problem however, albeit i was curious in the battery thingy hehe....

what i'm gonna do now is download the 2nd nightly since the lord told me that he has that nightly installed. stay tuned :)
[ONE Original Android Development] andip71:
Another of my test users flashed beta9 cm11 now, his response:

Flashed. Colors are fine

•

1 Min.

Andi
[ONE Original Android Development] magnamentis:
ok

just flashed cm11 2nd of november and same result, so i'll see if i have more ideas what could be the reason, for now i tried 3 nightlies with 2 different kernels with and without xposed installed and got the identical problem with beta9.

however if you don't have that and someone else also not it must be on my side, even though i ran out of ideas what it could be for now, which

does not matter, sooner or later it will get solved, be it with or without having found the culprit.

for now i see it as settled as far as the public exchange is concerned. behind scenes i will evaluate a bit more and should someone else come up with the same issue we can have a look at it again. for now i consider this as a problem with my config, something in my userspace.

thanks for assistance and your time
[ONE Original Android Development] f100cleveland:
I flashed beta 9 over a local build of Slim that was sync'd late yesterday afternoon and all the colors are normal like they were on beta 8.

Very odd that you're getting those results. Did you try a clean install?
[ONE Original Android Development] magnamentis:
not yet

not yet, still testing what might be the culprit, after all i have a running config, cm11 6th nightly with beta8 runs great, so i try to go from there. only thing i changed today was the supersu 2.19 installed, will try to go back to 2.16 as well. i'll keep you all current when i find something worth to mention. thanks for reporting and confirm more or less that i have to search here.

clean install will be last resort but i at least want to try without and learn something in the process

enjoy furhter
[ONE Original Android Development] vikrant82:
A reboot on beta 8. Though on sm build and "undervolt light". Not bothered, but I'll leave it here for just in case anyone is interested.

[ 544.039749] switch_fast_chg: switch_fast_chg end,allow_fast_chg:0
[ 550.038234] is_alow_fast_chg: is_alow_fast_chg auth:1,temp:370,cap:99,chg_type:5,low_temp_full:0
[ 550.038286] switch_fast_chg: switch_fast_chg end,allow_fast_chg:0
[ 550.638329] CPU0 hotplug is not supported
[ 550.638378] _cpu_down: attempt to take down CPU 0 failed
[ 550.649159] faux123: user voltage table modified!
[ 550.649285] faux123: user voltage table modified!
[ 550.649414] faux123: user voltage table modified!
[ 550.649578] faux123: user voltage table modified!
[COLOR="Red"][ 551.774480] CPU0 hotplug is not supported[/COLOR]
[ 551.774563] _cpu_down: attempt to take down CPU 0 failed
[ 551.785082] dyn_fsync_active_store: dynamic fsync enabled
[ 551.813785] ext4_msg: 10 callbacks suppressed
[ 551.813832] EXT4-fs (mmcblk0p16): re-mounted. Opts: commit=20
[ 551.820534] EXT4-fs (mmcblk0p28): re-mounted. Opts: commit=20
[ONE Original Android Development] vikrant82:
Also possibly another suggestion for future builds. If someone has an overclock, would the max frequency be the overclocked frequency during boot ? Especially if you are on ART and you wipe the cache/dalvik, the device boils (on an OC of 2572 here) during boot. Could we limit it to stock ?
[ONE Original Android Development] andip71:
Again - root has NOTHING to do with the kernel!

And when you still use (meanwhile buggy) SuperSu instead of well-working internal superuser, I cannot help further.

Yes, it happens because of the removal of the GPU step. I already regret to have done it.

But I will work on an app update for it.

Andi
[ONE Original Android Development] cybersonic2k:
Ok i know , but what can i do?

I use COS not cm. How can i root, without supersu?

I used always supersu and it was ok.

Gesendet von meinem A0001 mit Tapatalk
[ONE Original Android Development] andip71:
Here:

https://forums.oneplus.net/threads/...egrated-superuser.297089/page-6#post-14402201

Read the OP as well for instructions.

In fact, all you need to do is:

- remove supersu completely

- flash this zip in recovery

- flash boeffla kernel afterwards again in recovery

- enable root access in developer options, done

People that need supersu still for some reasons, I recommend to not use any other version than 2.52. All newer versions patch the ramdisk images, which is gone after every next kernel flash (I do not like that approach at all).

Andi
[ONE Original Android Development] cybersonic2k:
Thx, i try this

Gesendet von meinem A0001 mit Tapatalk
[ONE Original Android Development] mahesh ritz:
Will this work on exodus 5.1.1

Will this kernel work on exodus 5.1.1???
[ONE Original Android Development] Aavion:
you may try the cm12.1 version (CM, NOT COS!) and report how it works...

but boeffla kernel is only build for official roms (oos, cos) and cyanogenmod, so there's neither a guarantee nor any support for other roms ;)

Gesendet von meinem A0001 mit Tapatalk
[ONE Original Android Development] mahesh ritz:
cool... Fashed it ..working fine thanx dude :D
[ONE Original Android Development] andip71:
Announcement:

https://twitter.com/andip71/status/699906353595314180

Andi
[ONE Original Android Development] Orphee:
Great job, i would like to buy it to replace my one
[ONE Original Android Development] andip71:
Are you really sure?

I would not consider it, it has lower specs than the OnePlus One!!!

Slower CPU, no 5 GHz wifi, no touch button lights...

Andi
[ONE Original Android Development] Aavion:
No, you wouldn't :D

And an unfinished OS with no real features that could beat cyanogen (subjective feeling)...

I'd wait for the next "flagship killer" if you want to replace your one with a new OnePlus device ;) They seem to have learned from the past and I guess, it will be a really dev-friendly device again with decent specs while not being overbloated with useless oem-addons and not being too overpowered to get a good battery life... But that's only a guessing by myself, based upon all the feedback in forums and amas and all their past efforts to serve it :)

Gesendet von meinem A0001 mit Tapatalk
[ONE Original Android Development] andip71:
I mean, to be fair:

Three things are really nice about the OPX:

- nice AMOLED display

- smaller device = perfect for ladies

- double sim or ext. sd card

But thats it, yes.

Andi
[ONE Original Android Development] Orphee:
I know the Oneplus X isn't better than the Oneplus One.

But I really like the size of the Oneplus X, I like the quality it seems to have.

I'm little afraid about the AMOLED screen, I had it on my Motorola Razr HD, and the screen "burned-in"... maybe because it was quite often on the same screen (GPS app) behind the car window

quite hot with the sun shining on it...

I'm not using the Oneplus One for the same stuff, I kept the Motorola dedicated for the car, but sometimes when i'm in another car, it happens... And I know the Oneplus One screen won't burn-in... It might happen on the Oneplus X...

I'm not using the Oneplus One as a power user... I mean it is quite customized, rooted, Xposed framework (I know Lord Boeffla, I know... :p) with Xprivacy (I couldn't have a phone without this module). But the CPU Max freq is minored to 1958Mhz with boeffla app, I'm using it for surfing (Firefox), forums (Tapatalk), some Twitch live streams, little bit of Youtube, mails, GPS nav sometimes...

So I don't think I will see a really lack of performance with the Oneplus X, maybe i'm wrong...

The other thing I miss is the NFC, but since CM12.1 taglost hack (apk modified and/or Xposed module) does not work anymore.

And without this feature, I don't use NFC anymore on my Oneplus One... So I guess I can live without it...

And last but not least, there is an unofficial CM12.1 ROM that seems quite stable when I read the XDA thread...

Edit : I never used any 5Ghz wifi...

And yes, the lack of button lights is really bad... :/
[ONE Original Android Development] Pablo.x:
There are some things that are not working properly on CM for OPX yet... Like camera for example.

Even OxygenOS isn't stable 100% yet, but anyway it's a new phone and the scene it's improving every day.

Enviado desde mi A0001 mediante Tapatalk
[ONE Original Android Development] 99piotrek:
Yeah you know my wife replaced her iPhone 5s with OPX and she's really happy with that.

After I Flashed CM13 few days ago she loves that phone to death.

Yes camera doesn't work but she is a photographer so hates to use phone camera anyway.

Overall OPX is great for the girls but I wouldn't replace my OPO for that! I wouldn't even replace it by OPT.

Can't wait for your kernel on OPX
[ONE Original Android Development] Orphee:
I'm not talking about CM13, but CM12.1 : http://xdaforums.com/oneplus-x/orig-development/rom-cyanogenmod-12-1-oneplus-x-t3254072

Camera seems to work on it, no ?
[ONE Original Android Development] Pablo.x:
Yep, but cm12.1 has network drops as OPO had (at least I had on 12.1 but not on cm13)

Enviado desde mi A0001 mediante Tapatalk
[ONE Original Android Development] Stroky:
Just wanted to say that the phone crashes when i tried to switch to zzmoove governor.
[ONE Original Android Development] Aavion:
I also have problems with zzmoove (phone freezing, random reboots...)... Just use interactive or yankactive until this problems are fixed :)

Gesendet von meinem A0001 mit Tapatalk
[ONE Original Android Development] andip71:
Kernel version?

Rom version?

Configuration?

Mods?

Guys, I do not know how many time I have to repeat this.

Your postings are really not usefuly without that basic information.

I will in short place the message in all threads and everywhere, that no support anymore without some basic information provided.

[MENTION=3279788]ZaneZam[/MENTION]: As you use zzmoove as your daily driver on your OPO - anything known?

Andi
[ONE Original Android Development] Stroky:
Sorry Andi,

CM 13 Nightly 03.02.16

Latest Kernel

No mods like xposed or something like that.

Tried it right now with the Opo from my colleague with the same settings, like CM 13 and other settings stock and it also freezes and then shut down while switching to zzmoove.

Running now Interactive, everything is good.
[ONE Original Android Development] andip71:
You have a very old nightly. So in general, the last kernel is not ideal for you.

I am currently on OOS, will switch to CM13 later today and test myself against latest nightly. But I am sure if there is something really wrong, Zane would have already given notice.

Andi
[ONE Original Android Development] 15H44N:
I'm so sorry as this is irrelevant to the discussion...

How can I use cm inbuilt root instead of SuperSU in resurrection remix M builds?

Someone please help me..
[ONE Original Android Development] Stroky:
My colleague is on the nightly from the 14.02 and he also noticed the reboot, but its not a big deal, the first time ever i notice a "problem" with your Kernel....:)
[ONE Original Android Development] andip71:
The thing is just.. zzmoove has not changed for months now. So it makes completely no sense.

It reboots as soon as you switch, right?

Because I cannot confirm that, just did it myself on latest nightly, look yourself here:

https://www.dropbox.com/s/wqvpqp85ovjod70/SCR_20160217_164006.mp4?dl=0

Andi
[ONE Original Android Development] Stroky:
really strange, who knows what that causes.

Yeah exactly..its freezing when i switch the governor.

But i will stay at your close to stock logic with interactive ;)

thanks for your effort
[ONE Original Android Development] ZaneZam:
and guys it would be enormous helpful to use the build-in boeffla app function: "crate debug info file" (in action menue last entry), at least if u want to help

a in that case veeery "blind" dev :) there is a saying around here on xda: no log = crash didn't happen, but well i believe u guys because im a believer *g*

no xposed = very good as u get some plus points from lord boeffla and as we have one disturbing factor lesser ;)

and i'm running zzmoove since i can't remember how long actually *g* on almost all nightlies without problems, even with my builds and even with the most problematic one of them the Uber 6.0.0 build.

now comes the "BUT" i never change the governor and that might be the point. so will check that when i got my dev device in hand again ;) but one question: "zzmoove native hotplug" enabled or disabled?
[ONE Original Android Development] Crazy_Oni:
Im using zzmove with zzmove battery plus as my profile with xposed and this since a few months now and i use evety outcoming nightly. If i play a game i switch to Standard settings profule and after that back to my profile. I got no reboots or anything like that. It's not kernel related i think.

Gesendet von meinem A0001 mit Tapatalk
[ONE Original Android Development] EvilPat:
I have never had problems with zzmove. I use U600, Zzmove optimal tripnroid, zzmove native hotplug and Xposed. Great Job for ZaneZam and Lord Boeffla!!
[ONE Original Android Development] cloudx720:
I will still be rocking my opo in the year 2020, heck even 2030 ?
[ONE Original Android Development] Aavion:
my strange random reboots i reported some weeks ago were also gone after switching to interactive, what i'm using until now...

these were both with native and default hotplugging... using both your linaro builds and andis builds...

using l531 solved some problems i had before with l521 and it's now as solid as andis builds, so i only got reboots when using zzmoove :/

you've seen my pretty useless kmsg-screenies back then... would a debug info file give you more information? if so, i'd test again and feed you with all information i can gather and would offer myself for testing purposes, since my device seems to be affected by this issues, other than yours :) i really liked zzmoove all the time since the good old gs3 days :D so i'd be happy to help ^^

cos12.1.1

Gesendet von meinem A0001 mit Tapatalk
[ONE Original Android Development] andip71:
Yes, indeed it gives much more information.

A debug info file contains much more than just the logs, also the configuration, kernel boot logs, boeffla-config logs etc etc.

So this gives the full 360 degree picture a dev needs.

Andi
[ONE Original Android Development] ZaneZam:
thank u Aavion I would appreciate that as I really can't reproduce it. playing around since 15 min on latest and previous nightly with uber 600 build. ;)

yeah I remember we were not able to get much info out of your logs back then but anyways... maybe we have luck... I mean there must be something related to zzmoove as u can cure it by using another gov. but as said for me all is OK so I rely on the logs from "problematic systems"

Gesendet von meinem A0001 mit Tapatalk
[ONE Original Android Development] Aavion:
Then I'm testing zzmoove again until my phone crashes again :D May takes 2-3 days until the first reboot, even when those freezes occur more often...

Actual configuration:

COS12.1.1 (edit: fresh flashed k1 factory image, in case that there won't be any problems, that's the "fix" :D )

Boeffla Kernel 4.2b6 (Andi's build)

fiops shed

Zzmoove - Moderate

Zzmoove native default hotplug

no uv, no oc, input boost lowered to 960, no system mods beside integrated superuser. (only headphone gain +5, led blink speed 6 and lmk values adjusted - 8, 16, 32, 64, 128, 256).

won't change anything (beside kernel updates, if any).

hope i can be helpful :D

Gesendet von meinem A0001 mit Tapatalk
[ONE Original Android Development] Fenvarien:
I'm using zzmove with the relax profile and tripndroid scheduler since weeks and never had a freeze or reboot caused by this combination. But I had problems with a custom busybox installation (stericson pro), after removing this my OPO went back to a normal and stable behavior.
[ONE Original Android Development] Aavion:
[MENTION=947981]Lord Boeffla[/MENTION] Andi? I just noticed, that min gpu freq default is set to 200mhz in 4.2b6... i remember it being set to 27mhz, did you change that? and for what reason? just wondering if it's safe to change it back to 27 :D

Gesendet von meinem A0001 mit Tapatalk
[ONE Original Android Development] kalapapa:
Usually the GPU goes to 27mhz when it's idle so it probably will do that even if it's set to 200 as minimum
[ONE Original Android Development] Fenvarien:
We need to check and if necessary reapply the GPU settings after the Lord fixed/removed a GPU frequency step some days ago. My OPO used 200 MHz quite a lot if it was not slumbering but the 27 MHz step was ignored until I adjusted my settings.
[ONE Original Android Development] andip71:
That is why the app showed you an information message after the flash...

Have you ignored it? [emoji3]

It was due to the removal of the useless oc gpu step.

Andi
[ONE Original Android Development] andip71:
Absolutely correct.

So one at least read the message [emoji12]

Andi
[ONE Original Android Development] Aavion:
I've read it, but as I never changed a thing in gpu settings, and as I did a clean flash (factory image) yesterday for the zzmoove tests, I was going to stick with your preset defaults :) and that default raised from 27 to 200 ^^

I may misunderstood the message somehow, but I thougt that you were talking about custom changes that could be messed up after an update, but I did a clean flash :D

Gesendet von meinem A0001 mit Tapatalk