yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] eng.stk:
blu_spark r17 hybrid beta

All right crew!

Newhybrid build is up. Wicked!

This should fix the charging situation, all the rest seems solid.

Keep an eye out for battery levels, temperatures etc

Although it works nicely on the OP3T, keep in mind this is an experimental beta, you can brick your device or turn it into a Note 7.

This is highly untested and it's not a production build! Don't bother download if you don't want to give feedback.

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

Don't forget to hit thanks, it's free ;)
[OnePlus 3 & 3T Cross Device Development] nmlssit:
Anyone here having OOS 3.2.8 w r168, trwp -28 AND phone encrypted w PIN at boot?

Since i moved from OB8 to stable i had to wipe /data so now it's decrypted, but i am scared if i will decrypt it back i will have the same issues twrp has with crypted ob8.
[OnePlus 3 & 3T Cross Device Development] juginkrebs:
İ dont have any Problem With Charging :D i am at OOS 3.2.8 R16 Hybrid great Kernel

Gesendet von meinem ONEPLUS A3003 mit Tapatalk
[OnePlus 3 & 3T Cross Device Development] tofuboi01:
R17 fixed the LED charging indication and also charged successfully to 100%.
[OnePlus 3 & 3T Cross Device Development] FahrenGrade:
So the op3t link in this ^ post is an experimental build as an attempt to make your kernel work on both devices?
[OnePlus 3 & 3T Cross Device Development] candiesdoodle:
Charging and everything else just works fine on r17. Waiting to see battery life.
[OnePlus 3 & 3T Cross Device Development] madsponge26:
R17 is smooth but temperature is higher that R168.
[OnePlus 3 & 3T Cross Device Development] nmlssit:
Why the heck i can't have f2fs on 3.2.8?

I was on f2fs 3.2.8, but i wanted to re-encrypt my phone (As i wrote in this page some posts above). I started the encryption procedure (on r17 3.2.8 f2fs) but after 4 hrs still in boot animation i rebooted, lucky nothing happened to the system. I thought it was some problem in either custom kernel or r17 then i decided to dirty flash 3.2.8 image to have stock kernel.

Result: wiped phone, from 328 f2fs decrypted to 328 ext4 encrypted.

WTF? OOS 328 doens't like f2fs changed in TWRP? Do i must use Open Beta 7 internal wipe to obtain f2fs everytime? Damn this phone is stressful, i miss my Nexus 5.
[OnePlus 3 & 3T Cross Device Development] Chaplan:
To re-encript i formated data partition to Ext4. Rebooted to TWRP, flashed 3.2.8, flashed TWRP and rebooted to TWRP and then rebooted to system.

After this you will be encrypted, I believe the stock kernel may have a part to play on this. Back to TWRP, format data do f2fs, flash Superuser if you need root and Blu kernel to boot with f2fs.

You will be encripted on f2fs withou dm-verity error on boot.

Sorry for the OT.
[OnePlus 3 & 3T Cross Device Development] eng.stk:
blu_spark r18 hybrid

All right crew!

New build is up. First hybrid OP3/3T release is here, wicked!

From now on, builds for OP3/3T will be unified, using 3T base (so can be flashed in both devices).

Although this seems very solid, keep on mind that it still is hacky.

So, by flashing this you accept that your phone can become a paperweight, transform into a Note 7 and your cat/dog can start dancing ballet in the middle of your bedroom.

All downloads will be on 3T thread from now on: http://xdaforums.com/devdb/project/?id=18270#downloads

Enjoy :)

Keep in mind: I will give no active support for custom ROMs or OB. Meaning, if using anything besides stable OOS don't bother posting about it.

I am only interested on debugging stuff in stable OOS (with logs and reproducible steps to replicate the issue).

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 3 & 3T Cross Device Development] derdjango:
Wicked stuff! I'm a sucker for stable stuff so will probably wait a little how things turn out with the hybrids. Edit: Yeah, strike that. Just flashed, madafaka.

I guess this thread is done? Better start to subscribe to the 3T thread then. It was a good ride ;)
[OnePlus 3 & 3T Cross Device Development] candiesdoodle:
Already feeling sad. The original op3 is slowly becoming the lesser badass! Damn

Lol

The kernel is smooth as hell. Thanks mate. No issues so far
[OnePlus 3 & 3T Cross Device Development] samisharora:
Have been a fan of your work, the kernel has been so smooth and bug free always. But now having 3T as base and referring to 3T page for updates, not liking the fact. Anyways it makes sense after what Oneplus did to 3 :)
[OnePlus 3 & 3T Cross Device Development] eng.stk:
Nah, I'll be around and posting on both places

Since the base is from the 3T, makes sense.

I see no poiny on pushing the same builds all over.

Why this is bad? Having newer and improved sources is not nice?
[OnePlus 3 & 3T Cross Device Development] samisharora:
It looked like you will be active on 3T now, but yes if you will be posting on both places. Then we are good :)

3 is special right, 3T comes from 3 afterall!
[OnePlus 3 & 3T Cross Device Development] Jole7:
I totally agree with you.
[OnePlus 3 & 3T Cross Device Development] t-shock:
3T has an OOS 3.5.3 while the 3 has the 3.2.8. 3.5.3 is like a community build, so are we able to install it on the CB with my noobish/weird logic?

Thanks

PS I dont know if this question has been asked and answer, if so then I'm sorry
[OnePlus 3 & 3T Cross Device Development] nmlssit:
[MENTION=3873953]eng.stk[/MENTION] Why does this feel like trying to round the edges of a cube to pass it through the round hole? If this will have 3T as base, for sure code needs to be adapted for 3's differences (as we saw with r16 for battery) so what's the point? What's the difference between adapting a 3T kernel instead of taking the goodies from its source and port them to our 3?

PS: Don't see this message as a criticism, it's just a question :)
[OnePlus 3 & 3T Cross Device Development] trawel:
I'd like to ask if this is kernel related - I was using franco kernel and download speed on WiFi was good. Then I switched to blu_spark (dirty flash ROM - OOS 3.2.8) and for me, WiFi speed is lower than on franco (the same place in my room).

Does kernel have anything common? Is there any option to try to make WiFi speed better?

Thanks
[OnePlus 3 & 3T Cross Device Development] NickosD:
You can. Someone already did it. Keep a nandroid just in case
[OnePlus 3 & 3T Cross Device Development] derdjango:
Little script for overclocking. Remove .txt and put in /su/su.d
[OnePlus 3 & 3T Cross Device Development] crzykiller:
hey man, i was wondering if you could make it so that the OP3 can use the frequencies the OP3T uses, as in 2.35ghz for the big and whatever frequency for the little cores.
[OnePlus 3 & 3T Cross Device Development] Piyush lalwani:
You can't overclock the op3 to use 2.35 GHz like op3 because both have different processors . And 820 can only be over clocked only to 2.25Ghz.
[OnePlus 3 & 3T Cross Device Development] Der-Knuffi:
Where can I find the latest TWRP 3.0.2.28? There is no link in op.

Gesendet von meinem ONEPLUS A3003 mit Tapatalk
[OnePlus 3 & 3T Cross Device Development] wokdogol:
here u go :good:

http://xdaforums.com/devdb/project/dl/?id=21835
[OnePlus 3 & 3T Cross Device Development] Der-Knuffi:
Thanks, one last question:

With this I can install beta ROMs as well as official ones?

And backup both?

Gesendet von meinem ONEPLUS A3003 mit Tapatalk
[OnePlus 3 & 3T Cross Device Development] Jole7:
It has been added already and it's stable check out Xceed kernel by kairi_Zeroblade 2.34x big and 1.78x little gpu overclock is coming
[OnePlus 3 & 3T Cross Device Development] Piyush lalwani:
Can you link me to the post where he announced that he had overclocked the CPU to 2.3x GHz and will be overclocking GPU as well?
[OnePlus 3 & 3T Cross Device Development] Jole7:
Read the forum and Github - commits
[OnePlus 3 & 3T Cross Device Development] Piyush lalwani:
Wonderful Reply Sir. If I had a lot of free time I would probably have read the commits and each and every comment of the thread.

Thank You!!
[OnePlus 3 & 3T Cross Device Development] Jole7:
Check the last 2 pages its not so hard i think
[OnePlus 3 & 3T Cross Device Development] Mostafa Wael:
I honestly don't know why the fuzz about overclocking. If you are not doing something like media converting on your phone, you will barely notice a difference. I have been testing stock max freqs, normal overclocked freqs (1728 MHz + 2265 MHz) and the 'abnormal' overclocked freqs (1758 MHz + 2342 MHz) and I barely notice a difference in speed, if not at all. Geekbench scores only sees a bump in single core score with the latter option, but again, app launches and everything else is actually the same! Unless you do some media converting like changing mp4 files to mp3 or whatever, you will barely notice anything. Also I would like to deduce that the voltage spike with the latter option of 2342 MHz and 1758 MHz is massive, it may not be that good probably. But, I dunno, maybe the dev has another opinion.

This is just an opinion from a power maniac obsessed with speed and power, and 'Burnouts' ;)

Enjoy the masterpiece crafted by the dev and relax. Let the testers do the hassle :highfive:

Cheers!
[OnePlus 3 & 3T Cross Device Development] wokdogol:
im not sure if the beta rom work, maybe anyone here already try that. :confused:
[OnePlus 3 & 3T Cross Device Development] eng.stk:
I never had issues with WIFI on 3.2, but the ROM wifi config is not optimal.

Wifi on OOS 3.5 with exactly the same kernel driver is much better.

Will work on OOS 3.2 and M OB (not on N)
[OnePlus 3 & 3T Cross Device Development] habylab:
I think underclocking is where it's at. I don't game, so it's nice to save a little battery to profit.
[OnePlus 3 & 3T Cross Device Development] crzykiller:
Since you don't game, underclocking actually does not improve battery at all. You may get slightly better screen on time (+15minutes max) but everything will be slower on your phone so you end up doing the same amount of work on it. Considering the 2150mhz and 2265mhz big cores use the same voltage and the 1593mhz + 1728mhz little cores use the same voltage, you actually get better battery life considering things are happening quicker, tasks are being completed faster and the cores can get to their "sleep" mode faster. I've been running the over clocked frequencies since they were available and Everytime I go back to the stock frequencies, I have worse battery life
[OnePlus 3 & 3T Cross Device Development] habylab:
Yep, I've always thought this. Undervolting is what would really help, but it depends how much variance OP devices have, which I imagine is a lot.
[OnePlus 3 & 3T Cross Device Development] anshmiester78900:
The download link is showing only for 3T and not for 3. Where can I find links for this kernel for OP3?

Is this the one I should download for 3.2.8 OOS : blu_spark_r18-oos_op3-op3t_f3d1080.zip
[OnePlus 3 & 3T Cross Device Development] Remorcer:
Yep.
[OnePlus 3 & 3T Cross Device Development] anshmiester78900:
Thanks
[OnePlus 3 & 3T Cross Device Development] Explorer23:
The question was related to your modified TWRP, not kernel (... so offtopic) ðŸ˜Š

And TWRP .1-28 does work with *all* ROMs to date.
[OnePlus 3 & 3T Cross Device Development] laggardkernel:
r168 with oos 3.2.7, f2fs /data partition. Unknown network err occurred on client when using USB tethering. Client connecting through WiFi hotspot couldn't connect to the internet neither. Does anyone experience similar problem?

Edit 1:

