Describe the bug
A clear and concise description of what the bug is, a screenshot helps a lot. Do not use AI to generate this.
To Reproduce
Steps to reproduce the behavior:
- Open the file using "Open with" or from within the app
Expected behavior
Open the files like it does the seconds before it crashes
System Information:
F3D Information
type: crash
osVersion: google/cheetah/cheetah:16/BP4A.251205.006/2026050701:user/release-keys
flags: dev options enabled
package: app.f3d.F3D.android:1, targetSdk 35
process: app.f3d.F3D.android
installer: com.android.packageinstaller
signal 6 (SIGABRT), code -1 (SI_QUEUE), fault addr --------
Abort message: 'getHistoricalRawPointerCoords: Invalid array index 2 for MotionEvent { mAction=DOWN, mDownTime=0ns, mDeviceId=0, mSource=UNKNOWN, mDisplayId=0, mEventId=0x0, mPointerProperties=(0)[], mSampleEventTimes=(0)[], mSamplePointerCoords=(0)[] }'
backtrace:
#00 pc 000000000007bf2c /apex/com.android.runtime/lib64/bionic/libc.so (abort+156) (BuildId: e0ce667cc0126de53687d50691e2e2ee)
f3d-app/f3d#1 pc 0000000000920d14 /apex/com.android.art/lib64/libart.so (art::Runtime::Abort(char const*)+1012) (BuildId: 18171138f568afd8f62ab03b00113051)
f3d-app/f3d#2 pc 0000000000014df0 /apex/com.android.art/lib64/libbase.so (android::base::SetAborter(std::__1::function<void (char const*)>&&)::$_0::__invoke(char const*)+80) (BuildId: 16a65a739667269682cf6911c12bfbbc)
f3d-app/f3d#3 pc 000000000008c0d8 /system/lib64/libbinder.so (android::base::LogMessage::~LogMessage()+696) (BuildId: e54d7e13834472fce7f36a2d8f0ad89d)
f3d-app/f3d#4 pc 000000000022af54 /system/lib64/libinput.so (android::MotionEvent::getAxisValue(int, unsigned long) const+1860) (BuildId: 155ec9927273b5d6b1483de1343b7890)
f3d-app/f3d#5 pc 0000000000843ec0 /system/framework/arm64/boot-framework.oat (art_jni_trampoline+96) (BuildId: f401dc1bd056a87f005ece005b9dc28fb82e4e5f)
f3d-app/f3d#6 pc 00000000009dae74 /data/app/~~mD4Dt2T7hpDhJMcUJS2YaA==/app.f3d.F3D.android-GM7iDovNFz6jLZ-gSsrgjw==/oat/arm64/base.odex (app.f3d.F3D.android.RotateGestureDetector.onTouchEvent+276)
f3d-app/f3d#7 pc 00000000009d8788 /data/app/~~mD4Dt2T7hpDhJMcUJS2YaA==/app.f3d.F3D.android-GM7iDovNFz6jLZ-gSsrgjw==/oat/arm64/base.odex (app.f3d.F3D.android.MainView$$ExternalSyntheticLambda0.run+152)
f3d-app/f3d#8 pc 0000000000681524 /apex/com.android.art/lib64/libart.so (nterp_helper+7636) (BuildId: 18171138f568afd8f62ab03b00113051)
f3d-app/f3d#9 pc 0000000000235302 /system/framework/framework.jar (offset 0x1212000) (android.opengl.GLSurfaceView$GLThread.guardedRun+686)
f3d-app/f3d#10 pc 00000000006806a4 /apex/com.android.art/lib64/libart.so (nterp_helper+3924) (BuildId: 18171138f568afd8f62ab03b00113051)
f3d-app/f3d#11 pc 0000000000235b24 /system/framework/framework.jar (offset 0x1212000) (android.opengl.GLSurfaceView$GLThread.run+52)
f3d-app/f3d#12 pc 00000000002fd594 /apex/com.android.art/lib64/libart.so (art_quick_invoke_stub+612) (BuildId: 18171138f568afd8f62ab03b00113051)
f3d-app/f3d#13 pc 0000000000270dcc /apex/com.android.art/lib64/libart.so (art::ArtMethod::Invoke(art::Thread*, unsigned int*, unsigned int, art::JValue*, char const*)+220) (BuildId: 18171138f568afd8f62ab03b00113051)
f3d-app/f3d#14 pc 000000000048e578 /apex/com.android.art/lib64/libart.so (art::Thread::CreateCallback(void*)+1176) (BuildId: 18171138f568afd8f62ab03b00113051)
f3d-app/f3d#15 pc 000000000048e0c8 /apex/com.android.art/lib64/libart.so (art::Thread::CreateCallbackWithUffdGc(void*)+8) (BuildId: 18171138f568afd8f62ab03b00113051)
f3d-app/f3d#16 pc 000000000008e53c /apex/com.android.runtime/lib64/bionic/libc.so (__pthread_start(void*) (.__uniq.67847048707805468364044055584648682506)+236) (BuildId: e0ce667cc0126de53687d50691e2e2ee)
f3d-app/f3d#17 pc 000000000007f120 /apex/com.android.runtime/lib64/bionic/libc.so (__start_thread+64) (BuildId: e0ce667cc0126de53687d50691e2e2ee)
Additional context
GrapheneOS is very restrictive to how apps access the system.
idk if that is related to the root cause of the problem
Describe the bug
A clear and concise description of what the bug is, a screenshot helps a lot. Do not use AI to generate this.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Open the files like it does the seconds before it crashes
System Information:
F3D Information
Additional context
GrapheneOS is very restrictive to how apps access the system.
idk if that is related to the root cause of the problem