[TAMA][AOSP11] Google Camera doesn't work with latest OEMv5 #695
Comments
|
After the fix in the new OEMv5 we catched the next bug on our way to gcam happiness: |
|
Akari only has two sensors, so only cameraId 0 and 1 are valid. |
|
Here it is |
|
Thank you. |
|
Ok. I'll try to find some info how to change these id's (if problem here) in decompiled app. Thanks anyway. |
|
Maybe the GCAM you tried is modified for 3 camers (2 on the back) and we need a specific gcam port, @jevgenp ? |
|
@MartinX3 No idea, I'm just regular user, |
|
I tried few more apps that uses raw for capturing and processing (PhotonCam, GelioSoft Camera2), but they also crashes. |
|
@sraase Do you think that problem is in the OEM part or in the kernel? :) TL;DR: Full Log Section: Edit: |
|
@MartinX3 I think after camera crash in first app it became inaccessible for another. I'll upload now correct ones logs. |
|
|
@jevgenp |
This usually happens after an error when switching between apps. Many apps do not handle this well and forget to close the camera device, blocking it for other apps even when sent to the background. Please make sure to always stop camera apps completely before starting a new one. The logs above seem truncated. Try to run "adb logcat -c -G128m" before creating the log. To check platform behaviour, we need the CamX/CHI output. |
|
@sraase am I allowed to share the CamX/CHI debugging instructions you gave me via email? :) |
|
Better not. |
|
Okidoki, then I look the next time I can flash SODP on my phone and create the logs. :) |
|
If still needed (don't know is that or not): |
|
Dear @sraase here is the special log I tested it with OpenGapps Pico and this GCam |
|
I don't get this application...
... it probes for all cameras (bad style, you can ask the system), then ignored the main camera (don't know any reason from the log), and then it fails trying to get the characteristics of a camera which it has already proven does not exist. edit: The log you shared does not contain any platform information either, so no CamX/CHI stuff. |
|
So it's google camera problem then? And any of apps that using raw? |
|
@sraase That's weird, I enabled the entire logging stuff. @jevgenp I don't know if on Android 9 a gcam 8.1 (with this camera id hack) will work I try to get a gcam version without this weird camera id logic hack after speaking with some gcam developers. |
|
@MartinX3 I was talking about version that worked on A9 - Arnova's 1.6/2.2 (or San1ty 9.3/9.4). |
|
@jevgenp according to their readme |
|
@MartinX3 I know, but in this case the same version that worked on A9 (6.2.030) runs on A11, but when you press Capture button - processing message appears in notification area and doesn't disappear until you exit application. |
|
@jevgenp Ah I thought you get the same crash on starting the app. Edit: I think I found the app in the recommended section at 6.2/6.3 |
|
@MartinX3 https://www.celsoazevedo.com/files/android/google-camera/f/changelog593/ There is a newest version (that doesn't have buffer fix in settings and viewfinder freezes) that at least starts, but you need fast press settings on startup and change setting "Level Camera2 API" to "JPEG level Full" under "Setting up the mod" to avoid crash: |
|
@sraase I was able to gather a log and receive a loop of errors. https://f.celsoazevedo.com/file/cfiles/gcm1/Gcam_6.2.030_Advanced_V2.2.190716.1800-Final.apk Or this |
|
Are you using a stock Open Devices build, or did you change it in any way? |
|
I just compiled AOSP 11 and use OEMv5 on my Xperia XZ2 |
|
I built AOSP 11 using OEMv5 on Xperia XZ2, installed the APK you linked to and received the following error:
|
|
@sraase do you have GAPPS installed? GAPPS are needing a fullwipe, otherwise problems occur.
Sometimes if I use the hardware buttons to enter the bootloader, I just get a black screen using |
|
Does the same issue happen with the front camera? If yes, then it is not a driver issue. |
|
I'm far from programming, but you want to say that all of these apps that working with raw on a bunch of devices without problems doesn't work on sony and it is an apps issue? Sounds strange. Added: https://drive.google.com/file/d/1SCiRWItXovHaCfHxHjdH3piFr5bjRnMW/view?usp=sharing |
|
No, this is not what I want to say. The drivers are one part of the camera system. If a problem happens for both the front and back cameras, then the drivers are unlikely to be at fault (different drivers). Thanks for the APK. Issue looks similar to #544 but caused by the app requesting RAW16 format. |
|
Maybe some more info needed? As I see Martin didn't answer your question about front camera :) And few questions off topic but related to camera: |
|
I just need some free time because of job, studies and a dataloss (ssd damage, but i have an older backup and was able to recover data from the failed ssd) On the front camera the gcam did freeze too. And i need to analyse why i can't record and send videos in telegram anynore since I use SODP (wrong video codec it says), but that's stuff for a new ticket. |
Currently not needed. I was able to reproduce the problem, but did not look into it yet.
The ISO values shown are very likely wrong.
Please clarify your question. |
Ah ok, but in this case calculated exposure value is correct?
Me bad, talked about shutter speed. What about vignetting - darkening of image corners when compared to the center. |
|
The actual exposure time (lineCount) and ISO (gain values) are shown in logcat.
Camera output on AOSP will have increased noise compared to Xperia, especially in darkness. This is known and cannot be fixed. About the vignetting, please remove /odm/lib64/camera/com.sony.eeprom.blakiston.so (this will disable LSC) and see if the situation improves. Restart your device after removing. |
Seems yes, thanks!
Noted. And what about manual SS control? |
To early I made conclusion... |
|
Just tried august release with OEMv6, and now I'm unable to take raw even with SnapCamera HDR (that worked with previous build and OEMv5). |
|
Not sure what's going on. The HAL appears to open the camera correctly, then Gcam (APK linked above) throws |
|
Are you talking about 6.2.030 version? |
|
Gcam_6.2.030_Advanced_V2.2.190716.1800-Final.apk |
|
Vignetting is caused by actual lens optics so RAW should always show it. Software can remove/hide it, of course, so JPEG may not show any vignetting. |
|
Do you need any new log from latest r43+oemv7? Because situation didn't change. Gapps installed. Crashes on startup: Starts but not taking a photo (needs buffer fix to be enabled in advanced settings): Viewfinder freezes in photo modes (Photo, Portrait, Night), not taking a photo: All apps here: https://drive.google.com/drive/folders/1EbpnzCUlEHxWCSnmvt8S8kawPTmeeOM-?usp=sharing |
|
Discontinued Android version |
Platform: TAMA
Device: XZ2 Compact
Kernel version: 4.14
Android version: 11 r36 (from actual sources at this moment)
Software binaries version: OEM v5
Previously working on
None (Worked only on A9)
Description
Google Cameras crashes on start (list of tried versions on screenshot), except that one worked on AOSP A9 (6.2.030).
This version starts, but viewfinder freezes (helps enabling of buffer fix in settings), and doesn't react on a capture button.
Symptoms
Crashes on start/Doesn't react on a capture button.
How to reproduce
Install any of versions from screenshot.
Additional context
gcam.txt
The text was updated successfully, but these errors were encountered: