Device comes with Android 9.0.
I've unlocked it, flashed Android 8.0, put TWRP recovery and gained root.
But during testing i've discovered the fact that camera lost it's autofocus ability in stock application.
Tried OpenCamera with Camera API 1/2 with the same result.
Any ideas?
so you didn't read about what happens when you unlock bootloader?
Related
Hi, miui 9 global, android 7. samsung sensor.
i just magisk rooted my phone and edited build.prop to emable camera2api , so i could try google camera.. thats great, but now the stock camera no longer works in hdr or panorama modes. enable hdr mode and it says "cant connect to camera" and crashes.. panorama mode just immediately crashes. panorama mode on google camera is terrible, so i will really miss this feature.
i hoped that installing the extra features on the stock camera might help. i added those with a magisk module. new functions appear but same issue.
in frustration, i reverted build.prop back to original state..
camera still broken!!
ive rebooted and cleared cache in twrp.
help?
robinlawrie said:
Hi, miui 9 global, android 7. samsung sensor.
i just magisk rooted my phone and edited build.prop to emable camera2api , so i could try google camera.. thats great, but now the stock camera no longer works in hdr or panorama modes. enable hdr mode and it says "cant connect to camera" and crashes.. panorama mode just immediately crashes. panorama mode on google camera is terrible, so i will really miss this feature.
i hoped that installing the extra features on the stock camera might help. i added those with a magisk module. new functions appear but same issue.
in frustration, i reverted build.prop back to original state..
camera still broken!!
ive rebooted and cleared cache in twrp.
help?
Click to expand...
Click to collapse
Same issue on my redmi note 4
robinlawrie said:
Hi, miui 9 global, android 7. samsung sensor.
i just magisk rooted my phone and edited build.prop to emable camera2api , so i could try google camera.. thats great, but now the stock camera no longer works in hdr or panorama modes. enable hdr mode and it says "cant connect to camera" and crashes.. panorama mode just immediately crashes. panorama mode on google camera is terrible, so i will really miss this feature.
i hoped that installing the extra features on the stock camera might help. i added those with a magisk module. new functions appear but same issue.
in frustration, i reverted build.prop back to original state..
camera still broken!!
ive rebooted and cleared cache in twrp.
help?
Click to expand...
Click to collapse
suvi-lover said:
Same issue on my redmi note 4
Click to expand...
Click to collapse
You all need to re install miui rom to fix it. I'm having sony sensor, and it fixed it.
Hello,
I have a leagoo m8 pro and recently I had tried to flash a new custom rom on it and it didn't work. My phone was soft bricked and I brought it to a store and it repaired it by flashing an official android os on it but since then my selfie camera has stopped working
I tried downloading other camera apps to switch to selfie mode but it still didn't work, I also factory resetted my phone but it was still not working
I was thinking that maybe it was the os or else it's a hardware problem..please I really need your help!!:crying:
I want to try out android 10 on my mi a3. I've even downloaded it. But i don't know how to install it. Some one help me please.
Android 10 for mia3 haven't out yat. you need to use custom rom in order to use it.
You just need twrp but if i were you stay on pie for now. Two unwanted changes concerning fingerprint and camera pro mode arising in android 10. It makes me wanna downgrade but cant anymore
amnher said:
You just need twrp but if i were you stay on pie for now. Two unwanted changes concerning fingerprint and camera pro mode arising in android 10. It makes me wanna downgrade but cant anymore
Click to expand...
Click to collapse
No issues with camera or fingerprint here on my device.
Try clearing data for camera or something. Have you tried anything at all with your camera app to get it working?
I did a factory reset after updating to 10. Set fingerprints, installed all apps, fhen restarted! That restart broke my fingerprint completely. Its completely non functional now. Only works once after restarting to open the phone, then its not there at all.
garylawwd said:
No issues with camera or fingerprint here on my device.
Try clearing data for camera or something. Have you tried anything at all with your camera app to get it working?
Click to expand...
Click to collapse
My camera is working same goes with fingerprint. But it is not featured the way it was on pie.
No 32s on pro mode
Fingerprint requires a tap for fod to display.
The rollout was pulled due to bugs. I had downloaded a copy and booted into recover using the power and volume up buttons. Once I saw the open Android I pressed power and tapped volume up again to get to options menu. I hit the apply update from SD option. It started to update but kept failing shortly after it started update. Kind of glad it didn't since there's a lot of bugs. Let's see how long before they start pushing update again SMH.
Hello.
After installing XperiFix, my camera is still not working. I am uploading the logs below. I noticed that the Magick 17.1 version from XperiFix doesn't work, and when I try to update or upload from a new one, I see a black screen after booting the phone, but when I press and hold power button I see a window to a turn off device and sometimes top bar appears (time, battery, etc.). I tried to install Magisk v25.2.
I also tried to upload the stock camera (https://gitlab.com/xperiance/camera/-/releases) but without the higher version of Magick I can't do it.
I have FW .205, before that I tried .270 but it didn't work, bootloop when starting the phone.
In the morning I will install the update from OTA to .235 and try to upload XperiFix or install the .145 version and see what happens next.
I tried Open Camera and made logs, but they didn't save, but the camera still doesn't work ;/
EDIT: I flashed FW .145 but didn't help.
I flashed Android 9 FW 47.2.A.11.228 to test, but I cant flashed XperiFix, because in TWRP write "read-only partition detected" and I see that I flashed Magisk nothing happens, it's as if it didn't install, I don't know why but I didn't have a problem with it before... In TWRP this options "read-only" is unchecked.
Translated with www.DeepL.com/Translator (free version)
Is it possible to fix this somehow, anyone know anything? I've read a lot of forum posts about it but nothing works, I'll just add that after installing some AOSP(probably Android 11) the front camera works but very poorly and after taking a picture you can see green artifacts on it.
Hey, do you know how to fix camera app on sony xperia xz1 not capturin?
My xperia xz1 is android 8, so I decided to flash an android 9 firmware using newflasher. After flashing the firmware, my camera has a problem that can't capture. Anyone can tell how to fix this issue? Plz help me. Sorry for bad English
Your browser is not able to display this video.
This is what happen on my xperia xz1. Camera is not capturing and not save a picture, recording also object tracking not working. This is happen after flash from android 8 version to android 9. Anybody know to fix this? Please help me. before flash the new android version, i didn't do any backup and my xperia is locked bootader. I'm using newflasher to flash the android 9 firmware.
NeoInfo, a tool for the Galaxy S3 Neo
AboutNeoInfo is a tool for the Samsung Galaxy S3 Neo which aim to figure out the bootloader, modem and camera sensor of the device. Those information are the most important prerequisites for modern Custom ROMs. Additionally it displays some more or less important information such as the current CSC, front cam type and more.
Features
Works without root access
Very obvious but yes, it displays your bootloader and modem versions
Get the best possible accurate information about the camera
Capable to detect the current battery/charger driver
Dark mode
Requirements
At least Android 4.4
A Galaxy S3 Neo (Duos)
Download/InstallationYou can get the latest APK from here. Install the App as normal APK.
Changelog
Code:
v1.0:
- initial release
Camera PermissionNeoInfo needs on Android 4.4 access to the Camera to get two specific rear camera characteristics in order to check if the rear camera does actually work. On Android 5.0 or newer this permission is not required nor asked.
Sourcehttps://github.com/prototype74/NeoInfo
F.A.Q.
Q: Does it need Root?
A: No, didn't I mention it in first post?
Q: The color of my Booloader/Modem version is orange. What does that mean?
A: Your Booloader/Modem is from 2015 release and might be outdated. If you face RIL issues or any other issue that might be related to your Booloader/Modem, consider upgrading if possible.
Q: The color of my Booloader/Modem version is red. That's not good right?
A: Yes, you have one of the oldest Booloader/Modem (from 2014) which will definitely cause RIL issues or bootloops at setup screen in modern Custom ROMs. You should upgrade to the latest Booloader/Modem if possible.
Q: What does SLSI_S5K4H5YB/SONY_IMX175 mean?
A: SLSI_S5K4H5YB = Samsung camera sensor | SONY_IMX175 = Sony camera sensor
Q: In camera section, all my camera types are okay but the camera status shows "Not working". What should I do?
A: That means you either have a different camera sensor or (if you're sure its the correct sensor) your camera hardware might be broken. If the first one is the case, flash a different Firmware/ROM that supports your sensor. For example, if your camera types show "SLSI_S5K4H5YB", flash a Sony firmware.
Q: The back camera type note shows "Your back camera kernel type does not match the others but it should not affect the camera functionality". Should I be worried?
A: No, as it says in the text "..but it should not affect the camera functionality", because it actually doesn't affect the camera functionality at all.
Q: The back camera type note shows "Your back camera firmware type does not match the vendor type" but my camera works?
A: If you camera works then good for you! This case however is unusual but happens if you flashed a stock firmware before which was meant for a different camera sensor. So the text in Vendor back camera type is your true camera sensor in this case.
Q: The back camera type note shows "Your back camera firmware type does not match the vendor type" and the camera status shows "Not working"! Help!
A: If your camera is actually not working then you need to research how the ROM you flashed does manage that:
Does the ROM offer a camera patch? If so, flash it to fix the camera.
Does the ROM offer an option to select the camera sensor (e.g. SEPerience-ROM)? Then you selected the wrong sensor. Reflashing the ROM and selecting the other sensor should fix it.
Does the ROM offer different builds (e.g. LineageOS)? Then you flashed the wrong build. Flash the correct build to fix the camera.
Tip: check what the Firmware back camera type does show. For example, if it shows "SLSI_S5K4H5YB" but your Vendor back camera type shows "SONY_IMX175" then you have a Samsung sensor.
Q: The Vendor camera type shows "SLSI_S5K4H5YB && SONY_IMX175", does that mean I got both sensors!?
A: No, but there are two reasons why that could happen:
You flashed a camera patch fix that didn't remove the unused camera blobs
Or, the ROM developer does include both camera blobs in their builds
In this case it's not easy to figure out which camera sensor you actually have. Thus, Back camera status will also display "Unable to check your back camera type".
Q: Can I install the App on a different Android device than S3 Neo?
A: Yes, you can install the App on any Android device but the features the App offers will be limited as it was desinged for the Galaxy S3 Neo.