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

Galaxy S8 with Android 7 - Photo crash #133

Closed
gnerred opened this issue Jun 2, 2017 · 26 comments
Closed

Galaxy S8 with Android 7 - Photo crash #133

gnerred opened this issue Jun 2, 2017 · 26 comments

Comments

@gnerred
Copy link

gnerred commented Jun 2, 2017

Some users reported me problems for making QField work on Galaxy S8 and Android 7. At this time I don't have all details, but :

  • Geolocation not working
  • Problem saving data
  • Crash when doing a picture

Are problems known with this configuration ?

@m-kuhn
Copy link
Member

m-kuhn commented Jun 2, 2017

Apparently there is a problem with loading the CRS database.
We are not sure if it's related to this device or to Android 7 in general or something else.

@gnerred
Copy link
Author

gnerred commented Jun 2, 2017

Ok thanks, let met know if we can help in solving this issue.

@m-kuhn
Copy link
Member

m-kuhn commented Jun 2, 2017

A device and ~2 days (very rough estimation, might be better or worse) to investigate will help

@gnerred
Copy link
Author

gnerred commented Jun 2, 2017

Ok thanks I will come back to you if I can find what you need.

@MieWinstrup
Copy link

Background information
QField version 0.8.8
Device: Samsung Galaxy S6 Edge, Andoid 7
QField project is made with QGIS 2.18.9 where the fieldtype for the photo-field is defined as External resources:
image

The case

  • Geolocation working :)
  • Saving data works fine :)
  • BUT Crash when saving a picture

