Develop Bugs

[CLOSED][ROM][UNOFFICIAL][9.0][Daredevil] Pixel Experience [2019/11/28]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
PixelExperience for Nokia 7.2 [Daredevil]
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 9.0
Whats working?
Ril
Wifi
Mobile data
Double tap to wake
Double tap to sleep
Adaptive brightness
Dark theme
Ambient display
Flash light
Sound / vibration
Camera
Volte
Fingerprint
Known issues
comment below if you face any bugs
DON'T FLASH GAPPS, ALREADY INCLUDED
Installation procedure
Note - I don't recommend you people to flash any other custom kernels on this ROM untill Nokia release kernel sources. Because this ROM supports only stock kernel .
1. Download Rom.zip , Perf-Stock-9.0-DDV_sprout.zip , twrp.img & vbmeta.img
2. power off your phone boot in to bootloader mode and flash twrp
3. Boot in to Twrp
4. Format data by typing yes
5. Wipe everything
6. Flash rom.zip
7. Now tap on reboot and tap on recovery now your phone reboots in to twrp again
8. Tap on reboot and check your current active slot.
Example - if twrp shows current active slot A change to B if B change to A
9. Now flash Perf-Stock-9.0-DDV_sprout.zip
10. Wipe all except system & vendor
11. Tap on reboot bootloader
12. Now your phone boots in to bootloader mode
13. Now open cmd in pc flash vbmeta using this command
for slot-a > fastboot flash vbmeta_a --disable-verity --disable-verification vbmeta.img
for slot-b> fastboot flash vbmeta_b --disable-verity --disable-verification vbmeta.img
( thanks to @singhnsk for this step )
14. now type fastboot reboot
and wait for 3 min rom will boot up
Credits
* Pixel Experience & CO (For Source Code)
* All the authors in my git sources
* Nokia For Prebuilt Vendor & Kernel Source
* Moderators (For Giving Freedom To Post Threads)
* My entire Nokia 7.2 community Thank you all for your massive support Again
Join Nokia 7.2 Community ​
​
Download Rom
Download Stock Pie kernel
Download vbmeta
Download Official Twrp
Android OS version: 9.0.0_r47
Security patch level: November 2019
Build author: Raghu varma
My build script: https://github.com/RaghuVarma331/scripts
Kernel Source code: https://github.com/RaghuVarma331/android_kernel_nokia_sdm660
Source code: https://github.com/PixelExperience
​

reserved

I was going to give this a go and see how folks liked it. Any feedback yet?

jumpup said:
I was going to give this a go and see how folks liked it. Any feedback yet?
Click to expand...
Click to collapse
I used it for about an hour and it felt snappier than stock

I'm now having the infamous issue where the Wifi toggle switch. When Wifi is enabled, it immediately disables.. I believe this is because I need to perform another session following instructions to the absolute letter.
Fortunately, I always make a TWRP image along with Titanium Backup sets, copied externally, before testing.
Is there any reliable means to resolve this pervasive wifi bug?

jumpup said:
I'm now having the infamous issue where the Wifi toggle switch. When Wifi is enabled, it immediately disables.. I believe this is because I need to perform another session following instructions to the absolute letter.
Fortunately, I always make a TWRP image along with Titanium Backup sets, copied externally, before testing.
Is there any reliable means to resolve this pervasive wifi bug?
Click to expand...
Click to collapse
I'm having this same wifi issue with stock image. It has appeared since September update. Also faced same kind of problem with bluetooth but it disappeared after December update.

Richard Lamm said:
I'm having this same wifi issue with stock image. It has appeared since September update. Also faced same kind of problem with bluetooth but it disappeared after December update.
Click to expand...
Click to collapse
I've found a method to permanently resolve it, so long as the modified monthly image matches that of the ROM. Let me know if you'd like a write-up.

jumpup said:
I've found a method to permanently resolve it, so long as the modified monthly image matches that of the ROM. Let me know if you'd like a write-up.
Click to expand...
Click to collapse
The issue dissappeared for now after Google's security patch for January 2020 (build 00WW_1_400). Hope so that it won't come back:fingers-crossed:

