• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[KERNEL] Furnace for AOSP [D850/1/2/5/LS990/VS985][3/1/2015][LiveSharp][KCAL]

Search This thread

Sc4ryB3ar

Senior Member
Mar 3, 2012
961
516
Plymouth
I'm coming from a Nexus 5, and have only owned my G3 for 4 days....what I'm reading is throwing me for a small loop. Hoping for an explanation. Title of the thread for this kernel states aosp, but the description in the 1st post states cm based....I thought aosp and caf were totally different beasts, an I wrong?
 

marcdw

Senior Member
Sep 24, 2014
5,731
2,882
57
Baldwin Park
Yeah but in this case AOSP means not stock-based. Furnace is also available for the original KitKat stock-based ROMs.
For the most part when you see AOSP that also includes CM (anything non-stock).

Sent from my LG-D851 using Tapatalk
 

m1trand1r

Senior Member
Mar 6, 2011
12,403
9,586
You don't wanna know.....
I'm coming from a Nexus 5, and have only owned my G3 for 4 days....what I'm reading is throwing me for a small loop. Hoping for an explanation. Title of the thread for this kernel states aosp, but the description in the 1st post states cm based....I thought aosp and caf were totally different beasts, an I wrong?
well...maybe you're wrong....maybe not....AOSP meaning is somewhat abused on G3...IMHO ....because I saw claims of rom "devs" that some roms are AOSP based....which in my experience has very little or almost nothing to do with CM based roms....and all roms have one thing which connects them tightly ....bugs....so....when you see label AOSP...take it as CM....This kernel is very good work IMHO (tested thoroughly by myself ) but as developer himself said...it's CM based....only source avaliable....and most if not all custom roms base is also CM derivate...:)
My 0.02€ :)

/LG-G3/d-855/16Gb/Titanium Black/
 
  • Like
Reactions: jhr5474

fatapia

Senior Member
Apr 21, 2010
291
71
But cm is based off of aosp...

Anyways something interesting ive found out. I started having problems with my lockscreen on wake, and eh performance. So as far as 5.1 and 5.1.1 and the 2-28 edition of the vs985 zip, sharpening really hurts performance. Turned it back off and everything was smooth again.
 

teddy0209

Senior Member
Feb 5, 2011
2,318
690
I'm coming from a Nexus 5, and have only owned my G3 for 4 days....what I'm reading is throwing me for a small loop. Hoping for an explanation. Title of the thread for this kernel states aosp, but the description in the 1st post states cm based....I thought aosp and caf were totally different beasts, an I wrong?


I'm also a nexus user, where aosp is different from cm/caf on roms and kernels... Just ignore that, here in the G3, AOSP is any other rom except stock based... That includes cm... [emoji6]


Sent from my iPhone using Tapatalk
 

wargear

Senior Member
Jun 12, 2012
193
98
pensacola fla
trying your kernel on my build of liquidsmooth 4.1 for the g3 d850... very nice boots fast I installed your accompanying furnace app from play store (free) to enable dt2w and sw2sleep however the controls for that are not present do they not work for the g3? If you can pm me or snd a hangouts msg have a couple items I'd like to run by you. Thanks for all the work you've done! wargear
 

