Assigned
Status Update
Comments
ba...@google.com <ba...@google.com> #2
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.
ya...@gmail.com <ya...@gmail.com> #3
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());
}
}
ba...@google.com <ba...@google.com> #4
[Comment deleted]
ya...@gmail.com <ya...@gmail.com> #5
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
What's the Problem?
We know that installing apps can be a concern for users who value their online security and privacy. That's why we're introducing this new feature to provide you with greater control over app permissions.
How Does it Work?
With Android 16, you'll have the ability to install applications in either:
Android Space: If an app is downloaded from the Google Play Store or a trusted source, it will be verified and installed in the Android space.
Sandboxed Side: If an app is obtained from an external source, it will be installed in the sandboxed side.
This approach allows you to grant temporary or limited permissions, or deny access altogether, within the sandboxed environment.
Benefits for Users
With this new feature, you'll enjoy:
Enhanced App Privacy: By installing apps in a secure, isolated environment, you'll have greater control over your personal data.
Improved Security: Sandbox app installation reduces the risk of malware and other security threats.
Greater Flexibility: You'll be able to choose whether to install an app temporarily in either the sandboxed side or the Android space, depending on your needs.
Better App Permission Control: With this feature, you'll have more control over which permissions are granted to each app.
Technical Details
Here's a breakdown of how this feature works:
Sandbox Environment: The sandbox environment is a secure, isolated area where apps are installed and run. It's designed to prevent unauthorized access to sensitive data.
Verification Process: When an app is downloaded from the Google Play Store or a trusted source, it will be verified through a secure process to ensure its authenticity and security.
Permission Control: Within the sandboxed environment, you'll have control over which permissions are granted to each app. You can choose to grant temporary or limited permissions, or deny access altogether.