yashsingh1/xdaforums huggingface dataset:
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] dudinha:
Why don't you compile the plus version too?

By the size of the partition it is not (I think), because the redmi note 4x has the same size as the system partition and has the official Pixel Experience 13 Plus.
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] 暗夜很无语:
I forgot a bug, that is, Bluetooth can't connect to another mobile phone, and the connection is disconnected for seconds
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] -+BB+-:
I need to know if you can reach that links in China, the https link is the one you are replacing with the ADB command, it's specific for China and it's used when a Chinese SIm is inserted in the device, I don't understand why ist' not working.

NOTE: it's AOSP code, 99.9% of custom ROM use that code, probably also official Pixel devices use it as is

Because I don't have ~500 Gb of free space in my NVME for downloading and compiling PE plus
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] 暗夜很无语:
In China, 99% of foreign websites are blocked and inaccessible. They can only be accessed with the help of VPN, but xda has not been blocked. Do you have 1 these social software
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] 暗夜很无语:
Not 1, but line. I don't know how to delete this comment
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] mandayugana:
I found some issues.

* Sometimes I can't lock the screen using the power button. It's back to working after several minutes.

* Sometimes taking photo with GCam make the phone suddenly turns off. Long pressing power button can't turn back on the phone. I can turn back on the phone after plugging in charger to the phone then long pressing the power button. Updating Shamim's GCam to the latest version doesn't seem to fix the issue.

* Long exposure still doesn't work.
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] -+BB+-:
That's not a web page , it's the default page used by Captive Portal when you connect to a network, if Captive Portal receive a SUCCESS response then Android lets you use the networks, otherwise the exclamation mark will appear and internet doesn't work. That links are the default used by AOSP and probably even Google use them on their Pixel, that's the reason why I don't understand what's happening, there should be a lot of reports for this bug. I've checked my local sources and that overlay is applied when you insert a Chinese SIM card in your phone, no matter what carrier you have, it's used for MCC 460, which is China country code. Unless you are using the phone without a SIM card that links are used and should be working fine

NOTE: i haven't reviewed all the code but without a SIM card inserted there's the possibility that Android falls back to the stock Captive Portal pages, probably blacklisted in China. If that is the case, it's how Android works, if you consider it a bug then should be addressed to AOSP

Even disabling EIS ANDROID_CONTROL_VIDEO_STABILIZATION_MODE_ON it's still declared and may cause issues, media profiles were also outdated and partially not working, I've uploaded my last internal build, it's in RC folder, here's the direct download link, please try with this and let me know if still reboots, I've picked i think 50 photos in a couple of hours without a reboot or any other issues. The power button issue surprises me, as no one reported that problem with none of my builds (strange thing is that long press does not reset the device, should work everytime, no matter what the phone is doing), and I'm using it as primary device at the moment, hopefully this build fixes the bug for you too!

NOTE: i will compile the monthly update with the same kernel/dt sources, on kernel side i've not decided yet for a couple of commits (still testing tracing removal, but without IORap should not be needed by anything else in Android), but the merge work is over, this is the definitive kernel on my ROM, I've merged 99% of infinity kernel except some commits that triggers CLANG warns and LZ4 backport from 4.19 kernel (the root cause of the reboot of all 4.4 ROMs in these years), it's rock solid for me and performance now are probably better than my old PE 12.1 ROM

@mrinfinity0007 please let me know if the new build fixes the issues you encountered, unfortunately at certain point thermal throttling is unavoidable with a legacy device like our Gemini, but with latest changes phone is much more smoother, even when starts to getting hot

EDIT: I've used USB tether for ROM upload, so i can confirm that it's working fine :)
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] mandayugana:
The power button surprised me too. Long pressing power button always reboot the phone, no matter what. But, in my case it wasn't. I replaced the battery about 2 weeks ago with a battery from a different brand, so it's probably a hardware issue triggered by GCam.

Now downloading your new build. Will try. Is it okay to dirty flash over previous build?
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] -+BB+-:
Yes you can safely dirty flash!

