yashsingh1/xdaforums huggingface dataset:
[OnePlus X Original Android Development] pompe90:
Perhaps it was accidentally released or they are testing the Ota system before M(not likely) or they want all users to be on 2.2.1-x so upgrade to OOS 3 will install without any issues.

But yeah, just like you said it's really weird to push this ota [emoji14] not gonna install it anyway.

Skickat från min ONE E1003 via Tapatalk
[OnePlus X Original Android Development] W!ld:
I too got it in india
[OnePlus X Original Android Development] Kéno40:
Changelog is the same?

Helen talked about a fix update soon...
[OnePlus X Original Android Development] crian:
The X update fixes only a issue with the German Telekom.

So don't know why they pushed it outside of Germany.
[OnePlus X Original Android Development] Kéno40:
So as everybody as the same before a bigger upgrade.
[OnePlus X Original Android Development] motherninja:
Yeah, I'm in Indonesia and today I also received the notification about the OTA update to 2.2.1-X and I skipped it. If they are about to release a major OOS update to MM, I will flash the full package, though.
[OnePlus X Original Android Development] Stottlemeyer TDi:
Yes i'm in Italy and today i also received the notification about the OTA update to 2.2.1-X...
[OnePlus X Original Android Development] ckret:
probably this
[OnePlus X Original Android Development] eng.stk:
Thanks guys, seems like most of us are getting it then.

Case closed :good:

I'm getting some PM asking me about OP3 support, I'll post here so I don't need to reply to all of them:

Yes, I'm getting the OP3 :highfive:
[OnePlus X Original Android Development] Sytis:
The only thing that kept me using my Nexus 5 with a broken Speaker, crack in the screen and some dead pixels was your great Kernel. I planned on buying the OP3 but wasn't 100% sure yet.

But if Blu_Spark will be available on the OP3 I'll happily buy it ;)
[OnePlus X Original Android Development] eng.stk:
Wicked :cool:
[OnePlus X Original Android Development] Part.0:
so does it mean that you probably no longer support (or let say being less) for OPX (OOS 5.1.1) anymore?

well i know sometimes ppl get excited with new toys and forget the old ones. *hope you don't.
[OnePlus X Original Android Development] vinz_uk80:
Hi Falcon,

I have the exact same wake lock on my OPX, ProximityWakeLock, detected by BetterBattery Stats.

I am also running OOS 2.2.1, with the Blue spark kernel, with an old version, the 123 version.

I already noticed that when the screen rotates from portrait to landscape, this is when it triggers the wake lock, thus prevents the phone to go to deep sleep mode.

I can see this by installing CPUZ, and going to the sensors tab. If there is a value in Proximity sensor, there won't be a wake lock, but if you tilt the phone to landscape, and back to portrait, I notice on my phone that the value disappears.

To make it reappear, I just put my finger on the proximity sensor (on the right of the phone speaker) and the value pops up, and there won't be wake locks.

Sometimes, over night, even in airplane mode, the phone can't go to deep sleep, this it loses something like 10% overnight, instead of 1 to 2% overnight, without this wake lock.

I don't know what is the problem with my phone, that creates this wake lock, but I'd like to find it out.

Appart from this small bug, everything is great, especially this great kernel, thanks a lot eng.stk for your hard work.

