yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] CaspaTheGhost:
Spelt correctly mate, most in his own thread couldn't get it right so :thumbup:

Myths will live as long as we let them breed freely.

Mobile reception has a massive effect of battery life. I've never had a lovely continuous green signal stat like that.

2G, that'll explain it then.

Flash, forget, profit.

Never judge battery life on small chunks as its disproportionate, but as someone else mentioned you're actually on track for 5hrs.

Its always Colin Cross.

Your talking about two completely different things, the RGB of the screen and the LED.

Sent from my Nexus 4
[Nexus 4 Original Android Development] ptrm2:
I just updated to 15 a couple days ago now getting ready for 16 and 17 is out holy crap
[Nexus 4 Original Android Development] :
Just wanted to say thanks, bought the app and am running r17 and noticing better battery life right away, and I'm sure it'll get better after I actually calibrate it. My color balance seems a bit more blue but i've got some reading to do on how to make it look more stock.

Feels great to have a phone with actual dev support! :good:

Thanks again.
[Nexus 4 Original Android Development] estallings15:
No calibration is necessary. It's a placebo.
[Nexus 4 Original Android Development] trailblazerz11:
From what ive read, Calibration can help the accuracy of the battery % but it won't affect actual battery life. It is all in these 'smart batteries'..

that said calibration is unneeded after flashing a kernel/ROM. Maybe once every couple months, so your phone knows the mV value that is 0% and that it should shut down at to preserve the battery.
[Nexus 4 Original Android Development] estallings15:
Flash at 100% and let your phone drain to 0% once in awhile (like you said). People who flash, charge their phone to 100% and wipe battery stats kill me.
[Nexus 4 Original Android Development] Simer03:
What colors do you use Franco? I remember you told me but I can't remember now

Sent from my Google Nexus 4
[Nexus 4 Original Android Development] albundy2010:
I suggest trying multiple settings to see what works best for you.

My RMA device came today. So i had two phones side by side with same kernel and same settings and had quite a difference in colors.
[Nexus 4 Original Android Development] Shnew:
Does the app need root permissions? Can I just install the kernel straight from the app?

Thanks
[Nexus 4 Original Android Development] albundy2010:
You need root to do most things with the app. Download and auto flash the .IMG yes. Download the .zip then manually flash it in custom recovery you don't.
[Nexus 4 Original Android Development] franciscofranco:
r18:

* New revision of r17's patch from Todd Poynor (Google)

* Another 2 more Interactive governor patches

* Compiled with Google's GCC 4.7 toolchain
[Nexus 4 Original Android Development] BRKotucs:
Thank you Sr! Will report back in a few...

EDIT: Flashing went great. Kernel feels fast and smooth..I will keep it at stock settings. I'll be testing it and report back to let you know how it's doing.

Thank you for the update ! Greatly appreciated...
[Nexus 4 Original Android Development] ceejay83:
Seems like the server is down

Edit: never mind it's up
[Nexus 4 Original Android Development] Underground_XI:
Do not go around the bush. Forget news articles, anandtech reviews and crap. Post me here your 6 hours screen on time with stock kernel on your phone and i will ship you my phone for free take it is yours. Until then you should keep mouth shut because users have every right to post their battery screenshots and be happy with 6 hours custom kernels give them. P.S By the way, what are you even doing in this thread, since stock kernel gives you same results as custom kernels?;)

---------- Post added at 04:05 AM ---------- Previous post was at 04:04 AM ----------

Franco wanted some discussion, thread was too quiet lol

---------- Post added at 04:06 AM ---------- Previous post was at 04:05 AM ----------

Franco wanted some discussion, thread was too quiet lol
[Nexus 4 Original Android Development] sirxdroid:
Is there a proper example for an init.d script until the latest features are exposed in the f.Ku app?
[Nexus 4 Original Android Development] Underground_XI:
Damn this tapatalk!
[Nexus 4 Original Android Development] franciscofranco:
echo X > path
[Nexus 4 Original Android Development] sirxdroid:
Does that survive reboots?
[Nexus 4 Original Android Development] franciscofranco:
No, that's why you need to add a script to init.d. App will be updated this weekend though.
[Nexus 4 Original Android Development] sirxdroid:
Cool, thanks. Let us know if we need to update the color profiles to change those pesky 114s and maybe other values that were not correctly saved by the app.
[Nexus 4 Original Android Development] freddysam:
I've done a lot of testing with the Nexus 4 using different kernels. The stock kernel and franco have vary similar battery drain with the screen on and the CPU being utilized. I got slightly worse results using faux, but the truth is that SOT isn't going to be effected much by the kernel. The screen (even at it's lowest brightness) consumes the majority of the power when the device is awake. The kernel can't change that. And if you are doing a task that requires a lot of computing power, the CPU is going to be burning through your battery no matter your kernel. Under-clocking your device will only slow down your device and cause it to take longer to complete any task. With the screen still consuming the same amount of power, under-clocking will only hurt your SOT.

Where I have noticed a difference in power consumption is with the idle power drain. If a kernel can quickly and efficiently perform simple tasks and put the phone back into deep sleep, then you are going to see drastic improvements in the standby time. This is where Franco's kernel has a clear advantage over stock and faux. The problem is, the more SOT you have, the less the standby time matters. If you lose 4% battery overnight but then use up 50% playing games in the morning, it really won't change things if you switch to Franco and lose only 1% over night.

That's my experience anyways.

Also, the amount of SOT you personally get depends on the programs you have installed. It doesn't make sense to compare SOT between two different Nexus 4s running different apps. You have to compare the SOT on your device with stock vs Franco. Try it and you'll see that you'll get basically the same SOT.
[Nexus 4 Original Android Development] michael_ta315:
good point! SOT is nothing when someone is doing something who knows what half way around the world and comparing it to another person. One might live next to a radio station and get super reception while the other live in a middle of a desert. one might only use it for texting and calling, the other might running facebook twitter instagram and playing angry birds everyday. SOT comparison is fun, yes, informative? kinda but not much. Not unless someone really do a test between 2 nex 4 with exactly the same settings and hardware down to the core. nominal vs faster might be different. gosh weather could be a factor too since someone might live in the arctic and the other live in desert with crazy heat. :silly::silly::silly:
[Nexus 4 Original Android Development] Zainiak:
nothing to see here...
[Nexus 4 Original Android Development] franciscofranco:
Just pushed r119 with small fixes and improvements. No functional changes from r118, just mostly small things.
[Nexus 4 Original Android Development] simorangkir_dcs:
+1 this
[Nexus 4 Original Android Development] gianton:
Flashing now, r118 was the best so far both for speed and battery life.

Thanks for your hard work!
[Nexus 4 Original Android Development] nachordez:
Trying it! :)

Do you ever sleep? ;)
[Nexus 4 Original Android Development] franciscofranco:
r119 should be the same, was just fixes :)

Nope :highfive:
[Nexus 4 Original Android Development] toniexly:
ha,just downloading 118,netspeed here is terrible....now start over dl r119-。-
[Nexus 4 Original Android Development] Mercado_Negro:
This post should be in the OP. It pretty much clears out many expectations we see around this thread. People see all these screenshots and wonder why they aren't getting the same results. It happened to me until I started thinking this through and it coincides with this explanation.
[Nexus 4 Original Android Development] dark_ente:
not on nexus 4 but I see someone posted controlled test with the Nexus 7 which show Franco has more than 50% battery life than stock

http://xdaforums.com/showthread.php?t=1889571

Your argument about screen drain the most power is invalid.

I believe if someone is patient enough to do with the Nexus 4, it should be the same here. Based on my experience with SOT anyway. with franco on wifi, I have 5 min/1%, with stock I have around 3-4 min /%, flipping through flipboard.

And also on anandtech, if they don't touch the screen then mpdecision doesn't kick in, hence the 6 hours battery life.
[Nexus 4 Original Android Development] Zainiak:
weird problem: Can't get a signal no matter what i try. And every time I reboot, I end up stuck at the boot logo. Not a rom problem for sure. tried rasbean and cfx. If I want to boot, I have to flash the rom again
[Nexus 4 Original Android Development] franciscofranco:
I flash a gazillion kernels every day, I never have signal problems, I never have bootloops other than the ones I know I'm causing. Sorry, its on your end.
[Nexus 4 Original Android Development] Zainiak:
yup. you were right (as expected :D ). Problem just went away after flashing and booting 3 times.
[Nexus 4 Original Android Development] casonswag:
Hey just wondering do u really need to wipe cache and dalvik when flashing a kernel?

NEXUS⁴
[Nexus 4 Original Android Development] CrimsonSmear:
I maintain a link in my signature to my init.d script so that it is easily accessible to anyone that seeks up-to-date/original color profiles plus common/new control values.
[Nexus 4 Original Android Development] ceejay83:
no
[Nexus 4 Original Android Development] Mercado_Negro:
No, just install it and reboot normally.

Cheers
[Nexus 4 Original Android Development] casonswag:
Okay thnks just making sure

NEXUS⁴
[Nexus 4 Original Android Development] GFXi0N:
Ok, i dont know if this could be kernel related or what.... Tell me what you think:

I had a mini heart attack some hours ago: I just updated to r118 and was testing some Twrp skins. When i rebooted to recovery, my screen went white, with some darker vertical lines, and I had to force switch off the device. Then, after some seconds, i booted into bootloader, and some colors (the green android) were flickering..... I normal booted into the rom (cm 10) and i swear I could still see some flickering in the background with some colors... I freaked out and switched off. Then I tel the phone rest for some seconds, booted again and didn't see any strange behavior anymore..... The he'll just happened? Any idea if it's kernel related, rom related or hardware related?

My phone is like 3 weeks old and today I have been playing real racing 3 like for 2 or 3 hours directly plugged to the ac. And some frontline commando.....
[Nexus 4 Original Android Development] jcmaddox1:
Uhm... >.> I think your app might be going a bit crazy.
[Nexus 4 Original Android Development] Koraboros:
Hmm you really should not play games while plugged in... that will likely kill the battery faster, and the charging heat + gaming heat could've caused something to overheat.
[Nexus 4 Original Android Development] franciscofranco:
As soon as you leave Android OS the kernel has nothing to do with any of your possible issues, thats one point.

Second point is... don't play for 3 hours connected to AC, you'll destroy your phone due to heat if you do this in a regular basis. I think you experience a side effect of prolonged heat - its just a guess though.
[Nexus 4 Original Android Development] franciscofranco:
Its absolutely fine here. I hope you're running r118 in 4.2.2 and not 4.2.1...
[Nexus 4 Original Android Development] yoyoz808:
Franco, whatever fix you did works really well on r119. Not having those stutters and the hotplugging seems to be working perfectly.
[Nexus 4 Original Android Development] blueren:
All this while, i've left the kernel in its default settings. Thought I'd do some tinkering with things.

I'd like to know what each element does in GOVERNOR CONTROL. Where can I read about it?.. How it affects n stuff.

Also things about underclocking voltages.

Any place I can get a head start?

Also, are the default voltages same accross all users using FK? Or is it dynamically set by reading things from each phone?

PS: I did use the search option on this thread. Nothing found in particular.
[Nexus 4 Original Android Development] fozzie:
It's a bit sad that people actually spend 6hrs a day (or even over 2 days) looking at their phone's screen. Don't these people have work or studying to do? It's no wonder the global economy has gone up sh1t creek!

#justsaying
[Nexus 4 Original Android Development] ragnarokx:
2/10

Sent from my Nexus 4
[Nexus 4 Original Android Development] FaithCry:
Some people work as software testers and spend all day looking at phones. Work for them is looking at their phones. Same with app developers and people who can't carry around a laptop everywhere to reply to emails from work etc.

Just saying. :P
[Nexus 4 Original Android Development] :
I've managed to get 6hrs SOT or pretty close to 6 on just about every kernel I've used when I'm at home, outside my house it's impossible, I have great signal. I personally stopped bothering battery, I look for performance, features and heat management in a kernel, Franco app is convenient :D
[Nexus 4 Original Android Development] DarK_DemoN:
Here you are: http://xdaforums.com/showthread.php?t=2017715

Very good thread full of a ton of info on all the different governors available.

And from what I gather (mostly guessing) voltage levels are dynamically set by Franco in each release. The user then sets them to the levels he/she desires.

-Sent from that.... you know.... thing that sends these things-
[Nexus 4 Original Android Development] prioxxx:
I flashed 119 and seems very fast. Great work Franco

Sent from outer space
[Nexus 4 Original Android Development] simorangkir_dcs:
Agree, it's smoother then 118. If the battery life is as good as 117, will be amazing.

I'm on PA with default setting, interactive governor and -100mV (nominal cpu bin)

Thanks franco!
[Nexus 4 Original Android Development] blueren:
Quite rare to find someone who helps right off. Thanks.
[Nexus 4 Original Android Development] steviewevie:
I suspect that this is related to the issues where the sliders don't seem to work properly the first time you ever start adjusting them (and you need to slide them to min then max and then they work properly).

But feedback just saying "+1 r111 was better" is useless. Yes, I have written code myself. If you want to help the dev, then explain *how* r111 was better, e.g. where exactly you are seeing any slowdowns, how to reproduce it etc.

Sent from my Nexus 4
[Nexus 4 Original Android Development] franciscofranco:
The sliders are 0 because the value read from the file isn't one of the valid bytes so the slider just stays at the initial position. I'm currently making some changes to that code to at least show the value in the file, even if its invalid, but the sliders only roll on the valid bytes.
[Nexus 4 Original Android Development] ben_pyett:
When you get the time could you amend the app's load colour profile function to indicate the presence of invalid values on load and the adjust gamma sliders so that they also indicate on screen if the set value is invalid, in case the user doesn't change the value? Cheers

Loving latest 119, smooth and responsive, straight out of the box.
[Nexus 4 Original Android Development] franciscofranco:
Thats a bit more work than it seems. My initial code is not scalable at all and I have to re-write a big portion of it to scale it between valid and invalid bytes. Even displaying the values in the color dialogs required some workarounds because I made it to only show valid bytes. Time is short now so I'll do it the easy way, then with time I'll re-write it and make it pretty
[Nexus 4 Original Android Development] ben_pyett:
in which back to your hot plugging code, which has much greater impact if you find options for improvement,..... I'm personally more than happy with my color settings....so that can go to the bottom of the list. :)
[Nexus 4 Original Android Development] JaqaL06:
+++++1 i have posted two times and good to see that i am not alone :) please franco check thread and give us your magical kernel :)
[Nexus 4 Original Android Development] draginslygj:
suspended freq

i tried tweaking the hotplug settings but it keeps reverting back after reboot. do i need to change the permissions or something. need help!
[Nexus 4 Original Android Development] walkingmike:
Franco, 119 is super smooth.

And that's with a 125mV Undervolting.
[Nexus 4 Original Android Development] wirtzpeitz:
Since r90 or so I've had an issue with my lock screen. When a pattern lock is enabled the touch screen will occasionally be unresponsive when waking the phone. Entering the pattern a second time will always work fine. The problem seems entirely sporadic but occurs often enough to be a major nuisance. I reflashed the stock kernel and never experienced this problem in several days of use. The problem also does not arise without a pattern lock. I run the stock ROM. Any ideas?
[Nexus 4 Original Android Development] JNewms:
Unfortunately I have no idea what's causing that. I've honestly never had a lock screen issue, I've been using a pattern lock consistently for weeks without a hitch. Hopefully someone with more knowledge than me can help you.

Sent from my Nexus 4 using Xparent Skyblue Tapatalk 2
[Nexus 4 Original Android Development] ben_pyett:
I also use pattern lock and have done for months with zero issues always on latest Franco version..Guessing that this may be rom related? I'm on AOKP (see SIG always latest pub build) Do you have a screen protector?
[Nexus 4 Original Android Development] hospital349:
It's either a ROM issue or you'll find the a full wipe might solve your issue. If you haven't wiped for a while, bits of dried up crap stick to your anus, making it very itchy and unpleasant. It can also cause random bugs and glitches on your device!
[Nexus 4 Original Android Development] scream4cheese:
Ohmygoodness!
[Nexus 4 Original Android Development] adil_:
I've the same issue... I'm on PA BTW...

Sent from my Nexus 4
[Nexus 4 Original Android Development] ben_pyett:
try to see of the problem exists on stock or AOKP rom and Franco kernel

speechless.
[Nexus 4 Original Android Development] Puzzlegirl:
I've had a pattern lock for ages and the response is always instant.

Kernel's running great :)
[Nexus 4 Original Android Development] BrandoHD:
This seems to be some type of Nexus 4 hardware issue, it happened with me while on stock kernel during boot, so I don't think it is software related at all, it seems that sometimes the refresh rate of the screen gets thrown out of sync and cause flickering :confused:

I just left my device for a few minutes and the screen returned to normal after some time. and it has not happened since, and I have had this device for about 3 months
[Nexus 4 Original Android Development] Foxnov1990:
I know for a fact that one cause of that problem is "TouchControl" app.. Which the developer is rewriting atm because everyone is experiencing those kind of problems from late kernels. Also issues that the screen became unresponsive so they had to reboot. All that app.

---

So if you use that one. Just deinstall it and wait till his newer version comes out but if you don't have the app try the following workaround.

You can use Tasker (or if you don't have that app you can use Actions, there's a free lite version available: https://play.google.com/store/apps/d...29ya3NmcmVlIl0.) to disable Touch Control when a call is active and enable it afterwards automatically.

To enable/disable it:

To disable it run as a shell command:

echo disable > /proc/ponury/status

To enable it run as as shell command:

echo enable > /proc/ponury/status
[Nexus 4 Original Android Development] wathefak:
Nice image you have there
[Nexus 4 Original Android Development] iOStoAndroid:
Sorry, this might be a stupid Q.

I am on AOKP MR 1 - Build 6

I flashed the Franco kernel (stable build), i cannot see any control App.

Am I missing something?
[Nexus 4 Original Android Development] Pulsu:
Get it from play store.. :)
[Nexus 4 Original Android Development] LaboDJ:
Yep... FREE

PAID
[Nexus 4 Original Android Development] iOStoAndroid:
Thanks. That was quick

But there seems to just an updater, no control options? I tried the free one
[Nexus 4 Original Android Development] leader288:
If you want the controls you need to use the PAID app, or this https://play.google.com/store/apps/details?id=com.bigeyes0x0.trickstermod&hl=en
[Nexus 4 Original Android Development] Shano56:
Free one is just the updater. The paid one contains the kernel controls. Read the app descriptions in the play store.
[Nexus 4 Original Android Development] DrunkFuX666:
Hey guys a quick question... Just decided to try out Franco since its supposed to be the best... I'm not really looking for any performance enhancements, just looking for better battery life... I KNOW its a very subjective thing, but people who have tried both the M1 and the r119, which did they feel churns out the most battery life...?

Currently on Stock kernel with cm10.1...

Sent from my Nexus⁴
[Nexus 4 Original Android Development] Pulsu:
You have to try it by yourself.. :) I have tried both and there's no big difference.. Both are fast and battery friendly.
[Nexus 4 Original Android Development] emanuele1986:
Hi!

this kernel is already undevolted out of the box??
[Nexus 4 Original Android Development] techmatlock:
No.
[Nexus 4 Original Android Development] MikeRL100:
Yeah I know talk about quick. Bugs patched in a day or two. Yay! No issues here.

Sent from my Windows XP machine using ie6
[Nexus 4 Original Android Development] :
I used r118 for a day and was having an annoying issue, I use the same UV settings (-125mv with 384/486/1026 at -150mv) BTW, after a call the screen would take awhile to respond to touches

On r119 for a couple hours and it has been running without issue above, performance seems about the same
[Nexus 4 Original Android Development] Utini:
just bought your app. Lets hope for more and positive future updates ! ;)
[Nexus 4 Original Android Development] Loccy:
Franco will probably hit me, but if you're going to try out different kernels also try r111, which was a beast of a kernel - solid as a rock and great battery. That said I think r119 is the first keeper (for me) with the new hotplug driver. Working nicely on my device, for my use case, with my apps and on my mobile network. Your mileage may vary, which is why you should try them all.
[Nexus 4 Original Android Development] Hyflex:
Up hopefully I'll get a reply
[Nexus 4 Original Android Development] sandpappa:
So r119 is the best yet? I´m still on r110 because of the awsome battery! :)
[Nexus 4 Original Android Development] Arstoien:
I think you mean "kernel", not "ROM", but anyway. Franco said several times he's not going to include delayed notifications on wifi fixes and patches until Google release a fix for it. You have probably been ignored the last time because that's been asked many times in the thread.

As far as msm_hsic_host wakelock – mine's well under control. I don't know if Franco's done something to it since he reverted all related patches (back then I used to get ~17% wakelock) but now it's excellent. And I'm talking about 3g, not wifi.
[Nexus 4 Original Android Development] Pulsu:
You have to try it.. :) You can always flash back r110..
[Nexus 4 Original Android Development] meangreenie:
he already said no to it a while a go