A couple of our Australian users have had issues with the Samsung Galaxy Tab 2 10.1” running Mappt out of the box.
The problem is that in Australia, the Android 4.1 (Jellybean) update has not been universally applied as yet, unlike in many countries overseas. You can’t update to Jellybean using the Samsung Kies software or natively from the Tab2 Settings. However, we do have some lucky Tab 2 users in Australia. As far as we understand, Galaxay tab 2 users will probably get Android 4.3 Jellybean when it’s available.
However, some telco tied tabs (e.g. Vodafone, Telstra) have 4.1 available but Samsung Australia is behind the times for Tab 2 users not shackled to one of these plans.
So what is the solution?
There really isn’t an ideal one but there are
two three things you can do:
- You can “root” your device (not what you probably think if you are an Aussie); or
- You can try a workaround.
Neither is ideal (or recommended by Mappt as there are real risks that something goes wrong). Both of these options will likely void your warranty and rooting your device can turn it into an expensive paperweight (yes we will apply that meaning of rooted here).
Alternately you can wait for Samsung to release a 4.1 Android update or (option 3)
- Go for a different tablet!
Have we tried Mappt on overseas and rooted Galaxy Tab 2s?
Yes and it works on Tab2 with Jellybean (those outside Aus) and on rooted Tab2s as well.
Yours truly went down the rooting process with their Galaxy Tab 2 using CyanogenMod 10.1 and I don’t have many issues other than the limits of the Tab2 dealing with bigger files.
But I did it at my own risk and a *LOT* or research and stuffing about (took me quite a few hours of finding everything I needed to know) and only took me a few goes to get it right once I “knew” what to do.
I consider myself pretty good at these things and it took me a lot of effort to find the right combo to work. So be warned, rooting your device might cost you more in your time than buying a new tablet!