According to a report in Android Police, Android 11, the next version of the world’s most popular mobile operating system, will prevent apps from using third-party camera software to take photos. Instead, the phone’s default built-in camera app will have to be used.

When taking photos, current versions of Android allow apps to display a pop-up camera picker from which the user can select their preferred camera app. However, this option has been removed in Android 11. 

This means users who installed popular camera apps such as VSCO, Adobe Lightroom or A Better Camera, will have to revert to their phone’s built-in camera software when taking photos or video from within another app. Users will still be free to use any camera app they wish by launching it directly. Only the camera picker option is affected.

The new restriction exists to prevent apps from grabbing your location without permission. Even if an app has been denied access to your location data, it’s still possible to circumvent this restriction when using third-party camera apps.

The problem arises because camera apps typically embed location data within their image files, and without the new restriction there’s no way to prevent this information from being returned to the calling app along with the photo. 

While I can understand Google’s reasoning here, the current solution feels like an unnecessary inconvenience that doesn’t completely solve the problem. Disabling the camera picker doesn’t prevent images, complete with embedded location data, from being uploaded from the gallery instead.

Anyone updating to a new version of Android will surely be surprised and frustrated to find such a convenient feature removed, so I hope a more elegant solution can be found sooner rather than later. A simple way for advanced users to re-enable the camera picker would probably do just fine.

https://www.forbes.com/sites/paulmonckton/2020/08/22/google-android-11-camera-picker-privacy

https://www.androidpolice.com/2020/08/20/android-11-camera-apps-chooser


#Google #camera #gcam #Android #Android11

Signature Spoofing for Android 11
Guide by bluede-v Will

First of all Flash your ROM and Magisk (you need to download the latest version to get Magisk working on Android 11)

Click on Build number (7x) to enable Developer Options

After that enable ADB-Debugging and Root-ADB-Debugging in your ROM in case of LineageOS go to Setting -> System -> Developer Options

So Lets go this is the more complicated part. but also really easy if you done it once.

I'm using Debian Linux but it should be possible on every OS. In Windows use the Linux Subsystem.

You need to have ADB installed on your System tho.

ADB link: https://adbdownload.com

First of all you need to download this 2 Files:
https://gitlab.com/oF2pks/haystack/-/blob/11-attempt/spoof_AVDapi30.zip.ONLY'MAGISK&ANDROID-STUDIO

https://github.com/microg/GmsCore/files/5652857/microG_AVDx86api30_magiskMaRViN.zip

Rename "spoof\_AVDapi30.zip.ONLY'MAGISK&ANDROID-STUDIO" to "spoof\_AVDapi30.zip"

Next Download this zip: https://gitlab.com/oF2pks/haystack/-/archive/11-attempt/haystack-11-attempt.zip

Also download this jar file: https://github.com/DexPatcher/dexpatcher-tool/releases/download/v1.8.0-beta1/dexpatcher-1.8.0-beta1.jar

So now unzip the haystack-11-attempt.zip and put the dexpatcher.jar file into to Folder.

This part I use Bash shell in Linux.
Bash:
adb pull /system/framework/services.jar

java -jar dexpatcher-1.8.0-beta1.jar -a 11 -M -v -d -o ./ services.jar 11-hook-services.jar.dex 11core-services.jar.dex
(After that Command you should have 4 files all named classes*.dex)
Bash:
mkdir repack

zip -j repack/services.jar classes*.dex
After that you should have a new services.jar in your repack Folder.

Now You need to open the spoof\_AVDapi30.zip go in /system/framework/ and delete the old services.jar and put your own file in. that's in your repack Folder.

Don't ruin the zip-format of the file tho because otherwise Magisk will cry while install.

After that put your spoof-AVDapi30.zip and your microG\_AVDx86api30\_magiskMaRViN.zip on your Phone and Flash via Magisk.

Reboot and you hopefully have Signature spoofig working. If you run in any Problems check out the GitHub Links here. there will be comments that maybe will help.

https://forum.xda-developers.com/t/signature-spoofing-on-unsuported-android-11-r-roms.4214143/


#sigspoof #signature #spoofing #android11 #a11 #r