File: control

package info (click to toggle)
dummydroid 1.2-2
  • links: PTS, VCS
  • area: main
  • in suites: buster, sid
  • size: 6,524 kB
  • sloc: java: 2,617; xml: 100; makefile: 2
file content (41 lines) | stat: -rw-r--r-- 1,815 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
Source: dummydroid
Section: devel
Priority: optional
Maintainer: Android tools Maintainer <android-tools-devel@lists.alioth.debian.org>
Uploaders: Hans-Christoph Steiner <hans@eds.org>
Build-Depends: debhelper (>= 11),
               default-jdk,
               javahelper,
               junit,
               libmaven-assembly-plugin-java,
               libprotobuf-java,
               maven-debian-helper (>= 1.5~)
Standards-Version: 4.2.1
Vcs-Git: https://salsa.debian.org/android-tools-team/dummydroid.git
Vcs-Browser: https://salsa.debian.org/android-tools-team/dummydroid
Homepage: http://www.onyxbits.de/dummydroid

Package: dummydroid
Architecture: all
Depends: ${java:Depends}, ${misc:Depends},
         libhttpclient-java,
         libhttpcore-java
Recommends: ${java:Recommends}
Description: Register a GSF ID for mock-up Android devices
 Dummy Droid allows you to create hardware profiles for arbitrary
 Android devices and upload them into your Google Play account,
 thereby creating a "Google Services Framework ID".
 .
 Mocks can either be generated from the /system/build.prop file of
 existing hardware or be completely made up from scratch. You (may)
 need this tool if Google Play won't give you access to an app because
 of device incompatibilities, country or carrier restrictions. You
 (may) also need this tool if you are an app developer yourself and
 want to test compatibility filter settings without actually owning
 the target device.
 .
 Word of warning: Dummy Droid grants you absolute freedom, including
 the freedom to specify absolute nonsense (such as a smart-tv with a
 screensize of 1 pixel). Please pay attention to the instructions and
 use a throw-away account for testing. Otherwise you might end up with
 dozens of mocks in your main account you cannot get rid of again!