Samsung pulls Galaxy Tab Android 3.2 update
Wi-Fi only tablet loses... Wi-Fi
Samsung has yanked the Android 3.2 Honeycomb update it posted last night for the Wi-Fi only version of its Galaxy Tab 10.1in after it quickly emerged that the software disables Wi-Fi.
Certainly, that's happened to a fair few folk who did perform the update before the software was pulled. That said, not everyone appears to have been affected by the glitch.
Deleting Wi-Fi settings and using a static IP address appears to fix the problem.
Other woes include broken Bluetooth, video playback issues, disabled screen rotation and syncing trouble with Samsung's Kies app, according to posters on various Android forums.
As yet there's no word from Samsung as to when the (fixed) 3.2 update will be released. ®
How does an update get that close to release and not be tested properly?
Where were the testers?
"Right, you've all been testing the update for the past week. Any problems?"
Well, WiFi doesn't work."
"Bluetooth is broken."
"I found some video playback issues."
"The screen won't rotate."
"I can't get the Kies app to sync."
"But apart that, it's OK? Fine. Release it.
This is getting more and more common
The coders and testers have all caught Googleitus. This increasingly common condition causes the sufferer to believe that it's okay to release beta grade code for consumers to test for you and the inevitable problems can be simply solved by pushing out patches every few days and nobody will mind.
I had 3 apps last week update every day for a week (one updated 3 times in one day!) to fix bugs. Most of the updates were simply to fix new bugs introduced in the previous update. The time spent fixing bugs caused by rushing to issue updates would be better spent doing a bit of QA surely? This patch and update mentality is killing software quality.
One upside, old school coders in their 40's are in very high demand now ;)
As a tester, I guess they focussed to much on testing factory images (ie re-imaging the device everytime with the newest test version), and that they did not perform sufficient testing with various upgrade scenarios (or if they did: they did not test sufficiently after upgrading the device).