Assigned
Status Update
Comments
ga...@gmail.com <ga...@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.
ga...@gmail.com <ga...@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>
ga...@gmail.com <ga...@gmail.com> #4
[Comment deleted]
ga...@gmail.com <ga...@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
User experience
What type of Android issue is this?
User Interface
What steps would let us observe this issue?
What did you expect to happen?
Smooth, 120hz animations to play without jarring cuts or interruptions
What actually happened?
Animations flicker, occasionally fly unpredictably and are interrupted or clip
What was the effect of this issue on your device usage, such as lost time or work?
High
Additional comments
Attached video has the animation duration set to 2x in order to more easily showcase and communicate the animation issues.
Flickering has started since A16B1 for me (I never used any of the DP builds).
Animations ending early if another animation starts or the current animation is otherwise interrupted has been an issue since I purchased this device. This could be due to the absence of parallel animations in Pixel Android (other devices such as Samsung with OneUI and OnePlus OxygenOS, or Apple with iOS DO have these parallel animations and it makes the devices appear much more fluid).
Animation flight path being janky is worsened by the 2x animation duration but is also triggered by fast inputs at 1x speed.
I appreciate that some dodgy animation behaviour can be expected with new versions, especially with Beta 1s, however there are a lot of animation regressions with this build. See here: https://issuetracker.google.com/issues/391729535 for an example of another issue I have experienced (and is indeed shown in the attached video) that has been introduced in this build.
It is my understanding that there is some SystemUI level reorganisation with a codename that got mine and an engineer's comments on another report hidden (so I won't mention it again here), so if this is in the pipeline to be fixed then I will hang tight and wait for the updates to come, but I and I'm sure other testers would at least appreciate some more communication on bug reports than 'Case assigned to person x' or 'We have handed this off to our engineers to review'.
Pixel Android is probably now the least smooth and stable Android skin in my opinion, both as a result of Google's poor and/or worsening animations/UX and other manufacturers leaving Pixel Android behind, despite Google designing both the hardware and software. There are a significant number of broken animations dotted around the launcher and indeed the entire OS, and they are left for months or years on end being ignored. I'm sure many Pixel users including myself would appreciate some improvements on the animations and UX front.
Thank you for reading this far and I apologise if this came off as a rant. I appreciate that I am testing early beta software and stuff like this does happen, but I'm concerned that most UX issues go under the radar.
If there is anything else I can provide to help with this issue, then please reach out. Thanks again for your time.
When
Time and frequency
When did this happen?
Jan 28, 2025 3:00 AM GMT+00:00
How often has this happened?
Every time
Where
Component
Originating component: <not visible> (1684638)
Build and device data
- Build Number: google/raven_beta/raven: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 250332035 (25.03.32 (260400-716700083))
System App (Updated)
Android System WebView
com.google.android.webview
Version 677826033 (131.0.6778.260)
System App (Updated)
Network operator: O2 - UK
SIM operator: giffgaff
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