TWRP 3.5.0 released with support for devices that launched with Android 10

One of the most common reasons that users come to our forums is to flash custom mods, kernels, or ROMs. But none of these aftermarket development efforts are feasible without having the means to install them. That’s where the incredibly popular Team Win Recovery Project, or TWRP for short, comes in. Available on a plethora of Android-powered devices, TWRP has been the go-to custom recovery for anyone looking to modify the software on their device. And now, the project has been bumped to version 3.5.0, bringing many improvements in decryption, bug fixes, and support with devices that launched with Android 10.

The full changelog for the new major version of TWRP can be found below, but for regular users and developers, the most important change will be Android 10 compatibility. Till TWRP 3.4.0, support for dynamic/logical partitions and many other changes introduced in AOSP 10 hadn’t been fully implemented. Most of the limitations are no longer present in TWRP 3.5.0, which means devices that are released with Android 10 out of the box can finally install official TWRP builds when available. XDA Recognized Developer Captain_Throwback worked with XDA Recognized Developer mauronofrio, XDA Senior Member noahajac, and AndroidableDroid to make this possible by rewriting a significant portion of the TWRP codebase from scratch.

Going forward, TWRP maintainers will be presented with two separate branches while porting the custom recovery: Devices that are released with Android 10 will be supported under the android-10 branch, while legacy devices will be built out of the android-9.0 branch. Moreover, two lead TWRP team members, XDA Senior Recognized Developer Dees_Troy and bigbiff, are already working on an Android 11 release, with the Google Pixel 5 bring up slated for the near future.

Here’s the full changelog for the update:

TWRP 3.5.0 Changelog

• Android 9
  • Fix building in android-5.1 trees – CaptainThrowback
  • New QTI Haptics Support – AndroidableDroid
  • New TSPDriver Haptics Support – LameMonster82
  • Selinux restore issues – AndroidableDroid
  • OEM build fixes – Fighter19
  • More file extension support in Gui file selector – Mauronofrio
  • FBE Fixes – CaptainThrowback
  • Ozip Decryption – Mauronofrio
  • Don’t use persist for recovery logs – bigbiff
  • Delay touch startup if necessary – bigbiff
  • Spanish translation Updates – R0rt1z2
  • Fix cache wiping on Slot A only devices – AndroidableDroid
  • Exclude dumpsys directory from backups – DarthJabba9
  • Gerrman translation Updates – 4ndyZ
  • HW Rotation during runtime (does not affect touch panel) – webgeek1234
  • API 24 fixes – AndroidableDroid
  • vold_decrypt error on unmount – CaptainThrowback
  • Multiuser – warn when users are not decrypted – noahajac
  • FDE encryption fixes – CaptainThrowback
  • Crypto state fixes – nebrassy
  • Chinese translation Updates – Whyle
  • Theme updates to match android-10 release: CaptainThrowback
  • Move TWRP App install to Advanced page – Dees_Troy
  • Update Russian Translation – f2065
• Android 10
  • You can see the list of changes at Github

You can download the latest build of the custom recovery for your device from the official website linked below. For now, version 3.5.0 will be built for only Android 9 Pie and Android 10-based devices, so if your device is currently being maintained, then you should see an update in a few hours or days. Be sure to check the XDA forum for your device as the TWRP maintainer for your device may post updates when the build goes live.

Download TWRP for your device

In case you want to download the latest version of TWRP right from your device, you should check out the official TWRP app from Google Play.

Official TWRP App (Free⁺, Google Play) →

The post TWRP 3.5.0 released with support for devices that launched with Android 10 appeared first on xda-developers.

from xda-developers https://ift.tt/34VN46A
via IFTTT

TWRP 3.5.0 released with support for devices that launched with Android 10

One of the most common reasons that users come to our forums is to flash custom mods, kernels, or ROMs. But none of these aftermarket development efforts are feasible without having the means to install them. That’s where the incredibly popular Team Win Recovery Project, or TWRP for short, comes in. Available on a plethora of Android-powered devices, TWRP has been the go-to custom recovery for anyone looking to modify the software on their device. And now, the project has been bumped to version 3.5.0, bringing many improvements in decryption, bug fixes, and support with devices that launched with Android 10.

The full changelog for the new major version of TWRP can be found below, but for regular users and developers, the most important change will be Android 10 compatibility. Till TWRP 3.4.0, support for dynamic/logical partitions and many other changes introduced in AOSP 10 hadn’t been fully implemented. Most of the limitations are no longer present in TWRP 3.5.0, which means devices that are released with Android 10 out of the box can finally install official TWRP builds when available. XDA Recognized Developer Captain_Throwback worked with XDA Recognized Developer mauronofrio, XDA Senior Member noahajac, and AndroidableDroid to make this possible by rewriting a significant portion of the TWRP codebase from scratch.

Going forward, TWRP maintainers will be presented with two separate branches while porting the custom recovery: Devices that are released with Android 10 will be supported under the android-10 branch, while legacy devices will be built out of the android-9.0 branch. Moreover, two lead TWRP team members, XDA Senior Recognized Developer Dees_Troy and bigbiff, are already working on an Android 11 release, with the Google Pixel 5 bring up slated for the near future.

Here’s the full changelog for the update:

TWRP 3.5.0 Changelog

• Android 9
  • Fix building in android-5.1 trees – CaptainThrowback
  • New QTI Haptics Support – AndroidableDroid
  • New TSPDriver Haptics Support – LameMonster82
  • Selinux restore issues – AndroidableDroid
  • OEM build fixes – Fighter19
  • More file extension support in Gui file selector – Mauronofrio
  • FBE Fixes – CaptainThrowback
  • Ozip Decryption – Mauronofrio
  • Don’t use persist for recovery logs – bigbiff
  • Delay touch startup if necessary – bigbiff
  • Spanish translation Updates – R0rt1z2
  • Fix cache wiping on Slot A only devices – AndroidableDroid
  • Exclude dumpsys directory from backups – DarthJabba9
  • Gerrman translation Updates – 4ndyZ
  • HW Rotation during runtime (does not affect touch panel) – webgeek1234
  • API 24 fixes – AndroidableDroid
  • vold_decrypt error on unmount – CaptainThrowback
  • Multiuser – warn when users are not decrypted – noahajac
  • FDE encryption fixes – CaptainThrowback
  • Crypto state fixes – nebrassy
  • Chinese translation Updates – Whyle
  • Theme updates to match android-10 release: CaptainThrowback
  • Move TWRP App install to Advanced page – Dees_Troy
  • Update Russian Translation – f2065
• Android 10
  • You can see the list of changes at Github

You can download the latest build of the custom recovery for your device from the official website linked below. For now, version 3.5.0 will be built for only Android 9 Pie and Android 10-based devices, so if your device is currently being maintained, then you should see an update in a few hours or days. Be sure to check the XDA forum for your device as the TWRP maintainer for your device may post updates when the build goes live.

Download TWRP for your device

In case you want to download the latest version of TWRP right from your device, you should check out the official TWRP app from Google Play.

Official TWRP App (Free⁺, Google Play) →

The post TWRP 3.5.0 released with support for devices that launched with Android 10 appeared first on xda-developers.

from xda-developers https://ift.tt/34VN46A
via IFTTT

Amazon acquires the Wondery podcast network to compete with Spotify

Amazon is the second most valued company in the US. Besides the online and offline retail and logistics business, it has a plethora of entertainment services under one umbrella. Some of these services include established brand names such as Audible, Kindle, Amazon Music, Prime Video, and Prime Music. And now, popular podcast network Wondery is joining the list with the announcement of its acquisition by Amazon.

Wondery is one of the top five podcast publishers in the US and is home to noted podcast shows such as Dr. Death and Dirty John. As per the blog post announcement, content from Wondery will be available on Amazon Music, which received support for podcasts in September 2020. Amazon notes that after this deal, the existing Wondery shows will continue to be available on all of the existing platforms and not restricted to Amazon Music exclusively. This means if you are a user, you can access shows on Spotify, Apple Music, and a whole lot of other podcast streaming services.

The blog notes that the deal completion awaits “customary closing conditions.” Until then, nothing changes in terms of how the platform works. Moreover, there is no clear information on what happens to the existing Wonder+ subscribers once the deal concludes. Meanwhile, Ben Mullin of The Wall Street Journal reports that once the deal goes through, Wondery CEO Hernan Lopez will step down from their existing role and COO Jen Sargent will be filling the position.

