yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] benblb:
A few things:

1.) Up at 7:40am. Now 12:10am next day with 60% battery on r30. (Flashed around 9am) Awesome! EDIT: Pretty light use.

2.) I have read that a custom kernel can have issues with Qi wireless charging and overheating. True? Is this kernel safe?

3.) I had some data drops last night and this morning on r29, but none with r30.

4.) I don't know much about this, and really have no idea how it would work, but would it be possible to conserve more battery while searching for signal? I spend my weekdays at school which gets awful reception from At&t and my battery gets hit as a result.

5.) My largest wakelocks are now com.google.android.apps.plus.content.EsProvider_Account and Google+ realtimechat (which I never use) What should I do to fix this? Would restricting background data from Google+ mess up my instant uploads? If so, are there other solutions? Why is the Google+ app so awful on battery life?

Thanks for reading through all this. :highfive:
[Nexus 4 Original Android Development] Ok_Kaleidoscope5109:
Its so stuffy at McCarran. Congrats for being able to concentrate
[Nexus 4 Original Android Development] Hanny:
i tested phone hardware for 2 hours and flashed franco kernel on the day i received the phone lol so... didnt quite try out intense games on stock

but some users switch alot between stock and franco and they discussed it before, telling stock doesnt lag that much (as in r2X) as throttling is not that aggressive

for more detailed info try input "stock gaming" into the search bar ;)
[Nexus 4 Original Android Development] SacredAce:
G+ realtimechat is high on my wakelock list, and I can only presume that it is a G+ issue, so maybe clear data / reinstall would fix it. Anyway, even so, the battery life is great and r31 seems even smoother on my phone.

As for battery life (with the previous r30), I got a 40% left this morning, with a 20h use and 3.5h screen on, WiFi/Data around 80/20 ratio, Bluetooth for about 2h, regular daily use. This thing just keeps getting better.
[Nexus 4 Original Android Development] benblb:
Impressive! Making me jealous. I think the low signal is really what is making my use different from most others. I have no way to test it though since the signal in my house is awful!
[Nexus 4 Original Android Development] SacredAce:
No doubt the bad signal is one of the best battery killers. I remember a few times being on a mountain with a really bad signal, the phone battery died literally in a few hours.
[Nexus 4 Original Android Development] visceralpsyche:
I use the Panasonic TM101 Qi charger with Franco's kernel and CM10.1, and it works perfectly.

HTH!
[Nexus 4 Original Android Development] gt-kingz:
Great battery. Didnt even charge my phone for nearly 2 days yet, and still ~ half of battery left on r29! Switching to r31 now!
[Nexus 4 Original Android Development] ObihoernchenDE:
r30:

Lost 0% overnight (7h) Sync and everything on except Latitude :)

Great!
[Nexus 4 Original Android Development] blueren:
Just wondering if a kernel has anything to do with gps.. when I was in r30, it took around 9 sec for a gps lock. Now on r31, it's still hunting for gps.. even after a minute! I'm using the gps status app, btw.

Sent from a Nexus
[Nexus 4 Original Android Development] ben_pyett:
Already liking #31 over #30, as even though initially the offline'ing of cores worked fine on #30, after a full night sleep this morning when I woke all four cores stayed online (even though throttled low) no matter what I did or how long I waited.
[Nexus 4 Original Android Development] Arstoien:
@miasmic

Nice review. Have you tried to see if there would be a difference if you switch the governor to performance? If I understood correctly you used interactive?
[Nexus 4 Original Android Development] veyka:
Aye, but the terrible network performance is more of an issue for me, and forcing GPU rendering is a bit of a bodge hehe
[Nexus 4 Original Android Development] nakaori:
after updating from r28 to r30 battery life got worse again. anyone else experiencing this?

msm hsic wakelock went high again.
[Nexus 4 Original Android Development] STIawdFTW:
I installed it and it works but when I turn the screen off it reverts back to stock. When I boot the phone it works because I have it set to resume on boot but as soon as i shut the screen off it's gone.
[Nexus 4 Original Android Development] franciscofranco:
Hmm, that doesn't happen with me anymore, that was fixed on update 1.3. Are you using any task killers that kill the app? If you do so thats the reason.
[Nexus 4 Original Android Development] STIawdFTW:
That's probably it but the task killer is set to every half hour and it happens as soon as I set the values, turn the screen off, and turn the screen back on. I will try uninstalling the task killer.

