yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] RenderBroken:
R10 is HERE!!!

Download

Changelog:

R10

1003423 (HEAD, origin/cm-12.0, origin/HEAD, cm-12.0) ARM: dts: A0001: Update Truly panel commands

0703073 synaptics: Update firmware to 14001227

187fd9b (r10) Build-AnyKernel: Use new Self Compiled Uber Toolchain (4.9.3)

cb4b6fa wlan: Fix for dead lock during cancel ROC.

5ae54ba wlan: Synchronize cancel remain on channel and ROC expiry.

d08697e prima: Update to LA.BF.1.1.1_rb1.20

42c440c Defconfig: Disable CONFIG_SUSPEND_TIME * This does not work on QC devices and will always report as zero.

1c19f54 msm: mdss: update max fence wait timeout for all acquire fence

b605ecf msm: mdss: Adjust fence timeouts

adab6f5 mdss: fb: wait for idle only on last fb release

2ef069c mdss: dsi: fix potential race conditions in mdp busy wait

b8dea7a sps_bam: Fix Build Error

3c37f74 msm: sps: Squashed commit of upstream changes

9565c9f msm: camera: ispif: Validate vfe_intf parameter

168b817 msm: camera: add check for csid_cid to prevent of overwrite memory

9bcffd6 mmc: core: update host->card after getting RCA for SD card

8f47227 ARM: dts: msm: update the DSI PHY lane configuration settings

7f62ef0 sched: Remove one division operation in find_busiest_queue()

a73ca04 sched: Update cpu load after task_tick

5128fe80f ARM: dts: A0001: Update Truly panel init sequence
[ONE Original Android Development] NikoZBK:
As Austin Powers would say... yeah baby!
[ONE Original Android Development] kalpik:
Bootloops at the OnePlus screen for me :(

Sent from my A0001
[ONE Original Android Development] mnhs1010:
Latest R10 causes bootloop on my euphoria 3/5 , R9 was working well.
[ONE Original Android Development] RenderBroken:
Dont see how as I use the same build but hang tight and I will take a look . . .
[ONE Original Android Development] HAvoktek:
How the hell is my Avatar showing up on this post?!?
[ONE Original Android Development] NuLLV01D:
The 14/05 Nightly of CM had Major Ramdisk Changes. Thus, Any ROM before 14th will most likely not boot up
[ONE Original Android Development] kalpik:
Thanks! Sitting tight till you figure it out ?

Sent from my A0001

---------- Post added at 08:16 AM ---------- Previous post was at 08:16 AM ----------

Shouldn't matter with anykernel.

Sent from my A0001
[ONE Original Android Development] RenderBroken:
Most times not but with the crap like Transparent Compression, you never know lol. I do know that a test build I used since yesterday boots fine. It has all but the latest two changes from CM. I merged the last two, booted and had been running with it for a couple hours with no problem thus releasing the build. Then I rebooted to see if I can get it to not boot and finally ran into an issue. Still looking into it

Still looking into it but wont release a new build tonight. Need to relax before bed so I will continue tomorrow. Thanks guys. Another Example that not all phones are created equal. It booted fine for me but after the 3rd reboot it looped. So I dont know. The only difference was the new TouchScreen drivers and some panel updates. Maybe CM has more to push through.

EDIT#2

I was able to flash Euphoria 5/3 over my borked rom of Euphori 5/4 to restore the ramdisk and boot.img. Then flashed R10 again and its working fine again. lol who knows.
[ONE Original Android Development] endriuss:
I'm using the latest Euphoria 5/3 with April 9th firmware and Oxygen modem. I was before on R9. What I did was simply delete Synapse folder, clear Synapse data/cache, reboot to recovery, flash Render UKM 3.8.1.4, R10 kernel, UKM once again and rebbot to system without any single issue:) I've limited max CPU to 1958 MHz and disabled CPU boost - what a speed! I don't have any single lag and everything is fluid as a hell! Another masterpiece! Thank you [MENTION=5438598]RenderBroken[/MENTION] for your great work and your effort!
[ONE Original Android Development] Norapapa:
The Link is down
[ONE Original Android Development] kalpik:
There's a problem with the kernel, so it was probably pulled. Wait for an update :)
[ONE Original Android Development] Upakul:
Touchscreen firmware added?
[ONE Original Android Development] zedbg:
Dont bother reading the changelog, asking is faster
[ONE Original Android Development] RenderBroken:
You are right, though it works for me, two ppl complaining of bootloops is not something I want to see over and over. And I really dont know what blew up either. I am sure when I can dig into it later today I will find something out. I believe my issue was caused when I accidentally booted my "second" rom in multirom and forced it off while it was booting. After that everything was borked so I don't know if that was the kernel or something else.

I was thinking about releasing R10 as a test build to see if others are having issues. Thanks.

I left it out specifically. (Not really ;) )
[ONE Original Android Development] kalpik:
I'm not running multirom, just so you know :)
[ONE Original Android Development] RenderBroken:
I didn't think so. You seem knowledgeable so I gave your report more credence. Thanks for letting me know.
[ONE Original Android Development] RenderBroken:
Here is R10-T2:

