yashsingh1/xdaforums huggingface dataset:
[Nexus 6 Android Development] papanut:
Well, I for one have not had any issues. Basic settings, Interactivex, noop, 512 read ahead. Going on 24 hours on a charge, fairly light use but still 68 % battery left damn good!
[Nexus 6 Android Development] :
512 honestly isn't optimal for this device... 1536 is.

I won't promise a groundbreaking change, but there's really no reason to go with a different value.
[Nexus 6 Android Development] akaHardison:
Revert the kernel back to v3.2 then my phone works very good.Don't know what changes in v3.6 cause my phone screen split again.:)Hoping you can fix it in next version.:good:
[Nexus 6 Android Development] ohad129:
Smartmax-eps removed any segestions for other with good bat life

---------- Post added at 08:50 AM ---------- Previous post was at 08:49 AM ----------

Going to revert to 3.5
[Nexus 6 Android Development] :
lol man. That's not a great suggestion... There's a lot of commits between the two.

We'll be taking a look at *all* the commits between the two. Likely spending hours on hours between us reverting/compiling/testing to figure out what went wrong...

But, a full revert? Really unnecessary.
[Nexus 6 Android Development] akaHardison:
No ,I mean I flash back to 3.2,not the kernel commitment.Sorry for the mistake.
[Nexus 6 Android Development] :
Anyone out there have any ideas?

I'm trying to toggle all the hotplugs to off except the one being currently being toggled. Currently this causes a device lockup. I guess this isn't a great solution, since a user *could* be toggling one off, after toggling one on. But I think this would also cover that. One is implemented correctly anyway.

https://github.com/Team-Singularity/KernelAdiutor/commit/85945859eb9bbef65d118ebbf76a5c26f76a4230

https://github.com/Team-Singularity/KernelAdiutor/commit/f75a2d8a57b463fb3fd5bdc814be1646f7ba20a0

The first commit caused a recursive endless loop because of the way I was calling the activate functions. I thought that the second commit would fix it, turns out that it didn't.
[Nexus 6 Android Development] ohad129:
Where i can find 3.5 +bcl please
[Nexus 6 Android Development] Mr_S:
Awesome job on latest build..always had RR pretty much straight away on your mm builds(not lp tho') but flagged newest version and used [MENTION=4231562]Yoinx[/MENTION] k.a.

Runng like a champ at max and min oc/uc.

Will be staying with this kernel atm.

Kudos
[Nexus 6 Android Development] fedef12evo:
using your kernel adiutor and last build, all good except for input boost settings, if i change them and reboot settings dont stick, only setting for first core stick, other 3 dont
[Nexus 6 Android Development] DreamFX:
I wouldn't spend hours for one user having instability. I have been blasting every governor the last two days with no stability issues. I would say it's stable.
[Nexus 6 Android Development] Mr_S:
Had a s.o.d browsing on chrome....

Had to hard reboot...

https://www.dropbox.com/sh/m4c3wd33778cmdh/AAB8iUX1fCeadXx8SdrVc8z9a?dl=0

Pure nexus
[Nexus 6 Android Development] :
No, I've noticed the same thing. But don't really use that setting so didn't pay much attention. A bug is still a bug.

---------- Post added at 08:08 AM ---------- Previous post was at 08:07 AM ----------

I'm willing to bet it's a no... But did three others stick with the KA from the playstore?
[Nexus 6 Android Development] fedef12evo:
no,using playstore one same issue
[Nexus 6 Android Development] :
Thought so, thanks.
[Nexus 6 Android Development] apophis9283:
Theres is nothing to cause any of these issues. Theres only a hand full of commits. Mainly re doing f2fs which im told now works and I re did fastcharge which works perfectly. I removed smartmax_eps. I explained in the post why I did it. I removed smartmax_eps because there was no need for it after I added PMC. Now PMC is basically smartmax with heavy battery settings which is why its called performance may cry. I have had 0 reboots, no lag, not even an ounce of issues.
[Nexus 6 Android Development] ohad129:
Ill try it
[Nexus 6 Android Development] apophis9283:
Just for you, smartmax_eps will be back next build
[Nexus 6 Android Development] apophis9283:
Kernel Version 3.7 is in the OP and should be downloadable from the app
[Nexus 6 Android Development] jcrompton:
Thank you guys for the hard work that we get to enjoy!
[Nexus 6 Android Development] ohad129:
Thx for smartmax eps
[Nexus 6 Android Development] apophis9283:
Not a problem
[Nexus 6 Android Development] :
If recommend reflashing your roms boot image when flashing this, as we stopped overwriting the sepolicy. Old back that prevented people from having to use chainfire's boot images. It's long since become obsolete.
[Nexus 6 Android Development] apophis9283:
It took me a second to get it all, it was the fist time i had updated the kernel through the app. Link is right. MD5 is right and now it says 3.7
[Nexus 6 Android Development] apophis9283:
I know I just released 3.7, but later tonight or by evening tomorrow I will have a new build. Some good stuff. I reverted powersuspend back to 1.5. All this should smooth out some things.
[Nexus 6 Android Development] :
I'm not seeing much in the last_kmsg. Likely related to the update power suspend drivers. I'd be interested to know if you still get a S.o.D after 3.8 is released (rolls back to Power Supsend 1.5)
[Nexus 6 Android Development] apophis9283:
Kernel Version 3.8 is live in the OP and in the Kernel Auditor app. Hopefully this is a bit more stable, less freezes. Enjoy
[Nexus 6 Android Development] :
Sorry for the noob question...been flashing ROMs for years and just now getting more into kernels tuning them etc... This kernel is smooth and has lots of settings I'm learning about.. My question is, do I have to dirty flash my ROM to update the kernel when a new version is released? Once again sorry for the noob question.
[Nexus 6 Android Development] apophis9283:
No. you can flash kernel over kernel. No need to flash your rom every time you update the kernel
[Nexus 6 Android Development] str8str:
3.8 is the best since 2.6 IMO. Very smooth fast. Good work

Straight Shooter
[Nexus 6 Android Development] apophis9283:
Good to hear
[Nexus 6 Android Development] :
So, I know it's late... Yes, I was wearing my Mad Scientist robe pretty late tonight...

I lost a few hours trying to make per-core-governors work.. apparently that's an MSM_Limiter thing though. (that's in the works soon).

