yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] Pure Drive GT:
franco.Kernel Updater App

I just updated the app and am very pleased with the new interface. It's very nice and have not me with any bug until now. Keep up the good job!

I'm thinking about buying the System Moniter App by Christian Göllner. One thing I seem to miss is the CPU temp. Is it really not there or is it just me not being able to find it?
[Nexus 4 Original Android Development] zephiK:
Slide out menu -> Status.... CPU temperature. Unless you meant the CPU temp in the system monitor app.. that would be in the system monitor app keep scrolling and you'll get a tab in red labeled temperature.. its to the right of battery.

http://i.imgur.com/Etz4EHt.png
[Nexus 4 Original Android Development] Pure Drive GT:
Well this is the battery temperature. I'm not so interested in this. I would like to see how my cpu temp is affected by different processes. :)

Gesendet von meinem Nexus 4 mit Tapatalk 4
[Nexus 4 Original Android Development] drawde40599:
Status tab
[Nexus 4 Original Android Development] theMaDHakkeR:
I just updated to the new app and noticed it set my IO Scheduler to Noop? I cleared app data and had the same result. I set it back to Deadline as I thought this was the default for R151.

Anyone else?
[Nexus 4 Original Android Development] gm.cinalli:
Is this the latest r1222? There's not any v1, v2...?
[Nexus 4 Original Android Development] eugenesan:
Thanks for the tip.

But I wonder if going back to stock hsic is the answer, after all 143 which probably built with non-stock hsic, is working normally.
[Nexus 4 Original Android Development] noneabove:
Does that mean n10 kernel to be merged with n4 changes soon? ;) Grats either way, looks fantastic :)
[Nexus 4 Original Android Development] gm.cinalli:
http://xdaforums.com/showpost.php?p=42332887&postcount=35644
[Nexus 4 Original Android Development] franciscofranco:
Its simple. Google's implementation of the drawer close its stupid because they close it while loading the new Fragment. What I did was making the mDrawerLayout public, then in the new Fragment class I in the end of the onCreate I did something like if mDrawerLayout is open, close it. And I removed the closeDrawers from the selectItem (which loads the new fragment base on the ListView position in the drawer that you just clicked). This way the closing animation only happens after the Fragment layout has been drawn on the screen. Major profit :)

Both cores are boosted to the same frequency defined by input_boost_freq.

Yes, during this next week.
[Nexus 4 Original Android Development] z3r0_x:
In the current r1222? I thought you wanted to implement that in the next nightly, if I watch the System Monitor, I can't confirm the Boost on the second core.
[Nexus 4 Original Android Development] franciscofranco:
My local build does that, no nightly has been released as of now. I want more people to update to the new app with the 12hour UpdateService interval by default, which will decrease server load under new nightly releases. Maybe later today I'll release a new version.
[Nexus 4 Original Android Development] PelegK:
Looking forward to it.
[Nexus 4 Original Android Development] Bobtehblob:
Is there a fix to the FC on opening of the app coming Franco?
[Nexus 4 Original Android Development] mitchdickson:
Been up in the play store for 12 hours.

Sent from my iPad 4
[Nexus 4 Original Android Development] PelegK:
Did you try to install the app again?
[Nexus 4 Original Android Development] panart:
That issue was fixed in version 10.0.1
[Nexus 4 Original Android Development] Bobtehblob:
Hmmmm, i'm on 10.0.01 an i'm still getting the FC. Will try reinstalling.
[Nexus 4 Original Android Development] franciscofranco:
I fixed all the FCs reported on my Developer's console on v10.0.2, which it should be hitting the servers any minute.
[Nexus 4 Original Android Development] Bobtehblob:
Cheers! :highfive:
[Nexus 4 Original Android Development] noneabove:
Yesssssssssssssss :)
[Nexus 4 Original Android Development] LibiSC:
I have a question... I have two cores only at 384 mhz but then it decides doesn't need one... So only one cpu at 384 mhz remains... How much does it take to change its frequency to what it needs... I mean the cpu it's at 384 when there are 2 cores but when there is only on might need more
[Nexus 4 Original Android Development] Mercado_Negro:
Franco, did you change the activity name in your app? I don't have the old version to compare but I always use the same theme in my launchers and all icons are replaced using the app activity. Now, since the beta your icon wasn't themed anymore but I thought it was intentional because it was a beta and I thought it'd change back again once you'd release it but it's not. Just want to know if I should contact the themer and let him know about this change.
[Nexus 4 Original Android Development] Zlatan9.:
BUMP i think he didnst see it
[Nexus 4 Original Android Development] franciscofranco:
Yes the first activity name has changed from Main to MainActivity.
[Nexus 4 Original Android Development] nexusmaniac:
The new font looks great :)
[Nexus 4 Original Android Development] z3r0_x:
Have you thought about the asymmetrical boost someone implemented here? Two cores at 1024 Mhz seems like an overkill - 1024 and 702 should be enough and easier on the battery.
[Nexus 4 Original Android Development] franciscofranco:
Frequency handling in these cores is asymmetrical by default. I don't see it as an overkill. By default input_boost_freq will be 702MHz because both cores will go up to that on touch. If Android needs more frequency to do its tasks it will ramp up normally from 702MHz, it just won't go below the boosted freq before we stop interacting with the screen.
[Nexus 4 Original Android Development] z3r0_x:
That sounds absolutely reasonable, thanks for the clarification!
[Nexus 4 Original Android Development] Mercado_Negro:
Ok, thanks. I'll let him know :)

Cheers
[Nexus 4 Original Android Development] TG2708:
Not sure if it should be asked here but how and what do i need to enable touch to wake?
[Nexus 4 Original Android Development] franciscofranco:
Nothing, that is not supported and won't ever be. Read the OP under "whats not coming" part.
[Nexus 4 Original Android Development] TG2708:
Ok thanks although it was a general question and not kernel dependent (which based on your reply is), hence the "not sure."
[Nexus 4 Original Android Development] franciscofranco:
Yes that feature is Kernel dependent.
[Nexus 4 Original Android Development] Shano56:
App suggestion, not sure if its been suggest is. I think on the status page, long pressing each button should take it to the appropriate menu. Thoughts?
[Nexus 4 Original Android Development] franciscofranco:
Explain.

Personally I don't see the point because everything is in the Drawer.
[Nexus 4 Original Android Development] TG2708:
Great. With all the awesome support you offer, I have no desire to use any other kernel, even bought the app. Latest nightly has been rock solid and gaming performance equally so. Keep up the good work.
[Nexus 4 Original Android Development] Zlatan9.:
BUMP
[Nexus 4 Original Android Development] nachordez:
He has said he's probably adding tasked support in future. Then, will be very easy to do that, or to change to preset depending on app, or whatever you can imagine.

By now, you could also do that with tasked via shell commands, not difficult if you are used to bash and terminal...

nexus4 / stock / last Franco.kernel nightly / V4A sound

gt-p5110 / PAC rom / V4A sound
[Nexus 4 Original Android Development] franciscofranco:
I have plans for more automated operations :)
[Nexus 4 Original Android Development] gm.cinalli:
Is this normal? As you notice from the screenshots I've a 53% no signal, but from the signal bar there's not any red bar...
[Nexus 4 Original Android Development] GerhardKi:
r151 is great. Best battery life of any franco kernel I have jused so far and still really smooth. Thanks for the great work!

I really like the design of the new fku app!
[Nexus 4 Original Android Development] scandalousk:
I'm guessing he wants it so that if you long press, lets say the max freq in status section, it'll take you to the frequencies/voltages section in the app for example.

Although I agree it's kinda pointless. Most of the information displayed in the status section is regulated from the frequencies/voltages section anyway. It's one or two clicks away.
[Nexus 4 Original Android Development] brodern:
New font, roboto light looks great!

One of the best looking apps out there along with system monitor and of course some of Google's own!

Keep up the good work :)
[Nexus 4 Original Android Development] derPianist:
WE NEED WIDGETS.

P
[Nexus 4 Original Android Development] nuwan32:
For some reason it won't download fku. It gets stuck at 100% downloading and doesn't install. When I restart the device, it says package name invalid
[Nexus 4 Original Android Development] ki2luminati:
Franco i just discovered that when your app is in horizontal mode, and then you click on the kernel update menu the app is crashing. Can you guys reproduce this? Just trying to help, love your work franco!
[Nexus 4 Original Android Development] aimcr7:
Uninstall old fku then redownload fku from play store
[Nexus 4 Original Android Development] thebryceee:
Hold it in portrait mode :P
[Nexus 4 Original Android Development] The Gingerbread Man:
Haha a classic 'your holding it wrong' momemt
[Nexus 4 Original Android Development] nuwan32:
still nothing. i even flashed latest gapps and cleared play store data/cache. just gets stuck at 100%
[Nexus 4 Original Android Development] drawde40599:
Uninstall it then go to data /data make sure its not still there, if it is delete it and reboot try agn.... if it is gone, try google it usually i find someone with my playstore issue
[Nexus 4 Original Android Development] nuwan32:
Yea thanks I fixed it, but there wasn't any trace app data it was because of auto run manager
[Nexus 4 Original Android Development] Nethojs29:
Just go out of xda for like 3 days because the admission tests of the university and now there is a r151... God franco, do you even sleep? Flashed the newer test and it is running perfect!
[Nexus 4 Original Android Development] franciscofranco:
No time to sleep!
[Nexus 4 Original Android Development] Shano56:
Like if you long press on max freq, it'll take you to frequency settings, kinda like quick toggles in the notification bar in 4.2. Little shortcuts for commonly used functions
[Nexus 4 Original Android Development] nellisere:
Just updated fku. Went to check for kernel updates, stuck in fetching with no WiFi activity, internet works fine so not sure if its your server, the app, or my internet, but then I was repeatedly pressing back to get back to my launcher (instead of the home button) and when I got to the home screen, fku fc'ed, sent the report but not sure if it goes to you or Google.
[Nexus 4 Original Android Development] lolrus101:
I've been getting random reboots for about a week now, even on stock and rooted. Anyone else? :(

Sent from my Nexus 4
[Nexus 4 Original Android Development] TrenchKato:
Under volt much?

Nexus⁴ Life
[Nexus 4 Original Android Development] franciscofranco:
Just pushed r152.
[Nexus 4 Original Android Development] nellisere:
Just had a force close after selecting autoflash for r152, do you need logcat or is sending the fc report OK?
[Nexus 4 Original Android Development] franciscofranco:
Try again, I named the boot.img wrongly on the server.
[Nexus 4 Original Android Development] nellisere:
Yup, no problems now, thanks for your hard work!
[Nexus 4 Original Android Development] asm19:
Yes, works fine for me.

Sent from my Nexus 4
[Nexus 4 Original Android Development] nellisere:
Not sure if this has been mentioned before, but would it be possible to add a cancel button to the download prompt? Sometimes I've been downloading on 3G and its just been so slow so I have to close the app and everything and switch to WiFi and it's just be easier with a cancel button. Just a thought.
[Nexus 4 Original Android Development] franciscofranco:
Yes improvements on that are planned. A cancel button and a button to push the download to the background/notification bar. I should've added it long ago, but been lazy because I like how simple and great the dialog looks.
[Nexus 4 Original Android Development] alanwyl:
Franco says he will make downloading in the background later.

--

oops
[Nexus 4 Original Android Development] franciscofranco:
Also I want to hold on new releases for a while for serious testing on r152.
[Nexus 4 Original Android Development] ryanytchan:
Major difference between 1222 and 152?
[Nexus 4 Original Android Development] Mercado_Negro:
Good idea.
[Nexus 4 Original Android Development] pyr0sphere:
Will see what other people say, but I'm getting a lot of lag overall compared to r151. And I'm not sure it's the type caused by rebuilding cache

Let's see what others say
[Nexus 4 Original Android Development] Cuzz1369:
So quick question. Is the input boost locked at 702 while touching or should it be scaling higher. I notice while playing a game or on my home screen or app drawer it won't go above 702 while touching the screen but if I swipe and let it scroll without touching it goes considerably higher only to lockdown again at 702 when touched. And I even tried vigorously swiping without lifting my finger and both cores stayed at 702. I am on r152 with the latest app update.

Carbonized and francofied N4
[Nexus 4 Original Android Development] goTouch:
Franciscofranco, maybe I'm pointing something that doesn't make sense.

If any app is already using a core, for example, at 1.5 GHz, when you touch the screen, the kernel is forcing to 702 Mhz, both kernels. I did a test and I think it's happening.

My English is not that good and I don't know if a made myself clear.

Enviado do meu Nexus 4
[Nexus 4 Original Android Development] nellisere:
Another app issue. I cleared the data after flashing r152, then rebooted, but opened the app before a data connection was established, so it came up with the licence error, once a connection was made, I went to click retry, but nothing happened, it went blue like I pressed it, but nothing, stayed on that screen no matter how many times I pressed it, closed the app and opened again and all is fine.
[Nexus 4 Original Android Development] goTouch:
Sorry... double post!

Enviado do meu Nexus 4
[Nexus 4 Original Android Development] PetritH:
input_boost_freq changed from 1026 to 702...this is what I can see, the others are franco's magic
[Nexus 4 Original Android Development] strainhunter:
I was saying the same a while ago. I always said "I can sleep when I am dead"

Then after being awake for around 4 days I started seeing things^^ (but maybe there was some other influence :) ) So I try to get at least 6h daylie.

In Germany we say : "Was der Schlaf für den Körper ist die Freude für den Geist"

In english : "What's the sleep for the body, is the joy for the mind"

Keep up the good work! And get your rest^^

Maybe you should try power-napping ;)

Gesendet von meinem Nexus⁴ <CarbonROM>+franco.Kernel(faux123 atm)
[Nexus 4 Original Android Development] Cuzz1369:
Lol thanks for repeating 25 times what I just said.

Carbonized and francofied N4
[Nexus 4 Original Android Development] PetritH:
Btw Franco,im having huge fps drops and lags in beach buggy blitz,can you check that or its just me. Thanks
[Nexus 4 Original Android Development] Connor Baker:
Franco Francisco doesn't need sleep; sleep needs Franco Francisco.

Connor Baker
[Nexus 4 Original Android Development] Bobtehblob:
Our N4's are at the ready!
[Nexus 4 Original Android Development] goTouch:
Really sorry about that. Didn't do it on purpose! I was trying to edit my post and something went wrong with tapatalk beta

Enviado do meu Nexus 4
[Nexus 4 Original Android Development] Cuzz1369:
Just fooling around with ya. Tapatalk sucks balls.

Carbonized and francofied N4
[Nexus 4 Original Android Development] goTouch:
Sorry about the mess! Tapatalk beta went crazy on my device!

Enviado do meu Nexus 4
[Nexus 4 Original Android Development] zellleonhart:
Just flashed r152, it was extremely laggy when it just booted into OS, all animations are jagged and stuttering.

But after like 3-5 minutes settling down is it smooth. Trying a few more reboots now

ADD ON: overall I feel that r1222 is way more responsive, it feels like scrolling through pages in app drawer is slow and not touch sensitive. The lag for 3-5minutes at startup is unbearable.

Or maybe just me? I am sure I cleared FKU app data before flashing. Didn't clear any caches.
[Nexus 4 Original Android Development] gravitysandwich:
Ok I'm had a random reboot again from unlocking screen to view notification but I'm not sure since it might've been the gamma code bug. But I'll just post the log just in case. And Thankfully I noticed it since I was drunk as f'. (Hangovers are not fun) here you go...

http://pastebin.com/VCj7FQ55
[Nexus 4 Original Android Development] Mercado_Negro:
There's just one threshold now? Set to 60, as far as I can see. I just read some pages ago that you lowered the first threshold but I didn't know the other two were not needed anymore.

[EDIT] Already found an explanation about this.
[Nexus 4 Original Android Development] PetritH:
Its so smooth to me mate, reflash again and clear fku app data,the only lag I see atm is playing beach buggy blitz, extremely lagy and huge frame drops but UI is smooth as hell
[Nexus 4 Original Android Development] zellleonhart:
I will try again. need not to clear cache and dalvik right?
[Nexus 4 Original Android Development] zephiK:
Clear cache and dalvik means nothing for the kernel. Franco has stated this a long time ago.
[Nexus 4 Original Android Development] PetritH:
No,its not needed, just clear fku app data after u install the kernel and reboot
[Nexus 4 Original Android Development] evostevo1:
I had the same lag for a couple minutes. I let the phone settle a little more then reboot. I have no more lag. Seems really smooth to me now.
[Nexus 4 Original Android Development] aimcr7:
UI is smooth even after first boot, tried beach buggy blitz, it is not that laggy only occasional frame drops, not as smooth as on r151 tho.
[Nexus 4 Original Android Development] PetritH:
Yeah, not as smooth as r151, and I have too many stutters in that game but temple run 2 and bad piggies work better than in r151. Thanks for your reply, at least im not the only one having frame drops in beach buggy blitz
[Nexus 4 Original Android Development] goTouch:
Every time you touch the screen, cpu0 and cpu1 is going down to 702 Mhz. Same lag here.

But overall performance is really great with r152.

Enviado do meu Nexus 4
[Nexus 4 Original Android Development] zephiK:
Having the same lag with r152 at the beginning. Cleared app settings and all that before flashing.
[Nexus 4 Original Android Development] zellleonhart:
I just flashed again and the result is the same.

I did this from r1222 to r152: cleared FKU data > boot into CWM > flash > reboot

It lagged terribly. Waited it to settle down and clear FKU data again, rebooted. And now it is still laggy from time to time, I flashed back to r1222 and everything is smooth again.

I notice it takes a long time after every reboot for r152 to settle down to useable smoothness. at least 10 minutes
[Nexus 4 Original Android Development] pyr0sphere:
After about 50 min the lag hasn't gone away and all of the caches should have been rebuilt

Will return to r151 and eagerly await r153
[Nexus 4 Original Android Development] franciscofranco:
Hmm maybe a small derp in my code that I didnt catch. I tested this r152 for 24h without a single lag though :(
[Nexus 4 Original Android Development] ridikolous:
On a fresh ROM install(3 different roms). I downloaded the fku app, upon first loading up the app. I got a message saying " I don't have root and I must exit and restart." Its fine after an app restart.
[Nexus 4 Original Android Development] LibiSC:
Have you pushed the changes to github?
[Nexus 4 Original Android Development] Mercado_Negro:
Maybe this has something to do with it?

I don't know, maybe there's an explanation for it and I missed it.

[EDIT] Already found an explanation about this.
[Nexus 4 Original Android Development] Cuzz1369:
I don't notice any lag after boot. The touch being locked at 702 kinda bothers me though. 2 cores at 702 is enough for most tasks and I could also up that manually. But I definitely don't want 2 cores at 1.5 everytime I touch.

Carbonized and francofied N4
[Nexus 4 Original Android Development] goTouch:
Overall performance here is amazing. Best release so far.

In some games it really lags sometimes.

Enviado do meu Nexus 4
[Nexus 4 Original Android Development] zellleonhart:
I don't know, I am using PA 3.57 ROM anyway. There are 3 more people having the lag like me (from what I observe in the replies now).

I flashed back to r1222 and immediately noticed the difference, r1222 is like wayyyyy smoother than the r152 in my phone. Very very distinct difference.
[Nexus 4 Original Android Development] germanj:
I don't know how you coded the new hotplug mechanism but there has been a significant battery life improvement over previous versions with r152, all that without performance decrease. Seriously.
[Nexus 4 Original Android Development] Cuzz1369:
Touch boost is 1026 in r1222. 702 on r152. Might be more to it than that. But that's my guess.

Carbonized and francofied N4
[Nexus 4 Original Android Development] zellleonhart:
I even changed the touch boost to 1350, it doesn't help much. On the other hand, setting touch boost to 702 on r1222 is still smoother than 1350 in r152.
[Nexus 4 Original Android Development] Cuzz1369:
Must be a deep in the code somewhere else like he just said.

Carbonized and francofied N4
[Nexus 4 Original Android Development] drawde40599:
No lag

Not seeing any lag here after second reboot after install , Before reboot everything was in slow motion, actually made me laugh :P but after reboot everything is fine no lag anywere been on for good hour now its running fine, feels good so far, dont really feel much diffrent than 1222. im Using with AOKP

Thanks franco

EDIT : that includes playing temple run 2 , no lag there whatsoever
[Nexus 4 Original Android Development] :
Pretty good battery life and smoothness on r151. We'll see what r152 brings to the table. But one thing I notice, it's pretty smooth. Thanks franco.

Sent from my Nexus 4
[Nexus 4 Original Android Development] Sukhi:
No lags here ...running flawless with both Input and boost freq capped at 702Mhz. Battery drain has been minimal within the last 45mins of usage. I guess w.r.t lags, something to do with the Rom rather than totally being dependent on the Kernel.
[Nexus 4 Original Android Development] TrenchKato:
Agreed. Only took a minute or two for 152 to settle here

Nexus⁴ Life
[Nexus 4 Original Android Development] hol17:
On r152 and I haven't noticed any slow downs or "slow motion". Seems the same as r1222 in terms of speed and performance right now. Will test more when I'm in a work environment and need to constantly use my phone.
[Nexus 4 Original Android Development] TonySkate:
Running o the latest pa and r152 my nexus present lag even with the stock launcher.... I am back with the r146

Enviado desde mi Nexus 4 usando Tapatalk 2
[Nexus 4 Original Android Development] goTouch:
It may be something related with PA. CM10.1 is flying with r152.

Enviado do meu Nexus 4
[Nexus 4 Original Android Development] spaceman860:
[MENTION=470754]Franco[/MENTION] getting f/c in the app when trying to go into updater tab while the phone is in landscape here's a log of the crash

http://db.tt/JSIQnRD4

Sent from my Nexus 4
[Nexus 4 Original Android Development] ngkongArm:
yes, happened on me too. using carbon. i'm back to 151, and feels better.
[Nexus 4 Original Android Development] zellleonhart:
You're using Carbon ROM? Now I've seen PA and Carbon users reporting the lag. Not from CM though.
[Nexus 4 Original Android Development] Holcomb227:
I have no problem with r152 but I noticed the kernel settings stayed the same coming from r151. The I/O Scheduler was still on noop even after I cleared the apps data. Had to reboot after clearing the app data to get the kernel to default.