yashsingh1/xdaforums huggingface dataset:
[G2 Android Development] Vollspacken:
On mahdi 10/27 this r23 kernel is beast.

The first 10% are missing because of reboot, but i can say that i had one hour sot and i even switched from dalvik to art in those 10%. The rest of the day i browsed the worldwidewebz, installed some apps, chatted with friends, watched some 720p youtube videos and listened to music for nearly 4h while studying. Was at home all day, so only wifi usage while cellular data was disabled. Auto brightness with relatively high brightness set up.

All together if i would sum up this usage and just transform it into SOT only it might be possible to achieve 9h SOT and i never achieved that on a perfectly set up stock rom. Compared to Liquidsmooth it's one or two level above.

Comments to the kernel itself:

With my settings (lowering frequencies of hotplug, touchboost and some other values, main values like min and max frequencies were untouched) the phone stays very cool, it nearly didn't heat up above 43-45 degrees in normal usage.

So thank you for your awesome kernel and keep up the good work. I will finally stay with this combination until a good aosp-android 5 version is coming out.

Keep up the good work!
[G2 Android Development] Formhault:
[MENTION=5558742]Vollspacken[/MENTION] Mahdi is fine, right? I mean no FCs, no reboots etc...?
[G2 Android Development] Vollspacken:
[MENTION=4129455]Formhault[/MENTION] Yes, it's fine so far. Only a bit stuttering compared to liquidsmooth, but that's not that much.
[G2 Android Development] RenderBroken:
Building now for all variants.
[G2 Android Development] RenderBroken:
So many new things of note in R24:

Changelog

* Compiled using a Custom Builts 4.9.3 toolchain for msm8974

* Reworked Synapse to add features, remove some, and make the GUI make a little more sense (to me at least)

* Dynamic FSync - Since the device has been rock solid I thought we can have this back again!

* Massive OOM and LMK Overhaul: Now using Auto OOM. This essentially manages the usual LMK Minfree settings automatically and will adjust accordingly to your needs. I am trying this out to see how much better it is or if it causes issues. Should result in a smoother experience anyways.

* Fast Charge 2.3: Many cool additions. Details: https://github.com/RenderBroken/msm8974_G2_render_kernel/commits/cfd9f955637aa141844605710b568082c9588320/arch/arm/mach-msm/fastchg.c

* Simple GPU from Faux - you can essentailly make your GPU smple faster thus Ramp up faster or slower depending on how you tune it. Just gives more control to your GPU

* GPU OC to 650 (Though I have only hit 533 in tests) - I may have to work on this further but there are more steps in between as well. Not just OC Freqs. Now your GPU Governors are good for something! Yea!

* lge_touch_core: Expose jitter/accuracy filters

* Sweep2Dim - Cool feature that essentailly ties into sweep2wake and allows you to either brighten or dim the screen by swiping the nav bar. Thanks [MENTION=4316709]savoca[/MENTION] !
[G2 Android Development] :
Will you be building the F2FS build tonight as well? :)
[G2 Android Development] RenderBroken:
No, I plan on merging those in tomorrow. Afterwards I will be building.
[G2 Android Development] Choristav:
Maybe you ought to add the sub 200MHz step (like 100MHz)?
[G2 Android Development] RenderBroken:
Already done
[G2 Android Development] ckyy:
Am i the only one that finds bacon extremely laggy and slow? It feels like it's 2011 all over again, using my Sony Ericsson xperia arc lol. Every other governor seems fine.
[G2 Android Development] 1ceb0x:
same here... same on blackbird..
[G2 Android Development] allan1229:
Where's the option for dynamic fsync? Am I missing it?
[G2 Android Development] allan1229:
I guess I'm blind. :) Its not there
[G2 Android Development] jonatutu:
I am using bacon with min set to 192mhz and max at 1958mhz it feels alright. But what I want to ask is the advantage of Bacon and Optimax.

