[ROM][Note 10/10+][A12] iodéOS = LineageOS 19.1 + MicroG + adblocker [04/04/2023] - Samsung Galaxy Note 10+ ROMs, Kernels, Recoveries,

{
"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"
}
Introduction
iodéOS is a privacy-focused operating system powered by LineageOS and based on the Android mobile platform. iodéOS aims at protecting the user's privacy with a built-in adblocker and by freeing the smartphone from snitches.
The objectives in the conception of this ROM are threefold:
To keep the stability and security level of LineageOS, by minimizing the modifications made to the system. Apart the system modifications required by the adblocker, we mainly only added a few useful options commonly found in other custom ROMs, made some cosmetic changes, modified a few default settings to prevent data leaks to Google servers.
To ease a quick adoption of this ROM by new users. We especially target users that are concerned by the protection of their privacy, but are not reluctant to still use inquisitive apps like Google ones. We thus included MicroG as well as a coherent set of default apps, and simplified the initial setup of the system. Particularly, an initialization of MicroG has been made with GCM notifications allowed by default, a privacy-friendly network location provider (DéjàVu) pre-selected, as well as Nominatim Geocoder.
To provide a new and powerful way of blocking ads, malwares, data leaks of all kinds to many intrusive servers. We are developing an analyzer, tightly integrated into the system, that captures all DNS requests and network traffic, as well as a user interface (the iodé app). Compared to some other well-known adblockers, this has the advantages of:
Avoiding to lock the VPN for that use. You can even use another adblocker that uses VPN technology alongside our blocker.
Being independent of the kind of DNS server used by the system or set by an independent app: classical DNS on UDP port 53 or any other one, DNS over TLS (DoT), DNS over HTTPS (DoH), ..., as we capture the DNS requests before they are transmitted to the system function that emits the DNS request. What we do not support, is DoH when it is natively built into applications, i.e. when an app communicates directly with a DoH server, without asking name resolution to the system. It would require to decrypt HTTPS packets between such an app and the DoH server, which may create a big security hole.
Precisely mapping DNS requests and network packets to the Android apps that emitted (or received) them.
Deciding which apps have a filtered network usage (by default, all apps), and which ones can communicate with blacklisted servers.
Since its first versions, we added many features to the iodé blocker: several levels of protection, fine-grained control over the hosts that should be blocked or authorized, displaying statistics on a map to see the quantity of data exchanged to which countries, clearing statistics... We are actively developing the blocker, and new functionalities will be regularly added.
Features
Changes in LineageOS to prevent data leaks:
Default DNS server: Google's DNS replaced by Quad9's 'unblocked' servers in all parts of the system.
A-GPS: patches to avoid leaking personnal information like IMSI to supl server.
Captive portal login: connectivitycheck.gstatic.com replaced by captiveportal.kuketz.de for connectivity check.
Dialer: Google default option replaced by OpenStreetMap for phone number lookup.
Pre-installed apps:
We included many useful default apps, but our choice cannot suit everyone; so we added the possibility to remove them. It can be done at the end of the phone setup, or at any time by going to Parameters -> Apps & Notifications -> Preinstalled apps.
MicroG core apps: GmsCore, GsfProxy, FakeStore.
NLP backends for MicroG : DejaVuNLPBackend (default), MozillaNLPBackend, AppleNLPBackend, RadioCellsNLPBackend, Nominatim Geocoder.
App stores : FDroid (with F-Droid Privileged Extension) and Aurora Store.
Browser: our own fork of Firefox (with Qwant as default search engine, many other ones added, telemetry disabled, parts of telemetry code removed) instead of Lineage’s default browser Jelly.
SMS: QKSMS instead of Lineage's default SMS app.
Email: p≡p (Pretty Easy Privacy).
Camera: our own fork of Open Camera, with a few tweaks.
Maps/navigation: Magic Earth GPS & Navigation (the only one free but not open source).
Keyboard: OpenBoard instead of AOSP keyboard.
PDF: Pdf Viewer Plus.
Personnal notes: Carnet.
{Ad/Malware/Data leak}-blocker: iodé.
News: to keep users informed about our developments, as well as a FAQ.
Meteo: Geometric Weather.
Pre-included FDroid repository:
The apps that we tweak or develop (microG services, the browser based on Firefox, the News app, Open Camera ...) are available through a repository that we included in FDroid (check the "Apps for iodéOS" category). For this purpose and to avoid name conflicts of some apps, we also had to make a few changes in FDroid.
Useful options from other custom ROMs:
Smart charging (disables charging when a given level is reached, to protect battery health).
Fingerprint vibration toggle.
Swipe down to clear all in recent apps (Android 10 only).
Installation Instructions
To download and flash our latest build, see https://gitlab.com/iode/ota.
You can also find here direct links to the latest builds.
Supported devices
Fairphone FP3/FP3+
Fairphone FP4
Google Pixel 3
Google Pixel 4
Google Pixel 5
Google Pixel 6
Google Pixel 6a
OnePlus 9
OnePlus 9 Pro
Samsung Galaxy A5/A7 2017 (a5j17lte/a7j17lte)
Samsung Galaxy S9/S9+ (starlte/star2lte)
Samsung Galaxy Note 9 (crownlte)
Samsung S10e/S10/S10+ (beyond{0,1,2}lte)
Samsung Note 10 (d1)
Samsung Note 10+ (d2s)
Sony Xperia XA2 (pioneer)
Sony Xperia XZ1 (poplar)
Sony Xperia XZ2 (akari)
Sony Xperia XZ3 (akatsuki)
Xiaomi Mi9 (cepheus)
Teracube 2e
Xiaomi Mi 10T 5G / Mi 10T Pro 5G
Xiaomi Mi 10 Lite 5G
Sources
iodéOS: https://gitlab.com/iode/os
LineageOS: https://github.com/lineageos
device tree:
https://gitlab.com/iode/os/public/devices/samsung/device_samsung_d1
https://gitlab.com/iode/os/public/devices/samsung/device_samsung_d2s
https://gitlab.com/iode/os/public/devices/samsung/device_samsung_exynos9820-common
kernel: https://github.com/LineageOS/android_kernel_samsung_exynos9820
Bug Reporting
You can post a message in this thread or (preferred) open an issue here.
Credits
LineageOS is a free, community built, aftermarket firmware distribution of android, which is designed to increase performance and reliability over stock android for your device.
All the source code for LineageOS is available in the LineageOS Github repo. If you would like to contribute to LineageOS, please visit their Wiki for more details.
This ROM would be nothing without the tremendous work made on MicroG, and all the other open source apps that we included. We are very grateful to their authors.
Contributors
Direct contributors: @iodeOS, @vince31fr
Indirect contributors (too numerous to list): All the people that contributed to the device tree, to LineageOS, and to the included open source apps.
Sponsoring
You can help in the development of this ROM by paying us a coffee here: https://paypal.me/iodeOS.
Screenshots

Downloads : iodéOS
04/04/2023 (build 20230401) for Note 10 (d1) and Note 10+ (d2s):
Blocker: improved use of blocking lists (sub-domains blocking)
FDroid: fixes an issue on apps update
LineageOS synchronized with March security patch included
All apps updated
07/02/2023 (build 20230131) for Note 10 (d1) and Note 10+ (d2s):
Blocker:
Improved blocking settings. You can now choose 'Standard' blocking (ads, trackers, malwares, etc) or 'Reinforced' blocking (same objective but more extensive), and then select additional categories.
The 'Porn' category has been extended to a wider 'Sensitive content' one, that also includes fake news, gambling, drugs, piracy, torrent..., with mainly child protection in mind.
The 'Extreme' category has been removed, as it is now part of the reinforced blocking.
Improved blocking lists. We merge several acknowledged and up-to-date sources, and have diversified our sources to produce more complete lists. The standard list has however been reduced a bit, to avoid as much as possible interference with apps expected behavior.
Added a new network location provider: Local NLP Backend. It is an improved version of the DéjàVu NLP backend which was already available in iodéOS. Like DéjàVu, it builds a local database connecting localizations learned from other NLP backends and apps using GPS, and mobile antennas/Wifi; but also has an active mode (not preselected) that can trigger GPS requests. To configure it: Settings -> System -> microG -> Location modules
LineageOS synchronized with January security patch included
All apps updated
New devices support: Pixel 3, 6, 6a
20/12/2022 (build 20221218) for Note 10 (d1) and Note 10+ (d2s):
Fixes smart charging issue
16/12/2022 (build 20221215) for Note 10 (d1) and Note 10+ (d2s):
Blocker: added multiple selection in settings / domain customization. Long-press on a domain, select several domains or all, apply actions (block all, authorize all...)
PdfViewerPlus: improved security by updating core libraries
Network settings: added a switch to disable connectivity check (and thus captive portal detection)
LineageOS synchronized with December security patch included
All apps updated
New devices support: Pixel 4 & 5, OnePlus 9 & 9 Pro
24/11/2022 (build 20221121) for Note 10 (d1) and Note 10+ (d2s):
Improvements in the blocker user interface (iodé app)
LineageOS synced with September security patch included
All apps updated
17/10/2022 (build 20221014) for Note 10 (d1) and Note 10+ (d2s):
Blocker:
Network blockings following their type (Wifi, mobile data, VPN) added
Default blockings definition for new apps
Personnalized recipients management improved
iodé's app access restrictions by password added
Search filters added in report and map
Display theme selection
Automatic and 'real-time' refresh of the whole app
Performance and fluidity improvements of the app
LineageOS synced with September security patch included
All apps updated
27/07/2022 (build 20220726) for Note 10 (d1) and Note 10+ (d2s):
SafetyNet certification activated: allows many apps, notably banking ones, to fully work
Setup wizard: the push notifications configuration page now also activates SafetyNet (fine-grained control in Settings->System->microG)
OpenCamera: the 'Use alternative flash method' in photo settings is no more necessary and can be disabled, allowing flash optimization
News app: German translations
LineageOS synced with July security patch included
All apps updated
21/07/2022 (build 20220530) for Note 10 (d1) and Note 10+ (d2s):
Upgrade to Android 12 / Lineage 19.1
Setup Wizard: new page to configure push notifications through microG
Lockscreen settings: switch added to disable fingerprint unlock when screen is off
Improved German translations
Bug fixes and improvements
LineageOS synced with May security patch included
All apps updated
03/02/2022 (build 20220407/08) for Note 10 (d1) and Note 10+ (d2s):
News app reworked
Setup Wizard: new iodé introduction
iodé blocker: pull to refresh replaced by automatic refresh in report tab
Teracube 2e 2022 batch released, video playback in browser and video recording fixed
Music app : playlist crash fixed
Open Camera : crash when tapping thumbnail of a newly recorded video fixed, photos and videos now editable
LineageOS synced with March security patch
All apps updated
03/02/2022 (build 20220126) for Note 10 (d1) and Note 10+ (d2s):
New iodé blocker map feature
Build mode changed to 'user' (i.e. release) mode): more apps work out-of-the-box and more secure device, but more restrictive recovery
Camera app changed to Open Camera
Wireguard kernel module included
Dark bootanimation
January security patch
Preinstalled apps updated
Beware: Play store Magisk module broken
18/11/2021 (build 20211108) for Note 10 (d1) and Note 10+ (d2s):
LineageOS updated (November security patch)
Preinstalled apps updated
Iodé blocker: hosts can now be customized, either globally or by app
05/09/2021 (build 20210905) for Note 10 (d1) and Note 10+ (d2s):
LineageOS updated (August security patch)
Preinstalled apps updated
Backup app included: Seedvault
microG now uninstallable: Settings -> Apps & notifications -> Preinstalled apps
New default accent color (clear blue from iodé logo)
13/08/2021 (build 20210811) for Note 10 (d1) and Note 10+ (d2s): first publicly available builds.
Downloads : add-ons
phonesky-magiskV2.zip : Magisk module for NanoDroid patched Play Store, for those who really need to get access to their paid apps that don't work with microG. This module can be generally be deactivated when you have installed and ran once the paid apps.
NB : you may have to wait a couple of hours after activating the module for being able to install paid apps.

Why is there no N9750 (d2q)? Which god can develop a d2q ROM? d2q heart pain.

And the d2x? Note 10+5g model?

Do you root this like lineage? By flashing a patched boot image?

Morutimeru said:
Do you root this like lineage? By flashing a patched boot image?
Click to expand...
Click to collapse
Yes, you can use magisk for instance.

biggary said:
And the d2x? Note 10+5g model?
Click to expand...
Click to collapse
We will maybe build for d2x. Stay tuned!

vince31fr said:
Yes, you can use magisk for instance.
Click to expand...
Click to collapse
Just flashed the ROM and rooted, had a hard time with twrp bootlooping after flashing. Its working phenomenal with Lineage Recovery. Thanks Dev, this ROM is awesome.

Great idea and work. Thanks for making this rom. I'll test asap.

Sorry if this has already been asked but from what I can see with all roms if you flash them you lose 5g and the ability to use WiFi calling and calling over 4g/volte? This is because of Samsung baking it into their framework?

+++ New Update : 10/09/2021 +++
Available as OTA (see OP)​

During the "patching system image unconditionally..." I keep getting "E:Error in /sideload/package.zip (status 1) in recovery output when I use Lineage recovery 18.1 (most recent) or the IODE recovery to perform the adb sideload command. Most recently after a clean install of the latest samsung firmware for the note 10+.
I checked zip file(s) integrity using 7 zip. It reports no errors. I also used both the iode 2.1 from 0811 and 0905 earlier with the iode 0905 recovery.
Any suggestions?

*** New Update : 18/11/2021 ***
Available as OTA (see OP)​

vince31fr said:
*** New Update : 18/11/2021 ***
Available as OTA (see OP)​
Click to expand...
Click to collapse
Still no D2X version???

am on the way to get a 10+ and will try this OS. Looks good!
After reading the installing instructions tho I am a bit unsure whether it is done in windows or linux. I've only worked in windows and with twrp so far...
Can anyone bring some clarity?
Besides, i am wondering few things:
- do both sims work?
- does the phone recognize full 512GB microSD? Or god forbide, 1TB?

If we already have lineageOS running, can we just boot into lineage recovery and sideload IODE'. Or does anyone mind providing some instructions on how to do this?
Thanks for any help. I'm learning all this and it takes me awhile to figure it all out.

Hello,
New here and fairly new to the whole rooting/booting/ROM thing. Although I have loaded cyanogen on a phone years ago. Some tech/coding experience.
I would like to use Iode on a Note 10. NOT Note 10+, just Note 10
Earlier in the thread I see d1, d2q and d2x
Which specifically do each of these apply to? I am thinking that
d1 = Note 10 but with Exynos chipset
d2q = Note 10+
d2x = Note 10+ 5G
Do I have these right?
What is the codename of the snapdragon Note 10 (N970U) ?
I would like to use Iode on the snapdragon Note 10. Is this possible?
Do I have to have the Exynos chipset - and if so, will that chipset give me pain when using with US GSM cell network?
Thank you!!! Much appreciated!

*** New Update : 03/02/2022 ***
Available as OTA (see OP)​
Beware: Play Store Magisk module broken

Good job keep it on very good rom battery is awesom

i don't understand what recovery shall I have to install? Adb it's ok, Oem unlocked, but I think I have download the original recovery...

Related

[APP][6.0+][UPDATED] FrontFlash Notification v2.5 (20190424)

