Android 10 custom ROMs are available for the OnePlus 3/3T, Xiaomi Mi Pad 4 & Mi 6X, Huawei P Smart 2018, Samsung Galaxy A70, and Sony Xperia XA2 Ultra

Google released the Android 10 source code early last month, shortly after it rolled out stable Android 10 to the Pixel lineup. Since then, several devices have received Android 10-based custom ROMs, including the Xiaomi Redmi 2, Moto G 2015, Sony Xperia Z3 Compact, HTC 10, HTC One M8, Realme 3 Pro, Samsung Galaxy S7, Xiaomi Mi A2 Lite, Lenovo ZUK Z1, and Sony Xperia XA2. Most recently, the Xiaomi Mi A3, Moto G5S Plus, LeEco Le 2, Lenovo Vibe K5 Plus, Samsung Galaxy A5 and Huawei Mediapad M3 Lite got a taste of Android 10. And now, six more devices, including the OnePlus 3/3T, Xiaomi Mi Pad 4 & Mi 6X, Huawei P Smart 2018, Samsung Galaxy A70, and Sony Xperia XA2 Ultra, have joined the list.

OnePlus 3/3T

While OnePlus still plans to roll out Android 10 to the OnePlus 5 and OnePlus 5T, their predecessors won’t be getting the same treatment. Thankfully though, you now have three Android 10-based custom ROMs for the OnePlus 3 and OnePlus 3T. There’s, of course, an experimental build of LineageOS 17.0 for both the devices, along with a stable beta for the MSM Xtended XQ Release v2 and the Nitrogen OS beta. If you happen to have a OnePlus 3/3T lying around, you can try these custom ROMs on your phone by following the links below.

LineageOS 17.0 for the OnePlus 3/3T

MSM Xtended XQ Release 2 for the OnePlus 3/3T

Nitrogen OS Beta for the OnePlus 3/3T

OnePlus 3 XDA Forums || OnePlus 3T XDA Forums

Xiaomi Mi Pad 4/ Mi Pad 4 Plus

The Xiaomi Mi Pad 4 from last year has also received a LineageOS build based on Android 10. While the ROM is currently a beta release, it doesn’t seem to have any known issues. Try it out on your Mi Pad 4 by downloading it from the link below. Just make sure you flash TWRP v3.3.1 before flashing the ROM on your device.

LineageOS 17.0 for the Xiaomi Mi Pad 4/Plus

Xiaomi Mi Pad 4 XDA Forums

Xiaomi Mi 6X

The Xiaomi Mi 6X, which was launched under the Mi A2 moniker in some markets, has also received a LineageOS 17.0 ROM based on Android 10. The ROM works on both the Mi 6X and the Mi A2, but once again, you’ll need to flash TWRP v3.3.1 on your device before flashing the ROM.

LineageOS 17.0 for the Xiaomi Mi 6X

Xiaomi Mi A2 XDA Forums

Huawei P Smart 2018

The Huawei P Smart 2018, also known as the Huawei Enjoy 7S in China, has received an Android 10 AOSP custom ROM, with which you can enjoy a stock Android experience on your Huawei device. Before you go ahead and flash this ROM though, it’s worth noting that you might encounter some issues with the fingerprint scanner.

AOSP 10.0 for the Huawei P Smart 2018

Huawei P Smart XDA Forums

Samsung Galaxy A70

Samsung’s Galaxy A70 from earlier this year has also received a LineageOS 17.0 build based on Android 10. However, since the ROM is a beta release, it has a number of known issues. For instance, the VoLTE and VoWiFi are not working, the camera only offers an 8MP resolution, the camera preview is broken for 4:3 aspect ratio, and more. So I’d advise you not to flash this ROM on your daily driver in its current state.

LineageOS 17.0 for the Samsung Galaxy A70

Samsung Galaxy A70 XDA Forums

Sony Xperia XA2 Ultra

The Sony Xperia XA2 Ultra now also has an unofficial LineageOS 17.0 build based on Android 10. There are some minor issues in the current version of the ROM, but for the most part the ROM is good enough for day to day use. Try it out on your XA2 Ultra by following the link below.

LineageOS 17.0 for the Sony Xperia XA2 Ultra

Sony Xperia XA2 Ultra XDA Forums

The post Android 10 custom ROMs are available for the OnePlus 3/3T, Xiaomi Mi Pad 4 & Mi 6X, Huawei P Smart 2018, Samsung Galaxy A70, and Sony Xperia XA2 Ultra appeared first on xda-developers.

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

ASUS drops plans to update the ZenFone 4 to Android Pie

Taiwanese smartphone manufacturer Asus launched the ZenFone 4 back in late 2017, running Android Nougat out of the box. The device was then updated to Android Oreo shortly thereafter. Earlier this year, to the joy of ZenFone 4 owners worldwide, the company rolled out an Android Pie beta update for the device. However, the joy was shortlived, as Asus has now officially dropped plans for the Android Pie update.

As reported by Android Police, the Asus ZenFone 4 won’t be getting an official Android Pie update after all. In a recent post on the company’s ZenTalk forums, the company has revealed that in order to “preserve the system performance and stability of ZenFone 4(ZE554KL), ASUS does not have plans to further upgrade Android 9 (Pie), but will continue to maintain in Android Oreo.” 

Asus further noted that users could still install the last Android Pie beta release on their devices, however, the company would not support the release with routine updates. This news was met with strong criticism from the community, with users vouching to never buy another smartphone from the company.

The ZenFone 4 is the mid-range option in the company’s lineup for 2017. It features Qualcomm’s Snapdragon 630 Soc, 4GB of RAM, 64GB of storage, and a 5.5-inch FHD display. The device has two cameras on the back (12MP + 8MP wide-angle), and an 8MP selfie shooter. The device is backed by a 3,300mAh battery. The device was launched alongside the ZenFone 4 Pro and the ZenFone 4 Max. As of now, we have no information on the company’s plans to release updates for the other two devices.

---

Source: Asus

Via: Android Police

The post ASUS drops plans to update the ZenFone 4 to Android Pie appeared first on xda-developers.

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

Google Camera 7.2 mod brings Astrophotography, Super Res Zoom, and more to older Pixel phones

The Google Pixel 4 has only just launched, and we’re already getting new Google Camera ports with added features that previously weren’t available. One such feature that people really love is the new Astrophotography shooting mode, which is great for picking up stars and other cosmic activity with just your smartphone and a steady surface. We tested it a little while ago, which you can read more about here. A modification of Google Camera 7.2 has brought Super Res Zoom and the aforementioned Astrophotography mode to older Pixel smartphones. It was specifically tested on the Google Pixel 2, though should be universal for older Pixel smartphones. You can check out the changelog below from XDA Senior Member cstark27.

• Enable Astro mode for Pixel 1 & 2
• Enable Focus options in Night Sight (along with “infinity” – may be same as far)
• Modded lib for Learned Depth in Portrait Mode (Pixel 2)
• Enable Super Res Zoom while zoomed or in Night Sight (no zoom required) – this is like Pixel 3 stock
• Enable auto timer (photobooth), it’s in the selfie camera in the Timer options
• Enable synthetic fill flash for Pixel 2 and enable SFF in Camera mode for 3a

Generally speaking, features from newer Pixels have had to be ported to older Pixels before we’ve seen them ported to other devices too. Google Camera ports have been an extremely popular way to improve the camera on basically any device, largely in thanks to a number of unique features and enhanced photo quality over many stock camera applications. Features like Night Sight have been near-revolutionary when it comes to photo-taking, and these are the features that users typically want to be ported for their smartphone. If you don’t own a Pixel, this port won’t work just yet. We recommend checking out the XDA forums for your device to see if a Google Camera port is available.

If you do own an older Pixel smartphone, you can check out cstark27’s thread below to download the modified Google Camera 7.2 APK which has both Astrophotography and Super Res Zoom.

Download Google Camera 7.2 mod for older Pixel smartphones

The post Google Camera 7.2 mod brings Astrophotography, Super Res Zoom, and more to older Pixel phones appeared first on xda-developers.

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

Huawei launches the Mate X foldable smartphone in China, teases the Kirin 990 Mate Xs for 2020

Earlier this year in February, we first got our first look at Huawei’s foldable smartphone — the Huawei Mate X. Revealed shortly after the Samsung Galaxy Fold, Huawei’s next-gen device took a slightly different approach and wowed enthusiasts worldwide. However, following the Galaxy Fold fiasco, Huawei has delayed its launch a fair few times. The device has even received some design changes in the past few months and the company has even upgraded its specifications since the original announcement. Now, it seems like the Huawei Mate X is finally ready for prime time, as it has officially been launched in China.

As reported by GSMArena, the Mate X was launched at a recent event in Shenzhen, China alongside the Mate 30 5G and the Mate 30 Pro 5G. The device has been priced at 16,999 Yuan (~$2,400) and is expected to hit the shelves on November 15. At the event, the company also announced the Mate Xs — a slightly upgraded version of the Mate X. While the Mate Xs seems to be identical to the regular Mate X on the outside, it features Huawei’s new flagship Kirin 990 5G SoC.

The newer and more powerful chipset from the company is built on the 7nm+ EUV process. The chip comes with an integrated 5G modem, as opposed to the external one used in the original Mate X. The chipset also packs in a more powerful NPU, in addition to overclocked Cortex A76 and A55 cores. While the Mali-G76 GPU remains the same as the Kirin 980, it now has six more cores, resulting in a total of 16 cores.

If you’re interested in purchasing the newer Huawei Mate Xs though, you’ll have to wait quite a while as Huawei has scheduled its launch for March 2020. It’s also worth noting that other than its chipset, we have no further information on the specifications of the Mate Xs, but we expect to learn more over the next couple of months.

---

Source: Droidholic

Via: GSMArena

The post Huawei launches the Mate X foldable smartphone in China, teases the Kirin 990 Mate Xs for 2020 appeared first on xda-developers.

from xda-developers https://ift.tt/340revJ
via IFTTT

Google Pixel 4 and Pixel 4 XL factory images and kernel source code are now available

Google launched the Pixel 4 and Pixel 4 XL about ten days ago at an event in New York. Thanks to the plethora of leaks around the phone, there weren’t many surprises to the phones. The Pixel 4 series was also slated to reach consumers from October 24, 2019, onwards. Between the extensive leaks and the time lag between pre-orders at launch and actual availability, we did admittedly get the feeling that the Pixel 4 has been around for much longer, and that too, without a factory image or kernel source code release. That is not the case though, as Google has released the factory images and the kernel source code for the Pixel 4 and the Pixel 4 XL right alongside its public availability.

Google Pixel 4 XDA Forums || Google Pixel 4 XL XDA Forums

Factory Images for Google Pixel 4 and Google Pixel 4 XL

Factory images are important for devices as they make experimenting with the software easier on the mind, as you know that you have an option to get back to a working device in case things go wrong (which they often will). Even for those who do have not purchased the phone, the factory images give access to the Pixel 4’s apps and other system files, which aid in porting over exclusive features to other devices.

Device	Version	Download Link
Google Pixel 4 “flame”	Android 10.0.0, build QD1A.190821.007, Oct 2019 Security Patch	Link
Google Pixel 4 XL “coral”	Android 10.0.0, build QD1A.190821.007, Oct 2019 Security Patch	Link

You can also find two older builds on the main download page.

Framework and Kernel Source Code

The framework sources, the kernel sources and the device tree for the new Pixels have also been uploaded. The framework sources will allow developers to peek into some of the decisions that Google has made with the Pixel 4’s software, such as why the PIxel 4’s 90Hz refresh rate is limited to high brightnesses only when used alongside the dynamic switching option. The kernel source code and device tree will be useful for custom kernel, recovery and ROM developers in order to kickstart third-party development efforts on the phone.

Framework and Device Tree for the Google Pixel 4

Kernel Sources for the Google Pixel 4

The post Google Pixel 4 and Pixel 4 XL factory images and kernel source code are now available appeared first on xda-developers.

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

Google Messages 5.2 adds chat reminders and prepares to support bubble notifications and suggested stickers

Google tests a number of features on its apps before they’re released to the stable or beta channel. If these features are implemented but made inaccessible, we are sometimes able to enable them before public release. And more often than not, these features gradually make their way to the stable channel. We’ve previously discovered features like Instagram-style effects, verified SMS and SMS reminders in the Google Messages app. Now, Google is finally rolling out SMS reminders with the latest stable update.

As reported by AndroidPolice, Google Messages version 5.2 has now officially enabled chat reminders for all users. This new feature will let you set a reminder for any chat if you wish to go back to them sometime later. To set a reminder you just need to tap and hold on the chat to reveal the new reminder icon in the top right corner. Tapping on the icon will bring up a new context menu, which will let you set a reminder for one hour, the next morning, noon, or night. The feature also lets you choose a specific date and time for the reminder in case none of the default options work for you.

Once the reminder is set, you’ll notice a clock icon to the right of the chat. You can edit or remove the reminder by opening the conversation. When the time is up, you’ll receive a new notification of the last message in the chat. You can either tap to open it or delay it by an hour from the notification itself.

Additionally, recent tweets from Jane Manchun Wong reveal that Google Messages is also prepping up to add support for Android’s new Bubbles API which is currently in Developer Preview in Android 10. While we’ve previously seen this feature in action, it’s set to go live with Android 11 next year.

Google Messages to implement bubble notifications for Android 10 pic.twitter.com/St8ejZrKAU

— Jane Manchun Wong (@wongmjane) October 24, 2019

Furthermore, Wong also discovered that Google is testing a new Suggested stickers toggle within the Messages settings. When enabled, this feature will bring up intelligent sticker suggestions within a conversation.

Google Messages is testing “Suggested stickers” toggle setting pic.twitter.com/QtKXoQDBpw

— Jane Manchun Wong (@wongmjane) October 24, 2019

As of now, Google Messages 5.2 is slowly rolling out to users via the Play Store. If you have the app installed on your phone already, you should receive the update notification soon. In case you don’t, you can download the latest version available on the Play Store from the link below.

Messages (Free, Google Play) →

---

Source: Android Police

The post Google Messages 5.2 adds chat reminders and prepares to support bubble notifications and suggested stickers appeared first on xda-developers.

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

Why Google Limits 90Hz on the Pixel 4 to High Brightnesses

Just recently, a keen Reddit user figured out that the 90Hz “Smooth Display” on the Google Pixel 4 only stays at 90Hz during high brightness levels. Many early Pixel 4 adopters were able to notice that the display did not seem to stick to 90Hz very often, and this system behavior seems to have been the reason why. Naturally, some users were outraged about the matter, and some were curious about why Google would implement one of their products’ biggest features in this peculiar way. Many people believed the reason had to do with battery life, but that didn’t really make any sense — why would 90Hz be limited to higher brightness, when battery consumption is more of an issue? While digging through the updated Android 10 source code release coinciding with Pixel 4 launch day, XDA’s Editor-in-Chief Mishaal Rahman found a commit that explains the official reason why Google enabled this behavior:

 

Google says the reason they limit 90Hz to higher brightnesses on the Pixel 4 is that screen flicker may be visible when the display and ambient brightness are low, due to hardware limitation. This hardware limitation is related to the panels’ pulse-width modulation (PWM), which is how display brightness is primarily controlled for OLED displays. Google expands that their displays have different gamma curves for different refresh rates (which is true for most displays) and that it is difficult to match the brightness between the two calibrations. Since the display brightness is controlled by PWM, which flickers the screen on-and-off in very fast succession, the different calibration curves could ever-so-slightly alter the PWM “pattern,” and that could introduce a noticeable “flicker” upon switching between 90Hz and 60Hz.

Google’s Smooth Display system keeps the display at 60Hz whenever the screen is idle or displaying animation/video that is 60fps or less, and immediately switches back to 90Hz as soon as you touch the display or an on-screen animation (like a notification) occurs, so it switches between 90Hz and 60Hz very often — a slight flicker upon every switch may indeed become annoying. This seems to only be an issue at lower brightness because that is when the PWM pulses are shorter and more prone to its flicker being noticeable. No flicker issues are present with the “Force 90Hz” option in the developer options since that does not switch between the two refresh rates.

Furthermore, Google claims that human eyes are more sensitive to the flicker in darker viewing environments, which is suggested through some studies. This is the reason why Google allows the display to switch to 90Hz at lower display brightness levels, even though flicker may be visible, because the flicker may not be as apparent in a brighter environment.

Google released a statement to The Verge that the company “constantly assess whether these parameters lead to the best overall user experience,” and that they have “previously planned updates that [they’ll] roll out in the coming weeks that include enabling 90hz in more brightness conditions.” Hopefully, Google can improve the tuning, and perhaps provide an option to completely disable their brightness-conditioned throttling so we can still enjoy some of the battery savings from their “smart” switching.

Google Pixel 4 Forums ||| Google Pixel 4 XL Forums

The post Why Google Limits 90Hz on the Pixel 4 to High Brightnesses appeared first on xda-developers.

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