Download

I need to see if more have the same boot loop issue or not. Any help would be appreciated!
[ONE Original Android Development] kalpik:
Still the same ?

Sent from my A0001
[ONE Original Android Development] :
Still bootloop using exodus
[ONE Original Android Development] RenderBroken:
can you guys go through the process you take to flash?

I did a clean flash of Euphoria 5/3 and set it all up along with restore my apps. I then made a backup in TWRP, flashed R12-T2 and it boots fine. . . lol
[ONE Original Android Development] kalpik:
Well, I'm on flex os, and not euphoria. This is the process I follow:

1. Wipe /system

2. Flash ROM (flex os in this case)

3. Flash gapps (banks)

4. Flash kernel

5. Flash supersu

Sent from my A0001
[ONE Original Android Development] smoki3:
Have you tried a clean flash? (wipe data also)
[ONE Original Android Development] kalpik:
Why should it matter? It's just getting stuck at the OnePlus screen. Also, other kernels work fine.

Sent from my A0001
[ONE Original Android Development] smoki3:
booting fine for me on cm-12.1
[ONE Original Android Development] :
I just flahed r10 with TWRP, i've been using exodus a couple of days... I havnt done nothing special... ?
[ONE Original Android Development] Renosh:
[MENTION=5438598]RenderBroken[/MENTION]

Isn't this the cause of the boot-loops?
[ONE Original Android Development] kalpik:
Not applicable to anykernel based kernels.

Sent from my A0001
[ONE Original Android Development] HaTrED_:
+1 on that boot looping thing under RobbieL811's Uber CM12.1 :(:crying:

Edit: no such thing as F2FS here...
[ONE Original Android Development] LiquidSolstice:
I'm on the latest Euphoria, and have been for three builds. Each time, I've been flashing your kernel releases on top.

R10-T2 was no different. Flashed over R9 and I booted just fine. I didn't try the official R10 before you pulled it.
[ONE Original Android Development] RenderBroken:
Have you tried flashing R10+?
[ONE Original Android Development] HAvoktek:
[MENTION=5438598]RenderBroken[/MENTION] I'm on Temasek 11.v4 running the R10T2, no bootloops here, no issues....as of now
[ONE Original Android Development] Norapapa:
R10T2 works fine with the euphoria from 3.5, no bootloops
[ONE Original Android Development] RenderBroken:
Those having issues with R10. Are you using F2FS?
[ONE Original Android Development] Gusy_80:
SlimSaber 20150415 (fusionjack) + R10T2 = bootloops.