Ps: I'm at work now and can't answer, later i will post another message for the power button, hopefully it's not broken
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] -+BB+-:
@mandayugana I disassembled my gemini too some months ago when i decided to work again on it, I replaced MoBo and battery, and I had a similar issue with camera, mine was completely not recognized by system, I simply removed the protection plate and pressed again the camera connector, then camera started to work as it should, but before try to do this wait some report of other users, I never had a reboot taking photos with last build, but it's not an extensive test, and it' not enough, if you experience again reboots using the camera please report here, but wait some days before disassembly the phone. As for the power button when I disassembled mine I realized that there was really a lot of dust and dirt in the interlocking area of the back cover. The power button is not covered by the protective plate, during the opening operation if a part of the dirty ended up between the power button and the motherboard it is possible that the button gets blocked or does not work properly. I think the best thing is to remove the back cover and take a look in this point:

Good luck! :)
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] mrinfinity0007:
1) in internet calls the caller having echo from me..tried with different person and different social media like messenger/whatsapp... even tried group call but same they all hearing echo whenever i join them( used with and without earphone but same result) not sure what causing it

2) sometimes screen didn't turned off automatically i noticed in previous build also but that time i thought i set screen timeout 30min because i used it sometimes... but this time i checked properly..i had 30 sec screen off timout but it wont turn off automatically..( not happening everytime but sometimes i already noticed 3-4 times in this build)

3) consuming more power and heating issue slightly more but its faster than before i guess :)

i get it....its a lagacy devices that much we can sacrifice

4) checked again usb tethering not working..,,, i have a secondary phone ,,,i used its as usb tethering its working but not working in my gemini donno whats the issue :)

Note: i used clean flash this rom :)
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] -+BB+-:
1 - Was it working fine on previous build? I've tried a test call with Skype and it's working without echo for me, BTW there are some issues with audio/ record concurrency, there's still some work to do on audio side

2 - It's a know bug in Android 13 fixed in QPR3, if PE devs rebase their work over QPR3 sources we will have the fix merged in next public release

3 - My primary goal was to catch the reboot bug we had in previous 4.4 ROMs keeping all the work xNombre made for Gemini, in particular way on kernel, now we have a solid base with good performance and we can tune things a bit. :) Only drawback of this kernel compared to infinity kernel is compression/decompression speed, I've already tried to port the updates from 4.19 kernel and i ended up with the exact same sources of infinity kernel (and the reboot bug), I've also tried to update LZ4 to 1.8.3 (and I'm 100% sure it's working on 4.19 kernels because it's used by erofs) and things get worse (same reboot without logs, but every few hours, sometimes minutes).

4 - That' s really weird. The device is recognized and there' s no network or is not recognized at all?
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] mrinfinity0007:
tried some call test again... no echo this time..very strange :)

and about usb tethering its recognizing but no internet....( anyway i don't use that very much so not that kinda problem for me)

thanks for ur amazing work and keep gemini alive... :)
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] -+BB+-:
Hi to everyone, march update is out, here' the changelog from latest public build:

ROM

- Updated sources to latest PE

- Merged AOSP android-13.0.0_r35 updates

Proprietary blobs

- Update Adreno, SDM and postproc blobs to LA.UM.9.6.2.r1-04100-89xx.0

- Update media blobs to LA.UM.9.6.2.r1-04100-89xx.0

- Update graphics firmware from LA.UM.9.6.2.r1-04100-89xx.0

- Update audio and ADSP blobs from LA.UM.9.6.2.r1-04100-89xx.0 and and Oneplus 3T PKQ1.181203.001

Device tree

- Set UI rendering Skiagl with skiaglthreaded

- Clean up useless log spams

- wifi: smarter decisions on whether to use a 2- or 5Ghz AP

- camera: mix fixes and improvements for memory, stability and timeout logic (long exposure now should work, or at least doesn't crash camera app)

- props: add missing ro.vendor.extension_library prop

- Updated conf and props for R media and display HALs

- QCOM HALs: migrate to R HALs

- Reworked and updated pixel dance service

- fstab: enable discard option on /data partition

- Update configuration and props for R audio HAL

- Bluetooth: disabled APCF extended features

- Misc updates/fixes/improvements

Kernel

- backport speculative page fault

- backport ashmem and binder from 4.19

- mbcache: misc updates and fixes

- random: misc updates and fixes

- fix LD_DEAD_CODE_DATA_ELIMINATION, add support for our arch and enable it

- kbuild: misc updates/improvements

- improve thin archives

- crypto: port specific accelerated libs and enable them

- port LTO fixes and enable CLANG LTO

- Optimizations: compile with O3 flag

- disable frame pointers

- port and enable flatmem

- ported missing cutoff and capacity approximation changes from Xiaomi

- Disable all debugging and tracing

- Enable several optimisations

- Misc fixes

- take a look at my repo for all other updates, changes are really huge

Here's the direct download link

IMPORTANT: roll back from this version to older version is not possible without a clean flash, if someone needs to roll back to a 100% safe release without wiping the device download and flash latest internal build i shared, it has been used for days by several users and can be used safely for daily usage, here's the download link

Enjoy :)

@mrinfinity0007 sounds more like an APN configuration issue, did you check your APN settings?
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] -+BB+-:
Hi to everyone, I've decided to share my latest personal build if someone wants to try it, there are only some small changes in dt sources, but improvements are noticeable, especially in UI smoothness. There are also a couple of fixes for some small bugs i found in latest public release.

Here's a small changelog from latest public build:

Device tree

- Disable prefer_idle when screen goes off, this will optimize task placement for energy

- Fix power hints for camera (were working only partially)

- Fix adsprpcd and vendor audio service entry

- Assign several services to system-background cpuset

- Audio: misc fixes/updates and enabled call recording. NOTE: Google Dialer Call Recording is actually broken, 3rd party apps works fine

- Audio: switch to AOSP impl for sw effects

- Use GPU HW for rendering (improve UI smoothness)

- Small generic updates that i had no time to merge in public build

BONUS: I've synced my sources with PE, in this release some Pixel exclusive features has been unlocked

Here's the direct download link
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] iTz.siAm:
Thanks a LOT ❤️❤️
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] dudinha:
Hi,the high-res audio is not working (when I switch to it there is no sound)

Video showing this: https://drive.google.com/file/d/1mRD0SuqxA5g_6karVPFDqhPapCDwU3Ia/view?usp=drivesdk

And logs: https://drive.google.com/uc?id=1gRSp7ao0QF-6ZGksASUbvTr7latAqBlk&export=download

And as far as I remember before you switched to the OnePlus 3T/CAF audio blobs, the high-res audio still worked. :/

Date of build>28/03/2023
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] -+BB+-:
Hi, thanks for the report but im' afraid there's something messed up in your device configuration, I've tested hi-res audio with Poweramp free and it's working fine on both speaker and headphones. Weirdest thing in log you posted is the NFC crash, i never had once and no one reported anything related to NFC since the initial release, could you please try to clean NFC and TAG app data and see if stops crashing?

PS: if doesn't stop even clearing the apps data probably a full wipe is required, according to the kernel log NFC starts crashing during the boot and keeps restarting and crashing recursively every 4-6 seconds. Luckily this doesn't happen when screen is off, so at least device enter in deep sleep and doesn't drain more battery when phone is not used
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] dudinha:
My "NFC Module" is died,my nfc doesn't even work on miui :/

maybe because my mi5, is a "prototype" / engineering version
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] dudinha:
would it be possible for you to implement stereo audio for the speakers?
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] ecabmad:
@-+BB+- Thank you for the ROM, for the installation of build 28/03 do we need to flash any firmware or vendor before the ROM, or are they included already?
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] -+BB+-:
According to logs you posted the NFC HW is the same used in production devices

D NxpHal : getChipType HwVersion : 0x18
D NxpHal : getChipType Product : PN66T

There are not so much info in that logs but it's crashing when it's powering on and tries to enter in discovery mode, probably NFC is faulty and must be replaced

Hi, no need to flash everything else, sideload the ROM as usual :)
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] LMFuture:
could you make it official?
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] mandayugana:
I confirm that the first and second were hardware related issues. I just replaced the power button and the battery, it's working perfectly fine.
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] -+BB+-:
Honestly, at this stage of development i'm thinking about it, but first i want to see if the next public release goes well, there are some unreleased changes that I'm testing that really improves device smoothness, no problem so far but I want to be 100% sure before asking to go official :)

Also I'd like to move to Vulkan for UI rendering, but even if it's working really well there's a graphical glitch on the lockscreen clock that i wasn't able to fix yet, happens only when the device is on charge when there are no notification, it doesn't break anything and it's small, but it's terribly ugly to see

This is really a good news, for you and for me too! :) Regarding long exposure our camera HAL needs to be rewritten and updated, even if it's working fine there are some ugly hacks that i'd like to fix, and some changes that apparently has been removed from QCOM camera repos, i cannot find any reference about them in any CAF repos, but i cannot remove that code "as is" without breaking everything, i must port the updated changes from CAF and adapt the code for our device, may require a bit of time but it's something that should be done soon or late

PS: since you are the one with the most experience with GCAM feel free to suggest any configuration changes or share your config file if you decide to spend some time testing the various options , in that case with your permission I will add it in my GitHub and in OP :)

@dudinha there''s the possibility that your NFC chip is working, but the embedded firmware is broken. Firmware download/update functions does not work at all because PN66T support in hardware/nxp/nfc has been dropped years ago, and for what i saw in these years update firmware function never worked for our device, unless XIaomi fixed that in MIUI (i don't think they did, if i remember well i saw some logs from MIUI with the exact errors we have in custom ROMs). I've added back PN66T support in my local sources, doesn't work yet but at least now our chip is properly recognized and FW is downloaded. Could you please enable NFC additional debug, reboot the device and post the logcat? I'm curious to see if the firmware is loaded in your device. You can enable the additional debug with adb and a text editor:

adb root
adb shell mount -o rw,remount /vendor
adb pull /vendor/etc/libnfc-nxp.conf

Open libnfc-nxp.conf with a text editor and replace from line 13 to line 20 0x00 with 0x03, then

adb push libnfc-nxp.conf /vendor/etc/libnfc-nxp.conf
adb reboot

Once you finish disable the debug and reboot your device, or in your case NFC will spam a ton of logs every few seconds
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] LMFuture:
Are those changes committed to the device tree? I want to test them.
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] -+BB+-:
Yes, I've pushed everything a week ago, that changes are not included in latest build i shared
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] dudinha:
The logs:https://drive.google.com/uc?id=1wr1gjubip0gjtuoOl6q0j-sum-FJ40mM&export=download

I'm not in Pixel Experience, but if you want the logs in it, just say
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] LMFuture:
What compiler did you use to compile this kernel
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] mandayugana:
Don't get me wrong. I'm not an expert in GCam. I just played with it. I'm thinking of generating noise model of your ROM. I already generated for LOS 18, but some ROMs I tried generated different noise models. It is better to generate noise model while using your ROM. Unfortunately, I switched to Android 10 a few days ago, so currently I can't generate it.

I usually set these parameters on GCam. Actually these are very basic configurations for Mi 5.

Set front camera black level to 16, back camera black level should be 64 or default.

Enable "set videos efficiently" to enable H265 encoding. This resulted in smaller video file, but uses more CPU.

Merge algorithm: "SABRE merge" for front and back camera. "Spatial RGB" results in lower noise, but much slower HDR processing.

Device interface: "Pixel 2XL" or "Pixel 3".

Device selection for HDR: "Pixel 2XL" or "Pixel 3".

Noise modelers: "IMX374_SONY" for back camera, "ov8856 (RN8P)" for front camera. It's always better to use manual noise model, but we need to generate noise model to get the values.

Further noise reduction can be achieved by adjusting some values in LibPatcher. I'm still doing experiment on it.

Video bitrate: 5 Mbps for smaller video file. This should be good for H265.

Set "Disable hexagon" to off. Snapdragon 820 has hexagon processor.

My current GCam config is a mess. As soon as I get the right time, I will generate my config and share it here.

BTW, last time I use your ROM, I experienced:

Noticable lags on camera and video viewfinder. It was smoother on Android 10 ROMs.

Failure to update e-money (NFC card) balance. The NFC card needed to be tapped to the phone for a few seconds, but in the end the process always failed. No issue reading balance (quick tapping) from the card. If I remember correctly, this also happened on stock ROM. I have no idea if this fixable or not.

Update 20240212:

Updating e-money (it is probably writing data to NFC card) balance works on stock ROM.
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] chinhnguyen12:
is there new miui for mi5? im using miui10 android 8. it seems miui has stopped updating to a newer version?
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] dudinha:
I changed this lines only .
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] -+BB+-:
The config is slightly different than mine, in your file from line 27 to line 32 change all 0x01 with 0x03, in line 33 replace 0 with 1 and reboot

PS: in your case completely disable debug is a better choice, as your NFC crashes and restart every few seconds. No matter the ROM your use, you should replace 0x01 with 0x00 for daily usage
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] dudinha:
Now I think it's right ; - ;

logcat.txt - AnonFiles

anonfiles.com
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] -+BB+-:
Yes, in the log you posted NFC is in verbose mode, I'll take a look in these days if your crash is caused by a wrong firmware or something else :)

PS: apparently the ROM you are using supports download/update fw operations for our NFC chip, but:

1 the firmware file is missing or probably in the wrong path, please check if you have this file: vendor/lib/libpn548ad_fw.so if you have it in that path, try to move the file in vendor/lib64/ , that's the correct path where NXP hal search for firmware updates

2 even with the firmware file in the correct path, you'll probably end up with this error in logs and fw does not update, that part of code has been changed some years ago in order to avoid memory corruption in some cases, but our NFC chip even when init is finished never tries again to update firmware. That's the point where I'm stuck, only idea i had to make it working is to revert that changes or remove them, but this will change the update method for a lot of devices, it's not a good solution
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] -+BB+-:
Hi to everyone! I made a test build of PE Plus (this build includes all latest changes in my device tree branches), if everything works fine i will provide both versions. Here's the download link if someone wants to try it, let me know if some Plus feature does not work.

NOTE: A clean flash is required, dirty flash from stock PE will result in Settings screwed

EDIT: LINK REMOVED, DOWNLOAD APRIL UPDATE
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] -+BB+-:
Hi to everyone, April update is out and starting from this month i will provide PE Plus version too.

Here's the changelog from last public release:

ROM

- Sync sources with latest PE changes

- Merged android-13.0.0_r41 AOSP updates

Device tree

- Disable prefer_idle when screen goes off, this will optimize task placement for energy

- Fix power hints for camera (were working only partially)

- Fix adsprpcd and vendor audio service entry

- Assign several services to system-background cpuset

- Audio: misc fixes/updates and enabled call recording. NOTE: Google Dialer Call Recording is actually broken, 3rd party apps works fine

- Audio: switch to AOSP impl for sw effects

- Use GPU HW for rendering (improve UI smoothness)

- disable ripple unlock animation

- Update conf and SEPolicy for new blobs

- Small generic updates that i had no time to merge in previous public build

- Added back LiveDisplay feature (Plus version only)

Kernel

- Small cleaning

Pixel Experience 13 Direct download link

Pixel Experience 13 PLUS Direct download link

NOTE: Plus version can be dirty flashed over default version

Enjoy :)
[Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev] :
ROM is smooth and stable enough but the GPS was unusable. It was finding me with a precision of 100m of distance! Got back to LOS19.1 and now it works as it should. Hope it gets fixed in next releases!