Thread: iGO Primo Israel 9.6.29.636868 (Mar 03 2016)

Originally Posted by Golom

A 32 bit app?

I am also surprised that a Samsung with And.14 allows a 32bit app installation 🤔 after many users wrote to me that a 9.35.xx 32bit cannot be installed.
Murphy apparently 🤷*♂️😉

regarding what boki said above, I have the same issue on my car's Chinese screen,many versions from here of igo cannot be installed, while on my tablet and mobile everything is ok.the manufacturer of the screen has in my car the igo my way version of March 2016

There's nothing abnormal, it's not because devices are under android14 that they're of the latest generation, some have been sold basic with an android12 and for the developer go from android 12 to 14 requires much less maintenance than to upgrade a device with android9 for example: the most recent processors benefit from instruction sets that are adapted to the 14 or older versionsgraph, which will have to be emulated for an older cpu unless it is attached to an external graphic chip in a free dwelling)

coming back to different generations of devices, the most recent ones will only work with 64-bit apks specially compiled for them. older devices will have been able to switch from android 9 to android 12 or from 12 to 14 and these are largely those on which 32 or 64-bit apk can be installed (it is possible to know this using aida64), Each version of apk according to the JDK may not work on some devices, while on others this will not pose any problems.

if the explanation seems unclear, it is enough to draw the parallel with different pc sold pre-installed with a version of windows at the time of purchase, some are scalable to a certain point, the too old will have to end up staying on a shelf for lack of updates or good for the recycling of the parts

Updated post #[Only registered and activated users can see links. ]

@yesigo and all others!

Your images are useless for most members because they, as me, don't understand that language.
Official forum language is English.
Before making screenshots, change language to 'English', and later change back to whichever language you use.

In future, I will 'trash' such posts without any warning.

For information:
it is the FBL that mainly contains the names of streets and cities, but not everything that exists can be included because otherwise the size of the file would become unmanageable,

the FBL contains as a priority the road space itself, and the use of geographical points could be sufficient for the creation of itineraries. It may very well contain only the main traffic routes, or go as far as the referencing of all the roads and hiking trails, it is like an encyclopedia containing only the essentials, or a whole host of detail, the weight of knowledge is no longer the same.

Overlaying of city and street data could also be found in ancillary files such as FTR,FDA,FPA, HNR, POI, etc. in simple or premium versions linked to licences.

Not finding streets associated with a lost village at the top of a mountain is not surprising and the configuration of igo is not in question, everything is based on the richness of the databases on which the research carried out is based.

search, for example, using an external provider as a google using an internet connection, if it is installed in igo, will in turn make it possible to obtain the geographical coordinates of the street searched and then located on the navigation map.

Another technique is to select the destination point on the map and see if the name of the street is inscribed in it, which will confirm that this name is correctly referenced in the FBL

It must be a little bit clearer for everyone