Let's see, since you already had a 2DIN, I thought it was a Smartphone and it gave you the proven solution for the server problem.
But 2DIN is another movie. I suppose you have read in post 1 the incompatibility of the reported chip, and I know of many users who already had that problem since 1.4, simply could not install it.
Anyway there is something you should be aware of.
There are a lot of users and devices many do not have the obb folder, and it is passed to facilitate the installation all complete
obb / com.tomtom.gplay.navapp / main.xxx.com.tomtom.gplay.navapp.obb
When the original version of Play is obtained and the installation is verified, the content of obb is created and created if there is no obb and at the end of the installation it is deleted.
But the obb folder has not been invented by tomtom, on many devices depending on the apps they have installed, at the root, within Android there is the data folder and the obb folder, example on my device, in this case in external memory I have data, media (com.fundesvs.app.mediaconverter) and the obb folder it contains (com.facebok.katana and com microsoft.office.word) i.e.
the obb folder is system, and if it doesn't let you delete nothing happens, what counts is its content, and if it doesn't appear com.tomtom.gplay.navapp / main.xxx.com.tomtom.gplay.navapp.obb Well, this is it, the obb folder alone does nothing.
At first when passed com.tomtom.gplay.navapp / main.xxx.com.tomtom.gplay.navapp.obb more people confused copied it into data directly, and you don't see what a mess.
Regarding what other browser to use, if you can fit, put both of them to the test and decide, you should go little by little reading and clarifying ideas, because it is something new, the difference between a debutant and a veteran is that he has screwed up 2000 times more that you
Regards