yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] Dan53:
Makes sense. My thinking was values are between 0-100. Therefore, second level goes up more cores that are online, preventing what you are saying. But of course that doesn't make much sense either
[Nexus 4 Original Android Development] jrxtepan:
Installed

Ok So I installed M2 and got so far the best battery life I've ever achieved.

After all the great reviews for 134 I decided to move there. Testing now.

Great work Franco, keep up the excellent work!!! :good:
[Nexus 4 Original Android Development] pikachukaki:
Im noticing a lag when hearing music i thought it was rom problem but this happent with PA and with slimrom...the music lags like im hearing from internet with big lag...any thoughts?
[Nexus 4 Original Android Development] emmib:
For me, with CM10.1, r134 gave me EXCELLENT battery life on WiFi. The moment I switched to 3G, it all went to hell. 1% every couple of minutes screen on time or so. Anyone else get this? Around 20% in 15 minutes or so, plugged it in when it hit 4% and flashed Milestone 2.
[Nexus 4 Original Android Development] vjales:
franco, could you please explain or post on op, if maybe one day we need to leave your kernel, we need to do something special? Or just overwrite your kernel with another kernel? Because some peoples are having problem after leaving your kernel, e.g. lags etc...
[Nexus 4 Original Android Development] Mercado_Negro:
Yep, that's how it is on 3G. I run out of battery really quick when I'm browsing forums with Opera mini or just the stock AOSP browser. Pretty much how you said, about 20% in 15 minutes or so. Crazy but that's life :)
[Nexus 4 Original Android Development] republicano:
other than flashing your roms kernel or stock kernel due to ramdisk modifications?
[Nexus 4 Original Android Development] italia0101:
Well on a side note . barca got totally ass invaded 7-0 over two legs
[Nexus 4 Original Android Development] franciscofranco:
I'm at the airport, I jumped a few posts before I read that you guys already had figured that out.

Ok so now that I'm waiting for my flight I'll try to explain the logic of the Hotplug driver, again.

Lets start on how the thresholds scale based on the number of online cpus:

For each online cpu the system load on the driver is reported as current_load * num_online_cpus(), this this:

first_level = stats.default_first_level * stats.online_cpus;
second_level = stats.default_second_level * stats.online_cpus;
third_level = stats.default_third_level * stats.online_cpus;

Now that part is out of the way we can understand how my algorithm works:

If the system load is > than 25% (since the thresholds scale with the num_online_cpus 25% can be 25/100 in case of only 1 core online, 50/200 with two cores online, and so forth, basic math) and we only have 1 core online it will bypass the time_diff (which is 2 seconds to prevent too many online/offline and bust battery life) and online the second cpu right away.

else if (load >= second_level)

then

if (stats.online_cpus < 2 || (now - stats.time_stamp) >= temp_diff)

After the 2 cores are online there are at least 2 possible scenarios:

- if the load bigger than 25% but less than 80% (new high threshold) for the next 4 seconds it will online the third cpu, and then another 4 seconds for the last cpu

- if the load is lower than 25% it will fall to the last check and it will eventually offline all remaining cpus.

But now that I'm typing this the 25% for medium and 50% for low doesn't make much sense at this point because it checks for medium load first then low load, so if the load is < 25% it will offline all the cores no matter what, so the 50% is kinda... obsolete.

I'm gonna test 80% high, 50% or 40% medium and 25% low, might as well boost performance a little bit.

But then again if we decrease the medium load the second core will need more load to come online and that might decrease scrolling smoothness or something.

Fun times I guess, we'll find some ideas together!

Thanks for the nice feedback guys, I love when the thread is like this!!!!
[Nexus 4 Original Android Development] italia0101:
Also in case no one knows . touch control has been updated for latest Franco kernels .

Sorry if I'm late with it
[Nexus 4 Original Android Development] Nethojs29:
I remember when I used to understand what people were talking on this thread

I'll have fun tomorrow making fun about the game, a lot of friends lines barca.

Enviado desde mi Google Nexus⁴
[Nexus 4 Original Android Development] nexusmaniac:
Are the default governor control settings good for battery life or is it worth lowering the high speed frequency and the input boost frequency?

