yashsingh1/xdaforums huggingface dataset:
[Nexus 6 Android Development] Mistertac:
Well I obviously realize that stats like these are totally subjective but I can say that using ZRam certainly didn't negatively effect my use today at work...

I don't yet know enough about it to make any conclusions myself, but either way, things are still great if you ask me.
[Nexus 6 Android Development] Xileforce:
I posted about this in the FAQs. But essentially I wanted to get it out there and let people test it for a bit to see how useful it is. The CPU cycles used should be less than normal due to significantly updated drivers across the board and using lz4 which will compress and decompress much faster and more efficiently. The other reason I'm giving it a shot is because I've tweaked the vfs, VM and dirty ratios to be much more generous in its use of ram. Theoretically it should keep more stuff in ram and give a performance and battery boost. To offset this I added zram, disabled by default, to essentially give us more free ram. In my testing over a few hours it had already used 20% of my 300mb zram partition. If it turns out to be useless for most people I have no qualms with removing it :)
[Nexus 6 Android Development] philosophics:
I just want to be able to try it out without buying faux clock. Very interested to see results!

Sent by a Whale
[Nexus 6 Android Development] Xileforce:
Search zram on play store. There may be an app to control it. To verify its working go into terminal and type "free" without quotes. If the swap section is all 0s it didn't work.
[Nexus 6 Android Development] philosophics:
Good to know. This leads to another question.

How do I know if my cache partition is f2fs?

Sent by a Whale
[Nexus 6 Android Development] rignfool:
Open terminal emulator...

Grant superuser

Type mount

Find the cache partition

Look for either ext4 or f2fs on that line
[Nexus 6 Android Development] Xileforce:
Awesome man! I was googling an easy way to display it when you posted this :)
[Nexus 6 Android Development] philosophics:
Ya, I would have to say that helps!

Now I know that my cache partition is f2fs but my data partition is still ext4 which I find interesting considering that I thought I made the data partition f2fs as well. Now I have to wipe and go through that process again.

Just wish there was a way to enable Zram without fauxclock. Looked on the play store for an app that could enable, found one but when going to terminal and typing free after enabling Zram, nothing happens.

Epic Whomp sauce!

Sent by a Whale
[Nexus 6 Android Development] Xileforce:
Yup one of my beta testers, makes it. He said there's a patch coming out for it soon to fix it since he moved servers. He's actually gonna be a maintainer for Vindicator on N7 which we r working on ATM.
[Nexus 6 Android Development] Xileforce:
2.2 should be even better! Lots of optimizations, patches and other cool things. Glad you are liking it! Already working on 2.3 :D may have a test build out tonight. With some cool stuff.
[Nexus 6 Android Development] wrongway213:
Highest N6 benchmark I've ever seen
[Nexus 6 Android Development] Xileforce:
In guessing that was at 3.033. I can't run 3.033 even at max voltage :(
[Nexus 6 Android Development] Megaflop666:
Wait, there's going to be vindicator for my n7 too? Get on my n9 too please. :)

You should invite me to your beta team while you're at it. :D
[Nexus 6 Android Development] Xileforce:
Woops weird double post
[Nexus 6 Android Development] Xileforce:
Pmd you :) I'll ha e to take a look at N9. I would be blind building sadly :(
[Nexus 6 Android Development] le1tho:
It was only on 2.88GHz, all 4 cores at 2.88 set with the load threshold at 0, GPU 700/700 with perf governor however GPU still jumps between 27 and 700MHz, only skips the steps between when you set it to 700/700, didn't find any other setting how to make it stick at 700, vsync off, fsync off, encrypted, but seems these last two settings don't have any performance impact. Also in the msm thermal driver there is option for soc temperature, but seem it's not working, because either if i turn it off or on or set it to higher temp CPU still starts to throttle between 70-75, also GPU starts to throttle even earlier at 60-65. Xileforce, can you build into your kernel some really working thermal driver? At least CPU throttling frequency is not that little, but still 80-85 would be much better-nexus 4,5 easily get 100C and it was normal for them(loosy LG-all their phones are always throttling because the do not include any thermal pads on socs, G3 same issue, GFlex 2 same...sad LG), but GPU throttling temp is really crucial for me, because i like to play Asphalt 7 and it gets choppy when GPU reaches 60-65 degrees and will start throttle to 500, 433, 389 MHz. On your 2.0 kernel i was able to set it to higher temp.
[Nexus 6 Android Development] bbedward:
Some adjustments and you'll get the highest benchmark the N6 has ever seen on antutu.

