I've used Messager, Textra and Pulse and all the pics come through to other people blurred than originals. I didn't seem to have this issue on my Nexus 6p so not quite sure what's going on. Has anyone experienced this?
I'm experiencing the same thing on my US version Matter 10 Pro. Gifs are also pixelating once sent. My Mate 9 did not have this issue.
Just did a little experiment.
I sent a picture to my wife using my Mate 10 Pro. Then, I put my sim card into my Pixel 2 XL and sent the same picture. Then, I put the sim card into my HP Elite X3 and sent the same picture. In my wife's text thread, all three pictures showed up clear compared to each other once they were clicked on. But, just looking at them in the thread without clicking on them, the picture from my Mate 10 Pro appears to be about half the size. I'm ok with that, since after the pictures were clicked on, they appeared normal.
I did the same experiment again with an animated gif. The gifs from the Pixel 2 XL and the Elite X3 showed up exactly as they looked when I sent them. However, the gif from my Mate 10 Pro was completely pixelated and appeared tiny.
So, the question is: If AT&T allows my P2XL and Elite X3 to send pictures and gifs normally, why does my Mate 10 Pro struggle sending the same media types? This is not a carrier thing, in my case. It is strictly a Mate 10 Pro thing.
I'm using the A09 Mate 10 Pro on AT&T with the Android Messages app as my default messaging app.
I also us the Android Messages app on my P2XL.
I have found the best and stable GCam for our beloved Max Pro M1.
It's the BCG's V6.2
https://www.celsoazevedo.com/files/android/google-camera/f/changelog498/
Once you install the GCam, set the base model of Front camera to Nexus 6P.
I've seen that all the gcam ports just make my face pink-ish inspite of the good lightning. I've also found a fix to it!
Go into settings (gcam) and go further into Advanced under Photo section.
Over there you'll find a saturation section for adjusting saturation.
Set the Highlight Saturation to 0.8 & Shadow Saturation to 1.2 and then you're good to go!
This gcam also does not have any grey shutter or shutter lag in Portrait mode. Everything works fine including Night Sight.
Slo-mo works?
Mr.Ak said:
Slo-mo works?
Click to expand...
Click to collapse
Not on mine
Hello after install it works and all, But I cant seem to find the shortcut icon?
"MGC_6.2.024_BSG-based_TlnNeun.apk" is the best Gcam port I've tried on this phone in terms of features and reliability.
Here's my review:
I tested "MGC_6.2.024_BSG-based_TlnNeun.apk" on Android 9. Although it has some problems, so far this is the best Gcam port I've used on this phone.
Shooting modes:
1. Camera (default)
2. Portrait
3. Panorama
4. Lens Blur
5. Video
6. Night Sight
7. Photo Sphere
8. Google Lens
The modes I care about (1-6) all work.
Here are the problems I've discovered so far:
1. Hardware details
When photos are produced by this app, sometimes the information embedded in the photo files incorrectly identifies my phone as a Huawei phone, and incorrectly identifies my camera as "Huawei ASUS_X00TD." (This is an Asus phone; it has nothing to do with Huawei.)
Strangely, sometimes the photos produced by the app will instead say that the camera used to shoot them is "asus ASUS_X00TD," which is correct. (X00TD is the generic model code for this kind of phone by Asus, and my global 4 GB variant of the phone specifically has model code X00TDB.)
To me, these inconsistent details are irrelevant.
2. Location (Coordinates) Details
By default, Location Saving was enabled by the app. However, this data did not actually save to any of the photos produced by the app. It was only after manually disabling Location within the app and then re-enabling it that the app eventually saved this data to photos.
I do care about having Location details saved to photos. Although the feature is buggy and does not work as it should by default, it thankfully can work reliably once you fiddle with it.
3. App crashes
I discovered two ways to inadvertently crash the app.
First, turning off HDR causes the app to crash with a "Camera keeps stopping error."
Fortunately, once you re-start the app, HDR is disabled and you don't see that error anymore. Presumably HDR is actually disabled until manually re-enabled by the user.
The second way I crashed the app was by going into Settings and then clicking on Help. This produced the same fatal error as disabling HDR. The app thankfully works fine once you re-start it, so the fatal crash will not recur unless you repeat your actions.
Hardware: Asus Zenfone Max Pro M1, model X00TDB (the 4 GB global variant of the phone)
Operating System: Android 9 (AospExtended-v6.6-X00TD-20190819-1346-OFFICIAL.zip)
Max Pro M1 User said:
"MGC_6.2.024_BSG-based_TlnNeun.apk" is the best Gcam port I've tried on this phone in terms of features and reliability.
Here's my review:
I tested "MGC_6.2.024_BSG-based_TlnNeun.apk" on Android 9. Although it has some problems, so far this is the best Gcam port I've used on this phone.
Shooting modes:
1. Camera (default)
2. Portrait
3. Panorama
4. Lens Blur
5. Video
6. Night Sight
7. Photo Sphere
8. Google Lens
The modes I care about (1-6) all work.
Here are the problems I've discovered so far:
1. Hardware details
When photos are produced by this app, sometimes the information embedded in the photo files incorrectly identifies my phone as a Huawei phone, and incorrectly identifies my camera as "Huawei ASUS_X00TD." (This is an Asus phone; it has nothing to do with Huawei.)
Strangely, sometimes the photos produced by the app will instead say that the camera used to shoot them is "asus ASUS_X00TD," which is correct. (X00TD is the generic model code for this kind of phone by Asus, and my global 4 GB variant of the phone specifically has model code X00TDB.)
To me, these inconsistent details are irrelevant.
2. Location (Coordinates) Details
By default, Location Saving was enabled by the app. However, this data did not actually save to any of the photos produced by the app. It was only after manually disabling Location within the app and then re-enabling it that the app eventually saved this data to photos.
I do care about having Location details saved to photos. Although the feature is buggy and does not work as it should by default, it thankfully can work reliably once you fiddle with it.
3. App crashes
I discovered two ways to inadvertently crash the app.
First, turning off HDR causes the app to crash with a "Camera keeps stopping error."
Fortunately, once you re-start the app, HDR is disabled and you don't see that error anymore. Presumably HDR is actually disabled until manually re-enabled by the user.
The second way I crashed the app was by going into Settings and then clicking on Help. This produced the same fatal error as disabling HDR. The app thankfully works fine once you re-start it, so the fatal crash will not recur unless you repeat your actions.
Hardware: Asus Zenfone Max Pro M1, model X00TDB (the 4 GB global variant of the phone)
Operating System: Android 9 (AospExtended-v6.6-X00TD-20190819-1346-OFFICIAL.zip)
Click to expand...
Click to collapse
Max Pro M1 User said:
"MGC_6.2.024_BSG-based_TlnNeun.apk" is the best Gcam port I've tried on this phone in terms of features and reliability.
Here's my review:
I tested "MGC_6.2.024_BSG-based_TlnNeun.apk" on Android 9. Although it has some problems, so far this is the best Gcam port I've used on this phone.
Shooting modes:
1. Camera (default)
2. Portrait
3. Panorama
4. Lens Blur
5. Video
6. Night Sight
7. Photo Sphere
8. Google Lens
The modes I care about (1-6) all work.
Here are the problems I've discovered so far:
1. Hardware details
When photos are produced by this app, sometimes the information embedded in the photo files incorrectly identifies my phone as a Huawei phone, and incorrectly identifies my camera as "Huawei ASUS_X00TD." (This is an Asus phone; it has nothing to do with Huawei.)
Strangely, sometimes the photos produced by the app will instead say that the camera used to shoot them is "asus ASUS_X00TD," which is correct. (X00TD is the generic model code for this kind of phone by Asus, and my global 4 GB variant of the phone specifically has model code X00TDB.)
To me, these inconsistent details are irrelevant.
2. Location (Coordinates) Details
By default, Location Saving was enabled by the app. However, this data did not actually save to any of the photos produced by the app. It was only after manually disabling Location within the app and then re-enabling it that the app eventually saved this data to photos.
I do care about having Location details saved to photos. Although the feature is buggy and does not work as it should by default, it thankfully can work reliably once you fiddle with it.
3. App crashes
I discovered two ways to inadvertently crash the app.
First, turning off HDR causes the app to crash with a "Camera keeps stopping error."
Fortunately, once you re-start the app, HDR is disabled and you don't see that error anymore. Presumably HDR is actually disabled until manually re-enabled by the user.
The second way I crashed the app was by going into Settings and then clicking on Help. This produced the same fatal error as disabling HDR. The app thankfully works fine once you re-start it, so the fatal crash will not recur unless you repeat your actions.
Hardware: Asus Zenfone Max Pro M1, model X00TDB (the 4 GB global variant of the phone)
Operating System: Android 9 (AospExtended-v6.6-X00TD-20190819-1346-OFFICIAL.zip)
Click to expand...
Click to collapse
But in my asus max m1 pro device it's automatically back and it remains show me black screen only and automatically turn back I also use same device and camera to api isn't enable in my device and I'm also in same version
aryankr_147 said:
But in my asus max m1 pro device it's automatically back and it remains show me black screen only and automatically turn back I also use same device and camera to api isn't enable in my device and I'm also in same version
Click to expand...
Click to collapse
Sorry, your message is not clear. I don't understand you, but it seems like you're having problems using the camera app on your Max Pro M1.
If English is not your first language, maybe try posting your message in your native language, as someone may understand it. Alternatively, maybe someone can translate for you.
I've had varying degrees of success with these Google Camera ports on my Max Pro M1:
trCamera_V1.1_Eugene_Onegin
PMGC_7.2.014_Zoom_V4
MGC_6.2.024_BSG-based_TlnNeun
MGC_7.3.020_Parrot043-v2
Max Pro M1 User said:
Sorry, your message is not clear. I don't understand you, but it seems like you're having problems using the camera app on your Max Pro M1.
If English is not your first language, maybe try posting your message in your native language, as someone may understand it. Alternatively, maybe someone can translate for you.
I've had varying degrees of success with these Google Camera ports on my Max Pro M1:
trCamera_V1.1_Eugene_Onegin
PMGC_7.2.014_Zoom_V4
MGC_6.2.024_BSG-based_TlnNeun
MGC_7.3.020_Parrot043-v2
Click to expand...
Click to collapse
In my device camera to api isn't enabled
So, will this gcam work in my device
I also use asus max m1 pro. But 3/32 gb varrient
If any gcam works then I already used What you said
Suggest me a better gcam That works on this device
aryankr_147 said:
In my device camera to api isn't enabled
So, will this gcam work in my device
I also use asus max m1 pro. But 3/32 gb varrient
If any gcam works then I already used What you said
Suggest me a better gcam That works on this device
Click to expand...
Click to collapse
I don't think any Gcam app will work until you enable Camera 2 API or install a custom ROM.
Why don't you enable Camera 2 API? It's not so difficult to do if you have a computer and have successfully installed the ADB program and the generic USB driver for Android phones.
Hello,
I recently got a mi a3.
Today the stock camera ''keeps stopping'' , I can still use open camera and Google camera redmi note 7 port by BSG. I installed the last update with 5 July security patch yesterday maybe it's linked.
Does anyone have the same problem ?
Does anyone know if we can use the wide angle camera with an other app ?
I don't have that kind of issues on latest security updates...stock camera work fine here...try clearing stock camera data and cache first...
iPusak Gaoq™ said:
I don't have that kind of issues on latest security updates...stock camera work fine here...try clearing stock camera data and cache first...
Click to expand...
Click to collapse
I already tried that :/ Even with safe reboot it doesn't work.
I'm going to factory reset.
I'm having the same issue. Also, the camera is very laggy, whenever I click a photo the camera takes 1 or 2 seconds to respond.
Mi a3 camera stop working problem
I have that problem too.
And finally I found problem.
I wish work for you to.
Go to usage acsses and allow camera app.
If was enable renable agane...
I mean just allow the app usage acsses.
That work to me I hope working for you too
Hi
Check usage acsses and enabling if not enable.
Go app info
Time spent in App
Change in setting
Camera
Allowed
I hope working for you
Hallo.. I have bought today this phone (Mi a3)..
After i power on my phone and did the update i begin to test the phone..
On camera every time i try to record a video it crashes.. After this i have to restart the phone.. if i try to record video again same thing.
I tried hard reset.. google camera.. camera from messenger.. same thing on all cameras.. include selfie camera..
Taking photos is ok with all cameras but videos crashes the camera..
Anyone else with this problem?Hallo.. I have bought today this phone (Mi a3)..
After i power on my phone and did the update i begin to test the phone..
On camera every time i try to record a video it crashes.. After this i have to restart the phone.. if i try to record video again same thing.
I tried hard reset.. google camera.. camera from messenger.. same thing on all cameras.. include selfie camera..
Taking photos is ok with all cameras but videos crashes the camera..
Anyone else with this problem?
Eslovable said:
I have that problem too.
And finally I found problem.
I wish work for you to.
Go to usage acsses and allow camera app.
If was enable renable agane...
I mean just allow the app usage acsses.
That work to me I hope working for you too
Click to expand...
Click to collapse
Yaaaaay It worked perfectly. Tnxxxxx
Just open settings -> search "Usage access" -> tap on the result -> choose "usage access" from list -> allow camera. DONE
(It's suspicious why camera needs usage access tho!!!!)
I'm running Lineage 17.0 (Raphael) on my Mi 9t pro (Redmi K20). Today I was using the selfie camera (pop-up) when I rebooted my phone.
The camera was still stuck up when I rebooted. It didn't contract, and I tried opening the camera and swapping front-to-back a few times, nothing happened. Rebooted again, nothing. New camera app, or even reinstalling the app, nothing. The automatic retraction on drop is disabled for some reason I cannot explain.
Have you got any ideas how to fix this?
Try oiling it.
Serious answer is to go back to stock miui and open the camera app.
Has anyone else had camera problems since the android 12 update. The camera settings menu has disappeared.
Which particular camera setting? I am on 12 but settings are there.
Mine are there but sometimes opening the app has a hiccup and takes a few minutes longer or studders for a split second.
All camera sertings. The entire menu dissapeared. I had to do a factory reset to fix it.
pflatlyne said:
All camera sertings. The entire menu dissapeared. I had to do a factory reset to fix it.
Click to expand...
Click to collapse
Old thread but still actual.
Oppo device here, on Android 11 vanilla phone I only had video settings but no photo size or resolution settings.
I updated to Android 12 (official Oppo update) and now all video and photo settings disappeared!
Now a stupid photo's size is 9Mb and I haven't tried video yet but I know the files will be HUGE thanks to Oppo ignorant developers!
I also checked a friend's phone a Samsung and he also has no settings.
Searching further, people with Samsung phones are complaining that since Android 11 photo and video settings were REMOVED!
I wonder what is wrong with these [email protected] who develop Android???