yashsingh1/xdaforums huggingface dataset:
[Google Pixel 8 Pro] raze5115:
how did you install the rom? I tried going through the official pixel flashing too and the flash-all.bat methods and both caused the same problem that I listed above. The only method I haven't tried is the ota method. Which I can't do the ota method bc the bootloader is unlocked on my pixel 8p and I root my pixel 8p
[Google Pixel 8 Pro] Megaman01:
I joined beta program and installed ota.
[Google Pixel 8 Pro] raze5115:
ok that explains it. apparently it only works via ota and doesn't work via the official pixel flashing tool nor the flash-all.bat methods aka it only works on dirty flashing method which totally sucks bc I want to try it too. And it doesn't work on pixel phones with unlocked bootloaders.
[Google Pixel 8 Pro] roirraW "edor" ehT:
Have you tried a factory reset?
[Google Pixel 8 Pro] Dr.No.pt:
I would say it's mandatory (factory reset) when upgrading from 14 to 15 to avoid issues.
[Google Pixel 8 Pro] Lughnasadh:
Not experiencing any of these problems, even with dirty flashing from A14 to A15 (haven't cleaned flashed since October). Runs well as a daily driver for me. Been using flash-all.bat the whole time.
[Google Pixel 8 Pro] bdr127:
OTA works with unlocked bootloader.... In fact, Google *highly* recommends unlocking your bootloader before flashing a beta OTA (as noted in the OP -- with animated "DANGER" images and all... Hahaha...)

Unless something changed recently?
[Google Pixel 8 Pro] ponczoszek:
Hi, 2.2 beta broke android auto for me, yesterday on 2.1 all AA base features worked flawless, but since 2.2 Google maps are force closing when connecting to AA. Can someone confirm this or this is on my side ?
[Google Pixel 8 Pro] roirraW "edor" ehT:
I'm getting exactly this problem on Android 14 Stable as well, so I don't think it's an Android 15 Beta-specific issue. I very rarely have any issue with Android Auto, and I don't remember if I've ever had this issue before. I was able to play music and see my apps in Android Auto, but anytime I switched to Maps in the car, it showed a black screen.

Maps loaded just fine on my phone itself. I've rebooted since I drove this morning, so I'll see if anything's different when I drive again here in the next 2+ hours.

Edit: Just noting that Android Auto also worked for me 100% fine yesterday, and it was only three hours ago when I encountered the issue.
[Google Pixel 8 Pro] Lughnasadh:
Are you guys using the beta version of Google maps? If so, known issue but there is a workaround...

Google Maps latest beta is crashing on Android Auto, but you can fix it

Google Maps beta is crashing in Android Auto! Here is how to fix it

www.androidpolice.com
[Google Pixel 8 Pro] roirraW "edor" ehT:
Thanks! Ah, I forgot I was in the Beta program for Maps. I'm sure I did so for some specific feature, previously.

I thought at some point there was a place in the Play Store for viewing all apps that you're in the Beta program for, but I'm not finding it. I did just leave the Beta program for Maps, though.
[Google Pixel 8 Pro] Lughnasadh:
I think there used to be a beta section when you looked at the installed apps sections, but that was many, many, many moons ago I believe. That would be nice though, considering I am using betas on just about every app I can 🤣
[Google Pixel 8 Pro] ponczoszek:
Guys, after clearing all the cache files and uninstalling all updates it started working ok, so to be clear it's not beta 2.2 issue.
[Google Pixel 8 Pro] roirraW "edor" ehT:
...making notes about what keeps Lughnasadh busy...

🤪
[Google Pixel 8 Pro] LLStarks:
First date

First date is usually the core firmware date, second date is usually the carrier config date.
[Google Pixel 8 Pro] raze5115:
yes obviously and I tried installing the rom like 3 times with both the official pixel flasher and fab. The only way it works is by ota.

yeah OTA is the only way it works.
[Google Pixel 8 Pro] fil3s:
Yeah. I tried lineage os, and I have to say, coming back to the chronic lag and instability of stock has been a woeful experience, and I'm not even rooted. In 2024, I find it hard to believe such issues are still so prevalent. Microsoft have gotten their act together with windows 11 more than Google have with android 14 on this phone.

Edit. Seems to be a lot better after I raised the font size by one notch.
[Google Pixel 8 Pro] gettinwicked:
Anyone else's voicemail button disappearing from the phone app? Mine was gone when I first updated to beta 2.2, but it came back the same day. Today it is gone again. Restarting isn't helping.
[Google Pixel 8 Pro] ponczoszek:
Is it a known issue, that then talking on speaker or via headphones, the screen is unresponsive most of the time , the only workaround that works is to relock the screen. Kinda sad to have so many bugs on "flagship" device.
[Google Pixel 8 Pro] znel52:
Well that is what Beta firmware is for...Finding the bugs before actual release.
[Google Pixel 8 Pro] Dr.Pepper:
Feels like moden in 2.1 was much better than in 2.2:(

With i 2.2 i dont have stable lte connection while with 2.1 it was stable enough.

Hope
[Google Pixel 8 Pro] fabiodifa:
Yes, the wi-fi calling too was better in 2.1
[Google Pixel 8 Pro] stardomains:
I use a stylus and the screen is very erratic with it on this beta. Work 100% fine with the stable. Tried Screen Protector Mode and even took the screen protector off and neither helped.
[Google Pixel 8 Pro] Lughnasadh:
I've noticed that since A15 Beta 2, when first turning on/waking up the display, a stylus doesn't work for about 5 seconds (fingers work fine), but after that it seems to work fine, for me at least. But yeah, there's definitely something wonky going on with using a stylus on A15 Beta 2+.
[Google Pixel 8 Pro] stardomains:
Yep. That's it.
[Google Pixel 8 Pro] roirraW "edor" ehT:
Android 15 takes killing an app to the next level

When you force-stop an app in Android 15, the home screen widget of that app will also be temporarily disabled.

www.androidauthority.com
[Google Pixel 8 Pro] Lughnasadh:
A15 Beta 3 likely tomorrow...

x.com

x.com
[Google Pixel 8 Pro] Lughnasadh:
Yabba Dabba Doo!!!​
[Google Pixel 8 Pro] roirraW "edor" ehT:
June 18, 2024

:

Android 15 Beta 3:

Android 15 Preview | Android Developers

How the Android 15 Preview works, the timeline, and what is included.

developer.android.com

Release notes | Android Developers

Release notes and known issues for the latest Android 15 builds.

developer.android.com

Android 15 | Android Developers

<!-- hide description -->

developer.android.com

Get Android 15 | Android Developers

Get Android 15 on your eligible device.

developer.android.com

Factory images for Google Pixel | Android Developers

Instructions for downloading and installing preview system images for Pixel devices.

developer.android.com

OTA images for Google Pixel | Android Developers

Instructions for downloading and applying preview OTA images for Pixel devices.

developer.android.com
[Google Pixel 8 Pro] roirraW "edor" ehT:
Here’s everything new in Android 15 Beta 3 [Gallery]

Android 15 Beta 3 is available today with final system behaviors as part of the Platform Stability milestone...

9to5google.com
[Google Pixel 8 Pro] roirraW "edor" ehT:
Android 15 can automatically delete your face or fingerprint unlock if they aren't working well

Android 15 can delete your face or fingerprint unlock when they aren’t working well and then prompt you to set them up again.

www.androidauthority.com
[Google Pixel 8 Pro] cmh714:
Considering finally updating to 15 from the June v14 version.....any gotchas I may have missed?? Can I just use the 15 OTA over the top or some other method?? Since I am in Thailand now, dont want to screw myself.....TIA!!!
[Google Pixel 8 Pro] roirraW "edor" ehT:
I can only answer that yes, you should be able to use the OTA without issue. I haven't been running the Beta, though, so I can't advise further. If you at least have full access to a computer and some free time to fix if the worst happens, then you'd likely be good. If you're rooted and use LSposed, you likely want to upgrade to LSposed_mod 1.9.3 by another developer first.

I don't know if anyone has been using Magisk Stable 27 with Android 15 Beta or what, though. I don't recall what's been said.

Good luck, whatever you choose!
[Google Pixel 8 Pro] ScoobyWRX:
Why am I still not getting 2 line names in the app drawer :confused: I've toggled it on
[Google Pixel 8 Pro] Lughnasadh:
Working here. Not sure why it's not working for you.
[Google Pixel 8 Pro] roirraW "edor" ehT:
Google is preparing to make the Settings app in Android 15 more organized (APK teardown)

Google is preparing to revamp the Settings app in Android 15 to be more organized. Here's what the new top-level settings might look like.

www.androidauthority.com
[Google Pixel 8 Pro] roirraW "edor" ehT:
Release v16.0 · chiteroman/PlayIntegrityFix

WORKING TEE = STRONG PASS

github.com

"WORKING TEE = STRONG PASS"

Hmmmm....

Edit: There's already been a newer pre-release, though (up to 16.2 right now), so I like to hold off for a week without new activity before upgrading to the latest Stable release.

Edit 2: Meant to post this in my Stable thread, which I have since. :)
[Google Pixel 8 Pro] Lughnasadh:
This is changing by the minute, lol. Probably best to wait and see how things shake out. His latest message....

Sailfish fingerprint is banned for RCS, so even passing Strong it won't work.

But now you have a valid certificate chain, you can use more fingerprints, including newer ones.

Also you can use your device fingerprint 😊

ONLY IF YOUR TEE IS OK
[Google Pixel 8 Pro] roirraW "edor" ehT:
Yep, I like to I like to hold off for (at least) a week without new activity before upgrading to the latest Stable release.
[Google Pixel 8 Pro] Lughnasadh:
I don't even use any of this stuff. Just following along for the fun of it 🤣

Not trying to pass any integrity. Don't use banking apps and using SMS/MMS is fine for me. I may be getting even older 😅
[Google Pixel 8 Pro] ScoobyWRX:
Well......I've messed about with font and display size, grid sizes. Cleared cache, turn off and on, still not working for me ☹️ I feel so left out! 😭😇
[Google Pixel 8 Pro] ArtuCer:
Me too😢
[Google Pixel 8 Pro] jiliian177:
Should use "too" not "to"

Use "to" when indicating where you're going or where something belongs. pen_spark

Use "too" when you want more of something or to include yourself with something
[Google Pixel 8 Pro] nibera:
Hi, I'm with Android 15 beta 2.2 rotated with Magisk 27, no problem, now I'll do the same thing with beta 3 full ota with pixel flasher, any particular precautions or do I do as I've done before? Thank you
[Google Pixel 8 Pro] roirraW "edor" ehT:
@jiliian177, please don't correct user's spelling or grammar. This isn't the purpose of XDA or this thread.
[Google Pixel 8 Pro] Dr.No.pt:
Did you flashed A15 Beta on top of A14 or just clean install A15 Beta?
[Google Pixel 8 Pro] ScoobyWRX:
OTA beta from stable 14
[Google Pixel 8 Pro] FunktasticLucky:
Running a Pixel 8 and have been doing OTA since moving from beta 14. This is the first time I have had any weird issues with my phone.

The screen randomly turns on in lock screen like AOD is enabled but at like full brightness. The other weird behavior is that it doesn't default to the fingerprint. It pops up asking for pin usually and I have to swipe down to get back to the fingerprint. Very strange behavior.
[Google Pixel 8 Pro] roirraW "edor" ehT:
Sounds like a factory reset, or if that doesn't do the job, using their Official Flash Tool might be prescribed.

Android Flash Tool

flash.android.com
[Google Pixel 8 Pro] sunit_talwar:
Even I do experience the same issue with new Beta 3 Update , wrt to screen turning on (AOD Mode - black background with white text) with full brighness . Not sure when the screen eventually turns off but i have noticed screen to be active for quite some time.

i Have updated from Beta 2.2 to Beta 3
[Google Pixel 8 Pro] FunktasticLucky:
I don't think it ever turns off. I usually notice it and just click the power button to turn it back off. I think it's a random bug with this build I'll report it later today since others are also experiencing it.
[Google Pixel 8 Pro] jiliian177:
My bad, not intended to be mee, I'll know that from now
[Google Pixel 8 Pro] roirraW "edor" ehT:
No problem! :)
[Google Pixel 8 Pro] RainneDecember:
Does anyone have any recommendations for root apps/modules tailored for Android 15? I'm already using despair kernel
[Google Pixel 8 Pro] rester555:
EDIT: When you flash the OTA of A15 over A14, does it wipe the device using PF? I read more of the thread, you can flash the OTA without wiping from A14. I might have to factory reset though after flashing with the OTA.
[Google Pixel 8 Pro] Dr.No.pt:
You can/might get some bugs when not wipping from A14 > A15.
[Google Pixel 8 Pro] BillGoss:
Why do you think you need to do a factory reset after installing this A15 beta?

And, to be pedantic, the A15 beta is not an ota but a factory image. If it was an ota it would come as a payload.bin file and you could install it while the phone is booted normally via System Update. But what we have is a collection of IMG files and you install them using fastboot.
[Google Pixel 8 Pro] Lughnasadh:
Google has provided both factory images to flash and Full OTAs to sideload (as well as the delta OTAs) for A15. So that person can do it either way.
[Google Pixel 8 Pro] BillGoss:
Ah, thanks for that. I didn't come across the ota page when i read the info about the A15 beta program.

I chose to install it manually instead of using the flash tool.
[Google Pixel 8 Pro] gettinwicked:
What I typically do when going to a DP or beta is wipe on stable, setup apps, then take the OTA to the beta or whatever. Doing that first helps more apps to work correctly. I've had issues setting up apps on a beta in the past. Also, it seems like only the OTA works. I've tried flashing 15 and it messes up most of the time.
[Google Pixel 8 Pro] Lughnasadh:
For what it's worth, I've had no problems flashing any of the A15 beta factory images using flash-all.
[Google Pixel 8 Pro] stardomains:
Anyone else have these problems with this latest A15 beta:

- Battery Saver quick tile doesn't work to turn on Battery Saver. And even in settings I have problems turning it on.

- Google Play Services is stuck on January 1st, 2024 and shows no update.

- Stylus use right after screen turns on is still wonky but not as bad as 2.2.
[Google Pixel 8 Pro] Lughnasadh:
No problem here with either QS tile or from settings

There are no GPSU updates yet for API 35, so that's why. However, Google has likely installed beta modules into the factory images/OTAs, so not really anything to worry about and it's typical for betas.

Same
[Google Pixel 8 Pro] BillGoss:
I never use flash-all because it wipes the phone and then I'd have to go through the whole process of reinstalling my apps and setting up all the settings the way I like then.

I run flash-base.sh followed by fastboot update image-husky*.zip.

Of course, you could edit flash-all to remove the -w, but that's adding another step.
[Google Pixel 8 Pro] Lughnasadh:
Yeah, I remove the -w. Takes literally 5 seconds so I don't mind.
[Google Pixel 8 Pro] roirraW "edor" ehT:
Hi again @BillGoss!

I don't know if you're aware or if it matters to you, but @Lughnasadh and @badabing2003 educated me in the last year and a half about how flashing the factory image instead of Full OTA Zip makes it so that only the most recent slot you flashed the factory image to is fully useable. i.e. if you switch to the other slot (either on purpose, or if something happened that made the phone automatically switch), it will start to boot, but Android in the other slot won't actually work.

This is why (although I'm not on the Beta) I use the Full OTA Zip each month, and actually I flash it twice, since it changes slots each time you flash it, and so I have the same updated firmware on both slots, since using updated app data with old firmware in an emergency will likely have some kinds of issues.

Also brought to my attention by them was that at least in some cases it was found that a brand-new Pixel didn't have anything at all flashed to the second slot - not even a bootloader, which is dangerous since if, again, the software decides to boot the other slot, if it doesn't even have a bootloader, it'll be hard bricked requiring an RMA to Google as the only solution.

So if you've never taken an OTA on your Pixel, or never manually switches slots and flashed firmware, you should do so at least once - even if you're still using the factory image instead of the Full OTA Zip, since that'll at least get the bootloader flashed the phone's other slot.

Edit: Oh, and the Full OTA Zip can't wipe your phone, so no special steps required.
[Google Pixel 8 Pro] BillGoss:
I'm now at that point in life where I am getting more and more forgetful ☹️ so I need to make my processes foolproof 🤣 (billproof)
[Google Pixel 8 Pro] Lughnasadh:
I hear ya. After I leave the house I often look down just to make sure I remembered to put on my pants 🙃
[Google Pixel 8 Pro] BillGoss:
Thanks for this.

I read your OP (very nice and comprehensive 👍) when I first got my p8p. My previous phone was a OnePlus 8T so I've I learnt about A/B phones over the years. I also learnt something new from your OP, namely that Magisk can extract and patch init_boot from a full OTA zip - thanks!

The one scenario where I think flashing both slots is a real bonus is if you want to have a rooted and an unrooted system available.

Part of my update process is to switch slots.

The A/B configuration was designed for taking OTA updates. You need a separate set of partitions that you can write the updates to. While it's feasible to write the updates to the current partitions, if something goes wrong then you've got no fallback position. Hence A/B and, for the logical partitions in the single super partition, the horrible COW (copy on write) files.

But it was never really designed to enable two full system installations.

The one thing I miss on the p8p is the ability to process a full OTA zip while the phone is running. There's no option to update the running phone from a selected file - at least I've not found that option. Because my preferred way of updating is to do it all on the phone without using a PC.
[Google Pixel 8 Pro] roirraW "edor" ehT:
You're welcome! Yes, I was pleasantly surprised to find out that worked. Likely I was told by someone else.

Absolutely, although that won't be a solution for all apps that have trouble with rooted systems, since just having the bootloader be unlocked (and no root mitigations in place) makes some apps still fail to work. But it's good to have choices.

Oh, good!

I miss being able to update solely using my phone, too, although I only have experience having done so with @Chainfire's app FlashFire that used to work so well on my Pixel 1. I'm amazed it's still in the Play Store, and the website for it is still up.

:) Last updated in 2017. I'm sure there's no way it would work.
[Google Pixel 8 Pro] BillGoss:
I don't use an app to do the update because I like to know (and control) exactly how things work. So I wrote myself a series of shell scripts (yes, that's technically an app!) to do the work.
[Google Pixel 8 Pro] rester555:
I finally got RCS working. I had to go to a15 beta 3 to get it working. Using apatch latest, pif 16.4, zygisk next.
[Google Pixel 8 Pro] fabiodifa:
I have a strange issue with my P8P since (more or less) one month. When I try to send a message using vocal command, Assistant asks to me if I want to send or modify it. When I say "send", Assistant tells me again if I want to send the message or modify it, I say again "send it" and Assistant starts to explaine the meaning of the verb "to send"...I tried to delete cache and memory of Assistant, but the issue is still there. I have the same issue with A15 Beta 3 and with A14 stock. Has anyone the same issue???

Thanks in advance!
[Google Pixel 8 Pro] roirraW "edor" ehT:
On P8P Android 14 June Stable firmware, I told the assistant "Send a message to (my wife's name)". It asked what the message was, I said "Test", then it asked if I want to send it or change it, I said "Send", and it sent, and I confirmed she received it (send and received via Google Messages). Try rebooting?
[Google Pixel 8 Pro] fabiodifa:
Yes, tried everything. I have no idea...
[Google Pixel 8 Pro] gururoop:
Has anyone been able to update to the latest version of Magisk? I was running 27002 debug and when I try to update (both direct install and patch boot image), it ends with error "unable to unpack boot image, installation failed).
[Google Pixel 8 Pro] Lughnasadh:
See my post here.
[Google Pixel 8 Pro] theincognito:
I dunno if you remember me, but you used to help me test the TWRP when I was the TWRP maintainer for OnePlus 8T. So thanks for that again and nice to see you here, Bill! 😁

Sorry for the OT @roirraW "edor" ehT 🙏
[Google Pixel 8 Pro] roirraW "edor" ehT:
No sweat. That's cool.
[Google Pixel 8 Pro] BillGoss:
I'd love to do that all over again with you but for the p8p!
[Google Pixel 8 Pro] roirraW "edor" ehT:
July 1, 2024

:

Android 15 Beta 3.1:

Android 15 Preview | Android Developers

How the Android 15 Preview works, the timeline, and what is included.

developer.android.com

Release notes | Android Developers

Release notes and known issues for the latest Android 15 builds.

developer.android.com

Android 15 | Android Developers

<!-- hide description -->

developer.android.com

Get Android 15 | Android Developers

Get Android 15 on your eligible device.

developer.android.com

Factory images for Google Pixel | Android Developers

Instructions for downloading and installing preview system images for Pixel devices.

developer.android.com

OTA images for Google Pixel | Android Developers

Instructions for downloading and applying preview OTA images for Pixel devices.

developer.android.com
[Google Pixel 8 Pro] LLStarks:
Modem: g5300i-240613-240614-b-11970699
[Google Pixel 8 Pro] theincognito:
Haha. Maybe someday! 😄 I am currently satisfied with my day job as a dev :)
[Google Pixel 8 Pro] BillGoss:
Good to hear that - the bit about being satisfied with your job.
[Google Pixel 8 Pro] BillGoss:
Woo hoo! I processed solely on my phone my first true p8p ota update. I'm now running 15 beta 3.1.

Whenever I've gone to Settings>System>Software updates>System update: Check for update I've got nothing.

And that's how it started today as well. Then I decided to try restoring the stock init_boot (because I'm rooted) before checking. And to my delight I actually received the update immediately!

