yashsingh1/xdaforums huggingface dataset:
[ONE Android Development] abhibnl:
Man!! I forgot how snappy slimsaber actually was. Thanks for the amazing gift. However one request, could you please let me know how to or make a patch to limit max cpi freq to 19xxMhz? 2.3ghz is overkill for my usage pattern and kernel auditor can't edit max frequency. I would really appreciate if you can help me with it.

Sent from OnePlus One
[ONE Android Development] gwindlord:
Try this one: https://dl.dropboxusercontent.com/u/66673431/Sultan-bacon-Enable-CPU-Underclock.zip

It is reverted Sultan's patch. Could you please tell me then if it works?..
[ONE Android Development] abhibnl:
Tried the zip but the max CPU freq still scales upto 2.3 ghz. So i would presume the fix is not working.

Sent from OnePlus One
[ONE Android Development] gwindlord:
Then, if you don't mind to be kind of tester, I can offer you a bit experimental build:

https://dl.dropboxusercontent.com/u/66673431/SlimSaber-bacon-5.1.1-20160409-0934.zip.md5

https://dl.dropboxusercontent.com/u/66673431/SlimSaber-bacon-5.1.1-20160409-0934.zip

I've built it today, installed on my phone, but did not really perform any serious test yet. There are some changes, including kernel ones, enumerated in the "Settings - Advanced - Build changelog" text, including kernel underclock (I've finally decided to try it myself and check if it really gives any battery improvement).
[ONE Android Development] abhibnl:
I'll try it asap mate. Thanks! Out of curiosity, are you planning to maintain this build for a good amount of time or do you have any plans to move to MM? I personally this build way stable and snappy than MM already. And would love to follow n flash the updates.

Sent from OnePlus One
[ONE Android Development] gwindlord:
Well, I plan to maintain this build for a certain amount of time I suppose, because I build it mainly for myself, and I'm not ready yet to move on MM, configure everything from scratch, face the new bugs and kang the missing features I use every day. Also fusionjack rebased SlimSaber to Omni on MM, and I cannot include Sultan's work there - device trees are too different, and I have to look for a new code base. So one day I'll think about going to MM, but not today :) Honestly I have a thought to support it while Google supports LP because of the security patches, but not sure how long is it exactly, so cannot 100% guarantee.

Only hesitating about placing any future versions in this topic - it is not mine actually and I was not planned to do it on regular basis. I thought one more LP ROM is not really necessary and decided just to try once, but now I'm not so sure anymore. Also the main focus in this build is my needs, not anyone's else - this sound selfish in a certain degree, but in the end I do build it for myself and just share for everyone who has the same needs. And trying to make something good for everyone usually means spoiling everything.
[ONE Android Development] abhibnl:
Well i totally understand that and i would love to use your builds. I would really appreciate if u can post your future builds here or maybe pm me. Of course the build already has every feature that i use and stability is awesome. So i believe most of the updated stuff will be from sultan with his kernel and device changes. Again, you would never get any redundant feature request from my side. I'm really enjoying this build and looking forward to the future builds, whenever you feel like building one. Thanks for your work again! [emoji4]

Sent from OnePlus One
[ONE Android Development] Setting.Out:
If you do move to 6.x, AOSPB is a good choice, several Slim builders are maintaining it.. ;)
[ONE Android Development] abhibnl:
I have just finished flashing this build and i can confirm the UC is working. Thanks alot for that!

Also one change i have noticed from the changelog is with the RIL. Will test to see if there are any signal or data speed gains.
[ONE Android Development] gwindlord:
Let me use this topic again. Built the update:

https://dl.dropboxusercontent.com/u/66673431/SlimSaber-bacon-5.1.1-20160417-1256.zip.md5

https://dl.dropboxusercontent.com/u/66673431/SlimSaber-bacon-5.1.1-20160417-1256.zip

Changelog is inside (Settings - Advanced - Build changelog). The big changes - replaced SnapdragonCamera with Snap for LP, it may work even a bit better, and updated camera HAL with the Sultan's one. Also got rid of the new RIL - according to Sultan, it is not bad, just has no benefits for LP, and the diagnostic driver enabling for SnoopSnitch utility support may be worth to mention.

Note: the changelog inside shows changes since SlimSaber-bacon-5.1.1-20160405-0927 one, not the temporary SlimSaber-bacon-5.1.1-20160409-0934!
[ONE Android Development] cesarp3791:
Thank you very much! Downloading at the moment..

Could you advise which xposed version or zip to install? I would like to use the XHaloFloatingWindow module, among others :fingers-crossed:

Also, do you recommend opengapps nano or pico? SuperSU latest or older? Thanks in advance, i'm still kind of a noob and still scare to death if a get a bootloop :confused:
[ONE Android Development] gwindlord:
Not sure about the Xposed version unfortunately, I do not use it. As for opengapps and SuperSU, I use pico and 2.65. And remember: if you have nandroid backup, most of bootloops are not so scary as then seem :)
[ONE Android Development] kalapapa:
Check out this post earlier which also applies for slim saber 5.1

http://xdaforums.com/oneplus-one/development/custom-slimsaber-builds-mods-t3175742/post65046594
[ONE Android Development] cesarp3791:
Thanks to both of you! I'll backup some stuff and download the files, and tomorrow, hopefully, will be flashing and setting it up..

Will report my outcome in chance others also have this kind of situation/doubts [emoji6]
[ONE Android Development] abhibnl:
Thanks for this. Downloading as i type this :P

One question, are they any other changes than the previous test build you built for UC? I believe you did revert the RIL to LP in that test build and some kernel stuff was updated. Nevertheless, i'mm flash this one as well.

:good:
[ONE Android Development] gwindlord:
There are some changes comparing with the test build, I was just trying to say that some items in the changelog can be the same as in the test build.
[ONE Android Development] Natakranta:
I flashed it yesterday. Running smooth.

Did you notice ringer volume slider stacked on the panel and not moving? Only after changing volume in settings it works back on panel?

The Answer to The Ultimate Question of Life, the Universe, and Everything is: CLEAN FLASH.
[ONE Android Development] gwindlord:
I've just checked - my slider at volume panel can be moved with volume keys and manually and from settings. You may have Settings - Sound & notifications - Advanced options - Media control option enabled?..
[ONE Android Development] Natakranta:
No, I have that option dissed.

I rebooted and it's working back. I remember this bug a while back but I don't recall what was the problem. I'll be watching what is the trigger and let you know if I manage to find out what is causing it in my setup.

Thanks!

The Answer to The Ultimate Question of Life, the Universe, and Everything is: CLEAN FLASH.
[ONE Android Development] abhibnl:
I face the same bug(media volume bar not moving when we try to move it by sliding) atleast once a day, but a reboot takes care of that. I remember this bug from the good ol' slimsaber days :P
[ONE Android Development] deepaklunked:
Hi.. How did you manage to get Layers theme working on it.. I too installed Domination, but got so many overlay issues. Like white text on white background and so on. Please let me know how. Also, I am on the latest build by [MENTION=4921047]gwindlord[/MENTION]
[ONE Android Development] Natakranta:
Where do you see wrote on white?

I used latest Domination Donate from Play, but Domination Free is exactly the same.

Settings menu is not right, funny colour bit that's due to different way layers work in settings in LP and MM. Having to chose Dave made it MM correct of course. I have somewhere LP Domination settings layer, I'll upload when I find it.

Did you flash theme ready gapps? Get the latest version and just flash over your current setup.

The Answer to The Ultimate Question of Life, the Universe, and Everything is: CLEAN FLASH.
[ONE Android Development] deepaklunked:
I don't exactly remember where I saw white on white. And yea, I flashed the latest theme ready gapps. One more thing I found was, the layers are not applied properly at all. For example, I tried applying softbar layers alone, from play store. But even that didn't apply.. Thought something is wrong with the rom. #nooffense
[ONE Android Development] Natakranta:
Did you update Layers Manager o play? Check it's permissions.

I just accept current layers, few months deep into MM may not be entirely compatibility with LP ROM.

That doesn't bother me much because Nexus 6P is on the way [emoji12]

LP settings layer

The Answer to The Ultimate Question of Life, the Universe, and Everything is: CLEAN FLASH.
[ONE Android Development] deepaklunked:
Lucky you.. Have fun with Nexus.. I installed layers from backup, that was taken in a MM ROM. Will try again with fresh play store install. Will report back if I find anything..
[ONE Android Development] gwindlord:
Layers Manager seems to have some backup-restore issues since they moved away from Busybox, so I have to restore my backup manually for a couple of months already :)

By the way, my ringer slider is fine, but the multimedia slider is not moving during the music playing, though volume changes according to the volume keys, what a funny thing.
[ONE Android Development] trotos:
For me it was on hangouts. I removed the layer from the specific app. (But then again I am giving a go on MM. I still am not convinced)
[ONE Android Development] abhibnl:
[MENTION=4921047]gwindlord[/MENTION]

If it's not too much work, can you please try n add these 2 commits n bake an experimental kernel?
[ONE Android Development] gwindlord:
I had some time today, please check, how it goes.
[ONE Android Development] abhibnl:
Kernel flashed successfully. So far i don't feel any significant UX improvements tbh. Will test more n let you know. BTW, if you have time, could you please explain what setting HZ to 300 actually does? [emoji13] [emoji16]

Sent from OnePlus One
[ONE Android Development] gwindlord:
Good that it works, I remember once I've picked bunch of kernel commits and got battery drain without noticeable source. As for the explanation, it's easy - I have no idea :D I'm not a programmer at all and hoping for Sultan and CM guys on that.
[ONE Android Development] abhibnl:
Lol!! :silly: :silly:
[MENTION=4800121]Sultanxda[/MENTION] Could you please pitch in if you have some time about some knowledge or advantages of setting HZ to 300 in kernel? :)
[ONE Android Development] adinkwok:
That is the frequency, "rate of refreshing" if you will, of certain hardware-software and vice versa components. Increasing that increases frequency, thus leading to faster refreshes, leading to faster hardware input to software (increases speed of this process: screen touch -> what you actually see on the screen). Mathematically, performance should be increased because things run faster, but since things are faster battery may be affected. The commit messages say that through CM's testing, the increased rate does not noticeably affect battery life, which is why it was merged. Hopefully this sums all the mumbo-jumbo up.
[ONE Android Development] abhibnl:
As always, yoshi ftw!!

Sent from OnePlus One
[ONE Android Development] abhibnl:
[MENTION=4921047]gwindlord[/MENTION]

Just as a FYI, sultan's latest caf kernel has new thermal driver implemented. Just want to keep you updated regarding any worth considering features. Let me know if you would have time for the kernel only and would want me to test.

Sent from OnePlus One
[ONE Android Development] gaspolo:
Download broken -_-
[ONE Android Development] gwindlord:
Because it is outdated, please use one from this post.
[ONE Android Development] gaspolo:
xposed working > https://drive.google.com/open?id=0Bw0l2qeHF2U2WjJVUEQySVBOcmM
[ONE Android Development] abhibnl:
I have tested both kernels with and without stock HZ 300 tick clock, and honestly, i never saw a bit of a difference between both of them in terms of UX/UI improvements. However, the phone gets hot really quick with the HZ 300 version and battery is a bit bad than the normal version. So, i'm back at the stock hz version.

Sent from OnePlus One
[ONE Android Development] gwindlord:
Hi there,

As I can see, Google did not provide security updates for 5.1.1, which makes me having dark thoughts about end of support and so on. But anyway I've built an update. There are some browser small fixes, some Snap changes (e.g. manual focus added), recent media driver updates from Sultan, Nova Launcher updated to 4.3.1 and kernel security updates from CM - please see the internal changelog. Also this build includes 8 thermal zones from Sultan, but no idea, how it could be used. As for setting CONFIG_HZ to 300, I reverted it, because it seems no to have any practical sense.

EDIT:

So sorry, I've managed to include Google May security bulletin fixes into 5.1.1 (wasn't sure about that), taking commits from here, so the new version with Android Security Bulletin - May 2016 is

https://dl.dropboxusercontent.com/u/66673431/SlimSaber-bacon-5.1.1-20160509-0759.zip.md5

https://dl.dropboxusercontent.com/u/66673431/SlimSaber-bacon-5.1.1-20160509-0759.zip
[ONE Android Development] abhibnl:
Latest version flashed successfully. No bugs or anything as of now. I'm in love with the stability of this rom. However, i do experience a bit of reduction in overall UI smoothness. [MENTION=4921047]gwindlord[/MENTION] any changes in latest version that you think may affect UI fluidity? Teating the 8 zone thermal control. Will try to check the details about it today. I also saw some changes in cpu boost. Hope so that isn't the issue. Will update if there are any more findings

Sent from OnePlus One
[ONE Android Development] gwindlord:
The only thing I can assume could be some kernel changes, which I do not handle, just taking Sultan's work. Kernel commits would also explain the CPU boost difference. Or the UI changes can be something like placebo, which can change after some usage time and/or e.g. reboot - I cannot say I see any difference, but after your words I may see it even if it is not there - everyone secretly wants the UI to be as smooth, as possible, that's why I'm talking about placebo :)
[ONE Android Development] abhibnl:
Well it was definitely not placebo. E.g. the keyboard popping animations in whatsapp and some other text apps is not "smooth". Some app switching animations are also not as much smooth but again, like u said, it could be due to a fresh flashing as well. But the stability is top notch which is more important. (Y)

Sometimes i wonder where the hell is that "consistent 60 fps animations" that google promised, i believe with Jelly bean :P
[ONE Android Development] kalapapa:
Slim YAOSP marshmallow for bacon

All credits to creator [MENTION=7031867]Bongofriend[/MENTION]

https://www.androidfilehost.com/?fid=24533103863141690
[ONE Android Development] wingedpanther:
Have you tried it ??
[ONE Android Development] kalapapa:
Not yet but I'm planning to tonight

It is using stock caf kernel
[ONE Android Development] zedbg:
Installed and working great for now, many thanks [MENTION=7031867]Bongofriend[/MENTION]
[ONE Android Development] wingedpanther:
Mind share features of it ?!
[ONE Android Development] JaylanPHNX:
http://xdaforums.com/showthread.php?p=66884003

It's baconnn!
[ONE Android Development] abhibnl:
Do you have the OP for this link? Or any thread? This seems exciting.

Sent from OnePlus One
[ONE Android Development] wingedpanther:
I couldn't find anything except this http://xdaforums.com/showpost.php?p=66927019
[ONE Android Development] JaylanPHNX:
The thread I linked to above (the Slim Builders Collective) is the only official source. Yank took all the features from his YAOSP ROM (which were mostly slim features to begin with) and added them to the base Slim 6 ROM. Then others used his sources to build for various devices.

It's baconnn!
[ONE Android Development] abhibnl:
have you tried it? Mind sharing the initial impressions, any bugs, screenshots etc?

---------- Post added at 08:35 PM ---------- Previous post was at 08:33 PM ----------

I hope the OP this bacon build can open a separate thread or start posting builds here. :fingers-crossed:
[ONE Android Development] kalapapa:
Not yet because I have been having really good battery and performance with [MENTION=2040569]jgcaap[/MENTION] rom so I'm hesitant to return to slim
[ONE Android Development] bclark:
I've been running it since last night, i haven't come across any bugs to speak of and so far battery doesn't have excessive drain. I dirty flashed over Candy6 with just a /system wipe
[ONE Android Development] JaylanPHNX:
My only complaint so far (still restoring apps) is that hardware keys can't be shut down completely (you can set them to take no action, but they still light up and vibrate).

From my SlimTab Pro 8.4
[ONE Android Development] gordon.shameway:
Thanks a lot [MENTION=7031867]Bongofriend[/MENTION] ! Really appreciate it!

#whiteuimustdie
[ONE Android Development] abhibnl:
Thank you so much for this. Will try and i hope it would have the custom codec support from CM. This is d only reason i'm not able to use aosp/caf based MM roms. However, the slim/aosp LP roms have those codecs.

Sent from OnePlus One
[ONE Android Development] JaylanPHNX:
Thanks for this build. The only thing that I'd like to see added (device specific) is the ability to fully disable capacitive keys, so they don't light up or anything if you're using soft keys.

From my SlimTab Pro 8.4
[ONE Android Development] zedbg:
Does the camera on SlimYaosp work for you guys?
[ONE Android Development] menkey:
No problems here.
[ONE Android Development] praveen7682:
+1...I get camera is stopped error after taking the pics...I am going to try different camera...
[ONE Android Development] Bongofriend:
I will look into that
[ONE Android Development] JaylanPHNX:
Has anyone had any strange behaviour regarding Layers theming on SlimYAOSP? For some reason, the Framework Colors part of Spectrum won't apply. It's weird.

It's baconnn!
[ONE Android Development] bclark:
Yeah I didn't realize at first but I also have the issue even after a clean flash.

I tried with the OPPO+Camera too

No issues with Magpie
[ONE Android Development] Bongofriend:
All camera apps are affected by this bug. The next update might take a while since I have some upcoming exams.

I will update and fix the issue when I have the time.
[ONE Android Development] Bongofriend:
Fixed the issue with the camera. I will upload the next build when its finished
[ONE Android Development] zedbg:
Great job [MENTION=7031867]Bongofriend[/MENTION]
[ONE Android Development] Bongofriend:
Camera should be fixed. If you encounter any other bug feel free to leave a post.

https://www.androidfilehost.com/?fid=24533103863143057
[ONE Android Development] menkey:
Camera is working fine here. Thanks!
[ONE Android Development] praveen7682:
Flashed the build yesterday..so far working good..Camera working fine here..Still no hardware remapping..Unable to access recents..That's not a deal breaker for me at least..will test the build for sometime and leave feedback here..Thanks for bringing slim MM for our device..
[ONE Android Development] Renosh:
I tried out this build yesterday. Hardware button remapping was either in Language and Input or Accessibility in Settings. Look through the various options they are sort of hidden
[ONE Android Development] praveen7682:
Thanks...found it..[emoji106]..Generally I don't go into that option..
[ONE Android Development] abhibnl:
Could you please check if the build can play H.265 files in HW mode with MX Player and also the old H.264 mkv format?
[ONE Android Development] kalapapa:
I'm having trouble with getting ambient display working. For some reason it won't show up when I get a notification or try picking it up. I've tried the newest oxygen firmware and also the the current cm firmware. Anybody else having this issue?
[ONE Android Development] abhibnl:
[MENTION=4921047]gwindlord[/MENTION]

Hi gwin! I've noticed the following commit for bacon:

My guess is it somehow helps in the overall UI/UX fluidity. If you would get some time, could you please bake a fresh test build with this commit along with any other updations you seem worth adding?

Edit: Went through github and it seems more of an update to the Interactive governor implementation rather than any device specific enhancement. Feel free to correct me if i'm wrong.
[ONE Android Development] gwindlord:
Hi [MENTION=4296062]abhibnl[/MENTION] nice to hear back from you :)

Regarding this change - it is possible to include that change, but not via direct cherry-picking because of different 5.1-6.0 file structure, will have to do the replacement. I will definitely try this thing along with some other changes I've got (though in theory it could decrease a bit the upper frequency limitation battery saving effect).

Could you please also tell more about these governor changes?.. I've took a glance into CM repos, but didn't find anything like that.
[ONE Android Development] abhibnl:
Well i'm not an expert or even have enough knowledge about these things to discuss changes. I just tracked this commit to github

From what i could see & understand was that Steve has made some changes to Interactive governor. However, i could be wrong as well and interactive here may not directly mean interactive governor. I have made manual changes for now as per that commit and i can't notice any improvements. Maybe that's not how this is supposed to work or something. But i definitely don't see any noticeable improvements.
[ONE Android Development] gwindlord:
Neither do I, so we're all sometimes guessing more or less :) It really means the Interactive governor, I just thought that there are some changes in the governor code itself, my mistake. This is only configuration change, which is activated after the system boots. I wonder where did you do that changes, as 5.1.1 just does not have init.qcom.power.rc file. But I think I may try it anyway.
[ONE Android Development] abhibnl:
Well it may sound silly but i followed the path from github.

and

and made changes as per the commit. I have no idea how to change things in this "init.qcom.power.rc" file. So like i said, i just did changes myself and that could be the reason i'm not seeing any improvements.
[ONE Android Development] Setting.Out:
Not a big change.. Doubt you'd see much, looks like it may help battery more than performance...
[ONE Android Development] gwindlord:
You're right, shame on stupid me :o But it won't hurt I hope. Also there could be some long-term effects, so if you notice some, please give me a call. In the meantime I'll try to include it into the next build.
[ONE Android Development] abhibnl:
As of now, like i mentioned, no notieable changes. Will update if there'd be any battery improvements. My phone is already 1.5 years old so my battery would not be the best one to test :P

Sure! I'l keep you in loop.
[ONE Android Development] abhibnl:
[MENTION=4921047]gwindlord[/MENTION]

Looks like we have some updates from Sultan on kernel side as well. Also, to re-test, and only if you would have some free time, can you re-add the scheduler tick rate commit(Hz 300) and sync it with Sultan's changes? I guess i do feel that the things were bit smooth overall on that kernel, but battery definitely took minor hit. But you can build that as an experimental kernel. With the latest thermal throttling changes, i believe it can work better overall.