yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] dolbylogic:
As weird as it sounds. Whatever the problem is... It has something to do with reboot. I remember one time i flashed twrp 2.7.0.0 to flash Aroma LP Gapps (15May) and then re-flash back twrp 2.8.6.0 then rebooted, bammm bootloop. Weird isn't it? , but I just booted back into recovery, powered off the phone for a couple of mins and Bingo.... My OPO booted up. I am currently using R11-T1. CM Nightly 18/05/2015.
[ONE Original Android Development] Norapapa:
Back to R10T3 with euphoria, no bootloops.
[ONE Original Android Development] Hiro Nakamura:
R11-T3 working good on 2015-05-23 nightly.
[ONE Original Android Development] schaggo:
[MENTION=5438598]RenderBroken[/MENTION] would you mind compiling the latest build with the synaptics commit included? Due to the unbearable touch issues I face, I cannot run a kernel without it included ?
[ONE Original Android Development] dahndahnbo:
sam probleme here bootloop on both version R11-T3 and R10-T1 revert to previwes one R9 , and steel waiting soonest for new version

in the meanntime i want to say thank you render for your great work, good continuation
[ONE Original Android Development] erad1:
I have been using the R11-T1 without issue for days now. Latest cycle got me 48 hours uptime with 4.5 hours SOT. (Bit of a moderate user, stock 17L) Not sure why so many have the boot issue but the method I used worked and throughout several intentional reboots still no issues. You guys are missing out on a great kernel.
[ONE Original Android Development] RenderBroken:
Thanks!

Yea I don't really get it either. I have leads to go on but it doesn't make sense regardless, if it was just the commits that I added for r10 then it should have caused the same issues for AK since he merged the same ones. But I got tired of messing with it so decided to take a short break from it all and chill for a bit. I plan on taking another stay at it sometime tomorrow though. It is a bummer but I won't give up on it regardless. I enjoy doing this work too much. Also I enjoy sharing. I could do builds for myself all day long but that's not as fun.
[ONE Original Android Development] dolbylogic:
You got it right this is an awesome kernel. Thanks to [MENTION=5438598]RenderBroken[/MENTION]. Been using R11-T1 with out any issues what so ever.... Take your time Render, relax and enjoy....
[ONE Original Android Development] HaTrED_:
Still on R11-T3 and enjoying! [emoji106]
[ONE Original Android Development] schaggo:
Without the updated synaptics driver thats a na-ah for me. I tried it, the device seems to become worse and worse when running without it.

I am still tinkering with intellimm btw. I think I'm getting there. Its just that for whatever reason the limited top freq gets reset to 2.5GHz from 1.9GHz every once in a while ?
[ONE Original Android Development] schaggo:
Bootpoop discovery

