yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] maxed4901:
[MENTION=4296062]abhibnl[/MENTION]- So far as i know, you arent the Dev here... theres a saying that goes... i am ok>goat is OK> what is your problem... but seeing your are trying to make a good point, by saying OP> i didnt mean you or this specific one.. if you have been hanging around xda; you would know that the standards are only half maintained. what would give me the idea that this thread isnt? My question here was because i use SOKP rom. Which is AOSP base.. and some kernels have failed to boot.. The developer could say also- "AOSP Compatible" or some funky language. to tell you another example, this kernel has 2 branches.. 1 being CAF and other being CM- which again, i dont see as being highlighted in page.

Mind you, its people like us who become developers.. you are noob only until you start. and i dont see any reason for any developer to look down on any noobs or any persons because 90% of issues about roms are reported by so called "noobs" and 99.99% of roms are also tested by noobs and developed to further builds. but talk about rudeness.... you could have also said "PLEASE DONT POST AN ENTIRE OP" instead of Never ever. yes i did not know i cannot do it and its the first time any one on xda said anything about it- including rudest way to say it.

I respect the developers... as a noob- and i intend the same to come back in return. I have edited the post and lost my interest here.
[ONE Original Android Development] abhibnl:
Well i don't want to clutter this thread anymore with our off-topic talks. And there's no point trying to explain you things which you should understand. A couteous way of speaking is all that is required here. [MENTION=5438598]RenderBroken[/MENTION] is an exceptionally talented and very generous developer. So ranting that he could have mentioned "AOSP Supported or Not Supported" is pretty much useless. You mentioned that many kernels haven't worked with SOKP, then the fault is yours. You could politely ask in a kernel's thread, in case the OP wouldn't mention anything about AOSP support, if AOSP roms are supported or not. Also to make the matter clear once and for all, 99% of the kernels here are CM based. Only Donkey One kernel is AOSP supported and the dev is no longer working on that. So you are forced to use stock kernel. Also, i'm not a dev here but i'm a concerned XDA user who just want to make sure these developer threads are not cluttered with useless ranting and explaining things to people to help them as much as i can. Also i would appreciate if you won't continue this conversation on this thread. You are free to PM me but not here. Let us make sure to keep the thread clean as much as possible. Nobody is being rude to you btw. It's your own perspective. :good:
[ONE Original Android Development] DerRomtester:
I was pretty sure that this was related to that. It is worth a try. :) Maybe it was sth else and i am wrong.
[ONE Original Android Development] RenderBroken:
Well to put an end to it once and for all. I think the OPo was pretty clear in that it works for only CM12S / CM12 / CM12.1 / CM12-CAF based roms. I am not being rude when I say this but I did not note AOSP. I try to specifically make it clear what this kernel is compatible with.

Regardless i hope you find something compatible. Right now i have been running my CAF kernel with CAF-Euphoria and I have been VERY Pleased. I never have been a camera person but the way [MENTION=4800121]Sultanxda[/MENTION] has improved our Camera it makes it hard to not want to take some cool vids and pics. Also CAF seems to just run better and performance faster while keeping a little bit better batterylife.
[ONE Original Android Development] Quasar:
Looking at all the discussion, the continued mention of "AOSP based ROMs" for the device aggravates my OCD :p. All non Nexus devices use the CAF kernel, hence all ROMs are technically "CAF ROMs" unless there's a wonderdev who can port the AOSP kernel. All ROMs are based off the AOSP source, naturally since that's the source provided by Google, but no ROMs are AOSP ROMs for devices using the CAF kernel. ;)
[ONE Original Android Development] Setting.Out:
In reference, your kernel works on all aosp/slim ROMs I've tried, including sokp... However there is an issue with xenonhd, but its with the rom, not your kernel.. :)
[ONE Original Android Development] KenjiHannya:
https://drive.google.com/file/d/0B-GVJKBx9-GneVR1S0U0bktvNEk/view?usp=docslist_api[/QUOTE]

