yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] HaTrED_:
Yes, I am! Haven't tried R5...with R6 it gives boot loop and takes me directly to recovery, on second boot loop!

[emoji19]

Tapatalked!
[ONE Original Android Development] sneakerspark:
Ok let me know when you look through it thoroughly. Thanks. :)
[ONE Original Android Development] 1ceb0x:
Not sure actually. it started to happen 1 month ago.
[ONE Original Android Development] schaggo:
Tempted to say its either rom or your specific setup dependant.

I dirty flashed R6 oder R5, on "official" cm12.1 nightly from 18.4. and not a single hickup.

What do logs show?
[ONE Original Android Development] miloita:
where do you find his special ukm edition??

what are teh differences?
[ONE Original Android Development] RenderBroken:
Yea I am kinda agreeing. It could be the new f2fs stuff I added. Maybe the init binary cannot handle it on some roms. Not sure. Still testing but it works flawlessly for me.
[ONE Original Android Development] ak:
All roms with f2fs support have to update the fstab for use it with the new kernel implementation side.
[ONE Original Android Development] RenderBroken:
I replace the rom fstab with my own during flash. I have tested this and it worked at least on euphoria. But that's why I was saying that their init binary may not be compatible, it has to support the multiple mount options in fstab. But this is definitely weird. Thanks for chiming in though!
[ONE Original Android Development] HaTrED_:
CM pulled out 19 and 20's nightly... that means something... :confused:
[ONE Original Android Development] RenderBroken:
Yea, I just heard there was some issues lately which all the roms having boot issues are using that source. So I may be chasing my tail . . . Thanks for the info!
[ONE Original Android Development] 1ceb0x:
[MENTION=3115338]smoki3[/MENTION] and all other dudes who have bootloops in recovery or whatever..try these steps and report back, please!

Cheers!
[ONE Original Android Development] johnhere:
No issues here on CM12 nightly 15-4 (latest incremental update) with R6.

Just like earlier comments it sleeps so good and i never had such a good battery life and performance. A-mazing :good:
[ONE Original Android Development] Flak:
I'm using R6 with your 4/17 build without issue.
[ONE Original Android Development] shoman94:
R6 does not boot with 4/19 thru 4/21. It never reaches the boot animation.
[ONE Original Android Development] RenderBroken:
Yea I have been testing too. Not sure what the deal is. Can you test r5 on the new cm builds?
[ONE Original Android Development] shoman94:
Same problem with r5. Maybe it has something to do with this? http://xdaforums.com/showthread.php?p=60253755
[ONE Original Android Development] RenderBroken:
yea. . . maybe. . . .I really did not want to merge that code in. Why do we need transparent compression? Are we short of space on our partitions? I just dont get why CM merged it when its not thoroughly tested on android. At least I have never seen it before in Android. This may also change the mount options in fstab too . . . I will have to look but I pulled Robbie's CM12.1 ramdisk for one of his recent builds and the matched except for the F2FS lines I had in mine. Still I guess I can . . .merge. . .it. That way we can see. Thanks for the info!
[ONE Original Android Development] RenderBroken:
Well . . . .Transparent Compression was the cause of the GD no-boots. . . I have personally tested this.

*sigh* I guess we will all have to live with it. So, I am working on a new build anyways, some cool stuff on the way of course! But expect R7 to be dropping today which should in-turn fix the issues with bootloops.

Also note that it is backwards compatible. I can use this on older LP roms. Just don't know how old they can be though.
[ONE Original Android Development] G-DannY:
Better to wait?
[ONE Original Android Development] Maestropcxp:
No problem with r6 and euphoria 1.1 (4/14). Runs better than Ak 220.
[ONE Original Android Development] schaggo:
Was just about to post as well: 21 april is the only build wit compression enabled. Next build will have it disabled. Given the urgency probably in the next few hours.

What makes me a bit nervous: "Steve Kondik: msm8974: Disable compression * We're seeing huge memory usage in some cases. Disable for now." :rolleyes:
[ONE Original Android Development] smoki3:
Yes problem is fixed. Already tryed
[ONE Original Android Development] RenderBroken:
Let me just say:

1. I told you so

2. My head is about to go 'sploded

So literally that should mean that R6 will work on the next nightly. (And I have been wasting all my precious time the past few days. . .) *pop*
[ONE Original Android Development] shoman94:
Sounds like it will be back at some point though.... At least you'll be ready.....
[ONE Original Android Development] RenderBroken:
Yea, I left it and just disabled it for now . . .

Also I loved your roms back on my old i777 days!
[ONE Original Android Development] RenderBroken:
Almost done with R7. No it will not have Transparent Compression if i can help it. I am about to test with the latest CM12 nightly to see. But alot of cool updates are in this build. Stay tuned. . .
[ONE Original Android Development] aamitabh28:
I hope everything works out!

Really want to try this new baby out.. Cnt wait to know what the new changes are!!
[ONE Original Android Development] shoman94:
Haha thanks.... Jeboo and I are thinking about starting a rom for this phone. We both just don't have the time we use to have. I think he's ready and I'm just on the fence. We'll see what happens.... I just need to make sure my family comes first. Keep doing what you're doing. ?
[ONE Original Android Development] _ASSASSIN_:
Github is a really cool place ;)

https://github.com/RenderBroken/msm8974_OPO_render_kernel/commits/r7-t1
[ONE Original Android Development] aamitabh28:
Kernel shows only 849 kb?

Not fully updated yet?
[ONE Original Android Development] RenderBroken:
Thanks, not sure what that is about. one sec and I will re-upload.

EDIT: Fixed. Thanks for the heads up. well one of the positive side effects to using my current flash able is that even when the kernel isn't actually included and you flash it, you can still boot up just fine.
[ONE Original Android Development] gianton:
Flashed R7 over R6 on SlimSaber everything is working great!
[ONE Original Android Development] thedao:
How does the fast charge function work and can it damage the phone if i enable it?
[ONE Original Android Development] EasyGoingXD:
I think it changes the max. mA what you phone can handle with. Normal its about 1200mA and with fast charge its about 2000mA. Can it damage your phone?, yes but i have never heard from somebody that something like that happend to him
[ONE Original Android Development] MBurns2:
are you sure that normal is 1200? i thought it was 1.8

thanks
[ONE Original Android Development] EasyGoingXD:
I think i read it 4-5 months ago in AK's kernel thread
[ONE Original Android Development] MBurns2:
good, i need to investigate better :)
[ONE Original Android Development] Upakul:
Android 5.1.1

Is this kernel updated to work with Android 5.1.1 aka latest cyanogenmod nightlies 22 and above?
[ONE Original Android Development] Formhault:
Cyanogen merged 5.1.1 into their latest nightlies builds? It can't be. 5.1.1 just got out...
[ONE Original Android Development] Upakul:
Yes they did in today's nightly 22. I thought R7 was released today so asked..
[ONE Original Android Development] Formhault:
Jesus Christ, that was fast.

Well, give R7 a try, but I doubt it got merged. I mean Render didn't mention it, so... :confused:
[ONE Original Android Development] SlickMeister:
It's running great for me on my CM12.1 build with 5.1.1! Thanks RenderBroken!
[ONE Original Android Development] g_Four:
How to install? I got bootloop on CM12.1 5.1.1. [emoji17]
[ONE Original Android Development] Formhault:
Oh my God, it's been like 12 hours and 5.1.1 is already all over the place?

Okay, I give up. I can't handle such speed...
[ONE Original Android Development] HaTrED_:
Just flashed over SlimSaber, latest release from 20th of April, and all seems to be running extremely well. Kudos to you mate, i'm really appreciating your work!

;)

Later on, 'ill try under CM lastest nightly 5.1.1.... WoW!! :fingers-crossed:
[ONE Original Android Development] Nandeh:
Flashed last R7 over R6 in last BlissPop, and everything is perfect [emoji4]
[ONE Original Android Development] RenderBroken:
Well they have not merged that in yet but this does work on their latest nightly.
[ONE Original Android Development] g_Four:
R7 work perfect on euphoria 1.1.. [emoji2]
[ONE Original Android Development] dolbylogic:
Am on CM12.1 nightly 22APR Android 5.1.1 with RK-v7 and everything seems fine.. Phone seems sleeping well.. Very snappy...

Thanks [MENTION=5438598]RenderBroken[/MENTION]...
[ONE Original Android Development] usmani:
Working awesome r7, Nice work with the live ukm display (y) a quick question though, whats the reason behind Adding an option for stock charging logic now? Because as I recall, you said stock logic was intact already. Again Very nice work ?
[ONE Original Android Development] RenderBroken:
Well for the stock Charging Option is there for those that dont remember the stock levels to manually set them to. Setting to 0 is just easy to remember.
[ONE Original Android Development] justimagination:
This kernel is just simply awesome. Smooth sailing, great battery, timely updates. Thanks renderbroken
[ONE Original Android Development] EasyGoingXD:
Try this awesome combo :D

http://xdaforums.com/oneplus-one/development/rom-ubercm12-unoffical-t3062145

Stock-Kernel settings and its awesome (the dev of the rom itself made some battery saving changes on the kernel)
[ONE Original Android Development] Alfiemarquis:
Got the kernel yesterday n it's easily the best av used, but R7 doesn't seem to support multirom. No kexec-hardboot patch
[ONE Original Android Development] 1ceb0x:
R7 rolling smoothly with some changes under the hood:

- disabled cyanogenmod cpu boost.

- moved down the max cpu to 2342 mhz

- -50 uV

- 512 mb readahead

- laptop mode enabled

Everything is smooth, animations are awesome, no lag, no slow downs, just pure awesomeness!

Thanks bro, [MENTION=5438598]RenderBroken[/MENTION]!
[ONE Original Android Development] Formhault:
512 MB readahead?!
[ONE Original Android Development] Thunderbolt:
512 gb bro.
[ONE Original Android Development] NuLLV01D:
If that was sarcasm....then LOL.....if no....then it's kb
[ONE Original Android Development] Thunderbolt:
That was a joke, no sarcasm :)
[ONE Original Android Development] NuLLV01D:
Now THIS!!! is PURE AWESOMENESS!!

Latest Euphoria 14/04 with R7 (tweaked settings a Lil)
[ONE Original Android Development] clock51:
I slimLp 04/20 and kernel AK 229, can I install "Render 7" on "AK229" or do I have flashed before slim dirt and then Render7
[ONE Original Android Development] NuLLV01D:
Dirty flash ROM 1st then R7
[ONE Original Android Development] RenderBroken:
Man that is awesome! Thanks for posting and helping others!
[ONE Original Android Development] EasyGoingXD:
Hey [MENTION=5438598]RenderBroken[/MENTION] :)

I need your help! Could you give me a link with a crash-course for the oneplus one how to do something like that? :)

https://plus.google.com/photos/1111...031&sqsi=b174ecc4-854d-424c-8192-00bce34064d8

Wanna do that little project for myself in the future with the next Mahdi/Euphoria Rom + your PURE AWESOMENESS Kernel :D (+ F2FS)

How does this work compiling....uber toolchain...sources....so as you can see i have no ****ing clue ^^

I opened a new thread here, would be cool if you could help me to get started...learning from the boss :D

http://xdaforums.com/oneplus-one/help/compiling-rom-uber-toolchain-noob-t3090809
[ONE Original Android Development] ahaq:
what tweaks did you make and s this 5.0 or 5.1 europhia, please if mind share ur settings
[ONE Original Android Development] NuLLV01D:
Sure I'll post them in a moment
[ONE Original Android Development] Formhault:
I was gonna ask what effect would that have but nevermind lol.
[ONE Original Android Development] NuLLV01D:
Here You Go Guys:-

