yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] franciscofranco:
Onlining and offlining a cpu core is expensive and hurts. Two cpus always online will save you from UI interaction lags, save performance hit due to the onlining/offlining process, will save you batter because the load will be better distributed in two cores instead of relying on just one that would be probably hitting max freq more often. Two cores online won't make your device hotter than before. More 3ºC or less 3ºC is meaningless specially if its either 33ºC, 36ºC or 39ºC. Do you know your body temperature? Its around 36,5ºC. Think about it.

I'm a bit tired of explaining the same thing every now and then :/
[Nexus 4 Original Android Development] rmead01:
since you hate explaining this stuff, could a short post in OP or post after that saying this exact stuff be edited? Then when you get the questions either yourself or even others can just link to the post. Might save some headaches :highfive:
[Nexus 4 Original Android Development] 3mmar3d:
hi sir

which image should i choose ??
[Nexus 4 Original Android Development] ShinnAsuka:
M3 is the latest.
[Nexus 4 Original Android Development] franciscofranco:
I like to explain, its just easier if users search a bit ;) Nobody cares about the OP anyway :)
[Nexus 4 Original Android Development] 3mmar3d:
thanx

should make a backup before flash ???

sorry bad English
[Nexus 4 Original Android Development] ShinnAsuka:
General rule of thumb, always backup before flashing anything.
[Nexus 4 Original Android Development] rmead01:
LOL heard that, wish I didn't hear that, amirite?

No problem educating the users, i'm an advocate of educating, but it was just a thought to direct people to where the answers already are to save you some time and let you focus on where the real magic happens in the code. Us, your minions, could link to your education for you :p
[Nexus 4 Original Android Development] 3mmar3d:
finally did't

all app still with no changes

but why the phone colors changed ??

its normal ??
[Nexus 4 Original Android Development] ShinnAsuka:
Not quite sure what you mean? Can you upload a screenshot of your problem?
[Nexus 4 Original Android Development] rockafellor:
I dirty flashed my brothers nexus 4 several times and I experience a lot of app crashes like in minion rush. Using Franco m3 kernel. Can a clean flash help? Also app drawer is loading very slow or sometimes doesn't show any apps

Sent from my paranoid francofied Nexus 4
[Nexus 4 Original Android Development] franciscofranco:
That rom is fúcked.
[Nexus 4 Original Android Development] trillo69:
Actually, I just care about OP, it's clean and clear, and changelogs are (almost) all we need to know. OP is always understimated. :)
[Nexus 4 Original Android Development] rockafellor:
Which Rom do you use if custom?

Haha

Sent from my paranoid francofied Nexus 4
[Nexus 4 Original Android Development] franciscofranco:
Stock.
[Nexus 4 Original Android Development] 3mmar3d:
sorry now colors OK

is there any settings for good battery life ???

---------- Post added at 05:04 PM ---------- Previous post was at 05:00 PM ----------

thanx franco

what the deference between free and paid app (Franco Kernel) ??
[Nexus 4 Original Android Development] franciscofranco:
Too many, read the apps description.
[Nexus 4 Original Android Development] ShinnAsuka:
Try the beastly battery power profile of you have the FKU app paid version
[Nexus 4 Original Android Development] kioshi:
r163 fixed it Franco. No high Android OS & Android Systems for me either, thank you sir!
[Nexus 4 Original Android Development] thebryceee:
More fluid

I'd imagine that per-app modes wouldn't work if you greenified it since you're forcing it to hibernate instead of letting it make it's checks

The free app just lets you update the kernel version. The paid app lets you control everything but the kitchen sink. Maybe even control your kitchen sink :/
[Nexus 4 Original Android Development] rmead01:
There is no reason to greenfy franco kernel. The app may be in the background but you will never see it causing a wakelock.
[Nexus 4 Original Android Development] Pure Drive GT:
of **** my life.. got lazy and just pushed the update button on cm updater... few seconds later o found out why I never do it... kernel gone... all ****ty sys apps back... -.- btw i noticed that while charging phone goes to sleep once reching 90% just mentioning it ;)

update: while i'm already at it i tought ill give cm kernel a try and monitor it. what i can say is: it is bloody fast but kind of random at times. most of the time 2 cores just sit at 1ghz and only goes to 1 core when no interactions. it randomly jumps to max freq now and then and also very fast when load gets a bit higher. i can truly feel how it gets hot and hotter. what i can say is that it goes crazy on any hint of an incoming load thus seeming super crazy insane smoothz but totally overkilling the task its supposed to do. i can imagine franco's code being so much simpler and more efficient. so i probably am not going to stay much longer on this kernel to test battery life :)

