yashsingh1/xdaforums huggingface dataset:
[Google Pixel 7 Pro] roirraW "edor" ehT:
Google Photos is getting an even better search bar with support for "complex queries"

Google is making it easier to search for photos in your collection.

www.xda-developers.com

Google Pixel phones could save your hearing with intriguing At a Glance update

A future update could give Pixel users a heads-up when something in an environment can damage their hearing.

www.xda-developers.com

Google could bring a separate volume control for calls and notifications

After 13 versions of Android, the feature is finally on its way. The Android OS is known for having many features, some more obscure than others but one...

www.gsmarena.com
[Google Pixel 7 Pro] roirraW "edor" ehT:
Android’s May 2023 security patch prevents downgrades to infinitely old system app versions

May’s security patch fixes a potential security issue

www.androidpolice.com
[Google Pixel 7 Pro] vurtomatic:
I'm T-Mobile but I don't understand what that means. Should I avoid flashing the latest update?
[Google Pixel 7 Pro] simplepinoi177:
Basically, what @LLStarks meant is that, a couple (months) of updates ago, it disabled a type of "band" (I'm guessing here) on T-Mobile that works best (as it has a higher "capacity"; probably akin to 2.4GHz being over-crowded and polluted that 5GHz & 6GHz are at a higher band with more channels -- so bigger "capacity"), and it hasn't been corrected or re-enabled by May's monthly update nor the latest QPR -- in which he states that, it seems the best one can hope for is the stable QPR3 to fix the restriction.

Either way, avoiding flashing will most likely not do anything for you, especially if you have updated the firmware past January (I'm estimating, I believe I recall seeing T-Mobile having update issues in Feb.) because, in any case, you're not going to have all the "bands" available anyways, whether you update this month or not...
[Google Pixel 7 Pro] vurtomatic:
Thank so much for the clarity! Too late for me then. I didn't even notice. :ROFLMAO:
[Google Pixel 7 Pro] LLStarks:
Yes, this is an ongoing nightmare for T-Mobile users on stable releases. Betas haven't been immune either over the months. Features like VoNR or 3CA would appear and disappear.

Google and Samsung have extremely poor quality control and branching for the modem and vendor partitions. And it's so pointless. Almost every other phone on the market can freely advertise its network features and take advantage of whatever a tower offers. But not the Pixel. Every single carrier, feature, VoLTE support, 5G support, VoWifi, bandwidth for bands, etc has to be explicitly declared in firmware. All of that just to region lock a phone and keep some unspecified party happy.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Used Google's Nearby Sharing Beta for Windows for the second time to transfer my init_boot.img and Magisk'd init_boot.img back and forth between my PC and phone, and all worked well again.
[Google Pixel 7 Pro] roirraW "edor" ehT:
I just wiped my phone by accident. LOL! Got to laugh or cry. I had taken the -w out of the flash-all.bat, but I was trying to figure out why I was getting a failure after the Sending sparse 'product_a' 1/12 (262112 KB), so I re-extracted both Platform-Tools 33.0.3 and the latest firmware, and I was prepared to re-edit the freshly extracted flash-all.bat, but it slipped my mind.

The good news, the phone flashed fine this time, although ironically, this last time I attempted it, I was doing it through a powered USB-A USB 3.2 Gen 2 powered hub that's 20 feet away in a different room from my desktop computer, where it's attached via USB-C to a USB 3.2 Gen 2 port. I've had no problems flashing through the hub before, but it's funny that all three of my much closer USB-C ports and cables failed consistently, but through the hub worked perfectly.

I'm glad I at least keep both root and non-root cloud backups, plus a few backups from individual apps that have the feature (Nova Launcher 7.x, AOSP Mods...).
[Google Pixel 7 Pro] Lughnasadh:
A little cleansing is good for the soul, so I hear 🙃
[Google Pixel 7 Pro] roirraW "edor" ehT:
LOL! The biggest pain is my work's 2FA, since we can't choose what we 2FA with, and you also can't choose more than one device to 2FA with. It's been so long since I needed to deal with my work's helpdesk, I almost forgot how to contact them.
[Google Pixel 7 Pro] amders:
i fell you man... it really suck when setup again.. especially when inserting username and password then otp 2fa code what-so-ever
[Google Pixel 7 Pro] Ghisy:
Awww man, that sucks!! :(

I always check multiple times if my flash-all file is edited the way it should before connecting my phone and rebooting to bootloader.

Just updated mine, all good! Next will be the June Feature Drop!
[Google Pixel 7 Pro] roirraW "edor" ehT:
Another good thing out of accidentally wiping my phone is that as I had posted about sometime in the last month, my Zidoo remote control app is now connected automatically to the device as long as I'm connected to my home Wi-Fi, which is how it was for me for a few weeks after I set the app to have unrestricted battery use. I've set it again as unrestricted. Here's hoping it won't go like last time, and in a few weeks stop being connected on its own without me going to its main screen and back into the remote part of the app.

I probably won't get that lucky, though.

Hmmmm, just had a thought. If it does happen again, after I reinstall my root adblocker, I'll have to try setting that app as an exception. I don't get ads in that app anyway, but I didn't have the adblocker installed for a while, and maybe installing it caused the Zidoo app to stop automatically being connected in some weird way. We'll see!

Doesn't appear to be AdAway, at least not right away.
[Google Pixel 7 Pro] roirraW "edor" ehT:
The Pixies vs. Pixels: 'Where Is My Mind?' Is Turning Off Alarms on Google Phones

The Pixies tweeted “Sorry about that! ⏰ 📱 🛑” after fans noticed the band's hit was deactivating their a alarms.

gizmodo.com

https://twitter.com/i/web/status/1653669158817607680
[Google Pixel 7 Pro] hpower1:
Another successful update to May for me. Using platform tools v33.0.3 and magisk 26101.

A thank you again to the info here and all that keep this thread alive and updated.
[Google Pixel 7 Pro] amders:
thank for the information.. going to update
[Google Pixel 7 Pro] oko17:
Shall still safetynet-fix-v2.3.1-MOD_2.0 be used or is there something newer?

Sorry, I've been out of rooting for few months
[Google Pixel 7 Pro] roirraW "edor" ehT:
In general, I would always use whichever of these two are the newest:

Displax Universal SafetyNet Fix Mod on XDA.

Official Universal SafetyNet Fix released by kdrag0n available at XDA.

At this moment, Displax' 2.4.0 Mod 1.2 is the newest.

You can also find this information at:
[Google Pixel 7 Pro] oko17:
Thank you, for your detailed answer! :)
[Google Pixel 7 Pro] roirraW "edor" ehT:
Great improvements in [Themes / Apps / Mods] Better Internet Tiles - Bring back Wi-Fi and mobile data toggles! (non-root) v3.0.0-beta!
[Google Pixel 7 Pro] Lakino:
Well that totally sucks man! Sorry to hear!

Glad to hear you had some backups. I hate having to reconfigure everything from scratch.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Thanks! It was definitely a doh moment for me, but yes, those backups are awesome! Especially for root apps, Magisk modules, and lsposed modules, and a few non-root as well.

At least, as I observed a few posts back, it did at least temporarily solve the issue with my one remote control app. I just have no idea why it started to have the issue it had before, so who knows if it'll pop back up as suddenly this time.

I still have to copy my hundreds of GB of FLAC music back over.
[Google Pixel 7 Pro] Lakino:
Thanks. Just updated with this. Appears to be working fine. 👍🍻
[Google Pixel 7 Pro] Lakino:
🤣🤣🤣 Enjoy! 😁
[Google Pixel 7 Pro] roirraW "edor" ehT:
The platform-tools at https://dl.google.com/android/repository/platform-tools-latest-windows.zip still comes out as v34.0.1, but the zip file is dated today (May 10, 2023) and the file size of the zip is 5.79 MB instead of 5.84 MB as the zip was for 34.0.1 previously.

The SHA-256 hash of the fastboot.exe in each are different, too, so something has been definitely changed.

Now the question: Who is brave enough to test?
[Google Pixel 7 Pro] Lughnasadh:
Ah, I was wondering. I saw this a few days ago but didn't post anything about it because it had the same version number. Luckily I don't have anything to flash at the moment to test 😅
[Google Pixel 7 Pro] roirraW "edor" ehT:
LOL! If no one tests on purpose, I'm sure someone will test by accident eventually, although we might only hear about it if things are still broken. It'll be fun clarifying if users are using the new 34.0.1 or the old one.
[Google Pixel 7 Pro] roirraW "edor" ehT:
They changed the time stamp of the zip again, but it's the same file as earlier today.
[Google Pixel 7 Pro] Homeboy76:
What is the new time stamp and what are you using to see it?
[Google Pixel 7 Pro] roirraW "edor" ehT:
I use Aignes Website-Watcher (on my Windows computer) to monitor (among a great many other things) the link https://dl.google.com/android/repository/platform-tools-latest-windows.zip, which always auto-resolves into the zip file with the version number in the filename (right now, platform-tools_r34.0.1-windows.zip).

Because Website-Watcher recognizes that the URL leads to a file (as opposed to a webpage), it notes the date/timestamp of the file.

This is it right now:

As you can see, I have Website-Watcher set to 1) highlight in yellow anything that's changed (19:30:00, which is 7:30 PM), 2) show which item is the "last" change on the page (*END*), and 3) also shows what item(s) used to be there which aren't now (Removed Elements).

The copy of the file from earlier today showed:
[Google Pixel 7 Pro] simplepinoi177:
Do you mind sharing how you back up modules???

Here I was, naively thinking my Swift Backup and SMS Backup & Restore was enough to cover most everything!

It might actually also be a nice addition to the guide/OP.......
[Google Pixel 7 Pro] Fishawy:
+1, very curious to know that too.
[Google Pixel 7 Pro] veitograf:
hey guys i am trying to ota update my pixel 7 and followed these instructions:

How to install OTA updates and keep root on your Google Pixel phone

Looking for a way to keep root access after OTA updates on your Google Pixel phone? Here's a step-by-step guide on how to do so.

www.xda-developers.com

but when i try to flash init_boot.img i always get the error message:

C:\adb>fastboot flash init_boot init_boot.img

target reported max download size of 261095424 bytes

sending 'init_boot' (8192 KB)...

OKAY [ 0.059s]

writing 'init_boot'...

FAILED (remote: partition (init_boot) not found)

finished. total time: 0.106s

i am in fastboot mode and "fastboot devices" shows my device. what am i doing wrong?

EDIT: i updated my adb/platform tools and now its working :)
[Google Pixel 7 Pro] roirraW "edor" ehT:
Swift Backup backs up both apps and data associated with the two LSposed modules I'm currently using. That's all I mean. :)

Out of curiosity, do you know what version of Platform Tools you were on, and what you updated to? Thanks!
[Google Pixel 7 Pro] Fishawy:
Huh, interesting! I'm already using Swift Backup to backup apps & data, is there a certain setting that I might have possibly missed?
[Google Pixel 7 Pro] roirraW "edor" ehT:
They show up with all the rest of the apps Swift Backup handles for me. I don't think there was any related setting.

I'm only using AOSP Mods and Classic Power Menu right now, as far as LSposed modules.
[Google Pixel 7 Pro] Fishawy:
Even more interesting!

AOSP Mods is a system app, and Swift Backup defaults to user apps. That's why I never thought about backing up something like Google Wallet for example as it's baked into Pixel ROMs.

Are you able to schedule a daily/weekly backup for both user and system apps?

Apologies if I hijacked the thread.
[Google Pixel 7 Pro] roirraW "edor" ehT:
No apologies necessary.

Since I configured Swift Backup maybe a year and a half ago, I do all my backups to the cloud, and it restores all settings from the cloud, I forgot about any settings I might have tweaked.

I checked now.

In Swift Backup, switch to the Account tab at the bottom-right. Choose Settings / App backups / toggle Show system apps. I also toggle "Archive old version of an app backup". I think I changed some other settings/toggles from their default, too.

I have two schedules set to run at 1AM if my battery level is at least 40%. I don't charge the battery overnight (and further off-topic, I start charging when it gets down to 25%, and stop charging at 75% - I use ACC and ACC settings to automatically stop charging at 75%, and I use GSam to alert me with different tones when it gets down to 25% and when it's charged to 75%).

My Swift Backup schedules are overkill, but it's better to have too much backed up, rather than not enough.

The first schedule backs up pending and updated apps - both System and User, and I chose every single "App parts".

The second schedule backs up all the apps I've Favorited - i.e. whether they've been updated or not. That way I know I have my most recent settings/app data backed up.

Spoiler content hidden.
[Google Pixel 7 Pro] Fishawy:
You're awesome. Thank you!
[Google Pixel 7 Pro] roirraW "edor" ehT:
Glad to help, you're welcome!
[Google Pixel 7 Pro] veitograf:
I'm sorry I dont know exactly. The new one is 34 and the older version could have been 31.
[Google Pixel 7 Pro] roirraW "edor" ehT:
That's okay. That's probably confirmation that the new 34.01 works fine. I wish they would change the version number, since the 34.01 that came out two months ago was broken. I can't imagine why they wouldn't at least make the new one 34.02, or better yet, 35.0.

Thanks for the information!
[Google Pixel 7 Pro] Lughnasadh:
"Why on Earth" wouldn't they do this? 😉🙃
[Google Pixel 7 Pro] roirraW "edor" ehT:
LOL! I guess the same reason they never took the broken builds down, and why the site still has a changelog mentioning 34.0.0 RC2. Whatever the reason for those are. :)
[Google Pixel 7 Pro] JakeDHS07:
So wait is confirmed that the new build is working? I would love to go back to not having to tell noobs to no longer use latest platform tools. It just feels wrong
[Google Pixel 7 Pro] Lughnasadh:
I'm confident they will give you a detailed explanation in comment #29 😅
[Google Pixel 7 Pro] roirraW "edor" ehT:
With both @badabing2003's and @veitograf's comments, I feel fairly safe. That said, I don't plan on upgrading my Platform-Tools until I absolutely have to (until 33.0.3 no longer works for the monthly firmware update). :D But I could change my mind.
[Google Pixel 7 Pro] Ghisy:
Same here. It's a safe bet for now!
[Google Pixel 7 Pro] Lughnasadh:
Seems like some are still having problems with 34.0.1...

"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 "

https://xdaforums.com/t/guide-root-...der-pass-safetynet-more.4505353/post-88530127
[Google Pixel 7 Pro] roirraW "edor" ehT:
Thanks much, @Lughnasadh and @Homeboy76! CC: @badabing2003 and @veitograf, in case you weren't already aware, or in case you would miss this information anywhere.
[Google Pixel 7 Pro] badabing2003:
Thanks for keeping me in the loop.

What a screw up by Google. This is very sloppy and honestly quite worrisome.

Not only they make changes which doesn't fix the issues, they don't change the version numbers. And just change the binaries without even giving notice.

I just finished adding logic to whitelist the checksums of the latest binaries because I can't just blacklist based on version numbers, now I have to undo all that.

I worry about people blindly using the latest just because it is the latest.
[Google Pixel 7 Pro] roirraW "edor" ehT:
You're welcome! Yes, it's very frustrating and perplexing, to say the least.
[Google Pixel 7 Pro] vurtomatic:
Maybe all the layoffs affected this ... :rolleyes:
[Google Pixel 7 Pro] roirraW "edor" ehT:
UPDATE: Regarding overheating and battery drainage on android devices (fixed) - Google Pixel Community
[Google Pixel 7 Pro] Lughnasadh:
Looks like Platform Tools 34.0.3 may be on the way soon...