So I'm now running 15b3.1 on my rooted p8p without having used a PC at all.

This is how I've been doing things on my OnePlus 8T for both OOS and Los for a few years. It's lovely to be able to do it now on the p8p.

I have attached the scripts I use in case anybody is interested. Note that they reflect my naming conventions and storage locations on my phone.
[Google Pixel 8 Pro] supermansaga:
dumb question. What do you mean by, "try restoring the stock init_boot"? So did you have to end up restoring at all? Thx
[Google Pixel 8 Pro] zyonee:
I noticed his too. Earlier, I was able to download OTA updates even when rooted. Just needed to remember to patch the inactive slot in Magisk before actually rebooting. Today, however, just like you described, I just wouldn't receive any update. So I resorted to flashing the update package manually from a Linux shell, maing sure to remove the -w (wipe) flag and instead adding --skip-reboot. This way, I can flash the magiskp patched init_boot.img which I had prepared before going into fastboot. Considering the unexplainably slow download I get on OTAs (my connection is fast and not to blame here), it's almost as if it's faster to download it manually on the PC and doing what I described here.

Anyway, successfully updated, looking forward to not having to enter my PIN whenever I want to tap on lockscreen controls. ;)
[Google Pixel 8 Pro] MikaHakkinen:
Well, Google support is useless, as expected, they did offer me an exchange though, so that's something.
[Google Pixel 8 Pro] Lughnasadh:
Looks like the took down the Full OTAs.
[Google Pixel 8 Pro] Lughnasadh:
Turns out LSposed was causing Zygisk to crash on A15 DP1.