-
Notifications
You must be signed in to change notification settings - Fork 5.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
robot controller6.2 crash in android 10 #119
Comments
This is currently a known issue. As no competition legal devices currently run Android 10, fixing this has not been high on the priority list, but it will be investigated at some point. |
I experience RobotController 6.2 crash on Android 10, too, also as soon as Driver Station connected to Robot Controller. But I don't see "libc :Access denied finding property "ro.serialno" in logs, instead, my crash backtrace is like below: 04-16 18:55:52.641 15797 15797 F DEBUG : signal 31 (SIGSYS), code -6 (SI_TKILL), fault addr -------- 04-16 18:55:53.025 15797 15797 F DEBUG : backtrace: With some google search it seems settimeofday() requires root privilege and probably this is why the app get killed. Is this the same problem as reported above, or a different one? (Complete log collected through "adb logcat" and AndroidStudio attached. |
Good sleuthing! We already figured out that was the issue, and have it fixed for the next release. |
Yes, this is indeed the issue. The Control Hub has a custom kernel to allow the system call, and unmodified Android versions before Pie will simply silently fail when making the call. However, newer versions will cause a native crash if an app tries to invoke that system call. This will be fixed in the next release of the SDK. |
Fixed in 7.0 |
when I try to use Driver Station to connect robot controller,RC crash every time. My android version is 10 ,and I try android 9,it has the same issue. But it works perfect in android 8.1.
I notice that the logs has tow orange information: libc :Access denied finding property "ro.serialno"
The text was updated successfully, but these errors were encountered: