Yureka Device Review: Sensors, Bugs, and More

Introduction to Yureka

The Yureka, a popular device manufactured by Xiaomi, is well-known for its sleek design and impressive features. However, like many devices, it comes with its share of challenges and potential bugs. This review will delve into the sensors, major defects, and unresolved bugs reported by users, focusing on the accelerometer, gyro, and proximity sensors, as well as the broader user experience issues.

Sensors in Yureka

The core sensors in the Yureka include the accelerometer, gyro, and proximity sensors. These sensors play a crucial role in enhancing the device's functionality, from responsive touchscreen interactions to phone calls. Shivam mentioned the use of these sensors, which is an essential aspect of any mobile device.

Sensors and User Feedback

Shortly after the release, issues with the proximity sensor were identified. This sensor is responsible for detecting the proximity of an object to the device's screen to activate or deactivate the screen. Shivam reported that the device's first batch had an issue with the proximity sensor, which required calibration (using the code 7769) to resolve.

Major Bugs and Defects

Several bugs and defects have been reported by users:

Contact List Issues

On CyanogenMod 11 and 12, the contact list did not provide an option to display contacts only from the phone memory, displaying additional contacts from other accounts as well, making it difficult to navigate. In CM12, the option to display SIM contacts in the contact list is missing, which is available in stock Android Lollipop. There is no option to set the default write disk to external storage, such as an SD card, which is available in stock Android but not in CyanogenMod.

Time Format Issue

The 12-hour time format did not display AM or PM on the status bar or in the clock widget, leading to user dissatisfaction. Shivam noted that this was a major bug in both CyanogenMod versions.

Proximity Sensor Update

Interestingly, the proximity sensor issue resolved itself for many users when they updated their phones through Over-The-Air (OTA) updates. However, some users reported issues with the Sensor.TYPE_ORIENTATION in a custom application, indicating that while the update helped, it may not have resolved every sensor-related problem for everyone.

Conclusion and Recommendations

Given the varied user experiences and reported bugs, users should consider these factors before purchasing a Yureka device. While some issues have been resolved through updates, it's important for users to weigh these against their individual needs and preferences.

Conclusion

Understanding the sensors, bugs, and unresolved issues in the Yureka can help potential buyers make an informed decision. Whether you are a developer or a regular user, this review aims to provide insights into the device's performance and potential challenges. Stay informed and keep your device up to date to enjoy a smoother user experience.