Enviado desde mi OnePlus One
[ONE Original Android Development] smoki3:
Tried it on every ROM I have on my phone. Every ROM is booting.
[ONE Original Android Development] MexiDroid:
Hi, has the r10 the latest driver from synaptic? ?
[ONE Original Android Development] schaggo:
Stop asking. Start reading. http://xdaforums.com/showpost.php?p=59358678&postcount=2

---------- Post added at 21:14 ---------- Previous post was at 20:59 ----------

Default CM12.1 nightly from today (15.05) boots up fine.

Downloaded using OTA updater, stock default build.
[ONE Original Android Development] ak0r:
With SlimSaber(fusionjack) no issues... Running smooth... Obviously dirty flashed :D
[ONE Original Android Development] MexiDroid:
There is no links to download r10....
[ONE Original Android Development] ak0r:
Here you go...
[ONE Original Android Development] schaggo:
OMG :eek:

OMG :eek:

Is there a lazier pack than you guys?
[ONE Original Android Development] RenderBroken:
Ma head jus 'sploded lol

Yes, its in R10.

OK, I have been looking at my source and it all looks fine to me. I really don't have anything that could have caused such issues but I did build R10 using a new tool chain I self compiled. I built this next build with the other toolchain to see if that was somehow the cause.

R10-T3
[ONE Original Android Development] LiquidSolstice:
:( I updated from R10-T2 to T3, and I'm bootlooping. I tried flashing back to T2 and I'm still bootlooping.

Is there any relevant logging information I can provide you?
[ONE Original Android Development] RenderBroken:
Not really but thanks, I dont know what the cause is. Especially since it works for me an others on the same roms it doesn't work for some. IDK but the problem is already getting old. . .
[ONE Original Android Development] LiquidSolstice:
Do you think perhaps I should just wait for an update to Euphoria that syncs up with the rest of CM first?
[ONE Original Android Development] Gusy_80:
SlimSaber 20150415 (fusionjack) + R10T3 = running smooth

Enviado desde mi OnePlus One
[ONE Original Android Development] LiquidSolstice:
Wow, okay, this is weird. I did the whole "Flash with TWRP & PowerOff first before rebooting" trick and now I've booted with R10-T3.

I don't understand why though?
[ONE Original Android Development] RenderBroken:
Thing is, I am using Euphoria 5/3 with R10. I am not having any issues. So thats why its confusing. It should also work for everyone else.
[ONE Original Android Development] LiquidSolstice:
Yeah, I can now confirm; turning the phone off from recovery right after flashing (instead of immediately rebooting) seems to have done the trick. I just rebooted the phone 4 times over to see if it would loop, and it continues to boot fine.

Mind boggled.
[ONE Original Android Development] kalpik:
Weird! Really weird!

Sent from my A0001
[ONE Original Android Development] MexiDroid:
i have bootloop with R10 T2, and i read if you turn off after flash, then there is no bootloop,

so sad because my OPO is building the ART and im on CM 12.1 nightly from today (i reflash it again in order to boot)

---------- Post added at 01:47 PM ---------- Previous post was at 01:41 PM ----------

its funny how you guys an experimented users, quoted my post to say nothing, really i search but maybe i did a "lazy" search, somepeople like to help, and i appreaciate that :)
[ONE Original Android Development] HaTrED_:
This is some crazy sh!!!t!!!

Tried again and flashed R10-T2 but this time now i have performed a power off in recovery! Guess what? It booted!!!! :confused::confused: :p:p :confused::confused:

Could it be, somehow, recovery related?

I'm using this one: http://xdaforums.com/showpost.php?p=60525330&postcount=482
[ONE Original Android Development] kalpik:
I'm using official TWRP, so that rules it out ?

