yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] Ok_Kaleidoscope5109:
Well that's great and all. Maybe someone should do a controlled battery test like I've said time and time again. I've asked Brian if he can give us the script for their tests, and I would gladly test Franco kernel.

If you watch the live CPU stats while running the browser test, it does ramp up 2 cores up to 3 sometimes. Flicking and scrolling might be more intensive than the browser test, but when you get 6 hours are you constantly interacting with the phone for the whole 6 hours?

I hate to argue about personal use and stuff because it's not very comparative, but when I do things like read long articles, I can get decent battery life. Sure I'm flipping around, but that's far less work than launching a new app, switching over, using data, etc. Reading a book I can get great SOT (never measured).

Either way the browser test doesn't have to be CPU intensive for it to mean something. The Anand test is focused on measuring:

- Screen drain

- Some CPU drain from having a browser work

- Wifi data flowing through or 3G radio drain

- Comparing phone to phone.

I think too many people are getting hung up on how it isn't reflective of how a phone is actually being used, but that's not the point of the test is it? That's what GSM Arena's "endurance rating" is for....

---------- Post added at 08:28 AM ---------- Previous post was at 08:25 AM ----------

Okay... my point wanst to debate others that Anand's test is superior or whatever. It's just to say that all of those SOT posts are quite useless because it's applicable to one user only at that certain day of use. I can't relate to your SOT time and nor can you relate to mine.

Remember there was once a time when people posted Antutu and Linpack and Quadrant and Geekbench scores all the time. "OMG how come r121 only gets me 12k but I was getting 13k on r111????" Now we frown on that because it's absolutely useless. Well pretty soon we'll realize how stupid posting SOT is, and it will go the same way those annoying benchmark posts go. I mean just for example battery life screenshots are forbidden on the CM 10.1 thread because it's not even constructive at all.
[Nexus 4 Original Android Development] ÜBER™:
To be honest im not debating its accuracy its a decently controlled test. Im debating what you've said early, that in fact, running Franco does not improve battery life. Because the guys at anadntech can get 6 SOT with the stock kernel and thats all you see here. I call BS on that because 6 SOT actually using the phone and not running some controlled test is proof that it does in fact increase battery life. Im sure that if one were to run that controlled test that it would easily reach 7-7.5 HRS SOT.
[Nexus 4 Original Android Development] CamoGeko:
Tells you what chip your CPU is.
[Nexus 4 Original Android Development] ceejay83:
You flash this revert

http://xdaforums.com/showpost.php?p=40110312&postcount=797
[Nexus 4 Original Android Development] jsylvia007:
Thanks!

I assume that I flash CM10.1, then Franco, then the patch, and do this for every update of CM10.1 or Kernel?
[Nexus 4 Original Android Development] BrandoHD:
Well if you browse through most kernel threads, people still post those benchmarks, do you know what I do, I skip past them instead of making multiple posts saying they are useless.

If they are useless to you, skip past them, let the OP of this thread dictate what should be posted here, because all you are doing is making another useless post about other "useless" posts that wouldn't stop because 10 pages down the line, there will be more of those "useless" posts.

All you are doing is trying to "spin a top in mud"

Or find a way to get moderator status and go through XDA threads deleting all the posts you find "useless"

Sent from neXus 4 using Tapatalk 2
[Nexus 4 Original Android Development] ceejay83:
The zip has the cm kernel in it, so you flash Franco after it. You should flash the revert after every cm update
[Nexus 4 Original Android Development] jsylvia007:
Thanks very much!!
[Nexus 4 Original Android Development] vickpick:
Oh, okay. Mine says faster. I guess I'll UV 100 rather than my usual 75mV.
[Nexus 4 Original Android Development] Spec-Chum:
I wouldn't read to much into the binning buddy, my nominal does -150mV although granted I start from a higher voltage...

Trial and error is the way forward :)
[Nexus 4 Original Android Development] vickpick:
4% per hour is exactly the drain I get during 4G. It's just that I only use 4G when I'm on bus to campus or going out to eat or something. Once I get to campus, I have WiFi, just like at home. So max 2-3 hours of 4G per day
[Nexus 4 Original Android Development] ngkongArm:
Just want to ask, with my screenshot below. Is this normal battery life? I'm using 121 just change suspend freuency to the lowest. I didn't change fhe others.
[Nexus 4 Original Android Development] vickpick:
Yeah, I'm sure I can UV more, but I don't see the purpose. I wanted a little less heat production and I'm getting that.
[Nexus 4 Original Android Development] dapsANDpoundz:
But you can't remove the battery text/icon without a custom ROM, right?
[Nexus 4 Original Android Development] vergilbt:
Could it be possible that I don't get all push notification using this kernel? When I switch I got all? I'm crazy?

Gesendet von meinem Nexus 4 mit Tapatalk 2
[Nexus 4 Original Android Development] akiv:
Kernel is rock solid however I have noticed a couple of times when turning wifi off the phone doesn't connect to mobile data. It turns on only after manually cycling mobile data on and off.

Not sure if this could be kernel related.

Didn't notice that before switching to r121.

Stock rom.
[Nexus 4 Original Android Development] hosmsdos:
Do u guys recommend lowering hot plug high or leave at 90 . using Franco 121
[Nexus 4 Original Android Development] Loccy:
Another -150 on a nominal here. Seems quite happy although I am not remotely interested in games so it's possible that were I to hammer it it might have problems. Try it on a set of values, see if it holds up for a week or so on your chosen values and if it does you're probably good to set the "set on boot" tick box.
[Nexus 4 Original Android Development] Utini:
-150mV on "Fast" here
[Nexus 4 Original Android Development] Banished Angel:
+1. Running Paranoid Android and r121. If I disconnect from wifi I have to enter airplane mode and then exit it to get mobile data working.
[Nexus 4 Original Android Development] Dody83:
With my fast CPU, I can UV -125mV, at -150mV I have reboot..
[Nexus 4 Original Android Development] ctfrommn:
All my radio/data related issues went away once I flashed .27 radio.....48 is terrible.
[Nexus 4 Original Android Development] I2IEAILiiTY:
That's expected
[Nexus 4 Original Android Development] yokuyuki:
Looks fairly normal. It's going to vary from user to user, but I don't see any particularly bad wakelocks unless you're not actually using LINE.

Well, you can on stock... but I think it has to be deodexed so you do still have to flash something.
[Nexus 4 Original Android Development] ngkongArm:
Ahh.. I see it'll different on each user. Just wondering is it normal or not. Because i see a lot of post that they have quite long SOT.

Yeah it depends on how to use the phone.

Thanks,
[Nexus 4 Original Android Development] vickpick:
Faster, trying out 150 and seems to be working fine, but weird enough.. faster battery drain. Makes no sense
[Nexus 4 Original Android Development] CrimsonSmear:
Franco,

Just wanted to point out a couple governor userspace issues (nothing overly disastrous):

interactive - boostpulse remains (albeit an invalid file)

ondemand & interactive - sampling_rate_min has 444 permissions (rather than 644) causing value not to hold (even in f.K_U)
[Nexus 4 Original Android Development] QUIETLYloud:
there's a tread in the themes section that has them.

edit... http://xdaforums.com/showthread.php?t=2227222
[Nexus 4 Original Android Development] italia0101:
Thoughts on this ?

http://xdaforums.com/showpost.php?p=40148351&postcount=9754

Deeper stats of sleep ...
[Nexus 4 Original Android Development] CamoGeko:
Well, you got the best chip that N4 has to offer.

It should handle a large amount of UV'ing just fine, whether you need it or not is subjective.
[Nexus 4 Original Android Development] franciscofranco:
What about it? I already explained how that worked months ago when I debugged the Power Retention thing, its not rocket science, although faux's explanation is well wrote and most users will understand without a problem.
[Nexus 4 Original Android Development] yokuyuki:
I think he's asking whether you enabled "deep sleep" on this kernel or not.
[Nexus 4 Original Android Development] franciscofranco:
But all those states are enabled as they should from stock kernel... I don't even...
[Nexus 4 Original Android Development] Banished Angel:
A speechless Franco? Now you guys did it lol
[Nexus 4 Original Android Development] Testraindrop:
Franco got a kernel panic on r121:

260.930631] [<c031ffcc>] (adreno_stop+0x0/0x78) from [<c030a53c>] (kgsl_pwrctrl_sleep+0x178/0x3ac)

[17260.930966] r4:c0ddabc8 r3:c031ffcc

[17260.931455] [<c030a3c4>] (kgsl_pwrctrl_sleep+0x0/0x3ac) from [<c030ad40>] (kgsl_idle_check+0x60/0xdc)

[17260.931760] r6:c000a194 r5:c0ddadac r4:c0ddac8c r3:00000004

[17260.932736] [<c030ace0>] (kgsl_idle_check+0x0/0xdc) from [<c00941f0>] (process_one_work+0x124/0x404)

[17260.933041] r7:00000000 r6:cf8cec00 r5:c0e87a00 r4:e3ba3480

[17260.933865] [<c00940cc>] (process_one_work+0x0/0x404) from [<c0094818>] (worker_thread+0x16c/0x384)

[17260.934232] [<c00946ac>] (worker_thread+0x0/0x384) from [<c0098ee8>] (kthread+0xbc/0xc8)

[17260.934567] [<c0098e2c>] (kthread+0x0/0xc8) from [<c0080868>] (do_exit+0x0/0x850)

[17260.934842] wcnss_8960: crash shutdown : 0

[17264.441159] Rebooting in 5 seconds..

[17269.449246] Going down for restart now

No errors detected

Boot info:

Last boot reason: kernel_panic

Log is still short :(

BTW. Am I the only one who's fku is not saving 0 for grey in gamma ?

After reboot the app always shows 114...

Gesendet von meinem Nexus 4 mit Tapatalk 2
[Nexus 4 Original Android Development] franciscofranco:
The GPU driver crapped itself, nothing I can do about that :(

Weird, I'll check the gamma code, thanks.
[Nexus 4 Original Android Development] jlear3:
R121 is straight butter but running carbon rom most of the time I unlock the phone it takes a couple of clicks of the button. Can anyone confirm this here?
[Nexus 4 Original Android Development] vickpick:
nice catch, color tuning stuff is def. messed up. the sliders don't match up to the numbers of loaded profiles, etc..

---------- Post added at 07:22 PM ---------- Previous post was at 07:22 PM ----------

probably the ROM, doesn't happen on stock
[Nexus 4 Original Android Development] Cantacid:
Im on Fast myself, started of with -75 went all the way to 150 with no issue at all. Thats when somebody in this thread told me to go easy on the UV and I dint care anything more than -100. But just for fun, i m on -125mV. All seems to solid and not dying. *TouchWood* :angel:

Btw just to thank Franco, on r120 I had noticed that everytime i used to touch the screen with my full thumb (Just to play around with the UI) the icon page used to bounce back and forth, somthing to do with multitouch or somthing i guess. Apparently Franco has fixed that, and what an improvement it has been.

Franco, what are you going to do with all this karma man, just let us have some! ;):good:

I just realised, once new nexus is released, franco stops developing this kernel? Stopped developing on Gnex?

First smartphone, first kernel discussion thread, first and the last developer i would run to for my kernel issue. :D.
[Nexus 4 Original Android Development] nellisere:
Reboot after sending a photo through Facebook Messenger.

264>] (atomic_notifier_call_chain+0x20/0x28)

[ 5118.588562] r7:eea92a40 r6:c000a194 r5:eea92a40 r4:e2f6801c

[ 5118.589385] [<c009f244>] (atomic_notifier_call_chain+0x0/0x28) from [<c0010b94>] (__switch_to+0x2c/0x58)

[ 5118.589721] [<c0899b80>] (__schedule+0x0/0x5e4) from [<c089a29c>] (schedule+0x38/0x78)

[ 5118.590026] [<c089a264>] (schedule+0x0/0x78) from [<c0899604>] (schedule_hrtimeout_range_clock+0x114/0x130)

[ 5118.590240] [<c08994f0>] (schedule_hrtimeout_range_clock+0x0/0x130) from [<c0899634>] (schedule_hrtimeout_range+0x14/0x18)

[ 5118.590576] [<c0899620>] (schedule_hrtimeout_range+0x0/0x18) from [<c0161650>] (sys_epoll_wait+0x350/0x3f0)

[ 5118.590881] [<c0161300>] (sys_epoll_wait+0x0/0x3f0) from [<c0010bc0>] (ret_fast_syscall+0x0/0x30)

[ 5118.591247] wcnss_8960: crash shutdown : 0

[ 5122.096893] Rebooting in 5 seconds..

[ 5127.104370] Going down for restart now

No errors detected

Boot info:

Last boot reason: kernel_panic

Everything default on r121 but -125mV (have no issues) and changed hispeed_freq to 1026Mhz
[Nexus 4 Original Android Development] vickpick:
The UVing might be it. Have you tried taking a few pictures, fast. or playing a slight demanding game after you started 125mV UV?
[Nexus 4 Original Android Development] leets4uc3:
My hot plug is now set to 90/55/80. Seems nice. But I want know know if this is good or not. What is every running?
[Nexus 4 Original Android Development] nellisere:
Yup, pictures are fine, games are fine, I've always UV'd by 125mV and never had any problems. I'm fast binned.
[Nexus 4 Original Android Development] franciscofranco:
As I said countless times, if problems happen without UV I can help, problems arise with UV I don't give support.
[Nexus 4 Original Android Development] vickpick:
default, 90,25,50
[Nexus 4 Original Android Development] MWBehr:
I think that portion is what he was wondering about. It seems like Faux was implying that the stock kernel/Qualcomm driver doesn't allow core 0 to go beyond C0 state, but his kernel does. No idea if that's an accurate interpretation though.

-125mv is too much for my fast binned cpu. It runs that way, but get occasional errors (not freezes or reboots). Stick with -100mv.
[Nexus 4 Original Android Development] Shano56:
Really...-125mv and you get a reboot...and you say the UV isn't the problem...wow
[Nexus 4 Original Android Development] franciscofranco:
Lol... cpu0 goes to Power Collapse during screen off. During screen on as far as I know it goes to C0 that is called WFI (waiting for interrupt) (not sure we can call it C0 state but its called WFI) and maybe Retention C1 if all other cores are offline.

During screen off it goes to Power Collapse -> dmesg | grep power collapse

I dont remember exactly but I think if all other cores are offline cpu0 can enter power collapse standalone, but don't take me word on this one, I not 100% sure as I debugged this long time ago. Or its the other cpus that enter power collapse standalone if they are online during screen off, but only cpu0 can reach Power Collapse which is the deepest state. Something like this, I don't remember all of it.
[Nexus 4 Original Android Development] ctfrommn:
That being the case, what would the point be of having that "feature".....seems a bit silly if you ask me. :)
[Nexus 4 Original Android Development] franciscofranco:
No s h i t.
[Nexus 4 Original Android Development] ctfrommn:
I see what you and Morfic mean by bulls*** free now :D
[Nexus 4 Original Android Development] ceejay83:
the answer to that is pretty clear
[Nexus 4 Original Android Development] jaeiger:
Hey guys, I was just using my phone streaming music via bluetooth in the car with data on, and my phone randomly shut off and I haven't been able to turn it on since. When plugged in it sometimes flashes its LED red, sometimes doesn't. Phone's unresponsive to any button input, I'm running M1.

Any thoughts?
[Nexus 4 Original Android Development] franciscofranco:
What a bunch of bull****.

I dont know what hes talking about really. If its about C1 -> retention then its not anything special, device can only achieve retention if all cpus but cpu0 are turned down, and theres some other code rules and checks. Check the source.
[Nexus 4 Original Android Development] AshtonTS:
Hard brick. You can try opening the phone and disconnecting the battery and reconnecting it or RMA it

Sent from my Nexus 4
[Nexus 4 Original Android Development] ctfrommn:
Sounds like Red Light of Death.....havent ever seen that apart from overclocking heavily. What seems to work best to fix it is

1) Hold power button down for 20-30 seconds

2)Plug phone in (you should see the battery charging animation)

3)Leave it charge for an hour or so

4)Hold power button down untill it reboots

5)All should be well again
[Nexus 4 Original Android Development] simms22:
it happens to people at lower cpu speeds(1512 and below), unrooted, during normal use too. if thw above fix doesnt work, disconnecting the battery and reconnecting it seems to work nearly 100%.
[Nexus 4 Original Android Development] thebryceee:
Well, one theory is that certain tasks that is more power intensive isn't getting the required voltage so it has to work harder and increases the power draw.
[Nexus 4 Original Android Development] simms22:
more chances for creating buzzwords
[Nexus 4 Original Android Development] vickpick:
yeah, that's what I was thinking. I'm thinking about selectively UVing, where the high freq aren't too UVed.
[Nexus 4 Original Android Development] Karlo666:
I was doing 100 mV UV all across board one day i had random reboot so i would say 75 mV UV is fine im keeping 50 mV UV just to be safe.

Other day i tryed 125mV UV across board and each time i did device freezed.

My Nexus 4 has Tapatalked.
[Nexus 4 Original Android Development] Vangelis13:
Deeper sleep..?

As in, more difficult to wake up then or what..?
[Nexus 4 Original Android Development] jaeiger:
What do you mean by disconnecting the battery?
[Nexus 4 Original Android Development] ctfrommn:
I would use that as a last resort.....you have to open the case and physically disconnect it. Not terribly difficult, but Im not a fan of operating on my phone. Leaving it plugged SHOULD work. It always has for me anyway.
[Nexus 4 Original Android Development] mc01319:
Hi, can someone tell me the stock voltage of 384 MHz.

I can't remember how much I undervolted the CPU.
[Nexus 4 Original Android Development] ctfrommn:
Either 850 or 900 depending on your cpu binning.
[Nexus 4 Original Android Development] |Logic|:
You could uncheck set voltage on boot, then reboot. I forget what its on in stock, mines sitting on 760mv currently.
[Nexus 4 Original Android Development] Underground_XI:
850
[Nexus 4 Original Android Development] ctfrommn:
For fast or faster....Slow and nominal is 900
[Nexus 4 Original Android Development] Foxnov1990:
Nominal binning: 900

Fast / Faster binning: 850
[Nexus 4 Original Android Development] casonswag:
Is it me or does touch seems real sensitive on 121? I like that though

NEXUS⁴
[Nexus 4 Original Android Development] mc01319:
Thanks, I've unchecked the box with set values on boot and I have 850 mV.
[Nexus 4 Original Android Development] hospital349:
I'm disappointed that this Kernel doesn't have associated buzzwords. What a load of bullsh*t. Without buzzwords, all you're left with are 'words'. There's no fun in that.

I compiled a small list of them. I hope that you might consider adding them to the thread so people might change from other kernels to this one:

Franco's Tweaked Interactive: Interactive2053 - ('cuz itz 50 yrs ahed 'ov all otha gov'nors on da planetz, y'all!)

Franco's Deep Sleep: PLAYDEAD - (Barely alive, but saving every ounce of strength!) ;)

Franco's Headphone Volume Boost: Earjizz - (Will make your ears actually ejaculate.)

Please say you'll add them. FRANCO, don't you want to make your kernel more popular than Google's Stock?!?! If you do, you're doing it all wrong.
[Nexus 4 Original Android Development] nellisere:
Considering I've been using -125mV since r50 or so and haven't had any issues, yeah, I don't blame UV. It's about -140mV where my phone starts freezing and rebooting.
[Nexus 4 Original Android Development] hospital349:
This made me laugh so hard that milk actually came out of my nose.

Even though I wasn't drinking milk. :good:
[Nexus 4 Original Android Development] Underground_XI:
It has always been sensitive.
[Nexus 4 Original Android Development] Xers662:
Can someone tell me what the audioOut_2 and RILJ partial wakelocks are?

Seem to be sucking quite a lot of battery
[Nexus 4 Original Android Development] casonswag:
I havent used this kernel in a while so i wouldnt know

NEXUS⁴
[Nexus 4 Original Android Development] cAase:
Actually ive had the same audio wakelocks on the latest kernels. May be some issue from my side.
[Nexus 4 Original Android Development] Karlo666:
Audio2 is sound of your lock sound or clicking sound for softkeys.

RILJ is phone that wakelock is used to awake mobile data or when reciveing calls.

My Nexus 4 has Tapatalked.
[Nexus 4 Original Android Development] Underground_XI:
Franco has made no changes to touchscreen sensitivity as far as i know. (Because there has been no need) So most probably it is placebo.
[Nexus 4 Original Android Development] franciscofranco:
Yes its placebo.
[Nexus 4 Original Android Development] ctfrommn:
Awww, cmon F....call it something cool besides placebo. Maybe touchmatic or something.....money to be made here :D
[Nexus 4 Original Android Development] Vangelis13:
Buzztastic Touch Input (BTI)
[Nexus 4 Original Android Development] simms22:
POD(passed out drunk) Sleep
[Nexus 4 Original Android Development] Curtis7990:
It is just me, or every kernel after 111 drain battery faster than 111?
[Nexus 4 Original Android Development] ctfrommn:
Trinity already has that one.....or was it slipped into a coma sleep? I forget.
[Nexus 4 Original Android Development] Vangelis13:
(We're trinitizing the thread, F probably getting p.off...)
[Nexus 4 Original Android Development] 309041291a:
No matter what I do I can never get as good battery than I could on 111, so I keep defaulting to it

Sent from my Nexus 4
[Nexus 4 Original Android Development] ctfrommn:
Youre right....back to my hole for now :)
[Nexus 4 Original Android Development] Underground_XI:
Now I see how trinity gets to have 10k posts :)
[Nexus 4 Original Android Development] simms22:
Francisco.. heres one of the trouble makers that you should keep an eye on. i tell you, this one is ****! heres a video of him abusing every good developer on xda.. http://goo.gl/YG5Gl :p
[Nexus 4 Original Android Development] Vangelis13:
Fully trinitized now.
[Nexus 4 Original Android Development] ctfrommn:
The sign of a good kernel.....s*** aint broke so gotta talk about something.
[Nexus 4 Original Android Development] Loccy:
You went full Trinity.

Never go full Trinity.

:)
[Nexus 4 Original Android Development] marcel9998:
I have got a noob question:

I am on M1 right now and really dig it! Although i think faux gave me a better battery life on powersafe! But may be just imagination!

Got it on 1026 MHZ Max and conservative!

So what is the equivalent nightly to M1?!?

Better update to newest nightly for me as a noob to kernels?
[Nexus 4 Original Android Development] ctfrommn:
You can select 1026 max and conservative here also.

R111 is probably the closest as it was the last that used mpdecision, but I would just go R121 and dont look back.
[Nexus 4 Original Android Development] wathefak:
omg.. earjizz.. reallyy?? sounds catchy :good:
[Nexus 4 Original Android Development] Loccy:
This. It took me a while to get on board Franco's hotplug train - I kept switching back to r111, which worked really well for me - but with r121 he really has created something special.
[Nexus 4 Original Android Development] vickpick:
My 121 battery usage statistics
[Nexus 4 Original Android Development] lightosx:
I'm still having trouble getting over how fast r121 is, truly unbelievable! You really outdid yourself with this one Franco. :thumbup:
[Nexus 4 Original Android Development] PetritH:
Sorry to ask this... but can anyone share their custom kernel settings.. I don't know what to change there.. would be much appreciated.
[Nexus 4 Original Android Development] ceejay83:
Don't change anything
[Nexus 4 Original Android Development] BrandoHD:
Stock Kernel settings are recommended
[Nexus 4 Original Android Development] Alexkidd85:
Sync? Facebook? Whatsapp?