yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] Renosh:
FKUpdater and Faux124 Kernel Enhancement Pro both work well on Lollipop 5.1.1 with Render R9 or any other kernel available (AK, Boeffla etc). They're both paid apps though
[ONE Original Android Development] _ASSASSIN_:
Omni ROM has it built in Omni performance which allows you to set specific per-app profiles. Pretty slick but any CM12 based kernel such as Render won't work with Omni.
[ONE Original Android Development] Spider-Vice:
I'm on the latest CM 12.1 nightly and the latest render kernel, followed someone's suggestion of lowering the voltages globally by -60 mV and I'm getting quite some rubbish battery life, and the battery is warming up a bit. This kernel has amazing performance with the nightlies so any suggestions I would want to avoid lowering max frequencies and such... Unless it is the ROM.

There are no wakelocks.
[ONE Original Android Development] RenderBroken:
Well, lower voltages further than the chip needs can also cause degradation. Such as heat and shotty battery life. So you may need to just find a sweet spot.
[ONE Original Android Development] Spider-Vice:
I guess that explains it, then, going to compare the stock voltages with my current set up and see what's happening.
[ONE Original Android Development] CounterC:
[MENTION=5438598]RenderBroken[/MENTION] [MENTION=3115338]smoki3[/MENTION] thanks guys
[ONE Original Android Development] RenderBroken:
You are welcome!
[ONE Original Android Development] _ASSASSIN_:
Anyone else getting an issue with the impulse tunables all being zero?

Also [MENTION=5438598]RenderBroken[/MENTION] could you consider adding yankactive and optimax? :D
[ONE Original Android Development] rajat339:
I am on CM12.1, after flashi R9 i am getting bootloop, why? Any help/suggestion.
[ONE Original Android Development] MBurns2:
dirty flash your rom then flash render kernel.
[ONE Original Android Development] 1337jay:
Just wondering, did you find anything in those logs? Thanks in advance :P
[ONE Original Android Development] sneakerspark:
Thank you [MENTION=5438598]RenderBroken[/MENTION]
[ONE Original Android Development] HaTrED_:
Well, just updated my system to latest release after been using R8's along with CM12.1 for about 150 hours!

Not a single issue... [emoji106]
[ONE Original Android Development] MexiDroid:
Does this Kernel suffers sometimes a delay on Double Tap 2 Wake like AK Kernel???
[ONE Original Android Development] sneakerspark:
It doesn't
[ONE Original Android Development] wicked245:
Sorry, but have to install new gapps over old ones? Withou wiping everything?
[ONE Original Android Development] RenderBroken:
Yes, but it is not a priority. It should be in by next build.

I would hold off for a bit. Do you use Ambient Display? If so could you disable it and let me know?

I do know that I have reduced retention c-state voltages so that may be where the issue resides. I will most likely post a test build for users to try out that were having reboot issues before.
[ONE Original Android Development] störte:
Great idea. Would be happy to help

Send by Hyperdrive on one+One
[ONE Original Android Development] RenderBroken:
I can confirm, Ambient Display is the cause for the reboots. I seen this first hand. I will continue looking into it.
[ONE Original Android Development] WidowCranky:
I was just about to post with my results. I got 4 1/2 hours of stability, still with BlissPop 2.2, re-enabled Ambient Display and within 5 minutes got a reboot.

No notification, just a random reboot.

AD was set to Full Doze if that's any use to you.
[ONE Original Android Development] clockworkstop:
No reboots since I turned off Ambient Display.
[ONE Original Android Development] RenderBroken:
OK, I think I found the issue. It is caused buy Ambient Display but that is not the problem. The problem is when Ambient Display is used the hotplug driver is suspended. What happens is it will suspend twice causing a crash thus resulting in reboot. I am currently working on a fix for this. Just FYI

In the meantime don't use Ambient Display. Thanks guys!
[ONE Original Android Development] RenderBroken:
Test Build:

https://drive.google.com/file/d/0B-GVJKBx9-Gnb1RpdWRyUGdVWk0/view?usp=sharing

Let me know if you have any issues. There isn't much difference between these builds except I dropped LCD Notify and went with Powersuspend to handle sleep functions. I believe Ambient Display was causing a crash using LCD_Notify. Powersuspend is a bit more lenient. Also Bricked Hotplug is coded to use LCD_Notify so I will either drop it or code it for powersuspend at a later date.
[ONE Original Android Development] störte:
Just flashed it. with wipe cache and dalvic on the latest PSD and activate ambient display. Will report tomorrow how it went
[ONE Original Android Development] clockworkstop:
No reboots with the new test build and Ambient Display.
[ONE Original Android Development] DerRomtester:
Maybe this helps https://github.com/andip71/boeffla-kernel-cm-bacon/commit/871901d62fe620b965245024133eab412c931fe3
[ONE Original Android Development] WidowCranky:
Confirmed. Even had a notification come through without reboot.

Great work.
[ONE Original Android Development] RenderBroken:
I will try it out. Thanks for the link!
[ONE Original Android Development] RenderBroken:
This seems to have helped. Good find!
[ONE Original Android Development] störte:
10 hours working without any problems. Great

Send by Hyperdrive on one+One
[ONE Original Android Development] smoki3:
Incredible battery life ! Great work
[ONE Original Android Development] RenderBroken:
Nice! I will take that!

I will be working on R2 today now that the reboot issue is understood and under control. Thanks to those who sent in logs and helped point me in the right direction. I would love to come up with a generic way to tie into the Back light like Boeffla had done but we will see. What it means is everything is back on track! I will continue to rework different subsystems. I had already updated OOM and CPUFREQ. I think next will be touching LMK and maybe CPUIDLE. I will also work on stream lining my ramdisk and update it. I will be working on SlimSaber compatibility as well.

I think we are off to a great start. I love my new OPO and hope to make it run even better!
[ONE Original Android Development] smoki3:
Looking forward to test if it runs on slimsaber. Dont get r1 running on slim
[ONE Original Android Development] RenderBroken:
I am fairly certain its a Ramdisk issue. I am looking into it. Thanks!
[ONE Original Android Development] MBurns2:
[MENTION=5438598]RenderBroken[/MENTION] glad to find you here mate ! good work ;)
[ONE Original Android Development] clockworkstop:
It does for me.
[ONE Original Android Development] Nandeh:
Not for me... It's fast as wind :)
[ONE Original Android Development] MBurns2:
even with stock settings?
[ONE Original Android Development] LiquidSolstice:
Double tap to wake on the OPO has always been about 1.5-2 seconds for me. It's disappointing, but I've gotten used to it.
[ONE Original Android Development] mp3deviant721:
Works fine for me on Euphoria.

OnePlus One | Powered by EuphoriaOS x RenderKernel
[ONE Original Android Development] MexiDroid:
i now after 05Q there is a delay (very annoying) but always is the same time with stock kernel, with AK even with wake boost, there is a variation of time sometimes fast and sometimes 3 secs... i will try this kernel thanks a lot guys :)
[ONE Original Android Development] RenderBroken:
This kernel has had wakeup_boost (and Hotplug_boost) for awhile now so I don't think that really plays into the DT2W feature working better. I imagine the real deviation comes from the sleep state your phone is at when DT2W is kicked up. Our Chipset uses 4 states: WFI (Wait For Interrupt), Retention, Stand Alone Power Collapse and Power Collapse. These are similar to your computer's C States.

As for Wakeup_boost, all it really does is fire up all 4 cores when the phone is turned on. This should lower the chance of micro lag when you turn your phone on and unlock the screen and such.
[ONE Original Android Development] ak:
Why you point your finger to kernel, remember gestures and 2wake are rom side. So please stop spam with always the same question.

Inviato dal mio A0001

---------- Post added at 06:09 PM ---------- Previous post was at 06:07 PM ----------

My kernel dont support 05Q.

Inviato dal mio A0001
[ONE Original Android Development] rom08:
Hello. I really like the kernel and it perform really well but I prefer stock colors. Can someone post the values to enter in synapse for stock colors please. Thanks.
[ONE Original Android Development] _ASSASSIN_:
Color: 256, 256, 256

Value: 255

contrast: 255

saturation: 255
[ONE Original Android Development] MexiDroid:
I ask this because i didn't ask before (i remember i asked a question on your kernel Forum,not on this, and i didn't ask the same question sorry)

I know your kernel doesn't support 05Q, i didn't tried on cm11 ak kernel, only stock and franco.

You don't even add a answer for my question.

I have tried for half day this kernel (render), i really like and i have a question

How can import a profile? I mean download a profile and import? Thanks :D

---------- Post added at 04:47 PM ---------- Previous post was at 04:45 PM ----------

Maybe disable the optiom on synapse, that is what i do :D
[ONE Original Android Development] MexiDroid:
after re-read my post, i got it, i understand,

the only reaseon that i finger ak kernel its because an example and maybe here somebody suffers same with ak or another kernerls, i got WORTS DT2W time on franco (only on lollipop)

