yashsingh1/xdaforums huggingface dataset:
[G2 Android Development] bleached45:
I used tasker to flash the back LED when I received a new notification and my screen was off.

I'm sure it isn't the cleanest implementation but it does seem to work.

The files that control the back LED (actually, both LEDs, there are 2 behind the power button, left and right side) do exist.

I'll attach the exported XMLs from tasker... Not sure if you can just import it or not, you will probably have to remove the .txt extension.

And it needs root.
[G2 Android Development] hailang215:
Could you offer the MD5 of those .zip?

I flashed the kernel and endless loop boot,I'm not sure it is broken package cause by blocked internet or compatible of roms.

I used G3 ROM from Cloudy.I think it just suitable to your AOSP kernel.
[G2 Android Development] Matze060906:
Do I understand it right? You flashed this kernel over a g3 rom?
[G2 Android Development] RenderBroken:
That rom would be considered a Stock rom and not AOSP even though they are kinda close to each other. Main difference is I use the same ramdisk for all phone variants but Stock uses a separate one for each. md5's would not hurt though.

TL DR: Not compatible with my kernel
[G2 Android Development] Formhault:
Just woke up. Unplugged phone from USB. Proximity sensor borked.

Flashing back to R23... :(
[G2 Android Development] Matze060906:
Could it be, that this is a problem with your rom? I'm running LS 10/10 with R24 and have no problems with sensors...
[G2 Android Development] Formhault:
Starting to think so. Because... look what's happening again... :eek:
[G2 Android Development] Matze060906:
Never seen this before. Do you have a wakelock detector?
[G2 Android Development] Formhault:
No. But I'm going to flash... I don't know what :eek: . AOKP maybe.
[G2 Android Development] Matze060906:
Have you ever tried liquid smooth?
[G2 Android Development] Formhault:
Been on LS until 10 mins ago... I'm already missing it.
[G2 Android Development] Matze060906:
Oh, I thought you're running Mahdi...
[G2 Android Development] Formhault:
I was gonna. But then I heard it's full of issues so... AOKP for the time being.
[G2 Android Development] Matze060906:
Yeah, I was running on Mahdi before I flashed ls (july build). Since august, Mahdi got more and more issues. I tried aokp too (3 months ago). It was very slow for me and had many lags by scrolling and poor battery life, but everyone have to test for himself...
[G2 Android Development] crazy4tricks:
Hi running AICP 02/11 build.. with R24 no issues so far.. may try this ROM
[G2 Android Development] Formhault:
AOKP must be 4.2 since flashing Render made it stuck at LG logo...

---------- Post added at 10:58 AM ---------- Previous post was at 10:55 AM ----------

Will do asap! Thanks for reminding me about AICP :laugh:

EDIT : flashed AICP. :)
[G2 Android Development] :
Let me know how AICP is. One of the roms I wanted to try, just never had the time. And I do believe AOKP is on 4.2. Maybe sometime I can try building AOKP w/ dr87 4.4.x sources.
[G2 Android Development] Formhault:
It's alright... but it's best to give AICP a shot yourself and see if you like it. I personally prefer the way things are arranged in LS (customization settings & such).
[G2 Android Development] RenderBroken:
Right now, AICP is one of the few that had reverted the commits that introduced the sensor issue. At the moment, I am using LS 10/26 with no issues. But I have the D800. Still I am glad o know its not a problem with my kernel. Thanks guys for assisting others in this thread. I am not really one to gripe about OT because I think it leads to a better community and thread as long as its not crazy OT.
[G2 Android Development] :
I'll definitely give it a whirl when I get a new digitizer and LCD. Broke my touchscreen a couple days ago from dropping it, so I can't use the G2 at the moment. I should be able to get them in a couple weeks. When I do get them, I'll run my PA build (Self-compiled with dr87 4.4 sources, and sensors should be working, thanks [MENTION=5438598]RenderBroken[/MENTION] for linking me to the commits!) and AICP with Render. LS ran really nicely with Render.

Oh, and slightly off topic, but if there are any D800 owners that want to help me test my PA build before I slap it up on a thread, shoot me a PM. LS kernel is baked in, but Render should definitely be flashable.
[G2 Android Development] 1ceb0x:
this is totally unrelated to Render's kernel, but will you build for d802 as well? :)
[G2 Android Development] Formhault:
[MENTION=5438598]RenderBroken[/MENTION] you've been working on some stuff lately... How's that R25 release coming? :silly:
[G2 Android Development] :
Providing I have time, sure. It's just such a pain because I have a really low tier CPU, so building takes me about 5 to 6 hours. D800 build will be done in a couple hours, but I have to head out for a couple hours. Once I get back, I'll start building.
[G2 Android Development] RenderBroken:
Its all good. ;) Never know, may have render included in the future. . . and kinda turn into the Paranoid Saberdroid project. Where it is just a complete custom rom!