Waiting for r5 ?
[ONE Original Android Development] maxed4901:
Thank you

Well... i didnt mean to be rude but i guess it was a bad day. Aorry guys.. i have let go of SOKP- it is a permissive rom meaning flash of other kernels will also be troublesome.. But thanks anyway. Great kernel here.
[ONE Original Android Development] RenderBroken:
It's all good.

Also I have been able to work out the max freq not sticking issue. With Sultans help he pointed to his thermal driver as the cause. The way it a setup to throttle the max freq reliably is the cause. So for now I have went back with Franco's thermal driver with some modifications. I will release asap.
[ONE Original Android Development] venky716:
Secondary ROM support pls :fingers-crossed:

I think it has to do with anykernel .

TYR uses boot.img zip and his installs just fine. Render gets stuck while flashing the zip.

Or if you could post the boot.img those using multirom can flash it on their own.

Thanks.
[ONE Original Android Development] Setting.Out:
There have been a significant number of commits merged with cm, any chances for a maintenance update to r20 ?
[ONE Original Android Development] RenderBroken:
Yes you are right. It has to deal with AnyKernel. I think if you modify how you setup the second rom it should work. Can you explain your process your are using step by step? Also creating a boot.img of each release would require me to maintain a ramdisk thus making anykernel worthless. The problem with maintaining a ramdisk is its a PITA and makes things not as universal unfortunately. But I am fairly sure we can get the second rom working. Just need to make sure to flash my kernel on top of the second rom before booting.

Working on it now ;)
[ONE Original Android Development] RenderBroken:
CM-OPO: R20 is HERE!!!

Remember this is for CM Builds ONLY!!!!

Download

Things to note:

Brought inline with CM

Added Power Aware Scheduling!

Changelog:

a19ffd8 (HEAD, r20-t1, cm-12.x) Build: Update new paths

9717966 sched: add missing headers and cleanup duplicate functions

c6b3dc9 (origin/r20-t1) sched/fair: Propagate 'struct lb_env' usage into find_busiest_group

777c3f5 Remove duplicate variables in kernel/sched/fair.c

9e52b40 sched: packing task to per cpu horse power in periodic balance

cbd37e6 sched: packing task per cpu power in fork/exec/wakeup balance

28d474a sched: only use instant utilization in burst wakeup balance

cb5425b sched: make sure select_tas_rq_fair get a cpu

a247eeb sched: don't do power balance on share cpu power domain

527604d sched: lazy power balance

3ea6029 sched: power aware load balance

091f784 sched: add new members of sd_lb_stats

0b5e953 sched: no balance for prefer_sibling in power scheduling

f60e035 sched: pull all tasks from source group

9045c27 sched: add power/performance balance allow flag

f011551 sched: packing transitory tasks in wakeup power balancing

a662000 sched: using avg_idle to detect bursty wakeup

5b2ec77 sched: add sched_burst_threshold_ns as wakeup burst indicator

2900485d sched: add power aware scheduling in fork/exec/wake

416f492 sched: get rq potential maximum utilization

799cacc sched: scale_rt_power rename and meaning change

b26df25 sched: move sg/sd_lb_stats struct ahead

05885e1 sched: add new sg/sd_lb_stats fields for incoming fork/exec/wake balancing

adb3c40 sched: log the cpu utilization at rq

b90734c sched: add sysfs interface for sched_balance_policy selection

84749d2 sched: add sched balance policies in kernel

80f8a11 sched: set initial value of runnable avg for new forked task

9c5547d Revert "sched: Introduce temporary FAIR_GROUP_SCHED dependency for load-tracking"

6c4eb0b video: mdss: Fix issues when setting a channel to zero

1d48907 video: mdss: Simplify PCC combiner even more

0dc2eb2 video: mdss: Simplify PCC combiner

26bfd43 ASoC: msm: qdsp6v2: Fix invalid num_codecs

6d0d125 video: mdss: Implement PCC combining for LiveDisplay

efc0107 SoC: msm: qdsp6v2: Enable gapless for pcm offload

65e37fc ASoC: msm: qdsp6v2: fix incomplete playback issue for non-gapless formats

eabb1cf ASoC: msm: qdsp6v2: add error handling on write done during partial drain

4b7c169 ASoC: msm: qdsp6v2: remove flush wait queue

41a0d73 ARM: 7919/1: mm: refactor v7 cache cleaning ops to use way/index sequence

51b32fd ARM: mm: use inner-shareable barriers for TLB and user cache operations

cdc6bd4 ARM: 8387/1: arm/mm/dma-mapping.c: Add arm_coherent_dma_mmap

7804546 msm: mdss: Move LCD 5V EN gpio enable out of loop

a8fb24b android: drivers: workaround debugfs race in binder

e0c757d bacon: Update defconfig

62a32c9 Revert "Revert "Revert "mm: add cma pcp list"""

5b02c3f (origin/cm-12.x, origin/HEAD) Build: Update Self Compiled UBER-TCs
[ONE Original Android Development] geekynoob:
Waiting for r5 now.. Was back to r3.. R4 had some niggles that's what I felt.. Euphoria caf is updated now r5 may come soon.. Its a good day.. Lol..
[ONE Original Android Development] RenderBroken:
what was wrong with R4?
[ONE Original Android Development] venky716:
Just two steps actually.

Flash ROM

Flash kernel

It gets stuck there for a while, waited for 10 mins then force reboot.
[ONE Original Android Development] RenderBroken:
ok I will try to set it up on my end and play with it.
[ONE Original Android Development] LiquidSolstice:
I mean it sounds like he was really, really specific about what was wrong.

"Niggles", man. "Niggles". Can't you read??

/s
[ONE Original Android Development] RenderBroken:
lol, I KNOW!

I cant believe he use the word "niggles" in the same sentence as R4!
[ONE Original Android Development] geekynoob:
No offence.. My frequencies were not sticking plus I just felt while listening to music as the device was left suspended the battery drain was a tad bit more.. May be placebo.. Love your work.. Just don't get me wrong..

---------- Post added at 12:02 AM ---------- Previous post was at 12:02 AM ----------

You troll :(
[ONE Original Android Development] LiquidSolstice:
All in good fun, thanks for giving him a bit more specific info to work with ;)
[ONE Original Android Development] renaltosonylevi:
The frequencies not sticking we know about and will be addressed in the next build. And the battery drain while listening to music was a mistake by [MENTION=4800121]Sultanxda[/MENTION] that he found a couple of days ago.
[ONE Original Android Development] geekynoob:
Yep.. Following both threads.. Looking forward to the update..

Sent from my Render CAF powered Euphoriad 1+1
[ONE Original Android Development] nfin1te:
R20 running with euphoria 08/03 noncaf - basically it works fine, just synapse stopped working.

Here's what I did:

- Flash Kernel in Recovery (TWRP 2.8.7.0)

- Clear Caches

- Reboot

- Synapse says that last settings have not been stable (which is normal), but as soon as I change smth -> soft reboot

Then I figured, might be UKM, reinstalled RenderUKM 3.8.1 and rebooted - now synapse says device not supported. Wut?

Then flashed R20 again on top, now synapse doesn't act up on boot, but I can't change CPU voltage for undervolting without a soft reboot. Any ideas? (it has worked on R19)

Euphoria too old maybe? Wrong UKM? I remember smth being said many pages ago, but I can't find it.

What can I do? Thanks!
[ONE Original Android Development] RenderBroken:
I will drop a new build for CAF today when I get home. Yes, frequencies are sticking now. ;)
[ONE Original Android Development] Setting.Out:
Anyone have WiFi not working on r20?.. Flashed on new Sokp and lost WiFi..
[ONE Original Android Development] opee:
Same here on exodus... WiFi gets broken!?

Gesendet von meinem A0001 mit Tapatalk
[ONE Original Android Development] Ofthecats:
Have you tried clearing synapse app data?
[ONE Original Android Development] nfin1te:
Yes, tried that aswell. It seems that only Cpu voltage adjustment causes the freeze and soft reboot, everything else works in synapse.

