MagicContext
Awareness Context Automation
Note: this app is not actively maintained anymore.
MagicContext allows the creation of rules to launch a specific playlist. a
rule can be defined by an activity and/or location and/or headphone and a
playlist.
You have to own a Deezer account to use this app.
Anti-Features: NonFreeDep
: The application depends on a non-free application (e.g. Google Maps) - i.e. it requires it to be installed on the device, but does not include it.NonFreeNet
: This application promotes or entirely depends a non-Free network service.

Packages
Version 1.0 (2016-08-11)
Android Versions:
11 Libraries detected:
Libraries:
- Android Support v4 (Development Framework)
requires 4 permissions: android.permission.VIBRATE, android.permission.ACCESS_NETWORK_STATE, android.permission.INTERNET, android.permission.WAKE_LOCK
The Android Support Library is not actually a single library, but rather a collection of libraries that can roughly be divided into two groups: compatibility and component libraries. For details, please see
Understanding the Android Support Library.
- Google Core Libraries for Java 6+ (Utility)
requires 1 permissions: android.permission.INTERNET
a set of core libraries that includes new collection types (such as multimap and multiset), immutable collections, a graph library, functional types, an in-memory cache, and APIs/utilities for concurrency, I/O, hashing, primitives, reflection, string processing, and much more.
- Google Core Libraries (3rd Party) (Utility)
- FasterXML (Utility)
requires 1 permissions: android.permission.INTERNET
a fast and compliant streaming JSON parser/writer with a StAX-like API and support for marshalling/unmarshalling POJOs via annotations.
- Glide (Utility)
requires 3 permissions: android.permission.INTERNET, android.permission.ACCESS_NETWORK_STATE, android.permission.VIBRATE
An image loading and caching library for Android focused on smooth scrolling
- Android Design Support Library (Utility)
provides APIs to support additional important material design components and patterns to applications beyond those covered by the Android framework, to all devices running Android 2.1 or later.
- Android Support v7 (Development Framework)
The Android Support Library is not actually a single library, but rather a collection of libraries that can roughly be divided into two groups: compatibility and component libraries. For details, please see
Understanding the Android Support Library.
- Google Maps APIⒹⓃ (Map)
API to automatically handle access to Google Maps servers, data downloading, map display, and response to map gestures.
- Google Mobile ServicesⒹ (Development Framework)
Google Mobile Services in terms of the Android library refers to
Google Play Services, a proprietary background service and API package for Android devices which is
not part of the Android Open Source Project (AOSP). The library does not contain those services (i.e. it usually requires the Google Framework, often referred to as „GApps“, being installed on the device), but allows an app to communicate with them. Be aware this usually goes along with transferring at least parts of your personal data to the Google network.
- Dagger (Utility)
A fast dependency injector for Android and Java.
- JavaX Dependency Injection (Utility)
specifies a means for obtaining objects in such a way as to maximize reusability, testability and maintainability compared to traditional approaches such as constructors, factories, and service locators (e.g., JNDI). This process, known as dependency injection, is beneficial to most nontrivial applications.
Payment Modules:
- None found
specifies a means for obtaining objects in such a way as to maximize reusability, testability and maintainability compared to traditional approaches such as constructors, factories, and service locators (e.g., JNDI). This process, known as dependency injection, is beneficial to most nontrivial applications.
Ads & Analytics:
- None found
specifies a means for obtaining objects in such a way as to maximize reusability, testability and maintainability compared to traditional approaches such as constructors, factories, and service locators (e.g., JNDI). This process, known as dependency injection, is beneficial to most nontrivial applications.
Download (4.2 M)