platform-tools-34.0.3 - platform/frameworks/base - Git at Google
[Google Pixel 7 Pro] roirraW "edor" ehT:
Spoiler content hidden.

:D

All, ignore my post (now deleted) about a new Verizon build. Confused this thread with my P6P thread again. DOH!
[Google Pixel 7 Pro] LLStarks:
Is there a git log for that branch? Curious to see if anything was fixed so we don't have to go in blind.
[Google Pixel 7 Pro] Displax:
Comparison of old and new 34.0.1 (utilities version changes)

Old:

ADB: 1.0.41 (34.0.1-9680074)

Fastboot: 34.0.1-9680074

Make_f2fs (casefold): 1.15.0 (2022-05-20)

Mke2fs: 1.46.6 (1-Feb-2023)

New:

ADB: 1.0.41 (34.0.1-9979309)

Fastboot: 34.0.1-9979309

Make_f2fs (casefold): 1.16.0 (2023-04-11)

Mke2fs: 1.46.6 (1-Feb-2023)
[Google Pixel 7 Pro] JakeDHS07:
Hopefully a release that actually works
[Google Pixel 7 Pro] roirraW "edor" ehT:
Google will soon let Pixel phones double as dashcams

Rather than needing to buy a (sometimes pricey) dedicated gadget, you should soon be able to use your Pixel (and...

9to5google.com
[Google Pixel 7 Pro] amders:
anyone here with may patch, the wireless charging got problem?

mine p7pro put on the pixel dock overnight only charging on first few minutes.. and in the morning nothing charge
[Google Pixel 7 Pro] roirraW "edor" ehT:
Wow, when using

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.

www.android.com

I get much faster transfer speeds between my desktop and my Pixel 7 Pro (up to 60 MB/s) than between my desktop and my Samsung Galaxy Tab S8 Ultra (up to 100 KB/s). I wonder what's up with that.

And I'm sending an 8.5 GB file, so it makes a huge difference.

Edit 1: Going back from my P7P to my desktop, I get up to 70 MB/s. I might have to test back from the tablet as well.

Edit 2: When looking at GSMArena https://www.gsmarena.com/compare.php3?idPhone1=11908&idPhone2=11274#diff- , I do see that the P7P's Wi-Fi is tri-band whereas the tablet's is dual-band.

Edit 3: Updated the tablet's firmware to the one that was just made available, and now Nearby Share is working at up to 75 MB/s or so.
[Google Pixel 7 Pro] madmuthertrucker:
I'm curious how do you get back to the bootloader or get the phone to boot up once you get to this stage of a failed install? I don't want to panic and brick my phone.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Can you give it the command:

fastboot reboot bootloader

?

If so, then do that and start from scratch (using Platform-Tools v33.0.3 instead).
[Google Pixel 7 Pro] madmuthertrucker:
I didn't do it. I'm still using 33.0.3 but I'm assuming that @Lughnasadh did. I'm curious how he got out of it. Just in case I find myself in that situation. It's good info. I like your idea.
[Google Pixel 7 Pro] roirraW "edor" ehT:
My memory may be rusty, since it's been between a month and a half and three months when I had the issue, but I believe the way I said is how I got out of it.

(I think the bad 34.0.0 came out in February, or very early March, so I possibly first experienced the issue with March's firmware update. Then 34.0.1 came out in March, and it was still bad, and then more recently a revamped 34.0.1 came out, and it's still bad, although initially it looked like it was better than the previous releases.)
[Google Pixel 7 Pro] Lughnasadh:
I never used 34+ so I never had to deal with the problems it came with. @roirraW "edor" ehT has some good advice above.
[Google Pixel 7 Pro] roirraW "edor" ehT:
As @Lughnasadh said it likely would, Platform-Tools v34.0.3 is out. Test at your own risk.

https://dl.google.com/android/repository/platform-tools-latest-windows.zip

https://dl.google.com/android/repository/platform-tools_r34.0.3-windows.zip

(both links resolve to the same zip)

Nothing in the release notes about it yet.

Edit: The adb.exe and fastboot.exe do indeed have different hashes than the most recent 34.0.1.
[Google Pixel 7 Pro] Lughnasadh:
For what it's worth, Mishaal Rahman said he tested it and the problem has been fixed.
[Google Pixel 7 Pro] badabing2003:
This is scandalous for Google.

Didn't work on redfin

fastboot: error: ANDROID_PRODUCT_OUT not set
[Google Pixel 7 Pro] Lughnasadh:
Does this help if on Windows?
[Google Pixel 7 Pro] badabing2003:
Yes it does, and it does without having to reboot to fastbootd.

In the previous versions, you would just specify full path to fastboot, and it would set automatically the directory to be ANDROID_PRODUCT_OUT, now we have to explicitly set an environment. :(
[Google Pixel 7 Pro] roirraW "edor" ehT:
What in the Holy Hand Grenade of Antioch? So I wonder if we can expect a second 34.0.3, or a 34.0.3 R2, or if this is intended behavior / "good enough" for Google for now.

And thanks!
[Google Pixel 7 Pro] badabing2003:
It works good if the environment variable is set.

I made adjustments in PF to set it as I'm not too optimistic for Google fixing it any time soon.
[Google Pixel 7 Pro] xunholyx:
"Holy Hand Grenade of Antioch"? Classic statement that most here will not get at all. That's hilarious and an awesome reference! I should quote from that more often. Lots of cases where MP quotes would be appropriate.

Your phone isn't dead, it's just resting. Probably pining for the fjords

​
[Google Pixel 7 Pro] Lughnasadh:
You're welcome! I have no idea if this is a feature or a bug, and I'm guessing Google doesn't either 🤣
[Google Pixel 7 Pro] badabing2003:
I can't perceive how it would be a feature, it has a dependency on AdbWinApi.dll, it used to be able to find it in the same directory as fastboot / adb, now it can't unless the environment is set.

I haven't tested running from the directory where fastboot is, perhaps that still works, but specifying full path no longer does without setting environment variable.

On the other hand being able to mount and interact with logical partitions without needing to get into userspace fastboot is definitely a feature, a nice one that would help for Mac M1 systems as often they have issues getting into userspace fastboot.
[Google Pixel 7 Pro] LLStarks:
File a bug on the issue tracker.
[Google Pixel 7 Pro] badabing2003:
Feel free to report if you are so inclined, I'm not going to bother, don't have faith that they'd pay attention to it, based on the history of the mess we've seen with 34.x

How do they even release without proper testing, 34.0.0 and 34.0.1 has bricked many phones and it wasn't pulled off.
[Google Pixel 7 Pro] Gordietm:
Can you please explain where you put this command line. I'm not exactly sure how to add it.
[Google Pixel 7 Pro] badabing2003:
I assume you want to use this now because you're on Mac and have fastbootd issues?

Otherwise stick to 33.0.3, I've integrated it into next version of PF so that you don't have to do it.

If you absolutely need to do it before PF is released, which could be today or at latest by the weekend, then you need to define a System or User environment variable, the key being ANDROID_PRODUCT_OUT, and the value being where platform tools is.

For example on Mac you would add

export ANDROID_PRODUCT_OUT=<path_to_sdk> in your shell profile.
[Google Pixel 7 Pro] Gordietm:
Thanks, I'm on Windows and I'll stay with 33.0.3 until it's fixed