yashsingh1/xdaforums huggingface dataset:
[OnePlus X Original Android Development] Mojar7070:
Hello all,

I'm receiving a error 7 while flashing the stable release of this kernel.

Currently running OOS 2.2.0-x with twrp 3.0.0-1.

Mods: camera hal by sultanxda, SuperSU 2.65 and that's all.

Would like some help please and thank you.

Edit: I downloaded the wrong kernel. Sorry for the interruption. Flashed correct and OS booting fine. Thanks.
[OnePlus X Original Android Development] variant0:
I am sure this question was posted many times, but i couldn't find the answer.

I do not need to root my device to flash this kernel right? After i flash the kernel the device becomes rooted ?

I have TWRP but did not root my device. Can i flash directly ?

Thanks
[OnePlus X Original Android Development] andip71:
No, the kernel does not automatically root your phone.

There are people that do not like that, so I did not implement that.

To root, you still need to flash Chainfires Supersu in recovery yourself.

Andi
[OnePlus X Original Android Development] variant0:
Thank you for your fast answer , so i believe with this kernel flash, all OTA will still be installed, all i have to do is reflash this kernel after correct?

Thank you for your time
[OnePlus X Original Android Development] andip71:
You should receive OTAs with the kernel installed itself, I guess.

I am not entirely sure as I never put OTAs in but always flash it in recovery myself already before the OTA is even available for my region here.

Andi
[OnePlus X Original Android Development] CertifiedBlyndGuy:
I think we're ready for the next frequency step! Everything has been really stable on my end.
[OnePlus X Original Android Development] variant0:
Well, i just flashed the latest boeffla kernel and everything went great, BUT...

I than flashed the latest supersu, wiped cache and dalvik, with not errors, but the device is not rooted. I can also not load de boeffla config because the root is not working. Any idea what is wrong?

Maybe i should have installed supersu before boeffla kernel ?
[OnePlus X Original Android Development] andip71:
It does not matter what sequence you take.

Especially as the kernel has nothing to do with root.

Maybe you need to use an older supersu version. I use inbuilt superuser of cm, so don't have the Supersu trouble.

Andi
[OnePlus X Original Android Development] ihs0201:
i've had both on my opx and think that this one is better, as it allows overclocking and has many more cpu governers. some things 'common' people may like more in Boeffla:

Can change led brightness

Configurable sounds (speaker and headphones)

but if your a 'common' person then i wouldn't understand why you would want a kernel. Bluspark allows fast usb charging (1 amp from a pc usb port), but other than that it offers no additional feautures that a common person would use. anyway, hope this helps, probably didnt though ;)
[OnePlus X Original Android Development] Falcon36:
Hi my lord. I know you from s3. I am very happy to see you here. I knew that you had an one plus but not the oneplus x. I am very happy. [emoji2]

One plus X
[OnePlus X Original Android Development] andip71:
Only once cm comes to the opx officially.

I have no time anymore to support unofficial stuff.

Twrp issue, yes.

But you solved it.

What is unclear on the website?

You basically just need to find your device and load the kernel.

But I am open to good suggestions as long as they do not cause more work for me.

Bear in mind the large set of devices and kernel variants I offer... Not so easy.

You can also load with 1a from usb port with my kernel.

You can even configure much much more... Charge rates very granular separate for usb and wall charger.

Andi
[OnePlus X Original Android Development] hellcat50:
[MENTION=947981]Lord Boeffla[/MENTION]

I don't have the phone, but my brother does. I flashed the kernel and the app says that mpdecision is missing in system/bin (or lib idk). Anyways I found a file called "mpdecision-bak" and I copied it and renamed to "mpdecision". Is there anything wrong with that?
[OnePlus X Original Android Development] Alastal:
Wow lord boeffla by him self!

Your kernel is one of my best

I was using it with my old dead S3 :D

Waiting for official CM and boeffla kernel support

Best regards
[OnePlus X Original Android Development] andip71:
Seems there was another kernel installed before that in a "rude" way removed mpdecision. Not nice practice, but well...

What you did is totally correct.

Rename it, restart the phone, and the message should be gone forever.

Andi
[OnePlus X Original Android Development] hellcat50:
Yes, he used blue spark kernel before.

Now you just have to build a kernel for the Galaxy Tab A[emoji14] No, just kidding, this would be too good to become true.
[OnePlus X Original Android Development] ihs0201:
its most likely just me, i can be easily overwhelmed by a list :o Your website is absolutely fine, it's just me.

