Fix the problem that the Sensor Frameowk and UAF use different data
authorsaerome.kim <saerome.kim@samsung.com>
Mon, 21 Oct 2019 11:44:26 +0000 (20:44 +0900)
committersaerome.kim <saerome.kim@samsung.com>
Fri, 1 Nov 2019 03:53:55 +0000 (12:53 +0900)
commit65e02cdce6f6c595d390ae5fa87cd22c72516ae5
tree258904fa37f88c03601635fe52d3c8f25e8e6d53
parent959befc110142a7f954321584ad541f8d2355aa0
Fix the problem that the Sensor Frameowk and UAF use different data
format

- Problem: The data format of timestamp is not different from the sensor framework.
- Cause: The UAF uses 32 bit timestamp but the sensor framework uses 64
bit timestamp.
- Solution: Change timestamps in UAF with 64-bit unsigned long long.

Change-Id: I237f7201d7e7fed00858c47ca9350fcb1ad655c4
Signed-off-by: saerome.kim <saerome.kim@samsung.com>
include/ua-api.h
packaging/ua-manager.spec
ua-api/src/ua-event-handler.c
ua-daemon/include/ua-manager-core.h
ua-daemon/include/ua-manager-database.h
ua-daemon/src/pm/ua-motion-plugin-handler.c
ua-daemon/src/pm/ua-pm-util.c
ua-daemon/src/ua-manager-core.c
ua-daemon/src/ua-manager-device-db.c
ua-plugins/include/ua-plugin.h