yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] Shano56:
Oh ****.. I think we have a winner. Running r121 for 10hrs. 10hrs+ on battery and 4hr SOT. Also had Pandora running in the background for a while. On previous builds I would struggle to get 4hr SOT and if I was listening to music there was no chance for 4hr, now I got 4hr and still have 8% battery to spare. 121 is ****in smooth and great battery. Thanks a ton Franco! :D
[Nexus 4 Original Android Development] andyli1985:
OMG. This is my first time having no lags when scrolling in tapatalk and Facebook. (I know, they are bad apps, but still). r121 is ****ing smooth!
[Nexus 4 Original Android Development] thebryceee:
So...M2, yes?
[Nexus 4 Original Android Development] Shano56:
No, 121
[Nexus 4 Original Android Development] Bluewall:
Thank you mate, well appreciated :)
[Nexus 4 Original Android Development] vickpick:
man, how are you guys getting these crazy battery lives. The people getting 5+ hours of battery life make me feel like Nexus 4's have high variability in hardware quality, where some cpu's are well built and highly efficient and others are not.
[Nexus 4 Original Android Development] thebryceee:
:banghead:
[Nexus 4 Original Android Development] :
I don't understand the obsession with the M tag, just use the kernel and enjoy it, if you want to just change the name on the zip
[Nexus 4 Original Android Development] thebryceee:
More so for the non-flashaholics. It's easily identifiable.
[Nexus 4 Original Android Development] irishrally:
There is nothing wrong with your N4. It's all about individual usage, how the "phone" is set up, installed apps, sync frequencies, signal strength, screen brightness etc. ...
[Nexus 4 Original Android Development] vickpick:
Yeah, no I don't think there is anything wrong with my device. Just that there might be some quality variability. But I guess it's probably the usage style variability more than hardware quality.
[Nexus 4 Original Android Development] drawde40599:
Nothing wrong with your phone 2.5-4 hours is normal . but five + is easy , dim down your screen , stay on WiFi as much as possible use 2 g when u can , don't use sync , don't use background apps ,drop max freq , Lil stuff like that is how there doing it , I find it easier to just use the phone and keep a charger around .

---------- Post added at 10:45 PM ---------- Previous post was at 10:42 PM ----------

Yep , I think Franco could put milestone on worst bug infested build he has and people would say was the best because they love seeing that "m" human brain pretty fancy like that
[Nexus 4 Original Android Development] Bluewall:
I've spotted Franco in my town yesterday !

http://www.youtube.com/watch?feature=player_detailpage&v=Y7ixXVcPBHM

(Kidding btw :D but I know you're a big fan of Temple Run)
[Nexus 4 Original Android Development] jmudrick:
Some people may reduce max freq, I've not found it necessary to do so to get 6+ hrs SOT.
[Nexus 4 Original Android Development] vickpick:
I don't use my phone much, so even with the screen time I'm getting I can probably last 2 days w/o charging. I use about 1 to 2 hours of screen time a day.. 2 hours is max. But I keep all the sync on, GPS off, 4g when out, Wifi when home. I have pretty good signals in my city.
[Nexus 4 Original Android Development] :
Thanks for the reply. I guess I'll look for another ROM.
[Nexus 4 Original Android Development] fozzie:
Just change the settings back.
[Nexus 4 Original Android Development] rocklee80:
@franco

any chance that you could add wheatley governor? because in the governor controls it can change the min cores online and max core online? thanks
[Nexus 4 Original Android Development] franciscofranco:
I don't know where you got that info, but that is false and wrong.
[Nexus 4 Original Android Development] :
He probably misread this

He's referring to motley max online CPU and thought wheatley is what does that

Wheatley explanation is in the link though
[Nexus 4 Original Android Development] :
While that wasn't helpful to the max, it did made me Google and find the setting. Changed the McastBcastFilter from 0 to 3, lets see how it goes.
[Nexus 4 Original Android Development] rocklee80:
sorry if this was a false information but i only saw this picture at matr1x kernels forum that i attached now. and the description was that if you choose wheatley governor and go into the governor control you can choose the min and max cores. Didnt know that it wasnt managed by the governor itself. thanks :)
[Nexus 4 Original Android Development] fozzie:
The previous link to the github commit showed you what the (2) changes were, so there was no need to Google. You just needed to click & read ;)
[Nexus 4 Original Android Development] jan.ringas:
So both changes should be reverted?

"McastBcastFilter" back to "3" and "hostArpOffload" back to "0"?
[Nexus 4 Original Android Development] leader288:
How exactly do you measure stutter? XDA app? Cause it still lags while scrolling for me.

Sent from my Nexus⁴
[Nexus 4 Original Android Development] Vangelis13:
In settings, developer options, enable "force gpu rendering". That might help.
[Nexus 4 Original Android Development] CamoGeko:
Well yeah, is say that the heat issue is def solvable by UV'ing.

Sent from my Nexus 7
[Nexus 4 Original Android Development] ChaosChris:
Wow i am very impressed. On r121 my n4 is much cooler than before and battery life has also improved! My n4 is idling at 21°C on HSDPA before it was at 30-35°C thank you franco wor your awesome work :thumbup:

Sent from my AOSPA3+ Nexus⁴
[Nexus 4 Original Android Development] myfluxi:
QCOM wifi config is in: system/etc/wifi/WCNSS_qcom_cfg.ini

Usually less packet filtering may lead to more wakeups (and hence wakelocks). As the QCOM firmware is a binary and not source, I'd start looking for more wakelocks with BBS or something. No reason to use another ROM, though as it's still just speculation.

Edit: Maybe the reverted ARP commit indeed causes an incompatibilty.
[Nexus 4 Original Android Development] vaibkulk:
Can anyone with Nominal Bin share their stable UV...

Thanks.
[Nexus 4 Original Android Development] steviewevie:
Every chip is different, even ones in the same bin. Don't use someone else's settings, experiment to see what works for your phone. Don't set the voltages on boot until you're sure they are stable.

Sent from my Nexus 4
[Nexus 4 Original Android Development] vaibkulk:
Just need it for reference...
[Nexus 4 Original Android Development] combatdeity:
Could someone post all the different bin voltages if they have them handy? I keep forgetting to note them down.
[Nexus 4 Original Android Development] monkey hung:
Don't know if this is kernel related but Is anyone else having battery charge problems in the latest build? I'm running Franco r121 with PA April 8 build and it's taking almost 2 hours to charge 3%. What's going on? I cleared cache and dalvik and still getting extremely slow charge times
[Nexus 4 Original Android Development] Foxnov1990:
Like a couple posts above me, it really depends on your specific phone.. but I get why for "nominal" as they start at 900, while Fast starts at 850 stock (if I recall right).

But I've been reading this forum for quite a while already and reading a lot of reports from -75uv to -150.. (both Nominal & Fast binned)

---

I'd say, start with -75 and work your way down until your device spontaniously starts rebooting or you notice fragments while taking pictures etc... (until you're really sure about that it's stable, only then click "Set voltages on boot"

Good luck

PS: for your answer, although I'm fast binned. Personally I'm on -75 and it's good enough for me. Could propably go lower but cba atm :p
[Nexus 4 Original Android Development] fozzie:
Yep - that would put them back to the stock values.
[Nexus 4 Original Android Development] ChaosChris:
No i am on pa and r121 too and dont have that problem

Sent from my AOSPA3+ Nexus⁴
[Nexus 4 Original Android Development] rocklee80:
maybe you just have a bad battery cycle. let it drain it to ~15% and shut the phone off and on and charge than
[Nexus 4 Original Android Development] santeana:
See? That really irritates me. And sorry if it's a little off topic, it just caught my eye. You're using 4g and you say you're getting decent battery and I see that a lot. Yet when I throw the old radio on and fire up the 4g, battery drain goes from 1%/hr up to nearly 4%/hr! No other changes. Just 4g. It sucks because I get better speed on that than I do through my router! =(
[Nexus 4 Original Android Development] :
He mentioned he has great signal that could greatly reduce battery drain, my home area I get 5 bars of 3G signal so I get great battery life and I'm always on 2G cause of Wi-Fi
[Nexus 4 Original Android Development] santeana:
Yeah good signal here too. But as much as I'd like to discuss it, it's going to wind up hijacking the thread and I don't want to do that. Just wanted to tell everyone who has 4g AND great battery at the same time that I hate them with a passion that burns with the intensity of a thousand suns. Lol
[Nexus 4 Original Android Development] ironjon:
Confirmed, I am in the same situation

