ARMv7 v1.1.41 crashes on launch on some devices

[PlasmaticRiver]

After updating to v1.1.41, Obtainium crashes to launcher with a gray screen on a 2018 4k Firestick running Fire OS 6.7.0.9.

Steps to reproduce the behavior:

1. Sideload ARMv7 Obtainium APK onto device
2. Install APK
3. Launch from stock or 3rd party launcher

[ImranR98]

Does the OS give you any logs? The only thing that's changed that would be relevant is the Flutter (and some package) versions.

[PlasmaticRiver]

Sorry, accidentally closed this issue. FireOS doesn't have traditional logs the way stock Android does so I'd have to sideload something like LogFox and hope it works. I'll try to see if I can find something helpful, but I noticed that the previous version works fine and the current version also makes the stick make a weird sound when it attempts to launch.

[PlasmaticRiver]

Another thing, I can't pick an export directory on my Google TV Onn 4k box. I can on the fire TV altho the interface is really bad, but none of the third-party file managers come up when that's selected, only for choosing a file to import. My Onn device has no documentsui file picker built in and sideloading one doesn't work.

[yotoprules]

Same issue here,
Obtainium instantly crashes when launched, no error message.
I have tried both the F-Droid and non-F-Droid builds, both same issue.
This is an older device so I have only tried the v7 builds.
Nexus 5 - LineageOS 20 (Android 13).
Thank you!
1.1.40 works fine.

[xad0x]

similar issue, when i try to open the app with any version above 1.1.40 it is just stuck in the loading screen (where you just see the app logo)
samsung galaxy a40 running crdroid 9.11, android 13

[PlasmaticRiver]

similar issue, when i try to open the app with any version above 1.1.40 it is just stuck in the loading screen (where you just see the app logo) samsung galaxy a40 running crdroid 9.11, android 13

Think you could grab a logcat? Can't really do it on FireTV easily and it might point the dev to the problem.

[yotoprules]

similar issue, when i try to open the app with any version above 1.1.40 it is just stuck in the loading screen (where you just see the app logo) samsung galaxy a40 running crdroid 9.11, android 13

Think you could grab a logcat? Can't really do it on FireTV easily and it might point the dev to the problem.

First time doing logcat, hopefully done this correctly!

obtainiumcrash.txt

[mgg69420]

Hello!

I have the same problems with a Samsung Galaxy S5 running a LineageOS 18.1 fork, Android 11.

Last version that worked was 1.1.40.

Spent quite a bit of time filtering the logcat.
Also, i attached the tombstone related to the crash.

logcat.txt
tombstone_29.txt

Hope this helps.

[xad0x]

v1.1.46 fixes this issue for me! Both with armeabi-v7a and arm64-v8.

[PlasmaticRiver]

v1.1.46 fixes this issue for me! Both with armeabi-v7a and arm64-v8.

Just tried it and on Fire TV it still crashes like normal except the screen is now white instead of gray or something IDK.

[xad0x]

That's sad...

[PlasmaticRiver]

That's sad...

Latest works fine on my Onn 4k Google TV. That's also ARMv7 I'm pretty sure so I don't even know if the Fire Stick being ARMv7 is what's causing it. Could be some sort of Android dependency that is needed on the latest version? What device do you have that wasn't working and is now fixed?

[mgg69420]

Saddly v1.1.46 does not fix the issue for me.

I attached logcat and tombstone for the latest version of Obtainium (v1.1.46)

logcat.txt
tombstone_09.txt

Still the same error:

signal 11 (SIGSEGV), code 1 (SEGV_MAPERR) [...]
Cause: null pointer dereference

Maybe is not Obtainium's fault directly, maybe some dependancy of Obtainium is feeling funcky on ARMv7.

Best wishes!

[xad0x]

What device do you have that wasn't working and is now fixed?

Samsung galaxy a40 running crdroid 9.11, android 13

[yotoprules]

I can confirm 1.1.46 also has the exact same issue only Nexus 5, Android 13.

[ImranR98]

Can anyone with an affected device set up a dev environment and try troubleshooting? The logcats don't really have enough info and I don't have an affected device.

[yotoprules]

Can anyone with an affected device set up a dev environment and try troubleshooting? The logcats don't really have enough info and I don't have an affected device.

How do you do this, if I knew what to do I could give it a go.

[ImranR98]

You would need to install Flutter and Android dependencies (https://docs.flutter.dev/get-started/install), then clone the Obtainium repo and open it in Android Studio (or VSCode which is what I use alongside the Flutter extension). Then adjust the build configs, enable USB debugging on your device, connect it and build. From there you can start changing the code and investigating the problem.

If you're not a software dev it may not be feasible (or at least would take a long time).