XDA

jeudi 12 mars 2020

[Update 4: Realme UI beta recruitment for Realme X2 Pro] Realme announces its Android 10 update roadmap for the Realme X series

Update 4 (03/12/20 @ 03:13 AM EST): Realme X2 Pro users can now apply for Realme UI beta testing.

Update 3 (01/20/20 @ 00:55 AM EST): Realme X2 users in India can now apply for Realme UI beta starting today until January 27th, 2020. Meanwhile, the beta for Realme X2 Pro has already begun while stable updates for the Realme 3 Pro and XT have started to roll out.

Update 2 (11/27/19 @ 02:15 AM EST): Realme X2 Pro users can now apply to be a part of the ColorOS 7 beta in India starting today until December 3, 2019.

Update 1 (11/25/19 @ 03:15 AM EST): Realme announces ColorOS 7 update release roadmap for Indian devices, including a beta for Realme 3 Pro, Realme XT, and the Realme X2 Pro starting December 18, 2019.

The table below has been updated with a month-wise roll-out schedule for India and China. The remaining parts of the original article from October 30, 2019, remain unchanged.

Realme is treading with a fast pace, especially when it comes to launching new devices. Earlier this month, they launched their first true flagship, the Realme X2 Pro, with Snapdragon 855+, 50W SuperVOOC charging, 64MP quad cameras, and so many other exciting features. At the same event in Madrid, Spain, the company also launched the Realme X2, which is the Realme XT but with faster 30W charging and a Snapdragon 730G for better performance, and the Realme Q (Realme 5 Pro in India). But one aspect of Realme phones that has left user expectations sore is the software and the company is now working to bring the experience closer to stock Android with ColorOS 7.

In the meantime, Realme is also working on making Android 10 available to the users and had earlier announced its timeline for the update for several older devices. They have now announced the Android 10 roll-out schedule for newer devices including the Realme X2 Pro and the Realme X2. As per the update, Realme X2 Pro will start receiving the Color OS 7 update based on Android 10 in the second quarter of 2020.

Realme X2 Pro XDA Forums || Realme X2 XDA Forums || Realme XT XDA Forums || Realme 5 Pro/Q XDA Forums || Realme X XDA Forums || Realme 3 Pro/X Lite XDA Forums

Notably, the schedule for the roll-out is for Chinese variants of the smartphones so we expect the global roll-out to come in the weeks following the initial updates. Realme should reveal dates for the Indian variants while launching the phone next month.

Source: Realme Community (Chinese) | Via: MySmartPrice

Update 1: Realme’s ColorOS 7 & Android 10 update schedules for Realme 3 Pro, XT, X2 Pro, others

Realme has updated the ColorOS 7 update schedule for India with a month-wise breakdown. In India, Realme will release a custom UI based on ColorOS 7 based on Android 10. This echoes their promise of bringing a UI closer to stock Android but we’re not sure of the exact changes yet. OPPO is set to announce ColorOS 6 in India on November 26, 2019, which is when we might get to learn more about this customized UI.

Delighted to share that we have created realme's own customised UI based on ColorOS 7 & Android 10 for better RAM management, closer to stock Android experience and smoother gaming experience. Here is the update roadmap, mark your calendar.
Know more: https://t.co/kYP3CJegYt pic.twitter.com/mUasb42jki

— realme (@realmemobiles) November 25, 2019

ColorOS 7 beta will also be released in India and China for certain devices starting December 18, 2019. Realme notes that users who’ve signed up for ColorOS 6.7 beta on Realme XT and Project X for Realme 3 Pro will also be eligible for the ColorOS 7 beta update but the toll out may take as long as Feb 2020. Beta registrations for Realme X2 Pro beta will begin on November 27 in India while the registration link will go live after the company concludes a poll on which devices besides the X2 Pro must get the beta update.

The table below notes the roll-out schedule for ColorOS 7 based on Android 10 for China and India. No announcement has been made by the European team for the update in the region.

