Develop Bugs

Samsung pay app help

So, I got accepted into the Samsung pay beta, and I'm supposed to open the pay app, and its supposed to give me the option to install the app.
However, all I get is the same screen telling me it's coming soon.
I have a call in to Samsung pay support, but she had to escalate it to a higher tech to try and figure out what's wrong.
Anyone else in the beta have issues getting the app installed?
Sent from my SAMSUNG-SM-N920A using Tapatalk

harlenm said:
So, I got accepted into the Samsung pay beta, and I'm supposed to open the pay app, and its supposed to give me the option to install the app.
However, all I get is the same screen telling me it's coming soon.
I have a call in to Samsung pay support, but she had to escalate it to a higher tech to try and figure out what's wrong.
Anyone else in the beta have issues getting the app installed?
Sent from my SAMSUNG-SM-N920A using Tapatalk
Click to expand...
Click to collapse
If you haven't already, try running AT&T software update by going to Settings -> About Device -> Software Updates

czechpunk said:
If you haven't already, try running AT&T software update by going to Settings -> About Device -> Software Updates
Click to expand...
Click to collapse
There is no update. Spoke to Samsung, they told me to try again this evening or Sunday morning.
Sent from my SAMSUNG-SM-N920A using Tapatalk

harlenm said:
There is no update. Spoke to Samsung, they told me to try again this evening or Sunday morning.
Sent from my SAMSUNG-SM-N920A using Tapatalk
Click to expand...
Click to collapse
Bummer, sorry about that.

harlenm said:
There is no update. Spoke to Samsung, they told me to try again this evening or Sunday morning.
Sent from my SAMSUNG-SM-N920A using Tapatalk
Click to expand...
Click to collapse
I'm reading this thread because I am in the exact same boat as you. I got my invite, but my version of samsung pay isn't updated... apparently. So I guess I still wait. :crying:
---------- Post added at 11:38 AM ---------- Previous post was at 11:22 AM ----------
I just did a chat with Samsung Pay support... here is what they said....
Stella: I see that you are trying to get a Samsung pay beta for the Note 5 device with AT&T carrier.
Kevin: yes
Stella: Thank you for confirming.
Stella: I should inform you that, as of now there is no Samsung pay Beta application available for AT&T carrier. It requires a software update and update will be released from carrier. We are expecting the update as soon as possible for AT&T carrier devices.
Click to expand...
Click to collapse
So , we wait for at&t to push a update to the device. .. we know what that tends to mean... it could be hours or years.

We don't need an OTA from AT&T, we already have the app stub and the framework
Sent from my SAMSUNG-SM-N920A using Tapatalk

I was able to install last night and I am on ATT.

I'm on beta AT&T. Try rebooting your phone.

Still nothing. Very frustrating.
Sent from my SAMSUNG-SM-N920A using Tapatalk

In my case I think I might have figured out the problem... I needed to exchange my phone. I think the invitation to the beta was coded to my old IMIE number, and not my new one. So maybe that is the problem. I went into my Samsung account and deactivated my old phone, but I have a feeling it is too late. I doubt I will get another invite... though I might, who knows.

boufa said:
In my case I think I might have figured out the problem... I needed to exchange my phone. I think the invitation to the beta was coded to my old IMIE number, and not my new one. So maybe that is the problem. I went into my Samsung account and deactivated my old phone, but I have a feeling it is too late. I doubt I will get another invite... though I might, who knows.
Click to expand...
Click to collapse
Mine was attached to the wrong imei, they said they fixed it.
Still doesn't work.

Here you go. Framework first. Then app. FYI works perfectly on my AT&T note 5. http://forum.xda-developers.com/showthread.php?p=62431710

jackdforme said:
Here you go. Framework first. Then app. FYI works perfectly on my AT&T note 5. http://forum.xda-developers.com/showthread.php?p=62431710
Click to expand...
Click to collapse
Doesn't help if the account isn't provisioned properly to work
Sent from my SAMSUNG-SM-N920A using Tapatalk

I'm aware of that. But if you got the welcome to email some users aren't seeing the updates for the app and framework. Doing my part.

