yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] Hanny:
hey guys miss u all, was being very inactive because of academic and irl stuffs, and didnt keep up my fps reports because per-app power modes allows total full power for all games on our phones :p

as in before the latest interactive (defaults) we got good battery life in exchange for the not-so-powerful gaming behaviour IF we are not setting a powerful power mode for that game, and this even applies to moderate games like riptide gp2 and beach buggy.

however this ondemand, even with the same hotplug threshold, is really cool. I don't comment on UI performance as many others may have done but I was expecting and waiting for one day that per-app power modes arent essential anymore for light/moderate gaming while the default settings can be good enough for them and THIS day has come :) :)

riptide gp2 running very smooth with 3 cores always on and 4th one on occasionally, the defaults ondemand 384/1512 threshold 60 has no noticeable difference with my previous (deleted) power mode with interactive 384/1512 hotplug threshold 10 (yes- it is laggy for my eyes if i play it with interactive defaults). of course per-app modes are still good there for those who prefer an ensured performance but for me i just love to test until the default settings can handle all different kinds of usage by itself ;) can be said as a restoration of the core functionality but maintaining the necessary improvements - nice job done franco!

then i went to test gtavc heavy road (yeah yeah my old good friend and im still keeping it for kernel testing lol) with everything defaults and the fps went down to 20 something, under system monitor's refresh rate the cores are 3x1512 + 1x1ghz most of the time, not sure whether the freqs are fluctuating quickly inbetween the 1 second or anything else. Next up i set min freq to 1512 so its 1512/1512 with other settings default then the fps went back to normal ones about 35 something which is as smooth as my previous power mode - interactive 384/1512 threshold 10. at least i can draw a conclusion that hotplug is really cool that 4 cores are there even with threshold 60. but then for the low fps at 384 min is it because touch boost isnt exist yet on ondemand? (driving requires constant touching so 1512 was supposedly active all the time in interactive even my min was 384 before)

oh one thing - if anyone recommend me to get rid of gta because its an outdated garbage with everything coded wrongly, please do - ill consider it and it saves me 1.5gb storage space :highfive:
[Nexus 4 Original Android Development] darthaled:
I noticed worse battery life in 182 than 181 and 178. I think 178 is the best I tried, opposite to many users for me was smooth and fast.
[Nexus 4 Original Android Development] danageis:
This... Look, I know you guys want me not to 'blame the kernel', but nobody comes to this thread to bash the kernel/dev, I am obviously using the kernel so why not try to post something useful instead of acting like you need to defend this kernel lol. Looking through BBS from yesterday, my phone had been kept awake while screen was off for over 4 hours, with the ENTIRE time of my listed partial wakelocks coming to around 2 minutes. So whether or not this kernel had anything to do with CAUSING the bad battery life, it is most certainly involved since it won't allow me to view the kernel wakelocks that were giving me such horrible life and I do not know of any other way to investigate issues like this aside from looking for wakelocks, hence coming to this thread looking for help...
[Nexus 4 Original Android Development] jak3z:
Glad to you see back Miasmic! :cowboy:
[Nexus 4 Original Android Development] fozzie:
Random reboot (kernel panic) on r182.
[Nexus 4 Original Android Development] Utini:
Do I need the JSS-Kernel for the latest PA 3.99 ROM ?
[Nexus 4 Original Android Development] jutley:
No just the normal zip
[Nexus 4 Original Android Development] franciscofranco:
Users having problems lately with device being awake for no apparent reason and some weird panics are you using the latest Chrome Beta version?
[Nexus 4 Original Android Development] yukkio:
Yes sir, I have a lot of wake locks. But I have sync off so it suppose that chrome doesn't sync anything, right?
[Nexus 4 Original Android Development] fozzie:
Yup. Gonna uninstall it and see what happens.
[Nexus 4 Original Android Development] jak3z:
Looks like something went wrong with the WiFi driver.
[Nexus 4 Original Android Development] pkelly517:
No Chrome Beta here.
[Nexus 4 Original Android Development] NYLimited:
I do have the latest Chrome beta installed (on both N4 and N7). Using your latest nightly on N4. No significant drain or wakelock issues. Stock, JWR66Y.
[Nexus 4 Original Android Development] danageis:
No, I have been testing out wakelocks seeing if it was something to do with Gapps, and unfortunately I'm not even sure those are an issue... I have been getting almost always awake without any listed partial wakelocks with minimal Gapps (I use cataclysm which doesn't have built in gapps, all are market downloaded) and also without any Gapps installed at all (aside from chrome and aosp keyboard) and still have the wakelock issues. But no I have never used chrome beta.
[Nexus 4 Original Android Development] franciscofranco:
Is it Google Services by any luck?
[Nexus 4 Original Android Development] theTqM:
For PAC did you just flash the 182 JSS .img? or did you follow the OPs full instructions for the AOSP 4.3 install?
[Nexus 4 Original Android Development] Utini:
just updated to 4.3 PA with franco kernel 182.. so color settings dont work yet ?
[Nexus 4 Original Android Development] franciscofranco:
Turn the display off/on...
[Nexus 4 Original Android Development] Utini:
Oh thanks :eek:

Well.. 4.3 feels slower than 4.2.2 ... wondering if that is cause STOCK > PA or just 4.2.2 > 4.3
[Nexus 4 Original Android Development] Lt.Win:
I've been using CM10.2 for a few days and I noticed random freezes. They last anything from 15 20 seconds.

Happening with anyone else? Should I try reinstalling CM?
[Nexus 4 Original Android Development] zephiK:
Its JSS with deadlocks. All JSS roms are affected by this. Use a JWR rom or hybrid or live with it
[Nexus 4 Original Android Development] Lt.Win:
Alright. Thanks for the quick reply.
[Nexus 4 Original Android Development] bkai:
Dead locks... it's a bug with 4.3 JSS as far as I know. In other words, it plagues all roms but I hear PA has integrated parts of JWR to fix this. Best we can do is either use PA or wait for someone (or Google) to figure it out and release an updated aosp.
[Nexus 4 Original Android Development] Krunk83:
Is there a setting in the Franco app to allow Wifi to still download things while the phone sleeps?

nexus⁴
[Nexus 4 Original Android Development] ROFLkopter:
I used to get them all the time with PA when they were using JSS. You're best bet is, as said before, using a JWR ROM. The 4.3 release seems to have been nothing but trouble for developers.

Nexus 4: Paranoid Android 3.99 - franco.Kernel r182 - Tapatalk 4!
[Nexus 4 Original Android Development] danageis:
I'm not really sure if I've checked in all the ways possible, but I don't think so. Nothing with google services is listed as draining battery in a significant way under battery settings in battery settings during the time I get the wakelocks, and only partial wakelock listed in BBS involving google is a 7 second GTALK one.

I have been trying other settings with FKU now though, and going back to interactive seems to alleviate the wakelocks. I'm not sure if this is placebo or what, but could the new ondemand patches from N7 be behind this? If it helps here is some info about my phone: Cataclysm 4.3 JWR66Y ROM, r182 UV -100mV, wakelocks occuring both with wifi and on mobile data (3G, no lte) and I have all location services turned off but sync on for gmail and a couple other Gapps.

EDIT: Also, I am running .33 radio. Would that have anything to do with it?
[Nexus 4 Original Android Development] akyboy:
Carbon with franco:

Battery:1d 15h

Sot: 2:54min

Calls: 43min

Remaining: 10%

WOW
[Nexus 4 Original Android Development] franciscofranco:
Nope. Just turn off Wi-Fi optimisation from the Wi-Fi settings.

Governors have nothing to do with that, its just placebo. Maybe your problem is the radio.
[Nexus 4 Original Android Development] BrandoHD:
Those wakelock issues could be Google location services, I think its now called NlpcollectorWakelock and NlpWakelock, they both keep the device awake for unnecessary amounts of time.

They seem to hide under the Android OS in the Android battery stats but in apps like Wakelock Detector (the one I use) I caught them redhanded.

I think they are attached to Location Services, after I deactivated Location Services on my N7, the wakelock disappeared, but apps like Google now lose some of their functionality

Sent from my Nexus 7
[Nexus 4 Original Android Development] yukkio:
I haven't enabled GPS or Wi-Fi GPS, also sync off but that didn't help.
[Nexus 4 Original Android Development] LibiSC:
You can build the kernel yourself with the kernel wakelock stats enabled in the config

Enviado desde mi Nexus 4 usando Tapatalk 4
[Nexus 4 Original Android Development] jmudrick:
Running same ROM and settings with plenty of brief google wakelocks as usual but no big deep sleep issues. Using 33/84 hybrid radio though.
[Nexus 4 Original Android Development] anwedr:
I know this is OT, but to chime in on the issue, I could not believe battery life was so poor after upgrading to 4.3 and r178. 9 hours since the phone is unplugged and battery life went down to 23%. I disabled Location Access completely under settings and now battery life is amazing. On r182 and after 9 hours of normal usage battery life is down to 79%. This was not the case for 4.2.2 where I was able to leave Location access on and Franco kernel would still give my device awesome battery life. Yes, it's also Nlpwakelock.
[Nexus 4 Original Android Development] Lt.Win:
I only just recently switched from 3.99 to CM to give it a spin. Guess I'm going back again. PA seems to be better and also they didn't have the deadlocks.
[Nexus 4 Original Android Development] franciscofranco:
Google Services also fúck me sometimes, I kill it like 10 times a day.
[Nexus 4 Original Android Development] cobyman7035:
Interactive is more smoother than ondemand ?

Via Google voice Δ |\|€×u$™ 7 FHD on Tapatalk²
[Nexus 4 Original Android Development] Andre_Vitto:
felt it too..my antatu scores are also lower.. but i'm not worried about antatu but yes device feels slower on 4.3
[Nexus 4 Original Android Development] cobyman7035:
What app is that? It's weird BBS doesn't show any kernel wakelocks on my nexus 4

Via Google voice Δ |\|€×u$™ 7 FHD on Tapatalk²
[Nexus 4 Original Android Development] drawde40599:
Battery life is worse on 4.3 for me on stock kernel, franco kernel, jwr, jss... Its 4.3 all around, i liked 4.2.2 for speed and battery alot better

---------- Post added at 07:47 PM ---------- Previous post was at 07:46 PM ----------

4.3 is slower (not talking about franco kernel just 4.3 itself
[Nexus 4 Original Android Development] franciscofranco:
I don't necessarily agree, but a lot of problems are coming from the Google Services. Android needs a serious improvement in the PowerManager department and how the OS handles Wakelocks and pending app requests in the background.

Unfortunately for Mako and for us Google/CAF is not using the latest Kernel Power drivers that for example Manta does. I don't know why to be honest. I tried merging them once but things went kaboom after I flashed it for reasons that I'm too tired to explain at the moment. Not saying that the problem is that Power drivers, but the newer implementation that is used on Manta is much improved from Mako's code (which is pretty old in that department). These drivers are responsible for the PowerManagement routines from the Kernel side, wakelocks, suspend etc etc. Also Mako doesn't have a proper idle-state scaling like Manta or Tuna does, and that is also a big letdown. With proper C-state implementation the device wouldn't need to use Hotplugging to reduce power usage. I could go on and on. If the new Nexus comes with a proper modem solution, not this USB crap that we have, I'm sure things will be so much better in the long run.
[Nexus 4 Original Android Development] tiru.adi13:
I keep having these random reboots once or twice a day on stock JWR66V+r178. Sometimes the phone even refuses to turn on after locking the screen and I have to switch it off and on again. Any help?

Sent from my Nexus 4
[Nexus 4 Original Android Development] philosophics:
Not sure what the problem is. Rocking r182 - jss and I get 13-14 hours out of a charge ondemand. Interactive, 14-15 hours. This is with 4.3 and I had half the battery life with 4.2 so I would have to say that you're doing it wrong. :)
[Nexus 4 Original Android Development] franciscofranco:
1 - we're past r178, time to flash a newer one

2 - no log, no fix
[Nexus 4 Original Android Development] tiru.adi13:
Okay, will try r182 and report back if I face any issues. Thanks :)

Sent from my Nexus 4
[Nexus 4 Original Android Development] Luigiesin:
I've had even better battery with 4.3 using PA and Franco 181 (Interactive).

I greenified all google store services aside from the google play... That helps a lot with battery since there are less Gservices running on the background... And when I need them I just open the apps and that's it... Don't lose anything.

I still have a lag on my notification bar when I'm using any app... Not on my homescreen.

Sent from my \m/ Nexus 4

PA + Franco
[Nexus 4 Original Android Development] Krayvon:
!

couldn't get 182 to boot on cm latest nightlies. didn't see anyone else with issues. hmmm
[Nexus 4 Original Android Development] Luigiesin:
Make sure you flash JSS Franco since you're using CM

Sent from my \m/ Nexus 4

PA + Franco
[Nexus 4 Original Android Development] Krayvon:
yup i did flash jss. i even tried fastboot flashing it lol
[Nexus 4 Original Android Development] Chris_n00bz:
I noticed that recently my nexus got really hot, like 64°, just by browsing with chrome under 3G connection. Anyone else with similar experience? Is there any other solution but UV?

---------- Post added at 11:36 AM ---------- Previous post was at 11:34 AM ----------
[Nexus 4 Original Android Development] franciscofranco:
Time for a beta for franco.Kernel updater - just pushed it to Google Servers.

We have a couple of additions and logs of fixes

* Added a simple and very non-bull**** File Explorer inside the Backup&Restore section. It lets you browse your device and flash a Kernel image from anywhere. You don't need to move a kernel.img to the backups directory anymore, just navigate, click and done. It also shows you the files contents if you click, for example, a text file. Its still in Beta but I don't plan to do much more with it, I was it very basic and easy to use without any crap;

* Added an option called "Prepare for OTA" in the Support section that basically reverts any changes to /system that FK might've done when you flashed it. Currently only for Tuna and Mako because Grouper and Manta are unaffected by /system changes;

* Added an option called "Prevent saved settings to load on boot" in the Settings section. It prevents the app to load the saved settings after boot if this option is ticked, but it doesn't wipe the application data. If you flash a new Kernel and you want to see the defaults this is the best and safest thing to do. Just click and in the next reboots (until unticked) your saved options won't load on boot;

* The "Automatic flashing" option is now ticked by default and it actually works so now when you untick it the device won't automatically reboot after you auto-flash;

* Fixed the bug that didn't let you change the Kernel settings unless you changed the Default System Mode, now you can change your frequencies, governor etc in their own sections and it will actually stick and it will update automatically the selected System Mode;

* The TCP Congestion Avoidance Algorithm functionality will now work if you don't have BusyBox installed;

* Updated the okhttp and libsuperuser libraries to their latest versions;

* Under-the-hood improvements to the Kernel download functions and the respective notifications that show the downloading progress;

* Improved how fetches for Kernel information from the server so that it doesn't starve the server. I plan to add a refresh button in the ActionBar either in the next Beta or directly to the production update so that if it gets stuck at "Fetching" instead of having to leave the section and re-enter it will just refresh the server query and get done with it;

* Made the Navigation Drawer a bit wider

This is a big update and it MAY have problems here and there. I've been testing it a lot and didn't find any big bugs, but you bug-hunters will surely find something that I didn't catch.

Google+ post: https://plus.google.com/u/0/106873500108976028532/posts/fMGV5ubksSm

Have fun guys!
[Nexus 4 Original Android Development] Luigiesin:
Try flashing your ROM again.. Let it boot and then flash Franco from FK app after cleaning data (FK). Something's gotta be stuck there.

Sent from my \m/ Nexus 4

PA + Franco
[Nexus 4 Original Android Development] Mercado_Negro:
Will this new feature "Prepare for OTA" be useful when switching to a different kernel?
[Nexus 4 Original Android Development] dsbrohan:
Having a weird problem, ran into some issues on PA and went to reflash. Reflashed PA and went to fastboot flash r182, (Redownloaded that also to make sure I had a new clean install) and fastboot was giving me errors. tried opening the boot-r182.img and it is saying its corrupt. iv'e tried redownloading multiple times.
[Nexus 4 Original Android Development] svnhvn:
Thanks [MENTION=3292224]franciscofranco[/MENTION] !!
[Nexus 4 Original Android Development] franciscofranco:
If that Kernel uses mpdecision yes :)
[Nexus 4 Original Android Development] Mercado_Negro:
Pardon my ignorance, may I ask why does it have to use mpdecision, specifically?
[Nexus 4 Original Android Development] arlenwoot:
The latest nightlies are broken. Flash 9/5 or earlier.
[Nexus 4 Original Android Development] philosophics:
How exactly are they broken? I'm using r182-jss (which is what you would use with cm) and no problems. Check the md5 or redownload. Can't use the app to dl/flash. Do it manually. Zip is easy, use twrp
[Nexus 4 Original Android Development] theclaytons:
Cm 10.2 nightlies are broken, not this kernel. This kernel is awesome.
[Nexus 4 Original Android Development] philosophics:
Oh. Glad you specified. Haha
[Nexus 4 Original Android Development] dsbrohan:
I can't seem to get a good download of the kernel. Every time I do I receive one that is corrupted and I can't flash it.
[Nexus 4 Original Android Development] gee2012:
Do you download from the minooch internet website or from the FKU app (autoflash or zip)? Me personaly i never had an issue with both of them.
[Nexus 4 Original Android Development] dsbrohan:
Hmmmm, I think my PC is the problem actually. Just used the app and flashed through cvm and it's fine. My PC however is telling me all of my .IMG files aren't mountable and that they are corrupt. Even after a redownload.
[Nexus 4 Original Android Development] UgoBoss:
I get random fc on Franco.kernel Updater is that normal ?
[Nexus 4 Original Android Development] wildestpixel:
Try clearing the apps data.
[Nexus 4 Original Android Development] drawde40599:
I couldn't get cm to boot on cm :P switch to chainfire SU , all my issues with CM went away after doing this
[Nexus 4 Original Android Development] steviewevie:
Kernel wakelock stats are disabled in this kernel.
[Nexus 4 Original Android Development] UgoBoss:
Already tried but nothing..
[Nexus 4 Original Android Development] franciscofranco:
I need the logcat...
[Nexus 4 Original Android Development] Redneck Trash:
[MENTION=3292224]franciscofranco[/MENTION] Do you see anything within ondemand that is beneficial for you to develop for or will your focus continue along interactive? Or do you plan to develop for both governors?
[Nexus 4 Original Android Development] Martin_Ro:
Android Logcat.... the upcoming Android Version after KitKat :silly::cool:
[Nexus 4 Original Android Development] franciscofranco:
I will maintain both. I plan on adding the thread migration notifier to Interactive this upcoming week. But I like to have two strong and well oiled governors, offers more choice.
[Nexus 4 Original Android Development] jak3z:
FKU beta works perfectly here, though I would make the file explorer font way smaller, looks too big to me. The option to not load config file on next reboot is awesome as well.
[Nexus 4 Original Android Development] 1ceb0x:
Hello Francisco,

Slimbean team has updated their base and compiled a beta 5 rom. They changed a commit in hwcomposer that allows the rom to run on JWR kernels (rest of the rom remains on jss base) (commit: https://github.com/SlimRoms/hardware_qcom_display/commit/99d44d266ba02ce2cee74fdde8eaca70ecb14167)

The rom boots only with your JSS kernel (and stock slim kernel obviously, but I want to use yours) but sutters everywhere (because of this commit).

A word from Slim's kernel dev

Is there a way we can make your JWR version to boot? I'm sorry, I cannot take a logcat of it trying to boot on JWR because I'm getting the "device is offline" message in adb.

Thank you!
[Nexus 4 Original Android Development] re4lsk:
There is a JSS version you can use, both JSS and JWR are the same kernel just made for each corresponding build.

Enviado desde mi Nexus 4 usando Tapatalk
[Nexus 4 Original Android Development] meangreenie:
May others follow you lead, good governor settings are crucial.
[Nexus 4 Original Android Development] Shardzmi:
Please answer this Francisco! I hope that we can use your kernel with slim once again :)
[Nexus 4 Original Android Development] franciscofranco:
Im sorry I cannot and I wont build 3 different Kernels.
[Nexus 4 Original Android Development] fozzie:
No reboots so far, since uninstalling it late last night...
[Nexus 4 Original Android Development] franciscofranco:
Figured as much. Crap started after Google deployed the latest Chrome Beta and seen users with complete stock device having random reboots after exiting Chrome Beta.
[Nexus 4 Original Android Development] Shardzmi:
I understant that the issue lies with the ramdisk of your kernel being different from the one they have ?
[Nexus 4 Original Android Development] franciscofranco:
Dunno now, spending the weekend out of home.
[Nexus 4 Original Android Development] 75markus:
relax & have a nice weekend :cool:

no need to rack your brain with kernel stuff ;)
[Nexus 4 Original Android Development] jak3z:
Hoi! Make sure to come back on Monday!
[Nexus 4 Original Android Development] 1ceb0x:
Delete. Changing the ramdisk with the one from slim will make jwr franco kernel to work. Thank you Franco in taking our request into consideration.
[Nexus 4 Original Android Development] frozst:
I just bought the Franco Kernel and I've discovered that the autoupdater doesn't work with CM room, so I have to manually download the Kernel and flash from the recovery as the app installs the default one leaving the system with a loop boot.

I won't ask for a refund since I'm not a "nightly paranoid" but it would be great having this feature working on CyanogenMod.
[Nexus 4 Original Android Development] Testraindrop:
Get your money back, the Kernel is free, as always :D

Anyway, CM needs JSS kernel...
[Nexus 4 Original Android Development] jak3z:
It's not a problem with Cyanogen it's a problem with your Android OS version, JWR is the official version for Nexus 4, others using JSS need to do it by hand, be glad franco created 2 kernels for the same device.
[Nexus 4 Original Android Development] Testraindrop:
Hey Franco,

read this: http://www.androidpolice.com/2013/0...ss-power-and-30-less-heat-than-existing-tech/

As far as I know the Note 3 uses the same Snapdragon 800 SOC as the rumored new Nexus, what do you think about this?

Seems that the 800 is not crippled with the USB crap and the Modem is more evolved than in the S4 Pro...