readme.md

@@ -2,8 +2,7 @@
 
 ## Purpose of this project
 
-Garmin created fantastic Head-up Display, but they had it discontinued in 2015[^1].
+Garmin created fantastic Head-up Display, but they had it discontinued in 2015 [src](https://support.garmin.com/pl-PL/?faq=gJy4U1QaPL2gBs3AqQ7Lm5). Fortunately, whole protocol had beed [reverse engineered](https://github.com/gabonator/Work-in-progress/tree/master/GarminHud). This allowed community to createte their own works.
-Fortunately, whole protocol had been reverse engineered[^2]. This allowed community to create their own works.
 
 ## Works
 
@@ -15,34 +14,19 @@ Two weeks later I switched to Mapbox as completely standalone solution. Despite
 
 ### Stack
 
-- Kotlin 1.9 
+- Kotlin 1.9i
 - Mapbox SDK 11.5.1
   - Navigation SDK 3.2.0
   - Search SDK 2.4.0
 
 ### Future works
 
-All the plans cannot be simply specified as they depend on many factors.
+- optimisation
-Main conception is not firmly grunted so it can depend on final decisions:
+- bug fixes
-
+  - camera behaviour
-1. Standalone application
+  - search prompt graphics
-   - optimisation
+  - reconnect button style
-   - bug fixes
+  - garmin connection fixes - socket behaviour on reconnect
-     - camera behaviour
+  - maneuver processing (on long distances it refreshes every 10+ km)
-     - search prompt graphics
+- Android Auto integration
-     - reconnect button style
+- create fork for first idea of proxying GMaps
-     - garmin connection fixes - socket behaviour on reconnect
-     - maneuver processing (on long distances it refreshes every 10+ km)
-   - Android Auto integration
-   - POIs
-   - speed cameras database
-   - traffic data
-
-2. Proxy (one to choose from)
-   - Google Maps (probably)
-   - Yanosik
-   - Waze
-
-[^1]: Source: https://support.garmin.com/pl-PL/?faq=gJy4U1QaPL2gBs3AqQ7Lm5
-
-[^2]: As widely described on sites like Hackday. Most repeated repo link is https://github.com/gabonator/Work-in-progress/tree/master/GarminHud