yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] franciscofranco:
I'm not sure that saves any power/heat at all. They are separate cores, but its the same chip so I don't expect any difference at all. And what you're asking is a bit amount of work for almost no gain in my opinion.
[Nexus 4 Original Android Development] k_nivesout:
Franco, just wanted to say nice work. Your perseverance and work ethic are admirable, especially since it sounds like you have plenty of other things to keep you busy.

If I might make a small UI suggestion regarding the app (sorry if it's been mentioned before) - when you go to set vibration strength, perhaps make the number pad come up instead of the keyboard? It does this with the numerical governor controls, but not the haptic feedback strength.
[Nexus 4 Original Android Development] sucre213:
how many percent of battery did you lose after 1.5h gaming ？

for me web browsing can get more than 5hours display but game playing drain the battery crazy

highly doubt that it can get through 2hours
[Nexus 4 Original Android Development] chrisgtl:
I have a new kernel wakelock on #34 that I have never seen before.

pm8921_oec 21.6% (over 10 hours since flashing #34)

However my msm_hsic_host is only at 1.9% with #34 so that is a bonus!!
[Nexus 4 Original Android Development] benrees21:
That pm8921_oec is do to with charging I believe.

A Nexus Connoisseur!! AOSPA!! Trinity Kernel!!
[Nexus 4 Original Android Development] pro.aggro:
r34: WhatsApp drops on Wifi.

Sent from Nexus 4 powered by PARANOIDANDROID
[Nexus 4 Original Android Development] Vangelis13:
Check the router? Can't see how the kernel affects that..

Sent from my Nexus 4
[Nexus 4 Original Android Development] biffsmash:
While you might be able to fix it by altering settings on the router, its not the fault of the router and only affects nexus devices on the latest jelly bean. I can confirm HTC one x, galaxy s2 and galaxy s3 work perfectly on works router and so too did my HTC desire and xperia x10.

i doubt its the fault of the kernel either. I've had these data problems from stock, through every single kernel and custom ROM I've tried and according to Google's bug reports its there no matter what you do. Happens regular for me. As soon as screen of, notifications stop.

Not frankos fault though I'd say blame google as it happens on stock too.
[Nexus 4 Original Android Development] magictwins:
it's not "As soon as screen of, notifications stop."

it happens randomly when screen off
[Nexus 4 Original Android Development] bakedcricket:
Hi all, I've noticed that when I game on my phone, it gets really hot. Just giving feedbacks, I'm unsure if it's the cause of the kernel.

Sent from my Nexus 4
[Nexus 4 Original Android Development] Vangelis13:
Eventually it will get hot. You're peaking every functionality that generates heat basically, it's bound to get hot. Take a break for a minute. Good for your eyes as well.. ;)

Sent from my Nexus 4
[Nexus 4 Original Android Development] blueren:
It should and it will! But if it gets really really really hot, then you have a problem

Sent from a Nexus
[Nexus 4 Original Android Development] Harsh:
Its about end of charging(eoc) thing. pm8921 is our charger driver for many qualcomm soc.

This wakelock starts when your battery charges to more than 90% and, charging current is reduced to trickle charge. And you see this wakelock because when your phone is connected to charger even after being full charged, it is identified as full and its in "not charging" state even when connected. And batterystatus app starts picking wakeocks as soon as android report "not charging" state, or I may say it starts reporting as soon as it finishes charging.

Anyways nothing to worry about it, as when you are connected to AC or USB, your device is never in deepsleep. This wakelock does not effect battery, as its not waking up device from deepsleep.
[Nexus 4 Original Android Development] antih3ro:
It is a known problem of 4.2 look here: http://xdaforums.com/showthread.php?t=2072930&page=1
[Nexus 4 Original Android Development] franciscofranco:
No it doesn't. WhatsApp is open on my device since I came to the USA, I use it everyday to text with my GF and it never stops no matter how much crap I do with the kernel in my local testing.

It gets a little warm because you're taxing your device. Play on your Xbox or PS3 for a while and then put your hand over it and you'll feel it warm as well. Your device will throttle down a little bit if its too hot, don't worry and have fun.
[Nexus 4 Original Android Development] shadowcaster31:
Not sure about others but on r34 i still get some random data drops once in awhile (i was in the same place the entire day when it happens)... but then again could it be carrier specific?
[Nexus 4 Original Android Development] Arstoien:
Nothing more we can do about that. We're waiting for an update from Google. Hopefully all will get fixed soon.

Sent from my Nexus 4
[Nexus 4 Original Android Development] SacredAce:
I really don't get it, do people thing that intensive gaming will not result in heating the phone? What do you think happens with all the GPU's when you load them with intensive work? Just a side note, although chips are made to survive high temperatures, the increased heating does shorten their expected life. However, most of us don't use the same phone for a longer period than a few years, so I guess no problem in life expectation :)

Flashed r34 this morning, so far it has been cool, smooth and no problems.

Did get another data drop yesterday (r32), all bars gone for a few secs, then they were back and data worked. I'm quite positive that the network has a large impact on data drops, not the kernels. Does anybody got data drops on stock ROM&Kernel?
[Nexus 4 Original Android Development] zFayZz:
Thanks is the govener set on row by default?
[Nexus 4 Original Android Development] aMpeX:
ROW is an I/O Scheduler, not a Governor

default governor is interactive,

default I/O scheduler is deadline i believe
[Nexus 4 Original Android Development] Haomuch:
Use r34 for one day and the performance is great. Just found a sns wakelock for more than 30m. If I remember right it should be related to phone calls. But I didn't make any phone calls today. Just played some online music for about half hour. Is that normal?
[Nexus 4 Original Android Development] Arstoien:
I had that wakelock with a previous version but it went away by itself. Maybe give it some time?

And the default I/O scheduler is ROW.

Sent from my Nexus 4
[Nexus 4 Original Android Development] biffsmash:
Notifications stopping is every single time I turn off my screen. As for the grey bars, that is random, but whether they are blue or grey I get no notifications on WiFi when the screen is off, as soon as I shut off the screen.

As for this kernel, I have had no grey bars since r34 and with slightly tweaked settings the ui is nice and lag free.

Battery on r34 seems as good as ever for franko kernels :)

Cheers.

P.s. I won't mention the WiFi issue in this thread again as I'm being unfair to franko and his awesome kernel.
[Nexus 4 Original Android Development] eagleeyetom:
Thread cleaned. Proceed on topic.
[Nexus 4 Original Android Development] mobilehavoc:
I got those wake locks a ton on Franco but with same apps and usage I don't get them at all or very little on stock or another custom kernel. It may caused by an app or activity but there's something in the kernel that makes it happen. This has been my experience.
[Nexus 4 Original Android Development] benrees21:
Which means deleting my on topic post? Thanks.

Franco, R34 is great but there sometimes is a little lag opening recents. Not a big problem but thought I would mention it. Thanks.

A Nexus Connoisseur!! AOSPA!!
[Nexus 4 Original Android Development] DowntownJeffBrown:
That's from having your phone plugged in. You phone never sleeps while charging so u are fine that's not a new wake lock I've gotten it when charging since stock

Sent from my Nexus 4 using Xparent Blue Tapatalk 2

---------- Post added at 05:56 AM ---------- Previous post was at 05:51 AM ----------

r34 sleeps like a baby granted its just over 3 hours but I had to keep my phone plugged in till I had 100% charge and i stayed up very late then get up at 540am but here's what I got last night. Franco amazing build thank u so much :D:thumbup:

Sent from my Nexus 4 using Xparent Blue Tapatalk 2
[Nexus 4 Original Android Development] Vanhoud:
That just means your battery reporting is whacked. No way it could hold 100% for that long
[Nexus 4 Original Android Development] Arstoien:
Sorry but just to suggest: could you attach the photos next time so they don't come out so big? ;)
[Nexus 4 Original Android Development] Hali666:
Can Franco kernel be used on CM 10.1 ROMs ?
[Nexus 4 Original Android Development] flash-90:
Yes, see OP:
[Nexus 4 Original Android Development] DowntownJeffBrown:
Ummm Lol sure thing chief not a problem :thumbup: hurt your eyes?:eek:

Sent from my Nexus 4 using Xparent Blue Tapatalk 2
[Nexus 4 Original Android Development] Haomuch:
The sns wakelock keeps increasing even though I did noting afterwards. What the hell?

Updates: the wakelock disappeared after reboot. Guess it's due to some app.
[Nexus 4 Original Android Development] DowntownJeffBrown:
Yes it can lol what are you talking about its called deep sleep look at all my pics. On r31 I would get 1% drop in a 8 hour night this is how a battery should act when properly sleeping its not wacked reporting Franco just has my baby sleeping like a kitten.

Sent from my Nexus 4 using Xparent Blue Tapatalk 2
[Nexus 4 Original Android Development] DowntownJeffBrown:
Vanhoud this is since i woke my phone up see steady dropping as i use my phone almost an hour at 80% battery looking great to me nothing wacked lol It even straightens out when screen is off just like the first 3 hours

Sent from my Nexus 4 using Xparent Blue Tapatalk 2
[Nexus 4 Original Android Development] Ok_Kaleidoscope5109:
What does ROW stand for?
[Nexus 4 Original Android Development] kikisp:
read over write lol
[Nexus 4 Original Android Development] z3r0_x:
I still really wish for a proper gamme control, this is the last thing missing on this kernel - otherwise rock solid, smooth as butter and with amazing battery life, seriously, this is how the stock kernel should have been!
[Nexus 4 Original Android Development] Ibsonic:
Hmm weird.. I was on R34 and I received my whatsapp messages and other notifications when I unlocked my device. Sigh

I'm back to r32 where I didn't had that. Am I the only one ?

Verstuurd van mijn Nexus 4 met Tapatalk

---------- Post added at 02:26 PM ---------- Previous post was at 02:25 PM ----------

Read over write

Verstuurd van mijn Nexus 4 met Tapatalk
[Nexus 4 Original Android Development] Utini:
Any chance u could fix the delay when picking up a call ?
[Nexus 4 Original Android Development] jhericurls:
Google Wi-Fi issue, wait for 4.2.2

Rom issue, Romanbb has already fixed this in AOKP.
[Nexus 4 Original Android Development] DowntownJeffBrown:
I had that on CM10.1 but I don't get it on KillRom so its ROM related not Kernel

Sent from my Nexus 4 using Xparent Blue Tapatalk 2
[Nexus 4 Original Android Development] vindikleuk:
This might not be because of the kernel; do you happen to be on the Dutch "Hi" provider? I experienced the same issue yesterday, and I'm still completely stock. Might be a local (Netherlands) whatsapp issue, might be Hi. I don't think it's kernel-related.
[Nexus 4 Original Android Development] danielvc:
It's a known issue, not HI. Will be fixed in the next Android update, Google already said so in the bug tracker :)
[Nexus 4 Original Android Development] jundii:
What's goofy is that I had this issue on builds r24-r32, that I can remember. Once I flashed r33 and r34 I haven't had the WiFi delayed notification issue since. No changes to my router. Has me curious if it has anything to do with those "aggressive" wakelock patches initially released causing the issue to be more exaggerated during deep sleep. BUT, it doesn't explain why people have it on stock ROM and stock Kernel, except that maybe the router is handling the issue better and making it less noticeable in my case.

Regardless if it is happening on stock and not related to the kernel, then a fix in 4.2.2 will be great.
[Nexus 4 Original Android Development] djemgee:
I get it on any ROM even stock
[Nexus 4 Original Android Development] Ibsonic:
No I'm on T-mobile. And I though I was the only Dutchmen here in the Nexus 4 threads :D

Also thought that it has to do with those 2 hsic patches. But I'll wait for 4.2.2 thanks guys.

You guys had any drops? I didn't had any. Just want to make sure it was because of our dutch providers.

Verstuurd van mijn Nexus 4 met Tapatalk
[Nexus 4 Original Android Development] bakedcricket:
Yeah it was significantly hotter than r33 during gaming. Anyone else experiencing this too? If not, maybe it's just my phone.
[Nexus 4 Original Android Development] yokuyuki:
Was there a kernel fix to the random screen turning on? I don't seem to get them anymore in recent kernels.

I get that randomly and it goes away if I reboot. No idea what causes it though.

Not the patches. It's router dependent for me. Or you fix it from being router dependent with the multicast/broadcast fix.
[Nexus 4 Original Android Development] jmejiaa:
It's happened to me on stock and other Franco builds, I've been using every build since 9.. It doesn't always happen, it actually doesn't happen often.. You're just getting unlucky now and it's starting to happen to you.

It's a Google bug, not Franco.
[Nexus 4 Original Android Development] Ballastatuz:
Yeah the recent apps menu is a little laggy. It was super snappy in past builds. Great job on this build though. Battery is great. I went back to stock values.
[Nexus 4 Original Android Development] DowntownJeffBrown:
Yea my recent apps is a lil laggy too.

I'm not sure what that guy who said my battery must be wracked was talking about lol. I guess he doesn't understand what deep sleep is and how batteries work within the android system. Lol speaking out his butt i guess :rolleyes: did he look at all my pics including the wake locks cause if he did he would see my phone slept almost all night im guessing he doesn't understand wake locks either though.

Build r34 is the best to date

Sent from my Nexus 4 using Xparent Blue Tapatalk 2
[Nexus 4 Original Android Development] Utini:
And it is annoying as hell !
[Nexus 4 Original Android Development] DowntownJeffBrown:
Hmmm crazy it only happens for me on cm10.1 i would be like hello :confused: hello then the 2nd time they would answer me but once i flashed killrom it stopped

Sent from my Nexus 4 using Xparent Blue Tapatalk 2
[Nexus 4 Original Android Development] steviewevie:
Well, I can see where he was coming from.

Let's assume that your phone lost 1% of charge over those 185 minutes that it was on battery. If we extrapolate then it implies that your phone could last for 18500 minutes till the battery runs out, i.e. 308 hours, which is over 12 days. And given that it didn't even report a whole 1% loss, it would be more than that if the battery stats are correct. Do you really think that's likely?
[Nexus 4 Original Android Development] pro.aggro:
Wifi drops and thereby WhatsApp drops back with r34

On r33 it was fine.
[Nexus 4 Original Android Development] DowntownJeffBrown:
Look a few posts later i posted my battery stats at 80% in fact here ill post them again u tell me what to think then top 4 screen shots are when i woke up the bottom 3 are at 81% battery notice when my screen is off again almost a straight line deep sleep.and i didn't have any huge drop after i started using my phone i don't think my phone could last 18500 min that's ridiculous this was after a full charge then deep sleep not normal usage it was all with my screen off while i was asleep. When a phone is in deep sleep it shouldnt use much if any battery other than wake locks which i had very minimal of if u look at my stats

Sent from my Nexus 4 using Xparent Blue Tapatalk 2
[Nexus 4 Original Android Development] javacody:
Man. According to half the people posting, Franco's kernel is the Antichrist and responsible for all the evil in the world.

Its just getting ridiculous, the amount of laziness and ignorance showing up in this thread.

I wish some of you would just go back to stock already...
[Nexus 4 Original Android Development] deepsunzhine:
Here is mine..:)

Only 1% all night and i slept like 10 hours

Enviado desde mi Nexus 4 usando Tapatalk 2
[Nexus 4 Original Android Development] DowntownJeffBrown:
Hmmm so maybe my battery wasn't a fluke :D I think Franco just has the kernel under control and I'm loving it:thumbup:

Sent from my Nexus 4 using Xparent Blue Tapatalk 2
[Nexus 4 Original Android Development] biffsmash:
Franko's kernel is excellent, I have no complaints at all. As for 12 days standby, on this phone, I wouldn't be so sure, but on my previous phones, 1% to 2% battery loss with data off, over night, was absolutely possible, and was the norm for me. If you leave your phone on deep sleep, and it loses 2% per 8 hours, then you get 6.6 days standby, and 12 days if it's 1%. I will see what idle battery is like tonight over 8 hours, but I seriously doubt this phone will sleep at 1% per 8 hours.

Edit: Seems 1% over 8 hours is possible then lol Even better! :D
[Nexus 4 Original Android Development] alanwyl:
the screenshot says 2h something, that's not 10 hours
[Nexus 4 Original Android Development] lightosx:
I charged the phone a bit during that hour and a half, so I couldn't tell you precisely, but next time I play I will pay attention to that and I'll let you know.
[Nexus 4 Original Android Development] Ibsonic:
Indeed it's router depended ! I've tried it with the router of my neighbors. Damnit. Multicast/boradcast fix. could you PM me what that is? I'm not a hardware geek.
[Nexus 4 Original Android Development] lightosx:
Not saying that you didn't get 0% drain over the 3 hours, but with only 95% deepsleep it may be possible it is just the n4's crappy battery calibration. I test my idle drain every night and I've had it happen to me on a few occasions where I get 0 drain after 3-4 hour, but after 30 sec to a minute of using the device it drops 2-3%. Last night I had 0.3 drain / hour in almost 6 hours with 97.7% deepsleep and with 486 mhz as min.
[Nexus 4 Original Android Development] bleuf1sh:
I used to be one of those people with data losses on 3g.... After using r34 for a full day I'm glad to say that all's good. I'd even use the word great :)

Thanks franco

sent from my r34-Franco nexus 4
[Nexus 4 Original Android Development] ben_pyett:
i suspect that this is most probably a rom issue, rather than being kernel related.
[Nexus 4 Original Android Development] DowntownJeffBrown:
I understand and trust me i thought about that to but normally when that happens my battery will drop real fast as soon as i turn it on and if u look at my pics i don't think that happened it may have though.

My point was though in the beginning when i first posted those pics this morning was that r34 is a bad arse build and Franco is doing an amazing job with getting my phone into deep sleep.

Sent from my Nexus 4 using Xparent Blue Tapatalk 2
[Nexus 4 Original Android Development] vomer:
r34 summary:

*data responding well (when waking up from sleep and loading pages/apps)

