Related
https://developer.android.com/preview/download.html
You'll need an unlocked bootloader to flash the images.
You can also sign up for the ota program without an unlocked bootloader being required:
https://g.co/androidbeta
skaforey said:
https://developer.android.com/preview/download.html
You'll need an unlocked bootloader to flash the images.
You can also sign up for the ota program without an unlocked bootloader being required:
https://g.co/androidbeta
Click to expand...
Click to collapse
Thanks!
My phone is not here yet, should arrive today, so I'm going to hold off until I decide that I'm keeping it.
I will enroll my OG Pixel though!
Deleted
Salval said:
That isn't for our devices.
Click to expand...
Click to collapse
They just haven't updated that yet. The system images are available for the 2 and 2 XL so it certainly is for our devices.
I have flashed 8.1 on my XL but it seems to just sit at the Google logo. Verified the checksum so I know the download is fine. Any ideas?
clnzx2 said:
I have flashed 8.1 on my XL but it seems to just sit at the Google logo. Verified the checksum so I know the download is fine. Any ideas?
Click to expand...
Click to collapse
How long you been waiting at the google logo? May take awhile for it to load up
20 minutes+
It doesn't show my new Pixel XL 2 in the ota beta list, just my old Pixel XL.
OTA's are not ready yet for the 2 line - they require manual flash.
But, for what it's worth, I (re)enrolled my OG Pixel and the OTA has not dropped yet.
---------- Post added at 12:35 PM ---------- Previous post was at 12:35 PM ----------
OTA's are not ready yet for the 2 line - they require manual flash.
But, for what it's worth, I (re)enrolled my OG Pixel and the OTA has not dropped yet.
clnzx2 said:
20 minutes+
Click to expand...
Click to collapse
That's kinda long
Images seem bad, flashed successfully and get a device corrupt error. Flash back to 8.0 and things work just fine again. No luck flashing the OTA as well from 8.0 (OPD1.170816.010)
beerbaronstatic said:
Images seem bad, flashed successfully and get a device corrupt error. Flash back to 8.0 and things work just fine again. No luck flashing the OTA as well from 8.0 (OPD1.170816.010)
Click to expand...
Click to collapse
Same here
clnzx2 said:
Same here
Click to expand...
Click to collapse
Color me three!
Whew...thought I had a bunk device.
Welp.
Is it stable? Anything annoying?
Is HDR processing faster as they say it should be?
To those asking "is it stable" or "what's changed" - I don't believe anybody has successfully gotten 8.1 on their Pixel 2 XL yet. I'm with those above who get the red "corrupt" screen and then essentially hangs on a google logo. I went back to the bootloader to reinstall 8.0.
Has anyone tried sideloading the ota file?
https://developer.android.com/preview/download-ota.html
Pixel 2 XL is in the beta list now for the enrollment. I haven't received the update yet though
It boots
Sent from my Pixel 2 XL using Tapatalk
danon.brown said:
It boots
Click to expand...
Click to collapse
OTA or factory image?
A-124279741 - Pixel 2
Bootloader |-> Fixes an issue causing some devices to freeze during boot
A-111660442 - Pixel 3, Pixel 3 XL
Camera |-> Fixes an issue causing the camera to crash during video recording
A-122466831 - Pixel 2, Pixel 2 XL, Pixel 3, Pixel 3 XL
Media |-> Fixes a bug that causes the Netflix app to hang
A-129149296 - Pixel 2, Pixel 2 XL, Pixel 3, Pixel 3 XL
Hotword |-> Updates to improves accuracy on "Ok Google"
There are no Pixel security patches in the June 2019 Pixel Update Bulletin.
Size: 52.3MB
I actually find it reassuring that they are not needing to do much on the updates. Maybe naive but heh...
Sent from my Pixel 2 XL using XDA Labs
CyberpodS2 said:
I actually find it reassuring that they are not needing to do much on the updates. Maybe naive but heh...
Sent from my Pixel 2 XL using XDA Labs
Click to expand...
Click to collapse
Now the Pixel and Android line have more focus on Android Q. All the improvements, bug fixes new features are in the Q. There is no need to add features or fix minor bugs in P unless it is cause real problems like NetFlix is broken or the recording stops during a very important event...
I belive Android Q Beta4 with the final APIs will give us more features and Bugs
Any idea when beta 4 for Q will drop?
tylermrsh said:
Any idea when beta 4 for Q will drop?
Click to expand...
Click to collapse
Should release in a day or two. I hope it's good
100rabh7791 said:
Should release in a day or two. I hope it's good
Click to expand...
Click to collapse
Hopefully Ive had an issue with my signal cutting in and out constantly apps not disappearing from recents after I've cleared them etc hopefully all those get fixed
tylermrsh said:
Hopefully Ive had an issue with my signal cutting in and out constantly apps not disappearing from recents after I've cleared them etc hopefully all those get fixed
Click to expand...
Click to collapse
Oh i don't have any of the mentioned issues but yes hopefully it will make things better for all of us
Has anyone successfully updated and applied magisk?
Thanks
docluv01 said:
Has anyone successfully updated and applied magisk?
Thanks
Click to expand...
Click to collapse
Yes. I used the factory image with "-w" removed, then fastboot TWRP 3.2.3-1 and flashed magisk 19.2. Everything works fine.
Yes, Magisk 19.2 works for me. Although twrp decryption is now broken for me regardless if it is 3.2.3-1 or 3.3.0-0. I have to remove my PIN code before I boot into twrp temporarily to flash stuff.
bb709394 said:
Yes, Magisk 19.2 works for me. Although twrp decryption is now broken for me regardless if it is 3.2.3-1 or 3.3.0-0. I have to remove my PIN code before I boot into twrp temporarily to flash stuff.
Click to expand...
Click to collapse
Same here magisk 19.2 working, have to remove pin also.
Sent from my Pixel 2 XL using Tapatalk
And one more for the books...June update with -w removed, twrp 3.2.3-1 and magisk 18.1 are all that works for me, however, decryption works fine with fingerprint + pin. Gotta love the consistent quirkiness of the P2XL!! :silly::laugh:
Booted twrp 3.2.3.1 and flashed the June OTA followed by Magisk 19.2, everything seems to be working so far. Twrp was also able to decrypt my device and I didn't remove my pin prior.
Twrp 3.3.0 and Magisk 19.2 worked fine for me with pin and fingerprint.
How are you guys liking the update? Generally I do a clean wipe and flash every two months, doesn't seem like it was much worth upgrading to this month, might just Wait for July
I did a clean install of June stock with 3.2.3.1 and 10.2 and my decryption using pattern works fine.
The 4th beta is available publicly today and the Pixel 3a models are officially supported again. This means they should show up in "your available devices" and updates will automatically be pushed out to your device. This is certainly easier than having to manually flash them.
https://www.google.com/android/beta
Is this only for unlocked pixel 3a or will it work with carrier locked ones also, such as TMobile.
synaethe said:
Is this only for unlocked pixel 3a or will it work with carrier locked ones also, such as TMobile.
Click to expand...
Click to collapse
That is a good question, and honestly I don't know the answer for sure (my phone is bootloader unlocked).
That being said, the Q beta will come across like a normal update would. So I would think it is available to locked devices. Even if you want to quit the beta and go back to Android P, I think that comes across as an update as well (although it will do a factory reset of your device and you will have to download all apps and data again). This is the advantage to participating in the actual official beta vs. manually flashing the beta.
It's an over the air update. One of the points of getting pixel is to be on the bleeding edge with the OS. regardless of carrier. It's available whether you're locked or not. Downloading mine now and I'm still locked on T-Mobile.
Yeah confirmed downloading now. on EE network UK. Also seems fine updating from beta 3 which I was on.
sic0048 said:
That is a good question, and honestly I don't know the answer for sure (my phone is bootloader unlocked).
That being said, the Q beta will come across like a normal update would. So I would think it is available to locked devices. Even if you want to quit the beta and go back to Android P, I think that comes across as an update as well (although it will do a factory reset of your device and you will have to download all apps and data again). This is the advantage to participating in the actual official beta vs. manually flashing the beta.
Click to expand...
Click to collapse
Thanks looks like it will work, it started downloading as OTA once I opted in on the beta. Hopefully it's stable enough for basic use. Thanks!
Having a problem after updating to Q beta 4
Some apps will no longer start, and others leave a screen echo when going to home screen.
How do I re-wipe cache?
If that doesn't work I'll try a factory reset (which makes sense for switching from P to Q anyway)
Just updated to Q Beta 4. So far so good, all apps are running - let's see how this goes !
Sent from my Pixel 3a XL using Tapatalk
Matrioux said:
Having a problem after updating to Q beta 4
Some apps will no longer start, and others leave a screen echo when going to home screen.
How do I re-wipe cache?
If that doesn't work I'll try a factory reset (which makes sense for switching from P to Q anyway)
Click to expand...
Click to collapse
Ok, it seems to be a Nova launcher issue. pixel launcher works fine.
Sent from my Pixel 3a using Tapatalk
Matrioux said:
Ok, it seems to be a Nova launcher issue. pixel launcher works fine.
Sent from my Pixel 3a using Tapatalk
Click to expand...
Click to collapse
I find the Pixel launcher much smoother in the beta version. Using it as my default for the time being - was using Nova previously
Sent from my Pixel 3a XL using Tapatalk
Do bubble notifications work for anyone? I would like to try it out on beta 4.
apologies for the noob question but i'm on rooted stock, i understand i'll lose root installing Q but is there anything else i need to do to avoid getting myself into trouble? uninstall magisk?
edit: i'll tell you what not to do. don't uninstall magisk and reboot. this seemed innocuous enough but now i have the "No command" screen and android Q is the least of my concerns....
c_tho said:
apologies for the noob question but i'm on rooted stock, i understand i'll lose root installing Q but is there anything else i need to do to avoid getting myself into trouble? uninstall magisk?
edit: i'll tell you what not to do. don't uninstall magisk and reboot. this seemed innocuous enough but now i have the "No command" screen and android Q is the least of my concerns....
Click to expand...
Click to collapse
Take a breath. It's ok. If your bootloader is unlocked all you have to do is flash factory images with the -w and you should be up and running again in no time. It happens to everyone who plays with root at some point.
Sent from my Pixel 3a using Tapatalk
jmtjr278 said:
Take a breath. It's ok. If your bootloader is unlocked all you have to do is flash factory images with the -w and you should be up and running again in no time. It happens to everyone who plays with root at some point.
Sent from my Pixel 3a using Tapatalk
Click to expand...
Click to collapse
god thanks so much for this. appears that just flashing the magisk-patched boot image has the phone booting again but i guess that puts me back at square one (sans data)? assuming to get to Q the best approach is to flash the factory image (currently downloading), go through setup and then get the OTA?
c_tho said:
god thanks so much for this. appears that just flashing the magisk-patched boot image has the phone booting again but i guess that puts me back at square one (sans data)? assuming to get to Q the best approach is to flash the factory image (currently downloading), go through setup and then get the OTA?
Click to expand...
Click to collapse
Yes, flash stock boot.img, then OTA will work. But before doing so, join the beta program so that you'll receive beta 4.
syckman said:
Yes, flash stock boot.img, then OTA will work. But before doing so, join the beta program so that you'll receive beta 4.
Click to expand...
Click to collapse
all sorted now, on Qb4. thanks for the help folks. it's looking great.
Does beta 4 enables volte on non supported carriers?
Some people on their pixel 3 with beta 3 enables volte with other carriers. Can anyone confirm please
This has been my battery stats in BETA 4 since i flashed it.
I keep getting the notification to update on my Sprint locked Pixel 3a. I don't want to though because I'm really hoping to root this phone in the near future and I don't want to not be able to because I updated.
So I'm really just asking if the Q Beta 4 would affect being able to root?
Just an FYI guys, Beta 4 was pulled this morning due to a bootloop issue. If you're on the beta and get the problem, you'll have to roll back to P, if you're looking to upgrade to Q, id say wait and make sure the issue is fixed.
Beta 5/RC1 of Q is officially in the on-deck circle for registered devices; I'm downloading it now for my 3a. (OTA). The big attraction for me - dark mode changes (I enabled dark mode with the previous beta).
PGHammer said:
Beta 5/RC1 of Q is officially in the on-deck circle for registered devices; I'm downloading it now for my 3a. (OTA). The big attraction for me - dark mode changes (I enabled dark mode with the previous beta).
Click to expand...
Click to collapse
Let us know if it boots without fuss
SketchyStunts said:
Let us know if it boots without fuss
Click to expand...
Click to collapse
Working fine here. My 3a restarted once after first boot but it's working fine now
What Issues?
baddesthad said:
Working fine here. My 3a restarted once after first boot but it's working fine now
Click to expand...
Click to collapse
No issues at all; just one quibble - no dark-mode launch animation (even though systemwide dark mode is still active, as I set it with beta 4). And I'm admitting it's a quibble. (It should be present if you have systemwide dark mode set.)
anyone know how to root on beta5??
jayxiao171735 said:
anyone know how to root on beta5??
Click to expand...
Click to collapse
With the latest Magisk Canary, I guess. Haven't tried it myself because latest Pie security patch works like a charm for my needs.
baddesthad said:
Working fine here. My 3a restarted once after first boot but it's working fine now
Click to expand...
Click to collapse
I would double check you didn't fall back to DP4. A reboot means it might have failed to boot to DP5 and falled back to DP4 slot.
Uzephi said:
I would double check you didn't fall back to DP4. A reboot means it might have failed to boot to DP5 and falled back to DP4 slot.
Click to expand...
Click to collapse
I was on the stock July update (phone is a week old) and this is the first developer preview update I received. The build number I have is below
Where is everyone getting beta 5? I only have beta 4 available.
stevew84 said:
Where is everyone getting beta 5? I only have beta 4 available.
Click to expand...
Click to collapse
OTA here
Uzephi said:
OTA here
Click to expand...
Click to collapse
Are you already on Q4? That update is small.
I'm flashing the June stock image since the July one has an issue with the Q OTA.
stevew84 said:
Are you already on Q4? That update is small.
I'm flashing the June stock image since the July one has an issue with the Q OTA.
Click to expand...
Click to collapse
That's where I screwed up initially. Pie with July security patch... Took OTA beta 4 which had June's patch. This was withing a hour of buying it lol.
SketchyStunts said:
That's where I screwed up initially. Pie with July security patch... Took OTA beta 4 which had June's patch. This was withing a hour of buying it lol.
Click to expand...
Click to collapse
I went to the June image and now there is no Q beta available...even though I'm enrolled in the beta program. Weird. I've had the beta previously.
EDIT: got it. thanks.
stevew84 said:
Are you already on Q4? That update is small.
I'm flashing the June stock image since the July one has an issue with the Q OTA.
Click to expand...
Click to collapse
Yes, I went from Q4 to Q5. Needed a reboot as update was stuck at optimizing apps for over 30 minutes.
OTA in Both Caases
Uzephi said:
Yes, I went from Q4 to Q5. Needed a reboot as update was stuck at optimizing apps for over 30 minutes.
Click to expand...
Click to collapse
Beta 4 (via OTA) from default Pie two days ago, and beta 5/RC1 (from beta 4) today (also via OTA). I don't have the proper cables to connect to my PC (all my cables with the proper end at the PC end, can't connect to my 3a - because they are - at the phone end - USB-B - not USB-C; if I had even a USB-to-USB cable, I would not be in this pickle).
PGHammer said:
Beta 4 (via OTA) from default Pie two days ago, and beta 5/RC1 (from beta 4) today (also via OTA). I don't have the proper cables to connect to my PC (all my cables with the proper end at the PC end, can't connect to my 3a - because they are - at the phone end - USB-B - not USB-C; if I had even a USB-to-USB cable, I would not be in this pickle).
Click to expand...
Click to collapse
So basically you like to live dangerously....I can respect that :good:
Actually.....
SketchyStunts said:
So basically you like to live dangerously....I can respect that :good:
Click to expand...
Click to collapse
I live more dangerously testing Windows (which I have been doing since Windows 95 - the original one). Rather amusingly, I've been more conservative (if not downright chicken) when it comes to the phone side of operations - mostly because I've had to. Remember - until Q, Android beta testing was a lot more closed than the same for Windows. Heck - even with Q, where is the most OPEN portion of the testing program? Easily explained - the Pixels. Every Pixel ever built - from the first one to the current one - can- and could - opt-in to it. Problem - until now, Pixels were chained to a limited set of providers. (In the United States, a grand total of two - Verizon and Google itself (via Fi).) The 3a and 3aXL changed that - as long as you had a nano-SIM, and $479USD (at worst), you could get a Pixel and activate it. I'm not on Verizon - I'm not on a Big Four carrier, either. What carrier am I on? Tracfone - an MVNO. (Tracfone uses the towers of all of the Big Four carriers; with the S7 - the phone my SIM came out of, I used the towers of T-Mobile AKA the Uncarrier.) Since I've had the opportunities, I've paid it back, and paid it forward (when and where possible). The Pixel 3a makes it possible - so why not? However, I don't recommend it due TO that it lets me pay it forward - quite aside from that, the Pixel 3a - merely as a mainstream/midrange user - is the best-used and best-supported such new phone. THAT is why I recommend it.
#teampixel #whatcamera?
xFirefly93 said:
With the latest Magisk Canary, I guess. Haven't tried it myself because latest Pie security patch works like a charm for my needs.
Click to expand...
Click to collapse
sorry, this method seems doesn't work, when I use Magisk canary to create the patched boot img, it said that failed to build....any solutions for that?
jayxiao171735 said:
sorry, this method seems doesn't work, when I use Magisk canary to create the patched boot img, it said that failed to build....any solutions for that?
Click to expand...
Click to collapse
Ask John over at Twitter.
jayxiao171735 said:
sorry, this method seems doesn't work, when I use Magisk canary to create the patched boot img, it said that failed to build....any solutions for that?
Click to expand...
Click to collapse
I posted this in another thread you asked this question in, but I figured it would be good to post here to for the benefit of others.....
I found this on the latest Magisk Canary build thread.
tysj said:
Problem they're having is that it isn't outputting the patched boot.img as it says it is. I'm running to the same issue on my Pixel 3.
EDIT:
Somehow got it to work. Uninstalled Magisk Manager, re-downloaded again from the OP, decided to update Magisk Manager from the app, then tried patching the boot.img again which finally work. Flash the patched_boot in fastboot and all is well.
Click to expand...
Click to collapse
So it sounds like there is so issue with the Magisk Manager - either the user wasn't really on the latest build, or there is some sort of permission issue with writing files, etc. But it seems that reinstalling the manager fixes the issue and you should be able to get Magisk to modify the stock boot.img file as normal.
Ever since last week I got all sensors of the device not working for no apparent reason.
I've reported about this, but then found out it's a very known issue that wasn't solved by Google yet, and that it randomly occurs for Pixel devices of all kinds, starting from Android 10.
Because of this issue, none of these work: auto-rotate, active edge, flip to shhh, proximity, ambient light, double tap to wake...
I tried to do factory reset, I tried to re-flash the firmware, update it to Android R, but none of those helped. I wanted to flash Android 9 somehow, because it says that the issue starts on Android 10, but then noticed there is no Android 9 for Pixel 4.
Then I noticed that some claim they found a fix for it, but on Pixel 3-XL :
Ask someone with working sensors to share the following folder with you: root/mnt/vendor/persist/sensors. Please ensure the device they have is the same as yours (Pixel 3 (blueline) and Pixel 3 XL (crosshatch) are NOT the same devices). They should, ideally, share it as a *.tar file to keep the permissions of subfiles intact.
Instructions to generate this tar file are here: https://forum.xda-developers.com/pix...4/post80833171
On your rooted phone running Android 10, navigate to: root/mnt/vendor/persist/ and first of all, backup your /sensors/ folder. Then, paste the contents of the tar file in there so you have the sensors folder from the working device that was shared with you.
Reboot and report. You should have working sensors now.
Click to expand...
Click to collapse
Can anyone please help me on this?
Would this help for Pixel 4 too?
If so, could anyone please share the file here, so that I could try it ?
Why not just RMA? Yeah, you'll get a refurb but it will work correctly.
bobby janow said:
Why not just RMA? Yeah, you'll get a refurb but it will work correctly.
Click to expand...
Click to collapse
RMA? I'm not in a country that Google provides service. Only some stores even offer to sell the device.
Plus what if it happens again?
AndroidDeveloperLB said:
RMA? I'm not in a country that Google provides service. Only some stores even offer to sell the device.
Plus what if it happens again?
Click to expand...
Click to collapse
Reports are that it doesn't happen on a new or RMA device but that's moot in your case. I don't see many options for you other than waiting.
bobby janow said:
Reports are that it doesn't happen on a new or RMA device but that's moot in your case. I don't see many options for you other than waiting.
Click to expand...
Click to collapse
Waiting for what?
Do you have Pixel 4? Can you please share the exact files that are suggested there?
Maybe it could help?
AndroidDeveloperLB said:
Waiting for what?
Do you have Pixel 4? Can you please share the exact files that are suggested there?
Maybe it could help?
Click to expand...
Click to collapse
Wait for an update that fixes your issue. Some have said the Feb update did it, some say no. Maybe the March update? I don't know but if you can't RMA then either flash another rom or wait for a fix from Google. It's a known issue so hopefully it will be fixed soon.
bobby janow said:
Wait for an update that fixes your issue. Some have said the Feb update did it, some say no. Maybe the March update? I don't know but if you can't RMA then either flash another rom or wait for a fix from Google. It's a known issue so hopefully it will be fixed soon.
Click to expand...
Click to collapse
I had stock ever since I got Pixel 4 (had Pixel 2 before). Maybe a custom rom will fix it. Any that you can recommend? I thought there aren't any custom ROMs for it yet.
I actually don't know how to flash custom ROMs on Pixel 4. TWRP doesn't seem to be a possible solution on it yet, no?
I only succeeded rooting it with Magisk, by patching the boot file. Tried to do it on Android R (was worth it if it worked), but it didn't work, sadly.
On Pixel 2 I could use TWRP. For some reason I failed to let it stay, so I had to flash it each time via the PC just to run it. On Pixel 4 I couldn't even find TWRP. Maybe now it's available.
AndroidDeveloperLB said:
I had stock ever since I got Pixel 4 (had Pixel 2 before). Maybe a custom rom will fix it. Any that you can recommend? I thought there aren't any custom ROMs for it yet.
I actually don't know how to flash custom ROMs on Pixel 4. TWRP doesn't seem to be a possible solution on it yet, no?
I only succeeded rooting it with Magisk, by patching the boot file. Tried to do it on Android R (was worth it if it worked), but it didn't work, sadly.
On Pixel 2 I could use TWRP. For some reason I failed to let it stay, so I had to flash it each time via the PC just to run it. On Pixel 4 I couldn't even find TWRP. Maybe now it's available.
Click to expand...
Click to collapse
Hopefully, someone will jump in here and help you with a custom rom suggestion. I haven't bl unlocked since midway through my 5X so I'm not the one to ask. From what I understand TWRP is basically on hold but I could be wrong.
damn, after almost 3 years i come here with the same issue, seems like nobody linked the persist.img or fixed the issue here