yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] F3ELING1337:
But are there some tuneables to make it less aggressive? Or to tweak the governor itself? I tried a lot of Vox Populi but that doesn't tackle the high frequencies. I don't know how accurate android battery statistics are but in my opinion it is kind of extreme that ~10min browsing consume 300mAh and ~210min screen on the same amount. It's kind of funny because using the kernel feels really good and idle drain is superb with ~3% over a whole night but active drain seems to be relatively high in my scenario.
[OnePlus 3 & 3T Cross Device Development] Puddi_Puddin:
You could play with the schedutil settings.

Start with:

Up rate: 500

Down rate: 16000

(both clusters.)
[OnePlus 3 & 3T Cross Device Development] uudruid74:
I thought this would let it ramp up really fast and stay there.
[OnePlus 3 & 3T Cross Device Development] F3ELING1337:
Thank you for your suggestion but sadly it doesn't solve my problem:(
[OnePlus 3 & 3T Cross Device Development] cet90:
hi stupid question, is renderzenith working for OOS based rom?
[OnePlus 3 & 3T Cross Device Development] Puddi_Puddin:
No only Render Kernel itself. There are different options for OOS and LOS. Personally I recommend to switch to a EAS supporting rom
[OnePlus 3 & 3T Cross Device Development] krish@3T:
Oreo is under progress or haven't started ?
[OnePlus 3 & 3T Cross Device Development] Zielony360:
Is R2 compatible with OOS 4.5.0? [MENTION=5438598]RenderBroken[/MENTION] are you going to update kernel for OOS, especially with new kernel sources?
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
We are currently working on EAS for OREO. Sorry for the wait guys. I am sure it will be worth it though!
[OnePlus 3 & 3T Cross Device Development] SynaTech:
(deleted)
[OnePlus 3 & 3T Cross Device Development] krish@3T:
Los-O waiting ???
[OnePlus 3 & 3T Cross Device Development] ElementRn:
Good things need time.
[OnePlus 3 & 3T Cross Device Development] sazzadtanim007:
[MENTION=5438598]RenderBroken[/MENTION]

Missing render kernel in my op3t 4.5.1 ????.
[OnePlus 3 & 3T Cross Device Development] multi_rom_user:
He's been super busy getting latest blobs for many devices and put more together. Let's remain patient.
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
I have finally finished my other endeavors and will be focusing on the op3(t). I am excited to show you guys what [MENTION=6745491]joshuous[/MENTION] and I have in store for you all. We have been planning our o-eas work for sometime now and I feel confident that we will surpass what we did on N. I appreciate the patience from everyone while allowing us to pursue our projects in peace. It just goes to show that we have the best community out there.

Soon....

;)
[OnePlus 3 & 3T Cross Device Development] ElementRn:
Exciting times to be alive.
[OnePlus 3 & 3T Cross Device Development] cet90:
awaiting your OOS OREO EAS kernel :)
[OnePlus 3 & 3T Cross Device Development] crian:
Soon™
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
The new EAS-Oreo bringup is going very well. I should be done with the removal/cleanup process. It is still very much a work in progress but this is the first run or cleanup/removal:

[staging 608c439] 8996-EAS-O: Rollback CAF EAS/HMP Changes

49 files changed, 669 insertions(+), 39978 deletions(-)

Soon. . . .er. . . .
[OnePlus 3 & 3T Cross Device Development] Mostafa Wael:
Holy damn! That's quite a lot!
[OnePlus 3 & 3T Cross Device Development] Puddi_Puddin:
Dayumm boii. Hyped af
[OnePlus 3 & 3T Cross Device Development] DIDODa96:
Any news? Can't wait ?
[OnePlus 3 & 3T Cross Device Development] vsot13:
Turn on your TV [emoji16]
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
Been busy with work lately so still working on fixing build errors. Once all build errors are done, I will working on booting properly. If all is well, I will then work on fixing up other subsystems to make them compatible with the EAS changes made. Then I will cleanup all my commits made and make them so that they are topic branches for other devs to port EAS over to other 3.18-CAF-Oreo device kernels. Once the base is 100% I will then focus on pulling in just the right features.
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
All build errors fixed! Now on to cleanup.

Soon . . .er . . . .still
[OnePlus 3 & 3T Cross Device Development] doubleaykay:
Got a DevDB update notification but nothing has changed! What do you have in store for us [MENTION=5438598]RenderBroken[/MENTION]? Haha
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
MY bad, updated logo for staging for new release
[OnePlus 3 & 3T Cross Device Development] Bryandu13:
Hyped for the Oreo version !
[OnePlus 3 & 3T Cross Device Development] ContinuUE:
Is the latest update in August 14th, please? I'm looking forward to your update
[OnePlus 3 & 3T Cross Device Development] jasio2k:
Hi

The most recent one is RenderKernel-OP3-LOS-N-EAS-R8-PELT or I wrong ? Thx
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
Yes, that is the latest but I would refrain from flashing it.

My Oreo EAS bringup is going well. I thought I would get more dont during the break but my loaner laptop has a crappy keyboard. . .so its severely hampered what I can do and wont be back home till at least the 2nd. I have been able to get the kernel to compile without errors so now just finalizing a few things.
[OnePlus 3 & 3T Cross Device Development] Bryandu13:
Thanks for keeping us updated ! Good luck to the finalization !
[OnePlus 3 & 3T Cross Device Development] Aasresh:
Oreo EAS waiting for it badly.
[OnePlus 3 & 3T Cross Device Development] iceman0826:
I wonder what happened to the keyboard ?
[OnePlus 3 & 3T Cross Device Development] sazzadtanim007:
Are you working on OOS-oreo for op3/t ?@RenderBroken

Thanks.
[OnePlus 3 & 3T Cross Device Development] Aasresh:
Release for op3 too pls
[OnePlus 3 & 3T Cross Device Development] Puddi_Puddin:
He is, give him the time he needs. There are alot of great things comming soon!
[OnePlus 3 & 3T Cross Device Development] iceman0826:
Even if it takes another year, we will. ?
[OnePlus 3 & 3T Cross Device Development] joshuous:
Hopefully not that long ;)
[OnePlus 3 & 3T Cross Device Development] Bryandu13:
Better to wait for something perfect than something who'll need updates to work.
[OnePlus 3 & 3T Cross Device Development] joshuous:
Yes, that's the way [MENTION=5438598]RenderBroken[/MENTION] and I prefer to do our releases
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
I have done all the hardest part of the merge work. But I have an issue and is causing the build to not boot. I also have just been busy and haven't had the time to diagnose the issue much further. I am not putting anyone down when I say this but the work [MENTION=6745491]joshuous[/MENTION] and I are doing isn't just adding in some governors, pulling some patches from CAF. Its an entire re-work of an integral part of the Android Kernel. Just takes time.
[OnePlus 3 & 3T Cross Device Development] :
Thanks for keep us updated!
[OnePlus 3 & 3T Cross Device Development] Bryandu13:
The bests comes last.
[OnePlus 3 & 3T Cross Device Development] Skinpipe:
hi i have a oneplus 5t and a 3 do you think that raising the min freq and disabling touchboost of the 3 could be beneficial?

just wondered if you had an opinion on this, ive just made the changes to my 3 so ill find out i guess
[OnePlus 3 & 3T Cross Device Development] smitmakani:
No worries,

We are waiting for your best Kernel.. ;):o
[OnePlus 3 & 3T Cross Device Development] iceman0826:
The longer it takes, the better - just like a fine wine :)
[OnePlus 3 & 3T Cross Device Development] Flasher8:
Anyway I can download the kernel? The link not working.
[OnePlus 3 & 3T Cross Device Development] sazzadtanim007:
Is this project alive ? [MENTION=5438598]RenderBroken[/MENTION]
[OnePlus 3 & 3T Cross Device Development] ContinuUE:
When I play games with your kernel on oos, I often get stuck, is your setup really makes the cpu very lazy? Or my own cell phone problem?
[OnePlus 3 & 3T Cross Device Development] Aasresh:
Yea for op5
[OnePlus 3 & 3T Cross Device Development] Bryandu13:
RIP
[OnePlus 3 & 3T Cross Device Development] iceman0826:
Relax, it will be ready by last quarter of the year ?
[OnePlus 3 & 3T Cross Device Development] joshuous:
That's a target we should be able to meet. I'm currently focused on ROM development for op3 and will begin kernel work once ROM has stabilised
[OnePlus 3 & 3T Cross Device Development] Rhodesgod:
nice nice.we are waiting here :D:good:
[OnePlus 3 & 3T Cross Device Development] fapste:
[MENTION=5438598]RenderBroken[/MENTION] waiting for your awesome EAS implementation is torturous.
[OnePlus 3 & 3T Cross Device Development] Bryandu13:
Someone said project is dead. He's working on OP5 now.

