The last destination is now at the top of the "History" list in the new
directions menu. It's just a press away. This has at least one advantage.
Before, you could never fully clear a route to start over. Pressing the
directions button would automatically start navigation to the most recent
[Arrgh, my reply has somehow been deleted twice now!]
The OSM tags are correct, and it looks right in the standard OpenStreetMap
Mapnik/-carto tiles (attached): in the absence of an area tag, or with
area=no, the breakwater is drawn as an outline. With area=yes, it's a
solid shape.
It's
With latest 3.3.6 OsmAnd I've noticed, that app stopped using the last used
destination point I used before I close it. Why is that? I always use my
"Home" as my final destination. Driving to work, then returning to home.
Driving to shop, than returning to home again... All of my navigation are
Hi Adam
Does this problem appear for other instances of breakwaters, or only
locally?
ie. Could it be an OSM (map) error?
(I see various styles of rendering such structures, maybe depending on
construction or use?)
Paul W
On Tuesday, March 19, 2019 at 11:20:47 PM UTC, Adam Schneider wrote:
>
Hello Gildo Schuster.
Re 1:- "smartphone mounts ".
Have you tried these? > https://getfinn.com/en/ from
https://www.bikecitizens.net/ . Very stretchy. Great in dry weather, or if
your phone is rain-proof. If not, tuck a polythene bag over the front &
top. I had tried some cheap alternatives
2 months later. - All looking good now around The Isle Of Wight (off south
coast of England, in case you were wondering).
The areas which had been showing as flooded are now properly rendered.
Maybe a combination of OSM map updates and OsmAnd updates(?).
Thank you all for you input.
Paul W
On
On Sony Z1 compact (2 GB RAM) — works fast.
On Lenovo Tab 4 (2 GB RAM) — works not so fast as on Z1 but comfortable.
On old Motorola Atrix 2 (1 GB RAM) — works very slow, with hangs, with
crashes, sometimes reboot device.
--
You received this message because you are subscribed to the Google
@Harry's and @limom's description of how OsmAnd handles routes (as opposed
to tracks) was news to me, so I did some experimenting with RouteConverter
using v. 3.3.6--creating one GPX route for roads and a second for hiking
trails, and followed both. Some observations, based on this small
> I have an old nexus5 (which was way cool in 2013), and osmand runs ok on
> that, but I haven't tried to navigate with it lately.
I use a Samsung S5, which dates back to the same era (and both come
with 2GB of RAM) and Osmand runs fine in it, including navigation.
[ Funnily enough gsmarena.com
pap...@gmail.com writes:
> OsmAnd runs very slow at my old jelly beans phone. I will buy a new one.
> How much RAM and storage and how many cores with which frequency is needed
> to achieve a good performance for OsmAnd?
Hard to say, but a modern device with 3G of ram and a 64-bit arm chip
On Tuesday, 19 March 2019 12:06:30 UTC+1, pap...@gmail.com wrote:
>
> Hello,
>
> OsmAnd runs very slow at my old jelly beans phone. I will buy a new one.
> How much RAM and storage and how many cores with which frequency is needed
> to achieve a good performance for OsmAnd?
>
> Best regards,
>
Hello,
OsmAnd runs very slow at my old jelly beans phone. I will buy a new one.
How much RAM and storage and how many cores with which frequency is needed
to achieve a good performance for OsmAnd?
Best regards,
Klaus
--
You received this message because you are subscribed to the Google
I have a suggestion and a query, they both relate to the use of the app for
cycling:
- could we have an option to deactivate the green slope/gradient graph on route
info? It renders the blue elevation graph unreadable on longer routes. On a
mountainous area all I can see is a green cardiac
13 matches
Mail list logo