I tried googling these 2 cpu governor nothing came up like the rest of the governor which has tons of detailed explanation.
[G2 Android Development] Choristav:
What do people think of the alucard governor? Why is it not included in this kernel? I heard it was an improved version of ondemand. I personally use optimax now, but once again, based on heresay.
[G2 Android Development] TDSJR:
I AM NOT fan of Bacon either, in both Render r23 or Blackbird. Maybe it needs to spend a little more time at the high end?

I AM a fan of Alucard. For an ondemand (?) derivative, it is/was extremely smooth & battery friendly. Coincidentally, I just asked RenderBroken about it yesterday.
[G2 Android Development] Formhault:
I have noticed scrolling is a bit stuttery, but if that is what it takes for the battery to last me 7 hours with the screen on... I'm down with that! :)
[G2 Android Development] RenderBroken:
Lol I don't have that issue while I am using it. I am switch back to interactive as default or even ondemand

Weird. What phone model? Maybe it was left out in the defconfig somehow.
[G2 Android Development] Ace42:
Render, do you know why developers use MSM-adreno-tz, but never include MSM-dcvs for the CPU? They are both from QC, as well as ROW so I don't see why dcvs is never used.

Sent From Capsule Corp.
[G2 Android Development] rmsinaga:
Has R24 been released? :confused:
[G2 Android Development] enr88:
Yes! Go to OP then click to download page and u will find r24

Inviato dal mio LG-D802 con Tapatalk
[G2 Android Development] Formhault:
Screw the title. I've been tracking it all day long :eek:...

-----

Alright, so I went to the OP to download R24 and flashed it. :victory:

Now... [MENTION=5438598]RenderBroken[/MENTION] :D
[G2 Android Development] RenderBroken:
I am looking at bringing the governor.

Not sure, I had never used it before on previous devices I owned. I will check it out. Thanks for bringing to my attention. It looks like it could be useful!
[G2 Android Development] Formhault:
935 mV for ~1.8 GHz and only 1025 mV for 2.3 freaking gigahertz? What the hell? Is the Snapdragon 800 really that good, or what? I mean on the Snapdragon 600, 1.9 GHz would require at least 1150 mV (IIRC). Jesus!

I think it's been a long time since I last meddled with CPU voltage. Never even looked closely at the voltages on the G2 since I got it... so yeah, I'm all like "woah, amazing!".
[G2 Android Development] RenderBroken:
Thanks for the suggestions though it makes sense to me. When you are changing the different "Charging Rates" you are modifying the watts/volts you are taking in. Watts / Volts = Amps The charge gives a constant current. Lets say just say you have a charger that is 5v 1a. To get less than 1a the devices can only take less voltage to do so. Voltage is the only thing the device can control. There is no way it can still take 5v and only 300ma for example. Voltage and amperage go hand in hand and scale precisely with each other.

