yashsingh1/xdaforums huggingface dataset:
[Google Pixel 7 Pro] Lughnasadh:
Since this didn't carry over...

Appears Google is doing away with its "1st Monday of the Month" release schedule...

"We also dug into how we can deliver the highest quality, best tested updates to Pixel users on a consistent basis. As part of this effort, our security updates, bug fixes and feature updates won’t roll out on a specific day each month. Instead, we’ll deploy updates as soon as they’ve completed the necessary tests to ensure they improve the experience for all Pixel customers."

7 years of software updates for the Pixel 8 series

Pixel 8 and Pixel 8 Pro will receive seven years of ongoing software support across Android OS, security and Feature Drops.

blog.google
[Google Pixel 7 Pro] roirraW "edor" ehT:
Yay! We're back. :) Thanks for the re-post, @Lughnasadh!
[Google Pixel 7 Pro] simplepinoi177:
I just replied not 20 minutes ago, but I didn't know the migration would finish so soon, so I'll also repost my reply to this....

I saw an article title (androidauthority.com, maybe) that titled Samsung "dethroned" as the king of Android updates. I didn't bother clicking or reading it, but this must be the reason and what it was about.....

I guess Pixels will be the new "king"...?
[Google Pixel 7 Pro] roirraW "edor" ehT:
Note: I ordered the Pixel 8 Pro for my wife and I.

Wouldn't it be awesome if we started seeing more competitiveness regarding the length of support/updates?
[Google Pixel 7 Pro] simplepinoi177:
Congrats roirraW "edor" ehT! I didn't know pre-orders were live already...

I think you mentioned you were coming from the Pixel 6 or 5....I think you'll be happy; the P7P has been great for me...

Hopefully the battery life and SOT (among other complaints or criticisms) is better!
[Google Pixel 7 Pro] Pixel86:
Clean flashed Android 14 and relocked my bootloader for the first time in 6+months. Why does the phone seem much smoother not rooted vs. rooted with stock & custom kernels I tested during all the Android 14 Beta builds? Does using Magisk come with a perfomance hit?
[Google Pixel 7 Pro] roirraW "edor" ehT:
Thanks! Yeah, pre-orders were live at least partway through yesterday's official announcement/event, but I was doing research and talking about it with my wife to see if she wanted a new phone, too, and whether she wanted the Watch 2 or Buds Pro.

I'm coming from the P7P. I wonder what the P7P's maximum brightness will do to the battery life? :D

After a factory reset, whether rooted or not, it always seems smoother at first.
[Google Pixel 7 Pro] simplepinoi177:
I imagine when the user has root access, it slows the device a bit because of all the more access you/apps have; even with custom kernels or whatever else. Also, custom kernels tweak cpu and temperature and other things, so it may increase processing power and/or battery life, but it isn't meant to beat a purely streamlined UI experience (especially one that isn't slowed down by user & apps accessing root processes/files).

This is just my take on it anyway....
[Google Pixel 7 Pro] JakeDHS07:
I hate that the migration broke the already glitchy app which badly needs an update. Now you can't log in anymore.
[Google Pixel 7 Pro] Navalon:
Hello friends! I have the last 13 android version, this first 14 version is possible to flash with Pixel flasher and maintain the root?
[Google Pixel 7 Pro] Paz9:
Updated to 14... how can I remove the annoying arrow when swiping back, it looks tacky and cheap
[Google Pixel 7 Pro] simplepinoi177:
Hey! Thanks for the bulletin/reminder! I didn't know pre-orders came out; had forgotten about the announcement event coming these days. I had to be sure to use my $200 Google Store credit (from the launch P7P) for pre-order within the next week (or it expires and i lose it) and was waiting for the pre-orders to go live! Make getting the Google Watch 2 from $389 (with California tax & preferred care) to $189 (paid in 12 installments = $15.75 per month).

