yashsingh1/xdaforums huggingface dataset:
[OnePlus X Original Android Development] eng.stk:
blu_sp★rk r173

All right crew!

New beta build is up for OOS 3.1.* Wicked!

This is only compatible with OOS 3.1.*, you need it already installed with new bootloader and flash it with latest TWRP bluspark v41

Keep in mind: This is untested because I don't have the device anymore, so your milage may vary. I am only interested on debugging stuff in stable OOS, I will no longer build for custom ROMs.

Don't spam this thread with ROM problems or SuperSU not flashing, etc. Stick to kernel business.

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] Subhrajyoti Sen:
Got a bootloop after flashing r173 on OOS 3.1.3
[OnePlus X Original Android Development] eng.stk:
Any posting withtout logs will be ignored.
[OnePlus X Original Android Development] W!ld:
New version causes bootloop :(
[OnePlus X Original Android Development] maxweber1981:
I do not understand. this new kernel is only for OSS and also for the CM. The topic is the CyanogenMod but also in the description of an update (changelog) is the new version only for OSS.

whether it is actually required to write it the latest version twrp.

if the latest version of the double twrp does not boot or smartphone reboots and restarts after 2-3 seconds and will then reboots normally.
[OnePlus X Original Android Development] Kéno40:
Just want to tell that black reactor has a beta OOS 3 version which already boots. It could be use full maybe?

Will try your kernel Tomorrow!
[OnePlus X Original Android Development] Part.0:
hello [MENTION=3873953]eng.stk[/MENTION] sir i have some questions.. if i want to backup stock kernel of oos 3.1.3 using twrp v41, so..

1. can i use the same twrp v41 to backup/restore the kernel only on oos 3.1.3. will it works ?

2. or do i need to use stock oos recovery to backup and restore kernel ?

3. if its possible to backup/restore kernel. i only need to choose kernel (boot.img) right ?

i will flash the r173 soon as i get the anwers, i need to backup first in case such problem after flashing.. thank you very much for the hard work and for your remarkable support of opx/oos!

*or anyone got the answers for me? thx
[OnePlus X Original Android Development] Fatsodonkey:
I tried it and it works. Only restore boot and voila stock kernel in use. Make a full backup in case there is problems.

r173 reboots in boot animation. So it does not boot though.
[OnePlus X Original Android Development] Part.0:
thank you for reply. so u have flashed the r173 and got bootloop? and you used twrp v41 to backup/restore the stock kernel? only boot.img right? thx

*can you provide logs when flashed r173, so Dev. can fix it and work on it.. thx
[OnePlus X Original Android Development] :
I can confirm the bootloop. Still, since I haven't rooted my phone, it's going to be hard to allow adb to work during boot, thus making it difficult for me to get relevant logs. Any ideas on this? (or, if someone actually has the logs, please provide them!)

EDIT: also, when I restored the boot partition backup with twrp, wifi didn't work, even after clearing cache, etc. I had to dirty-flash OOS 3.1.3 again. Just leaving it here in case someone has the same problem after reverting to the previous kernel.
[OnePlus X Original Android Development] seacowx:
as far as I know you need to backup EFS partition alongside boot partition. EFS may contains IMEI, MaC address for wireless network which needed for Wifi to working.

and the other problem is there should be another two backup contains: modemst1, modemst2 which should be backed up along with boot partition folder. but now I couldn't find it.

I remembered with the previous 5.1.1 rom I had those two modems along with boot partition backup. I don't know if this issue related to OOS3 ROM or TWRP v41 restriction. maybe eng.stk could explain this.. tyvm.
[OnePlus X Original Android Development] Fatsodonkey:
Yes. Im sorry that i hesitated. Wifi does not infact work with only boot restored.
[OnePlus X Original Android Development] bundysoat:
The latest kernel works? Or cause bootloop?

Enviado desde mi OnePlus X.
[OnePlus X Original Android Development] eng.stk:
All blu_spark releases modify system partition because of modules, restoring boot and system is needed (is in OP), nothing to do with EFS or any if that.
[OnePlus X Original Android Development] seacowx:
got it. simply means dirty flash is needed.

so..any progress on r173 fixing..? as ussual it's not a demand just a wish.. tyvm for all the hard work & support on oos.
[OnePlus X Original Android Development] shinodoigt:
No logs, so no fix.
[OnePlus X Original Android Development] dhmlaz:
conflict

The version 173 creates continuity RESTART is conflict and retry to start the phone Oneplus X with OOS 3.1.3 :confused::crying:
[OnePlus X Original Android Development] Exodusche:
Had you read the previous comments you would of saved yourself some time and headache. Hopefully your read the OP and backed up system and boot.
[OnePlus X Original Android Development] cktoxin:
Alright, I've tried installing version 173. Same problem as the rest are reporting: boots into the OOS3 animation for about 8 to 10 seconds then forces a restart, and this process is repeated. I've tried running a logcat with the phone connected to the computer, but it stays on 'waiting for devices.' Hence I'm having trouble getting a logcat done during the boot, I've waited for about 5 minutes, but nothing on the screen. Meanwhile, the animation into rebooting keeps looping. I've tried doing desmg, but the same thing happens: no devices are detected in my cmd screen. When I restore my Boot and System partition, the phone boots fine, and I am able to get a logcat done during boot animation. Of course, this log is useless as I am on stock OOS3 kernel.

Is there anything else I could do to help? I'm quite familiar with googling before I start posting, but I can't find any way to get a log dumped during booting (of the latest kernel). I am on OOS 3.1.3, TWRP 3.0.2-2 | bluspark v41. If you'd like me to do some other kind of logging, I'd be happy to help out, but I'll need some pointers as to how to do it.
[OnePlus X Original Android Development] eng.stk:
I think opx uses console-ramoops, so it should be a menu for dump it on the bootloader.

/proc/last_kmsg can be available in recovery immediately booting to twrp after the reboot I think, search for /sys/fs/pstore/console-ramoops.

I don't have the device and no time for more atm, someone posted logs awhile ago so should be possible to got those [MENTION=1675826]peryndark[/MENTION] any help mate?
[OnePlus X Original Android Development] eng.stk:
blu_sp★rk r174

All right crew!

New beta build is up for OOS 3.1.* Wicked!

This is only compatible with OOS 3.1.*, you need it already installed with new bootloader and flash it with latest TWRP bluspark v41

So, I will give this one last try. blu_spark has to many goodies and optimizations merged, is impossible to me break stuff from ground zero with quality.

I added some Oneplus changes that were missing and a fix to GCC regression [MENTION=3279788]ZaneZam[/MENTION] found :good:

Hope it works or at least someone can get some logs :fingers-crossed:

If we can't get nowhere, I'll probably drop support on the opx, I can't do much more :(

Keep in mind: This is untested because I don't have the device anymore, so your milage may vary. I am only interested on debugging stuff in stable OOS, I will no longer build for custom ROMs.

Don't spam this thread with ROM problems or SuperSU not flashing, etc. Stick to kernel business.

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] cktoxin:
OK I tried running the command

