Skip to content
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

Closed
steveliu168 opened this issue Mar 26, 2021 · 5 comments
Closed

robot controller6.2 crash in android 10 #119

steveliu168 opened this issue Mar 26, 2021 · 5 comments

Comments

@steveliu168
Copy link

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"

@Windwoes
Copy link
Member

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.

1198159 referenced this issue in technototes/UltimateGoal2020 Mar 27, 2021
@pennygao
Copy link

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:
04-16 18:55:53.025 15797 15797 F DEBUG : #00 pc 00000000000cea28 /apex/com.android.runtime/lib64/bionic/libc.so (settimeofday+8) (BuildId: 4cd97724e0ae0bf213b33eacb7bfbbe8)
04-16 18:55:53.026 15797 15797 F DEBUG : #1 pc 0000000000021eb4 /data/app/com.qualcomm.ftcrobotcontroller-G5ASKIaCF3aKTBC4z9uJcg==/lib/arm64/libRobotCore.so (Java_org_firstinspires_ftc_robotcore_internal_system_AppUtil_nativeSetCurrentTimeMillis+156) (BuildId: 6b9c6ad4e62aa663f15cf9cefbfcd8cbce597f33)
04-16 18:55:53.026 15797 15797 F DEBUG : #2 pc 000000000002f374 /data/app/com.qualcomm.ftcrobotcontroller-G5ASKIaCF3aKTBC4z9uJcg==/oat/arm64/base.odex (art_jni_trampoline+132)
04-16 18:55:53.026 15797 15797 F DEBUG : #3 pc 0000000000137334 /apex/com.android.runtime/lib64/libart.so (art_quick_invoke_stub+548) (BuildId: e1ef08b5ba2ec71adc5b7c8230ae4048)
04-16 18:55:53.026 15797 15797 F DEBUG : #4 pc 000000000014606c /apex/com.android.runtime/lib64/libart.so (art::ArtMethod::Invoke(art::Thread*, unsigned int*, unsigned int, art::JValue*, char const*)+244) (BuildId: e1ef08b5ba2ec71adc5b7c8230ae4048)

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.

log_from_adb_logcat.log
log_from_AndroidStudio.log

@NoahAndrews
Copy link
Member

Good sleuthing! We already figured out that was the issue, and have it fixed for the next release.

@Windwoes
Copy link
Member

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?

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.

@Windwoes
Copy link
Member

Fixed in 7.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants