Database Info

[APP][2.2+] LBE Security Master 5.1.4722

For those who use this app, and like it more than the official lite English version.
Attached is the latest (beta) Chinese version Google English translated and repacked+signed.
All rights/Credits to creator at: www.lbesec.com
For older versions check this thread.
Or check market.
Note:
I have experienced issues with apps's functionality if it's not installed from clean slate. Even when using backup/restore functionality of LBE or TitaniumBackup.
I strongly recommend uninstalling previous versions before upgrading and to reconfigure the app from scratch.
Changelog:
10/11/2013 - The community here updated the translations for LBE_Security_5.1.4722
31/07/2013 - LBE 5.0.3720
16/07/2013 - LBE 5.0.3674 - Thanks to @sorg
28/06/2013 - LBE v5.0.3555 - A more Humanoid translation thanks to VicePoint can be found here.
23/05/2013 - LBE v4.6.3005
28/04/2013 - LBE v4.6.2925
26/04/2013 - LBE v4.6.2924
19/04/2013 - LBE v4.5.2917
06/02/2013 - LBE v4.4.2868
25/01/2013 - LBE v4.4.2829
24/01/2013 - LBE v4.4.2828
19/01/2013 - LBE v4.4.2803 - A release with multiple translations for English, French & German. Look here.
Newer modifications were added and attached here by Pax_fr.
14/01/2013 - LBE v4.4.2803 - here
14/12/2012 - LBE v4.3.2738 - here
16/11/2012 - LBE v4.2.2548 - Manual Translation - here
Should be fixing the Android 4.2 issues that reported in previous version.
14/11/2012 - LBE v4.2.2546 - Manual Translation - Here
21/09/2012 - Newer release from LBE - v4.1.2224 - Here
7/9/2012: A new version is out - v4.1.2175
Until we'd get to human translate the changes I'm posting the translations by Google Translate.
Update (21/09): Human/Manual translation version thanks to cdljl2005
Here's the change log (thanks to Google translate):
1 redesigned clean and simple style UI
2 new program lock function, face recognition
3. The new LBE task manager, at any interface can be a key to exhale, convenient
4 New switched vibration and missed reminders
5 Enhanced system-level call blocking feature, support for CDMA network phones, and HTC series mobile phone
6 new strange call delay of three seconds ringing function (This feature is dependent on system-level calls blocking)
7 spam messages and telephone notification, a separate notification bar message, you can just click once to enter the harassment intercept interface
8 Task Manager with HTC 4.0 phone compatibility
9. Significantly optimize memory usage, reduced to LBE 4.0 version level
10. Repair the charging time remaining prompts
11 to increase the depth of the SD card cleanup options
12. Repair Most common LBE Security Master 4.0 bug fixes some bug causes the program to crash
** Thanks to cdljl2005, we now have a manual translation for v4.0.1894.
If you like it give him a thanks too.
25/7/2012 - update translation to v4.0.1894 (Google translated)
4.0.1894 update logs
Active defense Added support for Android 4.1.1
The new revision of the main interface, more comfortable, more easy to use
The harassment blocking features full support for dual card dual standby type. You can set a different intercept for each SIM card mode and IP dialing mode
New design of software architecture, the memory footprint is reduced by 40%, half and even less of the same kind of security software
New depth of scanning capabilities, can help you to accurately scan the SD card in the garbage
Fixed clean up the desktop process error on Android 4.0 and 4.1 mobile phones
New notification bar shortcuts, so you do not need to enter the the LBE security master to complete the most common operations
Synchronization software uninstall feature new uninstall the software clean up the residual files of SD card
Traffic statistics to support the night half-price mode, you are free to set the half-period
Virus killing function supports background scanning, to avoid the depth of killing screen lock failure
Harassment intercept support dual card models include: the MOTO full range of dual-card models, HTCG + W card models, MTK full range of dual card models, ZTE U960, etc.
23/5/2012 - update translation to v3.7.2164 (seems lke there's a hardcoded chinese text in power saving screen, around the power scheme... )
Active defense:
0, fixes some versions prompted to restart the upgrade several times
A fix on some machines, the main anti-occasional failed to load;
2, FMR-compatible memory clean-up, hot restart and other software., Active defense can be automatically restored after a system crash;
To streamline the logging algorithm, the same event will not be multiple entry log;
Power-saving mode:
1, reconstruction of the power-saving optimization features: a variety of modes, charging tips, taskbar power icon (optional);
2, the power to show the accuracy on some devices;
3, repair N930 battery display inaccurate;
4, fix the first to enter the power saving mode, custom mode displays an error;
5, modify the name and description of the mode;
6, improved battery power for algorithms;
Flow correction:
Fix a bug, resulting in an automatic flow correction will be performed after each reboot;
Anti-theft features:
Two unlock failure complicated by the front camera camera sent to the safety of mobile phones
This feature requires ANDROID 2.3, and the phone has a front camera
Other:
Repair and the MIUI 2.3 backup and restore compatibility issues.
11/05/2012 - update translation to v3.6.2039
The new flow auto-correction function, support automatic and manual correction mode; automatic correction of repair traffic occasionally lead to software crashes, and flow calibration time interval too short;
Automatically upgrade the support to upgrade the anti-theft module;
Fix the problem of anti-theft module messages intercepted by the security master;
Anti-theft module:
A backup contact data is no longer the backup picture and other data, to prevent the backup failed because the data is too large lead
When the backup, positioning operation is executed, it will automatically open the network connection and GPS
The interface-digit password prompt, to prevent excessive password median
4 anti-theft login page to join the forgotten password option
29/04/2012 - update translation to v3.5.1999
a new anti-theft module
Enhanced the compatibility of the active defense
New anti-theft module, anti-theft module is an independent security master module, with the following features:
Automatic notification when the SIM card replacement security number phone positioning: Get cell phone current location data destruction: destruction of the address book, SMS, data, and clean up the SD card, to prevent the loss of privacy data backup: backup data to the cloud server, to prevent key card replacements notice: loss of data lock the phone: to prevent others from using your phone rings alarm: the maximum volume alarm sound to help retrieve the phone virtual Warning: send a custom warning message to your phone
Anti-theft module is tightly integrated with the LBE security master, support ROOT installation mode in the active defense to open the case, the LBE anti-theft module. LBE anti-theft module in this mode will be installed as a system component that can not be easily removed, even if the phone is clear the data, or restore factory settings, anti-theft module can still take effect.
19/04/2012 - update to v3.4.1974
enhance the compatibility of the active defense
- Repair the compatibility problems of the previous versions of the firmware of a small part of active defense
- Repair the failure of some of the Android 2.1 or Android 2.0 phone in the open active defense, the Task Manager
- Repair the in MIUI on the automatic update fails
- Improve the same part of the proactive defense without the phone features of the tablet device compatibility issues
- Repair of active defense compatibility issues with some of CyanogenMod ROM
- Added by default some of the core of the system component from the Kai housekeeper whitelist, to prevent the user inadvertently prohibit its start automatically lead to the abnormal working of the system (including: the MOTO phone can not connect to the PC, some ringtones error)
- New anti-virus log function, you can viewed in the interface of the virus killing virus scanning history
11/04/2012 - update to v3.3.1946
Change log is huge, read here
29/02/2012 - update to v3.2.1749
One fixes a large number of bug cause crash
Firewall support Samsung I9008 and I9108
3 virus database upgrade to the latest version of February 24, 2011 (20110224.d)
New Kung Fu Panda virus detection
5 fixes the Kung Fu Panda virus infection on the phone security master black screen no response
20/02/2012 - v3.2.1741 google translated (file named by author as 3.2.r741)
Bug fixes
Firewall support 9008 9108
Virus database upgrade to the latest version of the February 20
18/02/2012 - Fixed FCs on scan due to translation.

Changelog here:
http://www.lbesec.com/?cat=3
Google translated version:
http://translate.google.com/transla...ayout=2&eotf=1&u=http://www.lbesec.com/?cat=3

Terrible translation, did you edit the text yourself?

SWADED said:
Terrible translation, did you edit the text yourself?
Click to expand...
Click to collapse
Read OP again. Clearly states how translated.
Sent from my HD2

zagzag99 said:
Read OP again. Clearly states how translated.
Sent from my HD2
Click to expand...
Click to collapse
Read comment again. Clearly states edit instead of translated.
But let me make it even clearer: Did you just copy paste what you saw in Google translate or did you edit the text after letting Google **** it up?
Don't get me wrong I appreciate the effort but you could make the translation so much better by just using common sense.
I'm willing to translate it for you, if you can send me the text file or whatever.

SWADED said:
Read comment again. Clearly states edit instead of translated.
But let me make it even clearer: Did you just copy paste what you saw in Google translate or did you edit the text after letting Google **** it up?
Don't get me wrong I appreciate the effort but you could make the translation so much better by just using common sense.
I'm willing to translate it for you, if you can send me the text file or whatever.
Click to expand...
Click to collapse
meant Google translated. Not manual edit apart from some special chars.
Have no time to translate manually. There are many strings. If you want you can extract strings yourself with apktool.
Or I can attach later if you want.
Sent from my HD2

Hi zagzag
I don't seem able to find the download link to 3.1.1549 version on lbesec.com. Since this version is recommended I would like to give it a try. Any chance you can attach it to the op please? Thanks in advance.

Link: http://www.lbesec.com/download/LBE_Privacy_Guard_3.1.1549_A1.apk
It's where the android button is.
CSharpHeaven said:
Hi zagzag
I don't seem able to find the download link to 3.1.1549 version on lbesec.com. Since this version is recommended I would like to give it a try. Any chance you can attach it to the op please? Thanks in advance.
Click to expand...
Click to collapse

night_stalker_z said:
Link: http://www.lbesec.com/download/LBE_Privacy_Guard_3.1.1549_A1.apk
It's where the android button is.
Click to expand...
Click to collapse
Thank you for the link. Unfortunately, this one is in chinese language. I'll wait for the English version.
By the way, a general comment about the LBE's saga...
I think the efforts to improve the application should be seen as a positive thing. I've got a feeling I can trust the LBE's developer(s). A bit unfortunate no one in the development team is fluent in English. Kaspersky security software product is developed in Russia, so the location of the developer/vendor means nothing really.
Still on the matter... There are more people in the UK in prisons than the hackers in China who are after my credit cards. That doesn't make all British people criminals.

Updated OP with newer version.

zagzag99 said:
Updated OP with newer version.
Click to expand...
Click to collapse
Thank you.

Here is my very quick feedback...
The number of new features are very impressive.
Everything is configurable to your liking.
I have monitored the two main processes using OSMonitor app and couldn't detect anything suspicious. Since I disabled all reporting services I did not notice LBE making network connections.
After install I restarted the phone, it was an requirement.
I have checked the applications that would connect to the internet to pull adverts and as far as I could tell LBE was blocking them successfully.
The process usage has always been impressive in version 2 and I can say the same thing about 3 now. Please note; I use my phone extensively everyday and I use upto three batteries. I can easily tell if my battery usage has noticeably changed. Each battery gives me 6-9:30 hours of continuous use.
The interface looks really good and very distinguish from the rest.
Being still in alpha obviously, the interface requires a lot of attentions. For instance, going back to the app list of Active Defense from individual app setup screen does not maintain the application position. Things become bad when the system apps being shown.
It looks like the trusted app view is gone, which is a step backward in terms of usability.
Ok, I need to submit this now as my bus stop is next. Overall I'm very pleased with LBE so far. Thank you guys.

thanks for this!

Just a quick update...
I'm still alive after installing the latest build but unfortunately it was unstable -- reverted to version 2.x now.
Just a suggestion, if I may. Due to the number of new features I can tell how the team/dev are/is busy. However, it would be a good plan to fix version 2.x issues first. I just reverted to a version that I knew is not stable. For one, I have to keep my eyes on the settings to make sure they are not changed inappropriately. Thank you.

Thanks, best program I have installed. Just brilliant

So what's the difference between "LBE Security Manager" and "LBE Privacy Guard", if I may ask?

trollsperm said:
So what's the difference between "LBE Security Manager" and "LBE Privacy Guard", if I may ask?
Click to expand...
Click to collapse
It is the same only the version posted here is the newest beta, translated by the OP.

Not a big fan of it being able to do things that cost me money. Why is that permission there now?

Sandpapers said:
Not a big fan of it being able to do things that cost me money. Why is that permission there now?
Click to expand...
Click to collapse
That's how the permission is called but the feature behind it is that lbe can track your data plan costs and limit apps using data when you reach your limit.
This is good for those that don't have flat rate unlimited data plans.
Sent from my NexusHD2

New release 3.2.1650
Again, just google translated.
Check OP for link.
Change Log:
The LBE security master 3.2 full version (3.2.1650) is officially released! Increase the depth of clean-up of SD card, IP dialing
Virus killing] new ROOT mention the right type of software alarm
The virus killing anti-virus interface, you can view the details of each virus, including: the name of the virus, the risk of specific acts
Open the antivirus engine and virus database of killing the virus automatic update feature
[Interface] New security master password protection feature to prevent users without permission to modify the security master set
[Interface] support the flow of floating window click on the penetration function (need to lock the flow of floating window location)
Call firewall new system-level calls firewall, a significant reduction in call blocking time, the loud cry of resolve to intercept (system-level calls firewall needs to open the active defense capabilities to meet the call blocking mode is set to hang up when best)
Phone call firewall intercept model to add only accept contact with the White List number model
Call Firewall support calls attribution to feature HTC Sense 3.0 lock screen display (requires first set of calls attribution to the window position to lock)
[Coming call firewall support MMS block and recovery
Call firewall, support IP dialing, you can choose to automatically add all the numbers to IP prefixes, the only other provinces, the only foreign city numbers automatically add IP prefix
Call firewall attribution to the database is updated to the January version
[System] new deep cleaning function of the SD card, you can manually clean up the SD card on a variety of software cache
Android 4.0] to repair the Android 4.0 system, occasional failure of network access control
[Performance] fix bugs, and after two weeks of internal testing to ensure the stability of the 3.2 version from 3.0 since

[ROM][Treble][microG]LineageOS 16.0 for HUAWEI P9

This thread is dedicated to provide Lineage-OS 16.0 builds with microG included for the HUAWEI P9 with current security patches.
It is a treble build, therefore it could also work on other devices, but I haven't tested. And yes, the camera works!
(Although it is based on the work of phhusson's GSI builds, some specific adaptations have been made, so I guess, it is worth a try for further Huawei devices based on EMUI 8, but that's it...)
Features of this ROM
Download here
Pre-installed microG and F-Droid like the LineageOS for microG project (own fork)
Pre-installed AuroraStore
Root included (switch on in dev. settings)
eSpeakTTS (FOSS TTS engine)
Backported Audio balance (accessibility settings) from Android 10
Additional security hardening features listed below
Access to /proc/net blocked for user apps
Bundled netmonitor app to allow network monitoring
Enhanced Privacy Guard: Switches for motion sensors and other sensors
Cloudflare as default DNS (instead of Google)
Privacy-preferred default settings
Optional blocking of Facebook- and Google-Tracking
Optional disabling of captive portal detection
Firewall UI
No submission of IMSI/phone number to Google when GPS is in use
Default hosts file with many blocked ad/tracking sites
Privacy-enhanced Bromite SystemWebView Mulch Webview
Additional restrictions for secondary users
Increased password length
Hardened bionic lib and constified JNI method tables
Huawei Stock Camera
Current release levels
Custom build release 2023-05-01
Security string: 2022-01-01
AOSP tag: 9.0.0_r46
Mulch System Webview: M113
Source-code and build instructions
Device config.: https://github.com/lin16-microg/device_phh_treble/tree/lin-16.0-eva-p9
Build manifest: https://github.com/lin16-microg/local_manifests/tree/lin-16.0-treble
Installation Instructions
YOU ARE RESPONSIBLE SOLELY YOURSELF FOR ANY ACTIONS YOU DO WITH YOUR DEVICE !!!
Please note - I won't explain any single aspect (e.g. how to install 'fastboot' on your PC or troubleshoot USB connectivity issues under Windows). Search the net and consult the search engine of your choice or look here in XDA, there is plenty of information available.
Pre-Requisites
Have fastboot and adb installed on your PC and make sure, you can connect via USB to your device in fastboot mode and via adb
Know the key combinations to get your phone into fastboot mode and recovery mode
An unlocked bootloader
EMUI 8.0 firmware
Have the Huawei Stock recovery installed (not TWRP)
ONLY, If the above pre-requisites are met, download and unpack the linked ZIP file, and flash the .img file via fastboot (EMUI 8.0 is the tricky pre-requisite - see further below).
Get your device into fastboot mode and connect to your PC via USB - the screen should look like below, indicating "PHONE Unlocked"
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Flash the ROM with the command fastboot flash system <name of the rom img file>.img
Afterwards, enter the command fastboot reboot
Hold Power+Vol.Up to get into the Stock recovery:
Choose the option "wipe data/factory reset"
Don't 'panic' if the operation stops at a percentage significantly lower than 100% and you see a red exclamation mark, all is fine
Next, choose "wipe cache partition"
Finally choose "reboot system now"
Some hints:
If you come from an EMUI 8.0 stock ROM or a different treble build (which means, you are already on EMUI 8.0), don't forget the factory reset as described.
If you update one of my builds from this thread, you don't need to wipe anything, so you can skip everything after the 'fastboot reboot' step!
On some (but not all) PCs, you may have to run fastboot as Admin (Windows) or root/sudo (Linux)
If the above pre-requisites are NOT met, you will have some extra-rounds to perform, until you get there:
Unlocked Bootloader
Huawei has stopped providing unlock keys, so if you haven't got one, this thread, this link and/or of course the search-engine of your choice may be helpful. I was lucky enough to obtain an official unlock key on the last day of HUAWEI's unlock page, so I have no experience with the unofficial unlock methods - good luck!
EMUI 8.0 firmware
Get back to Stock ROM, if you use a Custom ROM. On Stock, if not yet done, apply all updates offered to you by the Stock ROM updater, until you are on the latest officially offered Android 7 (Nougat) EMUI 5.x release.
Huawei has shut down however their update servers for older devices and older software releases, so this may become difficult, if you are e.g. still on Android 6 - I don't have a good advice for you in this case.
Once you are on Android 7 (aka Nougat), please visit this thread, which really explains step-by-step, what needs to be done. Really carefully read everything and follow ALL the steps, especially, don't forget at the very end to flash the Stock EMUI recovery!
IMPORTANT UPDATE:
The linked thread, as well as the Openkirin documentation point - via a Russian firmware site - to the domain 'hicloud.com' for the firmware download, which seems to be down. As suggested by @zgfg you can try either his Mega link or e.g. https://androidhost.ru/search.html
Update: See this post to obtain the firmware!
Update 2: See also here
You need your unlock key handy: During this process, the bootloader will be automatically locked several times, so you need the key a couple of times to unlock again!
A hint for Linux users: The HWOTA tool is in fact a windows wrapper around Linux shell scripts, so there is no real need to use Windows, if you have a working Linux installation (however, make sure to replace the 'mkdir' commands in hwota_eng.sh with 'mkdir -p').
Android 10, 11, 12 or 13 builds?​Simple answer: There won't be any coming from my end (my aim is to provide daily-driver capable builds and not to boot an experimental GSI with lots of issues and a non-working camera) - so stop wasting everybody's time by repeatedly asking!
Bug reports:
If you have a problem, please create a post with these informations:
Build Date:
And try to get log as described here
Please note that I can't and won't support issues with builds using a different kernel or Xposed.
In regards to microG, I will try my best to help when it is related to this ROM (I use it myself), but any questions of the type "the YXZ-app can't do <some sort of fancy xyz Google functionality> properly" are better asked in the respective microG forums.
Credits
AOSP project
LineageOS project
openkirin.net
phhusson
AndyYan
Tecalote
microG project
Graphene OS project
csagan5 (Bromite)
WhyOrean (Aurora)
zgfg (for very helpful contributions in this thread)
XDA:DevDB Information
[ROM][Treble][microG]LineageOS 16.0 for HUAWEI P9, ROM for the Huawei P9
Contributors
MSe1969
Source Code: https://github.com/lin16-microg/device_phh_treble/tree/lin-16.0-eva-p9
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
ROM Firmware Required: EMUI 8 firmware
Based On: LineageOS
Version Information
Status: Stable
Stable Release Date: 2023-05-10
Created 2020-04-06
Last Updated 2023-05-11

Change Log
June 19th, 2023
Custom build release 2023-06-01
Mulch Webview 114.0.5735.131
microG updated to 0.2.28.231657-5
FakeStore updated to 0.2.0
Removed selected apps because of partition space restrictions
May 11th, 2023
Custom build release 2023-05-01
Mulch Webview 113.0.5672.77
April 19th, 2023
Custom build release 2023-04-01
Mulch Webview 112.0.5615.101
March 22nd, 2023
Custom build release 2023-03-01
Bromite Webview replaced by Mulch Webview 111.0.5563.58
February 19th, 2023
Custom build release 2023-02-01
microG on 0.2.27.223616-3
Spoof apps installed by G*PlayStore
January 07th, 2023
Custom build release 2023-01-01
Bromite Webview 108.0.5359.156
microG 0.2.26.223616-16
December 12th, 2022
Custom build release 2022-12-01
Bromite Webview 108.0.5359.106
microG 0.2.26.223616-2
November 14th, 2022
Custom build release 2022-11-01
Bromite Webview 106.0.5249.163
microG 0.2.25.223616-10
F-Droid 1.15.3
Timezone data updated to 2022f
October 12th, 2022
Custom build release 2022-10-01
Bromite Webview 105.0.5195.147
microG 0.2.24.223616-61
APN configurations updated
September 10th, 2022
Custom build release 2022-09-01
Bromite Webview 104.0.5112.91
microG 0.2.24.214816-30
Contacts app slightly 'de-Googled'
August 8th, 2022
Custom build release 2022-08-01
Bromite Webview 103.0.5060.140
July 14th, 2022
Custom build release 2022-07-01
June 15th, 2022
Custom build release 2022-06-01
Bromite Webview 102.0.5005.96
F-Droid 1.15.2
microG 0.2.24.214816-11
May 7th, 2022
Custom build release 2022-05-01
Bromite Webview 101.0.4951.53
F-Droid 1.15
MozillaNlpBackend 1.5.0
microG 0.2.24.214816-10
April 12th, 2022
Custom build release 2022-04-01
Bromite Webview 100.0.4896.57
March 15th, 2022
Custom build release 2022-03-01
AuroraStore 4.1.1
Bromite Webview 99.0.4844.58
February 19th, 2022
Custom build release 2022-02-01
F-Droid updated to 1.14, F-Droid privileged extension to 0.2.13
Bromite System Webview updated to 97.0.4692.106
microG updated to 0.2.24.214816-2
January 20th, 2022
ASB Security String 2022-01-01
Audio-Balance slider in accessibility settings back-ported from Android 10
Updated APN list
December 18th, 2021
ASB Security String 2021-12-01
Bromite System Webview 96.0.4664.54
microG 0.22.214516-21
November 9th, 2021
ASB Security String 2021-11-01
Bromite System Webview 94.0.4606.109
October 7th, 2021
ASB Security String 2021-10-01
Bromite System Webview 93.0.4577.83
September 12th, 2021
ASB Security string 2021-09-01
microG 0.2.22.212658-2
August 06th, 2021
ASB Security String 2021-08-01
Bromite Webview updated to 92.0.4515.134
F-Droid on 1.13
July 10th, 2021
ASB Security String 2021-07-01
Bromite Webview updated to 91.0.4472.146
microG 0.2.21.212158-2
AuroraStore 4.0.7
June 13th, 2021
ASB Security String 2021-06-01
Bromite Webview updated to 91.0.4472.102
microG 0.2.19211515-9
May 8th, 2021
ASB Security string 2021-05-01
Replaced LineageOS/AOSP Camera with Huawei Stock Camera
Fixed image size of system.img, so flash issues with some devices should be fixed
Fixed Firmware display info in case of B552 (was still showing as B550 before)
AuroraServices updated to version 1.1.1
Bromite Webview updated to 90.0.4430.204
April 10th, 2021
ASB Security string 2021-04-01
Bromite System Webview 90.0.4430.59
F-Droid 1.12
AuroraStore 4.0.4 with AuroraServices 1.1.0
March 8th, 2021
ASB Security string 2021-03-01
Bromite Webview on 88.0.4324.207
Updated microG from upstream to 0.2.18.204714 (picked until 87465cd)
Updated F-Droid to 1.11
Updated phh treble app
Extended phone number blocking options (Dialer settings)
February 5th, 2021
ASB Security string 2021-02-01
Bromite Webview on 88.0.4324.141
Updated microG from upstream to 0.2.17.204714-5 (picked until 3d2c7e9)
Updated F-Droid to 1.10-alpha-234
January 14th, 2021
ASB Security string 2021-01-01
Bromite Webview on 87.0.4280.131
Updated microG from upstream to 0.2.16.204713-10 (picked until 2f29b93)
Updated F-Droid to 1.10-alpha1-212
'ADB backup' now works
December 13th, 2020
ASB Security string 2020-12-01
Bromite Webview on 87.0.4280.106
Updated microG from upstream to 0.2.14.204215-15 (picked until 720b089)
Updated F-Droid to 1.10-alpha1-114
Removed AudioFX from build
November 07th, 2020
ASB Security string 2020-11-01
Bromite Webview on 86.0.4240.181
Fix for CVE-2020-15999
Rework of Hotspot Fix
Fix of AOSP mail app widget
Updated microG (see "interim build")
Replaced weak F-Droid signatures with ROM's V2 signatures
October 29th, 2020
Interim build with updated microG (fixes GCM issues and exposure notification API issues)
October 07th, 2020
ASB Security string 2020-10-01
Bromite Webview on 86.0.4240.73
microG 0.2.12.203315 - including "Exposure notification API" for use of Covid tracing apps
Additional hardening (bionic and constified JNI method tables)
Fixed: Hotspot is working now
Fixed: AuroraStore now finds all apps
September 12th, 2020
ASB Security string 2020-09-01
Bromite Webview on 85.0.4183.86
Added eSpeak TTS engine (FOSS TTS solution)
Added P9 overlay with proper power profile & battery stats
August 08th, 2020
ASB Security string 2020-08-01
Bromite Webview on 84.0.4147.113
The location of the firewall functionality has moved to Network > Data usage in Settings (latest cherry-pick from here)
July 10th, 2020
ASB Security string 2020-07-01
microG: updated prebuilt GmsCore fom /e/ project (fixed FCM registration issues)
F-Droid updated to 1.8 / F-Droid privileged extension updated to 0.2.11
Aurorastore updated to 3.2.9 / AuroraServices updated to 1.0.6
Bromite Webview on 83.0.4103.101
Sepolicy: Netmonitor exception f. "Tracker Control" app
June 04th, 2020
The June ASB for Android 9 are already part of the May build, see this post for more info
Therefore no separate new build for June (in July, there will be a new build again)
May 08th, 2020
Sec. string 2020-05-01
Bromite Webview on 81.0.4044.127
AuroraStore updated to 3.2.8
Fix of bundled 'netmonitor' app not starting
April 12th, 2020
Sec. string 2020-04-01
Fix for CVE-2020-8597 (external/ppp)
April 6th, 2020
Sec. string 2020-03-01
Initial feature list:
Pre-installed microG and F-Droid same as the LineageOS for microG project
Pre-installed AuroraStore (Version 3.2.4) with AuroraServices 1.0.5
Access to /proc/net blocked for user apps
Bundled netmonitor app to allow network monitoring
Enhanced Privacy Guard: Switches for motion sensors and other sensors
Cloudflare as default DNS (instead of Google)
Privacy-preferred default settings
Optional blocking of Facebook- and Google-Tracking
Optional disable captive portal detection
Firewall UI (Settings => Location & Security)
No submission of IMSI/IMEI to Google/Sony when GPS is in use
Default hosts file with many blocked ad/tracking sites
Privacy-enhanced Bromite SystemWebView 81.0.4044.76
Additional restrictions for secondary users
Increased password length

Additional security features in detail
1. Pre-installed microG and F-Droid
same as the LineageOS for microG project
2. Pre-installed AuroraStore
works w/o having to enable the "unknown sources feature"
3. Restrict access to /proc/net for user apps
An adapted SELinux policy prevents user apps from accessing the /proc/net pseudo file system, which can be misused to monitor and track the phone's internet traffic. For technical backgrounds, see here. For the legitimate use case of the smart phone owner him/herself monitoring the network traffic to see, what the installed apps do, the app Privacy-Friendly Network Monitor has been bundled.
4. Enhanced Privacy Guard - Sensor permission switches
An own sensor template to control access to motion sensors ('ask' mode) and all other sensors (allowed by default, but can be restricted) has been implemented into the Privacy Guard.
5. Cloudflare (instead of Google) default DNS
Cloudflare DNS has a better privacy policy than Google Public DNS and has DNS-over-TLS and DNS-over-HTTPS. In the deafult DNS settings (as fallback) and network diagnostics, the Cloudflare DNS adresses 1.1.1.1 and 1.0.0.1 are specified as defaults (instead of Google's 8.8.8.8 and 8.8.4.4)
6. Privacy-preferred default settings
When newly installed, the below settings are defaulted, different from standard LineageOS 16.0 (all settings can be changed at any time later):
Privacy Guard is enabled on install (proposal during Setup)
Anonymous LineageOS statistics disabled (proposal during Setup)
The standard browsing app does not get the location runtime permission automatically assigned
Sensitive information is hidden on the lock screen
Camera app: Location tagging disabled by default
Further, when a lock screen protection is set (PIN, pattern, password), the Nfc, Hotspot and airplane mode tiles require authentication and cannot be set without
7. Optional blocking of Facebook- and Google-Tracking
Settings => Network & Internet (scroll down)
When activated, all outgoing connection attempts to Facebook servers will be suppressed.
Same applies to Google, but certain apps on an internal exception list will still be able to connect (AuroraStore, microG, or e.g. NewPipe, if installed)
8. Optional disable captive portal detection
Settings => Network & Internet (scroll down)
When activated, the system will not ping a specific Google server any longer when establishing a WiFi connection to determine, whether a captive portal is being used.
9. No submission of IMSI or phone number to Google/Sony when GPS is in use
GPS also works fine, if no SIM card is present, so there obviously is no benefit for the phone holder (different from other involved parties ) to provide this data . . .
10. Default hosts file with many blocked ad/tracking sites
The system's hosts file redirects a comprehensive list of URLs known to be adware, tracking, etc. to 127.0.0.1 (ipv4) and ::1 (ipv6)
11. Privacy-enhanced Bromite SystemWebView
Instead of the default Chromium System Webview component, the Bromite SystemWebView is used offering more privacy, more ad blocking and less Google tracking.
12. Firewall UI
Settings => Network & Internet - Data usage - Admin. data usage
Lists all apps and allows to restrict Internet access per app in regards to WiFi, mobile network or VPN
This per-app feature is a standard feature in LineageOS, but the UI to show all apps is an Extra (taken from a topic in LineageOS's Gerrit - it may, or may not, become part of the official LineageOS one day)
13. Maximum password length increased to 64
14. Additional restriction options for secondary users
- Disallow app installation option
- Disallow audio recording option
15. Misc. low level hardening
- Hardened bionic lib (see GrapheneOS)
- Constified JNI method tables

Further tips & tricks and open issues​microG initial configuration after 1st install​After the first installation of this ROM, you need to setup microG.
Please read the instructions given on the LineageOS for microG site, section "Post Install - UnifiedNlp"
Install Google speech services to work 100% 'offline'
- Launch Aurora Store and search "Speech Services by Google"
- Do not simply install it, because we need an older version
- Manually download and install, via "choose version", the version 210354702
- Add the app afterwards to Aurora's block list to make sure, it does never get updated
- Activate it in Settings and download the speech files of your preferred language(s)
- Afterwards, block the network traffic for this app to force 100% offline mode
Custom Kernel ?​A treble build is usually only a system.img file, and the stock kernel is continued to be used. Hence, the stock kernel is outdated.
If you would like to use a more recent upstreamed kernel with the respective sec. patches, e.g. the ECO Kernel thread might be interesting for you. This is what I personally use, but please keep in mind that I cannot support here, all kernel issues should be addressed in that thread! - with newest firmware b560, kernel is fairly recent again
Reported to also work on other devices than HUAWEI P9 by forum participants​As I don't own those, I can't confirm - nevertheless, I will list them, when it is reported to me.
Honor 6X
Honor 8
P9 Plus
Magisk​I myself do not use Magisk and the ROM comes with a shipped root solution. Acknowledging, that there are people, who want to use Magisk, I have collected a couple of feedbacks from forum posts:
Huawei devices aren't officially supported any longer by current Magisk versions, the latest working version for EMUI 8.0 builds (like this one) is 20.4 - so please only use that version and Magisk Manager v7.5.1
You need the respective file RAMDISK.img from the Huwei Firmware of your device. When the Magisk instructions state 'boot.img', you take the file RAMDISK.img instead. The resulting 'patched_boot.img' file (whatever its real name will be, adapt the name accordingly for the following fastboot command) is to be used for the fastboot command fastboot flash ramdisk patched_boot.img
Current Issues (reported by others and/or observed by myself)​Below a list of known issues and/or limitations. If possible, I try to fix those; however - I definitely welcome any hint on how to solve (or even pull requests). Please report anything you observe, while using this ROM.
1. No LineageOS boot animation after input of encryption password at startup
Observed by: myself
Well, this is nothing of importance to me, so unless somebody points me to a solution, I won't spend time on fixing this
2. Bluetooth issues - confirmed no issue
Observed by: other thread participant(s)
Issue: No devices found to connect to.
I don't have any BT issues with my own device (other than the device initially pairing as "hello!", so you would have to manually change the device name as a one-time activity) - Can't therefore really do anything about it, but wil keep an eye on reports
3. AuroraStore does not find app 'xyz' - solved
In the AuroraStore support thread, this has been also mentioned; it seems that Google is right now altering the search API; the dev is working on it.
Different from a report here in this thread, I was able to search and find many popular apps - the only restriction, which I myself was confronted with, was Netflix. As a work-around, manually download the Netflix apk (older version) from a trustworthy source - the app itself runs fine.
4. Headphone issues (1)
(Physical, no BT) headphone put in headphone jack - solved via work-around
Observed by: myself
Issue: Testing sound volumes in Settings app => all fine. But playing audio / video files or streams only plays good sound for less than 0,5 seconds, afterwards it seems that only the high frequency sounds (treble) are audible, whilst medium and bass is hardly audible.
Work-around: Switch off Audio-FX, when headset plugged in (the cool thing is, Audio-FX remembers this, so it switches off, when headset plugged in and switches on again if head-set unplugged)
5. Headphone issues (2)
(Physical, no BT) headphone put in headphone jack
Observed by: other thread participant
Issue: Head-phone not recognized, sound continues to be output to speakers - workaround: "Lesser audioswitch" app
Could not reproduce this on my own device
6. WiFi Hotspot - solved
Observed by: other thread participant and confirmed on my own device
Issue: WiFi Hotspot does not work
7. Detailled Battery stats not available - solved
Observed by: other thread participant and confirmed on my own device
Issue: In Battery usage menu, no detail Battery use (per app) available
8. Battery drain - solved
A proper power profile has been added, so battery behavior is quite good now.
IMPORTANT:
Make sure that you make use of 'USB debugging' in the developer options only when you need it and directly turn it off again after use.
Turned on USB debugging is one major reason for battery drain for this device.

Works on Honor 8.
I will test the battery life in the coming days.

this rom passes safety net?

NervReaper said:
this rom passes safety net?
Click to expand...
Click to collapse
No - I don't think so, this ROM is Gapps-free.

it is safe to replace micro-g with opengapps and then install magisk?

rayend322 said:
it is safe to replace micro-g with opengapps and then install magisk?
Click to expand...
Click to collapse
Feel free to try, that's all I can say.
Not sure however, whether it'll work in regards to Gapps.
How do you want to flash them? There is AFAIK no TWRP available being able to decrypt the Huawei /data partitions ...
Regarding Magisk, where you definitely need to access the /data partition, there is some instruction on openkirin.net how to do that.
But as said, you're on your own when doing so!

ROM doesn't route sound to headphones no matter what I do. I tried to force it to switch to headset in phh options and it's still playing sound only on speakers. Also Bluetooth doesn't work, but WLAN and RIL do work.
Stock kernel + stock ramdisk + this ROM
Magisk can be installed by flashing a modified Magisk 18 image that works with B540-02 kernels and then updating it to latest with the manager. But I am not using it for now.
EDIT: Using Lesser Audioswitch from Aurora Store avoids the problem by forcing the audio to be routed manually, but it should work out of the box automatically! Bluetooth still not working.
That aside, good ROM. It is more functional than a generic phh-treble flash and video recording works well. Thanks for your time and effort, this is a good alternative to OpenKirin and ironing out these little issues would make it sweeter. Try looking at other source trees for the necessary device driver definitions
EDIT 2: I misdiagnosed the issue. Bluetooth in fact DOES work, but it has some quirks: The device is initially named 'hello', the BT icon doesn't appear in the status bar and the device must be paired before any transfer, but that seems to be a universal Kirin quirk as well. Further testing pairing, sending, receiving and streaming audio confirm that the BT chip does work but perhaps needs some changes in the Android side.
WLAN, RIL, BT and NFC are all functional.

Wattsensi said:
ROM doesn't route sound to headphones no matter what I do. I tried to force it to switch to headset in phh options and it's still playing sound only on speakers. Also Bluetooth doesn't work, but WLAN and RIL do work.
Stock kernel + stock ramdisk + this ROM
Magisk can be installed by flashing a modified Magisk 18 image that works with B540-02 kernels and then updating it to latest with the manager. But I am not using it for now.
EDIT: Using Lesser Audioswitch from Aurora Store avoids the problem by forcing the audio to be routed manually, but it should work out of the box automatically! Bluetooth still not working.
That aside, good ROM. It is more functional than a generic phh-treble flash and video recording works well. Thanks for your time and effort, this is a good alternative to OpenKirin and ironing out these little issues would make it sweeter. Try looking at other source trees for the necessary device driver definitions
Click to expand...
Click to collapse
Thanks for the comprehensive feedback and the in general positive rating. On my P9, headphones work out of the box - but indeed, the headphone sound isn't that good, will try to have a look here.
Bluetooth works fine as well on my device - haven't tested however after latest tweak for a different area not related to BT. Will test again later today.
Are you using a different device than the P9 maybe?
What is the BT issue exactly on your device?
EDIT: BT works w/o issues, just tested again.

Do you plan to provide regular updates with the latest security patches in the future?

dr4rzz said:
Do you plan to provide regular updates with the latest security patches in the future?
Click to expand...
Click to collapse
Yes, I do - April ASB is "already in the pipeline"...

MSe1969 said:
Are you using a different device than the P9 maybe?
Click to expand...
Click to collapse
It's an EVA-L09 rebranded to AL10, B540 Patch02 firmware. I'm pretty well sure it is indeed an original P9 with a HiSilicon hi3650 SoC.
MSe1969 said:
What is the BT issue exactly on your device?
Click to expand...
Click to collapse
BT icon on status bar doesn't appear when I try to enable Bluetooth, and the menu cannot find any devices. Also the default device is named 'hello' for some reason it seems like the ROM cannot autodetect the BT chip. I'll try to logcat the issue
Again, thanks for the quick response
EDIT: Bluetooth works as intended, but it doesn't display anything.

MSe1969 said:
Yes, I do - April ASB is "already in the pipeline"...
Click to expand...
Click to collapse
Perfect, that's great! Thank you!
I installed the ROM today and most of it works very well so far.
However, some apps like 'Signal Messenger' or 'WhatsApp' are somehow missing in the Aurora Store, whereas some other apps (e.g. Titanium Backup) can be found and installed as usual.
Since the Aurora Store 3.2.4 works fine with OpenKirin OmniRom Pie (tried today) this seems to be an issue of this ROM.
Wattsensi said:
It's an EVA-L09 rebranded to AL10, B540 Patch02 firmware. I'm pretty well sure it is indeed an original P9 with a HiSilicon hi3650 SoC.
BT icon on status bar doesn't appear when I try to enable Bluetooth, and the menu cannot find any devices. Also the default device is named 'hello' for some reason it seems like the ROM cannot autodetect the BT chip. I'll try to logcat the issue
Click to expand...
Click to collapse
I'm also using a P9 EVA-L09 rebranded to AL10.
On my phone the bluetooth connection works fine and if a device is connected, the BT icon also appears in the status bar.
But I can confirm, that there is no bluetooth icon in the status bar, when bluetooth is enabled, but no device is connected.

Most of things are works will , I have issue that can't find Netflix , Snapchat ...etc . In play store but installed Snapchat Manually and can't login. Try hide with magisk but not working , nice ROM.

albelushi7 said:
Most of things are works will , I have issue that can't find Netflix , Snapchat ...etc . In play store but installed Snapchat Manually and can't login. Try hide with magisk but not working , nice ROM.
Click to expand...
Click to collapse
Yeah, made that observation myself with Netflix, too.
Trying to work on it, any hints from anybody appreciated.

Wattsensi said:
It's an EVA-L09 rebranded to AL10, B540 Patch02 firmware. I'm pretty well sure it is indeed an original P9 with a HiSilicon hi3650 SoC.
BT icon on status bar doesn't appear when I try to enable Bluetooth, and the menu cannot find any devices. Also the default device is named 'hello' for some reason it seems like the ROM cannot autodetect the BT chip. I'll try to logcat the issue
Again, thanks for the quick response
Click to expand...
Click to collapse
I have the same device, thanks f. the logs, will have a look soon (after Easter).

dr4rzz said:
Perfect, that's great! Thank you!
I installed the ROM today and most of it works very well so far.
However, some apps like 'Signal Messenger' or 'WhatsApp' are somehow missing in the Aurora Store, whereas some other apps (e.g. Titanium Backup) can be found and installed as usual.
Since the Aurora Store 3.2.4 works fine with OpenKirin OmniRom Pie (tried today) this seems to be an issue of this ROM.
Click to expand...
Click to collapse
I was able w/o issues to see WA and Signal, but not Netflix. As with Netflix, there are special checks, so looking for a solution. Regarding Signal and WA, I know there is currently still an open issue with Aurora and the changed search API by Google, which causes random issues for search results...
dr4rzz said:
I'm also using a P9 EVA-L09 rebranded to AL10.
On my phone the bluetooth connection works fine and if a device is connected, the BT icon also appears in the status bar.
But I can confirm, that there is no bluetooth icon in the status bar, when bluetooth is enabled, but no device is connected.
Click to expand...
Click to collapse
Have same device, will have a closer look, thanks for the hint.

hi, I installed this rom but the phone goes into bootloop. reflash emui 8 original and tried again and bootloop: any ideas?
My P9 EVA-L09 rebranded to AL10

Captive Portal details (Android 11, LineageOS 18)

Hello Forum,
Samsung Galaxy S4, just flashed MicroG's latest build of LineageOS 18 (Android 11). Using ADB, I wanted to change the value of captive_portal_https_url and associated globals to not ping connectivitycheck.gstatic.com. However, I find that these globals do not exist. They are not in the list of global settings, and commands like:
adb shell 'settings put global captive_portal_https_url "https://captiveportal.kuketz.de"'
do not succeed, the error message was something to the effect that this is inaccessible. I did tell ADB to root and remount, it does work to use similar syntax to change other globals. The captive portal check global is set to 1.
I read that Android 11 changed the handling of captive portal to use an API, but the documentation notes that "If the API is not available, or if no portal is advertised, the system will continue to detect portals and verify internet connectivity using HTTP/HTTPS probes, as before." So why am I not seeing the globals captive_portal_http_url, captive_portal_https_url, etc.?
( I have not actually connected the device to any network yet, as I wished to get rid of the google ping before doing so, if that is relevant.)
Thanks.

Sentient Being said:
Hello Forum,
Samsung Galaxy S4, just flashed MicroG's latest build of LineageOS 18 (Android 11). Using ADB, I wanted to change the value of captive_portal_https_url and associated globals to not ping connectivitycheck.gstatic.com. However, I find that these globals do not exist. They are not in the list of global settings, and commands like:
adb shell 'settings put global captive_portal_https_url "https://captiveportal.kuketz.de"'
do not succeed, the error message was something to the effect that this is inaccessible. I did tell ADB to root and remount, it does work to use similar syntax to change other globals. The captive portal check global is set to 1.
I read that Android 11 changed the handling of captive portal to use an API, but the documentation notes that "If the API is not available, or if no portal is advertised, the system will continue to detect portals and verify internet connectivity using HTTP/HTTPS probes, as before." So why am I not seeing the globals captive_portal_http_url, captive_portal_https_url, etc.?
( I have not actually connected the device to any network yet, as I wished to get rid of the google ping before doing so, if that is relevant.)
Thanks.
Click to expand...
Click to collapse
Did you have any luck figuring this out by any chance?

motomotomotoG said:
Did you have any luck figuring this out by any chance?
Click to expand...
Click to collapse
Did you get it figured out?

Maybe this help?
Enhanced Privacy, Security and Battery Duration! My Measures...
Purpose: To share my personal experiences how I achieved an enhancement of my battery’s life, privacy and security. INDEX: Post #1 - General Statements, ROM and Kernel. Post #2 - Privacy Measures and Considerations. Post #3 – Better Battery...
forum.xda-developers.com

General Android 13 QPR3 went final in June 2023-opt-out now to get the OTA without wiping - Pixel 7 Pro [Cheetah] - [thread also for future Android QPR Betas]

Pixel 7 Pro [Cheetah] QPR Betas​
QPR stands for "Quarterly Platform Release". Android 13 QPR3 went final in June 2023. See main thread here for final/non-beta releases.
You can officially opt into the Android Beta Program there, or use the factory image or OTA below. You can no longer manually opt into the QPR3 Beta program - only the Android 14 Beta is offered to opt into:
Spoiler: Details:
xinseo said:
I'm only being allowed to Opt into the Android 14 beta program. I want to enroll in the Android 13 QPR Beta program instead. Any idea how?
Click to expand...
Click to collapse
roirraW edor ehT said:
I don't know for sure, but I suspect that no one can opt into the QPR3 Beta program any longer.
Even Google's QPR3 Beta release page:
Android 13 | Android Developers
<!-- hide description -->
developer.android.com
which has a link:
and leads to:
Get Android 13 | Android Developers
Get an Android 13 on your eligible device.
developer.android.com
the Enroll in Android 13 Beta for Pixel button there still leads to:
Android Beta Program
Android Beta Program allows you to enroll your Android device for beta releases.
www.google.com
which only mentions Android 14 Beta.
So I think your only choice if you want to try QPR3 Beta is to have an unlocked bootloader and flash the factory image, or I think it's possible to sideload the OTA without unlocking the bootloader - but it's highly discouraged to try a Beta with a locked bootloader, as you'll be locked into the Beta program (via manual OTA sideloads) until it goes final, and you'll have no choice but to deal with the issues.
Click to expand...
Click to collapse
Android 13 | Android Developers
<!-- hide description -->
developer.android.com
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developer.android.com
Full OTA Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developer.android.com
I don't plan on testing Betas of any sort, but feel free to use this thread for everything about the QPR Betas or major Android version betas for the Pixel 7 Pro. I'll update the information in the OP when necessary. See Post #2 in my main thread for general information (Unlocking Bootloader / Rooting / Updating | SafetyNet working again | ADB/Fastboot & Windows USB Drivers) but ask questions or make observations about all betas in this thread, please.
Once a QPR or major Android version goes final, I'll take those discussions to my main thread.

This post is too big to update, so I no longer have the most recent old information in here.
Spoiler: Old News
March 29, 2023:
Android 13 QPR3 Beta 2
Android 13 | Android Developers
<!-- hide description -->
developer.android.com
Release notes​bookmark
Beta 2Beta 1
Release dateMarch 29, 2023BuildT3B2.230316.003Security patch levelMarch 2023Google Play services23.08.15
About Android 13 QPR3​Following the stable release of Android 13 to AOSP, we continue to update the platform with fixes and improvements that are then rolled out to supported devices. These releases happen on a quarterly cadence through Quarterly Platform Releases (QPRs), which are delivered both to AOSP and to Google Pixel devices as part of Feature Drops.
Although these updates don't include app-impacting API changes, we provide images of the latest QPR beta builds so you can test your app with these builds as needed.
Unlike developer previews and betas for unreleased versions of Android, these builds are suitable for general use. However, please review any known issues that are listed on this page.
Android 13 QPR3 builds on the updates in Android 13 QPR2 and the initial Android 13 release and includes the next round of refinements such as bug fixes and improvements to stability and performance.
How to get QPR3 Beta 2​You can install Android 13 QPR3 Beta 2 on any of the following Google Pixel devices:
Pixel 4a and 4a (5G)
Pixel 5 and 5a
Pixel 6 and 6 Pro
Pixel 6a
Pixel 7 and 7 Pro
See Get Android 13 QPR beta builds for details on how to get started.
General advisories​Be aware of these general advisories about the release:
This release might have various stability, battery, or performance issues.
For users with accessibility needs, this release might not be appropriate for daily use.
Some apps might not function as expected when running on this release. This limitation includes Google's apps as well as other apps.
Android 13 QPR beta builds aren't Compatibility Test Suite (CTS)‑approved, but they have passed preliminary testing and provide a stable set of pre-release APIs for developers. Apps that depend on CTS-approved builds or use SafetyNet APIs might not work normally on Android 13 QPR beta builds.
Get support​Two primary support channels are available to you when developing and testing with Android 13 QPR3. The channel you should use to get support depends on where you are encountering your issue.
Support for device-specific issues, system issues, and issues with Google apps: Use the Issue Tracker to create new issues and to view and track issues that you and other developers have submitted.
Before creating your own issue, check the known issues listed on this page and search the lists of top open issues and recently created issues to see if someone else has already reported it. You can subscribe and vote for an issue by clicking star this issue.
See Where to report issues to find an issue template that best matches the type of issue that you are encountering.
Support for issues with other apps: Contact the app developer directly.
To discuss issues or ideas with other developers working with the Android 13 QPR Beta, join the android_beta community on Reddit.
Feature updates​
Improvements for Adaptive Charging that can automatically adjust to your charging needs using on-device signals.
Top resolved issues​The following issues have been resolved in Android 13 QPR3 Beta 2:
Fixed an issue that caused the volume panel to flicker when adjusting the volume using the volume buttons.
Fixed an issue that caused the system UI to get stuck in a blurry state in some cases, such as unlocking the device or finishing a phone call.
Fixed an issue where the notification shade was closing immediately after a user opened it.
Fixed an issue where the always-on display was displayed over apps and other content after unlocking the device.
Fixed an issue where a device couldn't copy apps and data wirelessly during first-time setup.
Top open issues​See top open issues for the latest list of top open issues that have been reported.
Other known issues​Based on our testing, you might encounter the following issues when using Android 13 QPR3. These issues are already known, so there's no need to file additional reports for similar issues.
Android Platform​
If the user tries to open the camera by pressing the power button twice, the camera displays a black screen instead.
In some cases when a work profile is switched on or off, the device reboots instead.
The list of Recent apps sometimes becomes unresponsive if the screen orientation is changed while the list is open.
Previous beta releases​Android 13 QPR3 Beta 1​Top resolved issues​The following issues have been resolved in Android 13 QPR3 Beta 1:
Fixed an issue where the clock text on the lockscreen was the wrong color.
Fixed an issue where Bluetooth audio wasn't working on some devices.
Fixed an issue where the fingerprint icon that is normally displayed on screen to indicate the position of the fingerprint sensor erroneously changed to an exclamation point (!).
Fixed an issue where live wallpapers could not be selected or used.
Fixed an issue where widgets, app icon positions, and other configurable options on the home screen were reset after installing an OTA update.
Fixed an issue that caused a device to be unenrolled from Face Unlock after installing an OTA update.
Other known issues​Based on our testing, you might encounter the following issues when using Android 13 QPR3 Beta 1. These issues are already known, so there's no need to file additional reports for similar issues.
Android Platform​
If the user tries to open the camera by pressing the power button twice, the camera displays a black screen instead.
In some cases when a work profile is switched on or off, the device reboots instead.
The list of Recent apps sometimes becomes unresponsive if the screen orientation is changed while the list is open.
Click to expand...
Click to collapse
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developer.android.com
Pixel 7 Procheetah-t3b2.230316.003-factory-06c87aeb.zip06c87aeb6ad1182f5735461a483f650e0c5ecc598dd5b35f68c5d36980913890
Full OTA Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developer.android.com
Pixel 7 Procheetah-ota-t3b2.230316.003-4bca3e1b.zip4bca3e1bf0a255354da9db7d77a10653f937d6720257dfa1b18d21b4cd68095b
March 15, 2023:
Other known issues​Based on our testing, you might encounter the following issues when using Android 13 QPR3. These issues are already known, so there's no need to file additional reports for similar issues.
Android Platform​
If the user tries to open the camera by pressing the power button twice, the camera displays a black screen instead.
In some cases when a work profile is switched on or off, the device reboots instead.
The list of Recent apps sometimes becomes unresponsive if the screen orientation is changed while the list is open.
Click to expand...
Click to collapse
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developer.android.com
Pixel 7 Procheetah-t3b1.230224.005-factory-08d6844d.zip08d6844d038fe0f104121c8d5967328d5f12817bd68e9cea80f74a12965f52ee
Full OTA Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developer.android.com
Pixel 7 Procheetah-ota-t3b1.230224.005-b9ea6269.zipb9ea62698c96f7d66e74c0104410388436ad1df00ac88c5c76c3134610ca82e9
Android 13 | Android Developers
<!-- hide description -->
developer.android.com
Release notes​bookmark
Beta 1
Release dateMarch 15, 2023BuildT3B1.230224.005Security patch levelMarch 2023Google Play services23.08.15
About Android 13 QPR3​Following the stable release of Android 13 to AOSP, we continue to update the platform with fixes and improvements that are then rolled out to supported devices. These releases happen on a quarterly cadence through Quarterly Platform Releases (QPRs), which are delivered both to AOSP and to Google Pixel devices as part of Feature Drops.
Although these updates don't include app-impacting API changes, we provide images of the latest QPR beta builds so you can test your app with these builds as needed.
Unlike developer previews and betas for unreleased versions of Android, these builds are suitable for general use. However, please review any known issues that are listed on this page.
Android 13 QPR3 builds on the updates in Android 13 QPR2 and the initial Android 13 release and includes the next round of refinements such as bug fixes and improvements to stability and performance.
How to get QPR3 Beta 1​You can install Android 13 QPR3 Beta 1 on any of the following Google Pixel devices:
Pixel 4a and 4a (5G)
Pixel 5 and 5a
Pixel 6 and 6 Pro
Pixel 6a
Pixel 7 and 7 Pro
See Get Android 13 QPR beta builds for details on how to get started.
General advisories​Be aware of these general advisories about the release:
This release might have various stability, battery, or performance issues.
For users with accessibility needs, this release might not be appropriate for daily use.
Some apps might not function as expected when running on this release. This limitation includes Google's apps as well as other apps.
Android 13 QPR beta builds aren't Compatibility Test Suite (CTS)‑approved, but they have passed preliminary testing and provide a stable set of pre-release APIs for developers. Apps that depend on CTS-approved builds or use SafetyNet APIs might not work normally on Android 13 QPR beta builds.
Get support​Two primary support channels are available to you when developing and testing with Android 13 QPR3. The channel you should use to get support depends on where you are encountering your issue.
Support for device-specific issues, system issues, and issues with Google apps: Use the Issue Tracker to create new issues and to view and track issues that you and other developers have submitted.
Before creating your own issue, check the known issues listed on this page and search the lists of top open issues and recently created issues to see if someone else has already reported it. You can subscribe and vote for an issue by clicking star this issue .
See Where to report issues to find an issue template that best matches the type of issue that you are encountering.
Support for issues with other apps: Contact the app developer directly.
To discuss issues or ideas with other developers working with the Android 13 QPR Beta, join the android_beta community on Reddit.
Top resolved issues​The following issues have been resolved in Android 13 QPR3 Beta 1:
Fixed an issue where the clock text on the lockscreen was the wrong color.
Fixed an issue where Bluetooth audio wasn't working on some devices.
Fixed an issue where the fingerprint icon that is normally displayed on screen to indicate the position of the fingerprint sensor erroneously changed to an exclamation point (!).
Fixed an issue where live wallpapers could not be selected or used.
Fixed an issue where widgets, app icon positions, and other configurable options on the home screen were reset after installing an OTA update.
Fixed an issue that caused a device to be unenrolled from Face Unlock after installing an OTA update.
Top open issues​See top open issues for the latest list of top open issues that have been reported.
Click to expand...
Click to collapse
Other known issues​Based on our testing, you might encounter the following issues when using Android 13 QPR3. These issues are already known, so there's no need to file additional reports for similar issues.
Android Platform​
If the user tries to open the camera by pressing the power button twice, the camera displays a black screen instead.
In some cases when a work profile is switched on or off, the device reboots instead.
The list of Recent apps sometimes becomes unresponsive if the screen orientation is changed while the list is open.
Click to expand...
Click to collapse
Lughnasadh said:
https://twitter.com/i/web/status/1634291746598207488
Click to expand...
Click to collapse
Note @Lughnasadh's post from the Pixel 7 Pro QPR thread, and XDA's article below:
Android 13 QPR3 Beta 1 set to arrive next week
It looks like Google is ready to start its next stage of testing, as it is set to release Android 13 QPR3 Beta 1 next week.
www.xda-developers.com
Android 13 QPR3 Beta 1 set to arrive next week​BYTIMI CANTISANO
PUBLISHED 20 HOURS AGO
It looks like Google is ready to start its next stage of testing, as it is set to release Android 13 QPR3 Beta 1 next week.
Pixel 7 Pro in Snow
Readers like you help support XDA Developers. When you make a purchase using links on our site, we may earn an affiliate commission. Read More.
Well, it looks like Google is ready to move onto the next step of its QPR (Quarterly Platform Release) beta program, announcing that Android 13 QPR3 Beta 1 will be arriving next week. This beta will allow users to get an early look at the Android 13 QPR3 release set to make its debut sometime in June.
The company announced the news through Reddit, giving users an early heads up of what to expect. While it didn't get into the details of what might show up in the beta release, it did state that those enrolled in the current Beta Program would automatically get the latest update when it's released.
Now, one thing to note, and something Google does state, is that in order to be eligible for the stable release of Android 13 QPR2, users will need to manually opt out. Previously, this update was rolled out to those in the Beta Program, but going forward, it looks like if you're enrolled in the beta, you'll just keep receiving beta releases, skipping over the general release of the OS.
While this isn't a big deal, sometimes betas aren't all that stable, so if you are using this on your main device, now might be a perfect time to opt out. Of course, you can always choose to opt out at any time, but by doing so in a beta release cycle you'll be forced to wipe out your device and start fresh. So, if you're having any second thoughts, now's the time to make the change.
Google does have some tips for users ahead of the Android 13 QPR3 Beta 1 release, stating that if you've opted out, just wait until the stable release and apply that update instead of downgrading. The main reason to go this route, and as stated above, is to avoid wiping your device. Now, for the most part, this and any other beta from Google will be released through its Beta Program or you can download and install the beta updates manually too.
Source: Reddit
Click to expand...
Click to collapse
For anyone who doesn't notice Google's official announcement in those above, and what to do if you're on the QPR2 Beta 3.x and want to be on stable:
https://www.reddit.com/r/android_beta/comments/11nz32q
Hi Beta users,
With the release of our final Android 13 QPR2 Beta update a few weeks ago, we are now preparing for our next Beta Program cycle that covers our Android 13 June release (QPR3). Android 13 QPR3 Beta 1 will kick off the week of March 13th. If you take no action and remain enrolled in the Beta Program, you will automatically receive Android 13 QPR3 Beta 1 starting next week.
We are changing our beta release process - to receive the upcoming March QPR2 public stable release, devices currently enrolled in Beta will need to first opt out of the program. Devices that remain enrolled in the Beta Program will receive Android 13 QPR3 Beta 1.
If you prefer to exit the Beta Program and receive the final public March QPR2 update without the need to wipe your data, please do one of the following:
Opt out of the program before March 13th, ignore/don’t apply the downgrade OTA update, and wait for the final public stable release of the March Feature Drop (QPR2) releasing this month. Opting out will not cause a data wipe as long as you don’t apply the downgrade OTA. Note: If you want to immediately return to the latest public version, you can apply the downgrade OTA which will require a data wipe per usual program guidelines.
If you receive the Android 13 QPR3 Beta 1 update, don’t install the update. Instead, first opt out of the program, ignore/don’t apply the downgrade OTA update, and wait for the official March public release. Note: If you opt-out of the program after installing the QPR3 beta 1 update, all user data on the device will get wiped per usual program guidelines.
We will continue to post updates and information on the upcoming Android 13 QPR3 Beta here in this community.
Click to expand...
Click to collapse
February 22, 2023:
QPR2 Beta 3.2:
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developer.android.com
Pixel 7 Procheetah-t2b3.230109.006.a1-factory-117742bc.zip117742bc5147f87f1b99337b4ba43fb5fcdbfd1277a80c87d0d0b17d71baa8d7
Full OTA Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developer.android.com
Pixel 7 Procheetah-ota-t2b3.230109.006.a1-e7cf02d7.zipe7cf02d73032f7e96dec3893e2a54ea89d460a2257abd3680a6ab443be2a2c05
Android 13 | Android Developers
<!-- hide description -->
developer.android.com
Beta 3.2Beta 3.1Beta 3Beta 2.1Beta 2Beta 1
Release dateFebruary 22, 2023BuildT2B3.230109.009, T2B3.230109.006.A1 (Pixel 7 Pro only)Security patch levelFebruary 2023Google Play services23.03.13
Android 13 QPR2 Beta 3.2 (February 2023)
This minor update to Android 13 QPR2 Beta 3 includes the following fixes:
Fixed issues that sometimes caused the screen on some devices to flash green or display other visual artifacts. (Issue #260941279, Issue #256052135)
Jio 5G network is now enabled for Pixel 6 and 7 series devices.
If you're already running a beta build, you'll automatically receive an over-the-air (OTA) update to Beta 3.2.
Note: Other known issues listed for the Beta 3 release still apply to Beta 3.2.
Android 13 QPR2 Beta 3.1 (February 2023)
This minor update to Android 13 QPR2 Beta 3 includes the following fixes:
Fixed an issue in the system Bluetooth module that could have allowed for possible out-of-bounds writes due to memory corruption. (Issue #259630761)
Fixed an issue where some Romanian translations were missing from the system image.
About Android 13 QPR2​Following the stable release of Android 13 to AOSP, we continue to update the platform with fixes and improvements that are then rolled out to supported devices. These releases happen on a quarterly cadence through Quarterly Platform Releases (QPRs), which are delivered both to AOSP and to Google Pixel devices as part of Feature Drops.
Although these updates don't include app-impacting API changes, we provide images of the latest QPR beta builds so you can test your app with these builds as needed.
Unlike developer previews and betas for unreleased versions of Android, these builds are suitable for general use. However, please review any known issues that are listed on this page.
Android 13 QPR2 builds on the updates in Android 13 QPR1 and the Android 13 initial release and includes the next round of refinements such as bug fixes and improvements to stability and performance.
How to get QPR2 Beta 3.2​You can install Android 13 QPR2 Beta 3.2 on any of the following Google Pixel devices:
Pixel 4a and 4a (5G)
Pixel 5 and 5a
Pixel 6 and 6 Pro
Pixel 6a
Pixel 7 and 7 Pro
See Get Android 13 QPR beta builds for details on how to get started.
General advisories​Be aware of these general advisories about the release:
This release might have various stability, battery, or performance issues.
For users with accessibility needs, this release might not be appropriate for daily use.
Some apps might not function as expected when running on this release. This limitation includes Google's apps as well as other apps.
Android 13 QPR beta builds aren't Compatibility Test Suite (CTS)‑approved, but they have passed preliminary testing and provide a stable set of pre-release APIs for developers. Apps that depend on CTS-approved builds or use SafetyNet APIs might not work normally on Android 13 QPR beta builds.
Get support​Two primary support channels are available to you when developing and testing with Android 13 QPR2. The channel you should use to get support depends on where you are encountering your issue.
Support for device-specific issues, system issues, and issues with Google apps: Use the Issue Tracker to create new issues and to view and track issues that you and other developers have submitted.
Before creating your own issue, check the known issues listed on this page and search the lists of top open issues and recently created issues to see if someone else has already reported it. You can subscribe and vote for an issue by clicking star this issue .
See Where to report issues to find an issue template that best matches the type of issue that you are encountering.
Support for issues with other apps: Contact the app developer directly.
To discuss issues or ideas with other developers working with the Android 13 QPR Beta, join the android_beta community on Reddit.
Top resolved issues​The following issues have been resolved in Android 13 QPR2 Beta 3:
Developer-reported and user-reported issues​
Fixed an issue where notifications in a notification group were sometimes displayed with straight corners instead of rounded corners. (Issue #264287776, Issue #265529116)
Fixed an issue where the message in the notification shade that indicates an active VPN connection overlapped with the message about apps with active foreground services. (Issue #266075977)
Fixed an issue where the overflow menu couldn't be accessed when editing Quick Settings tiles. (Issue #263484657)
Fixed an issue that sometimes caused a device with vibration enabled to vibrate for too long after it received a notification. (Issue #239676913)
Other resolved issues​
Fixed an issue that sometimes caused messaging apps to crash or fail to send notifications.
Fixed a GPU issue that prevented apps from using certain visual effects.
Fixed an issue where Quick Settings tiles for a work profile were not added after setting up a new device.
Fixed an issue that sometimes caused the Pixel launcher to crash when using the Search bar in the app drawer.
Fixed an issue that sometimes prevented a device from being unlocked using a pattern after the Google Assistant was activated.
Fixed an issue in the com.android.qns system process that sometimes caused crashes.
Fixed an issue with the Pixel launcher that prevented Chinese text input from being recognized when typing in the Search bar in the app drawer.
Fixed an issue where when entering and exiting Picture-in-picture (PiP) mode from an app after changing the screen orientation, the system Settings app crashed with a "Settings keeps stopping" message and then the system Settings app couldn't be opened.
Fixed an issue with the System UI that sometimes caused it to crash from a null pointer exception.
Fixed an issue where the connection status of a Bluetooth device sometimes did not match the actual device state.
Fixed an issue where the Pixel launcher crashed when a user tapped a web search suggestion for a query term.
Fixed an issue that caused status bar icons to overlap with the date text when font and display settings were set to their maximum level on a device.
Top open issues​See top open issues for the latest list of top open issues that have been reported.
Other known issues​Based on our testing, you might encounter the following issues when using Android 13 QPR2. These issues are already known, so there's no need to file additional reports for similar issues.
Android Platform​
The list of Recent apps sometimes becomes unresponsive if the screen orientation is changed while the list is open.
Previous beta releases​Android 13 QPR1 Beta 2​Android 13 QPR2 Beta 2.1 (January 2023)
This minor update to Android 13 QPR2 Beta 2 includes the following fixes:
Fixed an issue that sometimes prevented devices from automatically connecting to a 5G network even when it was available. (Issue #265093352)
Fixed an issue where devices did not drop or reset an existing, encrypted Bluetooth connection after receiving a command to disable link-layer encryption for that connection.
Top resolved issues​The following issues have been resolved in Android 13 QPR2 Beta 2:
Fixed an issue with the System UI that sometimes caused the Home screen to become unresponsive.
Fixed an issue where, after switching back to Normal video capture mode from Slow Motion mode in the Google Camera app, the app continued capturing slow-motion video if the capture speed was changed between 1/8x and 1/4x while in Slow Motion mode.
Other known issues​Based on our testing, you might encounter the following issues when using Android 13 QPR2 Beta 2. These issues are already known, so there's no need to file additional reports for similar issues.
Android Platform​
The list of Recent apps sometimes becomes unresponsive if the screen orientation is changed while the list is open.
In some cases when entering and exiting Picture-in-picture (PiP) mode from an app after changing the screen orientation, the system Settings app crashes with a "Settings keeps stopping" message and then the system Settings app can't be opened.
An issue with the System UI can sometimes cause it to crash from a null pointer exception.
Android 13 QPR1 Beta 1​Other known issues​Based on our testing, you might encounter the following issues when using Android 13 QPR2 Beta 1. These issues are already known, so there's no need to file additional reports for similar issues.
Android Platform​
The list of Recent apps sometimes becomes unresponsive if the screen orientation is changed while the list is open.
In some cases when entering and exiting Picture-in-picture (PiP) mode from an app after changing the screen orientation, the system Settings app crashes with a "Settings keeps stopping" message and then the system Settings app can't be opened.
An issue with the System UI can sometimes cause the Home screen to become unresponsive.
Google Apps​
After switching back to Normal video capture mode from Slow Motion mode in the Google Camera app, the app continues capturing slow-motion video if the capture speed was changed between 1/8x and 1/4x while in Slow Motion mode.
Click to expand...
Click to collapse
February 9, 2023:
Android 13 QPR2 Beta 3.1 (February 2023)
Android 13 | Android Developers
<!-- hide description -->
developer.android.com
Android Developers
Platform
Releases
Release notes​bookmark
Beta 3.1Beta 3Beta 2.1Beta 2Beta 1
Release dateFebruary 9, 2023BuildT2B3.230109.004Security patch levelFebruary 2023Google Play services23.03.13
Android 13 QPR2 Beta 3.1 (February 2023)
This minor update to Android 13 QPR2 Beta 3 includes the following fixes:
Fixed an issue in the system Bluetooth module that could have allowed for possible out-of-bounds writes due to memory corruption. (Issue #259630761)
Fixed an issue where some Romanian translations were missing from the system image.
If you're already running a beta build, you'll automatically receive an over-the-air (OTA) update to Beta 3.1.
Note: Other known issues listed for the Beta 3 release still apply to Beta 3.1.
About Android 13 QPR2​Following the stable release of Android 13 to AOSP, we continue to update the platform with fixes and improvements that are then rolled out to supported devices. These releases happen on a quarterly cadence through Quarterly Platform Releases (QPRs), which are delivered both to AOSP and to Google Pixel devices as part of Feature Drops.
Although these updates don't include app-impacting API changes, we provide images of the latest QPR beta builds so you can test your app with these builds as needed.
Unlike developer previews and betas for unreleased versions of Android, these builds are suitable for general use. However, please review any known issues that are listed on this page.
Android 13 QPR2 builds on the updates in Android 13 QPR1 and the Android 13 initial release and includes the next round of refinements such as bug fixes and improvements to stability and performance.
How to get QPR2 Beta 3.1​You can install Android 13 QPR2 Beta 3.1 on any of the following Google Pixel devices:
Pixel 4a and 4a (5G)
Pixel 5 and 5a
Pixel 6 and 6 Pro
Pixel 6a
Pixel 7 and 7 Pro
See Get Android 13 QPR beta builds for details on how to get started.
General advisories​Be aware of these general advisories about the release:
This release might have various stability, battery, or performance issues.
For users with accessibility needs, this release might not be appropriate for daily use.
Some apps might not function as expected when running on this release. This limitation includes Google's apps as well as other apps.
Android 13 QPR beta builds aren't Compatibility Test Suite (CTS)‑approved, but they have passed preliminary testing and provide a stable set of pre-release APIs for developers. Apps that depend on CTS-approved builds or use SafetyNet APIs might not work normally on Android 13 QPR beta builds.
Get support​Two primary support channels are available to you when developing and testing with Android 13 QPR2. The channel you should use to get support depends on where you are encountering your issue.
Support for device-specific issues, system issues, and issues with Google apps: Use the Issue Tracker to create new issues and to view and track issues that you and other developers have submitted.
Before creating your own issue, check the known issues listed on this page and search the lists of top open issues and recently created issues to see if someone else has already reported it. You can subscribe and vote for an issue by clicking star this issue .
See Where to report issues to find an issue template that best matches the type of issue that you are encountering.
Support for issues with other apps: Contact the app developer directly.
To discuss issues or ideas with other developers working with the Android 13 QPR Beta, join the android_beta community on Reddit.
Top resolved issues​The following issues have been resolved in Android 13 QPR2 Beta 3:
Developer-reported and user-reported issues​
Fixed an issue where notifications in a notification group were sometimes displayed with straight corners instead of rounded corners. (Issue #264287776, Issue #265529116)
Fixed an issue where the message in the notification shade that indicates an active VPN connection overlapped with the message about apps with active foreground services. (Issue #266075977)
Fixed an issue where the overflow menu couldn't be accessed when editing Quick Settings tiles. (Issue #263484657)
Fixed an issue that sometimes caused a device with vibration enabled to vibrate for too long after it received a notification. (Issue #239676913)
Other resolved issues​
Fixed an issue that sometimes caused messaging apps to crash or fail to send notifications.
Fixed a GPU issue that prevented apps from using certain visual effects.
Fixed an issue where Quick Settings tiles for a work profile were not added after setting up a new device.
Fixed an issue that sometimes caused the Pixel launcher to crash when using the Search bar in the app drawer.
Fixed an issue that sometimes prevented a device from being unlocked using a pattern after the Google Assistant was activated.
Fixed an issue in the com.android.qns system process that sometimes caused crashes.
Fixed an issue with the Pixel launcher that prevented Chinese text input from being recognized when typing in the Search bar in the app drawer.
Fixed an issue where when entering and exiting Picture-in-picture (PiP) mode from an app after changing the screen orientation, the system Settings app crashed with a "Settings keeps stopping" message and then the system Settings app couldn't be opened.
Fixed an issue with the System UI that sometimes caused it to crash from a null pointer exception.
Fixed an issue where the connection status of a Bluetooth device sometimes did not match the actual device state.
Fixed an issue where the Pixel launcher crashed when a user tapped a web search suggestion for a query term.
Fixed an issue that caused status bar icons to overlap with the date text when font and display settings were set to their maximum level on a device.
Top open issues​See top open issues for the latest list of top open issues that have been reported.
Other known issues​Based on our testing, you might encounter the following issues when using Android 13 QPR2. These issues are already known, so there's no need to file additional reports for similar issues.
Android Platform​
The list of Recent apps sometimes becomes unresponsive if the screen orientation is changed while the list is open.
Previous beta releases​Android 13 QPR1 Beta 2​Android 13 QPR2 Beta 2.1 (January 2023)
This minor update to Android 13 QPR2 Beta 2 includes the following fixes:
Fixed an issue that sometimes prevented devices from automatically connecting to a 5G network even when it was available. (Issue #265093352)
Fixed an issue where devices did not drop or reset an existing, encrypted Bluetooth connection after receiving a command to disable link-layer encryption for that connection.
Top resolved issues​The following issues have been resolved in Android 13 QPR2 Beta 2:
Fixed an issue with the System UI that sometimes caused the Home screen to become unresponsive.
Fixed an issue where, after switching back to Normal video capture mode from Slow Motion mode in the Google Camera app, the app continued capturing slow-motion video if the capture speed was changed between 1/8x and 1/4x while in Slow Motion mode.
Other known issues​Based on our testing, you might encounter the following issues when using Android 13 QPR2 Beta 2. These issues are already known, so there's no need to file additional reports for similar issues.
Android Platform​
The list of Recent apps sometimes becomes unresponsive if the screen orientation is changed while the list is open.
In some cases when entering and exiting Picture-in-picture (PiP) mode from an app after changing the screen orientation, the system Settings app crashes with a "Settings keeps stopping" message and then the system Settings app can't be opened.
An issue with the System UI can sometimes cause it to crash from a null pointer exception.
Android 13 QPR1 Beta 1​Other known issues​Based on our testing, you might encounter the following issues when using Android 13 QPR2 Beta 1. These issues are already known, so there's no need to file additional reports for similar issues.
Android Platform​
The list of Recent apps sometimes becomes unresponsive if the screen orientation is changed while the list is open.
In some cases when entering and exiting Picture-in-picture (PiP) mode from an app after changing the screen orientation, the system Settings app crashes with a "Settings keeps stopping" message and then the system Settings app can't be opened.
An issue with the System UI can sometimes cause the Home screen to become unresponsive.
Google Apps​
After switching back to Normal video capture mode from Slow Motion mode in the Google Camera app, the app continues capturing slow-motion video if the capture speed was changed between 1/8x and 1/4x while in Slow Motion mode.
Click to expand...
Click to collapse
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developer.android.com
Pixel 7 Procheetah-t2b3.230109.004-factory-004d470e.zip004d470e960d6240ebcf48d713f2b9a2c0b63bc307532216c85c9e48a92fce19
Full OTA Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developer.android.com
Pixel 7 Procheetah-ota-t2b3.230109.004-1fc7be52.zip1fc7be522cf1f0757f6bd4f2b9b5fbc2ab827580aad62502870d063795adf507
February 1, 2023:
QPR2 Beta 3
Pixel 7 Procheetah-t2b3.230109.002-factory-9b7903db.zip9b7903dbcf23bb41d1e3d86ed16eb5cd4309187c0def3aff148410dc34fcda5d
https://developer.android.com/about/versions/13/release-notes#beta3
Release notes​bookmark
Beta 3Beta 2.1Beta 2Beta 1
Release dateFebruary 1, 2023BuildT2B3.230109.002Security patch levelJanuary 2023Google Play services23.03.13
About Android 13 QPR2​Following the stable release of Android 13 to AOSP, we continue to update the platform with fixes and improvements that are then rolled out to supported devices. These releases happen on a quarterly cadence through Quarterly Platform Releases (QPRs), which are delivered both to AOSP and to Google Pixel devices as part of Feature Drops.
Although these updates don't include app-impacting API changes, we provide images of the latest QPR beta builds so you can test your app with these builds as needed.
Unlike developer previews and betas for unreleased versions of Android, these builds are suitable for general use. However, please review any known issues that are listed on this page.
Android 13 QPR2 builds on the updates in Android 13 QPR1 and the Android 13 initial release and includes the next round of refinements such as bug fixes and improvements to stability and performance.
How to get QPR2 Beta 3​You can install Android 13 QPR2 Beta 3 on any of the following Google Pixel devices:
Pixel 4a and 4a (5G)
Pixel 5 and 5a
Pixel 6 and 6 Pro
Pixel 6a
Pixel 7 and 7 Pro
See Get Android 13 QPR beta builds for details on how to get started.
General advisories​Be aware of these general advisories about the release:
This release might have various stability, battery, or performance issues.
For users with accessibility needs, this release might not be appropriate for daily use.
Some apps might not function as expected when running on this release. This limitation includes Google's apps as well as other apps.
Android 13 QPR beta builds aren't Compatibility Test Suite (CTS)‑approved, but they have passed preliminary testing and provide a stable set of pre-release APIs for developers. Apps that depend on CTS-approved builds or use SafetyNet APIs might not work normally on Android 13 QPR beta builds.
Get support​Two primary support channels are available to you when developing and testing with Android 13 QPR2. The channel you should use to get support depends on where you are encountering your issue.
Support for device-specific issues, system issues, and issues with Google apps: Use the Issue Tracker to create new issues and to view and track issues that you and other developers have submitted.
Before creating your own issue, check the known issues listed on this page and search the lists of top open issues and recently created issues to see if someone else has already reported it. You can subscribe and vote for an issue by clicking star this issue .
See Where to report issues to find an issue template that best matches the type of issue that you are encountering.
Support for issues with other apps: Contact the app developer directly.
To discuss issues or ideas with other developers working with the Android 13 QPR Beta, join the android_beta community on Reddit.
Top resolved issues​The following issues have been resolved in Android 13 QPR2 Beta 3:
Developer-reported and user-reported issues​
Fixed an issue where notifications in a notification group were sometimes displayed with straight corners instead of rounded corners. (Issue #264287776, Issue #265529116)
Fixed an issue where the message in the notification shade that indicates an active VPN connection overlapped with the message about apps with active foreground services. (Issue #266075977)
Fixed an issue where the overflow menu couldn't be accessed when editing Quick Settings tiles. (Issue #263484657)
Fixed an issue that sometimes caused a device with vibration enabled to vibrate for too long after it received a notification. (Issue #239676913)
Other resolved issues​
Fixed an issue that sometimes caused messaging apps to crash or fail to send notifications.
Fixed a GPU issue that prevented apps from using certain visual effects.
Fixed an issue where Quick Settings tiles for a work profile were not added after setting up a new device.
Fixed an issue that sometimes caused the Pixel launcher to crash when using the Search bar in the app drawer.
Fixed an issue that sometimes prevented a device from being unlocked using a pattern after the Google Assistant was activated.
Fixed an issue in the com.android.qns system process that sometimes caused crashes.
Fixed an issue with the Pixel launcher that prevented Chinese text input from being recognized when typing in the Search bar in the app drawer.
Fixed an issue where when entering and exiting Picture-in-picture (PiP) mode from an app after changing the screen orientation, the system Settings app crashed with a "Settings keeps stopping" message and then the system Settings app couldn't be opened.
Fixed an issue with the System UI that sometimes caused it to crash from a null pointer exception.
Fixed an issue where the connection status of a Bluetooth device sometimes did not match the actual device state.
Fixed an issue where the Pixel launcher crashed when a user tapped a web search suggestion for a query term.
Fixed an issue that caused status bar icons to overlap with the date text when font and display settings were set to their maximum level on a device.
Top open issues​See top open issues for the latest list of top open issues that have been reported.
Other known issues​Based on our testing, you might encounter the following issues when using Android 13 QPR2. These issues are already known, so there's no need to file additional reports for similar issues.
Android Platform​
The list of Recent apps sometimes becomes unresponsive if the screen orientation is changed while the list is open.
Previous beta releases​Android 13 QPR1 Beta 2​Android 13 QPR2 Beta 2.1 (January 2023)
This minor update to Android 13 QPR2 Beta 2 includes the following fixes:
Fixed an issue that sometimes prevented devices from automatically connecting to a 5G network even when it was available. (Issue #265093352)
Fixed an issue where devices did not drop or reset an existing, encrypted Bluetooth connection after receiving a command to disable link-layer encryption for that connection.
Top resolved issues​The following issues have been resolved in Android 13 QPR2 Beta 2:
Fixed an issue with the System UI that sometimes caused the Home screen to become unresponsive.
Fixed an issue where, after switching back to Normal video capture mode from Slow Motion mode in the Google Camera app, the app continued capturing slow-motion video if the capture speed was changed between 1/8x and 1/4x while in Slow Motion mode.
Other known issues​Based on our testing, you might encounter the following issues when using Android 13 QPR2 Beta 2. These issues are already known, so there's no need to file additional reports for similar issues.
Android Platform​
The list of Recent apps sometimes becomes unresponsive if the screen orientation is changed while the list is open.
In some cases when entering and exiting Picture-in-picture (PiP) mode from an app after changing the screen orientation, the system Settings app crashes with a "Settings keeps stopping" message and then the system Settings app can't be opened.
An issue with the System UI can sometimes cause it to crash from a null pointer exception.
Android 13 QPR1 Beta 1​Other known issues​Based on our testing, you might encounter the following issues when using Android 13 QPR2 Beta 1. These issues are already known, so there's no need to file additional reports for similar issues.
Android Platform​
The list of Recent apps sometimes becomes unresponsive if the screen orientation is changed while the list is open.
In some cases when entering and exiting Picture-in-picture (PiP) mode from an app after changing the screen orientation, the system Settings app crashes with a "Settings keeps stopping" message and then the system Settings app can't be opened.
An issue with the System UI can sometimes cause the Home screen to become unresponsive.
Google Apps​
After switching back to Normal video capture mode from Slow Motion mode in the Google Camera app, the app continues capturing slow-motion video if the capture speed was changed between 1/8x and 1/4x while in Slow Motion mode.
Click to expand...
Click to collapse
January 20, 2023:
Beta 2.1:
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developer.android.com
Normal system images: Use https://flash.android.com/preview/tm-qpr2-beta2.1
Pixel 7 Procheetah-t2b2.221216.008-factory-36873c04.zip36873c042e0eacb4fa634afe053444c4885c10c38565bcb01518750dc8030610
Android 13 | Android Developers
<!-- hide description -->
developer.android.com
Release notes​bookmark
Beta 2.1Beta 2Beta 1
Release dateJanuary 20, 2023BuildT2B2.221216.008Security patch levelJanuary 2023Google Play services22.41.13
Android 13 QPR2 Beta 2.1 (January 2023)
This minor update to Android 13 QPR2 Beta 2 includes the following fixes:
Fixed an issue that sometimes prevented devices from automatically connecting to a 5G network even when it was available. (Issue #265093352)
Fixed an issue where devices did not drop or reset an existing, encrypted Bluetooth connection after receiving a command to disable link-layer encryption for that connection.
About Android 13 QPR2​Following the stable release of Android 13 to AOSP, we continue to update the platform with fixes and improvements that are then rolled out to supported devices. These releases happen on a quarterly cadence through Quarterly Platform Releases (QPRs), which are delivered both to AOSP and to Google Pixel devices as part of Feature Drops.
Although these updates don't include app-impacting API changes, we provide images of the latest QPR beta builds so you can test your app with these builds as needed.
Unlike developer previews and betas for unreleased versions of Android, these builds are suitable for general use. However, please review any known issues that are listed on this page.
Android 13 QPR2 builds on the updates in Android 13 QPR1 and the Android 13 initial release and includes the next round of refinements such as bug fixes and improvements to stability and performance.
How to get QPR2 Beta 2.1​You can install Android 13 QPR2 Beta 2.1 on any of the following Google Pixel devices:
Pixel 4a and 4a (5G)
Pixel 5 and 5a
Pixel 6 and 6 Pro
Pixel 6a
Pixel 7 and 7 Pro
See Get Android 13 QPR beta builds for details on how to get started.
General advisories​Be aware of these general advisories about the release:
This release might have various stability, battery, or performance issues.
For users with accessibility needs, this release might not be appropriate for daily use.
Some apps might not function as expected when running on this release. This limitation includes Google's apps as well as other apps.
Android 13 QPR beta builds aren't Compatibility Test Suite (CTS)‑approved, but they have passed preliminary testing and provide a stable set of pre-release APIs for developers. Apps that depend on CTS-approved builds or use SafetyNet APIs might not work normally on Android 13 QPR beta builds.
Get support​Two primary support channels are available to you when developing and testing with Android 13 QPR2. The channel you should use to get support depends on where you are encountering your issue.
Support for device-specific issues, system issues, and issues with Google apps: Use the Issue Tracker to create new issues and to view and track issues that you and other developers have submitted.
Before creating your own issue, check the known issues listed on this page and search the lists of top open issues and recently created issues to see if someone else has already reported it. You can subscribe and vote for an issue by clicking star this issue .
See Where to report issues to find an issue template that best matches the type of issue that you are encountering.
Support for issues with other apps: Contact the app developer directly.
To discuss issues or ideas with other developers working with the Android 13 QPR Beta, join the android_beta community on Reddit.
Top resolved issues​The following issues have been resolved in Android 13 QPR2 Beta 2:
Fixed an issue with the System UI that sometimes caused the Home screen to become unresponsive.
Fixed an issue where, after switching back to Normal video capture mode from Slow Motion mode in the Google Camera app, the app continued capturing slow-motion video if the capture speed was changed between 1/8x and 1/4x while in Slow Motion mode.
Top open issues​See top open issues for the latest list of top open issues that have been reported.
Other known issues​Based on our testing, you might encounter the following issues when using Android 13 QPR2. These issues are already known, so there's no need to file additional reports for similar issues.
Android Platform​
The list of Recent apps sometimes becomes unresponsive if the screen orientation is changed while the list is open.
In some cases when entering and exiting Picture-in-picture (PiP) mode from an app after changing the screen orientation, the system Settings app crashes with a "Settings keeps stopping" message and then the system Settings app can't be opened.
An issue with the System UI can sometimes cause it to crash from a null pointer exception.
Previous beta releases​Android 13 QPR1 Beta 1​Other known issues​Based on our testing, you might encounter the following issues when using Android 13 QPR2. These issues are already known, so there's no need to file additional reports for similar issues.
Android Platform​
The list of Recent apps sometimes becomes unresponsive if the screen orientation is changed while the list is open.
In some cases when entering and exiting Picture-in-picture (PiP) mode from an app after changing the screen orientation, the system Settings app crashes with a "Settings keeps stopping" message and then the system Settings app can't be opened.
An issue with the System UI can sometimes cause the Home screen to become unresponsive.
Google Apps​
After switching back to Normal video capture mode from Slow Motion mode in the Google Camera app, the app continues capturing slow-motion video if the capture speed was changed between 1/8x and 1/4x while in Slow Motion mode.
Click to expand...
Click to collapse
January 9, 2023:
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developer.android.com
Pixel 7 Procheetah-t2b2.221216.006-factory-69f10917.zip69f109173eddc640cf73152e3dbb0a8926ebf9cb24db17c59d521861f2232033
Full OTA Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developer.android.com
Pixel 7 Procheetah-ota-t2b2.221216.006-17316d28.zip17316d28dad87f234dd648998587b4a5f325f17e6afeb477261f0c90a1854384
Android 13 GSI binaries and release notes | Android Developers
Notes and downloads for Generic System Images for Android 13 QPR beta builds.
developer.android.com
ARM64+GMSgsi_gms_arm64-exp-T2B2.221216.006-9443277-12a8e193.zip12a8e1935c6ef46d2d44dea6ea331fa238cb6240bd6df607f6ccb849d619b25cARM64aosp_arm64-exp-T2B2.221216.006-9443277-e508d63f.zipe508d63f27da01889734d36171dec11f226e2f2bc538526379e2184d51e9ffd3x86_64+GMSgsi_gms_x86_64-exp-T2B2.221216.006-9443277-5255002f.zip5255002f0d1249bb08725c06e3a264d8caaf2d84cdb9c40c7a7a8954249d6493x86_64aosp_x86_64-exp-T2B2.221216.006-9443277-02d675fb.zip02d675fb15c962fa7e35f494edfbfa2da7b886ef3f6e4709b73b1c57fb96b8ab
Android 13 | Android Developers
<!-- hide description -->
developer.android.com
Release notes​bookmark
Beta 2Beta 1
Release dateJanuary 9, 2023BuildT2B2.221216.006Security patch levelJanuary 2023Google Play services22.41.13
About Android 13 QPR2​Following the stable release of Android 13 to AOSP, we continue to update the platform with fixes and improvements that are then rolled out to supported devices. These releases happen on a quarterly cadence through Quarterly Platform Releases (QPRs), which are delivered both to AOSP and to Google Pixel devices as part of Feature Drops.
Although these updates don't include app-impacting API changes, we provide images of the latest QPR beta builds so you can test your app with these builds as needed.
Unlike developer previews and betas for unreleased versions of Android, these builds are suitable for general use. However, please review any known issues that are listed on this page.
Android 13 QPR2 builds on the updates in Android 13 QPR1 and the Android 13 initial release and includes the next round of refinements such as bug fixes and improvements to stability and performance.
How to get QPR2 Beta 2​You can install Android 13 QPR2 Beta 2 on any of the following Google Pixel devices:
Pixel 4a and 4a (5G)
Pixel 5 and 5a
Pixel 6 and 6 Pro
Pixel 6a
Pixel 7 and 7 Pro
See Get Android 13 QPR beta builds for details on how to get started.
General advisories​Be aware of these general advisories about the release:
This release might have various stability, battery, or performance issues.
For users with accessibility needs, this release might not be appropriate for daily use.
Some apps might not function as expected when running on this release. This limitation includes Google's apps as well as other apps.
Android 13 QPR beta builds aren't Compatibility Test Suite (CTS)‑approved, but they have passed preliminary testing and provide a stable set of pre-release APIs for developers. Apps that depend on CTS-approved builds or use SafetyNet APIs might not work normally on Android 13 QPR beta builds.
Get support​Two primary support channels are available to you when developing and testing with Android 13 QPR2. The channel you should use to get support depends on where you are encountering your issue.
Support for device-specific issues, system issues, and issues with Google apps: Use the Issue Tracker to create new issues and to view and track issues that you and other developers have submitted.
Before creating your own issue, check the known issues listed on this page and search the lists of top open issues and recently created issues to see if someone else has already reported it. You can subscribe and vote for an issue by clicking star this issue .
See Where to report issues to find an issue template that best matches the type of issue that you are encountering.
Support for issues with other apps: Contact the app developer directly.
To discuss issues or ideas with other developers working with the Android 13 QPR Beta, join the android_beta community on Reddit.
Top resolved issues​The following issues have been resolved in Android 13 QPR2 Beta 2:
Fixed an issue with the System UI that sometimes caused the Home screen to become unresponsive.
Fixed an issue where, after switching back to Normal video capture mode from Slow Motion mode in the Google Camera app, the app continued capturing slow-motion video if the capture speed was changed between 1/8x and 1/4x while in Slow Motion mode.
Top open issues​See top open issues for the latest list of top open issues that have been reported.
Other known issues​Based on our testing, you might encounter the following issues when using Android 13 QPR2. These issues are already known, so there's no need to file additional reports for similar issues.
Android Platform​
The list of Recent apps sometimes becomes unresponsive if the screen orientation is changed while the list is open.
In some cases when entering and exiting Picture-in-picture (PiP) mode from an app after changing the screen orientation, the system Settings app crashes with a "Settings keeps stopping" message and then the system Settings app can't be opened.
An issue with the System UI can sometimes cause it to crash from a null pointer exception.
Previous beta releases​Android 13 QPR1 Beta 1​Other known issues​Based on our testing, you might encounter the following issues when using Android 13 QPR2. These issues are already known, so there's no need to file additional reports for similar issues.
Android Platform​
The list of Recent apps sometimes becomes unresponsive if the screen orientation is changed while the list is open.
In some cases when entering and exiting Picture-in-picture (PiP) mode from an app after changing the screen orientation, the system Settings app crashes with a "Settings keeps stopping" message and then the system Settings app can't be opened.
An issue with the System UI can sometimes cause the Home screen to become unresponsive.
Google Apps​
After switching back to Normal video capture mode from Slow Motion mode in the Google Camera app, the app continues capturing slow-motion video if the capture speed was changed between 1/8x and 1/4x while in Slow Motion mode.
Click to expand...
Click to collapse
December 12, 2022:
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developer.android.com
Pixel 7 Procheetah-t2b1.221118.006-factory-a4882e16.zipa4882e16edb007358307a767a7df663dfb369d96262fceb364b34936d48a8cf5
Android 13 | Android Developers
<!-- hide description -->
developer.android.com
Release notes​bookmark
Beta 1
Release dateDecember 12, 2022BuildT2B1.221118.006Security patch levelDecember 2022Google Play services22.39.10
About Android 13 QPR2​Following the stable release of Android 13 to AOSP, we continue to update the platform with fixes and improvements that are then rolled out to supported devices. These releases happen on a quarterly cadence through Quarterly Platform Releases (QPRs), which are delivered both to AOSP and to Google Pixel devices as part of Feature Drops.
Although these updates don't include app-impacting API changes, we provide images of the latest QPR beta builds so you can test your app with these builds as needed.
Unlike developer previews and betas for unreleased versions of Android, these builds are suitable for general use. However, please review any known issues that are listed on this page.
Android 13 QPR2 builds on the updates in Android 13 QPR1 and the Android 13 initial release and includes the next round of refinements such as bug fixes and improvements to stability and performance.
How to get QPR2 Beta 1​You can install Android 13 QPR2 Beta 1 on any of the following Google Pixel devices:
Pixel 4a and 4a (5G)
Pixel 5 and 5a
Pixel 6 and 6 Pro
Pixel 6a
Pixel 7 and 7 Pro
See Get Android 13 QPR beta builds for details on how to get started.
General advisories​Be aware of these general advisories about the release:
This release might have various stability, battery, or performance issues.
For users with accessibility needs, this release might not be appropriate for daily use.
Some apps might not function as expected when running on this release. This limitation includes Google's apps as well as other apps.
Android 13 QPR beta builds aren't Compatibility Test Suite (CTS)‑approved, but they have passed preliminary testing and provide a stable set of pre-release APIs for developers. Apps that depend on CTS-approved builds or use SafetyNet APIs might not work normally on Android 13 QPR beta builds.
Get support​Two primary support channels are available to you when developing and testing with Android 13 QPR2. The channel you should use to get support depends on where you are encountering your issue.
Support for device-specific issues, system issues, and issues with Google apps: Use the Issue Tracker to create new issues and to view and track issues that you and other developers have submitted.
Before creating your own issue, check the known issues listed on this page and search the lists of top open issues and recently created issues to see if someone else has already reported it. You can subscribe and vote for an issue by clicking star this issue .
See Where to report issues to find an issue template that best matches the type of issue that you are encountering.
Support for issues with other apps: Contact the app developer directly.
To discuss issues or ideas with other developers working with the Android 13 QPR Beta, join the android_beta community on Reddit.
Top open issues​See top open issues for the latest list of top open issues that have been reported.
Other known issues​Based on our testing, you might encounter the following issues when using Android 13 QPR2. These issues are already known, so there's no need to file additional reports for similar issues.
Android Platform​
The list of Recent apps sometimes becomes unresponsive if the screen orientation is changed while the list is open.
In some cases when entering and exiting Picture-in-picture (PiP) mode from an app after changing the screen orientation, the system Settings app crashes with a "Settings keeps stopping" message and then the system Settings app can't be opened.
An issue with the System UI can sometimes cause the Home screen to become unresponsive.
Google Apps​
After switching back to Normal video capture mode from Slow Motion mode in the Google Camera app, the app continues capturing slow-motion video if the capture speed was changed between the 1/8x and 1/4x while in Slow Motion mode.
Click to expand...
Click to collapse
November 7, 2022:
Thanks @Lughnasadh. Literally caught me napping.
Lughnasadh said:
QPR1 Beta 3 is out for the Pixel 7 series ( the others). Is there a QPR thread started for this device @roirraW "edor" ehT ?
Click to expand...
Click to collapse
Factory images for Google Pixel | Android Developers
Instructions for downloading and installing QPR Beta system images for Pixel devices
developer.android.com
Pixel 7 Procheetah-t1b3.221003.008-factory-833888c0.zip833888c01857f2e7bbc970d0fc916625e53691c40dcba58ab607f20901630970
OTA images for Google Pixel | Android Developers
Instructions for downloading and installing QPR beta system images for Pixel devices
developer.android.com
Pixel 7 Procheetah-ota-t1b3.221003.008-9967bdf9.zip9967bdf9176d7b9f54ef2771621f621d576dff0eb7e32c9acfaa3e3b628b1729
Lughnasadh said:
QPR1 Beta 3.1 Release Notes...
Android 13 | Android Developers
<!-- hide description -->
developer.android.com
Click to expand...
Click to collapse
Release notes​Beta 3.1 Beta 3 Beta 2 Beta 1
Release dateNovember 7, 2022BuildT1B3.221003.008Security patch levelNovember 2022Google Play services22.36.16
Android 13 QPR1 Beta 3.1 (November 2022)
This minor update to Android 13 QPR1 Beta 3 includes the following fixes:
Fixed a platform issue that caused apps to crash when they were using a MediaSession to handle input from hardware media playback buttons. (Issue #251798994, Issue #252665746, Issue #251381423, Issue #251513135, Issue #255500998)
Fixed issues where a device's GPU drivers sometimes caused the system UI to freeze during normal device use.
Fixed an issue where Pixel phones sometimes displayed an incorrect "Missed call" notification instead of "Call answered on another device" when the call was answered remotely by Pixel Watch (in untethered mode).
Fixed an issue that sometimes caused the Google Camera app to crash.
Fixed an issue that prevented Google Assistant from being activated by hotword on some devices.
Fixed an issue that prevented motion-based gestures, such as "Lift to check phone" or "Flip to Shhh", from working on some devices.
Fixed an issue that sometimes caused artifacts to display when recording or viewing video on some devices.
Fixed an issue that sometimes caused the Google Camera app to launch slowly.
Fixed an issue for Pixel 6a devices that sometimes caused the CarrierSettings to crash when inserting a SIM card.
Fixed that issue that prevented the "Go to browser" option in the notification shade from working while using an instant app.
About Android 13 QPR1​Following the stable release of Android 13 to AOSP, we continue to update the platform with fixes and improvements that are then rolled out to supported devices. These releases happen on a quarterly cadence through Quarterly Platform Releases (QPRs), which are delivered both to AOSP and to Google Pixel devices as part of Feature Drops.
Although these updates don't include app-impacting API changes, we provide images of the latest QPR beta builds so you can test your app with these builds as needed.
Unlike developer previews and betas for unreleased versions of Android, these builds are suitable for general use. However, please review any known issues that are listed on this page.
Android 13 QPR1 builds on the updates in the Android 13 release and includes the next round of refinements such as bug fixes and improvements to stability and performance.
How to get QPR1 Beta 3.1​You can install Android 13 QPR1 Beta 3.1 on any of the following Google Pixel devices:
Pixel 4a and 4a (5G)
Pixel 5 and 5a
Pixel 6 and 6 Pro
Pixel 6a
Pixel 7 and 7 Pro
See Get Android 13 QPR beta builds for details on how to get started.
General advisories​Be aware of these general advisories about the release:
This release might have various stability, battery, or performance issues.
For users with accessibility needs, this release might not be appropriate for daily use.
Some apps might not function as expected when running on this release. This limitation includes Google's apps as well as other apps.
Android 13 QPR beta builds aren't Compatibility Test Suite (CTS)‑approved, but they have passed preliminary testing and provide a stable set of pre-release APIs for developers. Apps that depend on CTS-approved builds or use SafetyNet APIs might not work normally on Android 13 QPR beta builds.
Get support​Two primary support channels are available to you when developing and testing with Android 13 QPR1. The channel you should use to get support depends on where you are encountering your issue.
Support for device-specific issues, system issues, and issues with Google apps: Use the Issue Tracker to create new issues and to view and track issues that you and other developers have submitted.
Before creating your own issue, check the known issues listed on this page and search the lists of top open issues and recently created issues to see if someone else has already reported it. You can subscribe and vote for an issue by clicking star this issue.
See Where to report issues to find an issue template that best matches the type of issue that you are encountering.
Support for issues with other apps: Contact the app developer directly.
To discuss issues or ideas with other developers working with the Android 13 QPR Beta, join the android_beta community on Reddit.
Top resolved issues​The following issues have been resolved in Android 13 QPR1 Beta 3:
Developer-reported and user-reported issues​
Fixed an issue for some devices where the screen unlock UI was displayed over notifications and other lock-screen content. (Issue #254163754)
Other resolved issues​
Fixed an issue that prevented the "Flip camera for selfie" gesture from working on some devices.
Fixed an issue that sometimes caused the screen to go blank while attempting to unlock a device.
Fixed an issue that sometimes prevented a device from being unlocked using either Face Unlock or Fingerprint Unlock when the device had been idle for multiple hours.
Fixed an issue that sometimes caused fullscreen video playback to flicker after enabling always-on-display features and locking the screen.
Top open issues​See top open issues for the latest list of top open issues that have been reported.
Other known issues​Based on our testing, you might encounter the following issues when using Android 13 QPR1. These issues are already known, so there’s no need to file additional reports for similar issues.
Android Platform​
(Fixed in Beta 3.1) In some cases, issues with a device's GPU drivers cause the system UI to freeze during normal device use. To work around this issue, try restarting the device.
Pixel​
(Fixed in Beta 3.1) In some cases, Pixel phones display an incorrect "Missed call" notification instead of "Call answered on another device" when the call is answered remotely by Pixel Watch (in untethered mode).
Previous beta releases​Android 13 QPR1 Beta 1​Top resolved issues​The following issues have been resolved in Android 13 QPR1 Beta 1:
Developer-reported issues​
Fixed an issue for some devices that mistakenly caused a user's emergency contact to be dialed from the lock screen when the device was in their pocket. (Issue #233159557)
Other resolved issues​
Fixed various issues for Pixel 6a devices that made it difficult for users to unlock their device or to set up Fingerprint Unlock.
Fixed an issue that caused the system UI to crash in certain cases, such as gesturing from the edge of the screen to go back.
Fixed an issue that sometimes caused the 5G icon to be displayed instead of the 5G UW icon, even when the affected device was already successfully connected to a 5G UW network.
Click to expand...
Click to collapse
October 20, 2022:
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developer.android.com
Pixel 7 Procheetah-t1b3.221003.003-factory-0b002999.zip0b002999528e5fc30924af15a99fbecf52f8e515cec16b1652933706b9f4bc32
Full OTA Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developer.android.com
Pixel 7 Procheetah-ota-t1b3.221003.003-7695ecd6.zip7695ecd6679a9908e7f375b1ef94174389fa35d279ea1a0896b3f6f146ed85a7
Android 13 | Android Developers
<!-- hide description -->
developer.android.com
Release notes​bookmark
Beta 3Beta 2Beta 1
Release dateOctober 20, 2022BuildT1B3.221003.003Security patch levelOctober 2022Google Play services22.36.16
About Android 13 QPR1​Following the stable release of Android 13 to AOSP, we continue to update the platform with fixes and improvements that are then rolled out to supported devices. These releases happen on a quarterly cadence through Quarterly Platform Releases (QPRs), which are delivered both to AOSP and to Google Pixel devices as part of Feature Drops.
Although these updates don't include app-impacting API changes, we provide images of the latest QPR beta builds so you can test your app with these builds as needed.
Unlike developer previews and betas for unreleased versions of Android, these builds are suitable for general use. However, please review any known issues that are listed on this page.
Android 13 QPR1 builds on the updates in the Android 13 release and includes the next round of refinements such as bug fixes and improvements to stability and performance.
How to get QPR1 Beta 3​You can install Android 13 QPR1 Beta 3 on any of the following Google Pixel devices:
Pixel 4a and 4a (5G)
Pixel 5 and 5a
Pixel 6 and 6 Pro
Pixel 6a
Pixel 7 and 7 Pro
See Get Android 13 QPR beta builds for details on how to get started.
General advisories​Be aware of these general advisories about the release:
This release might have various stability, battery, or performance issues.
For users with accessibility needs, this release might not be appropriate for daily use.
Some apps might not function as expected when running on this release. This limitation includes Google's apps as well as other apps.
Android 13 QPR beta builds aren't Compatibility Test Suite (CTS)‑approved, but they have passed preliminary testing and provide a stable set of pre-release APIs for developers. Apps that depend on CTS-approved builds or use SafetyNet APIs might not work normally on Android 13 QPR beta builds.
Get support​Two primary support channels are available to you when developing and testing with Android 13 QPR1. The channel you should use to get support depends on where you are encountering your issue.
Support for device-specific issues, system issues, and issues with Google apps
Use the Issue Tracker to create new issues and to view and track issues that you and other developers have submitted. Before creating your own issue, check the known issues listed on this page and search the lists of top open issues and recently created issues to see if someone else has already reported it. You can subscribe and vote for an issue by clicking star this issue
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
.
See Where to report issues to find an issue template that best matches the type of issue that you are encountering.
Support for issues with other apps
Contact the app developer directly.
To discuss issues or ideas with other developers working with the Android 13 QPR Beta, join the android_beta community on Reddit.
Top resolved issues​The following issues have been resolved in Android 13 QPR1 Beta 3:
Developer-reported and user-reported issues​
Fixed an issue for some devices where the screen unlock UI was displayed over notifications and other lock-screen content. (Issue #254163754)
Other resolved issues​
Fixed an issue that prevented the "Flip camera for selfie" gesture from working on some devices.
Fixed an issue that sometimes caused the screen to go blank while attempting to unlock a device.
Fixed an issue that sometimes prevented a device from being unlocked using either Face Unlock or Fingerprint Unlock when the device had been idle for multiple hours.
Fixed an issue that sometimes caused fullscreen video playback to flicker after enabling always-on-display features and locking the screen.
Top open issues​See top open issues for the latest list of top open issues that have been reported.
Other known issues​Based on our testing, you might encounter the following issues when using Android 13 QPR1. These issues are already known, so there’s no need to file additional reports for similar issues.
Android Platform​
In some cases, issues with a device's GPU drivers cause the system UI to freeze during normal device use. To work around this issue, try restarting the device.
Pixel​
In some cases, Pixel phones display an incorrect "Missed call" notification instead of "Call answered on another device" when the call is answered remotely by Pixel Watch (in untethered mode).
Previous beta releases​Android 13 QPR1 Beta 1​Top resolved issues​The following issues have been resolved in Android 13 QPR1 Beta 1:
Developer-reported issues​
Fixed an issue for some devices that mistakenly caused a user's emergency contact to be dialed from the lock screen when the device was in their pocket. (Issue #233159557)
Other resolved issues​
Fixed various issues for Pixel 6a devices that made it difficult for users to unlock their device or to set up Fingerprint Unlock.
Fixed an issue that caused the system UI to crash in certain cases, such as gesturing from the edge of the screen to go back.
Fixed an issue that sometimes caused the 5G icon to be displayed instead of the 5G UW icon, even when the affected device was already successfully connected to a 5G UW network.
Click to expand...
Click to collapse
Android 13 QPR1 Beta 3 is here for the Google Pixel series
If you have a Google Pixel device, you can now install the latest QPR1 Beta based on Android 13.
www.xda-developers.com
Android 13 QPR1 Beta 3 is here for the Google Pixel series​By Adam Conway
Published 2 hours ago
+
If you have a Google Pixel device, you can now install the latest QPR1 Beta based on Android 13.
If you have a Google Pixel smartphone, you're undoubtedly aware of the advantage that you have in installing beta builds of the newest Android builds. Google has recently taken to releasing Quarterly Platform Release (QPR) betas, ahead of quarterly Google Pixel feature drops. Android 13 QPR1 Beta 1 was released in September this year and was quickly followed up by Beta 2 earlier this month. Now Android 13 QPR1 Beta 3 is here, and it has even more bug fixes and improvements.
This update is now live and available for supported Pixel devices like the Pixel 4a, Pixel 4a 5G, Pixel 5, Pixel 5a, Pixel 6, and even the Pixel 7 series of devices. This is the first beta that you can download for the Google Pixel 7 series. As mentioned before, QPR releases offer improvements or enhancements to Android that are not available to the public yet. The following changelog was shared by Google.
Fixed an issue for some devices where the screen unlock UI was displayed over notifications and other lock-screen content. (Issue #254163754)
Other resolved issues
Fixed an issue that prevented the "Flip camera for selfie" gesture from working on some devices.
Fixed an issue that sometimes caused the screen to go blank while attempting to unlock a device.
Fixed an issue that sometimes prevented a device from being unlocked using either Face Unlock or Fingerprint Unlock when the device had been idle for multiple hours.
Fixed an issue that sometimes caused fullscreen video playback to flicker after enabling always-on-display features and locking the screen.
If you want to download Android 13 QPR1 Beta 3 for your Google Pixel, be sure to check out the link below. To install the beta, you'll need to enroll in the company's beta program. Once you log in, will see all eligible devices for the program, which includes the Pixel devices mentioned above. If you choose to opt into the program with an eligible device, you will be asked to accept the terms and conditions. You will also have the option of receiving emails about the program and declaring yourself as a developer.
Once you're all set up, be sure to check out the official subreddit to share your thoughts or problems with regard to the latest updates. You should also take a look at on our guide on how to install Android 13 if you're unsure on the steps that you need to take..
Source: Android Developers Platform Releases
Click to expand...
Click to collapse

Reserved #3

Reserved #4

Reserved #5

Reserved #6

Reserved #7

yesssssss. it was great on my p6pro.. downloading now.

Thanks for sharing
Well done

Are these generally safe? I know that there is no EDL recovery type of thing for Tensor Pixels so is it common that they get permanently bricked by these updates or going back to the non-beta?

Up, rooted & running

EtherealRemnant said:
Are these generally safe? I know that there is no EDL recovery type of thing for Tensor Pixels so is it common that they get permanently bricked by these updates or going back to the non-beta?
Click to expand...
Click to collapse
ive been on beta for my last 3 phones.. no issues.. [3xl 6pro now 7pro]

EtherealRemnant said:
Are these generally safe? I know that there is no EDL recovery type of thing for Tensor Pixels so is it common that they get permanently bricked by these updates or going back to the non-beta?
Click to expand...
Click to collapse
They're safe. I ran them throughout Android 12. There is a window where you can go back to stable without having to wipe. That occurs when they release the stable build of each QPR, in this case the stable build of QPR1, which should be in December. Once that stable build is released you can unenroll in the beta program without having to wipe, as long as you do it before they release QPR2 Beta 1.
Android Beta Program
Android Beta Program allows you to enroll your Android device for beta releases.
www.google.com

bscabl said:
ive been on beta for my last 3 phones.. no issues.. [3xl 6pro now 7pro]
Click to expand...
Click to collapse
Lughnasadh said:
They're safe. I ran them throughout Android 12. There is a window where you can go back to stable without having to wipe. That occurs when they release the stable build of each QPR, in this case the stable build of QPR1, which should be in December. Once that stable build is released you can unenroll in the beta program without having to wipe, as long as you do it before they release QPR2 Beta 1.
Android Beta Program
Android Beta Program allows you to enroll your Android device for beta releases.
www.google.com
Click to expand...
Click to collapse
Thanks for the info. I will have to think about it. I normally like being bleeding edge but I also usually have a lot of bugs to complain about (so used to that with my OnePlus 9) and I don't have much to complain about here at all. Not sure I'm ready to tinker too much yet lol

Lughnasadh said:
Up, rooted & running
Click to expand...
Click to collapse
What process u did to keep root etc ? Do u use custom kernel?

Jiggs82 said:
What process u did to keep root etc ? Do u use custom kernel?
Click to expand...
Click to collapse
I flashed the factory image and re-rooted afterwards. Not using a custom kernel.

EtherealRemnant said:
Are these generally safe? I know that there is no EDL recovery type of thing for Tensor Pixels so is it common that they get permanently bricked by these updates or going back to the non-beta?
Click to expand...
Click to collapse
I don't specifically recall anyone in my Pixel 6 Pro QPR Beta thread having any non-user caused (or any at all, really) hard bricks. I think these are at least as safe as the Betas for major Android versions, but I just don't have time to set my phone up from scratch if there's a major Beta bug.
I should add the link for opting into the Beta officially, too.

Android 13 QPR1 Beta 3 is here for the Google Pixel series
If you have a Google Pixel device, you can now install the latest QPR1 Beta based on Android 13.
www.xda-developers.com

It's nice they released 2 betas this month. In their documentation it does say "up to 2 a month", but wasn't really expecting it. Hope they keep doing 2 a month.

Root installed fine.
Clear calling is now a toggle under the sound and vibration menu on the 7 pro. It is OFF by default.
Vo5G is enabled on T-Mobile for the 7 pro as well.

Is here a way to perform check/examination for build-in Android certificates and CA? (with no root)

Hello.
I have a question about Android preinstalled security certificates. There is possible to view them in system, turning off and on. But unfortunately there even no possible to copy-paste sha and it's fingerprint (maybe it just in particular ui of phone, don't know).
So if iam interested to bulk check all of them for issues/more info/research is there a way by some app or maybe pull them somehow from phone with ADB interface and then import and perform mentioned above tasks in some Windows software/ Linux/web frontend? And then turning off what is not good.
Because for example many of them has expired dates, some of them issued by CA or countries that iam personally have no default trust, etc.
p.s. Iam mentioning a FACTORY STATE OFFICIAL SOFTWARE and firmware phone, Android 12, December 2022 security patch.
Thanks!