---------- Post added at 11:34 AM ---------- Previous post was at 11:28 AM ----------

Unchecked it from the task killer menu and it works now. The task killer must have cleared right after I set the values. Weird coincidence that the half our landed right then but thanks for the help.
[Nexus 4 Original Android Development] deviusdragger:
I cant believe no one has told you this yet, Delete any and all task killers from your phone!!! That will fix your problem. Will try this kernel out.
[Nexus 4 Original Android Development] derPianist:
Hey Franco.

Do you remember me from GN Section?

Got my n4 today and first thing after unboxing was unlocking and flashing your kernel. Yeah.

Greeeaaat kernel so far.

Awesome work. :)

Gesendet von meinem Nexus 4 mit Tapatalk 2
[Nexus 4 Original Android Development] JNewms:
+1 to this. Task killers interfere with the Android system way too much.

Sent from my Nexus 4 using Xparent ICS Tapatalk 2
[Nexus 4 Original Android Development] franciscofranco:
Yep task killers are ridiculously stupid.
[Nexus 4 Original Android Development] wyild1:
Yes! Love your kernel! was using it on my GNex and glad to see your moving to an N4 as well! Just flashboot boot'ed it and its running smooooth. Will prob flash it later!

Keep up the awesome work! cant wait till the app is back up and going as well :)
[Nexus 4 Original Android Development] franciscofranco:
Eheh everything is running smoothly to be honest :)
[Nexus 4 Original Android Development] mobilehavoc:
I've been running v8 for a bit now but apart from stronger vibration it seems the same as stock. What were the changes made and what should I be seeing? Battery life seems the same to me also. That's why I was asking if I need to root and tweak some settings to take advantage of the kernel?

---------- Post added at 03:18 PM ---------- Previous post was at 02:36 PM ----------

I take it back, battery life when phone is sleeping seems worse than stock for me. Guess I'm going back to stock for now
[Nexus 4 Original Android Development] Puzzlegirl:
You must be doing something wrong! I'm getting 6 hours screen on time in nearly 16 hours! :D
[Nexus 4 Original Android Development] whittikins:
Even getting 5 hours of screen on time would be awesome. Mind stating your settings and anything you have disabled on the phone? Thanks
[Nexus 4 Original Android Development] STIawdFTW:
Never used a display control app its usually included in the rom. Why would I delete the task killer if I can just uncheck the stuff I dont want it to kill? How would anyone "tell me this yet" if I just experienced the problem and asked about it?
[Nexus 4 Original Android Development] Puzzlegirl:
Well I don't have Location enabled and GPS only on if I need it. I have lots of apps but nothing with lots of wakelocks (like Facebook). Everything except weather is turned off in Google Now, but Google sync is on. Auto brightness is on and I'm a heavy user so, I don't know really. I'm careful and if some app misbehaves or causes wakelocks, I troubleshoot, freeze it or get rid of it. My N4 was pretty good on battery out of the box, but Franco's kernel makes it fantastic - especially since #7. Thank you Franco! :)
[Nexus 4 Original Android Development] STIawdFTW:
Mine seems to work fine. I don't like stuff running that doesn't need to be running. A lot of apps like to try and run processes in the background and if I'm not using the app at that point it's better to not have processes running wasting battery and memory.
[Nexus 4 Original Android Development] wyild1:
http://lifehacker.com/5650894/andro...ed-what-they-do-and-why-you-shouldnt-use-them

<snip>

How Android Manages Processes

In Android, processes and Applications are two different things. An app can stay "running" in the background without any processes eating up your phone's resources. Android keeps the app in its memory so it launches more quickly and returns to its prior state. When your phone runs out of memory, Android will automatically start killing tasks on its own, starting with ones that you haven't used in awhile.

The problem is that Android uses RAM differently than, say, Windows. On Android, having your RAM nearly full is a good thing. It means that when you relaunch an app you've previously opened, the app launches quickly and returns to its previous state. So while Android actually uses RAM efficiently, most users see that their RAM is full and assume that's what's slowing down their phone. In reality, your CPU—which is only used by apps that are actually active—is almost always the bottleneck.

</snip> (bold added by me)
[Nexus 4 Original Android Development] Prod1702:
If a app is running in the background and draining the app is it either a bug on the app or a app that i would not run. There is no reason apps that run in the background need to drain the battery. I have alot of apps on my phone that run in the background and my phone still sleeps fine with no problems. I do not think i used a Task killer since 2.3.
[Nexus 4 Original Android Development] pedxing:
Loaded in RAM is different from actually running. Task killers simply waste CPU/battery because the OS tries to reload the app immediately anyway. Every Google engineer and kernel dev is unanimous on this subject. Just remove it..Android's mem management is extremely optimized at this point.

If you've managed to get 1.6 Donut on your N4, you have my sincere apologies. The app killer is probably useful on that revision.

:laugh:
[Nexus 4 Original Android Development] STIawdFTW:
I guess that's interesting info but I really haven't had a problem with it the way I have it set up. I'm not going to notice the difference between how fast apps launch with or without a task killer. I don't like facebook's services that start by them self even with notifications turned off along with everything else. A couple apps do the same thing so that't the main function of my task killer is to stop apps that start services by them self.
[Nexus 4 Original Android Development] comminus:
This is an old thread on the topic, but still good information; task killers have been known to do more harm than good for a long time.

http://xdaforums.com/showthread.php?t=678205.
[Nexus 4 Original Android Development] peterperfect:
Still will make it to the day that I will understand why people buy a top notch device and barely touch it for two days just for the sake of showing some battery life magic that everybody know that doesn't exist.
[Nexus 4 Original Android Development] djemgee:
:beer:
[Nexus 4 Original Android Development] SchmilK:
I've had that happen without Franco kernel. Sometimes if I hit the power button because I'm done using the phone but then remember I forgot to do something and turn it back on again real fast the backlight turns on but nothing is displayed. Waiting 5-10 seconds to power it back on again brings it back, but its not a 100% repeatable action.
[Nexus 4 Original Android Development] Vangelis13:
Ok, why is that? Why would it be bad to switch that on?

I have it on since it exists and haven't noticed any drawbacks in other apps, it certainly though helps the (and here I will more than agree with you!) badly designed XDA app.
[Nexus 4 Original Android Development] Hanny:
yup you're correct i was using interactive all the time

and haha that sounds interesting so i tested upon your question:

test with r31 performance governor

[Feel Temp: Cool]

Should be the major difference than interactive governor - just at the very beginning, its cpu0 and cpu3 working (but not cpu0 and cpu1)

and this continuous all the way, just cpu0 and cpu3

well of course cpu1 and 2 did active rarely but just 1 sec at a time then go back to sleep

After only 3 minutes [Feel Temp: Warm]

it is expected to heat up so fast because of always max mhz

but this is interesting because even though i already feel warm, i expect it to start throttle however it didnt

Until 7 minutes since the beginning [Feel Temp: Warm]

it starts to throttle at a rate of 3 sec lag per 30 secs

and amazingly the cpu resting mechanism start to work, this time cpu3 rest and cpu1 replace its work

After 15 minutes since the beginning [Feel Temp: Even Warmer]

throttling gets very very frequent - 10 sec lag, 5 sec smooth, 10 sec lag...

and the cpus start to be angry - cannot see a stable sequence, but the time of 4 cores online together has become more, no matter at 1.5ghz or throttling at 384mhz

At last, back to device monitor, no movement 20 seconds, and happy ending

thats it! the most noticeable differences between using interactive and performance is the initial use of which specific cpu, lol but that doesnt matter much right because at last when throttling the resting mechanism also worked

just for fun testing it out and personally i think performance gov is never good for gaming as it (as expected) heats up the phone way too fast

but feels nice leaving a record here though ;)
[Nexus 4 Original Android Development] Notorious544d:
Not sure if this has been mentioned but apparently harsh's kernel has fixed the data issues with no compromise to the hsic wakelock. Maybe Franco could contact him?
[Nexus 4 Original Android Development] rbanaco:
Miasmic, I feel I'm not getting the same performance as you under NFS MW... my game starts to lag as soon as it gets a little warm (i don't feel it is hot) and after that, gaming turns unbearable... I flashed back paranoid android kernel and gaming beggins to behave smoothly again =/
[Nexus 4 Original Android Development] Sim-1:
Coming from r22 my first impressions are that battery drains much faster here on r31. I will give it a few days to settle in.
[Nexus 4 Original Android Development] mihkohuy:
The same here. For me, r28 give me the superb battery performance, the battery is very bad on 29 & 30
[Nexus 4 Original Android Development] phillamg:
I'm reluctant to add a "me too", so instead I'll say a huge thanks to Franco for an incredible kernel - particularly r27 and r28 which (for me) has had the best battery by a long way.

Just a thought given the comment in your change log, perhaps bundle r28 as Milestone 1 given it's performance and stability...? Thanks again! :D
[Nexus 4 Original Android Development] Hanny:
first off are you charging your phone? that speeds up 2x the time your device gets hot

i dont have much time switching to other kernels and test so maybe try using perfmon, and setup various control variables [this is so important for comparison] between the two kernels setup then find out the culprit making the difference you've mentioned :fingers-crossed:
[Nexus 4 Original Android Development] fetto666:
Hm, i wanted to test NFS MW but play store says it's uncompatible with Nexus 4??
[Nexus 4 Original Android Development] Arstoien:
After a night of deep sleep, two hours of GTA VC, half hour of NFS MW and one more hour of on screen tine brought me down to 15%. And that on WiFi with messenger app running on background.

Quite happy with the battery. Getting better with each new version.

Gaming is a bit smoother with v31 compared to v30. It's less laggy.

Great job Franco! Thank you so much!

[Edited cause of mistake :P]

Sent from my Nexus 4
[Nexus 4 Original Android Development] itpromike:
Franco would you ever consider making it so the cpu uses all cores when tapping any of the navigation bar buttons? Currently tapping the screen only uses 2 cores I believe so when tapping the recents button it takes a second to load and the animation behaves slowly. Same applies to the home button. It makes the device feel slow and sluggish. What do you think? Is that even possible?
[Nexus 4 Original Android Development] derPianist:
I am praying that he does not do so.

via my ∞ awesome Nexus 4
[Nexus 4 Original Android Development] maddoggin:
Change the animation! ;)

I change the transition animation to. 5 and phone flies.

Edit: I think the animation had allot to do with the lag on this phone that some people blame the kernel for. Just my opinion.
[Nexus 4 Original Android Development] djemgee:
Where do you do that me old mate
[Nexus 4 Original Android Development] alcurtis93:
Same. That would be ridiculous.... Turning all cores on when clicking back on the messaging screen etc would be overkill
[Nexus 4 Original Android Development] maddoggin:
Settings/ developer/ transition animations
[Nexus 4 Original Android Development] djemgee:
What ROMs that minco? No bother found it :eek:
[Nexus 4 Original Android Development] alanwyl:
Go to settings about phone, tap the build number several times, that enables the developer options
[Nexus 4 Original Android Development] prim3:
Damn Franco, r31 is rocking my N4.. Battry live is great and even gaming is rock solid, great work and thx!!!! :good:
[Nexus 4 Original Android Development] Hanny:
yup, unfortunately since the game updated on Jan 09, Nexus 4 was excluded out of the supported list. it has been discussed here and the dev team is working on it according to here

I am currently playing with the one i got before it got taken off the compatibility list

maybe you can test the performance no matter with GTA III / GTA VC / Asphalt 7 / Modern Combat 3 / NOVA3 / Dungeon Hunter 3,

the major thing we need to check are just

- whether you throttle at the right time or so damn early

- how does your phone behave when throttling

- whether the cpu123 goes offline correctly after throttling

or if you have some insight,

- why xyz kernel is smoother

until franco has time to care about gaming and asks us to test something for him :)
[Nexus 4 Original Android Development] trueblueram:
Works fine for me
[Nexus 4 Original Android Development] maddoggin:
This is in all Roms bro. It's stock settings. Go to settings/about phone/tap on build date a bunch of times until you become a developer. Then the secret settings will be exposed.
[Nexus 4 Original Android Development] scream4cheese:
When your phone is searching for a signal when signal is bad or worse, it'll drain more power because it's struggling to stay connected to the network. When you have a strong signal it won't have to work as hard to stay connected. So the answer to your questions whether it can conserve battery power or not is..no it will not. Put your phone in airplane mode when you're in school and pay attention in class not your phone. LOL
[Nexus 4 Original Android Development] Testraindrop:
@Franco

When you look at Miasmic Screenshots its always at 384Mhz when its throttling, thats whats leads to the lagging experience.

As far as I remember stock Kernel throttles at 1026Mhz but I guess longer, I believe that avoids sudden lags.

Can you have a look at it?
[Nexus 4 Original Android Development] evaradar:
Just a quick question to Franco - when and if there's an update to 4.2.2 for the Nexus 4 or rather Nexus devices, will you update your kernel to support that? I ask, because in order to download the update, we need to revert back to the stock kernel which is not a problem, but one would wait for an update for your kernel in order for it to work on 4.2.2 correct?
[Nexus 4 Original Android Development] lightphoenix:
Great battery life with stock + r29: 44% after 30h with wifi on + 2h50 screen
[Nexus 4 Original Android Development] Utini:
For instructions it says:

Reading the OP, theres a reason why I added instructions on it.

But in the OP (First post ?!) I dont see any inctrusctions? :o
[Nexus 4 Original Android Development] Mahdi786:
Hi Franco, check your first commit when you added auto-hotplug driver Thalamus has made a comment on it.

Thanks
[Nexus 4 Original Android Development] maddoggin:
Did you figure it out?
[Nexus 4 Original Android Development] Hanny:
gosh, dude, thats an idea! i immediately located to my archive storing the screenshots i made in the 2 hours stock test before root...

max cpu stability test for straight 24 minutes and the "cpu" (didnt make record of which specific one) was hanging around 1ghz
[Nexus 4 Original Android Development] rbanaco:
No, not charging... my setup is the default, so I think it is... did you change anything from default? I installed paranoid android rom then this kernel (v30) then v31 and that's it... just to see if it was kernel fault i went back to stock and no lag. It's strange that you had a different experience. It lags even before it gets hot.
[Nexus 4 Original Android Development] Hanny:
stock you mean PA stock right? well yea i am using everything default from franco and i think most of us here dont lag at the beginning when everything is cool in temperature

to see what "fault" is causing the strange lag even when cool, the easiest way i can think of is:

flash franco, check settings, open perfmon, play NFS

- whether (at least) 2 cores are above 1026

- if not what are they

:D good luck
[Nexus 4 Original Android Development] veyka:
Last time it was discussed (this was in a gnexus kernel thread) the reasons not to use it was that it used more battery in some cases and didn't always help with performance (when Google where talking about adding 2d acceleration to android they said that half of the challenge was knowing when to use the GPU is faster, and when it's slower)

And it can cause some issues in other apps, im not saying not to use it, just that I don't ;)
[Nexus 4 Original Android Development] persheshhater:
384-1350 interactive r29 auto brightness.aokp. Thank you very much Franco!
[Nexus 4 Original Android Development] alanwyl:
I guess "instructions" = "how to"

How to flash:

fastboot flash boot image_name

or

flash the zip in the recovery
[Nexus 4 Original Android Development] rbanaco:
Ok flashed again r31! didn't change anything... So I started playing with only two cores at max 1512. at some point 4 core boosted up (unit was warm) when i felt noticeable lag was when all 4 core downed to 384. then lag passes and after some time again... and so on...
[Nexus 4 Original Android Development] Simer03:
You might not want to be rooting if you don't know how to flash something by now considering you should have flashed something to get your phone rooted in the first place

Sent from my Google Nexus 4
[Nexus 4 Original Android Development] alanwyl:
The toolkit makes it easy for everyone to one-click unlock BL and root and flash CWM.

Every one should be given a chance to learn right? That's why I directed him to the OP.
[Nexus 4 Original Android Development] Simer03:
That's why toolkits are no good... Nobody actually learns

Sent from my Google Nexus 4
[Nexus 4 Original Android Development] bleuf1sh:
Md5 of r31 please
[Nexus 4 Original Android Development] Hanny:
yup, then you are experiencing what i and other intense gamers are experiencing :) no problem at your side at all
[Nexus 4 Original Android Development] blinde:
Sad to say but these r3x kernel versions are far from r2x versions when comparing battery life.
[Nexus 4 Original Android Development] rbanaco:
hm... but I can only play lagfree the first game... the same for you all?
[Nexus 4 Original Android Development] pedxing:
I'm sorry for this report but i think r31 is a bit of an over correction for performance. I'm getting more heat than normal and I'm worried about what this means for battery. I'm uc'd to 1.3 GHz max with everything else at the default settings.

Maybe some config options in the app for how the hot plug is set up would let gamers be happy.
[Nexus 4 Original Android Development] Vangelis13:
66a86f1d4ec0cbff2e6621971425653f

---------- Post added at 06:06 PM ---------- Previous post was at 06:05 PM ----------

Majority in here will disagree with you I think..