Sent from my A0001
[ONE Original Android Development] LiquidSolstice:
Yep. Latest official TWRP here as well.
[ONE Original Android Development] Flak:
I picked up the reboot to recovery thing back on the EVO after flashing kernels. Probably why I never experienced it either.
[ONE Original Android Development] JRyu:
I can't find the R10, where is? ahah
[ONE Original Android Development] ak0r:
Strange, I didn't turned off. I am using multirom recovery. But still I got it booted without issues.
[ONE Original Android Development] endriuss:
I'm using the same the latest unoficiall twrp from katinatez and I've never ever experienced any bootloop flashing [MENTION=5438598]RenderBroken[/MENTION]'s kernel. So the version of TWRP is not the answer:)
[ONE Original Android Development] Norapapa:
R10T3 works fine with the euphoria build from 3.5. No bootloops.
[ONE Original Android Development] smoki3:
Render my self compiled ROM is working for other guys too. I used you source that you pushed on github
[ONE Original Android Development] vikrant82:
T3 / T2 bootlooping on Blisspop 20150515-1013 / TWRP 2.8.6.0 even with recovery-power-off trick.
[ONE Original Android Development] schaggo:
Still Intellimm...

Hey [MENTION=5438598]RenderBroken[/MENTION] I'm still trying to figure out Intellimm to make a balanced profile. Could you or anybody else for that matter give me a hint? [MENTION=3332811]faux123[/MENTION] himself seems not promptly reachable.

First step is trying to make sense of the different frequency ranges and steps Intellimm works with. For that there are some variables of which I'm trying to make sense of. It's freq_down_step_barrier optimal_freq_speed two_phase_freq. The one which is clear is input_event_min_freq, thats governor-owned touchboost.
[ONE Original Android Development] abhi08638:
I've tuned intellimm alot so I think I can help

out.

Optimal_freq_speed is the freq at which the cpu SHOULD EVENTUALLY throttle down towhen there is no load and the screen is on.

Freq_down_step_barrier is the freq which the cpu WILL step down to when the load decreases or there is no load. The goal is to go from this freq to the optimal freq over a certain amount of time (which is the down differential-- increase this value to make scaling down slower or decrease the value to make scaling down quicker).

Two phase freq (I think) is a battery saving technique. So for example when under load, you're at a Max freq of 1.9ghz. What this does is allow the cpu to temporarily scale to a lower freq and then spike back up to the higher freq when needed
[ONE Original Android Development] HaTrED_:
Just noticing an higher battery drain under latest version during deep sleep! That seems to be related with new touch screen drivers but it has to be proved tough... So, anyone with same feeling or am I the only one? [emoji51] [emoji16] [emoji12]
[ONE Original Android Development] schaggo:
Thanks [MENTION=4732904]abhi08638[/MENTION] for stepping in.

This is about where I got to as well. Although - same as you - I'm unsure where exactly two_phase_freq fits in. I'm not sure if it belongs in-between freq_down_step_barrier and optimal_freq_speed or if it belongs above freq_down_step_barrier. Depending on what's what.

What I thought how it works:

optimal_freq_speed is the main target frequency, governor tries to reach this freq (or below) as often as possible.

freq_down_step_barrier is the upper threshold, if the frequency crosses this barrier the governor tries to ramp back down as hard as possible.

two_phase_freq is the intermediate barrier, governor tries to not ramp above this freq and stay in-between optimal freq and this freq.

This leads to the following (IMO battery-oriented) values:

optimal_freq_speed 499

freq_down_step_barrier 1728

two_phase_freq 1190

input_event_min_freq 960 (4x)

I will do further tests and take your input into consideration, exchanging values for freq_down_step_barrier and two_phase_freq and see how this changes things.
[ONE Original Android Development] abhi08638:
Good, I find that setting down step and optimal freq to the same value acts like sort of an on off switch. When there's load, scale up to input event freq, if no load, scale back down to min freq with a down differential of 1. However, this causes jank in scrolling. I have found a way around this.

I am using the input event in conjunction with cpu boost driver for cpu0 only. Set the min boost to 2000ms and tada, no more jank. Also the other cores are now at then min freq anyway.

