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

Development [ROM][11][Mojito][Sunny] Pixel Experience [OFFICIAL][AOSP]

Search This thread

StaryMuz

Senior Member
Dec 27, 2012
431
140
AOD can inform about notifications just like the status bar. But for new notifications, it's the wake screen and not the AOD. The wake-up screen is a classic display mode with brightness adjusted to ambient light. AOD is a permanently posted information on the display with minimized power consumption. AOD has no brightness control.
 
Apr 23, 2018
6
3
AOD can inform about notifications just like the status bar. But for new notifications, it's the wake screen and not the AOD. The wake-up screen is a classic display mode with brightness adjusted to ambient light. AOD is a permanently posted information on the display with minimized power consumption. AOD has no brightness control.
but when I get notifications, the screen lights up, but very dark. I can't make the screen turn on more intensely when receiving notifications?
 

StaryMuz

Senior Member
Dec 27, 2012
431
140
If you have auto-brightness set by default, this screen should follow your existing preferences from the status bar settings in a particular ambient light. If you have auto-brightness turned off, it should turn on according to the brightness you last selected.
 
Apr 23, 2018
6
3
If you have auto-brightness set by default, this screen should follow your existing preferences from the status bar settings in a particular ambient light. If you have auto-brightness turned off, it should turn on according to the brightness you last selected.
in mine, regardless of how I set the brightness, the AOD and the new notification screen is too dark.
 

StaryMuz

Senior Member
Dec 27, 2012
431
140
Set your alarm for one minute more than the current time, place the screen under a light bulb and turn off the display. Wait for the notification screen and you'll see it get brighter. It reacts to what the ambient light is like.
 

rscm

Member
Nov 1, 2017
43
9
Redmi Note 10
Update (22/9/21):

Changelog:
• Bring back full stack of audio ACDB
• Update blobs from V12.5.3.0.RKGMIXM
• Added main display cutout overlays
• Fixed dimens values for display cutout
• Updated brightness overlay configs
• Added camera cutout ring like memeui
• Removed virtual framebuffer cmdline
• Labeled some more wakeup nodes
• Switched to aosp WiFi Display
• Mic issue is fixed other variant
thanks for the fix in the layout (display)
 

Animenerd

Member
Aug 16, 2021
34
7
Ok so everything looks good now, I haven't encountered any types of problems yet. One thing I noticed is that the upper two cutouts of the screen are a bit weird, they aren't done properly, also there are lags in some apps while none in others.
Anyway, thanks dev for the rom, hope these get fixed in the future update.
 

aspret

Member
Aug 3, 2016
7
1
Everything in this new update seems fine, except VIBER calling. cant hear anything from other side.
Came from august update directly
 

nash2212

Senior Member
Jan 13, 2016
53
8
I think the mic issue is still not fixed. The person i call on imo cannot here my voice. I am on the lastest build
 

Coff33Singh

Member
Dec 21, 2016
8
4
Redmi K20 Pro
Regulr calls is working as it should.

However, issue with no audio going to other part still persists on third party calling/video calling apps as Duo, IMO etc.

Will test out further and update.
Oh, YouTube Vanced can't login anymore.
 

Xeyoval

Member
Sep 18, 2021
5
0
Problems I've noticed with the latest version:
- same as other users issues with VOIP audio calls on WhatsApp/Telegram. When I make outgoing calls the other person manages to hear me (with difficulty though) Incoming calls on the other hand don't work (the other person doesn't hear me at all).
- same issue as Black_devil4559 above the OTA update didn't work I had an error message. I had to dirty flash from the SD card. Is it safe to update to new versions that way instead of native OTA updates? Does it risk breaking anything especially since we can't clear Dalvik and Cache on Pixel Recovery?
 

atharva.phadke

Senior Member
Feb 13, 2021
75
36
Redmi Note 10
Problems I've noticed with the latest version:
- same as other users issues with VOIP audio calls on WhatsApp/Telegram. When I make outgoing calls the other person manages to hear me (with difficulty though) Incoming calls on the other hand don't work (the other person doesn't hear me at all).
- same issue as Black_devil4559 above the OTA update didn't work I had an error message. I had to dirty flash from the SD card. Is it safe to update to new versions that way instead of native OTA updates? Does it risk breaking anything especially since we can't clear Dalvik and Cache on Pixel Recovery?
You need to be on pixel experience official latest recovery,then only ita update will work, if you have yeto/orangefox/los recovery,OTAs will not work.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    Yes

    Everything is up to date

    But still the error

    Is this because of the PE Rom
    Tested from a diff device but why don't you try this fix
    Just in case someone is facing an issue with a login on YT Vanced v16.02.35, follow the below steps to fix the issue:

    *The microG has some incompatibility issue with YT Vanced v16.02.35, hence the signing issue.

    1. Disable/Uninstall Chrome for Android.
    2. Uninstall MicroG, YT Vanced, YT Vanced Music
    3. Using the Vanced Manager install the Latest microG v0.2.16.204713
    4. Now install YT Vanced v15.43.32
    5. Open YT Vanced and signing.
    6. Now you can update YT Vanced or YT Vanced Music.

    Tested on Oneplus 6T ♥
    1
    Yes

    Everything is up to date

    But still the error

    Is this because of the PE Rom
    I'm also using vanced on this rom, so it's not possible. Try re installing (make sure to remove microg as well)
    1
    Did the same

    Using Vanced Manager
    To do so
    But the shows the same error
    then your last chance is trying to install Vanced with Root... i don't have any issues with that way
    1
    Tested from a diff device but why don't you try this fix
    Indeed it works

    Disabled all the Google apps and services

    Followed the above steps

    And at last click "Huawei" instead of "Sign in"

    Thanks
  • 48

    GtwTyCR.png

    PixelExperience for Redmi Note 10 [mojito/sunny]

    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.0



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


    Known issues
    Nothing

    HOW TO FLASH PE
    Guide

    DON'T FLASH GAPPS, ALREADY INCLUDED
    Download


    Donate
    Liked my work? Give me a beer

    Translation
    Help with project translation

    Stay tuned
    Our Telegram channel


    14
    Update (25/09/21):

    Changelog:
    • Fixed libperfmgr nodes crash
    • Added power stats moke service hals
    • Smarter decisions on whether to use 2/5Ghz AP
    • Disabled wifi firmware logging
    • Disabled NUD failure occurs logging
    • Added stock permission for hwcomposer service
    • Fixed ueventd permissions crash
    • Switched to multihal sensor service hal to 2.1
    • Enabled Wi-Fi hals power saving
    • Switched to Codec2 by default
    • Enabled Codec2 input surface
    • Enabled dalvik dex2oat64
    • Fixed props crashes in logs
    • Added minimal xiaomi parts
    • Fixed SDM and ultrasound_extn crashes
    • Fixed whatsapp mic delay or crashes
    • Improved overall system performance
    • Mic issue is fixed other variant
    11
    Source Changelog:
    • September security patch
    • Updated translations
    • Fixed safetynet
    • Others fixes

    Device Changelog:
    • Decommonized display color modes
    • Dropped useless soundtrigger
    • Updated WI-Fi display blobs from CAF
    • Defined OEM fast charge sysfs node
    • Set voice call volume steps to 10
    • Addressed more sepolicy rules
    • Added Xiaomi mlipay service blobs
    • Added Alipay and WeChat fingerprint payment support
    • Updated USB init configs from CAF tag
    • Added missing usb props
    • Switched to old touch FW
    • Updated device cutout corners
    • Dropped useless/unused blobs
    • Fixed touch issue
    • Fixed wifi display cast
    • Fixed thermal crash
    • Fixed Whatsapp/third party apps volume controls
    • Improved kernel optimization
    • Rest I forgot
    10
    ZIDAN44 is not active on XDA since the end of May. Must be some personal problems. If his health permits, I'm sure he'll be back again. This kind of work is also a personal interest and pleasure of every developer. The only question is whether he will continue his original work.
    Ha ha.. Updates will come soon.. :D
    9
    Update (22/9/21):

    Changelog:
    • Bring back full stack of audio ACDB
    • Update blobs from V12.5.3.0.RKGMIXM
    • Added main display cutout overlays
    • Fixed dimens values for display cutout
    • Updated brightness overlay configs
    • Added camera cutout ring like memeui
    • Removed virtual framebuffer cmdline
    • Labeled some more wakeup nodes
    • Switched to aosp WiFi Display
    • Mic issue is fixed other variant