Hope that I don't pollute your thread.
[OnePlus X Original Android Development] eng.stk:
prox wakelock probably is because ambient display and dt2w prox wakecheck (if you cover the sensor you can't make gestures)

I never use ambient display, but even when I did never had any sleep issues, it worked great like always.

My wife will take my OPX probably, so some kind of support may continue.

This device is almost all done to be honest, from a point on all we can do is a few small fixes and OOS updates.

My N5 was not my daily driver and I kept updating it like if it was, because the thread was so very much alive, users very supportive, etc. That counts a lot.

We'll see how it goes.
[OnePlus X Original Android Development] vinz_uk80:
Thanks for your answer eng.stk.

Indeed, I use ambiant display and dt2w on my OPX.

I tried to disable ambiant display, to see if there are any improvements.

I keep dt2w because this is very convenient, and I don't want to loose this functionality.

I also had this wake locks before installing your kernel, so absolutely not kernel related.

Strange, because I never installed any custom rom on the OPX. After root, I full wiped the phone, installed the OOS 2.2.1 full rom. so I have a clean ROM on my device.

I'm waiting a bit that Paranoid Rom gets a bit more mature, and I'll give it a try. Hopefully your great kernel can cope with PA.
[OnePlus X Original Android Development] Falcon36:
I have installed all from the beginning. Now the CPU goes to sleep better. Sometimes it goes for sleep after some minutes. But I think that now is without the problem I had. I don't want to disable the double touch and I have it enabled. The kernel is superb. I have the proximity wake lock again but the CPU now goes to sleep immediately or after a while but I don't know why it stays to 300mhz for some minutes. (I have all the apks wifi data closed)

Thanks again for the kernel eng.stk. Very good work. [emoji3]
[OnePlus X Original Android Development] :
[MENTION=3873953]eng.stk[/MENTION],

Do you plan on updating your kernel if OnePlus releases OOS3 for the X along with proper kernel sources, device trees, etc? Though it may take a while, I really think they're going to do it, and it would be a great loss not to have your kernel there :)

P.S. please don't leave us! :p
[OnePlus X Original Android Development] eng.stk:
I guess yes, unless MM only comes a year from now lol

imo, I think maybe 1 or 2 months after this OP3 frenzy, OP will release for OPX
[OnePlus X Original Android Development] Falcon36:
I had last night 10% battery drain. 300mhz all the night. I restarted the phone and it went to sleep. I don't know what to do and what was the problem. Last night i played with my phone a lot and I showed a movie with kodi. And I thought that the problem gone ?. I don't know if the problem is from kernel. Other people don't have this issue.
[OnePlus X Original Android Development] saurabh40629:
Again like oneplus x, OP3 will survive because of bluspark (and other development ). Oneplus is always good on hardware but bad on software. All talks about poor RAM and average camera makes my belief firm that software development is not their cup of tea. Though it's your decision, I would perhaps prefer next nexus over OP3 .
[OnePlus X Original Android Development] vinz_uk80:
Did you try what I explained with CPUZ, so that you can check if you have the same issue as I have.

Appart from this Proximity Wake Lock (indeed, even when it kicks in, it does not eat that much battery, as you mention, about 8-10% over night) it's great.

I tried disabling ambiant display, but no success.

So I leave with it for the moment, when I know that I won't use the OPX for a long period, I just check that my proximity sensor is not blank in CPUZ, and if not, I know that it won't keep the phone awake.
[OnePlus X Original Android Development] Falcon36:
You are right. I have the same problem man. I tried it with CPUZ. If I used my hand near the proximity sensor (not to be blank in cpuz) it goes to sleep immediately. You are right man.

I have a genuine cover. I'll try this. If i want to close my phone I'll use the cover to close it. If I close the cover the proximity will be enable and I will not have battery drain.

After a while: Yes it work. If I use the cover it goes to sleep[emoji3] .

Nobody else has this problem? It's weird.
[OnePlus X Original Android Development] vinz_uk80:
Yes, strange problem, but since now, I know how to kill this WKL, this is almost OK.

Now, we should try to figure out where it comes from, and how to fully get rid of this.

Hope that someone knowing the triggering of WKL better than me could provide help :)

Anyway, I don't know if we should open a thread for this issue, or if eng.stk allows us to stay in his topic.
[OnePlus X Original Android Development] eng.stk:
I had every single Nexus and went through every Android iteration: every single one had hw and sw annoyances.

And they ask too much money for nexus devices nowadays, so atm I'm cool with my decision.
[OnePlus X Original Android Development] saurabh40629:
Agree with you on price point, its not in mid range any more. I hope you will continue building for us. :fingers-crossed:
[OnePlus X Original Android Development] mafioso16:
Can you use Blu_spark CM version on AOSP ROMs?
[OnePlus X Original Android Development] pompe90:
Backup the phone and test, but yes ppl said its working ok.

Skickat från min ONE E1003 via Tapatalk
[OnePlus X Original Android Development] tet-bundy:
as far as i understood, it mainly depends on the ramdisk used for the roms kernel. so u can not generally tell on aosp/cm basis.. ull have to go for pope's advice;)

Gesendet von meinem ONE E1003 mit Tapatalk
[OnePlus X Original Android Development] eng.stk:
CM build is just because CM came first.

It is made to work with all non-OOS, meaning CM/AOSP based.

Maybe I'll call it custom next time.

Like the guys said, backup and try, I can't test everything out there.
[OnePlus X Original Android Development] mafioso16:
Thanks my friend, it works flawlessly, tested it on my own.

Each feature is working!
[OnePlus X Original Android Development] B0unze:
In the title it says oos/cm but in the post you say you only provider support on oos, so Will or won't this work on Official cm13?
[OnePlus X Original Android Development] mafioso16:
He only officially supports logfiles/debugging etc. for the OOS version, CM version works and almost all custom ROMs, including CM13.
[OnePlus X Original Android Development] B0unze:
Where can I find the cm Version?
[OnePlus X Original Android Development] mafioso16:
Press "download" in the first post, find the newest kernel (r158) with "CM" in the title, and flash it.

Come on man, at least try a bit for yourself.
[OnePlus X Original Android Development] B0unze:
Thanks, Sorry I didn't notice.
[OnePlus X Original Android Development] zer0se7en:
I only have my OnePlusX for almost a month and now it looks like it's going bye bye right away. ?

So no more OOS update coming?

Too bad... it's such a great and beautiful device for the price point. Especially when it has Blu_Spark kernel and Sultan's Camera HAL mod.
[OnePlus X Original Android Development] neopbm:
OnePlus will bring Marshmallow to the X. It's been said on official forum.

And maybe we will still be able to enjoy this kernel for the device.
[OnePlus X Original Android Development] tet-bundy:
seems op actually intends to sell their device

Gesendet von meinem ONE E1003 mit Tapatalk
[OnePlus X Original Android Development] neopbm:
OP here said he might give the device to his wife a few pages back. So maybe we still get kernel updates. Fingers crossed ?
[OnePlus X Original Android Development] tet-bundy:
i meant oneplus.

Gesendet von meinem ONE E1003 mit Tapatalk
[OnePlus X Original Android Development] neopbm:
Oups, sorry then!
[OnePlus X Original Android Development] Tiongkia:
Works great on sultan cm13. Thanks much
[OnePlus X Original Android Development] carlandermatias:
Is multicore power saving feature enabled by defalut with this kernel??

If so, does it really make a difference?
[OnePlus X Original Android Development] eng.stk:
Nope, doesn't really saves juice, but it will hit a bit on the performance.
[OnePlus X Original Android Development] eng.stk:
It's here!

Soon to be blu_spark'ed

View attachment 3791041
[OnePlus X Original Android Development] Kéno40:
\\Song\\

"Pleeeaaaase don't take us* home !!!" :p

//Song//

* US = OPX users :good:
[OnePlus X Original Android Development] andu86:
really good news, when i will buy my OP3 i will already have a kernel up and running :)
[OnePlus X Original Android Development] Exodusche:
Blu spark is truly magic. My new ROM would get quit warm until I remembered about my favorite kernel. Problem solved. :D
[OnePlus X Original Android Development] motherninja:
Holy moly!! That was fast!! :good:

Please don't stop making a custom kernel for OPX when OP released OOS 3 :crying:
[OnePlus X Original Android Development] eng.stk:
blu_sp★rk r160

All right crew!

New build is up. Wicked!

CM aka non-OOS custom ROMs build is also updated, this is made for Marshmallow 6.0.1 ROMs.

I decided to take CM build from beta, but same remains: using custom ROMs you're on your own ;)

You may flash this new build in CM 12.1, but you may find broken stuff (DT2W and gestures should work, tristate key you need to test it out).

Just use an old build (r98) if that's the case.

Keep in mind: I will give no active support for custom ROMs. I am only interested on debugging stuff in OOS.

Don't spam this thread with CM or other ROMs stuff like "this don't work, my app doesn't open, etc" or debugging features.

Also don't go spam and bug reporting on ROM threads if using this.

If you like my work, donations are always welcome (but not mandatory).

Don't forget to hit thanks, it's free ;)
[OnePlus X Original Android Development] neopbm:
Thanks for not giving up on OnePlus X!
[OnePlus X Original Android Development] Falcon36:
I flashed new kernel. All OK. Thanks eng.

OnePlus X
[OnePlus X Original Android Development] Tiongkia:
Thanks op. Latest r160 works great on sultan cm13
[OnePlus X Original Android Development] dingermtb:
Once again, running phenomenal on Exodus 6.0.1 with fastlane enabled?

Sent from Outside the 9 using my A.R.I.S.E. Exodus Zombiefied OnyX
[OnePlus X Original Android Development] W!ld:
3rd core is always at 2.3 GHz?
[OnePlus X Original Android Development] eng.stk:
Nope, it means you have some task hogging it.

Reboot.
[OnePlus X Original Android Development] W!ld:
Reboot solved the problem thanks
[OnePlus X Original Android Development] tet-bundy:
Just to confirm: Gestures work, tristate key works.
[OnePlus X Original Android Development] eng.stk:
Nice, good to know [emoji106]
[OnePlus X Original Android Development] andu86:
i have some battery drain with 160. reverted back to 158
[OnePlus X Original Android Development] tet-bundy:
yeah also feel like drain is higher on 160 compared to 158