Also I agree with changing the title part. We are beyond regular "USB Fast Charge" since we can now undercharge as well. I may play with the description as well to allay fears of messing with something you shouldn't. Thanks for the help.
[G2 Android Development] jeff5347:
Render, on syslog do u need all 4 logs (kernel, last kernel, ksm and modem) or just certain ones. I've never taken a log and on r2 I was getting reboots...( not sure if the kernel or ROM as it was Mahdi's latest, 7/8 ROM, which had bugs) so I just want to make sure if I give any I don't bog u down with unneeded info. Thanks
[G2 Android Development] RenderBroken:
wierd. I haven't had any issue but I am on 7/6 Mahdi build. It must be the Rom causing it. Unfortunately the last_kmsg is not showing any cause. Most times when you get a random reboot (Caused by the kernel) you will get a reboot reason at the bottom. Definitely keep my posted. Anyone else try the Test build? Have you had any issues like this?
[G2 Android Development] simon_lefisch:
The 7/8 build was taken down shortly after its release due to all the bugs it had. Latest build is 7/9. Reboots were most likely due to the ROM.
[G2 Android Development] Raagh:
Yeah i tried it but had 2 reboots while taking a shower so i flashed back r2. Sorry.
[G2 Android Development] jeff5347:
Well I guess I jinxed myself. Running the mahdi 7/9 build all day w no problems. I flashed the hotplug test and within 5 minutes a reboot. Came back took a log and then another reboot. Unfortunately I had to get on the stock kernel but I have a log from each reboot. Hope this helps Render, definitely want to use your rom
[G2 Android Development] bgx:
I'm also on last mahdi build and with test build I get also reboots 30sec after system start. Had a D802.
[G2 Android Development] jeff5347:
^^^^Not so sure on this now. Mahdi had no hiccups today til I flashed the hotplug test. Render please don't take any of my words as insults. I am hoping and praying with the logs u get and more tweaks this kernel will be THEE kernel to run
[G2 Android Development] RenderBroken:
K Thanks guys. not sure what the problem is but I am not on the newest Mahdi build. I am on 7/6 with no reboots so I am confused what the problem may be. I will take a look at the logs to see if anything shows.
[G2 Android Development] RenderBroken:
Unfortunately the last_kmsg shows nothing. Not your fault though. Thanks for providing them! I am downloading the newest Mahdi now to test. See if flashing the newer rom causes issues for myself.
[G2 Android Development] jeff5347:
Hmm weird. Granted my first logs ever.. But all boxes were checked...sorry
[G2 Android Development] crnkoj:
ive been running your other stable kernel with 7/9 mahdi for an hour now and there were no random reboots. ill let this for a day or so and than try an older mahdi with the test kernel.
[G2 Android Development] PWn3R:
I tried your new beta kernel on the 7/9 Mahdi this morning -- I had 7 random reboots in less than 20 minutes (somewhere between 15 and 20 minutes). I use my phone for work, so I had to back out the kernel update.
[G2 Android Development] RenderBroken:
Interesting . . . I dont believe its the Hotplug changes I had made. There are other kernel changes that have been made so I will look into those. I havnet had time to try Mahdi 7/9 yet so I cant test it yet. Thanks guys for your help!
[G2 Android Development] insomniakAD:
Just had another random reboot on Mahdi 6/28 w/ my D800. I noticed that once the phone started up again, I had gotten a text message so that may have triggered something. Here's the last_ksm log I pulled with Syslog.
[G2 Android Development] Raagh:
Hey [MENTION=5438598]RenderBroken[/MENTION] wouldnt be a good idea to rebase your kernel on simple kernel rather than furnace?

Dont get me wrong i was a furnace daily user since igot the phone but Latest furnace does not support mahdi as savoca have been busy for a while. But with simple kernel clearly ll be a fully compatible base.

Just an idea to solve the reboots
[G2 Android Development] RenderBroken:
No thanks. I have done too much work on my current base to then redo it. Also I feel my kernel is more compatible with more roms. I have a feeling that it would do the same if I rebased with Simple Kernel. Just need to pinpoint the problem commit and remove it or make further changes. Not too worried as R2 is pretty stable. The Test build has some major conflict with the newest build of Mahdi. So keeping that in mind, it may help me find the issue.
[G2 Android Development] Raagh:
Hope you find it men. Im still having reboots with r2. Next reboot i ll give you another log maybe you see sth :).

Simple love the kernel too much to leave it ahaha
[G2 Android Development] RenderBroken:
Yea, I know they are still present. Glad to hear!
[G2 Android Development] 1ceb0x:
Funny, I had no reboots on mahdi 7/7 with R2... and I installed them on 7 July.
[G2 Android Development] Dene_Bluesman:
Here is a log , D803 test kernel on mahdi 7/9, strange thing also after i flashed the kernel it uninstalled all my paid apps

