yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] schaggo:
Sorry, unclear wording: it bootloops, no matter if R11-T1 was flashed together with the rom or after a successful boot of the system. I will make more tests and see if I can somehow draw conclusions.

Gnah, still somewhat unclear: your kernel bootloops, no matter what. Stock kernel does not, and boots up fine.
[ONE Original Android Development] vikrant82:
R11-T1 also bootlooping on latest bliss 20150518-1807 (with all tricks that have been mentioned).
[ONE Original Android Development] dolbylogic:
Finally it boot up...

I flashed R11-T1 and it bootlooped once and then it boot up to android. I am on CM12.1 Nightly 05/18/2015. I did a dirty flash; not a clean wipe. With previous R10-Tx versions I always had bootloops no matter if I dirty flash or clean wipe. Hope this helps...
[ONE Original Android Development] Norapapa:
R11T1 with euphoria goes bootloop, only nandoid have rescue my system
[ONE Original Android Development] schaggo:
No, you could have simply reflashed your rom.

Anyway, got it to work. Same procedure as with R10-T2.

Wipe system, flash rom, gapps etc.

Boot the stock kernel, let the rom settle for a while (browsed a bit and checked email)

Reboot to recovery, flash renderkernel, shut device off (take off of power or it will boot immediately)

Renderkernel boots up fine.

I cannot tell if the complete powerdown from recovery is needed, as the device booted trying it this way. Next time I encounter the bootloop I'll apply the same procedure without powering down.

And of course, no logs... but I guess you expected that.
[ONE Original Android Development] HaTrED_:
+1 on boot looping poop and poop! :(
[ONE Original Android Development] erad1:
I got it to boot on stock Y17L. First I just flashed the kernel straight up and I got the boot loop, but then I went back into recovery...wiped cache, used the UKM uninstaller then flashed R11-T1. I then re-flashed Render UKM, wipe cache once again and "boom goes the dynamite"! All good here.
[ONE Original Android Development] RenderBroken:
Thanks for yalls help. All the info is helpful in narrowing down such a weird issue. I will look into the UKM angle. I do know that sometimes in flash my new kernel and on first boot synapse tries to automatically apply the settings on top the new kernel and it can cause kernel panic thus causing a reboot. I may need to setup my script to manually clean UKM data on kernel flash. I will whip up a new Test build asap.
[ONE Original Android Development] kalpik:
UKM shouldn't come into play at the very first boot screen, should it?

Sent from my Oneplus One
[ONE Original Android Development] RenderBroken:
You wouldn't think. But I also wouldn't think some random commits from cm would cause bootloops like this either. I am just looking at common denominators.
[ONE Original Android Development] schaggo:
I don't use UKM nor Synapse. I configure only the exposed basic characteristics of the kernel using Kernel Adiutor, I don't apply on boot though, I do it manually upon each boot.

This might not rule out something in your scripts, but it's not UKM or Synapse per se.
[ONE Original Android Development] RenderBroken:
Yea maybe, Its hard to tell really.

[MENTION=5284595]YoshiShaPow[/MENTION] was having similar issues with bootloops and he was able to fix them by updating TWRP. Guys, even if you have the most up to date TWRP, could you fastboot flash the newest version? If someone could try and let me know I would appreciate it. I don't have any bootloops so I cannot test for myself.

Also, I am going to do a test build of my latest kernel but with RAMDISK included. This new test build will not use AnyKernel and is there just to confirm if including Ramdisk fixes this issue. That will tell me that the kernel itself is fine, something with AnyKernel would be the culprit if it boots fine for those that have been having issues.
[ONE Original Android Development] Nandeh:
Dirty flashed last R11-T1 over last Blisspop nightly and everything working perfect.

The procedure as always:

1. Flash ROM

2. Flash Gapps

3. Clear cache and dalvik

4. Reboot to recreate dalvik cache

5. Boot into recovery

6. Flash Kernel and UKM

7. Reboot again

I haven't got never a bootloop with this kernel using this steps. Hope it can help you.

Thanks [MENTION=5438598]RenderBroken[/MENTION] for your work and your awesome support!! :)
[ONE Original Android Development] drdrewdown:
On mokee personally. Not using UKM/Synapse instead kernel audiutor & never seen a bootloop
[ONE Original Android Development] RenderBroken:
Yea, contrary to whats going on in the thread, bootloops are still pretty rare. Because you have to take into account the number of downloads compared to the number of actual complains. Its less than 5%. So I don't expect it to be an issue for everyone but I don't want it to be an issue for the 5% either. This is something that should just work.
[ONE Original Android Development] 1337jay:
I went back to Euphoria to try the newer versions of your kernel and I ended in a bootloop aswell. I wiped everything, flashed euphoria and gaaps and then normally booted the rom. After that I went back to TWRP (latest version), flashed R11-T1 + UKM and ended in a bootloop. Tried R10-T3 aswell, same thing...it was all working well with R9 back then.
[ONE Original Android Development] RenderBroken:
Thanks! I can mark that off my list.

I am just about done with my new test build that has ramdisk included.
[ONE Original Android Development] vikrant82:
Ok. Some success on Bliss's latest with R11 T1. I think as someone mentioned in the thread the key is to let bliss default kernel boot and rom settle down. Then sneak back into recovery and install render.

Off topic. I didn't have any touch screen issues or just ignored them. BUT now I realize the touch is so much better with new driver. So if we disable double tap to wake, there is no other regression from TouchPad perspective, right?
[ONE Original Android Development] RenderBroken:
For the main point, I was going to ask some ppl to give that a shot. See if booting the rom first WITHOUT my kernel then going back into recovery to flash my kernel helps. Can I get some more ppl that were having this issue to confirm this either helps or doesn't? Thanks guys!

As for OT, Not sure what you are asking.
[ONE Original Android Development] vikrant82:
Read somewhere, the extra power drain during screen off with new Synaptics driver is only when you enable screen-off gestures. I believe R11 T1 has that driver. Sorry for not being clear.
[ONE Original Android Development] RenderBroken:
Oh ok gotcha, I had not heard that but it makes sense.
[ONE Original Android Development] HaTrED_:
Well, some good news although really weird... Finally got a boot up after flashing latest R11-T1.

Followed this procedure:

- uninstalled UKM,

- flashed R11-T1,

- wiped caches,

- reboot,

- profit!

I'm gonna try another approaches to see if i can understand - under my limitations - what's going on!

[MENTION=5438598]RenderBroken[/MENTION]

Mate, could you provide R11, if possible!, without latest touch screen drivers?
[ONE Original Android Development] RenderBroken:
R11 comes without the latest already. Only that one R11 Build kept the new Firmware.

Also thanks for reporting what worked for you.

Here is the latest test build with Ramdisk included. It will ONLY work for CM12.1!

R11-T3-Ramdisk
[ONE Original Android Development] 1337jay:
No more bootloops on Euphoria with a clean flash, great work!

EDIT: It's actually stuck on the Euphoria boot animation now..seems like something is still off.
[ONE Original Android Development] HaTrED_:
Found some correlation: as soon as i flash UKM 3.8.1.4-> boot loop poop!!!

Uninstalled it, had 1 boot loop then it booted up normally!

Tried reboot again -> boot loop!! From this point onward i was never able to boot up again under R11-T1.

Kinda Fanky heim? :D

Gonna try R11-T3!

EDIT: [MENTION=5438598]RenderBroken[/MENTION]

R11-T3 boots up fine and reboots without poops! Always with UKM installed! :fingers-crossed: :good:
[ONE Original Android Development] jdjta:
Same for me on NucleaROM 2.8. R11-T1 worked without problems but now getting into bootloop when I flash it. Even tried reverting to R9 but can't get past bootanimation anymore with Render. Flashed stock ROM-kernel and boots to system again..
[ONE Original Android Development] RenderBroken:
So it seems we are narrowing it down. I do know that UKM has some soft of survival script and such. It may even be the way or timing of how some of its scripts run. I should have one more test build where I adjust the boot script to clean out some files for ukm so when you flash my kernel then open ukm, it treats it like a clean flash instead of trying to reapply the settings on Boot.
[ONE Original Android Development] jdjta:
I have to say I'm no expert but for what it's worth, I don't use UKM...or is it installed with the kernel automatically? I managed to get back to R9 after booting on stock. Works fine for me, smooth and decent battery without to many tweaks (gov: intelimm, io: row 1024). Thanks for your dedication, support and time spent on bringing us your masterpiece :D
[ONE Original Android Development] RenderBroken:
Thanks for your input. So its not UKM specifically but something about removing it first before flashing my kernel.
[ONE Original Android Development] dolbylogic:
[MENTION=5438598]RenderBroken[/MENTION]

