yashsingh1/xdaforums huggingface dataset:
[Google Pixel 3a Guides, News, & Discussion] bobby janow:
Without a doubt. However, I don't think you have to roll back to P if you bootloop. They are saying a factory reset will do the trick but then the whole point of an OTA is out the window. This is the time to sit back and cool your heels.
[Google Pixel 3a Guides, News, & Discussion] pharpe:
It's still available:

OTAs

https://developer.android.com/preview/download-ota.html

System images

https://developer.android.com/preview/download.html
[Google Pixel 3a Guides, News, & Discussion] sic0048:
You will definitely loose root if you take the beta 4 right now. I tried it (just for grins) and confirmed the normal Magisk installation process does not work (it doesn't prevent the system from working, but it doesn't actually install or allow root).

The unknown question is if this beta will ever have root access. Some (but not all) of the Pixel devices had root under the 3rd beta, so there is a chance someone will take the time to get root under beta 4. But I would not count on it. I ended up going back to Pie because I like my Magisk modules too much not to have root.
[Google Pixel 3a Guides, News, & Discussion] jayyskittles:
Is Pokemon Go working yet?
[Google Pixel 3a Guides, News, & Discussion] pharpe:
Magisk does not work on Pixel 3 or 3a on the Q beta due to logical partitions. The Magisk dev is working on it.

https://twitter.com/topjohnwu/status/1125315090280923138
[Google Pixel 3a Guides, News, & Discussion] 12paq:
You've asked on multiple threads... I hope this doesn't sound snarky.

1. Recovery.img doesn't exist alone, it is part of the boot.img

2. You can download it all from the Google factory images

3. Just Google it
[Google Pixel 3a Guides, News, & Discussion] :
Hey guys,

Opted out of the beta program - was having trouble with the screen not working with double tap, etc. Received the OTA update to go back to stable version but it continually pauses and I have to reset the download.

It has yet to actually download and install - its been two days now ?

Any ideas ?
[Google Pixel 3a Guides, News, & Discussion] oliver7:
Totally happy w beta 4.

Have not noticed any significant bugs.

Working: Wifi(full bandwidth), 4G+, bt, gpay(paid successfully), battery(day1 sot: 4h30/7% left), gesture nav(just the hiccup when a notification pops up). Banking app (Deutsche Bank): security error.

Loving Q.

P.S. It seems to be impossible to go to home - i.e. go to the first screen of the launcher when being on the 2nd, with gesture nav!? Or does anybody know how to??

P.P.S. There's a short flickering now when jumping to home from within an app - no idea why it's happening now, it wasn't there on the 1st day... anyone knows how to fix that?

//Update/fix: leave Google app beta, uninstall Google beta app, install stable Google app.
[Google Pixel 3a Guides, News, & Discussion] sic0048:
Make sure your screen doesn't turn off. You will probably have to increase the display sleep setting to 30 minutes.
[Google Pixel 3a Guides, News, & Discussion] :
Yep - that did it, thanks for the recommendation

Cheers !
[Google Pixel 3a Guides, News, & Discussion] misslebulletttttt:
do you have a product partition in your pixel 3a ?

I flash-all the Q-preview4, in fastboot mode, I got : remote: Partition product not found.
[Google Pixel 3a Guides, News, & Discussion] misslebulletttttt:
this can be avoided by using the latest fastboot
[Google Pixel 3a Guides, News, & Discussion] mrakifa:
How long does it typically take to get the update once opted in for Q?

It's been a full 24 hrs and still no update.

Thanks in advance.
[Google Pixel 3a Guides, News, & Discussion] bejunk:
Normal is instantly. Go to setting > updates and check a few times via the button. It should show up.
[Google Pixel 3a Guides, News, & Discussion] mrakifa:
Keeps saying system is up to date, not sure why the update is not being pushed.
[Google Pixel 3a Guides, News, & Discussion] pharpe:
Just sideload the OTA.

