yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] svnhvn:
All default except 50k of UV-ing. Location services and auto sync is off though.

Starring: Mako

Also starring: Purity, ART, franco.Kernel, TWRP, 98/33, and XDA Premium 4 mobile app
[Nexus 4 Original Android Development] foxguard:
Thanks mate. Can you tell me what you top volt is? I'm not sure if I did -25 or -50. Mine shows.

384/750
[Nexus 4 Original Android Development] xtrymind:
Just curious, why sometimes after flash kernel i got 70 vibration amp and sometimes i got 100 amp, it not big deal, just curious :p
[Nexus 4 Original Android Development] zorginho:
yesterday r203 17h up and 6h SOT all WiFi a little gaming and a lot of messaging!

Inviato dal mio Nexus 4 utilizzando Tapatalk
[Nexus 4 Original Android Development] svnhvn:
Mine is 800. You UV-ing [MENTION=228037]100[/MENTION]k.

Starring: Mako

Also starring: Purity, ART, franco.Kernel, TWRP, 98/33, and XDA Premium 4 mobile app
[Nexus 4 Original Android Development] Gallardo994:
How's this kernel in games? Does it give lags in Asphalt 8 as I have with hellscore?
[Nexus 4 Original Android Development] yochananmarqos:
I've never once had lags in games, myself.
[Nexus 4 Original Android Development] :
True, I almost never experience lags, unless I'm emulating heavy games on PPSSPP. From my experience Crisis Core lags a lot for example. Persona 3 runs smooth most of the time.
[Nexus 4 Original Android Development] Xaeons:
I dunno, figure it was Lux, or something in Paranoid Android 4.0 Beta 3, so I reverted to PA4.0 Beta 2 and r201 (where I had 3 days batt time with minimal usage) for the meantime. Went to sleep and when I checked it was 6hrs awake again. I uninstalled Lux and will be checking tomorrow..
[Nexus 4 Original Android Development] foxguard:
Sorry mate. Not really sure, all I did was hit the -25 button but after a flash wasn't sure if had been reset, appears not seeing as I was another 50 below you not done any thing else as have no clue.
[Nexus 4 Original Android Development] svnhvn:
Franco's default lowest clock was on 850k.

Starring: Mako

Also starring: Purity, ART, franco.Kernel, TWRP, 98/33, and XDA Premium 4 mobile app
[Nexus 4 Original Android Development] bragih:
Wow, really?

Care to share your settings?

Seems hard to believe though, since you're getting about 50-100% more SOT than anyone else :)

Gesendet von meinem Nexus 4 mit Tapatalk
[Nexus 4 Original Android Development] gtanner00:
I got 6h 50min SOT on r201 but I was using Google play books and internet browsing for a long time. I use auto brightness but only a little bit of 3g data. Mostly WiFi.

I also undervolt by 150mv and have tracked down every last wake lock.

Other than that o simply flash Franco and remain on the default governor settings.

A typical day for me will achieve 5h SOT with a small amount of gaming, lots of web browsing, tapatalk, and RSS, and some Facebook.
[Nexus 4 Original Android Development] attaint:
It's easy to believe because it's ALL wifi, if it were more 3G he would get less SOT.
[Nexus 4 Original Android Development] zorginho:
stock Franco settings 100uv

all day with WiFi and good signal.

Inviato dal mio Nexus 4 utilizzando Tapatalk
[Nexus 4 Original Android Development] zoym:
color setting has never been remembered after reboot.

stock with franco r203.
[Nexus 4 Original Android Development] ken_alpha24:
Need help fasttt
[Nexus 4 Original Android Development] RealSlimShadyMC:
Isn't kernel related at all. Try rebooting the device.

---------- Post added at 08:33 AM ---------- Previous post was at 08:33 AM ----------

Are you greenifying your kernel controller?

---------- Post added at 08:34 AM ---------- Previous post was at 08:33 AM ----------

Are you greenifying your kernel controller?