http://www.solidfiles.com/d/e7caf1ce0f/ViditM14_RenderR7_#1.tgz

I've Used Euphoria 1.1 14/04 build with 18/04 Banks GApps and Calkulin GPS fix

Please UV According to respective PVS Bins
[ONE Original Android Development] ahaq:
thanks and also 5.0 or 5.1 with the gapps u used. i m gonna try it out right after u post it with clean install

---------- Post added at 06:52 PM ---------- Previous post was at 06:51 PM ----------
[ONE Original Android Development] abhi08638:
Update your firmware to the latest CM nightly
[ONE Original Android Development] ahaq:
got it, abhi i used ur profile of ak v220, so damn nice. do you have anything for R7.
[ONE Original Android Development] Pradhan_89:
Flashed with dirty unicorn 5.1.1. Ultra smooth kernel. Thank you [MENTION=5438598]RenderBroken[/MENTION]
[ONE Original Android Development] abhi08638:
I'm going to be putting one up for 229 soon but the values are basically the same for this kernel. Just don't restore the tgz file, input them manually from the screenshots
[ONE Original Android Development] ahaq:
got it. my phone now keeps restarting and goes directly to fastboot
[ONE Original Android Development] abhi08638:
Boot into recovery by holding power + volume -

Restore backup if you haven't already.

Make sure you are not using the Oxygen OS firmware.

Use this instead. Cm12 2/09 firmware plus O2 modem

https://www.dropbox.com/s/rypitkxhdj0kjrx/Oxygen_firmware_update_2015_02_09.zip?dl=0
[ONE Original Android Development] ahaq:
each time i hold power + volume down it keeps restarting continously
[ONE Original Android Development] Spaulding89:
Hold Power button + volume down till the One plus screen appears then let the Buttons go and click only volume down till the recovery appears.

Sent from my metalbacon
[ONE Original Android Development] abhi08638:
Actually you don't even have to let go of volume down, only power when the vibrate happens
[ONE Original Android Development] ahaq:
i tried all methods and thn it boots flashboot like every single time
[ONE Original Android Development] Spaulding89:
Fastboot comes with volume up on my side

Sent from my metalbacon
[ONE Original Android Development] ahaq:
https://www.dropbox.com/s/ed8ryt106yoyxwi/IMG_1394.MOV?dl=0

[MENTION=5644065]Spaulding89[/MENTION] [MENTION=4732904]abhi08638[/MENTION]
[ONE Original Android Development] abhi08638:
Oh I've never had that problem before, I recommend searching in the general section.

Try here

http://xdaforums.com/showthread.php?t=2843675
[ONE Original Android Development] Spaulding89:
+1 never had this [MENTION=4271920]ahaq[/MENTION] Okay search and if you dont find something Flash Recovery per fastboot. You will find instructions for this

Sent from my metalbacon
[ONE Original Android Development] alexbk66:
Yeah? Check this out!
[ONE Original Android Development] NuLLV01D:
Though this is fantabulous! But you're using Boeffla Kernel...so you cannot post this achievement here.....no offence...am really impressed and "defeated" too...but you should either post it in RR ROM or Boeffla Kernel thread.
[ONE Original Android Development] alexbk66:
Yeah, sorry, got too excited:)

I switched to boeffla when rendel had bootloop issues like a week ago (or two).

Still planning to try some latest 5.1.1 ROM with r7 kernel, when I have time.
[ONE Original Android Development] aamitabh28:
I have been exoereincing SOD's similar to those in the ak kernel thread.. Maybe it is related to smartmax.. Which is sad coz it is so smooth!

Trying out the conservative governor now.. Seems smooth enough!

