Camera Library and Compatibility on Market

stefanoa

Active Member

Licensed User

Longtime User

• Jan 25, 2012

• #2

some help?

 

Upvote 0

vb1992

Well-Known Member

Licensed User

Longtime User

• Jan 25, 2012

• #3

Which camera library did you add?

There is two,

B4a library

and

ACL - Advanced Camera Library

 

Upvote 0

stefanoa

Active Member

Licensed User

Longtime User

• Jan 25, 2012

• #4

with B4A...

now i'm trying with ACL - Advanced Camera Library....

Authorization:
com.android.vending.CHECK_LICENSE, android.permission.READ_PHONE_STATE, android.permission.WRITE_EXTERNAL_STORAGE, android.permission.SEND_SMS, android.permission.CALL_PHONE, android.permission.READ_CONTACTS, android.permission.VIBRATE, android.permission.INTERNET, android.permission.CAMERA, android.permission.RECORD_AUDIO, android.permission.FLASHLIGHT, android.permission.RECORD_VIDEO, android.permission.WRITE_SECURE_SETTINGS, android.permission.BLUETOOTH, android.permission.BLUETOOTH_ADMIN

Functions:
android.hardware.camera, android.hardware.telephony, android.hardware.microphone, android.hardware.camera.autofocus, android.hardware.touchscreen


compatibility is changed when I've added "camera" library in project.....

 

Last edited: Jan 25, 2012

Upvote 0

stefanoa

Active Member

Licensed User

Longtime User

• Jan 25, 2012

• #5

I removed the camera library from project and now the application is back-compatible...

may be autofocus function the problem??

 

Upvote 0

vb1992

Well-Known Member

Licensed User

Longtime User

• Jan 25, 2012

• #6

might be the problem..

Does b4a library also add it

"android.hardware.camera.autofocus"

 

Upvote 0

stefanoa

Active Member

Licensed User

Longtime User

• Jan 25, 2012

• #7

There is a way to exclude autofocus module from library?

 

Upvote 0

Erel

B4X founder

Staff member

Licensed User

Longtime User

• Jan 26, 2012

• #8

Libraries only declared permissions, not features. You can see the list of permissions required by ACL library here: Basic4android - ACL

The autofocus is added automatically based on one of these permissions. You will need to find which one.

You can choose Project - Do not write manifest file and then manually remove the permission from the manifest file. Once you find it, I will show you how to remove it with the manifest editor.

 

Upvote 0

stefanoa

Active Member

Licensed User

Longtime User

• Jan 26, 2012

• #9

ok thanks... i try..

 

Upvote 0

D

DKnowles

Member

Licensed User

Longtime User

• Apr 27, 2012

• #10

Adding in camera lib adds android.hardware.camera.autofocus

Hi Erel

I have a similar problem to the rest of this discussion, if I add the ACL or Camera Libs to my application then permissions in the manifest are interpreted by market and not only add the camera (which we need) but also the autofocus which we don't.

Is their anyway to get around this, or do I have to release a special no camera version for the engineers (60 of them) that have the samsung mini phones that can't get the current version as it is filtered from google play.

David

 

Upvote 0

Erel

B4X founder

Staff member

Licensed User

Longtime User

• Apr 27, 2012

• #11

This is how the market works. Your only option is to remove the problematic permission.

 

Upvote 0

NeoTechni

Well-Known Member

Licensed User

Longtime User

• Jul 1, 2012

• #12

How do you do that?

I'd like to use the camera lib, but not if it excludes people who dont have the hardware

 

Upvote 0

Erel

B4X founder

Staff member

Licensed User

Longtime User

• Jul 2, 2012

• #13

You will not be able to use the camera with this permission.

 

Upvote 0