doubts of installing
I am planning to install this Pixel Experience ROM to my Nokia 7.2, i just want to know the latest info about the ROM like today, cuz i'm having doubts to install it, maybe cuz it will not run or work properly (newbie to this kind of thing)

Paranoid Android Quartz 4 - OnePlus 7T Pro

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
We are very excited to announce the release of Paranoid Android Quartz, based on Android 10.
On the first launch, you’ll notice a clean setup with a beautiful wallpaper from Hampus Olsson, who teamed up with us again to create several beautiful pieces of artwork. Hampus is a multi-disciplinary artist whose design stands for itself and we’re glad to have him onboard. We also added further UI touches that we believe enhance the overall user experience. You can find all of the Paranoid Android wallpapers and many more in the Abstruct app, included in our builds.
Our builds are based on the Code Aurora Forum Android base, which is optimized for Qualcomm platforms and has a higher degree of performance, battery life, and functionality compared to the Android Open Source Project platform. The Paranoid Android team and contributors are focusing on squashing existing bugs, and implementing and improving features, performance, and stability. We are dedicated to providing a user experience with the stability that you can expect from stock ROMs with best-in-class performance and features to help you get the most out of your device.
Device-specific issues
You tell me.
Note: Custom kernels are NOT supported!
Requirements
Make sure you've latest Stable firmware flashed on both the slots before flashing the ROM.
Download
Get the latest OnePlus 7T Pro build from here
Changelogs
Keep an eye on our Twitter account, @paranoidaospa, as we will be posting about new features getting included in the release builds, as well as links to betas for those devices that will get them.
Paranoid Android Quartz released
Instructions
This device runs under OxygenOS vendor, make sure you are coming from OxygenOS 10.0.7.0 or newer before flashing PA.
You can use the updater if you are already on Paranoid Android
Unzip the rom package
Flash the images inside the packages by opening a terminal and run the following commands inside the folder
Code:
fastboot reboot fastboot
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash system system.img
fastboot flash product product.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot reboot
** Format userdata by running the following command
Code:
fastboot -w
** Only required for the first flashing, and maybe optional.
Important / Useful links
Paranoid Android Twitter
Paranoid Android Channel (Telegram)
Paranoid Android Community (Telegram)
Kernel Source
from Arter97
Help us improve PA by submitting detailed bug reports with logs. Learn how to take logs here.
Cheers and #StayParanoid!
XDA:DevDB Information
Paranoid Android Quartz 4 - OnePlus 7T Pro, ROM for the OnePlus 7T Pro
Contributors
33bca, kessaras
Source Code: https://github.com/AOSPA
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: V10.0.7.0
Version Information
Status: Stable
Current Stable Version: 4
Stable Release Date: 2020-06-08
Created 2020-04-26
Last Updated 2020-07-23

FAQ
My device doesnt boot
- Follow the instructions and it will

Changelog
Quartz 4
- Added support for only dim FOD icon(fixes random screen flickers)
- Updated arter's kernel to r58
- Improved adaptative brightness
- Fixed AAC codec support(finally!)
- Smoothness improvements
Quartz 3
- June security patchset and Pixel Feature Drop 3.
- Improved Fingerprint On Display functionality.
- New clear all notifications button.
- Multi-user support.
- Data Switch tile.
- New accent colors.
- Fixed lockscreen adjustments for devices without FOD.
Quartz 2
- Initial release
Quartz 1
- We didn't release there

# Reserved 3

THANK YOU!!! :highfive:
#spamthanks

Awesome to see! Currently backing up my apps and will flash as soon as possible.
Thanks!
Sent from my OnePlus7TPro using XDA Labs

Thank you so much!! DOWNLOADING...

Any chance this will work for the TMobile 7t pro McLaren?

lendawg said:
Any chance this will work for the TMobile 7t pro McLaren?
Click to expand...
Click to collapse
It may but no RIL and most probably Wi-Fi...

Amazing rom, verte fast and smooth

Happy to know the OP7T Pro custom ROM scene finally lifting off - will have a nice choice of ROMs now.
Features of this ROM please....?
(AOSP-based I assume)

My device is stuck on "Waiting for any device" after executing fastboot reboot fastboot. I can see device in device manager, updated adb / fastboot and tried changing ports.
Anyone knows how to resolve this?
I can see the device in regular fastboot, bot not in fastbootd.
EDIT: I think i fixed it, will flash and see

Patched boot.img
I´ll try to keep this folder updated! :good:

Lossyx said:
My device is stuck on "Waiting for any device" after executing fastboot reboot fastboot. I can see device in device manager, updated adb / fastboot and tried changing ports.
Anyone knows how to resolve this?
I can see the device in regular fastboot, bot not in fastbootd.
EDIT: I think i fixed it, will flash and see
Click to expand...
Click to collapse
With your device turned on and connected through USB, type "adb reboot fastboot"

FSadino said:
With your device turned on and connected through USB, type "adb reboot fastboot"
Click to expand...
Click to collapse
Yep, I managed to fix it now Just flashed and booted, will spend rest of the night to explore the features and restore my apps.
Thanks!

Afther flasing it just boots back into fastboot, cant boot into system...

RicardoDimm said:
Afther flasing it just boots back into fastboot, cant boot into system...
Click to expand...
Click to collapse
Try flashing everything again, it worked for me then.

FSadino said:
Patched boot.img
I´ll try to keep this folder updated! :good:
Click to expand...
Click to collapse
great bro!! can you recommend some essential modules please.

Lossyx said:
Try flashing everything again, it worked for me then.
Click to expand...
Click to collapse
I did. Still no luck...

RicardoDimm said:
I did. Still no luck...
Click to expand...
Click to collapse
Do exactly as described:
With device turned ON and connected to PC type:
abd devices
abd reboot fastboot
fastboot -w
adb reboot fastboot
Flash all .img files in PA folder
Example: "fastboot flash boot boot.img"
Edit: I assume you have Platform-Tools and running your commands inside platform tools folder!
---------- Post added at 09:36 PM ---------- Previous post was at 09:30 PM ----------
GinoTonny said:
great bro!! can you recommend some essential modules please.
Click to expand...
Click to collapse
I don't use magisk modules

[KERNEL] EvilKernel to work properly with Nethunter and Andrax

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I am not responsible for using my kernel with bad intentions, the kernel only serves to test my network and devices.
Click to expand...
Click to collapse
Status: Beta
Developer: mozahist228
Kernel for Linux version: 4.9.226
Spoiler: Features
Generic IEEE 802.11 Networking Stack (mac80211)
HCI USB driver
HCI VHCI (Virtual HCI device) driver
USB RTL8150 based ethernet device support
Realtek RTL8152/RTL8153 Based USB Ethernet Adapters
Multi-purpose USB Networking Framework
CDC NCM support
OTG support
USB Wireless Device Management support
USB 2.0 OTG FSM implementation
USB Modem (CDC ACM) support
Atheros Wireless Cards
Linux Community AR9170 802.11n USB support
Ralink driver support
Spoiler: Note
Put it through TWRP. If necessary, then flash magisk because with the installation of the kernel, it will be erased.
Only for Lineage OS-based firmwares
Spoiler: Bags
Working with the Bluetooth interface is not available
Spoiler: Screenshots
Spoiler: Download
GoogleDisk
Source code: GitHub

