SlimKat 4.4.2 build.2.5.RC1

Hey guys,

We have finally removed the beta tag and Jenkins is in the process of building the new weekly builds. We are not far away from first stable release so this weekly will be tagged as RC1. Thanks to all of the users and testers that made this possible!!!!!!

This week we had 2 main aims. Firstly to iron out all of the small bugs which were present in preparation to go soon stable. Secondly to add back one of the important missing features that a lot of users have been requesting and asking why we hadn't merged yet when other ROMs had and that is Hardware key rebinding. The reason was very simple. The code and feature which we and all other ROMs have been using for about 2 years was nice but not that what we wanted to have with 4.4.2. So we decided to recode it completely in a more flexible, more centralized, less resource heavy way without affecting all of the non hardware key devices and with some nice enhancements of course.
DashClock also got some major updates mainly to tweak the UI even more.

ATTENTION: You need to update your gapps for this build!!!!!!

Note: If you have no backup accounts visible in  "Settings -> Backup and Security" after a fresh install just reboot and it will show up. It is due to a problem with googles native GoogleBackupTransport.apk control.

Changelog:

  • Frameworks base: Return: Custom Carrier Label
  • Frameworks base: Return: UMS support
  • Frameworks base: Handle backup transport registration dynamically
  • Frameworks base: Harden against transiently unavailable backup transports
  • Frameworks base: Slims Hardware Key Rebinding
  • Frameworks base: Speed up the navbar
  • Frameworks base: Make menu unlock configurable
  • Frameworks base: SystemUI: Pimp-up Media Tile (double tap during play)
  • Frameworks base: finally fix carrier lable shows on first boot sometimes
  • Frameworks base: use on virtual POWER_KEY own global menu handling
  • Frameworks base: TRDS change auto detect light conditions method
  • Frameworks base: Add support for ADB over network
  • Frameworks base: Notification : Fix app info long-press
  • Frameworks base: core: Added national roaming info for Jazztel Movil in Spain
  • Frameworks base: core: added national roaming info for Spring Mobil in Sweden...
  • Frameworks base: Initialize pointer members to NULL to avoid illegal reference
  • Frameworks base: MediaFocusControl: Deny audio focus if notification stream is 0
  • Frameworks base: Set Settings.Global.WIFI_SCAN_ALWAYS_AVAILABLE default value
  • Frameworks base: Fix error checking in MemoryFile.
  • Frameworks base: Fixed stylus eraser being rejected by palm rejection
  • Frameworks base: Fixed incorrect calculation of dirty invalidation area
  • Frameworks base: FLAG_PRIVILEGED disappears if privileged app is updated and rebooted
  • Frameworks base: Only send storage intents after boot complete
  • Frameworks base: Remove unused field from AssetManager.
  • Frameworks base: Telephony: Modify code to check that PUK code length is always 8.
  • Settings: fix Display settings FC on manta or devices without crt mode effect
  • Settings: Remove notification pulse and light for devices without LED
  • Settings: Add CPU & RAM info.
  • Bionic: Moar optimizations
  • dalvik/vm: Dalvik startup with a low memory footprint
  • Mms: reload default drawable if it changed during the instance
  • DashClock: Added condensed font option
  • DashClock: Added separator between extensions
  • DashClock: Added text density option
  • DashClock: Fixed touch feedback, broken in an earlier commit Fixed clock metrics for ...
  • DashClock: some TRDS adjustments
  • DashClock: add background color choice + add more colors for text then just ...
  • DashClock: add preference theme to NextAlarmSettingsActivity
  • DashClock: add src api paths back
  • DashClock: make actionbar consisten with KitKat theme and fix
  • DashClock: disable backgroundcolor preference if opacity = 0
  • DashClock: Fix menu overflow button on dslv
  • Updates on display-caf, audio-caf and media-caf
  • Updates on frameworks native
  • Tons of device upstream and device specific fixes (see device changelog in download area for details)
  • Translation updates

SlimKat beta 2.2 weekly

new weekly release is coming.....head to the changelog to see what changed

your SlimRoms Team

SlimKat beta 2.1 weekly

and here we go....first build 2014........read the changelog and have fun :)

SlimGerrit v2.0

Hi Slimmers!

A few weeks ago we finally published our Gerrit CodeReview server to the public.

The reason why we didn't do it sooner was that the old server was virtualized and shared resources with 10 other servers, therefore it was sufficient enough for the SlimTeam, but not capable enough to handle a large community like Slim.

As already mentioned we use Gerrit (created by AOSP for AOSP, and state-of-the-art for Gerrit).

The setup

The hardware is a 32G RAM server, with a quad-core processor. We run it with NGinx, and PostGreSql on Debian Wheezy. The performance we see at the moment is really astounding, with this pure-open-source setup.

Progress

Even if we had not announced our new Gerrit, we already have many code contributions from the community, which is one of the most important things for an Open-Source project as we are. Thanks to all!

Accumulative voting and submit

Gerrit bascically works in the way that you

  • "push" a change to the Server
  • one (or more) say it works" by giving a "+1"
  • and some kind of SuperUser pushs the "Submit" button

The last step publishes the change (more can be read here).

A lot of people that are familiar with Gerrit will know that sometimes it can take forever for the SuperUser to submit the patch, because these people are the bottleneck in this process.

Our solution

But... Gerrit is capable of customizing the whole submit process, so we set it up for an "accumulative voting and submit", which means many more people have the right for some granted repos to submit the changes as soon as the submit score reaches 3. That seems to speed up the whole process and our first impression is that it works pretty well, and gives us a faster submit process,  allowing us to concentrate more on developing Slim rather than maintaining sourcecode.

Contribution

So, please all developers out there feel encouraged to contribute sourcecode to Slim. With a strong and contributing community the Slim experience will be better and smoother than ever before.

Again, thanks to all!!!

SlimTeam

SlimKat beta 2 weekly

weekly SlimKat 4.4.2 is on the way...check out the changelog

Happy new year

cheers

SlimRoms Team