adb shell su -c cat /sys/fs/pstore/console-ramoops > kmsg.txt

And got this in the resulting text file:

/sbin/sh: su: not found

Will this help? Anything else I should do?
[OnePlus X Original Android Development] eng.stk:
You need to be rooted, if you're already in recovery all commands are made as root so you don't need su

You should cat to a rw location so you can get the file later, like > /sdcard/kmsg.txt
[OnePlus X Original Android Development] Part.0:
please post results for r174. is it working? as I am away from pc so haven't do backup, and please tell the needed steps if scripts are needed to flash it properly. thanks!
[OnePlus X Original Android Development] cktoxin:
Alright, this time I ran the command

cat /proc/last_kmsg > /sdcard/kmsg.txt

Found the kmsg.txt file and it gave me this:

http://pastebin.com/yWUvST0r

Judging from the timestamps it's the correct log. Hope this helps! If anything else is needed please don't hesitate to contact me, looking forward to a working kernel! :good:

Edit: I just realised you put up v174. Will flash and report back. Don't worry, I'll try to provide logs if I can find the time!
[OnePlus X Original Android Development] W!ld:
Pls provide twrp recovery pls
[OnePlus X Original Android Development] cktoxin:
Alright, [MENTION=3873953]eng.stk[/MENTION] I flashed v174, and got the same bootlooping issue. Here's the kmsg log:

http://pastebin.com/NCttUPYW

Hope this helps! If you need anything else, just ask :)
[OnePlus X Original Android Development] dhmlaz:
mission install R.174

Can was corrected in version 174, but authentic ROM 3.1.3. OOS still have a problem, and do follow reboot, in my phone OnePlus X:confused:
[OnePlus X Original Android Development] seacowx:
ok log has been provided, it should be useful. I'll be patient waiting for working kernel. thank you so much for the Dev spent his time. much appreciated.
[OnePlus X Original Android Development] eng.stk:
blu_sp★rk r175

Alright crew!

blu_spark r175 test for MM 3.1.* is up, you know the drill :good:
[OnePlus X Original Android Development] oneplusx:
Can anybody confirm that the bootloop issue is fixed on r175 build?
[OnePlus X Original Android Development] cktoxin:
Still bootlooping on v175 unfortunately, it almost finished the boot animation, but then proceeded to reboot. Here's the log:

http://pastebin.com/tBgpT9WR

Thanks so much for your time [MENTION=3873953]eng.stk[/MENTION], I really appreciate your effort in fixing this :good:
[OnePlus X Original Android Development] eng.stk:
blu_sp★rk r176

Alright crew!

blu_spark r176 test for MM 3.1.* is up, you know the drill :good:
[OnePlus X Original Android Development] mdsaif92:
R176 working??
[OnePlus X Original Android Development] malte41:
Too bad. I get stuck in the Bootloop :| would provide logs but i have to leave work now. Be back in a few hours.
[OnePlus X Original Android Development] Part.0:
ok 1 user says bootloop, other can confirm that?

---------- Post added at 06:26 PM ---------- Previous post was at 06:25 PM ----------

which ver.? there's new build r176. just to make sure..
[OnePlus X Original Android Development] mh2cc:
Yes I can confirm r176 bootloop
[OnePlus X Original Android Development] cktoxin:
Hey [MENTION=3873953]eng.stk[/MENTION], I'm sorry to confirm another bootloop (v176). Log is pasted here:

http://pastebin.com/pa9iPMyE

Again, the boot animation continues and crashes just as it starts the finishing animation.

Thanks for your hard work!
[OnePlus X Original Android Development] eng.stk:
Well bad news then...

I tried to do several obvious fixes, butthat wdog bite can be several stuff.

I would need to do a complete bringup from scratch and without the device is impossible.

