LightBlog

jeudi 23 juillet 2020

OxygenOS 10.5.2 for the OnePlus Nord adds OnePlus Buds support

Just a day after OnePlus hosted its AR launch event and unveiled the highly anticipated OnePlus Nord and OnePlus Buds, the company has started rolling out the second software update for its new mid-ranger. The update, OxygenOS v10.5.2, measures 143MB in size and brings official support for the OnePlus Buds to the device, Android security patches for July 2020, minor improvements for the camera, and more.

OnePlus Nord XDA Forums

Here’s the complete changelog for OxygenOS 10.5.2 for the OnePlus Nord:

  • System
    • Newly adapted OnePlus Buds firmware, easier to take advantage of wireless connection
    • Newly adapted Dailyhunt with 90Hz refresh rate (IN only)
    • Optimized the process of starting camera with gestures
    • Optimized video calling performance
    • Improved system stability and fixed general issues
    • Updated Android security patch to 2020.07
  • Camera
    • Optimized power efficiency for front camera video shooting at 4K 60fps
    • Improved camera experience and system stability

Just like all previous OxygenOS updates, the latest OTA for the OnePlus Nord is only being rolled out to a small percentage of users today. Once the company confirms that there aren’t any bugs in the release, the update should roll out to more users. As mentioned earlier, this is the second software update for the OnePlus Nord since its launch. The first update, OxygenOS v10.5.1, included optimizations for the video calling performance and a few camera improvements.

OnePlus Nord OxygenOS 10.5.2

 

We currently don’t have access to download links for the latest OxygenOS OTA update for the OnePlus Nord. We will update the post as soon as the download links are available. It’s also worth noting that since the OnePlus Nord hasn’t gone on sale in India, buyers should receive both the OTA updates right after they set up their new device. The OnePlus Nord goes on open sale in India on August 4th via OnePlus’s website and Amazon.in.


Source: OnePlus Forums

The post OxygenOS 10.5.2 for the OnePlus Nord adds OnePlus Buds support appeared first on xda-developers.



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

[Update: Rolling out] Google Translate 6.5 tests Android 10 dark mode support and continues work on Transcribe mode

Update 1 (07/24/2020 @ 01:45 AM ET): A new Dark Mode design is now rolling out to Google Translate. Scroll to the bottom for more information. The article as published on February 6, 2020, is preserved below.

A system-wide dark mode has arguably been one of the most requested features on Android for quite some time. Google finally delivered with the first stable rollout of Android 10 late last year, pushing a new darker theme for the operating system. The company also rolled out individual dark mode toggles for many of its apps, including Google Keep, Files, Photos, Duo and more. However, the dark mode hasn’t made it to all of Google’s Android apps yet. For instance, the Google Translate app still doesn’t have a dark theme. But the latest update for the app reveals that the company has finally started testing dark mode support for the app.

Our Editor-in-Chief, Mishaal Rahman, managed to manually enable the dark theme in version 6.5 of the Google Translate app on his Pixel 4. As you can see in the attached screenshots, turning on the dark mode switches the white elements in the app’s UI to a dark gray color without changing the color of the elements in blue.

Google Translate Google Translate Google Translate Google Translate

The dark gray color spans across the app’s home page, phrasebook, and language selection menu, but the app’s Settings menu has a black background. As of now, the feature isn’t enabled in version 6.5 of the Google Translate app and our Managing Editor, Joe Fedewa, didn’t see a similar dark theme on his Pixel upon sideloading the latest update.

Google Translate Google Translate Google Translate

Along with the dark mode, the app also continues work on the Transcribe Mode which was first spotted back in December last year. The feature essentially allows you to translate uninterrupted speed in Google Translate to facilitate a conversation between users who don’t speak the same language. Google officially showed off the feature late last month at its AI Press Day event. The feature now appears as an icon labeled Transcribe right next to the Camera and Conversation icons in the app. The rest of the UI remains the same as what we spotted last year.


Update: Google Translate’s Dark Mode is now rolling out

Google Translate’s Dark Mode is now rolling out to some users, presumably under a wider rollout plan.

The theme that is now rolling out looks much better than the one spotted earlier in the year. These screenshots are from the ASUS ROG Phone 3 running Android 10 with Google Translate version 6.10.0.05.

Story Via: AndroidPolice

The post [Update: Rolling out] Google Translate 6.5 tests Android 10 dark mode support and continues work on Transcribe mode appeared first on xda-developers.



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

The OPPO Watch will soon launch globally with Google’s Wear OS

OPPO entered the smartwatch segment earlier this year in March with the launch of the OPPO Watch. The Apple Watch lookalike was powered by the Snapdragon Wear 2500 SoC and ran OPPO’s proprietary ColorOS Watch software. Now, according to a recent report from Android Authority, the company is finally gearing up to launch the OPPO Watch internationally with Google’s Wear OS on board.

