Recent content by cyril279

Yes. Let the errors be your guide.

^^ This. I'm not sure what device you are building for, but you will need to find the relevant repo hosting the proprietary bits, and add it (them) to your local manifest. bacon needed find7op and msm8974-common from here: https://github.com/DonkeyCoyote/proprietary_vendor_oppo -Cheers

TESTERS NEEDED (OmniROM 7.1) I've built Omni, it boots just fine, and wifi works (camera is broken right now, I want core functionality first). This build doesn't detect my sim card (cricket wireless, USA), and I want to know if other carrier sim cards are detected...

I have been using supersu 2.79 successfully on slim7, since slim6 has built-in root, I never checked the compatibility. It should work though. The kernels are not very different in between six and seven. -Cyril

end of the line for slim6, but slim7 is now considered beta [email protected]+: So the recently posted 0.8 build is considered beta. I'm torn as to whether it's worth a new thread or not, I'm not a heavy poster, there are only about three total slim users for victara, and I'm going to post the...

build 2.0 released [Final] mostly security release and under-the-hood updates for marshmallow. https://www.androidfilehost.com/?w=files&flid=74028&sort_by=date&sort_dir=DESC OMS commits were merged into the 7.1 alpha 0.8 build. happy flashing -Cyril

Thanks for pointing that out. Before that flag can be successfully set in the victara device tree, another commit needs to be applied to frameworks base (which I don't even see pending in Slim's gerrit). I'm not into getting ahead of the team, so if they apply the FB commit, then I will gladly...

Where's the 1.18 weekly? Slim took their time releasing it, and after a recent switch to fedora, my build-box is apparently ill-configured to build 6.1. I should have things figured out within the week, and slim6.1 builds will continue. For those interested, Alpha 7.1 builds can be found in...

This post is mainly to communicate the packages required to get Fedora 25 ready to build android/AOSP. I don't intend to cover the Installation of Fedora, or the actual steps to generate the build (manifests, proprietary code, etc). From a clean installation of Fedora 25: Update the...

anderson mendes ...not sure what happened there, so try this: https://www.androidfilehost.com/?fid=385035244224382203 -Cyril

Where is this in settings? It looks like the timer menu, but I can't find it to reproduce the issue. -Cyril Edit: I see, it happens in Google's clock app from the play store. I'll look into it.

Not yet

In progress: https://bugs.slimroms.org/issues/41 Regarding the responsiveness, It MAY be an issue regarding the addition of navbar double-tap. Basically, the navbar does not respond immediately upon press, because it has to wait to see whether a second tap will occur. Best case scenario...

Yes, I see now that anything that is set as long-press registers a second touch, so it doesn't launch correctly. A workaround is to have now-on-tap launched by double-tap of home, instead of long-press. I'll have to look into the IME switcher as well, thanks for reporting. -Cyril

possibly, maybe, probably... It's simply too early in slim's development cycle to know exactly how (or whether) they will address such an issue. -Cyril