Assigned
Status Update
Comments
mi...@gmail.com <mi...@gmail.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.
gg...@google.com <gg...@google.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());
}
}
rc...@gmail.com <rc...@gmail.com> #4
[Comment deleted]
rc...@gmail.com <rc...@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.
pe...@gmail.com <pe...@gmail.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();
be...@gmail.com <be...@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());
}
be...@gmail.com <be...@gmail.com> #8
setLastModified doesn't work on Galaxy 10'1 tab OS 3.1 Help !!!
je...@gmail.com <je...@gmail.com> #9
setLastModified doesn't work on Galaxy 10'1 tab OS 3.1 Help !!!
da...@gmail.com <da...@gmail.com> #10
Bug still exists on unrooted HTJ85B. Hayes, did you run your test code as root?
co...@gmail.com <co...@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".
su...@gmail.com <su...@gmail.com> #12
Also happening in ICS 4.01, Galaxy Nexus.
ez...@gmail.com <ez...@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.
ez...@gmail.com <ez...@gmail.com> #14
Any update on this? Samsugn Galaxy Tab 10.1 with 3.2 - it doesn't work too.
ho...@gmail.com <ho...@gmail.com> #15
an update on this issue is greatly appreciated
ho...@gmail.com <ho...@gmail.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.
ro...@gmail.com <ro...@gmail.com> #17
... but 'touch' works from the shell.
m4...@gmail.com <m4...@gmail.com> #18
There are some indications that utimensat may work, at least on ICS.
m....@gmail.com <m....@gmail.com> #19
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.
je...@gmail.com <je...@gmail.com> #20
[Comment deleted]
je...@gmail.com <je...@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?
ta...@gmail.com <ta...@gmail.com> #22
This is also a problem on a T-Mobile Samsung Galaxy SIII running 4.0.4.
ja...@gmail.com <ja...@gmail.com> #23
Same issue on Nexus 7 running JB.
Workaround mentionned in comment #5 works to set modified time to current time.
Workaround mentionned in
ro...@gmail.com <ro...@gmail.com> #24
Yeah, same issue on Nexus 7 running JB.
there is a solution?
there is a solution?
rr...@gmail.com <rr...@gmail.com> #25
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
k8...@gmail.com <k8...@gmail.com> #26
Might be related: issue 36949180
k8...@gmail.com <k8...@gmail.com> #27
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:
sb...@gmail.com <sb...@gmail.com> #29
I can confirm this also happens on the Nexus 4.
di...@gmail.com <di...@gmail.com> #30
And on the ASUS TF700T
mt...@gmail.com <mt...@gmail.com> #31
Confirming on Nexus 7 2013. PLEASE solve.
mt...@gmail.com <mt...@gmail.com> #32
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
ir...@gmail.com <ir...@gmail.com> #33
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).
ir...@gmail.com <ir...@gmail.com> #34
Please fix it. I need sync files with remote storage.
ra...@gmail.com <ra...@gmail.com> #35
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.
ra...@gmail.com <ra...@gmail.com> #36
Information redacted by Android Beta Feedback.
ka...@gmail.com <ka...@gmail.com> #37
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.
al...@gmail.com <al...@gmail.com> #38
Root cause seems to have been identified in comment #29 . As many have already noted, this bug breaks all sync and backup programs unless the user has rooted his device. This bug exists on several non-rooted Android devices I own (different manufacturers and models). It does not exist on any rooted Android device I own. This is a significant issue. Can someone fix this?
mu...@gmail.com <mu...@gmail.com> #39
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.
pa...@gmail.com <pa...@gmail.com> #40
May I ask why this issue has not been fixed yet
ac...@gmail.com <ac...@gmail.com> #41
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!!!
dj...@gmail.com <dj...@gmail.com> #42
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!!!
Description
(Note: It is the build when sending this report. For exact build reference, please see the attached bugreport.)
What type of Android issue is this? Touch / Gesture
When did this happen?
23 Jan 2025 21:55 GMT+00:00
What steps would let us observe this issue?
1. Switching apps wallpaper flashes through the app when switching
What did you expect to happen?
For it to be normal
What actually happened?
Glitch when switching apps the wallpaper flashes through the apps when switching
How often has this happened?
Every time
What was the effect of this issue on your device usage, such as lost time or work?
None - device worked normally
Additional comments
Please get a hotfix out
Debugging information
Google Play services
com.google.android.gms
Version 250231035 (25.02.31 (260400-713337402))
System App (Bundled)
Android System WebView
com.google.android.webview
Version 661308832 (128.0.6613.88)
System App (Updated)
Network operator: O2 - UK
SIM operator: giffgaff
Filed by Android Beta Feedback. Version (Bundled): 2.25-betterbug.external_20220328_RC02
To learn more about our feedback process, please visit