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).
Beta 5/RC1 of Q on deck!
- Thread starter PGHammer
- Start date
Working fine here. My 3a restarted once after first boot but it's working fine now
Last edited:
What Issues?
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.)
With the latest Magisk Canary, I guess. Haven't tried it myself because latest Pie security patch works like a charm for my needs.
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.
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
Attachments
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.
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.
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.
Last edited:
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
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).
So basically you like to live dangerously....I can respect that :good:
Actually.....
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?
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?
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?
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.
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.
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone