Welcome guest, is this your first visit? Click the "Create Account" button now to join.
Page 2 of 3 FirstFirst 123 LastLast
Results 11 to 20 of 26
  1. #11
    Member +
    Join Date
    Feb 2010
    Location
    Sweden
    Posts
    37
    Rep Power
    8

    Default

    Can anyone confirm that its works on Nexus 5 with Marshmallow 6.01? I have tried with different paths but Avicsync only closes before starting is finished.
    Last edited by kalleh; 1st February 2016 at 07:28 PM.

  2.    Advertissements


  3. #12
    Member + iGo Primo & iGo nextgen - content folder on external SdCard on Android 4.4.4 , 5.0 , 5.1.1
    Join Date
    Nov 2014
    Location
    Toronto, Canada
    Posts
    63
    Rep Power
    46

    Default

    I have LG G4 with new Marshmallow update. In IGO nextgen and Avicsync this procedure works. In Primo 2.4, it used to work before the update. Now it won't find the maps. My new path in sys file is as follows:
    /storage/3339-6663/IGO

    3339-6663 is my external SD now.

    Why would it work with Avicsync and Nextgen, but not with Primo? I had to copy a few files in the internal sdcard for Primo to work with the maps. Tried deleting "save", reinstalling, but it only didn't work with Primo.

  4. #13
    Important User iGo Primo & iGo nextgen - content folder on external SdCard on Android 4.4.4 , 5.0 , 5.1.1
    iGo Primo & iGo nextgen - content folder on external SdCard on Android 4.4.4 , 5.0 , 5.1.1iGo Primo & iGo nextgen - content folder on external SdCard on Android 4.4.4 , 5.0 , 5.1.1iGo Primo & iGo nextgen - content folder on external SdCard on Android 4.4.4 , 5.0 , 5.1.1
    osiris4isis's Avatar
    Join Date
    Apr 2012
    Location
    Darkside of the Moon
    Posts
    2,449
    Rep Power
    541

    Default

    AvicSync and NextGen are newer NNG product than Primo. They are not the same. Did you tried different versions of Primo?

  5. #14
    Senior Member Nx4's Avatar
    Join Date
    Sep 2014
    Location
    79.933202, -99.228398
    Posts
    139
    Rep Power
    22

    Default

    What about data.zip and ux folder? In NextGen they are different then in Primo. How to use it in this situation? Also sys.txt is only one for both programs and should be placed in root iGO folder, right?

    Sent from my LG E960 Mako using Tapatalk

  6. #15
    Member + iGo Primo & iGo nextgen - content folder on external SdCard on Android 4.4.4 , 5.0 , 5.1.1
    Join Date
    Nov 2014
    Location
    Toronto, Canada
    Posts
    63
    Rep Power
    46

    Default

    Quote Originally Posted by osiris4isis View Post
    AvicSync and NextGen are newer NNG product than Primo. They are not the same. Did you tried different versions of Primo?
    Not sure if you were asking me.
    I have the three IGOs in my phone (Primo, Nextgen and Avicsync). Before I updated from Lollipop to Marshmallow, I had all maps in External sd card. Then I updated a few days ago. There were changes in the folder structure. Now the path changed and I corrected the path in the sys.txt accordingly. IGO avicsync and nextgen have no problem detecting the maps, but Primo says it cannot find them. I use the same path in the sys file... The only way I could make Primo find the files was by putting them in the internal sdcard folder, that is the usual folder structure. No problem with Avicsync and Nextgen.

  7. #16
    Important User iGo Primo & iGo nextgen - content folder on external SdCard on Android 4.4.4 , 5.0 , 5.1.1
    iGo Primo & iGo nextgen - content folder on external SdCard on Android 4.4.4 , 5.0 , 5.1.1iGo Primo & iGo nextgen - content folder on external SdCard on Android 4.4.4 , 5.0 , 5.1.1iGo Primo & iGo nextgen - content folder on external SdCard on Android 4.4.4 , 5.0 , 5.1.1
    osiris4isis's Avatar
    Join Date
    Apr 2012
    Location
    Darkside of the Moon
    Posts
    2,449
    Rep Power
    541

    Default

    @SOYEL1, Path access is different from different proggy on different OS*. This is why Primo (which version?) only see it on your internal card. Not all version of Primo can access external card. Why don't you get the map/poi/etc... installed under Primo directory first and then tell NextGen where to use it.

    * KitKat is example of not able to access external card natively while previous OS version could.

    @Nx4, Even if you could share data.zip and ux between Primo and NextGen, it's not a good idea to do so. You definitely do not want to share sys.txt!!
    Last edited by osiris4isis; 8th February 2016 at 02:36 AM.

  8. #17
    Member + iGo Primo & iGo nextgen - content folder on external SdCard on Android 4.4.4 , 5.0 , 5.1.1
    Join Date
    Nov 2014
    Location
    Toronto, Canada
    Posts
    63
    Rep Power
    46

    Default

    Osiris4isis, I had all three working fine before the update. After updating to Android 6.0, only IGO Primo cannot find the maps. Marshmallow renamed my external sd. When I first updated, all three showed "Map initialization error, Map files cannot be found". I went to the sys.txt file and corrected the path for the three, but only Primo (603974) cannot find the maps in the new android. If it were a problem with accessing the external sdcard, Avic would not find the maps either.
    Last edited by SOYEL1; 8th February 2016 at 02:53 AM.

  9. #18
    Important User iGo Primo & iGo nextgen - content folder on external SdCard on Android 4.4.4 , 5.0 , 5.1.1
    iGo Primo & iGo nextgen - content folder on external SdCard on Android 4.4.4 , 5.0 , 5.1.1iGo Primo & iGo nextgen - content folder on external SdCard on Android 4.4.4 , 5.0 , 5.1.1iGo Primo & iGo nextgen - content folder on external SdCard on Android 4.4.4 , 5.0 , 5.1.1
    osiris4isis's Avatar
    Join Date
    Apr 2012
    Location
    Darkside of the Moon
    Posts
    2,449
    Rep Power
    541

    Default

    Why would you assumed that NextGen proggy is same as Primo? Just because NextGen can access external card doesn't mean that Primo could. Some Primo (and depending on cracked or not) required access to internal card. Maybe you should double check Primo sys.txt to make sure the path is correct; verified it working when accessing internal card and if it doesn't work via external path, then it's a Primo problem.

  10. #19
    Master G-ulash's Avatar
    Join Date
    May 2014
    Location
    Yellow Brick Road
    Posts
    240
    Rep Power
    8

    Default

    If I may interfere here?
    MarshMellow introduced important features on Android. Seeing the external memory (the SDcard) as internal is one of them.

    Android 6.0 never will be officially released for my smartphone, not even 5.0 will. So far I am on 4.4 (rooted) and have no issues.
    Anyway 6.0 is in alpha on XDA, I don't intend to update soon, but I do follow the progress there. I read that many users have problems with the memory usage as this gives unexpected consequences with some apps. And the choice of using th SD as internal or not is made just after flashing and irreversible unless : Users have already reflashed the Android and reformatted the SD to fit their intentions.
    I don't know if the G4 has the same issues (even if Marshmellow is LG-made), I am just saying. However it worked before the update to 6.0, right?

  11. #20
    Member + iGo Primo & iGo nextgen - content folder on external SdCard on Android 4.4.4 , 5.0 , 5.1.1
    Join Date
    Nov 2014
    Location
    Toronto, Canada
    Posts
    63
    Rep Power
    46

    Default

    As I said, it worked before the update. Before the update it could read the SD, so I get it is not a Primo version problem. I have more than double checked that the path is correct. In fact, I just copy and paste the path that is working in Avicsync.

 

 
Page 2 of 3 FirstFirst 123 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.