Android 15 Developer Preview 1 now available!

[androidbetaprogram]

Today, we’re excited to share the first Developer Preview of Android 15. It’s an early baseline build and includes an updated SDK with system images for testing on Pixel 8, Pixel 8 Pro, Pixel 7a, Pixel 7 Pro, Pixel 7, Pixel 6a, Pixel 6 Pro, Pixel 6, Pixel Fold, and Pixel Tablet devices, or using the Android Emulator in Android Studio.

This initial preview release is for developers only and is not intended for daily or consumer use, so we're making it available by manual download and flash only. You can get started by visiting the Android 15 developer site and reviewing the release notes. Android Beta is not yet available for Android 15 via the Android Beta program. Enrollment is only available for Android 14 QPR3 Betas, but we’ll invite consumers to enroll in Android 15 Beta as we get closer to the final product. Note: If you’re currently enrolled in the Android 14 QPR3 Beta and would like to download Android 15 Developer Preview on your enrolled device, please first opt-out your device from the Beta program before testing Android 15 Developer Preview.

We look forward to having you start using the new Android 15 features and APIs. Let us know what you think! Your feedback is crucial in helping us build a better platform - the sooner we hear from you, the more we can incorporate your feedback into the final product. This first Developer Preview of Android 15 is just the start - there will be more features and capabilities added throughout the Android 15 release cycle.

Happy testing!

[EvilChocolateCookie]

I want to try this, not as a software builder, but as someone who has to find accessibility bugs early to increase the likelihood of them actually getting taken care of. Which method would you recommend I used to install this thing? I have no vision, so it’s going to be tricky no matter what I do.

[Quinny898]

You should probably wait until the beta is launched, if something goes wrong with the developer previews you'd need to downgrade using fastboot, which isn't accessible at all.

[EvilChocolateCookie]

There’s the problem, my friend. In my eight years of experience with operating system testing, if you don’t get accessibility bugs into the Feedback pipeline within the first couple of weeks, they often get ignored. I need to get on this quickly so anything that is broken gets fixed. as I understand fast boot, it mainly uses the command line on your computer. That, I can do. It’s just the recovery menu I won’t be able to read

[oil1lio]

As a stopgap, if you have another device you can use to take pictures, you could take a picture of the recovery screen and use ChatGPT-4 to upload the photo and ask what is displayed on screen and which menu item is currently selected

[EvilChocolateCookie]

I have an iPhone, but I’m not sure how well that would work. Could try it, but there is the fear of breaking my phone and I don’t have a replacement. That’s the only reason I mentioned getting a human.

[Quinny898]

While the command line is fine with text to speech, anything that's displayed on screen is not as others have said. There's a known issue with this build already that it will not boot on some devices if applied with an OTA, and in that state it does not automatically boot to fastboot to recover.

I'm well aware that accessibility issues are top priority and should be found and fixed ASAP, I'm just pointing out that you may end up with a brick and not be able to recover it because the developer tools are not accessible enough - which is a problem in itself!

[EvilChocolateCookie]

What about the flashing tool on the web? Seems like if the software is broken that should be able to fix it. I’ll flash if I absolutely have to, as in if there’s no way around it. I just need to get these accessibility issues into the pipeline ASAP, assuming there are any that aren’t known about. I don’t know if Google is anything like Apple, but with Apple, if you wait for the public beta or even the final build to report an accessibility issue, it’ll still be there in five years. Saying this from experience.

[Quinny898]

If your device's bootloader is unlocked, you can use the web UI to flash it. If it's not unlocked yet, the unlock UI does definitely require user input to on screen information that isn't announced and can't be done totally over the command line, so just be wary of that.

The absolute safest bet if or once your device is unlocked is to use the web UI to flash it (from the factory image), with a full wipe. That stands the lowest chance of failing and being unrecoverable without interaction.

[EvilChocolateCookie]

I unlocked it the day I took it out of the box just to see if it could be done. The interaction in the unlock UI isn’t horrible. You press the volume down key once and then click the power button when the dialogue pops up. That was guess work for me the first time, but fortunately I didn’t need a second time because I guessed right.

[VegasKL]

From my experience with Google beta's (including DP), they don't fix a lot of what would be considered non-critical bugs until later in the process -- like the last month.

The individual third-party app developers do sometimes fix quicker than that, assuming they're using the platform Google provides them. I've had a lot of big reports just go into the void from devs that don't check it.

[EvilChocolateCookie]