i said 05Q because after that update/driver the time on DT2W its more than 44s and before.

sorry for that.

AK you are a genious on Kernel Topics, and i think the AK Kernel its the most avanced Kernel for OPO.
[ONE Original Android Development] 1ceb0x:
saying this on a completely different Kernel thread.... take it to PM!
[ONE Original Android Development] ahepas:
This is not AK kernel thread.....and please do some reading before asking things that have been answered so many times... Don't be lazy.....
[ONE Original Android Development] schaggo:
Intellimm tunables

[MENTION=5438598]RenderBroken[/MENTION] I think I'll settle on Intellimm (IntelliMinMax) governor. After quite a bit of Trepn'ing I think it is the most versatile governor of the bunch.

I would like to further tune the governor, I was unable so far to find specifications or further explanations of the tunables though. Do you have a source of information at hand or have the time to quickly explain the most important tunables of Intellimm? Thanks in advance...!
[ONE Original Android Development] RenderBroken:
Unfortunately I don't really have any info on the different tunables and would love to find some as well. I will do some searching and see what I can come up with. It definitely has some interesting qualities.
[ONE Original Android Development] schaggo:
Thanks for your answer. Cool.

I've read about it in another kernel thread for a completely different device. The dev there said it's basically a conservative with two freq ranges, focusing on battery but just providing enough power to keep the UI fluid. He found that out by studying the code which - as I am not a single bit a coder - would be a rather fruitless endeavour if undertaken by me :D
[ONE Original Android Development] RenderBroken:
You are right, the objective is you use the least amount of power to accomplish the work needed. It's interesting for sure. I have played with it some.
[ONE Original Android Development] Bobbi lim:
[MENTION=5438598]RenderBroken[/MENTION] I tried to install your R6 and R9 on my OPO running CM12S with OxygenOS firmware and it threw my device into a bootloop. My guess is it might boot on CM12S firmware but the reason why I'm using OxygenOS firmware as I seem to be able to get around 3 bars of signal on 3g at home while with CM12S firmware, all I get is no network.

Edit: I was on stock kernel before that :)
[ONE Original Android Development] jmtjr278:
Have you tried just the modem from oxygen and not the full firmware? Give that a shot. Or you could flash ROM and render with cm firmware, boot rom, and then return to recovery and attempt to flash.
[ONE Original Android Development] Bobbi lim:
I tried to use only the modem from OxygenOS with CM12S and there was no difference in network - still losing connections all the time and my friend told me to flash the whole OxygenOS firmware and that's when my network start to see improvement.

I flashed CM12S kernel after which I flash Render kernel and firmware = bootloop

Flashed R6 only without firmware = bootloop

Flashed R9 over R6 = still bootloop

Flashed Franco = ROM boots

Flashed Franco with OxygenOS = ROM boots

Thus, render kernel might not work well with OxygenOS
[ONE Original Android Development] RenderBroken:
Well, The problem is you need to have a clean Rom flash before flashing R6. (I believe R9 will work) So are you clean flashing the rom each time you make a change to the flash order?
[ONE Original Android Development] Bobbi lim:
I flashed it over with clean and dirty wipes, but all it did was threw me into a bootloop :rolleyes:
[ONE Original Android Development] RenderBroken:
I know for a fact that R6 works with CM12s. Not sure about R9 since it has the Transparent Compression stuff in it. But a clean flash of CM12s then R6 works fine for me.
[ONE Original Android Development] deepu458:
Nice kernel R9 - using it on COS 12 with Oxygen Modem

Hi i have started trying different kernels like Franco & AK. Seems like this one holds more battery power. I have installed R9 version on my bacon and everything is working fine. Now i am using Conservative profile provided by abhi.

I dont know whether the magic is by profile or Kernel, but the combo is really good. If i want to uninstall UKM from the device how can i do? can i use the uninstaller provided by AK for removing UKM on this Kernel?
[ONE Original Android Development] ahaq:
which profile of abhi are you reffering
[ONE Original Android Development] deepu458:
"abhi08638-Render-R3"

this is the one im using. This is the one that is posted in Post # 3