It seems that my PC and iPad couldn't get correct addresses automatically, through DHCP. The hotspot/tethering phone's local IP is 192.168.42.129. While the other devices under the network get addresses begin with 169, which is totally wrong. I tried to configurate the IP address and DNS server manually according to the "ifconfig" result from the tethering phone. But I must set DNS server a explicit address except 192.168.42.129 or 192.168.42.1. I couldn't get a correct address of a domain name when 192.168.42.129 or 192.168.42.1 as my DNS server. On the basis of what i experienced, it seems the tethering phone failed to server as a DHCP server nor a DNS server. I'm not sure wheather the problem caused by the kernel now, since I'm not able to flash back to the default kernel with a f2fs data partition. Wish someone provide a verification.
[OnePlus 3 & 3T Cross Device Development] Butit:
Can I flash the touchscreen_fw_update.zip after the r18_op3_op3t_kernel.zip, or is the function of the touchscreen zip file incorporated into the r18 kernel zip file?
[OnePlus 3 & 3T Cross Device Development] immi803:
You can flash anyway before or after, didn't you see change log for r18?
[OnePlus 3 & 3T Cross Device Development] Butit:
Right.....thanks.
[OnePlus 3 & 3T Cross Device Development] candiesdoodle:
All right I have been on r18 for a couple of.days. super smooth

But I would say the battery is a bit on the negative side? I haven't had any usage changes .. lasts for 4-4.5 hrs sot. Prev versions (pre-hybrid) used to last 5.5-6 hrs sot.

Is this a common behaviour seen?
[OnePlus 3 & 3T Cross Device Development] daviss101:
Could someone please explain to me the difference in the TWRP available in the bluspark download section and the official or modified? Thankss
[OnePlus 3 & 3T Cross Device Development] Jole7:
Modified has the latest changes and upstream f2fs drivers from eng.stk i use the latest and it's perfect no issues
[OnePlus 3 & 3T Cross Device Development] daviss101:
Cheers for the reply mate I get you, which ROM are you using with the latest eng.stk TWRP? Just asking as im currently using an unknown modified version with oos beta 7 but can't flash cm14.1 roms as it deletes the TWRP on boot
[OnePlus 3 & 3T Cross Device Development] _PrEzi_:
I think I've faced a similar issue on trying to connect to a mac wlan hotspot - it got somehow connected to the wlan, but without internet access (asterix icon). I forgot unfortunately to check the IPs. I cannot verify too because of f2fs on data ....

But I am nearly sure this was not a problem on an earier version.... and now two changes I actually did that might have caused it ---

either the installation of OOS 3.2.8 (was working fine on 3.2.7) or it was the instalation of blu_spark newer than the r15x branch....

Unfortunately I don't quite remember which exact version of the kernel was fine...
[OnePlus 3 & 3T Cross Device Development] Butit:
I too noticed that r18 kernel has faster battery depletion and lesser SOT.
[OnePlus 3 & 3T Cross Device Development] Jole7:
Now i use Arter97 rom i didn't faced that problem with Jgcaap CM14.1 rom flashing it with latest twrp 28
[OnePlus 3 & 3T Cross Device Development] eng.stk:
Nothing is made on the kernel to change that.

Nothing like that on our testing, on the contrary.

Also, your usage make your battery life, not the kernel.
[OnePlus 3 & 3T Cross Device Development] 1337jay:
Hello guys, did anyone try this on Sultans CM build? I know there is no support for custom ROMs but still curious if anyone tried and how it went.

Thanks in advance!
[OnePlus 3 & 3T Cross Device Development] NickosD:
Won't work
[OnePlus 3 & 3T Cross Device Development] 1337jay:
Thought so, thanks for the quick reply.
[OnePlus 3 & 3T Cross Device Development] NickosD:
Try latest version for custom roms in old downloads link.
[OnePlus 3 & 3T Cross Device Development] laggardkernel:
Sorry to bother you with the tethering thing. The bad news is that I tried to switch to other kernels to have a test on it and ended in breaking my data partition, an I/O error occurred. The good news is that I formatted my data as ext4 again to fix the I/O error, and find that no correct IP addresses were gained on the clients even with an official kernel, 3.2.7.

So, it's absolutely not a error caused by kernel. Still don't figure out why this happened. The tethering/hotspot did work well some time before.