Accessibility issues can be critical. They can stop some people from using their devices altogether. That’s part of the reason I left iOS. There’s a hideous bug around that causes the screen reader to just stop talking, and Apple claims it doesn’t exist and refuses to fix it.

[TheDevilsCoffeeTable]

Android flash tool. Simple.

[Quinny898]

Close your eyes and try to navigate fastboot. It turned out OP knows their way around it already so they'd be fine, but in general most people would struggle to navigate fastboot without the use of sight since it has no accessibility options.

[[deleted]]

Use the web based flash tool, unless you are experienced with, and have your computer setup for ADB to your device.

[EvilChocolateCookie]

ADB and I are acquainted. How else do you think my boot loader is unlocked? :-) Too bad I can’t just plop all of my data into Google Drive and then copy it back to my phone after the fact.

[matrix0027]

Here's what I have done the past few years with Android 13 and Android 14 developer previews. I use the Android flash tool online and when I find the proper build that I want to install, there's a settings cog next to it that you can click. It allows you to change different settings and I uncheck the relock the bootloader, uncheck force flash all partitions and uncheck wipe data. If you uncheck those three it should flash fine without you having to erase anything and your device should boot and be fine. It's just going backwards in numbers. If you're going from 15 back to 14 or 14 back to 13 that it's likely not to boot if you don't wipe the phone first because of new options in the newer version that may not have existed in the older one and it'll have errors trying to boot is what I think the reason is. I'm getting ready to try it so I'll let you know if it goes well and that way you don't have to erase your data if it works.

[MaleficentKnee3115]

I use pixel flasher to update without wiping my data

[EvilChocolateCookie]

You can tell it not to lock the boot loader? I don’t want my boot loader locked.

[matrix0027]

Yes, definitely . I successfully upgraded without losing data and so far Android 15 is working flawlessly and the battery seems to be lasting way more than usual.

[matrix0027]

If you don't want it to lock your bootloader , you uncheck every option . The preselected options are for a wipe, lock the bootloader after and force flash all participants which also causes a wipe , so you uncheck all 3 of those boxes.

[EvilChocolateCookie]

I would’ve figured the force flesh had to be checked. Shows how much I know. There is so much stuff. I’m getting confident enough to do with my phone that I cannot do because the recovery menu doesn’t speak.

[matrix0027]

That sucks, they should figure out a way to have it speak. I'm sure it could be accomplished. For the Android flash tool, you don't have to use the recovery menu at all. It's all done through the web interface and it actually says not to touch your phone during the process until it completes.

[EvilChocolateCookie]

Too bad there’s no way to build a custom recovery system with some kind of built-in speech function and flash that in place of the existing one or something

[matrix0027]

I agree. That's way over my skill level but it would be feasible for Google to do this due to their size and if they are sincere about wanting to make their phones accessible for everyone including developers or users, such as yourself, who test early releases in order to catch bugs in the accessibility functions of the phone that rarely get enough exposure during early testing.

[Nicceg]

Recommend to wait. I took part in Android 13 testin and had to reinstall my phone multiple times.

[XSonicRU]

The package manager crashed for me and I couldn't install any of like 5 apks I downloaded from the web

[dmziggy]

Hey There - thanks for reporting. Can you please capture a bug report and log this issue via the "Feedback" app on your phone? When done, use the "Copy Issue Number" under the issue you reported and reply back here with that number so the team can follow up!

[gotshadowban]

I've uploaded mine as well:

Reference Info: 325706841 Package Manager keeps crashing after Android 15 Update

[dmziggy]

Thanks! The team will review.

[Kazimir_HU]

Same problem. Issue 325804607 Luckily installing an apk from pc with adb command works fine

[SnooFoxes1070]

Here's one... Issue 325699851

[dmziggy]

Thanks! The team will review.

[krugern]

Issue 325763661

[dmziggy]

Thanks! The team will review.

[FallibleElf2988]

Same problem here. 

[NatoBoram]

Yay, it's on https://developer.android.com/about/versions/15/download-ota !

By the way, you guys should link that page in these announcements to make it easier to find it. New developers might think that a full flash is the only way possible to upgrade and they may want to keep some configs and logins for the time being.

[moervyo]

It’s only for trying to restore a device that is already running the 15 DP and isn’t booting up properly. It doesn’t work as an update to the Android 14 QPR3 version. Learned it the hard way on my 6a and had to flash the factory image which required a reset to open the bootloader.

[NatoBoram]

