Welcome guest, is this your first visit? Click the "Create Account" button now to join.
Page 1 of 2 12 LastLast
Results 1 to 10 of 14
  1. #1
    Member
    Join Date
    Nov 2009
    Location
    Netherlands
    Age
    70
    Posts
    15
    Rep Power
    0

    Android Igo Primo Error message "not enough memory. Change routes option"

    Hallo navigators,
    After, say an hour or so, I get this error message. Or Igo reset it self without any massage and goes on a black screen. My configuration is as follows
    . Basarsoft Igo Primo 9.6.29.431282, sept 9 2014.
    . Samsung S4 (I9505) with Android 4.4.2
    . my sys txt as follows:
    See attached file!!!

    Now the strange thing is that I had this before with Android and other versions of IGo. for instance the continuous building up of the map on screen. This was clearly a matter of memory. But I've never figured out what the sollution was. Finally I gave Igo up and changed to TomTom. However Since I like to ride preconfigured routes from internet I recently had Igo installed. Now I have also a HTC HD2 (wince) where Igo runs on and this gives no problem. This device has a much smaller amount of memory. So the bottom line is: I don't know what to do or how to solve my android problem. Before I start Igo up I delete all the programs from memory because I found that this slows down Igo operating.

    Anybody any Ideas????
    Thanks in advance
    gr fred
    Attached Files Attached Files
    Last edited by fretjes; 10th May 2016 at 13:53.

  2.    Advertissements


  3. #2
    Member + lameriq's Avatar
    Join Date
    Dec 2015
    Location
    Slovakia
    Age
    35
    Posts
    69
    Rep Power
    49

    Default

    Hi there...
    Your SYS.TXT uses UNIX line encoding (LF) ? Grrr... you can try to use the Windows+UNIX line encoding (CR+LF) ha ha... many people uses OS Windows :-P When open the file with Windows-Notepad is the line encoding wrong. But with Notepad++ on MS-Windows system is all right.

    The file SYS.TXT is not your problem, but smartphone Samsung S4. Low memory may result in many problems. You have too much running applications maybe. Start the iGO and when iGO still running, then start any memory diagnostic tool ("[Only registered and activated users can see links. ]" for example - screenshot downward) or check the avaiable RAM in system configuration. If you have enough memory, then problem is maybe with accessing to a folder (internal flash drive / SD card).

    If you have 3D-terrain "DEM" files or "Buildings" files in your "\iGO\content\" directory, then simple delete it. Memory problems may consist of many causes. IMHO the WinCE is stupid system - uses a very bad memory management.

    After updating the program, we also need to delete the folder "SAVE" and again all set up - you did so ? You may also try running iGO directly without using a file "SYS.TXT" (rename it to "SYS_.TXT_" for backup) + also no directory "SAVE" (for example, rename the directory to "Save_" as a backup). New versions of iGO Primo can detect hardware quite successfully.

    The error is appear when you are planning the short route and the long route too ?

    Spoiler: 3C Process Monitor - screenshots

    [Only registered and activated users can see links. ][Only registered and activated users can see links. ]
    Last edited by lameriq; 14th May 2016 at 09:55.

  4. #3
    Member
    Join Date
    Nov 2009
    Location
    Netherlands
    Age
    70
    Posts
    15
    Rep Power
    0

    Default

    Hi Lameriq
    First the sys.txt, you're right but for some reason when I copied the sys.txt from mij samsung this has happened. I do not know yet how but is the last of my worries.

    As far for the running programs, since I have this problem a long time, I made (and make) it my buisness to close any program via taskmanager and then start Igo. Now of course I will follow your suggestion about 3C process Monitor and let you know the results.

    I have now deleted, on your suggestion the DEM and Buildings folders and wiped the Save folder, restart the whole thing.
    Unfortunately I'm not able to test it in the car or motorbike yet but will soon as the weather clears up overhere.
    You also talk about the WinCe memory management, however I don't have a problem with my WinCe. In Fact that works brilliant with Igo.
    I've also have put the sys.txt out.

    Now your question about when the error appears. It appeared as well on the short and long route. I have to mention that a similar error "not enough memory" appeared in the past whit normal operation so not a pro-configured route downloaded from internet and then load into Igo.

    Now I have to thank you for your elaborated answer and I hope that you will continue to think along with this problem. I'm grateful for any help on this because it is, for me, a long standing one (two years now) and I tried a lot of things.
    gr fred

  5. #4
    Important User

    zervdim's Avatar
    Join Date
    Mar 2013
    Location
    Salonica
    Posts
    749
    Rep Power
    701

    Default

    Quote Originally Posted by fretjes View Post
    Hallo navigators,
    After, say an hour or so, I get this error message. Or Igo reset it self without any massage and goes on a black screen. My configuration is as follows
    . Basarsoft Igo Primo 9.6.29.431282, sept 9 2014.
    . Samsung S4 (I9505) with Android 4.4.2
    As I remember I had issue with memory message, it takes to me one day to find out....
    Delete your folder license, delete save folder and add the following license to your device....
    This post requires you to click the "LIKE this post" button and hit F5 to read this content.

  6. #5
    Member
    Join Date
    Nov 2009
    Location
    Netherlands
    Age
    70
    Posts
    15
    Rep Power
    0

    Default

    zervdem,
    Thanks very much for your suggestion.
    Will try this also. I will get back to you with the result.
    Will take a week at the minimum because I'm very short on time the coming period.
    gr fred

  7. #6
    Member
    Join Date
    Nov 2009
    Location
    Netherlands
    Age
    70
    Posts
    15
    Rep Power
    0

    Default

    Hi there,
    As promised a feedback on the above mentioned possible solutions. I was able to test both options.
    But what I found was that there is a strange (at last to me) memory problem.
    The map shown on the Samsung keeps building up during navigation. This happens after say half an hour of navigation. The picture goes gray, the route disappears and then the picture builds up again, colors appear, the map is complete and the whole map or partial map disappears again, builds up again. This keeps continuing 4 to 8 times. Then the picture stays for about 5 to 10 minutes and the whole starts again. When switching of Igo and restart it it takes about 10 to 15 minutes before the whole cycle starts again of disappearing and building up.
    To me it looks like there is not enough (video) memory. I have started Igo and then 3C monitor (as suggested by "lameriq"), the available memory is from 900mb to 1100 mb. So in my opinion there's enough memory.
    So there it is,
    Any ideas anyone???
    gr fred

  8. #7
    Member + lameriq's Avatar
    Join Date
    Dec 2015
    Location
    Slovakia
    Age
    35
    Posts
    69
    Rep Power
    49

    Default

    Hi frejtes.

    It is quite possible that the problem is in the smartphone, not iGO. For example, on your smartphone can be installed service/process to the background that eating away at the available memory or alter the behavior of iGO. None of the above, however, will not help if the problem is in your smartphone (problem of another kind of software or even hardware problem) :-/ . You can also try other navigation software only for testing memory problems - such as Sygic.

    I forgot to file "Branding.zip" before. You can keep deleted file "Branding.zip". I think futility that causes nothing but trouble. In principle it governs only the boot screen, further logos and icons or other treatments applied on your SKIN (even the basic skin). Branding.zip is designed by GPS technology vendors. It is unnecessary, and often causes problems with the graphics (for example incompatible resoluion).

    Of course, you can also try to clear (do not forget to backup) directory buildings ("iGO/content/building/").

    There are also many settings for file SYS.TXT to reduce RAM usage. You can try adding the following entries to SYS.TXT for drastic restrictions to the use of memory. If the problem persists, then writes the file SYS.TXT blot again :-) . After each one modification of SYS.TXT file, you must delete the "SAVE" folder.
    Code:
    Please Login or Register to see the links
    If the problem is really in the graphic, you can try to disable HI-RESolution settings in SYS.TXT file. If you have not hi-res SKINs but your iGO must use 800_480 (converting into bigger resolution for your Samsung Galaxy S4) so also try this:
    Code:
    Please Login or Register to see the links
    Another thought occurred to me to try it without SYS.TXT file (rename it suffices for example to "SYS_.TXT_", delete SAVE folder and start iGO again). New versions of iGO Primo on Android are quite successful in autodetecting own configuration. SYS.TXT be added to only the necessary data such as entry the correct functionality without TTS-voices (entry of csv_voice_enabled=1).
    For example, I do not understand what it's looking in the file SYS.TXT this entry:
    Code:
    Please Login or Register to see the links
    My third thought by collaborating with a set SYS.TXT is changing the following settings extracted from the version of iGO Primo 2.4 9.6.29.483387 Israel Android (file "GT-I9505.ini"). These settings are primarily designed for the Samsung Galaxy S4 (i9505). You can try it too. The most important entries are at the bottom of the file:
    Spoiler: "GT-I9505.ini" file
    ;Samsung Galaxy S4
    ;Board = MSM8960
    ;Brand = samsung
    ;Device = jflte
    ;Model = GT-I9505

    [camera1]
    ; 2D settings
    minzoom2d=25
    maxzoom2d=100
    defaultzoom2d=50
    overview_zoom2d=1500
    ; 3D settings
    minzoom=18
    maxzoom=33
    maxangle=72
    defaultzoom3d=21
    defaultangle=69
    overview_zoom3d=300
    overview_angle=55

    [camera11]
    ; 2D settings
    minzoom2d=38
    maxzoom2d=150
    defaultzoom2d=100
    overview_zoom2d=1875
    ; 3D settings
    minzoom=20
    maxzoom=41
    maxangle=73
    defaultzoom3d=23
    defaultangle=71
    overview_zoom3d=300
    overview_angle=55

    [camera2]
    ; 2D settings
    minzoom2d=38
    maxzoom2d=188
    defaultzoom2d=70
    overview_zoom2d=1500
    ; 3D settings
    minzoom=32
    maxzoom=54
    maxangle=70
    defaultzoom3d=33
    defaultangle=60
    overview_zoom3d=300
    overview_angle=55

    [camera21]
    ; 2D settings
    minzoom2d=45
    maxzoom2d=250
    defaultzoom2d=175
    overview_zoom2d=1875
    ; 3D settings
    minzoom=41
    maxzoom=68
    maxangle=70
    defaultzoom3d=41
    defaultangle=67
    overview_zoom3d=300
    overview_angle=55

    [camera3]
    ; 2D settings
    minzoom2d=50
    maxzoom2d=625
    defaultzoom2d=200
    overview_zoom2d=1500
    ; 3D settings
    minzoom=34
    maxzoom=105
    maxangle=70
    defaultzoom3d=39
    defaultangle=55
    overview_zoom3d=300
    overview_angle=55

    [camera31]
    ; 2D settings
    minzoom2d=50
    maxzoom2d=750
    defaultzoom2d=300
    overview_zoom2d=1875
    ; 3D settings
    minzoom=36
    maxzoom=105
    maxangle=70
    defaultzoom3d=59
    defaultangle=65
    overview_zoom3d=300
    overview_angle=55





    [rawdisplay]
    highres = 1
    ;screen_xy="auto"
    screen_xy="800_480:1920x1006/1080x1846"

    [debug]
    ;show_performance=1
    double_pixel_mode=1


    [2d]
    dpi_based_correction = 1
    min_road_thickness_multiplier = 0.25

    [interface]
    vga=1
    minzoom2d=25

    Samsung Galaxy S4 uses a display resolution 1920x1080 (FullHD) but it requires also due DATA.ZIP file containing a fully functional original or alternate skins (GjAk Arine, Doupas, Dimka, etc.) containing the ingredient "1920_1080". Alternative file DATA.ZIP you can find and download from the internet - to some other test. Personally, I think the problem with the Samsung Galaxy S4 is based on a badly developed SKIN. You can try to use in your SYS.TXT values for resolution 800x480 (480x800 respectively), which are located at the end of the file "GT-I9505.ini". Then you will use the skin in 800x480 resolution. Of course, there is nothing to worry about resolutions. You will not see the difference between 480x800 and 1080x1920 resolutions on the small smartphone display (4" - 5").

    If none of the above does not work, here is the file DATA.ZIP which containing 1024x768 resolution skin + the file SYS.TXT with the entry to change resolution of original resolution 1024x768 to 1920x1080 resolution. These two files are from another user with Samsung Galaxy S4 (not mine). You might have to rename the downloaded file "data-1920x1080.zip" (what's wrong filename because the archive contains 1024x768 only and no 1920x1080) to the default filename "data.zip".
    Spoiler: download links
    [Only registered and activated users can see links. ]
    [Only registered and activated users can see links. ]


    Good Luck

    Last edited by lameriq; 20th May 2016 at 19:47.

  9. #8
    Member
    Join Date
    Nov 2009
    Location
    Netherlands
    Age
    70
    Posts
    15
    Rep Power
    0

    Default

    Hi, lameriq
    thanks for your elaborated answer. This opens up a whole range of possibileties.
    At the moment I'm on holiday so I will follow your suggestions somewhere the following week. I will come back with the result here.
    again thank you very much,
    Fred

  10. #9
    Member + lameriq's Avatar
    Join Date
    Dec 2015
    Location
    Slovakia
    Age
    35
    Posts
    69
    Rep Power
    49

    Default

    Hi there!
    I found the another solution :-) . You can try it too.
    Post No.54: [Only registered and activated users can see links. ]
    Quote Originally Posted by janch
    The problem causing "out of memory" errors on wince version are the licences. To many of them..try to remove some but than you might lose some functionalities.

  11. #10
    Important User

    wojpen's Avatar
    Join Date
    Nov 2013
    Location
    EU
    Posts
    1,224
    Rep Power
    813

    Default

    Gentlemen!
    Primo - this is not the Lotto.
    Finding error in the display must begin with an analysis of the files.
    A colleague @fretjes - showed his sys.txt - and from that had to be started.

    I have written several times about the declaration of the amount of memory (eg. here - [Only registered and activated users can see links. ] )

    Spoiler: Memory
    probably the most important thing for Full HD and QHD screen is:
    1. Record max_memory = ???? in section [debug] in sys.txt, which many very present.
    In data.zip by default max_memory = 83886080 (Byte), which is only 80 MB
    2. Even prescribing 150 MB you can still watch the brake.
    So the date we will not climb, and sys.txt write at least 200 MB (1mb = 1048576) and enjoy:
    [debug]
    max_memory = 209715200 or more...



    Meanwhile, in sys.txt lack of this declaration, and over it incorrectly indicated the driver for this type of screen.
    Colleagues - are unnecessary guesswork - type it can, and maybe something else - the system clearly communicated what was wrong with him!


    Mate fratjes - here you have the link:

    Spoiler: Link
    Code:
    Please Login or Register to see the links


    ...
    The archive contains a complete installation of Primo version 2.4 for your phone.
    Apk - 483387 - the most stable (IMO) to date version of iGO.
    Unpack, add your maps, POI and SpeedCam and install.

    NOTE: First, uninstall all the old apk and delete your old files!

    regards wojpen
    Password for My Files: wojpen
    User (when necessary): wojpen
    Closed Link - Please PM
    regards

 

 
Page 1 of 2 12 LastLast

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
This website uses cookies
We use cookies to store session information to facilitate remembering your login information, to allow you to save website preferences, to personalise content and ads, to provide social media features and to analyse our traffic. We also share information about your use of our site with our social media, advertising and analytics partners.