Téléchargement de l'application pour les conducteurs PYSAE Driver
Nicolas Jaulin avatar
Écrit par Nicolas Jaulin
Mis à jour cette semaine

Dernière version

La dernière version de l'application PYSAE Driver pour les conducteurs peut-être installée via Google Play.

mceclip0.png

Liens de téléchargement des APK pour les utilisateurs disposant d'un MDM

Le tableau ci-dessous répertorie les versions de PYSAE Driver et les liens pour le téléchargement des APK correspondant.

Version de PYSAE Driver

Evolutions

Version d'Android minimum

Lien de téléchargement

V4.2.3

Fix : fix HLP status

Recommandée : 13.0

Minimum : 11.0

V4.2.2

Fix : fix disabled "group" field

Recommandée : 13.0

Minimum : 11.0

V4.2.1

Fix : fix blank page on app launch for Android 9.0 devices

Recommandée : 13.0

Minimum : 9.0

V4.1.2

Fix : Display device_id in Driver Login view

Recommandée : 13.0

Minimum : 9.0

V4.1.1

Fix: Improve GPS refresh rate (60 pos/s)

Fix: issue with drivers / vehicles display on the left side of the Map view

Recommandée : 13.0

Minimum : 9.0

V4.1.0

Internal technical enhancements

Recommandée : 13.0

Minimum : 9.0

V4.0.5

Fix: blocking urgent message

Recommandée : 13.0

Minimum : 9.0

V4.0.4

Fix: fix delay calculation

Recommandée : 13.0

Minimum : 9.0

V4.0.3

Internal technical enhancements

Recommandée : 13.0

Minimum : 9.0

V4.0.2

Internal technical enhancements
Fix NMEA connector

Recommandée : 13.0

Minimum : 9.0

V4.0.1

Migrate to a whole new Framework

Mind : This version will disconnect the driver. Login is mandatory.

Recommandée : 13.0

Minimum : 9.0

V3.6.12

#307 Remove phone number

9.0

V3.6.11

#307 Remove phone number

#304 Lower Direction API pricing per month

#279 Get passenger count from network QIP

9.0

V3.6.9

303 Improve first stop distance calculation for stop detection in Driver

9.0

v3.6.8

302 Fix device name change in case of group change

296 Enable router config on ethernet

300 Redesign Admin - Clean unused code from groups properties

274 Switch Driver to new Vehicle and Drivers APIs

9.0

v3.6.7

  • 280 Add opStatus in duhIP connector

  • 297 Fix stop detection in case of multiple passages

  • 277 Remove 'without shape' trip capability

  • 271 Replace Here Maps with mapbox

9.0

v3.6.6

  • 290 Add stop detection to rest API

  • 295 Fix messages handling

9.0

v.3.6.5

  • 293 Fix datetime format in duhIp

9.0

v3.6.4

  • 257 Simplify stop detection

  • 287 Add GPS status debug

9.0

v3.6.3

  • 288 Add a retry mecanism to the router config

9.0

v3.6.2

  • 276 Reduce number of messages stored offline

  • 281 Fix setTimeout flood (trip-updates)

9.0

v.3.6.1

  • 265 Implement the new "Driver’s shift" (sequential service mode)

  • 240 Fix the departure time calculation when clocks changing

  • 273 Update targetSdkVersion Android Driver (API31 android 12)

  • 240-fix Fix hours displayed in trips view

  • 262 Create and display trip modification tags

9.0

v3.5.4

  • #275 Increase the interval for trip-updates polling

  • #269 Add block_id to the formatted name

  • #261 Create the "Do not service" stop components

  • #260 Implement the new "Driver's shift" (trip mode)

9.0

v.3.5.3

  • 270 Link AEP connector to the SSID

9.0

v.3.5.2

  • 263 Limit number of messages per minute in websocket

  • 256 Fix error on passenger cou

9.0

v.3.5.1

  • 264 Correcting the display conditions of stop info tags

  • 238 Display the "Stop info" on the banner on the schematic view and on the stop in question

  • 236 Display the "Stop info" on the banner on the map view and on the linked stop

9.0

v.3.5.0

  • 241 Update packages dependencies

  • 248 Fix UI after package updates

  • 249 Clean linter errors

  • 254 Apply and document the calculation rule for the "Wait at stop for departure time" function for Driver

9.0

v.3.4.21

  • 251 Change the url that Driver uses to retrieve its transport plan

  • 251-fix Change the url that Driver uses to retrieve its transport plan

