Koan-Sin Tan
Koan-Sin Tan
on rooted device, `adb shell` then `setenfoce 0`, and `adb shell setenforce 0` (meaning disabling all the permission checks by the SELinux). @mohitmundhragithub and @AhmedTElthakeb
@freedomtan to check the NHWC -> NCHW conversion.
@anhappdev this NHWC -> NCHW looks right to me. Maybe you can try to compare with the result of using a single transpose op TFLite model (Yes, it's posssible. E.g.,...
> I suggest we first release a version with only TFLite backend to the Play Store and see if we still have the issue with `untrusted app` after the app...
For 2.0 submission: - Qualcomm: Xiaomi Mi 12, - Samsung S22, - Google: Pixel 6 Pro, - MediaTek: Xiaomi Redmi K50 Pro
@jwookiehong we should consider to have each vendor (or say vendor backend) to send a device (or devices) to @d-uzlov or @anhappdev to set up CI. Or, @anhappdev suggests, we...
@d-uzlov will post the supported device list from firebase.
It seems most of them are Google devices (no surprise). And few of them are recent devices (see the `OS_VERSION_IDS` column, which is supposed to be [Android API level](https://developer.android.com/studio/releases/platforms))
@d-uzlov suggested we can use some available devices in Firebase, e.g., Pixel devices, at first. And testing accuracy seems to be good. At least if a backend is running or...
> Another suggestion is to use another testing service if they have the desired device. A quick search gives me this: https://aws.amazon.com/device-farm/device-list/ https://saucelabs.com/platform/supported-browsers-devices Let's explore this kind of alternative device...