Related
Friends we can finally use dual camera in any custom rom.
Install using Magisk.
If it does not work at the first attempt it is recommended to return to the stock rom and then install the custom rom.
That way everything will work without problem.
Venezolano desde Argentina.
Hmmm... Portrait mode on rear camera not working... It fc app.. Aosip
Works
I am on RR
adag1 said:
Hmmm... Portrait mode on rear camera not working... It fc app.. Aosip
Click to expand...
Click to collapse
Work on PE and EvolutionX
Portrait mode no work in RR
Force Close
leechgid said:
Portrait mode no work in RR
Force Close
Click to expand...
Click to collapse
Strange. I am on the latest build, with DragonHeart Kernel. All seems to work fine.
Portrait mode no work in Bootleggers 4.2
Force Close
Does this cam crashes frequently? I know cameras have been always the most difficult part o custom roms, I am still on stock only for the camera, other roms I tried (with a mi a1, to be honest) crashed when I need to take a quick picture... Also tried the GCam, it has better quality but it was worse at the end, it broke the whatsapp camera taking green pictures and random crashes were common. I would really like to install RR or any other rom, but the camera is dragging me back.
I wish there would be a debloated stock rom (no GAPS and the few xiaomi extras) just for keeping the camera working normally, but noone has done it (and I am far for been able to )
DARKEASC said:
Does this cam crashes frequently? I know cameras have been always the most difficult part o custom roms, I am still on stock only for the camera, other roms I tried (with a mi a1, to be honest) crashed when I need to take a quick picture... Also tried the GCam, it has better quality but it was worse at the end, it broke the whatsapp camera taking green pictures and random crashes were common. I would really like to install RR or any other rom, but the camera is dragging me back.
I wish there would be a debloated stock rom (no GAPS and the few xiaomi extras) just for keeping the camera working normally, but noone has done it (and I am far for been able to )
Click to expand...
Click to collapse
I get green tinted photos when I zoom in this camera app. Otherwise, I encounter no crashes or other problems.
Fix for the color bug:
Set the HDR mode to "live".
Portrait Mode is absent on AOSiP ROM
Portrait mode does not work on back camera.
Front camera has color bug. But, if hdr turn on or in portrait mode it works fine.
On superior OS
I got bootloop after flash this module in magisk 19.4 on (AEX) AOSP Extended v6.7 Is working only on LineageOS based roms?
lars00 said:
I got bootloop after flash this module in magisk 19.4 on (AEX) AOSP Extended v6.7 Is working only on LineageOS based roms?
Click to expand...
Click to collapse
Miui camera works with almost every custom rom : Superior , crdroid , POSP , RR (I've tested on them )
Portrait mode crashing with back camera is fixable , you'll need some file explorer with root permissions . The problem is with vendor mismatch , and you'll need to make some changes , here is the walkthrough:
How to solve vendor mismatch bug:
Find string ro.vendor.build.fingerprint in the file /vendor/build.prop, copy the value from it and replace this value to ro.build.fingerprint in the file /system/build.prop ,reboot and portrait mode has to be working , it works for me all the time
Unfortunately I don't know where is the problem. After install this module and restart device, then stuck on AEX boot animation. After uninstall module in Magisk Mnanager 4 Recovery boots again normally For me also not working MI A2 camera port in generic Magisk modules, respectively not all functions, no live image filters, crashing etc. Can't it cause the custom Vendor of AEX rom?
Base lineageos.snap camera and GCam 6.2.030 works fine. I use both of them, it is not the conflict in there?
Thank you for your tips...
lars00 said:
Unfortunately I don't know where is the problem. After install this module and restart device, then stuck on AEX boot animation. After uninstall module in Magisk Mnanager 4 Recovery boots again normally For me also not working MI A2 camera port in generic Magisk modules, respectively not all functions, no live image filters, crashing etc. Can't it cause the custom Vendor of AEX rom?
Base lineageos.snap camera and GCam 6.2.030 works fine. I use both of them, it is not the conflict in there?
Thank you for your tips...
Click to expand...
Click to collapse
Try using this magisk module:
https://drive.google.com/file/d/1po2DDLUifIEJe_zMJvpVXuWch8jffZzw/view?usp=drivesdk
This is stock Daisy camera ,uninstall miui camera from magisk ,then install this zip,reboot and try again
nikoman1987 said:
Try using this magisk module:
.......
This is stock Daisy camera ,uninstall miui camera from magisk ,then install this zip,reboot and try again
Click to expand...
Click to collapse
This link doesn't contain any magisk zip module, this is nova launcher backup file(?). I'm using Lawnchair on Aex.
I have all Magisk modules unistalled before flash MiuiCamera.zip of course, but stuck on AEX screen persist.
I have tried more versions of miui camera, but no satisfying success.
nikoman1987 said:
Try using this magisk module:
https://drive.google.com/file/d/1aSX4odE5fAqtl4ImEwRrDxdkWuABbX_J/view?usp=drivesdk
This is stock Daisy camera ,uninstall miui camera from magisk ,then install this zip,reboot and try again
Click to expand...
Click to collapse
wrong link bro
lars00 said:
This link doesn't contain any magisk zip module, this is nova launcher backup file(?). I'm using Lawnchair on Aex.
I have all Magisk modules unistalled before flash MiuiCamera.zip of course, but stuck on AEX screen persist.
I have tried more versions of miui camera, but no satisfying success.
Click to expand...
Click to collapse
Sorry , copied the wrong link , the link is fixed now
can this work on 10 GSI maybe? i would rather not bootloop
[GCAM] Buffer fix by Wyroczen
Hey, I've made buffer fix for LG V35 in a form of Magisk module:
It will fix lagging viewfinder in GCAM both nightsight and normal mode.
Requirements:
Stock android 9 work (may or may not work in others)
Downloads:
Celsoazevedo: https://www.celsoazevedo.com/files/android/p/lg-v35-buffer-fix/
Donation:
If you want, you can support my work by sending me donation
https://www.paypal.me/wyroczen
XDA: DevDB Information
LG V35 TWRP flashable lib fix.
Wyroczen said:
[GCAM] Buffer fix by Wyroczen
Hey, I've made buffer fix for LG V35 in a form of Magisk module:
It will fix lagging viewfinder in GCAM both nightsight and normal mode.
Requirements:
Stock android 9 work (may or may not work in others)
Downloads:
Celsoazevedo: https://www.celsoazevedo.com/files/android/p/lg-v35-buffer-fix/
Donation:
If you want, you can support my work by sending me donation
https://www.paypal.me/wyroczen
XDA: DevDB Information
LG V35 TWRP flashable lib fix.
Click to expand...
Click to collapse
Hello, sorry to ask that silly question...but i want to ask you that which app you are using to edit shared object file(IDA/hex workshop) ?
Bcz i need some help regarding ti edit my phone camera sensor library...
Krypt185 said:
Hello, sorry to ask that silly question...but i want to ask you that which app you are using to edit shared object file(IDA/hex workshop) ?
Bcz i need some help regarding ti edit my phone camera sensor library...
Click to expand...
Click to collapse
IDA and hexworkshop, depends on what I want to do
Wyroczen said:
IDA and hexworkshop, depends on what I want to do
Click to expand...
Click to collapse
how can i get TWRP for lg v35? i can't find it. And have you tested this file on V35?
Hi Wyroczen,
will there by a GCAM apk with this fix ? would be nice to use this on a non-rooted phone.
hi.
you know, when i flash this fix via Magisk, gcam and stock cam dont work, dont open. i need to uninstall that zip to fix it and that two cameras can work fine again.
do you know somethin about it.
thank you
caligulaprobablemente said:
hi.
you know, when i flash this fix via Magisk, gcam and stock cam dont work, dont open. i need to uninstall that zip to fix it and that two cameras can work fine again.
do you know somethin about it.
thank you
Click to expand...
Click to collapse
Hi, how can you flash this fix? unlock bootloader then flash TWRP right? can u guide me please
Hello Wyroczen,
Could you please prepare an APK for non rooted phones?
Also what is the base version for this one, 6.x or 7.x?
I am definitely going to donate if I am finally gonna get a proper gcam on my v35
Hello Thanks for the great fix. Unfortunately it seems to be causing some issues in Android 10. The software fades when opening Gcam (Burial 7.3, Pit 7.3) Opening the normal camera displays "Critical error".
Version: Android 10 (V350N30a)
Model：LM-V350N
Why??? why Xiaomi why...
I've followed a lot of tutorials to flash a camera 2api module enabler this shouldn't be complicated so i'm gonna post what i have been doing to see if someone can help
Bootloader unlocked
In fastboot mode:
fastboot flash recovery twrp.img (am using the latest)
So i flash twrp temporarely just to enable gcam
In twrp i used a lot of modules but none of them work
Some even say that the flash was sucessful but in manual camera compatibilty it knows that the cam2api isn't enabled
If anyone could help it would be amazin
(Miui 11.0.5 Android 9)
My fear is that i can't flash cam2api on pie that would be a shame
Also, i don't want to root the phone that's why i'm not using a build prop editor
Ok so this just got more bizarre i've extracted the build.prop and the changes are there
the value is set to 1!!... but i am still failing any camera 2 api test...
If someone could help me understand this behaviour it would help a lot
Same for me. All camera2api guides I've seen are more or less sophisticated ways of adding lines to /system/build.prop, but that doesn't seem to be enough to enable camera2api and I'm dying to know why.
Whyred, MIUI Global 11.0.3, Android 9, bootloader unlocked. When I pull build.prop to my PC, it contains both "persist.camera.HAL3.enabled=1" and "persist.vendor.camera.HAL3.enabled=1", but camera tests fail and ported gcams just crash.
All ideas welcome.
UPDATE:
temblor55 has made a Magisk patch for this problem, which he posted on 18 september::
https://drive.google.com/file/d/1-3y1CR6nfVhFYf9VpE11FXOmDEQl5VMt/view
Pat57 has confirmed that it works for him.
________________________________________________________________________________________________________
I have a RN8 from 11-2020 board ID 3.29
Instead of the usual Omnivision OV13855 frontcam, there is a new version OV13B10 inside.
This camera sensor is also installed in later Redmi phones
This new version works OK with Miui 11.0.11 -A9, and higher
Custom A11 rom's will problably work also all with this frontcam (I tried CrDroid 7.4 -A11 with succes)
But I can't find a custom A10 rom that can connect to this frontcam.
Always get the message "can not connect to camera"
Because of speed, stability and more development, I prefer a A10 custom rom (Resurrection Remix)
I think it isn't the Xiaomi FW, so maybe it could be the kernel.
I have tried the updated 2021 -A10 roms and A10 kernels without succes.
So problably it is about missing libs inside rom.
Is there a way to find these libs in a A11 custom rom or Miui rom and add them inside A10 rom?
I don't want to deep dig in it, because A11 will be the future solution.
But development on A11 rom's is fast ongoing, so there are bugs which some are irritating.
So if someone could give a direction, I will be thankfull
Elinx said:
I have a RN8 from 11-2020 board ID 3.29
Instead of the usual Omnivision OV13855 frontcam, there is a new version OV13B10 inside.
This camera sensor is also installed in later Redmi phones
This new version works OK with Miui 11.0.11 -A9, and higher
Custom A11 rom's will problably work also all with this frontcam (I tried CrDroid 7.4 -A11 with succes)
But I can't find a custom A10 rom that can connect to this frontcam.
Always get the message "can not connect to camera"
Because of speed, stability and more development, I prefer a A10 custom rom (Resurrection Remix)
I think it isn't the Xiaomi FW, so maybe it could be the kernel.
I have tried the updated 2021 -A10 roms and A10 kernels without succes.
So problably it is about missing libs inside rom.
Is there a way to find these libs in a A11 custom rom or Miui rom and add them inside A10 rom?
I don't want to deep dig in it, because A11 will be the future solution.
But development on A11 rom's is fast ongoing, so there are bugs which some are irritating.
So if someone could give a direction, I will be thankfull
Click to expand...
Click to collapse
I had similar problem, but i don't think it's not from the libs, it's a "persist" thing
restore "persistbak" and flash it (or if you already have a recovery backup of persist just restore it)
loopypalm said:
.... i don't think it's not from the libs, it's a "persist" thing
restore "persistbak" and flash it .....
Click to expand...
Click to collapse
No, I think it has nothing to do with the persist partition.
Because I have flashed several different rom's and kernels and found that only Miui and A11 custom does recognize the selfiecam
If the persist partition was corrupted, this wasn't possible.
Because FW is from Miui, it could be the kernel or rom.
A lot of A10 custom roms are EOL, they are build with the original early hardware drivers/libs
From 11-2020 PCB-ID 3.29 the camsensor is changed and the RN8 was also almost EOL.
In september 2020 the first A11 build came out and at the end of 2020 more and more builds.
So I assume most developers don't even think about updating the kernel or libs on their "old" A10 versions.
Inside the screenshots of the app "Device info HW" you see the 19 supported cams of CrDroid 7.4 and only 17 on RR 8.6.7
Elinx said:
No, I think it has nothing to do with the persist partition.
Because I have flashed several different rom's and kernels and found that only Miui and A11 custom does recognize the selfiecam
If the persist partition was corrupted, this wasn't possible.
Because FW is from Miui, it could be the kernel or rom.
A lot of A10 custom roms are EOL, they are build with the original early hardware drivers/libs
From 11-2020 PCB-ID 3.29 the camsensor is changed and the RN8 was also almost EOL.
In september 2020 the first A11 build came out and at the end of 2020 more and more builds.
So I assume most developers don't even think about updating the kernel or libs on their "old" A10 versions.
Inside the screenshots of the app "Device info HW" you see the 19 supported cams of CrDroid 7.4 and only 17 on RR 8.6.7
Click to expand...
Click to collapse
yes, on paper the problem sounds like it has nothing to do with persist
but as stupid as it sound ,it just worked ! (restoring persist) + latest stable A10 fw
devs didn't update the port because it just worked, and i heard it's a hard thing to mess with ...
loopypalm said:
...... as stupid as it sound ,it just worked ! (restoring persist) + latest stable A10 fw
devs didn't update the port because it just worked, and i heard it's a hard thing to mess with ...
Click to expand...
Click to collapse
For who has worked this? Have you one or more links to it?
I had read already the guides for restoring, but because all sensors does work I'm a bit holding back.
I like to read first some experiences with this, before I touch the persist partition.
Elinx said:
For who has worked this? Have you one or more links to it?
I had read already the guides for restoring, but because all sensors does work I'm a bit holding back.
I like to read first some experiences with this, before I touch the persist partition.
Click to expand...
Click to collapse
link to what ?
i had similar problem on my 128 variant and asked help in RR TG group (group is deleted by rodrigo) rr official dev is always offline, so rr users moved to milestone by zhan (which is miles better)
"all sensor work fine except camera"
nobody have idea and no dev support, so i try lot of things
and flashing latest A10 fw and restore persistbak + clean flash of RRos + 16 kernel are the last things i did and it worked
if you have orangfox do a backup of persist ,so if anything goes wrong you can just restore it
loopypalm said:
link to what ?
i had similar problem on my 128 variant and asked help in RR TG group (group is deleted by rodrigo) rr official dev is always offline, so rr users moved to milestone by zhan (which is miles better)
"all sensor work fine except camera"
nobody have idea and no dev support, so i try lot of things
and flashing latest A10 fw and restore persistbak + clean flash of RRos + 16 kernel are the last things i did and it worked
if you have orangfox do a backup of persist ,so if anything goes wrong you can just restore it
Click to expand...
Click to collapse
Ok I will try after backup
Which RN8 batch have you? Which camera didn't work?
Elinx said:
Which RN8 batch have you? Which camera didn't work?
Click to expand...
Click to collapse
what do you mean by batch ? i have ginkgo 6/128
the error was "can't connect to camera" (i guess,both front and back since i can't do anything while that error is apearing)
loopypalm said:
... batch ? i have ginkgo 6/128
the error was "can't connect to camera" (i guess,both front and back since i can't do anything while that error is apearing)
Click to expand...
Click to collapse
The batch date 11-2020 is the phone with problems.
First the problem with FW 12.01. This is the only phone that can't be flashed with that version. If you did with twrp, you had a brick.
Second the HW change of the selficam. I have seen I'm not the only one with Andoid Q "not connecting" to this specific cam.
On LOS 17 topic a saw there is a formel bug report published about this issue
I can use all other cams without problems. The error is only with selfiecam and A10. Not with Miui and not with A11.
That is why I think of a missing driver.
I read something about adding missing drivers, but think it isn't easy.
Also I understand that the vendor image contains the hardware drivers.
So trying kernels only hasn't influence on HW changes
I can imagine that A11 custom uses also later vendor images, that's why these roms work with selficam.
Next question would be.
Are vendor images for Ginkgo intechangable?
Elinx said:
That is why I think of a missing driver.
Click to expand...
Click to collapse
have you tried A10 latest stable FW ? (it has updated drivers in it)
Elinx said:
Are vendor images for Ginkgo intechangable?
Click to expand...
Click to collapse
as far as i tested(A10), they are all almost the same, except for some roms have some carrier overlays and BT in it and other have them in system
also audio mods and enhancement, some roms have it and other don't
loopypalm said:
have you tried A10 latest stable FW ?....
...
as far as i tested(A10), they are all almost the same, except for some roms ...
Click to expand...
Click to collapse
Yes I have the latest stable FW. First I thought that these contains the HW drivers.
But reading, I learned that with latest Android versions all drivers are inside vendor image.
That is why updating FW and kernel doesn't make any difference for RR.
Because of all brick/EDL troubles I'm being carefull what I flash.
I have made for now a twrp backup of vendor and efs partition.
The persist parttion must be backup with adb or terminal
My phone is still an empty phone so I can format data and so on.
I saw that Miui vendor files are downloadable.
The latest Global is 11.0.11
Elinx said:
The persist parttion must be backup with adb or terminal
Click to expand...
Click to collapse
use also recovery (you never know) ...
Elinx said:
I saw that Miui vendor files are downloadable.
Click to expand...
Click to collapse
before changing system try RR with A11 vendor just to make sure
(i did that between 2 A10 roms and it worked,but A11 = not tested)
you can wipe everything and flash rr since your data is not important
loopypalm said:
.....
before changing system try RR with A11 vendor just to make sure
(i did that between 2 A10 roms and it worked,but A11 = not tested)
...
Click to expand...
Click to collapse
Dit you flash the complete vendor.img from another A10 rom?
or replaced the 3 vendor files inside the rom's?
Elinx said:
Dit you flash the complete vendor.img from another A10 rom?
or replaced the 3 vendor files inside the rom's?
Click to expand...
Click to collapse
i flashed a rom (Don't remember the name) and i did a mess in vendor ,so instead of reflashing, i restored a recovery backup of vendor of an older rom (AEX) that was on my SD
of course error like app x stopped working popped off,so this is not a fix
this is just a crazy suggestion to test the compatibility of the drivers
also test this cam :
ɬɧɛ Ɩųŋąɬıƈ in Dtuxed Roms Public Group
t.me
it has updated libs
maybe it will work
loopypalm said:
...., i restored a recovery backup of vendor of an older rom (AEX) that was on my SD
.....
maybe it will work
Click to expand...
Click to collapse
Ok you flashed vendor.img with twrp
The download link is Miui camera.
There where no HW drivers inside
I already found also such a zip with libs, but without result
It is for improving camera results
Elinx said:
There where no HW drivers inside
Click to expand...
Click to collapse
i made a mistake in the zip
the cam that i wanted to give you is in the same group
i will see if i can find it
Try this bro
Thank you, I surely want to try this Magisk mod file, but the file isn't accessible without requist.
Maybe you have your reasons for that, but in that case it isn't possible to download.
I have tried to comment this with the video too, but you have disabled comments there.
temblor55 said:
Try this bro
Click to expand...
Click to collapse
temblor55 you forgot to make the file public
Sorry guy's made it public now
https://drive.google.com/file/d/1-3y1CR6nfVhFYf9VpE11FXOmDEQl5VMt/view
Hi, i'm going to try to install a GSI.
I never see anybody here to do it so i will do It on our beloved rog 6.
So, it seems to i have to have a vbmeta.img image to flash taking fron the ota update.
So, i will flash it along the GSI to see what happens. Anybody does that before? Please tell me if It works this way.
And what ROMs have you tried, and what work and doesnt.
Thank you.
1st Attemp:
I installed Pixel Experience Flashing vbmeta.img for disable encription (attached) And everything works minus Wide angle and macro cam on Gcam. Anyone know how to fix that?
Maybe something related to the camera ID on Gcam menu works.
The provided GSI is A12 GSI PHH Pixel Experience.
Attached vbmeta.img flash on both sluts.