yashsingh1/xdaforums huggingface dataset:
[Nexus 6 Android Development] raptoro07:
Optipop ROM

I was on Vindicator v35 :)

WiFi on but at work mostly on LTE

Bluetooth on

GPS on High Accuracy Mode

Screen AutoBrightness

IO read ahead on 1536 like default but on FIOPS

Stock Freq and Voltage and Interactive Gov

Pretty much leave settings as you have them by default for kernel.
[Nexus 6 Android Development] __NBH__:
Tried this kernel out last night and the results are brilliant so far. I left the settings as default apart from -25mv undervolt and reduced the GPU back to 605Mhz.

I'm currently at 73% with 2hrs 22 mins screen on time and that is mainly on mobile data, only just over an hour on WiFi this morning.

This is with Chroma ROM, latest slim gapps, bit of Facebook, XDA, WhatsApp, quick phone call, and general playing about with the phone.

Very impressed, keep up the good work:thumbup:
[Nexus 6 Android Development] sbollero:
Thanks for the reply. I will mess around with it and see if voltages or frequency's play a role. Great work and I appreciate it.
[Nexus 6 Android Development] le1tho:
Xileforce: Are you going to release "Anykernel" like version of your vindicator kernel? :)
[Nexus 6 Android Development] yellowman82:
Loving your kernel mate. This is stock settings, ambient display off, brightness at around 30~40%, auto sync on, location off, lots of texting some YouTube and world star hip hop for a lot of videos, Lot's of browsing on XDA using the premium app, lots of Facebook but on Chrome beta since the Facebook app sucks, minimum gaming on boom beach and clash of clan really satisfied with the performance.
[Nexus 6 Android Development] Xileforce:
Wow that's really good! No undervolt even??
[Nexus 6 Android Development] Xileforce:
Possibly, I've never looked into what's involved
[Nexus 6 Android Development] Xileforce:
Haha the voltage I was talking about can only be changed in the source. Not by the user.

