mardi 30 juin 2020

Qualcomm essentially confirms the OnePlus Nord has a 5G Snapdragon chipset

OnePlus recently confirmed that its upcoming affordable smartphone series, which was previously referred to as the OnePlus 8 Lite and later rumored to be the OnePlus Z, will be called OnePlus Nord. However, the company has still not released any official information about its specifications. While previous leaks about the device have given us a good look at its design and camera hardware, rumors about its internal specifications have been contradictory so far. At first, rumors suggested that the OnePlus Nord would be powered by the MediaTek Dimensity 1000 chipset. However, we later learned that it might feature Qualcomm’s Snapdragon 765 SoC. But now we can finally confirm that the OnePlus Nord will be powered by a 5G-enabled Qualcomm Snapdragon SoC.

According to a recent tweet from Qualcomm EU’s official Twitter handle, the upcoming OnePlus Nord will be powered by a “Snapdragon 5G chipset”. While the company hasn’t confirmed exactly which chipset will make an appearance on the OnePlus Nord it could be the Snapdragon 765G, if previous rumors are to be believed. We have already seen mention of the Qualcomm Snapdragon 765G in a survey from OnePlus which asked users whether they would be willing to purchase a smartphone from OnePlus with the processor, a 64MP triple camera setup, a 4,300mAh battery with 30W fast charging, and a 90Hz refresh rate display at ₹24,990. But we currently don’t have any confirmation if the upcoming device will offer these specifications. The OnePlus Nord is expected to launch in India and Europe on July 10th. OnePlus has confirmed that the device will be priced under $500.

The post Qualcomm essentially confirms the OnePlus Nord has a 5G Snapdragon chipset appeared first on xda-developers.



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

Motorola Razr and Realme 3/3i Android 10 kernel sources are now available

Measuring the developer-friendliness of a particular Android OEM is a difficult task. However, their stance on kernel source code release is undoubtedly an important parameter in this regard. Android device makers are obliged to provide the source code – at least upon request – for any Linux kernel binaries that ship on their devices to comply with the requirements of the GNU General Public License (GPL) v2. Not every company goes by the book, though, as a handful of them regularly publish source code for all the updates they roll out.

Motorola is one of the most notable names in this field, and the OEM has now updated their official GitHub repository with the kernel source code release for the Motorola Razr (code-name “olson”). We are talking about the recent incarnation of this iconic clamshell phone, which was launched with Android 9 Pie for some weird reason. Fortunately, the newly released kernel source corresponds to the Android 10 update that rolled out last month.

The release is tagged as QPV30.106-27, which is the build number of the Android 10 firmware running on the European Motorola Razr units. Note that the Verizon variant of the phone received a different build (QDV30.106-27) as its Android 10 update.

Motorola Razr Android 10 Kernel Sources ||| Motorola Razr XDA Forums

Apart from Motorola, Realme also has a good track record of releasing kernel sources in a timely manner. The Chinese smartphone brand has now refreshed its official GitHub repo with the unified Android 10 kernel source code for the Realme 3 and the Realme 3i. The phone duo received their Android 10-based Realme UI update back in April, which means Realme is slightly late to update the existing codebase this time around.

Realme 3 XDA Forums ||| Realme 3i XDA Forums

Realme 3/3i Android 10 Kernel Sources

The availability of these packages should help the aftermarket development community to build custom kernels and ROMs for the aforementioned devices.

The post Motorola Razr and Realme 3/3i Android 10 kernel sources are now available appeared first on xda-developers.



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

Samsung Galaxy A51 5G and LG Velvet are both headed to Verizon

Back in April, Samsung announced the availability of the Galaxy A51 5G for the U.S. market. The original Galaxy A51 was a vast improvement over the original Galaxy A50 and A50s with upgrades such as a more modern Infinity-O display, quad cameras, a different design language, and more. The Galaxy A51 5G took it even further by bundling in a hot 2020 feature: 5G support. Likewise, the LG Velvet was also announced recently with a mid-range Snapdragon 765G processor for 5G-enabled markets. As it turns out, both devices might be coming to Verizon soon.

At the time of its announcement, Samsung did not disclose when the Galaxy A51 5G will go on sale, what carriers it will be available on, or what processor it will use. But there’s mounting evidence that it might come soon under the Verizon banner and with a Qualcomm Snapdragon processor. The Wi-Fi Alliance has certified a Samsung phone with the model number SM-A516V, where SM-A516 is the Samsung Galaxy A51 5G and the V stands for Verizon. Likewise, the NFC Forum has certified the same model number, SM-A516V.

Another certification filing we’ve spotted reveals that the commercial name of SM-A516V is, indeed, “Galaxy A51 5G.” Since the name doesn’t mention “Galaxy A51 5G UW”, it’s possible the A51 won’t support mmWave 5G on Verizon’s Ultrawide Band 5G network (but rather Verizon’s upcoming sub-6GHz 5G network). However, this is merely speculation and there’s no concrete evidence one way or another. Next, multiple Geekbench listings for “SM-A516V” suggest that the device is running on Qualcomm’s lito platform, where “lito” is the code-name for the Snapdragon 765/765G. XDA’s Max Weinbach verifies that the build numbers submitted with these Geekbench filings are legitimate, though we can’t 100% confirm that the benchmark listing themselves are actually real.

What we can corroborate, though, is the fact that the Samsung Galaxy A51 5G is coming to Verizon and has a Qualcomm Snapdragon processor. We spotted a “samsung_a51xq” model being added to an internal Verizon listing, where “q” normally indicates a Qualcomm model. However, we can’t confirm if this is the Snapdragon 765/765G or not.

This internal Verizon listing also reveals a device code-named “caymanlm”, which is the code-name for the LG Velvet. This indicates that LG’s latest smartphone will also be coming to Verizon soon. Notably, another 5G Samsung device, the Galaxy A71 5G, is also coming to Verizon with the Snapdragon 765G, which seems to be the go-to choice for 5G mid-range phones this year. While the Snapdragon 690 was announced recently, no phone is using it just yet.

