yashsingh1/xdaforums huggingface dataset:
[Google Pixel 7 Pro] Schroeder09:
Thanks for the info and link. The article starts out saying Google is aware and is working on it, but there isn't any specific issue in the issue tracker mentioned that we can all dogpile. There is a screenshot of a user saying they entered an issue in issue tracking. I guess I will go to that. I don't have time now.

Later in the article in one of the march updates to the article the author says someone contacted Google, Google said they were unaware of the issue, and asked the user to send their phone in for a replacement. So are they working on it or not? My guess is they're not just using intelligence guided by experience. Also, the roots of the drain don't seem to be analyzed by power users. The sources of drain they mention seem to be the generic battery usage categories found within the android system settings app as opposed to specific wakelock names that would be obtained from an app like better battery stats. I guess the ImsService thing might be the one specific wakelock mentioned in the article.

I do show high network drain. When I look in BBS wakelocks though I don't see ImsService. I think I have seen it before but not regularly. It's the same old usual offenders: gms.services, android *job.deadline* alarms, etc. See attached screenshots below.
[Google Pixel 7 Pro] Schroeder09:
What's your usage during the day over that 50% drop as far as SOT? If it's like an hour and the rest is idle drain that 50% drop is NOT normal. The pixel 2xl I came came from gets nearly as good of battery as my p7p, and I replaced the battery in that. Aftermarket batteries are never as good as OEM. This idle drain is not normal. Google play services seems to be the issue- as always- but the s23U guys have the same gms stuff. They are seeing stellar battery life. I fear this IS hardware related and is due to using inferior, cheap, junk cell antennas or modems of some sort that have to make the phone work hard to search for good signal. I hope I am wrong and that the issue is software, but I don't remember battery life ever getting better through the life of the phone. It only ever gets worse with software and is never corrected. I should just go back to the November update and stop messing with updating this phone. Use it on November, 2022 update for 5 years until I get a new phone and forget about it!
[Google Pixel 7 Pro] xtcislove:
Quick questions:

I like to keep the abillity to use custom kernels if i update and i know i need to edit the flash all bat like this:

fastboot update image-cheetah-buildnumber.zip --disable-verity --disable-verification

1. Does pixel flasher keep verity etc diabled or do i need to tick disable verity and disable verification with advanced mode enabled?

2. If i use flash all bat or pixel flasher with verity/verfication option enabled to UPDATE the device will it wipe data?
[Google Pixel 7 Pro] davidgro:
My method is just replace the init_boot.img inside the image-cheetah zip (Using 7-Zip, using Explorer causes it to fail to flash for some reason), then it flashes already-rooted in one pass.

(Edited to specify 7-Zip)
[Google Pixel 7 Pro] Lughnasadh:
Tick it, although I believe it may be able to save that choice for you. Double check to make sure.

No, but if you decide to disable verity & verification again you will have to wipe.
[Google Pixel 7 Pro] badabing2003:
I'll answer it here now, but in the future, please post your question in PF thread to keep this thread relevant to the topic it covers.

These settings in PF are remembered, so unless you change them, next time you load PF, it will select what you last had.

Keep Data will keep Data (basically remove -w)

Disable Verity and Disable Verification are used for custom Kernels / ROMs

These settings only apply when you flash.
[Google Pixel 7 Pro] xtcislove:
Thanks. My question was a bit off maybe.

I like to know that if i update next month for example to a new version. Do i need to disable verity and verification AGAIN and will this wipe data AGAIN?

For me this question is not really pixel flasher specific thats why i asked here.
[Google Pixel 7 Pro] badabing2003:
First time you disable them, it will wipe.

Subsequent flashing, if you don't want to wipe, then you have to make sure they remain disabled.

See it as a state, you change the state, it wipes.
[Google Pixel 7 Pro] xtcislove:
Okay i think i got it thank you.

If i flash without:

fastboot update image-cheetah-buildnumber.zip --disable-verity --disable-verification

It would probably reenable verity/verification and result in a wipe.

But since i add --disable-verity --disable-verification the state will not change and there is no wipe.

English is not my native language so i needed clarification.
[Google Pixel 7 Pro] Lughnasadh:
If you flash without disabling the verity and verification flags it won't cause a wipe in and of itself. What causes a wipe is when you go from an enabled state to a disabled state.

Correct, sort of. See first answer.
[Google Pixel 7 Pro] roirraW "edor" ehT:
I've been getting this with my notifications on my lock screen. As far as I recall, starting yesterday. The notifications always start out minimized like this for at least several seconds, sometimes longer (the Google Voice notification):