---------- Post added at 08:34 AM ---------- Previous post was at 08:34 AM ----------

Are you greenifying your kernel controller?

---------- Post added at 08:35 AM ---------- Previous post was at 08:34 AM ----------

Are you greenifying your kernel controller?
[Nexus 4 Original Android Development] :
I'm using Lux as well, doesn't cause wakelocks here.
[Nexus 4 Original Android Development] svnhvn:
Lux never being a culprit for wakelocks no matter what kernel and rom i installed too..

Starring: Mako

Also starring: Purity, ART, hells-Core, TWRP, 98/33, and XDA Premium 4 mobile app
[Nexus 4 Original Android Development] Xaeons:
Yep it isn't, I updated my Nexus 4 plugin for lux, but I think I'm staying in r201 for now. I also updated PA to beta 3 and so far it's going smoothly..
[Nexus 4 Original Android Development] zoym:
never...
[Nexus 4 Original Android Development] alan-31:
Just got this phone.

I'm also seeing this using CatLog after doing the Franco kernel. I dont like it. Any way to fix that?

Also getting popups for a "themes provider has stopped". Dont know how to fix it. I have AOKP + Franco kernel. Trying other things.
[Nexus 4 Original Android Development] RealSlimShadyMC:
Ugh, read the thread. Use "SElinux mode changer" from the play store and set it to permissive to fix the popup. And most catlog issues from other kernels are just because they stop qualcomm's thermald and mpdecision from running
[Nexus 4 Original Android Development] Bill Gamble:
No, that's normal, don't worry about it.
[Nexus 4 Original Android Development] zoym:
still cannot fix the color and other setting when reboot. strange... it happens since r198.
[Nexus 4 Original Android Development] RealSlimShadyMC:
What ROM? colours work perfectly over here, using obsanitys AMOLED profile atm
[Nexus 4 Original Android Development] jegata:
Can someone please tell me the deafult values in Voltage Control? And recommend how much should I undervolt for better battery life? Sorry I am new but did not find answer in previews posts. Thanks in advance!
[Nexus 4 Original Android Development] attaint:
at 1512mhz it should be 1150mv.
[Nexus 4 Original Android Development] jegata:
What about at 384MHz ?
[Nexus 4 Original Android Development] attaint:
at 384mhz it should be 850mv.
[Nexus 4 Original Android Development] jegata:
I messed all up. Cane you tell me pleas at all MHz what should be ?
[Nexus 4 Original Android Development] attaint:
(mhz) - (mv)

384 - 850

486 - 875

594 - 900

702 - 925

810 - 975

918 - 1000

1026 - 1024

1134 - 1075

1242 - 1100

1350 - 1125

1458 - 1137

1512 - 1150

