Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • A AndroidAsync
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 333
    • Issues 333
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 19
    • Merge requests 19
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Koushik Dutta
  • AndroidAsync
  • Merge requests
  • !215

use another hash function if MD5 is not available

  • Review changes

  • Download
  • Email patches
  • Plain diff
Merged Steve Lhomme requested to merge github/fork/robUx4/missing_md5_workaround into master Jul 29, 2014
  • Overview 7
  • Commits 1
  • Pipelines 0
  • Changes 1

On some devices (at least some 4.0 and 4.1 ones) we can still look around for an other hash algorithm and use it for the rest of the lifetime of the app. Subsequent runs should produce the same result. An update of the OS should use MD5 if it's there and the old cache files with a different hash will die as new elements are pushed in the cache.

Assignee
Assign to
Reviewers
Request review from
Time tracking
Source branch: github/fork/robUx4/missing_md5_workaround