Question
After updating to Tizen 3.0.0.1, I'm experiencing a delay when the watch screen turns on or switches to the watch face.
I developed a web application for the watch, and this delay wasn't present in version 2.3.1. Upon comparing the visibilitychange event between these versions, I noticed the event triggers at different times, making it appear as a delay in 3.0.0.1.
How should I handle this issue in Tizen 3.0?
Answer
Problem Understanding
The user is experiencing a perceived delay in screen activation and watch face transitions after upgrading to Tizen 3.0.0.1. This appears to be related to changes in the visibilitychange event timing compared to version 2.3.1.
Solution Methods
- Verify with Sample Code: First, test the Basic Watch sample application from Tizen Studio on your device to confirm whether the issue is specific to your implementation or a general platform behavior.
- Event Handling Optimization: Consider optimizing your visibilitychange event handler to minimize processing time when the event triggers.
- Performance Profiling: Use Tizen Studio's profiling tools to identify any performance bottlenecks in your application.
Code Examples
document.addEventListener("visibilitychange", function() {
if (!document.hidden) {
updateWatch(); // Ensure this function is optimized
}
});
Additional Tips
- The Basic Watch sample application shows no delay issues on Gear S2 (2.3.2) or Gear S3/Sport (3.0.0.1), suggesting the issue might be specific to your implementation.
- Consider testing on multiple devices to isolate the problem.
- Review any custom code that might be running during the visibility change event.
