yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] Mostafa Wael:
[MENTION=5438598]RenderBroken[/MENTION] so a quick sit rep for your EAS kernel: it is almost flawless in terms of is it working or not (minority have some kernel panics and random reboots in specific occasions like when the phone is put to sleep) but it is missing one important piece; CPUSETs configuration. Any luck with that?

Also there is something i noticed with both the EAS kernel and the non-EAS kernel; sometimes when you wake up the phone, the screen lights up and all but it looks like the screen did not wake up and you have to lock the phone and unlock to get it back working. Very minor issue but worth saying i guess.

Thank you for all that awesomeness here! :good:
[OnePlus 3 & 3T Cross Device Development] habylab:
OnePlus just updated the kernel source!

https://github.com/OnePlusOSS/andro...mmit/93238877f9e8fbbbf801f2deeebc18f54d4bdc1b
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
May be related to kernel source needing to be updated for 2.6.8. Also, I use the Fingerprint sensor and have never had the issue you described. Do you use the power button to turn the phone on? Just curious.

Sweet thanks! New builds incoming shortly!
[OnePlus 3 & 3T Cross Device Development] weeka89:
i'm just checking this kernel's page every hour awaiting for the CM version :)

Keep on going man, great stuff

N.B this is not a nagging post :D
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
Once, I release R1 for OOS-NCB I will start one for CM. I should be able to port over all my work fairly easily.
[OnePlus 3 & 3T Cross Device Development] Flasher8:
Patiently waiting for CB [emoji16]
[OnePlus 3 & 3T Cross Device Development] 1337jay:
What ROM are you on, official OOS?
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
I am on Freedom OS Rom.
[OnePlus 3 & 3T Cross Device Development] habylab:
I never understood why this is highly rated, isn't it just stock Rom with some apps removed?
[OnePlus 3 & 3T Cross Device Development] crzykiller:
Pretty much that but with a couple tweaks here and there nothing major, it has slightly better battery life and performance while being more stable supposedly. Then again 2 hours into getting the phone I rooted it and installed Freedom OS haha. OOS just doesn't have the problems CyanogenMod does I find.
[OnePlus 3 & 3T Cross Device Development] habylab:
What are the tweaks that give it better battery life and performance?

Can't see anything mentioned that hints towards it. No special tweaks at all.
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
For me it just makes a few things easier. There are a large number of small tweaks. Ad away added iin and a few other things. Just easier to update with it.
[OnePlus 3 & 3T Cross Device Development] habylab:
Fair enough, but it does seem like snake oil in a way to me.

Allows for far more issues down the line versus using just Stock ROM.
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
possible, but I think not in this case. Otherwise I agree with you.
[OnePlus 3 & 3T Cross Device Development] fcisco13:
Everything works, oos camera (no port), installs with aroma installer, moxie kernel support. It just feels smoother and for me any other rom based on cm makes my signal crazy.
[OnePlus 3 & 3T Cross Device Development] Mostafa Wael:
Is anyone here having problems with Bluetooth connectivity ? I just tried to connect my bluetooth earbuds and it failed to communicate. Not sure if it is kernel related yet, will investigate later today.
[OnePlus 3 & 3T Cross Device Development] kash296:
You are aware that signal stats in OOS aren't accurate, right? [MENTION=2732888]fcisco13[/MENTION]
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
I use a BT headset all the time without issues. So not sure what the problem is you are having. Also, I have not made any changes related to BT. At least not knowingly, unless something changes with one of OnePlus' commits.

