Database Info

[Q] Oxygen ROM 2.3.2- Saga (HTC Desire S), camera not working

Hi,
I tried to install Oxygen ROM 2.3.2 - Saga for HTC Desire S - http://forum.xda-developers.com/showthread.php?t=1235864 - but my camera is not working properly.
The camera is supposed to show you a preview of what the camera is pointing at, updated real time - basically you are looking through the camera when you are pointing at things - but in my case the view gets stuck on first thing that the camera is pointing at when I turn it on... sometimes it updates the view after couple of seconds but it is so fitful that the camera is not usable.
When I try to switch to camcorder there is the same problem and when I try to make some video it is fitful... and when I watch the video it seems to be stuck for couple of seconds, than it moves a little and again it's stuck for another five seconds (so it's not just the preview, the real video produced by the camera is affected ass well).
I tried full wipe, I tried that ROM with or without Tiamat kernel - no change, I erased SD card, I erased everything and when I try the camera on clean new install of that ROM - it is not working.
I restored original factory build that comes with HTC Desire S and camera worked perfectly - but I would really love to use that Oxygen ROM - it's great and except for the camera it works perfectly... so much better then the original HTC thing.
I noticed that in the thread related to that ROM http://forum.xda-developers.com/showthread.php?t=1235864 there are messages where people mention that camera is working OK for them - please, do you have any idea what might be the problem? Any help would be really appreciated.
Thank you,
Jan

Thread moved to the proper section.

[Q] Camera and lamp won't open

Hi everyone, I've look everywhere and I'm kind of desperate now
So, I've had my nexus 5 since it came out here in Europe, never had an unsolvable issue (thanks to the internet), but right now I'm stuck
MY PROBLEM :
One day (just like this, I don't remember doing anything special with my phone), the camera completely stopped working, along with the lamp.
DETAILS ABOUT THE PROBLEM (The situation right now) :
1. Camera doesn't show up in the application drawers
2. It DOES show up in Settings/Applications, and in "My applications" tab from Google Play, but I cannot open it in any way. When I could, however, it would just crash away.
3. I am also unable to access the stock lamp from anywhere (quick settings, etc.)
THE INITIAL SITUATION AND THE EVOLUTION OF THE PROBLEM :
1. I was running CM12.1 (nightlies) on my Nexus 5, and I beieve it occured after an update, but I don't believe it really has much to do with it. When I tried to open the camera, it would show me "unable to get a link with the camera" (translation may not be exact) and the system lamp had disappeared
2. I tried to downgrade the phone, to an earlier nightly, but it didn't fix it.
3. I've donne every kind of wipes : Data, Dalvik, Cache, even Internal Storage
4. After a full Internal Storage Wipe, I reflashed fresh Marshmallow images from the official website, unrooted, reflashed stock recovery, relocked the bootloader and used the system factory reset again on my phone.
5. After this, the problem changed a little bit. The lamp is still impossible to find, but however this time the camera is too. What I mean is, on CM, it used to show up and crash, now I can't find it in the app drawer (See DETAILS ABOUT THE PROBLEM)
I think that's all, so yeah, this one is kind of a challenge.
If the solution is software... Well i really dont know what I could try else; if it's hardware, I'm not afraid to open up my phone. (however I'm a complete noob)
One last thing, I've contacted Google, but the phone they sent me back was in such a bad state that I'm keeping mine (or getting them to send me an other), because the power button was really used, and the lowest part of the screen really "white" (brighter than the rest, my guess was it had fallen)
Thank you very much !

Hi, looks like we have the same problem. Unfortunately I have no solution for you, either. I have ordered a new rear camera from ebay that should show up here end of January. I'll let you know if that fixed the problem.

As you can see from my recent post, I am also having the same problem. I have also order a replacement rear camera from ebay and I fitted it. It worked for one day and then it also stopped working. I am not sure whether it is worth repeating this experiment or I'd just be wasting money on replacement cameras. So annoying, because, apart from the camera (and the torch), the rest of the phone functionalities are still perfectly fine.

Has anyone tried to use a different camera or torch app?
Sent from my Nexus 5

ShapesBlue said:
Has anyone tried to use a different camera or torch app?
Sent from my Nexus 5
Click to expand...
Click to collapse
Of course.

maurimauri29 said:
Of course.
Click to expand...
Click to collapse
That's odd then. It seems like you've done nearly everything that should of been done. I'm at a loss for words here
Sent from my Nexus 5

CM13 Z5P E6853 Beta -- Updated NegaSpork

This is a no-frills thread.
Okay here it is.
cm_satsuki-Nega_Spork.zip
For dsds testing: cm_satsuki_dsds_test_boot.img Note: you will see the Sony Bootanimation instead of CM13, this is intentional. Also detection may take a minute or two. Provide clear reports.
For dsds model owners, flash rom clean, then in recovery reboot to bootloader and flash this test boot.img with fastboot
Code:
fastboot flash boot cm_satsuki_dsds_test_boot.img
fastboot reboot
NegaSpork
Working:
Sim [single]
Storage
NFC
Audio record fixed
The rest is the same.
What doesn't work:
Since the camera is still not "fixed" we will just say it doesn't work, deal with it.
Next on my todo list is fmradio
DSDS support is still being worked out by the project members. [see test boot image above]
NOTE: OpenGapps may bug out quickpanel/pulldown menu. This may be related to version used.
I experienced this with pico and nano. [see note below]
Click to expand...
Click to collapse
Thanks @KbaB.BroS for testing :good:
Everything from before works, cell, mobile data, nfc, etc.
Internet speeds are good.
It feels snappier than before, so smooth
The pulldown bar works, I can interact with the toggles without any force closes. If somebody complains about their devices, let them know to use OpenGAPPS. I use the mini version
Click to expand...
Click to collapse
Cyanogenmod Source
Thanks to/for
@CTXz Sources and convincing me to get a Z5P instead of another Sammy device.
Sony Kitakami Platform Developer Organization
@zacharias.maladroit For answering questions, many questions. :silly: [ still have more... xD ]
Those of you without a sense of humor, go away.
Okay current features i'm working on and stuff that works/doesn't work
UVC support enabled in kernel. probably need to build rom-side support still. libuvc avutils etc.
- This is for plugging in camera devices in conjuction with apps like LegitDashcam.
USB Gadget functionality as per pelya's work ,
- pelya/android-keyboard-gadget Use in conjuction with the include USB Keyboard app to utilize your phone as a keyboard/mousepad.
I am working my kernel source here toward net-huntery goodness.
The rest you tell me, and you tell me properly. Messages like
"waahhh my whatchamhoozit is all floompy"
are not acceptable.
This is not a random discussion thread either. Idle chatter belongs in general.
This is also NOT a discussion thread for Xposed,Viper, etc..
Thank you.
m

Notes and Updates
NOTE
I have been running this build for two days now and so far , meh it's alright.
Audio [mic] and Camera issues are definitely annoying.
SELinux is COMPLETELY disabled on this build. If You want security go back to stock.
SELinux enforcing is the goal though.
I strongly recommend using a "traditional" root os SuperSU over systemless-root.
Reasons:
Opengapps requires a factory-reset or fresh install to set up correctly!
Privacy Guard based root sucks. It forgets alot of permissions granted.
Use BETA-SuperSU-v2.52 , I wil attach below as it seems hard to find by conventional means.
Would have posted earlier but needed a smoke break *>cough<* :silly:

Updates and Notes
Reserved

Attached UPDATE-SuperSU-v2.46.zip for another option ,
since that worked the best for me in the past.

Thanks for the input. I get error: 7 to install the .zip file
any solution?

Rubensss said:
Thanks for the input. I get error: 7 to install the .zip file
any solution?
Click to expand...
Click to collapse
You need to use the recovery @moonbutt74 compiled from his other thread.
Sent from my Z5 Premium using XDA Labs

KbaB.BroS said:
You need to use the recovery @moonbutt74 compiled from his other thread.
Sent from my Z5 Premium using XDA Labs
Click to expand...
Click to collapse
Thanks , I have already installed.

@moonbutt74
Would be easier to keep the ROM as daily and test if it supported the dual sim version phones too
Apart from that, some of my observations during a small period of usage :
Pardon me if these are already mentioned.
Screen brightness doesn't reach full capacity
Speaker volume is low I think
For me, I felt the display had some slight glitches. Enabled GPU rendering in developer settings and felt it got better , can't guarantee on this though
Had to revert to stock based since sim functionality for me wasn't available ( I have a dual sim phone)

Ashray_Vk
Okay good deal, umm let me try compiling a seperate kernel package.
Yep brightness is currently HORRIBLE
I didn't notice any glitches display-wise, do you actually mean lag in some screen transitions?
I only tested with radioball and raging thunder.
The build i just tested out had full WOW, HOW THE HELL DO I TURN THIS DOWN BRIGHTNESS. :silly:
So either atm i get crappy brightness as max level which is like 75% of stock.
Or i get the nice stock brightness but the slider breaks/doesn't work.
The speaker volume is limited to where it actually should be. Use a mediaplayer that has an option for software decoding, that is a 100% [double] boost. It's not the idea to bomb out the speakers by default, each user can find their own tweak.
m
On the "daily build" thing, my upload time is horrible, so i will not be pushing out excessive/pointless builds. when i have something else fixed, then i will upload another build. Currently i'm boxing with the brightness issue and getting the mic working for audio recording.

moonbutt74 said:
Ashray_Vk
Okay good deal, umm let me try compiling a seperate kernel package.
Yep brightness is currently HORRIBLE
I didn't notice any glitches display-wise, do you actually mean lag in some screen transitions?
I only tested with radioball and raging thunder.
The build i just tested out had full WOW, HOW THE HELL DO I TURN THIS DOWN BRIGHTNESS. :silly:
So either atm i get crappy brightness as max level which is like 75% of stock.
Or i get the nice stock brightness but the slider breaks/doesn't work.
The speaker volume is limited to where it actually should be. Use a mediaplayer that has an option for software decoding, that is a 100% [double] boost. It's not the idea to bomb out the speakers by default, each user can find their own tweak.
m
On the "daily build" thing, my upload time is horrible, so i will not be pushing out excessive/pointless builds. when i have something else fixed, then i will upload another build. Currently i'm boxing with the brightness issue and getting the mic working for audio recording.
Click to expand...
Click to collapse
By screen glitches, I meant that I saw a few glitches when I scrolled down menus ( like even settings app).
Might be just my sleepy eyes too, lol. And in the beginning, everything was feeling laggy, till I enabled those GPU options in the developer settings and turned the screen off and turned it back on.
Don't rely on this data though, I hope someone else verifies this thing before you take it up as an issue .
-Ash

Ashray_Vk said:
By screen glitches, I meant that I saw a few glitches when I scrolled down menus ( like even settings app).
Might be just my sleepy eyes too, lol. And in the beginning, everything was feeling laggy, till I enabled those GPU options in the developer settings and turned the screen off and turned it back on.
Don't rely on this data though, I hope someone else verifies this thing before you take it up as an issue .
-Ash
Click to expand...
Click to collapse
No problem I'm just looking for clarification, are you talking about lag or screen tearing?

moonbutt74 said:
No problem I'm just looking for clarification, are you talking about lag or screen tearing?
Click to expand...
Click to collapse
There was lag in the beginning, no doubt. Lag was there since the boot animation itself.
Yes! Screen tearing is the term i was searching for. I felt like I saw minor issues of screen tearing along with the lag. ( especially when I scrolled down the settings )
I'm so sorry if I am not able to make things clear.

Nice. My question is does it work well with xposed? Other rom gives me random soft reboot randomly
Sent from my E6853 using XDA-Developers mobile app

Killastyle said:
Nice. My question is does it work well with xposed? Other rom gives me random soft reboot randomly
Sent from my E6853 using XDA-Developers mobile app
Click to expand...
Click to collapse
K,
right now we are working on an Alpha build, self evident in thread title. Xposed being superfluous/unecessary is not being discussed in this thread. Of course later on in the release/beta level thread it will most likely be covered.
@KbaB.BroS
On the good side got brightness and auto brightness sorted.
@Ashray_Vk , give me a bit on the dsds kernel, from what I'm understanding SS an DS were supposed to have been combined, so I am running a fresh build after resync, which on my comp will take a day :silly: adn probably not as long as the actual upload
:laugh:
m

moonbutt74 said:
K,
right now we are working on an Alpha build, self evident in thread title. Xposed being superfluous/unecessary is not being discussed in this thread. Of course later on in the release/beta level thread it will most likely be covered.
@KbaB.BroS
On the good side got brightness and auto brightness sorted.
@Ashray_Vk , give me a bit on the dsds kernel, from what I'm understanding SS an DS were supposed to have been combined, so I am running a fresh build after resync, which on my comp will take a day :silly: adn probably not as long as the actual upload
:laugh:
m
Click to expand...
Click to collapse
Normally, if I'd flash a stock based ROM which was meant for single sim, one sim would work in the dual sim models but the memory card would be not detected . sadly, that wasn't the case with cm though. Not even a single sim gets detected.

Ashray_Vk said:
Normally, if I'd flash a stock based ROM which was meant for single sim, one sim would work in the dual sim models but the memory card would be not detected . sadly, that wasn't the case with cm though. Not even a single sim gets detected.
Click to expand...
Click to collapse
you tried enabling only single SIM mode in Sony's (or other) "Stock" ROM and then flashing this ROM ?
Then at least one SIM might work - unless of course the Z5 devices handle things entirely differently

zacharias.maladroit said:
you tried enabling only single SIM mode in Sony's (or other) "Stock" ROM and then flashing this ROM ?
Then at least one SIM might work - unless of course the Z5 devices handle things entirely differently
Click to expand...
Click to collapse
Um, actually, was running rom aur and then had disabled one sim ( just because i didnt want to use that sim) and then had flashed this.
Unfortunately, not even a single sim worked in this.

Killastyle said:
Nice. My question is does it work well with xposed? Other rom gives me random soft reboot randomly
Sent from my E6853 using XDA-Developers mobile app
Click to expand...
Click to collapse
No problem with XPosed for some time here

Updated Build
CM13 Z5P E6853 Somehwere in Alpha -- Updated DragonLady
see OP , OH! and READ IT. grrrrrrr
Please verify communications are functioning, sim detection, in-call mic working etc.
Is your model SS or DS? Please state model number.
Brightnes and auto brightness should be fixed.
External storage fixed
Re-introduced kcal support in kernel
Included system apps [free, and free versions] - as we are testing , some creature comforts.
Adaway.apk
HKB.apk <--- hacker's keyboard
HKNDCTRU.apk <--- hacker's keyboard cyrillic/russian support
KernelAuditor.apk
NetworkDiscovery.apk <--- fairly useful network discovery app, find it on fdroid
NovaLauncher.apk
OpenCamera.apk
PicuriRam.apk
Quickpic.apk
Rebooter.apk
Superuser.apk <--- enable developer options and root access via that way first, then run supersu and update.
Terminal.apk < jackpal terminal
TotalCommander.apk
USB-Keyboard.apk
USBKB.apk < this one and the one above are the same app, i dun goofed.
Wifitoggle.apk
i am working a vanilla cm13 as well as my own custom build in the same turn, the custom utility in sbin is ccrypt, if you want to know how to use it, pm me and i'll give you a break down. do not use it to encrypt a block device !! single files only, and do not use a generated key, use a memorizable alpha-numeric password, else leave it alone.
m
@zacharias.maladroit WHAT HAPPENED TO PERRY !?!?!?!? :crying:

@moonbutt74
I'm sort of wiping the slate clean in several areas of my life - and that (unfortunately) was part of it :angel:

Qiku 360 N5s ROOT/TWRP/Custom ROM

So I bought the BLUE Qiku 360 N5s and found how to Root it from GizChina.it BUT for some reason whenever I flash the root developer rom (TO ROOT PHONE) that they provided, my phones camera gets messed up. Now heres the weird thing, I bought my girlfriend the same phone but in BLACK and followed there instructions and her camera works fine. Only my phone for some unknown reason doesn't work the the freaking developer rom. Its frustrating because I want to get rid of all the CHINESE bloatware with the custom rom they provided (which works) BUT I need TWRP to flash it and I need to ROOT my phone before I can install TWRP. Some please send me some guidance cause I'm stressed and desperate!!!! THANK YOU

Verified Rootable
Hi there,
I recently bought the same phone, (Black version), and was finally able to root it after a month of struggling. Other than the camera not functioning, exactly what problems are you experiencing? You were able to fully root your GFs black version? Unlocked bootloader confirmed? Let me know. I'll give you whatever help I can.

Zyraelindir said:
Hi there,
I recently bought the same phone, (Black version), and was finally able to root it after a month of struggling. Other than the camera not functioning, exactly what problems are you experiencing? You were able to fully root your GFs black version? Unlocked bootloader confirmed? Let me know. I'll give you whatever help I can.
Click to expand...
Click to collapse
Can you please tell me what you used to root it? Thats the only problem, after flashing the devrom the rear camera stops working and the front camera works but is grainy and all the functions for the camera stops working (flash beauty etc), I'm able to press on them but it doesn't do anything. The camera is still able to take a picture though. When I press the button to change it to the rear camera it freezes and stops working. I've tried downloading a 3rd party camera app but it doesn''t fix it eithier. Camera is still grainy on the app and the camera flip function doesn't work as well. Also I can't login to snapchat with this phone. I think its because the phone has a built in screen recorder so snapchat won't let me login. Can you help me with that as well? Thank you!!!

raymondchiu said:
all the functions for the camera stops working (flash beauty etc), I'm able to press on them but it doesn't do anything. The camera is still able to take a picture though. When I press the button to change it to the rear camera it freezes and stops working. I've tried downloading a 3rd party camera app but it doesn''t fix it eithier. Camera is still grainy on the app and the camera flip function doesn't work as well.
Click to expand...
Click to collapse
I unlocked the bootloader via fastboot after flashing Giz China's dev-rom. The only real roadblock to rooting it is having the developer software to bypass 360's proprietary bootloader restrictions. Once the dev-rom is flashed, you should be able to utilize all of the adb and fastboot resources as you would for a non-Chinese phone.
Now that you've described your camera problems a bit more, I have to say that it sounds like a compatibility issue. I can't be certain without testing it, but the dev-rom has a lot less bells and whistles than the stock rom, so it's quite possible that the dev-rom is missing the necessary files for running all of the extra camera filters. The dev-rom is just a temporary fix to allow you to alter the bootloader, and isn't ideal for daily use.
I recommend you try reflashing it so that you can get root access, or if you already have root access then simply flash a custom rom to replace it, and then see if your camera is still having the same issues. Don't forget that you'll need to flash SuperSU or Magisk or whatever SU app you're familiar with after flashing the rom. Also, if you try reflashing the dev-rom with 360's software, I recommend doing so via a Windows7 installation. I initially tried it via multiple Windows 10 machines and it failed horribly in all of them. It worked in a matter of minutes in each Windows7 machine though. Go figure.
GizChina also has a custom rom for the 360 n5s, not sure if you're aware of it or not. You can find it here:
ttps://rom.gizchina.it/360-n5s/
You might need to utilize Google translate if you can't read Italian .
Let me know if that helps or if you have more questions.

Yeah oddly it doesn't work with the blue phones. Only the black phone worked. I have 3 N5s's 2 are blue and 1 is black. The black one is completely fine and the two blue phones camera stops working after flashing the DevRom. I don't think theres anything I can do.

raymondchiu said:
Yeah oddly it doesn't work with the blue phones. Only the black phone worked. I have 3 N5s's 2 are blue and 1 is black. The black one is completely fine and the two blue phones camera stops working after flashing the DevRom. I don't think theres anything I can do.
Click to expand...
Click to collapse
Have you tried flashing the custom ROM I suggested? There's no harm in trying. Just backup your files with TWRP, flash the custom ROM, if it works great, if not you can restore the Dev-rom and your old files.

Zyraelindir said:
Have you tried flashing the custom ROM I suggested? There's no harm in trying. Just backup your files with TWRP, flash the custom ROM, if it works great, if not you can restore the Dev-rom and your old files.
Click to expand...
Click to collapse
The DevRom works and roots my phone but messes up my camera on the blue phone. The custom rom also works but it doesn't fix the problem I have with the camera... Keep in mind that I did this with a black N5s and it worked perfectly fine. But when I try it with 2 different blue N5s's they both encounter the problem with the camera. Only the black phone works properly. I have also flashed the blue phones ROM back to the manufacturers and it fixed the problem that the DevRom created with the cameras.

raymondchiu said:
The DevRom works and roots my phone but messes up my camera on the blue phone. The custom rom also works but it doesn't fix the problem I have with the camera... Keep in mind that I did this with a black N5s and it worked perfectly fine. But when I try it with 2 different blue N5s's they both encounter the problem with the camera. Only the black phone works properly. I have also flashed the blue phones ROM back to the manufacturers and it fixed the problem that the DevRom created with the cameras.
Click to expand...
Click to collapse
If that's true and the custom rom has the exact same issues running the camera filters then the only thing it could be is a lack of support built into the roms for those camera functions, or those functions are dependent on an app that has been removed from the new roms, but exists in the stock rom.
In order for either of those to be true though, it means that your black phone and your blue phone should have different camera functions, because the roms aren't changing, the only difference is your phone model (blue or black), so either you've accidentally erased something needed, or there is a series of support files that you could try installing back into the blue phone.
I wouldn't know which files though lol, you'd have to do some research. I doubt you will find much guidance on it by searching online. Your best bet would be to compare the file differences between your black phone and your blue phone to see which camera app files are on the blue one but not the black one (on the stock rom) and then try reinstalling all of those files and their support trees once you flash the dev-rom/custom-rom.
That is what I would do next if it was my phone.

Okay what about the snapchat problem where it doesn't let you login because of the built in screen recording feature in the phone?

Zyraelindir said:
If that's true and the custom rom has the exact same issues running the camera filters then the only thing it could be is a lack of support built into the roms for those camera functions, or those functions are dependent on an app that has been removed from the new roms, but exists in the stock rom.
In order for either of those to be true though, it means that your black phone and your blue phone should have different camera functions, because the roms aren't changing, the only difference is your phone model (blue or black), so either you've accidentally erased something needed, or there is a series of support files that you could try installing back into the blue phone.
I wouldn't know which files though lol, you'd have to do some research. I doubt you will find much guidance on it by searching online. Your best bet would be to compare the file differences between your black phone and your blue phone to see which camera app files are on the blue one but not the black one (on the stock rom) and then try reinstalling all of those files and their support trees once you flash the dev-rom/custom-rom.
That is what I would do next if it was my phone.
Click to expand...
Click to collapse
I've also noticed that the black phones kernal version is 3.10.84 while the blue phones kernal version is 3.10.84-perf (also the snapchat problem on both blue and black n5s)

[HELP] Camera won't work after Android 11 Update + Possible Cause?

I was previously on android 10 i believe just a few days ago and my camera was working just fine. The other day I got a notification telling me to update to android 11...so i did and didn't think anything of it.
I use my camera alot for photography so this is very important to me, google camera or any app that uses your camera no longer works.
Example 1: As soon as I launch google camera it just crashes.
Example 2: Snapchat, instagram, or any other apps just give me the error like "snapchat was unable to open the camera".
I know a lot of people are getting this same issue because if you go to the play store and go to google camera app and sort reviews by recent tons of users are experiencing this.
I have two theories on what's causing this.
Theory 1: I've been using an app called "lens cap - disable camera" for over a year now just for peace of mind, I guess it used some sort of device administrator priveledges to block all apps from accessing the camera.
I believe I had the lens cap on (camera disabled) before and when I started updating to android 11 and I think that may have caused a weird break in permissions that somehow has me permanently unable to use the camera anymore.
The reason why this is something I suspect is because according to the developer of that app "android 11 removed most of the functionality of device administrator in favor of enterprise work profiles" (not sure what this means) but I think for some reason this caused it to get permanently blocked.
I have the github page for the apps source code if anyone can possibly look at it and see what exactly the app was changing in the first place because then maybe that way someone can possibly come up with a way to fix mine and many others cameras.
Edit: Apparently I'm not allowed to post links on a new account but the program can be found on github called LensCap by a user named percula
Theory 2: Android 11 just broke the camera by itself and the lens cap app maybe has nothing to do with it.
Ive already done all the obvious troubleshooting like resetting permission/preferences, restarting in safe mode, uninstalling and reinstalling camera apps + clearing cache and storage etc
Sorry of my formatting or grammar is sloppy at all I've had a long day and I just really want to get this working again

If none of your troubleshooting fixed the issue, I think the next option is to do a full reset (using recovery - not the selection in the settings menu). Another alternative is to flash the full factory image and allow it to factory reset the phone as well.
This will mean loosing all your app data and pictures, etc, so back up before you do it. But I am confident it will fix your issue, regardless of the actual cause.

sic0048 said:
If none of your troubleshooting fixed the issue, I think the next option is to do a full reset (using recovery - not the selection in the settings menu). Another alternative is to flash the full factory image and allow it to factory reset the phone as well.
This will mean loosing all your app data and pictures, etc, so back up before you do it. But I am confident it will fix your issue, regardless of the actual cause.
Click to expand...
Click to collapse
So would you recommend doing "recovery" or "flashing"? Also how do I get to this "recovery" thing,
originally I was thinking about trying to downgrade back to android 10 but from what I remember the steps looked really confusing ;w;
Apparently a lot of people are getting this issue but in the end they said they had to try and RMA it, so I hope recovering or flashing fixes it, kinda worried this update actually permabricked something in my phone.
sorry if its a dumb question I don't know much about phone stuffs
thank you for your response.

There's definitely an issue with android 11 and the camera.
I didnt have any issues on the beta 2, 2.5, or 3. But upon installing the public, official version.. the camera fails. I've tried 2 factory resets. I've installed the ota.zip via adb sideload. And then did a complete format and install of the full image.
Here's what issue I'm having, personally:
When I open the gcam app, it freezes for about 15 seconds. Then I get the "not responding" screen. If I hit wait, about 15 second later, I get the camera on and it's images are on the screen. But it's so laggy that it's not even functional. For instance, If I try to zoom in, it's about 20 seconds until it actually does. Same for taking a picture. I have sent bug reports to them.
I'm gonna downgrade to a better/smoother version. Probably a custom android 10.
Like others, I use it24/7. The pixel 3a is an incredible camera. I hope it's fixed soon.

I don't even know where to post, I came here looking for a solution, but looks like there may be none, other than going back to Android 10 and never ever installing any kind of update on this phone.
I bought the 3a because of the camera, and because I was taking crappy quality pix of my toddler with my previous phone. A9 worked great, A10 worked great. Camera almost instant, switching from Camera, to Video to Portrait, no problem. Message that A11 is available, so hey why not, it's not IOS. Wrong. It totally screwed me, the camera takes from 1-8 seconds to start, to switch between modes. If I double click power when locked camera start (with delays), I then turn it off using power button, when I unlock the phone the camera app is open.
Sometimes when I open it a second time it stays on the setting I chose before (i.e. portrait, or video - not camera default - this would be a nice toggle in the options though - say if you always shoot portrait).
Portrait mode has reversed the picture order (left/right - blur/no blur).
I have missed many shots of my little one since I've upgraded because of this garbage update.
I have a lot of apps that aren't the "latest" version, that work as I need them to; can someone suggest an app that will let me back up my exact versions, then reinstall them after? I have no idea if such a backup/restore app could also save the app data; I don't have root
Also, if someone could point me to a post which shows the way to switch back to Android 10, step by step, I would appreciate it. If I need to reload all the apps and info, I might as well go back to a known working version.
I have also noticed that some other apps are acting funky now. A once rock stable and reliable phone, these days I just want to throw it straight down at the pavement with all my strength... often...

I have the same issue. Have you resolved it yet. My camera app is working but other app using camera gives error.i had also lenscap and problem arised after update to android 11