D
[ROM][AOSP JDQ39E][cfX 4.8.1-toolchain][SR20] OFFICIAL codefireX Nightlies!
- Thread starter synergye
- Start date
Sorry guys, BR1 won't have configurable quick settings just yet since they still are quite buggy and BR1 should be bug free IMO.
sent from codefireX
sent from codefireX
Just wondering if Any navbar modifications are coming?
Sent from my Nexus 4 using xda premium
KidCarter93
Retired Forum Moderator
About to merge. I track 54 local branches because of all the optimizations, so merging is extra fun compared to a CM build ;P. In the mean time, could someone test the new test build in the testbuilds folder for bluetooth? If that doesn't work, then I"m just going for 4.2.1. Thank you all!
Edit: BR1 (Beta Release 1) uploaded! Please check the changelog and report any issues you may have. Per the requests of a few users, I have left the kernel as the stock mako kernel, but highly recommend faux123's kernels. Thank you!
Last edited:
Can Nexus 4 run any better than it is now?
What are main things that can be fixed/upgraded except battery life in your opinion mate? Thx for your work
What are main things that can be fixed/upgraded except battery life in your opinion mate? Thx for your work
D
Deleted member 2915683
Guest
Wow, really slick rom... Pleasantly surprised by this, really well supported, stable as far as I can tell. and some really cool tweaks/settings for me to play with.
Thanks!
Thanks!
By any chance does the rom have settings for the nav bar? In terms of changing the color and size?
Sent from my Nexus 4 using xda premium
I'm very glad you all are enjoying this project. As a quick update as to what I'm working on: I just added longpress back to kill (with configurable long press timeout) and am now working on forward porting navbar customizations and configurable navbar/status bar transparency. I also apologize that the adb icon toggle isn't working in BR1; it's already fixed in source.
sent from codefireX
sent from codefireX
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
149You will not be able to find a faster source built rom. Built with a custom gcc 4.8.1 toolchain, strict aliasing, isoc++11 mode, O3 completely, and well as other optimizations. Click HERE for a better thread, discussion, download, and more info.
CLICK HERE FOR INTERACTIVE CHANGELOG
48fixed the security settings fc for good now. That upload was actually also accidental, lol. Ran the wrong script when I went to do a personal build (cron jobs and scripts are how the nightlies usually get done). Sorry about that guys...but at least you know that progress is being made. SELInux was being such a ***** that we went back to partial release repos with a lot of master parts with progress we made while working off master. Actually just did a build with the best performance we've had in a build yet.
A release will come soon, just need to make sure that it will give the SR prefix it's true meaning back - Everything's even going through review now. Also holding off on nightlies (and accidental script execution) until the stable release. We also have a few new guys contributing to cfx who are doing killer jobs and working their asses off as well30SR16 updated. This is a giant update and the first of it's kind (again) for a custom jb rom AFAICT. Think of arch linux or another rolling distribution but for android. This has many benefits such as staying more bleeding edge, but also means that we will no longer need to start over on the next major android release. This happens with all current custom android distributions, and is a real shame. Basically this means we're further ahead of the other roms even more so, and will be when the next major android release is merged in as well
Big thanks to this awesome team, all contributors, and all translators.
Now yes we're working on fixing the navbar size issue as well as the others. This rebase was just something I had on mind for awhile now.30Re: [ROM][AOSP OpenMaster][cfX 4.7.3-toolchain][SR16] OFFICIAL codefireX Nightlies!
A quick update: the nightlies aren't going right now because they would have the same selinux issue with root and sometimes not boot. I'm working on fixing it as well as Wi-Fi, and am hoping to have it fixed today.