First I have heard. Mine seem accurate enough. How bad are you saying it's off by?
[OnePlus 3 & 3T Cross Device Development] kash296:
Well, I've read in various threads in this device that OOS gives a more friendly report of signal readings. The CM signal values are slightly more accurate. From the dB values there's only like a minor, insignificant difference I'd say. But on the status bar, not quite. I am not 100% sure the info is correct, this is based on what I've read from multiple reports. To me it doesn't matter so much really, the call goes, I'm able to speak and hear clearly. Only time i check carefully is during mobile data usage, and for me that also seems to run fine on both OOS or CM based ROMs. cheers :)
[OnePlus 3 & 3T Cross Device Development] ndarkside93:
Hello fellow fans of the best kernel for the op3. I have launched a GoFundMe campaign to purchase Zach an op5(with approval) and would like to seek the support of the community.

https://m.gofund.me/buy-2-oneplus-5s-for-eas-developer
[OnePlus 3 & 3T Cross Device Development] Midomad:
FYI Kernel sources are updated for OOS 4.1.6

https://github.com/OnePlusOSS/android_kernel_oneplus_msm8996
[OnePlus 3 & 3T Cross Device Development] Midomad:
Now they release Kernel sources for betas,too!

Good job again,OnePlus!

https://github.com/OnePlusOSS/android_kernel_oneplus_msm8996/tree/oneplus/QC8996_N_7.1_Beta
[OnePlus 3 & 3T Cross Device Development] Balino:
Very nice.. looking forward to the update. This kernel is really awesome
[OnePlus 3 & 3T Cross Device Development] uudruid74:
I know the OP says USB Fast Charging is supported. I'm running Phoenix AEX, which should be the exact same kernel as this. With blu spark, USB Fast Charge could get up to 2A of current (1A otherwise). Dash was 4A (still the same). Right now, I don't seem to get over 1A without dash, and Kernel Auditor says Fast Charge is enabled.

Can anyone confirm current above 1A?
[OnePlus 3 & 3T Cross Device Development] ndarkside93:
USB fast charge is 900ma
[OnePlus 3 & 3T Cross Device Development] Formhault:
Wow, up to 2 amps... That's something.

1 amp over USB 3 is okay. But 2? That's insane. Depends on the PCH I suppose, but 2A via USB...
[OnePlus 3 & 3T Cross Device Development] ndarkside93:
I think he's referring to a standard USB charger. OnePlus blocked charging at a low rate if you don't use dash chargers.
[OnePlus 3 & 3T Cross Device Development] uudruid74:
My mistake. 1.5A. Dedicated USB Quick Charge is 1.5A but you give up MTP.
[OnePlus 3 & 3T Cross Device Development] Formhault:
Hmm, with a Samsung Adaptive Fast Charger my OP3 charges at 1.2-1.6A.

I never knew they used to block that.

Even that is high.

Actually, you're right. My work laptop (some HP ultra) has a fast charging USB port through which my OP3 can draw more than 1.2A, so... Yeah.

Again, depends on the source of the USB power. PCH, or whatever, I guess. My PC, for example, isn't able to push more than 900mA or so over the USB 3 port. And it's an FXA990 chipset, I'd say the PCH is capable enough. Soooo yeah, I don't know it seems :laugh:
[OnePlus 3 & 3T Cross Device Development] ndarkside93:
Yeah I bought a 3a charger just to find out this. Now I have to order a dash chargers for another 25.
[OnePlus 3 & 3T Cross Device Development] Formhault:
5V-3A? That's Power Delivery, and OnePlus doesn't have that. Blasphemy! Dash Charge or nothing! :laugh:
[OnePlus 3 & 3T Cross Device Development] ndarkside93:
Yeah. I realized that after. Somehow I was with my mom and the dash charger for lost. It's not the end of the world but still annoying that they capped the amperage so low compared to other manufacturers.
[OnePlus 3 & 3T Cross Device Development] Formhault:
Well, they didn't pay for Qualcomm Quick Charge either, so...

They want you to use Dash Charge, no matter what. Understandable...
[OnePlus 3 & 3T Cross Device Development] ndarkside93:
That's fair. But usb-PD is an open standard they could've supported that. And what I meant was that most phones sorry a full 2A if not using a quick charger.
[OnePlus 3 & 3T Cross Device Development] Formhault:
I know. Most phones - not OnePlus :silly:

They're trying to force Dash as much as they can. We'd love it if they accepted 5V-3A, but oh well.

Here's hoping they adopt PD and allow the full 20V 5A lol that'd be crazy.
[OnePlus 3 & 3T Cross Device Development] ndarkside93:
That'd be super crazy. But their overlords at bbk/oppo would never allow it
[OnePlus 3 & 3T Cross Device Development] uudruid74:
You only get the extra boost from a dedicated charging port with the feature enabled. It also can't be an Apple charger I don't think.

---------- Post added at 09:10 PM ---------- Previous post was at 09:08 PM ----------

Dash is 5V, up to 4A and its a smarter charge than the high voltage chargers. They actually did dash charge right
[OnePlus 3 & 3T Cross Device Development] Formhault:
Sure it's smart. In a way. But it doesn't do any processing, like OnePlus claimed. The phone still has to convert those 5V down to 4.3V, so, they lied.

It's just that the phone has circuitry efficient enough to not heat up during charge. See the LG G5, for example, it charges fast & doesn't get hot.

If that's what you were referring to with "smart".
[OnePlus 3 & 3T Cross Device Development] joshuous:
The 900 value is coded in the kernel as the max rate from non-Dash charge. I guess it's possible to change that or to add another check for quick charge, but I don't know what the physical constraints are
[OnePlus 3 & 3T Cross Device Development] uudruid74:
Its constantly reporting battery conditions to the charger over the USB connection. People have reverse engineered Dash Charge and its not bad at all.

As for 900mA limit, thats part of the USB spec. Trying to draw more than that can damage the port if its not a dedicated fast charger.
[OnePlus 3 & 3T Cross Device Development] Formhault:
Some USB 3.0 ports don't even push 500 mA, but more like 300 or so. Take, for example, a HP EliteDisplay - it has two USB 3.0 ports in the back and they're weak as hell.

Too bad. Some don't even go with the USB 3.0 spec, which can do 900 mA, as you said. They just slap it on there, paint it blue, and be like "Woo-hoo +$100 cause this is 3.0".

Reverse engineered? Hmm, care to elaborate, please?

My motherboard has one red - fast charging ports on the back of it... Actually, more than one are red, but only one is theoretically rated for "fast charging". It doesn't deliver as much as the front USB 3.0 port in terms of amperage :laugh:
[OnePlus 3 & 3T Cross Device Development] uudruid74:
What backwards bull**** your computer does has little to do with it. A dedicated charger bridges two pins ... I think 4 and 5. Basically grounds a data line. It makes it useless for data but you need a cable that has data lines (no charge-only cables).

Dash Charge ... https://www.google.com/amp/s/xdafor...s/dash-charge-protocol-analysis-t3431917/amp/
[OnePlus 3 & 3T Cross Device Development] Asiier:
Oh man, I wish I could "Thanks" a post twice or more :D

Great work as always :highfive:
[OnePlus 3 & 3T Cross Device Development] pratamaaudi:
waiting for oos version :o
[OnePlus 3 & 3T Cross Device Development] vsot13:
Holy ****! I don't understand 99% of the changelog, but man, whatever you did, this thing is a beast! Flash it on Zenity and it's flying
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
It is on the way, I base it off the the work I do for LOS. There has been major changes of late so I had to test, retest, test that test, test the first test again to make sure of no regressions, etc. I am sure you see where I am going. No point in just running each new build blindly believing that each build can do no wrong. But with that, I am really excited about the new build incoming for OOS. It will be worth the wait.

See above and you will understand my workflows to see how I try to improve each build
[OnePlus 3 & 3T Cross Device Development] Funk Wizard:
1+

