Assigned
Status Update
No update yet.
Comments
vi...@google.com
My SD card's file system supports a last modified timestamp; that is 'adb shell touch /mnt/sdcard/foo' works as expected. I need to check that calling from runtime works as well.
s3...@gmail.com
I couldn't reproduce this with a test case.
@hardwick.jim if this test doesn't pass for you, could you paste its output here? As well as your device's full version information. Thanks.
public final class FileTest extends TestCase {
public void testSetLastModified() {
File file = new File("/mnt/sdcard/foo");
assertTrue(file.setLastModified(0));
assertEquals(0, file.lastModified());
}
}
@hardwick.jim if this test doesn't pass for you, could you paste its output here? As well as your device's full version information. Thanks.
public final class FileTest extends TestCase {
public void testSetLastModified() {
File file = new File("/mnt/sdcard/foo");
assertTrue(file.setLastModified(0));
assertEquals(0, file.lastModified());
}
}
vi...@google.com
[Comment deleted]
vi...@google.com
Attached is the logcat lines from your testcase and my FileTest.java for line number references.
Device is a Motorola Xoom 3G from Verizon, Android 3.1, HMJ37, rooted. I'm not sure what other device info you need, so let me know if you need more.
I can also post the source and results of my tests on stock HMJ37 Xooms - both 3G and WiFi only - but it will take a couple days to get my hands on those devices again since I only own the rooted Xoom.
Device is a Motorola Xoom 3G from Verizon, Android 3.1, HMJ37, rooted. I'm not sure what other device info you need, so let me know if you need more.
I can also post the source and results of my tests on stock HMJ37 Xooms - both 3G and WiFi only - but it will take a couple days to get my hands on those devices again since I only own the rooted Xoom.
Description
Android build number: BP22.250124.008 dev-keys
Application: literaly any android application that:
android.permission.BODY_SENSORSpermissionExpected behaviour:
Actual behaviour:
Current behaviour makes Android 16 backward incompatible with earlier Android versions, as apps that target Android 15, use BODY_SENSORS permission and which don't use Health Connect (which would force privacy policy activity in manifest on them already) would not have any way to have access to heart rate data without updating app (to include privacy policy activity in manifest).
I assume this comes from fact that on Android 16 BODY_SENSORS permission is implicitly being replaced by HEART_RATE permission even for apps targeting android 15.
And HEART_RATE permission, being a part of Health Connect requires the app to have privacy policy, which was not a requirement for BODY_SENSORS permission.