Never noticed it before Pre 38R.
Any thoughts?
That's not new, been there at least since the last version
Send from OnePlus One using Tapatalk
Are you from the future? Or the past?
Related
I have been waiting for this update for the AT&T S3 for while. It was made available for download and install this morning in NYC. S3 updated to build R765AUCU2BQD4 from build R765AUCU1APJ. Tizzen updated to version 2.3.2.3 from 2.3.2.0. See attachment for update details.
Yes!!! Finally
Thanks for the info, updating now! I connect via IOS so will be interested to see any improvements.
Got my updated this morning too.
Doesn't look like they fixed the issue with Text Message notifications
Still no update for tmobile
Sent from my SM-G955F using Tapatalk
Check this Link... https://forum.xda-developers.com/gear-s3/development/rom-samsung-gear-s3-sm-r765-att-t3588066
It says "AT&T" but is 100% T-MOBILE
bimmerboii said:
Still no update for tmobile
Sent from my SM-G955F using Tapatalk
Click to expand...
Click to collapse
Battery Draining quickly since update
Anyone else experiencing any faster battery drainage after the update. I could go two days before this update between charges and now mine is dying within 6-8 hours off the charger. No new apps/settings since update. Same amount of usage
No changes for me.. still 2 to 3 days w/out charging...
bimmerboii said:
Still no update for tmobile
Sent from my SM-G955F using Tapatalk
Click to expand...
Click to collapse
Offandbackon said:
Anyone else experiencing any faster battery drainage after the update. I could go two days before this update between charges and now mine is dying within 6-8 hours off the charger. No new apps/settings since update. Same amount of usage
Click to expand...
Click to collapse
wisefreakz said:
Check this Link... https://forum.xda-developers.com/gear-s3/development/rom-samsung-gear-s3-sm-r765-att-t3588066
It says "AT&T" but is 100% T-MOBILE
Click to expand...
Click to collapse
That is the version I currently have and that update was released a while back. Tizen version is 2.3.2.2 while the latest one is 2.3.2.3
The one issue I've seen since the update is that if my S3 disconnects from my phone then reconnect, Wi-Fi does not turn off automatically as it should. This also contributes to increased battery drain. I set it to off rather than auto in the meantime
I've Google all of the reported issues of the Pixel and didn't see anyone complaining about this. When I make or receive a phone call, it takes about 10-20 seconds from the time we answer the phone to the time we can hear each other /talk. Anybody else having this issue?
Sent from my Pixel 2 using Tapatalk
Not sure what network you're on but I'm working closely with Verizon and Google on my LTE connection. I am getting my third RMA device on Tuesday. Also, if you are on Verizon, not sure if you have a Google or Verizon P2 - that may be a factor as well, as I'm finding out with my Google P2.
My Google version pixel 2 on Verizon is fine.
Sent from my Pixel 2 using Tapatalk
mtoomey79 said:
Not sure what network you're on but I'm working closely with Verizon and Google on my LTE connection. I am getting my third RMA device on Tuesday. Also, if you are on Verizon, not sure if you have a Google or Verizon P2 - that may be a factor as well, as I'm finding out with my Google P2.
Click to expand...
Click to collapse
I'm on Verizon and using a Verizon P2. Wish I had the Google version so I can manipulate software and see if a different radio/rom/hack would fix it.
I'm beginning to think it has something to do with HD calling. I received 2 calls over the weekend which worked fine (no long connection time). This morning my wife calls and it took 15+ seconds before we could hear each other. It was so slow that she hung up the first time and called back. This morning I distinctly remembered seeing HD calling on the phone as I answered. The next time someone calls I'll make note if it says HD or not.
Sent from my Pixel 2 using Tapatalk
Anyone get the new 8.1 beta 2 update? I'm on 8.0 with the November security update so I'm not eligible for the beta 1 update. I read that the beta 2 was just released but still no update even though I've unregistered and re-registered a half dozen times.
I'm hoping an update would fix this issue. If not I'll end up replacing this phone or going back to my Pixel 1.
I also navigated today for the first time and that was a horrible experience. The phone didn't move with me. The only way I could get it to update my location was to close navigation and restart it. I didn't realize this until after I'd missed my turn.
Sent from my Pixel 2 using Tapatalk
joshw0000 said:
Anyone get the new 8.1 beta 2 update? I'm on 8.0 with the November security update so I'm not eligible for the beta 1 update. I read that the beta 2 was just released but still no update even though I've unregistered and re-registered a half dozen times.
I'm hoping an update would fix this issue. If not I'll end up replacing this phone or going back to my Pixel 1.
I also navigated today for the first time and that was a horrible experience. The phone didn't move with me. The only way I could get it to update my location was to close navigation and restart it. I didn't realize this until after I'd missed my turn.
Sent from my Pixel 2 using Tapatalk
Click to expand...
Click to collapse
Why not just download the 8.1 DP2 firmware, remove the -w from flashall.bat script(so it doesn't wipe) and update manually?
You can dl here https://developer.android.com/preview/download.html
an21281 said:
Why not just download the 8.1 DP2 firmware, remove the -w from flashall.bat script(so it doesn't wipe) and update manually?
You can dl here https://developer.android.com/preview/download.html
Click to expand...
Click to collapse
I'd love to but I have a Vzw version.
Sent from my Pixel 2 using Tapatalk
joshw0000 said:
I'd love to but I have a Vzw version.
Sent from my Pixel 2 using Tapatalk
Click to expand...
Click to collapse
Why wouldn't manually updating to dp2 work on the Verizon pixel 2? Not sure if it will work with removing the - w, but with it left in I don't see what would stop it from working. You not rooting or unlocking anything... Or does it need to be Verizon firmware? You can also try removing the bootloader and radio imgs, and flash-all without those
Sent from my Pixel 2 XL using Tapatalk
an21281 said:
Why wouldn't manually updating to dp2 work on the Verizon pixel 2? Not sure if it will work with removing the - w, but with it left in I don't see what would stop it from working. You not rooting or unlocking anything... Or does it need to be Verizon firmware? You can also try removing the bootloader and radio imgs, and flash-all without those
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
If you read the instructions for manually flashing firmware, one of the first steps is to unlock the bootloader. Not sure why Google chose to do it that way but it won't work on a locked phone. I've tried before on a locked Pixel 1.
Sent from my Pixel 2 using Tapatalk
I feel dumb for not thinking of this earlier but I reset network connections today and it *seems* to be working fine. Time will tell.
Sent from my Pixel 2 using Tapatalk
I got my OnePlus 6 the other day and loaded the P beta. Before putting anything on it I was testing what works and found out that I was not able to be text message. I could send but not receive. When I downgraded back to 8.1 everything worked perfect. I know the beta says VoLte is broken (did not have issues making and receiving calls). Any suggestions to fix it, I bought the phone to play with P mostly. I can deal with most bugs, but I need to be able to receive text and pic messages. I am using T-Mobile and no other SIM cards.
MadHatter01 said:
I got my OnePlus 6 the other day and loaded the P beta. Before putting anything on it I was testing what works and found out that I was not able to be text message. I could send but not receive. When I downgraded back to 8.1 everything worked perfect. I know the beta says VoLte is broken (did not have issues making and receiving calls). Any suggestions to fix it, I bought the phone to play with P mostly. I can deal with most bugs, but I need to be able to receive text and pic messages. I am using T-Mobile and no other SIM cards.
Click to expand...
Click to collapse
You literally bought the OP6 mostly just to play with Android P??
Sent from my ONEPLUS A5010 using Tapatalk
iamterence said:
You literally bought the OP6 mostly just to play with Android P??
Sent from my ONEPLUS A5010 using Tapatalk
Click to expand...
Click to collapse
I have a Samsung S9+. I am tired of Samsung slow updates. So I thought I would give this a try. I bought it because of faster updates and very good specs.
iamterence said:
You literally bought the OP6 mostly just to play with Android P??
Click to expand...
Click to collapse
me too....
Anybody else get prompted on their 3A today September 30th to get Android 10 even though you already have ?
I got this update several days ago. I recall reading on the internet that it was a bug fixing update, although the one I received was rather large (over 1gb)
Sent from my Pixel 3a using Tapatalk
Mine's stating 12 MB...hmmmm.
And you'll get it next month, and every month after that... all 10.0.0, but with incremental bug and security fixes. They might bump to 10.1 along the way, or maybe not. They didn't for 9.0.0, it stayed that until the end.
9878 said:
Mine's stating 12 MB...hmmmm.
Click to expand...
Click to collapse
Recall that there were actually two versions of Android 10 when it was first released (19 and 20). It's possible the difference in size is due to the different versions originally installed. Just guessing though.
Sent from my MI PAD 4 using Tapatalk
Old build QP1A.190711.019 New build QP1A.190711.020.C3
Same security date.
Anyone know of it affects magisk?
Hello all
I purchased a Pixel 4a from Verizon 2 weeks ago . This is the first google pixel phone I have bought. Well my question is is should I have gotten the update by now or does it really take 2 weeks to push out to all phones?
Steve One said:
Hello all
I purchased a Pixel 4a from Verizon 2 weeks ago . This is the first google pixel phone I have bought. Well my question is is should I have gotten the update by now or does it really take 2 weeks to push out to all phones?
Click to expand...
Click to collapse
Can't speak to the Verizon varient but the A11 update was available first thing in the morning Sept 8th on my non carrier branded 4a.
Steve One said:
Hello all
I purchased a Pixel 4a from Verizon 2 weeks ago . This is the first google pixel phone I have bought. Well my question is is should I have gotten the update by now or does it really take 2 weeks to push out to all phones?
Click to expand...
Click to collapse
Historically, it can take up to two weeks for an OTA. Did you go into settings/system/advanced/system update and check for an update manually?
Yes I've done all of that. I've even factory reset the device to see if that would trigger the update. Guess I will have to keep waiting.
Thank you for answering my question.
Steve One said:
Yes I've done all of that. I've even factory reset the device to see if that would trigger the update. Guess I will have to keep waiting.
Thank you for answering my question.
Click to expand...
Click to collapse
Then I believe your only other option is to sideload the OTA
https://developers.google.com/android/ota
Golf c said:
Then I believe your only other option is to sideload the OTA
https://developers.google.com/android/ota
Click to expand...
Click to collapse
For anyone else in this situation.
Opt into the beta that is over and the official build will be ready when you go to and check for the update.
Steve One said:
Hello all
I purchased a Pixel 4a from Verizon 2 weeks ago . This is the first google pixel phone I have bought. Well my question is is should I have gotten the update by now or does it really take 2 weeks to push out to all phones?
Click to expand...
Click to collapse
Had mine now about a week and am seeing an issue with bluetooth media playing once the phone enters screen lock/screen saver. The media stops playing until the screen wakes up again. How did this get through the beta, anyway?
I'm on Verizon Prepaid and udated to Android 11 several days ago by manually checking for updates.
Anyone knows if touchscreen bug ITS already patch(on 11 update?