how to go back to previous version?

[Nico W]

Since the current version keeps crashing and I need a reliable version, how do I go back to 1.5?
I went to settings, about, clicked on 1.6.5 and a long list showed up. I selected "old nightly build 28-9-13". I used package installer and a download bar showed, followed by a message "download failed".
What am I doing wrong?

[EvanCanton]

You can find all of the versions here: http://download.osmand.net/releases/

Just use a web browser on your device to download the version you want, once downloaded, (to your downloads folder) click the .apk file in a file explorer, or use the Android DOWNLOADS icon and click the file to install it.  But first, you may have to go into SETTINGS on your device to allow installations from sources other than the play store.

You did not say if you were using the paid or the free version, I don't for sure know what would happen if you use this method to roll-back if you are using the OsmAnd+, I'm not sure the license will be retained, perhaps someone can chime in on that... If you are using the free version, there is nothing to worry about.

[Nico W]

I have the plus version and the free version. I did delete the free version after the pre-installation message showed the free version's logo. However downloading the 1.5 version again did re-install the free version and brought it from 1.3 to 1.5. The paid version never changed ( and is still useless). My phone does not give me the option to choose which version I want to change. I have reached the free download limit in the free version, so I can not update the maps anymore.

[EvanCanton]

I like to use ES File Manger (a free app in the app store) to make backups of all my apps each time they are updated, I then keep two old backups of each app on my device and transfer the older ones to my desktop for storage. Then if an updated app does not function properly, I can go back to the old version by simply clicking the .APK file it saves as a backup (they have version numbers).  I know that's not helpful to you now, but it is a great plan going forward, everyone should really be doing this or its equivalent with some other app.  It was a major disappointment to me that the App Store does not allow one to download old versions of apps, because updates are bound to cause problems sometimes.  Believe me, I had to find out the hard way.

[Nico W]

I am surprised though that Osmand does not give the option of which version to update / roll back.

[Nico W]

does any of the developers have a suggestion on how to solve this problem?

[Stephan75]

So you want a feature inside Osmand app to install an older apk file of Osmand?

I am not aware that ANY android app has such a feature.

IMHO you have to decide whether you want to use the Osmand versions from GooglePlay ... then you also get notifications about updates.

OR you use ONLY manually downloaded aps files from http://download.osmand.net/releases/ or even one of the nightly-builds. But no update message then.

When on the manually way, you can freely choose the apk file you want to go back if necessary.

Or did I not understand your issue completely?

Stephan

[Harry van der Wolf]

2013/11/30 Stephan75 <der.steph...@googlemail.com>

So you want a feature inside Osmand app to install an older apk file of Osmand?

OR you use ONLY manually downloaded aps files from http://download.osmand.net/releases/ or even one of the nightly-builds. But no update message then.

Not entirely true. The releases from http://download.osmand.net/releases/ are signed apks and have the same signature as the releases on Google Play. So if you download and install for example a 1.5.2 version on your phone/tablet, google play will notify you within 10-300 minutes (or so) that a new release (the current 1.6.5) is available. You have to switch off automatic updates and neither download the new version in that case.

Harry

[Sabra Sharaya]

I have always felt like these separate apk files, that are labeled as plug-ins, we're stupid. But this is one case in which it would be good. An external "plugin" app for maintaining new, old, and beta version of OsmAnd in the device.

[Rodolfo]

>> "You have to switch off automatic updates and neither download the new version in that case."

@Nico:
If you want to do it that way, then please have a look at Changelog.
It might save you a lot of "Google Play hassle".

[Nico W]

I need to go back to an older , less memory intense version. Osmand has grown to such a size that older phones (mine is 2 years old) running older versions of Android ( mine is 2.2.1) are not longer able to run this app. I have 11 MB of memory, 1.6 uses 16MB!
Victor send me a message that due to a different certificate, the plus (paid) version cannot be rolled back. The free version can, but already long ago I reached the download limit. Essentially I'm stuck with a useless app.

[Luke Bryan]

Osmand runs a little slow, but decently well on my older 2.2.2 Android. I don't think it's a memory problem, as all Android apps are limited to 16mb or 24mb or whatever their heap limit is set to.

I'm using the Nightly builds, they may be faster than the current release? There's also FDroid repo with Osmand, but last I checked the arm6 support was broken.

You might try these, maybe back up your favorites and uninstall, reinstall and see if it helps.

[Max]

I'm not sure, but maybe it has something to do with transparency function.

Just to be sure, do you have "no polygons" option enabled?

Transparency uses ARGB 8888 = 32 bit/pixel = 4 Byte/pixel

Without transparency RGB 565 is used = 16 bit/pixel = 2 Byte/pixel

Thus, if transparency is enabled, bitmap needs 2x memory.

But I don't know, if this this has something to do with your memory problem.

Regards,
Max

[Harry van der Wolf]

It definitely has to do with memory limitations. The apps listen to the heap size set in the build.prop (parameter dalvik.vm.heapsize).
On smaller phones with lower memeory the heapsize is already set to lower values. If you have a heap size of 24M on older phones and OsmAnd takes already 16MB, you only have 4MB left for rendering and route calculation. That is not enough.
Also the resolution of your screen counts whether it is 320x240, or 480x240 or 800x480 or bigger. It requires both memory, but also CPU.
In my case I have an 800x480 with enough memeory but the CPU is less powerful,. With Osmand 1.6.5 with double layers and a resolution of 800x480 it simply can keep up withrendering, whereas a maybe older phone with only 320x240 can still keep up with the rendering.

The new 1.6.5 is a real performance and memory hog.

The builds via the new SDK will even be bigger, but then the builds will be architecture dependent to decrease the memory footprint.

The old builds are multi-architecture.

Harry

2013/12/4 Luke Bryan <luk...@msn.com>

--
You received this message because you are subscribed to the Google Groups "Osmand" group.
To unsubscribe from this group and stop receiving emails from it, send an email to osmand+un...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Harry van der Wolf]

2013/12/5 Max <openstre...@nurfuerspam.de>

I'm not sure, but maybe it has something to do with transparency function.

Just to be sure, do you have "no polygons" option enabled?

Transparency uses ARGB 8888 = 32 bit/pixel = 4 Byte/pixel

Without transparency RGB 565 is used = 16 bit/pixel = 2 Byte/pixel

Thus, if transparency is enabled, bitmap needs 2x memory.

 Just to make sure I really understood: When polygons are switched off, you need twice as much memory for rendering?

Harry

[Max]

Hi Harry!

 Just to make sure I really understood: When polygons are switched off, you need twice as much memory for rendering?

Very good question!

I tested, but it does not increase at once, if I enable transparency.
My "Android limit" and "Dalvik values" values are increasing dynamically.
Maybe old Android versions are not able to encrease memory limit?

But after your question, I looked at the code again and I discovered, that now always ARGB 8888 is used, so my ARGB 8888 vs. RGB 565 information is outdated:
https://github.com/osmandapp/Osmand/commit/0b86665092c5a1748f39fe0051db6db9fd4a526b

So in both cases (transparent and non-transparent), the result is the same, bitmap always needs twice as much memory.

Regards,
Max

[Max]

But, native memory should be used, if native lib is available?
https://github.com/osmandapp/Osmand/blob/0b86665092c5a1748f39fe0051db6db9fd4a526b/OsmAnd/src/net/osmand/plus/render/MapRenderRepositories.java#L608

Regards,
Max

[Max]

Hi Nico!

Please could you make sure that the "No Polygons" and "safe mode" options are disabled and then test this 3 old versions:
http://download.osmand.net/night-builds/OsmAnd-old-master-nb-2013-10-16.apk
http://download.osmand.net/night-builds/OsmAnd-old-master-nb-2013-10-17.apk
http://download.osmand.net/night-builds/OsmAnd-old-master-nb-2013-10-18.apk

Which one is working/not working?
Always make sure, that "safe mode" is disabled (and OsmAnd does not enable it while you are testing these versions) and this option is not grayed out.

After your test, I know, if my assumption is right or wrong.

Regards,
Max

On Tuesday, December 3, 2013 8:47:03 AM UTC+1, Nico W wrote:

[Harry van der Wolf]

2013/12/5 Max <openstre...@nurfuerspam.de>

But, native memory should be used, if native lib is available?
https://github.com/osmandapp/Osmand/blob/0b86665092c5a1748f39fe0051db6db9fd4a526b/OsmAnd/src/net/osmand/plus/render/MapRenderRepositories.java#L608

Regards,
Max

So it seems that native memory is used. As such it doesn't matter. My daughters older phone, which I sometimes use for testing as well, has "only" 32MB. If "bare" OsmAnd takes 16 MB and Android system services are running, it doesn't matter much whether native memory is used or java heap space: there is not enough memory anyway.