---------- Post added at 09:31 AM ---------- Previous post was at 09:29 AM ----------

Thx for your reply. It seems that's not a problem relating to kernels. The tethering/hotspot did work well on some earlier version ROM.
[OnePlus 3 & 3T Cross Device Development] Rawwrius01:
[MENTION=3873953]eng.stk[/MENTION] some updates ago you posted something about fixed WhatsApp derp on f2fs (Dec 12th build in post #2198) what do you mean with that? Or can someone else explain?

Gesendet von meinem ONEPLUS A3003 mit Tapatalk
[OnePlus 3 & 3T Cross Device Development] marf28101995:
Sometimes WhatsApp wasn't saving the messages
[OnePlus 3 & 3T Cross Device Development] ungeeked:
Try disabling fsync. It fixed for me.
[OnePlus 3 & 3T Cross Device Development] Mostafa Wael:
If you are talking about tasks being done faster, max clock set is not the only factor. Other things like the optimisations done by the dev of the kernel and/or ROM, I/O settings, Scheduling settings and governor settings does indeed make a really stark difference. Taking governor settings as a demonstration, if you have set the governor to aggressively ramp up to the highest freq as quick as possible, resulting in ramping up to the 1478 MHz for instance, it will be faster than making the governor ramp up the freqs slower even if you have like 2 more freq steps more than the default max freq. And since we are talking about a L.b structured SoC, migrating the tasks to and from the big cluster does make a noticeable effect as well.

Long story short, it is not all about overclocking to make tasks get done faster, far from it.
[OnePlus 3 & 3T Cross Device Development] eng.stk:
No need for that, the issue has been addressed. He's just explaining what it was.
[OnePlus 3 & 3T Cross Device Development] vampire36:
[MENTION=3873953]eng.stk[/MENTION] : Sent you a pm for small help. Do reply once you find some time! Thanks!
[OnePlus 3 & 3T Cross Device Development] derdjango:
r20 fly like a g6!
[OnePlus 3 & 3T Cross Device Development] habylab:
Didn't see anything here, where's the changelog?

edit: found it in the OP3T thread.
[OnePlus 3 & 3T Cross Device Development] eng.stk:
blu_spark r20 unified

All right crew!

New build is up. Wicked!

Some security, performance, standby battery and general upstream fixes.

Latest OOS 3.5.4 changes merged, build with newest blu_naro-6.2 2016.12

Keep in mind: I will give no active support for custom ROMs or OB. Meaning, if using anything besides stable OOS don't bother posting about it.

I am only interested on debugging stuff in stable OOS (with logs and reproducible steps to replicate the issue).

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 3 & 3T Cross Device Development] nikhilsnigam:
r20 slick smooth.
[OnePlus 3 & 3T Cross Device Development] Chris.nl:
I went from 'old' r168 to r20 on 3.2.8, everything seems fine. Thnx mate!
[OnePlus 3 & 3T Cross Device Development] mysky911:
1+3+bluspark = Best smartphone 2016!

:cowboy:
[OnePlus 3 & 3T Cross Device Development] humzaahmed155:
R20 is magical dude. It flies.

Thank you.
[OnePlus 3 & 3T Cross Device Development] vatsal8286:
how is the battery life with this kernel?
[OnePlus 3 & 3T Cross Device Development] eng.stk:
Terrible.
[OnePlus 3 & 3T Cross Device Development] owaisnaim:
LOL!

Savage Level - eng.stk
[OnePlus 3 & 3T Cross Device Development] vatsal8286:
ok thanks for your kind reply
[OnePlus 3 & 3T Cross Device Development] galaxy16:
im now running on open beta 7 data changed to f2fs.. if i wanna use stock oos 3.2.8 with your kernel and my data to be stil on f2fs.. i have to do clean flash then follow the advance filesystem steps you given? and its gonna wipe internal too? i thought data is only like my apps..
[OnePlus 3 & 3T Cross Device Development] eng.stk:
Nope.

Just cleanflash (clear data, don't wipe internal), flash 3.2.8 and blu_spark.

Don't need to change to f2fs if you are already in f2fs...
[OnePlus 3 & 3T Cross Device Development] galaxy16:
alrights thanks! so i just do clean flash, flash super SU and flash kernel and reboot right? i think i need to change cache too, my cache is ext4 currently
[OnePlus 3 & 3T Cross Device Development] eng.stk:
Sure. But in OOS cache must remain ext4, nothing to change.
[OnePlus 3 & 3T Cross Device Development] galaxy16:
ahh.. okay then i dont think i need to do anything about the data n cache to f2fs already since its changed.. just clean flash rom n kernel.. thanks for the swift reply~
[OnePlus 3 & 3T Cross Device Development] cet90:
Hi all kind soul. Can I use this kernel with open beta 9 ROM? Isit compatible? Thanks
[OnePlus 3 & 3T Cross Device Development] Konskl:
I don't think so. Open beta 9 is based on nougat and the kernel is based on marshmallow
[OnePlus 3 & 3T Cross Device Development] jexsuzon:
Is it okay to dirty flash r165 to the current version?
[OnePlus 3 & 3T Cross Device Development] habylab:
Yes
[OnePlus 3 & 3T Cross Device Development] chinmai560621:
Can you check our Xceed kernel's GPU and CPU overclock ? Will you support it? I've tried, and it doesn't eat battery or doesn't have any bugs. Can you?
[OnePlus 3 & 3T Cross Device Development] eng.stk:
No, I'll not add unstable stuff.

Also GPU can't be OC'ed I think, trustzone overrides any stuff changed there.
[OnePlus 3 & 3T Cross Device Development] ungeeked:
Great minds think alike
[OnePlus 3 & 3T Cross Device Development] eng.stk:
Gladly, not always...
[OnePlus 3 & 3T Cross Device Development] m_reyna_16:
Does the latest 161 custom work with nougat aokp? I know u don't want cm talk but wanted to know since the build is there
[OnePlus 3 & 3T Cross Device Development] eng.stk:
No kernel for any N ROMs.
[OnePlus 3 & 3T Cross Device Development] mvlad:
Only data can be switched to f2fs on OOS/H2OS, or can system too and other partitions?

Sent from my OnePlus 3
[OnePlus 3 & 3T Cross Device Development] deeplyyoung:
[MENTION=3873953]eng.stk[/MENTION] is it compulsory to switch to f2fs?

Can we use this kernel with ext4 ? Both system and cache...
[OnePlus 3 & 3T Cross Device Development] eng.stk:
Already talked on this several times.

Only data, following OOS 3.5 and N betas approach.

No, you can use ext4 all around.
[OnePlus 3 & 3T Cross Device Development] JumboMan:
f2fs is optional. No need to convert partition to f2fs to use this awesome kernel.

by the way blu_spark support f2fs only on data partition
[OnePlus 3 & 3T Cross Device Development] chinmai560621:
You'll get a slight app opening speed difference with f2fs, nothing else. If you want the heavy difference wait for OSS 4.0 stable sources. Then we'll have sdcardfs support.
[OnePlus 3 & 3T Cross Device Development] eng.stk:
Better garbage collection, auto trim, improved cache for balanced ssd wear level, etc

It's not all about the speed.
[OnePlus 3 & 3T Cross Device Development] Old_King:
This kernel is silky smooth. Thx for your work Mr.OP.
[OnePlus 3 & 3T Cross Device Development] chinmai560621:
Yeah, but I can go to the terminal and execute the fstrim command. That'll do. No major difference in "benchmarks" . At least, that's what I noticed.
[OnePlus 3 & 3T Cross Device Development] eng.stk:
"benchmarks"... I could point out several stuff about this, but I already told much so about f2fs.

I lately read a very nice article about motorola (heavy using f2fs devices and the smoothest I ever used) that brings soem light into this.

http://taras.glek.net/post/Moto-Z-has-10x-less-lag-than-pixel/