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

Search This thread
By:
Advanced…
Dan53

Dan53

Senior Member
Sep 14, 2010
454
181
London
Re: [KERNEL][GPL][N4] franco.Kernel - r90

ArRaY92 said:
Franco, could you inplement sanity checks for the UV values? I accidentally typed in 105 instead of 1050 for 1.5Ghz, and it immediatly rebooted. I know it is my fault, but since the CPU couldn't ever run at that voltage anyway, it should probably set everything to 500 min?

Or if you are giving users maximum freedom to try to get as low as possible, that is fine too. Then disregard this. Also, if you already have the checks in place.
Click to expand...
Click to collapse

I don't think he cares for UV enough. You get no support for UV'ing which is probably why he didn't spend too much time on it.

Sent from my Nexus 4 using xda app-developers app
 
G

gotjazz

Senior Member
Apr 10, 2011
464
36
AW: [KERNEL][GPL][N4] franco.Kernel - r90

Hrm I'm getting anxious. Hope my favourite Rom is being updated soon so I can try the recent kernels....

Sent from my Nexus 4 using xda premium
 
-JFK-

-JFK-

Senior Member
Jul 24, 2010
1,324
501
42
Nantes
www.activeaudio.fr
Xiaomi Mi 11
Xiaomi Mi 11 Ultra
Benchmark question

Hi all,

I know that benchmark are less important than the feeling but I have a question.
I have just flash Xylon ROM (Full wipe) then do some Antutu tests :

Stock Kernel : 23000
Franco Kernel : 21000
Faux (@ 1.8GHz) : 12000

How can we explaine that a stock kernel give better score than an enchanced one with stock frequency (Franco) and much more better than an overclocked one (Faux) ???

Thank's for your help.
 
M

manjee

Senior Member
Dec 10, 2010
330
82
Lyon
OnePlus 7
Re: [KERNEL][GPL][N4] franco.Kernel - r90

Luigiesin said:
Uve got it.. Doing it right now

Sent from my Rock & Roll Nexus 4 \m/
ROM: PA 3.0 (Feb15)
Kernel: Franco r90
T-Mobile

---------- Post added at 11:31 PM ---------- Previous post was at 11:23 PM ----------



Was just able to uninstall the update.. Won't let me uninstall the whole app..
Also because of that my colors are all screwed up... So is definitely an issue with binary..
Checking on the play store, some users are reporting problems updating binary

Sent from my Rock & Roll Nexus 4 \m/
ROM: PA 3.0 (Feb15)
Kernel: Franco r90
T-Mobile

---------- Post added at 11:39 PM ---------- Previous post was at 11:31 PM ----------

Just installed the pro version and same thing.. Now it doesn't show any apps in the list and won't let me update binary..

Sent from my Rock & Roll Nexus 4 \m/
ROM: PA 3.0 (Feb15)
Kernel: Franco r90
T-Mobile

---------- Post added at 11:50 PM ---------- Previous post was at 11:39 PM ----------

Restoring nandroid... Wasn't able to fix it..... Let me know if you any ideas..

Sent from my Nexus 7 using tapatalk pro
ROM: MINCO v6.2.1 N7
Kernel: Franco r46
T-Mobile USA
Click to expand...
Click to collapse

Same thing happened to me with r85. I tried all things possible to solve the problem. Only thing that worked is dirty flashing my whole ROM again (without wiping data). BTW I'm on slim bean 4.2.1... Don't know if it matters but I use 4.2.2 kernel with no (other) issue.

HTH

Sent from my Nexus 4 using xda app-developers app
 
italia0101

italia0101

Senior Member
Nov 9, 2008
3,803
1,358
Re: [KERNEL][GPL][N4] franco.Kernel - r90

-JFK- said:
Hi all,

I know that benchmark are less important than the feeling but I have a question.
I have just flash Xylon ROM (Full wipe) then do some Antutu tests :

Stock Kernel : 23000
Franco Kernel : 21000
Faux (@ 1.8GHz) : 12000

How can we explaine that a stock kernel give better score than an enchanced one with stock frequency (Franco) and much more better than an overclocked one (Faux) ???

Thank's for your help.
Click to expand...
Click to collapse


Faxus scores low because he has his own implentation of hot plugging and ramping ... His kernel doesn't get tricked by high long loads like benches ... So it auto down clocks

So his kernel is still smooth butndossnt do well in benches

Sent from my Nexus



Sent from my Nexus 4 using Tapatalk 2
 
Last edited:
Bluewall

Bluewall

Senior Member
Apr 7, 2010
2,191
863
Sion
fr.miui.ch
-JFK- said:
Hi all,

I know that benchmark are less important than the feeling but I have a question.
I have just flash Xylon ROM (Full wipe) then do some Antutu tests :

Stock Kernel : 23000
Franco Kernel : 21000
Faux (@ 1.8GHz) : 12000

How can we explaine that a stock kernel give better score than an enchanced one with stock frequency (Franco) and much more better than an overclocked one (Faux) ???

Thank's for your help.
Click to expand...
Click to collapse

Because Faux doesn't get fooled by benchmark app and don't push all the power when you run the app :)

For Franco VS Stock the difference is minimal and it changes everytime you run the benchmark.

PS : Don't give more than 0 **** about benchmark (protip)
 
Vangelis13

Vangelis13

Senior Member
Feb 11, 2011
8,331
9,606
300 meters from the Rhein
Google Pixel 6 Pro
Re: [KERNEL][GPL][N4] franco.Kernel - r90

Vangelis13 said:
Follow this guide, A to Z. Turn it into a very educational experience! :)