By the way, great work on the kernel :good::good::good:, the phone is really snappy and your kernel allowed me to get 65k in antutu somehow.
[OnePlus X Original Android Development] Kiras_PL:
Can i just flash it over blu_spark or should i flash stock kernel first ?
[OnePlus X Original Android Development] Mojar7070:
[MENTION=947981]Lord Boeffla[/MENTION]

Hello, something interesting happened will flashing this kernel.

I did a clean flash of the latest OTA 2.2.0 using official TWRP 3.0.0.1, then I went ahead and flashed SuperSU and the kernel. Booted fine went through setup, good.

Finally, I went to see the kernel version on the "about phone" screen. Kernel was correct however, the OS version went back to 2.1.3-x. Again this is CLEAN flash of the 2.2.0.

Afterwards, I did another clean flash of the OTA without flashing the kernel and then OS version was correct again.

Any ideas as to what is going on??
[OnePlus X Original Android Development] Morphine1:
That's right, it is showing the previous oxygen os version after flashing the kernel.

However, it is just a mere visual effect, it is infact oxygen 2.2.

Tried to find a line in the build prop about the oxygen version but no line was shown. Other than that, just a minor thing.

Antutu is giving a great score by the way.
[OnePlus X Original Android Development] psychem:
whats the score on oos and h2os?
[OnePlus X Original Android Development] Thunderbottom:
63K on OOS for me :D
[OnePlus X Original Android Development] saurabh40629:
holly molly... is that with default setting or overclocking?
[OnePlus X Original Android Development] Thunderbottom:
On Default I get around 60-61.5k, with overclocking its 63k.

Regards.
[OnePlus X Original Android Development] saurabh40629:
Now I am tempted to go back to OOS.
[OnePlus X Original Android Development] andip71:
Sorry, never Samsung again. This is my strong believe.

So the Galaxy Tab kernel will not become true.

You can flash over.

But it seems, bluespark renames mpdecision. So you have to rename it back, see posts above.

Confirmed, cosmetical bug in beta1. Will be solved by beta2 in... well... a few minutes :)

Andi
[OnePlus X Original Android Development] andip71:
I might release one or two more OC steps over the time, when this first one turns out to run stable.

There is still room I guess :D

Andi
[OnePlus X Original Android Development] andip71:
New beta

Good morning (German time),

thanks for reporting the incorrect versinon information display.

I really started on the kernel long ago when we still had OOS 2.1.3, so I forgot to correct that finally.

Version

4.0-beta2

19.02.2016

First official build

Note: This kernel only runs on Oxygen OS 2.2.0 for the OnePlus X - nothing else !!!

Note: You need at least version 2.2.29 of Boeffla-Config V2 to allow all functionalities to be available

Fix: Fixed issue with incorrect version number display in rom settings

Tipp: You can easily download and flash in Boeffla-Config app. Tap on "Action", then select load&flash/store and then the rest should be clear.

Enjoy

Andi
[OnePlus X Original Android Development] Kiras_PL:
I don't know why but I don't have any of this files "mpdecision" and "mpdecision-bak" in both directories. Not in system/etc nor in system/lib. Any ideas ? Btw I'm still on blu_spark kernel. I just want to be sure that everything's going to be ok.

BTW is it possible to add this file by default in kernel package ? Could You do it so [MENTION=947981]Lord Boeffla[/MENTION] ?
[OnePlus X Original Android Development] Francis Tony:
Can i install this on my OPX with CM13?
[OnePlus X Original Android Development] Portgas D. Ace:
Only if you read post #1 carefully, where it says "this kernel is only for OxygenOS".
[OnePlus X Original Android Development] Francis Tony:
I did read the whole thing , i just wanted to confirm .
[OnePlus X Original Android Development] ZackoFF96:
and if you read just one or two pages back, you can read that boeffla kernel for cm13 is on alpha and will be available once cm13 for onyx goes official :D

peace :D
[OnePlus X Original Android Development] Francis Tony:
Thanks for the info man, any idea when its going official ?
[OnePlus X Original Android Development] variant0:
[MENTION=947981]Lord Boeffla[/MENTION] , should any problem or special procedure be expected flashing this kernel on an encrypted device?

Thanks
[OnePlus X Original Android Development] andip71:
Could cause problems.

I cannot say for sure, never tried to use encryption.

In the past on other devices it led to issues.

Maybe someone else knows more.