LG Velvet Forums ||| Samsung Galaxy A51 5G Forums

Featured image: Samsung Galaxy A51 5G

The post Samsung Galaxy A51 5G and LG Velvet are both headed to Verizon appeared first on xda-developers.



from xda-developers https://ift.tt/31sc0lj
via IFTTT

[Update: Windows app live] Amazon Prime Video finally gets a Windows app and may add live TV

Update (6/30/20 @ 11:25 AM ET): The Amazon Prime Video app for Windows is now live and users can sign in.

Streaming services are among the most popular applications on any platform, and that’s certainly the case for Microsoft’s Windows as well. While users on Windows have the option to stream videos from these services in a web browser, they can also opt for downloading dedicated apps from the Microsoft Store. Netflix and Hulu have apps available on the Microsoft Store, and it finally looks like Amazon will be joining the party with its own Prime Video Windows app. On top of that, a separate report from Protocol suggests that Amazon may be looking to add live TV to the mix.

Amazon Prime Video – Finally on the Microsoft Store

First, let’s talk about the Amazon Prime Video app for Windows. This is a UWP (Universal Windows Platform) app which means it is designed to not only be compatible with Windows desktops but also with tablets and Xbox consoles. That’s not major news for Xbox users, though, because there’s already a Prime Video app for Xbox and the Microsoft Store listing only lists “PC” under “Available on.” Netflix, another UWP app, for example, lists “Xbox One, PC, and Mobile device.”

Anyway, the app itself looks to be a pretty standard Amazon Prime Video client. The main screen features horizontal lists of shows and movies with a sidebar on the left. The sidebar can take you to the Amazon Store, channels, categories, “My Stuff,” downloads, and “Kids.” As the Downloads section suggests, the app does indeed support downloading videos to watch offline.

You can find the Prime Video app in the Microsoft Store right now and install it. At the time of publication, if you try to sign in you’ll get an error message. We expect Amazon to officially announce the app’s availability soon. Watching video in a web browser from primevideo.com (outside of the U.S.) or from Amazon.com was never a great experience, especially on Windows 10 on ARM devices like the Microsoft Surface Pro X, so we hope the UWP app provides a much better experience.

Live TV on Prime Video

The next bit of Prime Video news comes from Janko Roettgers at Protocol. According to the report, which cites both several job listings and unnamed sources, Amazon plans to add 24/7 live programming and linear programming to the service. 24/7 feeds would enable customers to watch streams of TV stations airing sports, news, movies, and more. This would make Prime Video a direct competitor to services like YouTube TV and Sling TV.

Prime Video has traditionally focused on on-demand streaming and rentals, though it has dabbled in live content before. Amazon has broadcasted NFL Thursday Night Football games and live Cheddar and ABC News channels in the News app. Users can also sign up for cable TV channels through the Amazon Channels feature.

Amazon’s combination of Prime Video on-demand content and live programming would make it a very attractive option in the streaming space. Even if it doesn’t have the same variety of channels as YouTube TV, it would be the cherry on top of an already popular service. Many people still watch linear TV channels and adding that to Prime Video would bring even more customers over. The fact that job listings for implementing this feature still up suggest that it could be a while before anything materializes, though.

Source 1: Microsoft Store | Via 1: Aggiornamenti Lumia | Source 2: Protocol


Update: Windows app live

Last week, the Amazon Prime Video app for Windows appeared in the Microsoft Store. The app could be installed, but it wasn’t possible to sign in. Amazon has now flipped the switch and users can sign in and use the app. You can download the app from the Microsoft Store link below. Go forth and stream!

Source: Microsoft Store | Via: MSPoweruser

The post [Update: Windows app live] Amazon Prime Video finally gets a Windows app and may add live TV appeared first on xda-developers.



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

Amazon Prime Video’s “Watch Party” feature lets you watch TV shows and movies together

Every day, more of our interactions with others happen over the Internet. You can play video games with a friend across the country, watch your nephew’s soccer game at home, and do a video call with a group of people all around the globe. Amazon’s latest feature for Prime Video is called “Watch Party” and it allows people to watch TV shows and movies together over the internet.

Amazon Prime Video “Watch Party” is a co-watching feature initially coming to subscribers in the U.S. It’s included with a Prime membership and it allows people to watch content remotely with others, perfectly synchronized. One person is the “host” and they can start, stop, and pause video playback for everyone. It’s like watching a movie in the same room and one person has control of the remote.

Each Watch Party session can include up to 100 participants who must also have Amazon Prime memberships. The session also includes a built-in chat for text and emoji conversations. Watch Party currently only works on the desktop and it supports thousands of the TV shows and movies available through Prime Video. Content that can be purchased or rented is not included, however.

To start a session, simply navigate to the TV show or movie you want to watch and click the Watch Party icon. The host will then be given a link that they can share with friends and family. Clicking the link will join the session and the content will then be synced with the host.

We’ve seen similar features and third-party extensions for other streaming services, so it’s great to see Prime Video joining in. Even before the COVID-19 pandemic kept many people at home, watching movies and TV shows with friends over the Internet is something that many people enjoyed doing. Now it’s even easier for Prime members to do.


Sources: Amazon (1), (2) | Via: TechCrunch

The post Amazon Prime Video’s “Watch Party” feature lets you watch TV shows and movies together appeared first on xda-developers.



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

Qualcomm unveils the Snapdragon Wear 4100 for better performance and battery life on Wear OS smartwatches

Qualcomm has announced the Snapdragon 4100 smartwatch platforms, consisting of the Snapdragon Wear 4100+ and the Snapdragon Wear 4100. These new smartwatch SoCs are designed for next-generation connected smartwatches and based on Qualcomm’s ultra-low-power hybrid architecture. To provide better context to this news release, let’s delve into the background of Wear OS first.