does anybody know in what ways cm kernel differs from stock?

Gesendet von meinem Nexus 4
[Nexus 4 Original Android Development] limeaide:
Wouldnt that be better asked in the CM thread?
[Nexus 4 Original Android Development] Redneck Trash:
You'll get flamed hard in the CM thread for mentioning a different kernel.
[Nexus 4 Original Android Development] thebryceee:
I know. But someone was suggesting to Greenify it and I'm saying that's a bad idea.
[Nexus 4 Original Android Development] aventu:
franco.Kernel-nightly-Mod

New build, based on r163:

previous changes:

- based on r162

new old hotplug driver:

- full scaling from 1 to 4 cores with individual thresholds

- 2 cores touchboost which stays for 3 seconds to prevent excessive hotplugging

- more interactive tunables

- a lot more, take a look

here

- ondemand touchboost, but interactive is strongly recommended (better battery)

hotplug thresholds:

cores; +2, +1, -1, -2

1; 80, 50, 0, 0

2; 90, 60, 20, 0

3; 100, 80, 30, 15

4; 100, 100, 50, 30

(100 and 0 = "don't care")

you can't change these values, let me know what you think about the values

new changes:

- r163 merge

- new load_history calculation implemented for mako_hotplug and simple gpu governor, big thx to andrey.tch

- fixed a possible bug which could cause lags after a day usage

benefits, I hope:

- no more lags with medium demanding games or apps, which need mostly 3 cores

- more battery because of 1 core and 3 core usage

recommended settings:

- row

- interactive: highspeed frequ 1512, touchboost 1026, dynamic_scaling true

https://github.com/reborn90/Franco
[Nexus 4 Original Android Development] limeaide:
Ill bite..

So its better to go to another kernel thread and ask about the differences there?

Im not debating this just asking wouldnt it be better to ask in the relevant thread?

If you are getting flamed for asking a legitimate question there is a cool thing on the top right of each of those posts and its called report post.

Ignore the trolls and report them.

**takes soapbox and exits**
[Nexus 4 Original Android Development] re4lsk:
what about making you own thread in android development gov'na?

Enviado desde mi Nexus 4 usando Tapatalk
[Nexus 4 Original Android Development] aventu:
These are only small and specific changes, which are not enough to open a new thread in my opinion. I just want to show a "different approach". I don't want to spam my custom builds in this thread. On the other hand, here is so much off topic, I just try to offer something productive.
[Nexus 4 Original Android Development] Demonic240:
Is it better on the battery to run interactive or on demand if you do a lot of waking the screen up to check for any notifications without unlocking? I read that interactive ramps the cpu up to max on screen on before slowly lowering it. I'm thinking that on demand wouldn't do it until there's a load that warrants it.
[Nexus 4 Original Android Development] franciscofranco:
CM Kernel is 99,99999999999999999999999999999999999999999999999999999999% stock!

Keep posting them here ;)
[Nexus 4 Original Android Development] leets4uc3:
Flashing right mrow :)

Sent from my Nexus 4
[Nexus 4 Original Android Development] franciscofranco:
Can you explain to me step by step your reasoning behind the code you made? Pros and cons. Why did you add that code to the trustzone policy? I already had a history programmed and its used since M3 or something. Thanks.
[Nexus 4 Original Android Development] gravitysandwich:
Give Franco some time, he promised he's gonna add it, because his girlfriend complained about the mic, and users asked a lot too. He needs time, and to remind himself to add it:)
[Nexus 4 Original Android Development] Pure Drive GT:
thanks for confirming that is exactly my feeling ^^

just one more question: all these security patches cm is adding. are they on kernel or rom level? if they were on kernel level and i'm using franco kernel instead, updating my rom would be an utter waste of time xD

Gesendet von meinem Nexus 4
[Nexus 4 Original Android Development] mitchdickson:
http://xdaforums.com/showthread.php?p=38290201

★ [ROM][4.2.2] CyanogenMod 10.1 ★ DISCUSSION,TALK, Q&A Thread

Sent from my iPad 4
[Nexus 4 Original Android Development] hughfollett:
Updating is never a waste of time :)

Inviato dal mio Nexus⁴ con Tapatalk⁴
[Nexus 4 Original Android Development] Arstoien:
I did experience lag today after a few hours of usage on 163. The CPU was not under load and I killed all apps but the lag was there. Went away with restart. It hasn't happened before.

Sent from my Nexus 4
[Nexus 4 Original Android Development] aventu:
andrey.tch came up with the idea of an algorithm with less calculation effort. Instead of adding all history values and dividing them by the history size, we can just kick out the old value of history[counter] and subtract it from full_load. Now we load the new idle_stat into history[counter] and add it to full_load.