EDIT: An undervolt of -100mv should be safe and is quite common, but you should always just -25mv, test for a bit and see if it's stable, and continue incrementally.
[Nexus 4 Original Android Development] Lebo-Wog:
Dear Franco, i know u hate requests (there shouldn't be any as ur kernel is close to perfection), and especily this one....

BUT can your please please do something for people with a bad power button, double tap to wake or slide to wake or whatever, please, i don't want to change kernels because of my bad power button, Franco kernel is a part of the family now :p
[Nexus 4 Original Android Development] Bill Gamble:
You're in luck! Doubletap-to-wake (such as it is) is already there.

Edit: to enable it,

1. Enter the following in Terminal Emulator, after invoking "su":

echo 1 > /sys/module/lge_touch_core/parameters/doubletap_to_wake

Or

2. Run that in an init.d script (you may need the assistance of an app like "Universal Init.d")

Or

3. Use a root file explorer to change the "N" to a "Y" in that file

Or

4. Download Trickster Mod, go to the "Specific" tab and turn it on there.﻿
[Nexus 4 Original Android Development] albundy2010:
Do not worry about what the default voltages are.

If you changed them already just untick the set on boot option and reboot. The defaults will be restored after a reboot.

There are different bins of the SoC ( 4) in the nexus 4. Each have their own voltage table ( defaults)

Your stock voltages may not be the same as another users stock voltages due to this cpu binning.
[Nexus 4 Original Android Development] RealSlimShadyMC:
Undervolting table is unique to each chipset, you can undervolt as much your OWN CPU allows. Some can do -50, I can do -125. I'm lucky.
[Nexus 4 Original Android Development] Lebo-Wog:
Thank mate, you made my day, i never noticed it in trickster because usually there is an option for screen wake control...
[Nexus 4 Original Android Development] sordna:
Just note this feature is unstable, and sometimes causes the phone to crash. If it gives you problems, you can try solutions that wake up your phone based on the proximity sensor, such as Simple Cover Lock

or Automaton Locker which also supports acceleromater (shake to wake).
[Nexus 4 Original Android Development] yochananmarqos:
You can also use Touch Control:
[Nexus 4 Original Android Development] Sir_gpm:
But probably that will drain more battery?

Enviado desde mi Nexus 4 usando Tapatalk 4
[Nexus 4 Original Android Development] arik100:
does franco kernel support tap to wake?

how do i enable it if yes?
[Nexus 4 Original Android Development] RealSlimShadyMC:
TricksterMod.
[Nexus 4 Original Android Development] Bill Gamble:
http://xdaforums.com/showthread.php?p=49803574
[Nexus 4 Original Android Development] pa.pn2:
For me r28 is perfect

Smooth, solid, no datadrops at all

50% left, nearly 3h screentime, uptime 23h

Just awesome

The phone is so much fun now

Thx franco
[Nexus 4 Original Android Development] Nebucatnetzer:
Ah I know now where that's coming from. I'll keep looking though.
[Nexus 4 Original Android Development] pro.aggro:
Whats with the push message dropdowns like whatsapp and gmail?

I tried this: http://xdaforums.com/showthread.php?t=2072930 but it does not work for me.

On stock kernel it's fine.
[Nexus 4 Original Android Development] rmanaudio:
Thanks for a amazing Kernal. I have been testing since day one.

Only issue I have been having with the latest 28 release and 26 test one: is at night when i turn phone off for charging, in the morning I do not have 100% battery. It will only charge to around 80%. I have to turn phone ON and charge it again for 100%.

Stock ROM with latest r28.
[Nexus 4 Original Android Development] ssauger:
+1 Same for me (only on wifi), but on CM kernel no problem. Will use stock till its fixed.
[Nexus 4 Original Android Development] siscim23:
Had data drop on r28. Had 5 bars, saw it drop to 0 bars for about 2 seconds, then back up to 5 bars and resumed connectivity. Didn't have to go into airplane mode or reboot. last_kmsg attached for what it's worth
[Nexus 4 Original Android Development] z3nith66:
why do you turn the phone off? there's really no need for that.
[Nexus 4 Original Android Development] drawde40599:
Maybe not for u ,but it happens on stock kernel also .

---------- Post added at 08:58 AM ---------- Previous post was at 08:57 AM ----------

Have u let it completly die then full charge while its off ? Mine charges just fine with this kernel and AOKP ROM
[Nexus 4 Original Android Development] hallucynogenyc:
Just happened for the third time, I made a screenshot. Reeboot did nothing.

I'm gonna reflash again now :/
[Nexus 4 Original Android Development] alcurtis93:
Check seating of sim card and is it cut properly
[Nexus 4 Original Android Development] schizophrenia:
happens to me quite often on r28

just saying
[Nexus 4 Original Android Development] rbanaco:
Is happening for me too... the fix didn't work =/
[Nexus 4 Original Android Development] Ibsonic:
I'm back on R22.. Love the fastest build out there.. I known that this one is also not battery friendly as r28 but well it'd better then frozen lock screen after a phone call :D

Verstuurd van mijn Nexus 4 met Tapatalk
[Nexus 4 Original Android Development] hallucynogenyc:
Sim has been fine until r28, went back to r20 and it's fine again.
[Nexus 4 Original Android Development] Net.silb:
Hey Franco,

Just had a "fast reboot" - I was using the phone and it suddenly went directly to the boot animation and booted in like 2 seconds...

Last_kmsg attached.

Running CM10.1 latest nightly + r28

The Last_kmsg ends like this:

[ 813.345093] auto_hotplug: CPU1 up.
[ 814.527605] Restarting system.
[ 814.527819] Going down for restart now

No errors detected
Boot info:
Last boot reason: reboot
[Nexus 4 Original Android Development] franciscofranco:
Thats a userspace reboot, not kernel.
[Nexus 4 Original Android Development] kaiser_tytnii:
I have very similar result on CM10.1 nighties with everything on (including location sharing 100% on 3G; no google+ sync though; data connection is okay compared to the test kernels; no drop so far, just takes a bit longer to load from time to time...)

Am i doing anything wrong or different from each other? last_kmsg included as well... thanks franco and whoever could give any insight!

what are the chances of getting a defective battery....? to be honest...
[Nexus 4 Original Android Development] franciscofranco:
Ok. I'm very close stop supporting CM until they come out with a decent and stable build for Mako. I've been seeing **** coming from people using CM10.1 all the time, either its wakelocks or whatever **** it is. Thats one of the reasons I HATE about CM, they just pump out builds and everyone else gets ****ed up because of their crap. Maybes its a coincidence, maybe its not.

From this second I won't be giving any type of support if you're running Cyanogen mod roms on your device. If you're using CM and you have a random reboot and the /proc/last_kmsg says "kernel panic" I will help, if it shows whatever besides that I won't even reply to your post.

Have a nice day everyone :)
[Nexus 4 Original Android Development] HyperM3:
FWIW, AOKP build one has been running harmoniously with your r23.
[Nexus 4 Original Android Development] Duuuude:
Can't blame you! As a former Flash-aholic, I just don't seen enough benefit of CM10.1 over stock just yet. I read the Mako CM10.1 thread daily and the problems do not outweigh the benefits IMO.

Rock stable with Franco Kernel and Stock. ;)
[Nexus 4 Original Android Development] arik100:
hey i can't find the option to enable it... ):

the link doesn't work
[Nexus 4 Original Android Development] Bill Gamble:
Sorry, here you go: http://xdaforums.com/showthread.php?p=49803574
[Nexus 4 Original Android Development] LordDeath:
I noticed that only with this kernel I get a little sound disruption every time when my connectivity changes (Wifi to 3G). So going around the campus and getting connected to a new access point every few meters makes listening to music a little hard.

Did anyone else notice this with the franco kernels?
[Nexus 4 Original Android Development] _Behemoth:
Just install Xposed and GravityBox and use the Volume rocker to wake the phone!
[Nexus 4 Original Android Development] dapsANDpoundz:
How's that any different than just using the power button?
[Nexus 4 Original Android Development] svnhvn:
Just in case if your power button was damage.

Starring: Mako

Also starring: Purity, ART, franco.Kernel, TWRP, 98/33, and XDA Premium 4 mobile app
[Nexus 4 Original Android Development] sordna:
Anything that utilizes a sensor, including the touch to wake which utilizes your screen digitizer, consumes some extra battery.

Nothing comes free ⛵
[Nexus 4 Original Android Development] svnhvn:
How you achieve that?

Starring: Mako

Also starring: Purity, ART, franco.Kernel, TWRP, .98, and XDA Premium 4 mobile app
[Nexus 4 Original Android Development] dapsANDpoundz:
solid day
[Nexus 4 Original Android Development] faizo:
So after I had some battery drain issues with r203, I reverted back to r201.

The following settings are what I currently have:

- Data almost always off when screen is off. Use a widget to disable it prior to locking screen.

- Data is used around 60-70% of when screen is on, not always. Other 40-30% is used for text and calling.