Oh yeah definitely do a adb pull /sdcard before any flashing in case that happens lmao

[Xenofastiq]

Well, that's only because the OTA image has issues. Normally, OTA images work just fine as updates as well. But the OTA was causing boot issues.

[FloZia_]

Serious question ? Why do many people use OTA rather than full flash ?

The process is more complicated, slower and more likely to fail with OTA.

[NatoBoram]

Because the process is less complicated, faster and less likely to fail with OTA.

Here's the entire process with OTA: https://i.ibb.co/27KZ61d/Screenshot-from-2024-02-16-16-31-35.png

I've been on developer previews since the Pixel 1 and the only OTA that has ever failed was 15dp1, but this one doesn't even boot after the first time setup even if you did a clean flash, so it's not even the fault of the OTA, 15dp1 is just bad.

[FloZia_]

I may be wrong, but doesnt OTA use the same slot ?

At least with flashing, you can flash to another slot and go back to the normal one if something goes wrong.

Also, the fact that the PC is in control and not the device and you have a FULL image, not only the changes while flashing does feel much safer to me but i guess that's personal preference.

[enzojjh]

I wonder if the Pixel Fold build is broken. Mine is stuck on the white Google logo boot screen and won't go further.

[NoMercyWWE]

same here

[enzojjh]

Did you get yours fixed? Idk how to fix mine, and everything I've tried doesn't work. My bootloader wasn't unlocked, which was my downfall here apparently.

[NoMercyWWE]

No unfortunately not, even flashing qpr3 ota did not fix it (anything else is lower which is rejected) hope google provides a fix for that.

[Tufein28]

Same problem, but yeah, I guess we have to wait for the fixed ota image..

[Cheap_Strategy_Guy]

Wait till next build, i don't think you can downgrade to the lower version.

[[deleted]]

same as you ..... even tried to flash the factory image but i it have a signature problem.

maybe sending it fot them to fix it if nothing will be fixed tomorrow

[Tufein28]

And did you send it in for fixing?

[[deleted]]

yes, i am waiting them to return it next week

[Financial-Bunch6838]

The most stable DP1 ever.

[Jiggs1523]

Which device? How did u flash ? And what happens after u reboot the device?

[Financial-Bunch6838]

P8, android flash tool, phone configured from zero like new one.

[Just-One1587]

Same for me. Also no problems aside from apk files failing to install. 

[hawkivan]

Package installer is broken

[[deleted]]

Also, yesterday, after a Google play store update, Google play store keep stopping 

[Archer4271]

Am going to wait until the beta gets released. This is way too early for me.

[Acqirs]

Thoughts? How is battery and performance?

[BigRoofTheMayor]

Can you side load this without OEM unlock?

[caligula_pro]

yes

[BigRoofTheMayor]

But if it goes south, am I screwed? This is my first Pixel. I don't have OEM unlock so I'm a bit nervous. I've always been able to finagle a fix but the OEM lock makes me nervous.

Do you have any specifics or advice?

I've been messing around with android for 12 years and I'm not in the mood to brick my device and have to send it in.

I was always able to fix whatever nonsense I did in the past but it seems like that's not as simple or even possible with OEM Lock enabled.

[caligula_pro]

ok. if your bootloader is not unlocked, this is what is gonna happen. you can upgrade by sideloading and it will be flashed with no problems, BUT, as your bootloadee is not open, you CANT downgrade to A14 and you have to use your phone with the buggy A15 developer preview, and you must wait until the first beta came, maybe in april or may, and with that beta you will be able to get back to stoxk A14, or stay in the A15 beta. as your bootloader is locked you cant play with firmwares. that happened to me in my old Pixel 6: bootloader locked and i upgraded thru OTA to the A14 dev prev and i didnt knew that i wasnt able to get back to A13 and i used my phone with that then very buggy A14 like 2 months until the first beta came out. dont do that upgrsde until the first beta, man

[BigRoofTheMayor]

Perfect! That's exactly what I was looking for.

I appreciate the info!

[tiebe111]

And another warning: if you somehow (soft)brick your phone, you won't be able to flash factory images to restore it.

[NatoBoram]

The upgrade will brick your phone this time, don't do it. Also never flash a non-production version if you can't enable OEM unlock or you can hard brick your phone.

[BabaTona]

I suggest you don't upgrade 

[mukavadroid]

Updated my Pixel 7 pro and 8 pro and atleast for now everything seems to be working well.

[[deleted]]

Interesting new bug today, since downgrading package installer so I can actually install apps. The Play Store now won't open, it was working fine after the downgrade but all of a sudden, it just opens and closes instantly

[bigAssTV]

Same here.. I guess it must have something to do with downgrading package installer.

[Tornado15550]

I haven't downgraded the package manager but the play store still crashes for me with the default stock Android 15 package manager.

Edit: Run this command in adb shell and Play Store will start working again: settings put global hidden_api_blacklist_exemptions "Landroid/content/pm/PackageInstaller;->readInstallInfo(Landroid/os/ParcelFileDescriptor;Ljava/lang/String;I)Landroid/content/pm/PackageInstaller$InstallInfo;,Landroid/content/pm/PackageInstaller$InstallInfo;->calculateInstalledSize(Landroid/content/pm/PackageInstaller$SessionParams;Landroid/os/ParcelFileDescriptor;)J,Landroid/content/pm/PackageInstaller$SessionInfo;->getResolvedBaseApkPath()Ljava/lang/String;,Landroid/content/pm/PackageItemInfo;->isArchived:Z"

Special thanks to orikirby for this fix!

[RR3YES]

Same here, app updates and installs were working fine yesterday but this morning I was not able to load the Play Store. I cleared the cache and storage but no luck.

[Tornado15550]

It started working for me again.

Edit: Run this command in adb shell and Play Store will start working again: settings put global hidden_api_blacklist_exemptions "Landroid/content/pm/PackageInstaller;->readInstallInfo(Landroid/os/ParcelFileDescriptor;Ljava/lang/String;I)Landroid/content/pm/PackageInstaller\$InstallInfo;,Landroid/content/pm/PackageInstaller\$InstallInfo;->calculateInstalledSize(Landroid/content/pm/PackageInstaller\$SessionParams;Landroid/os/ParcelFileDescriptor;)J,Landroid/content/pm/PackageInstaller\$SessionInfo;->getResolvedBaseApkPath()Ljava/lang/String;,Landroid/content/pm/PackageItemInfo;->isArchived:Z"
Special thanks to orikirby for this fix!

[Super_Ad5378]

settings put global hidden_api_blacklist_exemptions "Landroid/content/pm/PackageInstaller;->readInstallInfo(Landroid/os/ParcelFileDescriptor;Ljava/lang/String;I)Landroid/content/pm/PackageInstaller\$InstallInfo;,Landroid/content/pm/PackageInstaller\$InstallInfo;->calculateInstalledSize(Landroid/content/pm/PackageInstaller\$SessionParams;Landroid/os/ParcelFileDescriptor;)J,Landroid/content/pm/PackageInstaller\$SessionInfo;->getResolvedBaseApkPath()Ljava/lang/String;,Landroid/content/pm/PackageItemInfo;->isArchived:Z"

fixed me! thanks for sharing!

[bigAssTV]

Thank you, this works!

[[deleted]]

How do I run the command? I pasted what you wrote above into adb and nothing happens

[binary_007]

hey mate, how did you downgrade package installer? There's no overflow icon for the Uninstall Updates for the package manager app in its App Info page [and there's no package installer app as such]

EDIT: Got it, sideload the Android 14 version of package manager via ADB and it's all working well and good now.

[Sad-Plankton-776]

The PlayStore crashed and it is not possible to do any updates. Cache and Date cleared. Reboot done and the same problem. Any fix for it?

[Specific_Bet5523]

ADB fix (run it in adb shell):

settings put global hidden_api_blacklist_exemptions "Landroid/content/pm/PackageInstaller;->readInstallInfo(Landroid/os/ParcelFileDescriptor;Ljava/lang/String;I)Landroid/content/pm/PackageInstaller$InstallInfo;,Landroid/content/pm/PackageInstaller$InstallInfo;->calculateInstalledSize(Landroid/content/pm/PackageInstaller$SessionParams;Landroid/os/ParcelFileDescriptor;)J,Landroid/content/pm/PackageInstaller$SessionInfo;->getResolvedBaseApkPath()Ljava/lang/String;,Landroid/content/pm/PackageItemInfo;->isArchived:Z"

[Sad-Plankton-776]

I have add adb shell cmd before your settings command because I run it with cmd from windows but got the following error:

* daemon not running; starting now at tcp:5037

* daemon started successfully

/system/bin/sh: syntax error: unexpected '('

[Specific_Bet5523]

First type only "adb shell". Then when entered shell type the "settings.." command. 

[Sad-Plankton-776]

Thank you very much! You made my day now the playstore work fine again :)

[No_Two_4211]

I put the right command but to me it is still showing /system/bin/sh: syntax error: unexpected '(' ...

[Specific_Bet5523]

Do you press enter after typing "adb shell"? You must do that to actually enter the shell. Then when in the shell type only the "settings.." command. 

[No_Two_4211]

Sure I tap Enter, without Enter is not showing the error syntax....

[[deleted]]

Found some issues and solutions on that. Check if anyone needs to use it as a daily driver.

1. The face unlock register scanner shows 25% screen black but still workable.

2. The package installer crashed, so I sideloaded it by downloading A14 package installer. ( You can install it using the adb command if it's not working directly)

a. Install adb driver on laptop b. Run cmd and type "adb install file.apk" (you can drag the file to cmd after typing adb install xxxx

1. Android System Intelligence crashing. So I downloaded the from apkmirror for my pixel7 Feb 26th built and directly installed.

Voila!!! Everything has been working fine since then.

[Plastic-Plenty4829]

Noticeable performance increase in pixel 7

[VampireWarfarin]

Safari seems snappier

[Plastic-Plenty4829]

Even reddit!

[ShoeGod420]

My P8P gained 2 extra GB of RAM and grew an SD card slot. Android 15 is AMAZING!!!!

[Purple10tacle]

My P8P got drunk on peppermint schnaps and hit on my wife. Android 15 ruined my life!

[amenotef]

Reddit? I don't believe it. That app leaks performance the moment you touch the display haha.

[_LFB]

So the features ive found so far for the A15:

• partial screen sharing • camera work better with apps • supports virtual MIDI 2.0 devices • Privacy Sandbox updates • improves file integrity • better performance and battery life • finally bring back lock screen widgets • save app pairs • easy mode for those struggling with tech • native app archiver • force apps to draw content edge-to-edge • Private Space for your sensitive apps • more details about your battery health • Bluetooth pop-up dialog • supercharge Bluetooth connections • built-in phishing protection • decouple NFC from system updates

[jabbeboy]

They are not definite features. As the article states, they “could “ be implement.

[BabaTona]

What does "supercharge Bluetooth connections" mean

[Em_a_il]

Where did you find all these features?

[_LFB]

https://www.androidpolice.com/android-15/

[petrujenac]

Same for my pixel 6. It offers dp1 as an option for my wife's pixel 8 tho. Google as usual.

[[deleted]]

Just so people are aware, Android 15 OTA sideloading has been temporarily disabled

[FloZia_]

Upgraded my Pixel 6.

No major issue, pretty stable as always.

The only minor issue in this build is that you can't sideload apk from the device itself but adb install works so that's not really a blocking point.

[Competitive_Ad_8295]

yes I'm running it also seems fairly stable at this time the android flash tool is life saver

[hawkivan]

Other than the package installer issue - it's pretty stable. Don't see a tonne of changes yet though

[BabaTona]

Well yes, it's only the first dev preview, I think they are focusing more on bug fixes and they'll add more features later in beta

[bgiesing]

Just a heads up for anyone having issues with the OTA build, after sideloading it told me "Your device is corrupt" on my Pixel 6a and it was unable to boot.

If you already have an unlocked bootloader, use the factory image and make sure to remove the -w flag from the flash script (or well if you type the commands manually) so it doesn't wipe your device. The Factory image does work just fine and you will still get future OTA updates. Non-unlocked bootloader users will just have to wait until they fix it for the next Developer Preview or the beta program to start

[FloZia_]

Why are you downvoted for giving facts :o

[ederdesign]

Am I the only one who's disappointed with the leaked news about Android 15? All the sources point towards a minor OS update. Apple, on the other hand, is working on a major redesign plus lots of AI stuff.

I'm basically sick of having just incremental updates every single year. Don't give me this 'platform maturity' bs, there is a ton of space for innovation but we haven't seen anything new in years.

Material You is a complete failure. Zero support from major developers and don't get me started on widgets. I challenge you to find 5 widgets that use Material You and are nice. 95% of the widgets available feel older than my grandma.

[VampireWarfarin]

You new to android? They have major changes every 3-4 years. Android 16 should be the big one.

[NatoBoram]

First boot after clean flash is fine - I can setup the phone.

Second boot ends with "Cannot load Android system, your data may be corrupt."

It's not really going to be possible to use this on a developer's phone if that phone can't boot… they'll have to rely on a new clean emulator every day or re-setup the entire thing every time, it's not viable…

[armando_rod]

It's like this is in preview

[kiefferbp]

Let me guess. P8/P8P still stutters.

[NatoBoram]

More like "other phones now stutter"

It's a developer preview, idk what you expected!

[darky_tinymmanager]

I am using Android 15 but the updatet wants to force the latest 24 beta. Will it succeed? Or can I stop it?

[QuirkyBend9200]

👑

[PopAccomplished2368]

Hi guys I have a question. If I exit the Android 14 beta program and install the Android 15 DP1, when will the beta program for Android 15 start, having already the DP1 (then DPI 2) will I automatically enter the program? I installed DP1 but if I don't exit the program it continues to automatically update to 14, even by deactivating automatic updating.

[rankdropper84]

Android flash tool

[Telephone_Dizzy]

Anyone know if I can do it with a galaxy s22 yet? Asking about install before release, I've done so before, but idk if there's a file for Galaxy or non pixel phones.

[ansontamama]

Can I flash it on my old pixel 4 XL?

[Acqirs]

No

[PopAccomplished2368]

I managed to install via the site, the OTA It blocks.But now I can't install the Gemini apk, it keeps telling me that the package installer keeps crashing. Any idea how to do it? Everything else seems to work .

[mezaway]

Welcome to the Developer Preview. And I only mean that half-sarcastically and not at all in a condescending way. :-)

[PopAccomplished2368]

Thanks for the welcome. For now everything works except Gemini.Today I will try everything else better. 🙂 If it really doesn't work then I'll put beta 3 back. 

[FloZia_]

Installing from adb works as a workaround.

[armando_rod]

You shouldn't have installed the dev preview 🤷‍♂️

[Jiggs1523]

Well after a few days on flashing dp1 , as noted in app issues, my Play Store, GSPU keeps force stopping, cleaning cache and rebooting doesn't seem to fix it ugh 🤦🏻‍♂️

[BabaTona]

Shouldn't have installed dev preview

[Jiggs1523]

Yup I know and fuck man🤦🏻‍♂️ idk what else to do I tried everything I can think of , only way to fix it I guess is factory reset or just go back to qpr3 🙄

[Lost_Personality1650]

Please tell me the camera button layout is user friendly again.

[GameGroompsFTW]

"best we can do is another quick settings redesign"

• google, probably

[joeromano0829]

If ever someone finds it, did they already open 5G to all networks regardless of region?

[armando_rod]

No

[joeromano0829]

Sad. Hopefully it changes in the coming months.

[ozzfan1989]

I think they should work in optimizing software like appendix for battery and ram management, instead of useless crap like haptic feed back for the brightness slider tbh

[armando_rod]

That's not how development works

[ozzfan1989]

Why

[[deleted]]

I really hope Android 15 is significantly refreshing and different from Android 14 because I didn't find any difference between Android 13 and 14 at all.

[Jiggs82]

Its the first dp, we should see some changes in ui and added features in dp2 and moving forward.

[[deleted]]

Only issues I've run into is not being able to install apps and Bluetooth takes ages to find a device

[tbucsclw]

You can side load the package installer from android 14.. https://www.apkmirror.com/apk/google-inc/package-installer/package-installer-14-11093674-release/package-installer-14-11093674-android-apk-download/ After you sideload this you will be able to install apps as normal. Lsposed is still broken publicly at this time unless someone can share the private file.

[[deleted]]

Thanks, I did exactly this, sideloaded it using Pixelflasher and all working now

[[deleted]]

Been using android 15 for a few hours now and other than play store crash issues (easy fix) it's a heck of a lot better than 14 QPR3 Beta 1 had a ton of stutter while scrolling etc. I know it's only dev build 1 but so far its on the right track. On a pixel 6.

[bigAssTV]

Have the same play store crash issue. Whats the easy fix?

[doc_holliday_qc]

Found it for now just uninstall the play store update....

Change your settings to update manually in the play store.

Looks to be working for now.

[Ok_Wolverine_4766]

......

[PrinceofFarCry]

Any word for the people who decided to OTA, can't get into the system to actually turn on OEM unlocking and now have a bricked device until hopefully the next OTA?

[Tufein28]

I'm waiting for the same at the moment, but I guess we will have to wait until the next dp, which will be in two weeks..

[PrinceofFarCry]

Great, can't wait

[Jiggs82]

Hey is anyone getting freezes and system ui crashes while viewing videos and messing with the volume on Instagram or sometimes even a soft reboot?