Another conservative Profile from [MENTION=4732904]abhi08638[/MENTION] HERE
[ONE Original Android Development] RenderBroken:
Yes, you should be able to use the uninstaller from AK or even from the UKM thread. Glad you like the kernel!
[ONE Original Android Development] deepu458:
Thanks RenderBroken, can you suggest me the best profile for battery savings for Bacon COS12?
[ONE Original Android Development] ahaq:
what about your rom
[ONE Original Android Development] deepu458:
I am using COS12 17L.
[ONE Original Android Development] ahaq:
render we can flash kernel over a different kernel running right? dirty flash the rom?
[ONE Original Android Development] deepu458:
I was using AK 239 before this kernel, so i went in and loaded Stock kernel and then flashed back this Kernel and UKM. For me no bootloop from last 1.5 day.
[ONE Original Android Development] RenderBroken:
There are some great profiles linked in OP#3. I don't run a conservative setup, I like performance more than battery so I run the kernel stock.
[ONE Original Android Development] RenderBroken:
You should be able to but I would not recommend it. I use a special script that runs after the boot process is done, thus insuring that MY values apply LAST. SO even if AK changes all the settings in the individual init files, my settings should apply over his.
[ONE Original Android Development] demon507:
I know it's not supported, but I've flashed latest firmware on cm11s with kitkat modem. Can i flash R9?

Thank u
[ONE Original Android Development] RenderBroken:
No idea but the worst that can happen is it doesn't boot. Go ahead and try and report back!
[ONE Original Android Development] shaarven71:
Hey guys, is it normal for the ram usage to be always above 1gb even after cleaning all your apps on the latest kernel.?
[ONE Original Android Development] NuLLV01D:
It's totally alright for the RAM to be used. In fact, even if it's used like 2.5GB, it's still good because hey that's what it was made for right? The main thing is that this should not affect the overall performance and UI smoothness.
[ONE Original Android Development] LiquidSolstice:
Unless you had plans for that free RAM, there's not much point in using it.
[ONE Original Android Development] Formhault:
Actually, I have been asking myself the same question. I remember one big feature of Lollipop was its very low memory footprint. Well, what happened with that? OEMs cancelling Lollipop updates due to "insufficient RAM"... Android still taking up >1 GB of RAM (where it was touted to be able to work even on 512 MB devices)...

Marketing, huh? :(
[ONE Original Android Development] LiquidSolstice:
The big feature of Lollipop concerning memory was being able to run smoothly on lower end devices, which it very much does. There are plenty of low spec devices running Lollipop.

We have 3 GB of RAM. It makes more sense to utilize as much of that RAM as possible to keep as many apps cached and ready to load, so we can do things faster. Honestly, what else do you think RAM is for?
[ONE Original Android Development] NuLLV01D:
That's because of all the sh*tload of bloat they install on their devices.
[ONE Original Android Development] Formhault:
So many of my apps reload :) guess they aren't well optimized.

I always thought RAM is used for storing tiny bits of courtesy. Not on your side, though.
[ONE Original Android Development] LiquidSolstice:
Easy there, sparky, when I asked "what else do you think RAM is for?", I wasn't actually trying to mock you (although I see now how it sounded like it).

Then again, if that was all it took to offend you...

The point stands. People tend to be confused what RAM is useful for. Having a lot of it and then wondering why it's being used is a bit silly. 30% RAM usage is nothing to be concerned about. We're not running Arch Linux on our phones. Free RAM is not indicative of performance. It's indicative of...free RAM.

A device that has 512MB of RAM will balance its load proportionally to a device with 3 gigs of it. The point is that Lollipop will actually run decently well when you have so little RAM available to use in the first place. That doesn't mean the experience is going to be the same as a high-RAM device.
[ONE Original Android Development] Formhault:
Yeah, well, we've had our arguments in the past, so what did you expect, lol.
[ONE Original Android Development] LiquidSolstice:
Er...have we? If you say so.

Coming full circle to the original comment, 1GB of RAM usage is perfectly fine. Don't worry about it. If battery is your concern, it's not going to be RAM usage that affects it as much as the poor mobile data management in Lollipop compared to KitKat. Those phenomenal 5-7 hour SoTs we're used to? They're gone and won't be coming back for a while, sadly.
[ONE Original Android Development] amjath:
Guys,

I using cos12 with ak kernel. Wanted to try this kernel but after I flashed the kernel and ukm I cannot get past from 1+ splash screen. It keeps restarting. Help?
[ONE Original Android Development] Formhault:
Right. Guess it was just you, spewing out rubbish then. Oh well, nevermind that.

---------- Post added at 11:30 AM ---------- Previous post was at 11:28 AM ----------

Huh? Care to elaborate?

By the way, the max I ever got on the OPO was 5 hours. :(
[ONE Original Android Development] abhibnl:
Let me jump in for the mobile data management part. Well in lollipop, of you use wifi full day and no mobile data, you can easily get 7hrs SOT depending upon your usage. But start using mobile data and you can barely manage 4-5hrs. The reason is, somehow in lollipop, the mobile radio stays in active state even after you stop doing any data activity or turn the screen off. You can see "Mobile Radio Active" in battery stats. That's the cause of heavy drain n pathetic battery lyf on lollipop on 2g/3g/lte. I'm still using good ol' kitkat and i can easily get 6hrs sot with uptime of 30-36hours.

Sent from OnePlus One
[ONE Original Android Development] néonaloj:
I agree with this! When I only use wifi, I can get 6-7h sot on Blisspop rom + R9. But as soon as data is needed, its 4(-5) sot...
[ONE Original Android Development] RenderBroken:
Its not really even an Android issue, Its the way Linux works. If you had only 1GB Ram, you could still run LP and run it well. You wont be able to multitask but you can still run it just fine. The way memory management works is Linux will use almost ALL of the available ram to it. Whats the point of having 3GBs Ram if you only ever use 1GB and you are having your apps killed by the Low Memory Killer. And with how we use so many apps, we have alot left in memory for multitasking. So the argument about Ram and LP is invalid. Its working as intended. This is not just towards you but to the discussion as a whole.
[ONE Original Android Development] Formhault:
I see your point. I am mostly using 3G through the day, as I'm on the move. And I can barely hit the 5h SOT mark (if I let the battery dip below 15%).

I've seen Chrome, eBay or Tinfoil for Facebook using more active radio than the screen, so... not sure what's up with that. Now I think I know.

Here's hoping Android M fixes this? Then N, then O, and so on... there's always gonna be something to fix :(
[ONE Original Android Development] abhibnl:
If you are not into the eye-candy stuff, roll back to Kitkat and enjoy the great battery lyf once again. I don't give a damn about lollipop's animations and the ****ty Project Volta. KK is ****in' smooth and damn battery friendly for me. :laugh:
[ONE Original Android Development] Formhault:
Recommend me a KK ROM please. I don't wanna hear about stock CM11S ****.
[ONE Original Android Development] NuLLV01D:
Flash this And you'll be amazed:-

http://xdaforums.com/oneplus-one/development/rom-slimkat-unofficial-minuxbuild-t2920969
[ONE Original Android Development] Formhault:
Kinda old, but I guess that's enough lol. Thanks! Will do, soon.
[ONE Original Android Development] NuLLV01D:
Download the latest build from the last page...it's of Jan 2015
[ONE Original Android Development] ahaq:
[MENTION=5198126]ViditM14[/MENTION] any good profiles on hands?
[ONE Original Android Development] NuLLV01D:
The one by [MENTION=1546609]gianton[/MENTION] gives a good mix of battery performance. Try it out:-

https://docs.google.com/file/d/0B8mXr0tbx63LV2pUVF9tcWpGWVU/edit?usp=docslist_api

I Guess the profile is now the stock settings of this Kernel

Personally, I just keep CPU0 & CPU1 on smartmax and CPU2 & CPU3 on intellimm. Also, I increase the cpu boost driver frequencies to 1267MHz(all 4, results in smoother scrolling). Also, scheduler is fipos at 512 readahead. Rest is all stock :)
[ONE Original Android Development] LiquidSolstice:
Dunno what your problem is. You seem to really want to get into a fight, but I'm not going to take your bait.

Good luck with that.
[ONE Original Android Development] ahaq:
alight gonna give it a shot, whats ur avg battery with that setup
[ONE Original Android Development] NuLLV01D:
I Always Manage to get 5hrs SOT with Heavy Youtube, spotify and Social Internet warrior stuff:p I Use Euphoria 5.1 BTW
[ONE Original Android Development] Formhault:
I usually watch local videos with MX Video Player (so, no network, right?). Also, this month, I watched a lot of YouTube via 4G (unlimited for free this month only, as bonus from carrier)...

Guess what. YouTube via 4G seems to drain the battery slower than MX Player does with local 720p .mp4's (the phone gets somewhat hot while playing back these local files). :confused:
[ONE Original Android Development] abhibnl:
Well try Mahdi ROM, it's based on CM11 (not CM11s) with many added features and built in theme engine.

You can try slim roms as well but you won't have access to the CM theme engine. If theme engine is not your priority, go with slim base roms. They're snappier and better overall.
[ONE Original Android Development] HaTrED_:
[MENTION=5438598]RenderBroken[/MENTION]

there seems to be just around the corner a new touch firmware as well as new ram disk updates from CM!

I think that's time to make same cooking!! ???