I have the same problem with crash when saving a picture from QField. This means that I do get a possibility to open the camera and take a picture, but when I press 'OK', QField crashes (as illustrated below:

image

image

image

image

@donkey12345
Copy link

I think the picture is best stored in a file format.and Save the path to the database.

@m-kuhn
Copy link
Member

m-kuhn commented Jun 27, 2017

I think the picture is best stored in a file format.and Save the path to the database.

That's correct.

I recently found a device that shows a strange behavior with pictures (QField restarted) but unfortunately no hint in the logs what went wrong. Looks like the fix needs some more time invested.

@m-kuhn
Copy link
Member

m-kuhn commented Jul 3, 2017

Backtrace from an S7 Edge when the camera crashes

*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
Build fingerprint: 'samsung/hero2ltexx/hero2lte:7.0/NRD90M/G935FXXU1DQEI:user/release-keys'
Revision: '9'
ABI: 'arm'
pid: 27605, tid: 27605, name: .opengis.qfield  >>> ch.opengis.qfield <<<
signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
Abort message: 'art/runtime/java_vm_ext.cc:470] JNI DETECTED ERROR IN APPLICATION: java_class == null'
    r0 00000000  r1 00006bd5  r2 00000006  r3 00000008
    r4 e921858c  r5 00000006  r6 e9218534  r7 0000010c
    r8 e5bfd464  r9 00000000  sl ffe412d4  fp e5bea004
    ip 0000000d  sp ffe411e0  lr e64fe957  pc e65011c0  cpsr 600f0010

backtrace:
    #00 pc 0004a1c0  /system/lib/libc.so (tgkill+12)
    #01 pc 00047953  /system/lib/libc.so (pthread_kill+34)
    #02 pc 0001d955  /system/lib/libc.so (raise+10)
    #03 pc 000194a1  /system/lib/libc.so (__libc_android_abort+34)
    #04 pc 000170e8  /system/lib/libc.so (abort+4)
    #05 pc 0031b5c5  /system/lib/libart.so (_ZN3art7Runtime5AbortEv+252)
    #06 pc 000b4d47  /system/lib/libart.so (_ZN3art10LogMessageD2Ev+866)
    #07 pc 0023a1cd  /system/lib/libart.so (_ZN3art9JavaVMExt8JniAbortEPKcS2_+1584)
    #08 pc 0023a497  /system/lib/libart.so (_ZN3art9JavaVMExt9JniAbortFEPKcS2_z+66)
    #09 pc 00265d89  /system/lib/libart.so (_ZN3art3JNI11GetMethodIDEP7_JNIEnvP7_jclassPKcS6_+524)
    #10 pc 00149131  /data/app/ch.opengis.qfield-1/lib/arm/libQt5Core.so
    #11 pc 0014ae5b  /data/app/ch.opengis.qfield-1/lib/arm/libQt5Core.so
    #12 pc 0014b401  /data/app/ch.opengis.qfield-1/lib/arm/libQt5Core.so (_ZNK17QJNIObjectPrivate11callMethodVIiEET_PKcS3_St9__va_list+56)
    #13 pc 00008ee5  /data/app/ch.opengis.qfield-1/lib/arm/libQt5AndroidExtras.so (_ZNK17QAndroidJniObject10callMethodIiEET_PKcS3_z+24)

@hpethen
Copy link

hpethen commented Jul 12, 2017

I have also experienced this problem, exactly the same as MieWinstrup, but with my Galaxy tab S2, also running Android 7.

@treenerd
Copy link

treenerd commented Jul 14, 2017

Hi Same issue here with:
Nexus 5X and Android 7.1.2;
QGIS 2.18.9 on Fedora 25
export done with QFieldsync 1.0.0
QField version 0.10.0

@jbostoen
Copy link

jbostoen commented Oct 10, 2017

As regular users, what could we do to help solve the camera crash issue?

Tried it on 3 smartphones; it crashes.

  • Huawei Ascend Y II, Android 5.1 Lollipop
  • OnePlus 3, Android 7.1.1 Nougat
  • Moto G4, Android 7.0 Nougat

On a Samsung tablet, it works fine.

@mp-dmsi
Copy link

mp-dmsi commented Mar 8, 2018

Same issue on a Xiaomi MI 5s (Android 7.0 NRD90M)
Here´s the backtrace:


Build fingerprint: 'Xiaomi/capricorn/capricorn:7.0/NRD90M/V9.2.1.0.NAGMIEK:user/release-keys'
Revision: '0'
ABI: 'arm'
pid: 20686, tid: 20686, name: .opengis.qfield >>> ch.opengis.qfield <<<
signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
Abort message: 'art/runtime/java_vm_ext.cc:475] JNI DETECTED ERROR IN APPLICATION: java_class == null'
r0 00000000 r1 000050ce r2 00000006 r3 00000008
r4 e968a590 r5 00000006 r6 e968a538 r7 0000010c
r8 00000000 r9 e696a2fc sl 00000a8e fp e692f8cf
ip 0000000b sp ffd95730 lr e70e82c7 pc e70eab48 cpsr 200f0010

backtrace:
#00 pc 00049b48 /system/lib/libc.so (tgkill+12)
#1 pc 000472c3 /system/lib/libc.so (pthread_kill+34)
#2 pc 0001d565 /system/lib/libc.so (raise+10)
#3 pc 000190b1 /system/lib/libc.so (__libc_android_abort+34)
#4 pc 00017114 /system/lib/libc.so (abort+4)
#5 pc 003184f9 /system/lib/libart.so (_ZN3art7Runtime5AbortEv+252)
#6 pc 000b4b91 /system/lib/libart.so (_ZN3art10LogMessageD2Ev+864)
#7 pc 002380f5 /system/lib/libart.so (ZN3art9JavaVMExt8JniAbortEPKcS2+1664)
#8 pc 0023835b /system/lib/libart.so (_ZN3art9JavaVMExt9JniAbortFEPKcS2_z+66)
#9 pc 00263781 /system/lib/libart.so (ZN3art3JNI11GetMethodIDEP7_JNIEnvP7_jclassPKcS6+520)
#10 pc 001506bd /data/app/ch.opengis.qfield-1/lib/arm/libQt5Core.so
#11 pc 001523e7 /data/app/ch.opengis.qfield-1/lib/arm/libQt5Core.so
#12 pc 0015298d /data/app/ch.opengis.qfield-1/lib/arm/libQt5Core.so (_ZNK17QJNIObjectPrivate11callMethodVIiEET_PKcS3_St9__va_list+56)
#13 pc 00008f11 /data/app/ch.opengis.qfield-1/lib/arm/libQt5AndroidExtras.so (_ZNK17QAndroidJniObject10callMethodIiEET_PKcS3_z+24)

Hope it helps

@m-kuhn
Copy link
Member

m-kuhn commented Mar 8, 2018

for adventurous people.
we'll be happy to receive feedback on this apk, if it resolves the issue.
please only comment on if it crashes, we are fully aware, that it's not beautiful currently ;)

@jbostoen
Copy link

jbostoen commented Mar 9, 2018

It's different. On my smartphone, the picture is in the wrong orientation. Also, I don't see a 'take photo' button or whatever you want to call it. Just a picture.

@gnerred
Copy link
Author

gnerred commented Mar 9, 2018

I tried this version on a Galaxy S6 with Android 7 and when I take a picture :

  • the image is not oriented properly
  • there is no button to take the picture...

image

@m-kuhn
Copy link
Member

m-kuhn commented Mar 9, 2018

Sorry, forgot some context.
The device needs to be in portrait position and the buttons are well hidden (as said before, it's not yet nice to use).
We're also aware of the wrong picture orientation, that will be fixed in a final version.

Cam

@jbostoen
Copy link

jbostoen commented Mar 9, 2018

  • buttons were completely invisible for me
  • taking picture - doesn't crash :D
  • trying to press where you have the X, this doesn't seem to do much except for remving the photo and allowing you to take another one ?

@m-kuhn
Copy link
Member

m-kuhn commented Mar 9, 2018

taking picture - doesn't crash :D

🎉

@mrciftci
Copy link

Qfield closes because it can not create the folder (DCIM) when the picture is taken. How the problem can be solved.

@m-kuhn
Copy link
Member

m-kuhn commented Mar 13, 2018

because it can not create the folder (DCIM) when the picture is taken

do you have an error message that indicates this? which path is your project stored in?

@mp-dmsi
Copy link

mp-dmsi commented Mar 15, 2018

Tested this version on an ASUS P01T (Android 6.0.1) that previously crashed when taking picture and guess what?...no crash

@signedav
Copy link
Member

signedav commented Mar 26, 2018

#238 <- should be solved here.

@mrciftci Do you have this problem still with the latest version? I cannot reproduce it on my device. Thanks for your help!

@signedav signedav added this to the QField 1.0 milestone Mar 26, 2018
@signedav signedav changed the title Galaxy S8 with Android 7 Galaxy S8 with Android 7 - Photo crash Mar 26, 2018
@m-kuhn m-kuhn closed this as completed Mar 26, 2018
@VxTedxV
Copy link

VxTedxV commented Apr 11, 2018

Experienced same initial issue with the following config :
Samsung Galaxy XCover4 Android 7.0
QField 0.10.12
"use native camera function" checked
(when unchecked, works fine but bothered by the lack of parameters to take photos like no zooming for example -> do I have to open a request about that ?)

No bug with the same project on Samsung Galaxy XCover3 Android 6.0 QField 0.10.9

@signedav
Copy link
Member

Hi @VxTedxV Thanks. The native camera is the one that crashed and still crashes on some device. We disabled it per default.

There's not yet an open request for the zooming feature in the QField-Camera. But I agree that it would be good to have that. What are other things that could be needed in your opinion?

@VxTedxV
Copy link

VxTedxV commented Apr 11, 2018

With native camera I had access to different native tools :

  • image format (4:3, 16:9, 1:1...) with different width/height (more or less weight)
  • timer (countdown before taking picture)
  • geolocalisation EXIF tag on/off
  • zoom with fingers
  • flash on/off/auto
  • mode "pro" to adjust ISO/luminosity/WB/spot or matrice mesure and more...
  • panorama mode
  • ...
    That's a lot of features that can be useful outside ! But I understand that would be too much to develop. We both know the best answer would be to find what could make work native camera with any config !

@m-kuhn
Copy link
Member

m-kuhn commented Apr 12, 2018

Yes, that's why we originally implemented the native camera. I am confident that we can also get the native camera working again. We recently did some tests with promising results. We would need around 4 days to work on that, if it's important enough for someone to sponsor this, we will be more than happy to reintroduce it.

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

No branches or pull requests