*excellent standby time reminiscent of r31/32

*smooth all round w/ no lags

A great potential milestone candidate imo :good:
[Nexus 4 Original Android Development] deepsunzhine:
That is so true

Enviado desde mi Nexus 4 usando Tapatalk 2
[Nexus 4 Original Android Development] nokkenas:
My battery statistic on r34 with light usage on Wifi (only Whatsapp and almost no browsing).
[Nexus 4 Original Android Development] Z4nd4r:
After a day of use, no issues to report. Device doesn't get any hotter than stock, battery life is great, and speeds are excellent. To those having lag issues in their recent apps section, it's probably ROM related. I'm on the stock ROM and I can say with 100% confidence that my recent apps functions far quicker than it did with the stock kernel; it's a very noticeable difference.

All in all, very happy with the kernel. r34 definitely has my vote for milestone status.
[Nexus 4 Original Android Development] ctfrommn:
+1
[Nexus 4 Original Android Development] Luigiesin:
Same here... Most likely those lag issues are due to the ROM you're using... Not the kernel...

I suggest to people having those recent apps issues, to try reflashing the ROM.. Or clean install.

Sent from my Rock & Roll Nexus 4

ROM: MINCO V6

Kernel: Franco r34

T-Mobile
[Nexus 4 Original Android Development] ssauger:
Yesterday i did install factory image. Stock kernel was total smooth, then i flashed franco r33 and noticed some lags, scrolling in esfile explorer, all apps scrolling, scrolling widgets in app drawer.... The same i noticed on CM latest nightly, also with r34. Maybe some are no able to notice this little stutter. But great kernel so far :good:, locking forward and i hope it feels soon like stock kernel performance wise. ;)
[Nexus 4 Original Android Development] yokuyuki:
You can either fix your phone with http://xdaforums.com/showthread.php?t=2072930 or adjust tcp timeout on your router if you can adjust it using custom firmware like DD-WRT or Tomato. The former results in more battery use though.
[Nexus 4 Original Android Development] Pulsu:
Last thirteen hours I've been on stock rom and Franco kernel combo.. With stock settings.

No data drops, No lag.. No problems at all.. :)

Next step is a full charge and test a battery life..

Easily best combo so far! Keep up the good work Francisco! :)
[Nexus 4 Original Android Development] Nebucatnetzer:
Why's the milestone so freaking important for you guys? The only thing that will change is the name.
[Nexus 4 Original Android Development] Testraindrop:
I also never get it why everyone wants a "Milestone", "Stable", "You-name-it" build...

Hint: it won't be magically more stable/faster/make you coffee...

It's just another NAME!
[Nexus 4 Original Android Development] Puzzlegirl:
They want to get left behind ;) Or stop reading the thread? That might not be so bad - less repeated questions :p
[Nexus 4 Original Android Development] CaspaTheGhost:
Agreed. I've noticed it a little but I'm running a release candidate of something so attribute it to that rather than the kernel. Especially when its so smooth elsewhere.

They believe that when a milestone comes along it will allow them to stop flashing, little do they know!

Sent from my BAKED N4
[Nexus 4 Original Android Development] ctfrommn:
Like anyone can quit flashing....;)
[Nexus 4 Original Android Development] vomer:
You guys need to relax and read.

A milestone release is a stable "base" that can be used by people who do not like to experimental builds or for ROM devs to include in their builds to avoid conflicts and issues.

The idea behind a milestone is not for it to be better - the idea is to have a "standard" build with minimal to no issues to work from going forward (for adding new features or experimenting).
[Nexus 4 Original Android Development] nellisere:
Using Stock 4.2.1 (rooted) and r34, I'm getting data drops, but different from before. Before it would have blue bars, and just one arrow, now I'm getting grey bars. This happens when I wake the phone, and then I get my notifications. I don't get notifications with the screen off. This is not on WiFi either, it's HSPA+. Is this a kernel issue?
[Nexus 4 Original Android Development] prim3:
Here another Dutchman ;)
[Nexus 4 Original Android Development] Haomuch:
Yes. Some users will be satisfied with a build named with stable or milestone and stop or less frequently follow this thread. The feeling of stable is more important than the fact of stable.
[Nexus 4 Original Android Development] Nebucatnetzer:
I'm totally relaxed it just bothers me a bit to read the same stuff over and over again.

The milestone or whatever build will come when it's done what's the point in asking for it?
[Nexus 4 Original Android Development] jmejiaa:
Franco said he reverted the changes that would have caused data drops, so if it's a Kernel issue it's not a Franco Kernel issue but rather an issue with the stock code.