Modified default skin by arimi

hello, where can find full skin?
thank you

@rodanny
full here, [Only registered and activated users can see links. Click Here To Register...]

You could have tried and browsed the topic yourself :smile:

Quote:

---

Originally Posted by silkwormb [Only registered and activated users can see links. Click Here To Register...]

... when i try to watch a whole route or change route like add new waypoint program often shuts down. I used latest skin in other versions NextGen...Android 4.4.2 KitKat, 1 gb

Now I have new pad with 2gb,android 7.0 ... when I touch the map in navigation mode or try to change a route like add a new waypoint (some parking etc) the igo crashes. ...The best skin but unstable...

---

Somehow I missed this post, so maybe it’s too late to react.

No, this skin is not unstable at all, and personally I have never had a problem with it on any device.
You must know that when problems of such a case occur, the problem is ALMOST ALWAYS and exclusively - content.
If we exclude the case that the device itself may be problematic, (memory/storage, overloaded system, etc.), a file may be defective (very common with map add-ons), it's easy to overcrowd, too many licenses, too many speedcams, duplicate hnr files, unnecessary fds, with the newer map edition a fresh globalcfg is required, etc.
Sometimes it is enough to change the provider so that mistakes are lost.
For the specific errors you mentioned, hsp files are often to blame, for example.

Some general guidelines, except content:
For older editions of Android and weaker devices, the best skin edition is from the time period of that Android.
You don't even need all the extras from the skin (VR, TTS, visual/color "decorations", online services...), make a selection.
Put only one sure correct fbl file, the proper language/voice file, so give it a try. Compare behavior.
Then add the rest one by one - fda, fpa, fjw, poi...

For the newer device and the "problem" with it, the previous note on the content supports it. As we very often note - DO NOT OVERLOAD.
Btw, neither of these two devices is bursting with power, obviously, so adding skin can be too much for an already overloaded system.

@silkwormb and others,

Adding to explanation from Boki, I usually had similar problems when ALL HNR files were in map folder - Eastern Europe, Full Europe and Western Europe.
You need ONLY ONE package of them.
If you use all maps (complete Europe) then use ONLY Full Europe HNR files (not Eastern + Western Europe).
Same is for only Eastern or only Western maps, then use ONLY according HNR files.

You can use Full Europe HNR files regardless of maps combination.

But if some maps (FBL files) are missing, don't forget to put in sys.txt file:

Code:

---

[hnr]
ignored_missing_country_ids=*

[route]
hnr_ignored_missing_country_ids=*

---

Missing this could also be reason for crashing, so you can leave this in sys.txt also if you have all maps included.

Spoiler: two large screenshots

[Only registered and activated users can see links. Click Here To Register...]

[Only registered and activated users can see links. Click Here To Register...]

the best skin for a truck

Hi there,

Just installed iGO Nextgen 9.18.27.687519 (Israel) with Arimi skin version 12 March 2020, on Sony Xperia 10 III. Just wander, should Online traffic to work or not in this version? It seems now it is not working, as well as weather online. Should it suppose to work on this version? Maybe I need to change Sys file as well, or modify it? Thank you.

Oh another one ... another valuable and regular member who follows the events on the forum :smile:
Last asked literally a few days ago, in the [Only registered and activated users can see links. Click Here To Register...]
Same answer:
[Only registered and activated users can see links. Click Here To Register...]

Hi there,
I am using Arimi skin, I noticed that there is a continuous increase button while simulating in the_skin.lua file located at the_skin_ari_nextgen.zip\ui_nextgen\common\ui. How can we do it the other way around? So I also want it to be decreasing.
Thank you from now.
Its content is as follows:

Code:

---

function sc_simulate_speedup()
local SpeedPercent = MODEL.route.simulation_speed_percent()
local NewSpeedPercent = 100
if SpeedPercent == 100 then
NewSpeedPercent = 200
elseif SpeedPercent == 200 then
NewSpeedPercent = 300
elseif SpeedPercent == 300 then
NewSpeedPercent = 400
elseif SpeedPercent == 400 then
NewSpeedPercent = 500
elseif SpeedPercent == 500 then
NewSpeedPercent = 600
elseif SpeedPercent == 600 then
NewSpeedPercent = 700
elseif SpeedPercent == 700 then
NewSpeedPercent = 800
elseif SpeedPercent == 800 then
NewSpeedPercent = 900
elseif SpeedPercent == 900 then
NewSpeedPercent = 1000
elseif SpeedPercent == 1000 then
NewSpeedPercent = 1100
elseif SpeedPercent == 1100 then
NewSpeedPercent = 1200
elseif SpeedPercent == 1200 then
NewSpeedPercent = 1300
elseif SpeedPercent == 1300 then
NewSpeedPercent = 1400
elseif SpeedPercent == 1400 then
NewSpeedPercent = 1500
elseif SpeedPercent == 1500 then
NewSpeedPercent = 1600
else
NewSpeedPercent = 100
end
MODEL.route.simulation_speed_percent = NewSpeedPercent
end

---

Spoiler: screenshot

[Only registered and activated users can see links. Click Here To Register...]

Pausing the simulation allows you to return the speed to the minimum without additional button or function ;)


Otherwise,
add this function after the previous
function sc_simulate_speedup()
.....
end

Code:

---

function sc_simulate_speeddown()
local SpeedPercent = MODEL.route.simulation_speed_percent()
local NewSpeedPercent = 100
if SpeedPercent == 200 then
NewSpeedPercent = 100
elseif SpeedPercent == 300 then
NewSpeedPercent = 200
elseif SpeedPercent == 400 then
NewSpeedPercent = 300
elseif SpeedPercent == 500 then
NewSpeedPercent = 400
elseif SpeedPercent == 600 then
NewSpeedPercent = 500
elseif SpeedPercent == 700 then
NewSpeedPercent = 600
elseif SpeedPercent == 800 then
NewSpeedPercent = 700
elseif SpeedPercent == 900 then
NewSpeedPercent = 800
elseif SpeedPercent == 1000 then
NewSpeedPercent = 900
elseif SpeedPercent == 1100 then
NewSpeedPercent = 1000
elseif SpeedPercent == 1200 then
NewSpeedPercent = 1100
elseif SpeedPercent == 1300 then
NewSpeedPercent = 1200
elseif SpeedPercent == 1400 then
NewSpeedPercent = 1300
elseif SpeedPercent == 1500 then
NewSpeedPercent = 1400
elseif SpeedPercent == 1600 then
NewSpeedPercent = 1500
else
NewSpeedPercent = 100
end
MODEL.route.simulation_speed_percent = NewSpeedPercent
end

---

locate the appropriate navigatemap.ui containing the simulation buttons, find <layer ui_SimulationControls definition

copy the entire last button definition which contain sc_simulate_speedup() ad control speed of simulation ,

to add a 'decrease button' on left, put the previous copy just under <HBOX class="simulation_controls at first place in the uttons list and replace sc_simulate_speedup() in it by sc_simulate_speeddown()

save ui and lua, that's all

Hello friends, the problem I mentioned about has been solved. As our friend LUNAPARK shared it, tnx to him
GPS POWER GOOD LUCK.;)

Spoiler: +

[Only registered and activated users can see links. Click Here To Register...]