- Partial sync is ON. Some apps are allowed to sync, anything that's very important. Facebook and exchange email is on a 1hour refresh interval. Gmail is on a push service. Most of Google services are on always sync.

- Location is off.

- Music is run for at least 30minutes. Screen constantly on to change songs, data remains off here.

- auto brightness

- ART runtime is enabled

- Touch Control app is used always (works well with this Kernel BTW!)

Results: new record! 4hrs SOT

Only thing remains is to tackle remaining wakelocks, "Power Manager Service" and "msm_hsic_host". These suckers, as reported by better battery stats take around 44 and 41min, respectively. They are tricky indeed.

This is the best I have ever attained on a smart phone with mobile network and Data usage. WiFi was very very minimal.

If anyone has suggestions with those wake locks and r203, any is appreciated.

For now, I'll keep rocking this setup as it works!
[Nexus 4 Original Android Development] underskyzx:
Just had a reboot when I started Poweramp, logs attached.
[Nexus 4 Original Android Development] Dan1234567890:
I had problem with msm_hsci_host wakelock and it drained my battery. I learnt that it is connected with 3g signal strenght. I installled this (you need xposed): http://xdaforums.com/showthread.php?p=48720871

[APP] Intelli3G - 2G/3G/4G Toggle and battery saver for stock android

** This app will only work on ROOTED Stock Android 4.1+ or AOSP ROMS ** <br />

** Xposed framework is required http://xdaforums.com/showthread.php?t=1574401 **<br />

** N......

And not only that this wakelock disappeared, but it gave me cca 20% more battery, more that I managed to do with any kernel tweaking/installing or anything else that I tried which affects battery. :thumbup:
[Nexus 4 Original Android Development] yochananmarqos:
Thanks for actually sharing details about your daily usage paired with your battery screenshots. Most don't but probably turn off everything that makes a smart phone useful. The two wakelocks you mention are normal. 44 min is nothing over the span of hours of usage. The only wakelocks that should be addressed are misbehaving apps, but since 4.3 the exploit some apps would use is no more. Of course we monitor what's using our batteries to get through the day without charging.

Thanks to the awesome Android community here on XDA I've learned a lot.

Thanks Franco for blessing our devices with your creativity & know-how!
[Nexus 4 Original Android Development] :
This is a good option and it does solve the hsci_host wakelock. I suffered from it a lot and found the following 3G Manager app to be particularly helpful, since it disables 3G completely when screen is off. You can, however, choose to turn 3G on for a minute to get notifications once every 15min, for example. Great app, very recommended.

https://play.google.com/store/apps/details?id=com.falsite.ggovernor

Intelli3G is also a good option, I just decided to turn my 3G off completely and not revert back to 2G.
[Nexus 4 Original Android Development] _artem_:
r203, UV -100mv, everything else default
[Nexus 4 Original Android Development] cpanos:
thanx for the info, oohhh the choices... ART or xposed... smoothness vs customization :rolleyes: I wish they made xposed ART compatible.
[Nexus 4 Original Android Development] svnhvn:
Exactly. After surfing with ART for quite some time, i feel sooo reluctant to come back using Dalvik.

Wish they too..

Starring: Mako

Also starring: Purity, ART, franco.Kernel, TWRP, .98, and XDA Premium 4 mobile app
[Nexus 4 Original Android Development] churchmice:
Init.d scrpits are not workng in r203, and I found no hook in init.rc.
[Nexus 4 Original Android Development] Bill Gamble:
Since the first Franco KitKat kernel, the only way init.d scripts run for me is with the assistance of an app like Universal Init.d.
[Nexus 4 Original Android Development] churchmice:
Thanks for the confirmation, could not grab my computer right now. I would like to extract the boot.img and add the missing lines in init.rc to make it support the init.d scripts tomorrow. Just curious why such a simple yet important featute has not been implemented yet.
[Nexus 4 Original Android Development] Bill Gamble:
[MENTION=3292224]franciscofranco[/MENTION] is this something you could remedy?
[Nexus 4 Original Android Development] mymeatb18:
There is an app in the play store that I have that doesn't require root and works in art as its a very simple.

It turns off my data when screen off and turns on when screen on. Best thing ever.

I'm using pa and data switches back on faster than in stock.

Its called auto data off on
[Nexus 4 Original Android Development] svnhvn:
Thanks mate. Downloading now.

Starring: Mako

Also starring: Purity, ART, franco.Kernel, TWRP, .98, and XDA Premium 4 mobile app
[Nexus 4 Original Android Development] alan-31:
Things like this and others like the popup errors fix (SE linux app for permissive/enforcing) should be on the wiki. I will try to add stuff there.

(My bookmark to check later.)
[Nexus 4 Original Android Development] Dan1234567890:
I learned recently that even though you turn data off, you are still connected to 2g or 3g, only data is disabled. So if you are doing it to preserve battery, you should first switch to 2g and than disable data and stay on 2g.

If you just disable data and stay on 3g, you will only save battery regarding the fact that you are in fact, in sync off mode, but if you really want to boost your battery, you should be on 2g, regardless of data on/off. :thumbup:
[Nexus 4 Original Android Development] faizo:
This is cool. Question though, when you say turn off Data, I understand it like "turn off 3G/H" but texts and messages will still work. Correct?
[Nexus 4 Original Android Development] NYLimited:
Text messages (SMS) do not need data so they will keep working. Email, MMS, sync will not work.

---

Any clod can have the facts, but having an opinion is an art.
[Nexus 4 Original Android Development] :
I know this is Franco's thread but it is the only thread I'm following at XDA, so I actually want to say thanks to everyone who talked up ART in this thread, it's because of you I made the transfer and oh my, the difference is extremely noticeable. Great speed & great battery (better than before, actually). The only thing I'm missing is my Timely Alarm Clock which apparently does not work with ART.

Awesome!
[Nexus 4 Original Android Development] ranasrule:
do the 4.3 kernels have FUSE:Filesystem in Userspace support ?
[Nexus 4 Original Android Development] Bill Gamble:
FUSE has been present since 4.0:

http://xdaforums.com/showthread.php?p=47433066
[Nexus 4 Original Android Development] Piemo:
Fresh install of beta3 with battery calibration and Franco m

kernel r203.

Is it normal that android system, android OS and play service have this high consumption? Is there a way to reduce it?

All 3G with 15-20 min plague and 10 real racing 3. To me it seems to much drain..
[Nexus 4 Original Android Development] :
With 3G, yes that's within normal. Especially if you boot with 3G on. At least, that's what I experience too.
[Nexus 4 Original Android Development] Piemo:
So just 2hr of onscreen? :(
[Nexus 4 Original Android Development] :
Yes. In my case, with non-stop 3G, I get 3 hours screen on time for about 6-7 hours of battery life. I don't know if this normal, but it's what I get.
[Nexus 4 Original Android Development] churchmice:
In case if anyone want to give franco kernel a try, I have modded the original r203 nightly version with the following changs:

1. Support for init.d execution.

This is done by callling sysinit from init.extra.rc, which will in turn call all the scripts inside /etc/init.d .

2. Replace /sbin/adbd with one extracted from the slim kernel so that adbd would run default as root.

Without this, I always got "copy failed due to permission error" when I try to adb push something to my phone, even it is targeted to the /sdcard. After some diggging, I found the adbd is running as user "shell", which does not have the permissiong to write to /sdcard/ .

3. Change ro.secure and ro.adb.secure from 1 to 0 so that an "adb shell" command would defaults to root.

In the case you don't have sysinit, please download the attachedment, extract it and replace it in /system/bin/sysinit, also make sure you have changed the permission to 0755, change the user to root, and group to shell.

My time is limited and the network is terrible here, so I could not make a flashable zip, sorry for that.

I only tested this in slimkat rc2.5 for mako and I hold no responsibility for any damage.

Flash at your own risk.