I found that UMK puts a backup script file in the addon.d folder in the system. The name of the file is UMK.sh, I deleted it and dirty-reflash your kernel alone without over writing UMK and it bootup fine no bootloops.. I am going to try to dirty-flash your kernel and on top to reflash UMK.. Hope this helps... I am reflashing R11-T1..

Edit:

Reflash R11-T1 and UMK3.1.8.4. UMK.sh removed.. I have one boot loop then it boot up as normal.. Hope this helps...
[ONE Original Android Development] xtremez:
Been enjoying your kernel and looking for the next version! Anyone manage to get R10?
[ONE Original Android Development] HaTrED_:
[MENTION=5438598]RenderBroken[/MENTION]

I've been testing R11-T3 for last couple of hours and without any issues, the same ones that i was facing under R11-T1 - boot looping, reboot normally but after doing it my device went straight away on boot looping again.

With or without UKM, wiping, or not, cache or dalvik, R11-T3 just flashes and boots every time so it seems that something is going on with anykernel format?

Other then that, really appreciate your work and efforts! Great kernel! Thanks! :fingers-crossed:
[ONE Original Android Development] RenderBroken:
Me too! Did you get your OPO? I knew you were talking about it but hadn't heard for sure.
[ONE Original Android Development] MBurns2:
yeah mate.. i had the issue with g2 and i decided to take the opo.

This is my first day with it and i love it ! have a good day :) we will have the pleasure to speak again
[ONE Original Android Development] RenderBroken:
I should have a new build up soon. If there is a feature that you would like to have in a kernel, please share. This is a friendly thread for up and coming devs, seasoned devs, and noobs alike! (As long as you follow the rules :) ) If you have any questions, please feel free to ask. If you are thinking of getting into building kernels, please ask!

One thing I was thinking of adding is GPU OC, Updating Sound Control Further, and a few subsystem bring ups. I plan on working on this today.
[ONE Original Android Development] usmani:
Erm boeffla gestures? Plus Franco touch boost
[ONE Original Android Development] _ASSASSIN_:
Slimbus OC/DAC oversampling/CAF audio updates please? :).

Also a very noob question, but I want to compile this kernel myself. Could you direct me on how to do so and what toolchain you are using?

I'm on mint 17.1
[ONE Original Android Development] RenderBroken:
Gestures, maybe. I have to see if that fits with the theme of my kernel and/or if it makes sense to do so. Like someone asked for Sweep to wake but we already have DT2W so there is really no gain and tapping anywhere on the screen seems easier to me. This is just an example but I will look into it!

Most likely I will not use Franco's Touch Boost. I use CPU-Boost from CAF that is modified for hot plugs to use as well. Can you give me any benefits to using it? Thanks for the suggestions!
[ONE Original Android Development] RenderBroken:
Audio is def something I want to overhaul. Just have to see when would be best to do so.

As for A how to build my kernel, that I will write up and share below OP.
[ONE Original Android Development] cerealguy:
I like your philosopy! I will try your next release! Thanks for your efforts!
[ONE Original Android Development] _ASSASSIN_:
awesome stuff dude! Man am I looking forward to your work :) Thanks for doing this all.
[ONE Original Android Development] smoki3:
Do you have a test Version with working doze mode? Getting still best battery with your kernel
[ONE Original Android Development] _ASSASSIN_:
http://xdaforums.com/showpost.php?p=59465562&postcount=108
[ONE Original Android Development] :
Hello!

Little noob question:

Should I deactivate MPDecision? Im just curious because Synapse says that I should deactivate it (when I use another hotplug, I mean) and I read that I should deactivate it. But Boeffla said that we should leave it activated because it manages thermal throttling etc.

Thanks!
[ONE Original Android Development] abhi08638:
You should not have more than one hotplugging governor on at a time. MPDecision is a hotplug governor, so you must disable it if you want to use another one on the hot plugging page in synapse
[ONE Original Android Development] byAidan:
Great kernel so far thanks for the work! :)

I have a suggestion, please could you consider adding f2fs-mixed support?

Thank you!
[ONE Original Android Development] usmani:
I like the sweep to sleep on screen one. And there's no harm in adding touch boost, it's battery friendly and manages frequencies better, anyways you're the dev you know better. :)
[ONE Original Android Development] RenderBroken:
http://xdaforums.com/showpost.php?p=59465562&postcount=108

I use a different Thermal Driver that I feel is more efficient that does not need MPDecision. But its better to ask and be sure.

Thanks! I am not sure I will add F2FS Support or if I did, whether or not I would keep it. I may try it but with my G2 Kernel, even though it is up to date, users are having weird issues. That could be because all of the LG hax mixed in throughout the source causing some unseen bug or its just F2FS not ready for the wide world on all devices.

Touch boost is essentially CPU-Boost. I will double check the code but I am pretty certain the main objective is still the same. But because I was asked for twice. I will look into it with no guarantees. Thanks!

PS: Not all devs know better lol . . .but I do! . . .not really. . .
[ONE Original Android Development] DerRomtester:
franciscofranco said:
[ONE Original Android Development] smoki3:
I tried the R2T5 build. I miss the Bricked hotplug.
[ONE Original Android Development] schaggo:
Had a system freeze and subsequent crash. Here's the rundown:

Enabled "Simple GPU Algorithm" without changing any values anywhere else.

Launched "Ingress" (the game).

Ingress acted all weird, (partially) didn't react to touches.

Went back to the launcher (Home button).

Launcher came up but was seemingly frozen as well, didn't react to touches.

Tried putting the device to standby by pushing the powerbutton, where it did not react.

Tried powercycling the device by holding the power button, I believe it rebooted before the power button sequence finished tough.

last_kmsg attached.
[ONE Original Android Development] RenderBroken:
Thanks! That is essentially what I have already done with my version of CPU Boost. Its modified from Stock QCOM. I will still need to dig through the code but he may have externs that he uses with his hotplug driver and maybe more. Not sure, I have not really had a device where it also had Franco Kernel. I may need to give it a go. Thanks for the info!

The next build will have it back, now that the issue with LCD Notify causing reboots coupled with Ambient Display has been fixed. Thanks again [MENTION=4804871]DerRomtester[/MENTION] !! With it fixed I can now use Bricked HP since it uses LCD_Notify. The test build I am running has it back.

Interesting, I am a little perplexed. You log you provided was all jacked with wierd NUL Blocks and the last thing in the log was:

Corrected bytes, 2487 unrecoverable blocks

Seems like some sort of corruption NAND wise. Not sure what steps you could take to confirm and repair. IF you do find out please let us know. Thanks again for the log!
[ONE Original Android Development] vindows18:
Can u link me to the R11 kernel ? I looked into the download link attached this thread but couldn't find the latest one. Though I've older version from R9.

Edit : sorry, I found it ! I should've used search before [emoji4]
[ONE Original Android Development] schaggo:
[MENTION=5438598]RenderBroken[/MENTION] ugh, the device is unusable without the new touchdriver. I have outright dead spots where no touch is registered at all, ghost touches (device wakes itself with dt2w enabled) and cannot be restarted properly, it either refuses to accept my finger touching menu entries or touches different areas making the menu close. PITA!

Fun fact: the screen is flawless with the new driver, the dreaded dead spot is gone and all is working well.

DAFUQ is this!? Magic or what? Seriously puzzled...

tl;dr: touchdriver essential to operate the device. I stay on the one-time build with it included or I can forget to operate my device at all and throw it out the window.
[ONE Original Android Development] LiquidSolstice:
TWRP has been updated to 2.8.6.1. Not sure if it will help with the bootloop issues when flashing the kernel, but it might.

Fastboot flash or use Flashify to upgrade.

https://dl.twrp.me/bacon/twrp-2.8.6.1-bacon.img.html
[ONE Original Android Development] dolbylogic:
Some have tried it and it does the same...
[ONE Original Android Development] LiquidSolstice:
Derp. I should have read the thread first then before posting.

Bummer to hear that, though.
[ONE Original Android Development] RenderBroken:
Yea its definitely a weird issue.

I still need confirmation from someone who has bootloops to try and flash the rom and stuff first without my kernel, boot the rom, then reboot into recovery to flash my kernel. If someone can do that I would appreciate it!
[ONE Original Android Development] dolbylogic:
[MENTION=5438598]RenderBroken[/MENTION] which version of your kernel you want us to try? R11-T1 or R11-T3?
[ONE Original Android Development] vindows18:
I'm little late into the game but this might help u in fixing. I tried R10 T2 build first boot gave me a boot loop but second boot did work. And there's something with screen colors I see a bit darker colors compared to stock and ak kernel . Btw I'm on cm12s.
[ONE Original Android Development] RenderBroken:
Really any builds between r10 and 11-t2. R11-t3 has the ramdisk included. It should work without issues thus showing that it's not actually the kernel at fault but the anykernel setup. Ironically though, I haven't changed anything with anykernel for a long time now. . .
[ONE Original Android Development] ilfat12:
Hi! Where can I get the R11-T2?
[ONE Original Android Development] LiquidSolstice:
I don't think there was ever an R11-T2.
[ONE Original Android Development] HaTrED_:
Mate, been there and just have done that! Just now! :D

I'm using: [ROM+KERNEL] Uber CM-12.1---ONEPLUS [AK Kernel] [GCC 4.8 & 4.9] by RobbieL811 + Slim Mini Gapps.

Flashed latest release without any issue noted - wiped system, cache & dalvik - all booted up just fine on first attempt! Tweaked system as usual - DPI's and etc's, rebooted again, all rock stable expect for WiFi which seems to get some "trouble" with certain HotSpots... namely at work!

Next step, flashed you latest kernel - R11-T3 - kernel and then UKM. System booted up fine and till now all seems to be running well and i couldn't replicate the "issue" i was having with AK kernel and corporate Wifi network which - may? - indicate different WiFi driver's between this 2 kernels, right?
[ONE Original Android Development] mp3deviant721:
So I just wanna confirm what I've been reading the last couple of pages...

R11-T3 is the one to flash to avoid issues? I wanna flash it on smoki’s Euphoria and don't want to have any booting issues.

OnePlus One | Powered by EuphoriaOS x Boeffla
[ONE Original Android Development] RenderBroken:
Yes, that is correct.
[ONE Original Android Development] Norapapa:
I have bootloops with R11T3 and euphoria from 03.05.
[ONE Original Android Development] dolbylogic:
Did you wipe your /system?. Also what worked for me was to turn off the OPO from recovery for over 3 minutes. Give it a try...
[ONE Original Android Development] vishalssalwan:
I don't know y, but everytime i use this kernel it results in bootloops. The only way to avoid these bootloops is to switch off the phone for few minutes and then switch it back on. I don't know why it happens, but because of this I was not able to use flashify, or reboot to system after installing a new rom. Now I have installed boeffla kernel and it works smoothly. Please [MENTION=5438598]RenderBroken[/MENTION], if you can rectify this I would be more then happy to come back to this kernel as I had been following this since the initial development. All other aspects of this kernel are just too awesome
[ONE Original Android Development] RenderBroken:
If its too big of an issue, use r9. It's not outdated or anything. But it's up to you, Lord know that if I knew the exact fix, I would do so. I don't have the bootloop issue. So its hard for me to test. I have to put together all of the info that everyone has been adding to the thread and still it doesn't make sense. Also I have been working too much lately so I have been taking it easy this week but I plan on working on the issue this weekend. Thanks.
[ONE Original Android Development] RenderBroken:
The thing for me though is, there shouldn't be any need to turn off the phone for 3 minutes. This is a crazy issue. Lol
[ONE Original Android Development] vishalssalwan:
I know it is too difficult of an issue to check for, as some of the people have it and some don't... I just hope you will soon get a hold on this and get some people, me included, relieved of this :). Anyways, enjoy your week off bro!!! :)
[ONE Original Android Development] dolbylogic:
[MENTION=5438598]RenderBroken[/MENTION] I know its frustrating. Even if it does not make sense:eek:, that is the only way to keep this awesome kernel running in my OPO :D . I would not change it for anything ;) . This is just a small setback :( . I know this is nothing you can not handle :good: . Thank you for this awesome kernel and please don't think for once I am here to criticize your work or anything in the like :p . Keep it up buddy and if you need testers let me know :highfive: ... Don't work too hard.. lmao...
[ONE Original Android Development] 1337jay:
I have tried to let the ROM settle down with the default kernel for a while but when I flashed R11-T3 I ended in a bootloop, stuck at the bootanimation actually. Hoping for a new, working version soon - had to change kernel for now (but this one is the best I used on CM12.1 so far).
[ONE Original Android Development] dolbylogic:
Try R11-T1 it works. R11-T3 I would say you have to wipe /system. Just flash R11-T1 and power off your phone from recovery and wait. You will see; it will work.
[ONE Original Android Development] dude6595:
Add this to the list of odd... Had been using r10 on an euphoria, updated from r9, and hadn't had any issues. I hadn't tried r11 cause people having issues and also hadn't flashed anything since... Yesterday I flash a font I have used many times, and only the font, go to reboot and bam boot loop at the 1+ logo. Didn't have time to mess around with it so dirty flashed rom and went back to r9....weird stuff...