yashsingh1/xdaforums huggingface dataset:
[Google Pixel 7 Pro] Sui77:
Damn, flashed beta 15 two days ago :/

Would it make sense to flash a4 QPR stable and can I do it without wipe?
[Google Pixel 7 Pro] Ghisy:
I could be wrong but I think you need to wipe to downgrade. May not be worth it. YMMV.
[Google Pixel 7 Pro] fijasko:
to hijack a thread for a bit, there's a powerfull FREE open source app https://github.com/MuntashirAkon/AppManager that can list and block trackers and do much, much more.

it's really useful and working great.
[Google Pixel 7 Pro] re_endymion:
Hi Fishawy, what is the name of the application taken in screenshot ?
[Google Pixel 7 Pro] Fishawy:
Hey there, here you go.

GitHub - MuntashirAkon/AppManager: A full-featured package manager and viewer for Android

A full-featured package manager and viewer for Android - MuntashirAkon/AppManager

github.com
[Google Pixel 7 Pro] hxxmor:
My pixel lags after rebooting, what should I do to fix it?

Sent from Pixel 7 using ReLabs
[Google Pixel 7 Pro] re_endymion:
Thank you very much Fishawy
[Google Pixel 7 Pro] roirraW "edor" ehT:
Thanks everyone for sharing the information about Nova and AppManager. I'm still sticking with 7.0.58 myself, since the companion app doesn't work well with Nova 8 Stable yet, but it's good to get information.

I'm 100% sure that any kind of downgrade would require a wipe. Android 14 would not be able to handle Android 15 Beta's system app data.
[Google Pixel 7 Pro] UberNorse:
So if I'm understanding correctly then you load the OTA, and without doing anything special just process the image by selecting Apatch and it does its thing on init_boot.img only?

I'm just making sure there are no options where I need to have it patch boot.img in tandem or if just allowing Apatch and Pixelflasher to do their thing with no extra options needed?

Sorry for needing the clarity, I just don't want a paper weight phone. Thanks
[Google Pixel 7 Pro] otonieru:
Checking my firewall logs,

Nova doesn't even make that much of data request. It only make 28 connection request during last 90 days, and not even one request associated with any known trackers from adguard databases. It uses 3KB of data during these period,

now compare that to something like reddit that make 224 trackers request during same period, or 124 from spotify,

i'd say, we might actually put too much negativity on nova. Lol
[Google Pixel 7 Pro] Locoman_:
I've been using Nova 95% of the time since fire was invented. But getting comparative to other apps tracking doesn't make sense to me, it's like "This one sucks twice as much as that one. So that one is cool." ???

*Shameless plug for Discrete Launcher: <5mb of storage. No permission to grant. No phone home. Your battery and privacy will thank you.

I still love Nova, just feel a bit jilted. ;-)
[Google Pixel 7 Pro] Sib64:
Hey gents,

Some time ago I read that Platform-tools version 35.0.0 had a few problems and that it was preferable to play with version 33.0.0.

I've just seen that 35.0.1 has been released.

What advice do you have?

Stay with 33.0.0

Update to 35.0.0

or upgrade to 35.0.1

But I just don't feel it 🤨
[Google Pixel 7 Pro] otonieru:
now that you mentioned it, it make me remember that i still on 33 as well,