https://www.dropbox.com/s/j9vw4ptt3iorme6/2014-07-09_19.02.zip
[G2 Android Development] RenderBroken:
Yea it shocked me too and I even undervolt by 50. This SoC is pretty top end and there are even more things to be unlocked!
[G2 Android Development] Formhault:
No wonder the phone doesn't get nearly as hot as the Galaxy S4. Should have checked the voltages the day I got it... to make sure lol.

---------- Post added at 05:10 PM ---------- Previous post was at 05:07 PM ----------

Right. Current = voltage x resistance. I know that much :D. So f*** that teacher who flipped my amperage world upside down by saying "it obviously controls some sort of scalable resistor". I'll be sending you a PM shortly.

Oh and I edited the post. Check it out again, it's much more... eye-candy :silly:.
[G2 Android Development] Tribes11:
I'm sorry I didn't made myself very clear in the last post, I'm Brazilian and I may have lost myself in that post I wrote.

First of all i didn't fixed Netflix issue at all.

Second of all I flashed render kernel to fix a REBOOT I was having with baked kernel while running Antutu Benchmark.

I hope this now finally clarifies everything.

Netflix issue as far as I know haven't been fixed yet but the OP is looking foward on this issue..

Sorry for all this misinterpretation I caused.
[G2 Android Development] beandroid9:
After updating to R24 back function is not working in app drawer. pressing menu everytime.. Is it working for everyone?
[G2 Android Development] Formhault:
All buttons are working fine here... :confused:

Besides, the kernel shouldn't affect them at all, as that's the ROM's job as far as I know...
[G2 Android Development] Matze060906:
Sounds like an old issue from Mahdi. Do you run this rom?
[G2 Android Development] allan1229:
D801 on Slimkat 8.4
[G2 Android Development] Formhault:
[MENTION=5438598]RenderBroken[/MENTION]

The proximity sensor seems to be broken in R24. Rebooting didn't help. Flashed back to R23 for the time being. D802

Also, here's a thing... I am on LiquidSmooth (the 10/27 build, you know... the elusive build :silly: ). Up until a few hours ago, I was running your kernel (R23). This is what's happening like at least once a day : when I try to wake the phone (DT2W or power button), the screen just won't come on. Sounds come in, the LED is blinking, but it takes the screen like 5~10 seconds to come on. As I said, happens once a day (some times twice a day). Pretty rare.

Today, with R24... the same thing happened, just that this time the screen didn't come on 30 seconds after trying! I got a message and the LED started blinking (didn't stop blinking). When I put the phone to charge, the LED didn't change its behavior, so something got stock inside. Not sure if it's the ROM or kernel. Looked like a partial SOD, I guess. Couldn't take any log...

Just wanted to bring it into your attention, maybe you know something and this strenghtens your belief or I dunno :silly:
[G2 Android Development] tdawgg777:
I believe the proximity sensor issue may be rom related. I know slimkat build 8.10 has issues with it and rotation, due to some changes merged in cm11... other roms based of cm are also having same issues. but I have not tried r24 to be sure, I will flash soon and report
[G2 Android Development] Choristav:
As I'm new to the kernel I wasn't aware there was a misc tab, and it doesn't appear at all for me. I'm using a d806 (which is a d802 with another modem) and r23.

The misc settings appear on r24 though.

Yes, it's pretty good. I also like undervolting myself. I tried to fit all the frequencies on the screen.
[G2 Android Development] Formhault:
That's exactly why reverting to R23 fixes it... :rolleyes:
[G2 Android Development] tdawgg777:
Yeah... was hoping was just rom related. I just flashed r24 on slimkat 8.8 where I had no issues using r23, and proximity is not working. Heading back to r23 for now

Back on r23, all is good with proximity sensor... I should probably mention my device, VS980.
[G2 Android Development] RenderBroken:
Thats bunk. Don't know what would even touch the proximity sensor files. . . But If the proximity sensor is broken then shouldn't the phone not go blank when you are talking on it?
[G2 Android Development] allan1229:
Proximity sensor is working on Slimkat 8.4 which is 4.4 base
[G2 Android Development] RenderBroken:
Found issue and fixed. Thanks for reporting back!
[G2 Android Development] tdawgg777:
When I make a call running r24 the screen doesn't turn off when against my ear, r23 no problems. Is there a setting in synapse to control sensor? I honestly didn't play around much on r24 I tested the proximity sensor and then flashed right back to r23.
[G2 Android Development] RenderBroken:
Its working like a champ for me. I am using the D800. What model do you use? I looked through the commits and did not set anything that would bork the proximity sensor.
[G2 Android Development] tdawgg777:
I have the vs980. And running slimkat 8.8, kk base. And its fine... on r23. Anyone else having issues with proximity sensor using the vs980? Perhaps device specific issue? When I have some free time I will try a complete clean flash and see.
[G2 Android Development] ThatKidDrew:
In trickster go to specific and then screen wake control (if the kernel supports that) and change it to 2 and see if that helps

Liquefied VS980 4.4.4
[G2 Android Development] HueyT:
R24 all good with VS98026A using GUMMY 9/22/14 version. Knock ON, Netflix, Pandora, Google Play, Google Music all work great. Fast charge works too. Breathed new life to old but stable rom. Great job, Render :good:
[G2 Android Development] RenderBroken:
The issue appears to be R24 for some users but I dont see why it works for me and not for a few others. Also note I am on build 10/10 of LS.
[G2 Android Development] Formhault:
I have never seen triple digit milivoltage for the highest CPU frequency since... well, today! Jesus. <1 V for >2 GHz.

[MENTION=5438598]RenderBroken[/MENTION] How's that 8-core 4 GHz patch enabler going? :)

---------- Post added at 10:03 PM ---------- Previous post was at 10:03 PM ----------

Proximity sensor off / disconnected / broken = screen doesn't turn off when covering it during a phone call.

---------- Post added at 10:04 PM ---------- Previous post was at 10:03 PM ----------

