fdroid-data/metadata/au.id.micolous.farebot.yml

112 lines
3.3 KiB
YAML
Raw Blame History

This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

Categories:
- Navigation
License: GPL-3.0-or-later
WebSite: https://www.metrodroid.org
SourceCode: https://github.com/metrodroid/metrodroid
IssueTracker: https://github.com/metrodroid/metrodroid/issues
Translation: https://hosted.weblate.org/engage/metrodroid/
Changelog: https://github.com/metrodroid/metrodroid/wiki/Changelog
AutoName: Metrodroid
Description: |-
Metrodroid can read information from some public transport NFC smartcards. It
was formerly known as Farebot M.
This is a fork of Eric Butlers Farebot project, with support for additional
cards and bug fixes.
Supported cards:
* Bilhete Único - São Paulo, Brazil (1) (2) (5)
* Clipper - San Francisco, CA, USA
* EZ-Link - Singapore (3)
* Go card - Brisbane and South East Queensland, Australia (0) (1) (2)
* Manly Fast Ferry - Sydney (and surrounds), NSW, Australia (0) (1) (2)
* Matkakortti, HSL - Finland
* Myki - Melbourne (and surrounds), VIC, Australia (0) (4)
* MyWay - Australian Capital Territory, Australia (0) (1) (2) (5)
* NETS Flashpay - Singapore
* Octopus - Hong Kong (0)
* Opal - Sydney, NSW, Australia (0)
* ORCA - Seattle, WA, USA
* OV-chipkaart - Netherlands (1) (2)
* Shenzhen Tong - Shenzong, Guangdong Province, China (0)
* SmartRider - Western Australia, Australia (0) (1) (2)
* Suica, IOCOA, PASMO, Edy - Japan
* Transit Access Pass - Los Angeles, CA, USA (0) (1) (2)
(0): New in Metrodroid.
(1): Not compatible with all devices (Mifare Classic).
(2): Encryption keys are required to read this card.
(3): Not compatible with all devices (CEPAS).
(4): Only the card number can be read.
(5): Fallback reader -- must be explicitly enabled in the applications
preferences.
You require a NFC-compatible phone in order to read cards.
You need a NXP NFC chipset in your phone in order to read MIFARE Classic cards.
Some phones have NFC chips from other manufacturers, which do not read Mifare
Classic cards (eg: Nexus 4, Nexus 5, Samsung Galaxy S4). Check the About screen
in the app in order to determine if your phone supports MIFARE Classic.
Some agencies have encrypted cards. You will need to acquire encryption keys in
order to read them. These are generally unique to each card. Sorry, I cant help
you with this.
Some other agencies cards using Cubic Nextfare on Mifare Classic may also work.
RepoType: git
Repo: https://github.com/metrodroid/metrodroid
Builds:
- versionName: v2.9.30-fdroid
versionCode: 30
commit: v2.9.30
submodules: true
gradle:
- yes
forceversion: true
- versionName: v2.9.31-fdroid
versionCode: 31
commit: v2.9.31
submodules: true
gradle:
- yes
forceversion: true
- versionName: v2.9.32-fdroid
versionCode: 32
disable: Could not find com.android.tools.build:gradle:3.0.0
commit: v2.9.32
submodules: true
gradle:
- yes
forceversion: true
- versionName: 2.9.34
versionCode: 570
commit: v2.9.34
submodules: true
gradle:
- yes
forceversion: true
- versionName: 2.9.37
versionCode: 2005
commit: v2.9.37
submodules: true
gradle:
- yes
forceversion: true
AutoUpdateMode: None
UpdateCheckMode: Tags
CurrentVersion: 3.0.0