and so far, nothing make me feel the need to go 35 as well, lol
[Google Pixel 7 Pro] weriwd:
Bad news... Call dropping continues with the latest radio firmware. :( I flashed the radio from the October update. Let's see how it goes.
[Google Pixel 7 Pro] roirraW "edor" ehT:
I've been using 35.01 since it came out in March without any issue.
[Google Pixel 7 Pro] Ghisy:
Same here, I can vouch for 35.0.1.
[Google Pixel 7 Pro] JakeDHS07:
Can thrice. No issues with most recent Platform Tools since release
[Google Pixel 7 Pro] Sib64:
Ok, thanks for your answers.

Update to 35.0.1 done (y)
[Google Pixel 7 Pro] justDave:
As long this thread is about launchers...

It looks like Lawnchair has awoken from the dead. Development has been on again/off again for years but it's FOSS, available from F-Droid (sometimes) and hasn't given me trouble over the years.
[Google Pixel 7 Pro] Ghisy:
Same here. Although, since they've been acquired by Branch, I feel like support through Discord has been lacking.

Like I have a Nova gesture bug since the 8.1.0 release but because it's about the recents screen, they dismissed it as "it's an OS problem" and just closed my request. It started with their latest version so obviously, the bug comes from Nova. It's a little annoying.

Sorry for the OT.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Very nice! If I didn't like my widgets and Nova capabilities so much, I'd give it a try.

Awesome! It's good to have competition.

Sorry to hear that. I hope somehow they come around for you.
[Google Pixel 7 Pro] Locoman_:
Widget loss is my biggest gripe, I get that.
[Google Pixel 7 Pro] badabing2003:
I don't know about that.

My Firewall is flooded with Nova call attempts to 45.56.71.66l (i921-66.members.linode.com)
[Google Pixel 7 Pro] otonieru:
did you by chance enable 'Usage & Error Reporting' in Nova Setting ? Because i turned it off, since like, forever... lol
[Google Pixel 7 Pro] badabing2003:
Nope,

It's off.
[Google Pixel 7 Pro] roirraW "edor" ehT:
I didn't realize the AT&T versions of Pixels couldn't be bootloader unlocked once it's paid for. I presumed once it's paid for that it was carrier unlocked and that OEM unlocking would be ungrayed. It's hard for me to keep track - I know that's the case for T-Mobile.

Interesting. In my opinion, they should also just go ahead and start making 2.5Gb ports the base standard, as well. My first self-built desktop with gigabit Ethernet was from 13 years ago! Time to retire the standard. I know gigabit is still more than what the average user needs, but typically home networking uses faster speeds than ISPs, and gigabit internet is getting more and more common, although I mostly upgraded because it'll save me money over what my cable internet cost me.
[Google Pixel 7 Pro] rester555:
Yes, in my humble opinion they should make the base a x10 jump like they did from the 1990s to 2010... Go from 10 Mbps, to 100 Mbps, to 1gbE, to 10 gbE
[Google Pixel 7 Pro] Superguy:
No, they're bootloader unlockable once they're SIM unlocked. You have to request the unlock code though - it's not automatic.

T-MO's the only one I know of that does the weird server side unlock.
[Google Pixel 7 Pro] roirraW "edor" ehT:
I see, thanks for clarifying. About the only thing else I can say about it, then, is that talking about illegal ways to bypass the carrier's legal restrictions isn't allowed on XDA. :) But I understand where you're coming from.
[Google Pixel 7 Pro] roirraW "edor" ehT:
I wanted to say that too, but I held myself back since I figured that would be a pipe dream. :D
[Google Pixel 7 Pro] Superguy:
None of the ways are illegal. You either get the carrier to give you the code or find a service that will.

I would find methods used to root more questionable than a SIM unlock.
[Google Pixel 7 Pro] Superguy:
Heh, more likely to see 2.5 Gb become more common first, though it's still expensive and not really catching on yet.
[Google Pixel 7 Pro] NepoRood:
It's usually pretty easy to talk a T-Mobile rep into sim unlocking a device, as most of them really don't care one way or another. That's been my experience anyway, along with a few other people I know. Basically, just get on Twitter and ask, lol

Took me 3 tries with OnePlus 7 Pro, though...
[Google Pixel 7 Pro] roirraW "edor" ehT:
Hello @NepoRood! Always good to "meet" another RC and moderator who I wasn't familiar with.

I was much less active between 2017 and late 2021, though.
[Google Pixel 7 Pro] NepoRood:
Right on, no way I could keep up with the comings and goings of "The Staff". However, I have noticed a few of the guys members that were "Rookies" with me have moved on up to the East side these days.

I'm looking forward to the Pixel 7/Pro, the last device I actually purchased with my own money and did a bring-up on was the Pixel 3 XL, and that's been a while, lol
[Google Pixel 7 Pro] buddyj:
This is the first phone I'm getting at launch. How quickly has root typically become available in the past?

My plan right now is to unlock the bootloader immediately and root later once it's available.

But I'm worried about not being able to use banking apps etc. while the bootloader is unlocked and I have no way to hide it. Any advice/experience?
[Google Pixel 7 Pro] madmuthertrucker:
It should be rootable as soon as it shows up. The root method does not usually change that much. I see some of the developers on here already. They are some smart guys. I'm pretty confident you will have a root method on here quick.
[Google Pixel 7 Pro] roirraW "edor" ehT:
As @madmuthertrucker said, I expect it to be rootable immediately just as soon as we get our hands on it. Android 12 came out 24 days before the Pixel 6/Pro was received by the earliest pre-order customers, so the changes that were necessary for Magisk to work with Android 12 were either still in alpha or beta, or were just about to be alpha or beta.

Android 13 came out two months ago, so I think it's likely there won't have to be any changes to work on the Pixel 7 Pro. Only trying will tell, though. :D
[Google Pixel 7 Pro] NippleSauce:
This is why I always buy the faculty unlocked versions of the phones. I can unlock the bootloader immediately without any restrictions - even if the device hasn't been fully paid off yet.

As far as root goes, I agree with the others in this thread that we will have root immediately once we get our hands on the devices. Nothing questionable =)
[Google Pixel 7 Pro] wildlime:
When do we think OTA or factory images will be live? I have both the 7 and 7 pro. The 7 got the 0 day update already with all the new camera features but my pro hasn't updated yet!
[Google Pixel 7 Pro] roirraW "edor" ehT:
Will probably be made available on October 13th, the official release day.
[Google Pixel 7 Pro] Ghisy:
I guess we're gonna have to disable verity and verification again to be able to use custom kernels without any problem. Or am I the only one who did that on the P6P?
[Google Pixel 7 Pro] roirraW "edor" ehT:
You're not the only one, but I didn't disable Verity or Verification on my Pixel 6 Pro after last December or so, and I used a custom kernel every month. I don't remember what they did that made them able to be used without disabling Verity or Verification.
[Google Pixel 7 Pro] wildlime:
Ok thanks
[Google Pixel 7 Pro] roirraW "edor" ehT:
Added Thanks to 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:

@Az Biker

@direwolf1

@Displax

@Eleo

@foobar66

@Freak07

@kdrag0n

@LLStarks

@Lughnasadh

@rovo89

@siavash79

@StrangerWeather

@tbalden

@topjohnwu

@TotallyAnxious

@Tulsadiver

@Typhus_

@V0latyle

And many others from all of the previous years who I thanked in my previous OPs.

Also organized the heck out of the OP and reserved posts. I wanted to do this with my Pixel 6 Pro OP which became so much of a mess, and when I looked at the underlying BB-Code, it was even more of a mess than it seemed on the surface.
[Google Pixel 7 Pro] badabing2003:
not full OTA, full firmware.

Then you would modify flash-all.bat as follows.

Assuming that you created a patched init_boot.img and named it patched_init_boot.img

Then your flash-all.bat file would look like this.

PixelFlasher does this for you automatically, including the patching the file, but I strongly encourage everyone to understand how the patching is working, because only then when anything goes wrong, you'd be able to get yourself out of trouble, or provide pertinent details when asking for help.
[Google Pixel 7 Pro] Larakali:
I swear we need some sort of Discord Channel or smth for this all...

Its way to cluttery here
[Google Pixel 7 Pro] Annie the Eagle:
Thanks!!
[Google Pixel 7 Pro] roirraW "edor" ehT:
Yes, absolutely.

Glad you got it solved one way or another. Your Platform Tools (ADB /Fastboot) were completely up to date? I know you said you used the flash-all and that worked fine, so I'm guessing yes. Hopefully, next month goes smoother for you.

Great idea, thank you. I might just say "Limited SafetyNet" since there have been mixed reports of users still able to download the apps they should only be able to if they pass it, along with others who couldn't download them, and same with GPay/Wallet, if memory serves. I'll also "unspoiler" the main SafetyNet instructions and just the caveat at the beginning of what will and won't pass.

Thanks for the extensive testing and detailed analysis.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Added to Post #2, thanks again!
[Google Pixel 7 Pro] roirraW "edor" ehT:
Personally, I think it's easier for me to read every single post, and keep track of where I left off on here. :) I know there is a lot of interesting information in many user's posts, but for anything important and/or relevant to the topic of the thread, I add them to the OPs.
[Google Pixel 7 Pro] roirraW "edor" ehT:
My wife and I like ours so far. I'm experimenting with using the face unlock. It's definitely pretty quick. My wife and I both independently think the phone feels lighter, even though it's technically slightly heavier (2 grams, I believe). Makes sense with the weight redistribution, but it's funny that I thought it when I first held my phone, and she later thought it too and mentioned it, but it could also be how long-time couples start to become more and more alike.

I had a problem with a work 2FA app showing a black square when accessing the camera in order to scan a QR code, but another reboot of the phone did the trick.
[Google Pixel 7 Pro] 96carboard:
Actually, you might try with something like "fastboot boot boot.img init_boot.img"

Edit: After I read through the rest of the thread, I saw that someone tried this and it didn't work.
[Google Pixel 7 Pro] badabing2003:
Thanks for the info,

I don't have P7 or P7P, I'll wait for report from people who have it.

I gather boot.img os stock and init_boot.img is patched in this case.
[Google Pixel 7 Pro] 96carboard:
No, boot.img is the kernel and init_boot.img is the ramdisk. Thats the whole point -- they're split now.
[Google Pixel 7 Pro] WorldOfJohnboy:
Anyone else rooted, Build TD1A.220804.031 (Ver 13 Oct 5th) and have Camera force closing? I backed out the Camera app to previous version and it works fine now, but just curious if it's only me.
[Google Pixel 7 Pro] badabing2003:
yes yes, but in terms of files to pass

boot.img is the stock boot.img from the zip

init_boot.img is the patched init_boot.img

right?
[Google Pixel 7 Pro] 96carboard:
Sorry, yes. I misread your previous.
[Google Pixel 7 Pro] Annie the Eagle:
No issues here, try clearing the cache/data of the camera. I just took a 1 minute test 4K60 video + a few pics
[Google Pixel 7 Pro] roirraW "edor" ehT:
No issues here, yet, either. Also try reboot?
[Google Pixel 7 Pro] Ghisy:
Come on custom kernels!! (hopefully Kirisakura, among others)
[Google Pixel 7 Pro] swieder711:
I emailed the developer of Swiftbackup. He is looking into the problem.
[Google Pixel 7 Pro] daridima2:
Hi,

I have tried all the guide on my new pixel 7 pro, and everything works, except the safetynet integrity checks, which give me the errors I show you from the screenshots.

I think we need a more up-to-date magisk module
[Google Pixel 7 Pro] roirraW "edor" ehT:
Unfortunately, no luck, either with the Magisk'd or stock init_boot.img:

Whoops, disregard me too. :D Didn't see your edited post and I couldn't remember if this was the exact thing that was tried. Oh well.
[Google Pixel 7 Pro] Asma12:
Exactly, but I used the factory image instead of the OTA, I don't know if it makes any difference. Then I pressed the patch button and flash button, nothing else.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Google patches exploited Android zero-day on Pixel devices

