yashsingh1/xdaforums huggingface dataset:
[OnePlus X Original Android Development] andip71:
No. With my close to stock approach this is not possible.

I am using mpdecision, which does thermal throttling. And mpdecision is closed source.

Sorry

Andi
[OnePlus X Original Android Development] ChavitoArg:
Sir Boeffla thanks for this awesome kernel, could you share your personal settings for daily usage? Thanks in advance.

Enviado desde mi ONE E1005 mediante Tapatalk
[OnePlus X Original Android Development] CertifiedBlyndGuy:
It isn't there but over clocked this device doesn't get too hot. You also have the option of undervolting

---------- Post added at 04:43 PM ---------- Previous post was at 04:36 PM ----------

https://forums.oneplus.net/threads/boeffla-configuration-make-oxygen-fly.430693/

I made a tutorial for beta 3 and it's very much the same. The only things that are different is that you can raise the clock speed up higher to just 2.6ghz and you shouldn't enable multi core power saving. I get locked cores with it enabled.

Edit: updated my OP for beta 5
[OnePlus X Original Android Development] andip71:
I am not using my opx as daily driver, sorry.

To all: tomorrow I will release a maintenance update for the kernel to cater for the latest oos update (only cosmetical for the version information display).

Andi
[OnePlus X Original Android Development] fatino:
Well it doesn't because probably it gets thermal throttled which I'd like to avoid or at least adjust it to my likings like I can with Xperia L using intelithermal.

I'll make a thread about it in another subforum I guess. I don't want to go offtopic :)
[OnePlus X Original Android Development] andip71:
This is only possible with a custom thermal (and hot plugging) implementation - which is a complete no-go as per my objectives.

Sorry, maybe a different kernel can give you what you want.

Andi
[OnePlus X Original Android Development] CertifiedBlyndGuy:
Nope. No throttling whatsoever. The 801 is a relatively cool chip. Without my undervolt it throttles at around 65 when stress testing, but with it my temps never exceed the mid 50s. No throttling :)

This isn't the 810 we're taking about :)
[OnePlus X Original Android Development] ZackoFF96:
same here, no throttling :) also never went hot after a lot of undervolting :)

the thing i like about the opx is that the chip is located on the upper end of the device, so you can't feel the heat when holding it in one hand, nice design choice i guess? :D
[OnePlus X Original Android Development] andip71:
Hi all,

the promised maintenance update is released.

Version

4.0-beta6

29.02.2016

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

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

Change: Ramdisk of latest OOS version 2.2.0-x implemented (fixes the rom version information)

Change: Maximum charge rate for ac charger reduced to 1600 mA

(I got an USB current meter now and could confirm, the MSM8974Pro-AA SoC puts a hard limitiation above 1600 mA in)

Change: Do not display actual current anymore in Boeffla-Config overview screen

(my USB current meter showed this values were far off the real values, so I rather remove it before it is misleading)

Enjoy

Andi
[OnePlus X Original Android Development] Adam3Sixty:
Quick question for u:

I updated the wife's OPX yesterday, from what I gather, to 2.2.0-X, however, in the "About Phone" section it still only says 2.2.0.

When I go to update it says there are no new updates so I'm guessing it is on it -X version.

Does that sound right to u??
[OnePlus X Original Android Development] andip71:
Yes, this is why I released this new kernel version.

Stupidly, the OOS rom reads the version information from the kernel and not really the rom.

So when you now install this kernel version, you will see correctly 2.2.0-x in the version information.

Don't ask me why OOS is doing that in such a stupid way please :)

Andi
[OnePlus X Original Android Development] Adam3Sixty:
Awesome :)

Thanx for the info mate. So glad I got ur kernel on her device too now, not changing much on it, but just having it on there as it is will make such a difference for her.

However, just looked and can't seem to see the update in the app yet??
[OnePlus X Original Android Development] andip71:
I can see it. Maybe still cached somewhere. Try again in a few minutes or so...

Andi
[OnePlus X Original Android Development] Lazy Rich:
Thank you very much, this setting is absolutely flying. Never seen the OPX that fast and smooth.
[OnePlus X Original Android Development] hellcat50:
what changed in OOS 2.2.0-X? Because I flashed this kernel on 2.2.0 and it works perfect, no issues.
[OnePlus X Original Android Development] andip71:
Apparently only camera related stuff, according to oneplus change log.

