Android 12 beta now available.
- Thread starter Kizzy Catwoman
- Start date
- Status
Greedog
Well-known member
- Aug 29, 2016
- 269
- 0
- 0
Re: Android 12 Beta 1
Sorry about that. I did a search and nothing came up so I started the thread.
Yeah!
Sorry about that. I did a search and nothing came up so I started the thread.
- Feb 6, 2017
- 96,835
- 12,654
- 113
cbreze
Well-known member
- May 30, 2011
- 2,880
- 88
- 48
Haven't seen anybody else talking about it so maybe just starting to roll out. I'm usually one of the last ones to get a rollout, lol.
Only 2 minor issues so far on my 4XL. If the screen has been off for a while, double tap to wake doesn't work and I have to use power button to wake it up. If I then let the screen timeout, tap to wake works as it should. And yes, tap to wake is enabled and worked fine on A11.
Volume is definitely lower on the beta compared to A11. Yes, all settings are on max. I found an app called speaker boost in the playstore that solves the problem, but they need to fix it in a later beta.
The phone seems snappier and no problems at all with battery life.
Volume is definitely lower on the beta compared to A11. Yes, all settings are on max. I found an app called speaker boost in the playstore that solves the problem, but they need to fix it in a later beta.
The phone seems snappier and no problems at all with battery life.
- Feb 6, 2017
- 96,835
- 12,654
- 113
anthonium
Well-known member
- Nov 4, 2013
- 610
- 6
- 18
Major bug found though through some Google searching I found this bug has plagued some individuals on previous versions of Android. Upon regularly restarting the device (pressing power button, and restart) the phone booted back up and required PIN to unlock. Upon entering the PIN the phone loops back to the lock screen requiring the PIN again. There was no way to log into the device.
In the end I had to factory reset the device using the Recovery Option in the boot menu and this did not solve it. The phone boots back up with the initial set up but when prompted to enter the previous PIN to use on the device, it reverts back to the PIN screen. Attempting the "Use my Google account instead" option reverts back to the PIN screen so again stuck in a loop.
In the end the phone is inaccesible. Waiting on Google support to get back to me.
In the end I had to factory reset the device using the Recovery Option in the boot menu and this did not solve it. The phone boots back up with the initial set up but when prompted to enter the previous PIN to use on the device, it reverts back to the PIN screen. Attempting the "Use my Google account instead" option reverts back to the PIN screen so again stuck in a loop.
In the end the phone is inaccesible. Waiting on Google support to get back to me.
Interesting. I've rebooted my Pixel 4a many times since installing A12 Beta1 without issue.
I hope you get this fixed soon.
anthonium
Well-known member
- Nov 4, 2013
- 610
- 6
- 18
I never play around with Beta and went against my better judgement! Oh well there's no problem that can't be resolved. Mandatory phone detox.
It's quite a very odd error to encounter. I cannot even use ADB to sideload and revert back to Android 11 as I receive the message that it is an older version of Android. Unfortunately the boot screen is currently locked or I would try flashing it instead.
It's quite a very odd error to encounter. I cannot even use ADB to sideload and revert back to Android 11 as I receive the message that it is an older version of Android. Unfortunately the boot screen is currently locked or I would try flashing it instead.
anthonium
Well-known member
- Nov 4, 2013
- 610
- 6
- 18
Good news everyone! After hours of researching Reddit saves the day as usual!
I was able to find several threads about this issue in the Android Beta channel on Reddit. In one of those I found the below video which guides you on how to break out of this crazy loop. I have no idea how this person figured it out but I just tried it and my device is back up and running! I am going to proceed to opt out of the beta now. Lesson learned! PHEW!!!
Meanwhile Google specialists are scratching their heads...
https://www.youtube.com/watch?v=ZHdIBNXwJr8&ab_channel=ict'FIXict'FIX
I was able to find several threads about this issue in the Android Beta channel on Reddit. In one of those I found the below video which guides you on how to break out of this crazy loop. I have no idea how this person figured it out but I just tried it and my device is back up and running! I am going to proceed to opt out of the beta now. Lesson learned! PHEW!!!
Meanwhile Google specialists are scratching their heads...
https://www.youtube.com/watch?v=ZHdIBNXwJr8&ab_channel=ict'FIXict'FIX
- Feb 2, 2017
- 8,059
- 1,937
- 113
Same exact thing happened to me. I finally gave up hope and took it up to Verizon, they gave up and I ended up getting a replacement. I haven't sent the old one back yet and was gonna give the video you posted a try but I can't figure out what he did when he popped his sim card out. Did he replace it?
Either way, I'm staying away from the beta until at least the 3rd one
anthonium
Well-known member
- Nov 4, 2013
- 610
- 6
- 18
If it is your primary device I would stay away from any beta! Oddly this problem doesn't seem to just affect this beta, there are many videos on YouTube you can find about this issue just by searching "bypass frp google pixel".
As for your old device that isn't working, I'm glad Verizon was able to give you a replacement but do not get rid of the old one just yet! You may now be able to have TWO devices! I'll try to guide you a little blindly through here as I already got my device up and running. The SIM part didn't work for me completely on the video but I realized the main part of the fix was to mess with the keyboard so here goes.
1. Reset the device again
2. On bootup redo all the steps on the video up to the point where he leaves the sim card half way sticking out
3. I didn't get the notification he received to then get into the settings so I went all the way back to the first first screen where you choose the language
4. Leave it as English and go to the next step "WiFi" setup. You should already have established your Wifi previously so it likely jumps to the "Do not copy device" page. Once here, hit back on your device to get back to the WiFi area
5. Here comes the "trick"...Scroll down the list of WiFi available and click on the add network option. This will popup the box to setup your SSID.
6. Click on the area where you would enter your SSID and once the keyboard pops up, hold the space bar until it gives you the various keyboard options. It should list four with the last two being voice options. Click on the one before "Automatic Google Voice Typing". I think it's the third one. This brings up the keyboard with the microphone icon on the right. Click on the microphone icon and it will ask to allow to access voice. This will then take you to the permissions options of Gboard.
7. Once you are here click on the circular Gboard icon and from there it goes back into other settings. Then at the top it should appear a search option and you can type in "app notifications" to get into the appropriate section like in the above video and then follow the same steps on the video from there on.
I am 100% certain it can be fixed.
EDIT: I just got an idea. If the above doesn't work for you, maybe we can do a video call and you can point at your old device or hold it up to the webcam and I can walk you through (we don't need to see other if that is an uncomfortable idea for you). I leave the option up to you! Best of luck!
Last edited:
- Feb 2, 2017
- 8,059
- 1,937
- 113
I had an issue today with my Bluetooth headphones. I was listening to the radio and I took a phone call. Afterwards I could not get any media to play until I forgot and repaired my Bluetooth headphones again. I tried restarting the phone, the headphones etc. But it took a forget and repair to get it to work again. Bose QC 35ii with pixel 4a 5G. Reported it via feedback and a bug report.
- Feb 2, 2017
- 8,059
- 1,937
- 113
jhilker
Trusted Member
- Sep 21, 2009
- 1,737
- 767
- 113
Spoke too soon. It lasted a couple hours, but crashed again. Will wait for Beta 2 to try again.
Thank!! Yep it worked.. Lmao. My keyboard was set up a little different,but it all basically works the same after you run through the steps.
Thanks for taking the time.
I have to send back a phone or I get charged, but it was and is good information to know if it happens again. But I'm definitely staying away from the beta. This all started with a boot loop by the way, after I answered and then hung up from a phone call
Thanks for taking the time.
I have to send back a phone or I get charged, but it was and is good information to know if it happens again. But I'm definitely staying away from the beta. This all started with a boot loop by the way, after I answered and then hung up from a phone call
- Status
Similar threads
Trending Posts
-
Samsung Galaxy Tab A9 Plus (SM-X210) stuck in EDL Mode after USB port replacement – Need Firehose & XML files
- Started by aloha17
- Replies: 10
-
-
-
-
Facebook
Twitter
Instagram