I just discovered something regarding the recent bootpooping giving TGM Kernel (http://xdaforums.com/oneplus-one/orig-development/kernel-green-machine-v1-0-0-t2979540/) a shot. If I'm not mistaken, TGM also uses anykernel.

Ran RenderKernel R11 T1 (the latest with the updated synaptics drivers) on the nightly from 23.5.

It ran fine, had a while till it did (was bootlooping till I finally got the system up and running).

Flashed TGM 13.1 (the latest build with updated synaptics drivers in) right over R11 T1, no wiping.

Device bootpooped. Heavily.

Completely reflashed rom (dirty, only wipe /system) and TGM 13.1.

TMG 13.1 booted up just fine.

Does your anykernel setup produce a borked ramdisk?! Could that be the culprit? I'll do some more cross-flashing tests tomorrow, it's 1:30am and I have to leave for work at 6:15 so yeah...
[ONE Original Android Development] RenderBroken:
Here is the problem though, I thought of that but I didn't change ANYTHING regarding the anykernel/ramdisk setup. The only thing I changed from r9 to r10 was making the 10 or so cm commits. That's it. This is why it's such a pain in the ass because it makes no sense. But something is obviously wrong, even weirder is if it bootloops for one it should for all.
[ONE Original Android Development] acuicultor:
Hi render, I want to start compiling kernels and I'm planning to use yours for base, hope you don't mind. Of course if I'm able to do something good to share i will give you proper credits. At first versions only think to change toolchain and change compiling flags. Thanks in advance

Sent from my Nuclear bacon
[ONE Original Android Development] RenderBroken:
Sounds good to me! You planning on releasing or just for personal use? Let me know if you need anything. Everything I use to build is in my source. Also let me know what flags/toolchain you plan on using. I love to collaborate so Holler at me.
[ONE Original Android Development] acuicultor:
I'm planning to start with ubertc 4.8 and upgrade to 5.1 if all goes well and for compiling flags I will go for

-o3 for beginning point. I'm just a Noob willing to learn and just compiled some Roms for my personal use and want to try kernels too but if I consider the kernel good to share I will do it.

Sent from my Crispy Bacon
[ONE Original Android Development] RenderBroken:
Well. . .def keep me in the loop. As I said, I love to collaborate so if there is a cool addition you you make or find a certain flag works really good, I would be willing to merge such things in and give complete credit. Working together is how you get better.
[ONE Original Android Development] LiquidSolstice:
This should be interesting, definitely keeping an eye on it. I've gotta say, no other kernel has come close to yours, particularly concerning whatever it is you're doing with your Smartmax governor. Not even Smartmax on AK's kernel is as smooth as yours. I'm guessing you tune it manually to get it the way it is?
[ONE Original Android Development] RenderBroken:
Thanks! Well I used the tunings that [MENTION=1546609]gianton[/MENTION] had recommended and they are fantastic. I believe the smoothness is actually related to the entire setup of the kernel, from OOM and LMK to the hotplug driver (MSM_Hotplug), to how CPUFREQ has been coded along with scheduler changes that allow for a smarter approach to workload and how best to handle it and how best to schedule the workload across all cores. It is really a balancing act. Its easy to degrade the performance of the kernel just by making a small, incorrect change to any of these areas. I have personally seen it. For me to get msm_limiter to work right and without noticeable lag, I had to bringup cpufreq.c properly. Its really interesting and fun for me to see the changes and how the effect the outcome of the kernel.
[ONE Original Android Development] TLengert:
For some reason I can only find R9 kernels for OPO... Am I blind or missing something?
[ONE Original Android Development] RenderBroken:
No, you are not crazy. I dont like releasing "unstable" builds on the server. You can find test builds in the past 10 or so pages. Sorry for the inconvenience.
[ONE Original Android Development] TLengert:
Thanks for the heads up, a search found it... Also, R10-T3 is amazing so far. You have fixed my touch screen issues and, after 5'ish months, I finally love my OPO again. It is blazing fast when combined with 0526 nightly!
[ONE Original Android Development] RenderBroken:
Yea I will be releasing new builds tonight. One with new firmware and one without. I will most likely do this till the official firmware releases.

To combat the drainage using the new firmware, just disable DT2W.
[ONE Original Android Development] drdrewdown:
great, thanks for keeping us with touch screen problems in mind!
[ONE Original Android Development] acuicultor:
Hi, successfully builded your kernel with Ubertc 4.9.3 and -o3 optimizations,no other changes made. I'm running it and it seems to be pretty good and stable. I can share here if someone is interested and you don't mind.

On other hand I have some troubles willing to implement zzmove governor and his hotplug, i'm following the instructions provided by zazezam but no success I'm doing that way ( from zazezam's post added the possibility to use buildin hotplugging also on qualcomm platform. by defining the maco QCOM_NATIVE_HOTPLUGGING u can enable the

needed additional changes. Be aware that on qualcomm platform hotplugging from the usual present mpdecision userspace service has to be disabled

before using native hotplugging in the governor. you can achieve that by switching all cores to forced online mode via sysfs for example by doing

this: echo '1' >/sys/devices/system/cpu/cpu0/online_control from shell)

Please can you point me to some information for change/add the splash screen of the kernel

Thanks in advance

Sent from my Nuclear bacon
[ONE Original Android Development] LiquidSolstice:
Flashed R11-T5-OldTFW on Robbie's latest build. No bootloops, didn't need the recovery poweroff trick. :)
[ONE Original Android Development] LiquidSolstice:
Had to use the Recovery Poweroff trick to get R11-T5-OldTFW to boot BlissPop 3.3 (5/26). I'll try the older toolchain shortly to see if it helps.
[ONE Original Android Development] HaTrED_:
[MENTION=5438598]RenderBroken[/MENTION]

Later on i'll update my ROM to it's latest version along with your kernel - R11-T5-OldTFW. After that, i'll give you some feedback!
[ONE Original Android Development] Norapapa:
Me to
[ONE Original Android Development] dolbylogic:
[MENTION=5438598]RenderBroken[/MENTION]

I was able to install. R11-T5-NewTFW on my wife OPO and no boot loops it booted normally.. I installed on my OPO but I can not confirm if it boot loop or not.. But when I returned to pickup my phone it already boot up to android.. So I will assume that it did not bootloop. I say this because sometimes the OPO boot loops once and then it boots up to android. Thanks [MENTION=5438598]RenderBroken[/MENTION]
[ONE Original Android Development] Crazy-Silver:
Is normal that while charging GPU stay (minumum) on 200mhz freq? While no charging there is 27mhz also
[ONE Original Android Development] RenderBroken:
Maybe I could have just used a different term but it's new in that it's different from what I have normally been using.

Regarding those of you still having bootloops, I guess I will have to be surgical meaning that I know the 10 or so commits that made up r10 and will just have to remove/build by O e commit at a time.. .
[ONE Original Android Development] RenderBroken:
Hard to say for certain, depends on the gpu governor and such. But one thing for sure is I had not changed anything that should effect charging and the gpu. Thanks for the report though
[ONE Original Android Development] Crazy-Silver:
I think that this is related, like cpu, to the chargeing state. Phone while chargeing haven't deepsleep, I think that is something else for gpu.
[ONE Original Android Development] TLengert:
Just flashed RenderKernel-CM12_OPO-R11-T5-NewTFW and no issues so far. I have noticed lower scores in Geekbench 3 than the stock kernel. Also, overclocking doesn't seem to make much of a difference but the touch is still fully functional with no lag. Are there any settings in ROM Toolbox or Synapse anyone could recommend to help boost performance? Battery life isn't a concern for me.
[ONE Original Android Development] RenderBroken:
yea could be that because it's charging and doesn't allow for sleep States, the gpu could be spoofed I that it is robbed of its slumber state (27mhz) as well.

If you are looking for benchmark scores, just set your governor to performance then test. That's all the stock governor does with cm's performance profiles, ppl just don't notice it. This is why devs like me don't put stock into them too much because of that. You don't get a real world reading. I have it tuned so you get the same "performance" or user experience as stock kernel while using 2 less cores to do it. Watch using trickstermod or something like that where you see what cores are online and the freq they are at. Compare a stock kernel to mine and you will see that the stock kernel using 1 - 2 more cores to do the same thing my kernel does. You will see what I mean. But seriously, change gov to performance and re-test.
[ONE Original Android Development] TLengert:
Haha your kernel stomps the stock one... My phone was near unusable, mostly due to touch screen issues, and I was about to buy an iPhone. Your kernel has not only made my Android experience enjoyable again, but has motivated me to get back into tweaking and app development.

As for performance mode, still didn't help a whole lot. For example, multicore I'm at ~2,800 where stock is kernel is 3,000+. I am willing to lose out on benchmarks for a better feel/experience. Was just curious if there are any settings I can use to sacrifice battery life for performance.
[ONE Original Android Development] LiquidSolstice:
Hey, is it possible that maybe R11-T5-OldTFW is actually using the new touch firmware? I'm getting the Power Manager wakelock on it, using the latest BlissPop. Then again, I've never actually checked for this particular wakelock before, so I'm unsure if this is considered "excessive" or normal for users with DT2W enabled by default. I feel like it might be more than usual?
[ONE Original Android Development] ak:
I have the same with tc reverted, seem related to something outside kernel :highfive:
[ONE Original Android Development] schaggo:
Thanks [MENTION=5438598]RenderBroken[/MENTION] I will flash and try both and get back here with my findings.

You puzzle me a bit, to be honest. Not trying to attack you, but trying to understand. There is not much sense behind what you say. On the setup the OnePlus One has (MSM8974AC, Adreno330, 3GB of RAM), properly setup (governors, hotplugs, boost...) Android performs superbly (the "experience") with only two cores and frequencies in the range of 1200-1500MHz. Why would you want to invest A LOT (!!!) more for the exact same output, without actually gaining anything?

Car analogy: you're saying you only drive your car in first gear but at maximum rev because it feels better than in third gear at the same speed with much lower revs... and the point is? :confused:

PowerManagerService.WakeLocks is a placeholder for everything you find under "Partial Wakelocks" in BetterBatteryStats. It's not "a wakelock" but a container.

Power.ManagerService.Display is your screen-on time.

The new firmware does not produce any wakelocks, it simply consumes 30mA more power than the "old" one. I presume it does not properly power down the touchpanel in sleep to a dormant state or so... Dunno. But no wakelock, only consumption.

And to who ever who wants to quote this post: this is a multi-post adressing several people at once. Please delete the parts out of this rather large post to which you are not referring to. No need to quote EVERYTHING. Thanks.
[ONE Original Android Development] LiquidSolstice:
Aha. Good to know, thanks!

...oh. Welp. Learn something new every day. Thanks for the info, I will admit I'm not terribly educated on how wakelocks work (I was aware that not all were "bad" per se, but that's about it).
[ONE Original Android Development] RenderBroken:
Well it's more than just the governor, it's also the hotplug driver. MPDecision that is in Stock drivers is over zealous meaning that when you are benching you are still using 4 cores to bench while mine uses msm_hotplug and will really just use 2 cores.

Here lately I have been playing with interactive again and been really enjoying it.

You can also raise the input_boost_freq to 1.5GHz like the stock driver. That should give a noticeable boost in performance.

I am sure its not. Let me know if you still continue to have any issues that you know of.
[ONE Original Android Development] TLengert:
For average usage you are correct, more than 2 cores is generally not needed. However, I noticed the benchmark of both single and multicore to be slower than the stock kernel. Real world, this "slower" kernel is MUCH faster than stock because it is optimized. I get that... But my phone is usually plugged in be it the car, desk, etc. and battery life isn't a concern. I would like to have the larger V8 over the fuel efficient V6. Having maximum single and multi core performance is a higher priority than battery life for my usage. I enjoy the challenge if getting the maximum performance out of everything in life be it my car, computer, or phone. I even overclock my router/AP's at home :)

---------- Post added at 07:17 PM ---------- Previous post was at 07:11 PM ----------

I am having a really hard time with getting a better experience out of your driver. I can get the single core scores upwards of 1,100 from mid 900's but the feel of the phone is much worse.

Changing the I/O Scheduler to FIOPS seems to have helped with switching between apps. Will keep tweaking and will report my results when I am done.
[ONE Original Android Development] schaggo:
[MENTION=5438598]RenderBroken[/MENTION] the latest test build compiled with your ususal toolchain (Uber 6? Uber 5.x?) booted straight up. Not even that "one time hickup" reboot.

My original plan when I set off was that will flash the regular build, get bootloops and then flash the build built with the alternative toolchain to see if it makes a difference. "Unfortunately" the regular build worked out of the box. Happy of course, but dunno what to make of this.

Just one interesting thing: I did not wipe caches, it did "upgrade apps" though... Your script?

Stock official CM12.1 27.05.
[ONE Original Android Development] Nandeh:
RenderKernel-CM12_OPO-R11-T5-NewTFW is running smooth as butter with last BlissPop even dirty flashed.

Once battery drain will be fixed, OPO will become the perfect smartphone for me, of course using RenderKernel ;)

[MENTION=5438598]RenderBroken[/MENTION], could you explain to understand easily what need to be changed to fix this battery drainage? I have read some comments around the forum, but I have no clear conclusion... Don't know if it's a driver or firmware issue...

Thanks dude :)
[ONE Original Android Development] schaggo:
V8 is for smoothness (and sound) not pooowaaaah :D [MENTION=6716350]TLengert[/MENTION] a brutally high-revving super- and turbocharged (preferably bi-/tri-turbo in variable setup) small displacement engine with fewer cylindres beats any V8 hands down. Such a thing is undeniably seriously uncool though and I wouldnt wanna drive it :laugh:

Anyway, on topic: Why not turn hotplugging off, governor to performance and raise max frequency? Or alternatively with hotplugging on, 2-core min, input boost very high at 1700MHz or so and CPU boost set to 2500MHz or even higher. Thresholds quite low, say up at 50 and down at 20. This should close to fry the CPU but give THE MOST the system can, not much more is possible.

---------- Post added at 21:53 ---------- Previous post was at 21:51 ----------

