• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[ROM][OFFICIAL][ginkgo/willow] Pixel Experience [11.0]

do you like it ?


  • Total voters
    171
Search This thread

AzaelFLD

New member
Jul 5, 2021
1
0
When I install the ROM everything is fine, but after spending a while using it, the interface elements are icons, menus or text, they are marked on the screen making it annoying, this only does not happen in MIUI ROMS, is there a solution?
 

igos9185

New member
Aug 24, 2021
1
0
Добрый день, после прошивки быстрая зарядка перестала работать, она включается, если вы только перезагрузите телефон с уже подключенной зарядкой.
 

Sahilkhan9

Member
Aug 25, 2021
10
2
I flashed pe+ using orange fox recovery, and it was working great untill I switched off of phone and when i tried to on it my phone got stuck in orange fox custom recovery logo, and i wasn't even able to off or on the phone, i tried everything but nothing happened, do you guys have any solution to this problem???
 

Caju C.Lo 973

New member
Aug 4, 2017
4
1
View attachment 5250393

PixelExperience for Xiaomi Redmi Note 8/8T

What is this?
Pixel Experience is an AOSP based ROM, with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, bootanimation)

Our mission is to offer the maximum possible stability and security, along with essential and useful features for the proper functioning of the device

Based on Android 11



Whats working?
Wifi
RIL
Mobile data
GPS
Camera
Camcorder
Bluetooth/Audio
Fingerprint reader
Sound / vibration
DT2W


Known issues
You tell.

How to flash
Flash Latest Ten firmware
Wipe system
Wipe Vendor
Format Data
Flash ROM
Reboot

Telegram Group
Link


DON'T FLASH GAPPS, ALREADY INCLUDED
Link


Translation
Help with project translation

Stay tuned
Our Telegram channel
Our blog






XDA:DevDB Information
pixel-experience, ROM for the Xiaomi Redmi Note 8/8T

Contributors
iamsaalim
Source Code: https://github.com/PixelExperience-Devices/device_xiaomi_ginkgo

ROM OS Version: Android 11
ROM Kernel: Linux 4.x
ROM Firmware Required: Ten firmware.
Based On: AOSP

Version Information
Status:
Stable
Beta Release Date: 2021-03-13

Created 2021-03-15
Last Updated 2021-03-15

El Ajuste de imagen en LiveDisplay no funciona.
La bateria se drena mucho cuando el dispositivo esta en reposo.
 

kekusinkay

New member
Aug 26, 2021
1
0
Hi.
Fingerprints disappear after switching to the second user of the device. You have to set it up again every time. Is there a way to fix this?
 

iamsaalim

Recognized Developer
Bruh, I've installed this rom because of nice and clean Android and MIUI camera, now there is no MIUI camera app in the new update and the stock aosp camera is a joke. I know I can install some Gcam, but I can't say this is really reliable, because some versions may crash, some have different bugs and the MIUI one is always working great, especially when you need to do a quick photo. I don't want to install Magisk to get the MIUI camera app either. I think devs should leave the original camera app in these roms as it is working as it should with full functionality as intended. Going back to the previous version for now. Btw thanks for your work, I am very satisfied with this rom in general
we purposely included aosp camera such that users get a free choice to install any other camera they desire to in future, else miui cam can conflict with some gcams
 

Top Liked Posts

  • There are no posts matching your filters.
  • 6
    Thank you all who gave their valuable input in my quest to troubleshoot my issues. After immense trial and error with tons of google searches, I was finally able to frankenstien enough knowledge to create one final solution. As a sign of my respect for this community, I'll pen my experience down in hopes it saves the trouble for someone else down the line.

    Foremost, the installation guide linked was easy to understand and the ROM itself is light and extremely responsive. Apart from some minor hiccups here and there, this is a good Pixel Experience. Thank you iamsaalim!

    That being said, if you're an unfortunate person like me who lives in India and a victim of Xiomi's "yea I'll think about you last" attitude, there are a few things that the guide does not cover at the time of writing this post. Not the maintainers fault tbh, it's just bad luck. Here are the steps that I followed:

    • Grabbed both the ROM and Recovery from the link in the original post.
    • Followed the guide to the letter up until the point where I flashed the recovery in via adb.
    • Encountered recovery issue where the phone would just freeze trying to go into recovery via Vol+ and Power buttom. Tried "fastboot erase userdata" command. Freezing issue gone but instead of TWRP, MI Recovery showed up. After much trial and error and thanks to yn4v4s's input(you rock dude), I finally realized I'm on Q firmware which is Android 10 whereas the TWRP in the original post is meant for R firmware which is Android 11. Decided to grab the yn4v4s's recommended Global version.
    • Went to TWRP website and grabbed December 2020 recovery and flashed that via adb. Success as TWRP flares to life.
    • Continued on with the guide all excited thinking the worse is behind me as all I need is to install ROM, right? WRONG.
    • Immediately new problem: Factory Reset/Formatting failure/Wiping Failed. reason? Operation not Permitted
    • Selected Mount and spotted a weird anomaly. Cycling through the storage, noticed Internal storage was marked as (0) capacity. Immediately stuck that as odd. Google search intensified.
    • Went to Wipe> Selecting /data > Advance Wipe > Change file system, I saw that the file system was FTFS by default. Changed it to ext4 and formatted it. Now ftfs is supposed to be better but I noticed all other drive partitions were in ext4 format, so for the sake of simplicity I stuck with ext4 instead of reverting to ftfs.
    • Tried Factory resetting again. This time new error while formatting: Invalid Argument. Proceeded to chuck neighbor's cat out of the window and fight imaginary sharks to vent frustration.
    • Calmed down and went back a few steps. Realized, forgot to clear cache. Went back into Advance wipe and cleared Davlik /ART Cache, Cache, Data, System and Vendor.
    • Proceeded to format once again typing "yes" while praying. Finally, success!!
    • Time to flash and upgrade to Android 11 firmware first before the ROM. Placed the global firmware into the SD card via USB cable. Saw folks flashing ROMs from TWRP as well so placed PE ROM too.
    • Selected Install on TWRP and navigated to the firmware file. Executed the firmware and noticed it installing within seconds. A bit worrying sign but since no errors were thrown I continued on.
    • Navigated to the directory again, selected PE ROM image this time and installed it as well. Installation went without any incidents and returned with a success message. Okay...
    • Moment of Truth. Reboot! 1 minute passes, Google Icon spins up. YES! 2 minute passes, Google bar starts running. Encouraging! 3 minute passes, bar continues running. Erm. 4 minute passes, bar still. Uh oh.
    • Yeap, no cigar yet. I'm now stuck in a boot loop. To make matter worse, TWRP recovery gets overwritten by PE Recovery. Sigh.
    • Decide to grab the latest TWRP from their website and flash that instead since there is no point in using old Android 10 TWRP.
    • Aaand I'm frozen again on REDMI screen. WTF?! I flashed Android 11 global firmware so I'm pretty sure I'm on the new one. Flashed old TWRP again and sure enough I'm into the recovery. Confused as hell now. For the heck of it, I erased Cache again.
    • Noticed an odd new console error in red. Unable to decrypt FBE device
    • More google searches later, I come across discussion where community came to the conclusion that "console output Unable to decrypt FBE device was nothing but to tell us that incompatible operating system flashed"
    • OS can't be an issue, it's made for my Redmi Note 8 and I'm plenty sure I'm on ginkgo.
    • Going through this thread I noticed how folks swore by Chinese firmware. Decided to deviate and flash that firmware instead. Wiped everything again including the OS.
    • Went back to following the guide and decided to sideload selecting Advanced on TWRP and select "Side Load" option. Copied the ROM in my ADB directory on the PC and used the "sideload 'ROM NAME'.zip" command.
    • Waited patiently for the message: If the process succeeds the output will stop at 47% and report adb: failed to read command: Success/No error.
    • Process ends but no such message. Instead I get: Total xfer: 1.00x
    • Quick google search showed that this is an error message. Too tired to get angry or brainy at this point so I simply reboot for the heck of it.
    • 1 minute into boot and suddenly I see white light. COULD IT BE...?
    • Sure enough, Google bursts out of boot into first time setup. YAY?!!
    Apologies, if this became a weird wall of text but this is a sum total of my experience in the last couple of weeks. I've no idea if I have done this right or I just got lucky eventually but it somehow worked for me. From installing adb, to fighting with drivers to recognize my phone, to waiting 7 days for bootloader to open, to finally all that I listed above, it was truly a nightmarish experience. But in the end, it was worth it. The default camera was a bit of a letdown but thankfully GCam apk uploaded in this thread by another member was easy enough to install and runs without issues. Unable to move the clock on the wallpaper became a bit of an irritant but nothing Nova Launcher couldn't fix.

    All in all, apart from the installation pangs, I'm loving it. Thank you all for your advice. Truly would have been lost without your inputs.
    2
    Crap. That explains a bloody lot. Thank you for sharing that knowledge. I got hold of the R firmware but... damnnit, TWRP recovery simply won't execute. Screen just freezes. I think I'll have to find a reliable alternative to TWRP..
    Make sure you got the right version of TWRP for your device, you can use Pitch Black Recovery as well, just don't use OrangeFox, it breaks with PE
    2
    Please, are we getting Android 12?
    The Devs did a great job on the A11 PLUS EDITION, I swear.
    Thanks in advance.

    Please people, don't be like this. OP / mantainer is already doing a great job by providing a ROM wich works very well. Stop spamming threads with those ETA questions time after time, don't disrespect mantainers please.
    1
    firmware first then the pe rom. Otherwise the wifi will not work. I asked many people and they say that to prevent users from going from MIUI ROM xiaomi use broked vendor in Redmi Note 8. So for this after flashing any custom rom in note 8 the wifi doesn't work. Then a solution came that if you flash the MIUI firmware and then the custom rom wifi works. But then the phone stucks at bootloop. Then a solution came that you have to flash the miui firmware first and then custom rom. Then you have to do format data and then reboot the device. The device will actually boot and wifi will also work as a charm
    I did this and it's working great. I'm so happy with this rom, so smooth. Thank you for replying.
    1
    I just wanted to tell the OP / Maintainers a big "THANK YOU!"

    For me the ROM is working really fine now for about 6 Weeks, no flaws, nothing... yeah!
  • 21
    1615785682437.png


    PixelExperience for Xiaomi Redmi Note 8/8T

    What is this?
    Pixel Experience is an AOSP based ROM, with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, bootanimation)

    Our mission is to offer the maximum possible stability and security, along with essential and useful features for the proper functioning of the device

    Based on Android 11



    Whats working?
    Wifi
    RIL
    Mobile data
    GPS
    Camera
    Camcorder
    Bluetooth/Audio
    Fingerprint reader
    Sound / vibration
    DT2W


    Known issues
    You tell.

    How to flash
    Flash Latest Ten firmware
    Wipe system
    Wipe Vendor
    Format Data
    Flash ROM
    Reboot

    Telegram Group
    Link


    DON'T FLASH GAPPS, ALREADY INCLUDED
    Link


    Translation
    Help with project translation

    Stay tuned
    Our Telegram channel
    Our blog






    XDA:DevDB Information
    pixel-experience, ROM for the Xiaomi Redmi Note 8/8T

    Contributors
    iamsaalim
    Source Code: https://github.com/PixelExperience-Devices/device_xiaomi_ginkgo

    ROM OS Version: Android 11
    ROM Kernel: Linux 4.x
    ROM Firmware Required: Ten firmware.
    Based On: AOSP

    Version Information
    Status:
    Stable
    Beta Release Date: 2021-03-13

    Created 2021-03-15
    Last Updated 2021-03-15
    6
    Thank you all who gave their valuable input in my quest to troubleshoot my issues. After immense trial and error with tons of google searches, I was finally able to frankenstien enough knowledge to create one final solution. As a sign of my respect for this community, I'll pen my experience down in hopes it saves the trouble for someone else down the line.

    Foremost, the installation guide linked was easy to understand and the ROM itself is light and extremely responsive. Apart from some minor hiccups here and there, this is a good Pixel Experience. Thank you iamsaalim!

    That being said, if you're an unfortunate person like me who lives in India and a victim of Xiomi's "yea I'll think about you last" attitude, there are a few things that the guide does not cover at the time of writing this post. Not the maintainers fault tbh, it's just bad luck. Here are the steps that I followed:

    • Grabbed both the ROM and Recovery from the link in the original post.
    • Followed the guide to the letter up until the point where I flashed the recovery in via adb.
    • Encountered recovery issue where the phone would just freeze trying to go into recovery via Vol+ and Power buttom. Tried "fastboot erase userdata" command. Freezing issue gone but instead of TWRP, MI Recovery showed up. After much trial and error and thanks to yn4v4s's input(you rock dude), I finally realized I'm on Q firmware which is Android 10 whereas the TWRP in the original post is meant for R firmware which is Android 11. Decided to grab the yn4v4s's recommended Global version.
    • Went to TWRP website and grabbed December 2020 recovery and flashed that via adb. Success as TWRP flares to life.
    • Continued on with the guide all excited thinking the worse is behind me as all I need is to install ROM, right? WRONG.
    • Immediately new problem: Factory Reset/Formatting failure/Wiping Failed. reason? Operation not Permitted
    • Selected Mount and spotted a weird anomaly. Cycling through the storage, noticed Internal storage was marked as (0) capacity. Immediately stuck that as odd. Google search intensified.
    • Went to Wipe> Selecting /data > Advance Wipe > Change file system, I saw that the file system was FTFS by default. Changed it to ext4 and formatted it. Now ftfs is supposed to be better but I noticed all other drive partitions were in ext4 format, so for the sake of simplicity I stuck with ext4 instead of reverting to ftfs.
    • Tried Factory resetting again. This time new error while formatting: Invalid Argument. Proceeded to chuck neighbor's cat out of the window and fight imaginary sharks to vent frustration.
    • Calmed down and went back a few steps. Realized, forgot to clear cache. Went back into Advance wipe and cleared Davlik /ART Cache, Cache, Data, System and Vendor.
    • Proceeded to format once again typing "yes" while praying. Finally, success!!
    • Time to flash and upgrade to Android 11 firmware first before the ROM. Placed the global firmware into the SD card via USB cable. Saw folks flashing ROMs from TWRP as well so placed PE ROM too.
    • Selected Install on TWRP and navigated to the firmware file. Executed the firmware and noticed it installing within seconds. A bit worrying sign but since no errors were thrown I continued on.
    • Navigated to the directory again, selected PE ROM image this time and installed it as well. Installation went without any incidents and returned with a success message. Okay...
    • Moment of Truth. Reboot! 1 minute passes, Google Icon spins up. YES! 2 minute passes, Google bar starts running. Encouraging! 3 minute passes, bar continues running. Erm. 4 minute passes, bar still. Uh oh.
    • Yeap, no cigar yet. I'm now stuck in a boot loop. To make matter worse, TWRP recovery gets overwritten by PE Recovery. Sigh.
    • Decide to grab the latest TWRP from their website and flash that instead since there is no point in using old Android 10 TWRP.
    • Aaand I'm frozen again on REDMI screen. WTF?! I flashed Android 11 global firmware so I'm pretty sure I'm on the new one. Flashed old TWRP again and sure enough I'm into the recovery. Confused as hell now. For the heck of it, I erased Cache again.
    • Noticed an odd new console error in red. Unable to decrypt FBE device
    • More google searches later, I come across discussion where community came to the conclusion that "console output Unable to decrypt FBE device was nothing but to tell us that incompatible operating system flashed"
    • OS can't be an issue, it's made for my Redmi Note 8 and I'm plenty sure I'm on ginkgo.
    • Going through this thread I noticed how folks swore by Chinese firmware. Decided to deviate and flash that firmware instead. Wiped everything again including the OS.
    • Went back to following the guide and decided to sideload selecting Advanced on TWRP and select "Side Load" option. Copied the ROM in my ADB directory on the PC and used the "sideload 'ROM NAME'.zip" command.
    • Waited patiently for the message: If the process succeeds the output will stop at 47% and report adb: failed to read command: Success/No error.
    • Process ends but no such message. Instead I get: Total xfer: 1.00x
    • Quick google search showed that this is an error message. Too tired to get angry or brainy at this point so I simply reboot for the heck of it.
    • 1 minute into boot and suddenly I see white light. COULD IT BE...?
    • Sure enough, Google bursts out of boot into first time setup. YAY?!!
    Apologies, if this became a weird wall of text but this is a sum total of my experience in the last couple of weeks. I've no idea if I have done this right or I just got lucky eventually but it somehow worked for me. From installing adb, to fighting with drivers to recognize my phone, to waiting 7 days for bootloader to open, to finally all that I listed above, it was truly a nightmarish experience. But in the end, it was worth it. The default camera was a bit of a letdown but thankfully GCam apk uploaded in this thread by another member was easy enough to install and runs without issues. Unable to move the clock on the wallpaper became a bit of an irritant but nothing Nova Launcher couldn't fix.

    All in all, apart from the installation pangs, I'm loving it. Thank you all for your advice. Truly would have been lost without your inputs.
    5
    Yes sir, same for me yesterday with Willow. I thought it was caused by flashing DFE after flashing ROM, but so probably it's not the case. I solved flashing the latest stable fastboot MIUI rom from XiaomiAdbFastboot Tools, than flashing OrangeFox, wipe system etc., format data and than flashing the ROM zip. I also enabled the OTA updater settings in OrangeFox (I don't think it serves any purpose, but I'm writing it anyway).

    EDIT: I tried to go to recovery and I got stuck again......so don't try to open it again... @iamsaalim

    EDIT2 - installing Pitch Black Recovery (as said in previous posts) allows to open recovery but it got stuck on bootanimation if I reboot into system
    1. Flash vbmeta.img and recovery.img using adb fastboot
    2. Boot into recovery mode and connect ur phone to the computer using usb cable
    3. Copy the recovery file, ROM, latest 10 fw
    4. (In the recovery mode) flash recovery file
    5. Flash 10 fw
    6. Wipe cache/dalvik, data, vendor, internal storage, system
    7. Format data
    8. Install ROM
    9. Boot to system
    If u using the latest version of PE+ or PE I suggest using pitch black recovery
    3
    Hey guys, I figured out how to stop PE recovery from overwriting TWRP!(Noob here, so ignore if you already know this).

    All you have to do is format the cache partition in fastboot mode before booting to recovery. This can be done by fastboot erase cache , after fastboot flash recovery twrp-3.5.2_9-1-ginkgo.img .
    3
    Thread cleaned

    Please be friendly to each other and also respectful.
    Keep the thread on topic 👍

    If you have bugs, report them to the dev with logs etc. and contribute to make the rom bug-free.
    If you don't want to contribute, use it as it is and say at least thanks to the dev who provided his work freely here on XDA:) The dev owes you absolutely nothing and you're not his customer cause you did not pay him.

    This manner of posting is not tolerated.

    I recommend to read the FORUM RULES especially those:


    2.1 Language: XDA is a worldwide community. As a result, what may be OK to say in your part of the world, may not be OK elsewhere. Please don't direct profanity, sexually explicit language or other offensive content toward Members or their work. Conversely, while reading posts from other members, remember that the word you find offensive may not be offensive to the writer. Tolerance is a two-way street.

    2.3 Flaming / Lack of respect: XDA is about sharing and this does not involve virtual yelling (flaming) or rudeness. Flaming or posting with a lack of respect is unacceptable. Treat new members in the manner in which you would like to have been treated when you were a new member. When dealing with any member, provide them with guidance, advice and instructions when you can, showing them respect and courtesy. Never post in a demanding, argumentative, disrespectful or self-righteous manner.

    2.4 Personal attacks, racial, political and / or religious discussions: XDA is a discussion forum about certain mobile phones. Mobile phones are not racial, political, religious or personally offensive and therefore, none of these types of discussions are permitted on XDA.


    If you come across this just hit the report button and let the mods handle it, do not respond or become part of such a discussion.

    Regards!

    strongst
    Forum Moderator