Then it'll on its own switch to the expanded format I'm used to on the lockscreen (I obscured personal information):
[Google Pixel 7 Pro] simplepinoi177:
Looks like a different (i.e. weird) attempt at competing with the iPhone dynamic island...?

Do you know what might've been recently updated? I imagine maybe Pixel Launcher...
[Google Pixel 7 Pro] roirraW "edor" ehT:
Not that one, that's @Jawomo's [APP] dynamicSpot - iPhone 14 Pro Dynamic Island for android!. Sorry for not clarifying further. I mean in the middle of the screen, and Google Voice is just an example - all notifications were coming up minimized at first on my lock screen.

Then after a few seconds, they would maximize. In the last hour or two, the minimized lock screen notifications would no longer expand on their own, and not expand when I tried to manually expand them either, so I just checked, and my phone was set to hide sensitive content on my lock screen.

I can't swear which way I had it set most recently because there has been a time when I had sensitive content hidden, but I know my notifications had always used to come up as expanded on the lock screen - unless there were multiple notifications from the same app, that is.

Yesterday, I was fooling with BlueStacks Android emulator on my Windows PC, and I didn't set a lock screen or even fool with the lock screen settings, but I wonder if it synced some setting from there, but slowly in some strange way.

Either that or the whole thing is just some weird Google goings-on behind the scenes. So now I have it set to show sensitive content again, so the trouble should be over. Weird.

Edit: I don't use Pixel Launcher, I use Nova. I recently installed one 2FA app and a restaurant app, but I think that's all.
[Google Pixel 7 Pro] roirraW "edor" ehT:
I have another strange problem with a manufacturer's app to control their device I have. The problem again didn't coincide with the March release. It only started happening in the last week or less.

Since shortly after I stared using the app, I set it to Unrestricted for battery usage, which then kept the connection alive (via Wi-Fi) 100% of the time, even if I left the area and came back, it would reconnect without me having to do anything. The remote app hasn't been updated since 2021, FYI.

All of a sudden this past week, the remote app would eventually lose connection, and I'd have to back out twice to its main menu and go back in to choose Remote Control. After a couple of days of this, I checked the Battery usage setting for the app again, and it was back to Optimized. I switched it back to Unrestricted, but it still loses connection, just like it used to before I set it to Unrestricted the first time.

I even wiped app cache and data, uninstalled and reinstalled, with no luck, it still loses connection. Bummer.

I don't pay attention to Google Play System updates, so I don't know what version I was on when the remote would stay connected, but I'm on the March 1, 2023, Play System update now.

TQ2A.230305.008.C1 Global firmware, not that it's likely to matter.
[Google Pixel 7 Pro] WoKoschekk:
FYI: Google Play System Updates are included in your monthly security patch.

Android Security Bulletin—March 2023 | Android Open Source Project

source.android.com

If your manufacturer doesn't provide any OTAs for your device then Google is still able to update core components via the Google Play System Updates (Project Mainline).
[Google Pixel 7 Pro] simplepinoi177:
I don't know if this will resolve the issue -- or explain what the issue might be -- but if, somehow (if you are lucky), if you can enable the app in "device admin apps", it will force the app to be Unrestricted; Optimized and Restricted will actually be grayed out, so there's no choice but for the app to be Unrestricted. But I don't know what calls for an app to request/require device admin permissions, so I'm unsure if your app will be under that. But, if luckily it does, you can keep it at Unrestricted while you research the issue/problem and hopefully eventually not require it to have those permissions for it to stay.

I've noticed that I have to set some apps back to Unrestricted myself; but I wouldn't be able to recall what I had been doing when it had changed -- it was seemingly randomly me checking at any random time...
[Google Pixel 7 Pro] WoKoschekk:
Not at all. If an app requests DEVICE_ADMIN_ENABLED it doesn't have the permissions to do all the actions of an admin. The requested permissions are defined in policies. Nova Launcher for example could change the lock screen as device admin and nothing else.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Are they always included in the regular monthly firmware updates? I recall at least on the Pixel 6 Pro, many users including me were not always on the same Play System Update as other users, even when running on the same firmware version.

Also, there's a separate place to manually check for new Google Play system updates. At least once or twice, I was able to get an update to the Play system by manually checking for it, although I'm sure it would've updated automatically eventually, and I don't really pay attention to what version I'm on, normally.

This app doesn't appear among those available in the Device admin apps list, but a good idea to check. Thanks.
[Google Pixel 7 Pro] WoKoschekk:
Yes, they have to. The Google Play System Update is updating /system/apex/ which part of your firmware. These APEX files are special extended APK formats, but including a payload.img. For those users without the latest patch Google can download the APEX files through the Play Store. Then using the payload.img to update /system. APEX files are packed - like APKs - as ZIP archive.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Google's Nearby Share Beta is heading to Windows making file transfers from Android a breeze

A year after its announcement, Nearby Share is finally making an appearance for Windows.

www.xda-developers.com

The New Quick Share App for Windows | Android

Wirelessly share photos, documents, and more between Android devices and Windows PCs by downloading the Quick Share for Windows App.

android.com
[Google Pixel 7 Pro] simplepinoi177:
saw an article talking about this...am excited about it...

bluetooth transfer is finicky and slower, and opening particular apps (going all the way back to SuperBeam) could get clumsy and tedious...

I constantly transfer stuff between phones and my pc/laptop...
[Google Pixel 7 Pro] SimorghDroid:
Hi all,

Up untill the latest factory image update TQ2A.230305.008 there were no Canada version. I rooted my 7 pro to TQ1A.221205.011, Dec 2022 and haven't done any updates since then. I live in Canada, with Canadian carrier.

Should I grab the TQ2A.230305.008.A3, Mar 2023, WINDTRE/Canada or the Global, TQ2A.230305.008.C1, Mar 2023?

Would greatly appreciate your guidance.

Thanks
[Google Pixel 7 Pro] Gordietm:
I live in Toronto and I've tried the global and Canadian version and couldn't find any difference.
[Google Pixel 7 Pro] SimorghDroid:
Thank you. 👍🏼
[Google Pixel 7 Pro] roirraW "edor" ehT:
If you're on a Canadian carrier, theoretically it's best to be on the Canadian firmware, but theory doesn't always match reality and as @Gordietm pointed out, it can sometimes make no difference which firmware you flash.

Edit: At worst if you flashed one firmware, and you thought you weren't getting as good performance with your carrier, you'd always be able to dirty flash the other firmware(s) to try them instead.
[Google Pixel 7 Pro] AwildPikachu:
If I start my phone the CTS check will pass but after 30 seconds or so it will fail.

Has anyone had this problem?
[Google Pixel 7 Pro] roirraW "edor" ehT:
Hi, are on you on the latest USNF Mod, and you followed all the directions at:

Post #2 - Unlocking Bootloader / Rooting / Updating | SafetyNet | ADB/Fastboot & Windows USB Drivers:

SafetyNet
[Google Pixel 7 Pro] roirraW "edor" ehT:
Interesting (direct download links in OP still work).

SDK Platform Tools release notes | Android Studio | Android Developers

Android SDK Platform-Tools is a component for the Android SDK.

developer.android.com
[Google Pixel 7 Pro] AwildPikachu:
Thanks

I used the new mod and it's now working :)
[Google Pixel 7 Pro] simplepinoi177:
that's fairly concerning...!!!

is r34 giving them (or causing) that much trouble that they just shutdown dl'ing them for now...?!?!:eek:

*i imagine they did such an update to it that someone on staff didn't link to the new stuff properly...
[Google Pixel 7 Pro] roirraW "edor" ehT:
Awesome! I'm glad that worked for you.

Funnily enough, the direct download links to 34.x still work. Just take the links for 33.0.3 (which still work) and change the version number. That crazy Google🙀.
[Google Pixel 7 Pro] Ghisy:
So no April update yet, huh?

I gues it won't drop until next Tuesday since Monday is a Holiday.
[Google Pixel 7 Pro] Lughnasadh:
Easter is on Sunday and isn't observed on Monday like some other holidays that fall on a Sunday, so Monday is not a federal holiday.
[Google Pixel 7 Pro] Ghisy:
But Monday is Easter Monday, it's a Holiday here. I thought it was in the US as well? 🤔

Google Calendar says it is.
[Google Pixel 7 Pro] Dr.Pepper:
Since accidentally Google dropped april update for Pixel 5 user somehow which has build namber ****20230405, i guess tomorrow we will get at least April security update (maybe Android 14 beta also)
[Google Pixel 7 Pro] Lughnasadh:
Not in the U.S..

Federal Holidays

Welcome to opm.gov

www.opm.gov
[Google Pixel 7 Pro] roirraW "edor" ehT:
And it's back and without v34.x listed, BUT the download links download 34.0.1!

SDK Platform Tools release notes | Android Studio | Android Developers

Android SDK Platform-Tools is a component for the Android SDK.

developer.android.com
[Google Pixel 7 Pro] roirraW "edor" ehT:
Also, according to Website-Watcher, these parts of the changelog are new (highlighted in yellow):
[Google Pixel 7 Pro] roirraW "edor" ehT:
And...in the continuing saga of ADB/Fastboot, it's back to where we were before the page went down. 34.0.0, 34.0.1, and 34.0.0 RC2 release notes, and the downloads are still to 34.0.1.

SDK Platform Tools release notes | Android Studio | Android Developers

Android SDK Platform-Tools is a component for the Android SDK.

developer.android.com
[Google Pixel 7 Pro] Lughnasadh:
https://twitter.com/i/web/status/1643523279075020801

2023.4.5 Magisk v26.0

The Magic Mask for Android

topjohnwu.github.io
[Google Pixel 7 Pro] YassGo:
Guys, anyone with gps accuracy issues on latest build ?
[Google Pixel 7 Pro] roirraW "edor" ehT:
None here so far. I don't drive as often as I used to, but I use Android Auto every time I do, and I had no problems with it the 3-4 days I've driven in the last week.
[Google Pixel 7 Pro] roirraW "edor" ehT:
I wonder how long before it goes live as a Stable release on GitHub?
[Google Pixel 7 Pro] Lughnasadh:
Not sure. He usually releases a beta for a day or two before releasing the stable, but not sure if that will happen this time. Think they are still adding some last minute commits as well.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Ah! Yes, then I do hope it goes Beta first! :) Either way, I'll hold off until it's been broadly tested.
[Google Pixel 7 Pro] Lughnasadh:
Magisk 26 is out. Guess no beta, lol.

Release Magisk v26.0 · topjohnwu/Magisk@7cb0909

The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.

github.com
[Google Pixel 7 Pro] roirraW "edor" ehT:
Yes, it's Beta. I know, it's misleading the way it presents.

GitHub - topjohnwu/Magisk: The Magic Mask for Android

The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.

github.com
[Google Pixel 7 Pro] Lughnasadh:
Ah, ok. That's why it hasn't hit my phone yet, lol.
[Google Pixel 7 Pro] Ghisy:
So, has anyone updated Magisk to v26 stable yet? Does it affect Zygisk/LSPosed?
[Google Pixel 7 Pro] WoKoschekk:
is it already stable yet? Magisk release page says yes but Magisk app finds only an update for beta channel.
[Google Pixel 7 Pro] Ghisy:
V26 shows up on the stable releases' page: https://github.com/topjohnwu/Magisk/releases/tag/v26.0

But yeah, no update yet within the Magisk app. 🤷‍♀️
[Google Pixel 7 Pro] Lughnasadh:
Only the Beta and Canary channels have been updated. John usually waits a little bit before releasing the Stable build after releasing the Beta build to make sure there are no bugs.
[Google Pixel 7 Pro] WoKoschekk:
Checked it on my non rooted phone. Looks like stable.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Note that it says Current is 25.2. Installed is 26.0. That means 25.2 is the latest Stable.

Also, from the main page:
[Google Pixel 7 Pro] Lughnasadh:
Additionally....

https://twitter.com/i/web/status/1643677679424790528
[Google Pixel 7 Pro] roirraW "edor" ehT:
Hopefully coming soon, but no downloads yet:

And we're off!

Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers

developers.google.com

13.0.0 (TQ2A.230405.003.E1, Apr 2023)	Flash	Link	1f04869e24347c7b01a238bfdbeb472f68f557986da3533872158e4a4e6caa14

Google Pixel Update - April 2023 - Google Pixel Community

Android Security Bulletin—April 2023 | Android Open Source Project

source.android.com
[Google Pixel 7 Pro] roirraW "edor" ehT:
And we're off!

Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers

developers.google.com

13.0.0 (TQ2A.230405.003.E1, Apr 2023)	Flash	Link	1f04869e24347c7b01a238bfdbeb472f68f557986da3533872158e4a4e6caa14
[Google Pixel 7 Pro] rester555:
Has anyone installed magisk 26 and used adaway? I am jaded by the adaway not working with new builds.
[Google Pixel 7 Pro] Lughnasadh:
I have (Canary 26001) on my Pixel 6 Pro running A14 DP2 and it's working fine.
[Google Pixel 7 Pro] LLStarks:
I'm reading that there might be serious T-Mobile bugs in this release for the Pixel 7. I don't have any concrete details yet beyond maybe n25/n71 being forced and disrupting other signals that latch on as secondary.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Added to the OP, thank you. If you get more details, and/or find out that manually flashing an old modem.img helps, let us know and I'll add that information, too.
[Google Pixel 7 Pro] LLStarks:
Working theory: When connected to standalone 3CA 5G, radio performance degrades. This can also happen in 2CA if the two aggregated bands differ.

Per Josh and David from the Shannon Telegram channel.
[Google Pixel 7 Pro] radekmazur:
Where are you getting this from? I'm not gonna upgrade yet. Thanks.
[Google Pixel 7 Pro] LLStarks:
I already explained in my follow up post.
[Google Pixel 7 Pro] WhoIsJohnGalt1979:
Can some one confirm that this issue is resolved with the April update. Just checking, considering there is a USB fox component in the update.
[Google Pixel 7 Pro] WhoIsJohnGalt1979:
Issue fixed.
[Google Pixel 7 Pro] chaos193:
I had my USB debugging off and accidentally caused a bootloop. Is there a way for me to reflash back the build?

edit/ nvm fixed it by switching into safe mode and activating my usb debugging back.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Releases · topjohnwu/Magisk

The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.

github.com

Magisk v26.1 is listed, but Stable is still v25.2 and Beta is still 26.0.
[Google Pixel 7 Pro] WoKoschekk:
Magisk App offers an update to v26.1.
[Google Pixel 7 Pro] Fishawy:
Yes, updated from 25.2 stable to 26.1 stable via app prompt.
[Google Pixel 7 Pro] roirraW "edor" ehT:
I figured it was heading for Stable. No idea why the Github page still shows Stable as 25.2.

Additionally, the:

Release Notes

The Magic Mask for Android

topjohnwu.github.io

page, where it has:

v26.1

results in a 404 error. Shrug. Well, cool. Let us know if you encounter any issues with Magisk 26.1. It always gives me a little caution when the Stable has changes more recent than the Beta; i.e. the most recent changes weren't Beta-tested.

Releases · topjohnwu/Magisk

The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.

github.com
[Google Pixel 7 Pro] WoKoschekk:
Changelog v26.1
[Google Pixel 7 Pro] Sib64:
The update for Magisk shows me 25.2 to 26.1 and I only recover on the stable channel.

So I think 26.1 is a stable version.

I haven't yet installed.

I have a question @roirraW "edor" ehT , I didn't have time to do the March update so I'm going straight to the April update ?
[Google Pixel 7 Pro] Ghisy:
I also have 26.1 as an update in Magisk and I'm only using the stable channel. So I guess it was pushed to stable already.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Yes, you never have to go incremental, whether with the firmware image or the Full OTA zip. You can go straight from whatever old version to any newer version. At least, that's my understanding with the Full OTA zip, hence the "Full", but definitely with the firmware image.

Yep, I'm sure it's meant to be considered Stable, too. I got an email from GitHub for the update five hours ago with the subject [topjohnwu/Magisk] Release v26.1 - Magisk v26.0, which I'm guessing since it mentions both 26.1 and 26.0, is another symptom of whatever has been done which also resulted in the main GitHub page still showing 25.2 as Stable. I'm only guessing, though.
[Google Pixel 7 Pro] Lughnasadh:
Yes, it was pushed to the Stable Channel...

https://twitter.com/i/web/status/1645715571227635712
[Google Pixel 7 Pro] Ghisy:
I'll update everything later tonight! Big night ahead! 😁
[Google Pixel 7 Pro] Born<ICs:
I have a question @roirraW "edor" ehT , what is good method for organizing Windows platform tools folder?

What if you have more than one phone? I seem to get confused when dropping files into platform tools when others exist.

Thanks much
[Google Pixel 7 Pro] jlokos:
I set up different folders on the root directory for my wife's phone (P7Pro) and my phone (P6Pro), For e.g., Android P6P and Android P7P.
[Google Pixel 7 Pro] Ghisy:
Guys, are you still using platform tools 33.0.3 to update? I don't wanna install 34.x because it's still bugged, right?
[Google Pixel 7 Pro] Ghisy:
Mine is on C:\Android\platform-tools and looks like this (check the attached screenshot). Please note I've already copied the files from April (the first 4 files at the top of the list) as I'm preparing to update.
[Google Pixel 7 Pro] Lughnasadh:
I just keep my Platform Tools folder clean (only native files). When I want to flash something I copy the files to the Platform Tools folder, flash, and then immediately delete those files so there is never a worry about having "conflicting" files in that folder.