Page 1 of 3

camera not accessible from Android 5.0

Posted: Sun Jan 24, 2016 11:05 am
by EJLD

Hi There, I test 3 devices :
. MotoG upgraded from Android 4.4 - 5.0;
. Note3 upgraded fr Android 4.2 - 5.0
. Alcatel brand new 5.0.2
all 3 presents a bug with the camera.
the MotoG is the least with a functioning camera but the pic format loading to app UI is not same as before (i don't know what it is exactly), anyway, the cropper I built doesn't work anymore. image is too wide and blocked in the frame.
as for the 2 others (note3 and brand new alcatel), the devices throw a "camera not accessible" error.
Hv you guys experience such things on your side ?
thk you,
Eric


camera not accessible from Android 5.0

Posted: Sun Jan 24, 2016 12:46 pm
by Alena Prykhodko

Hello,

Can you provide more details, is it JQM or AngularJS project?
Screenshots and exact steps to reproduce this problem will help a lot.


camera not accessible from Android 5.0

Posted: Sun Jan 24, 2016 9:34 pm
by EJLD

Hi Alena, it is a JQ app
as for screen shot, not easy to take, the error is thrown on the black screen for few sec. then back to appUI

as for the cropper, you can go to :
1/ startScreen
2/ press button "the vault"
3/ footer = "add" button
4/ that should lead you to camera
5/ once pic loaded it is shown in a cropper
6/ on touch it was prior to OS upgrade possible to move the pic around on touch
still the scaling works
would you be able to find out how to customize the input pic format to get back to what it was prior to OS upgrade ?

my app is on share with support.
also passed them the login info by email.
pls install and experience
thks
Eric


camera not accessible from Android 5.0

Posted: Sun Jan 24, 2016 9:39 pm
by Illya Stepanov

Hi Eric -- Please remind us the name of your app.


camera not accessible from Android 5.0

Posted: Sun Jan 24, 2016 9:40 pm
by EJLD

collect4good


camera not accessible from Android 5.0

Posted: Tue Jan 26, 2016 5:26 pm
by Serhii Kulibaba

Hello,

Unfortunately this is something outside the scope of standard Appery.io platform support. You may consider purchasing Advisory Pack to get more in-depth help on this question. Here is more information about Advisory Pack (http://appery.io/services/#Advisory_Pack).


camera not accessible from Android 5.0

Posted: Tue Jan 26, 2016 10:13 pm
by EJLD

hi Sergiy, I understand and am ready to buy a advisory pack to get help on that issue. however, can you guys confirm that my 2 questions will be solved within a 5-hr pack:
a/ how to fix the incoming picture format issue to get it as before ?
b/ it seems that the touchStart, touchMove, touchEnd are not responsive any longer ?
I am fine to purchase a 5-hr pack but wouldn't like to have to buy another 5-hr :)
pls tell me
Eric


camera not accessible from Android 5.0

Posted: Wed Jan 27, 2016 12:41 pm
by Alena Prykhodko

Hi,

Hard to say, theoretically this is possible to solve within 5 hours.

We were able to replicate this issue on Android 5.0, and as you use external library you might be interested to check whether it's compatible with Android 5.0?


camera not accessible from Android 5.0

Posted: Wed Jan 27, 2016 11:01 pm
by EJLD

Hi Alena,

fine I take as within 5hrs :)

a/ could you be clearer on what you could replicate on your side ?
. is it the camera that does work ? or not consistently ?
. is it about the cropper:
. image to wide ?
. touch not responding ?

what would you be able to help fixing ?

b/ one more question, this function camera + code were used to work perfect under 4.2 and 4.4, isn't it Appery's job to keep itself uptodate in order to work same way on higher version like 5.0 onward ?

again, i'm very much happy with Appery features and service, and don't mind to give you some money to save time, however, it seems strange to me that this type of problem would not fall under Appery's scope of responsability. may I have your position again ?

to summarize, could you answer point a/ and b/,
thk you
Eric


camera not accessible from Android 5.0

Posted: Thu Jan 28, 2016 9:57 pm
by EJLD

Alena, may I ask you to come back to me on the 2 points above that we move forward ?
thk you,
Eric