Of course I don't put much stock in it, but people like to push the number :p

Page 200 is mine BTW
[Nexus 6 Android Development] Megaflop666:
I have an n9 to test on. :) your nemesis already wrote one bit it wasn't booting on cm
[Nexus 6 Android Development] bbedward:
My BFS runs great from what I hear though.

The fire-ice guy uses it but his kernels a bit extreme on the edge.
[Nexus 6 Android Development] Megaflop666:
I want to tear it up, I'd love to come off fire ice but it's not booting on latest cm builds. :(
[Nexus 6 Android Development] Xileforce:
Jesus man....2.88? Simms is getting close to that at 3.033. Also fsync actually does effect performance in benchmarks a bit. Adds like 1000 to my score usually. As for thermal stuff, that's not my domain. And I haven't seen any good. Custom thermal stuff yet for n6. I used to use intellithermal but it seemed kinda buggy to me. Ask bbedward he's a software engineer :P I actually think there's a way to disable the thermald service via terminal but I would have to look up the command.
[Nexus 6 Android Development] Xileforce:
This is my first kernel(second counting rebase) so I'm a bit nervous to try building for another device when I don't have it, nor know anything about the architecture. But it may be fun to mess around with :) bfs of course :) . how did your video gaming session go xD
[Nexus 6 Android Development] bbedward:
#stop thermal-engine

Is this a good idea? Probably not. But who am I to get in the way of benchmarks :p
[Nexus 6 Android Development] Xileforce:
Not its a horrible idea but the benchmark calls!
[Nexus 6 Android Development] le1tho:
Can't you make 2.2 or 2.3 with that Intellithermal driver again? For me it was working pretty ok, it was supposed to set CPU throttling temperature, but actually it was somewhat-maybe as a side effect also adjusting the GPU throttling temp-which was good to me :)
[Nexus 6 Android Development] Megaflop666:
Still going on. Already beat assassins creed unity but now I'm running around beating all the little mini missions
[Nexus 6 Android Development] Xileforce:
Lol gotta get those side missions. I love assassins creed. I need to pick up one of the newer ones...last one I played was brotherhood
[Nexus 6 Android Development] Megaflop666:
Oh crap.. get unity, it's amazing

When does n7 vindicator go into testing?
[Nexus 6 Android Development] Xileforce:
Talk to Jacob in hangouts, I think he's got something. I don't have the device, so he's getting all the groundwork stuff done and then imma start helping him.
[Nexus 6 Android Development] wrongway213:
I bought 3 and got sidetracked with life.. haven't played it yet. May revisit that after reading these posts.. 2 was so good lol (I don't really play video games all like that, save for GTA V and UFC Undisputed 3)
[Nexus 6 Android Development] Xileforce:
Haha yea been playing lots of GTA v lately :P probably why the releases have been taking longer xD
[Nexus 6 Android Development] wrongway213:
Literally the best game ever..if you're gonna put off the releases for something that isn't your family, your money or a lady, let it be that, lol.
[Nexus 6 Android Development] MarceloSiciliano:
Hahahaha been playing GTA5 every time, every day!!!
[Nexus 6 Android Development] Xileforce:
Yus!

Lol so true.
[Nexus 6 Android Development] TransportedMan:
How the hell can you make the kernel better than Google/Motorola can? One would think with their virtually unlimited resources they can modifiy kernels and make them run this good for consumers but no.....
[Nexus 6 Android Development] Xileforce:
I honestly ask myself the same question...the 3.10 kernel which we use is already several years old...and there's a lot of easy patches to fix problems and optimize better for our device. So I'm not too sure why google doesn't use them :/ maybe they just want to be rock solid or something. Idk.
[Nexus 6 Android Development] bbedward:
Google/Motorola are partly restricted to what Qualcomm is supporting with their drivers.

If Qualcomm supported newer versions we'd see msm stuff merged on newer android/common trees.

Also other components to a device release that cause neglect to areas like the kernel. Obviously people like you, me, ck, andamy others think the kernel space improvements can make a significant improvement to the user experience. But not everybody sees it this way :)
[Nexus 6 Android Development] Xileforce:
Good explanation! So far today I've brought CPU idle up to around linux 3.16 including the CPU idle governors. Problem is around there they start moving directories and such to make things more generic which then requires upstreaming stuff like preempt and sched.h as well and it becomes a massive hassle O_o but I think what I've got so far should still be a nice update.
[Nexus 6 Android Development] bbedward:
I just wanted to use the gif. I actually don't have a problem with what you're doing.
[Nexus 6 Android Development] Xileforce:
Hehehe I don't even know what I'm doing but I haven't had any issues so far and some of the patches seemed nice.
[Nexus 6 Android Development] Macusercom:
So far so good. I'm using Vindicator 2.2 on CM12.1 today and after 2,5h and 36 min. SoT I have 90%. If this lasts, I will hit 6h. Locked my GPU to 110Mhz btw and under volted everything (-75mV).

Overall entering the PIN feels a bit laggy, but then it is smooth. Not as smooth as with stock, but not annoying after a few minutes. As I'm unlocking my device automatically, I don't realise that it's lagging there and my touches are recognised so all's fine.

Vindicator looks like it's limiting the processing power very heavily, but apps still open very fast. Of course in order to save battery you need to limit performance and it seems that it's set to set minimum performance without interrupting normal usage. Great job!

Gesendet von meinem Nexus 6 mit Tapatalk
[Nexus 6 Android Development] Xileforce:
2.5h sot at 90%??? That's unheard of. I'm usually around 45 mins at 90%. GPU actually renders most of the interface so that could be potentially why you see lags in certain spots when limiting the GPU. In fact 110mhz is a frequency step I added. Stock min is 240, so you may want to try at a minimum 240 min. As for not using all of the CPU power, that really depends on how you have it setup. Default settings should be nicely balanced between performance and battery. Glad to hear you are enjoying it though!
[Nexus 6 Android Development] Macusercom:
LOL I meant I left it 2,5h unplugged and 36 min SoT. 36 min = 10%. 2,5 SoT would be ridiculous hahaha xD

With that I meant it's hardly getting over 2 cores and 1,5 Ghz, but when it needs more power (like opening an app which hasn't been opened before and isn't in the RAM) it quickly decides to clock to 2,6 and use 4 cores for a few seconds instead of having all cores permanently online and clock them to 2,6 like forever.

Will try 240Mhz for the GPU. I just wanted to know what's the max SoT I could get without making it unusable. When using it, it is only slightly slower than stock kernel but completely fine as it saves so much battery for so less performance loss.

EDIT: Setting the max clock to 300MHz the lock screen PIN lag is almost completely gone. Let's see how this affects battery life :P

Gesendet von meinem Nexus 6 mit Tapatalk
[Nexus 6 Android Development] Xileforce:
Haha I see what you meant now lol. And you still may see some lags at 240 but it will likely be a bit better. And yes since we use mako hotplug I've set it up to use 2 cores always default but it will ramp up to 4 if it needs them. Our phones so fast though that it doesnt typically need all 4 cores for most general tasks.
[Nexus 6 Android Development] Macusercom:
Yeah, true. I've locked it to 2 cores with hells-Core kernel and it saved no battery at all. If 2 cores are always at 2,6 GHz it's worse than having 4 online at 1,5 GHz and it was lagging like hell. Reduced the app opening time for 1-4 sec. Your interactive feels like Franco's conservative though (which is awesome). Vindicator seems to handle opening speeds better with lower clocks at the same time. Magic? xP

Gesendet von meinem Nexus 6 mit Tapatalk
[Nexus 6 Android Development] Xileforce:
Magic! And actually my interactive is Franco's interactive and my conservative is his conservative :) although he removed interactive after the 5.1 update when he switched to conservative. So you get both!
[Nexus 6 Android Development] bbedward:
Not for all improvements :)
[Nexus 6 Android Development] Xileforce:
Hehehe vrq vrq vrq! I should go have Jacob pester the vrq guy...he's good at that. We would have a working patch in hours.
[Nexus 6 Android Development] __NBH__:
This might be the wrong thread for this question but if I've made kernel changes in synapse or kernel auditor, how can I reset everything to get back to the kernel default?

I've tried uninstalling the apps but after reinstalling it seems to remember my settings, I searched for settings files but couldn't find any?
[Nexus 6 Android Development] Xileforce:
In synapse on the tools page there's a button to clear synapse data. For kernel aduitor I would try making all the settings NOT set on boot and then simply reboot the device. If you uninstall the app but don't reboot the settings will stick :)
[Nexus 6 Android Development] le1tho:
Intellithermal please? :)
[Nexus 6 Android Development] USA-RedDragon:
Soon. I soft bricked my n7. Lol
[Nexus 6 Android Development] linus207:
Hello. New kernel seems to be little bit more power hungry when screen is on.
[Nexus 6 Android Development] Megaflop666:
Odd, I was just coming in to point out the exact opposite, seems like better battery here.

I wasn't able to get a log because I was driving but I got a reboot earlier. It was in an area I know my phone switches towers, I was on the phone on a call, so I'm thinking that the tower switch caused a kernel panic. If it happens again, I'll pull a log.
[Nexus 6 Android Development] Macusercom:
Ok, so first day on Vindicator 2.2 with CM12.1 (28/04/2015) with GPU to 110MHz/230MHz/300MHz max (tried 3 settings today) and undervolted CPU with -75mV using Interactive governor and stock clocks. It was charged at 5:45 AM and now we have 6:45 PM. I've included everything from screen brightness to wakelocks. I've used GSam Battery Monitor btw. It is better than stock (4,5 SoT at max) but looks like 5 SoT seems reasonable, but not more :/
[Nexus 6 Android Development] Xileforce:
Definitely looks to me like you have some wakelocks going on. If you use synapse you can try going to the "misc" page and at the bottom set msm_hsic wakelock slider to 0. Also do you think you could install better battery stats and run for awhile then get me a screen shot of the "kernel wakelocks" page. I've never used gsam but I'm not seeing any kernel wakelocks showing up in it. Maybe I'm blind.
[Nexus 6 Android Development] bbedward:
http://cchalpha.blogspot.com/2015/04/vrq-04-update-for-linux-40y.html?m=1

ETA plz?
[Nexus 6 Android Development] Xileforce:
In theory you should get better battery life (updated bfs and CPU idle is updated significantly) cpuidle driver is what controls the phone going into sleep states like retention and power collapse. It actually uses these cstates when the screen is on and when your processor is on. So even if you have all 4 cores on. Its very likely that at least 3 of them are sleeping unless you are doing something intensive. Thus a more efficient cpuidle driver should save battery but who knows.

Interesting. Hopefully it turns out just to be tower switching! Do you disable msm_hsic wakelock? I too seem to be getting the best battery yet.
[Nexus 6 Android Development] Macusercom:
I have Wakelock Detector installed. I guess you were asking for these wakelocks? I'm not using synapse. Still using the Franco kernel app. Could try synapse though as I don't use Franco anymore.
[Nexus 6 Android Development] Xileforce:
YES! ETA! :D :D :D Hopefully its not broken still!!!
[Nexus 6 Android Development] LunaticSerenade:
What is the bcmdhd wake lock?

Sent from my Nexus 6
[Nexus 6 Android Development] bbedward:
Some of my upstream_bfs_gc has prerequisites added specifically for the vrq expansion. So you shouldn't have too hard of a time.

Just PM me when you are done :)
[Nexus 6 Android Development] Xileforce:
Hmm wakelocks look pretty good. Msm hsic is your highest but its only 8 minutes. You could still disable it to save some extra battery life though. You may also want to try the latest test build. It seems like you you use your phone quite a lot through the day in which case 5h sot isn't terrible. I usually get around 6h but I charge up around 30% so I can only guess. Here's a link to the latest test with CPU idle and bfs improvements among other power saving patches.

https://docs.google.com/file/d/0B6n0VW96A9MoenAzX3lBb2NfZUk/edit?usp=docslist_api
[Nexus 6 Android Development] Xileforce:
I will try when I home from work! :D I'm no software engineer though so don't expect miracles!
[Nexus 6 Android Development] Xileforce:
Bcmdhd controls the wlan_RX wakelock ;)
[Nexus 6 Android Development] bbedward:
I called off work because I have a bajillion things to do :P I will try to work through them quick and put them in a sched_upstream_bfs_vrq branch
[Nexus 6 Android Development] Macusercom:
Google Play Services need about 8% for 75% of battery. I guess this is normal right? IMO this even counts for app push notification or for receiving them. I could try reducing WhatsApp's wakelocks as it uses 5% and I've only used it like 5 times today. Tasker shouldn't be 18 min normally it keeps my device awake for 3-5, but I experimented with new settings today.

Yeah, I'm using my phone quite heavily. This happens when you have 8 hours of compulsory community service a day and got nothing to do haha xD So maybe 5 hours aren't so bad at all. The battery has about 7 cycles now so it should have its max capacity. I will try synapse now even though the first start up got me an instant OS crash :P

I will use Vindicator 2.3T1 tomorrow. Still hoping that WiFi battery usage is better with Vindicator. On my OnePlus One I got 4-4,5h SoT on mobile and 6-7 on WiFi. Now I get the same SoT or even worse when WiFi enabled.

EDIT: And btw you're awesome for always replying so fast. I'm almost thinking you're just sitting somewhere refreshing the page to reply to my posts xD
[Nexus 6 Android Development] Xileforce:
Yay another branch! Well I guess I won't bother now lol. Ur probably already done and likely coded a completely custom thermal drive too just for fun since my last reply.
[Nexus 6 Android Development] Xileforce:
Yea google play services actually has a issue in some builds that keeps the phone awake almost constantly and doesn't show up in kernel wakelocks. In fact the wakelocks page says your phone was awake for like an hour so something isn't showing up that's really killing you. You can try updating your play services to a newer one. And yes when I'm bored I literally refresh like every few minutes xD and I get emails.
[Nexus 6 Android Development] purian23:
Yeah he does this a lot LOL. He's detailing ideas or changes one min, then the next he's done or scrapped it. Started over or another test haha
[Nexus 6 Android Development] Megaflop666:
Yes
[Nexus 6 Android Development] Xileforce:
Lol ikr. It takes me five minutes to scroll through his branches. I was merging commits from the vrq_exp branch. Finished and compiled. Then noticed in the five mins i had done that, a new branch labeled vrq_less_exp had appeared...lol

I wonder if maybe having it disable screws it up when switching towers.
[Nexus 6 Android Development] Megaflop666:
I'll switch it to stock and see
[Nexus 6 Android Development] linus207:
Okay Xileforce, knowing that you're bored I have a question. What rom would you recommend from cm 12.1 series? Are there any worth trying?
[Nexus 6 Android Development] Xileforce:
I personally run Euphoria, but I tried Temasek when I was testing ramdisk stuff and it seemed quite fast.
[Nexus 6 Android Development] Macusercom:
Do you have any more recommendations which settings I should change in Synapse? It gives me tons of options I've never heard of :o
[Nexus 6 Android Development] linus207:
So I will try it. I am using chroma now but... You know... I have fully loaded kernel so also fully loaded rom would be nice.

Speaking of kernels. I really don't like how mako hotplug works. It's nasty and laggy. Turning on msm feels like a relief for me. Of course I am lowering some parameters to avoid drainage but overall idea of mako is not my thing. Do you really think that 2 cpus running running 3 ghz (for a moment of course ) are more power efficient that 4 running 1.2? Maybe I am wrong but I am just not buying it.
[Nexus 6 Android Development] Xileforce:
You can make mako run in quadcore mode by simply setting load threshold to 0. And idk. I'm torn. I asked bbedward and he seems to think its pretty close with bfs because bfs makes hotplugging less expensive. It really would depend on your usage. If you are doing something like listening to music or watching a movie. Likely you would benefit from letting it drop down to only two cores because having for cores would be overkill for that. Additionally with four cores, every time you touch the screen and it activates touchboost, you are now boosting 4 cores to 1497mhz instead of only 2 thus using 2x the power in essence. But then you have the benefits of in general spreading the load out and likely running lower frequencies on the four cores which saves battery. I personally dislike msm hotplug because of the way it hotplugs. For instance if you set msm hotplug to 2 core minimum and 4 core maximum. Unlike mako which always keeps cores 0 and 1 on min. Msm will always have core 0 on but then it may plug core 3 for the second core, then decide to unplug 3 and plug in core 1. And it just seems to bounce around a lot which obviously isn't very efficient. If you just want 4 cores I suggest using mako with load threshold at 0. Only reason I don't default mako to 4 core mode like Franco is because some people just love their hotplugging :P
[Nexus 6 Android Development] linus207:
So why just switching between apps it's much more smooth on msm? I am talking about animations and overall feeling . Maybe that's gpu thing then...
[Nexus 6 Android Development] wrongway213:
Cannot recommend Temasek's CM12 enough.. runs AWESOME with this kernel now that it's running lol
[Nexus 6 Android Development] Xileforce:
Likely because by default msm is much more generous in onlining more cores. Mako by default must reach 80% load before it will plug more. You can adjust this with kernel aduitor or synapse via load threshold. Lower means more hotplugging.
[Nexus 6 Android Development] bbedward:
FYI:

https://github.com/bbedward/ZenKernel_Shamu/commits/sched_upstream_bfs_vrq

I only tested it up to this commit, the rest is build tested:

"bfs: [3.10] vrq: implementation cleanup and fixes - correctly set pro…"
[Nexus 6 Android Development] bbedward:
[MENTION=647113]hellsgod[/MENTION] [MENTION=4517211]Xileforce[/MENTION] won't boot with " preempt task solution" commit.

I don't have time to investigate tonight anymore :) but you can investigate it for bugs or revert and try running it.
[Nexus 6 Android Development] Xileforce:
I've run the git reset command about 100 times today, so I'll play around with it :)