[KERNEL][GPL][N4] franco.Kernel - r217

Search This thread

omer7

Senior Member
Sep 20, 2012
1,040
232
I think Franco only uses interactive and performance governors. Don't quote me on it, but I think this is because interactive is hands down the best and most optimized for this kernel. Hopefully someone can chime in and clarify this.

Thanks for the reply.


But Interactive and performance governors r of CPU, i m talking abt GPU governors.

Sent from my Nexus 4 using Tapatalk
 

hardwareadictos

Senior Member
Jun 15, 2013
1,279
423
i dont think you need per app mode for this kind of app. per app mode specifically for heavy games.

It really helps with apps that dont need full power of S4 Pro, for example i use a profile for chat apps like telegram or whattsapp with maxium of 1Ghz and min of 384 for cpu and max of 128mhz for GPU, as i am chatting all day i can tell you the diference is noticeable, more cooler system and a decrease of battery

Enviado desde mi Nexus 4 mediante Tapatalk
 
  • Like
Reactions: m_harsh and kol1124

droid_legacy

Senior Member
Feb 16, 2012
267
113
Trier
It really helps with apps that dont need full power of S4 Pro, for example i use a profile for chat apps like telegram or whattsapp with maxium of 1Ghz and min of 384 for cpu and max of 128mhz for GPU, as i am chatting all day i can tell you the diference is noticeable, more cooler system and a decrease of battery

Enviado desde mi Nexus 4 mediante Tapatalk

If I remeber right (and I think I do), there is no possibility to set `max cpu speed`. Just Minimal CPU Speed and inpoot boost frequency.
Correct me if I am wrong. :D

This would be usefull for texting appsor something common, but if you only have min cpu frequency it think it is more usefull for games.

Of course you can set a low input boost frequency lox max gpu frequency and a high hotplug load to save some power. But governor will go to the speed it needs. So not queit sure about how much this will save in the end. :)


Nexus 4. R204
 

hardwareadictos

Senior Member
Jun 15, 2013
1,279
423
If I remeber right (and I think I do), there is no possibility to set `max cpu speed`. Just Minimal CPU Speed and inpoot boost frequency.
Correct me if I am wrong. :D

This would be usefull for texting appsor something common, but if you only have min cpu frequency it think it is more usefull for games.

Of course you can set a low input boost frequency lox max gpu frequency and a high hotplug load to save some power. But governor will go to the speed it needs. So not queit sure about how much this will save in the end. :)


Nexus 4. R204

It allows you to modify max freq.

Enviado desde mi Nexus 4 mediante Tapatalk
 

droid_legacy

Senior Member
Feb 16, 2012
267
113
Trier
But only global and not in per APP modes? Or do I miss something here.

Sent from my Nexus 4 using xda app-developers app
 

Attachments

  • uploadfromtaptalk1396179386870.jpg
    uploadfromtaptalk1396179386870.jpg
    34.4 KB · Views: 597

deedeeceleb

Senior Member
Oct 10, 2011
469
227
I'm able to change max CPU freq in per app modes... It's just above min CPU freq. Don't know why it isn't shown on your device. Perhaps update to latest fku

Gesendet von meinem Nexus 7 mit Tapatalk
 

droid_legacy

Senior Member
Feb 16, 2012
267
113
Trier
I'm able to change max CPU freq in per app modes... It's just above min CPU freq. Don't know why it isn't shown on your device. Perhaps update to latest fku

Gesendet von meinem Nexus 7 mit Tapatalk

I already am on latest FKU (11.4.1) and kernel Version .204. I own a Nexus 4. Which device do you got?

No possibility to scroll in this list or anything else. This is all I see! :D
 

deedeeceleb

Senior Member
Oct 10, 2011
469
227
N4 and n7 2013. Max CPU freq is available on both devices (r204 and r13). Will provide a screenshot from n4 in few minutes.

//e n4 screenshot:

nane5e4u.jpg


Gesendet von meinem Nexus 7 mit Tapatalk
 
Last edited:

maxsum

