yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Original Development] Lazarus416:
Big battery drain with Franco's kernel?

Ok, so I have to ask, I upgraded my N7 WiFi today from an old PA 2.X ROM and Trinity kernel to PA 3.94 and Franco's newest 4.3 based kernel and now my battery is draining almost fast enough to watch. It is actually draining so fast that when I have it hooked up to the computer it can't keep up with the charge. (meaning it still drains even when charging.) Not to mention the back of my N7 is getting VERY hot, which I assume means the CPUs are running at near max speeds. The old ROM/Kernel had a tremendous battery life and was smooth as silk without a huge increase in heat.. I have also seen a noticeable increase in lag since the upgrade. Is anyone else seeing this with the new kernel? Everything I have seen says that Franco has the best N7 kernel, but I am beginning to think I made a mistake in upgrading. Is there any way to make adjustments to the clock speed without buying the Franco update app? Unfortunately, I don't have the time to learn all of the ins and outs of kernels and ROMs. (I am technically inclined, I just don't have the time between work, 4 kids, college, etc etc.) I know enough to be able to root, flash, etc, but what is best to use. Should I drop back down to a 4.2.2 build so I can use the trinity kernel again? (I can't find one from them for 4.3.)
[Nexus 7 Original Development] bunnahabhain:
Same here. Tried other kernels but it is the same. The N7 is charging VERY slow as well. As you said: it couldn't keep up plugged in.

Galaxy Nexus / Tapatalk
[Nexus 7 Original Development] doiutzu:
This is my battery usage with 4.3 stock rom odex with r75.

I set interactive parameters with trickster mod. And the battery life is great (10 % /hour screen on with little to no kernel wakelocks)

I use my tablet for reading and browsing mostly. So I set the high speed to 640 and input boost to 475 with no dynamic scaling. My up threshold is set to 95.

Thank you Franco for this:D
[Nexus 7 Original Development] khaytsus:
You obviously have something wrong, unrelated to the kernel. Look for CPU usage etc..
[Nexus 7 Original Development] NYLimited:
Not necessarily wrong. I have tested for battery usage via numerous tools. What I (and many others) have talked about is the time when the N7 is plugged in and running with the screen on. When plugged into the car, for example (yes, using the proper charge only cable) and the screen remains on the battery actually discharges, albeit very slowly. The percentage of battery charge decreases even though it is plugged in. Battery stats will generally not show anything for this time since the device is not actually running on battery. Leaving everything running but turning the screen off will slowly charge the device.
[Nexus 7 Original Development] khaytsus:
I guess I abbreviated his long, rambling quote too much.

Yes, tablets take a lot of juice to run, we know this. His point was his battery was going down insanely fast, tablet is hot etc, which is not normal.
[Nexus 7 Original Development] dareino:
Hey Francisco, dont forget to add Kexec support!

thxs

d
[Nexus 7 Original Development] doiutzu:
+1
[Nexus 7 Original Development] Lazarus416:
Thanks for the replies guys. Yes whatever it is, it is DEFINITELY not normal and it has to either be the kernel or the new PA ROM as it was running just fine before I upgraded. And it most certainly is not keeping up with the charger, even when plugged into the wall. I was watching netflix last night before bed, with it plugged into the wall and it was still choppy and draining the battery. This morning, after 7.5 hours of charging, it is still only at 59% charge. And that's after I used Trickster MOD to make some adjustments and verify that the CPU is in interactive mode. Trickster it is only using 2 of the cores. Although, I will say that they seem to be linked and both running at the same speed all the time. I locked it down to 370MHz on the low side and 1GHz on the high side and it didn't do anything but make the performance worse and still drain the battery while on AC.
[Nexus 7 Original Development] dillis:
switched to trickster mod like someone suggested above,now the wake up has no delay :) :highfive:
[Nexus 7 Original Development] Lazarus416:
Is it possible to use a 4.2.2 kernel with a 4.3 ROM?
[Nexus 7 Original Development] FReaKRaNT:
No.

Cheers, FReaKRaNT
[Nexus 7 Original Development] blunatic:
is otg USB supported ?
[Nexus 7 Original Development] osm0sis:
Not without swapping the ramdisk out for a 4.3 one.
[Nexus 7 Original Development] sgt. meow:
Even then, wouldn't WiFi and Bluetooth throw problems?
[Nexus 7 Original Development] fozzie:
Yes, it works fine with StickMount.
[Nexus 7 Original Development] blunatic:
OK. But only with stickmount. Not nativ?

OnTheRoad
[Nexus 7 Original Development] osm0sis:
Worked okay when I did it on the GN. Trying to enable the new features would probably mess it up though.
[Nexus 7 Original Development] sgt. meow:
True. [MENTION=3292224]franciscofranco[/MENTION]

I have been meaning to ask you this for a long time:

How is battery capacity calculated at kernel level? Is it even calculated at kernel level?

I'm asking because I've thought of something incredibly stupid (and my mind won't rest 'til I've tried it) and I found some hooks at /sys/class/power_supply/battery etc.

Thanks in advance.

sgt. meow
[Nexus 7 Original Development] andrew9292:
[MENTION=3292224]franciscofranco[/MENTION] or gurus, hav a question...

Currently trying to underclock GPU for less heat & battery consumption.

While f.ku allows 325Mhz GPU underclock, i would like to go lower to 260.

Went to /sys/devices/system/cpu/cpu0/cpufreq/ and edited file 'gpu_oc' from value 325 to 260.

This change is also reflected in cpu1's gpu_oc file automatically...

My question is, doing this manually outside the app, does make the GPU max limit at 260?

Or does it affect highest in scale only?

Does it go 1xxMhz> 2xxMhz> 260Mhz (max, stop) or...

1xxMhz... 2xxMhz... 3xxMhz... 416Mhz... 260Mhz (lowered becaused 'oc value' is 260)
[Nexus 7 Original Development] osm0sis:
It used to crash when you went below the default 416, so I don't even know, it should scale though according to what Metallice was saying before.

See here: http://xdaforums.com/showpost.php?p=34851789
[Nexus 7 Original Development] andrew9292:
Thanks, yes that's where i got the proper values from.

260Mhz is applicable, but 208 causes crash immediately.

Logically, this means that 'gpu_oc' value should be a max-cap somewhat...but still not sure.

Are there apps to monitor real time gpu speeds?
[Nexus 7 Original Development] mpokwsths:
Tweaked touchscreen r75

As we know, not all Nexus7's have ideal touchscreen behaviour. Some users reported (myself included) that r62 had perfect touchscreen behavior while others hated that version. I think that I nailed down exactly what changed from r61 to r63 that affected the touchscreen. We need some testing.

Compiled (using latest Linaro toolchain) r75 with some of r62 commits. So go ahead, if you experience erratic touchscreen behaviour with all the "normal" kernels out there, flash this tweaked r75 and report back.

Note: It is Anykernel format, so flash the normal r75 first and then this.
[Nexus 7 Original Development] renefm:
When will be gpu oc (beyond 416 mhz) available again? I really miss it !!
[Nexus 7 Original Development] wags57:
Amazing man!!!!! Tks
[Nexus 7 Original Development] mpokwsths:
Thanks. And the good thing is that it is only one commit that makes all this difference. Tomorrow I will compile r75 as it is with only this commit changed.

Franco is a genius. He accidentally fixed the touchscreen driver for us by cleaning up the driver which he later reverted because for the rest of the users it produced unwelcome results. It is this commit: https://github.com/franciscofranco/Grouper-3.1.10/commit/85da05d715f458bc1579eeb82ccb8d4481d92a63

:D
[Nexus 7 Original Development] nexusmaniac:
Has anyone tested this on cm 10.2?
[Nexus 7 Original Development] mpokwsths:
If r75 works, it will work too. Just flash the normal r75 first.
[Nexus 7 Original Development] sjknight413:
Yes! thanks for this mate, r62 was perfect for me :)
[Nexus 7 Original Development] .torrented:
Lately I've been needed to hit the power button 3-4 times before the screen would come on... Switched to M-Kernel, howere I love the fact that Franco kernel app works with m-kernel :)
[Nexus 7 Original Development] TheDarkDefender:
Doesn't happen on stock. But happens on cm,for me. No idea what's the deal.

Sent from my Nexus 4
[Nexus 7 Original Development] olrait:
Happens to me on my n7 on stock since I flashed r75. No idea why. any ideas?

Enviado desde mi Nexus 7 con Tapatalk 4
[Nexus 7 Original Development] why always me:
Thank you so much mpokwsths. this give a new life to my N7 as well as r62 did. This modified version of r75 give me a perfect touchscreen behavior on my device.
[Nexus 7 Original Development] bunnahabhain:
Great tweaked r75 man. I can feel that the touch input is better

Galaxy Nexus / Tapatalk
[Nexus 7 Original Development] FReaKRaNT:
Did you guys flash r75 then tweaked r75? Or does it not matter?

Cheers, FReaKRaNT
[Nexus 7 Original Development] bunnahabhain:
Original r75 prior to the tweaked one. Otherwise it doesn't work

Galaxy Nexus / Tapatalk
[Nexus 7 Original Development] Gabrieltan:
Root Problem

after i flashed v75 and tweaked, my root lose even i reflash superuser zip file. i know that this question been asked before but i cant find an answer. anyone know how to get root back?

i solved my problem already... hahaha
[Nexus 7 Original Development] bluetigger68:
How did you solve the issue with cwm superuser?

Gesendet von meinem Nexus 4 mit Tapatalk 4
[Nexus 7 Original Development] bluetigger68:
It is funny indeed, it solves the root issue but not the issue with koushs superuser. But is there any way to get cwm superuser running with r75? It works flawlessly on my mako with fk and a stock Rom but not in my grouper.

Edit: tried several kernels, only one not working with cwm superuser is fk! So it's an issue kernel cwm superuser...

Gesendet von meinem Nexus 4 mit Tapatalk 4
[Nexus 7 Original Development] pit84:
hi francisco,r75 with paranoidandroid 3.96 workly good,very smooth but for gpu overclock?thanks for your great job

bye
[Nexus 7 Original Development] Gabrieltan:
just flash with latest superuser..it should can solve your problem
[Nexus 7 Original Development] wildestpixel:
For information - if Franco fixes this in the same way he intends to for the nexus 4 there will be an added couple of lines in init.DC in ramdisk which call the daemonmode SU which is required for SELinux in 4.3.
[Nexus 7 Original Development] TheByteSmasher:
General question, and if possible request (I guess).. is it possible to backport some of the 4.3 goodness to 4.2.2? For those whose custom ROMs don't yet support 4.3? If so, [MENTION=3292224]franciscofranco[/MENTION] would you please put one more 4.2.2 kernel out? Thanks all.
[Nexus 7 Original Development] TheByteSmasher:
OR, I could just stick with my ROM and ask... :p
[Nexus 7 Original Development] osm0sis:
Nah.. It's your ROM's job to update, not Franco's to backport. ;)
[Nexus 7 Original Development] khaytsus:
WHAT 4.3 goodness? Did I miss something? Or do you mean updates in the kernel since moving to 4.3?
[Nexus 7 Original Development] khaytsus:
And that stuff would be in rom and kernel, so... Backporting is nonsense.
[Nexus 7 Original Development] Harry GT-S5830:
Why buy a nexus and then not update to the latest software? :confused:
[Nexus 7 Original Development] khaytsus:
inorite?
[Nexus 7 Original Development] xclusiv8:
Hello guys/girls. I'm rather new at all this stuff and have a question. I just flashed Francos kernel and it seems to be doing fine. I mainly flashed for its famous ability to extend the battery life. A question I have is if TRIM is enabled in the 4.3 Franco kernel r75? 4.3 did wonder to my performance and I hope that it won't change to the worse.