While the conditions of the deal have not been made public, previous reports from Bloomberg and The Wall Street Journal suggest Wondery was valued at a minimum of $300 million. Before Amazon, Apple and Sony were also reportedly in talks to acquire the company.

While Amazon joined the podcast clan late, this deal is expected to put Amazon Music on the same level as competitors such as Apple Music and especially Spotify, which has signed exclusive deals with major creators such as Joe Rogan.

The post Amazon acquires the Wondery podcast network to compete with Spotify appeared first on xda-developers.

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

How to enable the Pixel 5’s Adaptive Sound feature on older Pixel phones

Google rolled out the fifth Pixel Feature Drop earlier this month, which brought a host of new features to both old and new Pixel phones. Some older Pixel phones gained features like Hold for Me and Extreme Battery Saver, while only Google’s latest Pixel 4a 5G and Pixel 5 got support for the new Adaptive Sound feature. The Adaptive Sound feature is designed to improve the phone’s audio output by tweaking its equalizer based on your surroundings, and thanks to XDA Recognized Developer Freak07, there’s a way to enable this feature on older Pixel devices. If you’re interested in trying it out on your phone, here’s what you need to do:

Enable Adaptive Sound on older Pixel devices (with root)

On rooted Pixel devices, you can enable the Adaptive Sound feature by following a couple of simple steps, and it will remain enabled even after your reboot your device. To do so, you’ll first need to download the Pixel 5-specific version of the Device Personalization Services app from APK Mirror and install it on your device. Yes, you will already have the Device Personalization Services app installed, but the version of the app that Google pushed to your phone doesn’t include the Adaptive Sound feature. Hence, you’ll need to grab the one that Google made for the Pixel 4a 5G and Pixel 5. You can download that version of the app by clicking this link.

Once you have the app installed, you’ll need to download and install the Adaptive_Audio_Settings_Enabler Magisk module from the Magisk Manager app and restart your device. Alternatively, you can download the module by following this link and flash it manually. A few moments after a successful reboot, you should see the Adaptive Sound option in device settings.

Enable Adaptive Sound on older Pixel devices (without root)

On non-rooted Pixel devices, the process to enable Adaptive Sound is a bit more complicated as you have to execute a couple of shell commands. But before you get to that, you have to install the Pixel 5-specific version of the Device Personalization Services from APK Mirror and install it on your device. You can get the app by following this link.

Once you have the app installed, make sure you have USB Debugging enabled on your device. You can do so by heading over to Developer Options and tapping on the toggle next to the USB Debugging setting. You’ll also need to ensure that you have a working ADB environment on your PC (we have a tutorial on that here). After you’ve done that, you’ll need to connect your phone to your PC and execute the following 3 commands one-by-one:

adb shell
device_config put device_personalization_services AdaptiveAudio__enable_adaptive_audio true
device_config put device_personalization_services AdaptiveAudio__show_promo_notification true

After you execute these three commands, you should see the Adaptive Sound option in the device settings. Unlike the method for rooted devices, though, this method doesn’t enable the Adaptive Sound option permanently, and it’s removed once you reboot your device. So, make sure you don’t reboot your device after following the aforementioned steps, or you’ll have to go through it once again.

Enable Adaptive Sound on older Pixel devices XDA Forums thread

The post How to enable the Pixel 5’s Adaptive Sound feature on older Pixel phones appeared first on xda-developers.

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

An Update on XDA Labs

It was five years ago that we launched XDA Labs after hundreds of hours of development. The primary purpose was to create an alternate app distribution platform for developers that couldn’t host on Google Play. Labs had other features such as beta and alpha channels (before Google added the same to Google Play) to enable developers to have more control over their app distribution and testing. Not only that, but Labs let users get early access to new versions of popular apps with an update mechanism that would “push” updates to phones often days or weeks before Google or other big developers did full rollouts of new app versions.

In addition to being an app platform, XDA Labs also included a way to browse the XDA forums through a ground-up forum app we built in house using our own API. However, it’s been five years, and we find ourselves having to make some difficult decisions as we look towards the future of XDA where we plan to make XDA the best place in the world to talk about your tech.

The most significant decision we’ve made recently was to move from an outdated software platform (vBulletin) to something more modern and flexible (XenForo). This undertaking was huge and presented issues that have been resolved (thanks everyone for your patience!), and we’re happy to report that the forums are now stable and relatively fast, and our members have been pretty happy with the upgrade. Along with the migration we recently introduced the new XDA App, built using a platform that allows a combination of native and webviews (for those trying to learn how to use the new app, we have a great guide in the forums).

There’s yet another big change we have to announce, and we do it with a heavy heart knowing that it will affect several developers who have come to rely on XDA Labs to distribute their app: XDA Labs has been shut off and there are no current plans for further development.

Why such a drastic move? There are multiple reasons for it, the biggest of which come down to resources: the team that runs XDA is small and we can no longer dedicate the resources needed to continue running and maintaining Labs. Labs has many inherent costs we are no longer able to support as a business. We always wanted Labs to be free, and we see no path to keep it viable at this juncture.

What about those that have relied on Labs to distribute their apps and will mourn its loss? We’re sorry that we have to pull the plug on this project, and we’re sympathetic to the fact that you put your trust in the Labs platform only to have it unplugged. If it’s any consolation, effective today (12/31/20), we are massively increasing attachment limits in the XDA forums to 2GB. External users do not require an XDA account to download attachments; just share the file URL as you need! While this isn’t the same as the Labs app store, we do hope this still provides you a resource from which to distribute your app.

When we first announced the forum migration a few months ago, we invited anyone interested in continuing to maintain Labs to contact us. Unfortunately, we’ve had no viable proposals. We are willing to open-source the entire project if anyone would like to pick up the mantle. If you’re interested, please contact XDA Admin svetius.

In the meantime, we want to say thank you to everyone who made Labs possible. Many thanks to XDA Recognized Developer blk_jack, who was the godfather and main creator of this app, plus the many other testers, coordinators, and developers that worked on Labs in any shape or form. Many thanks to the dev team at XDA for maintaining it over the years, and to all our forum members who made our Labs dream possible. Labs was born out of a need from our community and while we’re unable to support it going forward, we truly hope that the community will rise up and continue keeping Labs running.

We’ve got lots of special plans for XDA as a whole and the XDA community and we can’t wait to share them with you in 2021 and beyond! Thanks for your ongoing support!

The post An Update on XDA Labs appeared first on xda-developers.

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

How to enable the Pixel 5’s Adaptive Sound feature on older Pixel phones

Google rolled out the fifth Pixel Feature Drop earlier this month, which brought a host of new features to both old and new Pixel phones. Some older Pixel phones gained features like Hold for Me and Extreme Battery Saver, while only Google’s latest Pixel 4a 5G and Pixel 5 got support for the new Adaptive Sound feature. The Adaptive Sound feature is designed to improve the phone’s audio output by tweaking its equalizer based on your surroundings, and thanks to XDA Recognized Developer Freak07, there’s a way to enable this feature on older Pixel devices. If you’re interested in trying it out on your phone, here’s what you need to do:

Enable Adaptive Sound on older Pixel devices (with root)

On rooted Pixel devices, you can enable the Adaptive Sound feature by following a couple of simple steps, and it will remain enabled even after your reboot your device. To do so, you’ll first need to download the Pixel 5-specific version of the Device Personalization Services app from APK Mirror and install it on your device. Yes, you will already have the Device Personalization Services app installed, but the version of the app that Google pushed to your phone doesn’t include the Adaptive Sound feature. Hence, you’ll need to grab the one that Google made for the Pixel 4a 5G and Pixel 5. You can download that version of the app by clicking this link.

Once you have the app installed, you’ll need to download and install the Adaptive_Audio_Settings_Enabler Magisk module from the Magisk Manager app and restart your device. Alternatively, you can download the module by following this link and flash it manually. A few moments after a successful reboot, you should see the Adaptive Sound option in device settings.

Enable Adaptive Sound on older Pixel devices (without root)

On non-rooted Pixel devices, the process to enable Adaptive Sound is a bit more complicated as you have to execute a couple of shell commands. But before you get to that, you have to install the Pixel 5-specific version of the Device Personalization Services from APK Mirror and install it on your device. You can get the app by following this link.

Once you have the app installed, make sure you have USB Debugging enabled on your device. You can do so by heading over to Developer Options and tapping on the toggle next to the USB Debugging setting. You’ll also need to ensure that you have a working ADB environment on your PC (we have a tutorial on that here). After you’ve done that, you’ll need to connect your phone to your PC and execute the following 3 commands one-by-one:

adb shell
device_config put device_personalization_services AdaptiveAudio__enable_adaptive_audio true
device_config put device_personalization_services AdaptiveAudio__show_promo_notification true

After you execute these three commands, you should see the Adaptive Sound option in the device settings. Unlike the method for rooted devices, though, this method doesn’t enable the Adaptive Sound option permanently, and it’s removed once you reboot your device. So, make sure you don’t reboot your device after following the aforementioned steps, or you’ll have to go through it once again.

Enable Adaptive Sound on older Pixel devices XDA Forums thread

The post How to enable the Pixel 5’s Adaptive Sound feature on older Pixel phones appeared first on xda-developers.

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

An Update on XDA Labs

It was five years ago that we launched XDA Labs after hundreds of hours of development. The primary purpose was to create an alternate app distribution platform for developers that couldn’t host on Google Play. Labs had other features such as beta and alpha channels (before Google added the same to Google Play) to enable developers to have more control over their app distribution and testing. Not only that, but Labs let users get early access to new versions of popular apps with an update mechanism that would “push” updates to phones often days or weeks before Google or other big developers did full rollouts of new app versions.

In addition to being an app platform, XDA Labs also included a way to browse the XDA forums through a ground-up forum app we built in house using our own API. However, it’s been five years, and we find ourselves having to make some difficult decisions as we look towards the future of XDA where we plan to make XDA the best place in the world to talk about your tech.

The most significant decision we’ve made recently was to move from an outdated software platform (vBulletin) to something more modern and flexible (XenForo). This undertaking was huge and presented issues that have been resolved (thanks everyone for your patience!), and we’re happy to report that the forums are now stable and relatively fast, and our members have been pretty happy with the upgrade. Along with the migration we recently introduced the new XDA App, built using a platform that allows a combination of native and webviews (for those trying to learn how to use the new app, we have a great guide in the forums).

There’s yet another big change we have to announce, and we do it with a heavy heart knowing that it will affect several developers who have come to rely on XDA Labs to distribute their app: XDA Labs has been shut off and there are no current plans for further development.

Why such a drastic move? There are multiple reasons for it, the biggest of which come down to resources: the team that runs XDA is small and we can no longer dedicate the resources needed to continue running and maintaining Labs. Labs has many inherent costs we are no longer able to support as a business. We always wanted Labs to be free, and we see no path to keep it viable at this juncture.

What about those that have relied on Labs to distribute their apps and will mourn its loss? We’re sorry that we have to pull the plug on this project, and we’re sympathetic to the fact that you put your trust in the Labs platform only to have it unplugged. If it’s any consolation, effective today (12/31/20), we are massively increasing attachment limits in the XDA forums to 2GB. External users do not require an XDA account to download attachments; just share the file URL as you need! While this isn’t the same as the Labs app store, we do hope this still provides you a resource from which to distribute your app.

When we first announced the forum migration a few months ago, we invited anyone interested in continuing to maintain Labs to contact us. Unfortunately, we’ve had no viable proposals. We are willing to open-source the entire project if anyone would like to pick up the mantle. If you’re interested, please contact XDA Admin svetius.

In the meantime, we want to say thank you to everyone who made Labs possible. Many thanks to XDA Recognized Developer blk_jack, who was the godfather and main creator of this app, plus the many other testers, coordinators, and developers that worked on Labs in any shape or form. Many thanks to the dev team at XDA for maintaining it over the years, and to all our forum members who made our Labs dream possible. Labs was born out of a need from our community and while we’re unable to support it going forward, we truly hope that the community will rise up and continue keeping Labs running.

We’ve got lots of special plans for XDA as a whole and the XDA community and we can’t wait to share them with you in 2021 and beyond! Thanks for your ongoing support!

The post An Update on XDA Labs appeared first on xda-developers.

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