N4/N7 - CM 10.1 Nightly, Franco Kernel
[Nexus 4 Original Android Development] emmib:
I know but it's not usually that bad, on r127 I got relatively great battery life on 3G! loses around 10% after an hour and a half or so, 2 hours screen on time with 14-15 hours total
[Nexus 4 Original Android Development] LibiSC:
You can play with the time too
[Nexus 4 Original Android Development] Mercado_Negro:
But that's exactly what I get with the stock kernel or the other two I've used, Semaphore and SaberMod. It's never been good. I can't remember how it was on those older versions of Franco's, maybe I should try them again, that's a good idea, thx.
[Nexus 4 Original Android Development] Counter1602:
Touch control don't work with m2 :(
[Nexus 4 Original Android Development] sirxdroid:
[MENTION=3292224]franciscofranco[/MENTION] - if you now allow over-clocking, why not allow under-clocking too? I'd rather have under than over clocking. Thanks!
[Nexus 4 Original Android Development] realfelix:
Lol? you can underclock mate. Simply by lowering the frequency from 1512MHz to something lower?
[Nexus 4 Original Android Development] yoft1:
It does now, the dev just updated his app. In the future, keep touch control related issues in the touch control thread
[Nexus 4 Original Android Development] kyokeun1234:
I think he means having lower frequency like 194
[Nexus 4 Original Android Development] gharrrrrr:
Sent from my LG-E960 powered toaster.
[Nexus 4 Original Android Development] UgoBoss:
Great job on r134 Franco ! Better and better ! Thank's for awesome work , I get epic battery life :cyclops:
[Nexus 4 Original Android Development] Rivermind:
I think the mods should set up the profanity filters to replace "touch control" with "my OP reading skill" or something similar.
[Nexus 4 Original Android Development] fozzie:
... or "douche patrol"!
[Nexus 4 Original Android Development] gharrrrrr:
On r134. Besides a few derps, which I believe were entirely my fault, its been good. Had frequency at 1.7 for about 13 hrs now. Rest settings all stock. About 1 1/2 hrs SOT still at 73%. Only 3hrs on WiFi. Its pretty fast and smooth. No lagging.

I have had wake issues though. Only every once in a while I hit power button to unlock and it takes 30-40 seconds to wake up. Didn't have this problem on M2. Not even really a problem, just confusing and annoying. Still not sure if it is something on my device or the kernel. After this cycle I'm going to do full wipe reset and try again and see if issue there. Cheers.

Sent from my LG-E960 powered toaster.
[Nexus 4 Original Android Development] nexusmaniac:
Are you using the default settings? And what SOT are you getting?

N4/N7 - CM 10.1 Nightly, Franco Kernel
[Nexus 4 Original Android Development] pkelly517:
I always find it much easier just to scroll past the post.

If enough people DON'T answer, then maybe he does a search. And, as a perq, I get to move onto a relevant post much earlier.
[Nexus 4 Original Android Development] Arstoien:
50% low load works as 50 when all 4 cores are online, so it's not obsolete?
[Nexus 4 Original Android Development] sirxdroid:
Yes, that's exactly what I mean, min freq < 384. Maybe under-clock is not the right term for it but you get the idea.
[Nexus 4 Original Android Development] Testraindrop:
He already said he wont add it, that could lead to weird issues when coming from sleep or while deep sleep.
[Nexus 4 Original Android Development] realfelix:
Oh okay sorry then mate. I guess franco will consider that but dont expect much battery gain just because of 192Mhz less. And its a bit unstable when idling and will likely lag a bit when the cpu scales up fast e.g. when waking up the device.
[Nexus 4 Original Android Development] italia0101:
Dude that is unbelievable . 4-5 posts on the same page I just said touch control has been updated ... Come on..
[Nexus 4 Original Android Development] Skillfulshoe:
Your logic destroying my brain right now, it's that good.

Quick question to anyone reading, can under volting cause random sporadic attacks of touch presses all over the screen? That just happened to me. Im -75mV across the board. Fast CPU.
[Nexus 4 Original Android Development] thebryceee:
What service and what area do you live?
[Nexus 4 Original Android Development] CamoGeko:
I'm undervolted -150mV and I don't get any weird touch activity.

Sent from my Nexus 4
[Nexus 4 Original Android Development] Leegalaxy:
Lowering CPU frequencies can cause the dreaded SOD (look it up if you don't know that SOD is). Best to avoid that at all costs.
[Nexus 4 Original Android Development] sirxdroid:
I haven't used franco in a long time (that's 1 week for flashaholics) but just flashed r134. Looking good and feeling smooth. I thought it was hard to match MPDecision+ondemand (the stock kernel combo) but r134 feels very close.
[Nexus 4 Original Android Development] aimcr7:
Is it happen while charging? If yes, it's your charger, use different charger. If no, i UV -125 fast binned cpu with no issue at all.
[Nexus 4 Original Android Development] vjales:
Amazing kernel! Have been using this kernel for more or less 4 hours and is just amazing! I think it just decreases the smoothness of nexus a little bit, paying the price for a decent battery life. And another thing that is annoying is if I make a reboot, before more or less 2/3 hours of use, after the reboot it'll drop 3-4% of battery, like if it wasn't measuring correctly the battery percentage. You're amazing franco!
[Nexus 4 Original Android Development] Underground_XI:
it is normal that phone reboots consumes a coupw of battery percentages...
[Nexus 4 Original Android Development] thebryceee:
Anyone use groove ip and when you take your face away from the phone, the screen doesn't turn back on? I don't use a screen protector and always keep my screen clean. Not sure if this happens using regular phone calls either.

Edit: I'll try the Keep Screen On function and see if that solves it.
[Nexus 4 Original Android Development] Underground_XI:
what makes you think that is kernel's fault?
[Nexus 4 Original Android Development] thebryceee:
Just seeing if anyone is experiencing it or if it's an isolated incident. Truth is I have no idea if it's the kernel's fault or not, hence, why I'm asking.
[Nexus 4 Original Android Development] Underground_XI:
app fault.
[Nexus 4 Original Android Development] pyr0sphere:
Anybody extensively use both M2 and r134? Any recommendation? Currently using M2 and really enjoying it
[Nexus 4 Original Android Development] thebryceee:
I'm gonna try it with phone.apk
[Nexus 4 Original Android Development] republitarian:
I was on M2 up until 2 days ago. So far I have to say it is just as good as M2 if not better on battery life. I am finally hitting 5+ SOT (On both versions).
[Nexus 4 Original Android Development] Luigiesin:
+1

Sent from my Rock & Roll Nexus 4 \m/

ROM: PA 3.15

Kernel: Franco r134

T-Mobile
[Nexus 4 Original Android Development] Skillfulshoe:
I wasn't charging. It hasn't happened again yet. I'll let you guys know if it does.
[Nexus 4 Original Android Development] republitarian:
I have -200 UV and haven't come across this.
[Nexus 4 Original Android Development] germanj:
Just some feedback. Going from r127 to 134 SwiftKey keyboard now lags behind fast typing as opposed to the previous kernel version. All settings default.

The rest of the phone from browsing to ui transitions are perfectly smooth.
[Nexus 4 Original Android Development] 3dupunk:
I know it's been said here time and time again but thanks for the kernel franco! I don't use it all that much but I purchased your app because I feel it's important to supports devs such as yourself who continue to push the envelope. R134 43% after a full day of moderate use, -100 uv across the board, I can't really ask for more than that.

Waking the phone does lag, but it seems to only happen when you press the power button quickly. Other than that no complaints and I could live with that lol.....keep it up!
[Nexus 4 Original Android Development] 3dupunk:
I've been noticing the same thing but I run Swype, didn't really pay much mind to it nor did I think it was kernel related.....is it? Are their others having the same issue?
[Nexus 4 Original Android Development] :
Guys, I'm a noob here. I tried to search what is "fast-binned cpu" or how to do it but I couldn't. Could anyone please tell me how to set it or do it or post a link maybe? I am running r134 undervolted to - 150. It's very stable so far. Thanks a lot.
[Nexus 4 Original Android Development] michael_ta315:
-200 UV? The most I could UV was only -175 on nominal :eek: more than that it'll reboot. Which type are you running on? probably fastest?

http://xdaforums.com/showthread.php?t=2052496 ;)
[Nexus 4 Original Android Development] republitarian:
Believe it or not I have a nominal CPU when I checked the bin. Purchased the phone April 5th. Camera, temple run 2, and benchmarks are working with no crashes.

I might even try -225 :cool:
[Nexus 4 Original Android Development] :
Thanks, that was quick. I actually found it earlier but didn't understand. So basically, it's not a setting. You just have to execute the terminal command and that's it?
[Nexus 4 Original Android Development] 3dupunk:
I don't remember how to or rather the command I used in terminal emulator but if your stable at -150 I would say your fast binned (don't quote me on this though). Mine is, and I uv -100 across the board to keep my phone cooler. Here u go

http://xdaforums.com/showthread.php?t=2052496
[Nexus 4 Original Android Development] republitarian:
Not necessarily I am -200 and nominal
[Nexus 4 Original Android Development] michael_ta315:
Yeah it's like sorting your CPU, Fastest can handle the most UV, Faster will handle less UV than Faster but more UV than Nominal, Slower is the least UV-friendly :p
[Nexus 4 Original Android Development] rysup:
I use Swype too but I've only seen the delay once since r134 was added... And I've been doing a lot of typing err swyping!
[Nexus 4 Original Android Development] :
I got it. Thanks again. Mine is pretty stable at -150 and since I'm on HSPA round the clock it keeps my phone cool. It helps a lot especially that my country is tropical.
[Nexus 4 Original Android Development] 3dupunk:
Do you see any real advantage by uving that much besides the phone being cooler?
[Nexus 4 Original Android Development] michael_ta315:
Theoretically it saves battery. But I don't really see it or it maybe insignificant. But less heat is always a good thing. More heat is not good for CPU and could decrease battery life.
[Nexus 4 Original Android Development] republitarian:
From stock levels, not only is it cooler but battery life has improved. This isn't completely a scientific test but I probably squeeze approximately 20 minutes more of SOT(on wifi) from a 100%-0% charge.
[Nexus 4 Original Android Development] Shano56:
Battery life rocks
[Nexus 4 Original Android Development] 309041291a:
Get off WiFi :P, use 3G/HSPA+
[Nexus 4 Original Android Development] spicediablo:
Just a heads up. Touch control had been updated to support franco kernel. I have tested with m2 and it works. :beer:. Latest version of touch control is 1.6i

Sent from Mako⁴
[Nexus 4 Original Android Development] CrimsonSmear:
Try enabling input_boost in the Interactive governor and see if that helps with the issue.

In f.Ku, go to Frequencies/Voltages -> Governor control and change input_boost to "1"

or echo "1" > /sys/devices/system/cpu/cpufreq/interactive/input_boost
[Nexus 4 Original Android Development] :
Thanks for the heads up. Have you noticed your battery life impacted by Touch Control? It's actually a very helpful app but since uninstalling it, I noticed that my standby time has improved, maybe because it uses battery while monitoring gestures.
[Nexus 4 Original Android Development] JNewms:
After spending all day moving it's been awesome reading this thread and catching up.

I thought I'd share my latest tinkering with everyone. I'm a huge fan of Franco's hotplug routine, but thought I'd do a little experimenting. I've lowered my max cpu frequency to 1188, then I lowered my high loss threshold to 15, and suspend frequency to 384. So basically my phone is doing an amazing job holding battery while asleep, and then as soon as I turn the screen on and start doing something it onlines all 4 cores.

Now I will admit the Franco's default settings are a little better on battery life, but it's been amazingly fast on everything. I will probably go back to the hotplug routine in a day or two, but I just wanted to share these settings for anyone that wants to play around a bit. :thumbup:
[Nexus 4 Original Android Development] Underground_XI:
that app is awesome but drains lots of battery for me.
[Nexus 4 Original Android Development] spicediablo:
I am not really bothered by that as it doesn't significantly impact my battery life. Besides, it helps to preserve my power button. :)

Sent from Mako⁴
[Nexus 4 Original Android Development] :
That confirms my observation. Thanks..
[Nexus 4 Original Android Development] surtrafl:
After a long deep-sleep if someone calls me... my screen freezes. I can't answer the call. Bummer.
[Nexus 4 Original Android Development] Mo'HAWK:
Once my power button goes then I will resort to gesture control

Sent from my Nexus 4 using Xparent Green Tapatalk 2
[Nexus 4 Original Android Development] Shano56:
Or you could buy a new power button :p
[Nexus 4 Original Android Development] Redneck Trash:
Or not worry about it because you probably won't own the phone long enough to wear out the damn button.
[Nexus 4 Original Android Development] Mo'HAWK:
Which one would be cheaper lol?

NeXuS IV
[Nexus 4 Original Android Development] jeaniturrizaga:
I just tried the gesture app. And it is very need! A must...
[Nexus 4 Original Android Development] trailblazerz11:
Got mine in December and it wore out. Have to press center of it hard with my nail to work. Quite annoying.

Using lmt isas mostly now to screen off and CM volume key wake.

Sent from my Nexus 4
[Nexus 4 Original Android Development] ceejay83:
that sucks, why don't you use touch control? your volume keys are going to crap out on you :eek:
[Nexus 4 Original Android Development] combatdeity:
You should try get that fixed under warranty, unless you abuse your device, that's got to fall under general wear and tear usage.
[Nexus 4 Original Android Development] trailblazerz11:
Yeah I should probably try it, never got around to it.

It should but I'm in Hong Kong for awhile, they would charge for repair here.

Also have a small crack on a corner, not sure their policy on a phone with both accidental damage and defect... But it's chill, AMEX reimbursed the whole thing on their purchase protection so it was pretty much free.

Really off topic lol, but guess it's because kernel is great.

Sent from my Nexus 4
[Nexus 4 Original Android Development] thebryceee:
Had mine since December and my power button is fine :eek:. How many times a day do you unlock?! :p I would see if you can replace under warranty because that's not very long for the button to wear out already.

Anyone else on T-Mobile LTE getting better battery life than HSPA+ 42? Getting WiFi like battery life.
[Nexus 4 Original Android Development] Underground_XI:
some have weak unlock button themselves. first nexus i had was fine then this other one i got has weak unlock button. newest 304k were better builts.
[Nexus 4 Original Android Development] thebryceee:
Dang. Comes with the territory I guess of mass producing.
[Nexus 4 Original Android Development] wilee1928:
I'm just having the best battery life in a LONG time, everything is ON and Stock. Thanks for all the hard work Franco!

~ NEXUS 4 Stock/Rooted & franco.kernel r134 ~
[Nexus 4 Original Android Development] drawde40599:
Using swiftkey here with no such issue, i send 100's of texts /emails a day no lag. Strange
[Nexus 4 Original Android Development] blakmazk:
How did you get the 0b/s on thr staus bar?
[Nexus 4 Original Android Development] drawde40599:
After 2+ hours of constant use OC at "1700" youtube, games, internet, texting...... Phones still cool barely warm.

How u make it do this Franco :P. Loving 134
[Nexus 4 Original Android Development] blueren:
A couple of days ago someone suggested an idea about implementing something similar to Intel turbo boost.. seems like a very elusive idea! Franco, what do you think?

Sent from a Nexus
[Nexus 4 Original Android Development] justanut:
You mean like faux's kernel? Lol..
[Nexus 4 Original Android Development] blueren:
I do not know. Haven't used Any kernel apart from franco's. Just that the idea is nice.

Sent from a Nexus
[Nexus 4 Original Android Development] Mercado_Negro:
Do you mean this (second reply on his post)?

http://xdaforums.com/showpost.php?p=40900413&postcount=27935
[Nexus 4 Original Android Development] franciscofranco:
I did some changes in the Hotplug driver during my airplane trip which boosts performance again and minimizes the amount of online/offlines on the cpu1. I will post the diff in a bit for some theorycrafting. Runs great on my device so far.
[Nexus 4 Original Android Development] dusk1911:
Just got my Nexus 4 and installed the kernel and already feel the difference :) , now just one question. i feel the colors washed out a little bit. is there a control for this that i am missing ?
[Nexus 4 Original Android Development] CamoGeko:
Yes you're missing Franco's kernel updater app.

Find it on play store. ;)

Sent from my Nexus 4
[Nexus 4 Original Android Development] gee2012:
Yes, open the Franco Kernel Updater app and go to color settings. open gamma control and click recommended values. Set screen brightness to 50% manualy. Colors should look better now ;)
[Nexus 4 Original Android Development] benblb:
That's awesome! I hope that I have the same experience with r20. So far it's quicker than r19, but the battery is draining a bit faster. I'm now at 34% battery after 14 hours of use. I only have 1 hour of screen time though. Stock ROM. Does anyone think it's possible that I have a device with a faulty battery? Every Android phone I have ever owned has had a bad (defective) battery. Just my luck.

EDIT: Auto brightness with stock ROM. Used r19 today.

---------- Post added at 09:13 AM ---------- Previous post was at 09:13 AM ----------

I'm still rocking my HTC Nexus One wall charger. No one makes chargers like this anymore. I love HTC.
[Nexus 4 Original Android Development] drawde40599:
WOW Really ?

---------- Post added at 12:16 AM ---------- Previous post was at 12:14 AM ----------

Test agn after FULL charge

---------- Post added at 12:21 AM ---------- Previous post was at 12:16 AM ----------

That's all the info your going to share ? Bricked a Nexus? , i don't c that possible
[Nexus 4 Original Android Development] benblb:
Fair enough, but I'm still worried that I may have a defective battery. I have put a lot of effort into exactly mimicking what some users here have done, and I'm getting half their battery life if that. Is there any way for me to check this out? I have checked the developer menus and the phone is reporting that the battery is in good health. Anything more in-depth that I could post?
[Nexus 4 Original Android Development] ploopower79:
Merry Christmas Franco and xda peoples! Thank for all the hard work man
[Nexus 4 Original Android Development] martiii:
The performance on r20 is very impressive! So smooth Thanks

Sent from my Nexus 4
[Nexus 4 Original Android Development] Locksmith81:
Wrong thread.... Ask in faux thread :what:
[Nexus 4 Original Android Development] gt-kingz:
The problems must be ur apps. Check with cpu spy.