yashsingh1/xdaforums huggingface dataset:
[G2 Android Development] apollo07:
Try this boot.img. Removed

It's RenderKernel extracted from a Bliss-Rom test.

Tested on my D802 running [MENTION=5683755]sudosurootdev[/MENTION] 's vanir 5.1
[G2 Android Development] Lawlrus:
Doubt this should have been posted with it not being released by render. You should have pm'd this.
[G2 Android Development] jeyd02:
I noticed BlissPop 5.1 has a some type of test subject based of render but I mean the official fully functional kernel. With all its goodies.
[G2 Android Development] albertorodast2007:
XDA-Leaks :D

Patience boys patience
[G2 Android Development] Lawlrus:
Bliss has been using blackbird, not render on 5.1
[G2 Android Development] jeyd02:
Ohh, really? Sorry about that and thanks for clearing it up.

Well, hoping to see an more complete version of the kernel :)
[G2 Android Development] bolt890:
1st Build of lollipop 5.1 used Render, the latest one(i.e the 2nd one) used blackbird.D802.
[G2 Android Development] Dr.Vaska:
does anyone solved voice distortion problem ??? AT&T LG G2
[G2 Android Development] :
It's rom side. The patch s pushed to cyanogenmod's Gerrit by rashed. Bliss is using it now. It's just changes to /etc/audio_policy.conf

It also supposedly fixes voip.
[G2 Android Development] raahult:
Copy /etc/audio_policy.conf from stock lollipop rom which do not have this issue and replace the current audio_policy.conf with that.
[G2 Android Development] RenderBroken:
Thanks gents! I appreciate the civility!

I plan on releasing a new build for the G2 this weekend. I have been a little under the weather lately but should have something this Sunday.
[G2 Android Development] Player-J:
Of course, that would be awesome!!! But... Take care of yourself first. We aren't going anywhere. Get well my friend! :)
[G2 Android Development] bolt890:
[MENTION=5438598]RenderBroken[/MENTION] BTW there is Zzmoove governer in the source, it isnt enabled for some reason? Do you plan to add zzmoove?
[G2 Android Development] RenderBroken:
It was causing lockups, so I left it so I could come back to it later. I have a few ideas about the possible causes but I doubt I will be able to address them before the next release.
[G2 Android Development] jeyd02:
Going to have the 5.1 version soon enough? Perhaps tomorrow? :)
[G2 Android Development] RenderBroken:
I could just release with a new ramdisk and boom R11 is compatible. I may throw it together and release tonight just so everyone has a flashable for Android 5.1. I have also been working on a new way to flash and handle the ramdisk but because we have top deal with bump and loki it makes the process more difficult. Just hang tight and I will release R12. It essentially will just be R11 but will work with 5.1
[G2 Android Development] reemar:
[MENTION=5438598]RenderBroken[/MENTION], two things kept me stuck at 5.0.2 and away from 5.1 and are; xposed and f2fs kernel support, but, second you will give us the R12, I can safely proceed to 5.1, thanks for the hard work.
[G2 Android Development] RenderBroken:
Well if what I am working on works like I expect then that changes everything. I am getting everything together right now. Some minor changes will be in R12. Mainly I will be trying out a new default setup that on my OPO kernel, it has given AMAZING results. Great SoT and even better performance. I will be changing the default governor to SmartMAX and tuning it in such a way that you wont believe with how smooth it runs that you are actually getting better batterylife than before.
[G2 Android Development] TDSJR:
[MENTION=5438598]RenderBroken[/MENTION]

To clarify, R12 will ONLY work on 5.1?
[G2 Android Development] RenderBroken:
correct, I will make this clear in OP. Still you can have the same setup on R11. When I release I will also post what i have changed.
[G2 Android Development] RenderBroken:
OK I need a tester to test my new build for CM12.1 Anyone up for it?

Also in this build will be using my new self compiled tool chain and new build flags. I built Uber 4.9.3 specifically for our phone. Before I was building with -O2 and now I will be using -O3 among many other new flag changes.
[G2 Android Development] bolt890:
Me.
[G2 Android Development] RenderBroken:
What model?
[G2 Android Development] jameseytickner:
I actually use Interactive and deadline, with some of the values tweaked. But i've not had a single SoD or random reboot!
[G2 Android Development] Andrew_han:
could you share your interactive tweaks? curious to know what gave you those unreal battery stats
[G2 Android Development] bleached45:
I liked wheatly before I started using your interactive. Wheatly had great performance, but I like the balance of interactive here.

