yashsingh1/xdaforums huggingface dataset:
[G2 Android Development] kopter3161:
Exactly. Either its individual hardware fault or just software issue. Because i believe if it is hardware fault, then gps wouldnt be functional at all or at least the problem will not worsen,it will be constant over time. Maybe this problem are region specific?

Back on topic,R7 is working really great right now on my phone despite the very conservative behavior by default. No micro lags at all the time. And believe it or not, i've make it more conservative wayyy more but UI and games still fast and fluid. Doesnt had any performance impact on my usage.

My setting since past 2 weeks:

1.5 Ghz every core

1 Ghz touch boost

1 Ghz off-screen

Interactive governor

Hotplug and Wakeup boost disabled

Intelliplug (disabled MSMhotplug)

2x core boost

1x core off screen

-50mv underclocked

320 Mhz max Gpu

Simple_ondemand

And yes,i checked max cpu speed everytime after playing some games and indeed it kinda hit and miss. Sometimes max speed stick sometimes not at all. I hope R8 doesnt have this issue. Really looking forward for it! Good job [MENTION=5438598]RenderBroken[/MENTION]!
[G2 Android Development] RenderBroken:
What do you mean Max Speed doesnt stick? Can you explain further?
[G2 Android Development] berryman13:
The D800 is not a piece of sh**. Yours may be performing badly because of your configuration, but renders configuration works fantastically

Rebderbroken, what are you using nowadays for governor? I know you like fiops for io with f2fs but governor? Also what's the difference between the stock tuned interactive and intellimm, optimax, bacon, and hyper?
[G2 Android Development] Danzano:
Just to close the GPS debate it is a hardware issue across all variants it is where the antenna connects to the outer shell which is why the issue is sporadic in appearance and cannot be narrowed down to hardware/software. Good news is it's an easy fix with time and patience
[G2 Android Development] RenderBroken:
I am testing Bacon again, I have been pretty happy with it. On this note:

So far for R8 I have:

YankActive Governor from Yank555. I like his work. Its obviously based on interactive. Still we may like it. Who knows!?

Brought F2FS as up to date as possible and brought inline with the Creator of F2FS source.

Still to come,

Sound Control Rework

Other Optimizations.
[G2 Android Development] chrisexv6:
What is the fix?
[G2 Android Development] Danzano:
You have to open up the casing and slightly prop the touch points of the antenna there is a video on YouTube how to do this but like I said takes time and patience
[G2 Android Development] kopter3161:
What i mean is sometimes when im playing games, max speed of cpu automatically back to default 2.3Ghz as oppose to my preference at 1.5Ghz. I had to set it in synapse everytime it happen.

I just noticed something, this issue happen mainly when my cpu get hot. Is it because of throttling?
[G2 Android Development] Formhault:
I've read about that, too. Not sure what to say... but in my case, the issue seemed to be purely software related :) .
[G2 Android Development] RenderBroken:
Hmm, Could be. Maybe it throttles to 1.5GHz first then restores to 2.3GHz. Never really noticed but good catch. I will take a look to see what I can do. Does it happen all the time? Could you test this for me some more then get me a Syslog?
[G2 Android Development] phoenix_rizzen:
Well, that was a journey and a half. At the very least, I learnt something new about TWRP, adb, and getting files onto the phone when the internal memory is wiped completely clean. :)

TWRP 2.8.4.0

Backed everything up in TWRP first, and then copied everything off the phone onto the laptop.

Spent 2 days trying to get adb to work with the laptop and the phone while booted into the OS and into recovery. After much gnashing of teeth, pulling of hair, and banging of head on desk, I got it to work. (Please don't ask me to explain how I made it work ... I really don't think I could answer that.)

Formatted /data and /cache to F2FS in TWRP.

Then spent another hour-ish to get "adb sideload" to actually complete successfully. Discoverd that you can only run "adb sideload" once and then need to reboot back into recovery. But, eventually managed to get the following installed:

* BlissPop v1.8

* RenderKernel R8 (test)

* PA Gapps (nano)

* SuperSu 1.45