And it seems obvious because the OP isn't even responding to all those messages.
[OnePlus 3 & 3T Cross Device Development] iceman0826:
I remember he says about releasing it on 3rd or 4th quarter of the year. Glad we have other kernels to use while waiting.
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
Thanks for your patience. My time has been cut very short the past few months. I had started on the kernel for the OP3 and came to an impasse. Just need to find time to get through it as 90% of the work is done already.

I try to respond to @'s as I haven't had enough time to troll through threads for a while now.
[OnePlus 3 & 3T Cross Device Development] Bryandu13:
Good news so
[OnePlus 3 & 3T Cross Device Development] uudruid74:
Curious what the impasse was and if there is any way for someone to help (at least a few would volunteer to be slaves), maybe offload some of the tedium or provide an alternative viewpoint. Often we get too close to something to really see it from all sides.
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
I appreciate the support and the offer! I believe I found the issue. I had made changes to the device tree which cause the build to not boot. Sometimes you have to step back from something and come back to it later. I have been able to make adjustments and will be testing in the next few days. Finishing an OP5 release we have been working on and then will focus on getting out test builds for the OP3. Once I am happy with the first test build, I will release it here.
[OnePlus 3 & 3T Cross Device Development] Bryandu13:
Very cool info, I don't want to spam questions but for witch ROM this kernel will be ?
[OnePlus 3 & 3T Cross Device Development] mani169:
Can anybody share their ex kernel manager tweaks that increase the battery life. I have flashed this kernel on my OP3. I am using helix engine with this kernel but not so good so far. Can any body tell me their settings which i can also implement on kernel manager as i am seeing that many of you are getting sot of 4-5 hours but i am not able to touch 3. Thanks. ;)
[OnePlus 3 & 3T Cross Device Development] nexus_vl:
You shouldn't use Helix engine with an EAX based kernel.
[OnePlus 3 & 3T Cross Device Development] Sam Nakamura:
I think the Helix Engine OP states that it works regardless of EAS / HMP on any kernel... It's not AKT anymore
[OnePlus 3 & 3T Cross Device Development] joshuous:
Seems like we'll be one quarter ahead of schedule ;)
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
Hell Yea, we have our base done. Testing atm. [MENTION=6745491]joshuous[/MENTION] has done an amazing bringup for our beloved OP3. We are bringing some of our best work to the op3 and now that the base is pretty much done, we will be updating on a more regular basis.

I am sure once we release, for those devs out there interested, we should have a repo that is just of our clean eas commits. This way others will be able to do an eas bringup for other 3.18.x devices.
[OnePlus 3 & 3T Cross Device Development] Racpu_:
The party will start..:D

Thanks [MENTION=5438598]RenderBroken[/MENTION] and [MENTION=6745491]joshuous[/MENTION]
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
I just appreciate everyone's patience. I am certain the wait will be worth it.
[OnePlus 3 & 3T Cross Device Development] Racpu_:
We are all thankful for the great work
[OnePlus 3 & 3T Cross Device Development] FSadino:
That's the true spirit of open source. Thank you for keep it on XDA community :good:
[OnePlus 3 & 3T Cross Device Development] arifqur:
Waiting patiently for the new gem of a kernel
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
Guys, it has been my pleasure to develop and grow with you all. I have become a better dev and hopefully you all have become better users/tester/developers as well. That is the whole point of the projects [MENTION=6745491]joshuous[/MENTION] and I create. For everyone involved to learn and grow. To start a dialogue. To ignite a spark in you to start your own development project. Well when one door closes, another one opens. We will see you on the other side!

Kind Regards,

Zachariah
[OnePlus 3 & 3T Cross Device Development] Puddi_Puddin:
Thx! Great work.
[OnePlus 3 & 3T Cross Device Development] Konskl:
Yebi couldn't resist the temptation so i gave it a try yesterday....it works great :D open betas are the community builds from oneplus! It works great!!! Really smooth ;) I'll give it a couple of recharge cycles on its own to check the battery life and then try a profile ? btw in r2 is it possible to implement the gpu boost feature found in elementalx kernel? Ty for r1 !!! It's working great ;)
[OnePlus 3 & 3T Cross Device Development] Durrz:
Running on Freedom 1.7. So far so good! Snappy, and great battery life even with LTE on most of the time.
[OnePlus 3 & 3T Cross Device Development] Mistertac:
I'm also running this on Freedom Open Beta 7 and so far so good. Thanks for sharing.
[OnePlus 3 & 3T Cross Device Development] Mostafa Wael:
Yep, T70 is so much faster than anything else for me. Enjoy it :)
[OnePlus 3 & 3T Cross Device Development] Roykooiman:
U mean faster then Ex, Franco, Bluspark?
[OnePlus 3 & 3T Cross Device Development] Puddi_Puddin:
Franco and Render are my fav here now!. Both are so smooth.
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
I am curious to know as well because those three are ppl I have looked up to since starting out. It is amazing how easily things are for me know compared to when I first started. I remember when I Was trying to figure out how to cherry pick. lol But when I did, I was able to release KK on my old Captivate when we were doomed to just be stuck on JB.
[OnePlus 3 & 3T Cross Device Development] vatsal8286:
R1 is the stable build non EAS right?
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
Correct.