https://developer.android.com/preview/download-ota
[Google Pixel 3a Guides, News, & Discussion] mrakifa:
Are you still experiencing the flickering when exiting out of apps on full gesture?
[Google Pixel 3a Guides, News, & Discussion] oliver7:
No, I'm using Google app 10.4.5.21 which doesn't cause the bug.
[Google Pixel 3a Guides, News, & Discussion] mrakifa:
Thanks works like a charm!
[Google Pixel 3a Guides, News, & Discussion] sic0048:
I've heard we are in a period where Google has stopped pushing out the 4th beta, but haven't released the 5th beta yet.

Your choices are to either wait a few days for the 5th beta to be released, or sideload the 4th release. Personally I would just wait for the 5th release at this point.
[Google Pixel 3a Guides, News, & Discussion] mrakifa:
Actually the update got pushed to my device.
[Google Pixel 3a Guides, News, & Discussion] JustEgoist:
Got "no valid os" with no access to recovery mode after OTA update to Q (beta4). Any chance to revive or its a brick?
[Google Pixel 3a Guides, News, & Discussion] mrakifa:
I had the same problem, no way to recover, luckily my device was less than 14 days old bought unlocked from best buy, they exchanged it.
[Google Pixel 3a Guides, News, & Discussion] JustEgoist:
Mine is 12 days old, same from Best Buy. But I'm not in US right now till Monday. Dunno will they change it after 14 days
[Google Pixel 3a Guides, News, & Discussion] SketchyStunts:
Man...just got this phone a few hours ago. Did all the updates, opted into beta & took the OTA. Well, Google logo for 30 minutes. Manually rebooted & same thing. Factory reset, back into stock pie. So I side loaded it via adb with no issues. On reboot i got the awesome "couldn't detect a os". Couldn't get into factory recovery anymore either to factory reset. Luckily I ticked OEM unlock prior to this so "fastboot flashing unlock" forced factory reset & booted into Q beta. Everything has been peachy since lol :good:
[Google Pixel 3a Guides, News, & Discussion] JustEgoist:
Well, if I had oem unlocked I wouldn't be here :) Sadly, I didn't knew u could kill ur phone with OTA.
[Google Pixel 3a Guides, News, & Discussion] SketchyStunts:
That was my same thought initially as well. No boot on a OTA is no bueno.
[Google Pixel 3a Guides, News, & Discussion] stevew84:
Flashed July stock, then updated to the beta 4 of Q...stuck at the G screen and never got out. First time this happened.
[Google Pixel 3a Guides, News, & Discussion] 3377:
I have exactly the same problem with my Pixel 3a XL and Google denied the warranty. The device is 1 day old

After the first Restart after the Update the Pixel say:

Cant find valid Operating System

The Device will not start

USB Debugging is off

OEM Unlocking is off

Bootloader is locked

Recovery dont work
[Google Pixel 3a Guides, News, & Discussion] JustEgoist:
Wtf, what did they say? Cuz Im about to contact with them with excatly the same issue
[Google Pixel 3a Guides, News, & Discussion] 3377:
This is the Answer from the Support (with Google Translator from German to English)

Thank you for your chat with Google.

Unfortunately, because your device is pre-publishing Android, I am unable to verify that your device can be replaced or repaired. Preliminary releases of software may contain errors and defects that may affect the normal operation of your device.

If the problem persists after you have unsubscribed from the program and are using the stable, publicly accessible Android version again, feel free to contact us again

As my colleague has already explained to you, we can not help you in this case as it is a pre-release of software. When signing up for Android Beta, you should also have been told that the version may contain bugs and defects that may affect the normal functioning of your device.

We have no options and handle here. We can only help you if you have the normal Android version on your device.

If you have any questions or need help, you are welcome to submit them as an answer to this e-mail. Have a nice Sunday.
[Google Pixel 3a Guides, News, & Discussion] mrakifa:
They will not, after that you have to go through Google's warranty

---------- Post added at 03:26 AM ---------- Previous post was at 03:23 AM ----------

Wait...so they urge ppl to try their beta for feedback purposes but won't help if it bricks the device? Wow, just saying, Apple would replace without questions asked.
[Google Pixel 3a Guides, News, & Discussion] 3377:
I have now an RMA but I have to pay for the repair myself. How much I have to pay I do not know. I get an offer about the costs
[Google Pixel 3a Guides, News, & Discussion] Jordans6996:
Yeah i definitely had this problem as well but it was fixed with warranty replacement.

I had the T-Mobile version Pixel 3a and it was on July Security patch. I did the OTA Beta 4 of android q and reboot then i got the no Os thing going on. I contacted T-Mobile and lucky enough it was replaced with 2 day free shipping to a T-Mobile retail store where i had to go and get it and exchange my device there for the warranty one. Strangely enough they sent me the Pixel 3a XL instead of the Pixel 3a.

I was on T-Mobiles Protection 360 program ($12 adds to the bill every month) so thats why i was able to get the replacement by the way. They did charge $5 plus tax when exchanging the device for the warranty one.

To note T-Mobile version 'OEM unlocking' will be greyed out. Also with bootloader unlocking.

In this case don't update your device to beta 4 if you have the July security patch installed! Definitely just wait for beta 5 if you got July security patch on android pie.
[Google Pixel 3a Guides, News, & Discussion] mrakifa:
Yeah I've ticked the same thing just incase lol
[Google Pixel 3a Guides, News, & Discussion] Geo411m:
I had the same issue. I just did fastboot flashing unlock and was lucky to be able to unlock the bootloader and flash the factory image.
[Google Pixel 3a Guides, News, & Discussion] jacktheriefla:
As talked a bit to [MENTION=10020502]3377[/MENTION] in a German Board about his bad Luck.Can anybody Confirm this has something to do with Beta4 and July Security Update?
[Google Pixel 3a Guides, News, & Discussion] PGHammer:
In my case, was able to go semi-directly to the latest beta of Q via OTA. My 3a arrived this morning, and I did the update dance (connected it to the phone I was leaving, and then signed up for the Q beta). First off, the update (from my S7 Snapdragon - which is the phone I was leaving) was utterly both flawless and painless - and I got my first two (pleasant) shocks. First, the fingerprint sensor support - MUCH faster than the S7 - which was no slouch. (Remember - mainstream/midrange phone.) The second pleasant shock came with being able to transfer the SIM from the same S7 to the 3a - directly. No modding, trimming, or anything. (Since when does the Pixel 3a take micro-SIMs? That is indeed the SIM size the S7 takes; how is it that the 3a swallowed it directly?) Still, that it swallowed the micro-SIM straight up meant one less chore I had to do - no migration that way.) I wasn't through getting shocks, either. Shock #3 (pleasant variety) - upgrading to beta 4 of Q. I was able to do it OTA, and lost no data whatever. This led to shock #4 (pleasant variety - performance of beta 4 of Q. Seat of pants - faster than even Pie - which was faster than the S7 running Oreo. (This is supposed to be a mainstream/midrange phone; explain, please.)

So far, I have had exactly one unpleasant shock - and it has nothing to do with the 3a's firmware - it's a hardware quibble - no USB-C to USB cable or adapter. (While the Quick-Change adapter works for transferring data from old phone to new (easily one of the fastest such transfers I've seen) there is no similar adapter (or even cable) for connecting to a PC in the box. Still, it's a quibble (and I'm saying that much) - I have a three-pack of such cables on order via Amazon's AmazonBasics line. As to why nothing concerning the camera, the camera had nothing (at all) to do with why I bought the phone - it didn't figure into it in any way/shape/form. The Pixel 3a is what a mainstream/midrange phone SHOULD be - a proven utility infielder that does what is asked of it.
[Google Pixel 3a Guides, News, & Discussion] Gh05tly:
Care to share and maybe create a tutorial for this?

A LOT of people are getting bricked after July 5th update and OTA still installing Q4 over top of it. A tutorial would be nice in a dedicated thread. This includes my 3a. Bricked yesterday after OTA pushed Q4 over July 5th Pie update.
[Google Pixel 3a Guides, News, & Discussion] Geo411m:
First you also need the latest fastboot tool. You can get it from the Android SDK Platform-Tools package, which you can here

Next you'll need to unlock your bootloader by running

fastboot flashing unlock

Finally, grab a factory image from Here and unzip it. From command line run the flash-all.bat that you unzipped.

This link will explain things better
[Google Pixel 3a Guides, News, & Discussion] sic0048:
The 5th Q Beta release is now available!
[Google Pixel 3a Guides, News, & Discussion] SketchyStunts:
I'm on beta 4 now. Kind of scared to update at work away from a computer after the fiasco I had with beta 4 initially
[Google Pixel 3a Guides, News, & Discussion] sic0048:
I'm with you.

I wouldn't take this update on my daily driver unless I was near a computer that I can ADB and Fastboot with. Odds are you will be OK, but this is a beta and we are in the first couple of hours of release, so there is little feedback on possible bugs/issues right now.
[Google Pixel 3a Guides, News, & Discussion] PGHammer:
Ordinarily i would not have dared; however....

Given that we were basically in the home stretch when my 3a even showed up (and that I had a whole phone to go back to - albeit running Oreo), I chased the chicken back into the coop and not only signed up for the Q beta within an hour of unpacking my 3a, but downloaded the first update (to beta 4) when it showed up. So, I have been treating Q as a daily driver. My only change (from Oreo) was enabling systemwide dark mode - however, that is something Oreo didn't have. (If Oreo had it, would I have made the same change? Not only yes, but "heck yes" - because I DID enable it in Windows 10 Pro for Workstations - which is the daily driver of my desktop.) Number of apps/games/etc. that have broken in daily use of Q - none. Beta 5/RC1 of Q showed up today; it's bigger than beta 4 was, but I had the same lack-of-issues installing it. I have one quibble - how do you enable the dark launch options? (They don't enable by default - and I want them.)
[Google Pixel 3a Guides, News, & Discussion] Geo411m:
Coming from beta 4 to 5 no issues here.
[Google Pixel 3a Guides, News, & Discussion] PGHammer:
On Pixel Launcher...

I actually used Pixel Launcher two versions of Android (and two phones) ago - when I was running Nougat on my Galaxy Nexus; I was glad to get it back (naturally, for that reason, it's now my default again; sorry, Microsoft Launcher - which was my default with Oreo and my S7).

Another nice thing about the 3a (compared to the S7) - it is physically smaller, to the point that it now fits in front pockets (pants, jeans, shirts, etc.) than the S7 it replaces); therefore, "butt dialing" is physically impossible. (You can't "butt dial" if you aren't sitting on the phone.) Lastly, it is the thinnest (front-to-back) non-flip-phone I've ever owned, in addition to being the first new Android phone I've ever owned, and the first new phone of any sort I've ever purchased since the days OF flip-phones. (My previous two phones - passed-down (Galaxy Nexus) and *sweat equity* (Galaxy S7), respectively. and in order.)

---------- Post added at 08:48 PM ---------- Previous post was at 08:20 PM ----------

I'm seriously surprised you had the issues you had; in fact, I've been surprised that anybody with a 3a (or 3aXL, for that matter) had these sorts of issues - mainly because my own 3a has been absatively posilutely painless in all Q-related operations. Upgrading from Pie to beta 4 of Q was painless; running beta 4 was painless, upgrading from beta 4 to this build of Q was painless (both upgrades were OTA); I've had more issues with Windows 10 Pro for Workstations - by far - than I've had with Q - and all of those with Windows 10 related to Norton Security Online (therefore third-party software). It's why I made the comment regarding John DeLancie (Q in TNG) being chained to the command chair - I have no wish to go back to Pie (let alone Oreo).
[Google Pixel 3a Guides, News, & Discussion] SketchyStunts:
Had no issues going from 4 to 5. Nice & smooth as was beta 4
[Google Pixel 3a Guides, News, & Discussion] dollarpapa:
Installed the beta, just by joining the beta subscription, the phone booted to recovery mode. For a moment I didn't know what to do with it, I was just gonna say the F word.

Rebooted again, this time it was fine. There are still obvious issues and pretty close to full launch, it's worrying that they still have bugs like that. Some of my apps crashing at first try, and changed around wallpapers and when the phone woke, the lock screen wallpaper was squashed sideways, so I changed it to something else, so far it's fine. Never seen anything like that.
[Google Pixel 3a Guides, News, & Discussion] 3377:
Good News. Google has repaired my Pixel 3a XL for free. I did not have to pay anything..
[Google Pixel 3a Guides, News, & Discussion] zipredictive:
Stuttering recording video using camera and playground anyone?
[Google Pixel 3a Guides, News, & Discussion] Uzephi:
DP6 is being pushed today. My phone just got the OTA. 265.5mb delta.

https://android-developers.googleblog.com/2019/08/final-beta-update-official-android-q.html?m=1
[Google Pixel 3a Guides, News, & Discussion] c_tho:
they've fixed the thing where recents were sometimes zoomed in when using a third-party launcher, but no sign of the dark boot animation for us yet! oh well.
[Google Pixel 3a Guides, News, & Discussion] rahul4u:
Dark boot animation is working fine for me - to enable it you have to turn on the dark theme toggle under display settings.
[Google Pixel 3a Guides, News, & Discussion] Uzephi:
I had to toggle dark theme off then back on to enable dark boot.
[Google Pixel 3a Guides, News, & Discussion] PGHammer:
Your advice worked (also running DP6/RC2) - I finally got my Dark Launch. (It also means that my desktop and phone are sync'd up (Pro for Workstation was running in Dark Mode already - only the PHONE was not). To match up, I also chose one of the NASA Image Library wallpapers (home AND launch screen).
[Google Pixel 3a Guides, News, & Discussion] syckman:
Updated to newest Q beta this morning but the software update icon in status bar won't go away - anyone else have this issue and/or how can you make it go away. TIA
[Google Pixel 3a Guides, News, & Discussion] c_tho:
thanks for these tips, i did this and it worked!
[OnePlus 7 Pro Questions & Answers] OverLife:
Hey folks,

So the last 3 hours i spend investigating if the Diag driver is enabled :confused:

I poked around in /proc/config.gz on my oneplus itself and found

So this tells my the Diag "interface" is enabled but Snoop Snitch still tells me "Could not initialize DIAG interface."

According to the faq if i grep/search for the entry dia i get "246 media"

Could anyone help me out do i get it completely wrong ?

Ps. Sorry for the lack of links i would link all the needed stuff but not enough posts
[OnePlus 7 Pro Questions & Answers] CoinsClassic:
Same here with Sony Xperia 1.

I think Snoopsnitch isn't actively in development anymore sadly, thus no communication to Android 8+ diag interfaces, as seen in list of compatible devices https://opensource.srlabs.de/projects/snoopsnitch/wiki/DeviceList.

Last activity on the Project: https://opensource.srlabs.de/projects/snoopsnitch/activity?from=2019-04-19
[OnePlus 7 Pro Questions & Answers] cristihan:
Wrong..SnoopSnitch is still developed, a few days ago it was released the 2.0.10 ,64 bit version (I haven't tested it yet) and works on Android 9 LOS on my Samsung Galaxy S4 mini VE LTE (i9195i). It also runs on my Xiaomi Redmi 3S with 64 bit Reloaded CAF OS pie, noting that here I had to compile the kernel with the old DIAG_CHAR driver from MI Source on Github.
[OnePlus 7 Pro Questions & Answers] joelstitch:
I am also having the same issue trying to run SnoopSnitch. Would you explain how you compiled the kernel? I also have a Oneplus 7 Pro
[OnePlus 7 Pro Questions & Answers] Thireus:
Any luck guys? Does it work on the OnePlus 7 Pro?
[Amazfit] Amit Pinto:
Hello, I switched phones now and I have been trying for the past few days to connect my Amazfit Pace with the Amazfit Application.

Every time I try to sign in via Google, There is a pop-up window titled "Couldn't sign in".

Please help me and thank you in advance,

Amit Pinto
[Amazfit] delluk:
I am having the same problem with my MI login after flashing a new ROM on my phone and trying to log unto the Amazfit Watch app. I have even created a new login to no avail. It always comes up with an error code (C020004 or C020001).
[Amazfit] Wckddz:
I just bought an Amazfit Verge today and I also cant login to setup the watch. Is there even a way to setup the watch without the app ?

Tried login from different devices with different Android versions, different accounts, different login methods like Google, manually, Mi Account, always the same.

The same happens on the mi fit app, just can't create or sign in.

Anyone knows what's happening?

EDIT: Also tried over home WiFi and 4g data with and without VPN, same results.
[Amazfit] albertjh:
Same problem here. I tried everything but cannot register in mi fit app.

The smartwatch is useless this way.
[Amazfit] Kumidan:
Same for me, today I have flashed the Lineage OS 15.1 for my smartphone (Asus ZE550KL) and I can't login into Amazfit Watch app, I can't even create a new account, no matter the chosen method (email and pass, FB, Google...).

I suppose that Xiaomi checks the Android version and if the smartphone is unlocked, same as mobile banking apps do.
[Amazfit] Wckddz:
Well I tried on a stock one plus 7 pro, also on a stock old 4.4 and also asked a friend to try it. Same results, I don't think that should be the problem.. I'm gonna try on iOS and report my findings

EDIT: someone on Reddit contacted costumer support and they said it's a server problem wich should be fixed today or tomorrow.
[Amazfit] Tsubakini:
French user

I have the same problem and cannot use my new Amazfit Stratos 2!

Hope it will not be too long!
[Amazfit] dainiushappy:
Same problem for me. Motorola Moto G3 with android, same errors. My amazfit now is bricked by inability to log in through app. Hope for some solution.
[Amazfit] albertjh:
Tried it 5 minutes ago and now it works.
[Amazfit] dainiushappy:
If still not working for someone, maybe you can cet help from my situation:

This morning I found out that no videos playing on my phone (from youtube to pornhub :) ), then I removed youtube app from my phone, cleared cache, restarted phone, reinstalled YT app and videos issue was solved. Right after that I tried to log-in into Amazfit app and voila - vorked like a charm. I don't know if this is due to YT reset or due to Amazfit got back the servers. Hope this helps someone.
[Amazfit] xdauser2019:
Problem is fixed already. Amazfit knew about it yesterday and fixed.
[Amazfit] areisramalho:
I saw the problem today. I can't authenticate or reset the password (says the user doesn't exist) or create a new user ( "could not connect to network").
[Amazfit] palmdoc:
I couldn't sync watch data today

Tried resetting iPhone and reboot watch to no avail

In the end deleted and reinstalled app and now cannot sign in

I wonder if the Huami authentication server is down?
[Amazfit] 3rChuss:
Got the same problem here. Can't sign in....
[Amazfit] mumairmasood:
Same. Probably an issue with the authentication servers as tried logging in with all options on both Amazfit & MI Fit apps with no luck.
[Amazfit] suhail788:
Watch was not syncing. Uninstalled the app and not being able to sign in again. The new update is very bad the old software was more precise and more data eg Heart Rate and Floors Climed is not there in new app. Heart Rate shows only if continuous heart rate is ok
[Amazfit] nexusklaus:
Glad I'm not alone ....