yashsingh1/xdaforums huggingface dataset:
[G2 Android Development] MrDarkKV:
I think bad implementation is the main cause of such issues. The file-system itself is it actually generally stable, and I did run it for awhile on some other ROM's + kernels on the G2 with no issues. But that's just me; my voice hardly speaks for the masses.

I would say it's unfair to say F2FS would be applied to the masses if Render ever decides to support it; changing partitions is not something people would regularly do, for example even on XDA most people who flash kernels don't then actually go into the settings and change governors etc. Plus it'll keep most people away since a wipe of the partitions is required and a compatible ROM + custom TWRP to actually change the partition.
[G2 Android Development] 1ceb0x:
What i mean is "test it throughly before releasing it publicly here on xda" :)

You guys got me wrong. I am not against F2FS.. in fact, i was onr of the first who told Render about it and he did said he thinks about adding support for it. But we talking about it here and asking about it every day, will get tiresome and we don't want to make our dev tired :).
[G2 Android Development] crnkoj:
Been using f2fs for quite some time on my old nexus 7 2012 with the crappy flash and it's working better and faster than before with ext partitioning. Can't say anything about f2fs and the g2 though. Considering the g2 flash is like 6 times faster than that of the n7 2012 it probably won't make a difference (120ish mb/s vse 20ish mb/s)
[G2 Android Development] Garfield3333:
THX for this amazing Kernel !!!
[G2 Android Development] RenderBroken:
Yes, I have already cloned the repo and I will soon start merging in my 600 or so commits very soon. We will just have to see how it goes.
[G2 Android Development] :
I see no R23 d800 OC build. Only a R22 d801 build in place of it.
[G2 Android Development] RenderBroken:
Fixed, Thanks for the heads up!
[G2 Android Development] tdawgg777:
You sir are the man. Thank you.
[G2 Android Development] RenderBroken:
Just for the record, this sux. lol its like nothing is merging cleanly.
[G2 Android Development] :
Thanks! Gonna give it a whirl.
[G2 Android Development] NEO2598:
I'll flash tomorrow R23 on Plain Andy:) Can't wait ?
[G2 Android Development] tdawgg777:
I appreciate the work you put in here render... I have faith in you, and if it doesn't happen, I'll prob just stick to the last slim based on 4.4 and keep using your kernel, till the slim team starts deving lollipop
[G2 Android Development] RenderBroken:
So I have merged about 200 commits so far with about 400 more to go. I am going to stop for now. I will need some CM testers when ready. I will have to merge in some major features after all is done. I will let you all know when I am ready.
[G2 Android Development] Vollspacken:
First real cycle with LS 10/27 and underclock to 1.9ghz, awesome. Only normal usage like surfing, chatting, listening to musik for an hour and playing a bit.

Hope r24 will contain fastcharge to lower the loading power to 500ma, then it's the perfect kernel for me.
[G2 Android Development] RenderBroken:
R23 already contains fast charge. . . .

Look here

/sys/kernel/fast_charge
[G2 Android Development] Vollspacken:
Can't change values with root explorer, they won't stick after a reboot and charging rate doesn't change for me.
[G2 Android Development] phoenix_rizzen:
/sys is a virtual filesystem created when the kernel is loaded, that exposes information about the currently running kernel. When the phone shuts down/reboots, the /sys filesystem is destroyed. Thus, nothing you do in there will survive a reboot. The changes take effect instantaneously, though; no reboot required.
[G2 Android Development] Vollspacken:
Aaah, alright. Thank you!
[G2 Android Development] Formhault:
Which works f***ing amazingly!!! Charges at 1600+ mA even while (mildly) using it... Or so it seems.

Again, hope you are still working on that Synapse implementation.

Add 300mA too in Fast Charge Levels. Please :D. For those of us that sleep 10 hours, lol.
[G2 Android Development] NEO2598:
I installed the kernel yesterday on Plain Andy. I have - 50 UV and the other settings are default. What can I say?

The phone runs much cooler and is very fluid. Let's see now about that battery life:)

Awesome work [MENTION=5438598]RenderBroken[/MENTION] ?
[G2 Android Development] Steve125:
Absolutely love this kernel. Great audio quality and battery life, and no SOD's!
[G2 Android Development] Formhault:
[MENTION=5438598]RenderBroken[/MENTION]

Any way you can implement a vibration strenght for notifications in Synapse? :D
[G2 Android Development] moocamr:
Not complaining .... :D it is awsome Stable but dunno why i can see a little unsmooth scroll or swiping in setting or even on nova launcher ? Whats the advise for tuning governer ? Know that it can not be like dr87. Intercative which drain a lot but it's fu**in' snappier. How to make it smoother ? Dunno how to access q&a on tapatalk :(
[G2 Android Development] MrDarkKV:
Bacon works well for me, I did down the max clock speed on touch though, also enabled CPU multicore power saving- no stuttering at all! However this also depends on your ROM, for me with PA and the same settings it lags quite a bit, however Mahdi's latest release and these settings work amazingly! :good:
[G2 Android Development] TDSJR:
[MENTION=5438598]RenderBroken[/MENTION]

Any ideas why you lose sound when flashing to Houstonns PA 4.6 Beta?

Excellent work on R23! Thanks!
[G2 Android Development] Jerreth:
what version there was a release with no sound. you had to plug in headphones then unplug if im not to badly mistaken
[G2 Android Development] RenderBroken:
Yes, I have it on my todo list. Thanks.

Thanks! Not really sure about that though. Maybe a Ramdisk issue. I might have to add something to the one I use.

this would be interesting to find out if it worked.
[G2 Android Development] RenderBroken:
Two things:

1. I would like a proficient tester to try out a F2FS build I am working on. This would help [MENTION=5037435]REV3NT3CH[/MENTION] and I both. But you need to know your stuff and recover from a bad flash. Regardless this should not affect you getting back into recovery but you will need a TWRP recovery that supports F2FS. I will leave all that up to you. PM if interested.

2. CM's Source is Completely different from LG's. This means I have merged about 500 commits but they had been all done manually almost and I am afraid of dependencies missing because the source is so different. What I am planning is to water down what I am going to merge. I at least want to have all my main features but the problem places are the subsystems. Those may not be like my mainline builds at all but it may not make a noticeable different. It has just been a huge pain and I am going to have to scrap all of what I have done so far . . .lol But I would like to continue to get a CM build out.

Thanks Gents and occasional Gal!
[G2 Android Development] RenderBroken:
Also some new additions for R24!

MSM_Sleeper - Set MAX freq during screen off!

Simple GPU Algorithim - from Faux - Even more GPU Control

Added more GPU steps!!! - Now there are 100/200/320/389/450/533/650

Fast Charge Updated

More to come!
[G2 Android Development] moocamr:
hope to try it soon on mahdi 9/20 :D
[G2 Android Development] InfinitusDesigner:
I can test F2FS support in 2.8.1.1 TWRP with Thermal Control and F2FS, I will flash R24 as soon as you release this "beast" for download and also try the PA 4.6 BETA 5 together.
[G2 Android Development] :
Just as a complement to my PM, I am would be testing on the latest LS build, along with the TWRP 2.8.1.1 with F2FS support.
[G2 Android Development] RenderBroken:
Danke!

I will be building a personal test build to test my new features and synapse changes and then a build with F2FS after that.
[G2 Android Development] crnkoj:
What's the voltage on the gpu when overclocked?
[G2 Android Development] InfinitusDesigner:
Are you using personal ROM? I'm having troubles with new PA ROM, they've changed lots of stuff in their source and thats why my SIMcard is beeing recognized I think.
[G2 Android Development] RenderBroken:
Not certain, I would have to dig to check. Mainly you can set the min and max freq to whatever you want. Now that there are more steps to take, the different gpu governors play a larger role. If you find out before I do, can you post in thread? Thanks!

Not sure, I have not been keeping up with PA since I thought it wasn't compatible at all. I am currently using Liquid. Can you post the link to the PA Rom you are using? I imagine I just need to make changes to my Ramdisk.
[G2 Android Development] :
Well, right now the old PA maintainer, Houston is back, and made a test build (Which was intended for only one person, but someone found it and leaked it, and the thread went haywire), using his sources and stuff. I would wait until he releases a public build before making a PA compatible build.
[G2 Android Development] Formhault:
I wouldn't use any PA build that is experimental / beta / test. PA is famous for the inclusion of some weird commits that caused permanent black screens on the screen (back when that used to be a thing, you know...). So... my advice for you would be that the next time you see a wild PA test build appear, think thrice before flashing it.
[G2 Android Development] RenderBroken:
This is what I thought. Wanted to make sure I was not missing something lol. Thanks for reporting!
[G2 Android Development] rmsinaga:
What's the benefits of having more GPU steps? More battery friendly?

Thank you.
[G2 Android Development] InfinitusDesigner:
Here it is.

http://aospal.com/aospal/roms/d802/

As you can see someone was developing in this time Houstonn was out. Its very fast though, and thats why I use it, but this last build does not recognize my SIM card. I will install fluid smooth. Other ROM ive tried to use with your Kernel was Ehndroix but I got stuck in LG logo as well, I think they changed so much the original cm source.
[G2 Android Development] RenderBroken:
Yes and no. Really I like giving the user control. I had also implemented Faux's Simple GPU Control which allows you to have more control in how fast the freqs ramp up or down. On top of the regular GPU governors. Before we only had 3 freqs, that is not alot to choose from. Now with the 7, I have it set so 100MHz is the idle freq instead of 200MHz as before. This will lead to power savings. But now that you can OC the GPU you can have even more GPU power than before. Its really up to you.
[G2 Android Development] :
Any chance of TCP congestion settings (Also in Synapse) in the near future?
[G2 Android Development] 1ceb0x:
They were there before but the MISC tab from Synapse is not available in R23. Render is working to bring it back. I guess you can change them through Trickster in the meantime.
[G2 Android Development] :
Ah, thanks. I thought I saw them before at one time.
[G2 Android Development] RenderBroken:
You are correct! I have found and fixed the issue. Now I am working on fixing the GPU errors in Synapse. There has been so many new things added to R24. Alot more control through synapse. This tool is fantastic and will allow me to setup the program the way I want it to be.

EDIT

GPU is now showing properly in Synapse.
[G2 Android Development] crnkoj:
Yeah will post if I find it, but I'm not really sure where to search to check. One more consideration would be, if by using the additional steps and on possibility , the voltage for the non-oc frequencies stays stock or it goes up like with the cpu part when you implement/allow ocing. In that case it might not be worth having it
[G2 Android Development] Formhault:
---------- Post added at 11:29 AM ---------- Previous post was at 11:25 AM ----------

It's not closed to PA only, though. Users reported their screens developing problems even on stock ROMs or stock-based ROMs (albeit, they are much smaller in number than those who blamed PA and Carbon).

Besides, what the hell... I installed PA on the Galaxy Nexus I sold a few months ago. The buyer wanted it beforehand, so I had some time to play with it. It sucks. In 30 minutes, I couldn't find the customization options.
[G2 Android Development] MrDarkKV:
PA's new approach is a slimmed down version of AOSP with pie, but thats about it.. No other options, kinda sucks compared to the old PA.
[G2 Android Development] Formhault:
Awwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwww ParanoidAndroid got paranoid so they stripped off all the features? :(
[G2 Android Development] Raagh:
Yes exactly thay. If you want the old paranoid i recomend saberdroid ( its paranoid android compiled with sabermod and all the features we love in paranoid)
[G2 Android Development] RenderBroken:
No it does not raise the V-Core. The reason that happens for the CPU is how OC works on Krait SoCs. They have these Freq Tables that are already mapped out. This means that All freqs from Min to Max are aligned in a table with a preset Voltage per freq. Well there are numerous tables that have depend on your PVS bin number. The higher the number the higher you can OC but the OC we use is really not that big so it can be used on most if not all devices. So the PVS Bin decides which Freq Table to use. With the GPU you just recode and add to the table the freqs and bus speeds you want. As long as it is within reason and an actual freq the GPU can use.

So here is where we stand. I worked on this all day yesterday and Synapse is fully working now along with some changes i made to what is seen. I have added options as well. Another addition in r24 is dynamic FSync. Since I feel that my kernel is as solid as ever, this option is now in Synapse and will be enabled by the USER. NOT by default. Also Sweep2dim has been added. This is something I miss in most roms with swiping the top of the screen so I have been able to add it using savoca's sweep2dim feature. I love it so far and I think you will too. Vibrator strength was already a part of this kernel but I added an option in Synapse to control it (Under MISC). Hell because I love Synapse and its possibilities so much I even added new Buttons:

FSTRIM Partitions - Obvios but runs fstrim on /data /system /cache

Update Touchscreen Firmware - Updates touchscreen firmware so DT2W will work properly on AOSP Roms.
[G2 Android Development] Formhault:
Awesome! Keep that R24 coming! :D

Is this really necessary? I mean I've always wondered what that damned "Update touchscreen firmware" button in the hidden menu (in LG ROMs) does. I mean, it didn't seem to pull anything from the Internet... all it seemed to do was to basically reload the touchscreen driver. :confused:
[G2 Android Development] RenderBroken:
Yes, its worth it. This is what fixed DT2W for me. Beforeusing it, it would take me 5 taps to turn on the phone. Now it works with just 2. Also you cannot access the hidden menu when using AOSP roms. This is a way to manually kick it off for the few that need it.
[G2 Android Development] RenderBroken:
Also in R24, worked on OOM and LMK. I thought that they were lacking a bit so I wanted to bring them both up to speed. This allowed me to protect apps from deletion from RAM. This should also increase RAM performance and keep certain services and apps from closing out unexpectedly. Note, after R24 I will release special R24+F2FS builds.
[G2 Android Development] blacklight1025:
Its funny that you're talking about this now, cause my DT2W just stopped working this morning, and I was looking for that hidden menu lol explains why I couldn't find it.
[G2 Android Development] Formhault:
Weird. I mean I haven't seen any Wi-Fi traffic going on after trying to "update touch firmware" myself, so I'm still sceptic regarding what that thing actually does...
[G2 Android Development] Fade2:
So, how can I update touchscreen firmware if I'm running AOSP ROM?
[G2 Android Development] RenderBroken:
Check OP #2, Those are the manual steps to run it..

Yea I had the same results with the Hidden menu button. I even went as far to flash a stock rom to run it. lol. Didn't do a thing. But if you do it this other way you can tell it is doing something because everything freezes for a couple seconds.
[G2 Android Development] :
Oh man, starting to make me even more excited! Really hope R24+F2FS gets out by the end of the night! :D
[G2 Android Development] RenderBroken:
OP#2
[G2 Android Development] Formhault:
Because all I think it does is IT RELOADS THE TOUCHSCREEN DRIVER. So of course it freezes for a couple of seconds. Look in the code if you can and see what that freaking thing does... it's driving me nuts when people "update" it and all the sudden placebo pills cure cancer.

---------- Post added at 12:19 AM ---------- Previous post was at 12:16 AM ----------

I changed the value inside the fast_charge_level file from 1800 to 500 and the value inside the force_fast_charge file from 0 to 1. Reconnected charger... nothing. Rebooted phone... nothing. Nothing = phone still charges very fast (definetly not 500mA).
[G2 Android Development] RenderBroken:
I would agree that it's placebo if it didn't work for myself. The entire time I had the phone it always took 5 taps. Immediately after manually forcing the update the problem is fixed. No placebo, just results. Also please not that in the hidden me u there are actually two buttons the update touchscreen firmware. One does nothing and the other does what the command line command does. I will end this with yes, the command in OP#2 works. I am not one to push placebos. . .

As for fast charge, if you want to have 500ma you have to not change it to 1 (this is default on which makes it 1200ma if I remember correctly) you have to change it to "2". This sets it to custom mode where you can then set it to 500ma.

Also note guys, that I have updated fast charge so now it will automatically reconnect and enable when unplugged and replugged back in. It will also remember your settings. Also I have added 300ma as a charging options. There are many more new features to fast charge that I will have to explain further later.
[G2 Android Development] Formhault:
Hope you didn't take that as an offense or anything... cause I surely didn't want to make it look like so.

What two buttons, to be exact? I was talking about the "Update touch firmware" from the hidden menu in LG ROMs which, again, all it seemed to do was to reload the driver (as it didn't pull anything from the Internet). The way that thing works (cause it definetly solves stuff for some people) is a mistery to me... And there's only one such button there, lol.

Lol, I forgot about that. I thought it's gotta be 1 if we want the values in fast_charge_level to stick or 0 if we don't :silly:.

Hope... in Synapse :silly: :victory:
[G2 Android Development] RenderBroken:
We are good, no worries. The first firmware update button is under settings, the other one was in device test.

The second one is the one that is supposed to work.

Fast Charge is now in synapse. You can edit all the main settings. Yea that is the old fast charge settings. With this one you have off, on at 1200ma and custom.
[G2 Android Development] Raymonf:
Huh. When I flash it and reboot, I get stuck at the LG logo. After a few seconds, it dims a little.

What's wrong?
[G2 Android Development] 1ceb0x:
your rom and the fact that you don't read the OP.
[G2 Android Development] Raymonf:
I don't see anything about the LG logo in the OP. I'm using CM11. o_o

It worked before, but after updating to the lastest version for d800, it b0rked.
[G2 Android Development] :
Keep in mind it was clearly stated in the OP that CM sources are not used, so it was already luck you were able to run it. CM might've changed something in their sources that ran it.
[G2 Android Development] Raymonf:
Got it. Thanks!

I'll just blame CM for this one and move to another kernel.
[G2 Android Development] :
Furnace has a CM kernel, and Render is working on a CM kernel release at a later date. Good luck!

Also, [MENTION=5438598]RenderBroken[/MENTION], I'm going nuts checking the page every couple of hours for R24, all the features you are adding keep getting better and better, makes the wait even harder. :crying:
[G2 Android Development] Formhault:
:)

First 5 hours of SOT made the battery drop to ~50%. Was writing something down from a few .jpg files. During that time, I was briefly switching from 2G (2-4 bars) to 3G (0-2 bars) every ~20 minutes to browse Tapatalk and check e-mail + activate sync.

After those 5 hours (when I left from the University), I started browsing Tapatalk and Chrome a lot (constant 3G data + sync on). Sent/received some text messages (~20) and made some phone calls (~40 minutes). Reading Pocket, too.

Screen brightness was manually set at 40~60% most of the time (except for some relatively short periods of time when I had auto brightness on and it must have reached >70%).

I'm selling my power bank :).
[G2 Android Development] cloud628:
Im running the latest R23 build with my LG G2 D800 on Mahdi (10/27). I am getting cracking noises while watching youtube videos with my speakers as well as getting complaints of an echo from the other side during a phone call via data as well as wifi calls. The echo occurs in bother speaker phone as well as regular call. Anyone know why?
[G2 Android Development] RenderBroken:
NICE!

Not sure. . . But I have the D800 as well and don't have any problems like that. Also the lack of anyone else complaining of this issue makes me wonder if its a kernel issue and not a Rom issue. Not to just pass the buck. Have you had any issue with any prior builds? You can also make a backup and flash another rom to see if it still happens. But I don't believe the problem to be on my end. Thanks for reporting though. Let me know what you find out.
[G2 Android Development] RenderBroken:
I am soooo close to releasing. Fixing a build error now. . .
[G2 Android Development] cloud628:
I do recall having this issue on the R22 build as well. I just reverted to stock Mahdi + Dr87's kernal. The issue seems to have subsided (The In call echo's at least. Will test again tomorrow once I've reinstalled all my apps). Possibly a Kernal issue? not to sure either :/
[G2 Android Development] RenderBroken:
So I have fixed the weird build error for my LMK and OOM Overhaul. I just have a few minor things to change as far as the Synapse GUI and placement of options. I should be building when I get home from work in about 8 hours. I am pretty excited about this release. I believe it to be better than R23!
[G2 Android Development] :
Christmas is coming early! :)
[G2 Android Development] TDSJR:
[MENTION=5438598]RenderBroken[/MENTION]

Loving R23 and looking forward to 24.

Have you given any thought to including the Alucard gov. & hotplug in your builds? Have used them on Barts Dorimanx port in the past. Great battery life & smoothness. I actually think it MAY be a little better better overall than Optimax.

Not a request, just a question.

Keep up the GREAT work.

Thanks.
[G2 Android Development] Matze060906:
Christmas is when render release his next build and rev3nt3ch an new build of ls for D802 with working sensors...
[G2 Android Development] RenderBroken:
I have looked at them both. I may create a test build with them but looking at the source, I did not think it better than Msm_hotplug from myfluxi. Also I enjoy the customization you can have with it as well. If you want battery, tune it for so. If you want performance then make it so. But I can't rule it out til actually testing it out personally.

Also thanks guys for the kind words!
[G2 Android Development] Formhault:
2 and a half hours SOT. 3% time without a signal and about 35 minutes of voice calls.

Oh and... the battery's down to just 48%, so it looks like I won't be charging the phone up for tomorrow (midnight here).

On Reven's LiquidSmooth 10/27 build, of courss :D.