jackdforme said:
I'm aware of that. But if you got the welcome to email some users aren't seeing the updates for the app and framework. Doing my part.
Click to expand...
Click to collapse
I already downloaded the app and framework and it didn't work.
Sent from my SAMSUNG-SM-N920A using Tapatalk

Im on platinum status and it shows i am invited for the beta.
Im on the note 5 for at&t
Sent from my SAMSUNG-SM-N920A using XDA Free mobile app

blkghost22 said:
Im on platinum status and it shows i am invited for the beta.
Im on the note 5 for at&t
Sent from my SAMSUNG-SM-N920A using XDA Free mobile app
Click to expand...
Click to collapse
Everyone is invited, it's an open beta. But you need to wait for the acceptance email which takes a few days. I've gotten mine, but it still won't let me access it.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my SAMSUNG-SM-N920A using Tapatalk

Thanks good to know.
Will wait and see
Sent from my SAMSUNG-SM-N920A using XDA Free mobile app

works like a charm for me got the invite within 24 hours
Only three places it didn't work at.
1.) Taco Bell - had some weird card reader integrated into the bottom of the register.
2.) Twistie Treats - they had a magnetic reader fed by a wire into an iPad
3.) Gas station - only tried one but the typical swipe one where you insert the card it wouldn't read
Otherwise, it worked great everywhere else. My first try was at our local supermarket. Worked there easily. Then onto Saturday night partying and drinking. I was playing around with our waitress all night and at the end in my drunken state I said let me come up to your terminal and pay with my phone. She thought I was full of crap (since I was rather drunk) but she was shocked when it authorized the transaction.
Let's see, I had another place tell me we don't accept mobile payments yet. I told her that this one you will and she was like
Lastly, just a couple of malls and Best Buy to round it off all worked great. It was an expensive weekend.

I have the worst issue too.
I can't install the app even when I was invited.
This is part of the conversation with the Samsung Live chat guy.
Jonathan: is a Samsung Galaxy Note5, 64GB, (AT&T), Black Sapphire MODEL NUMBER: SM-N920AZKEATT HEX/IMEI #: ************5
Stark: Thank you for the details.
Jonathan: Ok
Stark: I have checked the details and your device is linked to your Samsung ID. You should see an install option, as you are unable to see the details, I will escalate the issue to our next level team.
Stark: Please provide me with the Android version and Baseband version and your working phone number.
Jonathan: ok
Jonathan: My number is ***-**-****. Android Version 5.1.1 and Baseband N920AUCU1AOGG
Stark: Thank you.
Stark: I have escalated the issue to our next level team, you will be contacted back in 1 to 2 business days.
So, that's all I got. I'LL WAIT THEN.

Marshmallow update

Really dont understand why it takes so long for the update for a "flagship device"? Focusing on pushing more hardware without taking care of your existing customer's is bad PR IMO. I just want to try something new

ssmr2t said:
Really dont understand why it takes so long for the update for a "flagship device"? Focusing on pushing more hardware without taking care of your existing customer's is bad PR IMO. I just want to try something new
Click to expand...
Click to collapse
I understand where you are coming from. I am looking forward to the update also but I would rather have an update that is finished then get an update that kills my battery life or has more bigs than a cheap whore.
Sent from my SM-G928T using XDA Premium HD app

Samsung probably already gave the rom to T-Mobile. T-Mobile then adds their stuff like wifi calling, VoLTE, advanced messaging, etc, then once they're done testing it for stability they push it out. So really it's not just samsung were waiting on.

Nexus comes stock with it. Google gave T-Mobile the firmware long ago.

We probably won't get an update until the s7 comes out, or worse case scenario when the new note and edge plus come out....sad but true

chronos7 said:
We probably won't get an update until the s7 comes out, or worse case scenario when the new note and edge plus come out....sad but true
Click to expand...
Click to collapse
That's what I figured too...they want to push people to buy new products, probably won't come out till two months the after release of the S7 I'm guessing.

Djspinister said:
Nexus comes stock with it. Google gave T-Mobile the firmware long ago.
Click to expand...
Click to collapse
Yes they may have the Firmware from Google for the nexus but that doesn't mean it works with Samsung's phone. They will still have to test the modem and make sure it works well on their network. Still need to test stability with the firmware from Samsung.

When i get update to 6.0 for SM-G928T?
Thanks for help!

tomitsa18 said:
When i get update to 6.0 for SM-G928T?
Thanks for help!
Click to expand...
Click to collapse
Probably toward the end of this year

michintom said:
Probably toward the end of this year
Click to expand...
Click to collapse
Sprint getting their update next month

It's kinda sad a phone that's 2 years old vzw lgg3 getting M before a flag ship that's only few months old
Sent from my SM-G928T using Tapatalk

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Srikar_NBK said:
Click to expand...
Click to collapse
That is for the unlocked model. Also, T-Mobile needs to add bloatware and test, which would take a few months probably.

I can never understand why people care about these mediocre updates sometimes, that even breaks the phone at times. When it comes it comes as long as it comes within a 6- 8 months of google releasing it im fine. The software on this phone is excellent now.

Because a lot of these people live t update things. Just keep wanting to update and not satisfied with current things. Sad really.

The t-mobile visual voice-mail update to support android 6.0 is a good sign.
Sent from my SM-G928T using XDA Premium HD app

Even Samsung just updated apps M support. We'll just have to wait and see
Sent from my SM-G928T using Tapatalk

cpugeeker said:
I can never understand why people care about these mediocre updates sometimes, that even breaks the phone at times. When it comes it comes as long as it comes within a 6- 8 months of google releasing it im fine. The software on this phone is excellent now.
Click to expand...
Click to collapse
Are you daft? The jump from L to M had a plethora of awesome features. And no, when all these other phones have M already it seems kind of ****ty that samsung, the biggest android phome manufacturer, is dragging behind like this.
---------- Post added at 02:48 AM ---------- Previous post was at 02:46 AM ----------
Maknora said:
Because a lot of these people live t update things. Just keep wanting to update and not satisfied with current things. Sad really.
Click to expand...
Click to collapse
Lol i dont know how people like you even end up at xda. Its all about doing what you want with your phone, which is getting harder and harder these days.

The new edge features in marshmallow looks sick, finally a really use for it imo. Hurry the eff up Samsung

otariq said:
The new edge features in marshmallow looks sick, finally a really use for it imo. Hurry the eff up Samsung
Click to expand...
Click to collapse
At this rate I expect to have swapped to an S7 Edge before the S6 Edge+ gets Marshmallow. Thank god for Jump! On Demand

Has anyone received the January Security Update via OTA?

So it's now January 18th and I've yet to receive the security update for January. Has anyone received it, via OTA?
Quite frankly I'm surprised that Google can be so late pushing it out given that there are probably not even 250,000 people who bought the thing.

Wouldn't surprise me if Google are holding off on it until a massive update is ready to fix/help other issues

Google will be lucky if 25,000 people bought the thing AND kept it.

undertaker2k14 said:
Google will be lucky if 25,000 people bought the thing AND kept it.
Click to expand...
Click to collapse
not sure they care about sale numbers.
Like previous Pixel devices, it's mainly for done for internal usage, PR, aura, showcase, exploring, reference platform, etc. And to acquire knowledge on how to build such devices.
The fact that they sell it to anyone is a just a bonus for fans and tech enthusiasts.

kgersen said:
not sure they care about sale numbers.
Like previous Pixel devices, it's mainly for done for internal usage, PR, aura, showcase, exploring, reference platform, etc. And to acquire knowledge on how to build such devices.
The fact that they sell it to anyone is a just a bonus for fans and tech enthusiasts.
Click to expand...
Click to collapse
interesting point. it would explain the lack of testing. but it does not explain the web site or many of the AMA answers or the AMA itself. google is certainly getting well deserved training on the return process with this device.

Yeah, I'm curious as well. Looked like the binaries had some pretty big updates

andreoidb said:
Yeah, I'm curious as well. Looked like the binaries had some pretty big updates
Click to expand...
Click to collapse
anyone get it ever, lol, its basically February. If no one got the January update, that does not bode well for future update support