Andi
[OnePlus X Original Android Development] variant0:
If anyone is running the kernel on an encrypted system without any problems let me know.
[OnePlus X Original Android Development] andip71:
I answered your email already.

Android is not really made for wired connections, so it is a lot of fiddling required.

And only adapters that use the asix driver will work.

Andi
[OnePlus X Original Android Development] matwaking:
And please dont quote the whole op
[OnePlus X Original Android Development] variant0:
[MENTION=947981]Lord Boeffla[/MENTION]

So i have been doing some tests with the kernel and encryption:

1- Flashing the kernel on an encrypted device, before or after encryption, breaks root, permanently..

2- Maybe because of that the defaults are not loaded correctly.

Its requires a special procedure to mantain root with supersu on an encrypted device. I believe it has to do with the fact that your kernel comes loaded with supersu binaries...

described here : http://xdaforums.com/note-4-tmobile...tSd7OU3zvjXIDCyXg&sig2=QqJIbUNvupVJnERW2w4K_w

Doing that procedure on the default kernel, works flawlessy, with your kernel, doesn't work, so root breaks.
[OnePlus X Original Android Development] andip71:
My kernel does not have any su binaries in anymore for the past few versions.

But yes, I said it is likely to break. So you just confirmed what I suspected.

But I am sorry, I will not try to do anything here.

Someone told me looong ago it would break the whole concept of my kernel loading the default settings already during kernel start and not via app.

I have no intention to change that as I do not use encryption and have no plans to use it.

Andi
[OnePlus X Original Android Development] variant0:
I understand that, but as you know your kernel better than anyone, do you have any clue what could cause it? sou i could investigate further myself?
[OnePlus X Original Android Development] andip71:
As I tried to explain, the kernel loads the configuration from a file in /data. But at that time the file I still encrypted.

So it would require to load kernel settings differently, not by kernel but by another process (ie the app).

And I decided 2 years ago I did not like the concept of app loading. So will not step back.

So imho it is not fixable without high effort.

But I also have not spent more time to investigate as I have no encryption use case.

Feel free to do some deep dive and let us know ☺

Sorry

Andi
[OnePlus X Original Android Development] chinmai560621:
[MENTION=947981]Lord Boeffla[/MENTION] I can't wait even a second for the release of the kernel for cm marshmallow.... When will it release? If it'll get late, how can I avail a copy of the kernel before the release ?(without being a tester)
[OnePlus X Original Android Development] andip71:
It will come out for public when cm is officially out with nightlies.

Andi
[OnePlus X Original Android Development] chinmai560621:
I bet that's not gonna happen..
[OnePlus X Original Android Development] andip71:
More optimism please.

It should happen, I am positive...

Andi
[OnePlus X Original Android Development] chinmai560621:
At the moment, I have holidays..summer holidays. The bluspark kernel does good on liquidity but gaming sucks heavily. UKM and synapse is not also compatible with Onyx. The only solution is your kernel. Pls release at least a beta. I can't. And I'm desperate to game

---------- Post added at 05:30 PM ---------- Previous post was at 05:26 PM ----------

I beg you to release please!!!!!
[OnePlus X Original Android Development] Firefly1337:
At least inform yourself before posting such nonsense.

http://review.cyanogenmod.org/#/c/133582/

That will be merged right after this one: http://review.cyanogenmod.org/#/c/132573/

And after that it's official.
[OnePlus X Original Android Development] taaeem:
And that seems very much done, I think functionality is all working and only thing is icon and settings place, but also that seems kinda finished.
[OnePlus X Original Android Development] Calvin2394:
Sorry for OT

Why does the commit "hudson: Cook nightlies for onyx" say Cannot Merge?
[OnePlus X Original Android Development] CertifiedBlyndGuy:
Because other changes are required before the commit can be considered. Some admins were making a big deal about merging the notification slider commits a while ago as only a few devices actually can utilise it. Looks like it just needs to be merged and night lies will begin
[OnePlus X Original Android Development] brausebirne:
New update of OOS - 2.2.1

It works with the current version of this kernel.
[OnePlus X Original Android Development] kaixuan_1995:
everything works well？ thanks
[OnePlus X Original Android Development] Tiongkia:
Works on 2.2.1.
[OnePlus X Original Android Development] andip71:
Just to let you know, no updated kernel sources available till now, so I cannot yet put an updated kernel out.

Fortunately this seems not to be required as you confirmed ☺

Andi
[OnePlus X Original Android Development] Tiongkia:
Hi boss

Not sure if your ' about' still shows 2.2.0-X?

I flashed full 2.2.0-X rom and flashed 2.2.1 ota. Boot in phone and ' about' shows 2.2.1.

Then i flashed your great Kernel, it shows 2.2.0-X. See attachment.

In oneplus forum, some suggested that it's Kernel. I am not sure.

Thanks in advance.
[OnePlus X Original Android Development] taaeem:
That was already a thing with 2.2.0 and 2.2.0-X because Oxygen OS reads somehow the rom version from the kernel and since the kernel wasn't updated yet...
[OnePlus X Original Android Development] andip71:
This is a consistent issue across all OOS roms - they read the rom version from the kernel ramdisk. I will never understand why, as other roms do it differently. Maybe I should ask OnePlus team one day about it.

But at least the rom version display could be fixed by me already without having the source codes released. All I would need is a full zip of the rom, is that already available, does someone know?

Thanks

Andi
[OnePlus X Original Android Development] MarocoKong:
Hi there,

some guys posted links on this thread, startiung around page 5 or 6 - but I guess its the OTA update only, not the full 2.2.1 ROM, but maybe it helps nonetheless :)

https://forums.oneplus.net/threads/oxygenos-2-2-1-rollout-is-starting-on-oneplus-x.440359/

I saw several links, one that seems to be working is https://drive.google.com/file/d/0B1jwnoWhDHA5bHRpNS1QZWlYUTg/view, leading to a file named:

OnePlusOxygen_14_OTA_009-010_patch_201604021001_54d6bba8f7d84502.zip

Cheers
[OnePlus X Original Android Development] brausebirne:
Full ROM: https://forums.oneplus.net/threads/download-full-2-2-1-rom.440406

I didn't test it. I used the OTA method.
[OnePlus X Original Android Development] Tiongkia:
I used full rom 2.2.0-X earlier so this doesn't happen to me. Thanks for sharing.

---------- Post added at 06:58 PM ---------- Previous post was at 06:58 PM ----------

Ok understand and thanks much.
[OnePlus X Original Android Development] andip71:
Okies, upgraded to 2.2.1 now and smoke testing the new kernel for it (4.1-beta1).

I think you can expect a release still today...

Andi
[OnePlus X Original Android Development] Tiongkia:
Tks much.
[OnePlus X Original Android Development] MarocoKong:
Dear Lord you are awesome! :)

Thank you very much
[OnePlus X Original Android Development] andip71:
Hi all,

here the promised kernel for OOS 2.2.1, which was recently released.

Version

4.1-beta1

06.04.2016

Note: This kernel only runs on Oxygen OS 2.2.1 for the OnePlus X - nothing else !!!

Change: Ramdisk of latest OOS version 2.2.1 implemented

Change: Internal kernel busybox updated to latest version 1.24.1 (self-compiled from sources, www.busybox.net)

Fix: Security flaw CVE-2015-1805 (memory corruption in pipe) fixed

Enjoy

Andi
[OnePlus X Original Android Development] Tiongkia:
Flashed latest Kernel and works well. It shows 2.2.1 too.

Thanks lord
[OnePlus X Original Android Development] poopwetpoop:
Looks great

Hey, looks awesome. Will be installing if theres a CM13 version. Thanks !
[OnePlus X Original Android Development] andip71:
For the CM13 lovers here... some good news (I hope):

http://xdaforums.com/oneplus-x/orig-development/kernel-boeffla-kernel-5-0-alpha6-11-04-t3357139

Andi
[OnePlus X Original Android Development] ihs0201:
Hi could someone kindly share their saturation, display value and contrast value from the dislplay+led section in the boeffla configuration app. I moved the slider a while ago but forgot to take a screenshot before doing so. Thanks a lot :)
[OnePlus X Original Android Development] matwaking:
255,all three
[OnePlus X Original Android Development] taaeem:
Possible bug report with the kernel app, it always sets the SELinux mode to strict when it applies the profile, even if I added the permissive stuff in Settings and kernel load, it just stays on moderate until the profile gets applied and after that it's on strict...

And because of that Viper4Android won't work..
[OnePlus X Original Android Development] jonrodz:
You need to go to settings > kernel startup actions and enable this...
[OnePlus X Original Android Development] CertifiedBlyndGuy:
I know Lord Boeffla said no, but would you be interested in making a CAF version of this kernel? I may try at it myself while I'm working on SwellKP and NH, but you obviously have a lot more experience
[OnePlus X Original Android Development] andip71:
Nope, no caf kernel.

