2018-04-28 12:49 GMT+02:00 Germano Massullo <[email protected]>:
> Il 28/04/2018 12:35, Harry van der Wolf ha scritto: > > - Having software rendering is NOT the issue. > More info about this? > > What do you mean exactly? Unless I should have stated it otherwise like: - The current software rendering is not the issue, although hardware rendering would probably give a smoother experience (not necessarily faster as what most people think). Hardware rendering is often overrated. To be able to use hardware render you also need a multi-threading application to be able to split off part of the graphic or calculation work to the GPU. Personally I would want, in the following order: - Get rid of the multi-zoom double layer rendering, or have an option to switch it off. - Make the app multi-threaded, also to improve the bi-directional A* navigation (re)calculations. - Add hardware rendering. Note also: I also use Mapfactor Navigator, which is fast in every aspect and light on memory use, but has low detailed maps when it comes to cycling or hiking. MNF has a setting to choose between hardware or software rendering, but on hardware rendering it even makes the phone (or Joying Android head unit in my car in my case) warmer. MNF on hardware render runs approximately 10 C higher than on software render. Also note that some phones really run warmer (extremely hot) than others. I have had several phones where some run a lot hotter than other doing the exact same tasks (incl. OsmAnd). -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
