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!
Related
/*
* Your warranty is... still valid?
*
* I am 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 me for messing up your device, I will laugh at you.
*
*/
Click to expand...
Click to collapse
Project Treble
Important!
Recommended for installation only for advanced users***What is Project Treble? ***
Project Treble allows to install - Generic System Images on our device with a minimum number of bugs.
Vendor - this is partition where proprietary files and drivers are stored, which are separate from the system.
***Userful Information***
Project Treble XDA Thread
Generic System Image (GSI) list
***Development and bugs***
Development has been started about 3 months. backwards During this time, dozens of errors were corrected and millions of nerve cells were lost.
Vendor is based on the stock firmware UOS273C with a large number of edits.
The kernel is used from vm03 with driver edits for working on Project Treble.
Bugs in Generic System Images:
On Oreo and Pie GSIs don't working SafetyNET.
My Magisk Module: Wileyfox Swift 2 SafetyNet Pass
Bugs in Vendor:
SELinux Permissive
For the fingerprint scanner to work correctly before being added to Settings, it is necessary to “poke” 5-6 times into it, for the driver to load correctly.
***Preparing device for support Project Treble***
Download TWRP Treble
Repartition script 16GB or 32GB
Download Treble Vendor
Download Treble Boot
Mirror on Google Drive
Mirror on Cloud Mail.ru
If you want get back default partition table just flash:
Download Revert - 16GB
Download Revert - 32GB
You need to copy all the necessary information to an external memory card or PC, since the internal memory will be formatted and devided into special partitions for Project Treble can work.
Install TWRP Treble in a convenient way for you.
Install Repartition script in TWRP. Depending on your internal memory size.
After installing repartition script, device will automatically reboot into Recovery, where you must do:
Format Data (Wipe > Format Data)
Wipe Vendor (Wipe > Advanced Wipe > Vendor)
After that necessarily to reboot the Recovery (Reboot > Recovery)
Flashing Treble Vendor (Just install zip archive)
Flashing Treble Boot (Select the option in the lower right corner Install Image, select Boot_Treble_new.img and flash it as Boot Image)
Install your favorite firmware (about this below). (Select the option in the lower right cornerInstall Image, than flash it as System Image)
***Installing Android Oreo or Android Pie GSIs***
Flash any GSi from Generic System Image (GSI) list or XDA Thread
always choose arm64 A-ONLY!
* If camera don't working on Pie flash:
Camera Pie GSI patch
* If the NFC item in the settings hangs, or the NFC does not turn on (this is usually the case in the old October GSI), flash:
NFC all GSI Patch
* Patch for fix fingerprint scanner on some Pie GSIs
Folder with patches
For ArrowOS GSI, HavocOS 2.0, AEX 6.1 fix not needed.
***Google Apps***
Install GApps only before the first launch of the ROM!
Open GApps Project
***Thanks***
Testing and moral support:
Kirill_MegaFon (4PDA)
xyzmean (4PDA)
Zent16 (4PDA)
backspace696 (4PDA)
Help in bug fixes and kernel sources:
vm03 (XDA)
Mirrors for download files:
anatoliy-is (4PDA)
Fingerprint overlay:
creativchic (4PDA)
XDA:DevDB Information
[Project Treble][UNOFFICIAL] for Wileyfox Swift 2/Plus/X, ROM for the Wileyfox Swift 2
Kernel Sourses
DevelopedInside
Contributors
fx-mod
ROM OS Version: Android 8.1.x and Android 9.x
Version Information
Status: Beta
Created 2018-09-30
Last Updated 2018-09-30
Never heard of 'Project Treble' before, but it sounds very interesting to be able to use 'Generic System Images'.
Before playing around with it - can you please also provide a 'Repartition Script' to get back to the default Partitioning ?
fred0r said:
Never heard of 'Project Treble' before, but it sounds very interesting to be able to use 'Generic System Images'.
Before playing around with it - can you please also provide a 'Repartition Script' to get back to the default Partitioning ?
Click to expand...
Click to collapse
To return the phone to stock, just install Factory Firmware.
fred0r said:
Never heard of 'Project Treble' before, but it sounds very interesting to be able to use 'Generic System Images'.
Before playing around with it - can you please also provide a 'Repartition Script' to get back to the default Partitioning ?
Click to expand...
Click to collapse
Done!
i installed treble according to your instruction and flashed a AOSP 8.1 image (system-arm64-aonly-gapps-su.img.xz) which should include gapps and su.
unfortunately the su-part wasnt available, so i tried to boot into the recovery by selecting it during the start of the phone - but i instantly came back to the 'boot-screen' without starting twrp.
for now the only way to get back on the 'treble-twrp' i need to boot it via fastboot (fastboot boot TWRP_Treble_marmite.img)
i this a bug or am i doing something wrong ?
[edit]
installed another rom which had the option in developers to reboot directly into the recovery - that worked.
---------- Post added 5th October 2018 at 12:12 AM ---------- Previous post was 4th October 2018 at 11:43 PM ----------
Now i installed the latest Oreo Resurrection-Remix from https://downloads.resurrectionremix.com/arm64aonly/ and during startup:
{
"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"
}
Another thing is, that on all GSI-Images i installed so far the system-fonts are very tiny - like it's using a too high screen-resolution.
fred0r said:
......so i tried to boot into the recovery by selecting it during the start of the phone - but i instantly came back to the 'boot-screen' without starting twrp.
for now the only way to get back on the 'treble-twrp' i need to boot it via fastboot (fastboot boot TWRP_Treble_marmite.img)
i this a bug or am i doing something wrong ?
Click to expand...
Click to collapse
Nevermind - it works also to boot from the start. i needed first to select 'boot recovery' and then press on 'start' to boot into it.
Just installed the GSI from PixelExperience from pixelexperience.org and also get that 'vendor mismatch' message.
fred0r said:
Nevermind - it works also to boot from the start. i needed first to select 'boot recovery' and then press on 'start' to boot into it.
Just installed the GSI from PixelExperience from pixelexperience.org and also get that 'vendor mismatch' message.
Click to expand...
Click to collapse
I had this issue too and I believe flashing the vendor zip again did the job for me, not completely sure though.
xXxSAMIxXx said:
I had this issue too and I believe flashing the vendor zip again did the job for me, not completely sure though.
Click to expand...
Click to collapse
vendor miscmatch message is a warning. Not an error!
a great work ..soon i will get this device
I'd like to try out Android P. Has anyone tried this with a Swift 2 device and can recommend a GSI to use?
Edit: I couldn't get Pixel Experience (9.0) to boot succesfully but phhusson's AOSP 9.0 works. It's very barebones indeed. Someone made an overlay that makes adaptive brightness possible but I still can't adjust the LED for notifications. Not being able to turn off the charging/low-battery LED is a bummer. Otherwise it runs fine but I'll try a different GSI today.
Did you use the arm64 a-only image? I tried the arm a-only and that wouldn't boot but I'm (quite) happily buzzing along with the former.
fx-mod said:
* Patch for fix fingerprint scanner on some Pie GSIs
Phh AOSP 9 v106 [02/10/2018] only
ArrowOS 9 [23/09/2018] only
Pixel Experience P [20/09/2018] only
Click to expand...
Click to collapse
Is it possible to update the Pixel Experience P fingerprint scanner patch? The latest version of the ROM fixes the hotspot issues but the fingerprint scanner patch does not work.
erasmuswill said:
Is it possible to update the Pixel Experience P fingerprint scanner patch? The latest version of the ROM fixes the hotspot issues but the fingerprint scanner patch does not work.
Click to expand...
Click to collapse
it is done!
wileyfox swift 2X with 32GB storage.
32 gb repartition file ? or should i use 16 gb ?
just to be sure i'm not destroying my phone
waver1967 said:
wileyfox swift 2X with 32GB storage.
32 gb repartition file ? or should i use 16 gb ?
just to be sure i'm not destroying my phone
Click to expand...
Click to collapse
32 GB of course
failed to mount system
after doing all the steps twrp says no os installed
oeps my mistake..
forgot to unrar gsi file
Is it possible to patch at least one of Pie GSI's to work almost perfectly? Right now it is not possible to use any of GSI's for more than a week because every one have some annoying bugs
puszekkk said:
(
Click to expand...
Click to collapse
What does not suit you?
anatoliy-is said:
What does not suit you?
Click to expand...
Click to collapse
Broken hotspot, dumped fingerprints after reboot, broken wifi, broken audio routing :/
{
"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"
}
Note - Iam Not Responsible for bricked devices
About LineageOS
LineageOS is a free and open-source operating system for set-top boxes, smartphones and tablet computers, based on the Android mobile platform. It is the successor to the custom ROM CyanogenMod, from which it was forked in December 2016 when Cyanogen Inc. announced it was discontinuing development and shut down the infrastructure behind the project. Since Cyanogen Inc. retained the rights to the Cyanogen name, the project rebranded its fork as LineageOS.
LineageOS was officially launched on December 24, 2016, with the source code available on GitHub. Since that time, LineageOS development builds now cover more than 185 phone models with over 1.9 million active installs,having doubled its user base in the month February–March 2017 And if you would like to contribute to LineageOS, please visit out Gerrit Code Review.
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 Gapps.zip
10. Now flash Perf-Stock-9.0-DDV_sprout.zip
11. Wipe all except system & vendor
10. Tap on reboot bootloader
11. Now your phone boots in to bootloader mode
12. 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 )
13. now type fastboot reboot
and wait for 3 min rom will boot up
Credits
* LineageOS & 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 Gapps
Download Official Twrp
Android OS version: 9.0.0_r46
Security patch level: October 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/LineageOS
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
Selinux - permissive
Fingerprint
Known issues
All fixed for now . comment below if you face any bugs
FLASH GAPPS MANUALLY
Awesome work.. Great work..!
Thank you. Works good
Works like a charm!! ????
This is just awesome. Thanks for being that fast!
I ordered a Nokia 7.2 as business phone. First thing I'll do is unlock and flash this rom. Wouldn't have ordered without LOS support.
How is the battery life compared to stock? Somebody who is currently using this, could someone pls let know about this? Thanks.
Hey! I guess I messed up... bootloader is unlocked but when I tried to flash with TWRP, for any reason I still having the "original" boot running and now I have no wifi... Any one can provide me a guidance?
JoSoFer said:
Hey! I guess I messed up... bootloader is unlocked but when I tried to flash with TWRP, for any reason I still having the "original" boot running and now I have no wifi... Any one can provide me a guidance?
Click to expand...
Click to collapse
Here twrp file will perform as two ways
Boot & twrp
If you know what exactly a/b partition phone does you won't get this doubt.
Do you HAVE to flash Gapps if you dont want them?
Talon Pro said:
Do you HAVE to flash Gapps if you dont want them?
Click to expand...
Click to collapse
Why? I have been using LineageOS on different devices without Gapps for years. So there is no need to flash them if you don't want them.
Ungewiss said:
Why? I have been using LineageOS on different devices without Gapps for years. So there is no need to flash them if you don't want them.
Click to expand...
Click to collapse
Just checking, oddly, Android is new to me...
Do we need or can we lock the bootloader after to keep the warning showing every time you reboot?
---------- Post added at 10:23 AM ---------- Previous post was at 10:04 AM ----------
BUG- Double tap to wake not working, the slider is set to ON. I tried turning it off and back on and rebooting the phone and that didnt work on this ROM.
Talon Pro said:
Do we need or can we lock the bootloader after to keep the warning showing every time you reboot?
Click to expand...
Click to collapse
Hi, please understand how bootloaders work. The locked bootloader ensures that secure boot is in place and the device will deny to boot if it notes any tampering from the OEM's hashes. So, never lock the bootloader on a custom software - the device will more or less become a brick ?
singhnsk said:
Hi, please understand how bootloaders work. The locked bootloader ensures that secure boot is in place and the device will deny to boot if it notes any tampering from the OEM's hashes. So, never lock the bootloader on a custom software - the device will more or less become a brick
Click to expand...
Click to collapse
All you had to say was "no".
Talon Pro said:
All you had to say was "no".
Click to expand...
Click to collapse
I just tried to explain it a bit.
nvm
Any idea on the DTTW issue?
Will this ROM become official?
BigFatTony said:
Will this ROM become official?
Click to expand...
Click to collapse
Not even interested to follow their rules & regulations towards official tag. Due to i don't know when i will do builds. & I don't know when i will update or bug fixes. completely depends on my schedule So not interested towards official tag & also iam not ready to follow their rules as well.
Main reason - my schedule and my infra
{
"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 the Sony Xperia XZ2 akari
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 10.0
Whats working?
Wifi
RIL
Volte
Mobile data
GPS
Camera
Flashlight
Camcorder
Bluetooth
Fingerprint reader
NFC
Lights
Sound / vibration
Known issues
Sony Open Devices bug tracker
DON'T FLASH GAPPS, ALREADY INCLUDED
Download from Pixel Experience website (Xperia XZ2 Single Sim)
Download from Pixel Experience website (Xperia XZ2 Dual Sim)
Flash instructions and special recovery coming on Monday 24/02/2020
Donate
Liked my work? Give me a beer
Translation
Help with project translation
Stay tuned
Our Telegram channel
Sony Specified Telegram channel
Our blog
Android OS version: 10.0.0_r27
Security patch level: February 2020
Build author/Device Maintainer: fastbooking
Device Source code: https://github.com/PixelExperience-Devices/device_sony_customization
Source code: https://github.com/PixelExperience
ROM Developer: jhenrique09
flash instructions? i think twrp is needed and we currently don't have it
nikkdib said:
flash instructions? i think twrp is needed and we currently don't have it
Click to expand...
Click to collapse
Detailed instructions on Pixel site. There are ROMs for many models, including 8314 and 8324. Yes, it seems that TWRP is needed, and it also seems that someone somewhere has managed to develop one for Q...
********** IMPORTANT: README **********
### Be sure to have the latest ODM, even when you get a OTA!!! ###
To get this ROM and the OTA updater to work fine, you NEED TO follow a few steps:
1. Download Androxyde's FlashTool
2. Flash the latest STOCK firmware for your device, in order to get a
bootloader bugfix for unlocked A/B
3. Before flashing this ROM through your favorite recovery environment,
you *HAVE TO* flash the latest Sony Open Devices binaries for
your device through fastboot. They cannot be distributed in this
zip package because you have to accept their EULA.
** Make sure you flash the Sony ODM image to both slots:
fastboot flash oem_a SW_binaries_for_Xperia_Android_(blahblah)
fastboot flash oem_b SW_binaries_for_Xperia_Android_(blahblah)
P.S.: If you get signature verification errors on TWRP, remember to
disable package signature verification in the TWRP settings!!!
Useful links:
## Androxyde's Flashtool: http://www.flashtool.net/
## Sony ODM binaries:
https://developer.sony.com/develop/open-devices/downloads/software-binaries/
Hey there ! On the previous -beta ish- builds, you have to decompile the zip and all to get the bootimage to flash the zip
Starting monday, I'll distribute a bootimage where you can go to aosp recovery, and flash the rom via sideload.
@Anti-root @nikkdib
fastbooking said:
Hey there ! On the previous -beta ish- builds, you have to decompile the zip and all to get the bootimage to flash the zip
Starting monday, I'll distribute a bootimage where you can go to aosp recovery, and flash the rom via sideload.
@Anti-root @nikkdib
Click to expand...
Click to collapse
Thank you! I am using Pixel ROM for my OP5, after trying all possible ROMS (there's many) and all possible kernels (there's many) and all possible cameras (there's many), and I can say that its simplicity and smoothness and speed are second to none! My battery drain when idle is 0.12% etc. etc. Let's hope that something similar is cooked for us here!
My XZ2C (H8314) is running android 9, it is rooted but without TWRP, since one has not been available for this phone, debloated, and running without the slightest problem. But, I would try the Pixel! (if you make it available also for the XZ2C).
Anti-root said:
Thank you! I am using Pixel ROM for my OP5, after trying all possible ROMS (there's many) and all possible kernels (there's many) and all possible cameras (there's many), and I can say that its simplicity and smoothness and speed are second to none! My battery drain when idle is 0.12% etc. etc. Let's hope that something similar is cooked for us here!
My XZ2C (H8314) is running android 9, it is rooted but without TWRP, since one has not been available for this phone, debloated, and running without the slightest problem. But, I would try the Pixel! (if you make it available also for the XZ2C).
Click to expand...
Click to collapse
Hey !
Well you have many ROMs available for your OP5 because people is using the same base for builds and it's very easy.
On sod we have an OSS tree.
Which gets constant upgrades and changes, this means that I'll build more than once a month.
Also there's special stuff to do, I'll write them on Monday when the needed oem release come out.
The advantage of this tree is that you can build any ROM pretty much very easily with minimal differences, just like other devices and it's with this process that I decided to settle for PE and maintain it
It happened for the second time for the phone to charge normally without being disconnected regularly. I took logs this time maybe it's helpful to you.
https://mega.nz/#!mkERWKgR!txl1b2HYCtiUl_fKhoCWjQ3m1O1GpvngzwsUQWnDGRU
Sent from my Xperia XZ2 Dual (AOSP) using Tapatalk
ASMstudent said:
It happened for the second time for the phone to charge normally without being disconnected regularly. I took logs this time maybe it's helpful to you.
https://mega.nz/#!mkERWKgR!txl1b2HYCtiUl_fKhoCWjQ3m1O1GpvngzwsUQWnDGRU
Sent from my Xperia XZ2 Dual (AOSP) using Tapatalk
Click to expand...
Click to collapse
Hi !
Thanks for the report, although, if you're using a Quick Charge 1/2/3 charger, it's normal because the charger tries to ramp up the voltage but the device refuses because those chargers aren't supported and it may damage your battery.
I recommend you using a standard 5V1A/1.5A charger or a USB Power Delivery charger.
Cheers !
It's working. But I also have a trouble with a wireless charger. It just didn't charge. Phone says "Pluged, didn't charging". I'm using Sony official qc charger and mi wireless charger pad. Type c in is broken.
Charging working when phone is completely off or just boot up placed on wireless charger pad. But when charging pad disabled - charge stop and didn't work till reboot (it may work, but very-very rare, after many enable/disable wireless pad).
Also, sometimes image didn't smooth and kinda laggy. On stock it was normal.
Offtop: google pay also broken on PE. Magisk hide and props didn't working.
Added: Seems, google pay start working, but battery dissappearing before our eyes. Audio also Is interrupting on YouTube when screen is off.
Does the camera permit to record RAW (DNG) files rather than JPEGs ?
tokumeino said:
Does the camera permit to record RAW (DNG) files rather than JPEGs ?
Click to expand...
Click to collapse
Of course
Camera2api is supported.
If you get any bug please put it in the bug tracker.
may i know how to flash this rom? as we don't have twrp xz2 for android 10?
i am aware of twrp for android 9 though. but how about the recovery for android 10?
wee2000 said:
may i know how to flash this rom? as we don't have twrp xz2 for android 10?
i am aware of twrp for android 9 though. but how about the recovery for android 10?
Click to expand...
Click to collapse
You have to unzip the payload.bin and get the various .img files that you will then flash through fastboot following the steps of any other android 10 aosp rom. Keep in mind that you'll have to flash the 17th of jenuary's oem files as the most recent ones do not work with this rom and you will end stucked in the sony logo
sorry a question; now we have a working twrp for android 10 tell me if these steps to install this rom are fine:
1)flash latest stock firmware
2)install twrp (SODP or STOCK version?)
3)with fastboot flash newest oem binary for our phone on slot a and b
4)reboot to twrp and flash the pixel experience zip without any wipe
5)reboot
ok?
dose this can use gcam？
Somehow i managed to install this rom
- Flash version 52.1.A.0.618
- Unlock Bootloader
- Fastboot flash ODM slot_a
- Fastboot flash ODM slot_b
- Fastboot boot twrp (sodp)
- Twrp format all
- Twrp install from SD (PE 10+)
- Success
But the camera is s**k
Does anyone know how to install working gcam?
was there any battery problem
thismeamirul.88 said:
Somehow i managed to install this rom
- Flash version 52.1.A.0.618
- Unlock Bootloader
- Fastboot flash ODM slot_a
- Fastboot flash ODM slot_b
- Fastboot boot twrp (sodp)
- Twrp format all
- Twrp install from SD (PE 10+)
- Success
But the camera is s**k
Does anyone know how to install working gcam?
Click to expand...
Click to collapse
did you have battery drain problems
btw can you send the twrp image you used
So...this is my first time use sony,I alreay unlock the bootlocker and runing 52.0.A.8.50(latest9.0)
I don't know how to flash,could you help me?:crying:
Sorry guys, i can't find a way to flash the latest firmware. I downloaded through xperifirm the latest but xperia xz2 is not listed in flashtools devices. Could I solve using newflasher? Please help me, I really like pixelexperience!!
matteopola said:
Sorry guys, i can't find a way to flash the latest firmware. I downloaded through xperifirm the latest but xperia xz2 is not listed in flashtools devices. Could I solve using newflasher? Please help me, I really like pixelexperience!!
Click to expand...
Click to collapse
Flashtool and newflasher should work both.
{
"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
Hello everyone,
To keep it short: Some of you may have noticed. Google uploaded a mainline 5.15 branch for the Pixel 6 Pro.
Here´s a build for those that dare trying or simply want to run a mainline kernel on their phone.
I don´t plan to update this much outside of the scope that googles does and what I already did. It´s more of a proof of concept and I think there are at least some that would be eager to try.
I was able to daily drive it two days without a single crash, due to disablng WiFi Calling and by not using my USB C buds, but rather bluetooth buds.
However now I´m back to 5.10 as it´s really just a piece of concept. Essentially mainline GKI kernel with downstream android driver changes. Some pieces that are in the 5.10 kernel that haven´t been brought to 5.15 yet, are missing.
Feel free to report bugs and I will add them to the list.
However if you have issues you have been warned
Features:
Main Features:
- Based on latest kernel sources from Google for 5.15
Bugs:
- powerhal broken due to several scheduler optimizations still missing , removed faulty hints when running powerhint mainline module
- vibration, fixed when running powerhint_mainline module
- USB-C devices crash the device upon connection usb c hub now works, connect mouse to usb c hub works too
- USB-C headphones do not output sound
- USB-C to 3.5mm adapter is not working
- having wifi calling/vowifi enabled makes a network driver crash the phone
- fast charging is not working correctly on my end
- probably many more I didn´t notice
DOWNLOAD:
Download is always located in this folder:
https://www.androidfilehost.com/?w=files&flid=329868
Changelog:
Android 12
Initial Release
Requirements
- unlocked Bootloader
- USB-Debugging in developer options enabled
- latest adb and fastboot binaries
- working adb and fastboot environment
- a device rooted with magisk
- vbmeta flashed with disabling verification and verity flags (check process how to root the phone here)
How to flash the Kernel:
1. Download the images provided in the downloads section to your PC.
2. Download the powerhint magisk module for mainline found in downloads section and flash it via Magisk Manager like any other magisk module.
3. Flash ALL the provided images using fastboot/bootloader and fastbootd (different to the regular Kirisakura Kernel)
4. Don´t forget to patch the boot.img with Magisk Manager prior to flashing it.
3. Magisk-patched boot.img, dtbo.img and vendor_boot.img need to be flashed in fastboot, while vendor_dlkm needs to be flashed via fastbootd
First boot to bootloader, either via the option in Magisk Manager or via adb command:
Code:
adb reboot bootloader
Now in fastboot flash boot.img and dtbo.img
Commands:
Code:
fastboot flash dtbo dtbo.img
fastboot flash boot yourmagiskpatchedboot.img
fastboot flash vendor_boot vendor_boot.img
How to boot to fastbootd
Code:
fastboot reboot fastboot
Once in fastbootd:
Code:
fastboot flash vendor_dlkm vendor_dlkm.img
4. Reboot either via buttons
or by typing
Code:
fastboot reboot
5. Profit!
@osm0sis for all his work on AK3.
@tbalden for being the best HTC, Pixel, OnePlus and Asus wingman!
@LeeDroid and @mwilky for their awesome roms and work I used on multiple devices!
@Captain_Throwback for all the mentoring and guidance!
@Eliminater74 for bringing me into the game and the Inspiration
@nathanchance for his upstream guidance and assistance
@RenderBroken for helping me out
@flar2 for all his work
@joshuous for all the help he provided to me in the past!
@arter97 for giving me advice
@kdrag0n for his help and advices!
@topjohnwu for magisk and his entire work!
google for all the work on this
Source Code: https://github.com/freak07/Kirisakura_Raviole
mine too
{
"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"
}
the belongs to me too.
and the last one
Did you notice any benefit performance/battery wise? I'll probably give it a try, thank you!
Tomatot- said:
Did you notice any benefit performance/battery wise? I'll probably give it a try, thank you!
Click to expand...
Click to collapse
probably both for the worse as several optimizations from google have not yet found their way to 5.15 from 5.10.
Does this mean it would be possible to run a linux operating system on the pixel 6 pro? For example, postmarketos, fedora or manjaro? Just like the pinephone?
deleted
This should work on P6 also correct?
ne0ns4l4m4nder said:
This should work on P6 also correct?
Click to expand...
Click to collapse
Just read the title... (also Raviole = Raven + Oriole)
Krullendhaar said:
Does this mean it would be possible to run a linux operating system on the pixel 6 pro? For example, postmarketos, fedora or manjaro? Just like the pinephone?
Click to expand...
Click to collapse
That would be possible anyway.
Freak07 said:
Essentially mainline GKI kernel with downstream android driver changes.
Click to expand...
Click to collapse
So its not really mainline, its google downstream, just not as big of a delta as usual. What I'd *really* love to see, is this hardware running on a real mainline straight from kernel.org.
So this is what rolling Android looks like lol
It seems to be amazing
bush911 said:
It seems to be amazing
Click to expand...
Click to collapse
have you flashed the kernel? if so, what's your experience like.
Alekos said:
have you flashed the kernel? if so, what's your experience like.
Click to expand...
Click to collapse
not yet, I prefer flash a zip kernel via EXKM, i am afraid of these commands
bencozzy said:
Best kernel period. Fixed all the stock bugs for me.
Only the known kernel bugs exist this is a step in the right direction.
Where can I send funds to buy you some adult beverages?
Click to expand...
Click to collapse
Click "Toggle signature" at the bottom of their post to show the donation link that's in their signature.
Worth looking at 5.17 or nah?
android-mainline-5.17
vassosman said:
Worth looking at 5.17 or nah?
android-mainline-5.17
Click to expand...
Click to collapse
If I find time, I might push out an updated build some time in the future.
but whether it´s based on 5.15, 5.17 or even 5.18 no clue.
I personally don´t think this is daily driver ready in any way, only a proof of concept and uninteresting for most.
Outta curiosity how did you figure out the boot.img config/offsets, or what are they I guess. Everytime I try to parse it through abootimg it crashes on me or complains about a missing page size.
I can boot this image just fine but I haven't been able to make my own yet