If you're wondering why i keep changing sections... its to rebuild the view. Basically, to re-read the values.

https://www.youtube.com/watch?v=-Y7FUq_8RGE&feature=youtu.be

* edit *

LIMITER values are on their way
[Nexus 6 Android Development] :
So after playing with this for a bit.... I'm not completely sure that I like doing the min/max directly in the cpufreq sysfs. In synapse we forced it through limiter, which made it easier to read/write and let the driver carry it over to cpufreq.

The problem now is that everything modifies those sysfs entries for their settings... Governors, boosts, screen off values, etc. So while setting them does work reading them always gives different values (no way to overcome the drivers doing that) which seems incredibly buggy to me.

Setting the values through the single sysfs for all cores works because the other drivers have no reason to modify that entry, the only modify the entries for each core.

So thoughts? I'm looking for some input...

Do people who like per core control also use limiter? Ie: would people have an issue setting the values for each core's values through limiter?

*edit*

Alright. Looks like it has to be done like that. Recoded it and now I'm much happier with the layout/function. I'll be working on governors here shortly.
[Nexus 6 Android Development] jcrompton:
Had some data issues (not kernel related) .... gotta wipe and reflash. Are you guys still using AICP or any other suggestions for latest work?
[Nexus 6 Android Development] :
Do you remember what you were doing when it happened?

I had my data corrupt a few times while doing my changes to Kernel Adiutor. (Not from the app, found a bug in the kernel that was causing a hard lockup from something that I was doing). Sometimes when the phone locks up from stuff like that, it corrupts some of the rom's data. Which is why I was curious what you were doing when the data got messed up.

Also, yes. We're both running AICP right now. I've been enjoying it so far, but I'm on the build from the 21st still. Haven't gotten around to flashing a new version.
[Nexus 6 Android Development] jcrompton:
No not exactly -- as far as remembering -- unfortunately I've been fairly busy with work so I haven't been able to do much except check in occasionally. But I was doing some things with KA.

I'll try the AICP rom again --- I think the Root Explorer developer updated the app so it would work with TinyBox also

We really appreciate all you guys work!!
[Nexus 6 Android Development] wase4711:
any idea where that setting is'?

I went through all the menus but cant find it

thanks
[Nexus 6 Android Development] apophis9283:
settings>display and lights below ambient display, double tap to wake
[Nexus 6 Android Development] apophis9283:
I think you all will like dynamic interactive
[Nexus 6 Android Development] apophis9283:
Vortex 1.4.2 is up for download.
[Nexus 6 Android Development] DreamFX:
Will try it out. Thank you.
[Nexus 6 Android Development] apophis9283:
I left in a commit i meant to revert and reverted a wrong commit. Nothing to worry about. everything will be fine, itll be corrected in my next release
[Nexus 6 Android Development] apophis9283:
I made a change, msm limiter normally starts at 35MHz min, to be inline with stock its now 300MHz. You can still change it as low as 35 but like i said to keep it closer to stock ive changed it
[Nexus 6 Android Development] adio201:
Don't see dynamic interactive
[Nexus 6 Android Development] apophis9283:
Its like dyninteractive. I just edited it and chose for it to be more battery saving than performance
[Nexus 6 Android Development] adio201:
But I can't find it on the settings for kernel
[Nexus 6 Android Development] apophis9283:
try wiping and reflashing.
[Nexus 6 Android Development] konradit:
Hi, what are the best settings for best battery life/performance on this kernel? So many settings!
[Nexus 6 Android Development] apophis9283:
Just uploaded 1.4.3 The purpose (other than a few changes) was to bring in "stock"frequencies to MSM_LIMITER. You can still go to 35MHz. But for stock its 300MHz now
[Nexus 6 Android Development] apophis9283:
Just play with it. If you need to know more about governors refer here

http://androidmodguide.blogspot.com/p/blog-page.html
[Nexus 6 Android Development] inzaghi75:
Just flashed 1.4.2 kernel and the bootanimation in AICP is too slow.

Gesendet von meinem Nexus 6 mit Tapatalk
[Nexus 6 Android Development] apophis9283:
try 1.4.3. I make min frequency 300 instead of 35. You can still go down. I havent had any issues wiith slow boot animations.
[Nexus 6 Android Development] droidkevlar:
Thanks for another update. I see people say using your settings...but couldn't find where you posted...could some one point me to that post plz...thanks
[Nexus 6 Android Development] apophis9283:
I will make a settings post in post 2 below the op give me a bit
[Nexus 6 Android Development] jcrompton:
That's awesome. You've been so gracious in the past with that......... But I know things change as we continue to experiment
[Nexus 6 Android Development] apophis9283:
Post #2 below the OP are the settings I use. Please (as i said in post 2) If you use your phone differently these settings may not work for you. In said case change things until they meet your needs. I even said in post 2 if you have some circumstances then try (this) Hope this helps

FYI Dynamic interactive is also a good governor.
[Nexus 6 Android Development] :
Yeah, the developer did update it to work with TinyBox now.

Hopefully that was just a coincidence then with your data being corrupted. (this is why backups are always important)
[Nexus 6 Android Development] jcrompton:
For sure
[Nexus 6 Android Development] apophis9283:
Kernel version 3.9 is up. Added some things kernel side. Also there are some commits in this kernel build that you will need for the next release of Singularity Kernel Auditor. I changed TC's to UBERTC-6.0. Its live in the OP and the app. Enjoy and wait in anticipation for the next Syngularity KA build.
[Nexus 6 Android Development] :
New build of Kernel Adiutor up. Link is is OP, here's another link to save you the trip ;)

So, I went a little different route from the way I had it in my video.

This build is all about changing the way that min/max/governors are selected. The way that I did the per-core control toggle and checks requires the new kernel build that Apophis9283 just posted. I'm using a sysfs path in MSM_limiter to identify that per-core controls are enabled. Without that path, it will never show the per-core stuff.

Enjoy!
[Nexus 6 Android Development] str8str:
Keep getting 404 error for both links and in op

Straight Shooter

---------- Post added at 19:59 ---------- Previous post was at 19:55 ----------

Edit op says 3.8 but downloads 3.9. But won't download in ka says no new version. Also the links for ka get 404 error page

Straight Shooter
[Nexus 6 Android Development] klabit87:
You guys are awesome!

I've had an average of 2.2% drain per hour and that's moderate use while at work.

Thanks guys. I've wanted to do my own kernel but this is exactly what I've wanted so no need.

Thanks again guys!
[Nexus 6 Android Development] :
Fixed the links for ka in post 2 and my previous post.
[Nexus 6 Android Development] apophis9283:
Really glad you are enjoying it.
[Nexus 6 Android Development] apophis9283:
Everyone!!!!!

We know kernel downloads arent working through app. Its because github is down. It wont work until its back up
[Nexus 6 Android Development] apophis9283:
Just an FYI, In-App downloads should be up and running. Github is back up
[Nexus 6 Android Development] an21281:
All the recent kernels have been running great, very happy with the switch to KA! Thanks for all the hard work put into these builds.

The only thing that hasn't been sticking for me in KA is input boost freq. After setting cores 1-4 to the same input boost freq's and rebooting, cores 1-3 go back to disabled. Only 4 stays enabled for some reason. Not sure if theres something else I need to change?
[Nexus 6 Android Development] :
No, it's likely a bug.

I was mostly focused on getting functionality back in ka that we had in synapse. Now that that is done I'm coming to start looking at bugs.

Sent from my Nexus 6

If I've helped you, don't forget to hit thanks!
[Nexus 6 Android Development] :
Ok, I've fixed that input boost bug where it's not setting itself back on boot.

I'll probably work on some other things though before I re-release anything.

Here's the fix/workaround for anyone that's interested. Took me a bit longer than it looks like it should've because I originally thought that maybe it had to do with the way that the views were being dynamically generated... so I re-wrote all of that first. :eek:

https://github.com/Team-Singularity/KernelAdiutor/commit/c685f2c35ca519920b911def84672dfe59bb06eb

Also, I'm going to apologize in advance... For the next build you're going to have to uninstall the old one and your TB backup data won't restore. I renamed the package to quit interfering with the official Kernel Adiutor. Also, my keystore got corrupt (and my backup was less existent than I thought it was)... So I had to create a new keystore.
[Nexus 6 Android Development] apophis9283:
Screenie. Havent done one in awhile
[Nexus 6 Android Development] :
What sot of tool uses twitter?

Yeah, I caught that.
[Nexus 6 Android Development] akaHardison:
Thank you guys.V3.9 runs perfectly on my buggy nexus 6.No screen spilt issue now.[emoji1]
[Nexus 6 Android Development] :
Request:

When posting requests or bugs, can you tag the first word of the post as "Request:" or "Bug:" respectively to make them easier to search for.

Also, anyone have any other bugs still?

Sent from my Nexus 6

If I've helped you, don't forget to hit thanks!
[Nexus 6 Android Development] baboomerang:
Bug: MSM Limiter

If I set maximum suspend frequency to 1190MHz or any other value, it is permanently set as maximum CPU Freq regardless if screen is off or on. Causes insane lag after waking up and sleeping the device at least twice in a row. Only way to temporary fix this is by hard-rebooting the phone. This bug made me get lost in downtown Manhattan, New York for like 7 minutes. :(

This bug has been present since like the beginning of time with HSB, I assumed it was fixed by now.

Eventhough MSM Limiter is really useful, I can't use it much for now.

Thanks for the V.3 Update of the Singularity KA app [MENTION=4231562]Yoinx[/MENTION]. :good::good::good::good::good::good:

Hope you can fix it :o :D :p :highfive:
[Nexus 6 Android Development] edjocute:
Bug: GPU Idle Freq

I have 2 phones with the latest v3.9 installed and KA seems to show the GPU idling at 100MHz. I remember that in previous versions (v2.x), KA shows the GPU idling at 27MHz instead. I've tried changing the GPU governor and turning Adeno Idler on and off but it doesn't help. Could it be just a frequency display issue?
[Nexus 6 Android Development] apophis9283:
This will be solved momentarily.

Actually mark it up as solved already
[Nexus 6 Android Development] :
Thanks for the report. We've fixed this, it should be in the next build.

We had a problem in the state notifier driver for some reason, it was never telling limiter that the screen was back on. Sorry that you got lost in New York. That place smells like urine... everywhere .:eek:
[Nexus 6 Android Development] DreamFX:
I have a problem/bug with the latest. I get too good of battery life and performance. It's much more than any other kernel. What is the deal with this phenomenon?
[Nexus 6 Android Development] apophis9283:
Kernel version 4.0 is up and live in the OP and in-app. I do believe Yoincx will be releasing a new KA version some time today
[Nexus 6 Android Development] :
Singularity - Kernel Adiutor v4

V4 is being released. Second post updated with download V4.1

Added HBM on/off intents, info in Post 2.

Consolidated the Hotplug Toggles all at the top, tunables will show up beneath them.

Removed Headphone PA gain, it doesnt actually work.

Added Wake gesture DT2W timeout,x/y feather (my modifications to the driver)

Modified the package name to stop interfering with Grarak's official Kernel Adiutor app (app is now called "Singularity Kernel Adiutor")

Fixed Input Boost Freq not being reapplied on boot

Wake - Misc fixes/changes - Removed a redundant wake option, added description to S2S, etc

Thermal was providing min/max Thermal limit values that didn't match our driver.

Pretty sure that's it for the major stuff.

I also added a card in the "About Us" section that will give your this V4 modification number. I'll try keeping that updated with any future builds so that you know whether or not you need to download the update.

*edit* V4.1 uploaded to address an issue I introduced with the thermal limits.
[Nexus 6 Android Development] apophis9283:
I just fixed the md5sum for in-app download sorry about that
[Nexus 6 Android Development] DreamFX:
404 Not Found

The page you are looking for could not be found.
[Nexus 6 Android Development] apophis9283:
Its being worked on now
[Nexus 6 Android Development] DreamFX:
I guess he said being released my bad. I jumped the gun lol.
[Nexus 6 Android Development] apophis9283:
No we released everything. Just some stuff got borked. Itll be out soon
[Nexus 6 Android Development] ztotherad:
just flashed the kernel and thus far doing amazingly. love the new ka, and loving interactive_pro governor. I've always been a fan of interactive and this governor seems to be kicking ass!
[Nexus 6 Android Development] apophis9283:
In app downloads should be working now. Sorry for the inconvenience
[Nexus 6 Android Development] apophis9283:
Thats how we roll here at Singularity Kernel :)
[Nexus 6 Android Development] :
Weird. I'll ask apophis about it.

Here's the right link.

http://singularity.swmirror.com/21a4a

I'll update the other posts soon.

Sent from my Nexus 6

If I've helped you, don't forget to hit thanks!
[Nexus 6 Android Development] laosguy:
Will this work on CM13
[Nexus 6 Android Development] :
No reason it shouldn't. We run on it roms with a cm base.

Sent from my Nexus 6

If I've helped you, don't forget to hit thanks!
[Nexus 6 Android Development] apophis9283:
I have updated the OP to reflect that it does work on AOSP and CM based ROMS
[Nexus 6 Android Development] apophis9283:
I know, I double posted. Sue me.

Link for the Singularity Kernel Auditor has been taken down while an issue is fixed. It shouldnt be long but he works at his own pace. So sit back and wait for him to tell you otherwise
[Nexus 6 Android Development] :
V4.1 uploaded, Links in Post 2 and Here updated. See the second link for a changelog of sorts.
[Nexus 6 Android Development] apophis9283:
WOOO! Everythings working right now! Hope you guys enjoy. Out for the night
[Nexus 6 Android Development] DreamFX:
I agree been testing the same governor for awhile now and it's amazing.
[Nexus 6 Android Development] apophis9283:
Glad you enjoy it. Spread the word. The more the merrier. (I secretly want to take over the N6 kernel wise)(Insert evil laugh)
[Nexus 6 Android Development] apophis9283:
Gonna be working on compiling with SaberMod TC thats speciffically for cortex-a15

We have features out the ying yang, I want it to be a bit smoother

Edit it will now be compiled with SABERMOD-6.0-CORTEX-A15 Ive already updated the OP to reflect the TC change. Just hang in there and Ill have a build ready sometime in the next day or two
[Nexus 6 Android Development] Meowdib:
Hydra kernel has CAF audio and I noticed a difference when I used it:

Any chance to get a similar thing on this kernel or does CAF break too many things?
[Nexus 6 Android Development] :
I don't think it would be impossible. However, it's probably going to be a good bit of work to get up and going. I wouldn't expect it too quick.
[Nexus 6 Android Development] apophis9283:
Ill track everything down tomorrow. Start work on it
[Nexus 6 Android Development] apophis9283:
So thats probably not happening. What I would like to do is kill fauxsound (I know headphones still work) and just have everyone use a flashable zip for an audio mod.

Like seen here

http://xdaforums.com/android/apps-games/mod-dolby-atmos-t3109446

Thats what Ive been using. On the other hand Yoinx wants to keep it. I figure leave it up to you all.
[Nexus 6 Android Development] :
Yeah. That's because unless someone enables it or tweaks the settings... It literally does nothing.

By removing it, the few people that use it won't be able to. While leaving it didn't affect the people that don't want to use it.

That app also doesn't boost headphones volume.

Sent from my Nexus 6

If I've helped you, don't forget to hit thanks!
[Nexus 6 Android Development] apophis9283:
Theres viper audio as well....

Im just gonna let Yoinx do whatever he wants to with sound.
[Nexus 6 Android Development] :
Possible Bug.... My CPU settings are not sticking after reboot, used test option in k.a. worked fine...rebooted and they did not stick.....
[Nexus 6 Android Development] :
Did you toggle the apply on boot for CPU in that section?
[Nexus 6 Android Development] :
Yes, actually did it a few times... still after a reboot I get the default interactive pro settings.. Still somewhat of a noob here, so maybe I'm not doing something right..
[Nexus 6 Android Development] :
Try changing the set on boot delay to a bit longer. There's an init script that changes the values on boot complete as well.

I use 10-20 secs, for good measure.

But you're the first person that it doesn't work for... Let me know if increasing the delay doesn't work.

Also, can you upload your /data/data/com.singularity.kerneladiutor/files/commands.json

Sent from my Nexus 6

If I've helped you, don't forget to hit thanks!
[Nexus 6 Android Development] :
Increased to 20 seconds working great now... Thanks for everything!!