This issue tracker has been migrated to GitHub ,
and is currently read-only.
For more information,
see the GitHub FAQs in the Python's Developer Guide.
| Author | yan12125 |
|---|---|
| Recipients | Alex.Willmer, Roman.Evstifeev, lemburg, xdegaye, yan12125 |
| Date | 2016年05月04日.19:47:19 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1462391239.91.0.0396646991777.issue26855@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
Several questions on implementation: 1. Should Android 4.1 supported? If not pass_fds and logics for deriving it can be removed. 2. I can't find ro.build.version.full on any device/emulator I have access to. Maybe it should be removed due to low popularity? Some related Android source codes, as my implementation basis: 1. Android 4.1's ANDROID_PROPERTY_WORKSPACE: https://android.googlesource.com/platform/bionic/+/android-4.1.1_r1/libc/bionic/system_properties.c#55 2. The Android Framework assumes property values to be valid UTF-8: https://android.googlesource.com/platform/frameworks/base/+/android-5.1.1_r37/core/jni/android_os_SystemProperties.cpp#49. In fact if I feed a malformed /system/build.prop to DalvikVM, it crashes [1] 3. Google's Android Compatibility Test Suite (CTS) [2] assumes `getprop` binary is in $PATH and can be executed: https://android.googlesource.com/platform/cts/+/android-5.1.1_r37/tests/tests/os/src/android/os/cts/BuildTest.java#110 [1] https://github.com/rave-engine/python3-android/pull/10#issuecomment-159390390 [2] https://source.android.com/compatibility/cts/ |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2016年05月04日 19:47:19 | yan12125 | set | recipients: + yan12125, lemburg, xdegaye, Roman.Evstifeev, Alex.Willmer |
| 2016年05月04日 19:47:19 | yan12125 | set | messageid: <1462391239.91.0.0396646991777.issue26855@psf.upfronthosting.co.za> |
| 2016年05月04日 19:47:19 | yan12125 | link | issue26855 messages |
| 2016年05月04日 19:47:19 | yan12125 | create | |