yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] Redneck Trash:
Now that I have a couple of charge cycles battery life seems better. Nothing huge. Just enough to notice. This is from mostly network usage.
[Nexus 4 Original Android Development] Scottyfer:
Happened to me as well. I just reflashed my rom and it booted up fine. Had crazy **** go down with fku, so I uninstalled the app, reflashed r133 (prior to r134) and then reinstalled fku.

It's a hassle, but way better than a data wipe.
[Nexus 4 Original Android Development] justibasa:
Franco doesn't need to change a thing. What he does is what makes this the best kick a** kernel for the n4.

Don't like me......BITE ME!!!!
[Nexus 4 Original Android Development] JNewms:
Dude, franco and synergy already finished that convo. No need to stir the pot.
[Nexus 4 Original Android Development] mrgwap:
Hey Franco in your dashclock monitor I would like to make a suggestion. Could u let it read where the country is currently in real time. And wen the lockscreen is up where it says monitor it would be cool to see where the cpu is currently in real time also
[Nexus 4 Original Android Development] kyokeun1234:
Also happened to me before, I had to wipe my phone sadly...
[Nexus 4 Original Android Development] hoangtungst:
I'm using stock Launcher but it's not smooth , animation still lags . So what is the best alternative launcher ?
[Nexus 4 Original Android Development] Scottyfer:
I use Nova, but I've also heard lots of good things about Apex.
[Nexus 4 Original Android Development] kyokeun1234:
Something closest to the stock launcher will be the apex or nova launcher. They both feel very smooth and they are very customizable. Have both of them installed.
[Nexus 4 Original Android Development] ÜBER™:
Wouldn't be such a big deal if this was the first time. Sadly this just happened a day ago. But I wasn't doing anything :\… And I didn't get the chance to backup my apps via TiBu... So I had to redo everything. Twice. -.-

Sent from my Nexus 4
[Nexus 4 Original Android Development] roi14:
try apex or nova prime, but i don't know why stock is giving you problems, it is smooth as it is., well that's for me though.;)
[Nexus 4 Original Android Development] kyokeun1234:
That really sucks... Hopefully everything goes fine now.
[Nexus 4 Original Android Development] Cuzz1369:
Prolly a typo but no need for country in a CPU stat. And Franco said a while ago he has plans for the dashclock app. He just needs some time. I tried to send him some but PayPal time conversion was down that day.
[Nexus 4 Original Android Development] hoangtungst:
The animation when i scrolling page in app drawer is not smooth
[Nexus 4 Original Android Development] Haomuch:
What is the default io governor of r134?
[Nexus 4 Original Android Development] DesertVelo:
Trick question? heheh.... IO scheduler is deadline, governor is interactive
[Nexus 4 Original Android Development] Shano56:
Scheduler? Deadline
[Nexus 4 Original Android Development] andyli1985:
I had this happened to me before. I just did a nandroid backup anyway and used TiBu to restores the data from the nandroid backup, after a full wipe. :p
[Nexus 4 Original Android Development] ÜBER™:
Tried that. And it wouldnt show any of my apps. Like it total fubared my data partition. :\

Sent from my Nexus 7
[Nexus 4 Original Android Development] Scottyfer:
Was fsync off? I leave it on fearing a major data corruption because I tinker with my phone a lot.
[Nexus 4 Original Android Development] Jedipottsy:
Would it be possible to implement slide to wake into the kernel and Franco updater. Love this ROM, but I miss slide to unlock and it doesn't seem to work with the latest touch control app. Be nice to have it built in. Thanks
[Nexus 4 Original Android Development] andyli1985:
Was your nandroid backup compressed by CWM or TWRP? I am using TWRP. I noticed that TiBu doesn't know how to read a compressed nandroid backup, which really sux.
[Nexus 4 Original Android Development] ceejay83:
Were you under volting? Only happens to me if I over do it
[Nexus 4 Original Android Development] yokuyuki:
He said no before. Also tell the touch control dev to fix it so it works with this kernel.
[Nexus 4 Original Android Development] hoangtungst:
Anybody knows the frequency of GPU on xperia Z ?
[Nexus 4 Original Android Development] PetritH:
Did you really need to quote yourself ? :eek:
[Nexus 4 Original Android Development] justibasa:
P.S. I'm really drunk right now so if I offend someone than too bad, I mean I'm sorry, I think.

Don't like me......BITE ME!!!!
[Nexus 4 Original Android Development] ÜBER™:
Always, but most that has ever done is trash my launcher setup. Never had an issue with entire corruption. Just keep it on when messing with voltages... Turn it off after you find a stable setup.

Yep... That would be why :\ thanks for the heads up.

Always... But the first time all I did was turn the screen off. Wouldn't come back on and I had to hard reboot. It got stuck at the bootani. This time was my fault... Sort of.

Sent from my Nexus 7
[Nexus 4 Original Android Development] franciscofranco:
Ok so lets talk about development. I need to know if the fsync option I added does anything. Hows Ondemand after the tweaks? Hows battery life?
[Nexus 4 Original Android Development] b4ifuru18:
Battery life was pretty poor to be honest.
[Nexus 4 Original Android Development] nic85:
I wanna know this too

Inviato dal mio LG-P920
[Nexus 4 Original Android Development] mbernusg:
+1
[Nexus 4 Original Android Development] Serious_Beans:
There was a post by morfic saying that him and Franco found some sort of code in the commits that had something to do with gamma.
[Nexus 4 Original Android Development] franciscofranco:
Yes its possible. I'll build an interface for that when I get the N4.

Battery life was poor? That seems like user error more than anything, I didn't change much from stock.
[Nexus 4 Original Android Development] nic85:
what about the thermal throttling?

Inviato dal mio LG-P920
[Nexus 4 Original Android Development] abjexstallion:
So Francisco, are you waiting for your N4 or waiting for order it? Fan of your work bro!!
[Nexus 4 Original Android Development] cpom1:
Battery life has been awesome. I haven't used the fsync option yet. I changed the tweaks of ondemand to tweaks I usually use. Honestly the kernel is awesome. The only thing I hate is the powerhal issue that you already know about. That's the only thing I can think of. Other than I love the kernel and just dying for you to get yours Franco. Morfic as well. Love both your kernels. I almost want to give you my N4 Franco :p

Sent from my Nexus 4
[Nexus 4 Original Android Development] CaspaTheGhost:
Hoping I can get one in the next batch and that its before Christmas, but great to see Franco magic is already in effect.

Working blind gives me even more reason to think he is a warlock.

Now, let me drag my feet back to the Gnex forum where I must stay for now.

Sent from my Galaxy Nexus
[Nexus 4 Original Android Development] qwahchees:
After a day of monitoring the phone does have the issue with the other 2 cores not being used.

1.06GHz touch booster also annoys me, and hotplugging doesn't seem to work too well because core 1/2 are generally active.

With my GS3 with the S4, after a bunch of kernel updates for Ktoonsz it had proper hotplugging and it was possible to disable touch booster.

Hope your kernel goes well :) , btw where did it go momentarily?
[Nexus 4 Original Android Development] franciscofranco:
That will be worked soon.

Yes I'm waiting for Google to fill their ****ing stock to get one.

Yes I'll work on hotplugging when I get the device. Touch booster I'll have to see if its in the touch kernel driver or somewhere else.
[Nexus 4 Original Android Development] sd_matto:
Thanks for the great kernel; liking it so far.

Curious if you can add to the list of what will be "worked" soon, namely call recording support.

Example patches (for different devices) found here: http://code.google.com/p/2-way-call-recording/

Thanks for letting us know.
[Nexus 4 Original Android Development] elmerct:
Agreed!
[Nexus 4 Original Android Development] goldfingerfif:
To be honest I didn't notice any improvements over stock but my perception might have been thrown off with running light flow as that seemed like the king of battery draining.
[Nexus 4 Original Android Development] drawde40599:
That's not an issue that's how it works , stock kernel works the same way , being only build 5 ID say this kernel still pretty "stock"

---------- Post added at 10:39 PM ---------- Previous post was at 10:36 PM ----------

I'm not seeing battery drain from light flow , getting same battery I was before I " hacked " phone with no light flow ( ran 100% stock be4 even rooting this N4 ( so ID have a comparison)
[Nexus 4 Original Android Development] sixdaysandy:
I'm on franco build 5, I haven't disabled fsync, nor have I added any additional tweaks, just running the Stock ROM and the Franco Kernel as supplied. I've had zero reboots, I can confirm that all four cores are being used (though the 3rd & 4th understandably only kick in when I put the device under some high load).

Battery life seems improved over Stock Kernel, but that could be a placebo as I've only have the phone four days so there's only been a couple of charging cycles so the battery could just be bedding down. Usage has been pretty consistent, yesterday I used the phone for 17 hours unplugged and battery was at 35% when I put it back on charge. Today I'm doing a lot of travelling so we'll see how it holds up with some additional usage and switching between cell towers every five minutes.
[Nexus 4 Original Android Development] renna1992:
Hi franco,

would you mind taking a look at this thread and see if there is anything you can do about it?

thanks :)
[Nexus 4 Original Android Development] ian577416:
Speaking of boot-5.img, I flashed it and while in settings noticed that it says "3.4.0-franco.Kernel francisco@francisco #4" Is this the 4th or 5th kernel? Sorry for the noob question but I'm confused and I can't decompile the .img to look inside at the moment.
[Nexus 4 Original Android Development] danielvc:
Mine says it too and I'm running boot5. No worries! :)
[Nexus 4 Original Android Development] UZ7:
I've had this happen before and if yours goes back and forth between charging and full then it could be the cord itself, I found out my LG cord was faulty as it would charge to 80-90% then stop, I then plugged it in and it would say full when it wasnt.
[Nexus 4 Original Android Development] Toaster Strudels:
Same. It told me it was full at 4% and when I unplugged it, it died. Lol :D

Sent from my Nexus 4
[Nexus 4 Original Android Development] ceejay83:
Think my cord is faulty too. I'll have it plugged into the wall and it'll say it's charging via usb. Have to reconnect the cable and it'll be fine.
[Nexus 4 Original Android Development] elliot.newnham:
Don't know why people put so much faith in OEM cables/chargers :confused:
[Nexus 4 Original Android Development] UZ7:
Yeah I was testing various cords and when it got to 96% it would jump to 100% so I tested my bros cord and it stayed at AC. I also tested with an HTC cable and that worked fine as it charged without skipping. So now I'm back to using my Samsung cord which changes 2x faster anyway :P

The two instances where I kinda knew it was my cord was when I left it plugged overnight when I fell asleep and following morning it was 80-90% still had the lightning icon but said not charging.
[Nexus 4 Original Android Development] tanjiajun_34:
Just a request, It would be really nice if you can add the screen gamma adjustment and the ability to change between LG and Google screen presets. Both are found in fauxclock but unable to use on this kernel :/
[Nexus 4 Original Android Development] JNewms:
He isn't taking requests. The man knows what he wants to do and where he wants to head with his kernel.

Sent from my Nexus 4 using Xparent ICS Tapatalk 2
[Nexus 4 Original Android Development] ma678:
My phone was bricked after upgrading from r19.

The phone cannot power on.
[Nexus 4 Original Android Development] c_86:
I searched but didn't see anything in regards to this. Might not have searched well enough. So if this has been mentioned. Sorry

But I have a question in regards to the colors.

The default settings for this kernel. Are they the same as stock? Ex. The defaults are all at 255. Is that what stock is like or not?

I know I could flash a stock kernel and see but I try to flash a little as possible.

Anyways thanks to all. And happy holidays.
[Nexus 4 Original Android Development] leets4uc3:
Comes with stock 255 255 255
[Nexus 4 Original Android Development] overhauling:
Try charging it....

Just kidding. Did you do anything prior to or after flashing r20?

No problems over here. Loving it :)
[Nexus 4 Original Android Development] ben_pyett:
i seriously doubt it. Provide more information.
[Nexus 4 Original Android Development] ReD_AvEnGeR:
Please add sweep2wake
[Nexus 4 Original Android Development] kypeth:
Sweep what? We don't have actual buttons to support sweep2wake. Does the notification light sense touch?
[Nexus 4 Original Android Development] zephiK:
im assuming he mentions something similar to PGM. PGM is not yet available to n4
[Nexus 4 Original Android Development] Puzzlegirl:
R20 is looking fantastic so far :) Thanks for the Christmas present Franco. Merry Christmas (but we can't keep away from Android, since we have an Android Christmas here ;))
[Nexus 4 Original Android Development] ReD_AvEnGeR:
In the brick Kernel it works :thumbup:
[Nexus 4 Original Android Development] Michealtbh:
S2W has already been added to both Bricked and Faux kernels and works great
[Nexus 4 Original Android Development] humjaba:
First kernel I've loaded on my new Nexus. Works well so far - haven't noticed any significant increase in speediness over stock, but no issues either. I'm mainly interested in battery life so we'll see how that goes over the next few days. Quadrant score was 5104, but I didn't do a before test. Thanks for the hard work!
[Nexus 4 Original Android Development] falconrulz:
I have the Faux Kernel v002, is there a way to activate this feature?
[Nexus 4 Original Android Development] Haomuch:
My default io is row. What happened?
[Nexus 4 Original Android Development] ceejay83:
You didn't clear app data before updating
[Nexus 4 Original Android Development] Scottyfer:
It's good to know that. On my old phone I turned it off and ended up with a brick, but custom roms weren't even remotely as stable as they are on a nexus, so it was probably something entirely different.
[Nexus 4 Original Android Development] Cuzz1369:
Lolz. Seriously took the words right out of my mouth. What a dink.
[Nexus 4 Original Android Development] JNewms:
I can promise you that he won't implement it. And in the op he clearly states that if slide to wake doesn't work you need to contact the dev for that app. From what I've seen people always have an issue after updating the kernel, nothing Franco can, or will do about it.
[Nexus 4 Original Android Development] drawde40599:
FAST

DAMN Franco, running 134 at 1728, with high load at 70 rest stock (all day) all i can say is i have or have had almost every damn new phone out for last few years and NONE of them perform like this , NONE ! This 134 is freaking fast and smooth as hell with no heat at all! Battery took small hit becasue of MY settings but not much, i havent had ANY issues at all

Dont no how your going top this one but from watching u with Gnex i no u will :P

Thanks for your time!
[Nexus 4 Original Android Development] spicediablo:
Running rc1 and encountered freeze upon waking up

Log attached

https://www.box.com/s/qxkg1xpdi0n77rtxky5a

Sent from Mako⁴
[Nexus 4 Original Android Development] JNewms:
You should update your kernel. RC1 is old news now.
[Nexus 4 Original Android Development] franciscofranco:
Yeah I'm pretty happy with r134 in all levels, but I feel there is still room for improvement somewhere, and thats what I'm going to keep tackling! Probably making the Hotplug driver even more efficient, even knowing its pretty darn good at this point. Some ideas I have:

- Add thermal throttling in conjunction with the Hotplug driver so that maybe instead of throttling to 1.0GHZ we could maybe go down to 1.3GHz and offline two cores? Some combination like that.

- When onlining a new core make sure that core goes alive with the current frequency of ~max_freq/2 for more fluid experience

- When offlining all cores make sure cpu0 is at least at 1.0GHz for X milliseconds so that the next time the user interacts with the device in that X ms period the experience is fluid enough

Those are just some ideas that I've been thinking about.
[Nexus 4 Original Android Development] ceejay83:
Those ideas sound great Franco :good:
[Nexus 4 Original Android Development] Goku80:
I have tried all the kernels under the sun while on the nexus. And what made me stay on yours. The hot plug for interactive and the way we can control the way it works through it. You have done amazing work and still surprised you went with OC but am not complaining. Hardly message lately on XDA so thank you Franco for curing my flashing addiction

Sent from my SlimBeaned Nexus 4
[Nexus 4 Original Android Development] ÜBER™:
I was Gunna talk crap about the dynamic gov deal while I was on r133. Surely enough my complaints were resolved with r134. As soon as I started playing with it I was like. "What sorcery is this!?" Whatever it is your doing... Keep it up. Its fantastic. I could care less if the option to shut off the dynamics never happen. :)

Sent from my Nexus 4
[Nexus 4 Original Android Development] thebryceee:
[MENTION=3292224]franciscofranco[/MENTION] what's the path for max core frequency and governor controls?

Settings don't survive reboots for some reason so I wanna use init.d scripts
[Nexus 4 Original Android Development] franciscofranco:
Governor control won't do jack squad in this interactive as my code scales them based on load automatically.

Max freq is /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq

Something like that. And you need to apply it to all cores so just add 4 lines, one for cpu0, cpu1, cpu2 and cpu3.
[Nexus 4 Original Android Development] Luigiesin:
That would definitely work with even better performance.... Now, having to fire up 2nd core at the same freq (1.3) don't you think that would hit the battery?

Also the timer of the 1st core staying at a hi frequency for longer definitely will improve performance while surfing Internet, Facebook, Flipboard, etc ...

I guess the only concern is the battery... Because all these sounds amazingly cutting edge... But it seems it could hit the battery.

Sent from my Rock & Roll Nexus 4 \m/

ROM: PA 3.15

Kernel: Franco r134

T-Mobile
[Nexus 4 Original Android Development] Josuhu:
Im not using a screen protector. I Start to reproduce this and see what comes up.
[Nexus 4 Original Android Development] hoangtungst:
[MENTION=3292224]franciscofranco[/MENTION] , can you add GPU OC in next release ?
[Nexus 4 Original Android Development] JNewms:
He has said no to this quite a few times.
[Nexus 4 Original Android Development] Luigiesin:
Dude... Reading is a virtue! ;)

Sent from my Rock & Roll Nexus 4 \m/

ROM: PA 3.15

Kernel: Franco r134

T-Mobile
[Nexus 4 Original Android Development] BrandoHD:
This was perfect, lol

Sent from neXus 4 using Tapatalk 2
[Nexus 4 Original Android Development] franciscofranco:
You got it a bit wrong :p

- in the first case its when we're thermal throttling. Instead of capping all cores to 1GHz we could offline 2 cores and cap the other 2 to 1.3GHz

- The other two cases are just temporary CPU ramps to fill in some slow-down after offlining all cores, or just online a core already at 706MHz for example, instead of onlining it, wait a sample on cpufreq layer and then ramp it up if needed.

No.
[Nexus 4 Original Android Development] lolbazor:
That's sensei pateince right there.

Skickat från min Nexus 4
[Nexus 4 Original Android Development] kelah:
I always thought that values for cpu1-3 copied from cpu0 when they are going online. Am I wrong?

Will it work if I put 1728 to cpu0-1 and ~1300 to cpu2-3?
[Nexus 4 Original Android Development] dhruvmalik:
Franco, I don't change any CPU settings using the Franco app, only do Gamma once in a while.

I have now factory reset the device and just flashed the kernel and no app what so ever.

My question is that is it necessary to change the CPU settings, or leave them as it is.

What are the defaults?

I want the minimal amount of interaction to customization possible, and i am quite happy with the current setup, but maybe think there is room for a small tweak I could do to make the battery life a bit better.

CPU: Fast binned - I am not looking towards UV.

Thanks in advance.
[Nexus 4 Original Android Development] I2IEAILiiTY:
Lower the max freq and greenify your apps.

Almost doubled my battery life
[Nexus 4 Original Android Development] franciscofranco:
In this chip the cores are asynchronous, they have a will of its own. Yep, you can do that.

The defaults are the ones you're running, 384-1512.
[Nexus 4 Original Android Development] Luigiesin:
OK.. Understand the throttle part... So basically before off lining all 4 cores, or the last two cores, the 2nd core will stay at 702+ for some samples until offline?

Sent from my Rock & Roll Nexus 4 \m/

ROM: PA 3.15

Kernel: Franco r134

T-Mobile
[Nexus 4 Original Android Development] fakudolan:
Amazing battery life with r134!!

First time ive ever gotten 5 hour screen on time. Francos work never stops getting better!!
[Nexus 4 Original Android Development] nexusmaniac:
Is this with auto brightness?

N7/N4 - CM10.1 Nightly, Franco Kernel
[Nexus 4 Original Android Development] fakudolan:
Yeap.
[Nexus 4 Original Android Development] tlf55:
And what settings do you use ?
[Nexus 4 Original Android Development] :
That's quite unbelievable..
[Nexus 4 Original Android Development] fakudolan:
stock settings that came with the kernel, but -125 UV across the board, fast-bin cpu
[Nexus 4 Original Android Development] atz6975:
[MENTION=5149117]fakudolan[/MENTION]. Do you have some Cpuspy like graph of used freqs?

Thx.

Sent from smooth EOS4 running Nexus4
[Nexus 4 Original Android Development] tnw513:
[MENTION=3292224]franciscofranco[/MENTION] for the next app update :)

Inviato dal mio Nexus 4
[Nexus 4 Original Android Development] naishadh:
Sorry for noob questions what make diff with this setting I don't find any diff with 1.7 and hot plug 70.
[Nexus 4 Original Android Development] Net.silb:
Can some one explain the hotplug logic to me?

I've understood the following algorthim:

If - load > high load - online all cores

Else if - load > medium load - online one more core

Else if load < low load - offline all cores but one

Our settings are:

High load - 80

Medium load - 25

Low load - 50

Here is my question, what happens if the load is 30?

Answer - one core goes online!

Than what is the point of having the low load? It would only be considered in a case where the load was lower than 25 anyways...

Can someone please explain the logic to me?

Why is low load bigger than medium load?
[Nexus 4 Original Android Development] atz6975:
Hi,

dmesg | grep PVS doesn't produce any result when issued against hotplugged kernels (>111). Not a big deal, but maybe fransisco cares. Probably hotpluggin doesn't convey all hardware info (from hal?)

Edit: WORKS with 134, must be me

Sent from smooth EOS4 running Nexus4
[Nexus 4 Original Android Development] tlf55:
One core goes online over 25 % load if it's needed .. But when it's not needed and is lower than 50% load, the second core will go offline ..

Admitting you're surfing on the web, you're at 35% load of the cpu, the second core will go online because you need it, but then you're idleing in a page, it's still a 30-35% but it's not needed to have 2 core online, so the seconde core will go offline ..
[Nexus 4 Original Android Development] Net.silb:
Thanks for trying but your explanation doesn't really make sense and doesn't answer my question.
[Nexus 4 Original Android Development] wreckone:
Loving M2 great performance and battery life!