Like a champ! I am debating finishing up my F2FS wok and then try it out myself! Not sure though. . . But its going pretty well. Not really alot of new features but cleaning up a few things in Synapse and such. F2FS will be part of this build for sure. As I said before it will be added in a away that is unobtrusive. It will support either ext4 or f2fs depending on how you have your partitions formatted. It will do it automatically!
[G2 Android Development] Formhault:
I'm not really that into F2FS right now. All I am looking forward to is the release of R25 so I can get rid of these once-every-oh-I-dunno-f***-you-I'm-code partial SODs :silly: .

Oh, and... I saw you enabled some audio controls in Synapse. But in-call volume / earpiece is missing :( . Could you add control for that, as well? So we can do it from Synapse, not Faux Sound (which I don't even know if it works or not)... all-in-one, you know :D

Also, hope you haven't forgot about those 300 miliampers :silly: :victory:
[G2 Android Development] RenderBroken:
Yea I understand about the SoDs. I will look into the audio addition. See what I can do. Lastly 300ma has already been added!
[G2 Android Development] Matze060906:
[MENTION=5438598]RenderBroken[/MENTION]: My little report after 1 day of use: r24 runs without issues on stock settings. The battery life is a little bit lower than with blackbird kernel which is built in in 10/10 build of ls. Tomorrow I'll play a little bit with synapse to see if I can get more battery life. Thanks for the great kernel and your efforts to build it without issues...
[G2 Android Development] NEROVINCIO:
after flash render kernel on AICP but I have call problem,how I can fix it?
[G2 Android Development] Formhault:
What exactly is the problem?! :confused:

---------- Post added at 10:35 PM ---------- Previous post was at 10:32 PM ----------

:victory:
[G2 Android Development] Choristav:
R24 works amazing so far with the new LS build and sensors are working on d802.

Might as well add I'm undervolting ("heavily") and even with the idle gpu on 27MHz I've not had a single SOD since the release. I also use the c1 setting.
[G2 Android Development] MrDarkKV:
Hmm, does anyone know how Optimax handles workload and CPU scaling compared to the other governors? I can't seem to find anything online about it.

Thanks.
[G2 Android Development] RenderBroken:
What kind of numbers you get with both? Just curious how much worse it was for you. Thanks!
[G2 Android Development] bleached45:
I am also looking forward to this. I'd love to just use synapse for everything. But the earpiece/microphone settings are missing and it says that it can't edit the poweramp values. Which is sad. Haha. The poweramp does seem to work from fauxsound (though you do sometimes have to move the slider with audio running after a reboot). Strange, the driver doesn't love our phones it seems.
[G2 Android Development] Matze060906:
With blackbird I get 6 hours sot and with r24 5,5 hours. It's not much. With r21 I got 4,5 - 5 hours sot.

---------- Post added at 06:27 AM ---------- Previous post was at 06:00 AM ----------

Which new build do you mean?
[G2 Android Development] Formhault:
I'm guessing he was talking about the milestone build of LS, which is being built for all G2 variants as we speak... He spilled the beans :)

Reventech will be releasing all builds within the next 2~3 hours. Hang on.
[G2 Android Development] REV3NT3CH:
ugh really wtf....now i cant trust ppl when i say i wanted it to be a SUPRISE!!!
[G2 Android Development] Vollspacken:
Speaking of D802 and still r23 on mahdi 27/10 with fourth core turned off and (optimized) optimax governor i reached 5h SOT in wifi and airplane mode (bad cellular signal in house) on two days using and had 46% left with browsing, chatting and listening to some music. Doesn't affect the performance and all and got rid of these lags i had with bacon governor and got even better lifetimes. There's much potential in this kernel and i think there's no big difference to stock anymore. So just play around carefully with some settings and you will easily get better battery lifetimes. ;)
[G2 Android Development] Matze060906:
Thanks for chiming in. I'll be very carefully, because synapse isn't easy to handle like trickster mod, that I used for a long time. It have very much options. I think to much for me...
[G2 Android Development] nfin1te:
Since F2FS is obviously getting more popular, is there some guide/general advice for converting the file systems?

Not that I intend to do it in the near future, just so I can read up and get some info on that topic.
[G2 Android Development] NEROVINCIO:
when I call someone I hear him but he did not hear me
[G2 Android Development] ckyy:
That would be great.
[G2 Android Development] Ace42:
(Correct if wrong)

1. Compatible recovery installed

2. Format partitions (but remem to backup)

3. Change partitions in TWRP to F2FS ( you can return to EXT4 again)

4. Adb push ROM/Kernel.zip to /sdcard (along with gapps, superSU)

5. Mount the phone to your PC (skip 4 if mount works, it never worked for me so I use ADB Shell)

6. Reboot

Sent From Capsule Corp.
[G2 Android Development] thackoon:
Looks like I spoke too soon. Wireless charging does not work. The phone charges, but it doesn't recognize when it's been taken off the charger. Requires reboot to fix. Anyone with a VS980 have wireless charging working?
[G2 Android Development] RenderBroken:
You can still use trickster. I just love Synapse because I am able to offer a free alternative to Faux Sound and Trickster (Paid app) and have the ability to add in what I want when I want it without having to wait. Thanks for giving me more info on the battery usage. What type of setup and was it the same on both kernels? Last question, I promise! ;)

Not a kernel issue, I think more would have the same problem is so. Sorry I cannot help more. Have you tried another Rom?

Is this what happens with other Kernels? Just curious. I may dig into this for you. Is the VS980 the only one with wireless charging?
[G2 Android Development] thackoon:
Yes, this also happened with dr87's kernel for Mahdi ROM. I did try Dorimanx AOSP kernel a few months ago, and that had a working implementation of wireless charging. But I had other issues with Dorimanx, so I had to stop using that kernel.

And yes, VS980 is the only variant with wireless charging.
[G2 Android Development] bleached45:
And this whole time I thought my D800 had wireless charging.

Luckily I never use it. Still makes me sad. Haha.

Maybe [MENTION=5438598]RenderBroken[/MENTION] can enable it in the kernel. :p

(Just kidding, obviously out of your hands).
[G2 Android Development] NEROVINCIO:
is a kernel issue cause with dori kernel for aosp i have not problem
[G2 Android Development] RenderBroken:
Then I am going to need more info. What phone model? Can you provide logs (KMSG and Logcat please)? What build of AICP and can you provide me a link to its OP? A good number of people also use AICP with no issue such as this. Still, provide me the correct info and I can hopefully work out the problem for you.
[G2 Android Development] NEROVINCIO:
Thanks,but before I want retry to flash your kernel doing wipe cache and dalvik before flash and after
[G2 Android Development] RenderBroken:
That should not matter in my opinion. Wiping caches is not as big of a deal as it used to be. But if it helps, let me know. I am always curious.
[G2 Android Development] Matze060906:
[MENTION=5438598]RenderBroken[/MENTION]: I used you kernel with stock settings (didn't open trickster) and blackbird with veno/flops/optimax and read ahead 2048...
[G2 Android Development] RenderBroken:
Thanks for sharing.
[G2 Android Development] NEO2598:
Just flashed on latest Mahdi.

Time to set it up:)
[G2 Android Development] TDSJR:
[MENTION=5438598]RenderBroken[/MENTION]

I've always set the multicore power saver to "aggressive", and I'm beginning to think that there may be a conflict with the hotplug, as far as performance and by extension battery life.

By default, its set to "disabled".

Would you please take a minute to give your opinion?

Thanks.
[G2 Android Development] RenderBroken:
I dont use it myself after reading that Mainline Linux Kernel Devs saying that its broken in its current form. That it may cause other unseen issues. So for a long time I have had mine disabled and only till recently have I started playing with it again. Still I dont notice and difference. What type of conflicts are you seeing? Would be good to note. Thanks!
[G2 Android Development] NEO2598:
I noticed that bacon is laggy and also the battery was bad while using it. I was like:"Serious??? ".

Changed to optimax and both issues are gone now.

Besides that everything is solid. Thanks Render. You're the man.
[G2 Android Development] TDSJR:
The conflicts are more theoretical than practical. My logic, which may be flawed, is that by compressing processes into the fewest cores (by means of the power saver) and then putting caps on those fewer cores (by means of hotplugging) the result would be a few cores fluctuating wildly, resulting in diminished performance and worse battery life. Thoughts?

Edit: MY logic probably IS flawed. ?
[G2 Android Development] jjlyons:
My wireless charging has worked with Render's kernel on a couple roms on my VS980. Currently running the PA built with dr87's sources for the VS980 with no problems.
[G2 Android Development] thackoon:
Have you ever tried Mahdi rom? I thought the problem was the kernel, not the rom, since wireless charging on dorimanx kernel worked for me with Mahdi rom.
[G2 Android Development] RenderBroken:
Thanks! Yea for some reason it's all over the place with yall users. I may just go back to interactive or tune ondemand/ optimax.

You are pretty close to how it works. But it doesn't actually stop and core Fluctuating. That still occurs regardless. Also in my own tests, it seemed to be pretty efficient but the main issue how it kinda forces the situation. Sometimes it's not conducive to stable kernel work. The biggest issue was the unforeseen problems that could occur.

Interesting. Thanks for sharing!
[G2 Android Development] jjlyons:
I haven't been on Mahdi since the early days of render kernel. I used to use dorimanx with vanir and wireless charging worked. I've also used render kernel with LS and AICP and wireless charging worked there too.
[G2 Android Development] the-erazer:
This kernel is awesome... I got great bettery life in aicp 02/11 nightly d802. Everything is working. Proximity sensor is doing his job. The only thing i habe noticed is quiet hours stops working after flashing the kernel.

Thanks for the good work...
[G2 Android Development] Formhault:
Wireless charging...? :eek:

EDIT : Oh right, the Verizon variant has it, while all the other variants are too weak to have wireless charging.
[G2 Android Development] RenderBroken:
I am working on bringing in some cool stuff. I am looking at adding the possibility to set Governor, Min freq and max freq PER core. This may be interesting. For example you could set an aggressive governor on Core0 and some more relaxed one on the rest. Still have to see how this is going to work but it is possible and the ground work has already been done. Now just need to give you the tools to manipulate these options via Synapse. Also I will repeat what I have said before. You can still use Trickster if that is what you are familiar with. But most here on XDA don't do what we do to keep it simple. We want better options so with Synapse I am working on giving them to you.

Also let me take time to thank [MENTION=5658634]apb_axel[/MENTION] He has kindly allowed me to use his work, Universal Kernel Manager, as an amazing base for my own work! Thank you for all you do!
[G2 Android Development] RenderBroken:
When you were getting the SoD's were you undervolting? I was getting them too and believe it was because I was undervolting. Now that I have stopped I have not had any issues. I am just curious about your case. Thanks bud!
[G2 Android Development] NEO2598:
I had SoD's with - 50mV on r23 and optimax, but bacon was good.

Now in r24, optimax and - 25 mv it is all good.
[G2 Android Development] RenderBroken:
Thanks for chiming in!
[G2 Android Development] MBurns2:
this kernel is amazing, thanks [MENTION=5438598]RenderBroken[/MENTION]. I really like synapse, for me is the best for kernel settings.

Two questions:

- i don't like bacon governor, which one is the best for battery between optimax-ondemand-interactive ?

-cpu and gpu voltage are like stock right ? (i don't want to uv-ov-uc-oc)

Thanks a lot !!!
[G2 Android Development] RenderBroken:
Thanks! I don't k of which would be best. I am revamping interactive for r25 and would need to spend time will all of them to tell you. Yes all voltages are stock out of the box.
[G2 Android Development] RenderBroken:
Thanks!!
[G2 Android Development] TDSJR:
I can send one, if you haven't gotten by now.

Edit: Sent
[G2 Android Development] RenderBroken:
Thanks boss. I have 3 work emails so it's something I have been wanting to try for awhile now.
[G2 Android Development] MBurns2:
guys what about lmk ? did you leave it stock ?

I like to have tons of open apps but sometimes my phone become a little bit laggy on some animation (es. recent panel..). Ty
[G2 Android Development] RenderBroken:
No, it is not stock. It has been reworked and Auto OOM has been enabled though I am going to run a test build with it off. Are you saying it becomes laggy with my kernel? Also no matter what kernel I have used, recents was kinda laggy for me. Slim and stock recents panel both. Thanks for the report though.

Really, aside from a few select things, nothing else in this kernel is stock.
[G2 Android Development] Formhault:
Speaking of Inbox... I know it's a tool that's set to "make our schedules perform best and never miss anything EVER F***ING AGAIN" (yeah right) but I can't wrap my head around it. I mean if Inbox will do for my e-mails what it claims it does... hell, Google will have to launch OrganiseYourCourses-tube and HouseCleaner Plus pretty soon.

Yeah. Not gonna happen.

---------- Post added at 12:04 AM ---------- Previous post was at 12:01 AM ----------

Nope, I haven't played with undervolt yet. And by the way, thanks for reminding me - I'll have to start experimenting. Hope I can reach -50 mV... I mean I want my phone to go below 0 Celsius so I can cool down the class room during courses. F*** University leadership. Who needs better ventilated rooms? Human beigns? Definetly not!

(2014 is the rant year :victory: )

---------- Post added at 12:08 AM ---------- Previous post was at 12:04 AM ----------

Speaking of SODs... I had one today. And you know what? I'm on the milestone LiquidSmooth build, with the included kernel (which is Reven's latest).

Why I am mentioning is... it was kind of weird. Phone was charging, I was transferring some stuff across via Wi-Fi (ES File Explorer FTP). I try to wake the phone, nothing. I disconnect the phone and the green LED turns off, phone vibrates and a sound plays (just like I set it up, so the ROM was good). I reconnect the phone, it vibrates and the LED turns on. About 30 seconds and 10 attempts to turn on the screen later... it woke up.

Same thing happened with 10/27 build of LS and R24. I'm guessing it's the same kind of SOD... but I never gave my phone that much time to respond, I almost always ended up force rebooting it. So... yeah, not sure what that's about.

I mean of course, unless both you and Reven set up the same 27 MHz implementation for the GPU... if you know what I mean. Regardless, this kind of SOD is a rare occurance - the too-rare-to-even-bother-working-on-fixing-especially-with-L-just-around-the-corner kind, you know :silly: .
[G2 Android Development] MBurns2:
thanks for the clarification, you re a good dev!

someone can give me stock lmk values? i want to try ;)
[G2 Android Development] RenderBroken:
No he had not added the same changes and I am now doubting that the GPu changes are the cause for the SoDs. I am also on the latest LS and am having some really weird issues that I didn't have on an older LS build with the same test build I am using. So at this point I am not sure if its kernel or rom related. I need to scour the Rom thread to see if others have the same problem. Thanks for your help brother.

