Jump to content

green light

Members
  • Posts

    126
  • Joined

  • Last visited

  • Days Won

    4

green light last won the day on October 17 2020

green light had the most liked content!

Reputation

10 Good

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I stored route that I configured (and stored) for a day in Februrary. But when I load that route now, start departure time is one hour earlier. I specified 9:00am but now it is shown as 8am. My guess: DST. I stored the same with a date later in April, all fine. Changed days again back, one hour changed.
  2. Even if you add such a charger to the route and set the charge rate to eg. 70kW, it won't respect it: same charge time estimation as on a 50kW charger is shown.
  3. My expirience is that the new UI is slow with all browsers except Chrome and chrome based browsers (like new MS Edge).
  4. I defined the start time of a route at 8am, for June. Then I started calculation of the route and it shows a departure time of 7am. If I set date to something this month (January) it's fine.
  5. Firefox. And yes, it happens _always_ after several minutes route planning. Then it does multiple connections per _second_.
  6. After few minutes of working with ABRP, your user tracker and user monitor "bugsnag" tries to write anything to their servers, up to several connections per second. Not that is a really bad thing, it makes ABRP really slow. Clicking on the map to select a charger is impossible. Why is that? I blocked the URL, but this crappy JavaScript is still trying to connect and slows everything down.
  7. No, please, never: https://killedbygoogle.com/
  8. Maybe you already know: https://www.androidpolice.com/2020/08/11/android-auto-is-adding-new-categories-for-apps-including-parking-and-electric-vehicle-charging/?amp For me I don't need routing with ABRP in Android Auto. But the SOC graph and planned charging stops. So maybe this is possible with this new category.
  9. Just tried that. Now satelite view is shown and I cant read any menu now. So stuck in an unusable view...
  10. After several updates of the App still looking this way. Thats intended look?
  11. ABRP is getting very slow after multiple plannings and I get massiv errors in the logs (multiple per second): Quellübergreifende (Cross-Origin) Anfrage blockiert: Die Gleiche-Quelle-Regel verbietet das Lesen der externen Ressource auf https://sessions.bugsnag.com/. (Grund: CORS-Anschlag schlug fehl).
  12. Today I had many many crashes of the Android app. Mostly while rotating the phone (as it rotated whenever I picked it up), sometimes it had problems with the route at all and crashed. And once I couldn't get it started again. I had to clean up app's storage (not just the cache) to get it working again. This is nothing I would like to have when I am the driver. Luckily when this happened I wasn't.
  13. There was a fix in Leaf Spy Pro few days ago regarding ABRP server messages.
  14. Ist mir nie bewusst aufgefallen, aber stimmt. Der Grund ist vermutlich auch einfach: Die App nutzt Google Maps, die können das. Im Browser ist das ein anderer Kartendienst und der kann das nicht. Eine Option dazu gibt es auch nicht. Das müsste das ABRP-Team hinzufügen, falls es überhaupt geht. Maybe there is an option to enable road numbers within the API of the map service used in the browser?
×
×
  • Create New...