Development [ROM][T][OFFICIAL] LineageOS 20 for POCO X3 Pro [vayu/bhima]

[qlum]

Hello!

I recently switched from dotOS to the official Lineage build (thank you for the support) and I noticed I can not use the macro lense when using gcam... That wasn't the issue on dotOS and I wonder if it's a matter of "just adding a few lines of code" or something more complicated. If it isn't a huge hassle, I would really appreciate if using the macro lense becomes possible in the next OTA

Thanks in advance

P.S.: The build itself is super smooth and stable, I did not encounter any other issues so far except for the macro lense thing.

I have noticed the same thing, though I never tried dotOS, the ultrawide lis also not supported.
That being said, neither of these camera sensors are that great.

 

[Sn0wPaw]

With some minor tweaks the macro lense is quite interesting, and make good photos

 

[biojo]

Which firmware ? Latest?

firmware V12.5.2.0
rom lineage-18.1-20210910-nightly-vayu-signed

 

[Ramesh006]

i have flashed latest version on top of miui 12.04. i know the recommended firmware is higher but due to ghost touch issue i decided to stay in 12.04. everything works. HGMI runs smoothAF, battery backup was excellent. charging speed also good. without any custom kernel i got this cpu score. using without gapps, all my apps restored perfectly with swiftbackup. i never had this cpu score on stock or other custom roms with custom kernel.
Thanks developer.

 

[schasch]

@SebaUbuntu

Many thanks for bringing official LOS to the X3 Pro.
My poco F1 display is broken, so I need new SD-compatible-xiaomi with official LOS.
Do you have plans to long time support official LOS in future?

regards

 

[Lu5ck]

I have noticed the same thing, though I never tried dotOS, the ultrawide lis also not supported.
That being said, neither of these camera sensors are that great.

how do you test each individual len?

 

[k3lcior]

i have flashed latest version on top of miui 12.04. i know the recommended firmware is higher but due to ghost touch issue i decided to stay in 12.04. everything works. HGMI runs smoothAF, battery backup was excellent. charging speed also good. without any custom kernel i got this cpu score. using without gapps, all my apps restored perfectly with swiftbackup. i never had this cpu score on stock or other custom roms with custom kernel.
Thanks developer.

Stock ArrowOS.

 

[dey18]

Huge thanks to @SebaUbuntu for official Lineage support and OSS tree
I just want to know why CTS fails even though the vbmeta.img is signed (and can it be resolved by using a blank vnmeta.img ?). And if not AVB, what causes CTS to fail?

Attached signature of blank vbmeta.img

 

[Lu5ck]

Huge thanks to @SebaUbuntu for official Lineage support and OSS tree
I just want to know why CTS fails even though the vbmeta.img is signed (and can it be resolved by using a blank vnmeta.img ?). And if not AVB, what causes CTS to fail?

Attached signature of blank vbmeta.img

Redirecting…

You will have to modify device fingerprint yourself through magisk

 

[Ramesh006]

Stock ArrowOS.

then i will give it a try

 

[Lu5ck]

Stock ArrowOS.

So you see, I was curious how come your graph is so consistent while @Ramesh006 had a drop after awhile. I went to playstore to dig up the said app and interestingly, I also had the same drop on my first run!

Then, half an hour later, I run again, I started at the dropped range, I wonder why.

Numerous hours later, I tried again and at 4th minute mark, it drop again and then I got a brilliant idea! I put the phone in my fridge and it goes up!!! So in conclusion, either lineage try to keep the phone cool or you are in a cool environment or arrowos doesn't throttle to keep phone cool.



In all honestly though, if performance is a primary concern, one should have top up a little more to buy Poco F3

 

[dey18]

Redirecting…

You will have to modify device fingerprint yourself, either through build.props or magisk

Thanks for your response. The question was about the reason for the failure and not fixes to make it pass! Hope you understand that.

 

[kiraryu]

Thanks for your response. The question was about the reason for the failure and not fixes to make it pass! Hope you understand that.

It is caused by the fingerprint does not match the security date

 

[Lu5ck]

Thanks for your response. The question was about the reason for the failure and not fixes to make it pass! Hope you understand that.

Your respond truly puzzle me.

The link tell you what is safetynet, why it fail and why lineage dev don't want to "fix" it.

Then telling you how to technically fix it is also indirectly telling you why it technically fail.

 

[dey18]

Your respond truly puzzle me.

The link tell you what is safetynet, why it fail and why lineage dev don't want to "fix" it.

Then telling you how to technically fix it is also indirectly telling you why it technically fail.

Sorry I don't seem to understand why it fails thought I've gone through the article. Can you please explain that in your words. Also can you confirm whether using a blank vbmeta.img mentioned above will help pass (not bypass) CTS.

 

[Lu5ck]

Sorry I don't seem to understand why it fails thought I've gone through the article. Can you please explain that in your words. Also can you confirm whether using a blank vbmeta.img mentioned above will help pass (not bypass) CTS.

I see where the potential problem now.

Are you referring to Compatibility Test Suite (CTS) Profile of Safetynet or something else?

If is the same CTS I am referring to, then, what puzzle me is what has vbmeta has to do with it? AFAIK, when people flash vbmeta, they are trying to install GSI roms because they need to disable AVB but that also puzzle me because you are posting in this thread thus you are not installing GSI rom unless you are posting in wrong thread?

If it is something else, then that is beyond my knowledge.

Lastly, as mentioned early, if you are using this rom, then by factory, the device fingerprint of this rom is invalid thus CTS will fail, the technical fix is to use magisk change it.

 

[qlum]

how do you test each individual len?

Normally as far as I know on setups with multiple camera modules you can switch between them. As can be done on the stock rom this is basically what I tested in aosp, open camera and google camera. Neither seem to work.

 

[X4r3X]

Hello!

I recently switched from dotOS to the official Lineage build (thank you for the support) and I noticed I can not use the macro lense when using gcam... That wasn't the issue on dotOS and I wonder if it's a matter of "just adding a few lines of code" or something more complicated. If it isn't a huge hassle, I would really appreciate if using the macro lense becomes possible in the next OTA

Thanks in advance

P.S.: The build itself is super smooth and stable, I did not encounter any other issues so far except for the macro lense thing.

Hows video recording?

 

[Sn0wPaw]

Hows video recording?

Video recording with the correct xml config works flawlessly (on custom roms usually the OSS ones)... Tho there are a couple of options to choose from, so i'd suggest joining a telegram group and testing each config to find the one best suiting your taste.

Edit: telegram group -
Poco X3 Pro | Photography
Official Group: @pocox3proglobalofficial
- Read rules (/rules), English only
- Only Share Pics Clicked With POCO X3 Pro
- Mention The Camera App Used
- Don't Share More Than 11 Pics
- Photos Must Have Captions
- No Promotion Allowed
- Slight OT Allowed

Poco X3 Pro | Photography

Official Group: @pocox3proglobalofficial - Read rules (/rules),Use English Only - Only Share Pics Clicked With POCO X3 Pro - Mention The Camera App & Config Used - Photos Must Have Captions - No Promotion Allowed - Slight OT Allowed

t.me

 

[SoyDPR]

How can I fix the safety net? I have tried a lot of methods with no results