yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] 1ceb0x:
it does not work randomly.

it works as long as you do that.

you must do that even after you already flashed the kernel but you go into recovery for some reason - sometimes you'll get passed the One+ logo, sometimes you'll just remain in bootloop.

I use this kernel and now I am not rebooting from Recovery anymore. I just power it off from recovery and then back on.

A small price to pay to use this kernel. Don't ask me why it does this as i have no idea...
[ONE Original Android Development] Zephyr!:
Well, do you use philz recovery?
[ONE Original Android Development] aamitabh28:
Just a heads up.. Uber TC has been updated!
[ONE Original Android Development] mft-dev:
[MENTION=5438598]RenderBroken[/MENTION]: I've upped the min frequency to 300 as you said, but can't for the life of me find screen_off_freq anywhere.

However, I've not seen the black screen behavior since I reset to default values either, so not sure if the min frequency is what caused it. I've poured over the dmesg log but it only contains the last boot after the crash so it's beyond unhelpful.

I think I'm going to fiddle a bit with the settings during the weekend to see if I can provoke a crash again.

Anyways, great kernel! I'm really enjoying the smoothness of my OPO now, and battery longevity is back to my stock ROM days (before Google and CM borked it all up). The only app that's lagging is Synapse, but I can live with that.
[ONE Original Android Development] 1ceb0x:
no.. i use twrp. it should be the same thing, no matter what recovery you have.
[ONE Original Android Development] Formhault:
I always reboot straight from recovery and never encountered boot loops... Except this one time when I was supposed to first boot the ROM with the provided kernel, before flashing a custom one...
[ONE Original Android Development] Zephyr!:
No what I noticed was after flashing with twrp the issue doesn't pops in.

IDK why so but I felt Philz recovery was the mess.

I might be wrong but for me twrp worked

---------- Post added at 04:58 PM ---------- Previous post was at 04:55 PM ----------

@RenderBroken Friend noticed SOD couple of times. Phone was idle, I pressed the power button. Hardware button glows up and stays the same forever. I had to reboot by pressing power button.

ROM: CM12s

Well now I flashed CM nightly and flashed your kernel, I hope the same doesn't happens again.
[ONE Original Android Development] Someguyfromhell:
I can boot fine to CM12s (latest 12L) and no issues whatsoever (apart from the colors being way oversaturated, gotta fix that).
[ONE Original Android Development] RenderBroken:
Ok Guys, I have one last test to help me track down these SoDs.

I need you to disable the new State Notifier Driver. To do that:

In Terminal:

echo N > /sys/module/state_notifier/parameters/use_fb_notifier

Or you could use an app like ES Explorer and just navigate to the file, open it and change it manually.

Please try this, this will tell me id its the new driver or one of the other changes I have made.
[ONE Original Android Development] Formhault:
delete
[ONE Original Android Development] schaggo:
Disable sunlight enhancements. Mentioned several times recently.

[MENTION=5438598]RenderBroken[/MENTION] intriguingly I get significantly more wakelock time for bam_dmux_wakelock on R7 and also R6 compared to stock CM12.1 kernel. Configuration otherwise unchanged, only replaced kernel. Stock 12.1, no mods, no ukm, only stock bare nightly and your kernel.

Not that it would matter much, but where would you guess this comes from and how could it be prevented? Could it simply be a difference in reporting thoroughness?
[ONE Original Android Development] miloita:
you mean r7?? cause i saw many problems with r7 on cm12s ( COS12 ) ... it is better to stay on r6?
[ONE Original Android Development] HaTrED_:
Well, I'm still sailing with no SOD at sight! None! But never went far down them 146MHz...

Tapatalked!
[ONE Original Android Development] Someguyfromhell:
R7, indeed.
[ONE Original Android Development] RenderBroken:
Not sure, I dont remember commiting anthing that should have modified it but you never know. The kernel is a bunch of layers tied together and you can change one thing and affect another in a big way. I will keep an eye on it though. Thanks bro
[ONE Original Android Development] _ASSASSIN_:
Just wondering, have you considered having synapse support built in automatically like [MENTION=3795148]neobuddy89[/MENTION]'s kernel?
[ONE Original Android Development] RenderBroken:
I have gone down that road before, it's a pain. I am trying to set something up that can be used across all my kernels. Where as I would have to manually update synapse per kernel/ramdisk. Doing it the current way, I can make the changes I want and it is universal.

Do you think that would be a better way to go or are you just curious? As for the only issue I see which is the device not supported error. I just need to modify the install script. Thanks.
[ONE Original Android Development] NuLLV01D:
Damn, you sure are an extremely helpful Dev! Always explaining things in the nicest ways, satisfying the curiosities of others and what not! Hats Off [MENTION=5438598]RenderBroken[/MENTION]!

BTW, sorry for a lil OT, but this ROM completely flies with your Kernel, Must Try!

https://www.androidfilehost.com/?w=files&flid=30274

Credits: [MENTION=3115338]smoki3[/MENTION] for Building it with UberTC and your kernel. P.S... Did I mention it was 5.1.1?[emoji1]
[ONE Original Android Development] _ASSASSIN_:
I don't exactly know how difficult it is, but I have seen that both code blue and hydra already have it built in. It just makes things a lot easier for noobs/takes less time.

I was curious but I would love to see it if I didn't lose any functionality that UKM provided :D
[ONE Original Android Development] smoki3:
It seems set min freq to 146mhz anstead of 96 fixed the sod
[ONE Original Android Development] RenderBroken:
Test build:

R8-T1

Moved some of the notifier code to the backlight. Same thing that fixed the weird issues with LCD_Notify and Ambient Diplay awhile back. Let me know if you experience any issues. Thanks!
[ONE Original Android Development] smoki3:
I will try. Bot sod with 146 MHz too. The sod happens only when I receive a notification.
[ONE Original Android Development] RenderBroken:
Thats what I hope the new change fixes. Thanks Brother!
[ONE Original Android Development] LucentBirch:
Same here.
[ONE Original Android Development] tmimaesk:
Just go into synapse and from hotplug

set min cpus to 2 and max cpus screen off to 2

everything else default and i never get any sod
[ONE Original Android Development] alexbk66:
I use R7 with Blisspop no problem, reboot from recovery as usual. Just wipe cache/dalvik after flashing the kernel.
[ONE Original Android Development] alexbk66:
Installed Blisspop with Render R7, works great!
[ONE Original Android Development] dolbylogic:
[MENTION=5438598]RenderBroken[/MENTION]

Me and my wife we both have a an OPO. My wife is on CM12 Android 5.0.2 latest nightly 15APR and she is having a lot of SoD.. For my part I am on CM12.1 Android 5.1.1 latest nightly 26APR and I have not expirience anything so far. I flashed your RKv8-T1 on her OPO and it seems that her phone is working fine for now.. I will let you know if it does it gain.. Hopefully this help you. My guess is that the problem might has a something to do with the CM version on the OPO.
[ONE Original Android Development] RenderBroken:
Well the issue to me seems to be the same issues that plagues phones with undervolting. Some phones can handle higher Under volting, some phones cant. So that's why I have not had a single SoD while others have. Even when we are both using the same rom, same builds. I believe moving the actual notifier hooks to the backlight (Like I had to do with LCD_Notify to fix random reboots) makes the State Notifier Driver "more forgiving". Not sure if that's the right words to use but I think the process of the phone waking is more forgiving and doesn't cause a race/kernel panic. So I feel that we should be good to go. Just need more testers to report back to confirm.
[ONE Original Android Development] Nandeh:
I would be glad to help, but I haven't got any SoD with any version of your kernel...

If you think I can help in any way, just tell me :)
[ONE Original Android Development] jmtjr278:
I am running your test version from this morning and so far so good. However, I have not been experiencing and sod's.

This morning before flashing the test I did have an unresponsive device. Power button or double taps would not wake. Had to hold power button. Is this related? I know it's hard/impossible to tell without a log.

Running slimsaber with r7 stock other than-25 UV.

Sent from my A0001
[ONE Original Android Development] dolbylogic:
Thanks [MENTION=5438598]RenderBroken[/MENTION] for your reply....
[ONE Original Android Development] smoki3:
Seems sod fixed with r8.
[ONE Original Android Development] RenderBroken:
Still had a report of one from another user. Now I am going to roll back some scheduler changes. . .
[ONE Original Android Development] 1ceb0x:
R8 looking good and running strong here. Had a few SODs on R7, now seems the phone wakes up quicker than before.
[ONE Original Android Development] alexbk66:
No luck

Nop, selebrated too early, started bootloop again, wtf?

Drives me mad, it boots ok first time, but then reboot again -> bootloop:crying:

Will try R8T1...

[EDIT]

Installed R8T1, first time boots fine, second time -> bootloop:(:confused: No UKM installed yet.

Guess back to boeffla...
[ONE Original Android Development] mft-dev:
Been running the R8-T1 kernel since it was posted here on Sunday and have not had any issues with SOD. Perhaps the unresponsive display is a ROM issue? CyanogenMod jira has an issue (BACON-2100) that quite closely describes pretty much exactly what I've seen. It's tagged as only affecting XNPH38R, yet it's unresolved.
[ONE Original Android Development] kitkatcamusa:
R7 is best kernel i have tryed on lollipop! Thanks Render :)
[ONE Original Android Development] smoki3:
Had one sod today too
[ONE Original Android Development] Hash code:
I am getting sod continuously.... Tried different profiles and tried r8 as well but no use..... But remaining all r great ...... I just hope that this issue is fixed ASAP when render has time....
[ONE Original Android Development] RenderBroken:
Hang tight, I will have a new build today. I am going to roll back some scheduler changes that could be a possible cause. If it still causes SoDs then I will roll back the new State Notifier Driver and just run with LCD_Notify.
[ONE Original Android Development] HaTrED_:
As far as my personal experience can go, till this moment i'm unable to register any SOD under R7/SlimSaber! Any! ;)

Just rock solid! :good:
[ONE Original Android Development] RenderBroken:
It just goes to show that not all phones are the same. I haven't had a single sod either. That's just how it goes. Still not here are plenty of steps to take. He'll I could even revert back the super r6 and just add the transparent crap to make it compatible with new cm12 roms. I have options.
[ONE Original Android Development] molonad:
Please I don't know what version of UKm to use? Thanx

Edit : 3.8.1.1 I know now
[ONE Original Android Development] molonad:
Is this ok? I flashed r7 and render UKm 3.8.1.1 and I have this in uv is this normal?
[ONE Original Android Development] ahaq:
no it should not have UV by default, there is something wrong. Reflash the rom dirty than flash the kernel again
[ONE Original Android Development] RenderBroken:
Not sure how that happened but I never undervolt or overvolt by default. It should be a fairly linear climb.

Also Test#2!!

Removed new Scheduler stuff. Lets see if SoDs still reside. If you have one, please report back. I want to rapidly keep building today to get past this hump so I can start work on R8.

R8-T2
[ONE Original Android Development] Hash code:
I get the same uv thing when I flash ur kernel I thought its the stock settings ..... I get it linearly increasing only by using profiles of gianton and other stuff..... Mind u posting ur stock settings in synapse here so that we can cross check and correct accordingly ...
[ONE Original Android Development] 1ceb0x:
you can clear synapse data, restart the app and you should have stock settings.
[ONE Original Android Development] Hash code:
I tried it but this is what I get when I open synapse after clearing app data and the same previous settings.....
[ONE Original Android Development] 1ceb0x:
go in terminal and type this:

su
uci
uci reset
uci

then enter synapse, press I understood in the warning message (if any) and press on the OK in the top bar.

You should have stock settings.

If not, here are stock UV settings:

96mhz: 735 mV
146mhz: 745 mV
223mhz: 755 mV
300mhz: 775 mV
345mhz: 775 mV
422mhz: 775 mV
499mhz: 775 mV
576mhz: 775 mV
652mhz: 775 mV
729mhz: 775 mV
806mhz: 775 mV
883mhz: 755 mV
960mhz: 790 mV
1036mhz: 800 mV
1113mhz: 810 mV
1190mhz: 820 mV
1267mhz: 830 mV
1344mhz: 840 mV
1420mhz: 850 mV
1497mhz: 860 mV
1574mhz: 870 mV
1651mhz: 880 mV
1728mhz: 890 mV
1958mhz: 935 mV
2265mhz: 995 mV
2342mhz: 1010 mV
2419mhz: 1025 mV
2457mhz: 1030 mV
2572mhz: 1085 mV
2726mhz: 1115 mV
2880mhz: 1145 mV
[ONE Original Android Development] 1ceb0x:
Some battery impressions so far. This kernel is really something!
[ONE Original Android Development] Norapapa:
R8-T2 run perfect with euphoria 1.1 26.04. Great battery life.
[ONE Original Android Development] Hash code:
R8-t2 going good no sod in the past 15 hrs of usage..... Ty render...
[ONE Original Android Development] dolbylogic:
No SoD so far. Working great Thanks [MENTION=5438598]RenderBroken[/MENTION].
[ONE Original Android Development] Hash code:
hey buddy did u remove any useful code or something in r8-t2 coz sods r gone but for the first time i am facing ghost touch issues ............. i am using blisspop 27-4 build....

edit: back to r6 and i am all good...... free from ghost touches
[ONE Original Android Development] venky716:
I'm getting event wakelocks again with 8t2, they're not there on previous versions v7 and before.

Any chance you changed something Wifi related, I've had these awful wakelocks before and found that they're related to Wifi.
[ONE Original Android Development] RenderBroken:
I doubt the ghost touches are do to my kernel. I just reverted 4 commits in regards to scheduling. Nothing that deals with touch. I have a friend having the same thing and we have tried everything. It is device related, not software. I am not trying to side step the issue either, if there were ghost touches for you, there would be for me and many others. Sorry I cant help further.

Same here, nothing has changed as far as wifi is concerned. Only some screen changes and scheduler changes.
[ONE Original Android Development] WidowCranky:
No, I just flashed the kernel and wiped cache/dalvik

Banks.
[ONE Original Android Development] störte:
Could the reboots be connected with gapps ?

I use pa gapps. If i have time tomorrow i think i try it with banks gapps.

Send by Hyperdrive on one+One
[ONE Original Android Development] WidowCranky:
Do'ink so. Never had them before and, since reflashing the stock kernel, they haven't happened again.

(I had a second one about half an hour after I first posted about it. It's then that I decided to go back to stock until RenderBroken has had a chance to look at the logs)

[MENTION=5438598]RenderBroken[/MENTION] Other than the reboots I was mighty impressed.
[ONE Original Android Development] RenderBroken:
If you can produce and logs that would help.

I had the same results. I don't see what the cause is for the reboots. The logs don't show anything substantial but regardless I still need more. Someone will have captured something. So when I am on PSD and have 0 issues and I am on other roms and have ) issues its hard for me when someone says that have reboots on the exact same rom. It doesn't make sense. Its not like we have numerous different phone models. . .But I don't know. I will do more digging. Thanks guys for giving logs so far. Please continue to do so.
[ONE Original Android Development] störte:
[MENTION=5438598]RenderBroken[/MENTION]

What do you think about gapps? You use Bank gapps without issue. I use pa gapps modular full and have reboots. Thats the difference i see here

Send by Hyperdrive on one+One
[ONE Original Android Development] skeamznz:
I don't think gapps could cause reboots. What kernel settings were you using my friend?
[ONE Original Android Development] RenderBroken:
Test it and see.

I would love to know.
[ONE Original Android Development] störte:
OK will do asap

Send by Hyperdrive on one+One
[ONE Original Android Development] vishalssalwan:
Hey,

I have installed your kernel and the battery backup and performance of the phone has been amazing since then. Kudos to the developer!!!

I have this 1 question, prior to the installation I had a flawless 3c toolbox running in my phone, but after the installation 3c toolbox shows it can't take backup of applications any more. What things have changed to make 3c toolbox not run properly. I would love of this thing can be corrected cos I am already loving this new kernel.. Please also tell me if any logs need to be attached. I have the same rom bliss pop 11/03/2015 and same gapps,, (PA) bit 3c shows error while I take backup :(.
[ONE Original Android Development] störte:
Try to clean flash the psd with last bank gapps and your kernel. Got allways fc play services. I used banks gapps from march 14 (i think they are for Lolipop 5.1). Will try it now with mini gapps from pa and see what happen.

So Made a clean flash with your kernel on PSD with mini modular Gapps from PA. Will report any observations
[ONE Original Android Development] clockworkstop:
I'm ashamed to admit the reboots on my side came because I forgot to turn off ambient display. Sorry guys.
[ONE Original Android Development] skeamznz:
Been running your brilliant kernel all day with Euphoria and can't find a single fault. Great performance smooth and the battery life is incredible. Amazing work with the kernel, donation on the way when pay day hits.

Cheers
[ONE Original Android Development] störte:
Ambient display could be the Problem. When i had a message on the screen phone rebooted here

Send by Hyperdrive on one+One
[ONE Original Android Development] WidowCranky:
I don't think I did. Ambient Display was enabled but the phone was just sitting on my desk when, all of a sudden, I heard it vibrate and the One+ logo came up. No notification just prior to it, nothing.

However, I am just about to disable Ambient Display and then flash the kernel again. I'll let yous know how that goes.

Shame though. I like the Ambient Display feature.
[ONE Original Android Development] Novacane7:
I have Ambient display enable and don't have any reboot so I don't think it's the problem
[ONE Original Android Development] störte:
I disable the ambient and all fine since then.

Can somebody provide me a link to previous banks gapps ? Latest banks seems to be for Android 5.1 and cause play services fc

Send by Hyperdrive on one+One
[ONE Original Android Development] Novacane7:
I can upload you Gapps, let me 5 minutes

---------- Post added at 13:13 ---------- Previous post was at 12:33 ----------

Banks Gapps L 3-5-15 + md5

https://drive.google.com/folderview...JiSkRHSDNVLWplY241U1B3UVdFSzJWTlU&usp=sharing
[ONE Original Android Development] WidowCranky:
You might get a wakelock problem out of the 3-5-15 GApps. If so, the previous one is Here
[ONE Original Android Development] wicked245:
can you add sweep2wake option?
[ONE Original Android Development] störte:
So far no reboots after 3 hours use

Send by Hyperdrive on one+One
[ONE Original Android Development] schaggo:
I found this ^^ in Francos kernel thread. I suspect the qcom_rx_wakelock which you just now quoted and the bam_dmux_wakelock which I also complained about a few pages back to be somehow connected. It's two terrible wakelocks, destroying battery and not being attributable to anything. Thus no angle of attack to fix it... :(

I mean check this out :crying:

bam_dmux_wakelock

Awake vs Screen on (1:30h unaccounted for) but according to kernel wakelocks (above) I should check partial wakelocks (below).

But partial wakelocks show nothing out of the ordinary...

It's a pain...

Edit: This is on R6. R7 did not do well. And ghost touches are not software related, they are definitely device related. I bet they also get worse when the device is warm/hot with you? A reboot fixes them for a couple minutes or hours, usually.
[ONE Original Android Development] mft-dev:
I'm getting an ungodly amount of wakelocks from the same places as the above guys. Although it does not seem to be keeping my device from sleeping. I'm on R8-T2, CM12.1 Nightly from 26/4. Can't grab a screenshot at the moment.

I was perusing gerrit over on cyanogenmod and it seems they reverted the transparent compression -> review.cyanogenmod.org/#/c/96244/
[ONE Original Android Development] nazfalas:
I get they're not software related, but I have used my OPO for months now without ghost touches and everything working perfectly fine and now since about CM nightly 24-04 it has started and many other people are reporting similar experiences. Things seem to be better with Render Kernel, though. Although I do not understand why that might be.
[ONE Original Android Development] Formhault:
To those of you who are experiencing funky touchscreens... Check this out.

Yes. This is what you get when you buy such an amazing phone for only 300 bucks. F***ED UP SH*T IN AREAS WHERE YOU LESS EXPECT IT. UGH!
[ONE Original Android Development] Writer01:
Yup. You get what you paid for...
[ONE Original Android Development] nazfalas:
I already know that post, but how can you explain a phone that has been working without any issues for >6 months now and suddenly starts having issues? Could wear at the affected area be a cause?

I have never had touch issues before.

Strangely enough the touch sluggishness (not ghost touches per se) starts about 10 seconds after boot.

When I scroll through settings after boot I can observe the point at which the issues start.
[ONE Original Android Development] 1ceb0x:
No such issues as kernel wakelocks qcom or badm, on R8 for 7 hours now. Not sure what you guys are on, but you really want to have good battery life while you add this godlike kernel on top of C(M)rap rom?
[ONE Original Android Development] Pepsy89:
So is there a fix for this or we must wait for a lolipop fix or something ?
[ONE Original Android Development] 1ceb0x:
No. Facebook and Facebook messenger are 2 retard apps that harm your battery and renders it pretty much empty in no time. Tested by me as well. Uninstall the apps and enjoy a good battery or keep the apps and enjoy 6 hours of battery backup :).
[ONE Original Android Development] mft-dev:
Alternatively, use facebook in the browser instead. No annoying notifactions and no tie in to the rest og the system.

As for what ROM to run, that's a personale choice. I'm open to suggestions if you have any. While debugging RenderKernel though, it's probably wise if at least some og us aren't changing the setup every other day.
[ONE Original Android Development] mrgnex:
Hey man I like your kernel but since I updated to R7 I get some SOD's (sleep of death). Any clu what can cause it? Any logs I can grab ( I need to reboor, aren't those logs gone?)?
[ONE Original Android Development] Pepsy89:
[MENTION=2688060]1ceb0x[/MENTION] - i ques you are right ... i will give it a try , usualy i use facebook and messenger app but maby i can forget about them, today i had like 4.5 h screen time 22% battery drain , and facebook i belive i used it for 30 min and had 17% battery drain wtf ....
[ONE Original Android Development] 1ceb0x:
There's an R8 a few pages back.
[ONE Original Android Development] smoki3:
Fix for what. No wakelock issues here. Its app/ROM related!

Try r8t2
[ONE Original Android Development] Formhault:
Have you ever looked at the permissions Facebook asks for? Use this instead, really...
[ONE Original Android Development] tmimaesk:
Woth R8t2 I an still getting SOD... i can only bypass that by changing min core to 2..