Side note (sorry for going off-topic on a Pixel 7 rooting guide); I am so glad to see they are offering an insurance plan that covers damage. I kept reading on how the Pixel Watch's screen scratches and cracks so easily, and yet Google has made no infrastructure or system in place to get them replaced/repaired! I read in an article that Google support reps and/or repair shops basically just say "buy another one" because there is no replacement parts to stock & repair them!
[Google Pixel 7 Pro] simplepinoi177:
From what I read about 14 betas, apparently they've enhanced the back gesture -- so you can preview what you're going back to and/or preview multiple screens back and go directly to it. I never flashed a QPR, so I'm unaware if you can disable/limit this like you can from gestures to button-navigation....

Sorry I couldn't offer directions to remove it; just information....
[Google Pixel 7 Pro] JakeDHS07:
It doesn't look like they've given the option to disable it. If I had to guess, it'll probably be part of AOSP mods
[Google Pixel 7 Pro] xflowy:
does anyone know if zygisk lsposed and universal safety fix are working on a14? i need both moduls.. :/
[Google Pixel 7 Pro] K1nsey6:
Both working fine for me
[Google Pixel 7 Pro] Nekromantik:
i hope the AI features on 8 Pro comes to 7 Pro as I cant afford to upgrade this year with the lower trade in value
[Google Pixel 7 Pro] Sib64:
Like to me after the update.

All modules are functionnal without problem, unlocked, rooted, all is clear :cool:(y)
[Google Pixel 7 Pro] jhjhjhjhjhjh:
Im not impressed with these new features yet untill they become more globalized.

I tell everyone this, there is no such thing as an upgrade unless it's years down the line. We get "Updates" until something revolutionary is mainstream..

My next upgrade the pixel 11….
[Google Pixel 7 Pro] jhjhjhjhjhjh:
This update has been awesome.

Battery life standy battery drain has improved,

Apps actually open up faster.. Stable A14 out of the gate is very stable..Google way to go...

I can't find the battery cycle count anyone else?

Im not on telegram so if anyone knows if AOSP Mods work on stable A14 please post

Gracias...
[Google Pixel 7 Pro] Locoman_:
AOSP module is working on 14. I haven't retested all its functionality but as I had it set, it's working.
[Google Pixel 7 Pro] jhjhjhjhjhjh:
Life saver I had no idea it worked. I ran the qpr1 a14 and assumed it wouldn't work on stable...yessss I need aosp on stock... thanks again for the reply.. I hate the white bar navigation. Lol

Navigation bar defeated....:)
[Google Pixel 7 Pro] simplepinoi177:
Yeah just saw someone said "$550 in BestBuy vs $420 in Google Store"! WT🤬

I mean, for my P7P, I traded in my Pixel 5 for $400 (at Google Store)! seriously?!?!?!

I was told that because I was confused after spouting Google Store banner advertises $750 trade-ins; made me realize it's probably for the S23 Ultra or even the iPhone 15 Pro Max....rip-off....
[Google Pixel 7 Pro] justDave:
I think what you're talking about is "Predictive back animations" which can be flipped on/off in developer options.
[Google Pixel 7 Pro] dmarden:
A little assistant appreciated... happy to go read something if needed, just not sure where exactly the issue is.

Thank you in advance.

Still running the September Android 13 update on my P7P... have not installed today's Android 14 update yet.

I've been rooted since release, but never really cared about safetynet/etc. Decided I wanted to take care of that now.

I followed the steps in post 1, I will outline below in case I missed one.

On the lated Magisk Canary (256301)...

Hid the Magisk App and gave it some name I will remember

Tap'd Systemless Host and confirmed it was listed as a module

Enabled Zygisk

Enabled Enforce Denylist

Added the following to that list: Google Play Games, Google Play Protect Services, Google Play Store

Installed Universal SafetyNet Fix 2.4.0-MOD_2.0 from Displax's Github (linked from the XDA post)

Rebooted.

Installed the two apps and YASNAC has CTS profile match as fail (eval type is Hardware_Backed instead of BASIC), Play Integrity API Checker has X for Meets Device Integrity...

Did the normal routine of clearing data and rebooting a few times from things just to make sure.

Did I miss a step?

Thanks!!!

Edit: I was able to resolve my issue by also installing this: https://xdaforums.com/t/play-integrity-fix-safetynet-fix-addon.4607985/
[Google Pixel 7 Pro] simplepinoi177:
Universal SafetyNet Fix 2.4.0-MOD_2.0 works intermittently/inconsistently; hence the fails (which is what seems to be happening for us P7P at least). For us P7P users, it's best to use v. MOD_1.3
[Google Pixel 7 Pro] dmarden:
Oh, interesting... so I wonder if I should downgrade to 1.3... do I need that other module I installed at that point?
[Google Pixel 7 Pro] simplepinoi177:
If you mean v2.0 (module), I doubt you can run v1.3 & v2.0 concurrently...in any case, if you mean v2.0, yes, you do not need that....
[Google Pixel 7 Pro] Lughnasadh:
You can continue to use Chiteroman's mod as long as it is working. You can also use Displax's 1.3, but not both at the same time.
[Google Pixel 7 Pro] justDave:
Use either Displax 1.3 or Play Integrity Fix, not both.

Edit: ... as @Lughnasadh just said.
[Google Pixel 7 Pro] dmarden:
No, sorry for being confusing re: my edit while you were replying.

I found this "PLAY INTEGRITY FIX": https://xdaforums.com/t/play-integrity-fix-safetynet-fix-addon.4607985/

And in conjunction with Displax's 2.4.0-MOD_2.0, seems to be working?
[Google Pixel 7 Pro] dmarden:
This seems wrong, are you sure? The Play Integrity Fix thread seems to say that it is specifically an addon for Displax's module. Or you mean 1.3 specifically I guess? As in, if I downgrade, lose the extra module?
[Google Pixel 7 Pro] simplepinoi177:
Oh...I don't know Displax's filenames by heart...Universal SafetyNet Fix 2.4.0-MOD_2.0 looks like Displax's filename as I recall it (i'm probably mistaken)...I usually go off of the "MOD", the "2.0" or "1.3", and the USNF; I usually forget what version of USNF Displax bases off of (2.4.0)....

So I assumed @dmarden was speaking on Displax....my apologies
[Google Pixel 7 Pro] simplepinoi177:
Play Integrity Fix works well enough, but, again, Displax's 2.0 module has issues with the P7P particularly. That's why we still use 1.3; with success.

Play Integrity Fix is fine with or without; whatever ends up working for you...
[Google Pixel 7 Pro] Locoman_:
I hate it to
[Google Pixel 7 Pro] justDave:
I thought I was sure. Now I'm not.

FWIW, I'm still using Displax 1.3 without Play integrity fix. It worked fine on Android 13 and is still fine after upgrading to 14.
[Google Pixel 7 Pro] dmarden:
I appreciate the help @justDave and @simplepinoi177
[Google Pixel 7 Pro] simplepinoi177:
This ^ . Me too. That's why I can't speak to Play Integrity Fix module.

But we aren't getting "MEETS_STRONG_INTEGRITY" any longer like we did for a couple of weeks on v2.0 (like Play Integrity Fix seems to help other devices pass).... :(
[Google Pixel 7 Pro] Lughnasadh:
1.3 specifically. You should use one or the other.
[Google Pixel 7 Pro] dmarden:
I respectfully think you are mistaken. In the thread, the author of Play Integrity Fix says:

And then he goes on to link the version of Display's module to use.
[Google Pixel 7 Pro] simplepinoi177:
I agree -- especially in consideration that 1.3 is the only working method for most P7Ps while Play Integrity Fix is built with 2.0 in mind -- wonder why the @chiteroman put this in OP
[Google Pixel 7 Pro] simplepinoi177:
Regardless @dmarden , I don't believe chiteroman uses a P7P nor is up to date with it necessarily; me and @Lughnasadh are....

and in our experience, Pixel 7's only really need the 1.3; the Play Integrity Fix doesn't necessarily do much more, if any....
[Google Pixel 7 Pro] dmarden:
As far as I can tell... 2.0 + the extra addon seems to be working for me. I am curious about removing the addon and dropping to 1.3. For science if nothing else.

