yashsingh1/xdaforums huggingface dataset:
[Nexus 6 Android Development] TheySaidWhat?!:
Thank you.
[Nexus 6 Android Development] Xileforce:
Thanks a bunch for this! I'll definitely add this to the guide and explain it!
[Nexus 6 Android Development] TheySaidWhat?!:
Thank you. And I'll give it a try :)
[Nexus 6 Android Development] Xileforce:
Please report back if I works!
[Nexus 6 Android Development] TheySaidWhat?!:
Certainly will, I'm giving my nexus a full charge then going into to work tonight while giving it use and observing.

I'm only using FKupdater to tweak the scheduler to deadline as well keep the cpu set to conservative and I'll leave the other settings on default. I like to apply minimal tweaks, is that Ok?
[Nexus 6 Android Development] Xileforce:
I suggest FIOPs over deadline. Idk if FKU let's you bet setting the read ahead buffer to 1536 also greatly helps IO performance. Just make sure you use an app such as trickster to turn off mpdecision. If you turn off mpdecision and don't enable intelliplug it will use Franco's hotplug. I did a pretty big write up on the third post that may help you. Hope you like it!
[Nexus 6 Android Development] TheySaidWhat?!:
FKU didn't have FIOPs in the selection. But it had deadline. And I reconsidered the minimal tweaks and will get trickster from the play store to do it right from top to bottom. Thank you. And will gladly report overall behavior after a full day (or night for me) of use :)
[Nexus 6 Android Development] Xileforce:
Sweet! Hope I works well for ya. Its weird that you don't see fiops as a choice. I just looked and it shows for me in fku.
[Nexus 6 Android Development] TheySaidWhat?!:
How? Am I overlooking a setting to get it to show? My options in FKU scheduler are noop, deadline, and cfq. But as long I can select it via trickster it's a non issue.

And that write up is rather interesting! And informative! Thanks for the share.
[Nexus 6 Android Development] Xileforce:
Thank you for clarifying sir. I hope nobody bugged you about this implementation. As I've said before I myself don't know much about the whole multirom deal. In fact, I've only used it once and that was to make sure it worked following the steps given to me by jamcswain before I pushed the build. Will be sure to merge your full patch as soon as its release :) Apologies for any trouble I may have caused.
[Nexus 6 Android Development] MarceloSiciliano:
Does vindicator 1.5 have support for 5.1? I tried flashing it on the stock ROM and it gave me a bootloop
[Nexus 6 Android Development] Mistertac:
It's not quite there yet no. You'll end just optimizing apps in an endless loop. He's working on it.
[Nexus 6 Android Development] MarceloSiciliano:
Yeah this is exactly what happened hahahaha
[Nexus 6 Android Development] jamescable:
We are working on it, and not saying this to u...but to everyone who reads this, do not ask for ETAs please....we will give it when we can
[Nexus 6 Android Development] Xileforce:
Yea imoseyon already managed to merge the latest changes into lean and is fixing up the remaining bugs now. He said it wasn't too bad. I may just wait for him to push and pull his chamges that way I can stay synced up with his work. Depends on how long it takes before he pushes though.
[Nexus 6 Android Development] StrifeSoldierVII:
Rocking the latest kernel update with Android 5.1. Great so far, and it's awesome that there's already a custom kernel with 5.1 support! Great work.
[Nexus 6 Android Development] Xileforce:
Wait what? How u do dis? Ur running 1.5 on android 5.1?? What ROM? You may have somehow altered science!
[Nexus 6 Android Development] StrifeSoldierVII:
Lol I like that, but I don't think I did. I just downloaded and flashed the 5.1 R2 version of the kernel. Working great so far.
[Nexus 6 Android Development] Xileforce:
Lol despair kernel ;) but hey, I'll take credit for that :P may want to pass your thanks on to despairfactor, he switched to anykernel which let's it boot on different android versions ;)
[Nexus 6 Android Development] StrifeSoldierVII:
Oh true, my bad. I just got excited to already have a custom kernel for 5.1. It's been barely a day or so. I tapped the wrong thread in the XDA app.
[Nexus 6 Android Development] Xileforce:
Lol no problem. xD I'm fine with OT stuff :) and correction, it looks like he's actually started over based on google 5.1 source not anykernel anymore. Cool to hear its working though! Progress has been made!
[Nexus 6 Android Development] USA-RedDragon:
Looking forward to full 5.1 support
[Nexus 6 Android Development] stevepick2:
Missing Vindicator already. Looking forward to the 5.1 build
[Nexus 6 Android Development] Xileforce:
Should have it today. Was going to do the merge myself. But imoseyon said he's gonna release today so, I figured I'd just wait for him to push all his changes instead. Lol
[Nexus 6 Android Development] aoaleman:
Hey Xileforce, I wonder if your 5.1 kernel will still have the kexec patch for MultiROM.?
[Nexus 6 Android Development] USA-RedDragon:
It will. And I'm working on getting some of the bugs out. There is one major bug keeping us from using all features of multi ROM. If it can't be fixed we're going to revert it and wait for Tasssadar's official patch
[Nexus 6 Android Development] aoaleman:
Wow, thanks a lot!
[Nexus 6 Android Development] Xileforce:
5.1 compatible build is up! :D retains all features of previous builds, simply merged all the latest and greatest 5.1 stuff in. Also has new lean kernel stuff and new franco stuff. Plus IntelliPlug v4 update and some other things! Have Fun!
[Nexus 6 Android Development] aoaleman:
Thank you! Thank you!
[Nexus 6 Android Development] Xileforce:
No problem, hope it works OK. I haven't even personally tested it yet. Just the beta testers. I'm not on 5.1 yet. BTW for anyone reading this do not flash 1.6 if you are on 5.0.2!!!! 1.6 is 5.1 only! Also the testers didn't test multirom but I imagine it should be unaffected by the update.
[Nexus 6 Android Development] aoaleman:
So far it's running good. Kexec, speed, faux sound, everything I need in a kernel. :)
[Nexus 6 Android Development] LunaticSerenade:
Running well on stock 5.1
[Nexus 6 Android Development] Xileforce:
Awesome! Good to hear its running well for eveeryone. Now that all that nonsense is out of the way its back to doing real updates :)
[Nexus 6 Android Development] blackhartct:
Sry to be a party pooper but in synapse when I try to disable mpd it automatically re-enabled it. Anyone else get that on 5.1?
[Nexus 6 Android Development] MarceloSiciliano:
im finding the1.6 highly unstable on the stock ROM. It keeps rebooting even without undervolting or overclocking

Even Fixing permissions on faux clock it seems that the settings simply dont stick! Very weird!
[Nexus 6 Android Development] Xileforce:
Hmmm. Can you check sys/fs/pstore/console-ramoops after u get a reboot and post the file here please? I'll be able to try and figure it out.
[Nexus 6 Android Development] Xileforce:
Could u try another kernel app? I'm not yet on 5.1 due to lack of Roms and issues with all sorts of stuff, but maybe some things tweaking out with synapse and the new mpd.
[Nexus 6 Android Development] MarceloSiciliano:
Sorry Xileforce, i really dont know how to do that :(

Can you explain to me please?
[Nexus 6 Android Development] Xileforce:
Sure, no problem. Basically you just use a file browser like root explorer. It has to be able to browse root. Then you just navigate to the directory I told you :) BTW the root directory is "/" you may have go go to that first then the directory I listed earlier.
[Nexus 6 Android Development] hellsgod:
On 5.0 it was enough to disable rq_stats and mpdecision was disabled automatically on boot (thats the only culprint I had why it was disabled as I booted up first with blu_plug on 5.0). On 5.1 I had to disable it in the ramdisk to get rid of it. Maybe some of your tester checks, if mpdecision is really disabled on boot and don't interfere with the built in hotplug solution. Or do you bootup with mpdecision default?

