Samsung Galaxy Tab 10.1 Wi-Fi tablet update brings Android 3.2 and problems (updated)

Posted on 14. Nov, 2011 by in Tablets

Samsung Galaxy Tab 10.1 tabletBetter late than never, maybe. Samsung has begun sending out OTA (over-the-air) updates to Samsung Galaxy Tab 10.1 Wi-Fi only tablet owners for Android 3.2 Honeycomb. The new update brings the most up-to-date version of Android for tablets which Google unveiled some three months ago, but it’s not a clean update with some major bugs being reported by owners.

According to some Samsung Galaxy Tab 10.1 Wi-Fi tablet owners the Android 3.2 update caused their tablet stop connecting to Wi-Fi connections with a DHCP dynamic IP addresses and stopped connecting to Kies. After rebooting their Galaxy Tab 10.1′s after the update some are also reporting “Firmware update failed. Please try installing using Kies (PC)” warnings and auto-rotate for the display isn’t working for some as well. Hard resets aren’t working to fix any of the issues.

All-around this is a buggy update, I don’t recommend updating until Samsung issues an official response to these customer complaints.

Update: Samsung Mobile has announced they have stopped sending out this update until they can fix the issues. If you get an alert to update, don’t do it.

[Via] [Samsung Galaxy Tab 10.1 user forums]

Tags: , , , , , , , , , , , , , , , , , , , , , , ,

5 Responses to “Samsung Galaxy Tab 10.1 Wi-Fi tablet update brings Android 3.2 and problems (updated)”

  1. Dave

    15. Nov, 2011

    HELP – just updated to 3.2 and Tab now useless – is there anything I can do to fix this or do I have to bin it!

    Reply to this comment
  2. JOhn

    15. Nov, 2011

    Dave- Samsung does not have a solution yet. You can set you tablet’s WiFI connection to static and get t to work in the meantime. You will probably also notice that the screen no longer rotates and bluetooth is gone.

    Reply to this comment
  3. Cloves

    15. Nov, 2011

    THIS IS NOT POROCEDE .. I upgraded and no ah no problem, and staff updated with the new XDA RON and had no problem … That is wrong

    Reply to this comment

Leave a Reply