Gitiles
Code Review Sign In
gerrit-public.fairphone.software / fp2-dev / vendor / fairphone / checkup / d3e094365e3d940d5b55b5b4aa7a6b1e3fccc0e1
commitd3e094365e3d940d5b55b5b4aa7a6b1e3fccc0e1[log] [tgz]
authorMaarten Derks <maarten@fairphone.com>Mon Dec 19 11:17:28 2016 +0100
committerMaarten Derks <maarten@fairphone.com>Mon Dec 19 11:17:28 2016 +0100
treef86141335b44d29cff67837a1c90c725cc8f4f96
parent9ce07bb94c8677a4717d2770218ffbe46650256e [diff]
parenta8ca8939adb38d912e5eb91da6160da592f01090 [diff]
Merge branch 'CHK-23' into 'master'

CHK-23: Prevent SecretCodeReceiver from disabling MainActivity

The SecretCodeReceiver was disabling the MainActivity in the package manager upon first boot. 
The reason we did not see this happen before was because the SecretCodeReceiver was launching a different activity (ModuleChooser) than the Settings app (MainActivity). Since version 2.0.0 both point to the same activity (MainActivity), so since then the issue has arisen.

The reason why our SecretCodeReceiver behaved like this is because it comes from the Hi-P test app. There you see a launcher icon, upon first launch it registers the SecretCodeReceiver and disables the launcher icon.

See merge request !19
tree: f86141335b44d29cff67837a1c90c725cc8f4f96
  1. app/
  2. gradle/
  3. .gitignore
  4. Android.mk
  5. build.gradle
  6. gradlew
  7. gradlew.bat
  8. LICENSE.txt
  9. README.md
  10. settings.gradle
README.md

Fairphone 2 module tester

Android app that allows users to test the modules and their components inside the Fairphone 2.

FP2
|-- Display module
|   |-- Display
|   `-- Digitizer
|-- Battery
|-- Receiver module
|   |-- Headphone jack
|   |-- Proximity sensor
|   |-- LED
|   |-- Ear speaker
|   `-- Front camera
|-- Camera module
|   |-- Rear camera
|   `-- Flash
|-- Speaker module
|   |-- Vibration motor
|   |-- Rear speaker
|   |-- Microphone
|   `-- USB port
`-- Tranceiver module
    |-- SIM slots
    |-- microSD slot
    |-- Hardware buttons
    |-- GPS
    `-- Gyroscope

(incomplete)

Versioning scheme

The app version (a.k.a Version Code) is based on the following scheme:

  • Major version number
  • Minor version number
  • Release status number (snapshot/release candidate/public release)

The rules are as follow:

  • The major version uses two digits
  • The minor version uses two digits
  • The release status uses two digits
  • The major version should be bumped when introducing new features
  • The minor version should be bumped whenever there is a (simple/hot) fix
  • The release status must be 0 while developing (snapshot)
  • The release status must be in [1;98] while testing releases (release candidate)
  • The release status must be 99 for a public release

The readable app version (a.k.a Version Name) is based on the app version with the following schemes:

  • Snapshots are named after .-SNAPSHOT
  • Release candidates are named after .-RC
  • Public releases are named after .