Assigned
Status Update
Comments
ad...@google.com <ad...@google.com>
ad...@google.com <ad...@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.
md...@gmail.com <md...@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());
}
}
md...@gmail.com <md...@gmail.com> #4
[Comment deleted]
ad...@google.com <ad...@google.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.
ad...@google.com <ad...@google.com> #6
Confirmed. When I'm not running as root I can create and delete files, but setLastModified() still fails. That's a bug! It works when running as root.
As a workaround, this ugly hack will set the last modified date to now:
RandomAccessFile raf = new RandomAccessFile(file, "rw");
long length = raf.length();
raf.setLength(length + 1);
raf.setLength(length);
raf.close();
As a workaround, this ugly hack will set the last modified date to now:
RandomAccessFile raf = new RandomAccessFile(file, "rw");
long length = raf.length();
raf.setLength(length + 1);
raf.setLength(length);
raf.close();
md...@gmail.com <md...@gmail.com> #7
It works for me on Xoom 3.2 Built HTJ85B
public void testSetLastModified() throws IOException {
long time = 1316137362000L;
File file = new File("/mnt/sdcard/foo");
file.createNewFile();
file.setLastModified(time);
assertEquals(time, file.lastModified());
}
public void testSetLastModified() throws IOException {
long time = 1316137362000L;
File file = new File("/mnt/sdcard/foo");
file.createNewFile();
file.setLastModified(time);
assertEquals(time, file.lastModified());
}
v1...@gmail.com <v1...@gmail.com> #8
setLastModified doesn't work on Galaxy 10'1 tab OS 3.1 Help !!!
ac...@gmail.com <ac...@gmail.com> #9
setLastModified doesn't work on Galaxy 10'1 tab OS 3.1 Help !!!
el...@gmail.com <el...@gmail.com> #10
Bug still exists on unrooted HTJ85B. Hayes, did you run your test code as root?
go...@gmail.com <go...@gmail.com> #11
On an Acer Iconia tablet with OS 3.2, it works for /mnt/external_sd (the removable SD card) and /mnt/usb_storage (the removable USB storage), but still NOT for /mnt/sdcard (the internal SD card). The return value is "false".
ps...@google.com <ps...@google.com> #12
Also happening in ICS 4.01, Galaxy Nexus.
v1...@gmail.com <v1...@gmail.com> #13
Any update on this? I'd like to know if it's ever going to be fixed - my app depends on setLastModified for its basic functionality.
Unfortunately Jesse, your workaround doesn't help me. I need to set times other than current.
Unfortunately Jesse, your workaround doesn't help me. I need to set times other than current.
ad...@google.com <ad...@google.com> #14
Any update on this? Samsugn Galaxy Tab 10.1 with 3.2 - it doesn't work too.
ro...@gmail.com <ro...@gmail.com> #15
an update on this issue is greatly appreciated
ad...@google.com <ad...@google.com> #16
On my transformer tf201, chmod and utime both fail with errno=1 (Operation not permitted)
This seems to be an issue with the fuse filesystem.
Test code attached.
This seems to be an issue with the fuse filesystem.
Test code attached.
na...@gmail.com <na...@gmail.com> #17
... but 'touch' works from the shell.
pe...@gmail.com <pe...@gmail.com> #18
There are some indications that utimensat may work, at least on ICS.
nu...@gmail.com <nu...@gmail.com> #19
Comment has been deleted.
ld...@gmail.com <ld...@gmail.com> #20
[Comment deleted]
pe...@gmail.com <pe...@gmail.com> #21
utimensat gives linkage error with the latest NDK, looks like declared but not implemented.
Fuse seems to be ok, but the mount is missing allow_utime. So seems like a permission error. Google can you atleast confirm if it's a feature or bug?
Fuse seems to be ok, but the mount is missing allow_utime. So seems like a permission error. Google can you atleast confirm if it's a feature or bug?
nu...@gmail.com <nu...@gmail.com> #22
This is also a problem on a T-Mobile Samsung Galaxy SIII running 4.0.4.
Description
This issue is related / continuation of this one: https://issuetracker.google.com/issues/342375585
Digi is a new operator in Portugal (already operating in other European countries). It supports VoWiFi in other devices (iOS and Samsung) but not in Pixels. In Pixels, the WiFi Calling option does not exist in the menu.
Are you an Android developer?" (Y/N)
Which Android Developer Preview build are you using? See Settings > About phone > Build number: BP22.250103.008
Is this a regression from Android 15 to 16? - No
What device are you using? (for example, Android Emulator, GSI, Pixel 9) - Pixel 7
What are the steps to reproduce the problem?
Use SIM card from the new Digi operator in Portugal and see that VoWiFi is not appearing in the menu as usual. Can only be enabled by using Shizuku + Pixel IMS
Issue Category e.g. Framework (platform), NDK (platform), Hardware (CPU, GPU, Sensor, Camera), ART (platform), Runtime Permissions etc:
Platform.
What was the expected result?
To have VoWiFi working like before.