The first Android Wear smartwatches were launched in 2014. For a while, Android Wear seemed the next big thing after big-screen smartphones. There was the much-hyped first-generation Moto 360, the halo Android Wear watch. There were popular watches launched by Huawei, ASUS, and others. Android Wear even arrived at the market a few months ahead of the Apple Watch. However, all of these early efforts fizzled out. The second-generation Moto 360 never received an official successor. Other companies withdrew from releasing new Android Wear watches. The Apple Watch was released in early 2015, and the rest is history. It is now by far the most popular smartwatch in the world, and the consensus of the industry agrees that Android Wear – re-branded by Google as Wear OS in 2018 – is far behind. While Apple is now the biggest watch company in the world, Wear OS watches suffer from the catch-22 issues of poor value, lack of consumer interest, lack of vision, and so much more.

Some blame for that lies on Google for failing to make Wear OS as good as it could be after showing promise in the beginning. But many reviewers would place a larger section of the blame on Qualcomm. All Wear OS smartwatches are powered by special low-power Qualcomm SoCs. The problem is that Qualcomm had been reluctant to innovate in the smartwatch SoC front. The release of the Snapdragon 3100 in 2018 was only a mild increment over the Snapdragon 2100 in 2016. The Snapdragon 3100 still featured relatively historical ARM Cortex-A7 cores manufactured on a relatively historical 28nm process, at a time when Apple’s smartwatch SoCs and Samsung’s low-power Exynos SoCs moved to much more efficient 14nm and then 10nm processes. Apple and Samsung are the two major players in the smartwatch market, and both of them use custom operating systems in the form of watchOS and Tizen respectively. Wear OS has been a second class citizen for too many years now, and user interest in new Wear OS smartwatches is lackluster, to say the least, but it still provides one of the better options that are compatible with Android smartphones.

Qualcomm, though, hasn’t given up on the smartwatch market yet.

Nearly two years after announcing the Snapdragon Wear 3100, the company has launched its successor in the form of the Snapdragon Wear 4100+ (yes, this is the chip we first thought was to be the Snapdragon Wear 3300). It’s the first Qualcomm smartwatch SoC to be made on a modern process node: 12nm FinFET. It’s also the first Qualcomm smartwatch SoC to adopt ARM Cortex-A53 cores, finally moving on from the 32-bit Cortex-A7.

The Snapdragon Wear 4100 platforms are said to bring super-fast performance and connectivity, a smarter co-processor, and an ultra-lower power platform. The substantial improvements in platform power have been achieved by moving to a 12nm process. This isn’t cutting-edge as Samsung’s Exynos 9110 is produced on a more efficient 10nm process, but it should still provide enormous improvements over the 28nm process that powers the Snapdragon Wear 3100.

Qualcomm notes that the wearable industry has seen strong growth over the last few years (even as Wear OS loses steam). According to IDC, the industry is expected to continue to grow at an accelerated pace. The growth has given rise to segments within the industry as we can now find a range of wearables for adults, children, and seniors, along with targeted applications for sports, health, communication, and fashion. Consumers’ importance of public health and well-being will drive accelerated growth in H2 2020 and beyond, according to the company.

The wearables segment requires a flexible architecture that delivers great experiences while also having extended battery life. Qualcomm believes the hybrid architecture with an A-Class SoC and an M-Class co-processor is best suited to help meet those requirements. To that end, the Snapdragon Wear 4100+ is a high-performance CPU with improved CPU, GPU, memory, cellular modem, and camera sub-systems in the 12nm low processor process, along with dual dedicated DSPs for modem, location and sensors, as well as audio.

The Snapdragon Wear 4100+ has an AON ultra-low power co-processor that offloads a series of use cases including display, sensor, maps, and time from the main CPU. It also features a stronger AON software interface to manage the interactions between the SoC and the co-processor.

Qualcomm’s new Snapdragon 4100+ makes an effort to distinguish itself from its middling predecessors. The company says the SoC’s architecture is engineered to deliver significant improvements in performance, connectivity, smartness, and power compared to its previous platforms. The smartwatch SoC is based on Qualcomm’s mobile Snapdragon 429 SoC. The key highlights of both platforms include the following:

Fast performance and connectivity. The SoC has quad-core ARM Cortex-A53 CPU cores. The Cortex-A53 was launched as the successor of the Cortex-A7 back in October 2012 – it’s seven years old now. In the smartphone SoC space, it was succeeded by the ARM Cortex-A55 in May 2017. The Cortex-A53 is still an in-order core, but importantly, it’s a 64-bit core (AArch64). Thus, the next-generation Wear OS smartwatches will be the first to have a 64-bit CPU architecture. The Cortex-A53 also features decent IPC improvements over the Cortex-A7, so CPU performance will be faster. The cores are clocked at up to 1.7GHz. Overall, Qualcomm says the SoC delivers 85% performance improvements over its predecessor.

The Cortex-A53 cores are paired with the Adreno 504 GPU, succeeding the Adreno 304 GPU in the Snapdragon Wear 3100. Qualcomm says this brings 2.5x improvements in GPU performance, which shouldn’t be too surprising considering how old and weak the Adreno 304 was. The Snapdragon Wear 4100+ features faster LPDDR3 memory (750MHz) and dual ISPs with support for up to 16MP cameras, although the last specification is redundant.

The new IP enhances the Snapdragon Wear 4100’s overall user experience with faster app launches, concurrent use cases, smoother and more responsive UX, and richer photo and video experiences, according to Qualcomm.

Connectivity. Qualcomm says the 4G LTE mode of the SoC, based on 12nm technology, has been significantly improved compared to its predecessor, and it has a dedicated DSP, low power features such as eDRX, platform-level power management, support for Cat 4/3/1 and single/dual antennas.

Smarter Always-On (AON) Co-Processor. The enhanced AON co-processor supports better offloaded experiences. Qualcomm has partitioned memory and performance to enable up to 64K colors and has extended offload experiences to include continuous heart rate monitoring, sleep for health and fitness, faster tilt-to-wake responsiveness, step counting, alarms, timers, and haptics for a more capable traditional watch mode.

Ultra-low power platform. The low power optimizations include 12nm process technology, dual DSPs for optimal workload partitioning, support for dynamic clock and voltage scaling (DVFS), Qualcomm Sensor Assisted Positioning PDR Wearables 2.0, low power location tracking support, and an enhanced Bluetooth 5.0 architecture. Combined, these improvements are designed to deliver more than 25% power reductions across key use cases – bringing bring extended battery life to the platform compared to its predecessors.

“Richer, enhanced experiences.” The hybrid platform in the Snapdragon Wear 4100+ is said to bring rich, enhanced experiences across interactive, ambient, sports, and watch modes. Qualcomm details this by explaining that in interactive mode, the platform supports additional “immersive experiences” with camera, voice assistant, and voice/video messaging. In ambient mode, the increase in number of colors from 16 to 64K and number kerning is designed to improve readability and offer more exciting design options as well. In sports mode, offloaded maps enhance the on-the-go experience. Finally, the traditional watch mode includes features such as heart rate, steps, alarms, reminders, and battery indicator with a “minimal impact” on performance or battery life.

Qualcomm says the first Snapdragon Wear 4100 platform-based products will ship later this year. A few companies have announced smartwatches based on the Snapdragon Wear 4100 in concurrence with Qualcomm’s enhancement. This includes imoo’s next-generation Z6 Ultra smartwatch based on the Snapdragon Wear 4100. imoo is a leading brand for kid smartwatches, and the Z6 Ultra is expected to start shipping over the next month. It will be the first smartwatch to use Qualcomm’s new platform.

Mobvoi is also announcing its next-generation TicWatch Pro smartwatches based on the Snapdragon Wear 4100 platform. The company says it’s the first brand to announce its next watch based on the Snapdragon 4100 and Wear OS.

The Snapdragon 4100 platforms come in two variants. The Snapdragon Wear 4100+ includes the main SoC (SDM429w or SDA429w) and the AON Co-Processor (QCC1110), along with the companion chips including PMIC, RF for modem/GPS and Wi-Fi/BT, and RFFE (radio frequency front-end). The Snapdragon Wear 4100, on the other hand, consists of the main SoC along with the companion chips, which means it lacks the AON co-processor.

The Snapdragon Wear 4100 platforms support both AOSP and Wear OS by Google. They are available and shipping now to consumers. For more information about them, readers can head to Qualcomm’s website.

The post Qualcomm unveils the Snapdragon Wear 4100 for better performance and battery life on Wear OS smartwatches appeared first on xda-developers.



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

Android’s AirDrop-like Nearby Share feature is rolling out in beta

Google has been working on a sharing feature similar to Apple’s AirDrop for a while now. Originally discovered over a year ago as “Fast Share,” it was eventually renamed to “Nearby Sharing” and finally just “Nearby Share.” The feature is getting very close to a public release as Google has confirmed it’s rolling out through Play Services beta.

So what exactly is Nearby Share? Basically, think of it as a sharing mechanism for nearly all Android devices. The magic of Apple’s AirDrop is it’s present on all Apple products, from iPhone to iPad to Mac. Apple users can easily share things with each other without any setup or thought. Nearby Share would work in the same way since it’s available through Play Services, which the overwhelming majority of Android phones have. There’s also evidence to believe it will work through the Chrome browser.

To get Nearby Share up and running, you’ll need to sign up to be a beta tester for Google Play Services. You can do that by simply visiting the Play Store listing and opting into the beta. After that, you’ll need to wait for a bit until an update appears. Once you have the beta installed, you should see “Nearby Share” in the share sheet when sharing from apps.

Nearby Share will show up differently depending on what you’re sharing. You will always see “Nearby Share” in the list of available apps to share with, but sometimes there will be a shortcut at the top of the sheet next to the “Copy” button. The first time you select Nearby Share you will be asked to turn it on.

Once you have it all set up, Nearby Share will look for other devices nearby that have it enabled as well. You can share files such as photos and videos, links, and other stuff as well. When a device nearby wants to share with you, a notification will appear and you can tap it to make your device visible. Both parties need to confirm before the sharing occurs. The Nearby Share settings allow you to adjust who can see your device and how things are shared (data, Wi-Fi only, without internet).

As mentioned, Nearby Share is currently rolling out via Google Play Services beta. On the three devices I tested, I was able to get it set up on one, so it’s not immediately available to everyone. If you do get it, you should see it in the share sheet immediately after installing the beta. It’s still early, but Nearby Share is shaping up to be a great feature.

Google Play services (Free, Google Play) →


Via: Android Police

The post Android’s AirDrop-like Nearby Share feature is rolling out in beta appeared first on xda-developers.



from xda-developers https://ift.tt/38etiUb
via IFTTT

Google Play Services prepares to show earthquake alerts in California powered by ShakeAlert

With the Third Pixel Feature Drop at the beginning of June, Google added a bunch of new features to Android 10 on Pixel devices. Among these, Google added some improvements to the Personal Safety app by extending the Crash Detection feature from Pixel 4/4XL to Pixel 3 series and adding two new features – “Safety Check” to keep emergency contacts updated about your whereabouts if you don’t respond to scheduled check-ins and “Crisis Alerts” to inform you of natural disasters in your area.

Although Crisis Alerts are not for any specific type of natural calamity, Google is preparing to add an alert mechanism specifically for earthquakes. We spotted references in the Google Play Services 20.26.12 beta that the company added for earthquake alerts specifically in California. These alerts are powered by ShakeAlert, a service that provides early warnings about earthquakes specifically for the West Coast.

An APK teardown can often predict features that may arrive in a future update of an application, but it is possible that any of the features we mention here may not make it in a future release. This is because these features are currently unimplemented in the live build and may be pulled at any time by Google in a future build.

In an APK teardown of the Google Play Services 20.26.12 beta, we found the following strings hinting towards the features and its applications:

<string name="about">About</string>
<string name="about_details">Earthquake alerts and info are provided by Google &amp; ShakeAlert®.</string>
<string name="about_details_link">Learn more or change settings</string>
<string name="demo_take_action_title">Earthquake Demo</string>
<string name="distance_to_epicenter_km">%.1f km away</string>
<string name="distance_to_epicenter_mile">%.1f miles away</string>
<string name="google_setting_eew_nearby_notification">Earthquake Nearby Notification</string>
<string name="google_setting_eew_occurred_notification">Earthquake Occurred Notification</string>
<string name="google_setting_take_action">Take action alert</string>
<string name="google_setting_take_action_delay">Take action alert after 3 minutes</string>
<string name="local_map_source">Source: ShakeAlert®</string>
<string name="quake_notification_high_importance_channel_name">Earthquake Early Warning Alert</string>
<string name="quake_notification_low_importance_channel_name">Earthquake Early Warning Updates</string>
<string name="ealert_activity_debug_google_setting_title">EEW System Debug</string>
<string name="ealert_latest_update_search_word">earthquake near me</string>
<string name="ealert_local_map_magnitude">Est. mag %.1f earthquake</string>
<string name="ealert_more_safety_tips">More safety tips</string>
<string name="ealert_nearby_notification_text" formatted="false">Expect shaking. Estimated magnitude %.1f about %s away.</string>
<string name="ealert_notification_nearby">Earthquake nearby</string>
<string name="ealert_notification_occurred">Earthquake occurred nearby</string>
<string name="ealert_notification_sender">Google - ShakeAlert®</string>
<string name="ealert_occurred_notification_text" formatted="false">Estimated magnitude %.1f about %s away. Tap to learn more.</string>
<string name="ealert_safety_demo">See a demo</string>
<string name="ealert_safety_info_label">Earthquake safety info</string>
<string name="ealert_safety_tip_content_1">Identify hazards and secure movable items</string>
<string name="ealert_safety_tip_content_10">If you live in a coastal area, relocate as soon as shaking stops to avoid tsunamis</string>
<string name="ealert_safety_tip_content_11">" "<li>"Don't touch downed or damaged utility lines"</li>"
"<li>"Don't use a damaged chimney. Approach downed or damaged chimneys with caution"</li>" "</string>
<string name="ealert_safety_tip_content_12">You may receive an alert if an aftershock is expected</string>
<string name="ealert_safety_tip_content_2">Create a disaster plan and decide how you will communicate in an emergency</string>
<string name="ealert_safety_tip_content_3">Put supplies in convenient locations</string>
<string name="ealert_safety_tip_content_4">Organize important documents, fix any structural issues on your property, and consider insurance</string>
<string name="ealert_safety_tip_content_5">During an earthquake, take cover under a table and hold on</string>
<string name="ealert_safety_tip_content_6">Evacuate if you smell gas or see building damage, help the injured, and stay away from anything that may fall</string>
<string name="ealert_safety_tip_content_7">Reach out to others, take pictures of any damage, and contact your insurance</string>
<string name="ealert_safety_tip_content_8">If water is shut off, use emergency supplies like a water heater or melted ice cubes</string>
<string name="ealert_safety_tip_content_9">" "<li>"Put out small fires. If you can't, evacuate."</li>"
"<li>Check electric, water lines, and appliances for damage. If you see a broken line, shut off the main valve.</li>"
"<li>Clean up spilled medicines, drugs, or other harmful materials</li>" "</string>
<string name="ealert_safety_tip_page_subtitle">Source: Earthquake Country Alliance</string>
<string name="ealert_safety_tip_page_title">Earthquake safety steps</string>
<string name="ealert_safety_tip_title_1">1. Secure your space</string>
<string name="ealert_safety_tip_title_10">Move to higher ground</string>
<string name="ealert_safety_tip_title_11">Avoid fallen objects</string>
<string name="ealert_safety_tip_title_12">Expect aftershocks</string>
<string name="ealert_safety_tip_title_2">2. Make a plan</string>
<string name="ealert_safety_tip_title_3">3. Organize disaster supplies</string>
<string name="ealert_safety_tip_title_4">4. Minimize financial hardship</string>
<string name="ealert_safety_tip_title_5">5. Drop, cover, and hold on</string>
<string name="ealert_safety_tip_title_6">6. Act quickly and cautiously</string>
<string name="ealert_safety_tip_title_7">7. Reconnect and restore</string>
<string name="ealert_safety_tip_title_8">Get your emergency supplies</string>
<string name="ealert_safety_tip_title_9">Use caution when cleaning up</string>
<string name="ealert_safety_tips_title">Learn earthquake safety tips</string>
<string name="ealert_settings_detected_text">"You'll get an alert with the estimated magnitude and distance from your location"</string>
<string name="ealert_settings_detected_title">When an earthquake is detected nearby</string>
<string name="ealert_settings_how_it_works_body_2_text">"Keep in mind:
"<li>Not all earthquakes can be detected</li>"
"<li>Magnitude and shaking intensity estimates may have errors</li>"
"<li>You may receive an alert before, during, or after shaking begins</li>"
"</string>
<string name="ealert_settings_how_it_works_body_text">Android uses your approximate location to send information about nearby earthquakes. Earthquakes are detected by ShakeAlert®.</string>
<string name="ealert_settings_how_it_works_title">How it works</string>
<string name="ealert_stay_safer_content_1">Before going anywhere, even to the next room</string>
<string name="ealert_stay_safer_content_2">"If you smell gas, turn off the gas main to the building. If you can't, evacuate."</string>
<string name="ealert_stay_safer_content_3">Check for cracks and damage. Evacuate if it looks like the building may collapse.</string>
<string name="ealert_stay_safer_title">Stay safer after an earthquake</string>
<string name="ealert_stay_safer_title_1">Get shoes</string>
<string name="ealert_stay_safer_title_2">Check gas</string>
<string name="ealert_stay_safer_title_3">Avoid damaged buildings</string>
<string name="ealert_take_action_cover">Cover</string>
<string name="ealert_take_action_drop">Drop</string>
<string name="ealert_take_action_hold">Hold</string>
<string name="ealert_take_action_magnitude">Estimated magnitude %.1f</string>
<string name="ealert_take_action_next_steps">Tap for next steps</string>
<string name="ealert_take_action_source">Google alert powered by ShakeAlert®</string>
<string name="ealert_take_action_title">Earthquake</string>
<string name="eew_share_link">Share</string>
<string name="eew_update_link">See latest updates</string>

The earthquake warning feature should share details including your distance from the epicenter, share tips on how to keep you safe as well as action points to follow in case you need to evacuate the premises.

Personal Safety (Free, Google Play) →

The post Google Play Services prepares to show earthquake alerts in California powered by ShakeAlert appeared first on xda-developers.



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

HUAWEI HMS Core Forum Recap [June]

HUAWEI Developers is a platform ecosystem that integrates various services and resources for developers to develop and promote their apps, which is committed to serving the vast number of mobile terminal developers. Relying on the advantages of terminal channels, global platform services, and industry chain resources, it aims at openness and innovation in development, testing, and promotion, monetization and other aspects, to help developers create a terminal-based all-scenario innovation experience in an all-round way and reach consumers through smart terminals so as to build an open and win-win innovation ecosystem. You can access the XDA Huawei Developers forum here. Interact with other HMS developers, find guides, and follow tutorials for beginners or more advanced developers. Best guides from June 2020:

HMS offers many kits to help developers build high-quality apps. Because of the availability of these kits, you can build your app quickly and at a very low cost.

Development Kits

It doesn’t stop at development. After you’ve built your app, these kits will help you grow your app userbase. Receive detailed analytics that will help you understand how people use your app.

Growth Kits

Make money off of your hard work. Use these kits to monetize your apps by implementing ads, in-app purchases, and digital wallets.

Monetization Kits

Visit the XDA Huawei Developers forum to become a part of the Huawei Developer community. XDA Huawei Developers forum

We thank Huawei for sponsoring this post. Our sponsors help us pay for the many costs associated with running XDA, including server costs, full time developers, news writers, and much more. While you might see sponsored content (which will always be labeled as such) alongside Portal content, the Portal team is in no way responsible for these posts. Sponsored content, advertising and XDA Depot are managed by a separate team entirely. XDA will never compromise its journalistic integrity by accepting money to write favorably about a company, or alter our opinions or views in any way. Our opinion cannot be bought.

The post HUAWEI HMS Core Forum Recap [June] appeared first on xda-developers.



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

Redmi 9A and Redmi 9C launch with big batteries, notched displays, and new MediaTek processors

Taiwanese chipmaker MediaTek just unveiled the new Helio G25 and Helio G35 chipsets for budget gaming smartphones. The new octa-core chipsets are manufactured on a 12nm fabrication process and feature 8x ARM Cortex-A53 CPU cores clocked at 2.0GHz and 2.3GHz, respectively. The chipsets are making a debut with Xiaomi’s new Redmi 9A and Redmi 9C, which have now been unveiled in Malaysia.

Xiaomi Redmi 9A and Redmi 9C: Specifications

Specifications Redmi 9A Redmi 9C
Dimensions & Weight
  • 164.9 x 77.07 x 9.0 mm
  • 194g
  • 164.9 x 77.07 x 9.0 mm
  • 196g
Display
  • 6.53″ LCD
  • HD+, 1600 x 720 pixels
  • 6.53″ LCD
  • HD+, 1600 x 720 pixels
SoC MediaTek Helio G25 MediaTek Helio G35
RAM
  • 2GB LPDDR4x
  • 3GB LPDDR4x
  • 2GB LPDDR4x
  • 3GB LPDDR4x
  • 4GB LPDDR4x
Storage 32GB eMMC 5.1
  • 32GB eMMC5.1
  • 64GB eMMC5.1
Battery & Charging
  • 5,000 mAh
  • 10W wired fast charging
  • 5,000 mAh
  • 10W wired fast charging
Rear Camera 13MP, f/2.2
  • Primary: 13MP, f/2.2
  • Secondary: 2MP, macro, f/2.4
  • Tertiary: 2MP depth sensor, f/2.4
Front Camera 5MP, f/2.2 5MP, f/2.2
Other Features
  • Micro USB
  • 3.5mm headphone jack
  • Rear-mounted fingerprint sensor
  • Micro USB
  • 3.5mm headphone jack
Colors
  • Granite Gray
  • Peacock Green
  • Sky Blue
  • Midnight Gray
  • Sunrise Orange
  • Twilight Blue

As seen in previous leaks, the latest devices in the Xiaomi Redmi 9 series feature large 5,000mAh batteries, notched displays, and MediaTek’s new chipsets. The new Redmi 9A features a design reminiscent of older devices in the series and is powered by the MediaTek G25 chip. The device features a 6.53-inch HD+ display (1600×720 pixels) with a waterdrop style notch, up to 3GB of LPDDR4x RAM, and 32GB of eMMC 5.1 storage.

Xiaomi Redmi 9A

In the camera department, the device packs in a single 13MP f/2.2 camera on the back and a 5MP f/2.2 selfie shooter over on the front. As mentioned earlier, the device features a massive 5,000mAh battery that includes support for 10W fast charging using the included charging brick. In terms of ports, the device includes a micro USB port for charging and data syncing, along with a 3.5mm headphone jack. The device doesn’t include a fingerprint sensor, but it does support face unlock using the selfie camera.

The Redmi 9C, on the other hand, features a slightly different design with a square camera module on the back, instead of the vertically oriented camera module found on the Redmi 9A, and it’s powered by the MediaTek Helio G35 chip. The device includes the same 6.53-inch HD+ display (1600×720 pixels) with a waterdrop style notch, up to 4GB of LPDDR4x RAM, and up to 64GB of eMMC 5.1 storage.

Xiaomi Redmi 9C

In the camera department, the device features a triple camera setup on the back with a 13MP f/2.2 primary camera, a 2MP f/2.4 macro camera, and a 2MP depth sensor. Over on the front, the device features the same 5MP f/2.2 selfie shooter. Much like the Redmi 9A, the Redmi 9C features a 5,000mAh battery with support for 10W fast charging using the included charger. In terms of ports, the device features a micro USB port for charging and data syncing, along with a 3.5mm headphone jack. Unlike the Redmi 9A, the Redmi 9C does include a capacitive fingerprint scanner on the back panel.

Pricing and Availability

The Redmi 9A has been launched in Malaysia at a price of RM359 (~$84) for the 2GB+32GB variant. The device comes in three color variants — Granite Gray, Peacock Green, and Sky Blue — and will be available for purchase on Lazada and Shopee starting from July 7th. The device will also be available at all authorized Mi stores in Malaysia starting from 14th July. As of now, the company hasn’t released any information about the pricing and availability for the 3GB+32GB variant, except for the fact that it will be available in Indonesia.

Redmi_9C_and_Redmi_9A_Pricing

The 2GB+32GB variant of the Redmi 9C has been priced at RM429 (~$100) and it also comes in three color variants — Midnight Gray, Sunrise Orange, and Twilight Blue. The device will be available for purchase towards the end of July in Malaysia and, much like the Redmi 9A, the higher-end 4GB+64GB variant of the device will be launched in Indonesia.


Source: Xiaomi Malaysia Facebook (1,2)

The post Redmi 9A and Redmi 9C launch with big batteries, notched displays, and new MediaTek processors appeared first on xda-developers.



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

lundi 29 juin 2020

SafetyNet’s dreaded hardware attestation is rolling out, making it much harder for Magisk to hide root

Back in March, a few users with Magisk installed noticed that their devices were failing SafetyNet attestation. This news was troubling to the community at XDA because it means that many crucial banking/financial apps and popular games like Pokémon Go and Fate/Grand Order were refusing to run on rooted devices. For some time, it seemed as if the tightened restrictions in SafetyNet were pulled back, only to roll out again for a handful of users in the last few weeks. However, Google quietly confirmed in early May that they testing hardware-backed attestation for SafetyNet responses, which is what made Magisk unable to hide the bootloader unlocking status back in March. If this change widely rolls out, it will mean that users will have to choose between having access to root/custom ROMs/kernels/etc. or their preferred banking apps and games. One of the biggest appeals of Android for power users could soon be gone.

To recap this series of events, we should first talk about SafetyNet itself. SafetyNet is a set of APIs in Google Play Services. The SafetyNet Attestation API is one of those APIs, and it can be called by third-party applications to check if the software environment of the device has been tampered with in any way. The API checks for various things like signs of superuser binaries, the bootloader unlock status, and more. When you root a device with Magisk, it “[creates] an isolated ‘safe environment’ for the [SafetyNet] 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,” per XDA Senior Recognized Developer topjohnwu. This allows the user to root their phone while ensuring that the API always returns “false” for any bootloader unlocking checks. This method of bypassing SafetyNet’s bootloader unlocking detection has been working out for Magisk for the last few years, but that’s only because Google has held off on verifying the integrity of the boot image using hardware attestation. In March, it seemed like Google was finally starting to employ hardware attestation in SafetyNet to verify the boot image, but we never got an official statement from Google confirming the change and only a few users were affected. As spotted by XDA Senior Member Displax, however, Google confirmed on May 5, 2020, that SafetyNet Attestation API responses from some devices now include hardware-backed checks.

On the Google Group for “SafetyNet API Clients,” Google detailed a new feature for the Attestation API: evaluationType. The JSON Web Signature (JWS) response from some devices will have a field named “evaluationType” that “will provide developers with insight into the types of signals/measurements that have contributed to each individual SafetyNet Attestation API response.” One of the supported tokens in this field is “HARDWARE_BACKED” which indicates that the API “[used] the available hardware-backed security features of the remote device (e.g. hardware-backed key attestation) to influence [its] evaluation.” Google says that they are “currently evaluating and adjusting the eligibility criteria for devices where we will rely on hardware-backed security features.” What this means is that, on some devices, Google Play Services is now using hardware-backed attestation to detect that the device’s software hasn’t been tampered with. Google has not officially documented this change outside of the announcement in the Google Group, so some developers that use SafetyNet may not be aware of this change (and thus aren’t yet checking for the “HARDWARE_BACKED” field in JWS responses.) However, for those apps that are checking for this field, there’s now no way to hide root access from them, provided your device is part of the test that Google is running.

According to topjohnwu, hardware-backed attestation means that Google Play Services now “[sends] an unmodified keystore certificate to SafetyNet servers, [verifies] its legitimacy, and [checks] certificate extension data to know whether your device [has] verified boot enabled (bootloader status).” Since the private keys from which the keystore certificates are derived from are backed by the phone’s isolated secure environment, retrieving them would involve defeating the security of the phone’s Trusted Execution Environment (TEE) or dedicated hardware security module (HSM). If one were somehow able to leak a private key, the keys would quickly be revoked once Google found out. Google and other companies offer hundreds of thousands of dollars in rewards for any critical security vulnerabilities in TEEs, so it’s incredibly unlikely for this to be a potential avenue to bypass bootloader unlocking detection anyways.

Another potential way that Magisk could continue to spoof the bootloader unlocking status is by modifying SafetyNet’s client-side code to always use the BASIC evaluation. As topjohnwu notes, though, this would require injecting custom code into Google Play Services via a hooking framework like the Xposed Framework. This is not only difficult to do because Google Play Services is highly obfuscated but it’s also impossible to hide as “some memory space analysis will reveal code manipulation very easily.” Furthermore, this would also only work if Google’s servers continue to accept BASIC evaluations and if HARDWARE_BACKED evaluations are not enforced on devices that support them. (SafetyNet responses “[come] from Google servers and are signed with Google’s private key,” according to topjohnwu, so the actual responses can’t be spoofed.)

Since Android 7 Nougat, Google has required that all devices have an isolated secure environment, meaning this change to how SafetyNet verifies bootloader unlocking will affect most devices that are out there. Since older devices without an isolated secure environment obviously can’t perform hardware-backed attestation, Magisk will still be able to hide root access on those devices. But if this change rolls out widely, everyone else will have to make a hard choice between root access and banking apps.

Unfortunately, there are probably a lot of apps out there that use SafetyNet checks when they don’t actually need to. One example cited by topjohnwu is the official McDonald’s app, which seemingly refuses to run on a bootloader unlocked device. On Twitter, topjohnwu calls out apps that overuse the API as creating a hostile environment for power users. XDA Recognized Developer Quinny899 joins in with an anecdote about how his team considered using SafetyNet to check the device security status. They ultimately decided not to go through with it since his team’s app encrypts all the sensitive data it works with. SafetyNet, he argues, should not be used in lieu of proper security and data handling practices, especially when considering the possibility of superuser exploits.


For more information on how the new SafetyNet change affects Magisk, check out topjohnwu’s excellent FAQ on Twitter. If you just want to check if your device is part of Google’s new SafetyNet test, then you can follow this guide by XDA Senior Member Displax.

The post SafetyNet’s dreaded hardware attestation is rolling out, making it much harder for Magisk to hide root appeared first on xda-developers.



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

MediaTek Helio G35 and G25 chipsets unveiled for gaming on a budget

Adding on to its list of gaming-focused Helio G series chipsets, Taiwanese chipmaker MediaTek has now unveiled the budget-friendly Helio G35 and Helio G25. The new budget chips come just a month after the company unveiled the mid-range Helio G85, which is an octa-core processor that’s built on a 12nm process. Much like the Helio G85, both the Helio G25 and Helio G35 are fabricated on a 12nm manufacturing process.

MediaTek Helio G25

Out of the two new chips, the entry-level MediaTek Helio G25 features 8x ARM Cortex A-53 CPU cores clocked at 2.0GHz and an Imagination PowerVR GE8320 GPU clocked at up to 650MHz. The G25 is capable of running displays at 1600×720 resolution at 60Hz. On the other hand, the MediaTek Helio G35 features 8x ARM Cortex A-53 CPU cores clocked at 2.3GHz, and an Imagination PowerVR GE8320 GPU clocked at up to 680MHz. The G35 is capable of running displays at 2400×1080 resolution at 60Hz.

MediaTek Helio G35

In the camera department, the Helio G25 supports dual 13MP+8MP cameras or a single 21MP camera with Zero Shutter Lag, while the G35 supports dual 13MP+13MP cameras or a single 25MP camera with Zero Shutter Lag. Both the Helio G25 and Helio G35 support MediaTek’s HyperEngine technology, which boasts of dynamic allocation of CPU, GPU, and memory while factoring in power, thermal, and gameplay requirements, to offer smooth gaming performance on budget devices, enhance power efficiency and facilitate low-latency connections. The new chipsets support up to 6GB LPDDR4x RAM at 1600MHz frequency, eMMC 5.1 storage, Dual 4G VoLTE, LTE Cat. 7 DL/Cat.13 UL, Wi-Fi 5 (b/g/n/ac), and Bluetooth 5.0.


Source: MediaTek

The post MediaTek Helio G35 and G25 chipsets unveiled for gaming on a budget appeared first on xda-developers.



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

Windows File Recovery is a new tool from Microsoft that may help you restore deleted files

Nothing is as frustrating as losing valuable information from your hard drive which can happen due to human error or hardware failure. There may still be a chance to recover some of those files, though, since a lot of file deletions involve deleting the file index until that block of storage is overwritten. Just a simple “delete” command in Windows, for example, is not enough to irrevocably make files unrecoverable. To do that, you need to securely wipe the drive by either writing a bunch of zeroes or other data to it over several iterations or physically destroy the drive. The point is is that if you’ve accidentally lost some of your valuable files, there is still a chance you can restore them. Microsoft just made that slightly easier to do with the release of the Windows File Recovery tool.

Windows File Recovery is available as a free app in Microsoft Store. Though, it’s not an app in the common sense of the term since it’s a command-line tool. Although it uses a CLI interface, it is still very newbie-friendly. After launching the tool, you have options to target files you want to recover by name, paths, or extensions. Microsoft says Windows File Recovery can recover data not only from the hard drive installed on your computer but from external storage, too. This means you can use the tool on USB drives, memory cards, external SSDs, and other storage devices, though Microsoft recommends using Signature Mode for recovering files from external storage. There are also Default and Segment modes for recovering files from NTFS-formatted drives. As of now, the tool supports drives formatted in NTFS, FAT, exFAT, and ReFS file systems and various file extensions such as PNGs, PDFs, MP3 and MP4s, and many more.

You can find more information about how to use the tool, what it’ll work on, and what files it can recover from Microsoft’s support page. You can download Windows File Recovery for free from the Microsoft Store linked below. Just make sure that you’re running Windows 10 2004 or later to install the app.

Windows File Recovery (Free, Microsoft Store) →


Via: Neowin

The post Windows File Recovery is a new tool from Microsoft that may help you restore deleted files appeared first on xda-developers.



from xda-developers https://ift.tt/38cbJUQ
via IFTTT