The benefit is that we only have to change a little piece of the total history sum. I think this saves calculation steps which is important because the simple_governor function is called very often.

static unsigned int history[HISTORY_SIZE] = {0};
static unsigned int counter = 0;
static unsigned int full_load = 0; //sum of the complete history array

unsigned int total = 0;

full_load -= history[counter]; //subtracting old value
history[counter] = idle_stat; //loading new value to array

full_load += history[counter]; //adding new value to sum

if (unlikely(++counter >= HISTORY_SIZE))
counter = 0;

total = full_load / HISTORY_SIZE;
[Nexus 4 Original Android Development] franciscofranco:
Yes might save a few cycles. Doubt its that noticeable though. I'll test.

One thing that I have been thinking about is linking cpu0 to cpu2 and cpu1 to cpu3, theoretically though. Something like this (this is pseudo code for explaining):

if cpu0 load is greater than X counter0++

then if counter0 is >= X_threshold0 make cpu2 online

if cpu1 load is greater than X counter1++

then if counter1 is >= X_threshold1 make cpu3 online

cpu0 and cpu1 always online as they are at the moment

Although I'm very happy with the current simplicity I agree that in some cases its only needed to have 3 cores online and not 4.
[Nexus 4 Original Android Development] aventu:
likely() and unlikely() also save just a few steps in the cpu pipeline. The repetitions make the difference I think.

I'm not sure how the upcoming tasks are distributed between the cores. Maybe there are not equal enough. But I don't know exactly how the load calculation work. I also try to make the 2 core state very long and it should only drop to 1 core if the load is really low.
[Nexus 4 Original Android Development] franciscofranco:
Yes, in that scenario it helps a bit because that code path is called a gazillion times, very fast.
[Nexus 4 Original Android Development] Hypoxic1:
RE: Per-app settings

(just a thought) Would it be prudent to have FKU not only check every 10 seconds, but also look for that possible broadcast that it launched? Is this possible and/or would this affect battery? This was mentioned a few days ago. I understood it that not all apps tell the UI that "I've launched," but couldn't it still have the double check?

RE: SITREP

Absolutely no problems/issues here on r163 & FKU beta. I have had ZERO issues... EVER! I'm also on the stock ROM, with loads of mods (LTE, no soft buttons, LMT Launcher to name a few), yet never had even ONE issue with this kernel since I first used it around the time M1 released.

I have loads of battery-sucking widgets like Currents, Beautiful Widgets, Tune In, Play Music, Google Keep & everything is syncing, etc. Games run great, Dish Anywhere streams well, Tune In Pro functions properly with screen off, and all other apps function as designed. I get a good 1.5 days out of my phone USING IT. I end up with at least 4 hours SOT, as well. Oh! Forgot to add that I'm using Next Launcher 3D. It runs very smooth with all the transitions & visual goodies.

Running 1026Mhz, 50% hotplug, 128Mhz GPU as default per-app & 702Mhz touch input boost, 594Mhz screen off. I have implemented many per-app settings for load-intensive apps. I NEVER UNDERVOLT!
[Nexus 4 Original Android Development] i860:
Hi Franco

Just flash 163 and went for my run ( same track, same carrier, same asylum cm10.01, same settings on fk like for m3, r161 and 162 ) no problems with the cut off on tunein radio and no gps signal lost on endomondo. Also battery drop only 10% comparing to 13-14% on m3 ( battery is a little to early ).
[Nexus 4 Original Android Development] Pure Drive GT:
just to inform cm users. all the security patches made by cm are included in the kernel so if you use franco kernel, updating their stable release makes no sense whatsoever because there are no changes on rom level.

Gesendet von meinem Nexus 4
[Nexus 4 Original Android Development] vaibkulk:
Delete
[Nexus 4 Original Android Development] dapsANDpoundz:
Flashing r163 using Auto Flash through the FK beta app caused a boot loop for me. Used a program to flash the stock kernel and then I manually downloaded+flashed the r163 zip through CWM recovery and everything's good now. Dunno why it did that. I was coming from M3, stock ROM stock FKU settings.
[Nexus 4 Original Android Development] Karlo666:
Oh snap i updated.Thanks for info BTW.
[Nexus 4 Original Android Development] franciscofranco:
That shouldn't matter. I don't agree on offlining cpu1, theres really no need for that.

No apps broadcast their intent state to the system, I can't catch it. I tried it for a while it just doesn't do a system broadcast so I can't catch it.

r163 is already patched with the fix for the leak.
[Nexus 4 Original Android Development] Testraindrop:
You sure about that?

There are absolutely no Security fixes in the mako kernel lately:

http://review.cyanogenmod.org/#/q/status:merged+project:CyanogenMod/android_device_lge_mako,n,z

Also the two issues fixed lately were related to app signing, what has a Kernel to do with it?
[Nexus 4 Original Android Development] Pure Drive GT:
thracemerin answered to this:

---Quote (Originally by Pure Drive GT)---

how does the cm kernel differ from stock kernel?

Gesendet von meinem Nexus 4

---End Quote---

"It doesn't except for security fixes."

he did not specify which fixes. so the apk signing may not be in the kernel.

Gesendet von meinem Nexus 4
[Nexus 4 Original Android Development] Hypoxic1:
Hey I forgot to mention that I never clear the app data, too! And I still have never had an issue!

If Franco made a Kernel for Flight Management Systems (FMS), the FMS would find a shorter route & save $$$ thousands on fuel! LOL!

This is ONE AMAZING KERNEL!

​
[Nexus 4 Original Android Development] franciscofranco:
I think this is completely flawed now that I sit down and read the code throughly. The variable full_load will always be a value equivalent of one sample because theres nowhere in your code that iterates the history array to get all average of it.
[Nexus 4 Original Android Development] fioda:
Think that there is a problem with the MD5 check and the apps flashes a corrupted kernel image... It happens to me also...
[Nexus 4 Original Android Development] franciscofranco:
This is the commit for the security fix: https://github.com/franciscofranco/mako/commit/b31dd200464b844159adaf70171c6d606754a0cc

They didn't commit it to Mako for some reason.
[Nexus 4 Original Android Development] Testraindrop:
I believe he meant some older fixes.

The recent one which lead to the CM Milestone updates are ROM level:

https://android.googlesource.com/platform/libcore/+/9edf43dfcc35c761d97eb9156ac4254152ddbc55

http://www.androidpolice.com/2013/0...er-key-goes-public-already-patched-by-google/

Sorry Franco for CM spam in your thread,just want to avoid people to believe your Kernel would be unsafer than CMs...
[Nexus 4 Original Android Development] Pure Drive GT:
thanks for clearing that up!

Gesendet von meinem Nexus 4
[Nexus 4 Original Android Development] aventu:
unsigned int total = 0;

full_load = full_load - history[counter]; //we want to iterate over the array to get a sum, but we only have to change one value (the oldest one)
history[counter] = idle_stat; //loading new value to array

full_load = full_load + history[counter]; //add the new value to the complete iteration, stored in full_load

if (unlikely(++counter >= HISTORY_SIZE))
counter = 0;

total = full_load / HISTORY_SIZE;

full_load is not a single sample, it stores the complete array. Maybe you missed the very tiny minus "-="

for example:

#define HISTORY_SIZE 5
history[HISTORY_SIZE] = {1,2,3,4,5};
full_load = 15; // sum of array
counter = 0;
idle_stat = 6;

------------

full_load = full_load - history[counter]; // full_load = 15 - 1

history[counter] = idle_stat; // history[0] = 6

full_load = full_load + history[counter]; // full_load = 14 + 6

total = full_load / HISTORY_SIZE; // total = 20 / 5

the old average was {1,2,3,4,5} -> full_load = 15 -> 15 / 5 = 3

the new one is {6,2,3,4,5} -> full_load = 20 -> 20 / 5 = 4

The trick is to iterate only the part we need and recalculate the refreshed total sum, because we already have the rest.
[Nexus 4 Original Android Development] sNoxious:
So that means that it doesn't matter if your Rom is patched with this fix or not cos it's for Kernels?

Sent from my Nexus 4
[Nexus 4 Original Android Development] RandomDude:
I use this in /data/local.prop:

persist.hwc.mdpcomp.enable=false

debug.mdpcomp.maxlayer=3

I think it helps. Picked those settings up from a previous 'flickering' bug
[Nexus 4 Original Android Development] C4SCA:
what are the stock settings for M3?
[Nexus 4 Original Android Development] realfelix:
Clear app data and you will know.
[Nexus 4 Original Android Development] C4SCA:
i dont have the app.. im stock unrooted for now but i wanna know if i flash this via fastboot it will help with the heat but at the same time dont underclock like some other kernels do by default.

can i get a awnser?
[Nexus 4 Original Android Development] re4lsk:
Nope it isn't under clocked, stock freq are 1512 and 384.

Enviado desde mi Nexus 4 usando Tapatalk
[Nexus 4 Original Android Development] nachordez:
Stock are no UC nor OC nor UV. Just tweaks about governor to make it less battery demanding and well balanced. You can use it as it comes, no problem.