{
"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"
}
What is this?
Basically by installing this application, as soon as you receive a notification there is a flash as your phone starts blinking for the LED notification.
It can be useful to anyone that has a device without the LED notification, but instead have a flash next to the selfie camera.
It also extends the concept of notification to the unread badges received from the applications (ex. the "Facebook like"). So, when an unread badge pops up, in the same way as a "normal" notification the flash starts blinking and you will be notified of what's going on.
Various settings are also available to better configure the application to suit your needs.
It works on all devices equipped with a front flash, regardless of whether or not they have the hardware LED notification. (read also the Hardware limitations section for more details)​
Main features
customizable activation based on the current display status and audio mode
pocket mode and recovery options
Samsung AOD support
single or double blink
optional custom delay for the first blink
use also the rear flash when the device is upside down
additional flashing loop with customizable frequency
three different gestures to dismiss the flashing loop
customizable exclusions for the incoming call, the missing call and the text messages
customizable exclusions for all the installed user applications
flash notifications for the unread badges received from compatible applications and customizable by app exclusions (only on Samsung devices with TouchWiz based ROM)
suspend on low battery
suspend during a customizable time slot
integration with the Android "Do not disturb" settings
custom quick setting tile in the quick settings panel to easily turn on/off the service (only on Android 7.x+ devices)
custom shortcut pressing the application icon to easily turn on/off the service (only on supported launchers and on Android 7.1.1+ devices)
built-in black list to avoid the flash for useless, fake or annoying notifications from some applications
optimized for memory usage
battery-friendly (usually takes up 2% in each 24 hour period)
dark theme
RTL support for Arabic languages
no ADS
no ROOT ACCESS needed to work
and more...
Languages
English
Italian
Arabic (Egyptian) @yshalsager
Arabic (Syrian) @mozzafar alali
Croatian @dugi9991
Czech @novas78
French @Primokorn
German @supergrobi94 / @Oswald Boelcke
Greek kynigosg
Polish @emcom
Portuguese (Brazilian) @Taivotat2 / @justjr
Russian @gaich
Simplified Chinese @ContactFront
Slovak @kubalav
Spanish @JHAM2005
Turkish @Fatih Fırıncı
Ukrainian @Alexiy_ua
Vietnamese @tphg
Privacy
This application is not ad-supported and can not collect and transmit any sort of privacy sensitive information.
This application can not collect, store or publish any user information.
This application can not use any data connection, detect your location or access your contacts. It also can not read any sensitive information stored on your device. This guarantees maximum security for your data and your privacy.​
Permissions
This application does not need any special permissions except for the one to bind the Android notification listener service. [android.permission.BIND_NOTIFICATION_LISTENER_SERVICE]
This is the only authorization required to properly interact with your incoming notifications (you will be asked about it explicitly when it is run for the first time).
Devices with Camera Hardware level: LIMITED (partial Camera2 API support)
On some devices the manufacturer implemented only partially the Android Camera2 API; this means limited hardware access to the camera for the developers. In this case the only way to let this application properly take control of the front flash is to use the old Android API and that's why you may also have to authorize the application to use the hardware camera. [android.permission.CAMERA]
With the first run and only if the application detects this limitation, as per the above case you will be asked explicitly to grant full camera access permission (even if the application should only use the front flash, the flash is strictly part of the hardware camera).
You must agree with providing access to your device camera, file system and audio recording for the application to function. This access is limited to user only. None of the data present in your device can be shared with me or any other person.
Keep in mind that if you deny any of these permissions the application will not work!
If you know how Android works and the meaning of application permissions, you can easily verify by yourself all the above statements.
So please, avoid claiming that we are a bunch of criminals here just to steal your data with this application... in doing that, you would be such an IDIOT!​
Hardware limitations
Lately several devices (mainly, but not only, running Android 8.x) are equipped with front flash with custom hardware that developers can not have access to. Furthermore, with the introduction of the new firmware based on Android 8.x, Samsung has inexplicably inhibited the use of front flash to developers on a wide range of devices.
Strangely enough, the front camera of your device may not be equipped with a "real" front flash for this application. When it "asks" through the Android API to your front camera some information about its front flash, the answer may be "no front flash available". There is no workaround this!
This is a software/hardware limitation imposed by the manufacturer (don't ask me why) and at the moment unfortunately there's nothing I can do. I understand your amazement, but if you experience this kind of issue at 99% of the time that's the reason why this application may not work and could report the non-availability of a front flash despite your eyes seeing a front flash.
Mainly only the branded (stock) camera application can handle this kind of front flash, using owned and reserved API.
Try it by yourself to install (from the app Store) an alternative camera application. Then shoot a front selfie and check if the front flash can turn on... or use any other application you expect to use the front flash (usually Instagram and Snapchat fail as well) and then let me know the results.
In addition, you can also try to install Device Info HW and then select the "Camera" tab and check all detailed information about the front camera of your device.
Finally, let me remind you that this app can't take control over the brightness, the color and the speed (On-Off phase) of a flash; unfortunately it isn't a LED... no way for the developers to handle these features.
All of them are strictly related to the hardware and its manufacturer and therefore vary from model to model.​
Main functioning
As you can imagine, this application must be able to take control of the front flash of your device to work properly. In an Android phone this can only happen in one way: through the front camera as the flash is strictly connected to it.
The developers in fact through dedicated instructions, can turn it on and off at will. But it always has a connection to the camera and not directly to the flash itself.
To handle all the incoming notifications, an Android service will run in background on your device.
These are the main functioning at the root of this application.​
Troubleshooting
If you installed any startup manager application (such as Startup Manager, Autorun Manager, AutoStart Manager, Advanced Task Manager, BootManager, etc) or any battery manager/optimizer application (such as Greenify, Doze, Brevent, Hibernator, App Freezer, etc) pay attention to avoid killing the running "Flash notification service" otherwise this application will not work!
I also want to draw your attention to the importance of the Android wakelocks in the lifecycle of this application (if you don't know what wakelocks are, disregard the sentance below).
If your device is running an application that detects and blocks wakelocks (such as Wakelock Detector, WakeBlock, No Wakelock, Wake Lock - PowerManager, etc), keep in mind that the main features of this application will not work as you expect. So add it to the white list if any, or if you are interested in using this application in any way avoid blocking the wakelocks.
In other words, because of unreasonable battery optimizations implemented by some brands but not only, you have to be careful not to put this application in hibernation without realizing it or maybe killing or blocking the background service without noticing it. These are the most common causes of the main problems you may experience!
Please verify the impact over this application by any system tools / Magisk - Xposed modules which you heavily rely on (especially if your device is ROOTED).
So, double check your system settings before reporting any issues, thanks.​
Battery consumption
It isn't strictly related to the application itself. What drains the battery is the flash not the background service in charge of managing your incoming notifications, I can't do more in terms of optimization.
Battery consumption mainly depends on how long you will let the flashing loop run before you dismiss it (the shorter it is the better for your battery) and also on how many notifications you receive a day.​
Issues & Known bugs
with the introduction of the new firmware based on Android 8.x, Samsung has inexplicably inhibited the use of front flash to developers on a wide range of devices, so this application stop working!!
System requirements
Android 6.x Marshmallow or later
a device with front camera and front flash (read also the Hardware limitations section for more details)
five minutes of your free-time and a little piece of your brain (just in case)
you do not need ROOT ACCESS for this application to work
Installation instructions
Just download the apk and open it as a normal application.​
Download
This application is available on the Google Play Store.
In order to keep in touch with the latest updates, I suggest you uninstall any previous version you downloaded here from XDA and then install the official version of the Play Store.
Get FrontFlash Notification​
Credits / Thanks to
thanks to @supergrobi94 for the graphic support
thanks to @Alexiy_ua, @ContactFront, @dugi9991, @emcom, @Fatih Fırıncı, @gaich, @JHAM2005, @justjr, @kubalav, kynigosg, @mozzafar alali, @novas78, @Oswald Boelcke, @Primokorn, @supergrobi94, @Taivotat2, @tphg, @yshalsager for the translations
Donation
Your donations are welcomed and appreciated, press the thanks button instead of saying it.
PayPal​
FrontFlash Notification
Version Information
Status: Stable
Current Stable Version: 2.5
Stable Release Date: 2019-04-24
Created: 2018-01-13
Last Updated: 2019-04-24
Screenshots
Changelog
2.5 (current release)
migration to native Android Pie 9 (API 28)
updated internal black-list for the auto-excluded applications
minor bug fixes
2.4.9 (stable)
minor bug fixes
2.4.7 (stable)
under the hood fixes and optimizations
2.4.5 (stable)
minor bug fixes
2.4.2 (stable)
fixed the custom shortcut icon issue on Android 7.1.x devices
minor bug fixes
2.4.1 (stable)
migration to native Android Oreo 8.1 (API 27)
added the option to delay the first blink
added a custom shortcut pressing the application icon to easily turn on/off the service only on supported launchers and on Android 7.1.1+ devices
added the Simplified Chinese translation
added the Greek translation
added the Ukrainian translation
updated all translations
updated internal black-list for the auto-excluded applications
lots of under the hood fixes and optimizations
2.3.3 (stable)
Android 8.x users may experience general malfunctions
added the sub-option to keep screen on if the "Turn display on" option when a notification occurs is selected
added the Slovak translation
added the Turkish translation
added the Vietnamese translation
updated the Czech and Russian translations
stability improvement
minor bug fixes
2.3 (stable)
This update will reset all user preferences to default at first run!
fixed the pocket mode issue
fixed the time slot suspension issue
added a custom quick setting tile on the quick settings panel to easily turn on/off the service only on Android 7.x+ devices
major code rewrite for the graphical user interface (flash notifications settings)
updated internal black-list for the auto-excluded applications
minor bug fixes and various adjustments
2.2.7 (stable)
fixed the pocket mode issue on some devices
fixed the time slot suspension issue on Android 8.x devices
fixed the incoming call flash notification issue
fixed the consecutive notifications issue
renewed badge notification service for Samsung devices (some tests may be needed)
minor bug fixes and various adjustments
2.2.5 (stable)
fixed the issue of annoying blinks while the device is in use (user present/screen on) in some particular conditions or by specific applications
fixed the issue of the suddenly stop working blink loop
battery life improved
new max limit for the blink loop duration
new increase values for the blink loop frequency
minor bug fixes and various adjustments
2.2.1 (stable)
fixed the service force close issue on Android 6.0 devices
minor adjustments
2.2 (stable)
minor bug fixes
2.1.6 (stable)
minor bug fixes
translation update for some languages
2.1.4 (stable)
minor bug fixes
2.1 (stable)
main code reengineering
stability and compatibility improvement
removed the flashing loop duration setting, from now is always unlimited
better performance
2.0 (stable)
code optimization
stability improvement
1.9.5 (stable)
code optimization
minor bug fixes
unlimited duration for the flashing loop
1.9.4 (stable)
added the Portuguese (Brazilian) translation
added the Arabic (Egyptian) translation
added the French translation
added the Czech translation
added the Croatian translation
added the Russian translation
added the Arabic (Syrian) translation
new range values for the duration and the frequency of the flashing loop
1.9.2 (stable)
added the option to force the English language
fixed the Samsung Email application issue
stability improvement
added the light sensor management (if present) for the flash type auto-adjustment (single/double)
added the option to use the rear flash when device is turn upside down
added RTL support for Arabic languages
1.9 (stable)
fixed the service force close issue and runtime exception on some Motorola devices
minor bug fixes
added the Spanish translation
1.8.3 (stable)
official Play Store release
minor bug fixes in the notifications detection engine
added compatibility to Android 8.0 Oreo (API 26)
added the Polish translation
1.7 (stable)
extended support to both Camera and Camera2 API to properly detect and manage the front flash also on devices with limited access to the camera (e.g. new Samsung device series)
fixed the issue with Gmail notifications on Android 6.0 devices
fixed the missing installed applications issue in the excluded applications list
fixed the wrong low battery detection issue on some devices
added a "select/unselect all" toggle switch in the excluded applications list
integration with the current Android "Do not disturb" settings as an additional way to disable the service in certain situations
minor fixes and code optimizations
updated internal black list for the auto-excluded applications
some GUI improvements and adjustments
new dark theme
new application icon
some corrections to writing errors
added the German translation
1.6 (stable)
added the option to choose a custom time slot for the service suspension (tap on time slot)
minor fixes
1.5 (stable)
added Samsung AOD detection and support
added the option to choose which applications exclude from the unread badges notification (tap on See list)
added the option to choose a custom sound for the unread badges notification (tap on Set sound)
improved both memory and cpu consumption
1.4 (release)
added the accelerometer sensor management and the relative “by shake” option
fixed the issue with duplicate items between the unread badges notification and the "normal" notification from the same application
new GUI
added the Italian translation
1.3 (beta 2)
added compatibility to Android 7.1.1 Nougat (API 25)
added the option to choose which applications exclude from flash notification (black list)
added the unread badges detection and the relative flash notification for all supported applications (only on Samsung devices with TW rom)
lots of under the hood fixes and optimizations
1.2 (beta 1)
added the proximity sensor option and its management
added the notifications badge count over the application icon in the app drawer and its relative option (only on supported device: Asus, Huawei, LG, HTC, Oppo, Samsung, Sony, Xiaomi, ZTE)
fine tuning in the notifications detection engine to avoid fake flash notifications from system and user applications
performance improvements
1.1 (alpha)
added the option to enable a blinking loop for all the incoming notifications
added the low battery status detection and the relative service suspension option
added an option to suspend the service during a specific time slot
bug fixes
1.0
initial release
Support
Feedback
Please write in this thread any suggestions or bugs you come to know to help me make this application better and better.
What's coming next
none
Translations
All translations are created by community volunteers and open for contribution. If you want this application in your language and you are interested in cooperate, please send me a PM.
Hardware limitations
Lately several devices (mainly, but not only, running Android 8.x) are equipped with front flash with custom hardware that developers can not have access to. Furthermore, with the introduction of the new firmware based on Android 8.x, Samsung has inexplicably inhibited the use of front flash to developers on a wide range of devices.
Strangely enough, the front camera of your device may not be equipped with a "real" front flash for this application. When it "asks" through the Android API to your front camera some information about its front flash, the answer may be "no front flash available". There is no workaround this!
This is a software/hardware limitation imposed by the manufacturer (don't ask me why) and at the moment unfortunately there's nothing I can do. I understand your amazement, but if you experience this kind of issue at 99% of the time that's the reason why this application may not work and could report the non-availability of a front flash despite your eyes seeing a front flash.
Mainly only the branded (stock) camera application can handle this kind of front flash, using owned and reserved API.
Try it by yourself to install (from the app Store) an alternative camera application. Then shoot a front selfie and check if the front flash can turn on... or use any other application you expect to use the front flash (usually Instagram and Snapchat fail as well) and then let me know the results.
In addition, you can also try to install Device Info HW and then select the "Camera" tab and check all detailed information about the front camera of your device.
Finally, let me remind you that this app can't take control over the brightness, the color and the speed (On-Off phase) of a flash; unfortunately it isn't a LED... no way for the developers to handle these features.
All of them are strictly related to the hardware and its manufacturer and therefore vary from model to model.
Main functioning
As you can imagine, this application must be able to take control of the front flash of your device to work properly. In an Android phone this can only happen in one way: through the front camera as the flash is strictly connected to it.
The developers in fact through dedicated instructions, can turn it on and off at will. But it always has a connection to the camera and not directly to the flash itself.
To handle all the incoming notifications, an Android service will run in background on your device.
These are the main functioning at the root of this application.
Common issues & Troubleshooting
If you installed any startup manager application (such as Startup Manager, Autorun Manager, AutoStart Manager, Advanced Task Manager, BootManager, etc) or any battery manager/optimizer application (such as Greenify, Doze, Brevent, Hibernator, App Freezer, etc) pay attention to avoid killing the running "Flash notification service" otherwise this application will not work!
I also want to draw your attention to the importance of the Android wakelocks in the lifecycle of this application (if you don't know what wakelocks are, disregard the sentance below).
If your device is running an application that detects and blocks wakelocks (such as Wakelock Detector, WakeBlock, No Wakelock, Wake Lock - PowerManager, etc), keep in mind that the main features of this application will not work as you expect. So add it to the white list if any, or if you are interested in using this application in any way avoid blocking the wakelocks.
In other words, because of unreasonable battery optimizations implemented by some brands but not only, you have to be careful not to put this application in hibernation without realizing it or maybe killing or blocking the background service without noticing it. These are the most common causes of the main problems you may experience!
Please verify the impact over this application by any system tools / Magisk - Xposed modules which you heavily rely on (especially if your device is ROOTED).
So, double check your system settings before reporting any issues, thanks.
Battery consumption
It isn't strictly related to the application itself. What drains the battery is the flash not the background service in charge of managing your incoming notifications, I can't do more in terms of optimization.
Battery consumption mainly depends on how long you will let the flashing loop run before you dismiss it (the shorter it is the better for your battery) and also on how many notifications you receive a day.
Hope I have been helpful in understanding.
Thank you nice work
I will add Arabic language
Can't enable the front flash.. Its not enabling.. Greyed out.. I have j7 pro.. Ty..
The app doesn't know I have Front Flash (J7 2016)
Sent from my j7xelte using XDA Labs
ickoslash said:
Can't enable the front flash.. Its not enabling.. Greyed out.. I have j7 pro.. Ty..
Click to expand...
Click to collapse
Oh... this sounds strange! Be more specific please.
Which android version?
Which label is displayed at the left of the greyed switch?
Did the app ask for "Notification access permission" at first run?
Open Options --> Lock screen and security --> Other security settings and check manually the notification access permission (if it's disabled, activate it now) and let me know.
Thanks
Arnaud Créative Studios said:
The app doesn't know I have Front Flash (J7 2016)
Sent from my j7xelte using XDA Labs
Click to expand...
Click to collapse
You mean did you received the "Front flash not present, service disabled" message?
Thanks
spacejam said:
You mean did you received the "Front flash not present, service disabled" message?
Thanks
Click to expand...
Click to collapse
Yes
Sent from my j7xelte using XDA Labs
spacejam said:
Oh... this sounds strange! Be more specific please.
Which android version?
Which label is displayed at the left of the greyed switch?
Did the app ask for "Notification access permission" at first run?
Open Options --> Lock screen and security --> Other security settings and check manually the notification access permission (if it's disabled, activate it now) and let me know.
Thanks
Click to expand...
Click to collapse
Got error message front flash not present.. Already enabled it in notifications under lock screen and security.. My phone's j7 pro.. So technically it's nougat..
Arnaud Créative Studios said:
Yes
Click to expand...
Click to collapse
SM-J710F model right?
Chipset Exynos or Snapdragon?
Stock ROM, Custom TWLauncher rom, AOSP rom... or what?
(I'm sorry for so many questions, but the more I know and the more it becomes easy to solve the problem, I hope)
ickoslash said:
Got error message front flash not present...
Click to expand...
Click to collapse
SM-J730G model right?
Seems like something go wrong during the front flash detection phase.
This app uses the standard Android Camera2 API to get access to the flash.
So, is something strictly related to your device model and Samsung hardware/firmware.
Maybe is the Exynos chipset variant... not so easy to investigate but I will try.
Thanks
spacejam said:
SM-J710F model right?
Chipset Exynos or Snapdragon?
Stock ROM, Custom TWLauncher rom, AOSP rom... or what?
(I'm sorry for so many questions, but the more I know and the more it becomes easy to solve the problem, I hope)
SM-J730G model right?
Seems like something go wrong during the front flash detection phase.
This app uses the standard Android Camera2 API to get access to the flash.
So, is something strictly related to your device model and Samsung hardware/firmware.
Maybe is the Exynos chipset variant... not so easy to investigate but I will try.
Thanks
Click to expand...
Click to collapse
Yep.. Exynos chipset.. It would be awesome if you could fix it dude.. Tnx a lot for making this app.. Will wait for the update.. :fingers-crossed:
spacejam said:
SM-J710F model right?
Chipset Exynos or Snapdragon?
Stock ROM, Custom TWLauncher rom, AOSP rom... or what?
(I'm sorry for so many questions, but the more I know and the more it becomes easy to solve the problem, I hope)
SM-J730G model right?
Seems like something go wrong during the front flash detection phase.
This app uses the standard Android Camera2 API to get access to the flash.
So, is something strictly related to your device model and Samsung hardware/firmware.
Maybe is the Exynos chipset variant... not so easy to investigate but I will try.
Thanks
Click to expand...
Click to collapse
SM-J710FN,Exynos,Stock TW Nougat Rom with Stock Launcher
Sent from my j7xelte using XDA Labs
FrontFlash Notification
Issues & known bugs:
on some Exynos chipset based devices, take control over the front flash fails. Check yours by yourself and let me know. (I'm working to understand how to fix it)
Thank you for this app, I will try it.
Works great on my Moto Z2 Play. Even dual flash works too. Awesome work !
This will be very useful on my Honor 7 since the notification LED is so small it's almost invisible.
Haven't been able to get it to work yet though.
First issue I got was that the service was running but not enabled. I figured out it was due to the "suspend on low battery" setting even though my battery was at 80%.
I unticked that and now the service is running and enabled.
I'm trying to get a notification when receiving an e-mail(gmail) but nothing is happening. Gmail is not in the possible exclusion list at all, maybe that has something to do with it?
Edit: It works for other apps like the calendar app.
Thanks for the work so far.
FrontFlash Notification
Just an update for Exynos chipset based device users... the front flash detection issue is not related to the chipset.
For some strange reasons (don't ask me why), on the new devices series (Exynos of course), Samsung has implemented only partially the Camera2 API for the developers. Hardware level: LIMITED (partial Camera2 support)
This is why at the time been my app can't use the front flash on your device.
In the next few days I'm going to produce a new 1.7 version, where if Camera2 fails the app takes control over the camera and his front flash using the old Android API.
Based on the first tests, fortunatelly this seems to fix the problem.
Keep in touch

Android Webview and webvr / webxr

Spend several days trying to make Android Webview go webvr / webxr
​
I have several projects to develop in VR and I used Unuty and Unreal for this. But with webvr/webxr coming it is a chance to get unified platform to distribute VR experience. Only problem I need to distribute it as stand-along app for google play and gearvr store (due to heavy video 360 4k/6k content - beyond Wi-Fi b/g/n capabilities).
​
Test device has android 7.1 - so webview is the chrome itself and in dev options set as chrome. Also tried to set it as chrome dev, chrome canary - no luck
​
my discovery for now
for webvr - this technology named deprecated and you need to set chrome://flags on normal chrome and it works well. Webview ignores that settings (might be if chrome://flags accessed from Webview it helps - have`t tried yet). There is an option to use chrome start-up parameters via adb but no good for production
​
for webxr you need to acquire Origin Trial Token from Goolge. And again stand alone chrome if accessing site with Origin Trial Token goes VR at no probs. But Webview simply ignores Token .
​
For now I have only one proper option - compile chromium and embed it in app. On windows I can distribute app using WinJS (.net and win32 also good) + Microsoft EDGE Webview. Works surprisingly well with Windows Mixed Reality. For SteamVR again I can compile Gecko or use supermedium (Gecko compiled by other guys).
​
But on android I still in search for way to show Webview with local html with my webxr content (based on threejs mostly).
Hilo

[APP|FOSS] GSF, Widevine L1/2/3, Treble & A/B device infos (+all IDs/Specs)

Re-branded KalturaDeviceInfo to provides GSF id (needed for Google uncertified devices) and checks about Widevine, Treble, a/b & media decoders (and all others possible device system definitions).
Code:
uses-permission android:name=
android.permission.WRITE_EXTERNAL_STORAGE android:maxSdkVersion="22"
android.permission.READ_EXTERNAL_STORAGE
android.permission.CAMERA
com.google.android.providers.gsf.permission.READ_GSERVICES
This app is a basic json example, it shows how much any app, can silently retrieve devices characteristics, but also simply provides :
testing any device sample, without Dev./Options unlocked, before purchasing (live or via email request to the seller)
add-on for static passive reporting in AOSP roms (conversely to active stats)
Treble advanced reviewing specifics
all-in-one floss without internet leak
(*.json can be easily browsed/parsed with FirefoxPC)​
code https://bitbucket.org/oF2pks/kaltura-device-info-android/src
prim-origin https://github.com/kaltura/kaltura-device-info-android
Edit : NOW ON F-Droid https://f-droid.org/en/packages/com.oF2pks.kalturadeviceinfos/​If you want some added, let me know, but due to privacy, I won't add any requiring <INTERNET> or <READ_PHONE_STATE> (or <READ_LOGS>)
Click to expand...
Click to collapse
° New Version: detection getprop for Treble & A/B seamless update + designation Soc & Kernel version
° JSON report doesn't include any {action}->privateIDs ; feel free to Post everywhere
° ... SharedLibs, Features, SecurityProviders, /proc/meminfo, GLESversion +...
° Services & init_svc & {action}-> getprop
° New Treble checks (ro.vndk.version) & ScreenMetrics
° improve gps.conf & treble + matrix
°/vendor detection, mounts, camera & cameraAPi2... (and Matrix_bug)
° CameraAPi2 global specs
° Display HDR modes
° etc/gps.conf miss in "private" dialog-box
° microG spec(s) detection
° multi screens support
° all sensors with mA consumption
° Binder Current Protocol Version
° api29 updates
° /vendor Sepolicy
° xml easy webView
° FingerprintedPartitions
° webView engine(s) detection via active button
° ultra lightweight ~350kb
° packagesInfos & permissionsInfos
° ro.build.system_root_image,
° android10 mediaCodec soft/hard + vendor indication.
NEW RELEASE RC21: android 11 (R/30) + Export: clipboard/share/save, camera colorFilter + fix logicalCam, Treble ld.config [Vendor], packagesInfos: foreground service + overlays
nota: works on JellyBean and up ; with Oreo, Android_id is discontinued, and Serial_id deprecated due to <read_phone_state> permission.
{
"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"
}
Can you explain what the purpose of this is? What we would use this for?
MishaalRahman said:
Can you explain what the purpose of this is? What we would use this for?
Click to expand...
Click to collapse
Hi, thanks for your interest, I'm huge xda{news} fan (everyday congrats), and was referring to
-GSFid https://www.xda-developers.com/how-to-fix-device-not-certified-by-google-error/ , this app throws a json on screen with finger touch copy/select/share; so users can copy it, also if Firefox is installed ( Fennec or Klar), on Lollipop and up, the share button to Firefox will straight open Google re-certification page (1st link in json).
-Widevine real level : https://www.xda-developers.com/xiaomi-poco-f1-widevine-l1-netflix-hd/ (and others Oneplus5...) thanks to Kaltura prim-origin, the app tests all possible drm inclusions.
-cpu soc64 without arm64 support: (thx to @mattwhite7102) some low cost oem provide devices with arm64 cpu without arch64 support https://forum.xda-developers.com/showpost.php?p=77789093&postcount=859
EDIT v2
-Treble detection https://www.xda-developers.com/project-treble-android-oreo/
-A/B seamless update https://www.xda-developers.com/how-to-check-android-device-supports-seamless-updates/
I will do my best to get this app auto-built by F-Droid, thus before buying a low cost device (example Treble project), buyers can ask sellers to process it, and send them this json by email. ( ? same for each new xda forum's device heading ?).
Finally, every (closed source) app with <internet> permission can leak this data to the net: it just visualizes this.
In that same purpose I'm also on releasing an upgrade of ApplicationsInfo with multiple additions, and without <internet> or other "excessive" permission : https://bitbucket.org/oF2pks/android-applications-info/downloads/ . (but untested on new Pie Update Inactive Apps screen to show buckets )
Awesome I will add this to my apk stash!
Sent from my Samsung SM-A520W using XDA Labs
Matrix ckick causes freeze
@oF2pks thanks for this! I'm no beginner when it comes to Android modding and such (check my sig) but the amount of info your app provides is overwhelming. More stuff for me to learn
PROBLEM: When I click on "Matrix" the app freezes, then I get the error "Kaltura Device Info is not responding".
MatLog output attchd
BTW, I learned about this because of link at
https://forum.xda-developers.com/pr...arm64aosp-9-0-0r21-microg-ufofficial-t3878115
Thanks so much.
DeviceInfo+++ This is a hidden gem, thank you very much.
@oF2pks
Hi,
thanks for the app but why on bitbucket the last release date is 2019-10-25 but on F-Droid the last release date is 2018-12-31?
@ale5000 , F-Droid packaging is usually out of scope of original developer(s). You should ask at https://gitlab.com/fdroid/fdroiddata/issues/
---------- Post added at 11:18 AM ---------- Previous post was at 10:54 AM ----------
Very nice app. Useful to gather inventory info from Android devices (similar to my Android port of system-report).
I just wonder why important data didn't make it into the resulting JSON? (namely `df`, `meminfo` etc.)
If the reason is privacy then a separate file could be created with `private` word in the filename...
ildar_prophet said:
@ale5000 , F-Droid packaging is ...
I just wonder why important data didn't make it into the resulting JSON? (namely `df`, `meminfo` etc.)
If the reason is privacy then a separate file could be created with `private` word in the filename...
Click to expand...
Click to collapse
I use 3 different packaging:
oF2pks said:
... xda for "pre-stage" debug flavor and bitbucket for debug testing "on-the-fly". F-Droid signed release is up, and should be uploaded at next [checkupdates]: https://f-droid.org/wiki/index.php?...m=&hidebots=0&hideanons=1&hideliu=1&limit=500 (~2/3 days).
Click to expand...
Click to collapse
Android10 finalized RC8 should be on F-Droid next checkupdates|build|deploy, unfortunately I couldn't find any Pixel4 user for testing latest Q modern changes like getPhysicalCameraIds or getKeysNeedingPermission. (but thanks to @seh6183 for multi-screen testing on LG G8X ThinQ).
The primary goal of this DeviceInfo app is to help purchasing devices by asking seller to send json to buyer (or run it directly in shops for powered-on devices when connected to wifi... or via bluetooth), and to provide straight full anonymous reports for rom developers (especially for project Treble); without any misses concerning deep defined characteristics (exception to Bluetooth version identification which even doesn't really exist in android (?)).
I use the alt button for private (or wip functionalities) or interactive dynamics data that could change in the lifetime of the device. Sometimes these also failed on alternative roms custom implementation.
(EDIT x10 thanks to @hackintosh5 for Binder arm protocol detection implementation https://github.com/penn5/TrebleCheck/tree/master/app/src/main/cpp)
Using my code, your code must be GPLv3. I can't find the source code, please can you link it.
oF2pks said:
...code https://bitbucket.org/oF2pks/kaltura-device-info-android/src
prim-origin https://github.com/kaltura/kaltura-device-info-android..
Click to expand...
Click to collapse
hackintosh5 said:
Using my code, your code must be GPLv3. I can't find the source code, please can you link it.
Click to expand...
Click to collapse
All F-Droid apps have public code linked in their own description
https://f-droid.org/en/packages/com.oF2pks.kalturadeviceinfos/
KalturaDeviceInfo use Unlicense, but all your code(s) have your original GPLv3 headings : https://bitbucket.org/oF2pks/kaltura-device-info-android/src/master/app/src/main/cpp/
oF2pks said:
All F-Droid apps have public code linked in their own description
https://f-droid.org/en/packages/com.oF2pks.kalturadeviceinfos/
KalturaDeviceInfo use Unlicense, but all your code(s) have your original GPLv3 headings : https://bitbucket.org/oF2pks/kaltura-device-info-android/src/master/app/src/main/cpp/
Click to expand...
Click to collapse
Oh well I was in a rush
Sorry but doesn't gpl part spoil the whole project to gpl? Need to check the GPL text
Отправлено с моего Aquaris X5 Plus через Tapatalk
edited
New rc9 with webView detection via active button
cqibhfkx said:
Force crash on Android 10.
Click to expand...
Click to collapse
Was lucky to test a Pixel4 and indeed 1.3.1-7 & 1.3.1-8 crash , but 1.3.1-6 ok; unfortunately I was not able to get an adb log. @cqibhfkx , can you push a logcat of the crash sequence (if any ?) on latest uploaded RC9 debug post#1 ?
ildar_prophet said:
Sorry but doesn't gpl part spoil the whole project to gpl? Need to check the GPL text
Click to expand...
Click to collapse
The headings in sources are normally sufficient ("fair goal") to identify distinct licenses & author from the global one. Check example : https://github.com/linkedin/qark/blob/master/LICENSE ; I will add missing LICENSE.md in sub projects :
- gplv3 for BinderProtocol ( @hackintosh5 )
- Apache2.0 for xml decryption (webView providers extraction) ( https://github.com/MajeurAndroid/An...ter/app/src/main/java/com/majeur/xmlapkparser)
Original app came without any license : https://github.com/kaltura/kaltura-device-info-android , that is why I choose "fair" Unlicense
ildar_prophet said:
I just wonder why important data didn't make it into the resulting JSON? (namely `df`, `meminfo` etc.)
If the reason is privacy then a separate file could be created with `private` word in the filename...
Click to expand...
Click to collapse
All these can be copied to clipboard via longPress + selection and paste anywhere.
Will also change app/Launcher name KalturaDeviceInfo to kDI (related to ˈkadē: caddy, help purchasing devices by asking seller to send json to buyer, or run it directly in shops for powered-on devices when connected to wifi... or via bluetooth... )
oF2pks said:
The headings in sources are normally sufficient ("fair goal") to identify distinct licenses & author from the global one. Check example : https://github.com/linkedin/qark/blob/master/LICENSE ; I will add missing LICENSE.md in sub projects :
- gplv3 for BinderProtocol ( @hackintosh5 )
- Apache2.0 for xml decryption (webView providers extraction) ( https://github.com/MajeurAndroid/An...er/app/src/main/java/com/majeur/xmlapkparser)
Original app came without any license : https://github.com/kaltura/kaltura-device-info-android , that is why I choose "fair" Unlicense
All these can be copied to clipboard via longPress + selection and paste anywhere.
Click to expand...
Click to collapse
It's not enough. You're violating GPL by statically linking it. Read the licenses
hackintosh5 said:
It's not enough.
Click to expand...
Click to collapse
So, what else should I do; I already added:
-gpl license to re-distributed [cpp] from your repo: https://bitbucket.org/oF2pks/kaltur...d1a3b7cd0d8f6d4a7fac/app/src/main/cpp/LICENSE
- boarded reference to your work (check attached screenshot/end) : https://bitbucket.org/oF2pks/kaltur.../app/src/main/res/values/strings.xml#lines-31
with, of course, your original headers in the code:
- https://bitbucket.org/oF2pks/kaltur...fac/app/src/main/cpp/BinderDetector.h#lines-7
- https://bitbucket.org/oF2pks/kaltur...c/app/src/main/cpp/BinderDetector.cpp#lines-7
There are 17 chapters in gpl license (Version 3, 29 June 2007), which one should I read carefully ? (https://www.gnu.org/licenses/license-list.html#Unlicense)
oF2pks said:
So, what else should I do; I already added:
-gpl license to re-distributed [cpp] from your repo: https://bitbucket.org/oF2pks/kaltur...d1a3b7cd0d8f6d4a7fac/app/src/main/cpp/LICENSE
- boarded reference to your work (check attached screenshot/end) : https://bitbucket.org/oF2pks/kaltur.../app/src/main/res/values/strings.xml#lines-31
with, of course, your original headers in the code:
- https://bitbucket.org/oF2pks/kaltur...fac/app/src/main/cpp/BinderDetector.h#lines-7
- https://bitbucket.org/oF2pks/kaltur...c/app/src/main/cpp/BinderDetector.cpp#lines-7
There are 17 chapters in gpl license (Version 3, 29 June 2007), which one should I read carefully ? (https://www.gnu.org/licenses/license-list.html#Unlicense)
Click to expand...
Click to collapse
https://softwareengineering.stackexchange.com/a/158792/291691
hackintosh5 said:
https://softwareengineering.stackexchange.com/a/158792/291691
Click to expand...
Click to collapse
Thanks for the link.
Did you read carefully the 2nd answer pounded 7 (just after 1st answer pounded 33, as today...): the third section of 2nd answer clearly disambiguates when licenses are GNU-compatible by liking to the same GNU reference ( that I did put in my previous post) ; check header there: GPLv3 is compatible with many licenses including [Unlicense] (and [Apache2.0]).
Code:
[URL="https://www.gnu.org/licenses/license-list.html#Unlicense"]Both public domain works and the lax license provided by the [U]Unlicense[/U] are [B][I]compatible[/I][/B] with the [U]GNU GPL[/U].[/URL]
As you link in your code to GPLv3, GNU/Licenses starts expressly with :
Code:
[URL="https://www.gnu.org/licenses/licenses.html"]To make it free software, you need to release it under a free software license.
We normally use the GNU General Public License (GNU GPL), specifying version 3 or any later version,
[B] but occasionally we use other free software licenses.[U] We use only licenses that are compatible with the GNU GPL for GNU software[/U][/B].[/URL]
Please, let me know if you have a different approach of GNU GPL license (Version 3, 29 June 2007) compatibility.
New Release (v2.0-20) lightweight ~350kb
oF2pks said:
The primary goal of this DeviceInfo app is to help purchasing devices by asking seller to send json to buyer (or run it directly in shops for powered-on devices when connected to wifi... or via bluetooth), and to provide straight full anonymous reports for rom developers (especially for project Treble); without any misses concerning deep defined characteristics (exception to Bluetooth version identification which even doesn't really exist in android (?)).
Click to expand...
Click to collapse
In that purpose, kDI is now ultra lightweight (~350kb) to help fast download (or Bluetooth transfer) in shops.
Also embedded are permissionsInfos (Chairlock) and applicationsInfos. Both of them will individually switch to heavyweight AppCompat/androidX/androidTV upgrade (+2.5Mb), but I will maintain lightweight library flavored editions in kDI: https://bitbucket.org/oF2pks/kaltura-device-info-android/commits/

[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

How To Guide June 20, 2023 TQ3A.230605.012.A1 Verizon/MVNOs / June 13, 2023 TQ3A.230605.012 Global - Unlock bootloader / Root Pixel 7 Pro [Cheetah] / SafetyNet

Pixel 7 Pro [Cheetah]​
Updated May 13, 2023
Note that more than three users have said that 34.0.1 (even May 10, 2023's binary update of 34.0.1) did not work correctly for them. I recommend sticking with 33.0.3 (just below these quotes)
Someone reported it to Google (added a comment about 34.0.1 to the existing 34.0.0 report).
Spoiler
b0uNz said:
tried to flash the latest build of AncientOS with it, did not work. Back to r33.0.3 and it worked fine
Click to expand...
Click to collapse
Aphex13 said:
platform-tools_r34.0.1-windows is not functioning properly. Back to 33.0.3 we go...
Click to expand...
Click to collapse
budmannxx said:
Add me to the list of users that had a problem with platform-tools 34.0.1. I got into a bootloop after running flash-all.bat. Downgraded to 33.0.3, reran the new (old) flash-all.bat, and was all good.
Using 34.0.1, the phone never even got to the fastbootd part of the process
Click to expand...
Click to collapse
May 10, 2023 binary update of 34.0.1:
Homeboy76 said:
Update
I tested SDK Platform-tools r. 34.0.1 it is not fixed. There are still problems with fastbootd. Use SDK Platform-tools r. 33.0.3
Click to expand...
Click to collapse
The download links for 33.0.3:
Namelesswonder said:
Anyone that updated their platform tools and needs to downgrade can use these links.
Windows
https://dl.google.com/android/repository/platform-tools_r33.0.3-windows.zip
Mac
https://dl.google.com/android/repository/platform-tools_r33.0.3-darwin.zip
Linux
https://dl.google.com/android/repository/platform-tools_r33.0.3-linux.zip
Click to expand...
Click to collapse
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
Google Pixel Update
Android Security Bulletins | Android Open Source Project
source.android.com
Here there be dragons. I am not responsible for anything at all.
VERY IMPORTANT - On the Pixel 7/Pro, we use Magisk to patch init_boot.img, NOT boot.img AND we flash the patched init_boot to the init_boot partition - do not flash it to the boot partition.​Thanks to @edcsxz, @Lughnasadh, and @AndyYan for news about that and confirming it.
Moved @mariusnoor's provided zero-day OTA.zip to Post #8 - Old news from the OP.
Spoiler: Warnings / FYI
Unlocking or locking the bootloader will wipe the device every single time, so be sure to have your data backed up before doing so, or better yet, just unlock it as soon as you get the device.​
Click to expand...
Click to collapse
Keep in mind that unlocking the bootloader or rooting might affect your phone's capability to use banking apps such as Google Pay, your local bank's app, or even the ability to install some apps like NetFlix. See Post #2 - Unlocking Bootloader / Rooting / Updating | SafetyNet | ADB/Fastboot & Windows USB Drivers.​
Click to expand...
Click to collapse
If you're going to re-lock the bootloader, make sure the ROM you have on your phone is completely stock (by flashing the latest official firmware) BEFORE re-locking it.​
Click to expand...
Click to collapse
There are no permanent negative consequences if you unlock or re-lock the bootloader other than it will wipe your phone, and while your bootloader is unlocked you get a brief screen when you boot the phone telling you (and anyone who sees your phone at the time) that it's unlocked. You will also continue to receive updates (if you've merely unlocked the bootloader, you can take updates as normal) unlike Samsung, Sony, et cetera, which have permanent major consequences with reduced functionality even if you un-root and re-lock your bootloader. If you're actually rooted (not just bootloader unlocked), you'll have to perform extra steps to manually update each month, and to keep root/re-root.​
Click to expand...
Click to collapse
INDEX:​
Post #2 - Unlocking Bootloader / Rooting / Updating | SafetyNet | ADB/Fastboot & Windows USB Drivers:
How to Root the first time / aka How to unlock the Bootloader
Unlocking Bootloader (required in order to root)
How to update each month (and also how to root)[requires an unlocked bootloader for updating via this factory image method]
OPTIONAL: If you want to flash both slots, after this first time, then after do the following
SafetyNet
Optional steps when updating - flashing custom kernels
The two schools of thought on disabling Verity and Verification
ADB/Fastboot and Windows USB Drivers - direct download links and the most recent changelog
Post #3 - Other, most important resources:
A list of other important apps
TWRP [not made for the Pixel 7 (or 6) Pro yet - will update when or if ever it has - don't hold your breath]
Factory Images (requires an unlocked bootloader)
Full OTA Images(doesn't require an unlocked bootloader - you can ask questions in this thread, but I won't be providing the steps necessary, as I always use the factory image)
@mariusnoor's provided official URL to download the zero-day OTA to TD1A.220804.031.
Check warranty status
Official Google Pixel Update and Software Repair (reported as of January 23, 2022 to still not be updated for the Pixel 6/Pro - no idea if it has yet now, or if it will be for the 7/Pro)
Official Google Pixel Install fingerprint calibration software (also available at the bottom of the Update and Software Repair page above) - I believe this is only helpful if you've replaced the screen - if it's anything like the Pixel 6 Pro: if you have the screen replaced, then you *must* have the fingerprint reader replaced as well.
Find problem apps, Magisk, and LSposed Modules by (three different methods)
Official Google Android Flash Tool (OEM Unlocking needs to be toggled on - you do not have to manually unlock the bootloader - their site will do that on its own)
How to determine if you already have Verity and Verification disabled (required for custom kernels for now)
How to unroot
Post #4 - Build ID definitions
Post #5 - Blank
Post #6 - Regarding P7P 5G model numbers and capabilities, and how to determine your hardware version
Post #7 - My personal advice for how to get your device back up and running as you had it before a factory reset
Post #8 - Old news from the OP
Thank you to the following users who have all contributed greatly to my knowledge of Pixels since I came back to XDA a year ago after a few years of mostly inactivity. Apologies if I miss anybody. In alphabetical order:
@AndyYan
@anirudhgupta109
@Az Biker
@bosox284
@capntrips
@Chainfire
@DespairFactor
@direwolf1
@Displax
@edcsxz
@Eleo
@flar2
@foobar66
@Freak07
@j4velin
@Jawomo
@Jon8RFC
@jorrik98
@kdrag0n
@[email protected]
@LLStarks
@Lughnasadh
@mariusnoor
@Namelesswonder
@PurppleMonkey
@Quinny899
@rovo89
@siavash79
@Sib64
@simplepinoi177
@StrangerWeather
@tbalden
@topjohnwu
@TotallyAnxious
@Tulsadiver
@Typhus_
@V0latyle
@VR25
@xgerryx
@xike456
@xstefen
And many others from all of the previous years who I thanked in my previous OPs.
Click to expand...
Click to collapse
Unlocking Bootloader / Rooting / Updating | SafetyNet | ADB/Fastboot & Windows USB Drivers​
Unlocking Bootloader / Rooting / Updating:​How to Root the first time / aka How to unlock the Bootloader:
Unlocking the bootloader will factory reset your device. There is no way around this. I highly suggest never re-locking your bootloader once you unlock it. If you do ever re-lock the bootloader, only do so after restoring the phone to 100% stock by using the latest Pixel 7 Pro Factory Image or Official Google Android Flash Tool.
Verizon variants:
Will never be able to have their bootloader unlocked. It's like winning the lottery, and just as rare and relatively random. There is nothing that anyone on XDA can do to help you unlock your Verizon variant.
Click to expand...
Click to collapse
T-Mobile and AT&T variants:
Can be unlocked once you pay the phone off, then you contact the carrier and arrange to Carrier unlock the phone. Once the phone is Carrier unlocked, then you can unlock the bootloader with the usual caveats (will wipe the device and there's no way around it).
Click to expand...
Click to collapse
The direct-from-Google (or other retailers who aren't U.S. Carriers), the factory Carrier Unlocked Pixels:
Can be bootloader unlocked at any time. I'd try it first before putting a SIM card in the phone. If OEM unlocking is grayed out, try connecting to Wi-Fi, and reboot if necessary. If it's still grayed out, try with your SIM card, and reboot again. Historically on Pixels, most of the time you can toggle OEM unlocking immediately, but occasionally some users have found it took a little while after being either connected to Wi-Fi or having your SIM card installed in it, and then eventually (hours? day? days?) you can toggle OEM unlocking.
Click to expand...
Click to collapse
The rest of the world's carriers:
No idea. Feel free to ask in the thread and hopefully, someone with specific knowledge will answer.
Click to expand...
Click to collapse
Other than trying the things I mentioned above, there is nothing else that anyone on XDA can do to help get OEM unlocking to be ungrayed.
Unlocking Bootloader (required in order to root)
The one-time first steps are:
Android Settings
About phone
Click on Build number repeatedly, about seven times
Go back to the main Android Settings
System
Developer options
Toggle OEM unlocking on. See @Namelesswonder's tip below (this won't help with variants that are supposed to be bootloader locked):
Namelesswonder said:
Also a little tip for anyone trying to enable OEM unlocking on a device and it is grayed out, you can force the phone to check for eligibility by connecting to the internet in whatever way, going to the dialer, and dialing *#*#2432546#*#* (CHECKIN).
You should receive a notification from Google Play services with "checkin succeeded" and OEM unlocking should be available immediately if the device is eligible.
Google account not needed, SIM not needed, no other setup required. Works on completely-skipped-setup-wizard. Just need to make sure to connect to the internet and select the connection as metered to avoid any updates.
Click to expand...
Click to collapse
Toggle USB debugging on.
[Optional] I highly suggest you also disable Automatic system updates. Note that in a situation such as the Android 12 serious bootloader security issue, this setting will not keep Google from forcing an update to come through anyway.
How to actually root follows the same steps below as how to update each month.
Download the latest ADB/Fastboot (SDK Platform Tools) and Windows USB Drivers.
Unzip the Platform Tools and Drivers.
NOTE: If you have USB drivers for other Android devices installed, like Samsung, they can alternately sometimes work and not work with Google Pixels. I recommend uninstalling those drivers, or at least updating that driver to Google's driver as instructed below (the Device Manager entry may be different with other OEMs).​
The Windows USB Drivers may have to be installed twice:
The first time while your phone is running and unlocked as normal.
In Windows, right-click on the Start Button and choose Device Manager.
Plug your phone into the computer and look for the new hardware entry in Device Manager. Near the top of Device Manager should be Android Device. Click the drop-down arrow to the left of it.
Below Android Device, it should now show Android Composite ADB Interface
Right-click the Android Composite ADB Interface and choose Update driver
Choose Browse my computer for drivers
Click Browse and navigate to where you unzipped the Windows USB drivers to.
Follow the prompts to install the driver.
Keep Device Manager itself open - you'll need it again in a minute, but you can close any other Device Manager windows after you have installed the driver.
Open a Command Prompt and navigate to the platform-tools folder.
Run command:
Code:
adb devices
On your Android device, you'll get an ADB prompt. Check the box to always give ADB permission and click OK.
Confirm that the command results in a list of Android devices. When doing these producedures, you should only have the one device you want to work on connected, to keep things simple.
The second time to install the driver is while the phone is in Bootloader (fastboot mode), notFastbootD (fastbootd) mode. I know it's confusing.
Run command:
Code:
adb reboot bootloader
Repeat the instructions above starting with "Right-click the Android Composite ADB Interface".
This second time installing the drivers while in Bootloader (fastboot mode), it will show up as "Android Bootloader Interface". Thanks @simplepinoi177 for the suggestion to add this detail.
Run command:
Code:
fastboot flashing unlock
On the phone, press either the up or down volume button once until you see Unlock the bootloader |>| beside the power button.
Press the power button. The phone will go black for a second and then show near the bottom Device state: unlocked.
After these first-time steps to unlock the bootloader, if you want to root, continue below at the step:
Download the latest Pixel 7 Pro Factory Image (at the bottom of the "Cheetah" section).
Click to expand...
Click to collapse
How to update each month (and also how to root) [requires an unlocked bootloader for updating via this factory image method]
These three instructions only apply if you're already rooted and updating from one firmware version to another:
Made sure all Magisk Modules have been updated.
Disable all Magisk Modules.
UNhide Magisk!
If you are going to use the Official Google Android Flash Tool, then skip the steps I indicate with FAB(Flash-All.Bat).
If using the Android Flash Tool to update/dirty flash, you should have the following items notselected:
Deselect Wipe
Deselect Force Flash all partitions (which will also wipe)
Deselect re-lock bootloader
Always use the latest ADB/Fastboot (SDK Platform Tools) and Windows USB Drivers.
Unzip the Platform Tools.
Download the latest Pixel 7 Pro Factory Image (at the bottom of the "Cheetah" section).
Unzip the factory image to the same platform-tools folder, i.e. so that flash-all.bat and all other files are in the same folder as ADB and Fastboot from the platform-tools.
* FAB VERY important - Edit the flash-all.bat (on Windows) or flash-all.sh (on Linux) and remove the -w from the fastboot update image-cheetah-etcetera.zip line. This will keep the script from wiping your phone when you run it.
Extract only the init_boot.img file from the image-cheetah-etcetera.zip to the same platform-tools folder.
Copy the init_boot.img from the PC to the phone's internal storage.
On the phone: Apply Magisk Stable to the new stock init_boot.img. NOTE: It is always possible that an Android Update (Monthly, QPR [Quarterly Platform Release], new major Android versions, and Beta versions) might need a new version of Magisk Stable, Beta, or Canary from GitHub to work correctly. XDA forum for Magisk is here.
Launch the Magisk app.
Beside "Magisk", click "Install".
Click "Select and Patch a File", and choose the init_boot.img that you just copied to the phone's storage.
Copy the Magisk'd init_boot.img (filename similar to magisk_patched-25200_1a2B3c.img)back over to the computer.
* FAB Run commands:
Code:
adb reboot bootloader
flash-all.bat (on Windows)
or
flash-all.sh (on Linux)
(Note: At least two Apple Macintosh users had trouble using the flash-all.sh - at least one of those users, everything went smooth once they used a Windows PC for this part of the process)
IMPORTANT - The flash-all will take several minutes and reboot on its own several times including to a mode called "FastbootD", and finally reboot into full Android when it's done. Do not interrupt this process. On the FastbootD screen on the phone, do not use any of the manual selection options - let the flash-all script do it's work. Do not unplug your phone until it has fully booted into Android.​ Thanks to @PurppleMonkey and @xgerryx for suggesting a warning about this. Thanks to @simplepinoi177 for suggesting the "FastbootD" clarification.
On the phone:
Wait for the phone to boot normally.
OPTIONAL: If you want to flash both slots, after this first time, then after do the following:
Code:
adb reboot bootloader
fastboot --set-active=other
flash-all.bat
So you're doing the flash-all.bat a second time on the second slot.
On the computer:
Open a Command Prompt and navigate to the platform-tools folder.
Run command:
Code:
adb reboot bootloader
After phone has rebooted into Bootloader (Fastboot) mode, run command:
Code:
fastboot flash init_boot magisk_patched-25200_1a2B3c.img
fastboot reboot
Unlock the phone.
Confirm that the phone boots completely normally.
Cautiously re-enable Magisk Modules.
Reboot.
Confirm everything worked fine.
If the phone won't boot correctly after having enabled Magisk Modules, see either of the two solutions below:
Jon8RFC said:
For the future, you don't need to go into safe mode unless that's your preference. I forgot what all it resets, but it's many settings and it's bothersome. I'd rather just reinstall my modules and not have to figure out those Android settings/changes which I come across days or weeks later when I infrequently do something. Have your phone reboot and run this:
Code:
adb wait-for-device shell magisk --remove-modules
I like to just do this first:
Code:
adb devices
So the server is running, then I have the long one pasted and ready to go once the phone turns off.
Click to expand...
Click to collapse
Find problem apps, Magisk, and LSposed Modules by (three different methods) section in my next post. After following that link, you may have to scroll up a little bit and the section title will be highlighted.
SafetyNet:​Use whichever of these is newer than the other:
@Displax Universal SafetyNet Fix Mod on XDA.
Official Universal SafetyNet Fix released by @kdrag0n available at XDA.
Launch the Magisk app.
Go to Magisk's Settings (Gear in top right).
Click Hide the Magisk app.
When you hide it, you'll have the optional opportunity to change the Magisk app's name to whatever you wish. It doesn't have to be complex to fool apps that check for Magisk.
Important: When you have the Magisk app hidden or renamed, you can accidentally install a new copy of Magisk. This situation won't work at all - neither copy of Magisk will work with two installed. This is one reason why I don't completely hide Magisk, so I can tell it's installed because I have it renamed as something easily recognizable.
Back to the Magisk app's Settings...
Click Systemless hosts. This adds a Magisk Module to Magisk, which you can verify in a later step.
Toggle Zygisk on.
Toggle Enforce DenyList on.
Click Configure DenyList.
Add every app that you want to explicitly deny root and the existence of root.
You can click the 3-dot menu and choose the options to display system and/or OS apps, if necessary.
Note that for many apps, it is not enough to click the single checkmark to the right of the app name in this list. For many but not all apps, you should click on the app name and you'll see it expand to two or more entries, each with its own toggles. In this expanded state, you can now check the single top checkbox beside the main app name and it'll toggle all individual sub-entries.
Some apps add new entries to this list from time to time, so if you find that an app used to work for you when rooted and doesn't now, check this list again and look for the entries that aren't fully checked. There will be an incomplete horizontal line above the apps that don't have all of their sub-entries toggled.
You can use the Search button at the top of this list to find specific apps quickly.
The most common apps you should definitely fully check in this list are:
IMPORTANT - There are some things, such as Google Play Services which it's fine to add to the DenyList, but it's perfectly normal when used in combination with the Universal SafetyNet Fix (USNF) that it is back to being unchecked the next time you visit the DenyList. Since USNF takes care of Google Play Services, you don't even have to add it to the DenyList in the first place.​
Google Play Store
Google Services Framework
Google Play Protect Service
Wallet
GPay
Any banking apps.
Any streaming apps that use DRM.
Any 2FA apps, especially those for work.
Some of those Google apps might not need denying, but it doesn't hurt to deny them.
Any time you toggle more entries in this list, it may be necessary to reboot the phone for it to take effect.
From the main screen in the Magisk app, go to Modules at the bottom.
Confirm that the Systemless hosts Magisk Module is added to this list, and enabled.
Install the appropriate Magisk Module: Universal SafetyNet Fix referenced above these numbered instructions.
Reboot.
Install from the Play Store:
YASNAC - SafetyNet Checker
Launch it.
Click Run SafetyNet Attestation.
It should say:
Basic integrity: Pass
CTS profile match: Pass
Evaluation type: BASIC
Play Integrity API Checker
Launch it.
Click Check.
It should have the following with a green checkmark:
MEETS_DEVICE_INTEGRITY
MEETS_BASIC_INTEGRITY
It's normal for MEETS_STRONG_INTEGRITY to have a red X.
You don't have to keep these installed, although I keep them handy.
Sometimes, clearing app cache and/or data for apps like the Google Play Store, GPay, Wallet and others (and then rebooting) after these steps may help pass SafetyNet as well.
See @V0latyle's explanation (and further linked post) for why we can't achieve STRONG_INTEGRITY with an unlocked bootloader.
See @V0latyle's [DISCUSSION] Play Integrity API regarding why SafetyNet, per se, is actually defunct and replaced with Play Integrity - and New Official Universal SafetyNet Fix released by @kdrag0n v2.4.0 referenced in the steps above takes care of the latter.
Click to expand...
Click to collapse
Optional steps when updating - flashing custom kernels:
Download the custom kernel of choice on the phone.
Be sure to read the particular installation instructions in the kernel threads' OP - any instructions in their OPs takes priority over anything I say here, which is generalized.​For now even the AK3 Zip versions of custom kernels requires Verity and Verification to be disabled.
How to determine if you already have Verity and Verification disabled - see section in Post #3 - Other, most important resources
The two schools of thought on disabling Verity and Verification:
My post here. If you want to discuss it any, please do so in my thread, or at least not in that custom kernel thread, so as to keep the thread on-topic.
Extract the vbmeta.img file from the inner Zip of the factory image zip and put it in the same folder with the latest extracted platform-tools.
Hook the phone up to your computer and run the following commands:
Code:
adb reboot bootloader
[wait for the phone to reboot to bootloader (fastboot mode)]
Code:
fastboot flash vbmeta vbmeta.img --disable-verity
fastboot reboot
Unlock the phone once it's booted up.
Make sure the Kernel Flasher app is up to date. XDA thread for the Kernel Flasher app is here.
Launch Kernel Flasher.
Select the slot that's mounted.
Choose Flash AK3 Zip.
Select the custom kernel zip just downloaded.
When it's done flashing, head to Android Settings and perform a Factory Reset, as is currently needed for Despair kernel.
If you failed to disable Verity and Verification ahead of time, if you have to, just force the phone off using these instructions: Turn your Pixel phone on & off, then press the Volume Down and Power buttons for a couple of seconds to get into the bootloader (fastboot mode). You'll still have to factory reset after disabling Verity in combination with this kernel, for now.
Whenever you use the flash-all to flash your phone, as long as you want to continue to disable Verity and Verification, you'll have to further modify the flash-all script as such:
Code:
fastboot update image-cheetah-buildnumber.zip --disable-verity --disable-verification
Click to expand...
Click to collapse
ADB/Fastboot & Windows USB Drivers:​Platform Tools was updated in August 2022 to v33.0.3 (don't use the newer v34.0.0 - it has issues):
Namelesswonder said:
Anyone that updated their platform tools and needs to downgrade can use these links.
Windows
https://dl.google.com/android/repository/platform-tools_r33.0.3-windows.zip
Mac
https://dl.google.com/android/repository/platform-tools_r33.0.3-darwin.zip
Linux
https://dl.google.com/android/repository/platform-tools_r33.0.3-linux.zip
Click to expand...
Click to collapse
Release Notes https://developer.android.com/studio/releases/platform-tools:
33.0.3 (Aug 2022)​
adb
Don't retry adb root if first attempt failed.
Fix track-devices duplicate entry.
Add receive windowing (increase throughput on high-latency connections).
More specific error messages in the "more than one device" failure cases.
Reject unexpected reverse forward requests.
Fix install-multi-package on Windows.
fastboot
Remove e2fsdroid as part of SDK platform-tools.
Print OemCmdHandler return message on success.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
You'll need this if you're going to unlock the bootloader on your Pixel 7 Pro: SDK Platform Tools (download links for Windows, Mac, and Linux). Note that you can find links to download the tools elsewhere, but I wouldn't trust them - you never know if they've been modified. Even if the person providing the link didn't do anything intentionally, the tools could be modified without them being aware. Why take a chance of putting your phone security further at risk?
You can alternately use the tools from the SDK Manager, but most of us will want to stick to the basic tools-only without the complications of the full development manager.
Click to expand...
Click to collapse
For Windows, get Google's drivers here Get the Google USB Driver (ADB will likely work while the phone is fully booted, but if you're like me, you'll need these drivers for after you adb reboot-bootloader, to be able to use ADB and Fastboot.
Click to expand...
Click to collapse
Other, most important resources​
A list of other important apps: - be sure to thank the respective OPs:
Here's the Magisk section of XDA's forums, for rooting. Magisk on GitHub.
@[email protected]'s section for Nova Launcher / Nova Launcher Prime - been using this since early 2012!
@capntrips' thread [DEV] Kernel Flasher
[KERNEL] CleanSlate |S2S|AdBlock|VIB|BatterySvr - Thanks @tbalden!
[Kernel] [Android Stable]Kirisakura for Pixel 7/Pro aka "Pantah" - thanks @Freak07!
[KERNEL]Despair Kernel - Thanks @DespairFactor!
Multi Timer StopWatch - this multiple timer app is the bomb. Got widgets, customization like crazy, you name it.
See my review with screenshots about Multi Timer StopWatch here.
@Chainfire's thread [APP][5.0+][2020.12.22] CF.lumen v3.74 - I used to use this app to enable my phones to go extra dim before Android developed the better native capability for that, and the app has been confirmed to work on the Pixel 7 Pro for color control, too
@jorrik98's thread [Themes / Apps / Mods] Better Internet Tiles - Bring back Wi-Fi and mobile data toggles! (non-root)
@VR25's thread Advanced Charging Controller (ACC)
CrazyBoyFeng's ACC Settings
MatteCarra's AccA (Advanced Charging Controller App)
@siavash79's thread [MOD][Xposed+Magisk][Pre-Release] AOSP Mods - System modifications for AOSP-based Android 12+. This is a big one for me, personally.
@Quinny899's thread [APP][ROOT][11+][19/07] Classic Power Menu - Power Menu Replacement w/ Wallet, Controls on Android 11, 12, 13+
Swift Backup
@j4velin's thread [APP] Wallpaper Changer - been using this since mid-2011!
@Jawomo's thread [Themes / Apps / Mods] aodNotify - Notification Light / LED - see my post in that thread here for the proper offsets to use the front camera notification circle on the Pixel 7 Pro.
@Jawomo's thread [APP] dynamicSpot - iPhone 14 Pro Dynamic Island for android!
How to unroot
One of these two options:
Official Google Android Flash Tool (OEM Unlocking needs to be toggled on - you do not have to manually unlock the bootloader - their site will do that on its own).
Select the options to:
Wipe
Force flash all partitions
Re-lock bootloader
Flash the completely stock init_boot.img from the same firmware version that you're on:
Code:
adb reboot bootloader
fastboot flash init_boot init_boot.img
TWRP [not made for the Pixel 7 (or 6) Pro yet - will update when or if ever it has - don't hold your breath]
I would guess that this should be the appropriate URL for official TWRP custom recovery for the Pixel 7 Pro, but who knows when/if that will actually be made available, and it may become available unofficially in these forum sections before being made official. I'll adjust this URL as needed. https://twrp.me/google/googlepixel7pro.html.
Click to expand...
Click to collapse
Factory Images (requires an unlocked bootloader)
It's also handy to have to the full official firmware available, whether it's to recover from accidents or for actual development. Note the official link to the general Factory Images for Nexus and Pixel Devices page. The following link goes directly to the Pixel 7 Pro (Cheetah) section: Pixel 7 Pro Factory Images. I prefer to actually bookmark a link to the device listed immediately below the device I want the firmware for, because Google dumbly (in my opinion) puts the latest firmware at the bottom of the list for each particular device, and that ends up making you scroll a lot after a year or two of monthly updates.
Click to expand...
Click to collapse
Full OTA Images (doesn't require an unlocked bootloader - you can ask questions in this thread, but I won't be providing the steps necessary, as I always use the factory image)
Full OTA Images for Nexus and Pixel Devices
Click to expand...
Click to collapse
Check warranty status - *may* reveal if a phone is refurbished, only if the phone was refurbished through Google - thanks to @Alekos for making me aware of the site.
Official Google Pixel Update and Software Repair (reported as of January 23, 2022 to still not be updated for the Pixel 6/Pro - no idea if it has yet now, or if it will be for the 7/Pro)
Official Google Pixel Install fingerprint calibration software (also available at the bottom of the Update and Software Repair page above) - I believe this is only helpful if you've replaced the screen - if it's anything like the Pixel 6 Pro: if you have the screen replaced, then you *must* have the fingerprint reader replaced as well.
Find problem apps, Magisk, and LSposed Modules by (three different methods):
Google's Help Page for Find problem apps by rebooting to safe mode - this can be a lifesaver and keep you from having to do a restore to 100% complete stock or even from having to do a factory reset. This will deactivate all Magisk modules, and they'll remain deactivated even after you boot normally after briefly booting to safe mode. You can re-enable the Magisk modules as you wish to try to narrow down the problem if it was caused by a Magisk module. This can even get things working again after a Magisk Module wasn't finished installing and potentially causing a bootloop.
You can also follow @Jon8RFC's advice:
Jon8RFC said:
For the future, you don't need to go into safe mode unless that's your preference. I forgot what all it resets, but it's many settings and it's bothersome. I'd rather just reinstall my modules and not have to figure out those Android settings/changes which I come across days or weeks later when I infrequently do something. Have your phone reboot and run this:
Code:
adb wait-for-device shell magisk --remove-modules
I like to just do this first:
Code:
adb devices
So the server is running, then I have the long one pasted and ready to go once the phone turns off.
Click to expand...
Click to collapse
Worked for me yesterday when I accidentally tried some old version of a Magisk Module. You have to reinstall your Magisk Modules, but if you're using a third-party widget, it won't disable them like Safe mode does.
(May only be for mis-behaving LSposed modules):
siavash79 said:
In the future try this
adb wait-for-device shell su -c "touch /data/adb/modules/zygisk_lsposed/disable"
adb reboot
Click to expand...
Click to collapse
Official Google Android Flash Tool (OEM Unlocking needs to be toggled on - you do not have to manually unlock the bootloader - their site will do that on its own)
Lughnasadh said:
OEM unlocking in developer options needs to be toggled on. I don't "believe" you have to actually do the "fastboot flashing unlock" command.
Click to expand...
Click to collapse
How to determine if you already have Verity and Verification disabled (required for custom kernels for now)
capntrips said:
I keep seeing this asked, so I added a Magisk module for it to the linked Github release. With the module installed, you can just run:
Code:
su
avbctl get-verity
avbctl get-verification
I spent way more time debugging that I downloaded Github's HTML of the update-binary script rather than the raw file than I care to admit. Off to bed.
Click to expand...
Click to collapse
Alternative two more manual ways of checking:
Freak07 said:
Since you´re probably already rooted anyway if you plan to flash this kernel, simply reboot your device. After you enter the device immediately take a kernel log with for example EXKM or any other app that allows to do that, terminal, etc.
Look for that line
[ 1.273480] init: [libfs_avb]AVB HASHTREE disabled on: /vendor_dlkm
If you see this line, verity/verification should be disabled.
Click to expand...
Click to collapse
capntrips said:
I've seen several cases where having the ability to check would have been handy, so I pushed an avbctl binary built against the latest aosp sources here.
The simplest way to use it would be the following:
Code:
adb push avbctl /data/local/tmp
adb shell
su
cd /data/local/tmp
chmod +x avbctl
./avbctl get-verity
./avbctl get-verification
Click to expand...
Click to collapse
Build ID definitions​
Build ID definitions: - thanks to @Namelesswonder for linking, quoting, and explanation:
Namelesswonder said:
https://source.android.com/docs/setup/about/build-numbers#build-ids-defined
First character is the version code of the release of Android, in this case Tiramisu (T) which is Android 13.
The second character is the branch of device platform that the build is from.
D: Device specific branch, what the device launches with until the next branch merge.
P: Primary branch, designates release branch for a successive version of Android for the device.
Q: Quarterly platform release, the feature drops that happen every quarter.
The third and fourth characters further define the subbranch. It's only well defined for QPRs, with the number defining which QPR the build is from. The number was "2" for the case of Android 12L.
The date roughly corresponds to when it was branched, but is mainly used to distinguish what the security patch level for release builds. Developers builds are closer to the true time it was branched.
The next three digits relate to versions based on that dated branch, and differ when a telecom needs a larger change, for example in the radio firmware or other larger change.
The last two characters are hotfixes, which usually include small changes for telecoms that need something like their APN changed after the date branch.
In this case TQ1A.230205.002 is Android 13 QPR1 that includes security patch 2023-02-05, and TQ2A.230305.008 is Android 13 QPR2 that includes security patch 2023-03-05.
Click to expand...
Click to collapse
Codenames, Tags, and Build Numbers | Android Open Source Project
source.android.com
Build ID definitions​In Android 8.0.0 (Oreo) and higher, individual builds are identified with the build ID format PVBB.YYMMDD.bbb[.Cn], where:
P represents the first letter of the codename of the platform release, for example, O is Oreo.
V represents a supported vertical. By convention, P represents the primary platform branch.
BB is an alphanumeric code that allows Google to identify the exact code branch the build was made from.
YYMMDD identifies the date when the release is branched from or synced with the development branch. It's not always the exact date at which a build was made as it's common for minor variations added to an existing build to re-use the same date code as the existing build.
bbb identifies individual versions related to the same date code, sequentially starting with 001.
Cn is an optional, alphanumeric that identifies a hotfix on top of an existing PVBB.YYMMDD.bbb build, starting from A1.
Older Android releases use a different, shorter build ID code (for example, FRF85B) where:
The first letter is the codename of the release family, for example, F is Froyo.
The second letter is a branch code that allows Google to identify the exact code branch the build was made from. By convention, R is the primary release branch.
The third letter and following two numbers are a date code. The letter counts quarters (A is Q1 2009, F is Q2 2010, and so on). The two numbers count days within the quarter (F85 is June 24, 2010). The date code isn't always the exact date at which a build was made as it's common for minor variations added to an existing build to re-use the same date code as the existing build.
The last letter identifies individual versions related to the same date code, sequentially starting with A (which is implicit and usually omitted for brevity).
Click to expand...
Click to collapse
Reserved #5.
Regarding P7P 5G model numbers and capabilities, and how to determine your hardware version:
Source 1
Source 2 - Thanks to @xike456 for the additional information
There are two hardware versions in the United States:
GP4BC
5G Sub 6GHz
UMTS/HSPA+/HSDPA: Bands 1,2,4,5,6,8,19
LTE: Bands B1/2/3/4/5/7/8/12/13/14/17/18/19/20/25/26/28/29/30/32/38/39/40/41/46/48/66/71
5G Sub-620: Bands n1/2/3/5/7/8/12/14/20/25/28/30/38/40/41/48/66/71/75/76/77/78
GE2AE
5G mmWave + Sub 6GHz
GSM/EDGE: Quad-band (850, 900, 1800, 1900 MHz)
UMTS/HSPA+/HSDPA: Bands 1,2,4,5,6,8,19
LTE: Bands B1/2/3/4/5/7/8/12/13/14/17/18/19/20/25/26/28/29/30/38/39/40/41/42/46/48/66/71
5G Sub-620: Bands n1/2/3/5/7/8/12/14/20/25/28/30/38/40/41/48/66/71/77/78
5G mmWave20: Bands n257/n258/n260/n261
Two other hardware versions. Not sure where they are distributed - possibly in Canada:
GVU6C
5G Sub 6GHz
GQML3
5G mmWave + Sub 6GHz
No other information is known
Two more hardware versions. Not sure where they are distributed, but Japan is one::
G03Z5 - information comes from here. For some reason lumped in with Model GVU6C above at that link and considered the same model.
5G Sub 6GHz
GFE4J - information comes from here. For some reason lumped in with Model GE2AE above at that link and considered the same model.
5G mmWave + Sub 6GHz
Click to expand...
Click to collapse
Thanks to @xike456 for the additional information above, and provided in their post:
xike456 said:
Here is my 7 pro model number: GFE4J
I found some info about this here.
unroot.
Click to expand...
Click to collapse
Thanks to @xstefen for providing this link:
xstefen said:
Google LLC Device Database
device.report
Click to expand...
Click to collapse
How to determine your hardware version:
Lughnasadh said:
Settings>About Phone>Regulatory Labels
Click to expand...
Click to collapse
Carrier/Color/Storage model numbers (gotten from Best Buy):
Unlocked:
Obsidian
128GB - GA03453-US
256GB - GA03456-US
512GB - GA03459-US
Hazel
128GB - GA03455-US
256GB - GA03458-US
512GB - GA03461-US
Snow
128GB - GA03454-US
256GB - GA03457-US
512GB - GA03460-US
Sprint:
Obsidian - 128GB - GA03443-US
Hazel - 128GB - GA03445-US
Snow - 128GB - GA03444-US
Verizon:
Obsidian
128GB - GA03414-US
256GB - GA03417-US
Hazel - 128GB - GA03416-US
Snow - 128GB - GA03415-US
T-Mobile
Obsidian - 128GB - GA03443-US
Hazel - 128GB - GA03445-US
Snow - 128GB - GA03444-US
No idea about AT&T model numbers - Google's site lists the carrier in their Store, but looks like Best Buy doesn't sell them.
Thanks, @Sib64!
Obsidian - 256GB - GA03465-GB - solded by Sosh France
Click to expand...
Click to collapse
Post #7 Pro
My personal advice for how to get your device back up and running as you had it before a factory reset:
I use Nova Launcher Prime, so I do backups anytime I change my home screen or app drawer/tabs setup, so widgets and app icons and other Nova-specific configurations are easier to restore.
Go to Android Settings and use Settings' search box for Backup. Make sure that your Google account is set up to backup your apps (and app data for the apps that developers have configured to use Google's Backup API). Make sure things are backed up. Note, this doesn't backup the apps themselves, only the list of apps, so only applies to apps installed from the Play Store. As I said in parentheses, developers have to choose to integrate Google's Backup API into their app, and those apps only will get their app data backed up into Google's cloud.
If you're rooted also, then you could use something like Swift Backup to backup to the cloud. I do so, although I still restore as much as possible through Google's backup, and I only restore through Swift on a case-by-case basis, as needed when I discover an app that's tough to set back up doesn't have it's data restored by Google.
If you've used Google Photos to backup your photos to Google's cloud, then hit the button in Google Photos to free up space. This will automatically and only delete your local copies of photos and videos that it's already backed up.
Once that ^ is done, look at your internal storage with your favorite File Manger and see if there's anything left that you want to back up manually, since a factory reset will wipe everything. Copy them to your computer or a flash drive.
When you're just starting the out of the box setup after the reset, when it asks you if you want to use a cable to restore things from an old phone, choose No, and that will lead you to Google's cloud backup where you can choose to restore everything, or you can select what you want to restore.
I think you can figure out the rest.
Also see Post #3 - Other, most important resources:
A list of other important apps
Spoiler: Old news from the OP:
March 9, 2023
Note that over three users have said that 34.0.1 did not work correctly for them.
Spoiler
Windows: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Mac: https://dl.google.com/android/repository/platform-tools-latest-darwin.zip
Linux: https://dl.google.com/android/repository/platform-tools-latest-linux.zip
SDK Platform Tools release notes | Android Studio | Android Developers
Android SDK Platform-Tools is a component for the Android SDK.
developer.android.com
Platform-Tools v34.0.1 is up!
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
https://dl.google.com/android/repository/platform-tools_r34.0.1-windows.zip
34.0.1 (March 2023)​
adb
macOS: Reverted "unstable connectivity (MacBook high speed cable)" resolution due to adb install hang (issue #270205252).
fastboot
Windows: Fixed "mke2fs: Illegal or malformed device name while trying to determine filesystem size" error introduced in Platform tools 34.0.0 (issue #271039230).
Click to expand...
Click to collapse
February 6, 2023
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
13.0.0 (TQ1A.230205.001.A2, Feb 2023, Telstra)FlashLinkf81c82a2687ee092b675e8329628a00dfc5ce722e47d0603c000a3dd8ddfb68d13.0.0 (TQ1A.230205.001.D2, Feb 2023, T-Mobile, T-Mobile MVNOs)FlashLinkf2c2d91a753f96c45cb7d31c79929eeac408ba4abff9603cf2c786e36aa8704213.0.0 (TQ1A.230205.002, Feb 2023)FlashLink4439927e14a29c71499ed7796756b7197e76096c197c7f43634638ccea89e237
Google Pixel Update - February 2023 - Google Pixel Community
https://support.google.com/profile/79501506
Kush M.
Community Manager•Original Poster
8 min. ago
Google Pixel Update - February 2023​Announcement
Hello Pixel Community,
We have provided the monthly software update for February 2023. All supported Pixel devices running Android 13 will receive these software updates starting today. The rollout will continue over the next week in phases depending on carrier and device. Users will receive a notification once the OTA becomes available for their device. We encourage you to check your Android version and update to receive the latest software.
Details of this month’s security fixes can be found on the Android Security Bulletin: https://source.android.com/security/bulletin
Thanks,
Google Pixel Support Team
Software versions
Global
Pixel 4a: TQ1A.230205.002
Pixel 4a (5G): TQ1A.230205.002
Pixel 5: TQ1A.230205.002
Pixel 5a (5G): TQ1A.230205.002
Pixel 6: TQ1A.230205.002
Pixel 6 Pro: TQ1A.230205.002
Pixel 6a: TQ1A.230205.002
Pixel 7: TQ1A.230205.002
Pixel 7 Pro: TQ1A.230205.002
Canada
Pixel 4a: TQ1A.230205.001.B2
Telstra (AU)
Pixel 7: TQ1A.230205.001.A2
Pixel 7 Pro: TQ1A.230205.001.A2
T-Mobile, Google Fi (US)
Pixel 4a (5G): TQ1A.230205.001.D2
Pixel 5: TQ1A.230205.001.D2
Pixel 5a (5G): TQ1A.230205.001.D2
Pixel 6: TQ1A.230205.001.D2
Pixel 6 Pro: TQ1A.230205.001.D2
Pixel 6a: TQ1A.230205.001.D2
Pixel 7: TQ1A.230205.001.D2
Pixel 7 Pro: TQ1A.230205.001.D2
What’s included
The February 2023 update includes bug fixes and improvements for Pixel users – see below for details.
Accessibility
Fix for issue preventing touch interaction with Braille keyboard in certain conditions
Audio
Fix for issue occasionally causing instability while Clear Calling is enabled in certain conditions *[1]
Bluetooth
Fix for issue occasionally preventing connection with certain Bluetooth devices or accessories
Framework
Fix for issue occasionally preventing Work profile calendar information from updating in the background
---------------------------------------------------------------
Device Applicability
Fixes are available for all supported Pixel devices unless otherwise indicated below.
*[1] Included on Pixel 7, Pixel 7 Pro
Details
Other
Click to expand...
Click to collapse
Pixel Update Bulletin—February 2023 | Android Open Source Project
source.android.com
Pixel Update Bulletin—February 2023​bookmark_border
Published February 6, 2023
The Pixel Update Bulletin contains details of security vulnerabilities and functional improvements affecting supported Pixel devices (Google devices). For Google devices, security patch levels of 2023-02-05 or later address all issues in this bulletin and all issues in the February 2023 Android Security Bulletin. To learn how to check a device's security patch level, see Check and update your Android version.
All supported Google devices will receive an update to the 2023-02-05 patch level. We encourage all customers to accept these updates to their devices.
Note: The Google device firmware images are available on the Google Developer site.
Announcements​
In addition to the security vulnerabilities described in the February 2023 Android Security Bulletin, Google devices also contain patches for the security vulnerabilities described below.
Security patches​Vulnerabilities are grouped under the component that they affect. There is a description of the issue and a table with the CVE, associated references, type of vulnerability, severity, and updated Android Open Source Project (AOSP) versions (where applicable). When available, we link the public change that addressed the issue to the bug ID, like the AOSP change list. When multiple changes relate to a single bug, additional references are linked to numbers following the bug ID.
Pixel​
CVEReferencesTypeSeveritySubcomponentCVE-2023-20949A-259323133 *IDHighregulator
Qualcomm components​
CVEReferencesSeveritySubcomponentCVE-2022-25711A-235114355
QC-CR#3003049ModerateCameraCVE-2022-33225A-240985973
QC-CR#3138506ModerateBootloader
Functional patches​For details on the new bug fixes and functional patches included in this release, refer to the Pixel Community forum.
Common questions and answers​This section answers common questions that may occur after reading this bulletin.
1. How do I determine if my device is updated to address these issues?
Security patch levels of 2023-02-05 or later address all issues associated with the 2023-02-05 security patch level and all previous patch levels. To learn how to check a device's security patch level, read the instructions on the Google device update schedule.
2. What do the entries in the Type column mean?
Entries in the Type column of the vulnerability details table reference the classification of the security vulnerability.
AbbreviationDefinitionRCERemote code executionEoPElevation of privilegeIDInformation disclosureDoSDenial of serviceN/AClassification not available
3. What do the entries in the References column mean?
Entries under the References column of the vulnerability details table may contain a prefix identifying the organization to which the reference value belongs.
PrefixReferenceA-Android bug IDQC-Qualcomm reference numberM-MediaTek reference numberN-NVIDIA reference numberB-Broadcom reference numberU-UNISOC reference number
4. What does an * next to the Android bug ID in the References column mean?
Issues that are not publicly available have an * next to the Android bug ID in the References column. The update for that issue is generally contained in the latest binary drivers for Pixel devices available from the Google Developer site.
5. Why are security vulnerabilities split between this bulletin and the Android Security Bulletins?
Security vulnerabilities that are documented in the Android Security Bulletins are required to declare the latest security patch level on Android devices. Additional security vulnerabilities, such as those documented in this bulletin are not required for declaring a security patch level.
Versions​
VersionDateNotes1.0February 6, 2023Bulletin Published
Click to expand...
Click to collapse
January 2023:​
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
13.0.0 (TQ1A.230105.002, Jan 2023)FlashLink34d676ff4d260f02d9ada1f16f24fd7995c9b9ca832410099950d9c510db879313.0.0 (TQ1A.230105.002.A1, Jan 2023, Telstra)FlashLink6632344c9647b04bfce622b0decf3733dfb3bc5c3b2c068ea118f8631c1b39b8
Android Security Bulletin—January 2023 | Android Open Source Project
source.android.com
Android Security Bulletin—January 2023​bookmark_border
Published January 3, 2022
The Android Security Bulletin contains details of security vulnerabilities affecting Android devices. Security patch levels of 2023-01-05 or later address all of these issues. To learn how to check a device's security patch level, see Check and update your Android version.
Android partners are notified of all issues at least a month before publication. Source code patches for these issues will be released to the Android Open Source Project (AOSP) repository in the next 48 hours. We will revise this bulletin with the AOSP links when they are available.
The most severe of these issues is a high security vulnerability in the Framework component that could lead to local escalation of privilege with no additional execution privileges needed. The severity assessment is based on the effect that exploiting the vulnerability would possibly have on an affected device, assuming the platform and service mitigations are turned off for development purposes or if successfully bypassed.
Refer to the Android and Google Play Protect mitigations section for details on the Android security platform protections and Google Play Protect, which improve the security of the Android platform.
Note: Information on the latest over-the-air update (OTA) and firmware images for Google devices is available in the January 2023 Pixel Update Bulletin.
Android and Google service mitigations​This is a summary of the mitigations provided by the Android security platform and service protections such as Google Play Protect. These capabilities reduce the likelihood that security vulnerabilities could be successfully exploited on Android.
Exploitation for many issues on Android is made more difficult by enhancements in newer versions of the Android platform. We encourage all users to update to the latest version of Android where possible.
The Android security team actively monitors for abuse through Google Play Protect and warns users about Potentially Harmful Applications. Google Play Protect is enabled by default on devices with Google Mobile Services, and is especially important for users who install apps from outside of Google Play.
2023-01-01 security patch level vulnerability details​In the sections below, we provide details for each of the security vulnerabilities that apply to the 2023-01-01 patch level. Vulnerabilities are grouped under the component they affect. Issues are described in the tables below and include CVE ID, associated references, type of vulnerability, severity, and updated AOSP versions (where applicable). When available, we link the public change that addressed the issue to the bug ID, like the AOSP change list. When multiple changes relate to a single bug, additional references are linked to numbers following the bug ID. Devices with Android 10 and later may receive security updates as well as Google Play system updates.
Framework​The most severe vulnerability in this section could lead to local escalation of privilege with no additional execution privileges needed.
CVEReferencesTypeSeverityUpdated AOSP versionsCVE-2022-20456A-242703780EoPHigh10, 11, 12, 12L, 13CVE-2022-20489A-242703460EoPHigh10, 11, 12, 12L, 13CVE-2022-20490A-242703505EoPHigh10, 11, 12, 12L, 13CVE-2022-20492A-242704043EoPHigh10, 11, 12, 12L, 13CVE-2022-20493A-242846316EoPHigh10, 11, 12, 12L, 13CVE-2023-20912A-246301995EoPHigh13CVE-2023-20916A-229256049EoPHigh12, 12LCVE-2023-20918A-243794108EoPHigh10, 11, 12, 12L, 13CVE-2023-20919A-252663068EoPHigh13CVE-2023-20920A-204584366EoPHigh10, 11, 12, 12L, 13CVE-2023-20921A-243378132EoPHigh10, 11, 12, 12L, 13CVE-2022-20494A-243794204DoSHigh10, 11, 12, 12L, 13CVE-2023-20908A-239415861DoSHigh10, 11, 12, 12L, 13CVE-2023-20922A-237291548DoSHigh11, 12, 12L, 13
System​The most severe vulnerability in this section could lead to local escalation of privilege of BLE with no additional execution privileges needed.
CVEReferencesTypeSeverityUpdated AOSP versionsCVE-2022-20461A-228602963EoPHigh10, 11, 12, 12L, 13CVE-2023-20904A-246300272EoPHigh12L, 13CVE-2023-20905A-241387741EoPHigh10CVE-2023-20913A-246933785EoPHigh10, 11, 12, 12L, 13CVE-2023-20915A-246930197EoPHigh10, 11, 12, 12L, 13
Google Play system updates​The following issues are included in Project Mainline components.
SubcomponentCVEMediaProviderCVE-2023-20912
2023-01-05 security patch level vulnerability details​In the sections below, we provide details for each of the security vulnerabilities that apply to the 2023-01-05 patch level. Vulnerabilities are grouped under the component they affect. Issues are described in the tables below and include CVE ID, associated references, type of vulnerability, severity, and updated AOSP versions (where applicable). When available, we link the public change that addressed the issue to the bug ID, like the AOSP change list. When multiple changes relate to a single bug, additional references are linked to numbers following the bug ID.
Kernel​The most severe vulnerability in this section could lead to remote code execution with no additional execution privileges needed.
CVEReferencesTypeSeveritySubcomponentCVE-2022-42719A-253642087
Upstream kernel [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12] [13] [14]RCECriticalmac80211CVE-2022-42720A-253642015
Upstream kernel [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12] [13] [14]RCECriticalWLANCVE-2022-42721A-253642088
Upstream kernel [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12] [13] [14]RCECriticalMultiple ModulesCVE-2022-2959A-244395411
Upstream kernelEoPHighPipe
Kernel components​The most severe vulnerability in this section could lead to remote code execution with no additional execution privileges needed.
CVEReferencesTypeSeveritySubcomponentCVE-2022-41674A-253641805
Upstream kernel [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12] [13] [14]RCECriticalWLANCVE-2023-20928A-254837884
Upstream kernelEoPHighBinder driver
Kernel LTS​The following kernel versions have been updated. Kernel version updates are dependent on the version of Android OS at the time of device launch.
ReferencesAndroid Launch VersionKernel Launch VersionMinimum Launch VersionA-224575820125.105.10.101
Imagination Technologies​This vulnerability affects Imagination Technologies components and further details are available directly from Imagination Technologies. The severity assessment of this issue is provided directly by Imagination Technologies.
CVEReferencesSeveritySubcomponentCVE-2022-20235A-259967780 *HighPowerVR-GPU
MediaTek components​These vulnerabilities affect MediaTek components and further details are available directly from MediaTek. The severity assessment of these issues is provided directly by MediaTek.
CVEReferencesSeveritySubcomponentCVE-2022-32635A-257714327
M-ALPS07573237 *HighgpsCVE-2022-32636A-257846591
M-ALPS07510064 *HighkeyinstallCVE-2022-32637A-257860658
M-ALPS07491374 *Highhevc decoder
Unisoc components​These vulnerabilities affect Unisoc components and further details are available directly from Unisoc. The severity assessment of these issues is provided directly by Unisoc.
CVEReferencesSeveritySubcomponentCVE-2022-44425A-258731891
U-2028856 *HighKernelCVE-2022-44426A-258728978
U-2028856 *HighKernelCVE-2022-44427A-258736883
U-1888565 *HighKernelCVE-2022-44428A-258741356
U-1888565 *HighKernelCVE-2022-44429A-258743555
U-1981296 *HighKernelCVE-2022-44430A-258749708
U-1888565 *HighKernelCVE-2022-44431A-258741360
U-1981296 *HighKernelCVE-2022-44432A-258743558
U-1981296 *HighKernelCVE-2022-44434A-258760518
U-2064988 *HighAndroidCVE-2022-44435A-258759189
U-2064988 *HighAndroidCVE-2022-44436A-258760519
U-2064988 *HighAndroidCVE-2022-44437A-258759192
U-2064988 *HighAndroidCVE-2022-44438A-258760781
U-2064988 *HighAndroid
Qualcomm components​These vulnerabilities affect Qualcomm components and are described in further detail in the appropriate Qualcomm security bulletin or security alert. The severity assessment of these issues is provided directly by Qualcomm.
CVEReferencesSeveritySubcomponentCVE-2022-22088A-231156521
QC-CR#3052411CriticalBluetoothCVE-2022-33255A-250627529
QC-CR#3212699HighBluetooth
Qualcomm closed-source components​These vulnerabilities affect Qualcomm closed-source components and are described in further detail in the appropriate Qualcomm security bulletin or security alert. The severity assessment of these issues is provided directly by Qualcomm.
CVEReferencesSeveritySubcomponentCVE-2021-35097A-209469821 *CriticalClosed-source componentCVE-2021-35113A-209469998 *CriticalClosed-source componentCVE-2021-35134A-213239776 *CriticalClosed-source componentCVE-2022-23960A-238203772 *HighClosed-source componentCVE-2022-25725A-238101314 *HighClosed-source componentCVE-2022-25746A-238106983 *HighClosed-source componentCVE-2022-33252A-250627159 *HighClosed-source componentCVE-2022-33253A-250627591 *HighClosed-source componentCVE-2022-33266A-250627569 *HighClosed-source componentCVE-2022-33274A-250627236 *HighClosed-source componentCVE-2022-33276A-250627271 *HighClosed-source componentCVE-2022-33283A-250627602 *HighClosed-source componentCVE-2022-33284A-250627218 *HighClosed-source componentCVE-2022-33285A-250627435 *HighClosed-source componentCVE-2022-33286A-250627240 *HighClosed-source component
Common questions and answers​This section answers common questions that may occur after reading this bulletin.
1. How do I determine if my device is updated to address these issues?
To learn how to check a device's security patch level, see Check and update your Android version.
Security patch levels of 2023-01-01 or later address all issues associated with the 2023-01-01 security patch level.
Security patch levels of 2023-01-05 or later address all issues associated with the 2023-01-05 security patch level and all previous patch levels.
Device manufacturers that include these updates should set the patch string level to:
[ro.build.version.security_patch]:[2023-01-01]
[ro.build.version.security_patch]:[2023-01-05]
For some devices on Android 10 or later, the Google Play system update will have a date string that matches the 2023-01-01 security patch level. Please see this article for more details on how to install security updates.
2. Why does this bulletin have two security patch levels?
This bulletin has two security patch levels so that Android partners have the flexibility to fix a subset of vulnerabilities that are similar across all Android devices more quickly. Android partners are encouraged to fix all issues in this bulletin and use the latest security patch level.
Devices that use the 2023-01-01 security patch level must include all issues associated with that security patch level, as well as fixes for all issues reported in previous security bulletins.
Devices that use the security patch level of 2023-01-05 or newer must include all applicable patches in this (and previous) security bulletins.
Partners are encouraged to bundle the fixes for all issues they are addressing in a single update.
3. What do the entries in the Type column mean?
Entries in the Type column of the vulnerability details table reference the classification of the security vulnerability.
AbbreviationDefinitionRCERemote code executionEoPElevation of privilegeIDInformation disclosureDoSDenial of serviceN/AClassification not available
4. What do the entries in the References column mean?
Entries under the References column of the vulnerability details table may contain a prefix identifying the organization to which the reference value belongs.
PrefixReferenceA-Android bug IDQC-Qualcomm reference numberM-MediaTek reference numberN-NVIDIA reference numberB-Broadcom reference numberU-UNISOC reference number
5. What does an * next to the Android bug ID in the References column mean?
Issues that are not publicly available have an * next to the corresponding reference ID. The update for that issue is generally contained in the latest binary drivers for Pixel devices available from the Google Developer site.
6. Why are security vulnerabilities split between this bulletin and device / partner security bulletins, such as the Pixel bulletin?
Security vulnerabilities that are documented in this security bulletin are required to declare the latest security patch level on Android devices. Additional security vulnerabilities that are documented in the device / partner security bulletins are not required for declaring a security patch level. Android device and chipset manufacturers may also publish security vulnerability details specific to their products, such as Google, Huawei, LGE, Motorola, Nokia, or Samsung.
Versions​
VersionDateNotes1.0January 3, 2022Bulletin Published
Click to expand...
Click to collapse
Google Pixel Update - January 2023 - Google Pixel Community
Kush M.
Community Manager•Original Poster
Google Pixel Update - January 2023​Announcement
Hello Pixel Community,
We have provided the monthly software update for January 2023. All supported Pixel devices running Android 13 will receive these software updates starting today. The rollout will continue over the next few weeks in phases depending on carrier and device. Users will receive a notification once the OTA becomes available for their device. We encourage you to check your Android version and update to receive the latest software.
Details of this month’s security fixes can be found on the Android Security Bulletin: https://source.android.com/security/bulletin
This update also includes support for static spatial audio, which will provide surround sound for any connected headset. Another update will roll out to Pixel Buds Pro in the coming weeks that will enable spatial audio with head tracking.
Thanks,
Google Pixel Support Team
Software versions
Global
Pixel 4a: TQ1A.230105.001
Pixel 4a (5G): TQ1A.230105.001
Pixel 5: TQ1A.230105.001
Pixel 5a (5G): TQ1A.230105.001
Pixel 6: TQ1A.230105.002
Pixel 6 Pro: TQ1A.230105.002
Pixel 6a: TQ1A.230105.001.A2
Pixel 7: TQ1A.230105.001.A2
Pixel 7 Pro: TQ1A.230105.002
Canada
Pixel 4a: TQ1A.230105.001.B1
Telstra (AU)
Pixel 7: TQ1A.230105.001.A3
Pixel 7 Pro: TQ1A.230105.002.A1
What’s included
The January 2023 update includes bug fixes and improvements for Pixel users – see below for details.
Audio
Add support for Spatial Audio with certain devices and accessories *[1]
Biometrics
Additional improvements for fingerprint recognition and response in certain conditions *[2]
Bluetooth
Fix for issue occasionally preventing certain Bluetooth Low Energy devices or accessories from pairing or reconnecting
Fix for issue preventing audio from playing over certain headphones or accessories while connected in certain conditions
Camera
Fix for issue occasionally causing captured photos to appear corrupted or distorted while zoomed in *[3]
Display & Graphics
Fix for issue occasionally preventing display from waking or appearing turned off while device is powered on *[3]
User Interface
Fix for issue occasionally causing UI to display in landscape layout while device is held in portrait mode
---------------------------------------------------------------
Device Applicability
Fixes are available for all supported Pixel devices unless otherwise indicated below.
*[1] Included on Pixel 6, Pixel 6 Pro, Pixel 7, Pixel 7 Pro
*[2] Included on Pixel 6a, Pixel 7
*[3] Included on Pixel 7, Pixel 7 Pro
Details
Other
Click to expand...
Click to collapse
​December 2022:​
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
13.0.0 (TQ1A.221205.011, Dec 2022)FlashLinkb144b4262b6a349efe756a9446c9e9ce9123d839280f5e5b06ebbc661c577b6813.0.0 (TQ1A.221205.012, Dec 2022, O2 UK)FlashLink4406695deca324c94ef49b9be594362e350d45bdf2e7fad40cf147cdcfe5dc89
Google Pixel Update - December 2022 - Google Pixel Community
Kush M.
Community Manager•Original Poster
3 min. ago
Google Pixel Update - December 2022​Announcement
Hello Pixel Community,
We have provided the monthly software update for December 2022. All supported Pixel devices running Android 13 will receive these software updates starting today. The rollout will continue over the next week in phases depending on carrier and device. Users will receive a notification once the OTA becomes available for their device. We encourage you to check your Android version and update to receive the latest software.
Details of this month’s security fixes can be found on the Android Security Bulletin: https://source.android.com/security/bulletin
Thanks,
Google Pixel Support Team
Software versions
Global
Pixel 4a: TQ1A.221205.011
Pixel 4a (5G): TQ1A.221205.011
Pixel 5: TQ1A.221205.011
Pixel 5a (5G): TQ1A.221205.011
Pixel 6: TQ1A.221205.011
Pixel 6 Pro: TQ1A.221205.011
Pixel 6a: TQ1A.221205.011
Pixel 7: TQ1A.221205.011
Pixel 7 Pro: TQ1A.221205.011
Canada
Pixel 4a: TQ1A.221205.011.B1
O2 (UK)
Pixel 6a: TQ1A.221205.012
Pixel 7: TQ1A.221205.012
Pixel 7 Pro: TQ1A.221205.012
What’s included
In addition to new features, the December 2022 software update for Pixel devices includes several fixes and improvements across several areas including device performance, stability, connectivity, and more – see below for some notable improvements.
Apps
Fix for issue causing text input to certain fields in the Phone app to display in a darker color
Fix for issue occasionally causing playback errors when seeking through video content in certain apps
Fix for issue occasionally preventing text messages from restoring from cloud backups during device setup
General improvements for background performance in certain Google apps
Audio
General improvements for USB audio support for various cables or accessories *[1]
General improvements to support various audio codecs with certain devices or accessories *[4]
Battery & Charging
Battery usage in Settings displays information since last full charge (up to 7 days)
Fix for issue occasionally causing device to power off while Battery Share is active *[4]
Fix for issue occasionally causing higher battery usage during media playback with certain apps *[2]
Fix for issue occasionally preventing Adaptive charging from working in certain conditions *[2]
Fix for issue occasionally preventing wireless charging from working with certain accessories *[2]
General improvements for charging, battery usage or thermal performance in certain conditions *[1]
Biometrics
Fix for issue occasionally causing audio to skip when played over certain Bluetooth devices or accessories *[2]
Fix for issue occasionally delaying when the fingerprint icon is displayed on the lock screen *[1]
Fix for issue occasionally preventing fingerprint sensor from detecting touch while always-on display is active *[3]
Fix for issue where fingerprint enrollment may occasionally display visual glitches in certain conditions *[1]
Improvements for face unlock lock screen helper text shown in certain conditions *[2]
Bluetooth
Fix for issue causing music playback to continue without audible sound after ending a call while using certain Bluetooth accessories *[2]
Fix for issue occasionally causing audio to skip when played over certain Bluetooth devices or accessories *[2]
Fix for issue occasionally preventing audio switching between connected Bluetooth devices in certain conditions
Fix for issue occasionally preventing Bluetooth Low Energy devices from displaying a device name during pairing
Fix for issue occasionally preventing connection to car head units using older Bluetooth versions
Fix for issue occasionally preventing discovery of certain Bluetooth devices or accessories
Fix for issue occasionally preventing previously paired Bluetooth devices from reconnecting
General improvements for Bluetooth stability and performance in certain conditions
Camera
Fix for issue occasionally causing Camera app to crash while zoomed in or switching modes *[2]
Fix for issue occasionally causing viewfinder preview to display a blank screen *[2]
Fix for issue where video that is recorded while switching between camera modes occasionally shows gaps in playback *[2]
General improvements for camera stability and performance in certain conditions
Display & Graphics
Fix for issue occasionally causing screen to flicker when waking from always-on display
Fix for issue occasionally causing visual artifacts or glitches while using certain apps or games *[3]
Framework
Fix for issue occasionally causing notifications to display in a different color theme from the system
Fix for issue occasionally causing the wrong character to display after a new line in certain apps or UI elements
Fix for issue occasionally causing Work Profile app notifications to appear even if Work Profile is paused
Fix for issue occasionally preventing certain apps to rotate to landscape orientation
Fix for issue occasionally preventing keyboard from being dismissed while using certain apps
Sensors
Fix for issue occasionally preventing "tap to wake" or "lift to wake" from working in certain conditions *[1]
Fix for issue occasionally preventing Adaptive brightness from activating in certain conditions
Fix for issue occasionally preventing Quick Tap from triggering app or system shortcuts in certain conditions
Fix to improve Adaptive brightness transitions during phone calls in certain conditions *[1]
General improvements for proximity sensor performance under certain lighting conditions *[1]
System
General improvements for system stability and performance in certain conditions
General improvements to optimize device thermal performance in certain conditions or use cases *[1]
Telephony
Fix for issue causing reduced network or call stability under certain conditions *[2]
Fix for issue occasionally preventing network SIM cards from activating in certain conditions *[3]
General improvements for network connection stability and performance in certain conditions
General improvements for network connectivity after toggling airplane mode off
General improvements for switching between 3G to 4G on certain carrier networks
General improvements for VPN connection stability and performance on mobile networks under certain conditions
General improvements for Wi-Fi calling stability and performance for certain carriers or networks
Improve dual SIM network connectivity in certain conditions *[3]
Improve RCS messaging stability under certain conditions *[2]
Touch
General improvements for touch response and performance in certain conditions *[1]
User Interface
Change for home screen search bar behavior to open the Google app when tapping the G logo
Fix for issue occasionally causing "Pause work apps" button display over app drawer or in the wrong position
Fix for issue occasionally causing certain Settings toggles to appear disabled, or set to the wrong state
Fix for issue occasionally causing device color theme to change unexpectedly
Fix for issue occasionally causing home screen app icons to appear duplicated after adjusting grid size
Fix for issue occasionally causing home screen widgets or icons to appear small or scaled down in certain conditions
Fix for issue occasionally causing media player controls to appear invisible or hidden in notification shade
Fix for issue occasionally causing notification overflow dot to overlay app icons on lock screen
Fix for issue occasionally causing notifications to disappear or appear invisible in notification shade
Fix for issue occasionally causing screenshot captures to fail in certain conditions
Fix for issue occasionally causing suggested apps in Search to overlap or display over results
Fix for issue occasionally causing text to appear incorrectly cutoff or truncated at different font sizes
Fix for issue occasionally causing UI to reset after adjusting display resolution
Fix for issue occasionally causing wallpaper to appear black or empty in certain conditions
Fix for issue occasionally enabling touch interaction during the lock screen transition after screen is turned off
Fix for issue occasionally preventing media player album art from updating when content changes
Fix for issue occasionally preventing media player controls from displaying on lock screen
Fix for issue occasionally preventing screen to appear blank or frozen after launching certain apps
Fix for issue where incoming notifications would occasionally display over others listed in the notification shade
Fix to improve responsiveness of At A Glance home and lock screen widget for certain conditions or use cases
Fix to improve spacing for certain UI modals in device setup and Settings
General improvements for performance in certain UI transitions and animationas
Wi-Fi
Fix for issue occasionally preventing hotspot from turning on in certain conditions *[1]
General improvements for Wi-Fi network connection stability & performance in certain conditions *[1]
---------------------------------------------------------------
Device Applicability
Fixes are available for all supported Pixel devices unless otherwise indicated below.
*[1] Included on Pixel 6, Pixel 6 Pro, Pixel 6a, Pixel 7, Pixel 7 Pro
*[2] Included on Pixel 7, Pixel 7 Pro
*[3] Included on Pixel 6, Pixel 6 Pro, Pixel 6a
*[4] Included on Pixel 6, Pixel 6 Pro, Pixel 7, Pixel 7 Pro
Details
Other
Click to expand...
Click to collapse
Click to expand...
Click to collapse
New software features have arrived to the Pixel family - Google Pixel Community
Kush M.
Community Manager•Original Poster
New software features have arrived to the Pixel family​Announcement
Your Pixel devices get a boost of helpfulness with Feature Drops *[1]. They’re automatic software updates that send new and upgraded features to your phone, earbuds, and watch, making them even better as time goes on. With the latest feature drop, your Pixel phone now has clearer incoming calls *[2], next-level audio with Pixel Buds Pro *[3], speaker labels on recordings *[4], a VPN by Google One for online protection *[5], and more. And it all happens over the air, so you get that new-device feeling without needing to get anything new.
The latest features will begin rolling out to Pixel devices starting on December 5, with rollout continuing over the next few weeks. Be sure to update to the latest Android version and update your Android apps, then look out for a notification from the Pixel Tips app to learn more about all of the ways your Pixel just got more helpful.
Hear voices clearly.
Pixel enhances the other caller’s voice and reduces their background noise to help you hear them when they’re in a noisy place *[2].
Surround yourself with sound (coming January 2023).
Feel like you’re at the center of the action in your favorite movies and shows. When paired with Pixel Buds Pro, your Pixel supports spatial audio with head tracking for immersive surround sound all around *[3].
Note taking just got easier.
Pixel helps you keep track of who said what in meetings and lectures with more than one participant. It transcribes recordings of multiple speakers by labeling each one and adding line breaks when speakers change *[4].
Extra protection when you’re online.
With VPN by Google One, Pixel 7 and Pixel 7 Pro help protect your online activity no matter what app or web browser you use. With no added cost to you *[5].
Wallpaper that wows.
Bring your Pixel screen to life with the new Live Bloom wallpaper collection. Explore the latest set of custom designs featuring vibrant images that shift and sway when your phone moves *[6].
New cultural wallpapers.
Keep your Pixel screens culturally relevant with the latest Curated Culture wallpapers. This new installment, illustrated by Morgan Harper Nichols, celebrates the International Day of Persons with Disabilities. Morgan is an artist, poet, podcaster, and author whose work is inspired by real-life interactions and stories.
Find it. Fast.
Bring the power of Google Search to your Pixel to search your entire phone and the web, so you can quickly find what you’re looking for – a contact, app, screenshot, setting, and more. Now available for Pixel 4a and later.
Security and privacy, simplified.
Now Pixel makes it easier to protect your phone, accounts, and passwords by having all your security and privacy settings in one place. This includes new action cards that notify you of any safety risks and provide easy steps to enhance your privacy and security.
More ways to lift language barriers.
Live Translate can now translate texts in your messaging apps into more languages, including Arabic, Persian, Swedish, Vietnamese, and Danish *[7].
Understand how you sleep.
Pixel can help you understand what affects your sleep, like coughing, snoring, or how much you’re on your phone at bedtime *[8], now available for Pixel 6 & Pixel 6 Pro.
Get smarter about your sleep.
Gain a better understanding of your sleep quality with helpful insights from Sleep Profile on Pixel Watch *[9]. It looks beyond your nightly sleep patterns and tracks your habits and trends over a month-long period. You’ll get a sleep analysis based on 10 key metrics, be matched with one of six sleep animals representing distinct sleeper types, and receive education and personalized metric ranges so you can understand what to focus on to get better rest.
Summary of availability per device
† Only available in English (US).
----------------------------------------------------------------
Disclaimers
*[1] Your Pixel will generally receive Feature Drops during the applicable Android update and support periods for the phone. See g.co/pixel/updates for details. Availability of some Feature Drops may vary.
*[2] Available only on Pixel 7 and Pixel 7 Pro. Not available on VOIP calls. Call quality of incoming call depends on the environment, carrier network conditions, and other factors. Actual results may vary.
*[3] Coming in January 2023. Available only on Pixel 6, Pixel 6 Pro, Pixel 7 and Pixel 7 Pro. Requires compatible app and supported content. See g.co/pixelbudspro/help for details. Pixel Buds Pro sold separately.
*[4] Available only on Pixel 6 or newer Pixel phones. Not available in all languages.
*[5] Available only on Pixel 7 and Pixel 7 Pro. Restrictions apply. Some data is not transmitted through VPN. Not available in all countries. All other Google One membership benefits sold separately. This VPN offer does not impact price or benefits of Google One Premium plan. Use of VPN may increase data costs depending on your plan. See g.co/pixel/vpn for details.
*[6] Available only on Pixel 6 or newer Pixel phones.
*[7] Available only on Pixel 6 or newer Pixel phones. Not available in all languages or countries. Not available on all media or apps. See g.co/pixel/livetranslate for more information.
*[8] Not intended to diagnose, cure, mitigate, prevent or treat any disease or condition. Consult your healthcare professional if you have questions about your health. See g.co/pixel/digitalwellbeing for details.
*[9] Requires Fitbit account and mobile app, and Fitbit Premium membership. Not intended for medical purposes. Consult your healthcare professional for questions about your health. Feature not available in all countries or languages.
Details
Other
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Pixel Update Bulletin—December2022 | Android Open Source Project
source.android.com
Pixel Update Bulletin—December2022​bookmark_border
Published December 5, 2022
The Pixel Update Bulletin contains details of security vulnerabilities and functional improvements affecting supported Pixel devices (Google devices). For Google devices, security patch levels of 2022-12-05 or later address all issues in this bulletin and all issues in the December 2022 Android Security Bulletin. To learn how to check a device's security patch level, see Check and update your Android version.
All supported Google devices will receive an update to the 2022-12-05 patch level. We encourage all customers to accept these updates to their devices.
Note: The Google device firmware images are available on the Google Developer site.
Announcements​
In addition to the security vulnerabilities described in the December 2022 Android Security Bulletin, Google devices also contain patches for the security vulnerabilities described below.
Security patches​Vulnerabilities are grouped under the component that they affect. There is a description of the issue and a table with the CVE, associated references, type of vulnerability, severity, and updated Android Open Source Project (AOSP) versions (where applicable). When available, we link the public change that addressed the issue to the bug ID, like the AOSP change list. When multiple changes relate to a single bug, additional references are linked to numbers following the bug ID.
Framework​
CVEReferencesTypeSeverityUpdated AOSP versionsCVE-2022-20504A-225878553EoPModerate13CVE-2022-20512A-238602879EoPModerate13CVE-2022-20514A-245727875EoPModerate13CVE-2022-20524A-228523213EoPModerate13CVE-2022-20553A-244155265EoPModerate13CVE-2022-20554A-245770596EoPModerate13CVE-2022-20510A-235822336IDModerate13CVE-2022-20511A-235821829IDModerate13CVE-2022-20513A-244569759IDModerate13CVE-2022-20523A-228222508IDModerate13CVE-2022-20530A-231585645IDModerate13CVE-2022-20538A-235601770IDModerate13CVE-2022-20559A-219739967IDModerate13CVE-2022-20543A-238178261DoSModerate13CVE-2022-20526A-229742774EoPLow13
Media Framework​
CVEReferencesTypeSeverityUpdated AOSP versionsCVE-2022-20548A-240919398EoPModerate13CVE-2022-20528A-230172711IDModerate13
System​
CVEReferencesTypeSeverityUpdated AOSP versionsCVE-2021-39771A-224545390EoPModerate13CVE-2022-20503A-224772890EoPModerate13CVE-2022-20505A-225981754EoPModerate13CVE-2022-20506A-226133034EoPModerate13CVE-2022-20507A-246649179EoPModerate13CVE-2022-20508A-218679614EoPModerate13CVE-2022-20509A-244713317EoPModerate13CVE-2022-20519A-224772678EoPModerate13CVE-2022-20520A-227203202EoPModerate13CVE-2022-20522A-227470877EoPModerate13CVE-2022-20525A-229742768EoPModerate13CVE-2022-20529A-231583603EoPModerate13CVE-2022-20533A-232798363EoPModerate13CVE-2022-20536A-235100180EoPModerate13CVE-2022-20537A-235601169EoPModerate13CVE-2022-20539A-237291425EoPModerate13CVE-2022-20540A-237291506EoPModerate13CVE-2022-20544A-238745070EoPModerate13CVE-2022-20546A-240266798EoPModerate13CVE-2022-20547A-240301753EoPModerate13CVE-2022-20549A-242702451EoPModerate13CVE-2022-20550A-242845514EoPModerate13CVE-2022-20556A-246301667EoPModerate13CVE-2022-20557A-247092734EoPModerate13CVE-2022-20558A-236264289EoPModerate13CVE-2022-42542A-231445184EoPModerate13CVE-2022-20199A-199291025IDModerate13CVE-2022-20515A-220733496IDModerate13CVE-2022-20516A-224002331IDModerate13CVE-2022-20517A-224769956IDModerate13CVE-2022-20518A-224770203IDModerate13CVE-2022-20527A-229994861IDModerate13CVE-2022-20531A-231988638IDModerate13CVE-2022-20535A-233605242IDModerate13CVE-2022-20541A-238083126IDModerate13CVE-2022-20552A-243922806IDModerate13CVE-2022-20555A-246194233IDModerate13CVE-2022-42535A-224770183IDModerate13CVE-2022-20521A-227203684DoSModerate13CVE-2022-20545A-239368697DoSModerate13
Kernel components​In addition to the platform fixes described above, Pixel also ingested the upstream kernel security fixes associated with snapping to LTS version 5.10.107.
More information is available at the Android Common Kernels page.
CVEReferencesTypeSeveritySubcomponentCVE-2022-0500A-228560539
Upstream kernelEoPModerateKernelCVE-2022-1116A-234020136
Upstream kernelEoPModerateKernelCVE-2022-1419A-235540888
Upstream kernelEoPModerateKernelCVE-2022-20565A-160818461
Upstream kernelEoPModerateKernelCVE-2022-20566A-165329981
Upstream kernel [2]EoPModerateBluetooth L2CAPCVE-2022-20567A-186777253
Upstream kernelEoPModerateKernelCVE-2022-20568A-220738351
Upstream kernelEoPModerateio_uringCVE-2022-20571A-234030265
Upstream kernelEoPModeratedm-verityCVE-2022-20572A-234475629
Upstream kernel [2]EoPModeratedm-verityCVE-2022-28390A-228694391
Upstream kernelEoPModerateKernelCVE-2022-30594A-233438137
Upstream kernel [2] [3]EoPModerateKernelCVE-2022-34494A-238479990
Upstream kernelEoPModerateKernelCVE-2022-34495A-238480163
Upstream kernelEoPModerateKernelCVE-2022-20573A-235183128
Upstream kernel [2]IDModerateKernel
Pixel​
CVEReferencesTypeSeveritySubcomponentCVE-2022-20582A-233645166 *EoPCriticalLDFWCVE-2022-20583A-234859169 *EoPCriticalLDFWCVE-2022-20584A-238366009 *EoPCriticalTF-ACVE-2022-20585A-238716781 *EoPCriticalLDFWCVE-2022-20586A-238718854 *EoPCriticalLDFWCVE-2022-20587A-238720411 *EoPCriticalLDFWCVE-2022-20588A-238785915 *EoPCriticalLDFWCVE-2022-20597A-243480506 *EoPCriticalLDFWCVE-2022-20598A-242357514 *EoPCriticalLDFWCVE-2022-20599A-242332706 *EoPCriticalPixel firmwareCVE-2022-42534A-237838301 *EoPCriticalTF-ACVE-2022-20498A-249998113 *IDCriticallibfdtCVE-2022-20589A-238841928 *IDCriticalLDFWCVE-2022-20590A-238932493 *IDCriticalLDFWCVE-2022-20591A-238939706 *IDCriticalLDFWCVE-2022-20592A-238976908 *IDCriticalLDFWCVE-2022-20603A-219265339 *RCEHighModemCVE-2022-20607A-238914868 *RCEHighCellular FirmwareCVE-2022-20610A-240462530 *RCEHighPixel cellular modemCVE-2022-20561A-222162870 *EoPHighAudioCVE-2022-20564A-243798789 *EoPHighlibufdtCVE-2022-42531A-231500967 *EoPHighTF-ACVE-2022-20562A-231630423 *IDHighAudio processorCVE-2022-20574A-237582191 *IDHighLDFWCVE-2022-20575A-237585040 *IDHighLDFWCVE-2022-20602A-211081867 *IDHighModemCVE-2022-20604A-230463606 *IDHighExynos FirmwareCVE-2022-20608A-239239246 *IDHighCellular firmwareCVE-2022-42529A-235292841 *IDHighKernelCVE-2022-42530A-242331893 *IDHighPixel firmwareCVE-2022-42532A-242332610 *IDHighPixel firmwareCVE-2022-20563A-242067561 *EoPModerateBootloaderCVE-2022-20569A-229258234 *EoPModeratePixel Thermal Control DriverCVE-2022-20576A-239701761 *EoPModerateTelephonyCVE-2022-20577A-241762281 *EoPModeratesitrilCVE-2022-20578A-243509749 *EoPModeraterild_exynosCVE-2022-20579A-243510139 *EoPModeraterild_exynosCVE-2022-20580A-243629453 *EoPModeratelibufdtCVE-2022-20581A-245916120 *EoPModeratePixel camera driverCVE-2022-20594A-239567689 *EoPModerateWireless ChargerCVE-2022-20596A-239700400 *EoPModerateWireless ChargerCVE-2022-20600A-239847859 *EoPModerateLWISCVE-2022-42501A-241231403 *EoPModeraterild_exynosCVE-2022-42502A-241231970 *EoPModeraterild_exynosCVE-2022-42503A-241231983 *EoPModeraterild_exynosCVE-2022-42504A-241232209 *EoPModeraterild_exynosCVE-2022-42505A-241232492 *EoPModeraterild_exynosCVE-2022-42506A-241388399 *EoPModeraterild_exynosCVE-2022-42507A-241388774 *EoPModeraterild_exynosCVE-2022-42508A-241388966 *EoPModeraterild_exynosCVE-2022-42509A-241544307 *EoPModeraterild_exynosCVE-2022-42510A-241762656 *EoPModeraterild_exynosCVE-2022-42511A-241762712 *EoPModeraterild_exynosCVE-2022-42513A-241763204 *EoPModeraterild_exynosCVE-2022-42518A-242536278 *EoPModeraterild_exynosCVE-2022-42519A-242540694 *EoPModeraterild_exynosCVE-2022-42520A-242994270 *EoPModeraterild_exynosCVE-2022-42521A-243130019 *EoPModeraterild_exynosCVE-2022-42523A-243376893 *EoPModeraterild_exynosCVE-2022-42525A-243509750 *EoPModeraterild_exynosCVE-2022-42526A-243509880 *EoPModeraterild_exynosCVE-2022-20560A-212623833 *IDModerateKernelCVE-2022-20570A-230660904 *IDModerateModemCVE-2022-20593A-239415809 *IDModerategrallocCVE-2022-20595A-239700137 *IDModerateWireless ChargerCVE-2022-20601A-204541506 *IDModerateModemCVE-2022-20605A-231722405 *IDModerateModemCVE-2022-20606A-233230674 *IDModerateModemCVE-2022-20609A-239240808 *IDModerateCellular firmwareCVE-2022-42512A-241763050 *IDModeraterild_exynosCVE-2022-42514A-241763298 *IDModeraterild_exynosCVE-2022-42515A-241763503 *IDModeraterild_exynosCVE-2022-42516A-241763577 *IDModeraterild_exynosCVE-2022-42517A-241763682 *IDModeraterild_exynosCVE-2022-42522A-243130038 *IDModeraterild_exynosCVE-2022-42524A-243401445 *IDModerateModemCVE-2022-42527A-244448906 *DoSModerateModem
Qualcomm components​
CVEReferencesSeveritySubcomponentCVE-2022-25677A-235114749
QC-CR#3122626
QC-CR#3103567ModerateBootloader
Qualcomm closed-source components​
CVEReferencesSeveritySubcomponentCVE-2021-30348A-202032128 *ModerateClosed-source componentCVE-2022-25675A-208302286 *ModerateClosed-source component
Functional patches​For details on the new bug fixes and functional patches included in this release, refer to the Pixel Community forum.
Common questions and answers​This section answers common questions that may occur after reading this bulletin.
1. How do I determine if my device is updated to address these issues?
Security patch levels of 2022-12-05 or later address all issues associated with the 2022-12-05 security patch level and all previous patch levels. To learn how to check a device's security patch level, read the instructions on the Google device update schedule.
2. What do the entries in the Type column mean?
Entries in the Type column of the vulnerability details table reference the classification of the security vulnerability.
AbbreviationDefinitionRCERemote code executionEoPElevation of privilegeIDInformation disclosureDoSDenial of serviceN/AClassification not available
3. What do the entries in the References column mean?
Entries under the References column of the vulnerability details table may contain a prefix identifying the organization to which the reference value belongs.
PrefixReferenceA-Android bug IDQC-Qualcomm reference numberM-MediaTek reference numberN-NVIDIA reference numberB-Broadcom reference numberU-UNISOC reference number
4. What does an * next to the Android bug ID in the References column mean?
Issues that are not publicly available have an * next to the Android bug ID in the References column. The update for that issue is generally contained in the latest binary drivers for Pixel devices available from the Google Developer site.
5. Why are security vulnerabilities split between this bulletin and the Android Security Bulletins?
Security vulnerabilities that are documented in the Android Security Bulletins are required to declare the latest security patch level on Android devices. Additional security vulnerabilities, such as those documented in this bulletin are not required for declaring a security patch level.
Versions​
VersionDateNotes1.0December 5, 2022Bulletin Published
Click to expand...
Click to collapse
Click to expand...
Click to collapse
November 2022:​Monday & Tuesday, November 7 & 8, 2022: Pixel 7 Pro Factory Images available:
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
13.0.0 (TD1A.221105.001, Nov 2022)FlashLinkf2793a62a48bc840b892e74dd515739b657d2727c25edd074064e3ab019e73bf13.0.0 (TD1A.221105.003, Nov 2022, Verizon, Verizon MVNOs)FlashLink021be73c7c602de0fdefcd3a4c43d0d745188b7847880a0d4a2ccb6aa64c47a6
Tuesday, November 8, 2022: But I lump it in after the standard day's two images above.
13.0.0 (TD1A.221105.001.A1, Nov 2022, Telia)FlashLink8c02369293402dc629728e0966d2ccc1976f513ed783ea2f64dcd1e55e221b3e
Thanks @Namelesswonder!
Namelesswonder said:
Much newer radio and modem on TD1A.221105.001.A1, even newer than QPR1 Beta 3.1.
Firmware Image​Radio Version​TD1A.221105.001​radio-cheetah-g5300g-220908-220908-b-9040061​TD1A.221105.001.A1​radio-cheetah-g5300g-220908-221031-b-9238462​TD1A.221105.003​radio-cheetah-g5300g-220908-221006-b-9144834​T1B3.221003.003​radio-cheetah-g5300g-220923-221001-b-9127780​T1B3.221003.008​radio-cheetah-g5300g-220923-221028-b-9229469​
Click to expand...
Click to collapse
Click to expand...
Click to collapse
October 2022:​
Monday, October 24, 2022: Two more custom kernels are released for the Pixel 7 Pro:
[KERNEL] CleanSlate T1.4.0 |S2S|AdBlock|VIB|BatterySvr - Thanks @tbalden!
[Kernel][24.10.2022][Android 13.0.0 Stable]Kirisakura for Pixel 7/Pro aka "Pantah" - thanks @Freak07!
Click to expand...
Click to collapse
Sunday, October 23, 2022: Thanks to @xike456 for additional hardware model number information, which you can find in Post #6 - Regarding P7P 5G model numbers and capabilities, and how to determine your hardware version.
Click to expand...
Click to collapse
Saturday, October 15, 2022: New Universal SafetyNet Fix released by @Displax, which is a later minor revision of the test MOD version previously posted in this thread, and of the original MOD 2.0 which apparently had some typos - the latter which didn't work due to the typos but is now fixed if you download the latest one. You can get it either from XDA or on GitHub.
Click to expand...
Click to collapse
Monday, October 14, 2022: A custom kernel is released for the Pixel 7 Pro:
[KERNEL]Despair Kernel - Thanks @DespairFactor!
Click to expand...
Click to collapse
Thursday, October 13, 2022: Pixel 7 Pro Factory Image is up! TD1A.220804.031 is confirmed to be the zero-day update, so is the most recent. Thanks to @bosox284 for confirming.
VersionFlashDownloadSHA-256 Checksum13.0.0 (TD1A.220804.009.A2, Oct 2022)FlashLink8e7393e1bd7f86d76d75cdea988d5e4ebfded3a50fac26d774b9eb07152c1ed513.0.0 (TD1A.220804.009.A5, Oct 2022, JP carriers)FlashLinkc68659bdd1d2b0b9a1740daa1502acbbf1b535be5b7e5bada157c82ef5fbf5c513.0.0 (TD1A.220804.031, Oct 2022)FlashLink6152f6f3d8437be0ef840ed7056f15d0f52ba181a1d029ff84bd9d83c860d49f
Click to expand...
Click to collapse
@roirraW "edor" ehT
You upgraded to the Pixel 7 Pro ?
When will the factory images for the 7 Pro most likely be posted?
Way to go @roirraW "edor" ehT!!
Let's get this party started!!!
Gordietm said:
When will the factory images for the 7 Pro most likely be posted?
Click to expand...
Click to collapse
Editing this post. The Pixel 6 factory images were posted on the same day the phone was released (not when pre-orders started). So maybe Oct. 13? or around there.
Glad to see you in the Pixel 7 pro forums! @roirraW "edor" ehT
Lughnasadh said:
I believe the factory images for the Pixel 6 series were first posted 9 days after the phones were released.
Click to expand...
Click to collapse
9 days after pre orders were announced or when you could buy them?
rester555 said:
9 days after pre orders were announced or when you could buy them?
Click to expand...
Click to collapse
EDIT: I was wrong. The Pixel 6 was released on Oct. 28, 2021 and the factory images were released the same day. Pre-orders for the Pixel 6 began on Oct. 19, if I remember correctly.
Sib64 said:
@roirraW "edor" ehT
You upgraded to the Pixel 7 Pro ?
Click to expand...
Click to collapse
Yes, sir! The USB 3.2 Gen 2 pushed me over the edge, believe it or not. I like to copy hundreds of gigs of FLAC music to my devices all the time.
Ghisy said:
Way to go @roirraW "edor" ehT!!
Let's get this party started!!!
Click to expand...
Click to collapse
rester555 said:
Glad to see you in the Pixel 7 pro forums! @roirraW "edor" ehT
Click to expand...
Click to collapse
Thanks! Would you believe I only one other time upgraded to a next up higher model of any phone - the last time being from the Sprint Samsung Galaxy S2/Epic 4G to the Verizon S3, and both phones had already been out for long enough to be a great deal under contract back then.
Lughnasadh said:
EDIT: I was wrong. The Pixel 6 was released on Oct. 28, 2021 and the factory images were released the same day. Pre-orders for the Pixel 6 began on Oct. 19, if I remember correctly.
Click to expand...
Click to collapse
That is exactly correct from my memory, too.
roirraW edor ehT said:
Yes, sir! The USB 3.2 Gen 2 pushed me over the edge, believe it or not. I like to copy hundreds of gigs of FLAC music to my devices all the time.
Thanks! Would you believe I only one other time upgraded to a next up higher model of any phone - the last time being from the Sprint Samsung Galaxy S2/Epic 4G to the Verizon S3, and both phones had already been out for long enough to be a great deal under contract back then.
That is exactly correct from my memory, too.
Click to expand...
Click to collapse
I/O controllers are so necessary and not many people talk about that with phones. I hate how slow transfer speeds are with subpar hardware.
My next move in house is to convert everything to wifi 7. 6E is not a big enough jump from wifi 5. Also wired 10 gbE everywhere or higher.
I have a NAS video server for the house and there is nothing out there to do better than 2.5 gbE. I am waiting for better hardware to make my house 10 gbE.
rester555 said:
I/O controllers are so necessary and not many people talk about that with phones. I hate how slow transfer speeds are with subpar hardware.
Click to expand...
Click to collapse
Absolutely! Especially these phones without MicroSD card slots, it just makes it worse - not that MicroSD cards are the complete solution, either. Especially if you don't want to take your phone case off, take out the card, put it back in later...
rester555 said:
My next move in house is to convert everything to wifi 7. 6E is not a big enough jump from wifi 5. Also wired 10 gbE everywhere or higher.
Click to expand...
Click to collapse
I went 6E in the last couple of weeks only because all Synology routers including their newest don't work directly with Frontier Fiber's gigabit ONT - they've got a serious bug and I worked with Synology for a month without any progress. I became completely burned out on continuously experimenting with my networking. To Synology's credit, they bent over backward and then even connected me directly with their developers, but I just couldn't take it anymore.
At some point, I felt I should start getting paid to help them debug their product, and at another point, I just have to continue on with life and just use my network without plugging / unplugging / factory resetting, you name it, every day.
I went with two high-end gaming Asus routers (I don't game, though) and they have been the easiest to set up and have no issues at all.
[/mini-rant]
rester555 said:
I have a NAS video server for the house and there is nothing out there to do better than 2.5 gbE. I am waiting for better hardware to make my house 10 gbE.
Click to expand...
Click to collapse
The Asus GT-AXE16000 - which I got a great deal on but it's still super expensive, has 2x10Gb, 1x2.5Gb, and 4x1Gb ports, and you can use any one or two of them as WAN, and it automatically makes the remaining LAN. Great flexibility. My second (mesh) router is their GT-AXE11000 - which I don't even remember if it has 10Gb, but probably does have one, and it definitely has 1x2.5Gb. I used each router's 2.5Gb for the mesh connection, although you can do so with Wi-Fi too if you wish. We have a small house but the opposite side of the house from my computer room can stand to have a little help for the best internet speeds, although the GT-AXE16000 by itself did quite well and much better than Synology's models.
I'd love to see places that can SIM unlock the AT&T version so I can unlock the bootloader. Stuck doing the carrier version - hard to pass up $3 a month with a trade.
roirraW edor ehT said:
Absolutely! Especially these phones without MicroSD card slots, it just makes it worse - not that MicroSD cards are the complete solution, either. Especially if you don't want to take your phone case off, take out the card, put it back in later...
I went 6E in the last couple of weeks only because all Synology routers including their newest don't work directly with Frontier Fiber's gigabit ONT - they've got a serious bug and I worked with Synology for a month without any progress. I became completely burned out on continuously experimenting with my networking. To Synology's credit, they bent over backward and then even connected me directly with their developers, but I just couldn't take it anymore.
At some point, I felt I should start getting paid to help them debug their product, and at another point, I just have to continue on with life and just use my network without plugging / unplugging / factory resetting, you name it, every day.
I went with two high-end gaming Asus routers (I don't game, though) and they have been the easiest to set up and have no issues at all.
[/mini-rant]
The Asus GT-AXE16000 - which I got a great deal on but it's still super expensive, has 2x10Gb, 1x2.5Gb, and 4x1Gb ports, and you can use any one or two of them as WAN, and it automatically makes the remaining LAN. Great flexibility. My second (mesh) router is their GT-AXE11000 - which I don't even remember if it has 10Gb, but probably does have one, but it definitely has 1x2.5Gb, and I used each router's 2.5Gb for the mesh connection, although you can do so with Wi-Fi too if you wish. We have a small house but the opposite side of the house from my computer room can stand to have a little help for the best internet speeds, although the GT-AXE16000 by itself did quite well and much better than Synology's models.
Click to expand...
Click to collapse
Understood on the gt-axe16000, it's great, but Wifi 7 combines all channels 2.4 GHz, 5 GHz, and 6 GHz into a 320 MHz bandpass channel. With 6E, you can only get half that. It's almost there but I can wait another 2 years. Then my desktop, phones, and routers will all be converted.

Categories

Resources