Fixed
Status Update
No update yet.
Comments
ra...@google.com
Thank you for reporting this issue. For us to further investigate this issue, please provide the following additional information:
What steps are needed to reproduce this issue? Frequency of occurrence?
Which Android build are you using? (e.g. OPP1.170223.012)
Which device did you use to reproduce this issue?
Android bug report (to be captured after reproducing the issue)
For steps to capture a bug report, please refer:https://developer.android.com/studio/debug/bug-report#bugreportdevice
Alternate method
Navigate to “Developer options”, ensure “USB debugging” is enabled, then enable “Bug report shortcut”. Capture bug report by holding the power button and selecting the “Take bug report” option.
Note: Please upload the bug report and screenshot to google drive and share the folder to android-bugreport@google.com, then share the link here.
What steps are needed to reproduce this issue? Frequency of occurrence?
Which Android build are you using? (e.g. OPP1.170223.012)
Which device did you use to reproduce this issue?
Android bug report (to be captured after reproducing the issue)
For steps to capture a bug report, please refer:
Alternate method
Navigate to “Developer options”, ensure “USB debugging” is enabled, then enable “Bug report shortcut”. Capture bug report by holding the power button and selecting the “Take bug report” option.
Note: Please upload the bug report and screenshot to google drive and share the folder to android-bugreport@google.com, then share the link here.
ra...@google.com
Android version: T
Problem recurrence: Execute Antutu, and pay attention to the XML processing score
Phenomenon: replace the "name expected" in the KXmlParser.java file on the ssi side with a variable. After modification, the XML processing score of Angora Rabbit improved significantly.
Modify to: static final private String NAME_ EXPECTED = "name expected"; And use NAME_ EXPECTED for subsequent "name expected"
Thanks!
Description
Description
The ambient mode screen of the smartwatch is being triggered every time there is a non-watchface app in the foreground, preventing that app from updating its UI and also to send haptic feedback, as it's the case for Google Maps during navigation. For "ambient mode screen" I mean the overlay that blurs the foreground app and just shows the time.
I tested that both during walking navigation and cycling navigation: the watch doesn't vibrate to indicate an upcoming turn, defeating the purpose of wearable navigation. Also, once I do the "wake-up" gesture with the wrist, the Google Maps US takes even more than a second to update the UI, which is less than ideal when cycling. See attached screenshots for Google Maps.
The same issue can be reproduced by opening the stock Stopwatch app and rotating away the wrist or covering the whole watch to put it into ambient mode, see screenshot.
Device info
Bugreport
This is the bugreport, shared withandroid-bugreport@google.com :
https://drive.google.com/file/d/1VJnuTpGSPFGhJ0ce5nFDpNfYEICjRRlJ/view?usp=sharing