That's super good! What bin are you? I'm a 5 and do -30
[Nexus 6 Android Development] Megaflop666:
Send your phone to Motorola and get it fixed. It's a known hardware issue in earlier models of the n6. I finally got a brand new phone from tmo because of that issue. Some kernels make it worse, but eventually all kernels will do it to you.
[Nexus 6 Android Development] Xileforce:
I mustve gotten lucky! Mine shipped from T-Mobile the day it came out! And never had an issue
[Nexus 6 Android Development] bmg1001:
Mines gets the screen tearing issue about once every 2 months
[Nexus 6 Android Development] Megaflop666:
I ordered mine the day it came out and it worked great for about 2 weeks before the first screen tear. Then it started happening more and more. Went to tmo, got a refurbed pos replacement, it started doing it right out of the box, 4 refurb replacements later, I filed with the BBB, tmo presidents office contacted me the next day and said they'd send me a brand new one if i removed my complaint... My new Phone has been working perfect ever since. :)
[Nexus 6 Android Development] Xileforce:
Wow! That's dedication man lol!
[Nexus 6 Android Development] Megaflop666:
When I pay $700, (or whatever i paid, i don't do payment plans), for something I expect it to work and that's all I'll accept.
[Nexus 6 Android Development] Xileforce:
Hehe well played sir, well played indeed. I'm surprised you had such bad luck with the first 5 even though they were refurbs xD
[Nexus 6 Android Development] Megaflop666:
That's why I went to the BBB, I kept telling tmo I paid for a brand new, fully functioning phone and I had yet to receive that.
[Nexus 6 Android Development] ChaosMinionX:
Love the kernel, but recently I have been getting "insufficient system storage" after flashing the 2.1, or 2.2T1 kernel on Blisspop 4/20 and 4/21 builds. Zen kernel seems to work, which I believe is what you built your rebase on.

Is this a known issue, or is there any logs you want me to pull to investigate?
[Nexus 6 Android Development] Megaflop666:
Were you recently on elemental x? I've ran into that after coming from that kernel. It's something in the ramdisk is what I was told. Best solution I've found is dirty flash your ROM to get back on stock kernel and ramdisk, reboot, and then go flash the kernel you want.
[Nexus 6 Android Development] ChaosMinionX:
I was on Vindicator 2.1 release prior to that, doing a full clean wipe and seeing if it fixes it.
[Nexus 6 Android Development] Megaflop666:
Hmmm...
[Nexus 6 Android Development] yellowman82:
Nope no undervolt involved.
[Nexus 6 Android Development] ChaosMinionX:
false alarm!

Full wipe resolved it, must have been some ramdisk issues going on with the updates from blisspop.

EDIT: spoke too soon, as soon as I rebooted it came up after the initial setup. Zen17 works though...
[Nexus 6 Android Development] Aerigon64:
Every time I reboot, synapse cancels boot and resets my settings. Even if I initiate the reboot. I turned of the reset setting in synapse which fixed it but I'm wondering if that's a known issue and if theres a fix. Also it keeps saying my backup files are corrupted.
[Nexus 6 Android Development] Xileforce:
I would try at least 25mv undervolt. Should be stable for anyone
[Nexus 6 Android Development] Megaflop666:
Didn't mean to thank the post... Meant to reply lol.

It's doing it after a full wipe and reinstall?

---------- Post added at 04:23 PM ---------- Previous post was at 04:22 PM ----------

Clear your synapse data. Also, if you don't let the phone finish boot and maintain it's settings for a couple minutes, synapse will do that to you.
[Nexus 6 Android Development] Aerigon64:
I do let it sit for two minutes. I'll try clearing data.
[Nexus 6 Android Development] ChaosMinionX:
Yep.

wiped system/data/cache/dalvik and proceeded to flash Bliss 4/21 build, with 2.1 official, and did another full wipe and tried 2.2T1 and both gave "insufficient system storage" after booting. If I clean wipe, and install the rom with Zen17 it works fine.
[Nexus 6 Android Development] Aerigon64:
How do I disable mako? Do I just enable msm?
[Nexus 6 Android Development] joshm.1219:
Ehh I don't even bother undervolting my low freq now, even 25 UV on those will reboot my bin 1 unfortunately
[Nexus 6 Android Development] Aerigon64:
Whats the average bin number. I'm 4 and I'm just wondering what everyone else has. What undervolt do you think I can get away with also?
[Nexus 6 Android Development] Xileforce:
I'm not sure what causes this issue... I know it happened to some people when using that new ART optimization in the build.prop which most ROMs now include. Idk what would cause it to say out of memory. Could you try going into synapse when you get the error and going to the tool section and saving the kernel dmesg? Then paste bin it plz. Maybe it will say what's happening.
[Nexus 6 Android Development] derekr44:
Mine's a 7 and it gets wonky at -50. I keep it at -25.
[Nexus 6 Android Development] Megaflop666:
Pvs13 running -30 with no issues. Have been lowering -5 every few hours until I finds it's breaking point.

---------- Post added at 05:09 PM ---------- Previous post was at 05:07 PM ----------

-10? -15?

Start with -5 and run that for about 4 hours of with some hard use (games, stability tester, antutu or something), if it doesn't give you problems or crashes, drop another 5. When you start getting unstable, go back up 5.
[Nexus 6 Android Development] Aerigon64:
I've been doing 30 with no issue. I'm on 35 now
[Nexus 6 Android Development] tdamocles:
I took this stable 2.1 release and now The Vindicator app tells me I don't have a Shamu . what is up with that?
[Nexus 6 Android Development] Megaflop666:
I was just guessing. This is my first time pushing my n6 to see what it can do.
[Nexus 6 Android Development] bmg1001:
Odd, I'm a 6 and it works just as normal.
[Nexus 6 Android Development] Xileforce:
O_O ur bin in synapse is 13? Because there's two tables but the one i put in synapse is the correct one. My other one told me I'm a 13 but it lied to me :(. I would be honored to meet a real living 13!
[Nexus 6 Android Development] yellowman82:
My bin is only 5, I'm a bit nervous on trying to undervolt but I just recently unplugged the phone since my last screenshot and just glad I get good battery for my use. This was 10% all browsing through XDA.
[Nexus 6 Android Development] yellowman82:
Forgot to upload picture lol.
[Nexus 6 Android Development] Megaflop666:
I don't see in synapse where it says my PVS bin. I did step away from vindicator for the day to test drive the latest Zen. Does he not have the PVS listed in his setup of synapse?
[Nexus 6 Android Development] Xileforce:
Heretic! Lol jk I even recommend zen in my OP xD. But no it will not display it because I had to modify UKM to look for the correct file. Otherwise it should be displayed on the first page in synapse ;)
[Nexus 6 Android Development] Xileforce:
Wow man you get great battery life! I'm a bin 5 too and I used to do -25 but now I've started doing -30 and haven't had an issue. We have a bin 1 beta tester and even he does -25.

Its a bug in the updated version of the app that he's fixing. Its because certain ROMs rename the device from something other than Nexus 6 to like shamu or something.

As a side note I'd like to remind everyone that Voltage is probably the largest portion of the power draw formula for frequencies. Its the voltage squared so it uses exponentially less power the more you reduce it. For instance -5mv is 25 but -10mv is 100. Basically..even small amounts will help :)
[Nexus 6 Android Development] LunaticSerenade:
I'm bin 7 and I run -55 on all but OC frequencies, -80ish on 960MHz and up.
[Nexus 6 Android Development] BrianTX:
I'm a bin 5 and I run -60 on everything but 2.5&2.6, lowest I can go on 2.6 is 1045. Also drop 98mhz to 500 mv. -65 gives a couple random reboots over the course of a day. Under volting makes a big difference for battery life and how much the phone heats up under hard use, for me anyway. I would love to have access to the GPU voltage table!
[Nexus 6 Android Development] Xileforce:
Wow I may have to try this! The GPU doesn't really use a voltage table from what I can see. It just uses a min and a max voltage range. Im not sure how that works but I've lowered the minimum voltage for the GPU quite a bit from stock.
[Nexus 6 Android Development] Aerigon64:
I'm just wondering if lowering frequencies really helps battery life. Wouldn't it take longer to execute tasks rather than entering deep sleep and thereby use more power?
[Nexus 6 Android Development] Xileforce:
Only if we assume you lock the frequency at a low frequency. If it needs more power it can always scale up. What you said is pretty much the argument people always used to use for using the performance governor. Race to idle. But I believe people proved that wrong. I'm no expert. But the lower frequencies use significantly less power. For insance, 35mhz uses ~15x less power than 300mv. So in order for it to use more power it would have to be running for atleast 15x longer than 300mhz would. The phone won't use the real low frequencies much unless you are doing something like reading a webpage, stuff where you are looking at the screen but not touching. A core can only enter a sleep state when there is nothing being processed on said core so its always nice IMO to have a nice low frequency it can sit at when its processing stuff but not able to sleep. Listening to music will also likely use the bare minimum frequency. Whew...hope that helps explain it a bit! There's also a short explaination on the FAQ section on first page.
[Nexus 6 Android Development] Aerigon64:
OK thanks so much for the great explanation.
[Nexus 6 Android Development] Megaflop666:
Just came back to vindicator. Don't know if I need to remove synapse and reinstall but it's not telling me a PVS bin....

Went -50 on all frequencies and ran a stability scaling test and passed with flying colors. Heated up the battery pretty nice. Lol

Okay, I think I found it on the info page. According to synapse, it says "a", I'm assuming it's using hex which would make the PVS bin 10. According to /sys/module/clock_krait...(etc etc).... It says 13. Either way, it's a good score.
[Nexus 6 Android Development] bbedward:
I understand but I will miss you :crying:
[Nexus 6 Android Development] Megaflop666:
Nothing against your wonderful kernel... Which technically I'm still running your kernel (lol) ... Just doing some more testing with undervolting and battery between the two, and random fooling around.

---------- Post added at 09:30 PM ---------- Previous post was at 09:25 PM ----------

-60mv scaling test passed. Can't go to -70 and test it yet, my phone is on fire after two scaling tests. Lol
[Nexus 6 Android Development] Xileforce:
Yup so your a bin 10 but u use the bin 13 voltage table. I'm a bin 5 and also use the bin 13 table. I have 0 clue why this is, but I saw someone ask imoseyon which one was correct and he said its the bin 10 one. I'm currently undervolted -60. No reboots....but I haven't tried a benchmark or stability test yet... U so lucky with ur fancy bin 10 :( also I don't want you to hang out with that bbedward guy anymore! He's a bad influence. :P
[Nexus 6 Android Development] Megaflop666:
But [MENTION=2632235]bbedward[/MENTION] offered me candy to get into his thread.

[MENTION=4517211]Xileforce[/MENTION], go download stability test from part store and use the scaling test, it works better than antutu and a lot of the other crap out there.
[Nexus 6 Android Development] Xileforce:
I knew he was a shady character, but I never knew he would resort to bribes! In other news, I shall download the stability test app :)
[Nexus 6 Android Development] Xileforce:
Working well using brianTX's settings!
[Nexus 6 Android Development] BrianTX:
I just want to add my experience with this, I posted this a while back with screen shots. Any way, I had the Google services wake lock which prevented my phone from deep sleeping but it did sit at 35mhz for hours. The drain was only about .5%/hour higher than deep sleep. I was blown away. When I had this same wake lock on two other kernels the phone got hot in my pocket and was draining around 11%/hour which is around 8.5%/hour more than when it sleeps normally. That's my real world experience to go with the theory.

