Related
Taken from the official Sprint thread here:
http://community.sprint.com/baw/thread/43883?start=540&tstart=0&reqsorting=dec
"Good news - an update will be released tomorrow 9/30. It will be rolled out over a 4 day period so not everyone will get it on day 1.
I will have the standard MR information (fixes included, rollout schedule, etc) available tomorrow morning and will post it in a new featured thread."
AWESOME!
yea, the day after the 30 days is up for people that bought on the first day, so not really that awesome, lets just pray it fixes the problem. I'm not really optomistic to be honest. Just to convenient to hold off like this.
Second update since release. I do have to admit, it's kind of nice to see Samsung actually supporting a phone for once.
This is great news! And we are getting Cyanogen Mod 6! I couldn't be happier. :-D
robl45 said:
yea, the day after the 30 days is up for people that bought on the first day, so not really that awesome, lets just pray it fixes the problem. I'm not really optomistic to be honest. Just to convenient to hold off like this.
Click to expand...
Click to collapse
While I understand where you're coming from, I agree with styckx that it's just good to see them doing something about it. I do wish they'd acted on this more quickly, but better to roll out a fix now than wait months to release one or not release one at all.
It's crazy to hear people complain about updates from Samsung from my perspective. I'm a Touch pro 1 owner that basically received no updates from Sprint/HTC. And previous to that was the Mogul that went months without an advertised feature (Rev A/GPS). I'm way more wary about HTC than Samsung.
Epic ordered finally here. Was waiting for 10/1.
fooo1 said:
It's crazy to hear people complain about updates from Samsung from my perspective. I'm a Touch pro 1 owner that basically received no updates from Sprint/HTC. And previous to that was the Mogul that went months without an advertised feature (Rev A/GPS). I'm way more wary about HTC than Samsung.
Epic ordered finally here. Was waiting for 10/1.
Click to expand...
Click to collapse
It stems from Samsung's history, mainly with the T-Mobile Behold 2. They advertised that it would be getting Android 2.x then never delivered on their promise and stranded users with 1.6. While HTC has probably been the best manufacturer in terms of supporting their Android phones.
I had a launch day Hero, and I don't think support was the fastest for that either. Most everything I did through XDA and androidforums.<---alot faster than waiting for the manufacturer/carrier to roll out and update.
Just my thoughts...
Chris
cswee1932 said:
I had a launch day Hero, and I don't think support was the fastest for that either. Most everything I did through XDA and androidforums.<---alot faster than waiting for the manufacturer/carrier to roll out and update.
Just my thoughts...
Chris
Click to expand...
Click to collapse
I've read a lot about Samsung after purchasing my Samsung Moment. I found they had a nice history of let downs and lack of support. Then the Moment went on and on without a mention of a fix, or patch, or anything. That was a complete lemon of a phone (data lock ups and unfixable GPS) that Samsung all but abandoned less than a year after launch and still to this day the Moment forums are mainly filled with people trying to fix data lock ups and the GPS. It's ashame really.
Epic was going to be my last run with Samsung, and despite some bumps in the road I've been pleased so far as they are at least taking initiative with this phone it seems. I personally think they have no choice. It's one thing to piss off 1 carriers customers, and another to piss off multiple carriers customers by not supporting a phone.
Hope the support continues.
so you guys are excited that they put out an update that fixed nothing and screwed up the phone? thats great, all it meant is I had to go and uninstall the mediahub crap so my battery life didn't suffer, the gps issue remains, the upload issue will likely remain after this update as well. so that really equates to them doing nothing in my eyes.
I've never experienced a upload cap on my phone. Does anyone know if this update includes other fixes other than just the 3g upload cap?
crajee16 said:
I've never experienced a upload cap on my phone. Does anyone know if this update includes other fixes other than just the 3g upload cap?
Click to expand...
Click to collapse
Have you ran the Speed Test app on 3G? I've yet to see anyone get over a stable 150kbps (sure it bounces upwards towards 200 on occasion but then levels out). From working in hosting it shows exact throttling behavior, as it uploads it jumps past the 150 mark to around 170-180 and then down to a stable 150 almost immediately. It's hard to believe this to be some sort of coincidence since it's able to be replicated in many different 3G markets across the country.
punzada said:
Have you ran the Speed Test app on 3G? I've yet to see anyone get over a stable 150kbps (sure it bounces upwards towards 200 on occasion but then levels out). From working in hosting it shows exact throttling behavior, as it uploads it jumps past the 150 mark to around 170-180 and then down to a stable 150 almost immediately. It's hard to believe this to be some sort of coincidence since it's able to be replicated in many different 3G markets across the country.
Click to expand...
Click to collapse
Lol, mine actually goes to like 6000+ for a little while, then dips down to under 50 kbps. Yes, under 50! I have some SpeedTest results that have come in under 20 kbps upload!
Even my 3G speed is horrible. Never over 500 download. I'm looking forward to this. Luckily I am usually either in a WiFi zone or a 4G zone.
punzada said:
From working in hosting it shows exact throttling behavior, as it uploads it jumps past the 150 mark to around 170-180 and then down to a stable 150 almost immediately.
Click to expand...
Click to collapse
It may seem to be throttling behavior. Ultimately though, those of us aware of how a data radio and associated software *actually works* know full well that it's because the dwarf hamsters spinning in their wheels are, in fact, unionized. Because of the upload tragedy of 2009, in which millions of poor hamsters perished on the Touch Pro 2 because of faulty speed governors installed in the cages, strict regulations were put in place for the Epic, dictating that no hamster may run unsupervised in their wheels, and that they must trade off shifts every 128kB with their spotting partners. It's this switching that causes the fluctuations you observe during the speedtest runs. You may have noticed a bit more heft in the Epic vs say, the Captivate. You might mistakenly believe it's the keyboard, when in fact it is the added weight of the supervisory hamsters.
Another shortfall in communications speed arises because Samsung, to save weight from the added hamsters, decided to use smoke signals as a databus between the CPU and the baseband processor. This was chosen over the "flashing mirrors" approach due to cost and weight issues. This compounds the upload cap problem because as the phone rests in your pocket, it accumulates moisture. The soot particles from the smoke then seed rainclouds, which can interrupt the dataflow between baseband and CPU as the receiver operators duck for cover at a nearby tavern.
So, you see, this is clearly a compound problem. Obviously, this week's update will include a staff of more hamsters, more wheels, and dehumidifiers, all so your phone can shuttle data more efficiently. This is a brilliant feat of engineering, I might add. So, expect your phone to weigh more by the end of the week, though how much more, nobody knows. And please, do post the truth about how the phone's internals really work, punzada... anything else would be a blatant disservice to the hard-working bit-crunchers in your phone.
^^ wat
Also from that thread:
Desi,
I'm on the phone right now with tier 2 support to try to find out what's in the update because this is my last day if I'm going to return the phone and I'm being told that they don't see anything about the battery life, GPS, or this data upload issue in this release.
I know you said that you're putting that information up tomorrow, but I have to make a decision today.
The tech is saying there is NO FIX FOR THE CAP ISSUE FROM SAMSUNG yet or anything to improve the battery.
Click to expand...
Click to collapse
Desi's (admin) reply:
Joe,
The 3G upload issue is definitely in the release.
I doubt the GPS issue is since I just forwarded input from this forum over to engineering for further analysis.
Click to expand...
Click to collapse
I guess we will have to see if it actually fixes anything. But it seems like tier 2 is at least finally aware of (or admitting to) the problem with the upload. Doesn't sound like there will be anything for the battery or GPS though.
GlassGorilla said:
I guess we will have to see if it actually fixes anything. But it seems like tier 2 is at least finally aware of (or admitting to) the problem with the upload. Doesn't sound like there will be anything for the battery or GPS though.
Click to expand...
Click to collapse
Battery and GPS are (for me, anyway) easy workarounds. 3G upload cap is what it is; there's no getting around it other than using wi-fi or 4G (which I can also usually do, but not everyone can).
I'll be happy to have that upload cap fixed if for no other reason than people will quit using it as an excuse to post "should I return my Epic for an Evo?" threads here and elsewhere.
My feeling is the amount of pressure on Sprint had an affect on how hard they pushed samsung.
That and the fact that until a few days ago users were being told for weeks running that no one but they were reporting the problem exacerbated the problem.
So it s a cause for celebration that they are pushing out a fix, but I don't think it is at all established that this would have occurred so soon if it where not for all the noise.
As far as GPS, not only are there problems, but the "advice" given by Sprint: use the unrelated "wireless networking" is an absolute laughable and patronizing dodge.
As others have noted, working around with cold starts or manual resets does fix the main issue.
I have been in contact with the moderator of eh Sprint forum privately some time ago, and he put me in with ADP (ADP, not ADS) on this issue. They are diagnosing it, and have not come to any conclusion other than they have seen the issue themselves.
aero1 said:
My feeling is the amount of pressure on Sprint had an affect on how hard they pushed samsung.
So it s a cause for celebration that they are pushing out a fix, but I don't think it is at all established that this would have occurred so soon if it where not for all the noise.
Click to expand...
Click to collapse
Well. Apparently we have a voice, which is a good thing.
I'm hopeful, but I am not holding my breath. I think it is likely the vast majority of Epics were pre-ordered or bought on launch, 08/31. 30 days would be 09/30. The announcement could be an attempt to get people who bought on launch that were going to return it on the last day to keep their phones, and then when the update doesn't "may increase" or "possibly enhance" or whatever the legal gymnastics statement said, those people can't return the phone any more and Sprint isn't really under any obligation to fix it.
Whether it's an angleshoot or a genuine attempt to fix it, I am anxiously awaiting the first reports tomorrow.
GlassGorilla said:
I think it is likely the vast majority of Epics were pre-ordered or bought on launch, 08/31. 30 days would be 09/30. The announcement could be an attempt to get people who bought on launch that were going to return it on the last day to keep their phones, and then when the update doesn't "may increase" or "possibly enhance" or whatever the legal gymnastics statement said, those people can't return the phone any more and Sprint isn't really under any obligation to fix it. .
Click to expand...
Click to collapse
Sprint is serious exposed to class action liberality, which involves not just awards, but legal costs, and more importantly really bad press.
I have a written note from ecare from last week saying no one has reported this issue. Hundreds of users seem to have been told the same thing. Not that the speeds are normal, but that they were low speeds but unique to the customer. That presents a legal liability for Sprint right here.
I think we will all know in a few days.
You guys should probably take a chill pill on the conspiracy theories already. I'm sure it would cost Sprint much less money and hassle just to fix this software issue rather than go out of their way to "conveniently" tell you that there's a "fix" that doesn't really exist but they used their "legal gymnastics" to trick you into holding onto your phone past the 30 day mark. They are a company that wishes to exist more than 2 more years, why would they go out of their way to screw you and guarantee you leave in two years when a couple of patches could save them and Samsung a ton of customers?
Its not like fixing this issue requires the recall and replacement of every phone, and them fixing this problem is not an incredibly inconvenient issue. You know why they're telling you the day before your 30 days that the update is coming? Because telling you after you return the phone wouldn't do anyone much good. Why didn't they tell you sooner? Because these things, while not impossible or some ludicrous endeavor, do take time.
I'm not even meaning to take their side really. Sure, they should have caught the issue before launch, and they should have addressed the issue in public... but if you're only gonna sign onto networks willing to do either of those things then you're not going to be purchasing a cell phone in America. I mean, Steve Job's stance on Antennagate is still "Shut up whiny babies, this issue doesn't exist, but I'll give you a free case if you shush and go back to fellating me..."
I saw a tweet by tmobile, talking about some ridiculous speed test score by the new Samsung Galaxy S 4G...and I was wondering, how much would hardware affect data speeds, and network connectivity?
Remember always, in high technology, that there are three types of lies: lies, damned lies, and benchmarks.
Don't put too much credence in them, even the ones you perform yourself.
jggimi said:
Remember always, in high technology, that there are three types of lies: lies, damned lies, and benchmarks.
Don't put too much credence in them, even the ones you perform yourself.
Click to expand...
Click to collapse
haha, like it. Yea... it didn't make too much sense to me. Either way I wouldn't switch, I LOVE this phone.. was just curious really.
http://www.engadget.com/2011/02/23/atandts-brewing-hsupa-gate-the-inside-story/
Though it really came to a head with the recently-launched Inspire 4G, users have noticed that there really aren't many phones in AT&T's stable that deliver stellar upload speeds -- the Atrix 4G is suffering the same sub-megabit performance, as are older devices that should seemingly support HSUPA like the Samsung Captivate.
We've chatted in the past few days with a source who offers an interesting explanation: AT&T currently requires that all handsets that it sells "handshake" with the network as 3GPP Release 5 devices, the last official set of 3G specifications that lacked support for HSUPA. That feature -- also known as EDCH, or FDD Enhanced Uplink -- was added in Release 6. Though AT&T is apparently working on permitting the bulk of its handsets to handshake Release 6, presently only the iPhone 4 (and presumably all of its recent data devices like USB modems, which may also use Release 7) are allowed. Neither we, nor our source, know why this is. Our source believes that the Release 6 certification may happen within a "month or two," which would explain why some AT&T sales reps in live HSPA+ areas are telling customers that the "4G network" isn't live yet.
You can form your own conclusions as to why AT&T might be imposing this arbitrary limitation, but we do know that "enhanced" backhaul figures prominently into the company's 4G story; there may be concerns that flipping on HSUPA for everyone right now would overwhelm its legacy infrastructure. At any rate, it sounds like this could all be solved soon through a combination of network changes and possibly firmware updates for individual devices, so let's keep our fingers crossed.
Click to expand...
Click to collapse
discuss.
domin8 said:
http://www.engadget.com/2011/02/23/atandts-brewing-hsupa-gate-the-inside-story/
discuss.
Click to expand...
Click to collapse
We already are, in a thread that's already been created & currently sits right above yours. Did you miss it?
http://forum.xda-developers.com/showthread.php?t=955933
The next time you get an urge to create a new thread, please use the Search button instead.
perdurabo2 said:
We already are, in a thread that's already been created & currently sits right above yours. Did you miss it?
http://forum.xda-developers.com/showthread.php?t=955933
The next time you get an urge to create a new thread, please use the Search button instead.
Click to expand...
Click to collapse
i found this useful as it's own thread. relax.
Ran across this article, and figured I would post it here as a heads up
Google, Samsung and Sprint probe Nexus S problems
Users say photos are being deleted, but cause remains unclear
Computerworld - Sprint, Samsung and Google are investigating customer complaints about problems with Nexus S smartphone connections and the deletion of photos taken with the devices, a Sprint spokesman said.
"We are aware of the connectivity reports being brought forward by a small number of Nexus S 4G customers," a Sprint spokesman said via email late yesterday. "Google, Sprint and Samsung are examining these reports and though we have not yet been able to identify any specific causes, we are working to determine exactly what our customers are experiencing."
Sprint began selling the Nexus S 4G May 8, although the reported problems are not specific to Sprint alone. Nexus S smartphones can be bought unlocked from any carrier and are sold by carriers around the globe in slightly different configurations, depending on the network.
Nexus S is an Android 2.3 (Gingerbread) device, and some customers have blamed upgrades of other smartphones to Android 2.3 for similar problems. Two other major U.S. carriers, Verizon Wireless and T-Mobile USA, did not respond to requests to comment, nor did Samsung or Google. An AT&T spokeswoman said that AT&T has not seen the problems.
Users for months have reported that their photos are being deleted from the Nexus S phones, according to various online user forums. Some have linked the missing photo problem with connections to a network, although there doesn't seem to a consistent explanation.
One UK-based Nexus S user said via email that he bought his device unlocked through Carphonewarehouse without a SIM card, although he uses the Orange network for connectivity.
The UK user, Julian Bhardwaj, described his problem this way: "Photos are randomly deleted from the phone. There seems to be no apparent pattern or cause to what or when photos are deleted, only that anyone using the Nexus S or a phone which they have upgraded to Android 2.3 has this issue. This problem seems to be ongoing since around the beginning of the year, just after Android 2.3 and the Nexus S was released.
"The only word from Google on this issue so far seems to be that the problem is not 'reproducible' so they cannot investigate it. For myself and many other Nexus S users, this is extremely frustrating. This is a critical flaw with the phone/operating system...."
Google's own mobile help form has a thread with 49 comments on the problem dating back to Jan. 3.
One person, "droid_ns," reported having 500-plus photos disappear from the Nexus S Gallery, and said: "This is unacceptable!"
A Google employee on the forum identified only as "MrEvan" apologized for the deleted photos on April 19, but said he wasn't "seeing a ton of consistency in reports" and asked for detailed information. "I'm so sorry to hear about your troubles here," MrEvan said. "I know how important photos are!"
On May 3, MrEvan posted: "Thanks for the responses. Seems like you are all having slight different experiences, but I'll pass your reports along and see what we can find!"
Some of the users on the forum reported using Sprint or T-Mobile USA as their carrier, but most did not indicate a carrier and blamed the problem on a bug in the Nexus S or Android 2.3 or both.
A developer forum, Forum.xda, also has comments regarding the problem, but only from March 2.
One user on the NexusOneForum, "jwagner3," indicated there could be some problem with missing photos that is related to the strength of the network connection being used. The commenter said that over a weak cellular signal at work, pictures appear to be missing, but at home on Wi-Fi, the pictures are all there.
Wi-Fi usually offers greater bandwidth for data than 3G cellular, and greater bandwidth is important to the transmission of photos and videos.
The Sprint spokesman said the Nexus S is one of Sprint's best selling devices and most users are "very happy" with their experience with it.
Click to expand...
Click to collapse
DCRocks said:
Ran across this article, and figured I would post it here as a heads up
Click to expand...
Click to collapse
Photos disappear and reappear based on signal strength? WTF? I'll eat a shoe if that's true.
The photos aren't actually being deleted. I had this problem without realizing it right after I rooted, but I only had one picture so it actually showed up after a while. Basically what happens is that the phone gets tied up looking for signal and stops doing whatever it was doing, such as loading photos. It took almost 5 minutes to load my one photo, so I can imagine that people just assumed the photos were gone. There are a few other things that stop being responsive randomly, such as fruit ninja. While on wifi the problem goes away because it is all related to the radio, which is looking for CDMA signal and some other signal that it can'y pick up, so all of the phone resources go to looking for signal until it switches back to CDMA.
Someone else can explain this more appropriately, but thats the basic jist of it
Thank you, that was nice and simple explanation. I generally ignore radio complaints, they are usually *****ing and whining, not realizing phone service
can suck depending on where you are (my vacation homes have the worst
signal, so I have just learned that is the way it is). It is also not the tendency
to have happy users get on these forums and rave.
So fortuntely this has not happend to me, but I'm glad I read and learned
something just in case, especially when I'm in one of those roam or almost
roam areas.
redandblack1287 said:
The photos aren't actually being deleted. I had this problem without realizing it right after I rooted, but I only had one picture so it actually showed up after a while. Basically what happens is that the phone gets tied up looking for signal and stops doing whatever it was doing, such as loading photos. It took almost 5 minutes to load my one photo, so I can imagine that people just assumed the photos were gone. There are a few other things that stop being responsive randomly, such as fruit ninja. While on wifi the problem goes away because it is all related to the radio, which is looking for CDMA signal and some other signal that it can'y pick up, so all of the phone resources go to looking for signal until it switches back to CDMA.
Click to expand...
Click to collapse
Makes perfect sense.
I had to photo issue. I deleted a few and the entire thread disappeared. I backed out, came in and the ones I didn't delete were there. Some updates need to come to fix these silly issues.
Sent from my Nexus S 4G using XDA Premium App
I also had the photo issue and also my causing had this issue but he also ran into it with his videos...
Fixes need to be done ASAP or I may jump in that Photon 4G whenever it drops ... I love my Nexus S 4G but I don't feel like Google has given it the same love the original Nexus 1 had. That's just my opinion... Then again I never think there will be a perfect phone for me, but I'm going to keep looking
Sent from my Nexus S 4G using XDA Premium App
Samsung is apparently down globally at the moment. There is some speculation that this is related to a fire at the Sds facility, which really begs an interesting question about how Samsung handles it's datacenter(s). I find it hard to believe that they would design something so poorly as to not have geographical fault tolerance, but by the same token, all of the hub services are down along with the samsung.com website.
At a minimum, this should be cause for concern about how and where Samsung stores our data and in my case has me in a bind because I'm actually having issues with the Hancom apps on my note pro 12.2. I actually uninstalled hword because it wouldn't open up documents and found out about Samsung being offline when I couldn't access the Samsung app store or Hancom updater to reinstall it.
A company the size of Samsung and they couldn't be bothered with a proper disaster recovery strategy that would ensure availability?
I sincerely hope nobody was injured in the reported fire, but it certainly seems to have provided some insight into what Samsung considers to be acceptable service levels. If this is how little regard they show for critical service availability, it's no wonder firmware updates are always an issue.
Sent from my SM-P900 using Tapatalk
http://www.isitdownrightnow.com/samsung.com.html
Sent from my SM-P900 using Tapatalk
All global site access down for somewhere between 4 and 8 hours without prior notice... That would be a career ending event for me or any of the folks I work with
Sites typically won't let you know before they go down. Even Google services go down once in a while.
Sent from my SM-P900 using Tapatalk
---------- Post added at 06:40 PM ---------- Previous post was at 06:29 PM ----------
http://www.engadget.com/2014/04/20/samsung-com-outage-sds-fire/
Sent from my SM-P900 using Tapatalk
I've yet to see Google play, maps, apps, and search engine take a dive at the same time. I work in a world of five nines availability with clients a hell of a lot smaller than samsung, so it really doesn't speak well for a company their size to take that kind of outage. I realize that things can happen from time to time, but last night's outage points to a serious flaw in their hosting design. Ever hear of geo load balancing?
Hey Samsung, you could stand to start here: https://f5.com/products/big-ip
Sent from my SM-P900 using Tapatalk
I didnt experience amy interruption. Strange. However have you dealt with any other large companies being hit by disasters like this? Or are you particularly familiar with their internal workings? Isnt it a bit unfair to judge them based on limited information? I mean that could have been their primary data hub. Even if it is backed up somewhere else it could take some time to reroute everything they run through another location. It was obviously backed uo somewhere or it wouldn't be working again already. You even started with samsung disapointed on yet another from. It sounds like you are looking forba reason to hate in samsung
Sent from my SCH-I605 using XDA Premium 4 mobile app
They had a major fire. Thankfully there were no fatalities. Let's not overreact to a very minor and temporary inconvenience.
Sent from my SM-P900 using Tapatalk
dodo99x said:
They had a major fire. Thankfully there were no fatalities. Let's not overreact to a very minor and temporary inconvenience.
Sent from my SM-P900 using Tapatalk
Click to expand...
Click to collapse
Exactly. Sorry you were inconvenienced, but I am certain people employed at the facility are inconvenienced a lot more.
Not a hater, just a realist. I'll reiterate that I hope nobody was injured.
That said, I'm speaking from a business perspective, not am personal attack on the employees of that datacenter. I've been designing networks and high availability data centers for nearly two decades and most of my customers demand 99.999% availability for customer facing services. These things would be served out of multiple active locations, not a single location with some dodgy backup. Even better, the non personal stuff like the app and media stores would be served by a CDN. In any case, the loss of a site would immediately reroute traffic and the time it takes for DNS cache to expire would likely be the slowest part.
It isn't insensitive to say that this incident pointed out a shortcoming and when you add it to numerous other recent issues with samsung tablets, the overall picture is disappointing. I went through a number of 10.1 2014 edition tablets before giving up on the faulty BT on that device, as Samsung never addressed it. I buy a note pro 12.2 that resolves it and the Hancom software wasn't pre installed or available to download on release day, now this. It's just a growing list of things that are each small, but show that Samsung just isn't on the ball when it comes to fit and finish. They make the only reasonably usable Android tablet with an active digitizer, so they get my business for now.
I'm not sure why the folks here can't separate a comment on service availability from the matter of personal safety. I'm not suggesting people should have been placed in harm's way to keep things running. I'm stating that there are design shortcomings in how the service is delivered.
Sent from my SM-P900 using Tapatalk
I don't think you'll get any argument that it would have been great if service didn't go down for as long as it did . . Nor do I think that people are having issue with separating personal safety from service availability. The issue more likely stems from the varying degree of tolerance for service interruptions.
On saturday night I was setting up my new tablet when I realized something was wrong with Samsung services. I poked around, realized that the incident was occurring, shrugged my shoulders and moved on to do something else before turning in for the night. Come sunday morning everything was back up and I didn't give the issue a second thought.
We get what you're saying; there's obvious room for improvement, but it could have been worse too . .
dpersuhn said:
Not a hater, just a realist. I'll reiterate that I hope nobody was injured.
That said, I'm speaking from a business perspective, not am personal attack on the employees of that datacenter. I've been designing networks and high availability data centers for nearly two decades and most of my customers demand 99.999% availability for customer facing services. These things would be served out of multiple active locations, not a single location with some dodgy backup. Even better, the non personal stuff like the app and media stores would be served by a CDN. In any case, the loss of a site would immediately reroute traffic and the time it takes for DNS cache to expire would likely be the slowest part.
It isn't insensitive to say that this incident pointed out a shortcoming and when you add it to numerous other recent issues with samsung tablets, the overall picture is disappointing. I went through a number of 10.1 2014 edition tablets before giving up on the faulty BT on that device, as Samsung never addressed it. I buy a note pro 12.2 that resolves it and the Hancom software wasn't pre installed or available to download on release day, now this. It's just a growing list of things that are each small, but show that Samsung just isn't on the ball when it comes to fit and finish. They make the only reasonably usable Android tablet with an active digitizer, so they get my business for now.
I'm not sure why the folks here can't separate a comment on service availability from the matter of personal safety. I'm not suggesting people should have been placed in harm's way to keep things running. I'm stating that there are design shortcomings in how the service is delivered.
Sent from my SM-P900 using Tapatalk
Click to expand...
Click to collapse
Well it sure does piss me off when google goes down, or ebay, or amazon, or any number of websites and services that go down unexpectedly. So why is it that absolutley none of these seem to have a flawless system of backups and service availability like you say they should despite being huge companies. I guess if they all hired you none of them would ever have service interuptions.
Sent from my SCH-I605 using XDA Premium 4 mobile app
Duly.noted said:
Well it sure does piss me off when google goes down, or ebay, or amazon, or any number of websites and services that go down unexpectedly. So why is it that absolutley none of these seem to have a flawless system of backups and service availability like you say they should despite being huge companies. I guess if they all hired you none of them would ever have service interuptions.
Sent from my SCH-I605 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
At first, I read this and was a bit torqued off at the personal attack, but then I remembered that this forum is already littered with nonsensical vitriol that you've spewed out in ignorance. Since you're apparently qualified to assess Samsung's INFRASTRUCTURE (note that this is not synonymous with website) availability based upon your extensive knowledge and experience in this field. How exactly do all of their services work? What made this a perfectly acceptable failure scenario based upon industry best-practice design standards? Please elaborate on the routers, switches, firewalls, intrusion prevention systems, load balancers, and redundant service provider connections that were all designed, implemented, and functioning properly at the time that this failure occurred. Oh, and don't forget about datacenter redundancy too. I'm anxiously awaiting some education about how modern high-availabilty design practices couldn't possibly have prevented or minimized this outage.
I'm one of thousands of engineers that could definitively elaborate on how it failed to meet the most basic best practice standards for what should be a high availability service. I'll be glad to discuss the finer points of service availability and disaster recovery with you whenever it becomes a technical conversation but based upon the lack of useful references you've made thus far, I'm quite sure that day will never come...
Just for comparison. Google's average website availability is currently tracked at 99.984%. That's less than 5 minutes per month of total downtime. To hold the same measure of availability after that outage, Samsung would have to never have a single second of downtime for at least the next four years (I didn't track the exact duration of the outage, so I'm using the most favorable number that I've seen). And even with that service level, I'd bet my career that the only downtime of the Google website has been software / server related, not infrastructure.
When exactly was it that you experienced an EXTENDED outage with Google, eBay, or Amazon?
dpersuhn said:
Just for comparison. Google's average website availability is currently tracked at 99.984%. That's less than 5 minutes per month of total downtime. To hold the same measure of availability after that outage, Samsung would have to never have a single second of downtime for at least the next four years (I didn't track the exact duration of the outage, so I'm using the most favorable number that I've seen). And even with that service level, I'd bet my career that the only downtime of the Google website has been software / server related, not infrastructure.
When exactly was it that you experienced an EXTENDED outage with Google, eBay, or Amazon?
Click to expand...
Click to collapse
I tried replying twice to no avail. The xda app times out on me all the time. Sorry my teasing offended you. It is apparent your care about this (even though nobody else does) so I decided to pick at it a little. My attempt to initiate a little banter obviously went badly and im sorry about that. My bad. Calling everything I post vitriol was a bit much though. When I do respond I usually have a very workable solution to the issue in question. I have only been notably rude to one person. And that was a very very bad day for me and the guy was just whining. Half the stuff he was wrong about anyways..but that doesnt matter. The point is sorry I made you angry.
Sent from my SCH-I605 using XDA Premium 4 mobile app
---------- Post added at 03:44 PM ---------- Previous post was at 03:43 PM ----------
Oh and netflix hasn't worked at my house for 4 months lol. Its so bad they just gave me 2 years of free service for the trouble
Sent from my SCH-I605 using XDA Premium 4 mobile app
Honest question: Exactly WHAT service was down?
I can't think of any "service" I need directly from Samsung, let alone that I'd even notice missing for an hour or two.
dpersuhn said:
Just for comparison. Google's average website availability is currently tracked at 99.984%. That's less than 5 minutes per month of total downtime. To hold the same measure of availability after that outage, Samsung would have to never have a single second of downtime for at least the next four years (I didn't track the exact duration of the outage, so I'm using the most favorable number that I've seen). And even with that service level, I'd bet my career that the only downtime of the Google website has been software / server related, not infrastructure.
When exactly was it that you experienced an EXTENDED outage with Google, eBay, or Amazon?
Click to expand...
Click to collapse
With all your ranting and claims you apparently have a high level of technical skills but no common sense. Samsung is not monitoring XDA for your personal rant on their lack of service redundancy and down time due to a major fire! Get over it and do something productive!
At what point did I ever say I expected Samsung to read it, respond, or otherwise? It is worth consideration for users that are placing their faith in things like Samsung cloud backups and such to know that their data could be inaccessible when they need it.
This thread really has been a good exercise in shaking out the Samsung cheerleaders, hasn't it? I bring up an availability concern and you'd think I went around personally slapping some folks upside the head. Oddly, I have yet to see any retort of technical merit. Fascinating...
Duly.noted said:
I
[/COLOR]Oh and netflix hasn't worked at my house for 4 months lol. Its so bad they just gave me 2 years of free service for the trouble
Sent from my SCH-I605 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Guess I'm the ass. I take it seriously for two reasons. 1. I forked over serious cash for a device that is supposed to be a business tool and expect Samsung to provide services at an appropriate level as such. 2. Infrastructure design has been my life for nearly two decades, so I see failures like this in a different light than most folks on here. If you think I'm overstating my position, realize that there are some IT folks who did or probably will lose their jobs over that outage.
As for netflix being unavailable at your house for months on end, wow. I can't believe that people tolerate handing cash over to a company (guessing your ISP in this case, maybe Comcast?) while they blatantly refuse to provide the services that you subscribed to (aka the best effort clause in every service provider agreement).
Personally, I wish Samsung would stop trying to host content and services for these devices and fall back to letting google do that part. Nothing spells fun like orphaned apps if I switch tablets. Just ask apple, they have a pile of them I left behind when I dumped my iPad.
zaptoons said:
Honest question: Exactly WHAT service was down?
I can't think of any "service" I need directly from Samsung, let alone that I'd even notice missing for an hour or two.
Click to expand...
Click to collapse
Samsung.com, samsung app and media stores, Hancom updater, cloud backup and restore. In my case, I was working on updating client docs for a morning meeting and only had my tablet with me. When I tried to use Hword, it kept bombing out for some reason. As a last resort, I figured if try to reinstall Hword, but couldn't because the samsung App Store was unavailable. I ended up buying Polaris office just so I could finish working. Not sure why Hword was dead, but it worked fine after the App Store came back online and I was able to reinstall.