yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] sordna:
Well, you can see in the picture, that I turn wifi on for short periods (when I want to access email/etc), but most of the time (when my phone is on standby) wifi is off as well. Some battery saver apps work the same way (turn on wifi when your screen is on, turn it off automatically when your screen turns off). I'm sure you can get same battery life as mine if you start turning your wifi off when you don't need it! Unless you want to read email the moment it arrives, as opposed to reading it at your own schedule :)
[Nexus 4 Original Android Development] bruce7373:
Doesn't Android turn mobile data off anyway whenever Wi-Fi connected? Or is the radio still on, just not being used?
[Nexus 4 Original Android Development] Arstoien:
It's on, just not being used, which is the same as having the data off. You're still connected cause you need to make and receive calls.
[Nexus 4 Original Android Development] :
[MENTION=3292224]franciscofranco[/MENTION]

Changing up_threshold to 90 makes the ondemand governor insanely smooth
[Nexus 4 Original Android Development] franciscofranco:
Ok I think FKU is ready for production. Flo/Deb support has been added in preparation for FK later today and I didn't find any major bugs since last Beta. You guys gonna love this update (the ones out of the Beta channel).
[Nexus 4 Original Android Development] sordna:
Thanks! Can't wait, especially since I'm not on google+ and unfortunately cannot do beta or even review apps anymore.
[Nexus 4 Original Android Development] appro77:
How much voltage reduction can normally be applied across the voltage range without problems? Some say 100mv. Is that for all frequencies?
[Nexus 4 Original Android Development] jak3z:
if you got a FAST type of chip, -100mv across all works most of the times.
[Nexus 4 Original Android Development] zephiK:
i do -125 and its not a problem on fast. it varies on phones. even though you're on fast, someone can UV more on someone elses fast.
[Nexus 4 Original Android Development] jak3z:
I didn't say you can't do more than -100, but as far as I saw, all the fast chips can handle -100mv with no problems, I can even do -175mV on low freqs.
[Nexus 4 Original Android Development] JNewms:
I see what you're doing Franco. You're going to release the kernels after you update the app so we can all use FKU to update, regardless of ROM. Well played, sir.
[Nexus 4 Original Android Development] spacebar2011:
Just to make it clear, PA is tagged JSS but uses JWR kernels. Hope that's known. Do NOT flash JSS kernels on PA 3.99 or the later nightlies.

[MENTION=470754]Franco[/MENTION] - Build.prop from latest PA nightly if you want:
[Nexus 4 Original Android Development] JNewms:
I may be wrong, but it looks like he's making it to where his app will differentiate between the automatically, which should help remove user errors.
[Nexus 4 Original Android Development] emperatour:
which version must be installed on official 4.3 JWR66V ? srry i am new to nexus 4
[Nexus 4 Original Android Development] zephiK:
jwr hence your version is JWR66V......
[Nexus 4 Original Android Development] emperatour:
cant see the link :( its milestone 4.2.2 or cyanogen nightlies... so so sorry

is that stable than stock kernel?
[Nexus 4 Original Android Development] gdekatt:
boot-r182.img from here http://franciscofranco.minooch.com/Nexus4/4.3/

NOT any of the -JSS images.
[Nexus 4 Original Android Development] WielebnyRay_PL:
[

FRANCO, do you need tester for beta release your kernel or FKU? I tried begin to develop in Xperia X8 thread, so I'm not totaly noob so I can try to find bugs or something else for example testing new features;) IM REALLY HELPFULL:D

Also I've got idea(nothing new but I would like to try) for my nexus, how to increase performance without burning N4, but I need your opinion;D

If you are interested in, send me PW;)
[Nexus 4 Original Android Development] spider623:
Pa is jwr with some fixes from jss
[Nexus 4 Original Android Development] jak3z:
If you want to betatest FKU apply on his google+ community and then participate in the beta, as for kernels he is no longer sending private tests to anyone, he does the testing by himself.
[Nexus 4 Original Android Development] spacebar2011:
It's tagged JSS. That was my point. And the latest nightlies are almost completely JSS with some JWR parts.

---------- Post added at 07:38 PM ---------- Previous post was at 07:36 PM ----------

You're right. What I was trying to say is that as the ROM is tagged JSS, it might download JSS kernels automatically. PA needs JWR kernels.
[Nexus 4 Original Android Development] arlenwoot:
Odd. Someone posted a screenshot of their PA build prop and it showed it was tagged JWR, but yours is tagged JSS. So whose screenshot is wrong, or are they both right and ones just outdated?
[Nexus 4 Original Android Development] spider623:
It is the thread title in the forum is wrong, the g+ community members all know it
[Nexus 4 Original Android Development] zephiK:
The one posted first is old, http://xdaforums.com/showpost.php?p=45560036&postcount=46712 Fri Aug 23 (Tagged JWR66Y)

The one posted a page ago is the newer one... which says JSS15Q compiled on Wed Sep 11

So the new PA ones are tagged JSS15Q but uses a JWR kernel.
[Nexus 4 Original Android Development] spider623:
It's jwr, go to the g+ community
[Nexus 4 Original Android Development] arlenwoot:
Ahh makes sense. Didn't notice the build dates.

---------- Post added at 04:37 PM ---------- Previous post was at 04:36 PM ----------

Do you by chance have a link to where this is talked about in the g+ community?
[Nexus 4 Original Android Development] spider623:
https://plus.google.com/106366026288198338538/posts/UYBdmujNqsv
[Nexus 4 Original Android Development] fkrone:
Just downloaded latest official PA-Build available for Mako and had a look at the build.prop:

# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=JWR66Y
ro.build.display.id=pa_mako-userdebug 4.3 JWR66Y eng.molesarecoming.20130823.170622 test-keys
ro.build.version.incremental=eng.molesarecoming.20130823.170622
ro.build.version.sdk=18
ro.build.version.codename=REL
ro.build.version.release=4.3
ro.build.date=Fri Aug 23 17:07:51 BST 2013
ro.build.date.utc=1377274071
ro.build.type=userdebug
ro.build.user=molesarecoming
ro.build.host=build1
ro.build.tags=test-keys
ro.product.model=Nexus 4
ro.product.brand=Google
ro.product.name=occam
ro.product.device=mako
ro.product.board=MAKO
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=LGE
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=msm8960
# ro.build.product is obsolete; use ro.product.device
ro.build.product=mako
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=occam-user 4.3 JSS15J 737497 release-keys
ro.build.fingerprint=google/occam/mako:4.3/JSS15J/737497:user/release-keys
ro.build.characteristics=nosdcard
# end build properties

So no more confusion ;)

Fabi's nightly:

# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=JWR66Y
ro.build.display.id=pa_mako-userdebug 4.3 JWR66Y eng..20130911.000931 test-keys
ro.build.version.incremental=eng..20130911.000931
ro.build.version.sdk=18
ro.build.version.codename=REL
ro.build.version.release=4.3
ro.build.date=Mi 11. Sep 00:10:21 CEST 2013
ro.build.date.utc=1378851021
ro.build.type=userdebug
ro.build.user=
ro.build.host=fabiserv
ro.build.tags=test-keys
ro.product.model=Nexus 4
ro.product.brand=Google
ro.product.name=occam
ro.product.device=mako
ro.product.board=MAKO
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=LGE
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=msm8960
# ro.build.product is obsolete; use ro.product.device
ro.build.product=mako
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=occam-user 4.3 JSS15J 737497 release-keys
ro.build.fingerprint=google/occam/mako:4.3/JSS15J/737497:user/release-keys
ro.build.characteristics=nosdcard
# end build properties

So PA seems to be tagged like this.
[Nexus 4 Original Android Development] appro77:
How do I know if I have a fast chip? I'm assuming from what has been said that not all the Nexus 4 phones have the fast chip. Can someone help me out and explain? Sorry for the newbie question.
[Nexus 4 Original Android Development] drawde40599:
Went back to 176 jss just to see , im having better results than i did with 182 with battery, speed and smoothness, just all around , is it just me or anyone else notice this.
[Nexus 4 Original Android Development] spacebar2011:
So are we all clear about PA being tagged JSS but using JWR kernels?

And the nightly I'm running is only available through the G+ community, so I'm aware of that. It's 97% JSS with some JWR bits, not the other way round.
[Nexus 4 Original Android Development] ben_pyett:
You need to determine the binning of your CPU by reading this

http://xdaforums.com/showthread.php?p=35566840

Took like ten seconds to Google....
[Nexus 4 Original Android Development] arlenwoot:
Nope looks like PA is tagged JWR. Can you link to the nightly you're using? Couldn't find it in the g+ community.
[Nexus 4 Original Android Development] spider623:
Install a terminal emulator reboot the phone, start the emulator and type

su

dmesg|grep PVS

OR

read it from the franco app
[Nexus 4 Original Android Development] jimbohurt:
No need for the fancy stuff. Franco's app tells you in status what your CPU type is.
[Nexus 4 Original Android Development] appro77:
Ok, Franco's app is telling me that the CPU type is FAST. This morning I dropped all voltages by 50mv using Franco's app and I had a reboot shortly afterwards. Maybe coincidence or maybe the chip won't handle a 50mv reduction in voltage.

I've just reduced all voltages by only 25mv from stock and will see how it goes. Should all the voltages be reduced by the same amount?

Any comments or help are appreciated.
[Nexus 4 Original Android Development] Mantulis:
Not really... For example this is my setup:

384mhz: 700 mV

486mhz: 700 mV

594mhz: 725 mV

702mhz: 750 mV

810mhz: 787 mV

918mhz: 800 mV

1026mhz: 825 mV

1134mhz: 875 mV

1242mhz: 900 mV

1350mhz: 950 mV

1458mhz: 987 mV

1512mhz: 1000 mV

Faster binned chip.
[Nexus 4 Original Android Development] andyli1985:
The screenshot you showed is from an unofficial PA build by Ayysir. All official PA builds by moles are tagged as JWR.
[Nexus 4 Original Android Development] CatsAreGods:
I have a nominal chip UVed 100 mg across the board and it's rock solid.
[Nexus 4 Original Android Development] samuelrf:
i have the "slow" chip and I have undervolt -100 and I'm not experiencing any problem ;)

NEXUS 4/ PA 3.99+/ FK r182
[Nexus 4 Original Android Development] drawde40599:
There was a issue i thought on how 4.3 reported what chip was what , don't no if that was fixed? Your not missing anything by UV this N4 with this kernel anyways.
[Nexus 4 Original Android Development] spacebar2011:
Sure:

https://plus.google.com/u/0/111629271059352473969/posts/EkyMSTbHx1p
[Nexus 4 Original Android Development] appro77:
Thanks guys for the uv info. :)
[Nexus 4 Original Android Development] franciscofranco:
I'll be releasing FKU for production after I finish a league of legends match to chill out, then after its up I'll release r183, then r76 for grouper, then r1 for Flo. This will be fun :)
[Nexus 4 Original Android Development] ben_pyett:
Excellent, now I've finally made the step up to 4.3, I can partake in your new offerings....I'll look forward to incoming in the morning... then :D
[Nexus 4 Original Android Development] Doo Doo:
i'm so excited i can't wait till you release its going to be epic :D:D:D

thanks for all the hard work you do for us franciscofranco you da man bro ;)
[Nexus 4 Original Android Development] jak3z:
LoL you play league of legends as well? :D
[Nexus 4 Original Android Development] leets4uc3:
Its all about that CSS!
[Nexus 4 Original Android Development] mightybrick:
I have a slow/nominal chip, and I have it undervolted by 100-125 on all steps and it has been rock solid. No reboots, camera artifacts, or any funny business.
[Nexus 4 Original Android Development] sordna:
Now that you mention camera artifacts, the other day, I went from camera to gallery back to camera, and the camera was honestly looking like an old analog TV, with horizontal bands and snow. Anyone ever seen that on the Nexus 4 ? I'm undervolted by 100mv. Exiting the camera fixed the issue, but I'm wondering if it has to do with the undervolting now that you said that.
[Nexus 4 Original Android Development] mightybrick:
It could be. About the only way to tell for sure would be to see if you could reproduce it, then up your voltages a bit and then try to reproduce it again.
[Nexus 4 Original Android Development] karthi89:
So our favourite custom rom getting updated after a long time along with a update of our favourite custom kernel also with a huge update of fku. Dono whether it's planned or simply a coincidence. Love you guys. Thanks Franco and PA team.
[Nexus 4 Original Android Development] franciscofranco:
PA's Kernel has nothing to do with FK since 4.3, I haven't yet had the time to work with them on that part. But r183 is coming, rebooting now to linux.
[Nexus 4 Original Android Development] karthi89:
Take your time mate. Am just waiting to boot in to recovery :D
[Nexus 4 Original Android Development] appro77:
I'm a bit lost in the color settings in the Franco app. Is there any way to get more color saturation other than choosing the S4 profile? The colors on my screen are definitely not saturated enough compared to real life.
[Nexus 4 Original Android Development] tkalli:
r1 will just be for Flo, no Deb?
[Nexus 4 Original Android Development] JNewms:
I'm glad I'm back on a ROM that works with your kernel. Just got back on 182 a little over an hour ago.

I'm pretty pumped for this one.
[Nexus 4 Original Android Development] franciscofranco:
Go to Misc option and increase the saturation and lower the brightness maybe.

Works the same on both.
[Nexus 4 Original Android Development] LibiSC:
Please do not forget to push your changes to jwr branch :thumbup:

Enviado desde mi Nexus 4 usando Tapatalk 4
[Nexus 4 Original Android Development] franciscofranco:
I won't I'm gonna push a new branch though, current JWR branch is a bit ****ed.
[Nexus 4 Original Android Development] wvcadle:
Who's favorite ROM? You and your brother's? :p J/K.

PA's too watered down as far as limited features for me. I'm a Carbon ROM guy through and through.

And although I do try other kernel's here and there, I'm a Franco kernel guy too.
[Nexus 4 Original Android Development] LibiSC:
Goddammit... more cloning and patching for me then :beer:

Enviado desde mi Nexus 4 usando Tapatalk 4
[Nexus 4 Original Android Development] franciscofranco:
Sorry, have to do it this time :)
[Nexus 4 Original Android Development] spacebar2011:
A lot of people's...

:silly:
[Nexus 4 Original Android Development] tkalli:
Just checking. Thanks.
[Nexus 4 Original Android Development] SpasilliumNexus:
Just got the update :thumbup:
[Nexus 4 Original Android Development] wvcadle:
I'm happy that you like your favorite ROM. Just don't lump me into your 'we' group. :)

I'm happy with mine too!
[Nexus 4 Original Android Development] JNewms:
The update has hit all of my devices. I'm ready to roll now! Lol
[Nexus 4 Original Android Development] Bobtehblob:
Just installed Franco Kernel updater onto my flo. My body is ready Franco.
[Nexus 4 Original Android Development] franciscofranco:
Ok lets go r183, I hope the servers handle everything!

r183:

* Revert a lot of changes from r178 and r182 that were causing issues and some random reboots for some users. Only left the governor changes, the others are just gone.