So long opx...
[OnePlus X Original Android Development] cktoxin:
I understand. Too bad, cause I loved your kernel on OOS2. Thanks for all your help, will probably be picking my next phone based on your kernel support haha.
[OnePlus X Original Android Development] motherninja:
Well, it's a sad news for OPX users, but it's OK, [MENTION=3873953]eng.stk[/MENTION]. You already did ur best for OPX. My next device would be the OP3! :good:
[OnePlus X Original Android Development] migueldbr:
Sad news [MENTION=3873953]eng.stk[/MENTION] ...you will be missed my fellow tuga=p
[OnePlus X Original Android Development] zer0se7en:
Oh man... :(

Yes you and your kernel for OPX will be missed, eng.stk
[OnePlus X Original Android Development] dchrono:
Sorry to see the kernel go, I too got bootloop. Perhaps update OP.

Thanks for your efforts.
[OnePlus X Original Android Development] seacowx:
perhaps..if he really has a spare time for opx to fixing this up (besides feed up the nexus+op3 things he managed) I'm sure we can have a bluspark great kernel for oos 3 onyx (like wise) back to it's glory. wether he doesn't own opx anymore I don't know..I just hope some miracle.

you'll be missed [MENTION=3873953]eng.stk[/MENTION] au revoir!
[OnePlus X Original Android Development] eng.stk:
I will not update this anymore, it was a good ride guys but it came to an end.

Since it's not doable to me to make new stuff thread will be closed.
[OnePlus X Original Android Development] Portgas D. Ace:
Then there is only one more thing to say:

Thank you for all your efforts and time you spend on this great project. I really appreciate it.
[OnePlus X Original Android Development] RinoFxx:
Sennheiser but i don't remember the model, i paid that 30€,not very much! I noticed that with play music the sound is high but with Spotify not.

Inviato dal mio ONE E1003 utilizzando Tapatalk
[OnePlus X Original Android Development] rockuppl:
R37 ....battery drain even in idle mode.... 100 to 73% SOT of 50mins... Any1?
[OnePlus X Original Android Development] Razertje:
Doesn't sound that bad? About the same usage here with Amplify, Greenify and PowerNap.
[OnePlus X Original Android Development] eng.stk:
No, kernel doesn't drain.

You have something else eating your juice.
[OnePlus X Original Android Development] supersonictt:
[MENTION=3873953]eng.stk[/MENTION]

Thank you for replying and considering this, I really appreciate it :)

I have a Nexus 5 with Euphoria-OS custom ROM, stock kernel and ElementalX Kernel (EXK) app. Comparing the two devices with default sound settings (I mean in Nexus 5 no adjustments for speaker sound in EXK app, the sound seems louder in OPX. Using headphones, they both produced almost the same sound.

In EXK app, there is an option to increase the headphone "Gain" and the headphone "Power amp gain". With these 2 settings increased, the sound is much louder. There is also an option for speaker gain, which gives louder sounds through the speaker.

That is why I asked if there any plans on implementing this in the kernel. The kernel is great in terms of battery and performance, so let's hope that these sound features would be added in the future :)

One more thing, does anyone know if there is a way to pump up the volume through the headphones in OPX for now? I believe equalizers will not do that good job in terms of loudness, but sure in terms of bass.

Viper4Android on OPX, any one tried that? (Sorry if it is off-topic, but I will remove this line if you ask me to do so [MENTION=3873953]eng.stk[/MENTION])

Thanks again for the great work.
[OnePlus X Original Android Development] mohammedtabish:
I have the same issue kernel drains battery in kernel auditor when system is idle it shows cpu cores at 18k mhz

PS : I am using blu_spark cpu governer
[OnePlus X Original Android Development] rockuppl:
Freshly booted without any apps with greenify....

Charged to 100% .... N zoooooooom approx. every 3 mins in idle state .. 1% down.

I have been vigrous tester for your Kernels from the very beginning
[OnePlus X Original Android Development] eng.stk:
Nope.

Thats not drain, that is battery calibration and other stuff at work.

Very noticeable in every 3.4 kernel device I had. I mean having 100 and some minutes alter 99% or 98%.

Some devices on 3.10 have smart battery meter and wear/life algorotgms, its a bit better.

Stay out exposed, greenify and crap like that.
[OnePlus X Original Android Development] Calvin2394:
How diffiult is it to forward port this device to a 3.10 kernel?

Has anyone done this sort of thing before with success?
[OnePlus X Original Android Development] eng.stk:
Close to impossible.
[OnePlus X Original Android Development] Maelstr0m:
6h SoT with stock settings

nice work [MENTION=3873953]eng.stk[/MENTION] :)

View attachment 3554359View attachment 3554360View attachment 3554361

Inviato dal mio ONE E1003 utilizzando Tapatalk
[OnePlus X Original Android Development] adity:
Does gaming performance improve with this kernel. Even my moto x 1st gen used to run smoothly
[OnePlus X Original Android Development] bubbl3:
I didn't try gaming before flashing this kernel, but I do not notice stuttering right now.
[OnePlus X Original Android Development] xlnzee:
I am facing the same issue, did not have this until I changed the file system to F2FS. Its really annoying on the lock screen, attached screenshot. Soft or normal reboot doesn't fix it for me.
[OnePlus X Original Android Development] bubbl3:
Try to switch airplane mode on and then off, it should disappear.
[OnePlus X Original Android Development] xlnzee:
That did the trick, thanks!
[OnePlus X Original Android Development] supersonictt:
I also didn't try gaming before flashing the kernel, but after flashing it, I tried Asphalt 8, which used to stutter and lag badly with users in OnePlus forum. It runs completely smooth with the kernel.
[OnePlus X Original Android Development] Zudikasxxx:
Sadly bug will come back after reboot.
[OnePlus X Original Android Development] primemonitor:
Just curious, do you plan on including more governors and I/O schedulers in future builds?
[OnePlus X Original Android Development] eng.stk:
This again?

Nothing to do with kernel.

Nope.
[OnePlus X Original Android Development] sarthakspiker:
Is it possible to add fast charge support? As I guess it's supported by the processor
[OnePlus X Original Android Development] eng.stk:
It's not possible to add QC, because although the SoC is compatible with QC 2.0, OnePlus used a PMIC and charging circuit that is not.
[OnePlus X Original Android Development] trveller72:
Guys, there are a lot of issues related to ROM. Please do not bring them here.
[OnePlus X Original Android Development] Roykooiman:
There was an Ota proof twrp recovery right? Can't find it someone knows which it is? Because I just got the system update and I need to flash it because I want to get the SD card fixed.

Verstuurd vanaf mijn ONE E1003 met Tapatalk
[OnePlus X Original Android Development] drakohla:
Just flashed the OTA using eng.stk Version of TWRP.

Follow the Link in the OP.
[OnePlus X Original Android Development] eng.stk:
:)

View attachment 3555146
[OnePlus X Original Android Development] Roykooiman:
Can't find a download link for it.

Verstuurd vanaf mijn ONE E1003 met Tapatalk
[OnePlus X Original Android Development] drakohla:
Just click "DOWNLOAD KERNEL ZIP" in the OP,

Than you can download "twrp-2.8.7.0-onyx_f2fs_r2.img"
[OnePlus X Original Android Development] Calvin2394:
I see #43.
[OnePlus X Original Android Development] Bitman64:
[/COLOR]

Any hint where to find latest OTA?

Gr. B.
[OnePlus X Original Android Development] loveboy_lion:
http://xdaforums.com/showthread.php?t=3257032

Here you go
[OnePlus X Original Android Development] Bitman64:
thanx a million.
[OnePlus X Original Android Development] Chronzy:
For the life of me I can't get this version of twrp to stick. I flash it and as seen below the boot command won't work...

I know not to boot into OS because it will flash stock so I PWR+VOL DOWN and reboot directly into twrp,

from there I reboot recovery from within twrp- back into twrp..

then I power down, PWR+VOL DOWN back into twrp...

after all that I reboot into OS, use advanced reboot to go back into twrp and stock recovery boots. WTH
[OnePlus X Original Android Development] dagger:
Is your bootloader unlocked?

If not, unlock it first.
[OnePlus X Original Android Development] Chronzy:
yes, i'm able to boot into twrp by PWR+VOLDOWN.

I've made 2 nandroids.

I've flashed the 2.1.3 update.

btw, what's with the 005 naming scheme for these updates? I don't see that anywhere in About phone OS info.
[OnePlus X Original Android Development] primemonitor:
You did the boot command wrong. Correct command is "fastboot boot recovery.img". What you did was "fastboot boot recovery recovery.img"
[OnePlus X Original Android Development] Chronzy:
Ok thanks, I would try that out but it's actually working now somehow.

I just tried to reboot to recovery using advanced reboot and it booted to twrp.

This is after flashing SuperSU 2.46 and xposed and getting my phone all set up. I have no idea what made it stick, but it's there now. Just booted into it twice.

Could it be the SuperSU flash? Unlikely huh.. so odd.
[OnePlus X Original Android Development] Roykooiman:
So I tried flashing the system update with the bluspark twrp, but it wouldn't flash. It gave the error executing binary in zip.... Anyone got a solution?

Verstuurd vanaf mijn ONE E1003 met Tapatalk
[OnePlus X Original Android Development] JayVee:
Me too. Just wondering if #37 will also work on the latest firmware version?

Beyond that flashing the new OTA with the latest TWRP (twrp-2.8.7.0-onyx_f2fs_r2) worked without any problems.

Flashed full 003, than patch 003-004 and patch 004-005 on top. Followed by Xposed and SuperSU.

Thanks!
[OnePlus X Original Android Development] Maelstr0m:
yes it works

Inviato dal mio ONE E1003 utilizzando Tapatalk
[OnePlus X Original Android Development] Calvin2394:
Will the kernel be compatible with CM12.1 and/or CM13 after they're released?
[OnePlus X Original Android Development] eng.stk:
As it is probably not, we'll see when they're out if I can make a compatible version.
[OnePlus X Original Android Development] mvanvoorden:
For me the same.
[OnePlus X Original Android Development] ajaysoranam:
Just flashed r37 everything is looking good, but my phone is heating up like hell( when compared to the stock kernel)... Whilst charging and idle the temperature reaches to 52c. I have underclocked it to 1728 mhz no undervolting, tried both blu_spark and interactive as governors.... Anything that i am missing or not doing right?

This heatingissue was also present when i tried out r25.
[OnePlus X Original Android Development] bubbl3:
Must be something else mate, it never gets more than a little warm for me.
[OnePlus X Original Android Development] Mojar7070:
Hello, I used flashify to flash the f2fs version of TWRP. is there a way to confirm whether I have the correct recovery installed??

On flashify it only shows the information on the screenshot below.

I was able to flash both otas with "new" recovery if thats any indication i did it right.
[OnePlus X Original Android Development] bubbl3:
Does it show the blue spark logo instead of the teamwin one when you boot in recovery?
[OnePlus X Original Android Development] Mojar7070:
Hello, it does say blue spark instead of TWRP. Thanks. Problem solved.
[OnePlus X Original Android Development] eng.stk:
blu_spark r44

All right crew!

New build is up, wicked :)

I also uploaded my TWRP r4 build with blu_spark inside, with a couple fixes

Understand that I give NO support for TWRP, it's the build I personally use and I only upload it so people have a OTA ready TWRP with a couple fixes and F2FS support.

About bugs and troubleshoots: don't bother to post if a log isn't ready or without steps so the behavior can be replicated. Also, I only support stock OSS with NO mods whatsoever (apart from root).

Save the SOT and battery stats/screenshots for general threads, here we deal with development, not personal tastes and results.

If you like my work, don't forget to hit thanks ;)
[OnePlus X Original Android Development] mvanvoorden:
When I flash the OTA, I now get:

"/system/bin/app_process32" has unexpected contents.
E: Error executing updater binary in zip '/sdcard/.OnePlusOta/OnePlusOxygen_14_OTA_004_005_patch201511232152.zip'

I have no XPosed or something running. Stock + root + latest blu_spark TWRP and kernel.

Edit: Oh wait, I guess I need to dirty flash the ROM and the earlier OTA's and then root again?

Edit2: Yes that was it :) Works now!