Sent from my phone using an app.
[G2 Android Development] fLipz:
just expressing and showing my gratitude how i'm impressed with [MENTION=5438598]RenderBroken[/MENTION] R3 Kernel

Stock Settings

24/7 Data-On (WCDMA Only)

WiFi during Office Hours (still not turning off Data)

Tethering from 7pm to 11 m.n.

Brightness=Auto

Never experience SOD

mahdi-718

Thank You! :good::good:
[G2 Android Development] 1ceb0x:
Awesome stats!!!!
[G2 Android Development] count_martin3z:
Guys, today I had to plug charger because 4% left. Checked the battery stats... Results:

2d 18 hrs

6h 38 min SOT

2h 43 min calls

718 Mahdi and R3 with default settings.

Zach, thank you man so much!
[G2 Android Development] chillstep1998:
I am using Intelliactive for CPU, and simple_ondemand for GPU. When I'm on DorimanxAOSP, I use alucard, and would love to see it in RenderKernel :)
[G2 Android Development] allan1229:
Am I missing something or is Dorimanx only for LG ROMs?
[G2 Android Development] 1ceb0x:
There is a dorimanx port in Vanir thread. Works for aosp but it has some issues...
[G2 Android Development] pippideniro:
Just want to share my experienced with Render Kernel V3 for AOSP ROMs working on Alegen Rom-temasek's Build - V6 which is a CM base Rom:p
[G2 Android Development] RenderBroken:
I have never used that particular hotplug driver. If anything, I would use Myfluxi's hotplug. when I used it for the Moto G it was fantastic! I believe it would scale even better on such a better SoC (400 vs 800) So this is something I will be testing in the near future. I am always looking for better ways to do something. I may try out Alucard's as well just to at least give it a shot. At first thought, I don't think I want to have a kernel with multiple hotplugs. Mainly because what changes to say cpufreq.c that may work and accentuate that hotplug, may hamper another.
[G2 Android Development] Raagh:
i have a wierd problem, when i flash render kernel r3 over latest mahdi(no matter if it is clean install or dirty flash) i lose all data conection. i mean even it says Uknown baseband inside phone information. no Data at all

the weird thing is if i flashed the patch again to go back to the stock mahdi kernel i recover data

any ideas?
[G2 Android Development] 1ceb0x:
I think he was talking about Alucard cpu governor and not hotplug? :D
[G2 Android Development] chillstep1998:
Exactly. Although the hotplug is awesome as well. :)
[G2 Android Development] count_martin3z:
What hotplug is forfor?
[G2 Android Development] simon_lefisch:
[MENTION=5438598]RenderBroken[/MENTION], I can confirm this. Happened on my vs980.
[G2 Android Development] chillstep1998:
Hotplug turns your CPU cores on and off based on utilization. One core is always online. (Online meaning active) There are different implementations of this, based on for ex. work queue or touch (cores on touch), etc.

Sent from my Munsta LG G² from XDA Premium⁴
[G2 Android Development] RenderBroken:
I havent been able to see why but you can fix it by:

Flashing Rom > Patch > Gapps > Maybe SuperSU? Then Reboot.

Let it boot up all the way and you will have Data. Then reboot one mo' gin into Recovery

Flash Render Kernel > Reboot

Then you will be good to go.

It really is weird. I have not tried flashing R3 on an older build of Mahdi so I don't know if its Kernel or Rom related though I do remember seeing the dr87 specifically said its best to do a clean flash on the build so I am not 100% sure. If someone wants to test R3 on an older build of Mahdi and let me know if the behavior still exists, I would be grateful! I am currently not in position to do so at the moment.
[G2 Android Development] simon_lefisch:
I reflashed Mahdi (clean) just to test some things and what I did was:

Wipe data/cache/dalvik/system (2x)

Flashed mahdi/patch/gapps/SuperSU/render

Rebooted

Data did not come on. I then clean flashed everything but render and data was back. Clean flashed everything again (including render) and something, no data. I then flashed ROM patch and rebooted, data was fine. Then flashed render and data was still OK. It was really weird.

In the end it worked out. Just thought it was kinda strange. I wonder of it had anything to do with the changes to the caf branch in the 7/18 build....
[G2 Android Development] jameseytickner:
http://xdaforums.com/showthread.php?p=50357142 used the values from this thread.
[G2 Android Development] tpike1296:
If you need an ls980 tester let me know. Not a dev but I can figure anything out.
[G2 Android Development] bolt890:
D802 :) I'm currently on F2FS do I need to go back to ext4?
[G2 Android Development] RenderBroken:
Building Now! I am pretty excited about this build. As I am with all my builds because they do have a difference between each iteration. I could build nightlies where I make a few commits but there really wouldn't be any substance each update if I did that.

EDIT:

Here you go

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

Also please report back ASAP so I can know whether or not to build for the rest or if I need to make more changes. Thanks!
[G2 Android Development] bolt890:
Nah I prefer those big updates:good: Just waiting for the phone to boot(Switched to EXT4) then ill flash the kernel.

---------- Post added at 03:13 AM ---------- Previous post was at 02:54 AM ----------

I have force closes on NFC and TREBUCHET cant get past the lockscreen keeps soft rebooting. An issue with the ramdisk maybe.(blisspop 3.0)
[G2 Android Development] RenderBroken:
Yea another user of bliss was saying the same. They must be doing something really different from cm. Not sure why they would diverge from them but who knows. I will check their ramdisk too. Thanks brother for testing!
[G2 Android Development] RenderBroken:
I dun goofed . . .lol I pulled the ramdisk from the wrong boot.img and it was a cm12 ramdisk not cm12.1 #fml

I am building again
[G2 Android Development] jeyd02:
Hey, I could test for d801 model if you want :). And do I need to change format to ext4?
[G2 Android Development] bolt890:
Let me warn you my TWRP 2.8.6.1 doesnot like F2FS with android 5.1( after flashing say goodbye to recovery(at least for me) then the recovery no longer boots. The only way to fix for me is kdz, check the twrp thread for I info).
[G2 Android Development] RenderBroken:
Here is a new build for you with the proper ramdisk:

D802

I will build for D801 shortly.

I don't see why F2FS would cause any issues but I do know it does depends on the recovery. If F2FS was not in mind when they built your Recovery then sure, there could be issues but this is just something the user has to be diligent ab out. And this goes to everyone, if you are unsure, Search. If you still cannot find your answer then ask in thread. What I do know is if you leave everything stock. It should work with 0 issues for you. But we are not here to not mess with our phones ;)
[G2 Android Development] RenderBroken:
[MENTION=3941232]jeyd02[/MENTION]

Here is a test build for D801:

https://drive.google.com/file/d/0B-GVJKBx9-Gncms4ci04bGlVZVU/view?usp=sharing
[G2 Android Development] jeyd02:
Awesome, I'll report back to you shortly.
[G2 Android Development] bolt890:
[MENTION=5438598]RenderBroken[/MENTION] still having force closes on blisspop. Email + treb.
[G2 Android Development] RenderBroken:
Can you get any logs?
[G2 Android Development] bolt890:
Is there a way to get em If the phone keeps rebooting. Going to sleep if possible I'll get you some logs BtW why don't you pull the ramdisk from blisspop boot.IMG, I successfully booted render kernel included in blisspop first build on ressurection remix rom
[G2 Android Development] RenderBroken:
I did pull it straight from Bliss. I will just have to dig into it later. Thanks for testing.
[G2 Android Development] RenderBroken:
Ok I see what the problem is. The new ramdisk script I am using to extract was not overwriting properly, After just deleting everything, it provides the proper ramdisk extracted files. I will rebuild one more time.

I just confirmed that the new builds are working properly, Thanks to Reventech for testing. I will be uploading shortly. . .
[G2 Android Development] jeyd02:
Okay just finished restored my device. Thank God I backed up. My phone happens to bootloop also with BlissPop 3.0 ROM. It's get choppy and after lockscreen restart in softboot loop.

---------- Post added at 01:07 AM ---------- Previous post was at 01:05 AM ----------

Oh great!, I could give it a second test :p or if you have it sorted out, then I'll eagerly wait maybe you can pass it before I go sleep :p
[G2 Android Development] RenderBroken:
Yes, glad you backed up.

Uploading proper builds now. These do work without issue. Thanks for testing!
[G2 Android Development] KevTheGuy:
Lol I just installed the one for d800 and was gonna report that everything seems fine, and I checked the default settings in Synapse and they are nice, I'll come back later when you post the proper ones :)
[G2 Android Development] jeyd02:
Thank you very much!!. Hope the kernel settings would stick on reboot :/.
[G2 Android Development] RenderBroken:
All builds are up. R12 is live. Please note that this is ONLY for Android 5.1.

Things to note in R12:

New build flags along with being compiled with my new Self Compiled uber Toolchain.

New Default Settings. Right now I am running with SmartMAX and have tuned the settings abit. I am pretty happy with the results.
[G2 Android Development] RenderBroken:
Didn't know that was an issue. Let me know if that is the case with R12.
[G2 Android Development] LeoPosas:
Hi community, glad to be part of G2 users!

Starting with this device, I flashed Resurrection with this Kernel that seems pretty cool. But, don't know why, I'm stuck in the LG logo, searching everything in this forum, flashed Bumped TWRP, JB Bootloader and 20c Modem. Came from stock 4.4.2 AT&T D800

Please need some hand here :) Really appreciate it.
[G2 Android Development] RenderBroken:
Which resurrection remix version? With what build of mine?

Also that ramdisk I used came from blisspop 5.1 build and should work for other android 5.@ builds but you never know. Currently I am working on a new way to create my flashable. It is a mix of anykernel. This way I don't have to deal with ramdisks anymore.
[G2 Android Development] Lawlrus:
If you're flashing the new builds they're 5.1, and this kernel is for 5.0.X. You would need to be using 3.9 or later.

Sent from my Vs980 running Temasek's ROM v9.4
[G2 Android Development] quangtuyen88:
F320

Sr just flash R12 on F320 with blisspop 5.1 but wifi still don't work :crying:
[G2 Android Development] LeoPosas:
Hi [MENTION=5438598]RenderBroken[/MENTION], thanks for your answer, I flashed this cm-Resurrection_Remix_LP_v5.4.1-20150410-d800 then RenderKernel-LP_d800-bumped-R11. It's normal that stuck in LG logo before Android setup wizard?, because I used to wait for Android Boot Animation after LG Logo.

Thanks for your answer, what do you mean with 3.9? Sorry, newbie yet. :silly:
[G2 Android Development] Lawlrus:
5.4+ does not work with this kernel.

You need to flash 5.3.9 or earlier builds.

Sent from my Vs980 running Temasek's ROM v9.4
[G2 Android Development] LeoPosas:
Thanks mate, copied that. But, Render R12 will work or not?
[G2 Android Development] Lawlrus:
Apparently its supposed too. Guess I missed the post where he dropped it.

I can't rey it myself as 5.1 ROMs have data issues with cdma

Sent from my Vs980 running Temasek's ROM v9.4
[G2 Android Development] LeoPosas:
Oh too bad, Will test if R12 works with 5.1.

Thanks for your time dude, really appreciate it. :good:
[G2 Android Development] jeyd02:
Actually now that I checked it does stick in synp kernel tweaker. Thanks for the great kernel. :p
[G2 Android Development] IOmega666:
If i wanna use some AOSP ROM like Omni for example, that i need JB Bootloader, can't use Render Kernel, right? 'cause it needs KK Bootloader, but, whick AOSP ROMs uses KK Bootloader?
[G2 Android Development] liusi522:
I'm glad to see you are building 5.1 kernel

you known，F320‘s kernel have lots of problems.External Card,deep sleep，wifi can't turn on after lock screen.:crying:I hope you can solve them.:o

Thank you for your R11.It is very good！:o:o:o
[G2 Android Development] jeyd02:
Well Idk if it's me only by I am using BlissPop had use Remix with Kk bootloader and now I have R12 render kernel. Everything running fine and no problem.
[G2 Android Development] liusi522:
yes 320 is too sad

I am also 320.our phone can't good to use aosp.:crying::crying::crying:
[G2 Android Development] bgx:
Hey render! I want use your new settings, fashed your kernel on blisspop and stock settings are now interactive? I think you have switched to smartmax?
[G2 Android Development] de.er:
hi, did you flash R12 on the BlissPop-v3.0-d802-OFFICIAL-20150408-1012 ? Is dt2w working now?
[G2 Android Development] bgx:
I flashed on the last nightly of blisspop. d2tw is working as good as every 5.1 rom. This means it working but screen keep turning on after dt2s.

I think its not a kernel thing.
[G2 Android Development] bolt890:
Change governer to smartmax :) ull have the new default settings.
[G2 Android Development] ckyy:
Is it me or is the min CPU freq stuck at 1.5ghz? D802 R12 on the latest ressurection rom. And is it possible to get Synapse working? It says no UCI support.
[G2 Android Development] bolt890:
Read the op you need to flash Universal Kernel Manager, link is in the op. No such issue here.
[G2 Android Development] LeoPosas:
Dead Screen

Well, high expectations, but...

In the first boot, after a couple of minutes, my screen started flickering very strange, I though that was normal but...