So, no surprise the kernel works fine on the 2.2.0 rom too.

Andi
[OnePlus X Original Android Development] skodaslx:
I updated from beta5 to beta6. Now it shows 2.2.0-X in about phone. But I didn't flashed the rom update.

Gesendet von meinem ONE E1003 mit Tapatalk
[OnePlus X Original Android Development] Aashay:
Being a senior member you should know that you've to read the posts before posting. As lord already said, opx reads the version from the kernel and not the rom. And since the updated version of kernel has 2.2.0-X as it's version hence it is showing 2.2.0-X even when you haven't actually updated.
[OnePlus X Original Android Development] andip71:
Of course.

I explained in detail the nonsense of oos reading the version information from the kernels ramdisk instead of the rom.

I don't know any other rom doing this, just oos...

Andi
[OnePlus X Original Android Development] sille1980:
Thanks for this awesome Kernel. Beste Grüße nach Potsdam :)
[OnePlus X Original Android Development] iPeppe89:
Thanks for your work!
[OnePlus X Original Android Development] MrPhilo:
Has anyone actually tried to flash this on cm13?
[OnePlus X Original Android Development] CertifiedBlyndGuy:
Tried with the first beta, but it just results in a bootloop. This is for Oxygen and H2OS (unnoficially) only
[OnePlus X Original Android Development] Arcanis87:
I was tempted to do the same.. but obviously isn't a wise option... lol. Can't wait for CM13 releases...
[OnePlus X Original Android Development] andip71:
I really wonder why I write change logs and OPs... I mention every time this kernel is for oos and nothing else.

Andi
[OnePlus X Original Android Development] saurabh40629:
That's the reason common sense is not that common. Even thread title makes it clear.
[OnePlus X Original Android Development] mshazrul82:
Thanx to you!!!

its cause of you after 4 month i'm not rooted OPX u make me really wanna do it

hahahahaha
[OnePlus X Original Android Development] Phaniraj_itng:
When I enabled double tap status bar to sleep from boeffla config app, the double tap sleep function in lockscreen stops working.?

I hope you understand my problem? :confused:
[OnePlus X Original Android Development] andip71:
Yes I understand.

And it shows, you were not paying attention to the change log when I introduced it.

It was clearly explained there why it cannot be avoided.

Also there is a workaround for that available, which I also explained there.

What else should I do than writing everything up in detail..?!? :confused:

http://boeffla.df-kunde.de/oneplusx/boeffla-kernel-oos/oos2xx/changelog.htm

Read change log of beta4...

Andi
[OnePlus X Original Android Development] Arcanis87:
Lord Boeffla,

Does this rom disable qualcomm anti tamper code? Some people could unlock LTE bands on their OPO, but cannot (at least try, we dont know if there is antenna support) on the OPX because the values set on QXDM/QPST reset after a reboot.

But the real question is.. can this be implementwd at a kernel level?

Thanks.
[OnePlus X Original Android Development] andip71:
First, this is a kernel and not a rom.

And I would not be aware this stuff can be done on kernel level.

LTE bands and 3g/4g communication is handled by the modem firmware.

Andi
[OnePlus X Original Android Development] hellcat50:
Is it possible we can see official CM for OPX? Look at the picture.
[OnePlus X Original Android Development] andip71:
Yes. This should just be a matter of time.

But, contrary to the op2, there should be nothing on the opx which blocks a proper cm version in future.

Andi
[OnePlus X Original Android Development] Addys123:
I got this error in twrp while flashing this kernel. Please help.
[OnePlus X Original Android Development] Addys123:
Why have u completed the installation so much. Where is the correct onyx version present? I looked every where on the site.
[OnePlus X Original Android Development] andip71:
Why are you flashing an old kernel? There is already beta6 out.

To whom was that question directed?
[OnePlus X Original Android Development] Addys123:
Sorry bro my bad. I messed it up with the version. I will flash the beta 6 now.
[OnePlus X Original Android Development] sille1980:
Hey Lord.... Is it possible to overclock up to 2.8 GHz? Best regards....:)
[OnePlus X Original Android Development] andip71:
I don't know, have never tried it.

But I am not too optimistic. Even one the oneplus one, which has a higher quality Soc, these high frequencies were not stable for everyone anymore.

We would need to try that out in order to see how much buffer is left on the AA SoC.

But for now this is not in my top priorities.