* Coded a new GPU governor algorithm which I think works better than what it was there before. Now you can tweak the GPU on your own pace here: /sysm/module/msm_kgsl_core/parameters and there inside is up_threshold which when the GPU load is above this then it ramps the frequency one level; down_threshold does the opposite, when the load is lower than this the driver drops one level; sample_time_ms is the sample rate of this algorithm. Currently it samples every 100ms, so if you want faster poll just decrease the value. Faster will improve performance on battery life cost, increasing will poll less times, but will improve battery in the long run (this is good for non-gamers);
[Nexus 4 Original Android Development] jimbohurt:
Got the update just now. Stoked for r183!
[Nexus 4 Original Android Development] spacebar2011:
Awesome Sauce!! :good:

Btw, FKU update still hasn't shown up on my N4. :mad:

---------- Post added at 03:34 AM ---------- Previous post was at 03:32 AM ----------

Its okay, no one was pushing you into that lump.. Chill :)
[Nexus 4 Original Android Development] svnhvn:
My best morning!! Thanks [MENTION=3292224]franciscofranco[/MENTION]!!
[Nexus 4 Original Android Development] franciscofranco:
Obviously expect GPU control in FKU if this new algorithm is nicely accepted by the community.
[Nexus 4 Original Android Development] drawde40599:
Play store updated and installed just fine. New kernel downloaded and installed also just fine from app Thanks Franco.
[Nexus 4 Original Android Development] Bobtehblob:
Franco, governor is resetting back to ondemand upon reboot for me. This happened on r182 for me as well. Everything else sticks fine though?
[Nexus 4 Original Android Development] JNewms:
It is supposed to do that. He has been using ondemand as default in the last two versions.
[Nexus 4 Original Android Development] bryanlimy:
Thanks franco!! Running latest 3.99 rc1 PA and r183, didnt lost root this time!!
[Nexus 4 Original Android Development] Bobtehblob:
I know it's default but I still prefer interactive for my use. Just rather not have to change it every reboot but if I have to :)
[Nexus 4 Original Android Development] JNewms:
I see what you're saying. You have to check the box to set governor settings on boot.
[Nexus 4 Original Android Development] franciscofranco:
You're ticking set on boot right? If you use PerAppSettings the default system mode will automatically apply your governor after reboot.
[Nexus 4 Original Android Development] Bobtehblob:
Derp. Cheers guys :o
[Nexus 4 Original Android Development] karthi89:
[MENTION=3292224]franciscofranco[/MENTION] what can be the maximum allowable sampling time? Some value or range?
[Nexus 4 Original Android Development] tkalli:
Servers are fine. Downloaded in no time.
[Nexus 4 Original Android Development] jimbohurt:
My download flew! And it correctly downloaded jss

Thanks franco!
[Nexus 4 Original Android Development] JNewms:
Right now is a moment I'm very grateful to have been given a second N4. Got one for my iPhone loving brother, and he ended up giving it back... Lol. I'm testing for Slim on my backup, and running Franco with AOKP on my primary one.

With that said, FKU did great on flashing the correct kernel for me. [MENTION=3292224]franciscofranco[/MENTION] I remember you saying that you fixed the issue with the cpu being stuck at higher frequencies on interactive. Did you make any changes to ondemand as well?
[Nexus 4 Original Android Development] dmourao:
Just flashed the latest version. Thanks for your amazing job as always. Gonna be buying FKU next week. :thumbup:

Enviado de meu Nexus 4 usando Tapatalk 4
[Nexus 4 Original Android Development] Redneck Trash:
Downloaded like it was double parked.
[Nexus 4 Original Android Development] lotherius:
Any chance the Franco updater could become smart enough to download JSS on CM10.2 and not JWR?
[Nexus 4 Original Android Development] franciscofranco:
Well... theres no range, but lets see it this way:

100 = 0,1s

You can take your conclusions from that ;)

:)