Sent from Funk Tuned 3T
[OnePlus 3 & 3T Cross Device Development] SlyUK:
Instead of the RenderZenith kernel included with Zenity RR, you are saying flash Render kernel for more beastly performance ?
[OnePlus 3 & 3T Cross Device Development] SlyUK:
Fair enough. Thanks for the recommendation :)
[OnePlus 3 & 3T Cross Device Development] maxs8007:
Waiting for OOS version update eagerly.
[OnePlus 3 & 3T Cross Device Development] svandasek:
404
[OnePlus 3 & 3T Cross Device Development] Funk Wizard:
Edited | Checked
[OnePlus 3 & 3T Cross Device Development] escorpion_sw:
after 2 hours I got a SOD in zenity rom ?

Sent from my ONEPLUS A3000
[OnePlus 3 & 3T Cross Device Development] lpsld:
I dont really understand how to start with this Kernel, it looks pretty damn good but I just dont know how to get the best out of this Kernel.

Whats Rom do you recommend me (Just need the Battery & Smoothness out of this Kernel).

I'm asking this because there are so much different Versions of this Kernel (f. e. EAS/HMP It looks like HMP is a bit faster but everyone says EAS is muuuch better)

Thank you RenderBroken providing us such a good work and I would be pleased if anyone could help me out :)
[OnePlus 3 & 3T Cross Device Development] AndreiVolk:
I think Josh implemented this kernel in his vertex rom in the best way possible.

On vertex os i got for the first time more than 5h sot with my usage. Usually is around 4h.

And the best part is that i didn't tweak anything, just clean flash the rom :D
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
Hard to help since you are the only one to have ever reported one and you have not provided any logs to back it up. I really need:

/sys/fs/pstore/console_ramoops

See below.

Agree, Vertex is the way to go. This isn't to knock any other rom out there that supports EAS but I have worked hand in hand with Josh on Vertex, I understand the design, I understand the passion so if I am going to make a personal recommendation, there is no contest.
[OnePlus 3 & 3T Cross Device Development] uudruid74:
Could you guys please not quote the entire post?

---------- Post added at 01:21 PM ---------- Previous post was at 01:08 PM ----------

What? Please explain the logic. Flashing erases the previous contents. It doesn't matter what was there before as you've erased it.
[OnePlus 3 & 3T Cross Device Development] Nagi2195:
All developers want their kernel to be flashed over stock. I don't know how it works for you but for me it didn't. So it would be better to flash stock first so that we don't have to face any issues later.
[OnePlus 3 & 3T Cross Device Development] Qliratu:
Is the oos version already available?
[OnePlus 3 & 3T Cross Device Development] Puddi_Puddin:
Patience :)
[OnePlus 3 & 3T Cross Device Development] novas78:
I'm running on Phoenix AEX with latest R7 Walt. This combo is hellishy fast & smooth without any lags. Thanks for your hard work [MENTION=5438598]RenderBroken[/MENTION], you are awesome man.
[OnePlus 3 & 3T Cross Device Development] KaszasM:
Flashing is not erase flashing overwrites the files only with the same name except the updater-script deletes also but thats very rare in kernel zips...

Im not sure how the "data/setting) part works but that could also cause some missbehavior if nowhere else or seemsless but on first boot for sure are errors .or that happened also sometimes in history that the new flashed kernel+app saw the allready undervolted values as stock ,so kernel config app was on stock values or 0 , but it was allready undervolt...
[OnePlus 3 & 3T Cross Device Development] Formhault:
No offense, but I find this post hard to read and understand...

I just know that RenderBroken has advised that we flash the stock ROM's boot.img prior to flashing any custom kernel - if we have flashed a custom kernel already, of course. I believe that is because the kernel flashing affects some files that a boot.img contains, and a boot.img reflash would replace all potentially affected files, so... it's as clean as possible.
[OnePlus 3 & 3T Cross Device Development] KaszasM:
Agree,

No offense but you wear the name of 1 dev in the slim rom team :)
[OnePlus 3 & 3T Cross Device Development] Formhault:
I didn't know, lol. Who?

I just checked their team at http://www.slimroms.net/index.php/team and couldn't find anyone with a similar nick.
[OnePlus 3 & 3T Cross Device Development] KaszasM:
Maybe not there but im pretty sure we had 1 with similar name
[OnePlus 3 & 3T Cross Device Development] Formhault:
How can you know I wear the name of one SlimRoms team member if you don't know his name :laugh:
[OnePlus 3 & 3T Cross Device Development] KaszasM:
In sad than im wrong ,but im sure i saw a dev somewhere in the last 10 years with a similar name ... Could be even formhault74 but ofc you are the FIRST and ONLY Formhault on that planet ;)

Stop OT PLS

good night
[OnePlus 3 & 3T Cross Device Development] Formhault:
Lmao.

Okay. Good night :D
[OnePlus 3 & 3T Cross Device Development] uudruid74:
What? A kernel always comes in a disk image. That will totally erase what is previously on that partition. It's written directly to the partition overwriting everything that is on it. You are spouting off nonsense. The previous contents of the partition are gone. FYI, different ZIP files are flashed differently, but a boot.img is a boot.img.

The previous kernel makes no difference. If you are tuning your kernel with an app, you should know that you need to wipe the app's config data before changing kernels. Changing to the stock kernel is a waste of time and does nothing. The kernel tuning app and its data are not stored on the boot partition. Flashing the stock kernel won't save you from that stupidity.

Second, any user that is undervolting needs their head examined. You really think you know better than the engineers that studied this stuff for years and have official docs from the manufacturer? And before you say "it works for me", yes, it will work 99.5% of the time until some weird condition where a single transistor doesn't quite open in time and you get a CPU error that can be anything from a math error to a system crash ... and you'll be in here telling the Dev that an app crashed and wanting him to fix it. Leave that **** alone! You'll waste everyone's time tracking down a bug that doesn't exist to have 5 minutes longer battery. Uninstall Facebook if you want to save battery. Undervolting is stupid.

SMH.
[OnePlus 3 & 3T Cross Device Development] KaszasM:
[MENTION=5880917]uudruid74[/MENTION]

Calm done, turn the screen off and relax .the devs prefering a rom flash actually before kernel change .why ?i know,and i think u too.if u troubleshoot and experience something aint means that u use that daily. Why Render sad only bootimg i dont know i never wrote that. I dont even have fb and that was not even a bugreport so LOL u are so funny ,and dont forget that if U got a problem with me is still your problem. Good night again
[OnePlus 3 & 3T Cross Device Development] Bearthquake:
Please stop. Don't flood the thread with stupid banter.
[OnePlus 3 & 3T Cross Device Development] joshuous:
1. Never undervolt, especially on EAS kernels. You'll screw up the energy model completely. The energy drain at various frequencies are supposed to be fixed in the energy model packaged in the kernel. Undervolting breaks the model's assumptions, and will lead to incorrect task placement decisions, and possibly lead to more drain.

2. Restore stock kernel's boot.img before you flash a custom kernel. For added safety, dirty flash the ROM first. Custom kernel zips consist of a zImage file, which is the compressed standalone kernel, (as well as some extras). However the zips can also be made to replace other files such as:

- system blobs ( [MENTION=5438598]RenderBroken[/MENTION] does this in his OOS kernel to replace the libcutils.so blob in system/..)

- ramdisk files: many kernel devs replace this. It contains the init scripts that changes how booting process works and various kinds of services that start up. [MENTION=5438598]RenderBroken[/MENTION] and I change this with our kernels. We use it to create EAS and Vox tunables, and enable spectrum support (See image attached for example. I replace init.qcom.power.rc and add init.spectrum.rc).

Restoring your boot.img will restore the zImage and ramdisk back to stock. Dirty flashing a kernel will only replace zImage, and whatever ramdisk files the custom kernel dev chooses to replace. If I don't restore boot.img and I dirty flash all kinds of custom kernels, my ramdisk files may be messed up (I may end up with several init.*.rc scripts from different devs!). So please restore boot.img at the very least first. However take note that restoring boot.img will not replace the system blobs, that's why you should dirty flash the entire ROM if you want to be safe (for OOS at least).

To see what files are replaced, open up the kernel zip and look inside ramdisk or system folders. If system files are replaced, dirty flash the ROM first. Otherwise restoring boot.img will suffice.

Please read this carefully and remember this, because unfortunately the majority of users don't know how this works, and it would help if you guys can educate the community.
[OnePlus 3 & 3T Cross Device Development] Bearthquake:
You're the man! Easily my favorite developer
[OnePlus 3 & 3T Cross Device Development] Navi44:
Under clock or under volt, I think user can't touch voltages. Just frequencies
[OnePlus 3 & 3T Cross Device Development] Puddi_Puddin:
Under clock he means I think.
[OnePlus 3 & 3T Cross Device Development] joshuous:
Undervolting I mean
[OnePlus 3 & 3T Cross Device Development] arifqur:
[MENTION=6745491]joshuous[/MENTION] you gave a very thorough explanation. No room left for any doubts. Great job man.
[OnePlus 3 & 3T Cross Device Development] Balino:
Will this boot on ob9? R1 was not booting at all. Thank you for your work man

Booted up Just fine
[OnePlus 3 & 3T Cross Device Development] sjknight413:
Could anybody clear some stuff up for me?

I'm a newish Oneplus 3T user that wants to flash this kernel on top of Joshuous' Vertex OS. His rom is based off of AOSP and CAF I believe, so would I flash the OOS or LOS version?

Second, what is the difference between WALT and PELT, I don't see anything in the OP about the two.

Thanks in advance!
[OnePlus 3 & 3T Cross Device Development] mady51:
U can flash it. Walt n pelt r 2 diff flavors and dev is experimenting. Dev suggest for Walt i think
[OnePlus 3 & 3T Cross Device Development] Bearthquake:
Pelt is apparently more battery friendly.

I noticed on pelt that the maximum cpu frequencies are lowered quite a bit, so that's where the battery saving partially comes from I assume. Walt all the way though for better performance all around
[OnePlus 3 & 3T Cross Device Development] genuine55:
Yes after a clean flash of rom let it boot up first then go back to recovery then flash the kernel wouldn't boot after straight flashing after rom had to let it boot up first.
[OnePlus 3 & 3T Cross Device Development] Rawwrius01:
Pelt won't boot on latest vertex. Anyone experience the same problem ?

Gesendet von meinem ONEPLUS A3003 mit Tapatalk
[OnePlus 3 & 3T Cross Device Development] vsot13:
Are sure you flashing the right version?
[OnePlus 3 & 3T Cross Device Development] fcisco13:
Did you by any chance dload the OOS version?? Wouldn't hurt to double check and flash rom then correct kernel version.
[OnePlus 3 & 3T Cross Device Development] multi_rom_user:
Also try flashing vertex, boot it fully and set it up, then reflash render kernel.
[OnePlus 3 & 3T Cross Device Development] Skinpipe:
When you flash render kernel, the voxpopuli is still active you have to manually disable it, personally I think it's too aggressive and makes the phone warm, render Walt is smooth without touch boost
[OnePlus 3 & 3T Cross Device Development] Bearthquake:
I've noticed it gets warm and drains battery when browsing internet and watching YouTube, how do you disable it? And would that help?

Edit: think I found it under /dev folder in "enable input boost" file. I just changed it to 0 for disable touch boost
[OnePlus 3 & 3T Cross Device Development] sushobith:
[MENTION=5438598]RenderBroken[/MENTION] will this work on open beta ?

Eas won't work on oos right ?

Why is it named oos n eas ?
[OnePlus 3 & 3T Cross Device Development] Bearthquake:
Read and search. Your answer is in some recent pages of this thread.