2.0 alone did not work (hence my original post), but as soon as I added the addon (which says it needs Displax's 2.0) things worked.

It seems to me that the choices are 1.3 OR 2.0+addon.
[Google Pixel 7 Pro] Lughnasadh:
I think when he says "and you will also need to use this...", he is still referring to Displax's 1.3. Think it may just be worded awkwardly.
[Google Pixel 7 Pro] simplepinoi177:
Very happy you got it working...like I said previously...

EDIT: Honestly, I'm betting you'd get it working just as well with v1.3+add-on....
[Google Pixel 7 Pro] dmarden:
Right right, I am with you there... just talking for the sake of discussion and clarity for other people.

I think saying that it's one or the other is inaccurate. I think saying 1.3 alone is the best bet may very well be accurate though.

2.0 + addon seems like an option at first glance, I am definitely not saying it is a better option. Obviously I don't have any idea, haha.
[Google Pixel 7 Pro] dmarden:
Nope, he links the specific release:

Promise I am not trying to beat a dead horse. I even completely 100% accept that your advice to use Displax's 1.3 is the best avenue. I am just clearing up specifics that the dev put in his post.
[Google Pixel 7 Pro] simplepinoi177:
It's why I pinged/mentioned him in my post...maybe he'd see these posts and he'd shed some light....
[Google Pixel 7 Pro] dmarden:
If 1.3 alone works by itself, I am just gonna go with that. No need to have multiple things if one thing does the job! :)
[Google Pixel 7 Pro] simplepinoi177:
It's how most of us have been going at it...chiteroman only created his thread (so probably created the module around the same time) in late July -- up until that point it's how we've done it successfully; even after....
[Google Pixel 7 Pro] chiteroman:
If you are using Displax module v1.3, my module will be useless because in service.sh it forces first_api_level.

The point of my module is to change that property in GMS unstable process only.

I put cheetah as example because it shipped with A13.

If Displax v1.3 works and don't cause bugs in system don't use my module.
[Google Pixel 7 Pro] chiteroman:
Yeah, I don't have it, thanks for remember I'm poor 🤣🤣🤣
[Google Pixel 7 Pro] UberNorse:
I believe the developer, Chiteroman, of PI-fix is now saying with his newest modules it will tell you on installation if you should use it in combination with Displax's module. I believe I remember reading some may need to and others won't. Hard to remember as some of the posts were lost in migration.

I believe either 8.9 or 9.0 does this but they both failed device for me so I reverted to 8.8 which works great.

EDIT - I have no idea how I missed so many messages above me stating this. This migration has me all screwed of sorts. :)
[Google Pixel 7 Pro] jiwanshu2003:
Anyone ever heard of a Verizon demo unit Pixel 7 Pro being bootloader unlocked? I currently have one that I removed the sim card from immediately when I got it last year, and when I finally wiped the device and set it up recently, I found that the OEM Unlock toggle was available. Immediately turned it on in case somebody tried to disable my ability, and interestingly Verizon didn't even have the phone registered under their system, I had to get them to register it as a Pixel 7 Pro unlocked because for some reason it also came fully unlocked. Its weird that every IMEI check I've run with swappa and through Google Support themselves claim its a locked Verizon device. Maybe I just got really lucky. Right now it still shows toggleable, and I don't plan on actually unlocking it until support ends for it.
[Google Pixel 7 Pro] dmarden:
I am able to confirm that 1.3 alone works. Not that I think anyone specifically wanted my confirmation, haha.
[Google Pixel 7 Pro] simplepinoi177:
You should at least tick it now....having an unlocked bootloader gives you more, better recovery options -- case in point, the Android Flash Tool can work with a locked bootloader as long as the "OEM unlocking" is ticked. There are innumerable examples on all the Pixel forums where members said "if only you had an unlocked bootloader...." when trying to help a bricking.

But I also had that sort of happen on my replacement Pixel 2; it was togglable, but once I rebooted or went into fastboot mode, the tick would grey.

Honestly, you are really lucky and it probably would be best for you to at least unlock it now. It's been proven that they can still lock/grey the "tick" OTA; they can't undo it once it