Looks like D802 is a complete clusterf***. Issues on LS... and now this proximity sensor thing... only in the D802 world lol... :(
[G2 Android Development] ebreo:
can you add compatibility with cm roms?
[G2 Android Development] allan1229:
Try raising minimum CPUs to 2 in the hotplug tab

LG D801
[G2 Android Development] hovanhuang:
Have some problems that the screen won't light up, no matter double tap or power button. But the phone is not dead. If i call myself, the phone will ring and the screen will light up. Then back to normal. Any ideas? 10/27 mahdi. Both r23and 24 have some issues.
[G2 Android Development] blacklight1025:
I've never ever had any problems with double tap to wake in the year I've had this phone, but it randomly stopped working and I realized that there's a small horizontal "strip" on my screen that doesn't respond to touch. Looks like nothings wrong till you try to draw a straight line. Maybe they're related somehow. I know this has nothing to really do with the kernel, but I thought it might be worth noting.
[G2 Android Development] ckyy:
R24 paired with unofficial CM seems pretty solid so far. I love the screen off max CPU clock speed setting. I have a question about the C States. Do i have to pick only one or can i use all of them at the same time?
[G2 Android Development] RenderBroken:
I'm telling you nothing changed in my source to only effect D802 users. You all use the same source and the same ramdisk as the other models. I am going to say that it's not a kernel issue or at least it's not a problem with R24. Maybe its the ROM and kernel combo. I don't know but it doesn't make any sense otherwise. Also for my kernel if it effects you, it would effect everyone.
[G2 Android Development] Formhault:
[MENTION=5438598]RenderBroken[/MENTION] for some reason when I press "QUOTE" the "New reply" thing comes on, with no quote inserted. So... mentions time.

I didn't mean to say you deliberately made the D802 build so that it borks the proximity sensor... I just said that R24 with 10/27 LS on D802 = proximity sensor borked and, naturally, since this doesn't happen with R23, it automatically makes me think it's an issue with R24, you know... :(

Oh well, looks like I'm staying on R23. :eek:
[G2 Android Development] :
R24, D802, 10 hours uptime, no issues. Too early to comment seriously on battery but seems good so far.
[G2 Android Development] phoenix_rizzen:
If you go back one version of LS, does it work correctly with R24? Oct 27 is right on the cusp of when things went to pot for D802 uses of LS (due to upstream commits pulled in from CM).
[G2 Android Development] luv2increase:
Are you going to make an OC version of r24?
[G2 Android Development] MrDarkKV:
Hey dude!

Would it be possible to downclock the GPU any further than 100mhz on idle?

R24 running fantastically on d802 + Mahdi final- can't wait on F2FS support!

Thanks.
[G2 Android Development] RenderBroken:
I think I might. Just because I fixed the MISC Tab in Synapse.

I thought about it but i think it would just cause more stutter than do any good. Before the lowest was 200MHz so I think 100MHz is a good starting point. Also how is the proximity sensor working for you? Does it turn off the screen when in a phone call? Once I am certain things are at a good place and not borked (somehow?!) then I will start work on F2FS. I already have the block of commits needed, I just need to merge them in.
[G2 Android Development] MrDarkKV:
Hmm, didn't notice that.. Yes, the proximity sensor does seem broken in call (screen stays on).

Here's a logcat if it helps, thanks!

View attachment logcat-2014-11-07.00.40.54.txt
[G2 Android Development] RenderBroken:
Are you changing ANY of the default settings in Synapse? Thanks!
[G2 Android Development] RenderBroken:
The default settings work best for all phones and are most stable. Retention can be enabled for more battery BUT it may cause your phone to have random reboots. My phone never seemed to have any issues but yours may be different. Still you can try it out.
[G2 Android Development] RenderBroken:
Can you try flashing R23 to see if that fixes the issue? Thanks! Just wanted to get more data on the problem.
[G2 Android Development] hovanhuang:
I think change to optimax. And set some different cpu speeds? Should i just try default with only optimax?
[G2 Android Development] RenderBroken:
Maybe optimax doesnt like msm_sleeper. OR something along those lines. Maybe bump that up some. Somewhere around 1.5GHz should be plenty. What cpu speeds?
[G2 Android Development] bleached45:
[MENTION=5438598]RenderBroken[/MENTION]

Just wanted to add in that proximity sensor works for me. I tested it with an app called Elixir 2.

https://play.google.com/store/apps/details?id=com.bartat.android.elixir

R24, AICP 11/5 nightly, D800
[G2 Android Development] RenderBroken:
Just wow . . . this is a great tool. Thanks for sharing!
[G2 Android Development] 1ceb0x:
d802 here, LS 27 version, R24 version - no issues with any sensors. i don't know what your problem might be :)
[G2 Android Development] mafukaz:
R24 with LS 10/10 no problems here on D802. Sensors working normally.
[G2 Android Development] MaluNoPeleke:
R24 Crash / random reboot while display on: https://www.dropbox.com/s/b2805xealjdnhw4/2014-11-07_07.39.zip?dl=0

D802 with 27/10 LS without retention enabled (no Synapse used).
[G2 Android Development] rmsinaga:
R24 report

No issue with R24 and Mahdi 10/27, proximity worked as usual, rotation as well.

Changed the governor to Conservative and some other parameters.

So far very good. Thanks a lot.
[G2 Android Development] Formhault:
I just reflashed R24 and the proximity sensor works fine now. :cyclops:

Yesterday, when I first flashed R24, I wiped cache & dalvik as well. Maybe that had something to do with it, or I dunno.
[G2 Android Development] nfin1te:
I think, that the sensor issues are rom related, several roms suffered from those problems recently.

I just installed R24 on Slim 8.8 / D802 - no problems involving sensors whatsoever, just checked incall.

Thanks!