Top Liked Posts

  • There are no posts matching your filters.
  • 88
    hhnNAaE.jpg


    Note: I will NOT add useless optimization drivers, "DanceLizard360" governor, or any random frequency step pulled out of who knows where. I WILL add features I've either written or thoroughly reviewed myself that actually serve a purpose. If you'd like to contribute or recommend a feature, think before you speak. This is not a toy, this is a tool to control the hardware on your device. That said... enjoy!

    download | source | features | tweaking

    Control your display sharpening on the fly! (Thanks to @autoprime for help! (and @sawdey21 for the name)).
    Whetstone

    This release is for Lollipop-based ROMs only. The kernel is based on cm-12.0, which is the only ROM officially supported.
    It is highly recommended that you are NOT coming from a a custom kernel during installation, unless you are updating from a previous furnace release.
    51
    It's a legitimate question, I'm not asking for "useless" stuff, alot of governors have more than just a few options, that's why people prefer to use 3rd party kernels, I mean this kernel has the exact same options as a stock kernel, I'm asking from a performance standpoint, the maintainer could easily add more governors and schedulers, alot of them can easily pass his "testing".

    I totally get where you're coming from, I really do. In fact not even a year ago I was pumping out kernels every week on the G2, with my only focus being a fat changelog and a massive defconfig (defconfig is where you enable or disable features before build). If there's anything I learned about kernel development and coding during my time spent being *that* kind of developer, it's this: Nothing.

    Yes, I literally learned nothing at that time. More interestingly, that was the biggest exposure I had been getting as a developer. Each update I posted raked me in 30+ thanks and that felt absolutely awesome. You know what would feel awesome-er? If I had actually learned something valuable instead of sitting there being a thanks-whore. When you focus on enabling *all* the settings, and adding *all* the drivers, and making the *biggest* changelogs, you trade experience for limelight. People begin to think you're a genius for all the big fancy words in your changelog and praise your talent when you announce that you were able to copy and paste a file into your kernel source tree and flip a switch, but in reality - you learn nothing about developing. You run into problems you can't fix and requests you can't fulfill, and questions you just can't answer.

    My biggest recent project was KCAL: http://forum.xda-developers.com/android/software-hacking/dev-kcal-advanced-color-control-t3032080

    KCAL took a collective 3+ months and hundreds of hours of work reversing and debugging highly vague (or nonexistent) documentation to develop. Had I stuck to being a changelog-whore, I wouldn't have even considered taking on KCAL. I'd still be waiting for some other dude to make it so I could cherry-pick and rake in the thanks.

    Here's how many lines that made it into the final release of KCAL for both mdp5 and mdp3: 928
    Here's how many lines it takes to enable a governor: 1

    Yes, just one line to enable a governor, and there's absolutely zero development involved, no thought process, and no debugging. I'm not afraid to admit that 90% of the kernels on XDA all follow the 1-liner design. I'll admit that it's way easier than developing something like KCAL, and I used to be that kind of dev, and the reward was much much greater. People donate to you, buy your app, view your thread, and you get popular.

    I'm pretty happy with my setup right now, actually. If I trade popularity and thread views/thanks for experience, then I pick up the ability to do what I want with my phone when I want, how I want. If there's an issue with the kernel, or a feature I want in the kernel, I can go at it 100% of the time. If I stick to being a 1-liner dev, then I have to wait for someone else to fix the issue for me, or create the feature, because I'd be spending all day flipping switches or adding compiler flags instead of learning something useful. So if this kernel lacks in features a little bit, it's because I'm busy learning and growing so that I can do great things later down the road, rather than continue doing the same things forever.

    Sorry this went a little off the rails in regards to you, but I felt I needed to get that out and it's pretty relevant to how a lot of people view my design philosophy.
    16
    Just posted 20150228 builds, re-synced changes from CM and *finally* released my KCAL driver, also reverted the furnace bootmode for now - KCAL app replaces.

    KCAL is advanced color control for all of the latest Qualcomm chipsets, it's been supported by other popular kernels and even integrated into CF.lumen by @Chainfire

    View my full write-up and release notes here: http://forum.xda-developers.com/android/software-hacking/dev-kcal-advanced-color-control-t3032080 - This thread also contains a link to my Color Control app so you can configure the display yourself.

    Check out some configurations provided by @wrinklefree here: http://forum.xda-developers.com/showpost.php?p=59092146&postcount=3017
    Configurations by @vomer here: http://forum.xda-developers.com/showpost.php?p=59009298&postcount=4268
    AMOLED-ey configuration by @abhi08638 here: http://forum.xda-developers.com/showpost.php?p=58907635&postcount=10776
    14
    20150123 builds are available now, added kexec-hardboot support (thanks @Skin1980) and the latest changes from CM. Seperate builds for d855 16G/32G versions.
    13
    Don't want anyone to think I've abandoned ship here, just been working on some display calibration/control features. Here's a video demonstration:


    Post processing types are:
    RGB with PGC (Gamma correction)
    Invert Display with IGC (Individual gamma curves)
    Saturation/Grayscale with PA (Picture adjustment)