yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] RenderBroken:
[MENTION=6259574]_ASSASSIN_[/MENTION]

I have not had any RRs for a very long time since like R14 or so.

Can you tell me if you undervolted? If so how low? What about any other changes (besides BluActive) from stock you made?

I had not seen that particular error before either. Some VERY Quick Googling found something where Faux pointed it out as being a hardware bug?! Not even sure if it relates here. I will digg further so if you get more or have any more info, please share.

http://xdaforums.com/nexus-4/orig-development/kernel-ver-039-mako-kk-4-4-uv-otg-cpu-t2008222/page1319
[ONE Original Android Development] schaggo:
I also suffered from random soft-reboots with R16/R17-T, they solely occured in standby/idle though. Because it was unbearable I went to Sultan's CAF based CM, but I suffer the same I just noticed.

I turned off UV after the first couple reboots, it did not help though. I also completely reset my config and started off clean again last week, full wipe and clean flash. Dunno, something seems borked... :\

Which log would help with soft-reboots? last_kmsg would be hardboots/kernel crashes I reckon, which one would cover soft-reboots? dmsg? logcat?
[ONE Original Android Development] abhibnl:
What is "blu_actice" btw? Could you provide a brief intro?

Sent from OnePlus One
[ONE Original Android Development] RenderBroken:
hmmmm, its weird though because you have been suffering this for awhile on non-CAF builds. Really all logs would be great, mainly last_kmsg and logcat. BUT really last_kmsg is the only one to help with the reboot.

So even with CAF you have these soft reboots and lockups? If so, I agree, something is definitely borked. But I would think the issue is Device side though. I am not one to just deny any issues with my kernel. I like to take the issues head on and learn from any problems but this seems suspect. Especially with everything in context. Still I would love more info because you never know. I also would love to figure out your problem and get you stable regardless if its my kernel(or other's) or a device issue.

From what I read though, it looked like it could be something that could be remedied somehow. Maybe a custom build with a slightly lowered L1 Cache speed. IDK but I am willing to try.
[ONE Original Android Development] phanitej:
A new cpu governor developed by eng.stk (featured in his Code_Blue kernels) based on interactive with upstream caf patches and ondemand governor bits too. This governor is mainly focused on performance like the other things the developer creates but it is also well balanced for gaming and general usage.

description source

Been a while since i used it on my N 5. But was probably the best for my use.

---------- Post added at 08:43 PM ---------- Previous post was at 08:41 PM ----------

Haven't had any reboots. Running smooth with R17. Im on minimal OS

Smooth as butter.
[ONE Original Android Development] Stylez Ray.:
R17 is a really nice release. Runs super smooth, battery is great. I am very impressed by the way you manage your kernel. It's good to know that you just don't merge thousands of commits like other kernel devs just to have them in their kernel. Sometimes it's not about just having all features, many governors and stuff merged but about a nice structured kernel like you did. Many thumbs up. Can't wait to see what you're cooking next

Gesendet von meinem A0001 mit Tapatalk
[ONE Original Android Development] _ASSASSIN_:
I have a UV of -100 and my PVS speed and PVS bin values are both 3.
[ONE Original Android Development] demon507:
I'm running slim base roms from 2-3 months and i tried many...almost every kernel out there and no random reboot except once when i went -110uv..i was testing limit.

Once i tried cm in b/w and bam random reboot.

That may be just a coincidence.

Hope this helps.
[ONE Original Android Development] RenderBroken:
That's pretty low. If you are using the 268mhz step you may try to bump the voltage back up slightly. Currently I have that step tuned to be ultra conservative to save battery. Meaning I am using slightly lower values for memory bandwidth and such. So it may be more sensitive to that kind of undervoltage. Definitely let me know if that helps at all and I will adjust the voltage accordingly.
[ONE Original Android Development] RenderBroken:
Not all phones can even go past -60mv. I know with assassin above, a bin of 3 is pretty low to be using an undervoltage of -100mv. Regardless if it works on other kernel. I have made changes to mine where I can hard set certain values that other kernel set automatically via devfreq upstream commits (that I reverted). So when they are using 75mhz as the lowest, I am using 50mhz for my 268 step.
[ONE Original Android Development] mp3deviant721:
Any plans for s2w to come back? It doesn't turn the screen on in the pocket like d2w does. That's probably the only thing keeping me from going to this kernel full time...

OnePlus One | Euphoria OS x Boeffla edition™
[ONE Original Android Development] RenderBroken:
You really having issues with dt2w? Sure I could add it back in. Especially when someone gives me a good reason to. Thanks, I will add it in for the next build.
[ONE Original Android Development] mp3deviant721:
Yeah I am. No matter what kernel I run. On hot humid days, it's really bad. On cooler less humid days, there's no problem with dt2w... I honestly dunno why this happens though. It's really annoying.

OnePlus One | Euphoria OS x Boeffla edition™
[ONE Original Android Development] ernestnwanu:
Hmm. Can't get Minimal to boot on the same kernel. Kinda faced the same issue with ak kernels, except this time the "turn off - turn back on" trick doesn't work. I'd offer to submit logs but I've faced the same issue on complete clean flashes before. Clean as can be. Would logs still help? Might just be different kinds of OPO's out there.. Just a thought.
[ONE Original Android Development] RenderBroken:
Can you tell me your flashing process? Also could you flash my kernel again over minimal OS and stay in recovery. Now connect to your phone to a computer to run adb. Run:

"adb pull /tmp/recovery.log ."

Notice the period at the end. I need that log to see why it fails to boot.
[ONE Original Android Development] ernestnwanu:
ROM, tk gapps, kernel + UKM. Tried that command prior to booting, resulted in "does not exist", after booting (and bootlooping over and over), it's "device not found"
[ONE Original Android Development] RenderBroken:
That means you don't have the right drivers installed for the computer/adb to recognize the phone. If you could work that out and get the log, that would be so awesome. I really need that to check out why some rare phones have issues with the anykernel method. Thanks again.
[ONE Original Android Development] kevinyohh:
This is so SMOOTH I'm scared! Thanks for your amazing work here, my 1+1 feels like new ? This is the perfect kernel to go. I'm on Bliss.

Oneplus One ~ Never Settle
[ONE Original Android Development] ernestnwanu:
That's odd.. Cause I do get the serial number when I do "adb devices".
[ONE Original Android Development] RenderBroken:
Hmm, really weird. Could you try pulling the log to a different directory other than". "
[ONE Original Android Development] Sir_gpm:
I was about to write about...but thinking if is just my perception.....thank for this gem.
[ONE Original Android Development] Flak:
I've got a better speed and bin than you and mine is not 100% stable @ -100.
[ONE Original Android Development] _ASSASSIN_:
I reverted to -85 and it's rock solid
[ONE Original Android Development] Blodgarm:
Hey I'm curious when do you plan on releasing that profile, i like you're previous no hotplugging profile

As Abraham Lincoln once said, MURICA!!!
[ONE Original Android Development] _ASSASSIN_:
I want to see how my profile is without messing with synapse for a couple days, see if it's both smooth and good on battery.
[ONE Original Android Development] threetwentyfizzle:
Is it possible to implement sweep to wake by swiping up as opposed to horizontally? If you decide to add it that is. Thanks again for providing quality kernels, and also for looking into adding Fauxsound in the future. Loving the latest release man keep up the good work ???
[ONE Original Android Development] mp3deviant721:
Yes it is possible. But if it is not implemented in the hardware, it'll cause a battery drain. That's how another dev explained it to me. If RenderBroken really wanted to, he could do it like how its done on some Nexus devices to avoid drain.

OnePlus One | Euphoria OS x Boeffla edition™
[ONE Original Android Development] 1ceb0x:
Have the same.. can't get past the 1+ logo.

Flashed Minimal OS

Flashed Banks Gapps

Reboot

Restored apps from Gplay

Reboot to Recovery

Clear cache and dalvik

Flash R17

Reboot

Bootloops..

Mind you I tried to take the log out of tmp but the adb will say: "error: device unauthorized. Please check the confirmation dialog on your device."

I do have the usb drivers installed that comes from the SDK package but there's no confirmation dialog in Recovery.

L.E: flashing R15 works without any issues.

maybe flashing R17 on top of R15? :)

L.E2: booted up with R15 and greeted with a SystemUI FC..
[ONE Original Android Development] thoiloidainhan:
Do I use a terminal to enter those values? Sorry for the noob question
[ONE Original Android Development] RenderBroken:
You could, or just use it as a guide.

Red: 250

Green: 250

Blue: 255

Min RGB Value: 35

Invert: Off

Saturation: 285

Screen Hue: Off

Screen Value: 245

Screen Contrast: 264
[ONE Original Android Development] thoiloidainhan:
Ukm doesn't work for me. Synapse force closed immediately after launch. Using dirty Unicorn which has kernel audiutor baked in so that's probably why =(
[ONE Original Android Development] HaTrED_:
It shouldn't be... Although, for the moment, i'm using ak + synapse, along with D.U. and they coexist without any issue! :)
[ONE Original Android Development] ernestnwanu:
Can confirm the same problem in regards to pulling the log file. Also, R15 booted fine for me.
[ONE Original Android Development] RenderBroken:
I realllllllllllllllllllyyyyyyyyyyy need that recovery log. . . Lol. Otherwise I can do anything about if because it works perfectly fine e for me and many others. I need someone to keep trying to get the log. If you can, give me the exact error and I will do the research to fix it and get back to you.
[ONE Original Android Development] RenderBroken:
[MENTION=2132602]ernestnwanu[/MENTION] [MENTION=2688060]1ceb0x[/MENTION]

OK few more things to try,

First, make sure your computer RSA Key is accepted. To do that, while the computer is connected, Uncheck USB Debugging then re-check it. It should come back up to accept the RSA Key.

Also make sure ADB has Root Access:

Go to:

Developer Options > Root Access > Apps and ADB

Also when you type in:>

adb devices

What does it say to the right of the device code. does it say offline or recovery? IF it says offline, just unplug then re-plug it back in.

Let me know how it goes please good sirs.
[ONE Original Android Development] akuma48465:
Im having the same issue, My opo doesnt boot with r16 and r17 T-T
[ONE Original Android Development] mutalikga:
I noticed one thing with R17 that , it bootloops only when cache and dalvik is wiped .

Thanks for such a wonderful kernel ...
[ONE Original Android Development] spr33:
Really, really impressed with R17. Currently putting blu_active through its paces and so far it's very smooth, possibly the smoothest I've ever seen the OPO?! Hope to see even more improvements soon :)
[ONE Original Android Development] ernestnwanu:
This should be it. Flashed the kernel, stayed in recovery and ran the command. It worked this time. This is prior to booting because I get "device not found" while trying to run it while it's booting. Hope this helps. (see attachment) [MENTION=5438598]RenderBroken[/MENTION]
[ONE Original Android Development] RenderBroken:
What Rom you trying to use?

What Rom you trying to use? Also I never wipe cache and dalvic. Still great find. May be on to something.
[ONE Original Android Development] RenderBroken:
Also note that I had tried to install my kernel (R15 - R17) and AK's kernel ontop fresh isntalls of Minimal OS and both get System UI Crashes. Not sure what the problem is. But thought I would point that out. Thanks everyone for their help in reporting issues!
[ONE Original Android Development] ernestnwanu:
Hoping the log I provided does shed some light on issues I've been facing. A similar issue I faced with certain ak kernels is that they would cause my OPO to bootloop when booting from recovery, but it'd boot just fine if I switch it off first and then boot it again. That's just strange and I've seen others needing to do this as well. However, that trick didn't work for me with R16 and R17. No matter what I do, (I've tried flashing the latest firmware again through recovery and fastboot, tried several roms that are deemed compatible in this thread, clean flashed over stock kernels, tried the "turn it off" trick) it just won't boot for me. Hence why I'm beginning to believe that some OPO's differ on a hardware level(?). I don't know. Hoping you come up with something as I am eager to try out Render.
[ONE Original Android Development] RenderBroken:
What Rom were you trying to flash this kernel onto?
[ONE Original Android Development] ernestnwanu:
I tried Euphoria, Team Validus' Tipsy rom, Minimal and CM12S

EDIT: The log is on Tipsy rom
[ONE Original Android Development] mutalikga:
I tried R17 on slimsaber AND ORION LP.

R15 boots fine after wiping cache.
[ONE Original Android Development] RenderBroken:
and from every single flash, you get a bootloop? Do you wipe dalvic/cache? If so, could you try without wiping them?

I have never heard of such an issue before lol. I will have to do more research then. There are some changes from R16 on that could be a possible culprit. The main one being OC/UC.

Thanks guys for the info. Every bit is helpful.
[ONE Original Android Development] ernestnwanu:
No wipe, just flash and boot.
[ONE Original Android Development] Nandeh:
I use to boot first the ROM with default kernel, then reboot to recovery, wipe just cache (dalvik is not necessary) , flash Render and full reboot, and haven't had any problem since the first releases, tested over most ROMs available
[ONE Original Android Development] slebit:
I use r17 on Tesla ROM. I have also tried it with both validus and tipsy. No issues...
[ONE Original Android Development] akuma48465:
Im using cyanogenmod 12.1 2015/07/16 built
[ONE Original Android Development] akuma48465:
After Falsh Cm12.1 Built 2015/07/17 without wipe cache and dalvic I didnt get any boot issue (y)
[ONE Original Android Development] 1ceb0x:
I suspect that this change https://github.com/RenderBroken/msm...mmit/e85211f62481571361baca0c2aafb83331d47615

causes some OPOs to fail to boot past the 1+ logo. maybe hardware is different for some.

This was commited right after R15 was released. R15 works fine for me and for a couple of others that experience same issue with R16.

R16 however, bootloops on several roms - if not, all of them - again, for some of us.

[MENTION=5438598]RenderBroken[/MENTION] - do you think we can make a test with this one removed?
[ONE Original Android Development] RenderBroken:
It's definitely a possibility. I may run a build with it reverted. I also suspect oc/uc. I may run a separate build with only that reverted. Thanks for the suggestion, if someone will take the time to do some homework, I am down for testing a hypothesis.
[ONE Original Android Development] akuma48465:
after make a backup of my rom cm 12.1 2015/07/17 built with twrp recovery, my phone is stock in a boot loop again and i didnt wipe the cache or dalvic
[ONE Original Android Development] RenderBroken:
Thanks for the report! I should have some test builds out shortly. I truly appreciate those that are testing this weird issue out with my kernel (and possible you with other "anykernel" kernels out there)
[ONE Original Android Development] RenderBroken:
[MENTION=5227927]akuma48465[/MENTION] [MENTION=2688060]1ceb0x[/MENTION]

or those of you having bootlooping, PLEASE Test this build and report back ASAP. I am waiting on this before releasing my next build. I am ready to do so now but want to make sure these changes help or not. Thanks again!

Here is the first Test Build - I had reverted the Voltage Changes

Download
[ONE Original Android Development] akuma48465:
get it, Im going to test this right now even going to make wipes to the cache
[ONE Original Android Development] jdjta:
Sorry I am the one bursting your bubble...With R17 and R18T4 I get into a bootloop flashing on top op Exodus nightly 20150717 :(. Didn't wipe caches. I'm afraid I can't provide any logs at this moment because I don't have a desktop or laptop at hand...
[ONE Original Android Development] _ASSASSIN_:
he might not have merged all the latest CM stuff which can cause an issue since exodus's kernel is basically just a more optimized CM kernel.
[ONE Original Android Development] akuma48465:
After test here is my result,

-After install kernel on cm 12.1 built 2015/07/17 and wipe cache opo boot in to system, install the apps everything cool.

-After two reboots phone boot into the system, install the apps everything cool.

-After make a twrp backup and reboot my phone get in to a boot loop and i didnt wipe cache :(

I have to flash another kernel to boot the system properly
[ONE Original Android Development] ak:
I don't think this is the problem. Bootloop can be related to overclock/underclock (bootloader loop) or related to a ramdisk/optimization problem (bootanimation loop).

It's always difficult to trouble without logs.
[ONE Original Android Development] akuma48465:
how can I get you logs ? syslogs work ?
[ONE Original Android Development] RenderBroken:
Even worse is that it only happens to a few ppl while it works perfectly fine for the other 97% of ppl that have downloaded the kernel. I am running a build with OC/UC reverted. Also note that I had not made any Ramdisk changes. Thanks Bud for popping in!
[ONE Original Android Development] RenderBroken:
Really I need you to pull the recovery log after flashing everything while in recovery. You would need to use a computer and ADB to pull it to your computer. the command would be:

"adb pull /tmp/recovery.log ."

Note the period at the end.
[ONE Original Android Development] RenderBroken:
[MENTION=5227927]akuma48465[/MENTION] [MENTION=2688060]1ceb0x[/MENTION]

Here is the build with OCUC Reverted.

Like before, please test and report ASAP. Thanks!!

Download
[ONE Original Android Development] akuma48465:
it doesnt work with that lasted test kernel, here recovery logs

https://drive.google.com/file/d/0B677WYrnRfITYkJUcTdBVURBYjg/view?usp=docslist_api
[ONE Original Android Development] RenderBroken:
So this is a log of after you made the backup?
[ONE Original Android Development] RenderBroken:
Guys, I have no idea why my kernel (and AK's for that matter) works for almost everyone but a few ppl. It drives me crazy because it makes all development stop. It drives me crazy because it should be the same for everyone but obviously its not. I have no leads to go on either but a few weird glitches like clearing Dalvic Cache/Cache. This make no sense to me either.

With that, I am moving on. I will continue testing this on the side though. So those of you still having issues. I would love for more testing and input. Please report to the thread any finding you have or PM me. If you have some ideas, I am willing to listen. Thanks for the testing you have done so far too. Unfortunately, I am not any closer to finding the culprit.

Regards,

Render
[ONE Original Android Development] akuma48465:
yes that logs are after make a backup
[ONE Original Android Development] akuma48465:
Well I have an idea, this kernel http://xdaforums.com/oneplus-one/development/radioactivekernel-team-nuclear-t3119830

works perfect even after doing a backup with twrp or wiping cache and dalvic

so, try to see the sourcode maybe you can find what tweaks or I dont now this kernel have and then try to revert any of the lasted changes I can test whatever you want.
[ONE Original Android Development] Nandeh:
Render is working fine for me even doing stress operations with multiRom as swapping ROMs.

Works fine as primary and as secondary.

Wiping cache and/or dalvik.

Don't use to backup and restore because I prefer test ROM in secondary slots with multiROM.

Have you tried with different versions of TWRP?
[ONE Original Android Development] _ASSASSIN_:
uhh.. just make it ak kernel right? xD
[ONE Original Android Development] venky716:
Render 18 all good on Euphoria July 5th release.

But Wifi seems dead slow on last few releases, tested both static and dhcp.
[ONE Original Android Development] RenderBroken:
i appreciate you trying to bring forth some info. I will try to take a look but he just had a single commit for all of his source so that'd out if the question. I will continue to work on this, just not full time like before.

Does AK work fine for you?

i agree, there is something that some phones are very sensitive to and I have no idea. I do know that if I went with a traditional ramdisk it would work fine but that is such a waste of time for me and I would have to have separate versions, one for cm, one for slimsaber, etc. Just not feasible. Regardless this kernel has been rock solid for me and most others. The ppl having issues is like 3 percent of the total downloads. Granted some don't report if there was an issue.

Lol this was a good one liner. I laughed to hard.

Currently I am testing a new feature were I can lock the UI FPS. so certain micro lag with the UI (that can occur even with all cores one and max freq) is now mostly gone. One example is when you have nova launcher and the persistent search bar. When you hit it it opens the Google now window. It will show the last three searches you made but it will kinda slide down to show them. There is almost always some slight lag with that drop down even though everything else is smooth like scrolling and such.

I am currently testing this to see what kind of extra battery drainage we will have while the screen is on. At the moment I have it set to a minimum of 30 FPS. it is noticeably smoother. Regardless I will release test builds just for those that are curious.
[ONE Original Android Development] RenderBroken:
Test builds!!!! You know I love them!

45FPS

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

30FPS

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

I will also make builds with lower FPS values. But try both. Try 45 and you will really see the difference. But with that build, while the screen is on, it's hard to idle like normal and there is alot more hotplugging. So this is not effective. 30FPS idles wayyyy better but not quite like normal. You will see what I mean. These builds are just proof of concepts.
[ONE Original Android Development] _ASSASSIN_:
BTW render I just want to say that I have a setup I think you might like.

I have tweaked touchboost and the impulse governor quite a bit along with bricked hotplug. I made it so it runs at a dual core system when in UI/low load, and then ramps up other cores and favors middle-lower frequencies with 3-4 cores and maybe the occasional frequency spike under full load in games. I'll PM you the config if you are interested.
[ONE Original Android Development] RenderBroken:
If course I am interested. Go ahead and pm me or post it in this thread.
[ONE Original Android Development] _ASSASSIN_:
Made this profile to work on the latest test build (made this one on the 45FPS one)

https://drive.google.com/file/d/0B4jMoQTFXGOaeE55ZmdyaHRlWGs/view?usp=sharing

tested on the 16/07 build of Exodus
[ONE Original Android Development] RenderBroken:
So what do you think about the smoothness? Isn't that crazy?!