Will report back
[ONE Original Android Development] NuLLV01D:
Try using my profile I posted a few posts back or use the intellimm governor which is nearly equivalent to smartmax
[ONE Original Android Development] Maestropcxp:
I had 2 SoD's in the same day. Everything without modifications. Euphoria 5.1 + R7
[ONE Original Android Development] RenderBroken:
Its cool.

I have had no such issues so if you guys can, I would love some logs using Syslog when its convenient. I also have really good uptime and using Euphoria as well. Thanks!

EDIT: also could you both bump up screen off freq? Its in the CPU Tab. that could be your problem. Stock is borderline low and may be too low for yall.
[ONE Original Android Development] HaTrED_:
Never, ever had a single SOD with this kernel and I'm using it since R4 with smart max! [emoji106]

Tapatalked!
[ONE Original Android Development] gianton:
+1 Same here not a single SOD since R1. Rock stable and very smooth!
[ONE Original Android Development] venky716:
New Profile, maybe.

So got bored of the stability and speed of R7 and thought I would try something out.

This again is based for performance and if I get decent battery life on the side then great.

Logic being the best possible battery life is achieved when freq stays in the middle, hotplugging and unplugging is minimal.

I found 1.5ghz to be acceptable in terms of scrolling smoothness.

So now freq stays around the mids and ramps up to max when needed like for opening apps or heavy Web browsing.

Will update with battery stats when I Complete a cycle.

EDIT: One major problem seems to be HEAT. Smartmax and Bricked don't go well together, I tried it on AK a while ago and it gave me the same troubles so gave up, it all suddenly came back to me.

So I guess you kinda need Intelliplug or MSM to efficiently use Smartmax, i.e Max freq when needed and 1-2 cores used most of the time.

FYI: I got around 3-3.30 SOT on 50% with 6-7 hours of standby. Couldn't use it extensively due to the heat.

Bacon
[ONE Original Android Development] RenderBroken:
Linked to this in OP#2. Thanks for sharing!
[ONE Original Android Development] mft-dev:
Phone unresponsive when waking

Hey, thanks for a great kernel.

I've been using R7 with cm12.1-20150422-NIGHTLY and have had some weird issues when phone comes out of sleep. I've seen it two times in the last two days:

All stock settings in Synapse, except CPU0-3 max_freq is set to max allowed (2880 I think it is)

double tap to wake.

hardware buttons light up, but screen stays black.

hardware buttons do not turn off, even after waiting the set 30s to have the phone sleep again

Only solution I have is to hold power button until the phone reboots. Note: for 95% of the time, the phone wakes as normal, so it's really hard to pin down what's going on here. I've saved the dmesg log after last time it happened but I'm unsure if there is anything of value in it. Last kmesg was empty according to Synapse.

Here's the install steps I took, in case anyone can spot something obviously moronic:

TWRP Factory reset

Flash CM

Flash PA.Gapps.PICO.5.1 from 201500418

Flash UKM.3.8.1 (the one from your OP)

Wipe cache/dalvik (or whatever it's called, the option on the screen beside the "Reboot System" button)

Reboot and let it set itself up

Reboot to TWRP

Flash R7

Reboot system (I honestly cannot remember if I wiped again at this stage - I'm a compulsive wiper, so I probably did, but can't be certain)

Privacy Guard -> Device -> Disallow Wake, Keep Awake and Auto-Start for Google Play Services

Steps I've taken to try and eliminate compatibility problems:

dirty flashed your UKM.3.8.1.3 from a few pages ago (you really should update the link in OP to this :) )

done the whole su -> uci -> uci reset -> uci ritual (did not do that prior to today, as I was not aware I had to).

reset Synapse to all default values for your kernel (my CPU is a bin 6, so I tentatively guess that the OC might be pushing it over the edge when waking?)

I'm not sure how else I can help. What logs/info do you need from me if I see it (the screen black when waking issue) again?

