yashsingh1/xdaforums huggingface dataset:
[Google Pixel 7 Pro] EtherealRemnant:
The 8 Gen 2 is beastly. I mean I couldn't believe how much faster my S23 Ultra is than my Pixel 7 Pro even just doing basic tasks like browsing. It's insane how smooth the device is. I don't even have to shut 5G off anymore because the drain between LTE and 5G is not as severe and I used my S23 Ultra while on mobile data 100% of the time for 42 hours before having to charge it. My Pixel 7 Pro would have been dead halfway through the first day if I was on 5G only like I was. It never even gets all that warm in regular use either which is great. The only real annoyance I have right now is the fact it has to reboot to change SIM cards. I don't even miss root since Samsung gives more customization with Good Lock.

Of course... it's hilarious... because the gains of the 8 Gen 2 are seemingly largely due to Qualcomm having TSMC fab it instead of Samsung lol.
[Google Pixel 7 Pro] roirraW "edor" ehT:
I think I liked my S3 so much that I was bored with it. There wasn't anything in particular I could think I would want to change about the S3 any longer, and I was excited about the prospect of Android 5, so I got the LG G3 either in 2014 or 2015.

Before I knew that Best Buy would have such a good deal on the smaller Pixel 1 32 GB model for ~$250, I bought me and my wife the HTC 10, since I had nostalgia about my first Android, the Droid Eris. Then later the same month bought the Pixel 1. I should've sent the tens back to HTC, but they just became our spares in case anything happened.

The only reason I went with Samsung in 2020 was because I was tired of waiting for a Pixel with more storage. Originally I was waiting for a 256 GB model, but by the time they came out with one, I wanted 512 GB minimum. I like all my music locally in FLAC files.

Very nice and good to know. Thanks. I haven't had any problem with battery life on either the P7P or the P6P.

Speaking of which, the last four days or so, I've been using my P7P in Battery Saver mode and haven't noticed any reason not to use it all the time - lasting even longer on battery. I usually charged only once a day. I might try Extreme Battery Saver mode once I configure several app exceptions.

I would really miss @siavash79's thread [MOD][Xposed+Magisk][Pre-Release] AOSP Mods - System modifications for AOSP-based Android 12+ if I could no longer use it.

I do have my Tab S8 rooted even though I don't use root as much on it.
[Google Pixel 7 Pro] xunholyx:
Yeah, one thing about the s3 was how many ROMs and other custom stuff there was. I think that the are still ROMs now for it. I know that a couple of years ago it got an update to the newest Android version. That was CarbonROM (which is what I used back then....)

Just googled it and I see there are Android 12 ROMs for it now. That's nuts!

Download and Install AOSP Android 12 on Samsung Galaxy S3

In this tutorial, we will guide you to install Android 12 Custom ROM on Samsung Galaxy S3. If you are someone who wants to install the vanilla

www.getdroidtips.com
[Google Pixel 7 Pro] Lughnasadh:
Mishaal's "What’s new in Android 14 QPR1 Beta 1"...

https://x.com/MishaalRahman/status/1704601566538321970?s=20
[Google Pixel 7 Pro] LLStarks:
Modem bumped from the June one used for the late 14 betas to a September build.
[Google Pixel 7 Pro] jhjhjhjhjhjh:
Anyone get aosp mods working on the qpr1 beta??
[Google Pixel 7 Pro] jhjhjhjhjhjh:
I opted out last week of the beta and just flashed the qpr1 beta via ota and kept all data if anyone wants to try the qpr1 beta without wiping.

Had to repatch the init.img and disable verity again no issues to report except no AOSP mods on this build...
[Google Pixel 7 Pro] JakeDHS07:
If I'm not mistaken they only release for stable. When it comes to mods support I never expect them to be able to keep up with beta releases. There's just too many variables
[Google Pixel 7 Pro] roirraW "edor" ehT:
I haven't had time to look, but guessing this is in there somewhere:

Google Pixel phones will show battery cycle counts starting with Android 14 QPR1

Starting in Android 14 QPR1, Google Pixel phones will start showing battery cycle counts via the Settings menu.

9to5google.com

They did eventually start developing for Android 14/Beta, but probably not until at least Beta 1 or 2 (not DP 1 or 2), but yeah, it wouldn't count on it ever working with a Beta especially until their changelog mentions it.
[Google Pixel 7 Pro] Pixel86:
Anyone else lose CLEAR CALLING from the sounds settings with today's QPR1 update? If I'm not an isolated case, I'm wondering if it's now "built-in".
[Google Pixel 7 Pro] Lughnasadh:
It is 👍

https://twitter.com/i/web/status/1704605423318245524
[Google Pixel 7 Pro] Lughnasadh:
I can't seem to find it either.
[Google Pixel 7 Pro] bradhoschar:
I was on Android 13, just opted in for the beta (U1B1.230908).

What magisk is everyone using?

I'm assuming I can't just uninstall magisk, and restore images in magisk as it's jumping from 13 to 14.
[Google Pixel 7 Pro] Dr.Pepper:
Kernel also has been a bit updated

5.10.177-android13-4-00003-gacbc9bacfebc-ab10753192

#1 Fri Sep 1 22:53:59 UTC 2023
[Google Pixel 7 Pro] Jwtiyar:
iam on beta 5.3 , Does this update will wipe? or future stable update after qpr1 will wipe?
[Google Pixel 7 Pro] rosms:
Anyone facing issues with wallet? It gives an error like its rooted or something similar. Qpr 1 September , not rooted
[Google Pixel 7 Pro] allenjthomsen:
just for anyone that wants it here is the link to the qpr1 gsi with gapps zip

https:\/\/dl.google.com\/developers\/android\/udc\/images\/gsi\/gsi_gms_arm64-exp-U1B1.230908.003-10811961-ea51ef48.zip

And Pure AOSP GSI

https:\/\/dl.google.com\/developers\/android\/udc\/images\/gsi\/aosp_arm64-exp-U1B1.230908.003-10811961-d0069741.zip
[Google Pixel 7 Pro] sawdoctor:
Maybe fc play services and clear cache see if it helps. There's something in the release notes about CTS issues but not seen anyone report wallet not working. Still I'd read the release notes in the op see if it helps
[Google Pixel 7 Pro] ScoobyWRX:
So I opted out of beta 5.3 so as not to wipe for stable 14, if I opt in to the this QPR1 what happens when 14 comes out on the 4th October?
[Google Pixel 7 Pro] Lughnasadh:
You'll have to wipe if you want to go back to stable.
[Google Pixel 7 Pro] ScoobyWRX:
Thanks
[Google Pixel 7 Pro] roirraW "edor" ehT:
The only time a wipe is involved is when there is a downgrade. Android 14 QPR1 Beta 1 is newer than Android 14 Beta 5.3, so no wipe.

If someone were going from Android 14 QPR1 Beta 1 to Android 14 Stable (when it's available), then that's a downgrade, so wipe will be involved.
[Google Pixel 7 Pro] Jwtiyar:
Ohh i thought it's not newer than a14, thank you.
[Google Pixel 7 Pro] roirraW "edor" ehT:
You're welcome!

Yep - Major Android version -> QPR1(*) -> QPR2(*) -> QPR3(*) -> Devloper Preview(#) -> Beta(#) -> Stable(#)...

(*) - includes Betas of those

(#) - new major Android version

Likewise, for example, Android 14 Beta 5.2 -> Android 14 Beta 5.3 - if someone wanted to downgrade from 5.3 to 5.2, they'd have to wipe

The reason is logical. Upgrades are expected, and not just apps, but the apps' data are also upgraded. If you were to install an older version of Android while keeping the upgraded version of the app (including system app) data, things would not work correctly, and in some cases the phone wouldn't even boot.

There is no facility to downgrade app data when downgrading the OS.
[Google Pixel 7 Pro] bradhoschar:
Searched the forum, but didn't see anything for rooting U1B1.230908.

Is it possible with the same process?
[Google Pixel 7 Pro] Lughnasadh:
Root as you normally would. Patch and flash the init_boot.img.
[Google Pixel 7 Pro] jhjhjhjhjhjh:
Anyone notice this feature
[Google Pixel 7 Pro] Sui77:
Is wipe also mandatory if flashing manually on a rooted device with pixel flasher?
[Google Pixel 7 Pro] roirraW "edor" ehT:
The same rules apply whether you're flashing manually, taking an OTA, rooted or not rooted, or anything.
[Google Pixel 7 Pro] Aks:
yeah, its not working on QPR1 build. I did a clean install. rooted using PF and as soon as i installed AOSP mods, system UI kept crashing and eventually it went to recovery stating device is corrupt and had to do it all over again.
[Google Pixel 7 Pro] LLStarks:
QPR battery life above average so far
[Google Pixel 7 Pro] cmh714:
Known issue: https://xdaforums.com/t/mod-xposed-...r-aosp-based-android-12.4421743/post-89030269
[Google Pixel 7 Pro] insestito:
Can you drop this init_boot please? I need it
[Google Pixel 7 Pro] vrda08:
Compared with beta 5.3 or 13 stable
[Google Pixel 7 Pro] LLStarks:
The Android 14 betas.
[Google Pixel 7 Pro] ScoobyWRX:
My cycle count is 0? :unsure:
[Google Pixel 7 Pro] vrda08:
Recharge it
[Google Pixel 7 Pro] ScoobyWRX:
Thanks. Up to 182, which still maybe a little low but better than 0! :)
[Google Pixel 7 Pro] ariesgodofwar:
Trusted Devices under Extend Unlock missing for anyone else now?
[Google Pixel 7 Pro] ArtuCer:
[Fixed] Smart Lock Trusted devices missing from Google Pixel, Samsung

In recent days, Google Pixel and Samsung owners have noticed that Smart Lock's Trusted devices option has gone missing...

9to5google.com
[Google Pixel 7 Pro] ariesgodofwar:
Thanks for that, I will keep a lookout for a Play Services update then, hope they get it fixed soon, as it is hell with Bluetooth Android Auto
[Google Pixel 7 Pro] V0latyle:
It's actually been removed from AOSP. It disappeared on my Pixel 5 with the September update, so I don't think this is something that's going to get "fixed"
[Google Pixel 7 Pro] sawdoctor:
I tried to use macrodroid to keep my phone unlocked when connected to the car but unfortunately it's not working. Hope they fix it soon as this was forced on us with no way to uninstall
[Google Pixel 7 Pro] sawdoctor:
It's extremely annoying they swapped smartlock with extend unlock without telling us and removed one of the most important features
[Google Pixel 7 Pro] V0latyle:
But then you'd have to assume software developers actually listen to their customers
[Google Pixel 7 Pro] ariesgodofwar:
Yeah, I can't imagine that this was intentional given the new wireless iterations of Android Auto alone. No alternative completely breaks this and diminishes the value of the platform from the standpoint of a vehicle manufacturer. Not that developers always think about those things, but this was also a huge benefit to WearOS as well. The only thing I could think might make sense was if there was some zero day exploit that they needed time to patch
[Google Pixel 7 Pro] bradhoschar:
Yeah, I dirty flashed QPR1, then rooted, and AOSP mods worked except the 'restart system UI', so had to do a regular restart, and I updated the module in magisk, and it broke. I should've backed up my magisk first...
[Google Pixel 7 Pro] jahmezis45:
i was on 5.3 and have had no issues with flashing ota's in the past but with this qr1 beta for whatever reason with pixel flasher the software doesn't change. itll flash and say it is complete but the rom doesnt seem to be changing. Any ideas or help is appreciated
[Google Pixel 7 Pro] roirraW "edor" ehT:
Use the phone's built-in OTA update method manually instead.

Full OTA Images for Nexus and Pixel Devices | Google Play services | Google for Developers

developer.android.com

Full OTA Images for Nexus and Pixel Devices | Google Play services | Google for Developers

developers.google.com

Then, if you want root, download the full firmware for QPR1 Beta 1 in order to Magisk the init_boot.img, and flash the rooted init_boot.img to the init_boot partition.

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

developer.android.com

More details about manually flashing here:

https://xdaforums.com/t/september-1...r-root-pixel-7-pro-cheetah-safetynet.4502805/
[Google Pixel 7 Pro] p51d007:
Just found this on Android Central...

Google Wallet is not currently functional on the first Android 14 QPR1 beta due to a security issue that prevents Pixel devices from meeting the requirements for contactless payments.

This issue affects all Pixel phones running Android 14 QPR1 Beta 1, regardless of whether they are rooted or not.

Google has acknowledged the issue and is working on a fix.

Anyone have G-pay issues? Just tried to use it at a convenience store I go to 2-3 times a day

and the g-pay app said my phone (pixel 7 pro) does not meet the minimum security bla bla bla.

Only thing I've done is install the QPR firmware that came down the other day.

Google phone, google app, google firmware and it doesn't meet the security requirements???
[Google Pixel 7 Pro] Lughnasadh:
In addition to the great advice of @roirraW "edor" ehT , you could also go over to the Pixel Flasher thread and submit a support zip so he can look at it and figure out what went wrong. If things have changed with A14 QPR1 Beta 1, I'm sure he would appreciate the heads up as well.
[Google Pixel 7 Pro] LLStarks:
I'm rooted with the play integrity module and I've had zero issues.

I've used the wallet and mobile payments repeatedly with the QPR.
[Google Pixel 7 Pro] justDave:
This is a wild guess but...

Take a look at the log window. Any chance it flashed the opposite partition but then didn't switch partitions before the reboot?
[Google Pixel 7 Pro] sawdoctor:
Reading various threads/YouTube vids it seems random. Both rooted and unrooted devices have been affected with no obvious connection between the affected devices
[Google Pixel 7 Pro] cmh714:
I read an article yesterday that said Wallet was having "issues" on QPR1....regardless of root. For some it worked and other it did not. So its not necessarily a root issue if you have Wallet problems.
[Google Pixel 7 Pro] caitsith810:
Funny enough, I had problems without root....I tested it just for fun and yeah, it wouldn't allow me to sign on or add cards.

I rooted and used the safetynet fix mod, and I'm all good. What a weird set of circumstances lol.

-------------

Heads up for those that use substratum themes. The ones I use(Flux & Liv Dark) don't work with QPR1 all the way compared to 5.3, the SystemUI crashes hard. Themer works just fine, however.
[Google Pixel 7 Pro] jahmezis45:
it appears im having some recovery issues when i adb to to recoery i get the android laying down with the red traingle and it says no command? any ideas
[Google Pixel 7 Pro] roirraW "edor" ehT:
That's expected, or normal.

Credit to @Lughnasadh and @badabing2003 for testing these steps previously. In your case, you've done step #04, so continue at step # 05 after that, and step #10 and beyond are optional if you want to flash the same update to both slots. I may post this in my main (Stable) thread sometime:

01. UN-hide Magisk on the phone

02. Disable all Magisk Modules just in case they're not compatible with and cause a bootloop on the new firmware

03. Copy init_boot.img from factory image to phone, run Magisk on it, copy back to PC

04. adb reboot recovery

➡05. Once Recovery Mode shows up 'No command', Press the Volume Up button while holding the Power button

06. Volume Down button to navigate to ''Apply update from ADB'' option, then press the Power button to select the option

07. adb sideload cheetah-ota-AB#a.YYMMDD.##-blah.zip

08. Choose recovery menu option ''reboot to bootloader''

09. fastboot flash init_boot Magisk'd_init_boot.img

Optional if you want to flash the update to the other slot, too:

​

10. fastboot --set-active=other​

(Manually switching slots is redundant and cross-purpose. I'll renumber these without that later.)​

11. Volume Down X2 to ''Recovery Mode'' and click the Power Button to choose it​

12. Once Recovery Mode shows up 'No command', Press the Volume Up button while holding the Power button​

13. Volume Down button to navigate to ''Apply update from ADB'' option, then press the Power button to select the option​

14. adb sideload cheetah-ota-AB#a.YYMMDD.##-blah.zip​

15. Choose recovery menu option ''reboot to bootloader''​

16. fastboot flash init_boot Magisk'd_init_boot.img​

17. fastboot reboot
[Google Pixel 7 Pro] badabing2003:
If one would chose to do step 10 and beyond, I'd change step 10 to this just to be double sure (I'm paranoid)

Boot to system to make sure it boots properly, and let the system do it's thing (in case there is an issue, you want your previous slot intact), then reboot back to bootloader and continue to step 11, actually there is no need to switch slots as in step 10, as sideloading will do that, otherwise you're rewriting to the same slot that you had already written to.

One last thing, step 3, you can extract init_boot from ota, it's in the payload.bin, this way you don't have to download both ota and factory.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Good point! I will adjust the directions there.

Oh! Thank you.

Edit: And manually switching slots still wouldn't be necessary if someone doesn't boot into the system to test it out, correct? (if they proceed with just flashing the other slot)

Interesting, thank you! Is the following what someone would use (at least on Windows, but it's multi-platform) or is there an easier way on Windows?

GitHub - ssut/payload-dumper-go: an android OTA payload dumper written in Go

an android OTA payload dumper written in Go. Contribute to ssut/payload-dumper-go development by creating an account on GitHub.

github.com

If so, in that case, I'd probably suggest an either/or option, as some users would likely prefer to just download the whole factory image over using the payload dumper, even though it is indeed quite a waste to do so just for that.
[Google Pixel 7 Pro] Lughnasadh:
Also, although I haven't tested it, Magisk should now be able to extract and patch the boot.img or init_boot.img from a full OTA zip if the full OTA is on your device. Of course you still have to flash the patched image yourself.
[Google Pixel 7 Pro] badabing2003:
Yes, payload-dumper-go is very good.

One can download single exe and not have to deal with python like the original payload dumper.

The command would be:

<full_path>payload-dumper-go.exe -p init_boot -o <output_dir> payload.bin
[Google Pixel 7 Pro] roirraW "edor" ehT:
Thanks! I don't know if I'd visit that part of the rabbit hole, though, since I'd like to keep the instructions as simple and unconditional as possible.

Thank you!

I think it's time this old guy goes to bed, though, so I'll have to refine my post later. I made an edit to my reply to you, I think you didn't see:

Manually switching slots still wouldn't be necessary if someone doesn't boot into the system to test it out, correct? (if they proceed with just flashing the other slot instead of testing)
[Google Pixel 7 Pro] badabing2003:
Correct, manually switching slots is not necessary regardless if one chooses to boot to system or not.
[Google Pixel 7 Pro] jahmezis45:
Only thing is I want planning on rooting because it keeps getting detected by sports betting apps. When I try step 7

actually it worked, Thanks a mil
[Google Pixel 7 Pro] Aks:
V4A working for any on QPR1? It was working well for me till 5.3 and now it says driver not found. When I try to install driver, progress is 0% for more than an hour. I tried uninstalling and reinstalling multiple times but nothing helped.

EDIT: Figured out, the latest version from GitHub isn't working. However, I was able to locate re-engineered version @Lughnasadh shared earlier and it's all good now.
[Google Pixel 7 Pro] Lughnasadh:
Yeah, I was just letting people know about this in case they were unaware 👍
[Google Pixel 7 Pro] gpvecchi:
Do you know if Iconify works on QPR1? Thanks!
[Google Pixel 7 Pro] WhoIsJohnGalt1979:
Out of topic. However, certain Xposed features like blur and fluid os theme and color engine works just fine. Only request don't try to change the tiles from the first tab. Your phone will crash and you will have to factory reset. I was lucky to be able to hook into pixel flasher for 15 seconds and disable the module.
[Google Pixel 7 Pro] gururoop:
I made a stupid mistake. Flashed Android 13 September Patch on my phone running Android 14 QPRB1 using platform-tools_r34.0.4-windows. Now my phone is bricked. I cannot go in Fastboot mode, it only shows as USB serial device in Windows 11 device manager. Anyone able to rescue the phone in a situation like this without sending it back to Google?
[Google Pixel 7 Pro] Pixel86:
Reflash Android QPR1 via bootloader using built-in FLASH-ALL Google provided script.
[Google Pixel 7 Pro] jhjhjhjhjhjh:
Glad i don't use platform tools ive seen a hit or miss when using r34 or r33 .

The only secure way to downgrade is using "android flash tool"

The program takes about an hour but it locks the bootloader after downgrading.

Also i only flash pixels with the android flash tool or ota sideloading..
[Google Pixel 7 Pro] roirraW "edor" ehT:
Only if you check/leave the box checked to re-lock the bootloader.
[Google Pixel 7 Pro] jhjhjhjhjhjh:
i didn't realize that option was there.. thanks

Anyone post when aosp mods is updated on the qprs.

Im getting aosp mod withdrawals..:(
[Google Pixel 7 Pro] bradhoschar:
Big same
[Google Pixel 7 Pro] sawdoctor:
Maybe subscribe to their telegram announcement thread I'm sure that will be the 1st place it's posted. I did read they'd fixed most options but would be a least a week until they pushed an update
[Google Pixel 7 Pro] gururoop:
I can't get in Fastboot mode only. Is there a way. Google tech support said they will get back to me in 24-48 hours.
[Google Pixel 7 Pro] Lughnasadh:
Try sideloading the Full OTA.
[Google Pixel 7 Pro] gururoop:
My phone is neither booting in the OS nor in Fastboot.
[Google Pixel 7 Pro] Lughnasadh:
Do you mean after you tried sideloading the Full OTA? You need to get into recovery mode to sideload, not fastboot mode.
[Google Pixel 7 Pro] gururoop:
How do I boot into recovery mode? Right now the screen is black and nothing happens if I try to power it while holding volume up or down or both buttons.
[Google Pixel 7 Pro] Lughnasadh:
If that's the case, then unfortunately you may be out of luck.
[Google Pixel 7 Pro] Nekromantik:
anyone else after september update have no hey google working anymore?
[Google Pixel 7 Pro] VerticalCobra:
Working ok on P7P 🤷‍♂️
[Google Pixel 7 Pro] sawdoctor:
Think Google have pulled their fingers out, trusted devices is now showing in extend unlock and i can keep my phone unlocked while connected to Bluetooth devices
[Google Pixel 7 Pro] V0latyle:
Same here
[Google Pixel 7 Pro] ScoobyWRX:
Hope they fix Google pay as soon as... 🙄
[Google Pixel 7 Pro] Lughnasadh:
Mishaal Rahman reported yesterday that he heard the issue should be resolved (in the last 24 hours), for what it's worth.
[Google Pixel 7 Pro] p51d007:
Mine worked after the QPR update, but I had rebooted my phone the day after and it wouldn't work.

I read on another site, that going into the wallet & gpay app and clearing the cache out would restore it, but I haven't

used my phone this weekend for any transactions.
[Google Pixel 7 Pro] p51d007:
Well, that didn't work. Cleared the app cache. It didn't give me the error on the phone that my phone didn't meet the security requirements, but the point of sale terminal said "declined". Had to use the card instead. You'd think Google would fix this ASAP because they lose a percentage of each transaction.
[Google Pixel 7 Pro] Lughnasadh:
"Google has caught wind of the issue, and it was quick to issue an update. The fix didn’t come via another Android update. Rather, this change came through a new Google System update, so it’s quick and painless. If you still can’t use your contactless payments, you may want to wait just a bit. The update might not have come to you just yet."

The Android 14 QPR is no longer breaking Google Wallet

A little while ago, the Android 14 QPR was breaking the Google Wallet app, but it appears that it's been fixed.

www.androidheadlines.com
[Google Pixel 7 Pro] p51d007:
Maybe I should have tried it again...I'll give it another shot tomorrow. If that doesn't work, I'll just uninstall/reinstall gpay & wallet. It says gpay was updated 4 days ago. Anyone know which app had to be updated?
[Google Pixel 7 Pro] Aks:
I installed an older apk of March and it's working for me 😀
[Google Pixel 7 Pro] p51d007:
Got a gpay update Tuesday morning. Gpay working again.