hells
[Nexus 6 Android Development] MarceloSiciliano:
Im trying, but it keeps rebooting:( and the settings just dont stick

---------- Post added at 09:48 PM ---------- Previous post was at 09:43 PM ----------

The folder pstore on root explorer is empty Xileforce
[Nexus 6 Android Development] Xileforce:
Yea check it after your next randm reboot and it should have stuff in it :)
[Nexus 6 Android Development] MarceloSiciliano:
https://drive.google.com/file/d/0B5bBJs9AXrmJaGlnNGk1SUhlWEE/view?usp=sharing

Made it!
[Nexus 6 Android Development] Xileforce:
Hmmm interesting. Kernel does boot mpd by default, but I'm not sure why you wouldn't be able to disable it via any normal kernel tweaking app. The beta testers are busy trying to get the kernel working with a test build of euphoria ATM. Once we get that working ill be able to test mpd stuff hopefully.
[Nexus 6 Android Development] hellsgod:
[ 196.380413] Unable to handle kernel NULL pointer dereference at virtual address 00000020
[ 196.380433] pgd = c495c000
[ 196.380440] [00000020] *pgd=00000000
[ 196.380454] Internal error: Oops: 5 [#1] PREEMPT SMP ARM
[ 196.380465] CPU: 3 PID: 366 Comm: mpdecision Tainted: G W 3.10.71-Vindicator_1.6- #1
[ 196.380473] task: f2820540 ti: c49ba000 task.ti: c49ba000
[ 196.380498] PC is at __cpufreq_governor+0x10/0x124
[ 196.380506] LR is at store_scaling_min_freq+0x80/0x9c
[ 196.380513] pc : [<c06a390c>] lr : [<c06a5860>] psr: 600f0013
[ 196.380513] sp : c49bbe50 ip : 00000000 fp : 00000001
[ 196.380519] r10: c49b48a4 r9 : c06a35b4 r8 : c49b4840
[ 196.380524] r7 : c0fcc7b8 r6 : 00000003 r5 : c49b4840 r4 : c49b4840
[ 196.380530] r3 : 00008bd8 r2 : 00000000 r1 : 00000000 r0 : c49b4840
[ 196.380538] Flags: nZCv IRQs on FIQs on Mode SVC_32 ISA ARM Segment user
[ 196.380544] Control: 10c5787d Table: 0495c06a DAC: 00000015

It seems to me mpdecision was online and wasn't happy about mako_hotplug.

hells

---------- Post added at 11:02 PM ---------- Previous post was at 11:00 PM ----------

Maybe it was just a Synapse derp? I could disabled mpdecision with Trickster Mod as I tried it on fully stock.

hells
[Nexus 6 Android Development] Xileforce:
Def something up with mpdecision but where do u see mako? Its saying the error is at the CPUfreq_governor. I'm a log reading noob tho :(
[Nexus 6 Android Development] hellsgod:
[ 180.850401] mako_hotplug: all cpus were offlined
[ 183.045176] mako_hotplug: all cpus were onlined
[ 183.354897] mako_hotplug: all cpus were offlined[ 180.850401] mako_hotplug: all cpus were offlined
[ 183.045176] mako_hotplug: all cpus were onlined
[ 183.354897] mako_hotplug: all cpus were offlined

So it seems mako_hotplug was interfering.

hells
[Nexus 6 Android Development] Xileforce:
Good eye! Although mako should only be active if mpd is disabled. So now I'm thoroughly confused :/ have u had any reboot issues hells?
[Nexus 6 Android Development] hellsgod:
I'm not using your kernel, sorry. I'm just jumping between some kernel threads and if I see something I try to help out :)

hells
[Nexus 6 Android Development] Xileforce:
lol well thanks for ur help. once i get the theme manager stuff figured out i guess ik what ill b looking into next.
[Nexus 6 Android Development] Xileforce:
Woot! Just fixed theme manager issues, and testers are reporting camera is fixed too...not really sure why camera would work but OK. Lol
[Nexus 6 Android Development] ahmarchi:
I was having a lot of issues using 1.6 with fauxclock. Especially when going into the hot plug tab and and using intelliplug and turning off touch boost. Usually caused a full restart. Some of the settings would not stick with CPU and only 2 cores were working. Say an app would install. The CPU load would only use 1 core at 100% when done smooth with 2 cores but no 4 cores online. Aside from that I love the speed and the oc GPU. Really makes a big diff. Once a few more fixes you have yourself another user. Great job
[Nexus 6 Android Development] Xileforce:
Thank you for the report! So many things to fix in 5.1 hoping to have them fixed soon
[Nexus 6 Android Development] elevatorguy:
Question. Using synapse, under msm limiter is the suspend max frequency the same as screen off max frequency? Also what does suspend defer time do? TIA
[Nexus 6 Android Development] Xileforce:
Quite honestly idk what that stuff related to msm limiter does. I may take a look through the code and see if I can figure it out. Or see if I can't find a bit better documentation. The screen off I use is interactivex.
[Nexus 6 Android Development] stevepick2:
Does the kernel have sepolicy commits?

Was going to try latest Euphoria, but most kernels are not compatible with it now
[Nexus 6 Android Development] Xileforce:
Been working with euphoria Dev for last few days. We've had a build for a day or two working with it. Will prob release tomorrow. Current implementation is pretty poor. Temp fix is flash the permissive.zip in the op after kernel and boot. Should work.
[Nexus 6 Android Development] MarceloSiciliano:
Xileforce i tried your kernel with sinless ROM and the result is instant reboot, just like with the stock google rom
[Nexus 6 Android Development] clnzx2:
Try flashing the permissive zip right after the kernel before rebooting
[Nexus 6 Android Development] daleski75:
Getting random reboots as well with vindicator 1.6
[Nexus 6 Android Development] spd2230:
I was getting SOD and random reboots when trying to use Wheatley on the first two cores. I disabled all of my tweaks in Synapse and re-enabled them one by one over several days to narrow it down. I haven't had time to look at the governor settings to see if I can get Wheatley to play nice. No issues whatsoever otherwise. Excellent kernel.
[Nexus 6 Android Development] Xileforce:
So you think Wheatley may be the cause? Interesting. Its possible there's some weird bug that cropped up on 5.1 I'll have to investigate further :P
[Nexus 6 Android Development] Xileforce:
1.7 is out! As usual change log in second post! May fix some stability issues.
[Nexus 6 Android Development] dannieloco:
After I've disabled MP decisions, dropped GPU to 300mhz, switched to Wheatly, Undervolted a little, and a few other things, Im still only getting 2 hors of Screen On time. Im not the most knowledgable about these settings and could appreciate some more advice to help me achieve better SOT. thanks!
[Nexus 6 Android Development] Xileforce:
Check your wakelocks, I heard the newer gapps don't allow deep sleep
[Nexus 6 Android Development] Mistertac:
Use Better Battery Stats and see what your Partial Wakelocks are. Or Wakelock Detector is also good.

So much depends on usage, but you should be able to get at least 4-5 hours screen on time I'd think.

What ROM are you running? If it has Privacy Guard ( aka App Ops ) go into its settings and tick off "Show All" then go and find Google Play Services, next go to the very bottom and Disable " Keep Awake " only. That will get you deep sleeping better and that issue has been killing all of us for the most part. Good place to start.

The next thing to think about with the Nexus is.... Less is more I believe when it comes to kernel tweaking. Meaning.. I've not had to do too too much to get great battery life. Try Interactive governor and have stock clock settings, and then try simply changing your Input Boost Freq to like 1ghz to start. If it's still smooth, next try Under Volting by only -25. If things are still smooth and to your liking, then start to tweak further but you may realize you don't even need to.

I've found if I change to many things at the same time, it's obviously hard to pin point what may cause an issue if i have one... And there's also some who change all sorts of stuff only to get much worse battery life.. Like yourself [emoji6]
[Nexus 6 Android Development] fahadali2315:
New apk for google play services is up... At apkmirror.com

