yashsingh1/xdaforums huggingface dataset:
[Nexus 6 Android Development] networkdood:
Touch boost? Where is that option? Or, how do I get that option? You over volt for stability? Never knew we had to for the Nexus 6, interesting. Thanks for the info.

Sent from....a phone

---------- Post added at 04:26 PM ---------- Previous post was at 04:24 PM ----------

It may have helped because at least now I can run the battery to 1% before the phone shuts off, rather than it being 8%-12%...

Sent from....a phone

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

Woohoo, just topped 7 hours SOT!!

First 10% of usage I did in battery saving mode, as well as last 10%.

You can actually put the device in battery saving mode all day...helpful for long trips. But if I play games, that number probably dips below 4 hours, depending on game usage, still, good to know I could do it.

How is the new Lollipop kernel version doing?
[Nexus 6 Android Development] KonoeKyon:
Actually it's input boost, under governor options, I don't think elementalx has that option though. And yes, voltages have to be tweaked when over clocking.
[Nexus 6 Android Development] Darian71:
Still on R21.1 test build and approaching 4 hours SOT with 28% battery left. I have not encountered the issue with my phone shutting off at 8-10%. Mine always goes to 1%. But I also flashed the M bootloader and radio about a month ago so not sure if that may be the reason or not.

Also just checked in recovery and my battery % is the same as shown on my phone.
[Nexus 6 Android Development] Darian71:
Granted I haven't used my device as much as usual today, and 7 hours of this has been while sleeping, but 1 more hour and I'm hitting 24 hours guys.
[Nexus 6 Android Development] jodvova:
Could you share the voltages?

Also, how do I set 1 second in input_boost_duration? Its currently set to 40000, is this value in microseconds or smth ?
[Nexus 6 Android Development] DespairFactor:
R21.1 is the last build before rebase, R22 has the rebase with the bad battery commits(we need to test if recalibration fixes it) and R23 has them reverted again and is a rebase
[Nexus 6 Android Development] adl:
Version R23 seems to fix the wrong displayed battery thing. On R22 I still had this problem.

EDIT:

Nevermind, see post above.
[Nexus 6 Android Development] KonoeKyon:
Voltages will be different for everyone, I gotta run 1140 @ 2918 1155 @ 2958 and 1190 @ 3033 for it to be stable for everything including benchmarking. I can run a tad lower with no issues if I'm not stressing the CPU though. And for 1 second its 1000000
[Nexus 6 Android Development] Darian71:
OK. At 25.5 hours battery life, and 4 hours and 58 minutes SOT, I was at 7% battery when my phone shut down even though my recovery percentage showed the same at 27% as my phone did. Plugged it up to the charger and booted directly Into recovery and showed 7% battery still. Was thinking of charging full and trying another cycle to see if it adjusted itself. Or would you rather someone test R22 [MENTION=5169465]DespairFactor[/MENTION]?
[Nexus 6 Android Development] DespairFactor:
R22 is what needs to be tested,R23 is more for people who hate me and don't want to try helping with testing these new power drivers with the battery issues. It looks like a calibration thing to me still.
[Nexus 6 Android Development] networkdood:
I under volt about a -40 to a -50, global setting:

Sent from....a phone
[Nexus 6 Android Development] pantmunu:
Liking the new name BTW .. But I got used to rping from one plus forums lol . as always great work sir.
[Nexus 6 Android Development] DespairFactor:
My old name was based on RIPng(RIP next generation routing protocol) my new one is named after an AFI song:P I have been a fan of them since I was young, so I thought it would be a good name.

Anyhow, try dirty flashing rom and flashing kernel and let me know.
[Nexus 6 Android Development] pantmunu:
Haha. Makes sense now. And yes will do. Will be back after flashing. Thanks.
[Nexus 6 Android Development] BrianTX:
Getting absolutely fantastic battery life on r6, will be trying r7 with the new kernel tweaking app. Thank you for this bad ass kernel!
[Nexus 6 Android Development] mjwhirly:
Never change your name :(
[Nexus 6 Android Development] DespairFactor:
Why?
[Nexus 6 Android Development] otisman:
Well to me you change your name at the perfect time new name new kernel new start much alohas
[Nexus 6 Android Development] rignfool:
He coulda gone with Miss Murder?
[Nexus 6 Android Development] caspersfi:
Bliss ROM

R7 kernel

422 Minimum

2764 Max

blu_active Gov.

FIOPS Scheduler

Things are just ridiculously smooth and fast.

Thanks once again you lazy bastard. ;) :)

Amazing work.
[Nexus 6 Android Development] schmolch:
Flashed r7 and had 2 reboots in the first hour. Dont know where to find pstore.
[Nexus 6 Android Development] philosophics:
No log provided either. I guess we'll never know how many licks it took you to get to the center of that tootsie roll pop...

Sent by a Whale
[Nexus 6 Android Development] DespairFactor:
I hate that song:/ I like older AFI:)

Thank engstk for the gov;) how is the battery?

/sys/fs/pstore or /dev/pstore
[Nexus 6 Android Development] caspersfi:
Not sure on the battery. Haven't been thru the second cycle yet. From what I can tell so far it's solid.
[Nexus 6 Android Development] DespairFactor:
With my setup idle drain is less than 1% an hour:)
[Nexus 6 Android Development] apophis9283:
im excited. any way you could get rid of touch boost
[Nexus 6 Android Development] DespairFactor:
Touchboost can be turned off in kernel adiutor, we've also got a few more options in the works, engstk and myself have sent feature requests.
[Nexus 6 Android Development] apophis9283:
i have it turned off. i can watch the min value jump up upon me touching the screen
[Nexus 6 Android Development] DespairFactor:
Cpuboost

Blu active also has a boostpulse setting.
[Nexus 6 Android Development] Bluemgt06:
I have experienced 2 hangs and reboots since installing R7. I'm running PureShamu 3.98. I have not overclocked or lowered voltages. Was crashing on R6 also, but R7 is crashing more often.
[Nexus 6 Android Development] DespairFactor:
Thanks for the log...
[Nexus 6 Android Development] Darian71:
You're the man. Grabbing R22 now and give some feedback tomorrow morning. :thumbup::thumbup:
[Nexus 6 Android Development] networkdood:
On the input boost, if the setting is already at 40000, then how would a higher number help?

***never mind, we are talking about duration so it makes sense now.***

Sent from....a phone
[Nexus 6 Android Development] Andromendous:
I think hes refurring to deleting the bootloader logs mentioned a few posts back.... Correct?
[Nexus 6 Android Development] info[]box1:
Well if the shoes fit I'll wear it. Lol

Edit: I'll flash back to 22 once my nightly ROM is released tonight.
[Nexus 6 Android Development] Darian71:
Back when I cycled R20.8 twice, it calibrated itself so I'm assuming R22 should do the same. But if needed I can try and clear those logs too. Upon boot of R22, kernel auditor didn't apply my settings as it said so I manually turned off core control in Thermal like I always do (and use no thermal), which allowed core 4 to come online as it was off. But once online core 4 stayed at the default MHz of 2649. So I adjusted Max MHz to my usual 2265 which lowered core 4 to that. So I then set my min MHz to 98 even though they were both already set to those MHz and she's running as usual now with conservative governor.
[Nexus 6 Android Development] KonoeKyon:
I set it higher so the duration is longer, at the default I sometimes get small stutters and at 1 second it works fine. Google has it set for like 4 seconds on stock kernel.
[Nexus 6 Android Development] hellsgod:
Yeah 1 second is a very good value :)

hells
[Nexus 6 Android Development] KonoeKyon:
I'm on r4 which is running good so far. Battery life is what I normally have, no odd draining so far. Based on my usage I'm on my way to about 5 hour SoT if usage stays the same with no issues before it runs dry.
[Nexus 6 Android Development] jodvova:
Thanks!

One question, does kernel auditor somehow throttle the max freq? I've set it to 3033, but when I check the app from time to time I see a lower value, as low as 1783. Why is it dropping it?
[Nexus 6 Android Development] KonoeKyon:
If you are at low battery it lowers max frequency.
[Nexus 6 Android Development] jodvova:
The battery is fine. Does it lower it when CPU temp goes up? I'm at about 55C now.
[Nexus 6 Android Development] KonoeKyon:
Yeah thermal throttling can happen especially when over clocking, it could also be the bcl driver, that has a tendency to limit frequency to 1958 under heavy loads and if the CPU temps are up enough it further limits to 1.7 depends on what you are doing really
[Nexus 6 Android Development] Darian71:
[MENTION=5169465]DespairFactor[/MENTION]. Looks like I lost 6% in my 5+ hours of sleep. Shows WiFi, Cell standby, phone idle all at that 5 hour+ with screen at 6 minutes since that's about what I used. it after unplugging it. Check back later. Currently at 89% i

Over the past 20 minutes of constant use
[Nexus 6 Android Development] jodvova:
Could you please share the init.d script to disable bcl driver?
[Nexus 6 Android Development] KonoeKyon:
#!/system/bin/sh

echo disabled > /sys/devices/qcom,bcl.39/mode

Make a new file using a root file explorer app paste that into it, then move it to /system/etc/init.d/ set permissions to 755, that will disable it on boot. Alternatively just to try it out you can use a terminal emulator with root and enter: echo disabled > /sys/devices/qcom,bcl.39/mode
[Nexus 6 Android Development] jodvova:
Thank you!

To get init.d support, I need busybox right? Is it enough to install the one that is flying around on this forum in a form of flashable zip: BusyBox-Android_M.zip or do I need to install one from the play store?
[Nexus 6 Android Development] Darian71:
My observations of R22 with minimal use today is that it doesn't deep sleep well. Approaching 14 hours with 8 of that while I was sleeping. (I took a nap before class tonight) I'll get a little over 2 hours SOT looks like. Sitting at 12% now waiting to hit that 7% mark again to see if she shuts down.

Update : OK, she made it down to 2% without shutting down and I read the SOT wrong. I got 3.5 hours, but could've gotten 4. I turned up screen brightness to kill the battery faster so I could get it charged up before I leave in an hour. Recharging now for a 2nd run [MENTION=5169465]DespairFactor[/MENTION].
[Nexus 6 Android Development] KonoeKyon:
Yeah that one should work, I'm using busybox pro by stericson from play store.
[Nexus 6 Android Development] DespairFactor:
I released R23.1, I have reverted the one commit causing the issue, it's not worth our time really.
[Nexus 6 Android Development] KonoeKyon:
This is what I got on r4 before I had to charge it and sleep after work

View attachment 3412718

View attachment 3412719

Keep in mind the phone stays in a metal locker in a factory the entire night with horrible cell reception. That's about what I normally get at work, according to the stats I was on my way to about 5 hours SoT if I was able to run it to shut down. I've had no issues with the new commits.
[Nexus 6 Android Development] Darian71:
Good deal. I wasn't really figuring 22 was gonna get much better but at least the battery percentages are fixed! Thank you
[Nexus 6 Android Development] Andromendous:
So... For now, 23.1 is probably the best choice for battery life/stability?
[Nexus 6 Android Development] Megaflop666:
So... Went full Mv2 on my n6 today and snagged despair kernel for M... Holy ****, talk about smooth and amazing battery. I've been using the hell out of my phone all afternoon and evening and just got 50%
[Nexus 6 Android Development] Darian71:
So far 23.1 is working great for me. In 3 hours of class time I had 3 phone calls, a few text, and hit the Web twice and only lost 5% battery. Home now and going to charge it to 100 % because I didnt get the chance to earlier and check the calibration down to 1% to see. As they say at McDonald's... I'M LOVIN' IT!
[Nexus 6 Android Development] DespairFactor:
R23.2 is coming, just need to build:P
[Nexus 6 Android Development] info[]box1:
Got it. I stay on your server. My playground.
[Nexus 6 Android Development] Darian71:
What could you possibly be improving on?? Lol
[Nexus 6 Android Development] e29:
From reading the thread it seems like battery life, but maybe I'm wrong?
[Nexus 6 Android Development] DespairFactor:
I added fast charge back in.
[Nexus 6 Android Development] info[]box1:
He can tell you about got about 684 different reasons. Don't get him started lol

---------- Post added at 08:30 AM ---------- Previous post was at 08:29 AM ----------

Thanks
[Nexus 6 Android Development] Darian71:
Lol. Yeah, thanks! I'm on hour 13 with 58% battery showing left, 4 hours sleep time, and a little over 2 hours SOT. Running smooth so far. :D:thumbup::thumbup:
[Nexus 6 Android Development] ptesmoke:
just reporting in, I'm on M preview 2, M R4 kernel...and seeing massive WiFi drain? anyone else?
[Nexus 6 Android Development] Megaflop666:
No Wi-Fi drain issues here. I'm getting normal to a little higher than normal drain on cellular. I've been using my phone at home on Wi-Fi for the last hour and only lost 1% battery
[Nexus 6 Android Development] ptesmoke:
thanks for your experience :) I'm on cell all day but still somehow WiFi is killing my battery, this is day one of a clean flash though so I'll chalk it up to settling in for now.
[Nexus 6 Android Development] Megaflop666:
First 48 hours are always screwy. I'm about halfway through my first cycle. Did you delete your battery stats file after charging to 100% to force the phone to make a new one? There's an app that does the same thing called battery calibration if I remember correctly.
[Nexus 6 Android Development] Andromendous:
The phone automatically wipes the battery stats when you charge it up paste 90%, this has been confirmed for a while now, why do people still do this?
[Nexus 6 Android Development] Megaflop666:
Actually it doesn't automatically delete it. The batterystats.bin file currently in my data/system/ is dated yesterday. My phone was charged to 100% this morning after I plugged it in at 530am. I've seen this mentioned a couple times but have yet to ever see it occur. When u check again tomorrow, the same batterystats.bin file will still be there.
[Nexus 6 Android Development] Andromendous:
http://m.androidcentral.com/wiping-battery-stats-doesnt-improve-battery-life-says-google-engineer
[Nexus 6 Android Development] Megaflop666:
Appreciate the article. Unfortunately it's one of those things that we could both post links to defend our argument. It's a practice I've done for years that doesn't hurt anything, so I'll agree to disagree. [emoji106]
[Nexus 6 Android Development] Andromendous:
Look im not trying to start a fight. But theres probably one big difference in the articles you would post. Their not from google engineers. I never wipe my stats, i never have major problems. Maybe if you stopped wiping them you wouldnt have to
[Nexus 6 Android Development] Megaflop666:
I don't have any problems. I read articles from Google engineers, users, devs, owners, etc. I'm not going to argue. Like I'd said in my last post, we can agree to disagree. Let it go man.
[Nexus 6 Android Development] Andromendous:
I am going to let it go, because i know there is no reason to push a user as yourself, who only looks at it from one way. My intention was for anyone ells out there reading this thread, to see both sides of the story so that they can form their own opinion based on multiple sources/opinions, i was not trying to change your mind. That is all.
[Nexus 6 Android Development] DespairFactor:
Guys, please stop this bickering. This should not be happening, just use the newest release and be happy.
[Nexus 6 Android Development] info[]box1:
OP is correct. I know how he works. He's stay on of every Google commits the hit the net. He working an sleepily manner to on the bleeding edge of Google tech. Plus to make sure it doesn't cut you deeply. Hit thanks on all his post. Matt a boss...
[Nexus 6 Android Development] Megaflop666:
The new release rocks Sir!
[Nexus 6 Android Development] Tylog:
Looks good :) 3,5 hours screen on, 57% battery left. Best result for me with N6 since I use the device. 99% of this time wifi on data off. I use no synch, when I need my mails I push them self.

Btw. This is with CM.

Cheers
[Nexus 6 Android Development] networkdood:
Which governor was used?
[Nexus 6 Android Development] Tylog:
Only Conservative
[Nexus 6 Android Development] networkdood:
Odd situation now, but when I flash the latest kernel, in about, it still shows 20.9...

Sent from....a phone
[Nexus 6 Android Development] Tylog:
Hm. Are you sure the flash process was fine? Maybe download and flash again. For me it show 23.2
[Nexus 6 Android Development] Darian71:
Well, [MENTION=5169465]DespairFactor[/MENTION], my device shut down at 10% with 23.1. Yet went to 2% before I plugged it up on the last release I tested which I forgot now for some reason. Lol. Should I just update to the newest and go again?

Edit : Went ahead and flashed 23.2.
[Nexus 6 Android Development] networkdood:
OK, never mind, my own stupidity is to blame as I flashed it onto my M ROM...I fixed that, flashed the 23.2 onto the CORRECT ROM..all set!

Sent from....a phone
[Nexus 6 Android Development] Tylog:
Hehe :) ok, going to Bed now. Good night.
[Nexus 6 Android Development] info[]box1:
I'm on that 23.2 and juicing baby. Battery life is on OJ on a Cali hwy.
[Nexus 6 Android Development] Darian71:
Nice analogy. Lol. I charged to 100% on 23.2 and unplugged and she has stayed on 100 for 10 full minutes of use so I'm gonna take a guess and say I'll shut down at 10% again. But I definitely agree, superb battery life. I got 2 hours of call time, 5 and a half of SOT, and great deep sleep on 23.1. So I'm sure 23.2 is going to be amazing ad well.
[Nexus 6 Android Development] Andromendous:
Yup, 23.2 doing amazing. 5 hrs and 23mins screen time, 2hrs youtube, 1 and a half hrs talk time. Id say its workin flawlessly. At 11% and hasnt shut down yet.
[Nexus 6 Android Development] DespairFactor:
I guess 23.2 was magical
[Nexus 6 Android Development] Darian71:
Awesome!!! 23.2 IS MAGICAL! :eek::thumbup::thumbup:
[Nexus 6 Android Development] DespairFactor:
I just pushed a new update for M and lollipop
[Nexus 6 Android Development] Tylog:
Uh. It can't get much better :)
[Nexus 6 Android Development] info[]box1:
Grab it 15 mins ago. You late. It's good I know are super busy person. Thank you.

"Energy and Persistence conquers all"
[Nexus 6 Android Development] nexusmaniac:
Just flashed M4.1 and in 'About Phone' I still see M3.8 build date July 22 :P

Pretty sure I'm running 4.1 though :)
[Nexus 6 Android Development] thuggn16315:
Running 23.2 and things are back on track muchos gracious
[Nexus 6 Android Development] Darian71:
IKR! He's pushing them out faster than I can kill a battery :rolleyes:
[Nexus 6 Android Development] Tylog:
Hehe yes :)
[Nexus 6 Android Development] DespairFactor:
This is what I am currently listening to and it is so good, just for you hardcore fans;)

https://www.youtube.com/watch?v=Fu9p22Xl2tk
[Nexus 6 Android Development] Tylog:
Soft Rock for my ears :) but it's ok. Solong it is no hip hop, rap, techno crap :)
[Nexus 6 Android Development] Megaflop666:
Need some maiden, dio, slayer, amon amarth, DragonForce or something like that blaring
[Nexus 6 Android Development] Darian71:
R23.2 JUST shut down on me at 7%. Moving on to the latest build and thinking I need to cycle through at least 2 charges.
[Nexus 6 Android Development] DespairFactor:
This is what the new problematic commit attempts to fix, but it was working for some and not others.
[Nexus 6 Android Development] Hen Ry:
Where is the mistake?

Despair.M.Shamu.R4.1.zip
[Nexus 6 Android Development] nexusmaniac:
I can't quite tell if that's /sarcasm? :)

The problem is exactly what you're saying/showing though - Flash M4.1 and it still shows M3.8 in the 'About Phone' section :P
[Nexus 6 Android Development] DespairFactor:
It's an error on my side, I will fix it now and post the build.
[Nexus 6 Android Development] eluspo:
Can i flash your kernel directly from stock? will i get the google verification screen before boot or not? thanks!
[Nexus 6 Android Development] nexusmaniac:
I've been flashing since M3 and the first time I was scared! I hadn't seen that verification message before.. But it's not too bad really ;) And I've seen it every reboot since :P - you might see the same result as me
[Nexus 6 Android Development] DespairFactor:
I uploaded the fixed version now, to get rid of that message there is a boot_rw.img you can flash before flashing the kernel.
[Nexus 6 Android Development] eluspo:
would you be so kind to link that boot_rw.img here? thanks!
[Nexus 6 Android Development] DespairFactor:
http://downloads.codefi.re/networkingpro/fix_rw_boot.img
[Nexus 6 Android Development] eluspo:
thank you!

---------- Post added at 05:05 PM ---------- Previous post was at 04:24 PM ----------

should i flash this first before your kernel or i can flash it after? what's recommended?
[Nexus 6 Android Development] DespairFactor:
Guys, looks like I will be updating CAKE today
[Nexus 6 Android Development] DespairFactor:
You would flash the rw boot before the kernel.
[Nexus 6 Android Development] aSquard:
Dumb question but what is CAKE?

Edit: found the explanation in the first post. Carry on!
[Nexus 6 Android Development] KonoeKyon:
Post 2 of the thread goes over that. :good:
[Nexus 6 Android Development] DespairFactor:
I will update it shortly
[Nexus 6 Android Development] Hen Ry:
[emoji106] [emoji1]
[Nexus 6 Android Development] info[]box1:
23.5 on the server. Dinner time.
[Nexus 6 Android Development] jodvova:
Do you by any chance know what's the difference between this image and insecure_noencrypt_boot.img (from this thread http://xdaforums.com/showpost.php?p=61974872&postcount=180) ?

I tried once flashing fix_rw_boot to get the rw system access but it hanged on boot and I had to reflash M2's boot.img. the sequence was: flash boot.img, flash fix_rw, flash kernel 4 -> hanged on boot.

But, when I flashed the noencrypt thing, it worked flawlessly fine. Same sequence of events applies.
[Nexus 6 Android Development] nexusmaniac:
Hi Despair,

I don't know if it's just me... But with M4.2 my mobile data is cutting in and out.. I'll have a 4G or H logo and then every few moments the logo will disappear and I'll have an exclamation mark on the signal bar :(

I'm on the 3 UK network, so are a few friends and none of them are experiencing mobile data issues

The only thing I've done between it working/not - is flashing 4.2 over 4.1(fixed 4.1 version)
[Nexus 6 Android Development] DespairFactor:
In that case use that rather than what I linked.

The only difference would be if you used CAKE or not, that's the only change between versions.
[Nexus 6 Android Development] nexusmaniac:
I haven't enabled CAKE :P Really not sure why I'm seeing this then... It even happens when I'm connected to WiFi which is strange (I.e. mobile data icon flicks between Exclamation mark and being normal even if I'm connected via a fully functioning WiFi AP)
[Nexus 6 Android Development] DespairFactor:
That's weird, it sounds like its trying to handover to your data from WiFi. Check your APN and other network stuff, try another qdisc possibly.
[Nexus 6 Android Development] nexusmaniac:
APN is all good, just checked it against the top result on Google ;)

It does it work WiFi on our off, tried aeroplane mode on/off a couple of times, still does it

And sorry :P I have no idea how to change qdisc correctly. I just have it a go and it tells me that rmnet_data0 doesn't exist. And that android doesn't support fq_pie when I try it on wlan0
[Nexus 6 Android Development] DespairFactor:
Screenshot the output of tc qdisc
[Nexus 6 Android Development] nexusmaniac:
Here you go :)

View attachment 3416697
[Nexus 6 Android Development] DespairFactor:
rmnet_data0 has fq_pie on it, try it on the wifi too. It is wlan0