This is a list of the issues that I notice with V4.3.x as I try to run it on the Phone and Garmin data sources - I 'll put them in one issue for now as these are all part of getting V4.3.x working for the first time.
Warning about initialising TensorFlowLite: unable to update local snapshot for com.google.android.libraries.consentverifier#uk.org.openseizuredetector, may result in stale flags.
java.util.concurrent.ExecutionException: java.lang.SecurityException: GoogleCertificatesRslt: not allowed: pkg=uk.org.openseizuredetector, sha256=[bfca1a0bc536b323aae20da6f22675c049dbea2f3312b3fd584530c89c2efcff], atk=false, ver=234212037.true (go/gsrlt)
But it did say that the interpreter was initialised ok.
DataSourcePhone.onSensorChanged - reports received data over 4.4 seconds, which is about right, but calculated sample frequency is 0Hz -
DataTime from DataSourcePhone shown as 01/01/1970
SdData from DataSourcePhone contains lots of zeroes.
Arithmetic error calculating specpower and ROI power because of divide by zero (probably because of zero sample frequency).
On Emulator, received StrictMode policy violation: android.os.strictmode.DiskReadViolation and the app re-started (no activity, just service running in the background).
Will update this list as I spot more, than start crossing them off as fixed...
This is a list of the issues that I notice with V4.3.x as I try to run it on the Phone and Garmin data sources - I 'll put them in one issue for now as these are all part of getting V4.3.x working for the first time.
Warning about initialising TensorFlowLite: unable to update local snapshot for com.google.android.libraries.consentverifier#uk.org.openseizuredetector, may result in stale flags. java.util.concurrent.ExecutionException: java.lang.SecurityException: GoogleCertificatesRslt: not allowed: pkg=uk.org.openseizuredetector, sha256=[bfca1a0bc536b323aae20da6f22675c049dbea2f3312b3fd584530c89c2efcff], atk=false, ver=234212037.true (go/gsrlt) But it did say that the interpreter was initialised ok.
DataSourcePhone.onSensorChanged - reports received data over 4.4 seconds, which is about right, but calculated sample frequency is 0Hz -
DataTime from DataSourcePhone shown as 01/01/1970
SdData from DataSourcePhone contains lots of zeroes.
Arithmetic error calculating specpower and ROI power because of divide by zero (probably because of zero sample frequency).
On Emulator, received StrictMode policy violation: android.os.strictmode.DiskReadViolation and the app re-started (no activity, just service running in the background).
Will update this list as I spot more, than start crossing them off as fixed...