There are too many Rom side changes to be made to use EAS properly. So it has been sidelined for now.
[OnePlus 3 & 3T Cross Device Development] Jole7:
Thanks for the kernel any plans to make a Cm14.1 kernel?
[OnePlus 3 & 3T Cross Device Development] Mostafa Wael:
put in the words of Francissco himself

"..Don't be that guy"

:D :angel:

---------- Post added at 05:54 PM ---------- Previous post was at 05:53 PM ----------

there are plans to support Nougat when it gets mature

by the time, this kernel will have more goodies :cowboy:

oh and btw, RC4 and RC4.1 are out, and i am making an RC5 as well ;)
[OnePlus 3 & 3T Cross Device Development] habylab:
Working really well but the WiFi isn't working for me. Did you use Osmosis updates to Any Kernel in this?

I'll flash back to stock and reflash. Otherwise smooth as silk :)
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
I use a modified version of his AK. When you flash my kernel it cleanrs out all modules from Host and then pushes my included Wifi Module. No one else has complained of such a problem so I am inclined to think that its something on your end. Can you tell me what kernel you were running before that you flashed mine on top of? Would be nice to know if I need to make further adjustments to my scripting to account for host changes.

I always let the stock rom and kernel boot first then go back into TWRP and backup /system and /boot. This way I can always make sure to have a clean flash when flashing 3rd party kernels and add ons.

Thanks for the report!
[OnePlus 3 & 3T Cross Device Development] habylab:
Bluspark. I have flashed to stock and back again, now working well.
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
Thanks for letting me know! I will take a look and see what the exact cause is then
[OnePlus 3 & 3T Cross Device Development] daothanhduy1996:
Because Bluspark used the systemless method to inject the wifi driver. So that if we flash ur kernel over Bluspark, it would also inherit the symlink to the bs's wifi driver instead of yours :) since your kernel is using any kernel method
[OnePlus 3 & 3T Cross Device Development] MrVoshel:
Tried with a clean flash, still no wifi >.>
[OnePlus 3 & 3T Cross Device Development] habylab:
Flash stock kernel first.
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
That's it! Thanks. I should be able to account for it in R2
[ZenFone 2 Q&A, Help & Troubleshooting] mudit99:
I was switching back to stock ROM from Resurrection Remix M on my ZE550ML because I wanted to update the firmware so that I can install Cyanogenmod 14.1. After I downloaded the firmware zip file from Asus, I copied the recovery.img, boot.img, and droidboot.img files. I rebooted my phone into the bootloader and flashed each file using fastboot flash. After this was done, I rebooted into recovery, but it never got to that point. Now my phone's stuck on the Asus Logo screen. I tried the key combination to boot into bootloader or recovery, but that didn't work. Neither adb nor fastboot can detect my phone. I don't know what to do. I looked at tons of posts, but nothing can help me. Any ideas that can help are appreciated. I'm in a pickle right now.
[One (M9) Q&A, Help & Troubleshooting] cedricpixler:
Hello everybody :cool:

I'm the owner of a HTC One M9 and I really love it! I'm kind of newbie on Android.

This is my case, I can't upgrade my firmware to 6.0.1 (or later) I'm still on Android 5.0.2 and I tried to install a cyanogenmod firm that kind of fit with my model... BUT! it start to have some many problems.. like the display starts to break the images and start to repetitive the image like an a glitch... when a phone call comes it turn off or restart it was like a dead phone... Then I install a MaximusHD 1.0.0 and it come back the same way it was but it returns to Android 5.0.2... I already unlock my phone and it's S-OFF via sunshine...

So, If you have some info that help me fix this (upgrade to Android 6.0.1 or later) or you have the same experience please leave your comment!

My data:

MODEL: htc_himawl

CID: LRA_001

MID: OPJA30000

Cheers!

Alvaro
[One (M9) Q&A, Help & Troubleshooting] Kartoffelrudi:
Boot your phone into download mode, connect it to your computer and make sure ADB and FASTBOOT drivers are installed and working.

To ensure your device is connected, type "fastboot devices".

Your Bootloader needs to be unlocked, this is done with "fastboot oem unlock".

First step: Change your CID to SuperCID "fastboot writecid 11111111"

Second step: Change your MID to 0PJA1100 "fastboot writemid 0PJA1100"

Third step: Flash latest RUU for developer edition. To make sure you have the right RUU, usually it is x.x.617.x.
[One (M9) Q&A, Help & Troubleshooting] Flippy498:
Please don't give such advise if you don't know what you're talking about. The OP owns a CDMA device and the dev firmware is GSM. GSM and CDMA aren't compatible and you can't convert the one into the other due to their different partition layouts. In the worst case this can lead to unrecoverable damages.

Edit: This post isn't meant to be an offense. I just want to prevent the OP from doing something he/she could regret afterwards.

Edit 2 [MENTION=7881233]cedricpixler[/MENTION]: You'll need a windows PC if you want to use the following instructions. Win 10 and 8 (or 8.1) might not work whereas win 7 is always fine. I'm using win 10 myself without any problems but others have been reporting that they needed to use a win 7 PC.

Charge your phone to at least 50 %.

Go to HTC's US website and download the latest RUU for your SKU. Your current firmware is stated in Download Mode in the line that starts with "OS". The SKU are the numbers behind the second dot of the firmware version.

If not already done you should download and install the HTC Sync manager. Uninstall it directly, afterwards. This way you update the needed drivers to the latest version. If you keep the manager you might face some connectivity issues during the upcoming steps. Next you need to boot your phone to Download Mode and to connect it via USB (if possible use a 2.0 cable and port instead of 3.0) with your PC.

Disconnect your PC from the internet. Disable your antivirus program and your firewall and execute the RUU as an admin. In some cases the flashing process might take some time so don't worry if it hasn't finished after 10 minutes.

When the RUU has finished you can re-activate your av program and your firewall. Afterwards you can re-connect your PC with the internet. Your phone should be up to date now.

Not every step is actually essential but if you follow these instructions the most frequently occurring problems should be prevented.

Sidenote: Every problem you faced with custom roms is based on the difference between your current firmware and the base of the mentioned roms.

If you want to use a sense-based custom rom after you updated your firmware you need to re-flash the stock boot.img of your firmware after you flashed the rom. For non-sense-based roms like CM you need to flash thicklizards mono kernel. If you don't do this your phone won't recognize your sim card.
[One (M9) Q&A, Help & Troubleshooting] cedricpixler:
Thank you [MENTION=5872674]Flippy498[/MENTION], I will take this steps you write and I will write here the results.

Somebody from LlaTooFer Maximus was helping me and send me this

"Well, your device is not capable with my custom rom due to different hardware. I recommend you to install Viper ROM prior that you need to update CID to VZW__001 and flash this full firmware https://www.androidfilehost.com/?fid=24651430732237625

After that you have to flash this RUU https://www.androidfilehost.com/?fid=24651430732238098

Once you do that you can install custom twrp recovery https://dl.twrp.me/hima/twrp-3.0.2-0-hima.img.html and custom rom http://xdaforums.com/one-m9/development/rom-viperonem9-1-0-0-tweaks-hub-t3072773

Make sure you set Verizon during installation."

I tried the first step (installing the full firmware but this error comes up "C:\Program Files (x86)\platform-tools>fastboot flash zip 3.37.605.13_FULL_firmware.zip

target reported max download size of 800000000 bytes

sending 'zip' (41818 KB)...

OKAY [ 3.430s]

writing 'zip'...

(bootloader) HOSD CL#523158

(bootloader) ERR CID not matched

(bootloader) ERR [SD_UPDATE_ERR] CID NOT ALLOWED

(bootloader) ERR [SD_UPDATE_ERR] sddownload failed: 7

(bootloader) ERR Update zip file failed.

(bootloader) Update zip file OK

(bootloader) ERR ZIP ERROR CODE, 7

(bootloader) end@Done

FAILED (remote: 7: fail to flash via downloadzip)

finished. total time: 4.567s"

But they or he doesn't tell me whats going on.... or what to do next.. [MENTION=5872674]Flippy498[/MENTION] do you know if this instructions could help to change my CID or MID..? and If my phone is CDMA can I re Write the CID or MID