PA + r121 running fast without any problem charging my device
[Nexus 4 Original Android Development] Luigiesin:
+1

Sent from my Nexus 7 \m/

ROM: PA 3.15

Kernel: Franco r55
[Nexus 4 Original Android Development] roi14:
anyone playing vector??? i've been experiencing stutters and lag on the game, all the settings are stock on fku except -50 mV. thanks!

other than that, certainly the best kernel for me. :D
[Nexus 4 Original Android Development] rocklee80:
i dont know why but with r121 i can undervolt -125mv each step and 1026mhz step -150mv on fast binned chip wihtout any problems so far. And so my phone is cooler than r120 and downwards :) On r120 and lower i could only -100mv undervolt. Very GOOOD!!
[Nexus 4 Original Android Development] vladm7:
I'm impressed. Far from every human can feel such a negligible difference in power dissipation, caused by 25mv voltage drop.
[Nexus 4 Original Android Development] BrandoHD:
Franco, I don't usually say much, but I must compliment you on r121, it is very smooth, and battery life seems to be better in my usage

I must also thank you for recoding Tapatalk and Plume, which is much smoother in my usage now. :thumbup: :p

Sent from neXus 4 using Tapatalk 2
[Nexus 4 Original Android Development] dj_unknown:
Flash by mistake wrong franco kernel

Hello,

I flashed by mistake the N7 kernel.

So my N4 is broken. (I am unable to switch it on put it in recovery)

Is there any way to flash stock image ?

Cheers
[Nexus 4 Original Android Development] Martin_Ro:
Hm, quite unusual, afaik recovery has it's own kernel that has no dependency to the "normal" kernel, therefore it still should work to go to recovery. Pressed the right keys to start bootloader ?

Otherwise, maybe the wrong kernel killed something on the hardwareside :crying:
[Nexus 4 Original Android Development] mammenj:
Does the color of WiFi on the status bar and quick tiles has anything do with the kernel?

After flashing 121, WiFi icon color is always grey, not turning blue.

Anyone else having the same issue?

Edit: now working after dalvik wipe :confused:
[Nexus 4 Original Android Development] matesc:
Download stock image from here:

https://developers.google.com/android/nexus/images

See here how to flash it:

https://plus.google.com/app/basic/stream/z13tjpabvnjagfhvg23dw5jr5kuzf5yhz04

Ensure that you have the correct drivers for ADB to recognise your device. :p
[Nexus 4 Original Android Development] :
Since when is Franco recoding Tapatalk and Plume :confused: someone lied to you!!!!!
[Nexus 4 Original Android Development] aarif_ziaee:
does franco. kernel support slide to wake ???

coz i am using motley kernal as previously i tried franco but slide to wake was not working
[Nexus 4 Original Android Development] scream4cheese:
No. There is no such function in this kernel. It will not be added either.
[Nexus 4 Original Android Development] Roxxas049:
It wouldn't be up to Franco to support slide to wake, it would up to the developer of S2W to support new kernels and it's features. That said, try touch control in the play store. If it works then yes, if not go bug the app dev.
[Nexus 4 Original Android Development] GFXi0N:
Just want to say: As long as I'm not using the phone, the battery usage is practically null... Incredible..... and I just flash and leave stock settings! (CM10.1 nightly)

Nice kernel and getting even better time after time :)

Congratulations.
[Nexus 4 Original Android Development] Dody83:
Now I UV -125mV and set gamma as recommended values: the colors is very nice, the battery usage in deep sleep and the heat are very very low!
[Nexus 4 Original Android Development] santeana:
I think he was joking. He just means it's smoother than ever =)
[Nexus 4 Original Android Development] Net.silb:
I have my 384 MHz on 700 mV (-150 mV) and I tried setting it to 675 mV (-175 mV) but every time I get out of the voltage screen and back in, it resets to 700 mV. When I try changing my 486 MHz from 725 mV (-150 mV) to 700 mV (-175 mV) it works. I've tried clearing the app's data and rebooting but no luck. Help?
[Nexus 4 Original Android Development] wathefak:
do you have any other kernel app installed? or init.d script set on boot?
[Nexus 4 Original Android Development] ÜBER™:
God no... XDA app is laggy. But definitely not as laggy on previous versions. Hell for the most part its smooth with its minor jerks and lags. But mostly I test with the android UI. Swiping the pull down and quickly hitting the settings to open the settings normally caused the animation to stutter. That is non existent now.

Sent from my Nexus 4
[Nexus 4 Original Android Development] hoseth0711:
What have you guys set your time_rater to? As far as i remember Franco recommended 50000 but i have also seen 35000 as the recommended setting
[Nexus 4 Original Android Development] blueren:
Franco added butter to butter to better the butter better. O_O yo dawg!
[Nexus 4 Original Android Development] yabdali:
I am running AOKP with Franco stable M1.

Can you suggest best battery life settings for for governor/IO scheduler?

Should I use ROM performance control or Franco app to do the settings?
[Nexus 4 Original Android Development] hospital349:
Default settings are pefect for battery life and performance, alike.
[Nexus 4 Original Android Development] Banished Angel:
On r121 the default is 30,000
[Nexus 4 Original Android Development] Net.silb:
No.

Franco, any clue?
[Nexus 4 Original Android Development] alanwyl:
I really like the 95 go hispeed load @ 1350 MHz, smoother in most of my usage.

Credits to the one who brought it up, I forgot who.:p

And for those of you having poor battery, I found out that removing the battery percentage text and icon helps.:good:
[Nexus 4 Original Android Development] alanwyl:
See?
[Nexus 4 Original Android Development] JoeBananas_:
Ok how? :D
[Nexus 4 Original Android Development] nachordez:
Amazing! r121 is terribly smooth. And battery as good as always!

Thanks, Franco.

Do you think it will be even better in next releases? You are being a very hard opponent... for yourself! ;)

Nexus 4, stock kernel, last Franco.kernel nightly
[Nexus 4 Original Android Development] alanwyl:
See the previous post
[Nexus 4 Original Android Development] paaaulo:
Yesterday TWRP had been updated to 2.5. I'm unable to flash kernel zip using Franco's app . After reboot to recovery it says 'unable to locate zip file'. It worked fine on 2.4.4.

Flashing manually on TWRP 2.5 works fine.
[Nexus 4 Original Android Development] yokuyuki:
I was pretty sure people here were above mocking others. Battery life posts here are really useless. Everyone uses their devices differently. One person may have a ton of google services syncing. Another person may run their device on the lowest brightness. This means you can't really compare battery life between each other's phones. So posting the battery life of your phone contributes nothing.

Anandtech and their senior smartphone editor, Brian Klug, are well respected in the community for producing highly detailed reviews and comparison tests between phones with a highly scientific and reproducible method. They test at a specific brightness and reload a webpage over and over again until the phone dies. This allows them to measure how the interplay between radio, screen, and cpu factors into battery life. You can't use this to directly compare to personal use as you have to account for the idle drain when you have your phone with you all day. Getting 6 hours on the wifi test on the Anandtech test doesn't translate to 6 hours of screen time in normal use as you're going to be idling your phone all day, but that doesn't mean the test isn't accurate. It's just that the test isn't meant to compare to normal use of the same phone; the test is meant to compare between phones to see how different phones handle the radio, screen, and cpu. However, if we're able to craft a similar test, it would be useful to test between kernels to see how different kernels affect the battery consumption of the device in an objective way.
[Nexus 4 Original Android Development] steviewevie:
Oh dear. Sorry but no, you have a hard brick there.

Sent from my Nexus 4
[Nexus 4 Original Android Development] scottx .:
It I tell the updater to download the kernel to a different place other than the default (/sdcard) when it reboots to TWRP it thinks the zip is in the default location and not the place I specified in settings. So it doesn't flash it and I have to do it manually.

And a profile.

Thanks Franco. You rock.
[Nexus 4 Original Android Development] Ok_Kaleidoscope5109:
lol okay... it's a controlled test. it may not be the best, but it's far better than User A talking about 7 hrs SOT and user B talking about 4 hrs SOT. You can't even compare the two because they have different usage patterns. And do you even know what accurate means? Are you questioning the validity of Anandtech's results or do you just have nothing better to say? Because while that test may not be perfect, it's far more "accurate" in benchmarking battery than any anecdotal evidence I see on this thread.

Certainly it's not the best test in gauging user habits, but it's one way of comparing Phone A against Phone B. It doesn't necessarily mean Phone A will perform the same way for a user, but it at least allows a user to gauge some aspect of battery in a controlled test. At the end of the day, we all know battery life is how YOU the user experience it. In your case Franco, I know you told us you turned off lots of things on your phone to get 1% drain overnight. Well others might not experience that because they don't want to turn it off. So yeah it will vary user to user and I wouldn't call Anandtech's test accurate in terms of determining what you might experience, but it's an accurate measure of screen drain and cpu drain, and to an extent 3G and Wifi drain when constantly being used.
[Nexus 4 Original Android Development] Prod1702:
If you can get into the bootloader you should be able to get back to stock.
[Nexus 4 Original Android Development] nellisere:
I'm pretty sure he put a sort of safety measure on the kernel so none of the frequencys can go below 700mV
[Nexus 4 Original Android Development] yokuyuki:
Yes, he did: https://github.com/franciscofranco/mako/commit/995fccbb92428eabd591000c088018d6cb312a2e

Also max voltage is 1300mV.
[Nexus 4 Original Android Development] jsylvia007:
Over here: http://xdaforums.com/showpost.php?p=40142747&postcount=9455

There was discussion that if there isn't a kernel patch, then battery life will suffer... I'm now worried that I'm going to be stuck with CM Kernel because Franco won't take the patch into his Kernel, and I could suffer from worse battery life.

I run both the latest CM10.1 nightlies and the latest Franco nightlies...

I guess, what I'm asking is, what is the current status on this? What are others in my same situation doing? I assume this is going to affect all CM-based ROMs, and I know I'm not the only one with this configuration.
[Nexus 4 Original Android Development] ÜBER™:
What did i say??? It was just a joke my god... and what did you do.. exactly what i said you would.. write a paragraph to prove your point. And im the one not contributing to the kernel by posting my battery results? Just an FYI, scrolling through UI and apps is much more CPU intensive than refreshing a page. So me actively using the phone and getting 6HRs SOT is better than stock. I would bet money that on the stock kernel... i wouldnt get but 4 hours.
[Nexus 4 Original Android Development] Ok_Kaleidoscope5109:
I don't want to get into a huge debate regarding this, but what's more important in saving power is making sure your CPU hits deep sleep and an idle state. This is generally how CPUs are made now. While the CPU draws massive power when on, it's about minimizing going to full load. You undervolt to squeeze a bit more battery and life out of it, but it's not going to be a night and day difference. In the end if you undevolt and you have something constantly wakelocking your phone or constantly draining 3G, your phone will die at similar rates to one that's not UVed.

I have yet to see someone stress test their CPUs at different voltages and post temperatures say 30 minutes in the test and show remarkable difference. It's not going to be 70C versus 50C. It's going to be a minor difference.
[Nexus 4 Original Android Development] walkingmike:
You need to take your debate to a different thread. It doesn't belong here.

What you really need to do is take on all the different kernel threads and chalenge every one of them to that Anandtech benchmark.

---------- Post added at 04:22 PM ---------- Previous post was at 04:18 PM ----------

Yep, 121 is completely stutter free.

Same here. I tried -150mV and it was fine, but finally decided that -125mV is good enough in terms of battery so I thought I'd give the chip an extra +25mV

-100mV seems to be the universally agreed starting point.

I have no problems running up to -150mV. Haven't tried -175mV (maybe I should, just to see how it works), but I settled on -125mV.
[Nexus 4 Original Android Development] vickpick:
Easily fixable, fastboot and flash the stock kernel. If you can't just call warranty and they'll fix it. They usually don't mind as long as its a software issue which this seems to be. I did something similar but even worse with my epic 4G and sent it in to Samsung and they fixed it. What I had done had also actually destroyed my speaker, and they replaced it as well.

I knows its not the thread for it, but can anyone explain what binning does?