Google has released patches for 50 security vulnerabilities impacting its Pixel devices and warned that one of them had already been exploited in targeted attacks as a zero-day.

www.bleepingcomputer.com

"It's fixed on Pixels with the June update (Android 14 QPR3) and will be fixed on other Android devices when they eventually update to Android 15. If they don't update to Android 15, they probably won't get the fix, since it has not been backported. Not all patches are backported."
[Google Pixel 7 Pro] hxxmor:
can someone help me?

Sent from Pixel 7 using ReLabs
[Google Pixel 7 Pro] schmeggy929:
Going to need a lot more information if you want someone to help you. When does it happen? using apps, newsfeed scrolling. playing games. navigating through menus, what? No one can help with it just lags.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Are you using a custom kernel on the June firmware? Has the custom kernel been updated to be able to be used properly with the June firmware? If you are using a custom kernel, have you tried switching to the stock kernel?
[Google Pixel 7 Pro] daduy:
Try using the fingerprint scanner (ie for unlocking the phone, opening secure app, etc) and see if that fixes it (temporarily)
[Google Pixel 7 Pro] Sib64:
I tested badabing2003's Pixel Flasher for the first time to install this new version, and I must admit I was a bit nervous [even though I trusted his tool - but it was mainly me who was afraid of missing something in the process - very well explained].

​

Once everything was ready, the ini_boot.img patched, the two slots, etc... I pressed the "Flash Pixel Phone" button.

​

I waited patiently, I admit anxiously, for the final moment and to check that everything was OK. And everything was. Thanks again @badabing2003

​
[Google Pixel 7 Pro] sawdoctor:
Best way to fix it ( you won't like it i know) is a full wipe then set up fresh
[Google Pixel 7 Pro] hxxmor:
When i reboot my phone, for like 5-6 minutes there's lag and some ui breaking in the qs panel
[Google Pixel 7 Pro] hxxmor:
I updated to the june firmware and also flashed a custom kernel, the kirisakura one (also i flashed the one meant for june's firmware)
[Google Pixel 7 Pro] roirraW "edor" ehT:
You can quote more than one post in a single reply. :) You can use the +Quote button, and then in your new post click "Insert quotes".

Has Kirisakura been updated for June, or did you flash May's kernel? No matter what the answer, unless/until you flash the stock kernel back (follow the instructions in the Kirisakura thread to do so), then you haven't ruled out that it's the kernel causing the issue. I'm not saying that it's the kernel, just that it's a possibility. Has anyone else in the Kirisakura thread mentioned lag? Even if not, that doesn't mean that it's not what's causing the lag on your phone.

Another possibility is that the lag is caused by some setting you've set to use with the custom kernel.
[Google Pixel 7 Pro] hxxmor:
I even experienced lag without the custom kernel flashed, I mean I'll still gonna give it a try

Sent from Pixel 7 using ReLabs
[Google Pixel 7 Pro] roirraW "edor" ehT:
Okay, it was worth checking. If you got lag when you were on the stock kernel to begin with, then there's probably no sense trying it again. I really can't advise anything further. Even though the Pixel 8 Pro is what I'm primarily using, I've had reasons to use my Pixel 7 Pro quite a lot this past week, and I haven't experienced any lag with the firmware stock, except for being rooted with Magisk Stable 27.0 (27000).
[Google Pixel 7 Pro] hxxmor:
Yeah, I'm experiencing lag while rooted

Sent from Pixel 7 using ReLabs
[Google Pixel 7 Pro] hxxmor:
Can someone share some Magisk Modules or ways to improve battery life on Pixels? Specifically a Pixel 7
[Google Pixel 7 Pro] Schroeder09:
It's been A while. I'm on the February update. Last time I updated to that version I had a lot of troubles. I got stuck in a boot loop. Pixel flasher saved me. It was the first time I had used it. I don't remember the details, but since I had the integrity or whatever set to off since that was an original requirement for the kiri kernel I was able to get my phone going.

Has anything changed with the methodology of dirty flashing since February? What platform tools should I be using?
[Google Pixel 7 Pro] roirraW "edor" ehT:
Nothing has changed. Many of us have been using the latest Platform Tools v35.01 directly from Google since it came out in March without issue.

The only potential change is whatever your custom kernel's particular directions/requirements are, if those have been changed.
[Google Pixel 7 Pro] otonieru:
Kirisakura is the only thing i need to improve battery life of my P7P.

i kinda feel your lag problem is due to some modules you used. Or you might forget deleting the old powerhint modules from older kirisakura (which no longer needed)
[Google Pixel 7 Pro] darkness4every1:
Isn't that normal? Some apps and modules like Repainter or Blendr will cause ui resets after boot.

Does it lag after?
[Google Pixel 7 Pro] hxxmor:
I've already flashed Kirisakura, the leap in battery life is not noticeable so far. Btw you're talking about the AK3 Helper Module?

Sent from Pixel 7 using ReLabs
[Google Pixel 7 Pro] hxxmor:
It doesn't lag after, also yes I have Blendr

Sent from Pixel 7 using ReLabs
[Google Pixel 7 Pro] UberNorse:
I'm a bit ambivalent as to which thread to post this but I decided here was best.

So, I have re-flashed the Full-OTA June update cheetah-ota-ap2a.240605.024-feba1b34. I uninstalled Magisk meaning I was un-rooted with a fresh flash.

I then used Pixel Flasher and re-flashed Full-OTA of June and used Apatch as root method and all went well.

Currently I can also confirm, with absolutely no modules installed simply rooted with Apatch, RCS is working. There are only a few modules I currently would like to install and use with Apatch and hopefully they don't break RCS.

I plan on using

Axet's Call Recorder

Youtube Revanced

YT Music Revanced

Pixel Audio Decompressor

Viper 4 Android

Hopefully, I can get these installed and working without breaking RCS, no need for PIF at this time since I don't care about Wallet working from my phone, I only value RCS working currently. Planning on installing one module at a time and seeing if RCS continues to work or it breaks. Will update on my findings whenever I'm finished later tonight or tomorrow.

UPDATE # 1 - So far I have installed four modules with Apatch and as of now RCS is still working. I need to add that I have all my banking, streaming, or other root sensitive apps effectively hidden using Apatch's feature which is called 'Exclude Modifications' and those apps are working currently.

Update # 2 - Went through the same process with my wife's phone and installed the same modules as mine, she has a Pixel 7a, and her RCS was working but just broke. Will find out why and report back.

Update # 3 - So seemingly the modules I used broke RCS. I am working on a solution for that but no idea if I will prevail. I did however at least skirt the failure of YT and YT music by just installing micro-G and the revanced apk's. That hasn't broke RCS as of yet. As of yet though, seemingly this method does work albeit nullifies most of the point of root, at least module wise.

I will not install any more modules until tomorrow to see if these hold up or will eventually interrupt E2EE on RCS. As of now the modules I have successfully installed and working are -

1. Axet's Call Recorder

2. Youtube Revanced Extended

3. YT Music Revanced Extended

4. Viper 4 Android
[Google Pixel 7 Pro] roirraW "edor" ehT:
Chrome rolling out 'Listen to this page' TTS on Android

Chrome for Android has been working on text-to-speech (TTS) for a few months now, and Google is now rolling out "Listen to this page."

9to5google.com

Thanks @UberNorse for sharing your experiences with APatch so far. I'll definitely be curious to see where the near future takes us with this alternative.
[Google Pixel 7 Pro] darkness4every1:
Then that's completely normal, nothing to worry about.
[Google Pixel 7 Pro] weriwd:
Same thing with October update... then I flashed the radio from June 2023, but it's still the same... I don't know what to do at this point.