---------- Post added at 11:05 PM ---------- Previous post was at 10:59 PM ----------

I've had this on my mind for a while now, maybe one of the great minds in here knows the answer. Why doesn't the gpu idle when the phone is charging? I can understand why the cpu goes crazy, but the gpu just sits at 110mhz instead of dropping to idle like it normally does. It's just been bugging me ever since I bought system monitor.
[Nexus 6 Android Development] Xileforce:
Hmmm... I'll have to plug in myself and take a look but my guess would be that since its plugged in it figures there's no need to conserve power and enter what is essentially the GPUs sleep state, so it just let's it idle at the first state instead. Likely the same reason that the CPUs won't deep sleep while charging too. Because its going to have to ramp up to 110 anyways as soon as pretty much anything happens on screen and since 27mhz is only for saving power it makes sense I guess.
[Nexus 6 Android Development] lasset:
I'm on Teamsek rom V10 and installed Vindicator 2.1.-0. After reboot I get "Diskspace soon ending" and I can not install any more apk. What's I' missing?
[Nexus 6 Android Development] bbedward:
I suspect GPU freq is related almost directly to normal suspend/sleep/idle activity.

Your phone is charging it never goes into deep sleep, probably because it isn't really necessary but also because the kernel is sending constant events to the userspace (it received battery percent changed notifiers among other things). The constant reading of these events would probably wake up the phone out of suspend constantly anyway.

As for the GPU not sleeping, I haven't observed it myself but if it's the case I presume it's because it's operating based on the same standard msm-pm/suspend driver as the CPU.

Probably wouldn't be a bad idea to work with the driver to suspend the GPU even while charging, but probably isn't really worth making a big deal of (the GPU is certainly drawing less power than the cpu cores on that silicon). With the turbo charger we're not really charging slow either way :p

(+1 for me)
[Nexus 6 Android Development] bbedward:
I haven't dug deep into the patch that makes the GPU display 27MHz while screen is on anyway. But the way it's implemented seems a little sketchy to me. (It just shows 27MHz by using the GPU frequency array floor - 1 to show the power state.

In other words I'm not sure its showing the actual frequency, but it tests if the device is in an idle state and just displays the very minimum frequency (which may not be the actual frequency but because the device is idle it shows that regardless)

Device idle or suspended is just never happening while charging

(So by the logic of the patch it will never show anything lower than the active frequency if device isn't considered idle)
[Nexus 6 Android Development] Xileforce:
Yea I noticed that it literally does -1 lol. Seems kinda weird. I'm not sure why 27mhz also isn't shown in the GPU freq selections either. There's nothing special in the apq8084-GPU.dtsi file on that frequency to tell it not to display so it must happen elsewhere.
[Nexus 6 Android Development] Megaflop666:
Your latest 2.2t2 r2d2 c3po build is running great on 4/22 temasek. That's all...
[Nexus 6 Android Development] jiv101:
How long did it take to boot for you
[Nexus 6 Android Development] Admiral2145:
Does it work with 5.1.1?
[Nexus 6 Android Development] ChaosMinionX:
Here you go...

dmesg, and screenshot of build/kernel and the error in notification panel.

Zen17 works, so I am not sure what might be causing it.

EDIT: might be an issue with the ramdisk... I was using the Zen17 anykernel2 version, let me try the other Zen17 and see if I get the same result.. Might be that the anykernel2 version is leaving the "working" ramdisk intact, where Vindicator tries to implement its own?

Zen17 without anykernel2 does not even boot. Guess its back to the drawing board...
[Nexus 6 Android Development] Megaflop666:
A few minutes. Be sure to clear dalvik and cache after flash
[Nexus 6 Android Development] angiest:
I'm running the Vindi test builds on the latest Chroma (5.1.1) with no problems.
[Nexus 6 Android Development] derekr44:
I dunno, maybe it's just mine. UV causes it to freeze and reboot right after setting it at -50.
[Nexus 6 Android Development] donnellyian:
How does one download the beta builds? That app isn't working for me.
[Nexus 6 Android Development] linus207:
Xileforce. Something it's very wrong with hotplug just after flashing update kernel. Next reboot after that flashing, it's somehow fixed. Look at some graphs when you have new beta flashed. Mines going crazy. Pluging cores, unpluging (and all of that in mako hotplug).

After reboot everything's fine.
[Nexus 6 Android Development] Megaflop666:
Might be something on your end. Haven't experienced that on the latest release or beta.

My vindicator app just started acting funny though.. Tells me my phone isn't a nexus 6. Lol

Just checked build prop and everything is normal in there... Any thoughts [MENTION=4517211]Xileforce[/MENTION] ?
[Nexus 6 Android Development] Xileforce:
Pushbullet also receives beta builds. He is working on an appupdate atm

Not sure, I've never had this happen. Mako will still hotplug though.

If you go to settings what us the device name? I don't make the app but the dev has removed that check in the next version I believe.
[Nexus 6 Android Development] Xileforce:
Interesting...the dmesg seems normal from what I can tell, it could be ramdisk related, I'm not sure what it would be but I guess I'll look through all the changes and see, I'm just not sure why only select few people seem to have this issue :/
[Nexus 6 Android Development] Megaflop666:
Model is nexus 6. Idk of it's because of anything with the new 5.1.1 or what. It was working fine this morning because I had the notification that the new beta build was out.
[Nexus 6 Android Development] Xileforce:
Weird, no clue. He said he's about to release a new update though without that issue and also will have changelogs. So should be out soon.
[Nexus 6 Android Development] USA-RedDragon:
Sorry. Fix+new features has been pushed. Pending play store approval ? should be available in about an hour. Idk why it worked for some people and not for others. I checked build.prop for it.

---------- Post added at 01:11 PM ---------- Previous post was at 01:09 PM ----------

New app update is pending on the play store. Give it about an hour
[Nexus 6 Android Development] derekr44:
Simple question: How does one go about resetting voltages? Reflash kernel?
[Nexus 6 Android Development] Xileforce:
Depends on the app. Easiest way is to just make voltages not set on boot for whatever app you use and then reboot
[Nexus 6 Android Development] __NBH__:
Tested another day with the kernel and something strange seems to be happening. Battery life is fantastic up to a point, then it seems to nose dive. I have attached a screen shot of the battery chart and you can see the deep sleep near the start but it never appears again despite the phone not being awake.

This happened with Chroma 5.1 and again with the latest Chroma 5.1.1. I checked better battery stats but nothing looks wrong?
[Nexus 6 Android Development] Xileforce:
From that picture alone its hard to say. Could you attach a picture of your BBS "other" "partial wakelocks" and "Kernel wakelocks" pages?
[Nexus 6 Android Development] __NBH__:
I have attached some more pics. Unfortunately as you can see from the chart my phone rebooted so I only have stats since the reboot.
[Nexus 6 Android Development] Xileforce:
Its that audiomix man. Its killing ya lol. Also I would disable msm hsic_wakelock using synapse, set it to 0. I don't see any known side effects. As for the audiomix, you may want to try greenifying YouTube or something. I'm not a wakelock expert :(
[Nexus 6 Android Development] __NBH__:
Lol I know, maybe not the best example. I will see if I can get better data tomorrow. It happened yesterday and I wasn't listening to that much music.
[Nexus 6 Android Development] wrongway213:
[MENTION=4517211]Xileforce[/MENTION] just went into a bootloop for like 20mins flashing 2.2test on Temasek 4/22 build. It finally stopped bootlooping when I got hooked up to adb and pulled a log, it just booted instead of pulling a log. So I got ramoops from pstore, it is here. I dunno what that means but worried if my phone is stable or what lol never seen this behavior before . http://hastebin.com/onisorowit.coffee
[Nexus 6 Android Development] bbedward:
Maybe get a logcat if possible because I suspect it's cm12.1 ramdisk related :)
[Nexus 6 Android Development] wrongway213:
Was hoping there'd be something in that file.. looks like it's mostly just showing stuff from my primary though as this is obviously not Unicornblood kernel.. trying to figure out how to get a log on MultiROM when the phone is not in a usable state is not proving as easy as I would like
[Nexus 6 Android Development] Xileforce:
Yea imoseyon was having issues too but apparently got it figured out. Waiting to see what he changed
[Nexus 6 Android Development] bbedward:
You can download his test build and pull it apart.

abootimg -x (or unmkbootimg)

Then gunzip -c initrd.img | cpio -i will get you the ramdisk.
[Nexus 6 Android Development] Xileforce:
Orlly....I never knew that... May try that.
[Nexus 6 Android Development] wrongway213:
I was able to backtrack through catlog and get the partial log but there's SO many errors/debugging as I was trying to pull an ADB log like I mentioed, I don't even know what I should filter for. Any ideas? It's a huge logcat without filtering but I don't know what to do with it as it is, not a typical crash issue...
[Nexus 6 Android Development] Aerigon64:
I just installed better battery stats and installed it as a system app. How do open it? The version in the launcher says its a companion app. Sorry if this is a basic question.
[Nexus 6 Android Development] Xileforce:
After installing it reboot and run normally