No time to build stuff I have no usage for.

Andi
[OnePlus X Original Android Development] andip71:
There is even a popup message telling that...

Oh dear, what else sh I do... [emoji2]
[OnePlus X Original Android Development] taaeem:
As j said I have that already enabled, sorry if that wasn't clear and yes I read the pop up
[OnePlus X Original Android Development] andip71:
Ok, when it is still not behaving as it should, please go into Boeffla-Config, action menu, last point is "create debug info file".

Do that and send me the file to support@boeffla-kernel.de

Then I can analyze.

Thanks

Andi
[OnePlus X Original Android Development] taaeem:
Oh I found the issue the kernel setting was working but there was a ROM option hidden in some menu that disables permissive SELinux and I hope it works now.
[OnePlus X Original Android Development] ihs0201:
Thanks so much :D
[OnePlus X Original Android Development] migueldbr:
[MENTION=947981]Lord Boeffla[/MENTION] the 27mhz idle gpu frequency seems to be the cause of scrolling stutters (micro stutters), is that why you have it disabled and set the min gpu @ 200mhz? A lot of kernel developers add the 27mhz step to the idle frequency and usually its not possible to remove it (with kernel adiutor it only lets me choose the min gpu freq to 200mhz, but when it idles it always goes back to 27mhz). But with your kernel and app it lets me choose the minimum gpu freq even when idle, which is awesome. I never understood why i had better scrolling performance on oxygen rom (because it uses min gpu freq @ 200mhz instead of 27mhz) because once i flashed your kernel i would edit right away, making the minimum gpu freq @ 27mhz. With min gpu freq @ 200mhz it solves my micro stutters when scrolling (im assuming the stutters happen because the gpu idles too soon, going to idle before even ending the scroll movement). Is this correct?

I also experienced this on my previous device (LG G2 on cm13) because it would also idle @ 27mhz, and did not experience it on stock rom (which goes to idle at higher gpu freq), so thats the only explanation that makes sense to me..
[OnePlus X Original Android Development] andip71:
More or less this is the reason why I default to 200 instead of 27 MHz.

Scrolling stutters a bit more with 27, and also GPU performance for other tasks is too low for some.

And I was tired of answering the same question over and over again why scrolling is less smooth with my kernel. So I put it on the stock 200 MHz. Everyone can then actively down it to 27, with knowing what he does.

Andi
[OnePlus X Original Android Development] migueldbr:
Sorry, didnt know you had already answered this question before, thanks for the explanation. It is much better @ 200mhz to be honest. Earlier I flashed ashwins cm13 and noticed it idled @ 200 too, that's probably why it is so smooth. But oxygen+boeffla kernel(@ 200mhz idle) is as smooth as cm13 imo. Thanks for the awesome kernel btw
[OnePlus X Original Android Development] SlanDev:
I had a few problems with boeffla:

- Boeffla Config app does not work. It won't change the settings, and there is no "apply" button. (MPDecision is on, app doesn't show the warning)

- Too low performance. On 2.57 GHz I got only 40k AnTuTu and 700 geekbench points. I know that Benchmarks =/= actual performance, but I think something's wrong when they are much lower than 2.3 GHz on blu.spark.

Changing voltages (using kernel adiutor since boeffla config doesn't work, as I mentioned) didn't make the benchmarks change.

Installation:

Dirty-flashed over blu.spark on Oxygen 2.2.1.

What did I do wrong?
[OnePlus X Original Android Development] andip71:
I do not know what is wrong, but there is something completely wrong!!!

When Boeffla-Config cannot apply settings, then something is

severely

messed up.

BTW - There is no apply button, as I do not like that philosophy in general.

As you said, you had blu spark before. No clue what all gets changed by blu spark, but recently another user was reporting similar stuff and he did a clean install as next step. Since then all is working fine for him.

I can only recommend to go for a clean install when you had another custom kernel etc installed before.

Andi
[OnePlus X Original Android Development] SlanDev:
Ok, then I'll use Titanium Backup for my apps and do a complete reinstall of OOS, and flash Boeffla over the original kernel.

If Boeflla Config has no apply button, does that mean it instantly applied changes or when I leave the app?
[OnePlus X Original Android Development] andip71:
Instantly.

Only exception: Voltage changes, here you will get an apply button in order to prevent you are doing changes by accident.

Andi