Make sure to disable Auto OOM first or the settings wont stick. Here is what I am going to use:

echo 1536,2048,4096,16384,28672,32768 > /sys/module/lowmemorykiller/parameters/minfree
[G2 Android Development] 1ceb0x:
Aren't these a bit too low? Seems that it is not that aggressive. I wonder how they will work.

Personally i prefer: 2560, 4096, 8192, 16384, 24576, 32768
[G2 Android Development] RenderBroken:
I think you are right. I found that a couple devs on the Hammerhead were using them. Thought I might try but I tend to agree with you on this one.
[G2 Android Development] RenderBroken:
wtf duplicate message
[G2 Android Development] 93fuelslut:
Can I flash this kernel? The OP said don't flash if your on CM but I'm running Mahdi and I think someone said Mahdi is CM based.

sent from your moms phone
[G2 Android Development] Ace42:
Mahdi is still AOSP based unless dr87 changed that recently...There are commits from CM, but AOSP kernels work on Mahdi (including the Dorimax port by Bart). It also uses KK sources unlike Omni and Mokee, so it should be compatible.

Sent From Capsule Corp.
[G2 Android Development] 1ceb0x:
A kernel cannot manipulate the applications unless it corrupted the /data partition which i doubt because otherwise all your apps will be gone.
[G2 Android Development] r_dub:
I have this same issue every time I flash this kernel over Mahdi. Happens every time without fail after install all paid apps are gone on reboot.
[G2 Android Development] 1ceb0x:
No issues here. How did you installed the kernel?

did you installed mahdi + patch, then reboot, setup, then install render on top?

if so, that's your issue. you need to install the kernel on top of the ROM + patch without rebooting between them.
[G2 Android Development] r_dub:
Wrong on both fronts happens both ways.
[G2 Android Development] bleached45:
Just to chime in, I don't think this kernel in particular has anything to do with paid apps uninstalling. I've had that happen randomly while installing other kernels before on my D800. Then again, it was usually between mahdi/carbon stock and furnace (which this is based on).

So maybe it is something with furnace. They work after a reinstall.
[G2 Android Development] phoenix_rizzen:
Just curious, but had anyone tested installing the Mahdi ROM, then this kernel, without installing the Mahdi patch?

Typos courtesy of my LG G2 (D803) running Mahdi-ROM.
[G2 Android Development] 1ceb0x:
the patch installs device specific files in order for your ROM to boot (besides the kernel) so if you only install mahdi + render you will end up in a bootloop.