yashsingh1/xdaforums huggingface dataset:
[ONE Android Development] gwindlord:
Hey man,

You won't believe, but I've just built the update :) Not so many new things though - the recent Sultan's changes (including setting CONFIG_HZ to 300 commit), PCM offload is back, the commit you've mentioned above and the Chromium Snapdragon M46 most recent changes.

https://dl.dropboxusercontent.com/u/66673431/SlimSaber-bacon-5.1.1-20160526-0740.zip.md5

https://dl.dropboxusercontent.com/u/66673431/SlimSaber-bacon-5.1.1-20160526-0740.zip
[ONE Android Development] abhibnl:
Awesome! Just to make sure, does it also include his recent thermal throttling changes from today's build?

I'll flash the build asap. :cool:
[ONE Android Development] gwindlord:
Well, the names of the included commits are different, but I assure you that all the changes, appeared today in Sultanxda's repo, are there.
[ONE Android Development] abhibnl:
Sounds awesome! The internet speed here kinda sucks, so still downloading. Will update you as soon as i'm done flashing the build.

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

@gwindlord

BTW i know we discussed this earlier and you don't have much time to dedicate towards bringing up a new base, what have you made any decisions to move towards a MM based rom? I guess it'll make for a good talk while the build is still downloading on this damn slow internet.
[ONE Android Development] gwindlord:
I guess SlimYAOSP would be the choice which fits my needs best, but I did not try it yet because of some lack of space due to Chromium Snapdragon M50 sources and some lack of time too. Also the thing which confuses me, is that I've heard a lot of negative comments about MM ROMs, regarding their battery, network, cell connectivity and only few positive ones. I cannot really understand the benefits besides the questionnable multi-window mode and unstoppable code development, and I'm still not sure that the MM is now better than LP (though Google forcibly moves us there, stopping the security bulletins for LP). Remember when the LP was stable and good? When the first MM ROMs were being prepared to be baked. So maybe it's wise to wait a bit more and take more stable and trustworthy code.

Though all the points above are arguable and to tell you the truth, they all come to a single one - convince me :D I'm thinking about going there too, but for now the price (in terms of the efforts) still looks higher than the gain.

And I'm not sure this is not the off-topic here - I've got used to 4pda and they have much more strict rules about that )))
[ONE Android Development] abhibnl:
SlimYAOSP, i haven't tried but hearing great things about it. Well, the biggest complaint that i have with LP is the Mobile Radio Active bug which destroys battery. Guess what, it still is present in MM. However, Doze mode does improve the battery a bit. Honestly, i have never used Multi-Window and it seems like a feature only beneficial for tablets and phablets, not much use on bacon. The cell and radio connectivity never showed any issues to me personally on all the MM roms I've tried. But i agree on one point, that is stability of LP. Truth be told, i'm only sticking to SlimSaber LP is "custom codec support". I don't know if slim team or [MENTION=1228651]fusionjack[/MENTION] has integrated those in SlimSaber LP, but this is the sole reason i'm sticking to this rom. I have tried many MM roms based on CAF/AOSP sources(atleast they claim to be non-CM), and none of them had custom codec support. The only exception is CM based MM roms, which supports almost all formats in MX Player HW mode. (for some reasons, 10-bit HEVC files still works on SW mode). And i'm not much of a CM fan, especially the theme engine. So that is my reason to stick to this SlimSaber LP, and i'm waiting for a good Slim/AOSP/CAF rom with non-cm base, and custom codec support. Seems like i need to learn to compile roms myself. If only i had good internet connection and money to buy a high-end PC :P
[ONE Android Development] gwindlord:
AFAIK we should thank Sultanxda for custom codecs support. So his MM CAF does not even have them?.. Well, even less reasons to leave LP now :) Except the one and the big: even Google seems to be stopping its support already.

I'm not also a fan of the CM theme engine. I admit it is comfortable - you apply theme once and for all, but this prevents from making different themes for different applications. The only thing I don't like with layers is reboot to apply them.

And you don't need high-end PC actually, you can just rent a VPS/VDS ;)

What a shame that CAF kernels audio drivers do not support Poweramp Hi-Res Output, I would at least try to hear the great sound :) I don't even know if I can hear the difference.
[ONE Android Development] abhibnl:
Thank CM team for adding custom codecs, not sultan(no offense/disrespect to his great work though). Like i said, CM and all roms build from cm sources have custom codec support. It's the aosp/caf based roms that don't have it. And i don't understand where have you gotten the impression that google is stopping support for MM? But i agree the jump to N was quick. I'll search more about VPS/VDS. Well i wasn't aware about the high res audio issue. I hope sultanxda will consider adding that in future.

A report on the slimsaber LP latest build:

Do you notice any issues with wi-fi? I'm seeing performance degradation in wifi after the latest update.

Sent from OnePlus One
[ONE Android Development] gwindlord:
Talking about custom codecs support on CM and not on AOSP, do you mean MM version? Because on LP codecs seem to work on SlimSaber CAF, which is AOSP, and I believe this was Sultan's drivers work.

I've got an impression that Google stops LP support, not MM :) Also Sultan said the hi-res issue requires many changes in audio HAL and he won't do that, at least for MM, but I doubt that on LP it is different.

As for WiFi, I use it for sites mostly, but on downloading applications it seemed to be fine for me. Let me try to download something when I reach home.
[ONE Android Development] abhibnl:
Yes, on MM no aosp/caf rom can play older mkv files at all. And i personally also don't see any point to work on LP anymore. It's a good thing that google is polishing every minute detail in N. I wish they can fix MRA bug this time or i am seriously disappointed in them.

One more thing regards to your build, somehow, i can't change the max freq. I want to bring it down to 1574 Mhz but it won't change. Any idea?

Sent from OnePlus One
[ONE Android Development] gwindlord:
Well, work in LP has the only point to my mind: it works and is still better than MM in some things, and there seem not to be better things in MM - I cannot get how did it happen, but it did, and I wish someone would show me I'm wrong.

I've never suffered from MRA bug somehow and start to think that it's reason is actually hardware or operator, but it obviously can and should be fixed in code.

As for the frequency, I'm afraid it's Sultan's CM13 kernel specific :( I have the same on this kernel with upper freq all the time.
[ONE Android Development] abhibnl:
Well MRA bug happens only when Mobile Data is active. I use 100% mobile data from monday-friday, so batt life is worse. Kitkat was n still is d best release of Android for me. I have flashed private kernel v15 for now. Works wonderfully well n i can overvolt n underclock both. Will test for few days and will definitely recommend to you.

Sent from OnePlus One
[ONE Android Development] d1ke:
Good morning everyone,

I hope this post is not completely in the wrong topic ^^

I came from OnePlus One's SlimSaber ROM but use the OnePlus Two for some weeks now. Through several ROMs (OxygenOS 2.x, 3.x; Purity, etc.) I'm quiet disappointed with the cameras and like to know if you guys can tell me which camera app is used for the SlimSaber ROM and if their is an install for that?

Thanks in advice.
[ONE Android Development] abhibnl:
Well a camera app simply won't make any difference. We have a custom camera HAL developed by the great [MENTION=4800121]Sultanxda[/MENTION] which is something that will only work on OnePlus One.

Sent from OnePlus One
[ONE Android Development] gwindlord:
But that takes much Sultan's work out. Though if it is better, then to stay only by loyalty sounds a bit stupid :D

Also funny conclusion: if every next release has some minor issues which the previous ones didn't, and I include just Sultan's changes (try not to take any kernel changes, because I obviously understand less in kernel than Sultan does), this may mean that either Sultan's changes become LP-intolerant, or they become not so good as they were before...
[ONE Android Development] cossali98:
I have just installed the rom and everything run smooth but I really like to know how change the buttons' function, tnx
[ONE Android Development] gwindlord:
It would be nice to know, which ROM you're talking about :)
[ONE Android Development] gwindlord:
Please find one more build. Numerous commits from Sultan to kernel and device tree, some fixes in Snap, recent changes for Chromium Snapdragon M46 and 5.1.1 implementation for Google's June Security Bulletin (it was not so easy to include it this time). Also I've replaced CAF audio with CM's one, which allows to use Hi-Res 24-bit output in Poweramp. Full changelog is inside the ROM.

https://dl.dropboxusercontent.com/u/66673431/SlimSaber-bacon-5.1.1-20160610-2236.zip.md5

https://dl.dropboxusercontent.com/u/66673431/SlimSaber-bacon-5.1.1-20160610-2236.zip
[ONE Android Development] abhibnl:
Thanks for the new build. [emoji4]

However, a small query, can i flash the private kernel r16? I have had some good results with r15. So are there any significant changes to the kernel that would imply that i should stay with stock one?

Sent from OnePlus One
[ONE Android Development] gwindlord:
Well, to my mind you should just be careful and make backup before flashing private kernel - or be ready to reflash the ROM if anything goes wrong. There are a few questionable commits regarding scheduler and security fixes, but I doubt they will influence much. I suppose there is should not be anything forbidding third-party kernels usage at all.
[ONE Android Development] abhibnl:
Thanks! Will flash the boot.img from the rom zip if anything goes wrong. Just wanted to check with you first. One doubt that i have is in-regards to the audio changes. Since private kernel incorporate all kernel changes, could it influence anything in regards to your audio changes and this move to CM audio implementation? Or is it something that is totally independent from the kernel?

Sent from OnePlus One
[ONE Android Development] gwindlord:
At least I've not found anything related to kernel in the audio HAL. For me it was like - I've replaced the repository and it just works as usual and also with Hi-Res.
[ONE Android Development] abhibnl:
Gotcha! Since i don't have any high res audio file or poweramp paid version, i can't test it. Great work on the rom side as usual!

Sent from OnePlus One
[ONE Android Development] gwindlord:
Just a note: Hi-Res output is in Poweramp alpha 703 version, not stable one, and this alpha will work for some days for free. I use it on my daily basis and it works just fine for me.
[ONE Android Development] gaspolo:
so il better fro battery cm13 sultan or this? any idea? every time i change cm12 sultan and after a week cam back su lp caf
[ONE Android Development] sagarshah1729:
@ kantjer

I tried building SlimSaber for my device but I was not able to as my device is CAF..

Can you please guide me to make SlimSaber Compatible with my Device??

Please Reply..
[ONE Android Development] dharmabm:
Devices aren't CAF, that's only a ROM base. Might help if you mention what device you have ;)
[ONE Android Development] sagarshah1729:
I have Yu Yuphoria aka Lettuce..

Here is the device tree..

www.github.com/cyanogenmod/android_device_yu_lettuce
[ONE Android Development] spacerule:
Hi Guys,

Does anyone still keep this build? please help to upload it?

Hi [MENTION=4921047]gwindlord[/MENTION],

Planning to update the build?
[ONE Android Development] gwindlord:
Will try, but cannot promise :) In the meantime you can use this one:

MD5:

https://dl.dropboxusercontent.com/u/66673431/SlimSaber-bacon-5.1.1-20160709-0901.zip.md5

Archive:

https://dl.dropboxusercontent.com/u/66673431/SlimSaber-bacon-5.1.1-20160709-0901.zip

Stable, integrated Google Security bulletins for June and July, updates for Chromium CAF M46 and some other small changes.
[ONE Android Development] spacerule:
Thank you Sir..really appreciated..
[ONE Android Development] :
Anyone here find any good MM alternatives to Kantjer's ROM? I tried the new Slim6 but it feels so slow and clunky compared to this. That, and I couldn't get the new CM13 music player to even work, and had trouble with viper4android. It's really annoying that I still can't find a good rom for MM. And most roms on here use CM theme engine which I personally can't stand, and prefer to use Layers.
[ONE Android Development] mrmcshagbag:
Fusionjacks omni slimsaber rom is recommended. It is the smoothest mm rom I have used. I have multirom and have tried most of them and slimsaber is the only rom that lasts on my phone for more than a day. I even have viper4android working on saber in enforcing if you need help with that. Oh and it comes with layers.
[ONE Android Development] :
Not asking for eta, but just curious if you're still working on your slimsaber rom for the August security update?

Edit;

Seems like these links are down now too :(
[ONE Android Development] gwindlord:
Well, I was, but it is on hold for now. The latest build I use myself is

https://dl.dropboxusercontent.com/u/66673431/SlimSaber-bacon-5.1.1-20160709-0901.zip.md5

https://dl.dropboxusercontent.com/u/66673431/SlimSaber-bacon-5.1.1-20160709-0901.zip

Being honest is it becoming hard to implement 6.0.1 fixes into 5.1.1 - the code is going to be really different and I'm not a programmer at all...
[ONE Android Development] :
How exactly do you go about patching the ROM with a security patch? Could you point me in any specific direction?
[ONE Android Development] gwindlord:
Sure, it's not a big deal. I go to Google's bulletins page and wait until there appear links to recent fixes, then try to merge them into the code manually. If it becomes too hard to do that, I wait until CM does that :p

By the way just installed the one with the latest September patch and all before that, and also recent kernel changes from Sultan:

https://dl.dropboxusercontent.com/u/66673431/SlimSaber-bacon-5.1.1-20160913-1716.zip.md5

https://dl.dropboxusercontent.com/u/66673431/SlimSaber-bacon-5.1.1-20160913-1716.zip
[ONE Android Development] :
Thank you!! Its like Christmas all over again. I'm planning on starting a custom slim6 ROM myself with sultan kernel and camera hal
[ONE Android Development] GirishSharma:
What is July 17, 1971 in many system apps which comes in Auto Start head in Aps ops option?
[ONE Android Development] :
Any news on a possible update with October security patch?
[ONE Android Development] gwindlord:
I think it is more practical to go from backwards this time and wait for CM to merge everything they can/will, and after that merge rest of Google code myself. So you're not waiting for me, we're actually both waiting for CM :)
[ONE Android Development] spacerule:
Hi Sir, Is the ROM ready... :D:D
[ONE Android Development] gwindlord:
CM is doing all the stuff quite long this time, not sure why... I would not like the thought they abandon 5.1 support, but this thought returns to me over and over again. Though I did not see any official confirmations of this.
[ONE Android Development] spacerule:
Noted Sir...
[ONE Android Development] :
You would think security updates should be quite important to the devs, more than new content.. :(
[ONE Android Development] gwindlord:
Just found out that those CM guys actually merged all necessary commits, but did not track them via Gerrit >_< So finally, at almost November, here is the build with the October security patch, recent Sultan's commits and few other kernel ones from CM - I hope it's better late than never.

https://dl.dropboxusercontent.com/u/66673431/SlimSaber-bacon-5.1.1-20161028-1831.zip.md5

https://dl.dropboxusercontent.com/u/66673431/SlimSaber-bacon-5.1.1-20161028-1831.zip

The most significant change is that Sultanxda removed deadline I/O scheduler, so system now defaults to CFQ one. Not sure why did he do that, but decided not to change it, at least for now. Full changelog is available in Settings as usual.

Also I hope Dropbox will not ban the shared file anymore, like it happened once with the previous build :D
[ONE Android Development] :
Yes!! Thank you. Still searching for a feasable 6.0.1 caf aosp ROM with sultans camera hal and the ones that are perfect candidates, like candysix, haven't been updated for over 3 months. Its still running the August security patch and that is a huge security risk for my data. Here you are releasing a ROM with October security patch. One of the few on XDA :) still the best ROM IMO. Updating immediately.

Edit: I wonder if there's a way to merge the latest xposed version with the older xposedbridge.jar that's compatible with this ROM like [MENTION=5890272]patrickph[/MENTION] did a while back. I can't run the latest rootcloak module because it needs > v74 xposed.
[ONE Android Development] gwindlord:
Thank you for your kind words :) To my mind Slim6 would be the best candidate, as the original SlimSaber is Omni-based and it is too hard to merge Sultan's and Omin sources - too different device trees. Though even with Slim6 it is a huge job, and for now I have enough time just to include security patches. Though I'm still thinking about it :)

Not sure about xposed, as I'm not using it, could you please give more details about this jar, where it should be merged and what's not working with this ROM?..
[ONE Android Development] :
Specifically the newest version of RootCloak and any xposed modules that use the newer api > v74. They just become grayed out and say "requires newer version of xposed". Found this release of xposed in the OP: http://xdaforums.com/showpost.php?p=63611653&postcount=14819

He merged the older xposedbridge jar with the newer release of xposed because for some reason the older xposedbridge jar is the last version compatible with this rom.

Edit: Yes! I'm sure if you started up your own Slim6 rom it would be greatly appreciated. I personally don't like the Slim6 available right now because it's using the CM camera HALs, which produce awful pictures compared to Sultan's and Color OS. That and Substratum support is what would make a perfect Slim6 rom :good:
[ONE Android Development] gwindlord:
New build at last. This one has some noticeable changes, so I just have to note them here

November Google Security patch;

Orion ringtone added back;

Qualcomm Chromium updated to M54 as the stable branch, so all opened tabs will be lost and it will be necessary to re-enter and re-sync the data (also that's why the archive became 33 Mb bigger); please be aware that the saved password may disappear - known Qualcomm Chromium bug;

Framework Layers themes other than TimberWolf may not work (you will find this out in case of bootloop after theme apply) because of recent security change (see my comments there). I've added TimberWolf there because it is my favorite theme, I can't stand the white UI and I hope this security hole is not so big. But anyway, be aware that /system/vendor/overlay/TimberWolf_Framework.apk has the permission to boot with the framework and I'm defining this explicitly for all of you to know that.

https://dl.dropboxusercontent.com/u/66673431/SlimSaber-bacon-5.1.1-20161122-1901.zip.md5

https://dl.dropboxusercontent.com/u/66673431/SlimSaber-bacon-5.1.1-20161122-1901.zip

Also I'm not sure about Slim6 anymore... I've checked and did not find there calls black list, which I do use sometimes, or non-intrusive calls and stuff like that. Please correct me if I'm wrong here.
[ONE Android Development] spacerule:
Xposed module v74 no longer works. Maybe this could be the same issue due to November Security Patch.
[ONE Android Development] Dhairya:
aha so with new security patch we have to be with one built in layers theme other will give bootloop :(
[ONE Android Development] gwindlord:
Yes and yes, our ancient theming and booting modules are now considered as vulnerable. This guy tried to include xposed, I can do the same, but - there's always "but" - I do not use it and hence cannot test it, so the bridge path may be different for us.

The sweetest thing is that the whitelist is hardcoded in the sources, and externalizing it into some file will just make this fix useless... choosing security instead of freedom (friendly interface) makes Android users undeserving both of them? :)
[ONE Android Development] :
I saw in your update post that you were able to get your layers theme to work by whitelisting the individual layers modules?

If so, do you think it would be possible to whitelist the layers modules in my version of commute UI? I have the oandbackup files in a zip here: https://mega.nz/#!Ht4mgIKa!VciQ-unVh9nBKSRBPJtCPYyVhhiUVODJzTKiye8OCeI

Oandbackup is just like titaniumbackup but open source and from the fdroid app store.

Its totally cool if you don't have the time I understand, but thought I might give it a shot, then I can focus on updating our xposed module to the soon-to-come-out v87 which fixes the issue with November security patch :)
[ONE Android Development] gwindlord:
Well... if you take a look here, you can see that there is a separate whitelist PATH_WHITELIST_EXTRA_H for applications like layers and so on. I believe it is technically possible to add the layer app there, it is just the precedent which is bothering me. One more app, then one more and more and then the whitelist has as many layers as the holes are in this fix.

Though I may already have made this precedent adding TimberWolf to whitelist, so it is probably not a big deal anymore. But I will need time and the layer apk name. Also I cannot open your file - Mega says there is a decryption key necessary.
[ONE Android Development] gwindlord:
The new release is here.

Okay, double post... It seems that CM dropped LP finally (never heard any official, but the repos are still not updated), so had to merge in fixes myself (luckily it was not too hard this time).

Brief changelog:

December security patch (with one Qualcomm fix from version 3.10, but without fix for CVE-2016-6769 unfortunately - cannot find any fix on it, having impression this one is somewhere in blobs);

Recent Sultanxda kernel commits and Snap cam fixes;

Chromium Snapdragon upgraded to 55;

Nova Launcher upgraded to 5.0.1;

SQLite upgraded to 3.15.2;

More music formats for alarm sound allowed;

Enable support for groups in External contacts accounts;

Hide Keypad for pattern lock.

Merry Christmas :o

https://dl.dropboxusercontent.com/u/66673431/SlimSaber-bacon-5.1.1-20161225-1300.zip

https://dl.dropboxusercontent.com/u/66673431/SlimSaber-bacon-5.1.1-20161225-1300.zip.md5
[ONE Android Development] abdullah.ibn.umar:
Color Os blobs ?
[ONE Android Development] gwindlord:
No, ColorOS blobs are hardly compatible with AOSP I believe. Why?
[ONE Android Development] abdullah.ibn.umar:
Because i love color os blobs. LoL
[ONE Android Development] gwindlord:
Last time I've kind of screwed up - forgot to include the fix for Camera sound turn off, so here is the one including it, and also 16-bit PCM offload disable and one more Sultanxda Snap cam fix:

https://dl.dropboxusercontent.com/u/66673431/SlimSaber-bacon-5.1.1-20161228-0807.zip

https://dl.dropboxusercontent.com/u/66673431/SlimSaber-bacon-5.1.1-20161228-0807.zip.md5
[ONE Android Development] gwindlord:
The new build. Not so many new things, just WebRefiner 2.6.6 on Chromium Snapdragon and Google January 2017 security fix.

https://dl.dropboxusercontent.com/u/66673431/SlimSaber-bacon-5.1.1-20170112-1520.zip.md5

https://dl.dropboxusercontent.com/u/66673431/SlimSaber-bacon-5.1.1-20170112-1520.zip
[ONE Android Development] lokesh.3440:
F2FS is still supported right buddy ??
[ONE Android Development] gwindlord:
Yeah, sure. At least I remember it worked fine and I didn't change anything related for quite a long time.