Just created an account to say thanks! This worked for me. I've been trying for the last week to get Nethunter to recognize my Wi-Fi USB adapters, and I think this package is what did it.
If anybody is curious, these are the steps I took
fastboot into TWRP, format everything/factory reset
in TWRP, adb sideload the new Lineage 18.1 ROM from this thread
still in TWRP, adb sideload the custom kernel OP posted
mozahist228 said:
Spoiler: Download GoogleDisk
Click to expand...
Click to collapse
Boot up Lineage OS, run through initial setup
Reboot back into recovery, use TWRP to sideload OpenGApps (optional) if you're going to do this, you *have* to get OpenGApps from this page, as their support for Android 11 is still in beta
use TWRP to sideload Magisk
use TWRP to sideload the Generic ARM64 Nethunter image from this page (or direct download by clicking me)
Boot back into Lineage, run the Nethunter app and ensure chroot is working properly (mine wasn't I had to do a bit of futzing around with it, but this was my own fault)
Finally, open the Magisk Manager app, go to the modules tab, search for and install "Wireless Firmware for Nethunter". Do *not* install the "KaliNethunter" module, as this continually caused problems for me.
I don't know if this is the best order to do it in, I'm very new with Android stuff, but just thought I'd share what worked for me. Thanks again OP!

Finally some Nethunter kernel for this device, Would love to see the feature : Monitor Mode on the SoC (SD625)

rubrex said:
Finally some Nethunter kernel for this device, Would love to see the feature : Monitor Mode on the SoC (SD625)
Click to expand...
Click to collapse
At the moment this is impossible, any patches do not work, and my knowledge is not enough to expand the driver's functionality

So, there is just usb adapters support with no monitor mode, or mode is available for external adapters? Anyway thanks for any movements to the right way!

mr.onegin said:
So, there is just usb adapters support with no monitor mode, or mode is available for external adapters? Anyway thanks for any movements to the right way!
Click to expand...
Click to collapse
I think this is all you wanted to see)

Are you planning to add HID support?

Firerust said:
Are you planning to add HID support?
Click to expand...
Click to collapse
It is already present

mozahist228 said:
It is already present
Click to expand...
Click to collapse
It doesn't work for me, using pelya's app to test HID feature

Firerust said:
View attachment 5219973
It doesn't work for me, using pelya's app to test HID feature
Click to expand...
Click to collapse
I don’t think it was adapted for new kernel versions.

mozahist228 said:
I don’t think it was adapted for new kernel versions.
Click to expand...
Click to collapse
Even last version of Rucky which was updated on 2020 doesn't work, it says kernel does not support HID, does this feature work for you?

Firerust said:
Even last version of Rucky which was updated on 2020 doesn't work, it says kernel does not support HID, does this feature work for you?
Click to expand...
Click to collapse
If you do not know the basic things then you should not go into this field

mozahist228 said:
If you do not know the basic things then you should not go into this field
Click to expand...
Click to collapse
Yeah you're right, just looking at your source I realized you have no idea of what I'm referring to, since f_hid.c hasn't been modified. Thanks anyway.

Firerust said:
Even last version of Rucky which was updated on 2020 doesn't work, it says kernel does not support HID, does this feature work for you?
Click to expand...
Click to collapse
I got Rucky to work, however I eventually had to reflash my device because it wouldn't boot up. Even before that, it would routinely take 5+ minutes to boot with this kernel installed. Not sure if this kernel is to blame or something Nethunter related.

Firerust said:
Yeah you're right, just looking at your source I realized you have no idea of what I'm referring to, since f_hid.c hasn't been modified. Thanks anyway.
Click to expand...
Click to collapse
He shouldn't have been changed

lmfao, so you literally got sleepy, kanged the defconfig + the commits you advertise as features. At least put proper authorship lmfao + no mention of lacia anywhere. NIce job sir

And FYI the sleepy source you used as a base is old af, newer one is in https://github.com/Couchpotato-sauce/kernel_xiaomi_sleepy

forsalebypwner said:
Just created an account to say thanks! This worked for me. I've been trying for the last week to get Nethunter to recognize my Wi-Fi USB adapters, and I think this package is what did it.
If anybody is curious, these are the steps I took
fastboot into TWRP, format everything/factory reset
in TWRP, adb sideload the new Lineage 18.1 ROM from this thread
still in TWRP, adb sideload the custom kernel OP posted
Boot up Lineage OS, run through initial setup
Reboot back into recovery, use TWRP to sideload OpenGApps (optional) if you're going to do this, you *have* to get OpenGApps from this page, as their support for Android 11 is still in beta
use TWRP to sideload Magisk
use TWRP to sideload the Generic ARM64 Nethunter image from this page (or direct download by clicking me)
Boot back into Lineage, run the Nethunter app and ensure chroot is working properly (mine wasn't I had to do a bit of futzing around with it, but this was my own fault)
Finally, open the Magisk Manager app, go to the modules tab, search for and install "Wireless Firmware for Nethunter". Do *not* install the "KaliNethunter" module, as this continually caused problems for me.
I don't know if this is the best order to do it in, I'm very new with Android stuff, but just thought I'd share what worked for me. Thanks again OP!
Click to expand...
Click to collapse
when i choose kali in the terminal, it just crashes, any idea on how to fix that?

Don't stop this project please, you are the one who delivered this "special" kernel!

Hello! I installed everything right. I tried a lot of variations. But when i boot into the system it shows the kali icon for a sec and then nothing visible its just a black screen. it reacts to the side buttons. This problem is only happen when i install nethunter on it, the kernel the lineageOS and the magisk is working properly.
Please help! I working on this for a very long time and i cant fix it.
Thanks in advance

[SODP][ROM][AOSP] SonyAOSP 13 [Alpha]

The Sony Open Devices Project is always happy about volunteers (coding, testing, etc)
Also mainlining your favorite snapdragon powered xperia device into the mainline kernel is possible and we will be glad to help you!
Official site
Unofficial site
Source Code
Code:
#include <std_disclaimer.h>
/*
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
This is the AOSP ROM for the Sony XZ2C (apollo)
This ROM build will always mainly based on Sony AOSP Code and maybe include cherry-picks.
I plan to make monthly builds, after a new security patch level, if there is no need for a critical hotfix.
FAQ:
fastboot & adb
https://developer.sony.com/develop/open-devices/get-started/flash-tool/useful-key-combinations/
https://wiki.lineageos.org/adb_fastboot_guide.html
https://developer.android.com/studio/releases/platform-tools
Stuck at SONY logo? Maybe you need to flash the OEM binary to oem_a and oem_b, while just oem is not enough.
Bugtracker:
SODP Bugtracker -> If you think the problem is in SODP
My Bugtracker -> If you think the problem is in my implementation
Bugreport:
A bugreport needs
Code:
logcat -b all
and a way to reproduce the issue.
A crash of the system requires the content of the /sys/fs/pstore folder as bug report
Be aware that a second reboot erases this folder
A crash to the recovery partition requires additionally the content of the /dev/block/by-name/misc partition
You get the content via `cat /dev/block/by-name/misc partition > /path/to/output/file.txt`
To rescue a not responding phone:
VOLUP+POWER for 3 Seconds -> RESTART with one Vibration.
VOLUP+POWER for 20 Seconds -> SHUTDOWN with 3 Vibrations.
VOLUP+POWER+CAMERA for 30 Seconds -> HARDWARE SHUTDOWN by discharging a capacitor.
Thank you very much for your help, code contribution & testing! (Random order):
@jerpelea, the sony employees and their volunteers (people like you and me) coding this wonderful piece of software
@dhacke for providing a download server
And many thanks to the few donators!
A telegram group for technical SODP stuff:
https://t.me/xda_tv

Download & Installation
Download ROM:
Android File Host
FTP-Server from @dhacke
Download Drivers:
OEM (Tama) binaries
GCAM Camera App:
GCAM Issue
Suggested GCams
Installation with a recovery:
fastboot flash oem _a oem_*.img (Only needed until the device receives mainline support by SODP)
Flash the ROM in a recovery
Reboot into recovery just to make sure you're on the new slot
OpenGapps (Requires TWRP or a custom ROM recovery)
Dual Sim Patcher (Requires TWRP or a custom ROM recovery)
(In case a modification prevents your device from booting) fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Flash the ROM without a recovery:
Extract the payload.bin from the .zip file
Extract the .img files with the Playload Dumper
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot -w (Wipes your internal storage and the userdata; only if needed)
Now you got the AOSP recovery, to please continue with the normal installation
fastboot flash oem_a oem_*.img (Only needed until the device receives mainline support by SODP)
fastboot flash vendor vendor.img
fastboot flash system system.img

News
07.10.2022
android-13.0.0_r7 (October security patchlevel)
Click to expand...
Click to collapse
OTA.zip generation is working again
Click to expand...
Click to collapse
08.09.2022
android-13.0.0_r4 (September security patchlevel)
Click to expand...
Click to collapse
06.09.2022
android-13.0.0_r1 (August security patchlevel)
Click to expand...
Click to collapse

Is there a stock camera app? Is it possible to record 60 fps videos?

Hi,
I installed AOSP 13 successfully, but after starting display don´t respond to touch, any solution?

07.10.2022
android-13.0.0_r7 (October security patchlevel)
Click to expand...
Click to collapse
OTA.zip generation is working again
Click to expand...
Click to collapse

Good news! I was not able to boot a single of the 12 versions, but Android started with your last build!
On my model the vbmeta line was needed:
```
fastboot --disable-verity --disable-verification flash vbmeta vbmeta
```
Touch screen is working, I'll check the rest later.

That sounds great, just tried it myself but on my device still touch is not working!
Which model do you have exactly? Which build did you install and which binaries?

bluep said:
That sounds great, just tried it myself but on my device still touch is not working!
Which model do you have exactly? Which build did you install and which binaries?
Click to expand...
Click to collapse
SW_binaries_for_Xperia_Android_12_4.19_v3a_tama.img
aosp-13-20221007_apollo.zip
I don't have the details here but my phone is a dual sims one from Europe.

Ok, same model here and I also used the same binaries and ROM. Unfortunately it doesn't have a working touch for me... :-(

Is it worth to switch from LOS 20 SonyAOSP 13? I have issues with my RAM, it looks like I'm constantly running out of RAM even if there aren't any Apps running in Background (Developer Tools -> Active Processes) :/
EDIT: Or shall I revert to Android 12 or older in generall because maybe Android uses too much RAM?

DrTrax said:
Is it worth to switch from LOS 20 SonyAOSP 13? I have issues with my RAM, it looks like I'm constantly running out of RAM even if there aren't any Apps running in Background (Developer Tools -> Active Processes) :/
EDIT: Or shall I revert to Android 12 or older in generall because maybe Android uses too much RAM?
Click to expand...
Click to collapse
Oh, I thought it was just me.
Since LOS 19 I also have the problem that the RAM gets full and the device slows down.
LOS20 after a full wipe has the same problem.
And I use the 6GB Ram edition.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
About SODP we need to wait for the OEM A13 binary or mainline to boot the device.
I don't know the release date.
Maybe the next time they release new binaries.

MartinX3 said:
Oh, I thought it was just me.
Since LOS 19 I also have the problem that the RAM gets full and the device slows down.
LOS20 after a full wipe has the same problem.
And I use the 6GB Ram edition.View attachment 5850687View attachment 5850691
About SODP we need to wait for the OEM A13 binary or mainline to boot the device.
I don't know the release date.
Maybe the next time they release new binaries.
Click to expand...
Click to collapse
German BOI, läuft alter
YOU ALSO HAD ISSUES WITH RAM ON LOS 19?!?!
Holy moly and I was deleting, wiping, changing this and that and still f-ed up everything!
What does it mean, we need to wait for OEM A13 binary? Does it mean that Sony is kinda still compiling code for the XZ2 devices but not the full ROM?

DrTrax said:
German BOI, läuft alter
YOU ALSO HAD ISSUES WITH RAM ON LOS 19?!?!
Holy moly and I was deleting, wiping, changing this and that and still f-ed up everything!
What does it mean, we need to wait for OEM A13 binary? Does it mean that Sony is kinda still compiling code for the XZ2 devices but not the full ROM?
Click to expand...
Click to collapse
That are the closed source hardware drivers until the device is fully supported by the mainline kernel.
I don't know the ETA for the next OEM binary release, but I'm preparing a new SODP 13 build.

MartinX3 said:
That are the closed source hardware drivers until the device is fully supported by the mainline kernel.
I don't know the ETA for the next OEM binary release, but I'm preparing a new SODP 13 build.
Click to expand...
Click to collapse
Sounds really great! I hope the memory issue get finally fixxed, I mean...
The Benchmarks with Antutu are still pretty good but cmon Sony... it's so sad that this device with 4GB memory suffers a lot and to be honest, it's size is perfectly for me!

Since SODP and LOS are different, they mostly don't share issues.
So you might get different issues on SODP.

MartinX3 said:
Since SODP and LOS are different, they mostly don't share issues.
So you might get different issues on SODP.
Click to expand...
Click to collapse
Hmmmm.... shall I dirty flash from LOS to SODP? I mean, you still call that ROM alpha which implies that it isn't perfect as a daily driver ^^

DrTrax said:
Hmmmm.... shall I dirty flash from LOS to SODP? I mean, you still call that ROM alpha which implies that it isn't perfect as a daily driver ^^
Click to expand...
Click to collapse
You need a fullwipe and beta isn't perfect as a daily driver.
You're lucky if alpha boots on your device all the time.

Hello thanks for the images !
I installed the rom but it doesn't have a working touch. Otherwise I see the lock screen and can use the volume butons. What should I do?

MartinX3 said:
That are the closed source hardware drivers until the device is fully supported by the mainline kernel.
I don't know the ETA for the next OEM binary release, but I'm preparing a new SODP 13 build.
Click to expand...
Click to collapse
Any news when you compile new SODP 13 build? Should touch work with the current build? Any major bugs know?
Thanks in advance!

Development [13][ROM][sGSI][CWAI+][Exynos2200] Pixel Experience Plus

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Pixel Experience Plus "s"GSI
DISCLAIMER
I am not to be held responsible for any damage that might come to your device while trying to install or using this rom. This is your own responsibility.
What is this?
Pixel Experience is an AOSP based ROM with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, boot animation)
Their 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 13
What makes these builds different from other GSIs and especially, what makes it different from the already-existing PE GSI builds?
- Fixed Auto-Brightness
- Fixed the microphone in video recording by default
- Fixed Adaptive Refresh Rate
- "Fixed" the green tint in low-lit environments by enforcing 120Hz during those times
- AOD is enforced to use the lowest available refresh rate
- Added MIN/MAX Refresh Rate options within Phh Settings
- Reverted the QS look to the actual Pixel one
- S22-relevant settings in Phh Settings are enabled by default
What is working?
Everything not listed under broken things.
What is NOT working?
- WiFi Direct
- 5G
- VoLTE
Known issues
- proximity sensor (it works - the screen will lock if you put the phone near your face while in a call but you have to wake the phone yourself afterwards)
- WiFi Hotspot (it has been fixed in the latest release of Loki kernel)
- RIL signal occasionally misbehaves once after a couple reboots(keep toggling airplane mode until it goes back to normal, this is a general TD GSI issue ATM and you have to do this once per boot in the rare cases when it does occur)
- Video recording is capped at [email protected] (thank Samsung for this)
Instructions
If you're new to this, visit THIS LINK
For the front camera to work in Google Camera ports, it's advised to flash the CWAI firmware or newer.
Do keep in mind that with that firmware (or BVJA, which was before CWAI), Samsung added anti-rollback so you won't be able to downgrade to A12.
1. Extract the .xz file
2. Reboot into recovery
3. Perform a Factory Reset
4. Boot into fastboot (you need a patched recovery for this, follow THIS GUIDE
5.Flash the extracted image with fastboot: fastboot flash system image.img
6. Reboot
Download
Github
MEGA Mirror
Add-ons
LOKI KERNEL
GCam 8.4 port by Shamim
1. Download the apk from HERE
2. Download the .xml config from HERE and copy it to /sdcard/SGCAM/XML (Thanks to Es Jot for the config)
3. Download the lib from HERE and copy it to /sdcard/SGCAM/LIB
4. Install the .apk, double-click between the shutter and gallery icons
5. Import the config
AGC Camera
1. Download the apk from HERE
2. Download the configuration from HERE
3. Install the apk
4. Import the config by choosing More Settings > Configs > Import
5. Go back to the camera view, press the top arrow and choose Load Config
Telegram
Samsung Galaxy S22 Exynos GSI Group
Translation
Help with project translation
Blog
Pixel Experience
Donate
jhenrique09
phhusson
AndyYan
eremitein
kdrag0n
ponces​
Build author: Jeik
Source code: PixelExperience
Device source code: device_phh_treble
ROM developer: jhenrique09
Contributors: Pixel Experience Team, phhusson, AndyYan, eremitein, kdrag0n and ponces

thanks for your work！but i am wondering that does it work on snap？

It's nice, but mobile network keep disconnecting and Bluetooth audio don't work

yzuunk said:
It's nice, but mobile network keep disconnecting and Bluetooth audio don't work
Click to expand...
Click to collapse
okay，can this problem be fixed？i want，to use gsi on my s22 snap daily

yzuunk said:
It's nice, but mobile network keep disconnecting and Bluetooth audio don't work
Click to expand...
Click to collapse

New build up.
Changes:
- BT audio should now work fine
For those on the previous build and with the mentioned issue, toggle the following option within Phh Settings > Misc

Jeik said:
New build up.
Changes:
- BT audio should now work fine
For those on the previous build and with the mentioned issue, toggle the following option within Phh Settings > Misc
View attachment 5895743
Click to expand...
Click to collapse
hey，nice to see you，does this rom work on snap s22?

Loving this rom

Daniel Dumile said:
Loving this rom
Click to expand...
Click to collapse
I love this very much,just do not know whether it works on my snap s22

huahuaa said:
hey，nice to see you，does this rom work on snap s22?
Click to expand...
Click to collapse
It will maybe boot but the fixes are pretty much exclusive to the Exynos variant of the S22, meaning you'll have the exact same bugs as you'd have with any other GSI if you flashed it on your SD variant.
In any case, I have absolutely no plans to try making it work on SD variants.

What a shame, but thanks to developers like you for their hard work, I just hope someone can do it, I can help test the system related issues, and I can also provide some donations, though not much

Jeik said:
It will maybe boot but the fixes are pretty much exclusive to the Exynos variant of the S22, meaning you'll have the exact same bugs as you'd have with any other GSI if you flashed it on your SD variant.
In any case, I have absolutely no plans to try making it work on SD variants.
Click to expand...
Click to collapse
What a shame, but thanks to developers like you for their hard work, I just hope someone can do it, I can help test the system related issues, and I can also provide some donations, though not much

How would one root with magisk ?

Hello !
I installed via Odin the Stock Rom "S901BXXS4CWD3_S901BOXM4CWCH_EUX" (latest for Europe).
Patch Recovery.img and install IMG via fastboot, and I have a bootloop, any idea?

sHnouL said:
Hello !
I installed via Odin the Stock Rom "S901BXXS4CWD3_S901BOXM4CWCH_EUX" (latest for Europe).
Patch Recovery.img and install IMG via fastboot, and I have a bootloop, any idea?
Click to expand...
Click to collapse
ya Must after Flash Recovery at First start Boot in Recovery so ya can Wipe Userdata and then ya can Start the System!!! Hope It helps, when not ya must Flash StockROM and Try Again!!And when ya Patch Recovery IMG ya must start Recovery Mode to have Root Rights in System, and than ya have no Recovery!!!

Pixel Experience Team, phhusson, AndyYan, eremitein, kdrag0n and ponces Nice work Guys!!! when ya have the Time can ya Build a LineageOS 20 GSI? or is anybody so nice a Beginner in Szenario Building GSI/ROMs the manifest*.xml make Public than i have Found nothing!!! So the Tutorial on XDA is uncomplete to Build a ROM!!!

New build up.
Changes:
- May security patch
- latest TrebleDroid changes
- offline charging seems to work now (confirmed on base S22, CWAI fw, latest Loki kernel)