yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] KingPen:
Quick question. Which governor is considered more conservative by default? Lionheart or Smartmax?
[ONE Original Android Development] KenjiHannya:
Smartmax
[ONE Original Android Development] KingPen:
Thanks for the quick answer
[ONE Original Android Development] LiquidSolstice:
Ahhhh. No, not your fault at all. I didn't know any of this, and now I do. Honestly, F2FS was a lot of messiness and hassle, and when I finally did boot it up, I found it not feeling much different at all. Given the choice between F2FS and your kernel, it's pretty obvious which one I'll take.

Oh well, I had been meaning to nuke my internal storage to clean up all the stuff I didn't care about, I guess I didn't think I'd be doing it so soon.

Thanks for your explanation!
[ONE Original Android Development] RenderBroken:
I know the feel. Sometimes its nice to start over clean. Also run SD Maid. I found alot of orphaned files.
[ONE Original Android Development] RenderBroken:
If I remember correctly it really needs the hotplug to go with it. I may take a look but no promises. I am pretty happy with the current set of governors.
[ONE Original Android Development] Blodgarm:
Alright thanks man

As Abraham Lincoln once said, MURICA!!!
[ONE Original Android Development] _ASSASSIN_:
gotta say man, running R21 with just a couple of tweaks and the impulse governor is a dream and has better battery life for my usage with than the exodus kernel.

Hoping that all focus isn't lost into the CAF kernel ^_^
[ONE Original Android Development] RenderBroken:
Not at all. I was planning on heading back to cm to keep things freshly in perspective. I have been testing out arteractive which is pretty conservative in a different way. I will commit my changes but there are some cool features in this new gov. Still playing with it but I plan on bringing it online within cm too.
[ONE Original Android Development] _ASSASSIN_:
BTW you might want to edit that OP, it's quite out of date along with the title heh.
[ONE Original Android Development] Blodgarm:
Hmmm arteractive, never heard of it but can't wait to see it. Is it similar to yankactive?

As Abraham Lincoln once said, MURICA!!!
[ONE Original Android Development] _ASSASSIN_:
Yeah, no clue what arteractive is, what functionality does it bring?
[ONE Original Android Development] kalapapa:
It's based off interactive and I'm assuming that it is just a pretty stock interactive with a couple of battery related scripts
[ONE Original Android Development] Ofthecats:
I'd also assume it was developed by the known dev arter97. This excites me lol
[ONE Original Android Development] Setting.Out:
+1 for the alucard hotplug, I'd love to try it with bluactive.. Also have we found what was causing issue with synapse?
[ONE Original Android Development] abhibnl:
Render, arter has warned devs in one of his tweets to stay away from arteractive for now. He himself is would not be using arteractive anymore. Just wanted to give you a heads up before you implement it. Check with him before adding it.

Sent from OnePlus One
[ONE Original Android Development] drdrewdown:
[MENTION=5438598]RenderBroken[/MENTION] you've done great work on the CAF kernel. Keep up the great work bro
[ONE Original Android Development] cerberusiscute:
This is happening when I try to use Synapse. I have flashed the UKM zip and all. Running CM12.1 nightlies.
[ONE Original Android Development] RenderBroken:
I will leave it in for others to play with. But thanks for the info. If it causes to many issues I will remove it completely.

thanks! I have moved back to cm yesterday and it is running better than the caf rom I was running. So, not sure why has happened with caf sources lately but I am sure it will be worked out. I will stick with cm for a time just to keep it fresh.

Most likely it has to do with previously using AK kernel. Can you try to make sure your ramdisk is clean before flashing UKM? Thanks.
[ONE Original Android Development] abhibnl:
For your reference. :)
[ONE Original Android Development] venky716:
Completely agreed!

Tried every other CAF ROM including sultan's and it has become a dissapointment recently, don't know why. My last good CAF rom experience was like a month ago.

Now I'm on Official Euphoria 03 and Render 21. The experience is so much better, no random reboots, no hiccups, android system shows up lower in bat stats, performance and battery life both are better.

Thanks a lot, completely satisfied with v21.
[ONE Original Android Development] abhibnl:
Just switched from COS 12.1 to slimsaber caf nandroid and i definitely feel it's a bit smoother. Also one More thing that I've tested and observed is that the stock theme provides the most snappiest experience. The minute you apply any overlay, smoothness decreases a bit.

Sent from OnePlus One
[ONE Original Android Development] Hiro Nakamura:
With R21 i still get reboots when trying to adjust the cpu voltage :(
[ONE Original Android Development] adinkwok:
How much are you increasing/decreasing the voltages by? Too much modification may cause reboots!
[ONE Original Android Development] Hiro Nakamura:
It's definitely a kernel problem. Just type any kind of undervolt in an app like kernel adiutor and the screen freezes and it reboots immediately.
[ONE Original Android Development] nfin1te:
I had the same problem, but I dirty flashed the rom two or three times. I went to CAF since then, and no problems there.

But one other user chimed in and said, that he didnt have any problems with undervolting on euphoria and R21. (seen here: http://xdaforums.com/showpost.php?p=62539612&postcount=2501 )

So I'd suggest, do a full backup, wipe, try it with a clean install if you didnt do that already and then restore or go on from that clean point, if undervolting is important to you.
[ONE Original Android Development] Setting.Out:
I had this on trickster, kernel auditor, but not synapse.. Use the ukm from this thread+synapse and you should be problem free..
[ONE Original Android Development] Hiro Nakamura:
Oh man i hate synapse :D
[ONE Original Android Development] RenderBroken:
I am using Kernel Aduitor to under-volt and its working fine. You must have a conflict from another kernel or maybe from the rom itself but that would be harder to believe. But Def try a clean install and see how that works for you. Let us know.
[ONE Original Android Development] Hiro Nakamura:
Well i did a clean flash. Maybe i should mention that i am using your kernel with the latest snapshot cm-12.1-20150901-SNAPSHOT-YOG4PAO236-bacon.zip.
[ONE Original Android Development] RenderBroken:
So even after a clean flash this occurs? OK, do you have synapse installed? What about other kernel apps that are st to apply settings on boot? Make sure all but one have been removed or at least disabled. I am using crDroid 8/28 build with 0 issues undervolting. Also nothing change voltage wise since it was included. Thanks for your help and reporting this issue.
[ONE Original Android Development] Hiro Nakamura:
Well i only have the kernel adiutor app installed and everytime i hit the global offset voltage my screen freezes and reboots.
[ONE Original Android Development] RenderBroken:
Any logs? I believe you are having an issue, just need to find out where. Also how low are you undercoating and what's your pvs? You can see it in the dmesg log.
[ONE Original Android Development] Hiro Nakamura:
I hope last_kmsg helps:

http://pastebin.com/H4VrS0ew
[ONE Original Android Development] RenderBroken:
Unfortunately it doesn't. It just shows the hang and reboot not the cause. Man I just don't know. I know there is a new tool out called Vysor that would allow me to remote into your phone. Maybe if I get time I can check it out if you are game.
[ONE Original Android Development] Hiro Nakamura:
Hm i guess i'll just skip UV for the time being. But i am not the first one who mentioned this problem :/
[ONE Original Android Development] RenderBroken:
You are right, you are the second person to report such but you are one of hundreds that download and use my kernel. I too am using R21 without issues so it has to be something on your end but I would really love to find out the glitch causing this issue. It may very well be something kernel side and something your doing is causing it to show up. Still thanks for your help so far!
[ONE Original Android Development] sneakerspark:
[MENTION=5438598]RenderBroken[/MENTION] since u like interacting with us noobs so i wanted to ask u something. :p

I have been wondering something about the UV lately. I have been trying to find out the real purpose of UV in the first place. We all do it to get some extra juice out of our phones battery but is that the case?

Processor at each frequency scale requires a certain amount of power in order to operate. As power = voltage*current, so in order to provide certain amount of power to the SOC a balance between the voltage and current is required. Now if we use the UV feature of this kernel, that means we are trading off lower voltage for higher current draw as to provide the same amount of power to the processor. And with more current draw means more battery drain.

I wanted to ask whether my theory makes any sense or my basics are way out of the way.? ￼
[ONE Original Android Development] _ASSASSIN_:
[MENTION=5048260]sneakerspark[/MENTION] if you use a global offset, it just changes how much voltage is drawn at each step. UV itself doesn't change how frequencies are handled, and just lower the amount of voltage and therefore heating going to the processor. UV can help if you have a higher binned chip that doesn't need as much voltage as the lowest common denominator.
[ONE Original Android Development] renaltosonylevi:
You remember ohms law? V/I=R .

V= voltage.

I = current (amps).

R= resistance (ohms)

So if you drop the voltage the current also drops. The main motivation for under volting is to reduce heat so thermal throttling is delayed.
[ONE Original Android Development] sneakerspark:
I thought about it too. But won't decreasing both current and voltage affect the output power?
[ONE Original Android Development] Setting.Out:
Yes, and could cause instability.. The smaller power output is negligible for hindering per frequency performance. Under-volting "could" allow for a more sustained performance due to lowered heat possibly increasing times without throttling at higher frequencies. It also "could" see battery gains from less draw/heat.. This is subjective and gains/losses aren't dramatic if enough to justify it...
[ONE Original Android Development] renaltosonylevi:
Yes it will.

Most of that output power is heat.

Now I am no electrical engineer and I will admit ohms law applied to a CPU is a little simplistic because of things like inductive and capacitive loads but having said that the basic principle applies.

As you reduce voltage you run the risk of transistors not responding inside the CPU which shows up as instability and crashes. A problem which gets worse when the CPU is hot.

When CPU's are made they are tested to find out how hot and how low a voltage they will operate and remain stable and according the results the CPU's are graded or "binned". In the case of the snapdragon 801 there is bin 1 to 17. Bin 1 is the most unstable and bin 17 is the most stable. Each bin rating comes with its own voltage table. So a bin 17 CPU runs at much lower voltage than a bin 1. Thus will consume less power run cooler and be thermally throttled less.

Unfortunately the CPU in your phone is all a matter of luck.
[ONE Original Android Development] deepaklunked:
Thanks for the nice explanation guys. Getting to learn new stuff..
[ONE Original Android Development] nfin1te:
[MENTION=5438598]RenderBroken[/MENTION], if you are interested, you might want to look at the cpuvoltage R21 softreboot-logs I pulled back then - I don't know if you had a chance to take a look at them, but since I wasn't the only one with that problem and the other log didn't show anything, here are they. I don't know if they contain any information though. http://xdaforums.com/showpost.php?p=62497739&postcount=2476
[ONE Original Android Development] sneakerspark:
Now that clears the air a bit. So qualcomm must have specified those per frequency voltages after several stress test and regretion testing. Right?
[ONE Original Android Development] RenderBroken:
Thanks. I took another look and I am going to try a different approach to UV.
[ONE Original Android Development] RenderBroken:
Yes, But the reason OC and UV work is because even though QCOM had done all of these thorough testing, QCOM is still being ultra conservative. They have to hedge their bet a bit in order to give guarantees about performance. So this allows for us to OC and UV with noticeable results. Are they huge gains? No. But they are gains nonetheless.
[ONE Original Android Development] sneakerspark:
Cool. Well too much off topic from my side. I'm really sorry about that. Let it just rest it here. Thank you all very much. :)
[ONE Original Android Development] AbedFa:
Links are dead?

EDIT: Nvm they worked
[ONE Original Android Development] syl0n:
Min/Max frequencies aren't sticking in Kernel Auditor. Is there another app I should use? Or it supported?
[ONE Original Android Development] nfin1te:
Dude, infos. ;)

What rom, caf/noncaf, ...
[ONE Original Android Development] syl0n:
CM12.1 stock. Non caf i guess.
[ONE Original Android Development] thoiloidainhan:
I have frequent screen lookups, freeze viewing websites with lots of images or videos. Have to reboot phone with power button. What logs can I pull to id the problem please? If possible I'd like to have both kernel and ROM logs to send.
[ONE Original Android Development] RenderBroken:
min never appears to stuck because cpu boost will boost the min freq when touching the screen. For max, it sticks for me with no problem. How low are you going?

All logs you can provide with Syslog. I am currently using the cm version of my kernel and have no such issues. Also no one else has reported these either. I only say this because it would seem that the issue is on your side. Maybe an app or some kernel setting causing a problem. If you can get the logs, that would help greatly. Thanks.
[ONE Original Android Development] endriuss:
I've had similar issue. I was using ViperFX so I've rewerted back to the stock audio drivers - no luck - still audio issue described above. I've flashed another RenderBroken's kernel - still the same. Finally I've decided to use stock RenderBroken's kernel settings - Victory! No problems with audio so far :) After a while I've only changed to smartmax governors (still no problems with audio) - because impulse gives me a little lags e.g. when I scrolling contacts :) I'm working in IT and now I know that in most cases "the user" caused problems not systems :) No offense - Joking ;) I was unable to investigate more but maybe playing with min/max cpu freq and the minimum CPU online at any time is the problem... I was using 146MHz min / 1958MHz max with disabled MSM Limiter and disabled CPU Boost Driver with Minimum CPU online at any time = 1. In the meantime (during the tests when I had audio problems) I've changed cpu governor to performance - still audio problems. Maybe Min CPU online was to low (as far as I remember this is the old issue in CM12 from the past)...

Nevertheless with stock kernel settings (even with smartmax gov) - no audio issue!

[MENTION=5438598]RenderBroken[/MENTION]: Thank you for your hard work and effort! Your kernel is simply emazing! My battery last me almost 1 hour SOT more compared to my previous configuration! Thank you. Keep up the good work.

ps. I really appreciate your positive attitude and the way you are cooperate with the people! Positive attitude is half way to success :)
[ONE Original Android Development] RenderBroken:
Fast Charge is already in this kernel. Have you tried that?

Glad you was able to work it out. I also had issues when setting the Screen Off Freq too low. I may go to interactive since its tuned to be a better overall governor for battery and performance. Thanks for your input!
[ONE Original Android Development] smoki3:
Any news about a cm12.1 kernel
[ONE Original Android Development] usmani:
This is what I was talking about. As you can see in the screenshot msm hotplug is disabled but still it's working and not turning all cores on. This is on r2, tried r3 t1 still the same but with 2 cores online minimum. Tweaking it didn't work either. How are you Tweaking it?
[ONE Original Android Development] Jole7:
Did you try with other governors?
[ONE Original Android Development] RenderBroken:
Yea, I have already setup the Ramdisk. I should have something today.

Sounds like your UKM install is borked. Try to re-install it.
[ONE Original Android Development] smoki3:
Sounds great
[ONE Original Android Development] Beaster:
R2 is running flawlessly on latest cm12 nightly.

