Fix an issue that audio timestamp is set to 0
A timestamp get from audio hal would sometimes jump up
over maximum value of INT32.
Since LinearMap does not assume that the data to be handled exceeds
INT32, it cannot return the correct timestamp.
Change to expand the data size of the problem location from INT32
to INT64.
Bug: 150258010
Bug: 162814479
Test: manual (see bug)
Test: AudioRecordTest#testTimestamp
Test: AudioTrackTest#testGetTimestamp AudioTrackTest#testFastTimestamp
Merged-In: I6582d62ea5b7e56a4da3c32c5dd5ec571931e149
Change-Id: I6582d62ea5b7e56a4da3c32c5dd5ec571931e149
1 file changed