9.0

v.3.4.20

  • 234 Fix service start inconsistencies

  • 231 Fix language list

9.0

v.3.4.19

  • 230 Reconnect automatically the websocket to the devices

9.0

v.3.4.18

  • 229 Add trip_short_name in SILV1

9.0

v.3.4.17

  • 222 Fix the estimated delay time on a break on the next stop

  • 227 Enhance TCP connections management

9.0

v.3.4.12

  • Send the next stop to Kuba only in the bubble of this stop.

  • Fix the multitude of socket connections on SILv1

  • Update the Kuba connector

  • Enable Code selection for KUBA in driver

7.0

v.3.4.11

  • Modify the centralized method for generating driver events

  • Fix the sending of messages with the new driver version number

7.0

v.3.4.10

  • Develop the SILv1 connector

7.0

v.3.4.9

  • Publish Driver APP to PlayStore

  • Make browserstack tests run on Android 10 devices

  • Update targetSdkVersion Android Driver (API30 android 11)

  • Add a maintenance mode build

  • Refactor Vix POC to Kuba interface

7.0

v.3.4.6

  • Fix estimated delay time on a break

  • Get a unique device ID

  • Add a "group" field in the identification view

  • Add a search engine in the " Trip list " view

7.0

v.3.4.5

  • Hardcode app version

  • Fix error when changing stop from Op

7.0

v.3.4.4

  • Update transport plan when starting from intent

7.0

v.3.4.3

  • Fix wrong transmission and display of the driver version in Driver and OP

  • Fix sending stop_sequence to AEP

  • Fix the browserstack "service mode" test

  • Highlight less past trips in the "trip list " view

  • Add "comment" field in "I can't find my trip" modal

7.0

v.3.4.2

  • Remove change name, mode and team from Driver

  • Fix the conditions of transit in "without shape" mode

  • Fix the Duhip "JP" network crash

7.0

v.3.4.1

  • Configure router port forwarding

  • Fix translations

  • Receive, manage and send PO information in Driver

  • Add and send message notifications in the background

  • Fix the stop change problem

  • Launch the Browserstack tests on a GTFS with trips without shapes

  • Fix router configuration

7.0

v.3.3.2

  • Update AEP IP

7.0

v.3.3.1

  • Update upload key

  • Fix incompatibility between android versions and Duhip serve

7.0

v 3.3.0

  • Enable multiple embedded interfaces (Driver)

  • Update environment for the preprod build of driver)

  • Change the width of NUM SERV field in AEP messages

7.0

3.2.6

  • Improve the monitoring of PYSAE Driver

  • Replace the tests in mode "Simulation" with mock GPS positions in Browserstack

  • Launch the Browertstack tests Large GTFS

  • Launch the Browserstack tests General

  • Send the trip selection information to the AEP system

  • Add build options

7.0

3.2.5

  • Add the AEP system in the Cordova plugin and service selection en +

7.0

3.2.3

  • Fix driver identification page display with the night mode en prod

7.0

3.2.2

  • Synchronize the GTFS only in the deadrunning view

7.0

Non disponible

3.2.1

  • Add the driver tests in Gitlab CI/CD

  • Add driver events in Pysae Tracer

  • Delay the loading of the shapes during the trip selection

7.0

3.2.0

  • Clean automatic service and line modes on Driver

  • Add a coefficient to api trip duration

  • Update Android target

7.0

3.1.0

  • Save the data when the driver app is in the background

  • Delete the nearby trips page

  • Implement a first test of Driver in browser stack

7.0

3.0.20

  • Add user list page in OP2

7.0

3.0.19

  • Change the delay calculation in driver

  • Fix the rules management of Driver's shift taken

  • Fix lost connection problem on driver app

  • Fix error on App resume

7.0

3.0.17

  • Fix delay sending to API by Driver

7.0

3.0.16

  • Removal of PYSAE Driver App autoupdate

  • Remove the page pysae.com/app

  • Fix forced start delay computation

7.0

3.0.15

  • Fix driver and vehicle selection

  • Fix stop trip simulation when mode is disabled

7.0

Nota Bene

La version minimum d'Android présentée est la version pour laquelle PYSAE garantit un fonctionnement de l'application embarquée. Pour les versions précédentes, l'application peut fonctionner mais PYSAE ne garantit pas son fonctionnement.

Avez-vous trouvé la réponse à votre question ?