is

unlocked.

MOST IMPORTANTLY,

3 years down the line (or is it 5?) when official support stops, I'm sure you'll have a lot of settings and particular things installed and running on the phone by then -- when you unlock the bootloader it wipes it back to factory! That's why it's always best on Pixels to unlock the bootloader first, so you don't have to deal with wiping on a used customized device...

You are lucky, but that's how I got lucky with my Verizon Pixel 2 XL; sent in for an RMA, got a global variant.
[Google Pixel 7 Pro] jhjhjhjhjhjh:
When you enter flashing unlock in fastboot does it prompt an option on the phone to actually unlock the bootloader??

My friends Samsung phone was able to tick the OEM UNLOCK but no fastboot commands worked...

VERIZON phones having bootloader unlockabilty but doesn't want to unlock.

Thees mega million I hit the jackpot Verizon bootloader stories with no viable proof seems trollage..

We don't want to give Verizon bought phones any false hope..Buy directly from Google...if you want an Unlockable bootloader/ root..
[Google Pixel 7 Pro] jiwanshu2003:
Indeed I am.
[Google Pixel 7 Pro] Schroeder09:
I quickly read over the last 3 pages. Maybe I kissed some of these answers.

1.) Rooting process is the same? Disable verify, remove the "-w", patch and flash the inir_boot image?

2.) I saw someone report that AOSP mods was working. What about xprivacy lua and Gphotos? Here's a picture of my lsposed modules but I care most about XPL, Gphotos, and AOSP mods working. The snapmods one isn't vital.
[Google Pixel 7 Pro] jhjhjhjhjhjh:
Awesome wishi the model number was present but you hit the jackpot!! Lol
[Google Pixel 7 Pro] jiwanshu2003:
It's a GE2AE LOL. I'll check the box at home for any sort of SKU as well because I'm pretty sure it's a Verizon SKU.
[Google Pixel 7 Pro] jhjhjhjhjhjh:
You have my curiosity..:)
[Google Pixel 7 Pro] K1nsey6:
On my end the 7Pro isn't even listed as a trade option
[Google Pixel 7 Pro] RYZONN:
what is the simple way to update for this version without loosing the root ?
[Google Pixel 7 Pro] Lughnasadh:
Pixel Flasher
[Google Pixel 7 Pro] LLStarks:
I guess play integrity fix and safety net fix are separate once again.
[Google Pixel 7 Pro] jhjhjhjhjhjh:
If you had a patched init for a14 already then it's easy.

Just flash the ota of A14 then immediately boot into bootloader mode and flash the patched init..

My rule of thumb is new software version I wipe completely and start fresh..
[Google Pixel 7 Pro] jhjhjhjhjhjh:
Any A14 kernels yet besides the ones with modules needed?
[Google Pixel 7 Pro] jiwanshu2003:
IQGA04426-US
[Google Pixel 7 Pro] Locoman_:
I get wipe - getting a clean start but I took the over the air update and let it do its thing. Disabled all modules. Had Magisk install to inactive slot prior to first boot. All is well. Aosp, full/immersive, Liveboot, systemless hosts, VFA reversed all seem okay.
[Google Pixel 7 Pro] gettinwicked:
Hey all, I know this isn't the best place for this question, but is there a way to change the fonts system wide? I've been using AOSP mods, but it isn't system wide. Thanks!
[Google Pixel 7 Pro] otonieru:
0.8.7 works well with A14, updated to 0.9 , now it fail the CTS

@chiteroman
[Google Pixel 7 Pro] simplepinoi177:
since you pinged him....are you talking about Play Integrity Fix? It has it's own support thread(that would be a better place to post, honestly)....and this one you posted in is not it....
[Google Pixel 7 Pro] Ghisy:
Anyone using Substratum on 14 stable? Does it work? (I'm using Liv Dark and Flux mostly)
[Google Pixel 7 Pro] pp085ster:
You neet to install Custom Font Installer (CFI) and the AFDKO module. Here's a link on how to setup AFDKO within CFI.
[Google Pixel 7 Pro] thehacker911:
Hello, I have a question about rooting. I'm currently on the current beta of Android 14. I have to load the stable image, deactivate all Magisk modules, flash the image, patch the init and then flash the patched init. Am I correct?
[Google Pixel 7 Pro] big-joh:
Hello, I upgraded to A14 with Magisk. But now everytime I unlock my phone with my PIN, it reboots after a couple of seconds.

Even when having all Magisk Modules disabled.

Currently running with a unpatched boot img, which does work.

Anyone experiencing the same problem, or knows what the problem is?
[Google Pixel 7 Pro] swieder711:
Do you patch boot or init_boot?

After I upgraded to A14, it worked with Magisk, but my corporate apps detected root. Trying to figure out how to get around that now.
[Google Pixel 7 Pro] big-joh:
I patched init_boot
[Google Pixel 7 Pro] swieder711:
Does your phone work fine with Magisk uninstalled?
[Google Pixel 7 Pro] big-joh:
Yes without Magisk it works fine. Did you setup MagiskHide for those apps?
[Google Pixel 7 Pro] swieder711:
I added my corporate apps to the deny list and hid the Magisk app. Is there another step or module for Magiskhide?
[Google Pixel 7 Pro] big-joh:
No that should be it.
[Google Pixel 7 Pro] UberNorse:
Maybe this post was lost in migration or I'm confused with QPR1 but wasn't 14 stable supposed to come with a battery cycle count in battery stats? I think I remember someone in this thread maybe mentioning they don't have it. I don't see anything new in battery settings either. Anyone confirm or am I just stupid.

I can see the cycle count when I run a full bug report but that shouldn't be necessary if this was supposed to be included.
[Google Pixel 7 Pro] thereason00:
Let us know what you figure out. I have a bunch of corp apps that don't like root, so gonna hold off on upgrade until I hear you got it sorted out.
[Google Pixel 7 Pro] swieder711:
Some one over on another thread says that their corp apps are working with A14, https://xdaforums.com/t/tutorial-ro...h-magisk-update-q3-2023.4402273/post-89085350
[Google Pixel 7 Pro] Lughnasadh:
-Extract the init_boot.img from the factory image of your current build

-Patch that image in Magisk

-Disable Magisk mods (research if any need to be updated before re-enabling to avoid a possible bootloop)

-Flash the patched init_boot.img in fastboot

-Done
[Google Pixel 7 Pro] crazyut:
This was posted after the change warning and I did not see it in my profile as a posting (which was warned in the change warning).

If I unlock the bootloader on the Japanese model that I have but not root, will this disable the Felica or NFC ship and will it affect banking or apps such as Toronto's Presto app.

Caveat: I know unlocking the bootloader wipes the devices (I mainly have it for my travel apps to Japan and such; I have my Fold 5/S23 Ultra for backup (to each other and for the P7P).
[Google Pixel 7 Pro] big-joh:
I ended up reflashing with a data wipe. Now Magisk is working again.
[Google Pixel 7 Pro] swieder711:
I did a wipe when I updated from A13 to A14. Glad you got it working.
[Google Pixel 7 Pro] big-joh:
Maybe if you try this safety net module. This is the only way to get my banking apps to work.

GitHub - Displax/safetynet-fix: SafetyNet & Play Integrity API workarounds for Magisk

SafetyNet & Play Integrity API workarounds for Magisk - Displax/safetynet-fix

github.com
[Google Pixel 7 Pro] savergiggio:
Hi guys, i'm trying to get root on my pixel 7 Android 14, but i get bootloop in google animation.

I patched the init_boot.img with magisk version 16.3, and flashed with adb 33 and tried 32 too but without fortune.

Someone else have the same problem? Thank you!
[Google Pixel 7 Pro] synesthete:
Do you mean 26.3? Magisk is up to version 26, so I would use a recent version if you are trying to use 16. Did you wipe the phone or flash without wiping?
[Google Pixel 7 Pro] roirraW "edor" ehT:
You will soon find all your Google Pixel updates in one place

Android 14 will soon display all your pending OS and app updates in one place

www.androidpolice.com