Typically the images are posted to the developer website before any OTAs go out. No updated image has been posted (other than MXB48K, which we know isn't a January update), so I wouldn't expect any OTA.

ckevinwelch said:
Typically the images are posted to the developer website before any OTAs go out. No updated image has been posted (other than MXB48K, which we know isn't a January update), so I wouldn't expect any OTA.
Click to expand...
Click to collapse
Yeah, ik, It is weird since they did say they would be on a 6 week update cycle. Still nothing. Not a great sign, guess they are trying to work out the WiFi and touchscreen issues in the first update. They probably tough to fix

andreoidb said:
yeah, ik, it is weird since they did say they would be on a 6 week update cycle. Still nothing. Not a great sign, guess they are trying to work out the wifi and touchscreen issues in the first update. They probably tough to fix
Click to expand...
Click to collapse
6.0.1 (mxb48j) is out since today

nbpf said:
6.0.1 (mxb48j) is out since today
Click to expand...
Click to collapse
Does this new update include the February 1st security update? If so, could you provide a screen capture?

MXB48T was the latest firmware if not mistaken , but still no OTA release yet , expected comin next week
http://www.androidcentral.com/googles-first-pixel-c-update-now-available

TokyoGuy said:
Does this new update include the February 1st security update? If so, could you provide a screen capture?
Click to expand...
Click to collapse
I do not know. You would like a screen capture of what?

Just bought the Pixel C and it came with 6.0. I haven't been promoted to update to 6.0.1 but I'm wondering if 6.0.1 is the OTA update or if I should just flash the factory image?
Also, is then 6.0.1 update the one that moves the buttons to opposite edges?
Thanks.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

bigboimike21 said:
Just bought the Pixel C and it came with 6.0. I haven't been promoted to update to 6.0.1 but I'm wondering if 6.0.1 is the OTA update or if I should just flash the factory image?
Also, is then 6.0.1 update the one that moves the buttons to opposite edges?
Thanks.
Click to expand...
Click to collapse
Whoa you should have been prompted to update to 6.0.1 right away there's not even a 6.0 factory image.

seems this pixel c was really beyond what they promises to delivered. every 6 weeks for new update. in fact nexus brand can get update almost on time.

bigboimike21 said:
Just bought the Pixel C and it came with 6.0. I haven't been promoted to update to 6.0.1 but I'm wondering if 6.0.1 is the OTA update or if I should just flash the factory image?
Also, is then 6.0.1 update the one that moves the buttons to opposite edges?
Thanks.
Click to expand...
Click to collapse
Same here. I had a warranty issue with my first Pixel, the replacement they sent me is also on 6.0, with no OTA to 6.0.1.
But honestly it seems to work better.
---------- Post added at 05:17 PM ---------- Previous post was at 04:34 PM ----------
In an attempt to ask Google why my device is still on October Security Patch and no 6.0.1 Update on my warranty replacement Pixel.

So I guess I just had to wait. I avoided flashing the 6.0.1 update since I had already set up my tablet using the "Setup my device" feature through Google Now from my 6P. Last night my Pixel C was prompted to install the 6.0.1 update and updated fine. I'm unsure of what be features are added other than security, but my home and back buttons are moved to the left while recent apps button is on the right. So I guess it worked. That and the fact that under about tablet it says 6.0.1 ha-ha.
It seems to run a bit smoother now so, there's that.

I got the OTA udpate last night. I am in San Diego, CA.

Yesterday I received MXB48T OTA update on my 32GB pixel C. The inconsistent WiFi speeds issues have not been solved.
Enviado desde mi Pixel C mediante Tapatalk

Baseband on phone is different than what TMO says it is

so i looked on TMOs site at the software update page and it shows the august update, which i took OTA before i rooted with CFAR
on my phone my baseband is M8998TMO_24.71.01.87R NUS
but TMO says it should be M8998TMO_04.17.01.76R
https://support.t-mobile.com/docs/DOC-35970
is it different because of CFAR?

Their website hasn't been updated. They didn't match up since the release of the phone.
Sent from my Moto Z (2) using Tapatalk

Lol figures

Midnight_Rider said:
Lol figures
Click to expand...
Click to collapse
They even said it doesn't support T-Mobile video calling but it does and also has duo preinstalled. You can test it out. Throw it in airplane mode and turn on wifi. You can't place a video call unless you use the duo app. If you turn cellular back on you can use the dialer built in one.
Sent from my Moto Z (2) using Tapatalk

so the .87R is the newest one? that is what I'm on, but I have the June security patch

CadillacMike said:
so the .87R is the newest one? that is what I'm on, but I have the June security patch
Click to expand...
Click to collapse
That's the version I am on. There was an update almost as soon as the device came out. What carrier are you on?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Nexus 5X using Tapatalk

T-Mobile

looks like i have a different kernel as well. how does that get updated? via OTA as well? I'm on the moto support forum, but not getting any responses about the security patch

CadillacMike said:
looks like i have a different kernel as well. how does that get updated? via OTA as well? I'm on the moto support forum, but not getting any responses about the security patch
Click to expand...
Click to collapse
You didn't get the last update? Should have had one since the device was released.
Sent from my Nexus 5X using Tapatalk

That's the thing we haven't got it yet we're still factory

joemossjr said:
That's the thing we haven't got it yet we're still factory
Click to expand...
Click to collapse
So you are on T-Mobile also? I don't remember hearing others but the T-Mobile version getting an update.
Sent from my Nexus 5X using Tapatalk

Yup, this is my 3rd Z2 Force. The other ones had an update, I just didn't remember the details.
This one I have had since October 3rd, got it from a physical corporate T-Mobile store, no updates since I have had it.
I even tried swapping the SIM card hoping it would Kickstart something

Is anyone still on the initial release build with the baseband listed on tmo's website? [M8998TMO_04.17.01.76R]
If so, could you boot into fastboot mode and do "fastboot getvar all" from terminal?
I'd like the "ro.build.version.full" value so I can try to find the first OTA to NCX26.122-49.

I'm still stuck on the June 1, 2017 security patch. T-Mobile Z2 Force, have been using the phone for almost a month. No update.

I am still on June 1st with a Tmo Z2 Force

sixteasy00 said:
I'm still stuck on the June 1, 2017 security patch. T-Mobile Z2 Force, have been using the phone for almost a month. No update.
Click to expand...
Click to collapse
CadillacMike said:
I am still on June 1st with a Tmo Z2 Force
Click to expand...
Click to collapse
T-Mobile pulled the update

Midnight_Rider said:
T-Mobile pulled the update
Click to expand...
Click to collapse
Source?
Sent from my Pixel 2 using Tapatalk

Tidbits said:
Source?
Click to expand...
Click to collapse
Well it would seem odd T-Mobile's update won't flash with unlocked bootloaders but Sprint's will. Sprint's users are on September security patch now...
Edit: if you look at OP's hyperlink, you'll see TMobile says only original software is currently available...

Uzephi said:
Well it would seem odd T-Mobile's update won't flash with unlocked bootloaders but Sprint's will. Sprint's users are on September security patch now...
Click to expand...
Click to collapse
If you at the source of the update file it belonged to Lenovo. Also with the amount of people who have troubles with texts and notifications Motorola could have pull it themselves.
Sprint version firmware is different than T-Mobiles and isn't a good gauge. It's not like the whole 6P thing going on.
Sent from my Pixel 2 using Tapatalk

Tidbits said:
If you at the source of the update file it belonged to Lenovo. Also with the amount of people who have troubles with texts and notifications Motorola could have pull it themselves.
Sprint version firmware is different than T-Mobiles and isn't a good gauge. It's not like the whole 6P thing going on.
Click to expand...
Click to collapse
Yes, version is different, but the only logical explanation is either Lenovo or Tmo pulled the update since other models are updating fine and users were getting the update until recently, but other phones are still able to update to August and September security updates.

Update from Verizon - Pulled Back?

There was an update for my Verizon Note 10+ 5G which supposedly failed and was successfully rolled back. I checked again and tried the PC tools which give me an error message saying my firmware is not compatible with the PC update tool. (I am NOT rooted.) I checked again OTA and now it says there is no update which means Verizon must have pulled it! I see no issues operationally with the phone - Note my s/w version as well. Anybody else run into this?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
View attachment 5086869View attachment 5086871
Sent from my SM-N976V using Tapatalk
View attachment 5086881

With AT&T I'm more afraid of their updates and automated downloads/flashes than malware... lol, still on Pie.
Best to keep updates blocked, let it roll out and see how many get rolled over by it.
Give it a couple weeks and then decide.
With Q I'm still not satisfied enough to load it and as such the backlog of security updates remain pending.
Whatever.

KruseLudsMobile said:
There was an update for my Verizon Note 10+ 5G which supposedly failed and was successfully rolled back. I checked again and tried the PC tools which give me an error message saying my firmware is not compatible with the PC update tool. (I am NOT rooted.) I checked again OTA and now it says there is no update which means Verizon must have pulled it! I see no issues operationally with the phone - Note my s/w version as well. Anybody else run into this?
Sent from my SM-N976V using Tapatalk
View attachment 5086881
Click to expand...
Click to collapse
I don't think it was pulled. I got the update a couple of days ago with no failures.
I have the Verizon Note 10+ 5G. Stock not rooted.
Sent from my SM-N976V using Tapatalk
View attachment 5087077

Then why does it say my upgrade failed but I have the most up to date version!?!?? What build do you have, does it match the build number in the photo shown of my phone?
Sent from my SM-N976V using Tapatalk

Girlfriends Verizon version got an update. She makes it known to tell me because of bad experiences with Verizon updates . I don't know what happened with hers though. She uses her pixel 4 as her personal but I'll ask.

coilbio said:
Girlfriends Verizon version got an update. She makes it known to tell me because of bad experiences with Verizon updates . I don't know what happened with hers though. She uses her pixel 4 as her personal but I'll ask.
Click to expand...
Click to collapse
Thank you for your reply but mine is specific to the Note 10+ 5G, so what you suggest is like comparing Apples to Oranges. I have noticed also as you can see by the photos originally supplied, although it tells me the update failed, the software version has changed and that may be why it also says there is no update available. I may actually be running the later version or not, there is no way to really tell, either way it was handled very sloppily by Verizon and is concerning.
However, I have also heard, Google will be discontinuing the Pixel line of phones so as they say, every company is screwed up, they are just screwed up different ways...!
Sent from my SM-N976V using Tapatalk

I was talking about her note, she has 2 phones.

The August update is a battery hog and it's also caused Bluetooth issues. If I didn't have to wipe the phone, I'd go back to the July update. Maybe enough people complained and they quietly pulled it.

Guyinlaca said:
The August update is a battery hog and it's also caused Bluetooth issues. If I didn't have to wipe the phone, I'd go back to the July update. Maybe enough people complained and they quietly pulled it.
Click to expand...
Click to collapse
Once I get a stable load that's running well, I leave it alone. Been running both Windows and Android like this for many years with very little trouble. As you are keenly aware of tracking down an update issue can be very time consuming*. Many times a hard reset due to malware be easier. Malware on Android has caused me only one hard reset in over 6 years.
I herd dinosaurs, lol, I take a conservative approach to updates because many times the cure is worse than the disease. A bare bones updated Windows or Android machine runs faster... I hate waiting.
Carriers are partnered with Samsung and jam their own crapware and app graphics "updates" in their too on OS upgrades.
These can make it usable... I remember the horror of Lollipop on my S4+, destroyed it... thanks AT&T. Not.
That's one reason I'm still running on Pie... with no issues.
*may be a settings issue. My Pie load runs best with all power management turned off especially 3rd party including Samsung. A new update means a Google search won't yield many solutions for it.
The first app I block is AT&T updates... no joke.

KruseLudsMobile said:
Then why does it say my upgrade failed but I have the most up to date version!?!?? What build do you have, does it match the build number in the photo shown of my phone?
Sent from my SM-N976V using Tapatalk
Click to expand...
Click to collapse
I don't know. Look up that error code 410.
Like I said, I don't think it was pulled.
Sent from my SM-N976V using Tapatalk

Guyinlaca said:
The August update is a battery hog and it's also caused Bluetooth issues. If I didn't have to wipe the phone, I'd go back to the July update. Maybe enough people complained and they quietly pulled it.
Click to expand...
Click to collapse
Odd. I'm not having battery or BT problems.
Sent from my SM-N976V using Tapatalk