I also have found a few tricks regarding this governor. If you want more info you can pm me
[ONE Original Android Development] clockworkstop:
http://www.ibtimes.co.uk/oneplus-on...yanogenmod-12-1-nightly-download-link-1501619

These were the touchscreen issues I was talking about a few weeks ago, in case anyone was wondering.
[ONE Original Android Development] silvan g:
Working great on latest aospal :) thanks !
[ONE Original Android Development] Nandeh:
Working perfect too with last Blisspop build, even with a dirty flash...
[ONE Original Android Development] NuLLV01D:
I doubt camera would be working for you. Is it? Or maybe the display settings FCing.
[ONE Original Android Development] silvan g:
Didn't test my camera yet, it isn't working indeed :(

Display settings works though
[ONE Original Android Development] NuLLV01D:
Crap, Man I was gonna celebrate if you'd have said Yes. [emoji23]
[ONE Original Android Development] ivan0909:
Where I can download R10?
[ONE Original Android Development] schaggo:
Use the force, Luke!

---------- Post added at 03:55 ---------- Previous post was at 03:54 ----------

Errr... scrap that, use the search instead.

Or the "Previous" buttons, they work.
[ONE Original Android Development] RenderBroken:
Have you flashed my R10 Test build and did it fix your issue?

Great info!

Yea its hard to say but All I did was bring up to date with CM.

Not sure what the problem is with the whole bootloop and rebooting while in recovery crap is about. I will have to dig into it though. Something is not working right and I am VERY interested to see what the actual cause was.
[ONE Original Android Development] smoki3:
On my latest euphoria with r10 some reports bootloops too. Is it possible that its related to multirom? For me with multirom everything is working
[ONE Original Android Development] ivan0909:
Thanks, I was searching in render's web
[ONE Original Android Development] schaggo:
I have encountered a bootloop as well, could cure it though. Unfortunately no logs, the crash happens before logs get written. Breakdown:

I always wipe /system and then completely reflash ROM, kernel and all addons. I never only flash a part of the package. I always reboot straight out of TWRP using the respective button on the flash success screen. Latest TWRP, customized kang build by katinez.

Couple days ago (see my post a bit further back) flashed R10T2 together with stock CM12.1 14/05 official.

Had a single-loop bootloop, means I hit reboot -> bootloader splashscreen -> reboot/vibrate -> bootloader splashscreen -> boots up fine. System ran fine since then.

Yesterday got R10T3 and 16/05 CM12.1 build. Did the whole wipe/flash procedure and ran into a full bootloop. Tried several combinations in attempt to fix it, didn't work, kept looping. Also power-off from recovery and manual power-on did not help.

Again wipe/flash and bootup on stock kernel. Then reboot to recovery, flash only R10T3 which resulted in that single-loop reboot (see #2) and then it booted up fine.

I took the time and ran through several kernels on offer in the dev section, only ak did that same single-loop reboot. Could it be related to anykernel? Unfortunately franco has no CM12.1 compatible kernel, so I could not test his. Latest Boeffla test build came up fine.

---------- Post added at 14:11 ---------- Previous post was at 14:04 ----------

Out of curiosity, I just now reflashed the whole package. CM12.1 official build from 16/05, let it boot on stock kernel, then reboot to recovery and only dirty-flashed RenderKernel R10T3, no wipes, and it came up straight. No hickup whatsoever.
[ONE Original Android Development] RenderBroken:
I was actually thinking the same thing. I would imagine that its related to AnyKernel somehow. Some supporting evidence would be:

When I first started building for OPO. [MENTION=2607022]Iceb0x[/MENTION] was testing my first few builds for me and when I went to Anykernel he started having this issue.

I will look into it further. In the meantime, Before you flash my kernel, try booting all the way into the rom first on clean flash then reboot into recovery to flash my kernel.
[ONE Original Android Development] OmegaBlaze:
Did you take the R10 build down? I can't find it...
[ONE Original Android Development] gianton:
Download R10 T3 from post #1291.
[ONE Original Android Development] Maestropcxp:
I try this, and get bootloop again (euphoria 05.03)
[ONE Original Android Development] OmegaBlaze:
Same. Boot Loop on SlimLP 5.1.1
[ONE Original Android Development] schaggo:
[MENTION=4595212]Maestropcxp[/MENTION] and [MENTION=2238538]OmegaBlaze[/MENTION] you both use a kang/third-party ROM. Allegedly there was a new firmware introduced in the CM builds from 15.05. and onwards. Maybe you want to flash the new firmware or the new CM build to get the firmware and then check if the kernel manages to come up on a third-party ROM? See here (also [MENTION=5438598]RenderBroken[/MENTION] :p of course):

http://xdaforums.com/showpost.php?p=60797018&postcount=633
[ONE Original Android Development] Maestropcxp:
Before flash the kernel on euphoria, i install cm 12.1 17.05 and the kernel and i get the same result
[ONE Original Android Development] dmd3746:
I have looked through the thread and the download section a few times, I am not asking when R10 is coming I am just wondering if I'm missing the download somewhere i can't find it?
[ONE Original Android Development] RenderBroken:
Are you asking for an eta?!?! Lol jk

I have only released test builds and its linked in the thread a couple posts back. I like to only have complete releases on my main site and test builds will only be linked in a post uploaded to Google Drive. I do it this way so I don't get too much exposure with the test builds and have alot of ppl reporting the same issue if they happen.
[ONE Original Android Development] ivan0909:
I've tried to flash R10 on lastest CyanideL, and bootloop. And I tried to flash last CM12.1 nightly and same.
[ONE Original Android Development] OmegaBlaze:
I'm already on the latest firmware . Still get boot loop.
[ONE Original Android Development] dude6595:
then try earlier versions....i havent update firmware in a while and im running euphoria with out issue....
[ONE Original Android Development] NuLLV01D:
I'm Running [MENTION=3115338]smoki3[/MENTION] 15/05 Euphoria Build with Render R10-T3 and Getting No Issues. Haven't Flashed the New Firmware Too.
[ONE Original Android Development] schaggo:
Just a heads up, TONS of commits in 18.05 nightly.

A specific one caught my attention: http://review.cyanogenmod.org/#/c/98677/

Although:
[ONE Original Android Development] drdrewdown:
Uggh. I don't think I can go back to the previous, touch screen is so much better now. I can live with some extra drain
[ONE Original Android Development] RenderBroken:
I am doing a new build, calling it R11-Tx. I am going to do two version of the new build. One with the new Touchscreen firmware and one without (For me with no issues and better deepsleep). Should be posted shortly.
[ONE Original Android Development] HaTrED_:
Can't hardly wait! itchy, itchy! ;) :p :D

Felt in love with R9 so expectations are high!
[ONE Original Android Development] RenderBroken:
New Build: WITH NEW TouchScreen Firmware

R11-T1

Let me know if you ppl still have flashing issues such as the "bootloop of poop".

Building new release with Touch Firmware reverted thus better batterylife. I didn't have any touch issues to begin with.
[ONE Original Android Development] schaggo:
Bootloop of poop, made my day ??? Oh man, why doesnt Chrome display emojis... lol.
[ONE Original Android Development] LiquidSolstice:
Flashed over R10-T3, no bootloops or recovery power-off needed. Thanks!
[ONE Original Android Development] schaggo:
Oh, emojis show up, I like this.

11-T1 poops on CM12.1 nightly from 16.05., regular procedure: wipe /system, flash ROM, kernel, Gapps and Addons.

It also poops when once booting the ROM on stock kernel.
[ONE Original Android Development] RenderBroken:
weird, so it has the dreaded "bootloop of poop" regardless if you flash my kernel or not?