# Android

## Additions

* `Trip.Expansion` includes few more expansions

```kotlin
/**
* Expand vehicle
*/
VEHICLE,

/**
* Expand include trip start and end points
*/
POIS,

/**
* Expand raw only data
*/
RAW_ONLY,

/**
* Expand include device id
*/
DEVICE,

/**
* Expand training status of the driver/passenger
*/
USER_TRAINING_STATUS,

/**
* Expand filters by association date
*/
FILTER_BY_ASSOCIATION_DATE
```

* Initialize DsDevice with `vehicleId` and associate the device using DsDeviceManager.associateDevice API for adding vehicle id to trip files for wedge solutions.
* TripService API Changes:
  * `TripService.fetch` and `TripService.fetchAll` now accept an additional roles parameter.
  * Use this to filter trips by `roles` when fetching.
* AccountRole Enum Expanded:
  * Two new cases have been added to the AccountRole enum:
  * namedDriver (for the "`NAMED_DRIVER`" role)
  * nonDrivingOwner (for the "`NON_DRIVING_OWNER`" role)
* Automatic Wedge Association Feature. Leare more here. [Link](https://sdk.ims.tech/automatic-wedge-association)
* Learn about the new WedgeService API. [Link](https://sdk.ims.tech/releases/1.25.0/broken-reference)

## Breaking Changes

* Trip.Expansion Updates:
  * The `GEOMETRY` property has been removed from `Trip.Expansion`. Please use the `POINTS` property instead.
* The DsDevice's batteryLevel property type is changed from Float to Int
  * `var batteryLevel: Int?`

## Limitations/Known issues

* Trip recording will continue uninterrupted after upgrading to SDK 1.25.0. However, existing trip files will not automatically include vehicle IDs. To add vehicle IDs to trip files for wedge solutions, initialize DsDevice with `vehicleId` and associate the device using DsDeviceManager.associateDevice API