Member
Sep 13, 2013
31
9
Canton(Guangzhou)
maxsum.me
Sometimes I found min frequency very high with PerAppMode. But I don't customize min freq in PerAppMode. Is this a bug?

I am sure it is caused by PerAppMode. I have never had a perappmode profile that set min freq higher than 384. See the log from SuperSU, the min freq is set to input_boost_freq. @franciscofranco
 

Attachments

  • Screenshot_2014-03-31-00-00-47.jpg
    Screenshot_2014-03-31-00-00-47.jpg
    122.2 KB · Views: 613
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 2376
    Hi all.

    Current builds (starting with r217) are for Lollipop 5.1 only.
    Builds (starting with r214 up to r216) are Android 5.0 Lollipop only.
    KitKat is dead and the last stable release was r213, which you're free to use if you're still on 4.4.4.

    Download:
    boot image:
    http://kernels.franco-lnx.net/Nexus4/5.1/
    zips:
    http://kernels.franco-lnx.net/Nexus4/5.1/zips

    Installation:
    fastboot flash boot boot_name_img
    or
    flash the .zip in the recovery

    Source:
    https://github.com/franciscofranco/mako/tree/lollipop-mr1

    Changelog:
    http://kernels.franco-lnx.net/Nexus4/5.1/appfiles/changelog.xml

    franco.Kernel updater Free apk: http://forum.xda-developers.com/showthread.php?t=1867127

    Got any questions that you couldn't find after searching?
    FAQ: http://forum.xda-developers.com/showthread.php?t=2532422
    197
    Color Calibration for the Nexus 4

    Thanks for all those of you who provided feedback on my color calibration settings using r72 and Franco's app.

    Someone messaged me to ask what the thinking was behind my settings, and I thought it might be worth posting the reasons here too so everyone can understand the why behind them.

    Because this thread moves so quickly, here are the settings I'm using again, so you don't have to go searching for them:

    R 175
    G 175
    B 175

    Whites 20
    Mids 100
    Blacks 255
    Contrast 0
    Brightness 0
    Saturation 200
    Grays 0

    Screen Brightness 50%

    These settings provide a VERY close approximation to my calibrated PC monitor when studying my photos in detail (I'm a cinematographer and photographer by profession - see here: http://www.visceralpsyche.com).

    A lot of you love the settings, but some of you also say they are too dark, or wonder why you can't put a lower screen brightness and compensate by increasing the RGB values to let more light through.

    To understand why I chose my settings, you have to remember that our displays are made up of two parts - the backlight (screen brightness control in Android) and the LCD panel itself (adjusted by Franco's app), which the backlight shines through.

    What I found with my testing was that with RGB set to 255, specular highlights (and white edges in general) tended to blow out, causing color fringing artifacts. This is easily seen as pink or yellow edges to what should be pure white images. As I pulled back the RGB values, this fringing began to get smaller, until by my settings of 175 there was no longer any color fringing to my whites. Think of it as a form of highlight recovery. By pulling the clipped channels down equally, I found the point at which the values didn't overflow the hardware limitation of the LCD panel itself.

    Once this was done, I went into the gamma interface and began looking for where the whites and blacks ran close to the limit, but not over. I adjusted the screen brightness to where I could distinguish the bottom and top values as individual shades. THis was close enough to 50% that I set it to 50% and tweaked it to be perfect.

    Then I played with the Mid and Gray values until middle grey was indeed in the middle, so that the tone curve wasn't biased to one direction.

    From there, I adjusted saturation to match my PC monitor's saturation level.

    After all that, I arrived at the values I posted above, and now have a screen which faithfully replicates the tonality of my photos without any artifacts or strange tone curves.

    If you want to test these values (or your own) I recommend the following images. The calibration chart is one I found online a long time ago, which is useful for seeing the top and bottom end of white and black, to make sure your screen is showing you all the proper values:

    calibration-chart.gif


    The photo is my own, and is useful because I know exactly how I processed it and therefore that it touches both the white end of the spectrum (the highlighted side of her face, with values at precisely full white) and the black end of the spectrum (the fine detail in her hair, which is very black but not crushed in the details):

    IMG_1362a_framed_sRGB_25.jpg


    You can also use her facial tonality to make sure you see a smooth transition through the grays, not steps.

    It's also black and white, which means that any color fringing you see is entirely due to artifacts introduced by errors in the color or gamma settings and not the backlight of the screen).

    Both images are hosted on my own server, so there are no compression artifacts introduced by the forum.

    Again - my aim with these settings is to give you a proper, reference screen that displays accurate colors without any artifacts or errors. Brightness is set to match a proper reference display (120cd/m2) and may be brighter or darker than you prefer.

    If you value absolute battery savings over accurate color, then these settings may not be for you. That's perfectly ok of course. But for me, in my line of work, I value accuracy over the little bit of battery savings I might get by lowering my screen brightness, so if that's your goal too, then you'll find these colors are a good basis for having the best possible photo viewing screen on any phone.

    Because I can tell you, I have never had a more accurate screen than the Nexus 4 when it comes to looking at my photos, when combined with Franco's fantastic color interface and kernel.

    Hope this helps!

    Cheers,

    Paul Leeming
    Writer/Director/Cinematographer
    Visceral Psyche Films
    http://www.visceralpsyche.com
    162
    Really sad to read some posts after all the work I put on this device for longer than an year. Anyway here's r204 that I've been working on for a while...

    * Introduce a new bunch of tunables for my Hotplug driver and squash all code improvements from Hammerhead's version
    * Uses a power efficient system workqueue to allow the cores to stay longer times on idle
    * Several key subsystems are now using a newer and more advanced kernel thread infrastructure to allow cores to allow for better power savings
    * Improved thermal throttle code
    * Merged all upstream 3.4.y patches
    * Merged misc patches

    Have fun.
    157
    I couldn't resist. My girlfriend is a bit mad at me, but I told her I would buy her some nice drinks after dinner so while she's happy I managed to get the new Kernel sources, build fresh with the new ramdisk and I only had time to merge my custom changes:

    - Cleaned config from crap
    - Added my Hotplug driver (bye mpdecision)
    - Added my custom changes to the Thermal driver (bye thermald)
    - Added my custom changes to Interactive Governor (and made it default)

    And thats pretty much it. I don't have more time now, (we'll see tomorrow, I rented a hut in the beach for tomorrow for me to work a bit on the Kernel/App while getting some nice sun and my GF won't get mad eheh - Android, GF, drinks, sun and beach, who doesn't love this. I'll take a picture tomorrow and share with you all). Attached is r170 for 4.3 with the changes I mentioned above.

    Have fun guys.
    140
    Ok I have a small gift for all of you that run FK for almost a year on this device. I always said that I would never implement any of those functionalities to wake the device without pressing the power button - point is that LG G2 has brought this feature, Oppo N1 has something very similar and... I've been getting emails that users are having the Power Buttons wore off. Initially I implemented this on the new Nexus 7 as a challenge and to have some fun. Couple code lines later I had the functionality working fine and dandy. The device deep sleeps and the only thing that is being kept active is the digitizer for this to work. I sent it to a couple of people and they enjoyed it specially because it worked better than other Kernels that had implemented similar options. Good, so lets try and implement it on Mako. It's 100% my code, pretty simple, and easy to understand. Please refer to git (I just pushed the code) for how it works in the touch driver and input subsystem.

    By default this option is disabled, but you can enable it by doing:

    echo 1 > /sys/module/lge_touch_core/parameters/touch_to_wake

    After this is enabled you can power up the display by double tapping just like the LG G2, and you can swipe from whenever you want on the display and it will power up. There is a 100ms (0.1s) minimum interval where the algorithm will detect touch events so filter ghost touches and some unintended shít. It seems very low value, but when we're touching the screen the digitizer is capturing hundreds of touch events every minute, and dozens every second. So this works as a filter.

    If you're using touch_control and you want to test this, please disable the module and reboot your device or you'll most likely get into some **** problems. And the same thing other way around.

    Oh and interactive is back to default, it just gives me more consistence results all around.

    Attached goes two test zips, flash, enable the touch thingy, test, and report back.
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone