yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] thegtfusion:
The BOSS everywhere.

pS: franco, r382 is perfect, so I think its ready for M7 (on gnex) , and give us the ''weed'' beans you inserted on n4 also on gnex :D
[Nexus 4 Original Android Development] Reatret:
Comparing to a stock nexus, app launches and going back home are quicker on stock.
[Nexus 4 Original Android Development] CaspaTheGhost:
Yes sir, I'll go flash it now.

Loving the new icons, the app is looking fantastic with them. Its running great and I appreciate the release so we can enjoy the download changes!

:thumbup:

Sent from my BAKED N4
[Nexus 4 Original Android Development] bokagavrilov:
Deleted ;)
[Nexus 4 Original Android Development] Reatret:
Changing minimum made no difference.
[Nexus 4 Original Android Development] albundy2010:
No. Stock min is not 1026.
[Nexus 4 Original Android Development] mbucks911:
ya, but battery life is better and doesn't get as hot. performance has gotten closer to stock than it was in the beginning releases. some people will say that its better on this but they are usually just used to franco so just think its as fast as stock. the difference is not huge so it is easy to get used to.

also, if you want to speed it up more overclock it to 1700
[Nexus 4 Original Android Development] ciprianruse88:
I think he got confused due to mpdecision on stock kernel.most of the time in trickster it showes 1026 as stock min freq :)

Sent from Inferno
[Nexus 4 Original Android Development] Cuzz1369:
I was under the same impression.

Carbonized and francofied N4
[Nexus 4 Original Android Development] Eaffon:
r156 feels smoother than r155 to me... I'll see about battery life. Great job!:good:
[Nexus 4 Original Android Development] franciscofranco:
Yes due to improvements on how the system reacts to dirty pages and how it flushes them, how often etc. Check git.
[Nexus 4 Original Android Development] Krunk83:
I'm getting random touch issues when waking the device and touching the screen. Google now and the notification drop down sometimes pop up on first touch. After that it's fine.

Sent from my Nexus 4
[Nexus 4 Original Android Development] pnut22r:
+1
[Nexus 4 Original Android Development] zephiK:
Really liking the Franco Kernel app update. App is so polished and the icons on the menu makes it that much better :)
[Nexus 4 Original Android Development] germanj:
Had a hard reboot on r155, many apps reset their settings. Happened while texting. Dmesg ( http://db.tt/LONK14KZ). Lastkmsg (

http://db.tt/quRWvGyk).

Running 100mv under volt since forever, so I doubt that's a reason
[Nexus 4 Original Android Development] dapsANDpoundz:
Flawless victory with r156. The little lag when using the swipe with the Google keyboard is gone and scrolling is a bit smoother.
[Nexus 4 Original Android Development] bleuwave:
http://xdaforums.com/showthread.php?t=2309980

[KERNEL][WI-FI FIX]][ARP Offloading][Push Notifications][19 June][UPDATED]

You can try this if you want.

Sent from my Nexus 4
[Nexus 4 Original Android Development] franciscofranco:
I don't want to, sorry.
[Nexus 4 Original Android Development] lonoguge:
The only thing missing from the kernel is the color tweaks like that of matrix kernel. Is there a mod I could flash to fix this? other than that, this is the best ever!
[Nexus 4 Original Android Development] mitchdickson:
Seriously?

Sent from my iPad 4
[Nexus 4 Original Android Development] yoyoz808:
I noticed something strange with the fku app. After i updated the kernel to r156, when i tried to go back and check the changelog it will only show up to r155. I cleared app data and rebooted. Anyone else have this?
[Nexus 4 Original Android Development] franciscofranco:
Looks better and more functional:
[Nexus 4 Original Android Development] thracemerin:
The fact that he says there's a bug in 4.2.2 that requires you use the push notification fixer (4.2.2 works fine with push notifications on any other device) makes me think that whatever he did to the Prima driver is smoke and mirrors since the push notification fixer app fixes the entire problem for most people anyway. The stuff he has added (or at least the stuff he made public) is just bits and pieces from the CAF Prima repo, nothing original or special, and nothing that has been proven to fix anything.
[Nexus 4 Original Android Development] franciscofranco:
Yeah I've seen the commit on your repo. In the end its better that we just wait for professionals to do what they are paid for, Google and Qualcomm will fix it ;) Just sad that they are taking this long, the device is almost 1 year old at this point.
[Nexus 4 Original Android Development] bpdev:
Franco would you consider adding a heartbeat interval setting into your app, similar to push notification fixer, so we can fix this with your app?
[Nexus 4 Original Android Development] lonoguge:
Am I missing something?
[Nexus 4 Original Android Development] jarjar124:
What is the default high speed delay?
[Nexus 4 Original Android Development] ultrapirate:
Check the color control tab.
[Nexus 4 Original Android Development] lonoguge:
Ooohhhhh no I'm aware of the screen color tuner on the Franco app but they're inferior to the matrix tweaks.
[Nexus 4 Original Android Development] sspyed:
Oh hell no.
[Nexus 4 Original Android Development] PetritH:
App FC when I try to download the kernel, also it doesn't show the latest nightly.. anyone having issues or its just me?
[Nexus 4 Original Android Development] Cuzz1369:
Purchase the fku app from the play store

Edit saw your last post. In that case use the matrix kernel.

Carbonized and francofied N4

---------- Post added at 11:13 PM ---------- Previous post was at 11:10 PM ----------

Worked fine for me. 1 minute from time of pressing download my phone had booted up and r156 is on my phone.

Carbonized and francofied N4

---------- Post added at 11:14 PM ---------- Previous post was at 11:13 PM ----------

Worked fine for me. 1 minute from time of pressing download my phone had booted up and r156 is on my phone.

Carbonized and francofied N4

---------- Post added at 11:15 PM ---------- Previous post was at 11:14 PM ----------

Worked fine for me. 1 minute from time of pressing download my phone had booted up and r156 is on my phone.

Carbonized and francofied N4
[Nexus 4 Original Android Development] PetritH:
Worked well for me all the time, even in latest 10.0.5, i've reinstalled still same issue, had to flash the kernel from recovery... I saw people having this problem before but it wasn't mentioned for a long time... I updated the ROM and maybe that caused the issue who knows. Thanks anwyaz mate.
[Nexus 4 Original Android Development] Cuzz1369:
Worked fine for me. 1 minute from time of pressing download my phone had booted up and r156 is on my phone.

Carbonized and francofied N4
[Nexus 4 Original Android Development] bpdev:
I was on r154 and also did not see the latest nightly untill after updating to r155.
[Nexus 4 Original Android Development] mrgwap:
Lmao I'm dien laughing right now
[Nexus 4 Original Android Development] digitallysick:
Unable to fetch latest nightly app doesnt show any updates humm
[Nexus 4 Original Android Development] PetritH:
Kool, im not the only one, yaaay
[Nexus 4 Original Android Development] yethz:
Hey bro [MENTION=470754]Franco[/MENTION],

I know u just recently published #156, and M3 is coming near.

Downloading now and flashed this right away.

Just hoping M3 will be out this week, so I can grab that M3 before me and my family moves out to a new place to stay. No dsl coverage yet on that area and I dont have a data plan on my mobile. (Im going back to Ice Age era. LOL!!)

Anyways, I just want to have your M3 build before I take a leap on a new journey of life. :o

Gonna miss your future builds now. I wanna thank u for such a great developer and a person.

Keep it up bro. Take care...

• Sent from Nexus 4 via Tapatalk

• Rom: AXI0M (6/13) / Kernel: Franco #155
[Nexus 4 Original Android Development] blankit:
After an 11 hour road trip GPS would lose signal and reconnect a lot of times. Never did it with stock kernel.
[Nexus 4 Original Android Development] mbucks911:
Service area...? :confused:
[Nexus 4 Original Android Development] jphilippon:
Anyone wanna shed some light on what Mediaserver is? In the last 3 hours it's been wakelocked for 45 mins.

sent from my Mako
[Nexus 4 Original Android Development] blueren:
Franco Franco Franco!

Widgets for power modes planned?
[Nexus 4 Original Android Development] limeaide:
http://bit.ly/19395Pv
[Nexus 4 Original Android Development] thebryceee:
What?

I can't....
[Nexus 4 Original Android Development] Cuzz1369:
Bwahahaha. That was f-ing awesome man. I was gonna past a link to the same page. So glad I clicked on that.

Carbonized and francofied N4
[Nexus 4 Original Android Development] hoangtungst:
i think that the r142's performance is better than r156
[Nexus 4 Original Android Development] ciprianruse88:
TrollloLOL ;) . You gave me the best morning laugh :thumbup:

Sent from Inferno
[Nexus 4 Original Android Development] kara mustafa:
Did you make a clear Flash? When have you last time done a Flash with factory image flashing?

Wysłane z mojego Nexus 7 za pomocą Tapatalk 4
[Nexus 4 Original Android Development] Simer03:
Weird....unfortunately it works on other kernels :/ not sure what to do! I love this kernel!! Fack!!

Sent from my Google Nexus 4
[Nexus 4 Original Android Development] pa.pn2:
ok.9% left amazing batterylife

used 384 min/1026 max.this is great
[Nexus 4 Original Android Development] franciscofranco:
I didn't change anything that could affect that at all! Can you get me a logcat when the game is loading? Maybe I can see whats up.
[Nexus 4 Original Android Development] immunityx:
GTA vice city works fine for me
[Nexus 4 Original Android Development] Ranguvar:
It forces all cores to hispeed_freq or higher, definitely not what you want for general use.
[Nexus 4 Original Android Development] z3r0_x:
Franco, have you tested the 3G improvements by Harsh? They sound promising.
[Nexus 4 Original Android Development] franciscofranco:
If you mean this: https://github.com/franciscofranco/mako/commit/0433e98ea20e231e97d8c07d940bb1a5e7e264b7

I've been running that for 13 hours yes. And its an improvement from Codeaurora, not from Harsh.
[Nexus 4 Original Android Development] manjee:
This is the setting I settled on too. No trade off in smoothness, we'll see if it really impacts battery life in a couple days ¶:)
[Nexus 4 Original Android Development] ceejay83:
Do you have vice city? Works fine for me
[Nexus 4 Original Android Development] Vangelis13:
That just had r23 written all over it.. :D
[Nexus 4 Original Android Development] manjee:
I have the same config as you and photosphere works like a charm. ;)

---------- Post added at 10:33 PM ---------- Previous post was at 10:31 PM ----------

Franco's app !

You can also use RomToolbox
[Nexus 4 Original Android Development] Simer03:
FML...I'll see if I can get a log cat

Edit: figured it out! Nvm

Sent from my Google Nexus 4
[Nexus 4 Original Android Development] franciscofranco:
Yes, I thought r22 would a Milestone but I managed to do some changes on the hotplug driver and had to change some thermal throttle parameters plus a bugfix from codeaurora to prevent a kernel panic in certain circumstances using interactive. Check my git, I already committed the changes.
[Nexus 4 Original Android Development] scream4cheese:
I found my sweet spot in one try! Go hi speed load at 65 and hi speed freq at 594mhz. :)
[Nexus 4 Original Android Development] DowntownJeffBrown:
I've been using 486 since your first post I may bump it up bit I haven't seen much if any more battery drain.:thumbup:

Sent from my Nexus 4 using Xparent Blue Tapatalk 2
[Nexus 4 Original Android Development] Vangelis13:
Big thanks young man! Having a couple of days off I hope?

We should ban you from xda for the next 2 days. Hm.. :p
[Nexus 4 Original Android Development] franciscofranco:
Not sure, I really enjoy tweaking my devices, have tons of fun :)
[Nexus 4 Original Android Development] realfelix:
Any more lag when using ondemand?
[Nexus 4 Original Android Development] z3r0_x:
Amazing! Thanks for your hard work!
[Nexus 4 Original Android Development] alcurtis93:
Any thoughts about adding lulzactive v2. Was a very good governor in my gs2 days
[Nexus 4 Original Android Development] limeaide:
You should see his previous posts. Especially in the SGS4G forums. Those will make you laugh, go wtf, and get up and walk away. That was just in one post.
[Nexus 4 Original Android Development] Net.silb:
I'm not Franco but I can tell you yes.
[Nexus 4 Original Android Development] hoangtungst:
Yes , i did . I have tried to wipe all when i flashed r153,54,55,56 because the performance was too bad but the performance didn't improve so i reverted back to r142
[Nexus 4 Original Android Development] ambuj:
Is it normal or my battery has gone? On Franco M2.

Total minutes for voice call: 20 mins
[Nexus 4 Original Android Development] lordvj:
Since the touch boost routines are applicable to governors other than interactive, does the latest fix to the touch boost algorithm benefit them too?

---------- Post added at 01:04 PM ---------- Previous post was at 12:58 PM ----------

and also it would be great if you could move the input_boost_freq out of the interactive governor settings menu in the app?

---------- Post added at 01:06 PM ---------- Previous post was at 01:04 PM ----------

and also it would be great if you could move the input_boost_freq out of the interactive governor settings menu in the app?
[Nexus 4 Original Android Development] ragnarokx:
Are you trying to summon him like Beetlejuice?

Sent from my Nexus 4
[Nexus 4 Original Android Development] Raza Qadri:
:/ no i call longer than that
[Nexus 4 Original Android Development] jphilippon:
Ah yes, very insightful. Phones vary. With some, it may be linked to an app or a certain feature, etc. But thanks for playing.

sent from my Mako
[Nexus 4 Original Android Development] Cantacid:
2 hrs daily here. Lasts me a day(24hrs)

Sent from The Deathstar
[Nexus 4 Original Android Development] bilago:
Franco.. Any chance you will add the functionality to your kernel to change the mic gain?
[Nexus 4 Original Android Development] rmead01:
Has anyone else you the kernel restore feature in the fku app recently? I made a backup of r156 before trying another rom and when I restored it, the settings were still stock after the reboot. Went back to the rom I was on previously and tried the restore again, didn't change any of the settings. Could be an isolated incident though.
[Nexus 4 Original Android Development] aimcr7:
Afaik kernel restore only restore kernel img without the settings, so the settings will be default kernel value.
[Nexus 4 Original Android Development] combatdeity:
I think he's said he will work on that after M3.
[Nexus 4 Original Android Development] rmead01:
ahhh ok, that makes sense then. For some reason I thought it also backed up the settings. Seems all is working then.
[Nexus 4 Original Android Development] anshumandash:
I don't know of you found the answer. Yes the 700 limit it's the lowest allowed by the kernel. I don't think it is just limited to 384 step though.
[Nexus 4 Original Android Development] gravitysandwich:
It means you can only hit the -25 mV button 6 times, or UV every frequency by -150. He does this to lowers complaints about random reboots because someone thinks they can undervolt all they want.
[Nexus 4 Original Android Development] kerngehirn:
How can I attend beta testing again?

I read it somewhere but wasn't interested. Now that I'm interested, I can't find it.
[Nexus 4 Original Android Development] Cuzz1369:
G+ community. He posted a link a few pages back. Search his posts

Carbonized and francofied N4
[Nexus 4 Original Android Development] bpdev:
Here you go, However have to join his community:

https://play.google.com/apps/testing/com.franco.kernel
[Nexus 4 Original Android Development] kerngehirn:
Thanks

Guys. I'm always complaining about people who don't search. Anyway, I was searching and couldn't find it. Maybe "how beta" were the wrong keywords.
[Nexus 4 Original Android Development] hwies:
With #156 i recognized today the following situation: while several updates were running (via Play Store ) 2 cores ran at max. Doing things in parallel was hardly possible. Cores 3/4 came not up although the first 2 cores were heavily busy (i use cpu stats).

Gesendet von meinem Nexus 4 mit Tapatalk 2
[Nexus 4 Original Android Development] Net.silb:
Try lowering high load threshold until you're satisfied. Its value is 0-100, 0 = 4 cores online all the time, 100 = 2 cores online all the time. The higher the value the "harder" it is for all 4 cores to be online. 70 is default.
[Nexus 4 Original Android Development] rmead01:
This is what i've always been wondering. The 2 cores were running at max freq but didn't hit the 70% threshold to online more cores. So what would be less battery intensive, 2 cores running max freq or 4 cores running low to mid freq?
[Nexus 4 Original Android Development] franciscofranco:
That happens on all my devices, being stock or not. Few months ago I had to reflash everything from scratch and while it was restoring my apps from the Play Store the device was just unusable, and it was using stock rom and stock kernel. Thats just how it is. My GT-I9500 doesn't derp that hard though.
[Nexus 4 Original Android Development] Net.silb:
I think 4 cores low-med is better for battery than 2 cores at max frequency, if I remember correctly [MENTION=3292224]franciscofranco[/MENTION] said this himself once.
[Nexus 4 Original Android Development] rmead01:
Which is what I was leaning towards but I don't have any actual proof. Excuse my ignorance because i've done some programming but nothing compared to all this kernel stuff, but is there a way to base the hotplugging not just off the $ of core used, but how long it's staying at max freq? That way if something is using 2 cores at max freq but only 60% core usage, it would still kick on the other 2 cores to reduce the overall freq of all cores.
[Nexus 4 Original Android Development] Net.silb:
Maybe if all four cores were online it would be fine...

---------- Post added at 06:40 PM ---------- Previous post was at 06:39 PM ----------

Probably not a good idea...
[Nexus 4 Original Android Development] franciscofranco:
They'll go online if theres really need for that.
[Nexus 4 Original Android Development] franciscofranco:
Not sure its a good idea. The device might need that max freq for a while for some odd reason, but the load is not high enough that it justifies all cores online.
[Nexus 4 Original Android Development] rmead01:
I imagine yeah. the stability, battery, and temp of your kernel is great and i'm very thankful for it. Going along the lines of removing the kernel wakelocks because too much is being spent monitoring them, watching your cpu's and what onlines and offlines them gets me thinking. May not always be the best ideas, but it's somewhere in or alongside the box.
[Nexus 4 Original Android Development] franciscofranco:
Maybe the algorithm to calculate the load can be perfected. I'm not sure its accounting for IO. I'll double check.
[Nexus 4 Original Android Development] Net.silb:
About that:

I remember you decided to make high load threshold 70 by default when you first implemented the new hotplug algorithm. That was when we only had 1 core online. The load in that algorithm calculates the load based solely on cpu0 alone, disregarding the other cpus. Now that we have 2 cores online the load on cpu0 will automatically be less than the previous method because some of the load will be on cpu1. This means that the calculated load will be less so it will be harder for 4 cores to be online. Due to this, I think high load threshold should be a lower value than the original value of 70 and we can only find that value by testing different values until we find our "sweet spot".
[Nexus 4 Original Android Development] rajarshi10:
156 running great here. Kudos to franco.
[Nexus 4 Original Android Development] franciscofranco:
Sure, try 60 and let me know.
[Nexus 4 Original Android Development] mrgwap:
156 s an excellent kernel. But wen im in a call and the screen is off my touch screen still senses my touch...
[Nexus 4 Original Android Development] Net.silb:
Looks like I was wrong...