Thank you.
[Nexus 7 Original Development] osm0sis:
I think this is what needs to be in init.superuser.rc for both SuperSU and Superuser to function correctly without the need for /system/etc/install-recovery.sh or init.d scripts:

# SuperSU daemonsu
service daemonsu /system/xbin/daemonsu --auto-daemon
class core
user root
group root
critical

# Superuser su_daemon
service su_daemon /system/xbin/su --daemon
oneshot

on property:persist.sys.root_access=0
stop su_daemon

on property:persist.sys.root_access=2
stop su_daemon

on property:persist.sys.root_access=1
start su_daemon

on property:persist.sys.root_access=3
start su_daemon

The Superuser part is the latest from koush's github. Francisco had an older version in there, so maybe that was the reason it didn't quite work. Also, since Chainfire's SuperSU service will bail if it sees it's already running (like from the oneshot command for koush's Superuser), SuperSU needs to be at the top to ensure it's running correctly as a native service. That should fix the issue where SuperSU wasn't working without the init.d script it installs.

Over the next few days I'm going to fix up the ramdisk on grouper like I did already for tuna. Won't make as much of a difference here, since there wasn't anything really broken except root under some circumstances, but there are updates for fkbootscript to fix lmk whitelist and launcher/systemui priority, as well as the mount tweaks from r65 and some cleaning up I can do. Stay tuned. :)
[Nexus 7 Original Development] icu64:
So your maintaining the kernel now? O.o
[Nexus 7 Original Development] Flukester69:
Posted in wrong forum. Plz ignore.
[Nexus 7 Original Development] Krayvon:
!

anyone experiencing wifi not turning on on r75 and cm builds?

i feel like i experienced this on my N4's first 10.2 cm build so it could be the rom.
[Nexus 7 Original Development] Flukester69:
Oh my apologies. I thought I was in PA thread...I updated my post.

BTW. I bought Franco kernel ages ago. Always been a good kernel. I haven't tried his app in ages. Very impressed with the updates and usability! :)
[Nexus 7 Original Development] icu64:
OK I see now, thanks
[Nexus 7 Original Development] franciscofranco:
CM10 to make sure the kernel works on it.

About the sods I know what it is, will be fixed later today.
[Nexus 7 Original Development] Travisdroidx2:
Sorry if this has been answered already I am waiting for my USB otg cable to show up and I am wondering if R-16 supports it? Been running Francos kernels and loving it on my N7.
[Nexus 7 Original Development] franciscofranco:
If it works in stock kernel it works here...
[Nexus 7 Original Development] Travisdroidx2:
Thank you sir I will be happy to report back once I get the cable in the mail. Great work!
[Nexus 7 Original Development] Toyeboy:
Are you going to add 520gpu over clock option? I love the faster i/o speeds in your kernal but that extra bump in gpu clock really helps games in motleys kernal. Thanks
[Nexus 7 Original Development] ÜBER™:
Yes he plans on making it possible to scale clock speeds. Meaning you can choose for yourself the Max frequency.
[Nexus 7 Original Development] noneabove:
Is there a file I can extract from kernel to check out the under voting ?
[Nexus 7 Original Development] ÜBER™:
Huh? :confused:
[Nexus 7 Original Development] mullemulle86:
Best way to check/change uv settings is via Francos app.

Buying his app is also a good way to support his work.

Gesendet von meinem Galaxy Nexus mit Tapatalk 2
[Nexus 7 Original Development] noneabove:
I wanted a way without flashing kernel to check under volt table XD
[Nexus 7 Original Development] rohan32:
Just look at the source on github... :eek:
[Nexus 7 Original Development] Obsidian...:
Just flashed this for the first time and I saw your comment so I just plugged mine in and yes USB otg works

Sent from my Nexus 7 using Xparent SkyBlue Tapatalk 2
[Nexus 7 Original Development] osm0sis:
Wait.. does OTG work on its own or do you still need stick mount?
[Nexus 7 Original Development] franciscofranco:
Just pushed r17:

* Updated BFQ to v5 from v4

* Some ramdisk tweaks

* Disabled CPUQuiet to fix SoD's

* Some other small changes

GPU scaling interface is still being worked on, I couldn't make it work properly for release so far.
[Nexus 7 Original Development] ÜBER™:
Hmm interesting the hot plug control was causing SOD's. Any plans to rework the tegra hot plug or use another?

Sent From My N7 via White Tapatalk
[Nexus 7 Original Development] franciscofranco:
Its using stock Tegra Auto-Hotplug driver for now.
[Nexus 7 Original Development] ÜBER™:
What I meant was do you plan to tweak it or maybe use another hot plug?
[Nexus 7 Original Development] CDeviant:
Is there any chance you would add support for CIFS?

Surely there can't be a downside.
[Nexus 7 Original Development] ÜBER™:
Already supports it.

Sent From My N7 via White Tapatalk
[Nexus 7 Original Development] noobhero:
http://xdaforums.com/showpost.php?p=30015337&postcount=48
[Nexus 7 Original Development] robgee789:
I'm using this kernel with lean rom and the battery life epic and there is no lag at all, I'm even thinking of underclocking to make the battery last even longer:)
[Nexus 7 Original Development] d0ge01:
Franco keep min 2 core online with screen on, this don't cause more battery drain on light activity like read pdf?
[Nexus 7 Original Development] wildestpixel:
Please can you try this which is the tweaked r75 but in normal img format - http://wildestpixel.co.uk/files/grouper/boot75tweaked.img, saving flashing twice you can just keep in your kernel backups folder
[Nexus 7 Original Development] slybunda:
yes it does cause more battery drain
[Nexus 7 Original Development] fozzie:
Testing by people in this thread (including Franco) concluded that it didn't. The power saved by only having a single core online was pretty much negated by the extra power required in the management and on-lining & off-lining a second core. There are many more things happening on the phone that will have a far greater impact on battery drain.

You're welcome.
[Nexus 7 Original Development] slybunda:
if thats the case, then why is there less battery drain using stock kernel when reading documents?
[Nexus 7 Original Development] fozzie:
If you say so.

I'm talking about normal usage of the device doing regular things with it over a period of time, rather than a single spot usage of a single application.

Anyway, 2 cores it is. While the rest of us enjoy the device, you enjoy your Kindle :)
[Nexus 7 Original Development] aLNG:
from logical point of view..it does drain more battery, but its up to you if that little juice seems acceptable or not. But if it is somehow proved (not drain more juice) via reliable testing, then its good for you
[Nexus 7 Original Development] MBQ_:
Depends on your setup dude.

Id go into it, but I don't want to insult your intelligence hahah.

It could be the colors that have subtle effects on the battery, if you have sync on, brightness, all that other stuff.

Cause like, if you're running lets say... Twitter or something, although I'm sure they did a thorough job on optimizations regarding how it affects your CPU and stuff, it is still, as you know.. Consuming battery, RAM, etc. Which means maybe the CPU is currently ramping up a little more aggressively (y'know, to handle the task). Which ultimately results in minor battery drain, versus a situation where maybe in this metaphorically current case, you indeed aren't* using Twitter, battery life is just a littttttle better.

Anyways.. :)
[Nexus 7 Original Development] pit84:
the app now support android 4.3?
[Nexus 7 Original Development] ChemicalSymphony:
Yeah
[Nexus 7 Original Development] slybunda:
you do know colours dont effect a non amoled screen right?
[Nexus 7 Original Development] MBQ_:
I do now! :cool:

Edit: also didn't realize this was the n7 forum hahah
[Nexus 7 Original Development] LordDeath:
Due to the missing tilapia 10.2 builds am I still on r65 but today for the first time I tried the GPU overclocking:

It seems that even 700 MHz seems to be stable on my device and this results in a much better experience in for example Asphalt 8. I understand that playing games will now result in a lower battery life but what about the normal non-gaming usage? Will my battery life suffer even outside games? Will every app which uses OpenGL automatically cause the full 700 MHz clock on the GPU?
[Nexus 7 Original Development] yaoverstand:
Any plans to bring Franco.kernel to the new nexus 7? I loved it on grouper.

From my CM FLO
[Nexus 7 Original Development] lordlad:
The new JWR66Y build of 4.3 is here (available in the nexus factory image page). Is the kernel compatible with this new build?
[Nexus 7 Original Development] osm0sis:
Stock kernel didn't even change with JWR66Y. ;)

---------- Post added at 01:47 AM ---------- Previous post was at 01:31 AM ----------

f.K-grouper-r75-fixed is uploaded now.

Fixed ramdisk with mount tweaks (from r65) added back in, except discard is only on system now because cache and data are handled by the vold fstrim every 24-48hrs as long as you plug in at night (or battery is above 80%). Also cool is that the nodiratime mount option doesn't require a workaround anymore with the new fstab version. :good: I fixed up Superuser/SuperSU native support services and updated fkbootscript.sh for JB4.3.

http://d-h.st/users/osm0sis/jb4_3/grouper/

I combined the context files from stock and Franco's (AOSP?) ramdisk like I did on tuna and it still worked great, except 3 entries in file_contexts that caused hung boots if I included any of them:

/dev/pn544	u:object_r:nfc_device:s0
/dev/nvmap	u:object_r:nv_device:s0
/dev/tegra.*	u:object_r:video_device:s0

Absolute mystery to me what the problem there is, considering those 3 entries are also in the stock file_contexts, and also merged together on my fixed tuna ramdisk without issue. Maybe [MENTION=3292224]franciscofranco[/MENTION] can shed some light on it, but I just commented them out for now and it boots fine.

I also threw in the fixed ramdisk with [MENTION=2180870]mpokwsths[/MENTION]'s tweaked touchscreen driver zImage build for those who prefer it. :D It's labeled "tweaked-fixed".
[Nexus 7 Original Development] beanaroo:
+1

MultiROM thread points to franco.kernel as having kexec-hardboot. But the new 4.3 doesn't appear to have the patch. :)
[Nexus 7 Original Development] Timo_SGS2:
Sorry for n00b question, but your kernel(s) are only for JWRxxx right ?

No JSS version?
[Nexus 7 Original Development] Bobtehblob:
There's only one build for the Nexus 7. It's the nexus 7 where there's a jss and jwr build :)

Sent from my Nexus 4
[Nexus 7 Original Development] Timo_SGS2:
Guess i understood it, but you mean the Nexus 4 has two kind of builds and the Nexus 7 has only one!

Thanks for this information, i was not aware of that :)
[Nexus 7 Original Development] Bobtehblob:
Ah yes I meant the nexus 4! Silly mistake! Basically Franco Kernel should be compatible on any 4.3 rom as far as I'm aware :)
[Nexus 7 Original Development] dimebagdan65:
Franco and Osm0sis have done it again! :) just one question/humble request: I know that USB OTG works (somewhat natively and totally with StickMount), my question is, is it possible to get USB Host mode working? I have an OTG y-cable that would accept a charge while seeing the flash drive on stock kernel but with Franco, it still sees the drive just no more simultaneous charging... Anyways, great work all around regardless of that teensy setback but if we could get that in there this thing would go from Cadillac, past Bently, and straight to Rolls Royce territory! :thumbup:
[Nexus 7 Original Development] Essentrix:
+1 Great work!
[Nexus 7 Original Development] rasmusj78:
I've rooted my Nexus 7 and have SuperSU 1.51 installed. I then download a .zip and flashing it using ClockWorkMod Recovery 6.0.1.9-grouper. I download franco's kernel for my Nexus 7 with Chrome and then put my Nexus 7 in recoverymode. From here I flash the .zip file and reboot my Nexus 7.

Then I lose my Root of my Nexus 7. SuperSU tells me that no binary is installed and tells me to re-root my device. Can anyone help me what to do?

I'm using a Mac.

Thanks again.

Rasmus, Denmark