Another weird issue, that I think has nothing to do with your kernel, is that sometimes when I get out of WiFi range (I'm only on WiFi at home), the cell data symbol will have an exclamation mark beside it. Browser refuses to connect to any websites, but if I open the Play Store and press "Try Again" it all magically works and keeps working for other apps. This scares me a little bit, I'd like to run a phone with 0 Google apps, but right now the only way I can consistently be guaranteed to have data, is to keep Play Store around.
[ONE Original Android Development] 1ceb0x:
Just to report here in case someone wants to try it out - flashing R7 on top of the new 5.1.1 Xenon HD rom causes System UI to crash constantly. Thought someone should know before trying it out.
[ONE Original Android Development] CounterC:
[MENTION=5438598]RenderBroken[/MENTION] R7 running great on Euphoria 5.1. Another question, is it possible to expose PVS and BIN in your UKM version and kernel?
[ONE Original Android Development] RenderBroken:
So for those having any SoD's Can you do two things?

1. Raise the Screen Off Freq

2. Raise the min Freq to 300MHz

I have no such issues but my phone may be able to handle lower freqs using the new state notifier driver (Replaced LCD Notify)

Do that and please report back. Thanks guys!
[ONE Original Android Development] aamitabh28:
So i did what u said.. Raised min to 300 and screen off freq

Still got a SOD

I am on teamasek 10.4 rom

Default configuration

I rebooted and saved the last_kmsg

Hopefully it wl help narrow down the issue!
[ONE Original Android Development] RenderBroken:
Thanks for your help!
[ONE Original Android Development] Zephyr!:
Phone keeps on rebooting on Boot logo i.e 1+ logo.

IMO kernel side issue because I flashed AK kernel and it booted.

ROM: CM12s
[ONE Original Android Development] jmtjr278:
Extremely unhelpful. If you are looking for any help/support from the Dev or other members we need more info. Tell us the steps you took. Have you dirty flashed your ROM after coming from ak?
[ONE Original Android Development] ahaq:
did you raise the maximum freq?

---------- Post added at 08:13 PM ---------- Previous post was at 08:12 PM ----------

there is no option besides dirty flashing the rom over again
[ONE Original Android Development] Zephyr!:
I was previously using blisspop rom with ak kernel. Clean flashed CM12S, flash R7 kernel and UKM. Reboot.

Keeps on vibrating and booting
[ONE Original Android Development] RenderBroken:
But the problem I see is, I was able to flash mine over a clean install with 0 issues. So its hard to say it's my kernel when it works fine for me and many others. When you flashed cm12s, did you clean flash it? Also r7 has experimental code from cm so it may not work on cm12s. Have you tried r6?
[ONE Original Android Development] usmani:
Has been working fine for me too since r1, have used cm12s, euphoria without any issues, though today had my first sod since then and it was using smartmax with default settings. Now using conservative and it's been pretty smooth.

Btw the sod was on euphoria.
[ONE Original Android Development] Zephyr!:
Ya I clean flashed. Just now tried to flash it over Smokies build.. Ended up with the same result.

Can't figure out the issue. All the flashes are clean flash.
[ONE Original Android Development] RenderBroken:
Then the issue is with the new transparent compression crap cm has merged in their kernel and r7 is online with their kernel. R6 works with cm12s with no issues. So I would recommend that. Thanks for letting me know.
[ONE Original Android Development] 1ceb0x:
go to recovery

flash the kernel

when is flashed, go back in the recovery menu

hit the Reboot button

hit the POWER OFF button

let it be for 1 minute

reboot

profit.

basically after you flash this kernel, DO NOT REBOOT from Recovery. Instead, use recovery to power off the phone and then power it on using your power button. It will work.

[MENTION=5438598]RenderBroken[/MENTION] - maybe put this as info somewhere for people who have this specific bootloop at the One+ Logo.
[ONE Original Android Development] Zephyr!:
FYI I had already tried this method, this works randomly.

The issue is with Render kernel as after flashing Smokies build when I reboot directly from philz recovery it stays on logo.