Connect with us

Google

Pixel 9 data collection sparks privacy debate: Google responds

Published

on

Recent research from Cybernews has raised concerns over how frequently the new Google Pixel 9 Pro XL sends personal data to Google servers, reportedly every 15 minutes. According to Aras Nazarovas, a security researcher at Cybernews, this data includes sensitive information such as the user’s location, email address, phone number, and other telemetry data. Furthermore, the device allegedly downloads and executes new code, leading to potential security risks.

Concerns Over Frequent Data Transmission

Nazarovas claims that the Pixel 9 Pro XL’s frequent use of personal information, such as location and network status, doesn’t align with the industry’s best practices for data anonymization. According to his analysis, the device sends authentication requests every 15 minutes and a ‘check-in’ request roughly every 40 minutes, even when GPS is disabled. The data is shared with multiple Google endpoints, including those related to device management, policy enforcement, and even Google Photos’ Face Grouping feature.

This continuous communication with Google’s servers, particularly without user interaction or explicit consent for specific services like facial recognition, has sparked concerns about how much control users truly have over their data.

Google’s Response to the Allegations

In response to these claims, Google refuted the allegations and clarified that data transmission is not only common but necessary for ensuring a smooth user experience across all devices, regardless of the manufacturer. The company emphasized that user security and privacy remain top priorities and that data sharing can be managed and configured during the device setup or in the settings.

A Google spokesperson responded by stating:
“This report lacks essential context and misinterprets technical details. Data transmissions are required for legitimate services on all mobile devices, regardless of the manufacturer, model, or OS. These services include software updates, on-demand features, and personalized experiences.”

Privacy and Consent Issues

One of the more alarming findings from the Cybernews report was the Pixel 9’s ability to connect to services like Google Photos’ Face Grouping feature without explicit user consent. This is particularly concerning, as biometric data such as facial recognition is involved. Nazarovas emphasized that these practices go against privacy norms, especially when it comes to sensitive data processing without users’ explicit approval.

Industry Implications

The privacy concerns surrounding the Pixel 9 Pro XL have ignited discussions in the tech community about data handling and consent. Many argue that companies should adopt stronger safeguards to ensure users are fully aware of and can control the data their devices are transmitting. With this report bringing such practices to light, it’s clear that transparency in data handling will continue to be a hot topic as technology evolves.

While Google maintains that the data collected is essential for maintaining device functionality and enhancing user experience, the need for clearer communication and user consent remains an area for improvement. The Pixel 9 data transmission report highlights the fine line between necessary data collection and user privacy, reinforcing the importance of trust in tech ecosystems.

Conclusion

As digital devices become more integrated into everyday life, concerns over privacy and data handling will only grow. While Google has addressed the report’s findings, the debate over implicit consent and data transparency raises important questions about how tech companies can better protect user information. Ultimately, the Pixel 9 case serves as a reminder that even routine data practices should be scrutinized for their impact on user privacy.

Source

Google

Android 15 introduces true variable refresh rate support, but there are limitations

Published

on

Android 15

Android 15 Brings True Variable Refresh Rate (VRR) Support

Most modern Android smartphones, including mid-range and flagship devices, come equipped with high-refresh-rate displays. These screens often operate at fixed rates like 60Hz, 90Hz, or 120Hz. Even some budget phones now feature refresh rates above the standard 60Hz. However, while many phones boast this feature, they lack true variable refresh rate (VRR) technology. Despite manufacturers marketing VRR support through LTPO (Low-Temperature Polycrystalline Oxide) displays, Android itself didn’t fully support VRR until the release of Android 15.

What Is Adaptive Refresh Rate in Android 15?

With Android 15, Google has introduced Adaptive Refresh Rate (ARR), a form of VRR, directly into the operating system. Previously, Android could switch between different fixed refresh rates like 60Hz and 90Hz based on the display mode. However, this was not a true adaptive system. The operating system would switch modes based on content but couldn’t seamlessly adjust refresh rates within a single mode.

In Android 15, ARR dynamically adjusts the refresh rate according to the content’s frame rate without needing to change display modes. This ensures a smoother user experience by adapting the screen refresh rate on the fly, whether you’re watching a video or playing a game.

Benefits of True Variable Refresh Rate in Android 15

Google highlights two main benefits of the ARR feature in Android 15:

  1. Power Efficiency: By allowing the display to operate at lower refresh rates when high refresh rates aren’t necessary, the device consumes less power. It ramps up the refresh rate only when the content requires it, reducing unnecessary battery drain.
  2. Improved Performance: Since ARR eliminates the need to switch between different display modes, it reduces potential “jank” or stuttering issues that occur during mode transitions, offering a smoother visual experience.

Why Wasn’t True VRR Supported Before?

Although smartphone manufacturers have promoted variable refresh rate features with LTPO displays, these implementations were limited. LTPO displays allowed for a broader range of refresh rates, from as low as 1Hz or 10Hz up to 120Hz. However, this was achieved by toggling between fixed display modes rather than dynamically adjusting within a single mode.

For example, on many Android devices with LTPO OLED panels, the refresh rate could drop to 10Hz during static content like reading, then jump to 120Hz during gaming. However, these changes were still tied to pre-defined modes and didn’t dynamically adapt based on real-time content needs, unlike true VRR seen in PC gaming monitors.

Technical Advancements in Android 15

In previous Android versions, some OEMs tried to implement VRR-like features at the kernel level. However, this approach required custom logic for each device, making it difficult to standardize due to Android’s Generic Kernel Image (GKI) requirements. The kernel, responsible for managing hardware, lacked deep insights into the content being displayed, limiting its ability to adjust the refresh rate effectively.

Android 15 addresses this by implementing VRR at the Hardware Composer (HWC) HAL (Hardware Abstraction Layer) level, specifically with the introduction of version 3 of HWC HAL APIs. This allows the operating system to make more informed decisions about when to adjust the refresh rate based on the content displayed. It offers a unified method for OEMs to implement adaptive refresh rates without needing complex customizations at the kernel level.

Device Compatibility and Challenges

While Android 15 introduces true VRR support, not all devices will be able to use it right away. For a phone to take advantage of this feature, it must have support for the updated HWC HAL version 3. Currently, devices like the Google Pixel 7 and newer models, as well as those powered by the Qualcomm Snapdragon 8 Elite chip, have this version. However, older devices, including the Google Pixel 6 series and phones using the Qualcomm Snapdragon 8 Gen 3, do not support the necessary HAL version.

Additionally, even if a device receives an update to Android 15, it may not support ARR due to hardware limitations or the effects of Google’s Requirements Freeze (GRF) program. This program prevents mandatory hardware changes in updated devices, so phones designed before the release of HWC HAL version 3 may not fully support Android 15’s adaptive refresh rate features.

Future Impact and Expectations

If Android 15’s adaptive refresh rate feature is widely adopted, it could lead to better performance and battery efficiency in everyday use. For instance, it may help devices reduce the refresh rate to 30Hz or 24Hz when playing films, rather than defaulting to 60Hz, which could conserve battery life.

However, it’s important to note that Android 15’s implementation is not the same as the true VRR seen in gaming PCs, where the refresh rate matches the frame rate of the game. Instead, Google’s documentation indicates that the adaptive refresh rate in Android 15 only supports rates that are divisors of the display’s native refresh rate to prevent tearing effects.

This means that while Android 15’s ARR feature offers significant improvements, it may not provide full synchronization between game frame rates and display refresh rates, as seen in PC monitors with NVIDIA G-Sync or AMD FreeSync.

Looking Forward

As more details emerge and updates roll out, it will be interesting to see which existing devices fully adopt Android 15’s adaptive refresh rate capabilities. Google’s future Pixel devices are likely candidates for early adoption, but broader support will depend on how quickly OEMs implement the necessary hardware and software changes.

In conclusion, Android 15 marks a significant step forward in providing true VRR support at the operating system level. While the feature is promising, its real-world impact will depend on device compatibility and OEM adoption. Users can look forward to a smoother experience and potentially better battery life, making it a long-overdue but welcome addition to the Android ecosystem.

Continue Reading

Google

Expanded support for RAW Photos in third-party Android camera apps

Published

on

Google

Google is making strides to enhance the quality of smartphone photography by bringing RAW photo support to more third-party camera apps through an update to the CameraX library. While the default JPEG photos from smartphones are sufficient for casual use, photography enthusiasts often prefer RAW images due to their superior editing capabilities.

Understanding RAW Photography

RAW photography captures unprocessed image data directly from the camera sensor. Unlike JPEG, which compresses and processes the image, RAW files retain more details, allowing photographers to adjust settings like white balance, exposure, and sharpness in post-processing. However, RAW files are significantly larger, consuming more storage space, which can be a concern for users with budget devices.

Current Limitations in Android Apps

Many camera apps on Android either do not support RAW photography or require manual activation due to its limited utility for most users. This gap exists because many developers opt to use the simpler CameraX library instead of the more complex Camera2 API. While Camera2 has supported RAW capture for a long time, CameraX, designed for ease of use and broader device compatibility, initially only supported JPEG output.

CameraX simplifies the integration of camera features into apps like social media platforms that do not need advanced camera functionalities. The trade-off has been the lack of advanced options like RAW photo capture. However, Google is addressing this by adding RAW capture capabilities in the upcoming release of CameraX version 1.5.0.

Upcoming Features in CameraX 1.5.0

With the 1.5.0 update, CameraX will introduce two new output formats: OUTPUT_FORMAT_RAW for capturing a single RAW image and OUTPUT_FORMAT_RAW_JPEG for capturing both RAW and JPEG images simultaneously. These RAW images will be saved in Adobe’s DNG format, a widely adopted standard in digital photography. This addition aims to bridge the feature gap between CameraX and Camera2, making RAW photo support more accessible to a broader range of apps​.

Implications for Developers and Users

This update will empower app developers who use CameraX to provide users with more advanced photography options without resorting to the more complex Camera2 API. It also reflects Google’s commitment to enhancing CameraX, making it a viable choice even for apps with more demanding camera requirements. As a result, more third-party camera apps may soon start offering RAW capture, appealing to users who prefer extensive photo editing and better image quality.

Conclusion

Google’s efforts to add RAW photo support to CameraX demonstrate an ongoing push to offer professional-grade features in a simpler package. This move is expected to make high-quality, detailed photography accessible even in apps that were previously limited to basic JPEG captures, enriching the overall Android photography experience for both developers and users.

Continue Reading

Google

Google Search’s Paddington Easter Egg and new Google Slides templates boost productivity

Published

on

Google

In anticipation of the upcoming movie Paddington in Peru, Google has added a playful Easter egg to its search engine. When users type “Paddington,” “Paddington 2,” or “Paddington in Peru” into Google Search, they notice a special marmalade sandwich button at the bottom right of the screen. Clicking this button results in the screen being “coated” with marmalade, mimicking Paddington’s love for his favorite snack. Each click adds more sticky sandwiches, creating a fun and interactive experience, especially for fans of the beloved bear​.

This Easter egg aligns well with the promotional activities for Paddington in Peru, which releases in November 2024 in the UK and January 2025 in the US. The film follows Paddington on a journey back to Peru, accompanied by the Brown family, as they explore his native land in a new adventure filled with mystery and charm​.

Enhancements in Google Slides: New Themed Templates

Google has also made updates to its Slides platform by introducing a variety of themed templates. This new feature is aimed at enhancing user productivity by simplifying the presentation creation process. Traditionally, users relied on basic themes and layouts, but now Google Slides offers pre-designed templates tailored for specific purposes like business pitches, educational projects, and collaborative team activities.

These templates include layouts, color schemes, and placeholder content, making it easier for users to jump straight into creating visually appealing and professional presentations. Some of the available templates are tailored for investor pitches, class overviews, and even team-building games. This update is rolling out to all Google Workspace customers, including individual subscribers and those with personal Google accounts, promising more templates in future updates​.

In summary, Google is boosting user engagement and productivity through these delightful additions. The Easter egg celebrates a cultural icon, while the new Slides templates help streamline the presentation process for both professional and personal use.

Continue Reading

Trending

Copyright © 2024 I AM Judge