Thank you!
[ONE Original Android Development] usmani:
Deleted
[ONE Original Android Development] gianton:
[MENTION=5438598]RenderBroken[/MENTION] with r2 and r3 test when I'm on call conversation with speakerphone the other party can't hear me. It's OK on stock.
[ONE Original Android Development] RenderBroken:
I have noticed the same but have not been able to debug yet. Thanks for the report. I will take a look asap.
[ONE Original Android Development] RenderBroken:
So I have added the ability to set CPU-Boost per core as well now. So you can disable it on any core. Also I have enabled the possibility to enable hotplug and wakeup boosting. What this means is:

Hotplug Boosting is whenever a core is hotplugged it will automatically be onlines at the input boost freq you have set for that core instead of waiting for the governor to ramp up to handle the workload. This should be a tremendous boost to performance since you can set the freq per core so if you want higher performance for core0-1 and lower for 2-3, then set the freqs accordingly.

Wake up Boosting is when you turn the phone on and you use the modified versions of Bricked HP, MSM_Hotplug, and Intelliplug that I use. All cores will automatically be onlines at input boost freq. This helps with turning on the phone and handling that instant burst of workload accessing the lock screen and unlocking the phone.

Lastly it is set so it will suspend, This means that with the current implementation that everyone is using still boosts even while screen is off. At least this was the case when i was deving for the Moto G and I don't believe anything has changes since then. Now it will actually be turned off when screen is off to prevent wasting battery boosting cores when not even needed. The Also it looks like I will be going to AnyKernel. This way I don't have to have multiple kernels with their own ramdisk. Still I really like the current implementation and will have to really setup the ability to prevent conflicts with other kernels since i know we are all flashoholics ;)
[ONE Original Android Development] aamitabh28:
Wow.. This sounds so cool!

I cant wait to test the new kernel

Glad to have a great dev like you onboard mate!
[ONE Original Android Development] gianton:
I like your work thanks a lot!
[ONE Original Android Development] molonad:
How about frequency per core control? ☺
[ONE Original Android Development] NuLLV01D:
If you mean to set the frequency of each core individually, it's already there
[ONE Original Android Development] molonad:
You mean in this kernel? Or you mean in another old kernel?
[ONE Original Android Development] NuLLV01D:
This one
[ONE Original Android Development] Stylez Ray.:
Your new implementations sound awesome. Will try your next version for sure.
[ONE Original Android Development] Jole7:
Simple amazing!!!
[ONE Original Android Development] syl0n:
Min 300

Max 1728
[ONE Original Android Development] RenderBroken:
I don't thing anything below 1.9ghz will stick because 1.9 is the first thermal throttle step in the thermal driver I am using. It overrides the max freq by setting it's own. Try setting it to 1.9 for now. I have a few ideas about how to fix the issue.
[ONE Original Android Development] RenderBroken:
So I have been busy with the start of school lately. But I have also been tweaking things behind the scenes. One, I completely reworked Low Memory Killer. I was not 100% satisfied that everything merged properly awhile back so I wanted to clean it up and I am happy I did. I did find some minor issues. Also I redid Voltage Control. I never had an issue but a couple others did so I wanted to try a slightly different approach so we can see if this works better for all. For me there is no difference. I just thought I would let you guys know whats been going on lately.
[ONE Original Android Development] venky716:
Getting a lot of qcom_rx_wakelock with R21 on wifi.

Couldn't find a solution, don't have any partial wakelocks just the kernel wakelocks.

[MENTION=5438598]RenderBroken[/MENTION] could you pls look into it.

Euphoria
[ONE Original Android Development] daltonhrrll:
Can't seem to get DL links working
[ONE Original Android Development] RenderBroken:
I had no issues all day. About what time did this occur and what time zone? Thanks.

I believe our CDN was having some issues and this may be related.
[ONE Original Android Development] daltonhrrll:
Around 9 am CMT
[ONE Original Android Development] RenderBroken:
So I have merged in the latest CM changes. Everything is going very well so I plan on releasing today. Also I have update my version of UKM (Thanks [MENTION=3685904]ak[/MENTION] !) so it should be working very well. So far all my testing is going fine without any issues. I do have a few other changes I plan on making to UKM before release.
[ONE Original Android Development] LiquidSolstice:
Thanks for all you do! Are you continuing your work on CAF, or are you going back? I've been using your kernel on SultanXDA's CM build and the reliability, stability, and smoothness has been top notch.
[ONE Original Android Development] 1ceb0x:
A new CAF version will be welcomed! ?

Thank you for your efforts, Render.
[ONE Original Android Development] RenderBroken:
It is Def in the works. I will not abandon either or.
[ONE Original Android Development] RenderBroken:
So I am finishing up some kernel work atm. Right now I have CM kernel ready for release and CAF is right behind it. I went back to CAF yesterday and really feel CAF is better than CM atm. I am at 88% battery with about an hour of SoT. Also the smoothness is noticeable better with CAF. Yesterday I was o CM and was having weird bugs and flakiness. I don't believe they were caused by my new CM kernel I was testing since I just merged inline with CM pretty much. But those that will use my CM kernel, please report any issues you come across. Even if its minor. I need to make sure its solid. Also remember I said I redid Voltage Control for my CM kernel so this should fix some possible issues that two users were having.
[ONE Original Android Development] Hiro Nakamura:
Sounds like a tasty update :fingers-crossed:
[ONE Original Android Development] Ofthecats:
+1 I agree that caf is noticeably smoother and more efficient
[ONE Original Android Development] opee:
Can I dirty flash a CAF euphoria version over the CM one?

Gesendet von meinem A0001 mit Tapatalk
[ONE Original Android Development] Setting.Out:
You realize you are in a kernel thread?.. Make a backup and find out..
[ONE Original Android Development] spr33:
Which CAF ROM is everyone using? I've been switching back and forth between the two, can't make my mind up.
[ONE Original Android Development] venky716:
Euphoria.

I always keep switching back to it, couldn't find a better ROM till now.

Three different builds to choose from, I would suggest using [MENTION=5021085]Bobbi lim[/MENTION] 's battery optimised version for now.

http://xdaforums.com/oneplus-one/development/rom-kernel-euphoria-os-1-1-3-4-0-caf-t3134828/page83

http://xdaforums.com/oneplus-one/development/rom-oxygen-mod-rom-best-battery-stock-t3109379/page89
[ONE Original Android Development] Setting.Out:
Darkobas... :)
[ONE Original Android Development] KenjiHannya:
1 Temasek CAF

2 12.1 CAF by Sultan

3 SlimSaber CAF

4 Euphoria CAF by CrazyBoy or ak