Just tested it with 70, downloading apps and surfing the web, using Facebook, very smooth, 4 cores went online when needed.
[Nexus 4 Original Android Development] aventu:
[MENTION=3292224]franciscofranco[/MENTION]

Lol you already got the right function in an older commit: https://github.com/franciscofranco/mako/commit/fb4cad419953d9d8ba1cff8b85f342f63b6072a5

// core0 to core3
#define TOUCHBOOST_CORES 1

static struct cpufreq_policy *policy;

/*
* Touch work function
*/
static void touch_work_func(struct work_struct *work)
{
struct lge_touch_data *ts =
container_of(work, struct lge_touch_data, work);
int int_pin = 0;
int next_work = 0;
int ret;

int cpu;

for_each_possible_cpu(cpu)
{
[COLOR="Lime"]cpufreq_get_policy(policy, cpu);[/COLOR]

if (policy->cur < TOUCH_BOOST_FREQ)
{
__cpufreq_driver_target(policy, TOUCH_BOOST_FREQ,
CPUFREQ_RELATION_H);
}

if (cpu >= TOUCHBOOST_CORES)
break;
}

It works really well now.

I think this part could need a function to your mako_hotplug for instant onlineing the needed cores. Of course there's no problem right now with 2 cores always on. I still got that color bug if I try to change settings (with my build only), super weird. My screen on time today was ~3h with bright light for some time and maybe 2 cores with 700MHz produced less heat than 1 core with 1188MHz or higher (the second "free" core goes crazy sometimes)

dunno, just thoughts :)
[Nexus 4 Original Android Development] Josh98:
Franco, any chance of adding Tasker integration? I'd love to be able to set a Task to switch to a power saving mode when opening certain apps like a ebook app for example.
[Nexus 4 Original Android Development] franciscofranco:
Although current state of the load calculator doesnt take into consideration iowait time and it thinks while waiting for IO that it counts as idle time. I just corrected on my local build and I think that iowait time should not be considered idle.
[Nexus 4 Original Android Development] franciscofranco:
Yeah I know, I was just seeing if you could find it ;) so on your build both cpu0 and cpu1 get boosted to 702MHz and are blocked of going below during UI interaction?
[Nexus 4 Original Android Development] franciscofranco:
Dunno. I have my own plans for per-app settings :)
[Nexus 4 Original Android Development] Josh98:
Sweet! Though Tasker integration would still be nice, could allow settings to change when battery reaches certain levels or whatever we want :)
[Nexus 4 Original Android Development] aventu:
Ah man kinda evil xD, yes they are locked while is_touching = true.

if (is_touching && pcpu->policy->cpu <= [COLOR="YellowGreen"]TOUCHBOOST_CORES[/COLOR])
{
if (ktime_to_ms(ktime_get()) - freq_boosted_time >= 1000)
is_touching = false;

if (new_freq < input_boost_freq [COLOR="SandyBrown"]|| pcpu->policy->cur < input_boost_freq[/COLOR])
new_freq = input_boost_freq;
}

cores which should be locked

just in case if a core couldn't be boosted, maybe not necessary

yay, I get random reboots and f**ed something up, was there an other reason for reverting this commit? :laugh:
[Nexus 4 Original Android Development] franciscofranco:
Show me the last_kmsg. I wouldn't be surprised if its some concurrency issue, maybe needs a lock before cpufreq_get_policy(policy, cpu); and after the operation is done. Need to see the panic log first.
[Nexus 4 Original Android Development] hughfollett:
[MENTION=3292224]franciscofranco[/MENTION] do you like the S4?? I bought the n4 this monday and I'm really loving it! I'm coming from the s2 and when my uncle bought the s4 i didn't like it :)
[Nexus 4 Original Android Development] franciscofranco:
I'm using the Exynos version. Its a fine device, the screen is great, touchscreen responsiveness is miles ahead from the N4. Touchwiz is meh, but I don't care, I just want an Android for me not to worry about for personal use.