Andi
[OnePlus X Original Android Development] Naman Bhalla:
Hola Andi !! How is everything going? :)

My OPX finally reached my friend's home. I will get it on Tuesday.... So will start working on my profile for it ;)

BTW Andi, can you please cherry pick this commit :-

https://github.com/Validus-Kernel/a...mmit/2ae49a190835d89762cbd5f7d0925cbf62e5e743

Will add kexec (MultiROM) support.

Thanks. :)
[OnePlus X Original Android Development] andip71:
Good stuff!

I will look at it for sure, even though I do not have a personal use case for it.

But I alway said: If someone ports kexec, I will put it in.

Thanks for pointing me to the commit.

Andi
[OnePlus X Original Android Development] awildsloth:
If that doesn't work either try to update TWRP since I was having the same error with 2.8.7.0. As soon as I updated to 3.0.0-1 I was able to flash the kernel and flash the OOS again :)

---------- Post added at 11:29 AM ---------- Previous post was at 11:24 AM ----------

Hey Lord Boeffla, how's the development going? When can we expect an improved beta 7 or the almost-flawless beta 6? You're awesome, keep up!
[OnePlus X Original Android Development] andip71:
Well, development is going good. But I am having not much time these days. So I was not working on the OPX OOS kernel.

No update expected very soon therefore :)

But as you said, beta6 works almost perfect (ok, I found a minor bug, but nothing critical)... so there is also no hurry.

Andi
[OnePlus X Original Android Development] andip71:
Hehehe

And to show what I was working on since yesterday, and to make some people already getting "nervous"...

Look at the screenshots :D

Andi
[OnePlus X Original Android Development] jonrodz:
Cant wait to play with this! :'D
[OnePlus X Original Android Development] Arcanis87:
Can't wait for a release of your CM13 kernel! I moved back to OOS 2.2.0 just to be able to use your kernel again...
[OnePlus X Original Android Development] andip71:
Lol, nice message.

Do not expect me to release it before CM13 gets official. I just did all the prep work already, so I am there on day one when it gets officially out.

Andi
[OnePlus X Original Android Development] awildsloth:
Same here dude, unofficial CM 12.1 had too many malfunctions for my taste, came back to OOS to be able to use LB's awesome kernel :D
[OnePlus X Original Android Development] SlanDev:
How's the battery life compared to blu spark? (Without overclocking ofcourse)
[OnePlus X Original Android Development] jonrodz:
I dont think this is a good place to ask that...

Besides, everyone gets different battery life, because it depends on the user usage.

So nobody can really answer that but yourself. You need to test them out. :)
[OnePlus X Original Android Development] kaixuan_1995:
bug report.screen get yellow when change to muliti task,but very few,in fact i just found once.do'nt know whether you have already knew.and thanks for your work.waiting for stable version.
[OnePlus X Original Android Development] CertifiedBlyndGuy:
Is Nethunter support a possibility? I think it relies on only a few commits. Im running it right now but I miss the features of Boeffla

For those curious Ill post a tutorial on how to install it. If your anxious give Phraya a search on AFH
[OnePlus X Original Android Development] andip71:
Never saw that here, so nothing I can look at.

Nope, too many changes away from stock = against my objectives.

Plus, sorry I am selfish, but you know that anyways: I have no personal use case for it.

Sorry

Andi
[OnePlus X Original Android Development] saurabh40629:
As said by OP, he tries to keep Kernel close to stock. So if you don't modify any kernel setting, battery life is identical to stock oos kernel. There are lots of features to play with the kernel . You need to install boeffla-config app for this. You may want to check default presets if you are scared to try things or simply don't know what you are doing. So you can get better battery life based on that.

The special thing about bluespark is bluespark governor and fiops io scheduler which in my opinion is optimized for balanced profile with more focus on battery.

By no means, I intend to compare these kernels because both are great. This has been my observation and I may be wrong. :fingers-crossed:
[OnePlus X Original Android Development] CertifiedBlyndGuy:
Back on the NetHunter thing. It looks really basic so when Nightlies hit I can do it myself:

https://github.com/offensive-security/kali-nethunter/wiki/Modifying-the-Kernel
[OnePlus X Original Android Development] andip71:
Good. Would appreciate that as I am not planning to integrate it into the official kernel.

You can always use my kernel as basis for it...

Thanks

Andi
[OnePlus X Original Android Development] CertifiedBlyndGuy:
I was looking at your source for the OPO and I noticed that the frequency table went all the way up to 2880mhz. I know it isn't a good idea to mesh code from other devices, but could it safely be added to the X? A regression could always be made if frequencies turn out to be unstable.

I did manage to build a NetHunter compatible kernel and I just need to take the zImage and ramdisk to produce a bootimg. I was just curious if something like this could be added in such a way.
[OnePlus X Original Android Development] andip71:
When you looked also at my x repo, you will see I added the full range up to 2.8 already, just I don't yet allow that full range so far. Step by step we will find out where the end for the AA revision of the soc is [emoji2]

For the kernel you need the zImage, the ramdisk and the dtb.

Andi
[OnePlus X Original Android Development] Naman Bhalla:
Thanks a lot Andi for your Hard work for the OnePlus X. I finally received my OPX today. Already started working on my separate profiles for all 3 kinds of usage.

BTW Boeffla Kernel Profiles Thread is UP :-

http://xdaforums.com/showthread.php?t=3330187

Rain of profiles starting soon :D
[OnePlus X Original Android Development] nasif69:
Which color?
[OnePlus X Original Android Development] andip71:
Result of recent poll about displaying actual charge current in Boeffla-Config.

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

In short - feature will be back in next updates, however slightly modified to indicate the information is potentially very inaccurate.

Andi
[OnePlus X Original Android Development] taaeem:
Okay the kernel is really good and I get really good battery life, but for some reason it seems like if I leave my phone at the charger overnight that the battery percentage hangs on 100% for a while (1-2 hours) and then drops into the 80s.

Never had these issues with Stock kernel or blu_spark.

I'm running OOS 2.2.0-X with Xposed, greenify, underclocked, undervolted.
[OnePlus X Original Android Development] andip71:
Not an "issue" really. It will sort itself after 2-3 charge cycles. This is sometimes the case after flashing something (and destroying the battery calibration).

At least I do not have that here anymore (had it once, as said).

Also - there is zero changed that could impact battery capacity control in my kernel.

And just by the way - xposed + undervolted = you are out of my support, see OP.

Andi
[OnePlus X Original Android Development] andip71:
Update

Hi all,

new kernel update for you:

Version

4.0-beta7

07.03.2016

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

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

Change: double tap 2 wake without haptic feedback does properly use proximity sensor now (avoid unwanted wake ups)

Change: swipe 2 wake gestures are now following the haptic feedback setting in Boeffla-Config as well

Change: Actual charge current is displayed again in Boeffla-Config, however prefixed with a tilde (~) sign to indicate it is very inaccurate

Fix: xbox module not loading correctly is fixed

New: Kexec hard boot implemented (untested as I have no use for it, maybe it works, maybe not)

Update: Internal kernel superuser updated to su 2.65

Enjoy

Andi
[OnePlus X Original Android Development] hellcat50:
This kernel works on 2.2.0 too (already said that)

2.2.0 and 2.2.0-x
[OnePlus X Original Android Development] taaeem:
Mmh is it governor and governor settings depended how much I can undervolt? On zzmove battery extreme yank I can go like - 100 without any impact on performance or hot reboots. On blu_spark and blu_active at - 100 it just reboots and with - 50 it's unstable. So is it kernel or governor depended?
[OnePlus X Original Android Development] ZaneZam:
it is uv dependent! the moment u change the stock voltages things r getting to be a lottery game. so everything is possible. mostly "everthing" means "nothing good" ;)

do u know that u r a lucky one regarding zzmoove? as normally it's vice versa u can't do much uv with zzmoove (due to it's fast freq switching) and more with other govs.

but this "less and more" is anyway and always in the "red zone". in short uv = expect everything ;)
[OnePlus X Original Android Development] MarocoKong:
Don't make yourself smaller than you are :D

From what I can say after only 3 days of testing this seems to be a very very great governor! Here to with zzmoove game-profile plus native zzmoove-hotplug and -75 mV superstable and and fluid phone and almost obscenely battery friendly too. Got to -75 with Blu_Spark as well though - but it ate more battery...

So huge thanks to you for the governor and The Lord for putting it into this wonderfull Kernel!

Cheers
[OnePlus X Original Android Development] CertifiedBlyndGuy:
I think it needs to be pointed out that an undervolt won't have anything to do with other kernel settings but rather the limitation of hardware and how far that hardware is being pushed. Zzmoove seems to be better about switching frequencies than most other governors which is why you and [MENTION=5738857]taaeem[/MENTION] are hitting walls much earlier. If a UV is stable with one kernel and unstable with another it's not the kernel, it's your undervolt. For example, on Blu Spark I was able to maintain a 925mv undervolt for the maximum frequency for a while however Blue Active seemed to stick with lower frequencies most of the time and spike up only when needed which was a rarity. However due to Zzmoove and it's great scaling it hits those higher frequencies for much longer. Now that same frequency required 975mv to operate safely. Because of this, I now know what settings truly work. When resting frequencies, try to test them individually with the performance governor. Lock your maximum clockspeed to the frequency on question and your good to go.
[OnePlus X Original Android Development] MarocoKong:
Thanks for your reply. Just to clarify, I got -75 mv undervolt stable in both boeffla and blu_spark. Used Kernel Adiutor for blu_spark which allows 5 mV steps instead of 25 mV in Boeffla Config so there I could get to - 85 stable (Actually -95 gave some seldom forced restarts when waking up from deep sleep and directly doing something demanding, so I gave it a little buffer ;) ).

I didn't even try -100 on boeffla. With zzmoove game and hotplug it's so battery friendly anyways I didn't see the need to push to the absolute limit.

Makes sense though, that it's not too much Kernel related apart from "how far the hardware is pushed" by governors. :)

Anyways, wasn't in any way intended as a complaint rather to praise you two for the great work!

Cheers
[OnePlus X Original Android Development] taaeem:
Thanks for all the responses, can somebody tell me what the stock voltages without undervolting are? I need to check something :)
[OnePlus X Original Android Development] andip71:
No, there are no single stock voltages, as this is dependent on your specific SoC quality.

Simplest way is: In boeffla config select the "no undervolting" pattern, then you get the stock values back and you can see them.

Andi
[OnePlus X Original Android Development] Naman Bhalla:
Ok. So some talks regarding undervolting were going on... So I thing I should share my experience with it on OPX too. While working for my profile, I was finding the best possible undervolting combo on OPX... To my surprise, I was able to achieve voltage of even 600mv (-250mv) for Frequencies upto 768 or so (Not using OPX as I type). After that the stable Frequency for the next was 627mv and it went till 1011mv (Only some 20mv undervolt) for the highest Frequency . This is the maximum possible undervolting on an OPX. You can't ever go beyond it...

Now the thing is how it can be used effectively. In the first impressions using Perfmon, I found that the kernel with stock settings touches 4 Frequencies in its cycle (mainly). These are the lowest, the highest, 7xx and 14xx. So till 14xx part, it works perfectly. When it jumps from that to the highest (I tried 19xx as highest), a reboot happens for sure. So, in case anyone is working on a heavy undervolting profile, just to make stability, tune your profile in such a way such that it touches atleast 8 Frequencies in its cycle (if you are taking 300 to 25xx).Then you will achieve a great stability with very awesome battery life too.
[OnePlus X Original Android Development] CertifiedBlyndGuy:
Every chip is binned differently. For instance mind won't do below 660mv however the maximum frequency is only using 1035mv. Your undervolts may not work with others devices.

[MENTION=947981]Lord Boeffla[/MENTION] When using a schedular such as deadline or ZEN for external storage, internal storage switches over to ROW. I have no idea why. I've tried both fiops and SIO for internal but it's the same story. I'm sure that there is a simple explanation for this. It's probably a stupid thing to bring up in the first place :)

---------- Post added at 01:02 AM ---------- Previous post was at 12:47 AM ----------

Investigated the issue further and it's with every governer. No matter what internal storage defaults to ROW...
[OnePlus X Original Android Development] Lazy Rich:
Do I have a super chip? I've set - 100mV on all and it runs totally stable, tried tons of apps and games. Max frequency runs with only 970mV, min with 725, maybe I can go a bit deeper with that.

I really love this chipset :)
[OnePlus X Original Android Development] andip71:
Hi,

no, there is definitely no simple explanation for this. It should not happen.

I am running on noop for both int and ext memory. And it sticks.

So next questions are:

- when does internal switch to row? after a reboot, or after some time running etc?

- are you sure you have not allowed scheduler overwrite in Boeffla-Config settings?

- anyone else seeing schedulers not sticking? (which should never happen as I lock them down in Boeffla-Config so nobody else can change them)

Andi