yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] SanXacobe:
Figured if I'm finally going to post something on XDA might as well be something that potentially bums out a dev!

Kidding aside I've dirty flashed R11-T5-OldTFW over R9 on smoki3's latest Euphoria rom with no issues, but actually resorted to that version as my initial attempt with R11-T5-NewTFW-NewTC yielded bootloops. To be fair I didn't try any pre-wipe of /system or post-flash shutdown from recovery tricks. If you'd like me to attempt either of those or try it again with an amended process I'm all yours.
[ONE Original Android Development] HaTrED_:
Flashed and booted up just fine! :good:
[ONE Original Android Development] RenderBroken:
Sorry, we all know first posters don't have anything worthy to say or post anything factual so I will just ignore yours ;)

BS aside, thanks for letting me know! I have my eye on a couple different commits that are different than normal. I will release new test builds tomorrow and I hope that those of you who had bootloops would do me a kindness and flash them at your convenience. They will be rapid fire. Also they will ALL have the new firmware and are just builds to rule out the problem commit. Once I know the commit causing me headaches, I can either just remove it or find out why and fix it if possible.
[ONE Original Android Development] SanXacobe:
It just so happens this unworthy, non-factual lurker has the day off tomorrow. I'll keep my eye on the thread and thanks for all your hard work.
[ONE Original Android Development] Nandeh:
Hi mate.

Unfortunately the drain is still present right now disabling dt2w... It worked some days ago but not now.

And is not possible to me use the phone with old drivers, it becomes unresponsive each time I put it in my pocket :(

Hope it can be fixed soon

Thanks anyway :)
[ONE Original Android Development] schaggo:
[MENTION=2504310]Nandeh[/MENTION] as I said, it must not forcibly be the touchscreen driver. Your drain might come from elsewhere.

Unfortunately you give no information whatsoever, so one can not help you.

Please instal BetterBatteryStats (free version available here on xda, search using google) and give your wakelock and drain statistics. It could be anything.
[ONE Original Android Development] :
on f2fs still bootloops. Tried new touch firmware both versions.
[ONE Original Android Development] RenderBroken:
What partitions are you changing to F2FS?
[ONE Original Android Development] :
data and cache. System on ext4
[ONE Original Android Development] RenderBroken:
Guys, I still don't have a definitive answer to why some boot loop and some don't. The issue does not make any sense to me. Does anyone have any thoughts or ideas? I am game to hear you all out on what your gut tells you.
[ONE Original Android Development] RenderBroken:
I am going to do another test build. One thing I did from R10 to R11 was update the toolchain. I don't think I have received a definitive answer regarding whether or not the toolchain may be the issue. Expect a new build very soon. Please test and get back to me in the thread.
[ONE Original Android Development] RenderBroken:
Here they are:

New Touch Firmware

Old Touch Firmware

Thanks Lady and Gents!
[ONE Original Android Development] nickhaven:
I see some notes about this kernel supporting wiimotes. Once I install this kernel, how does the wiimote pairing work? I have tried apps and in the Bluetooth stack. Is there a recommended process?
[ONE Original Android Development] RenderBroken:
You should be able to just connect to it like a normal BT device. At least that's what was told to me, I still need to try it out.
[ONE Original Android Development] Nandeh:
Hi again.

My problem is not wakelock related, I'm sure of that. The issue started just when new touch firmware appeared and I started to use kernel with its drivers included.

Anyway maybe this is not the thread to talk long about this...

Sorry for the OT.
[ONE Original Android Development] RenderBroken:
I agree, the problem is not a wake lock. It's just the new firmware itself causing the extra drainage. This is why it was pulled.
[ONE Original Android Development] SanXacobe:
Both R11-T6-OldTFW and R-11-T6-NewTFW kernels work perfectly with a dirty flash, no special steps. Don't know what kind of magic you worked but everything seems perfect on my end. Good work!
[ONE Original Android Development] nickhaven:
Hmm if that is the case maybe my ROM needs to support wiimote pairing too.
[ONE Original Android Development] RenderBroken:
I will take a look into this. I believe there may be something I have to enable in my defconfig.
[ONE Original Android Development] dahndahnbo:
Juste to say that i juste flached the R11-T6-OldTFW and have nom problème at thé boot nom boot loop like in thé preview version i am on the last stable Euphoria 03-05

PS: when i flach yesterday thé laste version only this one work for me R11-T5-OldTFW, thé others give me a boot loop ans lost my synapse installation and now all is in order after today version

Thank you Rendre
[ONE Original Android Development] SlickMeister:
Flashed R11-T6-OLD-TFW straight over R11-T5-OLD-TFW and got bootloops running Resurrection Remix. T5 was running perfectly fine for me.
[ONE Original Android Development] Nandeh:
I think you should flash ROM + Gapps (if needed) when you dirty flashed a kernel Anykernel based like RenderKernel.

I have flashed this way since almost first release and I haven't got a single bootloop.

I use to wipe cache and dalvik too when upgrade the kernel version.
[ONE Original Android Development] SlickMeister:
I actually wiped system partition, installed ROM, Gapps, etc and then the kernel, and I had the same problem. I did not wipe cache but I did not think that would be related to the bootloop?
[ONE Original Android Development] dude6595:
flashed R11-T6-OldTFW on euphoria, no bootloop
[ONE Original Android Development] RenderBroken:
Using F2FS or any other change like that? What Rom did you flash?
[ONE Original Android Development] schaggo:
CM12.1 nightly from 28.05. wipe system, flash rom, kernel and packages. Booted straight through, no hickups. Interestingly enough, caches were rebuilt although I did not wipe either cache.
[ONE Original Android Development] RenderBroken:
yea weird. I did not make any changes to my updater-script that would wipe caches or such. Maybe the problem was the toolchain. Not sure but i really hate leaving something unfinished. I have other projects I need to work on but want this kernel on solid ground.
[ONE Original Android Development] _ASSASSIN_:
you should try and make a Linaro or stock google GCC toolchain build to really narrow down the issue IMO.

Also I just noticed that it doesn't say in the OP, what optimization level do you use? -O2 or -O3?
[ONE Original Android Development] RenderBroken:
Well, for t6 I just used the same toolchain I used for r9 and under. I know that one is solid. So I don't think doing a build with the other toolchain will do much good. Also I use - O3.
[ONE Original Android Development] dolbylogic:
I flashed T11-R6 New Touch Firmware and no bootloops on my OPO. [MENTION=5438598]RenderBroken[/MENTION] thanks once again... CM12.1 05/29/15.
[ONE Original Android Development] schaggo:
I had flashed both verdiond og the previous release and had no issues. Maybe unfortunate luckypunch at exactly the wrong moment.

While typing this message I see my touch issues back. I can barely type a correct word. Is the synaptics commit really included in the build which should contain it?

I'll flash back to R11-T5 which had excellent touch.
[ONE Original Android Development] Norapapa:
No bootloops with R11T6 old and new with euphoria 3.5.
[ONE Original Android Development] ilfat12:
R10 on Euphoria - bootloop

R11-T5 on Euphoria - bootloop

R11-T6 on Euphoria - bootloop

is started after power off for a few minutes but not always

R11-T3-ramdisk on Temasek - no problems
[ONE Original Android Development] SlickMeister:
Yes. Sorry I forgot to mention that, I recently switched data and cache partitions to F2FS. I also flashed Resurrection Remix.
[ONE Original Android Development] Norapapa:
2 reboots in 3 hours with R11T6 old and euphoria. Back to R9
[ONE Original Android Development] RenderBroken:
Yes I am sure. But I think I named them backwards like a dummy. It's a pita to keep track of a revert of a revert of a revert commit. Lol sorry guys. I have edited the post I linked them in to reflect the proper version.

What is your normal flash process? Thanks for your help!

Any logs? I have not had any reboots and no one has reported any so I am more inclined to think it's something on your end but you never know. Thanks for the report.
[ONE Original Android Development] Flak:
Not to add more to this. But was anything in regards to WiFi changed in the R11 builds? I am getting horrible WiFi performance with the R11 builds so I am back to R9.
[ONE Original Android Development] RenderBroken:
yes, CM merged in new Wifi drivers. My wifi has been fine so I have not noticed and issues. What problems are you having? Is anyone else having such issues?
[ONE Original Android Development] Flak:
Extremely slow, or at least noticeably slower than LTE or HSPA for me. Slow enough that I am having issues using more than one thing at a time that uses network access. So say, I can't (or have lots of trouble) downloading from the play store and browsing the web at the same time on the phone. Or playing a game with an online component while something is downloading. I'm going to assume my other issues are also related to the speed problem. Play store downloads timing out, have to try to hit web pages multiple times for them to load, etc.

If it matters for this at all, I am on DU 5/26 weekly. I did a clean flash of everything last night to make sure something else wasn't causing the problem.
[ONE Original Android Development] dolbylogic:
[MENTION=5438598]RenderBroken[/MENTION]

I been having WiFi connection and disconnection issues. This is happening on both OPO's. But I updated both OPO's CM to 05/29 build in the morning and the problem seems to be gone, but I have not tested yet. I will test it again when I get home from work or my wife complains again about the WiFi. I have seen it that when WiFi disconnect you also lose Mobile Data. You will see an ! on both WiFi and Mobile Data. Sometimes you have reboot to get Wi-Fi and Mobile data back...
[ONE Original Android Development] RenderBroken:
Thanks guys! I will go ahead and revert or see if something will change in the near future. Either way I will look into making improvements for r12
[ONE Original Android Development] ilfat12:
[MENTION=5438598]RenderBroken[/MENTION]: "What is your normal flash process? Thanks for your help! "

Nandroid backup, UKM uninstaller, flash the kernel, reboot, sometimes wipe the cache and dalvik.

Phone reboots and I see logo 1+ and reboot again, logo 1+, reboot and so on.

It does not occur every time. Sometimes it's normal start.

The same thing happens if I turn off the phone and connect the charger (the screen is turned on, the logo 1+, vibration, restart and further cycle).

In short the phone does not start at a very early stage.
[ONE Original Android Development] dolbylogic:
Mate you need to provide more specific information.. For example: what version of OS are you using? Nightly or stable? What version of the kernel are you flashing? etc, etc, etc:D
[ONE Original Android Development] RenderBroken:
Thanks! I will try the same process myself. I have been doing clean flashes with all my builds and just cannot get it to bootloop whatsoever but I am not uninstalling UKM. Why are you uninstalling it?
[ONE Original Android Development] ilfat12:
[MENTION=3813765]dolbylogic[/MENTION], If you are interested, see above. I wrote ;)
[MENTION=5438598]RenderBroken[/MENTION], I want to defaults settings of your kernel and that nothing was left of the old kernel.

I do not think that the problem lies in the fact that I remove UKM.
[ONE Original Android Development] dolbylogic:
[MENTION=6693249]ilfat12[/MENTION] Oops... My apologies i did not see post #1494 and post #1497. I agree with you uninstalling UMK should not have any effect. As matter fact my sequence is:

ROM CM12.1 , Busybox uninstaller , Busybox 1.23.2 , SuperSU 2.49, UMK Uninstaller , RK Kernel , RK UMK , Full Oxygen Modem , Gapps and blah blah blah (the rest of the apps I flash)...:p
[ONE Original Android Development] Hiro Nakamura:
Hey renderbroken,

there is a new touch screen firmware with a battery fix floating around. Will you implement it? It's still experimental.
[ONE Original Android Development] RenderBroken:
Hard to say, I have seen it but I think that will even change soon.
[ONE Original Android Development] RenderBroken:
Well you never know. Could be something similar to when LP first came out and when you flashed CM12, and you had done a factory wipe, sometimes it would mess up the mounting of /system and the flash would fail. I am curious if something like that is happening. One thing for sure is the number of ppl having bootloops has been drastically reduced or at least the number of reported ones.
[ONE Original Android Development] schaggo:
Bootpoops again...

So this morning my bacon started to bootloop again. I flashed back and forth a bit until I decided to apply a system and document it, till I get a running config. I spent the last 1:30h flashing CM12.1 todays build 30.05. Two procedures:

1. Wipe /system, flash ROM, flash kernel, reboot from recovery.

2. Wipe /system, flash ROM, flash kernel, turn off. Wait 10s and turn on.

Each ROM+kernel combination was flashed at least 3 times. I redownloaded all files to make sure I have the "4real" ones. For easyness I made up a new moniker, an added ".1" means newTFW. All kernels are from the R11 release.

With direct reboot after flash, hitting "Reboot system" button at TWRP success screen:

1. T6 boots up fine. And again. And again.

2. T6.1 loops. And again. And again. Experiment: T6.1 dirty over working T6; nope, loops.

3. T5.1 loops. Again. And again.

4. T5.1 newTC loops. Again. Still does.

Turn off after flash and wait 10+ sec:

5. As T6 will probably boot, I'll set off with T6.1. Which loops. Funny fact: I flashed it earlier and let it sit for several minutes, it booted up fine. LOL and it now did just now, I have let it sit for ~30secs.

I have to leave now but I'll continue flashing on the go and will update this post once I get home.
[ONE Original Android Development] RenderBroken:
This makes absolutely no sense . . .lmao

Thanks for the great info. I have one. . .last . . .thing to try before I go in and start blowing stuff up lol. If I have to, i will just omit everything that made up the changes in R10. This issue is getting old, makes no sense, and I am just ready to move on.
[ONE Original Android Development] drdrewdown:
Latest test build is working flawlessly over the past couple days, keep up the great work Render
[ONE Original Android Development] samuk190:
can please implement gpu 27mhz step?
[ONE Original Android Development] falco090:
Unusable website.

That website isn't mobile optimized. Everything says ... And you can't read the names until you go into landscape even then, you can't see the dates of the kernels to see which one is the latest. . Maybe it's just me? I don't know.
[ONE Original Android Development] schaggo:
Yes I agree. As the device seems to boot if you turn it off and let it rest for a while. Could it be something external and not a change to your kernel? Say, cyngn pushed an updated bootloader which triggers something which was sleeping in your kernel since ever, but never triggered? Or something like that? Dunno... Either way, running R11T6.1 now on top of CM12.1 from 30.05. and it booted successfully after I let the device be for a minute or two.

Another question: the cpu max speed gets reset from time to time, from 1900 back to 2500MHz. Could that be the hotplug? I'm using your stock setup with adapted Smartmax parameters. And theoretically, if it wouldn't reset all the time, max cpu freq of 1958MHz. I dont use UKM&Synapse, I use Kernel Adiutor.

Is in since several weeks already. Let your device rest and the GPU will eventually scale down to 27MHz.
[ONE Original Android Development] Nandeh:
It happens to me too, but I remember it worked correctly last time I accessed the website... Weird [emoji16]
[ONE Original Android Development] HaTrED_:
Flashed R11-T6 and no single issue so far!
[ONE Original Android Development] RenderBroken:
Not needed

really. Just seems like a wasted step a when the gpu ramps up during touch events and other situations. So its also wasting time that it takes the gpu to get to that needed frequency. What ppl don't understand is 27mhz is already used as the gpu's "slumber" state frequency. Lastly if you were to graph out the time spend at each frequency and I added in 27mhz, you would see 27mhz used only a fraction compared to the others.

yea something is not right. Maybe need to rollback or apply an update to the webserver. We use h5ai and there are alot of cool features coming in the future.

I will take a look and see why it's not being respected. Thanks again!
[ONE Original Android Development] samuk190:
ok but i want 27mhz step gpu, don't matter haha, boeffla uses 27mhz step, why your kernel no? i can save alot of battery placing the gpu in powersaver 27mhz.
[ONE Original Android Development] Almayce:
Nice attitude, bro. I don't know if it's only your bad English or you really intended to be that rude though.
[ONE Original Android Development] samuk190:
and i agree that is not tottaly necessary but for me that is a battery saver fan, i need that.

Like an option for advanced users?
[ONE Original Android Development] DerRomtester:
His kernel has this idle step, too as he explained above.
[ONE Original Android Development] samuk190:
i live in brazil, i don't speak an good english, Im don't rude, sorry
[ONE Original Android Development] RenderBroken:
I doubt it's even a measurable difference. Also of it was such a good idea to add the slumber freq as a gpu step, QCOM would have done so. All you are doing is creating a micro stutter because 27mhz is soooo low it's not usable for anything. When you touch the screen the gpu governor ramps up. Adding that extra useless step just makes it work harder to get where it really needs to be. Lastly, and I say this without any disrespect, this is not boeffla's kernel. We all have our own vision of what a successful kernel should be. Mine does not include adding a useless step that is already in use as the default "slumber" freq. Boeffla added it in as an actual usable step, not just only for "slumber". I see this as unnecessary.

The above concept works with CPU Freq steps too. Look at the second to lowest freq you use (First step is the idle freq, similar to the gpu's Slumber freq) with something like Synapse or Kernel Adiutor and take a look at the time in state. For me I use 146MHz as the lowest so the next one up is 223MHz. 146MHz has been used for 1 hour 22 minutes and 223MHz was used 1 minute 31 seconds. CPU Governors are also very different from GPU Governors, this is why such steps don't degrade user experience for the CPU.
[ONE Original Android Development] Nandeh:
[MENTION=5438598]RenderBroken[/MENTION] love your arguments and your patience. I learn a lot each time I read you [emoji106]
[ONE Original Android Development] RenderBroken:
That's what I am here for. Some people get caught up in a change the logically seems to make sense. Logically adding 27MHz seems like a good idea but when everything is considered and research is done you will find that its not a good idea. Boeffla knows his stuff. I would imagine he has made other changes that support the GPU change. I know that in my current setup its not. But it is also not part of my design for this kernel. I wanted a kernel that is more performance over battery while maintaining solid battery life though. Also it takes perspective, I noticed English was not his first language and know things will and DO get lost in translation. This really hit me when I was Deving for the G2 and was finding my my kernel being posted on different foreign sites. It was a pleasant surprise to see such interest. I say this because I have had to deal with alot of different ppl that cannot speak English as eloquently. One last thing to keep in mind about this thread is from day 1, I treat this as a Development thread that is noob friendly. You cant expect anyone to learn properly by just telling them all to Google it. Sometimes things need to be explained in plain ol' simple talk and use simple reasoning. I am like this because of my job(s) and background. I am used to talking to lawyers, doctors and business owners and tell them the reason their (insert stupidly easy problem to fix) WAS easy to fix but its common and I do this for a living so its easy for me, or whatever it is, to make it not seem as big of a deal so I get paid for the 1 hours drive time and 5 minutes of work at $125/hour without them feeling a complete idiot. lol Customer service is everything. Being polite will get you further than just telling ppl to search google all the time.
[ONE Original Android Development] samuk190:
when i get rich,i will love to donate a big money quantity to you haha

(My english was learned from google translator)

Yes, i understand. if you put 27mhz the gpu, it will cost the cpu?

Ok.. and what about gpu voltage? -5mv ? secure voltages?

im using your kernel, and yes, have alot of options, and where i can download the R10? i tried find, and i only find old build r9

obs: You can't google about gpu of snapdragon, no much information can be found about that.
[ONE Original Android Development] mp3deviant721:
There's a test build on page 148 if you are on Tapatalk.

I have that test build installed on an unofficial Euphoria... Booted up fine. And is working great right now. We'll see how it does on subsequent reboots though.

OnePlus One | Powered by EuphoriaOS x RenderKernel
[ONE Original Android Development] RenderBroken:
No problem man. I get it. Yea the GPU is something that doesn't get as much exposure as CPU Governors and such because it is different from device to device where CPU governors can pretty much be used across different devices more easily. No, adding the GPU step of 27MHz doesnt hurt the CPU but causes the CPU to have micro lag that "could" be present while gaming or doing other intensive graphical actions. Not sure about GPu Voltages though. That is not something I have really explored on any device so I cannot weigh in on it. R10 was having weird issues with Bootloops so I pulled it to avoid more ppl having issues. There are some nice Test builds of R11 floating around about a page back. I would recommend it. The one labeled R11-T6-NewTFW has the new touchscreen firmware that will fix issues some are having at the cost to more battery drainage during deepsleep. But the drainage isn't much.
[ONE Original Android Development] mp3deviant721:
I got a couple of questions about the sound tweaks in this kernel.

1. Are you using Franco sound? (Looks similar to sound control in AK)

2. Kernel Adiutor reports that the headphone volume can be adjusted below 0 while Synapse says it can't... Any reason why this would be?

OnePlus One | Powered by EuphoriaOS x RenderKernel
[ONE Original Android Development] DerRomtester:
Franco sound supports also negative values from - 20 to + 20. So it is an app specific problem.
[ONE Original Android Development] abhi08638:
If that's true you can modify UKM to show those values. I'm in the process of doing that already and will be posting an optimized version for bacon only on the AK thread. Thanks for the info!

Edit: aaaandddd that parts done
[ONE Original Android Development] RenderBroken:
Why only for the AK thread? Are you only using AK's version of UKM? His is built in now so how would you do that?