On my 512MB phone with 800x480 resolution, Osmand uses up to 80MB! for rendering.
For calculating routes of about 100-150 kilometers it uses 95-105MB!
For calculating a route of 600 km it uses up to 188MB!
That is huge!

It's not a big mystery why this causes issues on smaller phones.

Harry

[Max]

Hi Harry,

yes, you are right.

But if I understood Nico right, it works with version 1.5 on his device.

If this problem occurs, because of the switch to ARGB 8888 (I'm not sure, if this makes the difference), maybe it would be possible to offer an option to disable transparency completely and use RGB 565 in this case.
Should only be a few lines of code.

Regards,
Max

[Nico W]

Hi Max, I unistalled the +version and installed the -18 version as you suggested for testing. Safe mode is not enabled (never was), but I do have the polygons enabled ( this way I can see park boundaries). The map renderes slow and a route I had made the program crah when I added a waypoint (a route that I try to make makes a wrong turn , so I need to add a waypoint to get it right). The little red progress bar when calculating the route went immediately full red, yet it took quite a while longer to get the route shown. Starting the simulation worked ok, but the voice only came on twice to warn of exceeding the speed limit. So far the program did not crash moving /scrolling the map. Over the next few days I will try to see how it does navigating and tracking ( last weekend a hike in the forest with gpx tracking enabled made the program crash every minute or two. I had a gpx log out of this world, but all tiny bits and pieces. I wish there was a way to glue them all together and make it one track).
Let me know of you want me to uninstall the - 18 version and test the 2 previous ones.

Thanks for the help so far, very much appreciated.

[Max]

Hi Nico!

Let me know of you want me to uninstall the - 18 version and test the 2 previous ones.

The mentioned change was about October 17.
16 should be "good" version, 18 should be "bad" version, if my assumption is correct.
17 could be "good" or "bad", don't know because I didn't compare exact times (time zones...).

Regards,
Max

[Max]

Yes, please also test 16 (and maybe 17).

Regards,
Max

[Nico W]

I did use the 18 version today, navigating for about 20 miles. On the way down it crashed soon after entering the freeway, I left it alone. On the way back it did not crash, but it told me to take every off- and on-ramp along the freeway, about 5 or 6 in total. Very strange.

I will uninstall -18 and try -16 next

[Nico W]

I did install version 16 and it has been relatively stable. It sometimes gives an error message on startup ( program stopped unexpectedly) and hitting "force close" brings it back to the osmand opening page. From then on it works quite well, although it takes time to draw the map. This is not an issue when driving.

There is a very interesting problem going on when driving on I-5 north of Seattle. When driving south the directions are fine. Driving north however it wants to take several off ramps and re-enter via the on-ramp.

The directions themselves are weird too. Not the straightest route or the fastest. All kinds of turns via small roads with low speed limits instead of straight larger roads with higher speed limits. I went from Lynnwood to the Martin L. King / Cherry Street intersection in Seattle. First attempt sent me to SR 522. Useless. Next went down I-5. Fine. When I took a turn to the 520 bridge to turn immediately right on Montlake Blvd / 23rd Ave it send me straight out to the Lake Washington Blvd, a very twisty 25 mph route through the arboratum and along lake Washington, followed by a turn back towards 23rd Ave later on. I don' get it.
I have noticed this before where I would program a route to a ferry (I-5 / SR 104 to Edmonds ferry).Instead of taking the most direct road that has the ferry waiting lanes on the side it takes a route that ends up at a point from where it is illegal to enter the ferry. You would have to go 3 miles back , make a U-turn and enter the ferry waiting lanes. If I put in a waypoint it will calculate the correct route. If you don't have local knowledge you'll have a very frustrating time.

There was a 120 degree right turn on the way back that was announced as "slightly right". Also giving complicated directions. Instead of giving a straight route towards I-5 it was going to make me turn right onto Broadway......

[Nico W]

Yesterday I used the-16 version in the pedestrian map while hiking, not to navigate but to see the trails and track my progress. The program crashed constantly. iI pulled the battery several times, turned the phone off and on but no difference. After 1.5 hours my battery had almost completely drained.
The car navigation to and from the forest went just fine.

So why does it work fine when moving fast on a freeway, complete with route recalculations and voice directions, but it crashes going 3 miles an hour in a forest where the entire screen is green with just a few red dotted lines ( trails)?