Theres different kind of drains with completely different sources. What kind of drain do you have? Wakelocks? I think you must elaborate a lot more before an answer can be attempted to be given.
[ONE Original Android Development] vikrant82:
Looking good on T5-OldTFW. No bootloops. I had earlier but I have changed my setup a bit. Dirty flashed over Temasak and another AnyKernel kernel.
[ONE Original Android Development] LiquidSolstice:
"Multi core performance" isn't offering you anything. Overclocking your computer and your router do have things to offer you. You're not getting "challenged" by anything. You're trying to see how high you can game benchmark scores, and if I'm totally honest, you shouldn't be bugging a kernel developer on ways to do that, not when no one else benefits from that and everyone else would suffer.

If you're really insistent on a useless pursuit of this notion of "high performance", you should figure it out yourself. You're not trying to "get the full power out of your V8". You're trying to drive the same 75 miles per hour as everyone else but you want to do it at 8,000 RPM instead of 2,500 RPM.

Unless you are compiling code, rendering three dimensional graphics, or performing offloaded number crunching for DARPA, nothing you do on your phone requires the performance you're looking for, and at worst, you are hurting your device. Good luck with that.
[ONE Original Android Development] RenderBroken:
Are you changing anything from default? Are you having lag and slowness because I have no such issues running on euphoria 5/3. Also what do you get with the stock kernel? Benchmark scores that is.
[ONE Original Android Development] Nandeh:
I'm talking about the battery drain due to new touch firmware, even in Deep Sleep... I have read that it is caused by a problem with new drivers, but didn't understand exactly the reason.

Thanks!
[ONE Original Android Development] schaggo:
[MENTION=2504310]Nandeh[/MENTION] if you can, use the kernel with the old drivers. If you cannot, you may use the kernel with the new drivers included and disable doubletap-to-wake (DT2W), this should lessen the additional drain.

[MENTION=5438598]RenderBroken[/MENTION] I just went ahead and flashed the build built with the "new" toolchain. As the other build, it came straight up. No rebooting or looping at all.

CM12.1, 27.5. build. Regular procedure, wipe /system and then flash rom and addons.
[ONE Original Android Development] RenderBroken:
To be more exact there are certain things in the kernel like the touchscreen, wifi, bluetooth, etc. Each have their own powerdraw. There are some things that we went from 52MHz and were able to downclock them to 19.2MHz to save battery and such like:

https://github.com/CyanogenMod/android_kernel_motorola_msm8974/commit/fa432cd85af00cd4ce23ba2778ff72a62f6b40a1

This is an example. Any lower would cause unstability and any higher than the old default would just be wasteful. Well the new touchscreen drivers looks like a bunch of random numbers but they correlate to different things like amperage to use when asleep and how much to use when touch is detected and for many different situations. Here is the source for the New Touch Screen Firmware:

https://github.com/RenderBroken/msm8974_OPO_render_kernel/blob/0703073e4f230ca42a360bdafab85e1ca9985980/drivers/input/touchscreen/synaptics_firmware_tpk_14001.h

I imagine there was something setup for testing (The higher power draw) and it wasnt removed in this test release of the new firmware. This is why they just reverted instead of fixing it because we don't have the means to correlate the hex entries.
[ONE Original Android Development] TLengert:
I asked the community what they would recommend to take the kernel to a higher performance level. The few tweaks I performed either made little to no difference or made the phone feel slower. I assumed battery life would be a priority on any kernel and am willing to sacrifice that for performance. The developer didn't have to respond but I am thankful he did.

I'm not wanting to "drive" at 8,000 RPM, but I want to be able to when I need to. You don't see the exotic super cars racing around the city and even those cars can drive at lower speeds and RPM's as SMART cars. Why would you want to put a 2,500 RPM governor on your car when it can go so much higher?...

I don't understand your attack on me for wanting the ability for my phone to perform the best it can when it is needed. Either way, it seems it is best I keep my findings to myself or start a new thread for this subject.
[ONE Original Android Development] RenderBroken:
Using my stock settings I was able to get 988 Single core and 3097 Multi. What is average for stock kernel? I would flash a rom and see but don't have time if you already know off the top of your head. Really curious because I really feel that this is the smoothest I have ever had Android so I want to see if something else is causing a bottleneck. Hell it could even be the new Touch Firmware. Could be causing undue overhead and is tied to the extra 30ma/h drainage.

Also I wanted confirmation. Has ANYONE had any bootloops? And I mean without having to do the special reboot while in recovery hack. I just want people to flash the kernel like normal. Want confirmation that we are past this or at least making headway.