http://xdaforums.com/showthread.php?t=2010312
Click to expand...
Click to collapse





DesertVelo said:
Vangelis - It is very refreshing to see people helping each other out instead of being flamed, even though the question was not related to Franco's kernel. Yes, we try to keep everything OT but you took the time to help out. Great people in this thread!
Click to expand...
Click to collapse

Any new user learning to use erfrant's guide and not a toolkit is a victory for all of us. (Re - linked it again, for reference..) ;)

As for the oot; not everything is the same. And anyway, a quick reply with an answer or referral is a million times better than a "search - read - flame" chain reaction.

End of oot. ;)
 
Last edited:
  • Like
Reactions: DV1510
i860

i860

Senior Member
Jan 24, 2013
494
212
Flash r90 ( not the test one ) and after reboot if i don't keep the screen on the phone will turn off and i had to hard reset.This happens after each reboot.
 

Attachments

  • last_kmsg.txt
    62.1 KB · Views: 11
alcurtis93

alcurtis93

Senior Member
Oct 31, 2010
1,271
181
Re: [KERNEL][GPL][N4] franco.Kernel - r90

i860 said:
Flash r90 ( not the test one ) and after reboot if i don't keep the screen on the phone will turn off and i had to hard reset.This happens after each reboot.
Click to expand...
Click to collapse

Looks like it was a kernel panic but no errors were detected

Sent from my Nexus 4 using Tapatalk 2
 
meangreenie

meangreenie

Senior Member
Mar 6, 2012
2,584
732
Bluewall said:
Because Faux doesn't get fooled by benchmark app and don't push all the power when you run the app :)

For Franco VS Stock the difference is minimal and it changes everytime you run the benchmark.

PS : Don't give more than 0 **** about benchmark (protip)
Click to expand...
Click to collapse

Do you actually beleive that?

you think faux's kernel sees antutu running and throttles down ?

pro tip, it's running all apps like that.
 
  • Like
Reactions: yokuyuki and -JFK-
J

jtroye32

Senior Member
Sep 24, 2009
267
32
Re: [KERNEL][GPL][N4] franco.Kernel - r90

R90 fixed the jittery ui problem I was experiencing on the last couple builds.. Must of been due to those GPU patches.

Sent from my Nexus 4 using xda premium
 
tyraelasd

tyraelasd

Senior Member
Nov 28, 2010
1,445
473
Concepcion
Re: [KERNEL][GPL][N4] franco.Kernel - r90

Hey @franco, why can't we set our own custom gamma values? I mean, you can't use the exact value that you want, there's only a set of values available.

Cheers

Sent from my Nexus 4 using Tapatalk 2
 
Z

zephiK

Inactive Recognized Developer
Aug 23, 2009
21,655
37,705
New York, NY
Re: [KERNEL][GPL][N4] franco.Kernel - r90

tyraelasd said:
Hey @franco, why can't we set our own custom gamma values? I mean, you can't use the exact value that you want, there's only a set of values available.

Cheers

Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse

Huh it's in his app under color control.

Sent from my Nexus 4 using xda premium
 
obsanity

obsanity

Senior Member
Jun 4, 2010
2,035
517
Re: [KERNEL][GPL][N4] franco.Kernel - r90

tyraelasd said:
Hey @franco, why can't we set our own custom gamma values? I mean, you can't use the exact value that you want, there's only a set of values available.

Cheers

Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse

Other values are invalid. Only valid values are allowed. Its been documented in revision history and on this forum about a million times.

Sent from my Nexus 4
 
  • Like
Reactions: drawde40599, yokuyuki, murdah204 and 2 others
A

ArRaY92

Senior Member
Jul 15, 2011
100
14
trailblazerz11 said:
Minimum is 750 still I think. Which would still cause 1512 to reboot.

Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse

It seemed to have accepted my 725 for 384mhz..

Also, 1512 seems to run fine on 975mV for me on performance governor, if I switch back to interactive after testing it immediatly hangs and resets my phone, so I have to reinstall franco kernel.

Why does it work on performance, but not on interactive?
 
You must log in or register to reply here.

Similar threads

faux123
[Kernel] (ver 041) Mako KK 4.4 (UV/OTG/CPU/GPU OC/Hybrid Linux 3.4+) [08-02-14]
Replies
17K
Views
3M
B
bubbleguuum
C
[ROM][Official][4.2.2] CyanogenMod 10.1 Nightlies for the Nexus 4 (mako)
Replies
14K
Views
3M
VinceCZ
VinceCZ
stratosk
[KERNEL] Semaphore N4 3.4.2
Replies
9K
Views
1M
stratosk
stratosk
DariosF
  • Locked
[ROM][GPL] [KK 4.4.4] ♦ PURITY ROM ♦ (Mako) 15/10
Replies
12K
Views
2M
Woody
Woody
CallMeAldy
  • Poll
[KERNEL] [N4] [6.0][3.4.0][AOSP/CM] [10/26] [M2] - AK
Replies
10K
Views
1M
RASTAVIPER
RASTAVIPER

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 2376
    franciscofranco
    franciscofranco
    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://xdaforums.com/showthread.php?t=1867127

    Got any questions that you couldn't find after searching?
    FAQ: http://xdaforums.com/showthread.php?t=2532422
    View
    197
    visceralpsyche
    visceralpsyche
    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
    View
    162
    franciscofranco
    franciscofranco
    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.
    View
    157
    franciscofranco
    franciscofranco
    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.
    View
    140
    franciscofranco
    franciscofranco
    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.
    View

New posts