July 7, 2022 7:35am Comment Pranob Mehrotra
Android 13’s Restricted setting feature will block malicious apps from accessing your notifications
Google is introducing a change with Android 13 that will prevent sideloaded apps from abusing the Accessibility APIs. The Restricted Setting feature will block the user from enabling the accessibility service for malicious applications. Upon identifying such an app, the Accessibility settings for that app will become inaccessible, and users will see a “Restricted setting” dialog stating that the setting is currently unavailable. But that’s not all there is to the new feature.
According to Mishaal Rahman, the Restricted setting feature will also block users from enabling an app’s Notification Listener. For the unaware, Android’s NotificationListenerService API lets apps intercept and interact with all notifications on a user’s behalf. If a malicious app gets access to the API, it can read all incoming notifications and get access to sensitive information. Android 13’s Restricted setting feature prevents that for all apps sideloaded using a non-session-based package installer.
Since most app stores use the session-based package installer, this restriction won’t apply to apps downloaded from app stores. It will only block apps that users sideload from outside of app stores, like through a browser or messaging app. However, there is a workaround to prevent the feature from blocking access for sideloaded apps.
Rahman notes that it’s “possible to acknowledge the restricted setting dialog and then re-enable access” to the Accessibility settings. You can learn more about the workaround in this blog post.
Featured image credit: Mishaal Rahman
Yeah also can't manually install Vanced as it comes preloaded with a newer version of YouTube/YouTube music. Honestly the differences between 12 to 13 seem so minor that it's not worth updating for what I use on a daily basis. Kinda disappointing to be honest.
There's a couple different methods outlined in this article to downgrade to earlier versions of an app, including split APKs like YouTube. I'm on A13 but haven't tried these methods yet. May work to get an earlier version of YouTube installed so Vanced will install. I installed NewPipe instead but may give this a go at some point.Yeah also can't manually install Vanced as it comes preloaded with a newer version of YouTube/YouTube music. Honestly the differences between 12 to 13 seem so minor that it's not worth updating for what I use on a daily basis. Kinda disappointing to be honest.
Yeah also can't manually install Vanced as it comes preloaded with a newer version of YouTube/YouTube music. Honestly the differences between 12 to 13 seem so minor that it's not worth updating for what I use on a daily basis. Kinda disappointing to be honest.
There are a few tutorials out there .. essentially you have to download the Vanced files and manually install and then replace a few files. I've been doing it without any issue. Instructions can be found here:I haven't been able to use Vanced for a while, even on A12. It installs but it will crash upon opening. I had to switch to NewPipe.
Nice. Figured there would be a few ways but didn't bother looking into it much. Already switched back to 12. If you do happen to try it, can you let us know how it works out?There's a couple different methods outlined in this article to downgrade to earlier versions of an app, including split APKs like YouTube. I'm on A13 but haven't tried these methods yet. May work to get an earlier version of YouTube installed so Vanced will install. I installed NewPipe instead but may give this a go at some point.
![]()
How to downgrade an app using Android’s hidden rollback feature
Android doesn't normally let users install an older version of an app (downgrade), but there's a hidden mechanism to rollback app updates.blog.esper.io
Will definitely let you know if it works if I try itNice. Figured there would be a few ways but didn't bother looking into it much. Already switched back to 12. If you do happen to try it, can you let us know how it works out?
There are easier ways to do it with root =).
I had battery drain before. I installed android 13 and unlocked bootloader, rooted, switch 5G and VoLTE and everything works perfect. But when I unlocked bootloader I had hard reset.
Either this week or next.
Beta 1: April 26 (Tues)
Pixel 6 Pro | raven-tpb4.220624.005-factory-e06d65e2.zip | e06d65e242faaad12f3bcc0a70441afda192475bfb9e699e944e757d80f820ad |
Perhaps it is because of Pixel 6/6 Pro. It is working fine with A12 on both the Pixel 6/6 Pro, however with A13, it gives driver looping, so far, I never see anyone able to have it working with Pixel 6/6 Pro on A13, the repackaged one which you had quoted has no exception.It works same way it did in Android 12. Been using it since Beta 1 on Pixel 4a.
This used to require some patches in the magisk install and funny reboot stuff but that's been all rolled into a single zip here: https://github.com/programminghoch10/ViPER4AndroidRepackaged
Indeed! In case someone needs it, I'm uploading the latest radio from Beta 4.1 (see attached file) for the P6P.Appears so...
Beta 4: radio-raven-g5123b-102852-220704-b-8796503
Beta 4.1: radio-raven-g5123b-102852-220713-b-8828409
Non-important statement incoming - but thank jeebus for that fix, haha. I never had a GPS issue in GMaps on the previous A13Beta builds, however, the app that I use to buy gas couldn't determine my location and wouldn't allow me to make gas purchases. So, this was certainly a beneficial change for me."Google’s three latest phones are getting a “Fix for GPS location failure under certain conditions.” For the Pixel 6 and 6 Pro, this is still just the July security patch, while the 6a is likely still on the June patch level."
Guess that explains the surprise new July builds, in part at least...
eecbcf5012785c409433fe2dc2cbac31431751af7414c47f3beb6381035c37d6
Pixel 6 Pro raven-tpb4.220624.008-factory-eecbcf50.zip
Release notes
Beta 4.1
Release date: July 25, 2022
Build: TPB4.220624.008
Emulator support: x86 (64-bit), ARM (v8-A)
Security patch level: July 2022
Google Play services: 22.21.16
API diff:
Android 13 Beta 4.1 (July 2022)
This minor update includes the following fixes:
- Fixed an issue that prevented an app from enabling or disabling Bluetooth if it didn't have the BLUETOOTH_CONNECT permission, even though the app was targeting an API level where the permission is not required. (Issue #232107689)
- Fixed issues that sometimes caused a device to crash and reboot when connecting to certain WiFi networks. (Issue #237308339, Issue #237886229, Issue #237878437)
- Fixed an issue where Meet connectivity could drop while driving.
- Fixed an issue where the system could incorrectly interpret GPS data.
eecbcf5012785c409433fe2dc2cbac31431751af7414c47f3beb6381035c37d6
Pixel 6 Pro raven-tpb4.220624.008-factory-eecbcf50.zip
Release notes
Beta 4.1
Release date: July 25, 2022
Build: TPB4.220624.008
Emulator support: x86 (64-bit), ARM (v8-A)
Security patch level: July 2022
Google Play services: 22.21.16
API diff:
Android 13 Beta 4.1 (July 2022)
This minor update includes the following fixes:
- Fixed an issue that prevented an app from enabling or disabling Bluetooth if it didn't have the BLUETOOTH_CONNECT permission, even though the app was targeting an API level where the permission is not required. (Issue #232107689)
- Fixed issues that sometimes caused a device to crash and reboot when connecting to certain WiFi networks. (Issue #237308339, Issue #237886229, Issue #237878437)
- Fixed an issue where Meet connectivity could drop while driving.
- Fixed an issue where the system could incorrectly interpret GPS data.
Pixel 6 Pro raven-tpb3.220617.002-factory-1acb43a3.zip 1acb43a3d082b8d2cd16cba834c1b1de25042c5d5122483bbf54ff4a16682186
Android 13 Beta 3.3 (June 2022)
Release date: June 27, 2022
Build: TPB3.220617.002
Emulator support: x86 (64-bit), ARM (v8-A)
Security patch level: June 2022
Google Play services: 22.21.16
API diff:
If you’re already running a Developer Preview or Beta build, you will automatically receive an over-the-air (OTA) update to Beta 3.3.
This minor update to Android 13 Beta 3 includes stability and performance improvements as well as the following fixes:
- Fixed an issue with the Pixel launcher where if the Always show keyboard option was enabled for the app drawer, then when the user closed the app drawer and opened an app folder on the Home screen, the keyboard was erroneously shown as well. (Issue #236584457)
- Fixed an issue where in some cases, such as gesturing to go back, the system UI crashed. (Issue #236558007)
- Fixed an issue where devices couldn't connect to a WiFi network in some cases even when the network was available and the signal strength was good. (Issue #236617510)
- Fixed an issue where the BluetoothManagerService continued to try and bind to the TbsService even when bluetooth.profile.ccp.server.enabled was false, leading to slow performance and cold starts for apps.
- Fixed an issue where in some cases after a device was plugged in to charge (for example, overnight), the device would become unresponsive until it was rebooted.
- Fixed a kernel issue with lib/list_debug.c that caused a kernel panic in certain cases on some devices.
- Fixed an issue with the Connectivity Thermal Power Manager that caused slow UI rendering, unresponsiveness in apps, and poor battery performance in some cases.
June 27, 2022 2:30pm Comment Skanda Hazarika
Google rolls out Android 13 Beta 3.3 with a bunch of bug fixes
The beta branch of Android 13 just picked up a new bug-squashing update. Following in the footsteps of Android 13 Beta 3’s earlier incremental updates, this new release fixes a whole bunch of issues, including slow UI rendering, inability to connect to a Wi-Fi network, system UI crashes, and a few other problems.
The build number of Android 13 Beta 3.3 is TPB3.220617.002. There is no change in the security patch level, though, hence it’s still June 2022 on this release. You can find the full list of published fixes in this update below:
Apart from the aforementioned bug fixes, the update also bumps the Google Play services version from 22.18.19 to 22.21.16.
- Fixed an issue with the Pixel launcher where if the Always show keyboard option was enabled for the app drawer, then when the user closed the app drawer and opened an app folder on the Home screen, the keyboard was erroneously shown as well. (Issue #236584457)
- Fixed an issue where in some cases, such as gesturing to go back, the system UI crashed. (Issue #236558007)
- Fixed an issue where devices couldn’t connect to a WiFi network in some cases even when the network was available and the signal strength was good. (Issue #236617510)
- Fixed an issue where the BluetoothManagerService continued to try and bind to the TbsService even when bluetooth.profile.ccp.server.enabled was false, leading to slow performance and cold starts for apps.
- Fixed an issue where in some cases after a device was plugged in to charge (for example, overnight), the device would become unresponsive until it was rebooted.
- Fixed a kernel issue with lib/list_debug.c that caused a kernel panic in certain cases on some devices.
- Fixed an issue with the Connectivity Thermal Power Manager that caused slow UI rendering, unresponsiveness in apps, and poor battery performance in some cases.
In case your Google Pixel device is already enrolled in the Android 13 beta program, you will automatically receive an over-the-air update to Beta 3.3. You can also download the full OTA or the factory image from the link below if you want to manually upgrade to the latest beta release.
Download Android 13 Beta 3.3
Source: Android Beta Program on Reddit
Good spot. Seeing as how that's now intended behaviour, I guess wiping and disabling verification is all our best moves from here.I think Magisk removed the need to pass the vbmeta disable verity/verification flag with Canary 24303. Here's a quote related to a kernel issue from yujincheng08 (LoveSy):
"Let me clarify the things.
Magisk was used to modify the fstab to inject Magisk components, and in the meantime, Magisk stipped avb_key and avb flags for all partitions. So, that 24300 works is just a side effect and has no insurance.
Now Magisk changed its way of injecting Magisk components, and it will no longer modify the fstab, and the side effect was thus gone together with the refactorization. Some configurations that rely on the fact that Magisk will strip those verification flags will no longer work, and that's expected. Users should disable the verification themselves since they are expected to have unlocked bootloaders."
This all relates to problems with custom kernels and Magisk, but may have further implications for us. Check out more in the issue here..
Some customized kernels are incompatible with Magisk 24303+ that no longer strips verification flags of early mount partitions · Issue #5777 · topjohnwu/Magisk
Device: Pixel 6 Pro Android version: 12.1...github.com