So that wakelock should be gone..phone should start sleeping like a baby again after updating :)
[Nexus 6 Android Development] dannieloco:
Hey! so I am running Chroma ROM and it doesn't have privacy guard. I switched from Wheatley to InteractiveX per your advice and because i had a few random reboots. I just made the Input Boost frequency 1ghz. and undervalued -25. I have installed the Wake Lock Detector and used Amplify app to disable a few wake locks from picture editing apps i have (though i have no idea what a wakelock is or what it does). Ill give this a try and hope for a longer SOT. Ive never been one to care about SOT but it'd be amazing to see 5+ hours of it. :D

---------- Post added at 02:54 PM ---------- Previous post was at 02:51 PM ----------

alright, just installed, I was running 6.7.76 before updating. How do u know the new Play Services is bug free or whatever..?
[Nexus 6 Android Development] fahadali2315:
Because i finally started to get some deep sleep on 5.1 :)

And nomore wakelocks from playservices.
[Nexus 6 Android Development] Xileforce:
I typically seem to hit 50-60% with about 3h sot. So I'm on track for around 6 and I'm a pretty heavy user. Obviously running 3D games is going to kill your battery faster. I usually charge before I get past 30% though so I never actually test. But let us know how those settings work for you. IK mistertac has some pretty good settings. He usually hits 7h.
[Nexus 6 Android Development] Mistertac:
If your ROM doesn't have Privacy Guard or App Ops you can always just grab one from the Play Store for free...

https://play.google.com/store/apps/details?id=com.findsdk.apppermission

I helped contribute to the running list of Alarms and Wakelocks for the Amplify Module.. It's a great Xposed Module but I've been holding off on running Xposed on Lollipop. Just be careful using Amplify too because you can end up limiting things you need lol just do your research that's all my friend and good luck.
[Nexus 6 Android Development] Xileforce:
Just move over to the new euphoria 5.1 from android 5.0 so I can better test now. I'd like to point out that you guys should check your minimum frequencies. I just noticed that my cores weren't going below 1.5ghz even though the min was set at 36mhz. Setting the min to something else then back to 36 fixed it. Not sure if its a synapse bug or a msm limiter bug. Or maybe I screwed up somewhere but I had it happen once before too back on 5.0. Anyways just a heads up.
[Nexus 6 Android Development] MarceloSiciliano:
Im on euphoria too! I cant ajust the vibration, IO/scheduler, but CPU frequencies are working!
[Nexus 6 Android Development] markwebb:
OTG USB didn't work for me on this latest version: had to go back to 1.6.
[Nexus 6 Android Development] Xileforce:
Hmm seems you are right with the vibration issue. Did this also not work on 1.6? However my io scheduler and everything else tweaks fine.
[Nexus 6 Android Development] Xileforce:
Hmm interesting. I'll look through my commits and see if I poked USB stuff :P thanks for letting me know
[Nexus 6 Android Development] MarceloSiciliano:
The vibration worked on 1.6

This is what i see on the I/O page
[Nexus 6 Android Development] Xileforce:
That's... Weird. Have u tried using synapse? Cuz I'm using synapse and it worked fine for me :/ or maybe try uninstalling or clearing data for faux.
[Nexus 6 Android Development] MarceloSiciliano:
Euphoria bugs started to apear so i tried stephan rom and when i opened fauxclock and changed the max frequency to 2,6 i had a reboot
[Nexus 6 Android Development] Xileforce:
That's not normal. I and all 10 or so beta testers haven't had an issue. Was the reboot only on Stephens? Also nearly all the beta testers say that fauxclock has given them reboots in the past so they stopped using it. I would try synapse. It has every option.
[Nexus 6 Android Development] VerdammteSeele:
1.7 bugs

I ran into problems with 1.7 too on Chroma 5.1 version 3/16/2015 and the fauxclock app. Vibration control is stuck at 0, I/O schedulers don't populate in the drop-down list, color setting are stuck at 0, and most other settings keep reverting back to defaults. I flash 1.6 back with complete success.

As for fixing 1.7 I tried reflashing ROM, GAPPS, and clear cache at various points in several ways, but nothing made a difference. I did reinstall fauxclock, but I did not try other kernel mod apps yet. I'll provide anything I can to help.
[Nexus 6 Android Development] Xileforce:
Give synapse a shot. If that's broken too then that narrows it down for me.
[Nexus 6 Android Development] LunaticSerenade:
Using 1.7 with Synapse, and the only issue I had was with fauxsound changes sticking. Enabled it with lkconfig, and it's sticking fine now.
[Nexus 6 Android Development] Xileforce:
So maybe all this is just fauxclock bugs? BTW just curious but are u guys using beta of fauxclock?
[Nexus 6 Android Development] Drefsab:
I've had an odd issue with synapse it just sits at the loading screen 10mins later its still loading. That's with chroma 5.1 3/16 build and kernel 1.7 anyone else had that or should I go log hunting?
[Nexus 6 Android Development] Mistertac:
If anyone wants to rule out Synapse or Faux acting up just use Kernel Auditor. It's free and very good. I've actually been using it lately myself.

Also keep in mind Synapse needs 2 full minutes after reboot for settings to take effect...
[Nexus 6 Android Development] knitler:
Just use LKconfig and be done with it. I don't see the reason to buy/use another UI unless you are doing color calibration or undervolting.

---------- Post added at 10:10 AM ---------- Previous post was at 09:55 AM ----------

I have 1.7 and AnTuTu is crashing and causing a reboot for me. I have all clocks/settings at default.
[Nexus 6 Android Development] Xileforce:
At what part does it reboot? Also u may want to try bumping voltages 25 for a benchmark just in case and maybe lowering Max GPU to 600. As for lkconfig, you can tweak half the stuff synapse can. I just ran antutu fine :(
[Nexus 6 Android Development] knitler:
I'll try the 25 bump, but on Leankernel I generally am fine even with a -50 uv from stock voltage.

It crashes at about 40% its one of the CPU tests, forget what one.
[Nexus 6 Android Development] Xileforce:
Yea, I ran antutu at -25 yesterday so I'm not sure what's going on. What ROM are you currently running? Also which hotplug are you running?
[Nexus 6 Android Development] knitler:
Completely stock.
[Nexus 6 Android Development] Xileforce:
So mpdecision? Hmm try switching to intelliplug and see if that let's you get through antutu. I've had a few bug reports with mpdecision in the logs.
[Nexus 6 Android Development] 9wire:
I'm on benzo ROM 5.1, unfortunately this breaks my camera.
[Nexus 6 Android Development] Xileforce:
Can works fine on euphoria. Have u tried other custom kernels on benzo.
[Nexus 6 Android Development] 9wire:
No, the ROM includes a modded kernel. Camera works on it, everything but camera works on vindicator.

Edit:ROM comes with lean kernel.
[Nexus 6 Android Development] Xileforce:
Could u try flashing leankernel zip from the lean thread? Its just that building the kernel inline with ROM is a completely different ramdisk. This would help narrow down the issue.
[Nexus 6 Android Development] 9wire:
There is some talk in the ROM thread about custom kernels breaking camera, dev is compiling a new build I guess, we'll see.
[Nexus 6 Android Development] Xileforce:
Sounds good. Keep me updated. Its probably a ramdisk issue with custom kernels.
[Nexus 6 Android Development] gamewarden234:
On euphoria multirom and camera work perfect. Thanks for the only kernel that seems to work with multirom
[Nexus 6 Android Development] USA-RedDragon:
You're welcome ^-^
[Nexus 6 Android Development] VerdammteSeele:
Synapse vs FauxClock

Everything sticks with Synapse on Chroma 5.1 build 3/18/2015 on Vindicator 1.7. FauxClock still fails for just about everything except CPU Governor. I'm kinda surprised the app makes that big a difference.
[Nexus 6 Android Development] Xileforce:
Well I guess its good to know that fauxclock seems to be buggy on 5.1. Just curious, but are you in the fauxclock beta? Maybe that's why its having issues. Thanks a ton for sharing this info for others.
[Nexus 6 Android Development] aoaleman:
Hi Xileforce, how can I get Synapse to work? I get a screen with "No UCI support detected". A quick Google search says this is also dependent on the ROM. Thanks!