Smartphone	China	India
Realme 2 Pro	Not available in the region	Jun 2020
Realme 3	Not available in the region	Apr 2020
Realme 3 Pro/Realme X Lite	Feb 2020	Jan 2020 (roll-out to existing beta users soon)
Realme X	Q1 2020	Feb 2020
Realme 3i	Not available in the region	Apr 2020
Realme 5 / 5s	Not available in the region	May 2020
Realme 5 Pro/Realme Q	Mar 2020	Feb 2020
Realme XT	Not available in the region	Jan 2020 (roll-out to existing beta users soon)
Realme X2	Apr 2020	Mar 2020
Realme X2 Pro	Apr 2020 (beta starting 12/18/19)	Mar 2020 (beta starting 12/18/19)
Realme C2	Not available in the region	Q3 2020

Sources: Realme Community India (1)(2) | Realme Community China | Weibo

Update 2: Realme begins recruiting beta testers for ColorOS 7 beta

Realme has started opened applications for testers for the Realme X2 Pro’s ColorOS 7 beta update. Interested users can show their interest by filling up this form before December 3rd. The selected beta testers will be announced on December 9th.

The company recently announced the ColorOS 7 update schedule for the European users.

Source: Realme Community

Update 3: Realme seeks beta testers for Realme UI beta on Realme X2

Realme rolled out its new Android interface – Realme UI – to the Realme 3 Pro and the Realme XT in the last few days. Now, the company is looking to recruit beta testers for Realme UI beta on its latest smartphone – Realme X2. You can apply for the beta by filling up your details on this page on or before January 27th.

Source: Realme Community

Update 4: Realme UI beta testing open for the Realme X2 Pro

Realme is now looking for beta testers who are interested in trying out the RealmeUI on the Realme X2 Pro. If you are interested, you can follow the instructions mentioned in this post.

Source: Realme Community

The post [Update 4: Realme UI beta recruitment for Realme X2 Pro] Realme announces its Android 10 update roadmap for the Realme X series appeared first on xda-developers.

from xda-developers https://ift.tt/368lgtE
via IFTTT

[Update 4: Realme UI beta recruitment for Realme X2 Pro] Realme announces its Android 10 update roadmap for the Realme X series

Update 4 (03/12/20 @ 03:13 AM EST): Realme X2 Pro users can now apply for Realme UI beta testing.

Update 2 (11/27/19 @ 02:15 AM EST): Realme X2 Pro users can now apply to be a part of the ColorOS 7 beta in India starting today until December 3, 2019.

The table below has been updated with a month-wise roll-out schedule for India and China. The remaining parts of the original article from October 30, 2019, remain unchanged.

Realme X2 Pro XDA Forums || Realme X2 XDA Forums || Realme XT XDA Forums || Realme 5 Pro/Q XDA Forums || Realme X XDA Forums || Realme 3 Pro/X Lite XDA Forums

Source: Realme Community (Chinese) | Via: MySmartPrice

Update 1: Realme’s ColorOS 7 & Android 10 update schedules for Realme 3 Pro, XT, X2 Pro, others

Delighted to share that we have created realme's own customised UI based on ColorOS 7 & Android 10 for better RAM management, closer to stock Android experience and smoother gaming experience. Here is the update roadmap, mark your calendar.
Know more: https://t.co/kYP3CJegYt pic.twitter.com/mUasb42jki

— realme (@realmemobiles) November 25, 2019

The table below notes the roll-out schedule for ColorOS 7 based on Android 10 for China and India. No announcement has been made by the European team for the update in the region.

Smartphone	China	India
Realme 2 Pro	Not available in the region	Jun 2020
Realme 3	Not available in the region	Apr 2020
Realme 3 Pro/Realme X Lite	Feb 2020	Jan 2020 (roll-out to existing beta users soon)
Realme X	Q1 2020	Feb 2020
Realme 3i	Not available in the region	Apr 2020
Realme 5 / 5s	Not available in the region	May 2020
Realme 5 Pro/Realme Q	Mar 2020	Feb 2020
Realme XT	Not available in the region	Jan 2020 (roll-out to existing beta users soon)
Realme X2	Apr 2020	Mar 2020
Realme X2 Pro	Apr 2020 (beta starting 12/18/19)	Mar 2020 (beta starting 12/18/19)
Realme C2	Not available in the region	Q3 2020

Sources: Realme Community India (1)(2) | Realme Community China | Weibo

Update 2: Realme begins recruiting beta testers for ColorOS 7 beta

The company recently announced the ColorOS 7 update schedule for the European users.

Source: Realme Community

Update 3: Realme seeks beta testers for Realme UI beta on Realme X2

Source: Realme Community

Update 4: Realme UI beta testing open for the Realme X2 Pro

Realme is now looking for beta testers who are interested in trying out the RealmeUI on the Realme X2 Pro. If you are interested, you can follow the instructions mentioned in this post.

Source: Realme Community

The post [Update 4: Realme UI beta recruitment for Realme X2 Pro] Realme announces its Android 10 update roadmap for the Realme X series appeared first on xda-developers.

from xda-developers https://ift.tt/368lgtE
via IFTTT

OPPO’s 30W Wireless VOOC charging is ready to launch commercially

All the way back in January last year, Chinese smartphone manufacturer OPPO joined the Wireless Power Consortium. This led many people to believe that OPPO would soon launch a smartphone with wireless charging support, however, that didn’t end up happening. Although the company didn’t launch any device with wireless charging support, it did showcase its 30W Wireless VOOC Flash Charge technology later in the year and claimed that the technology used “real-time adjustment of the charging process and efficient charging components to ensure a more efficient and safer charging while avoiding overheating.” Furthermore, in order to “enhance safety” OPPO also adopted several hardware designs to avoid overheating, HVDC and a foreign object detection function to ensure that charging stopped immediately if the charging board detected a foreign metal object.

OPPO’s 30W Wireless VOOC Flash Charge has since only been implemented in the company’s prototype smartphone that features an under-display camera. We expected the brand to include the technology in the recently launched OPPO Find X2 series, but the company decided to skip that as well. When our Editor-in-Chief, Mishaal Rahman, asked the company about this, Edward Tian, Charging Engineer at OPPO revealed that the company had completed R&D for the 30W wireless charging technology and that it’s technically ready for launch. He further added that the technology can co-exist with the 65W SuperVOOC 2.0 charging on the Find X2, so there’s no technical limitation preventing the company to add the technology to the Find X2 series. Sadly though, OPPO didn’t exactly reveal why the technology wasn’t included in the Find X2 series, beyond the argument that it really isn’t necessary when the phone already charges so fast with its 65W SuperVOOC 2.0 tech.

Even though OPPO hasn’t included its 30W Wireless VOOC Flash Charge technology on any of its devices, we might soon see it in the upcoming OnePlus 8. For the unaware, OnePlus is a brand under BBK Electronics, just like OPPO, and OnePlus’ Dash/Warp Charge technology is derived from OPPO’s VOOC. Up until now, OnePlus hasn’t included wireless charging support on any of its devices as the company has long argued that wireless charging isn’t fast enough for their liking. But at 30W, the new wireless charging tech is just as fast as OnePlus’ Warp Charge 30. Interestingly, OnePlus recently joined the Wireless Power Consortium and there are credible rumors that suggest that OnePlus 8 will support wireless charging. This leads us to believe that we might see a rebranded version of OPPO’s 30W Wireless Flash Charge tech in the upcoming OnePlus 8.

The post OPPO’s 30W Wireless VOOC charging is ready to launch commercially appeared first on xda-developers.

from xda-developers https://ift.tt/2W7Vggu
via IFTTT

OPPO’s 30W Wireless VOOC charging is ready to launch commercially

The post OPPO’s 30W Wireless VOOC charging is ready to launch commercially appeared first on xda-developers.

from xda-developers https://ift.tt/2W7Vggu
via IFTTT

mercredi 11 mars 2020

Samsung will bring One UI 2.1 to the Galaxy Note 10, S10, Note 9, and S9

Samsung launched its flagship S20 series early last month, offering some impressive hardware specifications. These included the 100x Space Zoom camera on the S20 Ultra, the 108MP primary shooter with Nona Binning, and up to 16GB of LPDDR5 RAM. On the software front, the devices rolled out with One UI 2.1 based on Android 10 that included a couple of additional features like Spotify support in the Clock app. Other than the Galaxy S20 series, the Galaxy Z Flip is the only Samsung smartphone that runs One UI 2.1 right now. However, according to a recent report from Sammobile, the company will soon roll out One UI 2.1 to the Galaxy Note 10, S10, Note 9, and S9.

Samsung One UI 2.1 update Galaxy S10, Note 10, S9, Note 9

The report cites a post from a Samsung community moderator on Samsung’s Korean community portal which confirms that Samsung has planned to roll out One UI 2.1 not only for last year’s Galaxy S10 and Note 10 series but also for the Galaxy S9 and Note 9 series. As of now, Samsung has not revealed a timeline for the One UI 2.1 rollout, but it’s safe to assume that the Galaxy S10 and Note 10 device will get the update before the Galaxy S9 and Note 9 devices. In terms of software features, One UI 2.1 brings relatively fewer features, including Screen Zoom, Samsung Quick Share and the aforementioned Spotify support in the Clock app. It’s also worth noting that hardware-related features like the option to switch to 120Hz refresh rate won’t be making it to older devices even after the update due to obvious lack of hardware support.

Source: Samsung Community

Via: Sammobile

The post Samsung will bring One UI 2.1 to the Galaxy Note 10, S10, Note 9, and S9 appeared first on xda-developers.

from xda-developers https://ift.tt/2TIzSwN
via IFTTT

Samsung will bring One UI 2.1 to the Galaxy Note 10, S10, Note 9, and S9

Samsung One UI 2.1 update Galaxy S10, Note 10, S9, Note 9

Source: Samsung Community

Via: Sammobile

The post Samsung will bring One UI 2.1 to the Galaxy Note 10, S10, Note 9, and S9 appeared first on xda-developers.

from xda-developers https://ift.tt/2TIzSwN
via IFTTT

Magisk may no longer be able to hide bootloader unlocking from apps

XDA Recognized Developer topjohnwu‘s “Magisk” project has essentially become synonymous with “root” in the Android community. One of the main reasons it’s so popular is because it can hide the fact that the user has modified their device. However, Google may be cracking down on the ability of Magisk to hide the bootloader unlock status from applications.

In order to root your phone, you usually need to unlock the bootloader, which allows you to flash modified boot images. This is needed because Magisk modifies the boot image to spoof bootloader status and/or the Verified Boot status checks. Google’s SafetyNet Attestation API, which is part of Google Play Services, is used to tell an app if it’s running on a tampered device; if the SafetyNet API detects that the bootloader has been unlocked, then it will return a failure status for the “Basic Integrity” check. Devices that fail this check can then be locked out from apps that use the SafetyNet API to determine the device integrity; such apps typically include banking apps, payment apps (like Google Pay), and many online games (like Pokémon Go). However, because the SafetyNet API has thus far only used software checks to determine if the device has been tampered with, Magisk can simply spoof the bootloader and/or Verified Boot status since it is installed at a lower level and with higher privileges than Google Play Services and other userspace applications. As topjohnwu explains, MagiskHide “[creates] an isolated ‘safe environment’ for the detection process, and it goes through Google’s API to create a legit SafetyNet result that does not reflect the real status of the device.”

Recently, though, users have noticed that their bootloader-unlocked devices are failing SafetyNet’s Basic Integrity check even though they used Magisk to patch the boot image. According to topjohnwu, this is because Google may have implemented hardware-level key attestation to verify that the boot image has not been tampered with. Specifically, this means Google Play Services “[sends] an unmodified keystore certificate to SafetyNet servers, verify its legitimacy, and check certificate extension data to know whether your device [has] verified boot enabled (bootloader status).” This means that it may no longer be possible to hide the fact that the bootloader has been unlocked, which will result in applications like Google Pay and Pokémon Go failing to operate normally.

So here we go, after years of fun messing around using Magisk, it seems that Google FINALLY decided to “fix” SafetyNet to something useful, and that is to use key attestation to verify device status (after 3 years since introduced to Android’s platform!)

— John Wu (@topjohnwu) March 11, 2020

As topjohnwu noted, this change to the way that SafetyNet checks the bootloader unlock status comes through a server-side update to the SafetyNet API contained in Google Play Services. However, not every user is failing these updated SafetyNet checks, so the new hardware-level key attestation may not be widely enforced yet.

We’ve seen topjohnwu overcome technical hurdles time and time again. Google frequently rolls out new checks in SafetyNet that topjohnwu then discovers and bypasses in Magisk. Each new version of Android brings changes to the partition structure or boot image, requiring topjohnwu to study the changes and then implement a new patching method. However, even topjohnwu may struggle to find a bypass this time around.

That’s because the workaround this time would involve hacking the Trusted Execution Environment (TEE) firmware of devices in order to retrieve the private key. However, this is incredibly difficult to do as it requires finding a vulnerability in firmware that is designed to be incredibly secure. In fact, many companies offer payments in the hundreds of thousands of dollars if such a vulnerability were to be found. Google, for instance, pays $250,000 for remote code execution vulnerabilities in the Pixel’s Trusted Execution Environment, and up to $1,000,000 for vulnerabilities in the Titan M security chip. Even if a private key were somehow to be leaked, it’s unlikely that it would be of much use since Google can remotely revoke the key so it can’t be used to verify the integrity of devices.

Yes, we will revoke them. If the keys are leaked, we’ll revoke them. If the firmware has an unrecoverable flaw, we’ll revoke them. If the firmware has a flaw that can be fixed via OTA, we’ll analyze the situation to decide if that is adequate.

— Shawn Willden (@shawnwillden) March 11, 2020

Once hardware-level key attestation is widely enforced for SafetyNet, most devices with unlocked bootloaders running Android 8.0 Oreo or higher will fail to pass SafetyNet’s Basic Integrity check. This is because all devices that launched with Android 8.0 Oreo or higher are required to have a hardware keystore implemented in a TEE. Certain devices nowadays even have dedicated hardware security modules (HSMs) that make exploitation even more difficult by moving the TEE away from the main processor; the Titan M in the Pixel 4 and Samsung’s new security chip in the Galaxy S20 are examples of this.

Topjohnwu also explains that other potential workarounds are either impossible or highly challenging. Using the Xposed Framework to modify the SafetyNet Attestation API in Google Play Services likely won’t work since “proper SafetyNet checks will verify results on a remote server, not on [the] device which can be manipulated by code injection frameworks.” Furthermore, Google Play Services is highly obfuscated, making the creation of such an Xposed Module incredibly challenging in the first place. Spoofing a SafetyNet test result won’t be doable either since the SafetyNet responses “come from Google servers and are signed with Google’s private key.”

Google has had the ability to harden SafetyNet checks using hardware-backed key attestation for several years now. The fact that they refrained to do so for 3 years has allowed users to enjoy root and Magisk Modules without sacrificing the ability to use banking apps. However, it seems that Magisk’s ability to effectively hide the bootloader unlock status is soon coming to an end. It’s a change that we’ve expected for years, but we’re sad to see it finally go into effect. We hope that Google updates the SafetyNet Attestation API to return whether the status check used hardware-based attestation as this would allow app developers to decide if they want to block all users who have unlocked the bootloader.

Thanks to Daniel Micay (@DanielMicay) for his input regarding this matter!

The post Magisk may no longer be able to hide bootloader unlocking from apps appeared first on xda-developers.

from xda-developers https://ift.tt/2QnrkJN
via IFTTT