Assigned
Status Update
No update yet.
Comments
xr...@gmail.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.
ga...@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());
}
}
so...@google.com
so...@google.com
[Comment deleted]
dr...@gmail.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.
ar...@gmail.com
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();
xr...@gmail.com
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());
}
xr...@gmail.com
setLastModified doesn't work on Galaxy 10'1 tab OS 3.1 Help !!!
tr...@gmail.com
setLastModified doesn't work on Galaxy 10'1 tab OS 3.1 Help !!!
tr...@gmail.com
Bug still exists on unrooted HTJ85B. Hayes, did you run your test code as root?
tr...@gmail.com
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".
tr...@gmail.com
Also happening in ICS 4.01, Galaxy Nexus.
gu...@google.com
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.
xr...@gmail.com
Any update on this? Samsugn Galaxy Tab 10.1 with 3.2 - it doesn't work too.
xr...@gmail.com
an update on this issue is greatly appreciated
a....@gmail.com
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.
a....@gmail.com
... but 'touch' works from the shell.
j5...@gmail.com
There are some indications that utimensat may work, at least on ICS.
j5...@gmail.com
confirming that it's still not working:
asus transformer prime
ICS
both utime/utimes (C++) and File.setLastModified (C++ JNI)
fails on modifying time of any kind of file on SD card.
asus transformer prime
ICS
both utime/utimes (C++) and File.setLastModified (C++ JNI)
fails on modifying time of any kind of file on SD card.
cu...@gmail.com
[Comment deleted]
cu...@gmail.com
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?
ti...@gmail.com
This is also a problem on a T-Mobile Samsung Galaxy SIII running 4.0.4.
ti...@gmail.com
Same issue on Nexus 7 running JB.
Workaround mentionned in
Workaround mentionned in
an...@gmail.com
Yeah, same issue on Nexus 7 running JB.
there is a solution?
there is a solution?
an...@gmail.com
Now reported to be happening on Galaxy Note 10.1" and Samsung Galaxy SII. It's basically rendering our app to be unusable because we rely on setLastModified(), and we would have to implement hacks/workarounds due to this bug.
Here are the specs on both devices:
Galaxy Note:
Model number: GT-N8013
Android version: 4.0.4 (stock ROM)
Kernel version: 3.0.15-1015435-user se.infra@SEP-120 #1 SMP PREEMPT Mon Aug 13 22:17:27 KST 2012
Build number: IMM76D.N8013UEALH2
Samsung Galaxy SII:
Model number: SAMSUNG-SGH-I727
Android version: 4.0.4 (custom ROM)
Kernel version: 3.0.8-perf-I727UCLE2-CL526987 se.infra@SEP-98 #1 SMP PREEMPT Tue May 8 22:27:38 KST 2012
Build number: SkY ICS 4.2E-7
Here are the specs on both devices:
Galaxy Note:
Model number: GT-N8013
Android version: 4.0.4 (stock ROM)
Kernel version: 3.0.15-1015435-user se.infra@SEP-120 #1 SMP PREEMPT Mon Aug 13 22:17:27 KST 2012
Build number: IMM76D.N8013UEALH2
Samsung Galaxy SII:
Model number: SAMSUNG-SGH-I727
Android version: 4.0.4 (custom ROM)
Kernel version: 3.0.8-perf-I727UCLE2-CL526987 se.infra@SEP-98 #1 SMP PREEMPT Tue May 8 22:27:38 KST 2012
Build number: SkY ICS 4.2E-7
er...@gmail.com
Might be related:
er...@gmail.com
It's a VFS permission problem, the syscall utimensat() fails with EPERM due to root ownership of all files / inappropriate permissions.
in platform/system/core/sdcard/sdcard.c:
> /* all files owned by root.sdcard */
> attr->uid = 0;
> attr->gid = AID_SDCARD_RW;
From utimensat()'s syscall man page:
in platform/system/core/sdcard/sdcard.c:
> /* all files owned by root.sdcard */
> attr->uid = 0;
> attr->gid = AID_SDCARD_RW;
From utimensat()'s syscall man page:
Old FAT allows offers an override of the iattr->valid flag via a mount option to allow changing timestamps to anyone, FUSE+Android's sdcard-FUSE don't do this at the moment (so the 'inode_change_ok() call fails) and the attempt gets rejected with -EPERM. Here's FAT's ./fs/fat/file.c:
xr...@gmail.com
I can confirm this also happens on the Nexus 4.
xr...@gmail.com
And on the ASUS TF700T
be...@gmail.com
Confirming on Nexus 7 2013. PLEASE solve.
be...@gmail.com
What a silly issue. Android was already miserable when it came to backups, and now I learn it can't even preserve the timestamp of a file, how PATHETIC :D
xr...@gmail.com
I'm also affected by this bug on Samsung HomeSync. When I'm copying files there for backup, I see that their modification time becomes current date/time. This is not acceptable as I need to know which file was last modified at what date (for work).
xr...@gmail.com
Please fix it. I need sync files with remote storage.
rl...@gmail.com
Still not solved at present date and Nexus 5 and Android 4.4 :-(
I coul'd not find any sync&backup tool/app which does not need preserving timestamp.
I coul'd not find any sync&backup tool/app which does not need preserving timestamp.
sa...@gmail.com
What
More information
Whe I using Google files it closes the app and won't open the pdf
Where
Build and device data
- Build Number: google/bluejay_beta/bluejay:Baklava/BP22.250103.008/12932282:user/release-keys
(Note: It is the build when sending this report. For exact build reference, please see the attached bugreport.)
Debugging information
Google Play services
com.google.android.gms
Version 250335035 (25.03.35 (260400-720971461))
System App (Updated)
Android System WebView
com.google.android.webview
Version 683416333 (132.0.6834.163)
System App (Updated)
Network operator: Home
SIM operator: TFW
Filed by Android Beta Feedback. Version (Updated): 2.46-betterbug.external_20241023_RC01 (DOGFOOD)
To learn more about our feedback process, please visit
wa...@gmail.com
Huge Issue for me too as I use automatic sync Tools that rely on this. This works just fine on all my non-nexus devices, but since upgrading both to Nexus 7 and 10, I can no longer sync these tablets automatically.
mi...@gmail.com
Root cause seems to have been identified in
an...@google.com
Reporting on non-rooted Samsung Galaxy S4 - like many others on the list above this bug stops syncing apps work correctly (in this case Syncme Wireless). Their list of known bugs/issues points directly to this issue (see http://goo.gl/9y2XO ). Please could this be fixed as soon as possible to enable simple wireless syncing to external devices.
da...@gmail.com
May I ask why this issue has not been fixed yet
md...@gmail.com
So, the Android team will ignore this bug FOREVER just like the others 5k+ bugs ignored on this website???
Google you are making us use MTP instead of Mass Storage because according to you "it was better". Now the files timestamp are messed up.
After transfering all my photos from my Nexus S to my Nexus 4, all the pictures have the same timestamp!! What the hell? The photos order are messed up! PLEASE fix this!!!
Google you are making us use MTP instead of Mass Storage because according to you "it was better". Now the files timestamp are messed up.
After transfering all my photos from my Nexus S to my Nexus 4, all the pictures have the same timestamp!! What the hell? The photos order are messed up! PLEASE fix this!!!
ve...@gmail.com
P.S. This bug is present in ALL MTP DEVICES!
That includes the following Nexus devices:
Nexus 7 (2012), Nexus 7 (2013), Galaxy Nexus, Nexus 4 and Nexus 5.
FIX IT AS SOON AS POSSIBLE PLEASE!!!
That includes the following Nexus devices:
Nexus 7 (2012), Nexus 7 (2013), Galaxy Nexus, Nexus 4 and Nexus 5.
FIX IT AS SOON AS POSSIBLE PLEASE!!!
ve...@gmail.com
Again found my problem in the android bug tracker, unfixed of course, as always.
Forget it guys, google will never fix nerd issues. I bed they not even look at the bug tracker.
We all should be lucky that android still keeps the filename. I see it coming, in the future android will change the filename like this foto.jpg > a1f687f1a851efc2.jpg ;D
But seriously, it is crucial for almost all file sync utilities, and as you may have notices, it's cloud age!
+1 for FIX IT AS SOON AS POSSIBLE PLEASE!!!
Forget it guys, google will never fix nerd issues. I bed they not even look at the bug tracker.
We all should be lucky that android still keeps the filename. I see it coming, in the future android will change the filename like this foto.jpg > a1f687f1a851efc2.jpg ;D
But seriously, it is crucial for almost all file sync utilities, and as you may have notices, it's cloud age!
+1 for FIX IT AS SOON AS POSSIBLE PLEASE!!!
ma...@gmail.com
PLEASE FIX THIS PROBLEM -- YOU ARE DRIVING US INSANE!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
ma...@gmail.com
The inability to preserve timestamps is, I propose, a FATAL flaw, in any file management system.
Whatever the reason that Google and other OS developers choose to ignore this flaw, they might consider that it is a sufficient reason to change platforms and unmitigated by the scores of other useless features.
If I can't rely on a file's date, why have one?
Whatever the reason that Google and other OS developers choose to ignore this flaw, they might consider that it is a sufficient reason to change platforms and unmitigated by the scores of other useless features.
If I can't rely on a file's date, why have one?
Description
What
User experience
What type of issue is this?
Crash
What steps would let us observe this issue?
What did you expect to happen?
Open file
What actually happened?
Crashes
What was the effect of this issue on your device usage, such as lost time or work?
None - device worked normally
When
Time and frequency
Time when bug report was triggered: Jan 23, 2025 9:11 PM GMT-06:00
How often has this happened?
Every time
Where
Component
Suggested component: <not visible> (1684638)
Build and device data
- Build Number: google/cheetah_beta/cheetah:Baklava/BP22.250103.008/12932282:user/release-keys
(Note: It is the build when sending this report. For exact build reference, please see the attached bugreport.)
Related apps
Files by Google
com.google.android.apps.nbu.files
Version 1184643 (1.6131.717750442.1-release)
System App (Updated)
Debugging information
Google Play services
com.google.android.gms
Version 250261035 (25.02.61 (260400-717007275))
System App (Updated)
Android System WebView
com.google.android.webview
Version 677826233 (131.0.6778.262)
System App (Updated)
Network operator: Google Fi
SIM operator: Google Fi
Filed by Android Beta Feedback. Version (Updated): 2.46-betterbug.external_20241023_RC01 (DOGFOOD)https://developer.android.com/preview/feedback#feedback-app .
To learn more about our feedback process, please visit