Nightly build.
What's changed in 0.4.1830
- Vela says when Google is giving it a limited view
- No colored strip behind the arrow when pausing or resuming a drive
- Passed street bubbles ride down to the bottom bar before fading
- Street-name bubbles stay until you pass them, then fade out
- Drives can remove the next stop, and every drive shows Edit route
- Navigation with a route up and the car parked stops redrawing the map, so the phone no longer runs hot, and a U-turn step no longer reads Bear uturn
- Manhattan and other dense cities stay smooth when zoomed in close, with no calibration update needed
- Offline search results and place pages show the city, state and ZIP when OpenStreetMap only tagged the street
- The route line no longer flickers when traffic refreshes, the road name stays up on ramps, plate cameras sit beside stoplights instead of on them, and a faster route chimes before it is offered
- A region with no place pack or places file published counts as fully downloaded instead of partly
- A region download keeps its progress card up until the map itself is in, says ready only then, and the Offline maps page lists downloaded regions with no signal
- Settings > Privacy starts a new Google session every week, every day or every time Vela opens, so what Google can link stays short
- Fresh installs keep Google's consent cookies on the long-running session, so EU users are not sent to the consent page
- Popular times show again on busy places: place details, photos and reviews use the WebView's long-running Google session
- The updater picks the APK for your phone's chip type, ready for smaller per-chip downloads
- Google requests use Chrome's own network stack on ARM phones, and emulators keep working on the old one
- Vela talks to Google through Chrome's own network stack, so its connections look like Chrome's instead of a Java library's
- Reviews stay on the page that keeps Google's full list, and the reviews page no longer throws away a working session
- The OpenStreetMap shops switch is gone now that the places data includes them, and hiding parks and civic places works on Vela's own places too
- Popular times and More photos come from plain requests too, so opening a place normally loads no Google page at all
- Places remember their photos and reviews for a few hours, the review list can load its next page, and each new Google method has a remote off switch
- Review and photo requests retry once in a fresh Google session instead of falling back to a page load
- Opening a place asks Google for its photos and reviews in one request each instead of loading Google's web app
- Opening a place loads its first photos and reviews instead of everything, and More photos gets the rest
- Google requests describe a real desktop window, picked once per install, instead of the same 1024x768 for everyone
- Famous landmarks show from farther out: the places bake counts how many languages a place is named in
- Vela claims Chrome 154 to Google, with the client hints Chrome 154 actually sends
- Vela now claims Chrome 154, with the exact client hints that release sends
- Full reviews page retries on a fresh session when Google's limited view stops More reviews, and the log says so
- Timed requests to Google get a random spread, and a daily check watches Google's answers and the Chrome version Vela claims
- Switching places to Google no longer hides the map's parks and temples
- Parks, museums, temples and other landmarks now come from Vela's own places, so the map draws one set of points instead of two
- Settings has a Performance page: load voice search at startup (on for roomy phones) and compatibility rendering
Full changelog: v0.4.1801...v0.4.1830