Samsung ad highlights Google Assistant support on the Galaxy Watch 4 ahead of the official rollout

In February this year, Samsung rolled out a major software update for the Galaxy Watch 4 and Galaxy Watch 4 Classic. In its official announcement post for the update, the company revealed that it would soon roll out streaming support on the YouTube Music app for Wear OS smartwatches with a future update. Furthermore, the company confirmed that its smartwatches would also get Google Assistant support in the “coming months.” But the company is yet to release Google Assistant support to the Galaxy Watch 4 and Galaxy Watch 4 Classic. However, that might change soon, given that we’ve now seen multiple teasers about Google Assistant support on the Galaxy Watch 4 series over the last few days.

Last week, Samsung rolled out a new software update for the Verizon variants of the Galaxy Watch 4 and Watch 4 Classic. An initial version of the changelog for the update shared by Verizon referenced Google Assistant support, and it even included screenshots showcasing how users would be able to enable the “Hey, Google” hotword and other settings. This led us to believe that Samsung was finally rolling out Assistant support to the smartwatches, but Verizon later removed all mentions of Google Assistant from the changelog, and Google said that Assistant support was “not rolling out to Galaxy Watch 4, and we don’t have an update on timing.”

Google Assistant settings screenshot from Verizon’s changelog

Now Samsung has published a new ad for the Galaxy Watch 4 through its Spain-based YouTube channel (via Reddit), and it showcases a person using Google Assistant voice commands on the Galaxy Watch 4. This has, once again, sparked rumors that Google Assistant support for the Galaxy Watch 4 could roll out soon.

Interestingly, Samsung has published the same ad in several other regions, suggesting that the company could roll out Google Assistant support globally. However, as 9to5Google notes, some of the other ads have an upload date of March 10, so we’re not sure if Samsung has the update ready for rollout or not.

Currently, we have no official confirmation from Samsung regarding the Google Assistant rollout. So we can’t say for sure if you’ll get the feature in the coming days. We’re keeping our eyes peeled for the update, and we’ll make sure to let you know as soon as it starts rolling out. Meanwhile, you can check out Samsung’s ad by clicking on the YouTube video embedded above.

---

Via: Reddit, 9to5Google

The post Samsung ad highlights Google Assistant support on the Galaxy Watch 4 ahead of the official rollout appeared first on XDA.

from XDA https://ift.tt/04A1gba
via IFTTT

LineageOS 19 based on Android 12 is now officially available

LineageOS has been a strong driving force in the world of aftermarket Android development. As the successor to CyanogenMod, the project spans over literal hundreds of devices, offering the enthusiast community a way out of heavy and bloated systems and a dive into modifications for those with minimal skins. Now, the LineageOS team is marking its major version bump up to LineageOS 19 with Android 12 as the base.

Why LineageOS 19 (and not 19.0/19.1)?

If you take a look at our list of Android 12 and 12L custom ROMs, you can find the numerous entries corresponding to LineageOS 19.0, as well as 19.1. As a matter if fact, the initial set of unofficial builds picked up “19.0” due to the obvious major platform update. The subsequent minor version number change happened with the release of Android 12L.

Meanwhile, Google moved onto the quarterly maintenance release model for Android. Naturally, the existing subversion nomenclature of LineageOS would be cumbersome for regular users in the long run. Owing to this (and to match AOSP’s versioning conventions), the team has decided to drop the subversion string. The new release is simply called “LineageOS 19,” although you can still find references of “19.1” in the ROM filename and the codebase.

New features in LineageOS 19

LineageOS 19 comes with a plethora of new features and enhancements:

• Security patches from March 2021 to April 2022 have been merged to LineageOS 16.0 through 19.
  • 19 builds are currently based on the android-12.1.0_r4 tag, which is the Pixel 6 series tag.
• WebView has been updated to Chromium 100.0.4896.58.
• The team has completely redone the volume panel introduced in Android 12, and instead made it a side pop-out expanding panel.
• The fork of the AOSP Gallery app has seen a large number of fixes and improvements.
• The Updater app has seen a large number of bug-fixes and improvements.
• The LineageOS web browser, Jelly has seen a number of bug fixes and improvements.
• The team has contributed a number of changes and improvements back upstream to the FOSS Etar calendar app they integrated some time back.
• The team contributed a number of changes and improvements back upstream to the Seedvault backup app.
• The LineageOS Recorder app has seen numerous bug fixes, improvements, and features added.
• Android TV builds now ship with an ad-free Android TV launcher, unlike Google’s ad-enabled launcher.
• Android TV builds now ship with a key-handler that enables us to support custom-keys on a wide-array of bluetooth and IR remotes.
• The LineageOS adb_root service is no longer tied to the build type property.
• The project’s extract utilities now support extracting from most types of factory images/packed OTA images, simplifying device-bring up and blob-extraction greatly.
• Support for high-touch polling rate has been added to our SDK, allowing it to be enabled on supported devices.
• The AOSP Clang toolchain is now the default toolchain use to compile the LineageOS kernels.
• Qualcomm’s Snapdragon Camera has been dropped, and devices that used it previously will now use Camera2.
• Dark mode is now enabled by default.
• There is an entirely new Setup Wizard, with all new Android 12 styled icons, animations, and ton of new configurable pages.
• A brand new set of icons for almost all apps, even system ones.

Apart from the improvements mentioned above, the following changes have also been incorporated in both the LineageOS 19 and the legacy 18.1 codebase:

• A whole new default wallpaper, and a full set of wallpapers to choose from. These wallpapers are designed with Android 12’s Monet theming features in mind.
• Wi-Fi display is available for all devices which choose to opt-in, via either the Qualcomm proprietary interface or the newly restored legacy Miracast interface!
• Support for custom charging sounds for different types of charging, cabled or wireless.

Further changes

Networking Restrictions

The built-in firewall, restricted networking mode, and per app data isolation features have been rewritten to support AOSP’s new restricted networking mode and the BPF (Berkeley Packet Filter) facility. Moreover, the data restriction and network isolation features have been merged into a single implementation.

eBPF over iptables

AOSP now includes an Extended Berkeley Packet Filter (eBPF) loader and library that loads eBPF programs at boot time to extend kernel functionality. It essentially deprecates iptables, and there is no easy way to backport the feature to legacy Linux kernel variants. The LineageOS team has created a functional backport for devices with Linux kernel 4.4, but porting the same to 3.18 kernel or older is a quite a burdensome job. Furthermore, you can’t restore iptables in the AOSP codebase without breaking things.

As a consequence, there will be no official support for LineageOS 19 for Android devices running Linux kernel 3.18 and below, until a proper workaround of BPF is brought to these kernel versions.

---

LineageOS 19 – Official builds for supported devices

The following is the official build roster for the initial batch of the LineageOS 19 rollout:

Sr. No.	Device and Forum Link	Device codename and Wiki Link	Maintainer
1.	ASUS ZenFone 5Z	Z01R	rohanpurohit, Jackeagle, ThEMarD
2.	ASUS ZenFone 8	sake	ZVNexus, Demon000
3.	F(x)tec Pro1	pro1	BadDaemon, bgcngm, intervigil, mccreary, npjohnson, tdm
4.	Google Pixel 2	walleye	Eamo5
5.	Google Pixel 2 XL	taimen	Eamo5
6.	Google Pixel 3	blueline	razorloves, cdesai, intervigil, mikeioannina
7.	Google Pixel 3 XL	crosshatch	razorloves, cdesai, intervigil, mikeioannina
8.	Google Pixel 3a	sargo	cdesai, mikeioannina, npjohnson
9.	Google Pixel 3a XL	bonito	cdesai, mikeioannina, npjohnson
10.	Google Pixel 4	flame	cdesai, Eamo5, mikeioannina, npjohnson
11.	Google Pixel 4 XL	coral	cdesai, Eamo5, mikeioannina, npjohnson
12.	Google Pixel 4a	sunfish	PeterCxy, cdesai, mikeioannina
13.	Google Pixel 4a 5G	bramble	aleasto, mikeioannina
14.	Google Pixel 5	redfin	aleasto, mikeioannina
15.	Google Pixel 5a	barbet	aleasto, mikeioannina
16.	Lenovo Z5 Pro GT	heart	themard, optionaltoast
17.	Lenovo Z6 Pro	zippo	Lucchetto, themard
18.	Moto G6 Plus	evert	Jleeblanch
19.	Moto G7	river	erfanoabdi, npjohnson, SyberHexen
20.	Moto G7 Plus	lake	Jleeblanch, npjohnson
21.	Moto G7 Power	ocean	SyberHexen, erfanoabdi, npjohnson
22.	Moto X4	payton	erfanoabdi, ThEMarD
23.	Moto Z2 Force	nash	erfanoabdi, npjohnson
24.	Moto Z3 Play	beckham	Jleeblanch
25.	Motorola One Action	troika	Stricted, npjohnson
26.	Motorola One Power	chef	Hasaber8
27.	Motorola One Vision/Motorola P50	kane	Stricted, npjohnson
28.	Nokia 6.1 (2018)	PL2	npjohnson, theimpulson
29.	Nokia 6.1 Plus	DRG	npjohnson, theimpulson
30.	OnePlus 6	enchilada	LuK1337
31.	OnePlus 6T	fajita	EdwinMoq
32.	Razer Phone 2	aura	mikeioannina, npjohnson
33.	Samsung Galaxy Tab S5e (LTE)	gts4lv	bgcngm, LuK1337
34.	Samsung Galaxy Tab S5e (Wi-Fi)	gts4lvwifi	LuK1337, bgcngm
35.	SHIFT SHIFT6mq	axolotl	amartinz, joey
36.	Sony Xperia XA2	pioneer	LuK1337, Stricted, cdesai
37.	Sony Xperia XA2 Plus	voyager	LuK1337
38.	Sony Xperia XA2 Ultra	discovery	LuK1337
39.	Sony Xperia 10	kirin	LuK1337
40.	Sony Xperia 10 Plus	mermaid	LuK1337
41.	Xiaomi POCO F1	beryllium	bgcngm, warabhishek

More devices should be making the transition soon to LineageOS 19, so keep an eye on our front page as we will run regular stories on the same.

Generic Targets

Just like the previous year’s release, the LineageOS team supports the Android Virtual Device (AVD), i.e. the default emulator environment provided by Android Studio, as a build target. That evolution continues with LineageOS 19 supporting Android Automotive build targets as well. Developers can build Generic System Image (GSI) packages in both mobile and Android TV configurations too, although the official download portal will not host any such pre-compiled builds.

What if my device is not listed here?

Just because your device isn’t listed here does not mean that you can’t get to enjoy LineageOS 19 by now. Because of its open source nature, there are a number of unofficial builds for many devices on our forums, many of which will eventually end up becoming official builds as development progresses. What’s more: most of them are, by now, perfectly stable as daily drivers, with the occasional minor quirk.

LineageOS XDA Forums

---

How to upgrade to LineageOS 19 from an older version

If you’re not familiar with the process behind installing custom ROMs or, in general, modifying your phone, you’ll first need to unlock the bootloader of your device and install an updated custom recovery, such as LineageOS Recovery or TWRP, before attempting to do anything. Then, once official LineageOS 19 builds become available for your device, you’ll need to install them through the custom recovery environment. Device-specific instructions may vary, so do check out the corresponding wiki page beforehand.

As for Google apps, they don’t come pre-installed on an LineageOS release. You need to pick a suitable GApps distribution and install it yourself.

---

LineageOS 18.1 – Official builds for supported devices

While maintainers work towards bringing up devices to official LineageOS 19 based on Android 12, you can still find automated builds for these devices that are supported for LineageOS 18.1:

LineageOS 18.1 Official Build List. Tap/click to expand.

Placeholder

Much like LineageOS 19 builds, we should see more devices making their way onto the LineageOS 18.1 build roster.

---

Source: LineageOS Blog

Thanks Mishaal Rahman for the tip!

The post LineageOS 19 based on Android 12 is now officially available appeared first on XDA.

from XDA https://ift.tt/wI9rTiW
via IFTTT

Windows 11 build 22000.652 fixes long boot times, subtitles, and more

Microsoft has released this month’s optional cumulative update for Windows 11 users, bringing along a handful of significant fixes to the experience. The latest update brings the Windows 11 build number up to 22000.652, and it’s essentially the same update that was rolled out to Insiders in the Release Preview channel a couple of weeks ago, which was build 22000.651.

The new update is labeled as KB5012643, and you can download it manually here. While the changelog is mostly the same as build 22000.651, Microsoft does highlight a few particular fixes this time around. Most notably, there was an issue that could have prevented the minimize, maximize, and close buttons from working on a maximized app window, and that’s been fixed. Here’s the list of highlights:

• Updates an issue that might cause video subtitles to be partially cut off.
• Updates an issue that incorrectly aligns video subtitles.
• Displays the temperature on top of the weather icon on the taskbar.
• Updates an issue that prevents you from using the minimize, maximize, and close buttons on a maximized app window.

While it’s not mentioned by Microsoft in the highlights, Windows 11 build 22000.652 also addresses a problem where your PC might take upwards of 40 minutes to boot up, which was certainly a major problem to have in the first place. If you’ve experienced this, it shouldn’t be an issue after this update. Here’s the full list of changes:

• New! Adds improvements for servicing the Secure Boot component of Windows.
• Addresses an issue that causes the AppX Deployment Service (AppXSvc) to stop working after you install certain MSIX apps.
• Addresses a race condition that occurs early in the startup process that might cause a stop error.
• Improves the Autopilot client to process updated Trusted Platform Module (TPM) capabilities that support self-deployment and pre-provisioning scenarios.
• Changes the timeout for Azure Active Directory (Azure AD) registration from 60 minutes to 90 minutes for hybrid Azure AD-joined Autopilot scenarios. This also addresses a race condition that causes an exception at timeout.
• Addresses an issue in which certain Point of Sale terminals experience occasional OS startup delays during restart of up to 40 minutes.
• Addresses a memory leak issue that affects Windows systems that are in use 24 hours each day of the week.
• Addresses an issue that affects the Dynamic Host Configuration Protocol (DHCP) option 119 (Domain Search Option) by preventing the use of the connection-specific DNS Suffix Search List.
• Addresses an issue that affects the Title attribute in Microsoft Ege IE mode.
• Addresses an issue in which mobile device management (MDM) policies were not allowed on Windows Enterprise editions that were upgraded to Enterprise using Azure AD-joined subscription entitlement.
• Addresses an issue that might cause video subtitles to be partially cut off.
• Addresses an issue that incorrectly aligns video subtitles.
• Addresses an issue that causes Kerberos authentication to fail, and the error is “0xc0030009 (RPC_NT_NULL_REF_POINTER)”. This occurs when a client machine attempts to use the Remote Desktop Protocol (RDP) to connect to another machine while Remote Credential Guard is enabled.
• Addresses an issue that causes Windows to go into BitLocker recovery after a servicing update.
• Addresses an issue that prevents retrieval of the Endorsement Key (EK) certificate from the TPM device.
• Addresses an issue that might fail to copy the security portion of a Group Policy to a machine.
• Addresses an issue that prevents the instantiation of the Microsoft RDP Client Control, version 11 and higher, inside a Microsoft Foundation Class (MFC) dialog.
• Displays the temperature on top of the weather icon on the taskbar.
• Addresses an issue that prevents you from using the minimize, maximize, and close buttons on a maximized app window. This issue occurs because the Notification Center keeps the input focus.
• Addresses an issue that might occur when you use Netdom.exe or the Active Directory Domains and Trusts snap-in to list or modify name suffixes routing. These procedures might fail. The error message is, “Insufficient system resources exist to complete the requested service.” This issue occurs after installing the January 2022 security update on the primary domain controller emulator (PDCe).
• Addresses an issue that causes the primary domain controller (PDC) of the root domain to generate warning and error events in the System log. This issue occurs when the PDC incorrectly tries to scan outgoing-only trusts.
• Addresses an issue that occurs when you map a network drive to a Server Message Block version 1 (SMBv1) share. After restarting the OS, you cannot access that network drive.
• Addresses an issue that affects an SMB multichannel connection and might generate a 13A or C2 error.
• Addresses an issue that damages a pool when a Client-Side Caching (CSC) cleanup method fails to delete a resource that was created.
• Addresses an issue that might cause the server to lock up because the nonpaged pool grows and uses up all memory. After a restart, the same issue occurs again when you try to repair the damage.
• Reduces the overhead of resource contention in high input/output operations per second (IOPS) scenarios that have many threads contending on a single file.

If you want to get these fixes right now, you can download the build 22000.652 manually using the link above or simply go to the Windows Update page in the Settings app on Windows 11. Because the update is optional, it won’t install automatically, but you can check for updates and it will show up as an optional update that you can install right away. This should be the easiest way to do it.

If you’d rather wait, the fixes included in this update will also be rolled into next month’s patch Tuesday, when Microsoft rolls out a set of mandatory updates to all supported versions of Windows. Those should also include additional fixes or tweaks.

The post Windows 11 build 22000.652 fixes long boot times, subtitles, and more appeared first on XDA.

from XDA https://ift.tt/78zdMgU
via IFTTT

Windows 11 gets improvements for Auto HDR in games

Microsoft has announced a series of improvements to the Auto HDR feature for games on Windows 11. With the latest updates to the Xbox Game Bar app, you can now adjust the intensity of the HDR effect, quickly enable or disable it, and more. Some of the new features are available to everyone right now, while others are only available to Insiders.

If you’re not aware, Auto HDR is a feature that allows games that don’t natively support HDR to benefit from HDR-capable monitors. It was introduced with Windows 11, and it’s one of the big highlights for gaming on the new OS. Of course, if a game natively supports HDR; it won’t be affected by this feature.

The most noteworthy of the new features coming to Auto HDR is a new intensity slider available in the Xbox Game Bar interface. With this slider, you can adjust how bright or dim you want the colors to be in your game. It’s a simple slider, with the lowest level being equivalent to turning Auto HDR off, and the highest level offering the most intense colors. Auto HDR intensity is saved for each game, so you can have different levels for different games and not worry about having to switch between levels every time you launch one of those titles. This option can be found in the Game Bar settings, under the Gaming features section.

Also in this section is a new option to disable or enable Auto HDR altogether. Previously, this option was only available in the Windows11 Settings app itself, but now it’s a little easier to access in the middle of a game, which is a welcome change.

Those two features are available to all Windows 11 users right now, but if you’re a Windows Insider, you also have a couple more. First off, Microsoft is working on adding multi-GPU support for Auto HDR games, such as systems using NVIDIA’s SLI or AMD CrossFire technology. This should enable you to use Auto HDR in more games running in a setup like this.

The last of the features is more of a convenience thing, and it has to do with notifications. If you’ve been bothered by the excessive number of notifications from Auto HDR while gaming, the feature is registered in the Windows 11 notifications settings (Settings -> System -> Notifications). That means you can disable notifications altogether or tweak them to your preference so you won’t be bothered by them anymore.

These are welcome additions, but we’re also still waiting on another big HDR improvement Microsoft announced a few months ago. The company is working on an HDR Calibration app for Windows 11, similar to what’s available on Xbox, to make the experience work as well as possible on all different kinds of monitors. That should be major news for some users, so hopefully we’ll hear more about that in the near future.

---

Source: Microsoft

The post Windows 11 gets improvements for Auto HDR in games appeared first on XDA.

from XDA https://ift.tt/E3YXfUl
via IFTTT

Steam Deck gets a huge update with new lock screen, uncapped frame rate and much more

Valve has continued its red hot pace with Steam Deck updates and the latest one is a big one. Pushing out now to owners through the stable channel, it adds some really interesting new features to the mix along with the usual fixes and improvements.

Top of the order is the new lock screen. Valve is calling this “The Lock Screen Update” on its blog, and it’s a nice addition. It’s simple enough in execution, doing exactly what it implies. When enabled in settings it gives you a six-character PIN code to lock the device with in three pre-determined scenarios. For me, it means I can put it down and be sure my kids haven’t bought Crash Bandicoot when I come back to it.

The lock screen isn’t the only hot new feature pushing out, though. An uncapped frame rate has been in testing in the beta channel for a little while now, and it’s made it into this build. This has a limited use case, as in, it’s pretty useless on the handheld’s display, but you can now go beyond the 60 FPS lock and let the Steam Deck rip. The new option is found on the FPS slider in the quick access menu.

The fun doesn’t stop there, either. Other headline features added in this latest update include more localized keyboards, an overhaul of the achievements page, and proper multi-window support. This means that apps and games that have more than one window, such as a web browser or those pesky game launchers, will now work better. Launchers have been a pretty irritating roadblock at times on the Steam Deck, so it’s nice to see Valve has fixed it when it’s clear the games won’t be updated. Switching between them is simple enough, each window is listed in the left-hand menu behind the Steam button.

Folks interested in running Windows on their Steam Decks will also be pleased to hear Valve has added fTPM support for Windows 11. So if you really want to, it’s now easier than ever. There are also a number of quality of life improvements, from the charging LED dimming so it’s less annoying at night, to warnings if you’re not using a good enough power adapter.

The full patch notes are extensive, so grab a beverage and take your time to digest them. This is one of the biggest patches yet for the Steam Deck in its young life and it keeps getting better with each one.

Source: Valve

The post Steam Deck gets a huge update with new lock screen, uncapped frame rate and much more appeared first on XDA.

from XDA https://ift.tt/wiS5KDr
via IFTTT

OnePlus 10 Pro update brings optimizations for fingerprint unlocking, power consumption, audio processing, and more

After rolling out OxygenOS A.11 to its flagship OnePlus 10 Pro earlier this month, OnePlus is now rolling out another update with various optimizations and bug fixes. The latest update, OxygenOS A.13, has started rolling out to users in India and NA, and it should reach all devices over the next few days.

According to a recent post on the OnePlus Community forums, OxygenOS A.13 for the OnePlus 10 Pro packs optimizations for the fingerprint algorithm, which improves the success rate of fingerprint unlocking. It also optimizes power consumption in some scenarios, improves audio processing for better communication quality, and fixes an occasional bug that prevents the phone from turning on automatically at a set time.

Credit: anujthakurece

In addition, OxygenOS A.13 for the OnePlus 10 Pro optimizes the camera quality for the device’s 32MP selfie shooter and improves network stability. Unfortunately, it doesn’t include the Android security patches for April 2022, and the device is still stuck on the March 2022 patches. In contrast, Samsung has already started rolling out the May 2022 security patches to its flagship Galaxy S22 lineup. You can check out the complete changelog in the section below.

• System
  • [Optimized] fingerprint algorithm, improved the success rate of fingerprint unlocking
  • [Optimized] the power consumption in some scenarios, improved user experience
  • [Optimized] audio processing, improved communication quality
  • [Fixed] the occasional issue that the phone may fail to turn on automatically at a set time
  • [Improved] system stability
• Camera
  • [Optimized] the quality of taking photos with the front camera
• Network
  • [Optimized] network stability

As always, OxygenOS A.13 is rolling out in a phased manner. It will reach a small percentage of OnePlus 10 Pro users today, with a broader rollout to follow in a few days. If you haven’t received the update on your device, you can check for it manually by heading to the software updates section in the device settings. Alternatively, you can download the firmware package from the link below and flash the update manually.

Download OxygenOS A.13 for the OnePlus 10 Pro

We only have access to the OxygenOS A.13 full OTA for the India region at the moment. We’ll update this post with the incremental and full OTA releases for the other regions as soon as they become available.

• OnePlus 10 Pro
  • India
    • Full OTA

---

Source: OnePlus Community forums

Thanks to XDA Recognized Developer mlgmxyysd for the download link!

The post OnePlus 10 Pro update brings optimizations for fingerprint unlocking, power consumption, audio processing, and more appeared first on XDA.

from XDA https://ift.tt/Un3TOjR
via IFTTT

Realme Narzo 50A Prime is the first phone from the company to ship without a charging brick

Realme has added another model to the Narzo 50 series. Today, the company unveiled the Realme Narzo 50A Prime in India, a budget-friendly smartphone that offers a good-looking design, a large battery, and a 50MP primary camera. It’s also the first smartphone from the company to ship without a charging brick.

Realme Narzo 50A Prime: Specifications

Specification	Realme Narzo 50A Prime
Dimensions and Weight	164.4 x 75.6 x 8.1mm 189g
Display	6.6-inch LCD FHD+ (2408 x 1080) 60Hz refresh rate 600nits peak brightness
SoC	Unisoc T612 2 x Cortex-A75 @1.8GHz and 6 x Cortex-A55 @ 1.8GHz 12nm Mali-G57
RAM and Storage	4GB/6GB RAM 64GB/128GB flash storage MicroSD card support
Battery & Charging	5,000 mAh battery 18W fast charging support (charger not included)
Rear Camera	Primary: 50MP f/1.8 Secondary: 2MP macro Tertiary: B&W sensor
Front Camera	8MP
Ports	USB Type-C port 3.5mm headphone jack
Connectivity	4G LTE Bluetooth 5.0 Type-C port WiFi 802.11.b/g/n/ac (2.4GHz + 5GHz)
Security	Side-mounted fingerprint reader
Software	Realme UI R Edition based on Android 11

The Reale Narzo 50A Prime appears to be a cheaper version of the Narzo 50A. In some way, it’s better than the 50A. For example, it features a 6.6-inch FHD+ LCD compared to the HD+ panel on the 50A and has a side-mounted fingerprint scanner instead of the awkwardly-positioned rear-mounted fingerprint scanner of the previous model.

Under the hood, the Realme Narzo 50A Prime packs a Unisoc T612 SoC, paired with 4GB/6GB RAM and 64GB/128GB UFS 2.2 storage. On the back, you get a triple camera setup, consisting of a 50MP main camera, a 2MP macro shooter, and a Black and White camera.

The Realme Narzo 50A Prime features a 5,000mAh battery with 18W fast charging support. As previously confirmed by the company, the Narzo 50A Prime doesn’t come with a charger inside the box, making it the first Realme phone to ship without a charging brick. On the software side, it runs Android 11 out of the box with Realme UI R Edition on top.

Pricing & Availability

The Realme Narzo 50A Prime is priced at ₹11,499 for the base model while the top variant with 6GB RAM and 128GB will set you back ₹12,499. Available in Flash Blue and Flash Black colors, the phone will go on sale via realme.com, Amazon India, and leading retail stores across India starting April 28.

The post Realme Narzo 50A Prime is the first phone from the company to ship without a charging brick appeared first on XDA.

from XDA https://ift.tt/FpVjKxA
via IFTTT