Neps, it was a patch from CAF directly into the cpufreq driver that derped it.
[Nexus 4 Original Android Development] Redneck Trash:
Have you updated to 10.3?
[Nexus 4 Original Android Development] franciscofranco:
If you read the new update changelog you'll have your answer.
[Nexus 4 Original Android Development] JNewms:
Good to know. Thanks for the update man!
[Nexus 4 Original Android Development] svnhvn:
[MENTION=3292224]franciscofranco[/MENTION]: After i downloaded r183 (not auto flashing it), i tried to look for it in your file explorer, found it, bookmarked it, and give it a touch on the zip file. Suddenly FKU crashed, a pop up appeared saying that FKU crashed.

Just for yo know though.
[Nexus 4 Original Android Development] franciscofranco:
Yes, bollocks I forgot add some wrappers to protect from unwanted clicks. Since a .zip is not "readable" the function that I use to read from text files doesn't know what to do so it crashes. I entirely forgot to add some protections. I didn't add a "click zip and auto-flash in the recovery" option, but thats something to consider.
[Nexus 4 Original Android Development] Luigi_2:
any reason why franco ditched interactive for ondemand instead?

he doesnt want to maintain it anymore or ondemand is better now? :D
[Nexus 4 Original Android Development] zephiK:
Don't think franco ditched interactive, just he prefers ondemand. You can still choose interactive if you choose to do so. He added some patches and stuff that he noticed that was happening on flo's ondemand and since flo has the same processor as n4. It just makes sense.
[Nexus 4 Original Android Development] franciscofranco:
Not ditched, they are both maintained at the same pace and work just fine.
[Nexus 4 Original Android Development] JNewms:
I'm on interactive right now, and I can't believe how fast everything is! Every app I go into is almost scrolling too fast! Lol
[Nexus 4 Original Android Development] Andre_Vitto:
You can safely UV more in slow or nominal binned chips than in fast chips..?
[Nexus 4 Original Android Development] svnhvn:
+1. With Nova launcher installed my app drawer scrolling like crazy.
[Nexus 4 Original Android Development] JNewms:
You've got that backwards man
[Nexus 4 Original Android Development] sethyx:
sns_* wakelocks = during phone call.

I'd assume you had roughly 50-55 minutes of phone calls in the last 12 hours. Correct?

Btw the msm_hsic_host wakelock is back to 10-15% for me as well on r26-test. Data is stable.
[Nexus 4 Original Android Development] Godaemon:


Thank you guys that's right call duration was about 45 min.just flashed r26 recharging and report back :)
[Nexus 4 Original Android Development] manjee:
Hi,

I wanted to testimony what I thought impossible: near 6h screen on time with normal usage !! :D total time on is 28h and 20 min, with night on airplane mode

My settings: fast binned cpu, cm10.1, franco's r24, auto brightness, interactive (70/1026), row, mostly on WiFi, location off.

I watched a few streamed videos, 20 minutes of gaming, 30 min calls, news, xda, maps...

Simply amazing !! THANK YOU Franco!

Edit: made it to 6h! I usually managed to get 3,5 to 4h before test 24.
[Nexus 4 Original Android Development] shrubbery:
Hi - I'm using the r26 test kernel with stock ROM and still have 56min of msm_hsic wakelock during 5h.

Can I provide any logs that may be of assistance?

Cheers.
[Nexus 4 Original Android Development] Boergen:
For me with r26: 14h 38m since unplugged, 9m 45s of msm_hsic_host, so basically nothing.
[Nexus 4 Original Android Development] ctfrommn:
I concur....wakelocks are back in force for me on R26. R24 was by far the best recent for me. Hopefully a way to have low wakelocks AND no data issues for anyone is close to reality.
[Nexus 4 Original Android Development] MontAlbert:
Try Lux from the market... You can use it to make your phone learn your preferred auto brightness levels in different light/brightness settings
[Nexus 4 Original Android Development] dwang:
Just to confirm what other people have been saying, r26 fixes my mobile data drops.

Nice job Franco.
[Nexus 4 Original Android Development] veyka:
R26 is now working well for me (cm10.1, on 3 in the uk), wake lock it up, but not as much as r23.

Whenever you are using mobile data you will most likerly get some hsic wake lock, it just depends how much.