But I would recommend you to use the app. You can adjust it to your taste, and set colors and gamma much nicer than original ones. It really is worth every penny.

And this kernel is just GREAT!

Nexus4 / Carbon / Franco / V4A

GT-P5110 / Carbon / Dohllmen / V4A
[Nexus 4 Original Android Development] occtec:
Hey guys, this might be a noob question :o but where is the download link for this kernel? There is allot to read through here so I thought I would ask the question as it does not appear in first post.

Thanks in advance ;)
[Nexus 4 Original Android Development] jimbohurt:
But but.. it is in the first post. Under download :)
[Nexus 4 Original Android Development] zephiK:
Front page.
[Nexus 4 Original Android Development] gharrrrrr:
LOL. On one of the least bloated, most basic "here it is" OPs around.

Sent from my Nexus 4 using a waffle iron.
[Nexus 4 Original Android Development] Raijin:
Is there any difference between Franco app color interface and Nexus 4 Display Control app?
[Nexus 4 Original Android Development] 3dupunk:
I'm pretty sure their the same.
[Nexus 4 Original Android Development] occtec:
Funny hey guys? Not really! For some strange reason I see the download section but no download button :banghead: I'm using the XDA premium app :confused: looks like I may have to use my PC instead.

---------- Post added at 10:40 AM ---------- Previous post was at 10:33 AM ----------

Read my above post banana!

---------- Post added at 10:40 AM ---------- Previous post was at 10:40 AM ----------

Read my above post banana!

---------- Post added at 10:41 AM ---------- Previous post was at 10:40 AM ----------

Read my above post banana!

---------- Post added at 10:41 AM ---------- Previous post was at 10:41 AM ----------

Read my above post banana!
[Nexus 4 Original Android Development] dapsANDpoundz:
OR, you could, you know, install the app? You did say its a noob question so sorry. But installing the app will make things a lot easier for flashing this kernel.
[Nexus 4 Original Android Development] occtec:
Which app is that?
[Nexus 4 Original Android Development] szucsgf:
https://play.google.com/store/apps/details?id=com.franco.kernel.free

That's the free app that downloads the kernel. The paid app lets you configure the kernel.
[Nexus 4 Original Android Development] occtec:
Does the paid version of Franco kernel updater include fauxsound/fauxdisplay within the app or do these need to be purchased separately??
[Nexus 4 Original Android Development] gharrrrrr:
This is too good.

Sent from my Nexus 4 using a waffle iron.
[Nexus 4 Original Android Development] Redneck Trash:
Faux's apps sold separately.
[Nexus 4 Original Android Development] gravitysandwich:
Someone clear this up for him.... PLEASE....
[Nexus 4 Original Android Development] occtec:
Yes please, what I would like to know is if I purchase the paid version of the Franco kernel updater does this app include the ability to be able to tweak display colors and sound as per the faux display and sound apps?

Thanks for your patience
[Nexus 4 Original Android Development] Redneck Trash:
You'll be able to tweak the colors or use the preloaded user contributed color profiles. For now the sound options are headphone volume boost and gain.
[Nexus 4 Original Android Development] drawde40599:
Yes for color (Franco gamma) no for sound there are no sound tweaks on this kernel, there is ability to change headset volume and gain tho and those r controlled by app
[Nexus 4 Original Android Development] rwaempires:
You can adjust colors with fku app...but no sound tweak..
[Nexus 4 Original Android Development] drawde40599:
Franco has his own gamma color control completely different from faux. Faux apps wont work

---------- Post added at 08:33 PM ---------- Previous post was at 08:28 PM ----------

163 running beautiful BTW, just as perfect as 162 but better ;)
[Nexus 4 Original Android Development] Virus1x:
Love this kernel on stock software
[Nexus 4 Original Android Development] Hypoxic1:
Yes, this kernel on the stock ROM tears apart the competition! Stable... Efficient... Effective.
[Nexus 4 Original Android Development] occtec:
Thank you very much for all the above and the time taken to explain!! Much appreciated :)
[Nexus 4 Original Android Development] gravitysandwich:
Lol! Agreed.

Been using this kernel since the beginning

of December (like r30 or r40's I believe) and back then when I got 3 and a half hrs sot is way different than the 6 hrs sot I get now. God back then that motherfūckin msm_hsic_host is the only thing that made me root and flash this kernel, and now I have 0000000 regrets for doing it:)
[Nexus 4 Original Android Development] occtec:
Yes BUT this kernel with Aliendroid 3.0 is better yet again ;)
[Nexus 4 Original Android Development] gravitysandwich:
deleted