PS: Wifi working on euphoria
[ONE Original Android Development] nfin1te:
I managed to pull the logs for the cpu volt problem, maybe [MENTION=5438598]RenderBroken[/MENTION] can find smth there. :)
[ONE Original Android Development] RenderBroken:
Thanks for the report!

Is this with CAF or CM? I have no such issue for CAF. But its been awhile since I used my CM kernel. Last I was on it, it worked fine. Still let me know and thanks for the logs!
[ONE Original Android Development] nfin1te:
Here's the post where I described the steps I took: http://xdaforums.com/showpost.php?p=62487864&postcount=2470

R20/CM. Currently, I am too lazy to set it all up again with CAF, the next time it will be CAF though. :)

Non-CAF just runs great, so I dont see the need to switch immediatly.
[ONE Original Android Development] RenderBroken:
OPO - CM - R21 is HERE!!!

Download

Things to note:

Made changes to possibly fix Wifi issues reported.

Also merged in a fix that has bugged me for a bit about Unbalanced IRQ Enabled.

More CM Updates

Changelog:

10a7414 (HEAD, cm-12.x) Build: Cleanup loggic in build script. Makes sure we are on the same page as the sourc

ea78c4a Revert "prima: firmware: use newer firmware that matches the Kernel space drivers"

b22b92d Revert "misc: shineled: Update driver for Find7S"

f2f5a03 bacon: Disable PIC1503_FASTCG

c662130 ARM: dts: oppo: Move shineled to x9007/a0001

e14c8c6 msm: oppo: Fix GPIO configuration when not selecting KS8851

916446f bacon/find7: Disable KS8851 ethernet

8b9b641 ARM: dts: oppo: Clean up LEDs configuration

1c6e09b ARM: dts: oppo: Remove unused devices & cleanup

d40b9b0 ARM: dts: oppo: Disable spi0
[ONE Original Android Development] RenderBroken:
OPO - CAF - R4!!!

Download

Things to note:

Updated inline with SultanXDA

Switched Thermal Solutions for now to fix Max Freq not sticking issue. NOTE: There is nothing wrong with Sultan's Thermal, Just it uses a more accurate and predictable way to enforce thermal mitigation. The means that it works without being overridden.

Updated Power Aware Scheduling some more.

A few minor changes.

Changelog:

e5b4307 (HEAD, cm-12.x-caf) Defconfig: Enable CONFIG_SCHED_DEBUG

591caf7 (origin/cm-12.x-caf, origin/HEAD) sched: Simplify can_migrate_task()

ffeb490 Sched: Add missing Headers and Remove Duplicate Functions

32ebd81 mm: Add notifier framework for showing memory

c7806af lowmemorykiller: Run the lowmemory notifier when killing

1f96145 msm: mdss: Don't save backlight brightness on blank

ee8813e Revert "Revert "msm: mdss: always save backlight brightness using unset_bl_level""

de628e2 ARM: dts: 14001: Increase panel reset delays (again)

5f56ec2 Revert "msm: mdss: always save backlight brightness using unset_bl_level"

8a54ce7 msm: thermal: simple: Set minfreq to maxfreq if minfreq > maxfreq

1b29a8a msm: thermal: simple: Remove inefficient code

c1529f0 ARM: dts: msm8974: Configure msm-thermal-simple device

0f81167 msm: thermal: simple: Use VADC device for temperature polling

1744a4b msm: thermal: simple: Clean up some variable naming

a5b051d msm: camera_v2: Create jpeg debugfs
[ONE Original Android Development] nfin1te:
Unfortunately, R21 still has the problem that i cant adjust cpu voltage without soft reboot.
[ONE Original Android Development] LiquidSolstice:
R4? Wouldn't it be R5? ;)
[ONE Original Android Development] geekynoob:
I thought it was intentional.. Probably he wanted to get rid of the niggles.. Lol
[ONE Original Android Development] Setting.Out:
Synapse is buggy on r21 and cellular networks take a solid minute to initialize.. Want a log?
[ONE Original Android Development] nfin1te:
None of those 2 problems on euphoria non-caf here.

You might want to add some info to your post, like what rom, etc.
[ONE Original Android Development] Setting.Out:
Sokp.. Kernel auditor and Trickstermod have no issues..
[ONE Original Android Development] mutalikga:
I'm having WiFi disconnection when screen off with new R4 on slimsaber CAF 24th build..

Didn't have this problem on previous R4

Edit : Sorry : Issue solved by clearing saved networks
[ONE Original Android Development] Neroga:
CAF R4 has been rock solid for me so far on Sultanxda's CM12.1 build. Was very happy to see Lionheart is included! Definitely gonna be sticking to CAF ROMs/kernels for a while.
[ONE Original Android Development] Blodgarm:
No more ak kernel profiles then?

As Abraham Lincoln once said, MURICA!!!
[ONE Original Android Development] Neroga:
Aha I didn't know anyone even used my profiles. My buddy is still running BrokenOS so I still update my profiles for non CAF builds. Gonna be some big changes. Love the way this kernel runs so I'm gonna make them pretty much the same. Lionheart for Render, Smartmax for AK.
[ONE Original Android Development] MrxSiN:
i cant get same result as my Pv1 profile on AK in this kernel. Trying on lionheart too for CAF
[ONE Original Android Development] RenderBroken:
What results you looking for, just curious.
[ONE Original Android Development] MrxSiN:
there r some missing parameter for smartmax, like ramp up during boost, input boost duration, touch poke. myb some more.
[ONE Original Android Development] DerRomtester:
On CAF? Sultan removed them because cpu boost driver is already doing that job
[ONE Original Android Development] MrxSiN:
I'm only miss that ramp up during boost. Not no enable it, but to disable it
[ONE Original Android Development] demon507:
Having wifi disconnects with slimsaber caf on r4.

Any solution or wait for r5?
[ONE Original Android Development] RenderBroken:
Nothing has changed as far as wifi goes. It must be something specific to Slimsaber. Let me know if you get more info.
[ONE Original Android Development] 1ceb0x:
It is disabled.
[ONE Original Android Development] Setting.Out:
Slim must have changed something.. r19 on SlimRemix, wifi wasn't working right, failing to connect.. (Using r19 because of previously mentioned synapse issue)..
[ONE Original Android Development] nfin1te:
FYI [MENTION=5438598]RenderBroken[/MENTION], I deinstalled synapse and UKM using the uninstallerv2 and installed kernel adiutor.

Same problem there with undervolting the cpu, so im fairly sure a problem with undervolting was introduced in R20+21.

Can somebody else please check this on their rom? Just undervolt by 5mv, if you get a soft reboot, please post here with logs and sysinfo, thanks!
[ONE Original Android Development] venky716:
No issues here.

Euphoria 8-03

Render21

Also [MENTION=5438598]RenderBroken[/MENTION] do you feel that pure CAF is actually better than CM ?

I've switched back to CM based Euphoria ROM now and both battery and performance seem better.
[ONE Original Android Development] nfin1te:
This is weird. You even use the same rom as me. Well, obvs time to go for CAF this weekend.

I dont have any clue what this could be.

Thanks for testing though!
[ONE Original Android Development] usmani:
Hey render can you add the regular non caf version of conversative in the next version?
[ONE Original Android Development] ugvpkn:
Please publish your profiles here. Thanks.
[ONE Original Android Development] RenderBroken:
In which kernel? Just to make sure I understand properly.

I agree, please share. I have ran the one sent to me and am very pleased with the results.
[ONE Original Android Development] usmani:
Caf.
[ONE Original Android Development] meetpatel:
Ukm download link is not working.
[ONE Original Android Development] nfin1te:
RenderUKM 3.8.1.4 attached - the latest available

[MENTION=5438598]RenderBroken[/MENTION]: I hope its ok that I post it here, ill take it down again as soon as the link works again.
[ONE Original Android Development] menkey:
Hi is there any updated battery profile for use with R4 CAF version? Thanks!
[ONE Original Android Development] CounterC:
[MENTION=5438598]RenderBroken[/MENTION] If I flash your CAF ZIP in recovery the screen hangs on installing, it takes very long. Is this normal?
[ONE Original Android Development] néonaloj:
Lionheart is like interactive when needed and conservative when possible, right?

I've the same impression. But it will finally be flashed successfully ;)
[ONE Original Android Development] usmani:
Happens only when flashing in multirom as secondary rom
[ONE Original Android Development] CounterC:
But does it really hang or will it go through?

---------- Post added at 04:21 PM ---------- Previous post was at 04:18 PM ----------

Can I just force reboot and the kernel will be flashed succesfully?
[ONE Original Android Development] néonaloj:
Juste wait 2 minutes untill it's correctly flashes ;)
[ONE Original Android Development] CounterC:
I've waited for over 15 minutes and it doesn't finish... Had to dirty flash stock kernel again...
[ONE Original Android Development] usmani:
Nope. Youll have to swap roms and flash it as primary.
[ONE Original Android Development] RenderBroken:
I have never had issues installing my kernel. It flashes very quickly for that matter. Maybe you could go into more detail about the process you use? Also first and second report I have ever seen about it taking longer than normal. Are others having issues?
[ONE Original Android Development] CounterC:
I have tried that and now I am stuck on OnePlus bootlogo when booting, no way past it.

I can still go into recovery though. Any idea what to do?
[ONE Original Android Development] nfin1te:
Switched from euphoria 08/03 noncaf with R21 to CAF euphoria 8/24 with R4 due to the strange cpu uv bug - happy to report that everything runs like butter until now. :)
[ONE Original Android Development] usmani:
only happens in multirom and only when flashng it as secondary

---------- Post added at 06:38 AM ---------- Previous post was at 06:32 AM ----------

you have to swap it back as secondary again. multirom is not working with caf version of render kernel as of now. flash a non caf rom with the non caf version of this kernel as primary. or some other kernel which ever you like.
[ONE Original Android Development] LiquidSolstice:
Out of curiousity, I wouldn't have any issue booting this kernel on an F2FS formatted device, would I?

For the first time in a long, long time, I decided to format my phone to F2FS, and I flashed Temasek and your kernel together, and I seem to stay at the OnePlus boot screen for a really long time without budging.

EDIT: I can now confirm that Render R21 (non-CAF) won't boot on Temasek on F2FS. I haven't yet tried going back to ext4, but I thought you should be aware of that!

Thanks for all your hard work.

EDIT: I'm slowly learning more about F2FS and the different ways it works. I've found out that most kernels either support full F2FS (/system, /data, /cache all being formatted to F2FS), or they support hybrid F2FS (/system as EXT4, with /data and /cache as F2FS). [MENTION=5438598]RenderBroken[/MENTION], would I be correct in assuming your kernel is the latter? If so, that would definitely explain why I was not booting properly.
[ONE Original Android Development] RenderBroken:
Hey!

Actually I have removed the ability to use F2FS. I was seeing too much weirdness and corruption like issues with it enabled. Also with /system you are primarily reading and that is where F2FS fails when compared to EXT4. So with everything in mind, it seemed that it was detrimental to leave it in. Sorry for the confusion.
[ONE Original Android Development] CounterC:
[MENTION=5438598]RenderBroken[/MENTION] can you add smartmax_eps governer?
[ONE Original Android Development] kalapapa:
That's just the smartmax governor tuned to be conservative
[ONE Original Android Development] RenderBroken:
No I will not. Its just SmartMAX tuned to be more conservative. So really just a waste of time when it could just easily be tuned. Still thanks for the request.
[ONE Original Android Development] Blodgarm:
[MENTION=5438598]RenderBroken[/MENTION] can you add in the Alucard governor?

As Abraham Lincoln once said, MURICA!!!