6f0a95b828
Update notifications setting when m.local_notification_settings.<device-id> event changes for current device (PSG-874) |
||
|---|---|---|
| .github | ||
| .idea | ||
| changelog.d | ||
| docs | ||
| fastlane | ||
| gradle/wrapper | ||
| library | ||
| matrix-sdk-android | ||
| matrix-sdk-android-flow | ||
| resources/img | ||
| tools | ||
| vector | ||
| vector-app | ||
| vector-config | ||
| .editorconfig | ||
| .gitattributes | ||
| .gitignore | ||
| AUTHORS.md | ||
| build.gradle | ||
| CHANGES.md | ||
| CONTRIBUTING.md | ||
| coverage.gradle | ||
| dependencies.gradle | ||
| dependencies_groups.gradle | ||
| Gemfile | ||
| Gemfile.lock | ||
| gradle.properties | ||
| gradlew | ||
| gradlew.bat | ||
| integration_tests_script.sh | ||
| integration_tests_script_github.sh | ||
| LICENSE | ||
| README.md | ||
| settings.gradle | ||
| towncrier.toml | ||
Element Android
Element Android is an Android Matrix Client provided by Element. The app can be run on every Android devices with Android OS Lollipop and more (API 21).
It is a total rewrite of Riot-Android with a new user experience.
Build of develop branch: Nightly test status: 
New Android SDK
Element is based on a new Android SDK fully written in Kotlin (like Element). In order to make the early development as fast as possible, Element and the new SDK currently share the same git repository.
At each Element release, the SDK module is copied to a dedicated repository: https://github.com/matrix-org/matrix-android-sdk2. That way, third party apps can add a regular gradle dependency to use it. So more details on how to do that here: https://github.com/matrix-org/matrix-android-sdk2.
Roadmap
The version 1.0.0 of Element still misses some features which was previously included in Riot-Android. The team will work to add them on a regular basis.
Releases to app stores
There is some delay between when a release is created and when it appears in the app stores (Google Play Store and F-Droid). Here are some of the reasons:
- Not all versioned releases that appear on GitHub are considered stable. Each release is first considered beta: this continues for at least two days. If the release is stable (no serious issues or crashes are reported), then it is released as a production release in Google Play Store, and a request is sent to F-Droid too.
- Each release on the Google Play Store undergoes review by Google before it comes out. This can take an unpredictable amount of time. In some cases it has taken several weeks.
- In order for F-Droid to guarantee that the app you receive exactly matches the public source code, they build releases themselves. When a release is considered stable, Element staff inform the F-Droid maintainers and it is added to the build queue. Depending on the load on F-Droid's infrastructure, it can take some time for releases to be built. This always takes at least 24 hours, and can take several days.
If you would like to receive releases more quickly (bearing in mind that they may not be stable) you have a number of options:
- Sign up to receive beta releases via the Google Play Store.
- Install a release APK directly - download the relevant .apk file and allow installing from untrusted sources in your device settings. Note: these releases are the Google Play version, which depend on some Google services. If you prefer to avoid that, try the latest dev builds, and choose the F-Droid version.
- If you're really brave, install the very latest dev build - pick a build, then click on
Summaryto download the APKs from there:vector-Fdroid-debugandvector-Gplay-debugcontains the APK for the desired store. Each file contains 5 APKs. 4 APKs for every supported specific architecture of device. In doubt you can install theuniversalAPK.
Contributing
Please refer to CONTRIBUTING.md if you want to contribute on Matrix Android projects!
Come chat with the community in the dedicated Matrix room.
Also this documentation can hopefully help developers to start working on the project.
Triaging issues
Issues are triaged by community members and the Android App Team, following the triage process.
We use issue labels to sort all incoming issues.