Everything is working the same as before. :) Just with /data and /cache now formatted as F2FS. :D
[G2 Android Development] RenderBroken:
Sorry Pal, you must have had the settings on hard mode. lol you could have easlily just went to Mount > Enable MTP. Sorry you had a hard time. Glad you got it working though!
[G2 Android Development] phoenix_rizzen:
Nope. No MTP options anywhere in my install of TWRP. :( That's what the first day was spent trying to make work. Running the "adb sideload" function in TWRP mentions "MTP enabled" ... but the device never showed up on the laptop. There were issues with the USB drivers on the laptop, as well, so it's possible that had something to do with it.

Long story short, everything is working now, and I have a better understanding of how recoveries, adb, and whatnot work together. So it's not a total loss or wasted time. :D
[G2 Android Development] RenderBroken:
Ewe, lol that really sux. Sorry bro. What version of TWRP did you have?
[G2 Android Development] kopter3161:
Yes i too think it is throttling issue since it will only happen when my phone get warm. Last times i reproduce it max cpu speed bumped to 1.9Ghz on core0 and 1.7Ghz other core.

Im sorry but i dont know how to take live logcat. Is there any way i could do it? I only know to get last kmsg though.
[G2 Android Development] vPro97:
When flashing this on lollipop, so you guys flash it at the same time as the ROM, or do you flash ROM, boot, reboot to recovery then flash kernel?
[G2 Android Development] RenderBroken:
kmsg is fine. Just use the App called Syslog in the Play Store. That would be the easiest way.

All at the same time. There is no need to flash them separately anymore. Not for a long time at least.
[G2 Android Development] enr88:
Usually flash ROM,boot and reboot to recovery..
[G2 Android Development] vPro97:
Great, thanks both. I ran out of thanks due to the stupid thanks limit.

Why are we back on R6 again? I downloaded R7 yesterday, is it buggy?
[G2 Android Development] RenderBroken:
There is a small issue with Sound not working correctly all the time. R6 also isn't setup to be ultra conservative either like R7 is.
[G2 Android Development] phoenix_rizzen:
TWRP 2.8.4.0 (blastagator version).
[G2 Android Development] RenderBroken:
Look again for me. Its under the Mount button and its a big button that says "Enable MTP". That would be weird if its not there.
[G2 Android Development] carlos67:
Where is the changelog for this kernel? I've clicked the link in the OP but all it seems to do is take me to the github. Can't see any changelog there.

Reason I ask is because I am thinking that R8 may be 1-2 weeks off being released and I believe that R6 is more responsive than R7( what I'm currently on) so I want to downgrade to R6 but want to know what I would lose by going from R7 to R6.

Anyone? :)
[G2 Android Development] phoenix_rizzen:
Huh. Now it's there. Actually, it's "Disable MTP", guess it's already enabled. Plugging the phone in while in recovery, it doesn't appear on the laptop. Pressing "Disable MTP" and then "Enable MTP", it shows up on the laptop.

I swear, it wasn't there yesterday when I was testing all the ADB/MTP stuff in the recovery. Wonder if the TWRP theme I was using wasn't showing it. It was a TWRP 2.7 theme that seemed to work nicely with 2.8.3.1, so I kept it when upgrading to 2.8.4.0.

I didn't bother checking for the MTP support again after re-formatting /data and it reverted to the default theme. My bad.

Well, now I know for next time I decide to go down the rabbit hole. :D

EDIT: Yeah, it's the theme. I re-enabled the theme and the MTP option isn't there. Remove the theme, and the MTP option is there.
[G2 Android Development] RenderBroken:
R8 is actually incoming pretty soon. The way it looks is a couple days. No real Changelog. If I gave one I would essentially just give you watered down info that is in the same list/order as Github. But with Github you see the changes happening and can click the ". . ." button and get more info on the individual change. Also even see the code that was changed if you click the commit. I cant think of a better change log then for me to literally regurgitate the same info just shorter. The only real loss is the dates. I used to have them included with the zips but removed them to save room so you could see the full name when downloading new kernels from your phone. I may rethink the changelog setup.

Its all good. I just wanted to make sure because I included that in my instructions and wanted to make sure.

Also for those interested I wrote up a little hot to on building my kernel and include everything you would need to do so.
[G2 Android Development] RenderBroken:
[MENTION=3116537]carlos67[/MENTION]

Now take a look at OP#2 at the bottom. I will start doing change logs like this.
[G2 Android Development] carlos67:
Thanks, wasn't looking for an ETA btw (honest!). But, I don't think I will go the F2FS route because it seems like a bear of a journey (with potential for a lot to go wrong) for a little extra performance, so the main thing I'm looking out for is an improvement in how Synapse behaves with profiles, eg. synapse crashing out when pressing restore profile option. Synapse is a great app but so frustrating sometimes in it's inconsistency of operation.

Anyone who has converted to f2fs, on a scale of 1-10 with 10 being the greatest, how much of a performance improvement (in general UI speed and smoothness eg app opening, scrolling etc) have you seen and was it worth it?

Edit: Changelog in OP#2 :good::good::good:
[G2 Android Development] RenderBroken:
Synapse Crashing out on restoring a profile is a non issue since it will do the same thing regardless. In the end it still restores the Profile. The way it is designed is to close out Synapse upon restore anyways. The crash of Synapse is a false positive. I will have to code a way to close it more gracefully. Yea its still growing too. There are alot of things I wish were natively supported like profiles but I have to use a coded way to do so. But at least I have that much freedom. Besides, users can still use the tried and trusted apps like Trickstermod and such without any issues from Synapse. That is one reason why I will not include it in R8 on. If a user wants to use it then they can install it. Still I feel Synapse enables me to offer more. Also I feel F2FS is stable at this point. I haven't had any issues and when writing to memory there is no comparison to EXT4. It just writes so fast its almost instantly. lol
[G2 Android Development] phoenix_rizzen:
It's like night and day, like having a new phone. Data transfers via MTP as several times faster than before. Apps install a lot quicker. And files download a lot faster (still limited by flash, but not nearly as much as before).

It's definitely worth it to format /data as F2FS, IMO. Granted, I only have a couple of hours experience to go by. :)

---------- Post added at 12:54 PM ---------- Previous post was at 12:42 PM ----------

I'm not sure if this is a kernel issue, a ROM issue, or something wacky with my phone.

But, since formatting /data as F2FS, I cannot reboot my phone. :(

Flash ROM, gapps, kernel, Viper, and SuperSU, can boot once without issues. Reboot the phone, and it sits as the boot animation forever.

Re-flash ROM, gapps, kernel, Viper, and SuperSU, can boot once without issues. Rinse and repeat.

Re-flash just the kernel, no change. Sits at the boot animation forever.

Re-flash the ROM and the kernel, and it boots correctly, although no gapps so all Google stuff breaks. And it doesn't reboot.

Have to force a power off and force it into recovery via Volume-Down + Power.

Unfortunately, this means I can't change the DPI, and 480 is just too "big" for me, used to 400.

EDIT: Correction, it seems a soft-reboot is enough to set the DPI. Now I just can't do anything that requires a reboot. ;)

D803

TWRP 2.8.4.0

BlissPop v1.8

RenderKernel R8-test

PA Gapps (nano)

SuperSU 2.45
[G2 Android Development] RenderBroken:
I am going to have to say that its Rom, Viper or Su In combination. I have the D800 as well with none of these issues. Also if formatting to /F2FS causes such issues, it would happen 100% of the time, not be selective. Also you would not be the only one to report such. I am not getting on to you, just want to make sure that we don't spread misinformation even when you are being helpful and reporting just like you should :) Can you run adb shell which booting up and then run dmesg. Can you get me that info? I would like to see exactly what the issue is. Thanks for reporting!
[G2 Android Development] phoenix_rizzen:
Fixed. Turned out it was the "Mount namespace separation" feature in SuperSu. It's now enabled by default, and I hadn't configured SuperSu yet in my testing (DPI is the most important, then Viper, then everything else; the former two require reboots).

Disabling that option allows it to reboot correctly. Tested several times now. :)
[G2 Android Development] RenderBroken:
Thats weird. I guess I will have to see what it does.
[G2 Android Development] fLipz:
[MENTION=5438598]RenderBroken[/MENTION]

Device: D802

Thank You for the R8 F2FS Test Kernel.

R8-Test Kernel working well on CM12-012715 Nightly with F2FS /cache /data and EXT4 on /system file system.

for your reference, i'll attached the KMSG and Last KMSG Log.
[G2 Android Development] kopter3161:
Here from syslog. I just tick kernel and last kmsg only.
[G2 Android Development] ktetreault14:
[MENTION=5438598]RenderBroken[/MENTION] we have found out why your latest kernels won't work with the multiboot method. Would it be possible to unbump a kernel and then Loki it?
[G2 Android Development] RenderBroken:
Yes, the reason is because its bumped. I will have to think about it but I don't really care to unbump my kernels. I may release R8 with both bump and loki though.

So why are you wanting to multiboot. What do you get out of it?
[G2 Android Development] ktetreault14:
Testing f2fs now

---------- Post added at 11:14 PM ---------- Previous post was at 10:35 PM ----------

I would say the main reason that I want to use it is to be able to test KK and Lp only stuff. Im backing up my data now to test f2fs and also looking to see if i could just loki the kernel and that be fine.
[G2 Android Development] RenderBroken:
Yea I am sure the issue is with it being bumped. That is only for the LG bootloader. Using this custom one won't work with it.
[G2 Android Development] ktetreault14:
Yeah [MENTION=5500870]vPro97[/MENTION] found out if we used r4 of your kernel it works, because it isn't bumped.
[G2 Android Development] RenderBroken:
Really the biggest problem I have is:

Bump is a soo much cleaner and proper way to flash. Loki, while it works, is a dirty way to flash. Sometimes you have to do the right thing and suffer til its adopted by all. Hopefully when LP drops and we get a new bootloader and such. We can move to bump all the time. But that's me dreaming. Its not hard for me to make loki builds at all. I may just modify my build script to create both zips at once going forward. You have the LS980?
[G2 Android Development] ktetreault14:
Yes I have LS980. Ive been trying to get F2FS working on Plain-Andy 15.1 but I cant get the rom to boot. Was going to use that rom because it supports rro.
[G2 Android Development] hotrodwinston:
Dang it [MENTION=5438598]RenderBroken[/MENTION] seeing a easy going great dev like you really makes me wish I had a computer that was usable for learning to build roms/kernels.
[G2 Android Development] rmsinaga:
Any other testimonials about the benefits of converting /data & /cache to f2fs?

Looking forward to R8 to try.

Thanks for your excellent work as always, [MENTION=5438598]RenderBroken[/MENTION] :thumbup:
[G2 Android Development] RenderBroken:
Well, it doesn't take much hardware to build kernel. The only way to learn is to jump in! ;)

Thanks! It's turning out to be a pretty substantial update.
[G2 Android Development] tropenfrucht:
Using Dual Boot Patcher doesn't change bootloader it's stock LG bootloader. But you have to patch the secondary kernel that it loads system and data from it's new locations /system/multiboot/dual/system and data/multiboot/dual/data. And when the boot.img gets patched by the app bump gets lost. That's the problem here.

Would it be possible for you to provide a zip file without actual boot.img but loki-script so that we can extract your bumped boot.img and put it into that zip for flashing?

As about the reasons for multibooting. For me it's GPS and camera. I would go fully AOSP but on every ROM I tried I have problems with GPS accuracy ranging from 10 m - 60/70 m (somtimes jumping to parallel streets while driving ^^) while on stock ROM I get an accuracy from 5m - max 20 m on the same route. And I've still not found a camera on AOSP thats nearly as good xdabbeb's XCam. It's also easier for testing new ROMs if you install it in dual or multi-slot so you can always switch back to your daily driver via button in the app or by flashing a simple zip-file instead of nandroid backup and restore.
[G2 Android Development] szabyka95:
which roms are compatible with /data and /cache formatted to f2fs ?

tried resurrection, but stuck at boot for 5+mins
[G2 Android Development] bgx:
As far as I know all CM12 based roms, but you must use render R8 kernel. I have cache and data on f2fs with rr and render r8 working here.

First boot need some time. Be patient it need some time!
[G2 Android Development] szabyka95:
and from where can i get the R8 kernel ?

i searched in thread, but i didn't found
[G2 Android Development] heleos:
It is not released yet, there are some test builds for f2fs functionality, but it is not complete yet
[G2 Android Development] bgx:
You don't searched good enought:

http://xdaforums.com/showpost.php?p=58383369&postcount=4548
[G2 Android Development] RenderBroken:
Thanks for explaining! Also that's not a bad Idea. I will give you one. In the mean time you can use 7zip and just delete the boot.img from R4. You can use that. Its really the same except that it will add Synapse on flashing. But I will create a clean zip for you guys.
[G2 Android Development] ktetreault14:
Thanks a bunch! You're a great dev
[G2 Android Development] RenderBroken:
Thanks!

Here is the zip:

Empty Loki.zip

Just place your boot.img at that root of the ZIP file.
[G2 Android Development] luv2increase:
R8 will be great. Anxious as ever. Good work Render
[G2 Android Development] vPro97:
Ok now I'm not sending this message using Internet Explorer, but I still thought I'd let you know.

Render kernel R4 is running like a dream! I'm so pleased with this kernel it's unbelievable. Sure it can be improved a bit (hence the reason I barely can wait for R8) and I really hope you'll release a lokied D802 version. I've been reading around and you seemed to have provided a way to loki our own boot images. If that's the case, I'll just do that instead once R8 hits, if you don't provide us with a pre-lokied kernel.
[G2 Android Development] megawebmaster:
I wanted to add: using test R8 kernel with F2FS for cache and data and got now everything works exceptionally great. Seems as stable as R7, not sure about real battery life. Will post again after a few days (probably Sunday) with next impressions.

Either way: incredibly good job!

Using D802 with 29th CM.
[G2 Android Development] reemar:
quick question, if we will have f2fs support, is it means that we need to do something special every rom flash or that its a one time initialization and that it for working with f2fs?
[G2 Android Development] heleos:
You need a compatible recovery, rom and kernel I believe. Once you make a partition f2fs, it's that way until you change it
[G2 Android Development] megawebmaster:
Nope, you need only recovery and kernel that supports F2FS for /data and /cache. For /system ROM support is also required, but old, good EXT4 is better for mostly read filesystem.
[G2 Android Development] carlos67:
Spot on.
[G2 Android Development] phoenix_rizzen:
Yes.

You need to make sure you flash a kernel that supports F2FS. That can be part of the ROM, or flashed separately. But if you have any F2FS-formatted filesystems, then you need a kernel that support that. Otherwise it won't boot.
[G2 Android Development] reemar:
so, if for instance, i have cm12 of 29.1.15 on f2fs recovery,kernel, all supported, for moving to 03.02.15 for instance, i can just flash the rom and right after it, to flash this kernel which support f2fs for it to work and that what is required for boot?, or there is more thing to be doing?
[G2 Android Development] phoenix_rizzen:
If the ROM kernel supports F2FS, then you just flash the ROM as per normal.

If the ROM kernel doesn't support F2FS, then you have to flash a kernel that does before you can boot.

Typos courtesy of my Blissful LG G2 (D803).
[G2 Android Development] bbender716:
All this f2fs talk is making this vs980 guy jelly [emoji14]
[G2 Android Development] TheSpaceManatee:
Anyone feel that F2FS causes your phone to stay on LG logo longer than when on ext4? Thanks!
[G2 Android Development] Floodland:
While F2FS is faster writing, it is slower for readings, so if you have /system formatted with it, for sure it will be slower. I personally find no valid reason to use f2fs for /system.

Anyway, keep in mind that reading operations are slower with f2fs, so booting could be a bit slower using it while reading from /data too. It constitute a trade-off, f2fs is still useful because writings are much faster with it, while readings just a bit slower.
[G2 Android Development] TheSpaceManatee:
Hi just to clarify, I did not have system formatted to F2FS and actually boot up takes like 10 seconds longer :/ just my experience.. But great job nonetheless
[G2 Android Development] hotrodwinston:
I may just do that - I am a "learns by doing" type person!

What I am really wanting to build is a -very slightly- modified aosp rom that is odexed (for the slight speed and stability bump it gives).

But I may start with kernels just to learn till I can get better hardware than my 8 year old athalon 64 dual core with 2 gigs of ram system (its primary purpose is a media center PC so it is more than powerful enough for that - thus the lack of upgrading).
[G2 Android Development] luv2increase:
Has r8 been released? I know render said a couple days a couple days and thought maybe there may be a different download location.
[G2 Android Development] jesssiii:
Nope

LG G2 Verizon
[G2 Android Development] RenderBroken:
When I release it will be uploaded on the main site. Mainly the only time I will every upload to other sites is for test builds. Also I have been on a roll lately and don't feel like stopping.
[G2 Android Development] luv2increase:
Since you are taking a break, have you thought about having someone else continue your work?
[G2 Android Development] heleos:
Did I miss where he said he was taking a break?
[G2 Android Development] bleached45:
No.

---------- Post added at 08:54 PM ---------- Previous post was at 08:52 PM ----------

He meant roll on the kernel development. He doesn't want to release while fixing and adding features is going well. Kind of like releasing an incomplete project.
[G2 Android Development] berryman13:
Is there a language barrier going on or something? He's doing more work on the Kernel than ever.
[G2 Android Development] lucaci.ed:
[MENTION=5438598]RenderBroken[/MENTION] I'm testing the r8 test build with /data and /cache formatted to f2fs and this kernel works very well! But in the Device control section (I have BlissPop 1.9) I can see that the max clock frequency is 650 mhz! So it's overlooked? Because without your kernel the max clock frequency is 450.

Thanks for your work!
[G2 Android Development] RenderBroken:
It is a false reading. It is weird though. I have looked into it a little bit and cant see what the cause is. I may try to hunt it down before release.
[G2 Android Development] luv2increase:
Great!