After enter in recovery again, I saw 5 black vertical lines in the right side, so, I think I messed up. :( (After looking the forums, I'm not the first one with this problem)

What do you recommend me guys? I mean, Can I tried again without worsening more? If not, which alternatives do I have?

Thanks for your replies , hoping to do something with this phone. :crying:
[G2 Android Development] IOmega666:
What i meant was Kit Kat AOSP ROMs, missed something hahaha. Omni for example, uses JB Bootloader, Mahdi the same i think, CM11 isn't supported, so, why is there a Kit Kat Kernel BUMPed that it needs a KK Bootloader. I don't wanna use Lollipop AOSP because of VOIP issue.
[G2 Android Development] deathrowz_sri:
[MENTION=5438598]RenderBroken[/MENTION]

Another F320 user who had high hopes on R12. Well im kind of disappointed since some random Korean guy who didnt know GIT or English was able to fix wifi and SD. It should be peanuts for a recognized and respected developer like you to incorporate what he already did on your work and you mentioned you have already found a solution. Anyways we F320 users always feel left out in AOSP world and stock ROM is like **** and slow. Waiting for that someday when developers will show some love to us.
[G2 Android Development] jeyd02:
There is a little fix for viop issues, are you talking about the sound?
[G2 Android Development] RenderBroken:
Dont try to call me out. I took a look at it and seen that it may cause issues for the other users. I could be wrong. I build all on the same tree for all my variants. Could I create a separate branch JUST for F320 users, sure. Will I? No. LP is so close we can taste it, Why should I waste even more of my already precious time on something that will soon be a non issue. I am kinda dissapointed that someone who sounds like they know English better than the Korean guy, couldn't do it his self? You already have a head start on him so it should be nothing for you. But don't veil your insult in false niceties. How long have I been showing you F320x users some love? Why don't we call out CM on why their crap source doesn't support your phone? Maybe we should call out LG for making so many variants so far apart with their built in components?

To everyone else:

I know there have been alot of confusion about the 5.1 builds from roms. They don't really have a stellar naming scheme so I know its confusing. I apologize and wish there was more I can do about that. One thing I am working on is going to make supplying my own ramdisk obsolete. This way it should technically work for 5.0 and 5.1 with the same flashable zip. This should also help lower the mass confusion going on. I am pretty excited about it and have been kinda working on it for a bit now. Hopefully soon I can start testing so I can move on with just building.
[G2 Android Development] RenderBroken:
Not sure, It could be the new borked SELinux not allowing my settings to be properly set. I wouldn't be surprised. lol

Also I don't have my old G2 near by and wont for another 3 weeks so I am deving blind right now.
[G2 Android Development] reemar:
[MENTION=5438598]RenderBroken[/MENTION] i have an issue, after update to 5.1(RR 5.4.1), clean flash and install R12 with it,phone boots.., but, when i get into recovery its shows teamwin blue screen for 5 sec then boot back to system, how can i be able to get into recovery?
[G2 Android Development] RenderBroken:
Not sure, never heard of that before. Maybe you have to re-flash your recovery but nothing in R12 should even touch your recovery. Let me know how this goes for you.
[G2 Android Development] reemar:
i reflash recovery from adb but its still happen, my recovery is [TWRP][2.8.6.1] by [MENTION=5031300]blastagator[/MENTION]..

and i stuck with all of it because cant enter recovery..
[G2 Android Development] RenderBroken:
Man I have no clue, Anyone else have this issue before?I know its not he kernel because my original tester (RevenTech) would have said something. But I would really like to know the fix for this. Did you change anything in the Rom itself? Isn't there a Cm recovery line in Dev Options? Is it enabled? I really don't know and I am grasping at straws here.
[G2 Android Development] deathrowz_sri:
Im no expert on English or GIT either. May be that led to asking such questions like ' cant you continue on what he did coz afterall he worked on what you developed? ' Anyways yes you have given F320x users what we always wanted to have. Please accept my apologies.
[G2 Android Development] RenderBroken:
Sure, apology accepted.

If the new LP kernel doesn't come as soon as I am thinking, I may re-address the issue. But currently, it looked like he took the WiFi source code from the F320 LP drop and just placed it on top of what I currently had. The problem with this is it didn't look to be generic in that it would also work for all the other variants using the same source. Also of times, in out beloved LG code, there are certain areas where certain IFDEF's will set a value depending on the phone variant. Well there were some changes that were not bracketed like this and it looked to me that it could cause issue for the other variants. So that is why I really need all the different LP source to drop so I can cross compare them to see if it will work, what has changed per device and etc.

One more thing to keep in mind is, CM NEVER supported F320x and they are way better devs than I. I looked through the code, I seen some missing code, I tried patching what I could and comparing to my KK source but they are completely different in so many ways.
[G2 Android Development] secret.animal:
I believe the 2.8.6.1 had an issue if you had f2fs on any of your partitions. Already I read that from one of the threads throughout the g2.