The company has shared a short teaser of the upcoming smartwatch, which gives us a brief glimpse of the design and confirms that it will feature Wear OS instead of OPPO’s proprietary software. The company has also revealed that the watch will be officially unveiled later this month on July 31st. While OPPO hasn’t released any details about the smartwatch’s hardware, an FCC listing of the OPPO Watch reveals that it will feature a 1.9-inch AMOLED display within a 46mm chassis, an optical heart rate sensor, and 5ATM water resistance.

The FCC listing doesn’t shed light on the SoC powering the smartwatch, but it does confirm that it will feature 1GB of RAM, 8GB of onboard storage, and eSIM support. The listing also reveals that the OPPO Watch will include a 430mAh battery. It’s worth noting that the Chinese version of the smartwatch is rated for approximately 40 hours of regular use on a single charge and 21 days in power-saving mode. However, since Wear OS is known to be a power-hungry OS, we suspect that the battery life for the international version won’t be as impressive.

The OPPO Watch was launched in China with a price tag of 1,499 yuan (~$215), but we expect the international variant to be a bit pricier considering the fact that it runs Wear OS instead of OPPO’s software.


Via: Android Authority

Featured image: Chinese variant of the OPPO Watch

The post The OPPO Watch will soon launch globally with Google’s Wear OS appeared first on xda-developers.



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

T-Mobile will require VoLTE for all phones starting January 2021, AT&T to follow suit in February 2022 – Here’s what that means for you

The constant evolution of network technology is exciting to follow but only if you have the means to stay up-to-date with new advancements. In our industry, that means buying new smartphones, routers, and plans from carriers. Furthermore, you have to make sure that whatever you purchase is actually compatible with the network you’re paying for. This week has reminded us once again of the importance of network compatibility, as we’re reminded that both AT&T and T-Mobile will eventually shut down their 3G networks. This shouldn’t come as a surprise since both carriers are in the process of rolling out their 5G networks, but it’s important to note because of the complicated nature of VoLTE on Android.

If you’re unfamiliar with VoLTE, it stands for “Voice over LTE” and it’s exactly what it sounds like. Phone calls are routed over a 4G LTE connection instead of 2G or 3G. A few years ago, this was seen as a big deal as the higher bandwidth of 4G LTE means that more data can be transmitted, resulting in reduced compression of voice data and thus better call quality for both parties. VoLTE is pretty standard nowadays, with pretty much all of the major carriers having implemented it and all devices with cellular modems supporting the technology. In fact, T-Mobile’s Q1 2020 earnings report states that “VoLTE comprised 91% of total voice calls” on the network. Many carriers have already shut down their legacy 2G networks because the vast majority of customers have upgraded to devices compatible with newer network technologies, and the carriers are gearing up to shut down their 3G networks, too.

Earlier today, AndroidPolice published a screenshot of an internal T-Mobile notice that reveals that the carrier will require VoLTE for all devices connecting to its 4G LTE and 5G networks. The publication also reported on emails that were sent to customers of AT&T informing them that their phones will eventually become incompatible with the carrier’s network. Here’s what you need to know about the upcoming shutdown of T-Mobile and AT&T’s 3G voice networks.

T-Mobile’s VoLTE Requirement – Coming Soon

T-Mobile’s VoLTE Device Compatibility Requirements. Source: T-Mobile. Via: AndroidPolice.

Starting August 4th, 2020, T-Mobile will stop activating new devices that do not support VoLTE on its network. T-Mobile says that all devices in its current lineup (meaning, devices sold through them) support VoLTE.

Starting January 2021, any device that does not support VoLTE on T-Mobile will no longer be able to connect to the carrier’s 4G LTE or 5G network. Existing T-Mobile and Metro by T-Mobile (formerly known as MetroPCS) customers who activate a non-VoLTE-compatible device before August 4th will be informed via a text message that their device will become incompatible with the network starting January 2021.

Although it hasn’t been confirmed yet, it’s possible that some devices purchased via Sprint will be affected by this change. Sprint has always required certification for devices to connect to its network, and that certification has included VoLTE compatibility. However, T-Mobile is in the process of refarming Sprint’s network to expand its own 5G network, so it’s possible that some Sprint devices won’t be VoLTE compatible with the new T-Mobile network.  We also don’t know how this change will affect devices from the myriad of other MVNOs that use T-Mobile’s network, including Ting, Consumer Cellular, and Mint Mobile.

T-Mobile issued the following statement to AndroidPolice in regards to this notice:

We’re making great progress building a truly transformative nationwide 5G network. As part of that, we will be phasing out some older technologies over time to free up even more capacity for LTE and 5G. In preparation for that and to give customers the best experience, those activating new lines at T-Mobile will need a VoLTE capable device, which is all we’ve offered for years now and represents the overwhelming majority of devices on the network.

The carrier, however, declined to explicitly confirm the timeline of its 2G and 3G voice network shutdown.

AT&T’s 3G Shutdown – Coming February 2022

Earlier this week, AT&T (poorly) warned many customers that they should upgrade their smartphones soon as their devices will soon become incompatible with the carrier’s network. AT&T sent out emails to customers telling them their device “is not compatible with the new network and [they] need to replace it to continue receiving service.” The part that AT&T failed to explicitly mention to customers is that they won’t be affected by this change until February 2022. The email, as it was worded, clearly suggested that customers take urgent action to upgrade their device, even going as far as outlining steps to “easily” get a new device.

To its credit, AT&T is at least informing customers of its impending 3G network shutdown well ahead of T-Mobile, but they did so incredibly poorly. AT&T provided a statement to AndroidPolice to clarify that this email was the first of many it plans to send to customers to keep them informed of the impending shutdown of the carrier’s 3G network. Here’s the statement the carrier sent to the publication:

This email was one of many planned to keep customers informed about the shutdown of our 3G network in early 2022. It should have included the date that certain devices would no longer be supported. We apologize for any confusion this may have caused and will be more clear in future updates.

So AT&T, like T-Mobile, will require all devices connected to its network to support VoLTE. AT&T calls this “HD Voice,” and like T-Mobile, will block voice and data service for phones that don’t support it. AT&T, unlike T-Mobile, whitelists devices for VoLTE/HD Voice. That whitelist, available here, includes the Essential Phone, all Google Pixel phones since the Pixel 2, the LG G7 and V35, 9 Motorola devices, the OnePlus 7 Pro and 7T Pro, and all Samsung Galaxy flagships since the S8.

What this means for BYOD, unlocked devices, and custom ROMs

If you have purchased a recent smartphone directly from AT&T or T-Mobile, then you very likely have nothing to worry about here. However, if you’re using an unlocked device or a device on a custom ROM, then you’ll want to pay attention to what’s coming. Since AT&T whitelists devices for VoLTE compatibility, you won’t be able to BYOD to the carrier starting February 2022 unless the carrier changes its practices or whitelists a lot more devices. There’s no reason they can’t—VoLTE is a standard protocol, after all—but thus far they haven’t. There’s nothing you, the device maker, or a custom ROM developer/modder can do about it.

While T-Mobile, on the other hand, doesn’t use a whitelist for VoLTE compatibility, many unlocked devices just straight up don’t support it regardless. The recently announced ASUS ROG Phone 3 does not currently support VoLTE on the network, for example. It’s not that these phones can’t support VoLTE on T-Mobile, it’s just that the device maker hasn’t done the work to outright support it. Modders on our ROG Phone II forums have figured out the steps needed to enable VoLTE on T-Mobile, proving that a little more work at the factory could enable support.

Theoretically, as long as your Android device has a working IMS (IP Multimedia Subsystem) stack, it should support VoLTE on T-Mobile (but not AT&T because of its whitelist system.) Typical Android devices with Qualcomm modems ship with a privileged application that bridges the radio interface layer (RIL) and the IMS, which developers take bundle in their custom ROMs to enable VoLTE support. LineageOS, for example, requires maintainers to support VoLTE if the stock ROM supports it. If the stock ROM doesn’t support it, then it’s unlikely you’ll be able to use the device on AT&T or T-Mobile once they shut down their 3G networks.

One more thing we need to talk about is support for phones purchased overseas. It’s likely that if your phone has the right hardware (which nearly all do) and the right IMS configuration (a bit iffier) to support VoLTE on T-Mobile and AT&T, then you’ll be able to make VoLTE calls on both networks, provided your carrier back home has a roaming agreement.

How to check if your phone supports VoLTE

There’s a pretty easy way to check if your phone supports VoLTE on your current carrier. Simply install the “Network Mode Universal” app from the Google Play Store, turn on mobile data (and turn off Wi-Fi so you don’t accidentally trigger VoWiFi), and make a phone call to another number. If the “Voice Network Type” line shows “LTE,” then your phone call is being routed over LTE. Congrats, your phone supports VoLTE on your carrier! If you see anything other than LTE, like GSM, WCDMA, UMTS, or just 3G, then your phone does not support VoLTE on the network. In this case, talk to the customer support of your carrier for your next options.

Network Mode Universal (Free, Google Play) →

Thanks to AndroidPolice for bringing this app to our attention.

The post T-Mobile will require VoLTE for all phones starting January 2021, AT&T to follow suit in February 2022 – Here’s what that means for you appeared first on xda-developers.



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

AT&T’s sub-6GHz 5G network is now available across the U.S.

The major US carriers are duking it out to offer the best 5G networks, and AT&T is, of course, one of the main contenders. While their growing 5G network doesn’t boast the same throughput as Verizon’s Ultra Wideband mmWave 5G, AT&T’s sub-6GHz provides far better coverage. Today, the carrier announced they’ve reached a big milestone. The carrier’s sub-6GHz 5G network is now available nationwide.

Now, in the context of coverage, the FCC dictates that “nationwide” means more than 200 million people in the U.S. are blanketed in coverage. AT&T activated 40 new markets today, bringing the total number of covered people to 205 million (and 395 markets). So while not everyone in the country is truly covered, it’s enough for the company to say their 5G network is nationwide.

AT&T is still a bit behind T-Mobile’s 5G coverage both in terms of speed (especially after the latter’s acquisition of Sprint’s mid-band frequencies) and coverage. Both are a bit behind Verizon when it comes to speeds. AT&T and T-Mobile, however, are focusing on the mid- and low-band, while Verizon has the faster and more limited mmWave. Verizon currently doesn’t offer anything in the mid- to low-band spectrums, in contrast. Of course, all of this is somewhat of a moot point since the vast majority of people don’t have 5G-capable phones yet.

Check for AT&T 5G coverage in your area here.


Source: AT&T | Via: Engadget

The post AT&T’s sub-6GHz 5G network is now available across the U.S. appeared first on xda-developers.



from xda-developers https://ift.tt/3hzwJIN
via IFTTT

Motorola One Fusion+, Motorola Edge, and Moto G7 Power Android 10 kernel source code are now available

Motorola has a fantastic track record when it comes to publishing the kernel source code for the smartphones they sell. The Lenovo-owned brand also regularly refreshes its official GitHub repository with updated kernel source code packages corresponding to new Android software builds alongside the relevant commit history. The kernel sources of two recently launched Motorola phones, the Motorola One Fusion+ and the Motorola Edge, are now up for grabs. The company has also released the kernel source code for the Moto G7 Power’s Android 10 update.

Motorola One Fusion+

The Motorola One Fusion+ (code-name “liber”) packs in a Qualcomm Snapdragon 730G chip and a 6.5-inch Total Vision display with full HD+ resolution and HDR10 support. This mid-range Moto phone runs Android 10 out of the box, and it features a 64MP primary camera, a massive 5,000mAh battery, and a dedicated Google Assistant button. The latest software version for this phone is QPI30.73-16-5-2, while the initial version of the kernel source is based on a slightly older build (QPI30.73-16-5).

Motorola One Fusion+ Kernel Sources ||| Motorola One Fusion+ XDA Forums

Motorola Edge

Unlike the One Fusion+, the Motorola Edge is a 5G capable device, thanks to the Snapdragon 765 SoC. The kernel source code for the “Plus” variant of the Motorola Edge (code-name “burton”) was released about a month ago, and now we have the package ready for the regular model (code-name “racer”) as well.

Motorola Edge Kernel Sources ||| Motorola Edge XDA Forums

Moto G7 Power

Alongside these releases, Motorola has also published updated kernel sources for the Moto G7 Power (code-name “ocean”). The company originally released the Android Pie-based kernel source code for this phone back in February of 2019. The new release, on the other hand, corresponds to the Android 10 update for the Moto G7 Power that came out a few months ago.

Moto G7 Power Android 10 Kernel Sources ||| Moto G7 Power XDA Forums

The post Motorola One Fusion+, Motorola Edge, and Moto G7 Power Android 10 kernel source code are now available appeared first on xda-developers.



from xda-developers https://ift.tt/3hpVM0A
via IFTTT

“Red Velvet Cake” is Android 11’s internal dessert name

Last year, with the launch of Android 10, Google’s tradition of giving major Android releases a dessert nickname came to an end. Up until that point we had feasted on cupcakes, donuts, eclairs, froyo, gingerbread, honeycomb, ice cream sandwiches, jelly beans, KitKats, lollipops, marshmallows, Oreos, and Pie. But what dessert could have been used for Android 11? Red Velvet Cake.

Last year, Android’s vice-president of engineering, Dave Burke, revealed that their internal nickname for Android 10 was “Quince Tart.” While the dessert names stopped being used for public releases, Google was still internally using them. Dave Burke has once again revealed an internal dessert nickname. Google is referring too Android 11 as “RVC” or “Red Velvet Cake.”

Don’t get your hopes up and expect to see “Red Velvet Cake” in any public branding, though. Burke says they’ve officially moved to numbers only, but “RVC” and “Red Velvet Cake” have become the nickname for Android 11 among his team of engineers. A cake nickname would be perfect right now as the internet is obsessed with hyper-realistic cake memes. Missed opportunity.

Do you think “Red Velvet Cake” would have been a good nickname for Android 11?


Source: All About Android | Via: Android Authority

The post “Red Velvet Cake” is Android 11’s internal dessert name appeared first on xda-developers.



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