Everything in threes is perfect (IntMem, SD card, All Android) iGO 9.6.29.596752 based

**osiris4isis** · 6th March 2016, 11:48 PM

Originally Posted by Adreno

Thanks wojpen.

However, it seems that the problem is not a problem of memory use, seems to be a problem of lack of CPU to move 3D maps in high resolution (maybe due to Marshmallow, to CyanogenMOD...).

As you can see in the images, the max RAM amount used by iGO was around 0.5 GB, far away from the 1 GB of free RAM.

Spoiler: screens

Sent from my Z1 using Tapatalk

Yeah, my gut feeling is non-optimal graphic driver used by CM; maybe you should check in CM forum on any report of slow display by migrating from Marsh to CM.

**corpcd** · 20th March 2017, 07:27 PM

Originally Posted by wojpen

Hello Friends Navigators,

In today's market navigation devices operate countless devices with different versions of operating systems and multiple screen sizes.
This causes - particularly among the new - less experienced users a lot of problems and confusion in the choice of our wonderful version of iGO.

Hi:

I have a car head unit which is 1024x600 with Android 6.0.1. I'm trying to get this version working, but i think i do not find the right parameters.

Clean installation, using only the files in this release, installed to the external sdcard.

What I've tried so far, all changes made to multimode.ini inside data.zip and sys.txt:

Code:

Please Login or Register to see the links

Spoiler: pics

**modemakias** · 20th March 2017, 09:57 PM

Hello....

Try with this multimode.ini

Replace these lines inside the data.zip \ui_android\multimode.ini...
or save in a text as "multimode.ini".... and place it inside the folder "ui_android" (iGO\ui_android)

[modes]
; mx=WidthMin..WidthMax, HeightMin..HeightMax,Folder
; OR
; mx=Width, Height ,Folder

;m1=400..480,196..320,"480_272"
;m2=234..320,400..480,"480_272"
m3=800..1050,500..600,"800_480"
m4=500..600,800..1050,"800_480"
;m5=1024..1280,552..800,"1024_768"
;m6=600..800,960..1280,"1024_768"

add these lines in your SYS...

[rawdisplay]
force_renderer="RENDER_MOYA"
driver=engine
screen_xy="auto"

1.delete save folder from iGO content...
2.go to settings -> app Manager -> iGO -> select "force stop" and then "clear cache mem"

run the iGO again for try...

**wojpen** · 21st March 2017, 12:13 AM

Hi.
Little note - but very important !!!
If the program was downloaded from my post # 1, or mirror Navigator - post # 2
Please absolutely !!! Turn off the line in sys.txt
screen_xy = "detect" -> ;screen_xy = "detect"
Otherwise, this - what @Modemakias proposes - will not work.

Probably not to disable this line was the cause of the error

This line from post
1:
m3 = 900..1050,450..620 "800_480"
m4 = 550..620,850..1050, "800_480"

it's ok.

regards wojpen

PS. Oryginal section from sys.txt this Pack:

[rawdisplay]
force_renderer="RENDER_MOYA"
driver=engine
screen_xy="detect" -> disable this line!!! - ;screen_xy="detect"
;driver="gdi" ;for HD & QHD
;highres=1 ;for HD & QHD

[interface]
;vga=1 ;for HD & QHD
extra_settings=1
save_checksum=0
maxzoom2d=6000000
minzoom2d=15
;show_glonass=1

**corpcd** · 21st March 2017, 07:46 AM

Originally Posted by wojpen

Hi.
Little note - but very important !!!
If the program was downloaded from my post # 1, or mirror Navigator - post # 2
Please absolutely !!! Turn off the line in sys.txt
screen_xy = "detect" -> ;screen_xy = "detect"

Yes, it's the version i downloaded from mirror post #2, and I think the first version has "detect" on and failed.

Originally Posted by wojpen

This line from post
1:
m3 = 900..1050,450..620 "800_480"
m4 = 550..620,850..1050, "800_480"

Yes, that's what I thought, the proposal from modemakias looks like the same I tried, both included my resolution.

Btw, yesterday I was trying all iGO releases and I found one that worked, iGO NextGen 9.18.27.658108, I will try your package setting detect off and report back, I'm curious.

Thank you both guys.

**corpcd** · 21st March 2017, 07:29 PM

Here are the test i made:

sys.txt

[rawdisplay]
force_renderer="RENDER_MOYA"
driver=engine
;screen_xy="detect"
;driver="gdi" ;for HD & QHD
;highres=1 ;for HD & QHD

multimode.ini in data.zip

[modes]
; mx=WidthMin..WidthMax, HeightMin..HeightMax,Folder
; OR
; mx=Width, Height ,Folder

;m1=400..480,196..320,"480_272"
;m2=234..320,400..480,"480_272"
;m3=768..960,400..600,"800_480"
;m4=480..600,700..960,"800_480"
;m5=1024..1280,552..800,"1024_768"
;m6=600..800,960..1280,"1024_768"
m3 = 900..1050,450..620 "800_480"
m4 = 550..620,850..1050, "800_480"

Cleared cache, restarted the device, and the result:

Spoiler: Picture:

I go back to the NextGen version that works.

**wojpen** · 22nd March 2017, 08:44 AM

Colleagues - You wrote "Cleared cache, restarted the device," and deleted the contents of SAVE folder?
If so - there can be only one cause:
Incorrectly updating data.zip file - after changing multimode.ini - unfortunately this happens quite often - the files are packed and should not be unpacked or changed in the wrong programs.
Multimode.ini is correct.

**corpcd** · 22nd March 2017, 11:43 AM

Originally Posted by wojpen

Colleagues - You wrote "Cleared cache, restarted the device," and deleted the contents of SAVE folder?
If so - there can be only one cause:
Incorrectly updating data.zip file - after changing multimode.ini - unfortunately this happens quite often - the files are packed and should not be unpacked or changed in the wrong programs.
Multimode.ini is correct.

Yes, deleted save folder.
Yes. ~~multimode.txt~~ multimode.ini file saved correctly, I checked again after saving (opening again the file to see if changes were aplyed).