Gesendet von meinem ONE E1003 mit Tapatalk
[OnePlus X Original Android Development] gllark:
Have the same impression. Same ROM, no new apps, no different using by me, but about 15-20 % less battery with 160 compared to 158 over the day. Don't believe this is coincidence. But blu_spark is already perfect, no need for upgrading for me anymore. Thanks [MENTION=3873953]eng.stk[/MENTION].
[OnePlus X Original Android Development] pdagenius:
I am trying this now too. Happen to have used v158 first of all with CM13 Official. My impression is that battery life is poorer with bku_spark so far in comparison to stock CM13.

So my query is what tweaks to the base kernel settings should I be looking at. It seems to me there are too many for just a trial and error process.
[OnePlus X Original Android Development] tet-bundy:
tweak ur gov. also i have power saving for multicore processors as aggressive... I'm actually quite satisfied with battery life.

Gesendet von meinem ONE E1003 mit Tapatalk
[OnePlus X Original Android Development] eng.stk:
Nothing has been done from r158 to r160 that would make battery life better or worse.
[OnePlus X Original Android Development] andu86:
this is weird behavior, you only changed "msm crypto updates" in 160 but the battery is draining a lot faster.

i have used my phone the same with 158 and 160 and with 160 i have higher drain in deep sleep.

I'm asking someone to confirm that the charging is slower, this was my observation with 160
[OnePlus X Original Android Development] nihilista:
Can't confirm that, battery drain overnight is the same here as before...
[OnePlus X Original Android Development] Falcon36:
Me too. No problem with new kernel.

OnePlus X
[OnePlus X Original Android Development] nasif69:
+1
[OnePlus X Original Android Development] W!ld:
with f2fs i was getting 6 hrs of SOT regularly

but with ext4 i m a getting 4 hrs of SOT.

is this ok or there is something wrong?
[OnePlus X Original Android Development] neopbm:
Also with ext4 at the moment.

Right now 4h of screen on time and 45% of battery left. So to me #160 is pretty good!
[OnePlus X Original Android Development] Anik.folia:
R u using CM13 or oxygen os?
[OnePlus X Original Android Development] neopbm:
Stock Oos
[OnePlus X Original Android Development] Tanner1294:
Just wanted to throw in something I've noticed (I know you don't debug the CM version, I'm not asking you too): I'm running TurboROM with the CM r160 and if I turn on fastlane it will never plug more than 2 cores even under heavy load. If I turn it off, it starts plugging cores normally.

Just an observation.
[OnePlus X Original Android Development] andu86:
i have flashed again r160 version, this time clearing the cache from recovery and everything works perfect now
[OnePlus X Original Android Development] ruifung:
Does adoptable storage work on CM13?

For some reason, for me it works fine, all the way up until vold tries to run e2fsck on /dev/block/dm-2.

Then it fails, with /dev/block/dm-2 is in use.

While I can't seem to find where it's in use.
[OnePlus X Original Android Development] eng.stk:
Hotplug works fine with fastlane on or off.

This isn't a CM13 ROM thread.
[OnePlus X Original Android Development] jayesh0099:
Hello Dev,

Thank you for awesome kernel for our device.

I have small issue, whenever i play "mini militia" game with you kernel, it lags.

But at the same time when i try to play this with stock kernel, i don't face any issue.

I tried changing the kernel parameters also, but no luck.

Will you please look into it and help me, because i want to use your kernel, but because of this reason i can't.

Sorry for my bad english.

Thank you.
[OnePlus X Original Android Development] phoberus:
Hallo guys :)

Do you have my a advice for extreme battery settings?

At the moment I made this changes:

max CPU: 1728MHz

fastlane: 1

input boost freq: 729600

hispeed freq: 1036800

Multicore Power Saving: Active

Minimum: 1 core

max: 3 cores

max screen off: 1 core

GPU Governor: simple_ondemand

I need it only for browsing and messaging, o lags with this settings but perhaps someone know still a optimision :)
[OnePlus X Original Android Development] nik_123:
Anyone please tell me the setting to make battery last longer. I play games occasionally and I would prefer a good SOT with recommended setting.

I get 5HR SOT on default settings
[OnePlus X Original Android Development] tet-bundy:
"the setting" simply does not exist.

u could disable touchboost as well as lower max freq and maybe also lower "highspeed" freq. u could also play with target loads. however this stuff would all require u to put some effort into it in the first place. meaning: reading>trying>reading>trying etc. mainly because it depends on usage profile.

Gesendet von meinem ONE E1003 mit Tapatalk
[OnePlus X Original Android Development] nik_123:
Well what I mean to say is I have already flashed the Kernel and I am using OOS 2.2.1-X.

On stock kernel I get around 5hr SOT with wifi + 9gag/insta/whatsapp and calling.

I want to know how much more I can get by tweaking this kernel.

I have seen people getting around 7-8 hrs SOT. How much you get ? Also share the tweaks if you know !
[OnePlus X Original Android Development] nihilista:
As tet-bundy said: you can lower max cpu frequencies to very low, lower gpu frequencies, set max online cores to 1 or 2 and you will get more sot but low performance. But you have to test whats best for you, there are no ultimate tweaks that gives you good performance and long battery same time. And its hard to compare with others, cause no one uses the phone same way with same apps like you ;) The only way to get really much battery savings is not to use the device :)
[OnePlus X Original Android Development] nik_123:
Share your settings and SOT pls.
[OnePlus X Original Android Development] nihilista:
No special settings, never tested sot time, for what? Its ok and depends on usage....
[OnePlus X Original Android Development] tet-bundy:
is eediting doze related variables generally possible with this kernel? or is it a rom related thing anyway? cause i'm having issues applying values and trying to figure out why.

regards

edit: using naptime

Gesendet von meinem ONE E1003 mit Tapatalk
[OnePlus X Original Android Development] migueldbr:
I dont see why not...you can do it in stock kernel as far as i know, and [MENTION=3873953]eng.stk[/MENTION] probably did not do anything to stop that

There is no magic formula...The way to get that kind of SOT is to use the phone continuously, almost without stopping, while using a kernel that has good battery backup (like this one) and stick to apps that are light (like whatsapp while typing, etc) along with indoor use to keep the brightness on the lower values. If you do anything more intensive then say goodbye to those 7h-8h SOT. But lets face it, probably like 99% of people dont use the phone 7h-8h straight in a day, so don't get your hopes up to get that kind of SOT. You could also try to underclock, it will help if your usage consists of more intensive apps (that use the cpu on higher loads)
[OnePlus X Original Android Development] tet-bundy:
yeah on stock it works also when i was running boeffla... however on my current setup (see signature) it doesn't. and as I'm not entirely sure, but think that doze is a kernel side (instead of rom) thing, i thought i'd first ask here...

Gesendet von meinem ONE E1003 mit Tapatalk
[OnePlus X Original Android Development] migueldbr:
Wait until he confirms that because im not sure=p
[OnePlus X Original Android Development] eng.stk:
blu_sp★rk r161

All right crew!

New build is up. Wicked!

CM aka non-OOS custom ROMs build is also updated, this is made for Marshmallow 6.0.1 ROMs.

I decided to take CM build from beta, but same remains: using custom ROMs you're on your own ;)

You may flash this new build in CM 12.1, but you may find broken stuff (DT2W and gestures should work, tristate key you need to test it out).

Just use an old build (r98) if that's the case.

Keep in mind: I will give no active support for custom ROMs. I am only interested on debugging stuff in OOS.

Don't spam this thread with CM or other ROMs stuff like "this don't work, my app doesn't open, etc" or debugging features.

Also don't go spam and bug reporting on ROM threads if using this.

If you like my work, donations are always welcome (but not mandatory).

Don't forget to hit thanks, it's free ;)
[OnePlus X Original Android Development] neopbm:
Already a new update?! Yeah! Thanks dev!
[OnePlus X Original Android Development] Tiongkia:
Thanks op. Flashed r161 on sultan cm13 and boot up with no issues
[OnePlus X Original Android Development] Exodusche:
Wow how do you do it!!. Runs cool , buttery smooth and battery life is unreal. I really feel the latest update is spot on . :D :D :D
[OnePlus X Original Android Development] andu86:
You are the man! A genius man!
[OnePlus X Original Android Development] shinodoigt:
Is there any special process to flash bluspark on Sultan ? He says that custom kernels won't boot on his ROM but I see a few people with this kernel on his ROM.
[OnePlus X Original Android Development] Tiongkia:
Latest boeffla official and unofficial kernels have issue on no baseband leading to no sim and imei. I tested. I even flashed rom again then boeffla kernel but have same issue. I tried restoring efs but same issue.

Bluspark works great. Just dirty flash bluspark kernel, flash supersu, and wipe cache and dalvik cache. Done.
[OnePlus X Original Android Development] :
Thanks for the update! In a time when OnePlus is ****ing everything up, it's good to know we have a great kernel to use with OOS 2.2.1 while custom ROMs aren't completely stable.

Keep up the good work!
[OnePlus X Original Android Development] saurabh40629:
This version is smoothest of all. Really good work. :good: