Xperia XZ1 G8341 Vanilla AOSP ROM
This is my first ROM and its fully Vanilla. I Just followed this Build guide without any modifications whatsoever.
The future goal is to build a stable Rom with mostly FOSS Software, stability and useful tools/settings.
Bugs/missing functions i discovered so far:
- Camera Not working always and -> Lens Distortion. Although RAW should be possible.
- Sony Bootlogo has some Artifacts
- No automatic APN setting
- No NFC 25.05 working
- No 90/120Hz mode (or does it?)
- No Display Colour Calibration
- Low Singlethread Geekbench Score (836) and (6060 Multicore) [Governors and schedulers not optimized]
Fingerprint Sensor is working and it takes some time to find Network (not sure if bug or normal).
I hope to find usable answers to those problems + ideas and hope, to receive enough feedback to improve as much as possible.
Just Flash all files (boot, recovery [or any working TWRP], system,vendor, userdata and the OEM Binaries [
SW_binaries_for_Xperia_Android_9.0_2.3.2_v9_yoshino.img] and you should be good to go.
XZ1 Single Sim(25.05.19)
XZ1 Dual Sim
SW_binaries_for_Xperia_Android_9.0_2.3.2_v9_yoshino.img
120Hz Mode
Obviously I am not responsible for bricked devices or anything that this could be related to.
XDA:DevDB Information
RumiRom, ROM for the Sony Xperia XZ1
Contributors
celeron1
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
Based On: Stock AOSP Userdebug
Version Information
Status: Testing
Created 2019-05-25
Last Updated 2019-05-30
Don't use V8 binaries, V9 are out
https://developer.sony.com/file/dow...-for-aosp-pie-android-9-0-kernel-4-9-yoshino/
Worse perfomance is expected because of lack of qti perf framework
marios199546 said:
Don't use V8 binaries, V9 are out
https://developer.sony.com/file/dow...-for-aosp-pie-android-9-0-kernel-4-9-yoshino/
Worse perfomance is expected because of lack of qti perf framework
Click to expand...
Click to collapse
Neat!
Im gonna try these. Thanks a lot.
I would marry if you turn 60fps to 90-120-144 omg plz plz
ΒΕΓΑ said:
I would marry if you turn 60fps to 90-120-144 omg plz plz
Click to expand...
Click to collapse
There is little to nothing about this I could find for the xz1 except one oreo based rom. I have to compile the kernel for it and find out if 60+ hz is really working and how to succesfully implement a toggle option for it. Since im new at this it might take some time without help but its something I want to impliment.
The Xz1s Display obviously is really underperforming in non Sony roms without the "Bravia engine" (colour apperence) imo compared to other open roms. I tried the Bravia magisk module but could not see any difference (also did not checked what it should do at system level).
So if someone has more knowledge feel free to share
I compiled a Kernel from here and modified:
arch/arm64/boot/dts/qcom/dsi-panel-somc-poplar-base-sde.dtsi
arch/arm64/boot/dts/qcom/dsi-panel-somc-poplar-sde.dtsi
arch/arm64/boot/dts/qcom/dsi-panel-somc-poplar.dtsi
(changed 60hz to 90/120hz).
How can I check if the Panel really is working under those frequencies and if other steps are needed?
When compiling I got an Error with drivers/staging/wlan-qc/qcacld-3.0 -> so i removed them from drivers/staging/Kconfig (So apparently no Wifi).
These are the Kernels (boot):
90Hz
*Update 29.05. I Fixed Wifi for the 120Hz version. link in first post
Camera seems to work without problems (also Raw) so I guess there is something wrong with the precompiled Sony Kernel.
Also the Sony bootlogo is not present (no artifakts??)
And again. Flash at own risk.
What about the version for two SIM cards?
Model G8342.
Your rom works perfect on my phone, thanks dev.
Btw, doesn't it support Treble? I cannot boot any of the GSI roms on the forum...
Riskypedia said:
Your rom works perfect on my phone, thanks dev.
Btw, doesn't it support Treble? I cannot boot any of the GSI roms on the forum...
Click to expand...
Click to collapse
It should support Treble.
Maybe you also need to flash "Disable DM Verity" and "Magisk" after
Can be used on G8342 ? ?
Sent from my Sony Xperia XZ1 using XDA Labs
celeron1 said:
I compiled a Kernel from here and modified:
arch/arm64/boot/dts/qcom/dsi-panel-somc-poplar-base-sde.dtsi
arch/arm64/boot/dts/qcom/dsi-panel-somc-poplar-sde.dtsi
arch/arm64/boot/dts/qcom/dsi-panel-somc-poplar.dtsi
(changed 60hz to 90/120hz).
How can I check if the Panel really is working under those frequencies and if other steps are needed?
When compiling I got an Error with drivers/staging/wlan-qc/qcacld-3.0 -> so i removed them from drivers/staging/Kconfig (So apparently no Wifi).
These are the Kernels (boot):
90Hz
120Hz
Camera seems to work without problems (also Raw) so I guess there is something wrong with the precompiled Sony Kernel.
Also the Sony bootlogo is not present (no artifakts??)
And again. Flash at own risk.
Click to expand...
Click to collapse
Can i use this kernel with stock sony rom? (Existenz patched btw...)
ΒΕΓΑ said:
Can i use this kernel with stock sony rom? (Existenz patched btw...)
Click to expand...
Click to collapse
The Kernel is for AOSP (Linux kernel 4.9) so normally it shouldnt work with the Stock Firmware but i dont know if it works with the patched Existenz rom.
therma.cpp said:
What about the version for two SIM cards?
Model G8342.
Click to expand...
Click to collapse
Its for the single Sim.
Im not satisfied with the current State but I can build a dual sim version as well. (Building on hdd due to small SSD so it might take a while)
Screen is not responsive (SOV36). Any suggestions?
update: not the rom. tried to flash different rom and same result.
sinkoo1979 said:
Screen is not responsive (SOV36). Any suggestions?
update: not the rom. tried to flash different rom and same result.
Click to expand...
Click to collapse
Does it respond different while charging?
Is the screen properly clean?
Try flashing the last stock rom > same result?
If not try flashing any gsi > result?
Then full cfw flash + sw binary.
And do factory resets before flashing.
Hoping for the best. Not sure how and if the SOV36 model differs from the rest
celeron1 said:
Does it respond different while charging?
Is the screen properly clean?
Try flashing the last stock rom > same result?
If not try flashing any gsi > result?
Then full cfw flash + sw binary.
And do factory resets before flashing.
Hoping for the best. Not sure how and if the SOV36 model differs from the rest
Click to expand...
Click to collapse
no
yes
no
did not work
works with stock
sinkoo1979 said:
no
yes
no
did not work
works with stock
Click to expand...
Click to collapse
Dis you try one of these GSIs and did you flash the SW-Binaries after?
How "non responsive" is it? Laggy/Not at all/Ghost touches etc.?
Since this is off-Topic i will delete this message after you read it. You shuld open a new Thread where the Problem could be discussed.:good:
celeron1 said:
Dis you try one of these GSIs and did you flash the SW-Binaries after?
How "non responsive" is it? Laggy/Not at all/Ghost touches etc.?
Since this is off-Topic i will delete this message after you read it. You shuld open a new Thread where the Problem could be discussed.:good:
Click to expand...
Click to collapse
Nothing at all
sinkoo1979 said:
Nothing at all
Click to expand...
Click to collapse
Try flashing a oreo based stock rom.(or if you only tried oreo then pie), then flash gsi etc
ΒΕΓΑ said:
I would marry if you turn 60fps to 90-120-144 omg plz plz
Click to expand...
Click to collapse
don't you think it would be the least manner to put some pics of your ass when you come around with "marrying-for-asking"? XD :silly::silly:
Related
Orginal post:
https://www.google.pl/amp/s/forum.x...lopment/experimental-phh-treble-t3709659/amp/
Downolad Version V10:
With gapps and Su:
https://androidfilehost.com/?fid=746010030569954763
Without gapps and Su
https://androidfilehost.com/?fid=673956719939820512
Installation:
- First, you MUST be running a stock Android 8.0 ROM.
- Obviously, unlock your bootloader
- Download the correct system.img variant (see list of devices above, and dowload links below)
- Flash the system.img
- Do a Factory reset
- Reboot
What nor working?
- Broken camera because DRM KEY...
But all probably work pretty good!
For Xperia XZ1 and XZ1 COMPACT FLASH ONLY A version!!
Changeleog
v10: (2018-02/18)
- Android 8.1 !
- Includes versioned vndk, so devices running both 8.1 and 8.0 should work.
i heard google camera hdr+ working on android 8.1. is it working? What about battery efficiency?
Idk i not test this because my phone go to repair. I think camera not work on all apk. Because drm key broken but i don't know on 100%.
ok I will try it
eggimong said:
ok I will try it
Click to expand...
Click to collapse
Give screen plz. I will add on #1 post. And thank u!
i stuck on bootloop..
i flashed the file include su and gapps on 47.1.A.12.75. it stuck at sony boot logo then i flashed nosu and it stuck at boot animation
then i downgraded xz1 on 47.1.A.8.49 and flashed both but same result
i am not good at english :/
eggimong said:
i heard google camera hdr+ working on android 8.1. is it working? What about battery efficiency?
Click to expand...
Click to collapse
Maybe off topic but in Xperia XZ, Google camera hdr mod work fine without DRM keys in AOSP rom. I guess should work the same for XZ1
snake218 said:
Maybe off topic but in Xperia XZ, Google camera hdr mod work fine without DRM keys in AOSP rom. I guess should work the same for XZ1
Click to expand...
Click to collapse
you're right I installed aosp 8.1 (https://forum.xda-developers.com/xperia-xz1/how-to/aosp-8-1-t3750951)because project treble cause bootloop. it works hdr+!
eggimong said:
you're right i installed aosp 8.1 (https://forum.xda-developers.com/xperia-xz1/how-to/aosp-8-1-t3750951)because project treble cause bootloop. It works hdr+!
Click to expand...
Click to collapse
but their are limitation from sony like back cemra is set to 17 mp and iso set to 800 only they are in kernel i am working on it i am now learning kernel patching i have not done before lets hope for best
You can use TWRP brush into it？
V11 released
who can test that version?
I'll give it a shot
Download link?
N1ghtr08d said:
Download link?
Click to expand...
Click to collapse
Can be found in the original post from the treble forums.
Here is the post:
https://forum.xda-developers.com/pr...-development/experimental-phh-treble-t3709659
Good luck, let us know.
Redcalibur said:
Can be found in the original post from the treble forums.
Here is the post:
https://forum.xda-developers.com/pr...-development/experimental-phh-treble-t3709659
Good luck, let us know.
Click to expand...
Click to collapse
Complete waste of time. I tried several different ways to flash this ROM but it's just not compatible with the XZ1 8341. Now i have to flash back to stock and the restore my TWRP backup.
Incompatible ROMs should NOT be posted on these forums unless they have been tested at the very least by the OP.
N1ghtr08d said:
Complete waste of time. I tried several different ways to flash this ROM but it's just not compatible with the XZ1 8341. Now i have to flash back to stock and the restore my TWRP backup.
Incompatible ROMs should NOT be posted on these forums unless they have been tested at the very least by the OP.
Click to expand...
Click to collapse
Hey, I'm asking this just to be sure that we can consider the rom incompatible for our device.
You used the rom that said A-only, right? Since the thread states that the XZ1 only supports build A-only. If so, we could try mentioning the issues you experienced in the original thread.
Thank you for your time.
Edit: I've just seen your posts in the original thread. Sorry for the quote.
No it's ok, I don't mind helping, it's just frustrating. I flashed the A only nosu vanilla version, then booted into TWRP and performed a factory reset and when I rebooted into system the phone just hangs on the Sony boot screen for ages then reboots and does the same thing again and again.
I had the same experience with all A-only versions.
N1ghtr08d said:
No it's ok, I don't mind helping, it's just frustrating. I flashed the A only nosu vanilla version, then booted into TWRP and performed a factory reset and when I rebooted into system the phone just hangs on the Sony boot screen for ages then reboots and does the same thing again and again.
Click to expand...
Click to collapse
try this version, for me on xz1c it loads to the inscription of "xperia", and it hangs https://drive.google.com/open?id=118pwXm2UK95AaYTvIfDAiWDBk-rUBh6Q
Infinite restart animation………………cnm?
So we have official 9.0 update now, which means we have pie vendor installed our devices.
However, it seems non of GSI pie roms work on xz1 even though our vendor and kernel are working properly with pie firmware.
Is there anyone successfully installed 9.0 GSI rom after the official Pie update? Or is there any idea why they don't work?
Riskypedia said:
So we have official 9.0 update now, which means we have pie vendor installed our devices.
However, it seems non of GSI pie roms work on xz1 even though our vendor and kernel are working properly with pie firmware.
Is there anyone successfully installed 9.0 GSI rom after the official Pie update? Or is there any idea why they don't work?
Click to expand...
Click to collapse
everything is working fine on GSI 9.0 pie roms but if u need gcam, flash on aosp boot and vendor(because full camera2api and raw support), on stock blobs gcam doesnt work because there is no raw support on stock.
arslancn said:
everything is working fine on GSI 9.0 pie roms but if u need gcam, flash on aosp boot and vendor(because full camera2api and raw support), on stock blobs gcam doesnt work because there is no raw support on stock.
Click to expand...
Click to collapse
Thanks for your reply Can you suggest some roms that worked? Because whenever I try to boot my phone with this rom(https://forum.xda-developers.com/pr...opment-a-only-roms/ported-p-sgsi-pr2-t3845789), I get bootlooped
Riskypedia said:
Thanks for your reply Can you suggest some roms that worked? Because whenever I try to boot my phone with this rom(https://forum.xda-developers.com/pr...opment-a-only-roms/ported-p-sgsi-pr2-t3845789), I get bootlooped
Click to expand...
Click to collapse
try any updated ''GSI''(not sGSI) arm64 a only rom from here. sGSI roms have alot of bugs
arslancn said:
try any updated ''GSI''(not sGSI) arm64 a only rom from here. sGSI roms have alot of bugs
Click to expand...
Click to collapse
Thanks to your support, I've got finally found a working rom(Pixel Experienced Rom)! Maybe I think the roms I've tried are all sGSI roms that caused bootloops
Now I'm trying to use gcam now, so I've installed pie aosp vendor uploaded in sony open device project(fasboot flash oem ~~~.img). However, it seems it doesn't have problem with booting but gcam still crashes(I think it's cam2api problem). According to your previous comment, it seems I should flash aosp kernel which isn't provided by Sony. So should I manually compile the kernel to make it working?
Sorry for bothering :crying:
Riskypedia said:
Thanks to your support, I've got finally found a working rom(Pixel Experienced Rom)! Maybe I think the roms I've tried are all sGSI roms that caused bootloops
Now I'm trying to use gcam now, so I've installed pie aosp vendor uploaded in sony open device project(fasboot flash oem ~~~.img). However, it seems it doesn't have problem with booting but gcam still crashes(I think it's cam2api problem). According to your previous comment, it seems I should flash aosp kernel which isn't provided by Sony. So should I manually compile the kernel to make it working?
Sorry for bothering :crying:
Click to expand...
Click to collapse
use this guide and build needed AOSP images, flash all of them (boot.img, vendor.img, system.img and SODP OEM image too)
reboot one time, after u see setup, reboot recovery and make full wipe(system, data, cache, dalvik, internal), format data and reboot recovery
flash gsi image and gapps(if gapps not included)
reboot recovery, flash magisk and reboot.
now u have aosp rom with working gcam
arslancn said:
use this guide and build needed AOSP images, flash all of them (boot.img, vendor.img, system.img and SODP OEM image too)
reboot one time, after u see setup, reboot recovery and make full wipe(system, data, cache, dalvik, internal), format data and reboot recovery
flash gsi image and gapps(if gapps not included)
reboot recovery, flash magisk and reboot.
now u have aosp rom with working gcam
Click to expand...
Click to collapse
which version of gcam works?
arslancn said:
use this guide and build needed AOSP images, flash all of them (boot.img, vendor.img, system.img and SODP OEM image too)
reboot one time, after u see setup, reboot recovery and make full wipe(system, data, cache, dalvik, internal), format data and reboot recovery
flash gsi image and gapps(if gapps not included)
reboot recovery, flash magisk and reboot.
now u have aosp rom with working gcam
Click to expand...
Click to collapse
Thank you bro, everything works fine! I think I should pack the built images and upload in case someone needs this XD
Respect to Turkey, from Korea.
Riskypedia said:
Thank you bro, everything works fine! I think I should pack the built images and upload in case someone needs this XD
Respect to Turkey, from Korea.
Click to expand...
Click to collapse
:highfive: u can make a thread about flashing treble with full cameraapi 2 support and share your images with other XZ1 users!
Riskypedia said:
Thank you bro, everything works fine! I think I should pack the built images and upload in case someone needs this XD
Respect to Turkey, from Korea.
Click to expand...
Click to collapse
did you have same bug on XZ1?
the battery level always in 20%.
arslancn said:
:highfive: u can make a thread about flashing treble with full cameraapi 2 support and share your images with other XZ1 users!
Click to expand...
Click to collapse
Sadly, it seems it's impossible to use AOSP based system because of its stability. It's way too unstable to use, but I think I can share the built images to make progress! Again, thanks for your help
gacky1601 said:
did you have same bug on XZ1?
the battery level always in 20%.
Click to expand...
Click to collapse
I've never experienced the bug when I used that. Did that happen to your XZ1? Or is it the problem of the other Xperia devices? The biggest problem was that it's too unstable that I can barely use that. The network oftenly disconnects and randomly reboots itself.
Riskypedia said:
I've never experienced the bug when I used that. Did that happen to your XZ1? Or is it the problem of the other Xperia devices? The biggest problem was that it's too unstable that I can barely use that. The network oftenly disconnects and randomly reboots itself.
Click to expand...
Click to collapse
Yes,my device is G8342. The wifi bug and battery level bug.
my device couldn't connect to any wifi,but sharing hotspot in 2.4ghz/5ghz was fine.
Screen colors look strange.
Randomly reboot,too.
I don't know any solution.
I only knew the methods to the image step by step from Sony's source.
Maybe we should build the kernel by ourselves
The problem you mentioned about disconnecting network, does it happens on wifi or mobile data?
Sorry, just a quick question has as resurrection remix has a treble room out, has anyone tried it?
gacky1601 said:
Yes,my device is G8342. The wifi bug and battery level bug.
my device couldn't connect to any wifi,but sharing hotspot in 2.4ghz/5ghz was fine.
Screen colors look strange.
Randomly reboot,too.
I don't know any solution.
I only knew how to build the image step by step from Sony's source.
Maybe we should build the kernel by ourselves[/QUOTE
Yeah, we should... I'm just a newbie developer, and really sad that we're lack of developers who can help XZ1 users, but I believe one day users make this out together. The dispaly color is because of AOSP's default display color temperature, maybe we can fix this out by touch some configs of kernel
Click to expand...
Click to collapse
lilbrat said:
Sorry, just a quick question has as resurrection remix has a treble room out, has anyone tried it?
Click to expand...
Click to collapse
I think you can just try it with stock boot , vendor and oem.
I will works perfectly.
Don't forget to report if there is any problem or it work properly.
---------- Post added at 04:37 PM ---------- Previous post was at 04:20 PM ----------
[/QUOTE
Yeah, we should... I'm just a newbie developer, and really sad that we're lack of developers who can help XZ1 users, but I believe one day users make this out together. The dispaly color is because of AOSP's default display color temperature, maybe we can fix this out by touch some configs of kernel [/QUOTE]
Yeah. I think there are a few developers work on XZ1.
Have .
The working perfectly rom will be our target, like the thread below.
https://forum.xda-developers.com/xperia-xz1-compact/how-to/xz1c-g8441-lilac-aosp8-1-t3762581
Share your all files so that i can work with gcam to be installed properly to latest pixel experience.
Lineage OS 16 For Xperia X [Treble]Based on Sony Open DevicesI am not responsible for bricked devices, dead SD cards,.Suitable for F5121 and F5122Reboot after your first boot please!
Opinional files:
Disable ForceEncrypt:Link
Required files:
[Tested]
V20190323:Link With: SW_binaries_for_Xperia_Android_9.0_2.3.2_v6_loire.zip
[OEM-Files]
Download Link
How to flash
Read README.txt in zip file please.
Optional step If you want to use a GSI
Flash a GSI compatible System image and boot!
Code:
fastboot flash system < Path of GSI-System.img >
Because of Anti-Rollback, If you want to Use GSI, You need to choose the same or newer one as the treble build date.
Update and known BUG:
V20190323:
Bugs:
1. Quick Charge is broken, you can use computer USB port charge.
2. Camera doesn't work on first boot, you need to reboot.
Source Codes
Sjll Script
Contributors
Sjll @infixremix
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
Paypal
I am very happy to receive your donation.
Version Information
Status: Testing
Created 2019-03-31
Last Updated 2019-03-31
I've used your Treble Pie for a while and it's awesome. Gotta try this as well. Thanks a lot for all the work!
P/s: Can you make a custom overclocked kernel for your Pie ROMs? I've been using Extreme Kernels (for stock Oreo) and they are amazing. I wonder if Pie can also get a similar kernel.
Yeah bro thanks for this work..can you optimize kernel to make sodp rom usable
LOLisLIFE said:
I've used your Treble Pie for a while and it's awesome. Gotta try this as well. Thanks a lot for all the work!
P/s: Can you make a custom overclocked kernel for your Pie ROMs? I've been using Extreme Kernels (for stock Oreo) and they are amazing. I wonder if Pie can also get a similar kernel.
Click to expand...
Click to collapse
lookmanns14 said:
Yeah bro thanks for this work..can you optimize kernel to make sodp rom usable
Click to expand...
Click to collapse
I will try to build a optimize kernel in free time.
Hi,
Can you please help me with the download from the GSI? Where can I get the right file from?
after install, bluetooth and settings tell me that it stops all the time and sim cant be detected. Also there is some encryption so i can't access data or system anymore with twrp... even magisk can't be installed. great...
After running into a ton of errors, I think I've done something wrong. I have a few questions:
1. Where does Disable ForcedEncryption (DFE) go to in the installation process? If I flash the zip before Lineage (or not flasing at all), the phone encrypts itself right on boot. If I flash DFE zip after Lineage, the camera (and all the sensors) die permanently.
2. Regardless of the phone's encryption status, sometimes the phone just fails to recognize all the sensors (except Wifi, battery and GPS). That means no accelerometer, no screen rotation, no compass or light sensor. Rebooting fixes this on Lineage (for a while), but on RR once it occurs all sensors die permanently. Also GPS reception is terrible, as I haven't got a single fix.
Hope anyone who has been using Treble roms could give me an answer. Thanks in advance.
iH8Ecchi said:
After running into a ton of errors, I think I've done something wrong. I have a few questions:
1. Where does Disable ForcedEncryption (DFE) go to in the installation process? If I flash the zip before Lineage (or not flasing at all), the phone encrypts itself right on boot. If I flash DFE zip after Lineage, the camera (and all the sensors) die permanently.
2. Regardless of the phone's encryption status, sometimes the phone just fails to recognize all the sensors (except Wifi, battery and GPS). That means no accelerometer, no screen rotation, no compass or light sensor. Rebooting fixes this on Lineage (for a while), but on RR once it occurs all sensors die permanently. Also GPS reception is terrible, as I haven't got a single fix.
Hope anyone who has been using Treble roms could give me an answer. Thanks in advance.
Click to expand...
Click to collapse
Trust me....its weird (this is what i do with every pie Rom I DONT GUARANTEE SUCCESS ON TREBLE ROMS BECAUSE I WASNT ABLE TO TEST THEM YET)
Flash OEM image which is advertised here
Flash the Rom without anything
Reboot
Go back to recovery by Holding
Power + vol up
Screen turns black= quickly switch to
Power + vol down
Flash disable force encrypt
Reboot
Done!
(Remember to flash anything else that you want)
Some random said:
Trust me....its weird (this is what i do with every pie Rom I DONT GUARANTEE SUCCESS ON TREBLE ROMS BECAUSE I WASNT ABLE TO TEST THEM YET)
Flash OEM image which is advertised here
Flash the Rom without anything
Reboot
Go back to recovery by Holding
Power + vol up
Screen turns black= quickly switch to
Power + vol down
Flash disable force encrypt
Reboot
Done!
(Remember to flash anything else that you want)
Click to expand...
Click to collapse
I only run into these problems on Treble roms. No problem with sensors or encryption with native ones, such as AOSP or Paranoid.
iH8Ecchi said:
I only run into these problems on Treble roms. No problem with sensors or encryption with native ones, such as AOSP or Paranoid.
Click to expand...
Click to collapse
Hmmmmm
Well like that it worked with all pie ROMs that I used
I've been trying to flash this ROM but couldn't flash the Lineage OS Zip file. It says "Zip treble compatibility error!"
"Invalid zip file format!"
can someone please help me out?
Fardin Rehman said:
I've been trying to flash this ROM but couldn't flash the Lineage OS Zip file. It says "Zip treble compatibility error!"
"Invalid zip file format!"
can someone please help me out?
Click to expand...
Click to collapse
Use Twrp-Q (Ask Simeone for Link)
Some random said:
Use Twrp-Q (Ask Simeone for Link)
Click to expand...
Click to collapse
Yeah I have TWRP-Q just need to flash recovery and then try again. Thank you very much for helping
Can anyone please tell me which Gcam can i use on this ROM?
New version of LOS 16 + Treble
This version of LOS is outdated and does not work on latest Treble.
An updated LOS build (with Expanded volume and latest security patch) can be downloaded on this thread and installed over latest Treble.
Since this phone requires arm64 A-only GSIs to boot, the compatible version should be lineage-16.0-2019xxxx-UNOFFICIAL-treble_arm64_avN.img.xz.
Installation tutorial: Click here. Keep in mind that system.img refers to the LOS build above.
Getting Magisk to work: Click here.
iH8Ecchi said:
This version of LOS is outdated and does not work on latest Treble.
An updated LOS build (with Expanded volume and latest security patch) can be downloaded on this thread and installed over latest Treble.
Since this phone requires arm64 A-only GSIs to boot, the compatible version should be lineage-16.0-2019xxxx-UNOFFICIAL-treble_arm64_avN.img.xz.
Installation tutorial: Click here. Keep in mind that system.img refers to the LOS build above.
Getting Magisk to work: Click here.
Click to expand...
Click to collapse
Thanks man the ROM is great! But is it possible to make the camera work like it did on the original Xperia X stock ROM. I mean the camera is pretty dark on all custom ROMs is there any fix for that?
Fardin Rehman said:
Thanks man the ROM is great! But is it possible to make the camera work like it did on the original Xperia X stock ROM. I mean the camera is pretty dark on all custom ROMs is there any fix for that?
Click to expand...
Click to collapse
You can use Chippa_a's Unofficial LOS16 instead. That one has some heating issues and gaming performance might not be optimal (due to CPU throttling), but camera and battery life is almost identical to stock. In fact, I only use Treble LOS as daily driver because I play games on my phone quite a lot.
If you still insist on using Treble however, you can check out Google Camera ports (scroll down a little bit on Treble page). With HDR+ or Night Mode the picture quality is stellar, but taking pictures might be a bit slow. As far as I know it only runs on Treble and Omni.
iH8Ecchi said:
You can use Chippa_a's Unofficial LOS16 instead. That one has some heating issues and gaming performance might not be optimal (due to CPU throttling), but camera and battery life is almost identical to stock. In fact, I only use Treble LOS as daily driver because I play games on my phone quite a lot.
If you still insist on using Treble however, you can check out Google Camera ports (scroll down a little bit on Treble page). With HDR+ or Night Mode the picture quality is stellar, but taking pictures might be a bit slow. As far as I know it only runs on Treble and Omni.
Click to expand...
Click to collapse
Yeah I am using the gcam port and I get pretty good pictures with it but not very good video quality so I guess I'm gonna give it a try to Chippa_a's Unofficial LOS16.
Below are Stock kernels with DT2W added. The kernels have been extracted from 47.2.A.11.228 firmware.
The kernels are SElinux enforcing (same as stock). They are in no way custom, all i have done is add the dtb from Iovf's .107 kernel to allow double tap 2 wake.
Some people have reported the DT2W feature requires a solid tap, and sometimes may not wake the screen instantly.
This is out of my hands, and capabilities, to do anything about.
Installation:
On stock .228 firmware:
Flash the kernel for your device in TWRP
Flash whatever Magisk.zip you prefer, and reboot. Once rebooted, install the magisk module below (DT2W_Magisk Module) and reboot.
(If you want permissive selinux, also install the Permissive module in Magisk at the same time).
eXistenZ users:
The kernels are also compatible. Same install steps apply (flash kernel, flash magisk, reboot)
If.you want to keep SElinux set to enforcing, use the DT2W_Magisk Module.
If you are using something to set SElinux to permissive for fonts (or whatever reason), you dont need the DT2W Magisk Module, only the Permissive module.
Also attached are the TWRP flashable stock .228 kernels.
Thanks to @iovf for the original kernels I pinched parts from.
Thanks to @shoey63 for the DT2W Magisk Module.
Stuck on Sony boot logo. I use the last eXistenz rom on last firmware .228
theflanker said:
Stuck on Sony boot logo. I use the last eXistenz rom on last firmware .228
Click to expand...
Click to collapse
Did you flash magisk after kernel?
theflanker said:
Stuck on Sony boot logo. I use the last eXistenz rom on last firmware .228
Click to expand...
Click to collapse
Which kernel? Single or dual?
kojak1989 said:
Did you flash magisk after kernel?
Click to expand...
Click to collapse
Yes of course, 20.0 version. Maybe I have to try 18.1. I will try and tell you.
Beetle84 said:
Which kernel? Single or dual?
Click to expand...
Click to collapse
Single
theflanker said:
Yes of course, 20.0 version. Maybe I have to try 18.1. I will try and tell you.
Single
Click to expand...
Click to collapse
Did tou do it with clean install ? If yes then you must do it with 18.1 and let eXistenZ boot once and for me iovf kernel make freezes.
theflanker said:
Yes of course, 20.0 version. Maybe I have to try 18.1. I will try and tell you.
Single
Click to expand...
Click to collapse
I use v20 on the XZP with no drama, can you try the dual sim kernel and let me know? There is no harm in using a dual kernel on a single sim phone. Thanks.
I tried these kernels, and it seems really inconsistent and finicky. However, I think I found the reason why there are so many issues with double tap to wake on the XZ1; a developer looked into implementing tap to wake and had this to say:
Myself5 said:
I roughly remember looking into this decades ago and the conclusion was that either the XZP/XZ1 kernel is super ****ed (beyond repair) or they have some sort of hardware issue causing the situations. When you used DT2W and combined it with using the power button in a specific order the touchscreen wouldn't work anymore until you turn the screen off/on again using the power button.
Click to expand...
Click to collapse
@Beetle84, do you know anyone who could look into this? It would be nice to see if this was a really bad software limitation, or just a hardware limitation.
Generic123. said:
I tried these kernels, and it seems really inconsistent and finicky. However, I think I found the reason why there are so many issues with double tap to wake on the XZ1; a developer looked into implementing tap to wake and had this to say:
@Beetle84, do you know anyone who could look into this? It would be nice to see if this was a really bad software limitation, or just a hardware limitation.
Click to expand...
Click to collapse
I think its the xz1 panel derf alot said somewhere in his LOS thread... xzp works flawlessly with dt2w, despite the above quote.
On another note, whih kernel did you try, the single or dual?
Beetle84 said:
I think its the xz1 panel derf alot said somewhere in his LOS thread... xzp works flawlessly with dt2w, despite the above quote.
On another note, whih kernel did you try, the single or dual?
Click to expand...
Click to collapse
Does that mean the XZ1 does not have the appropiate hardware for it? It's a shame if that's the case.
I used the single sim kernel, on existenz pie with the magisk module.
Generic123. said:
Does that mean the XZ1 does not have the appropiate hardware for it? It's a shame if that's the case.
I used the single sim kernel, on existenz pie with the magisk module.
Click to expand...
Click to collapse
I believe its hardware. For the xzp, the dt2w code was ported (by a different dev than iovf) from the xperia x to the xzp kernel. Im not sure if it will get any better ever. Im not positive how iovf did it.
Thanks for letting me know about which kernel you flashed, someone above bootlooped using the single sim kernel, no idea why. Its kinda hard to test myself without the xz1... A few guys tested before i uploaded them here, so I don't know what happened for him/her.
Beetle84 said:
I believe its hardware. For the xzp, the dt2w code was ported (by a different dev than iovf) from the xperia x to the xzp kernel. Im not sure if it will get any better ever. Im not positive how iovf did it.
Thanks for letting me know about which kernel you flashed, someone above bootlooped using the single sim kernel, no idea why. Its kinda hard to test myself without the xz1... A few guys tested before i uploaded them here, so I don't know what happened for him/her.
Click to expand...
Click to collapse
Is there any way you could contact iovf to ask him/her? Maybe we could see if the method you mentioned for the XZP might be able to get dt2w to work on the XZ1.
Generic123. said:
Is there any way you could contact iovf to ask him/her? Maybe we could see if the method you mentioned for the XZP might be able to get dt2w to work on the XZ1.
Click to expand...
Click to collapse
Will do
Beetle84 said:
Will do
Click to expand...
Click to collapse
Many thanks my dude.
I'm bit courious, as there has been only one person has mentioned what rom and firmware they are using, but for those that are using the the existenz rom have you tried going into the rom display settings and flipping on the dt2w switch to see if it helps..
see pic..
I tried to reflash everything with Magisk 18.1 but I have the same error.
But doesn't it work for me?
theflanker said:
I tried to reflash everything with Magisk 18.1 but I have the same error.
But doesn't it work for me?
Click to expand...
Click to collapse
No idea mate, single and dual are confirmed working. Try flashing the stock kernel, magisk and reboot
Then try the dt2w kernel, magisk and reboot.
Beetle84 said:
I think its the xz1 panel derf alot said somewhere in his LOS thread... xzp works flawlessly with dt2w, despite the above quote.
On another note, whih kernel did you try, the single or dual?
Click to expand...
Click to collapse
IIRC the Xperia XZ Premium got shipped with multiple touchscreens.
I can assure you mine is doing that, and I can provide you multiple other instances where it happened. I've been trying to use my XZP as a DD for around 2 months and had that issue nearly daily when DT2W was enabled. (Mind you, that was shortly after release though, so it's been a while).
Generic123. said:
Does that mean the XZ1 does not have the appropiate hardware for it? It's a shame if that's the case.
I used the single sim kernel, on existenz pie with the magisk module.
Click to expand...
Click to collapse
See above.
Beetle84 said:
I believe its hardware. For the xzp, the dt2w code was ported (by a different dev than iovf) from the xperia x to the xzp kernel. Im not sure if it will get any better ever. Im not positive how iovf did it.
Thanks for letting me know about which kernel you flashed, someone above bootlooped using the single sim kernel, no idea why. Its kinda hard to test myself without the xz1... A few guys tested before i uploaded them here, so I don't know what happened for him/her.
Click to expand...
Click to collapse
There is nothing that was "ported". Both devices have the code for Doubletap to wake in the kernel. It's a single matter of replacing a "false" with "true". None of that is standard code btw, so isn't it interesting that Sony put effort into adding Doubletap to wake just to disable it then?
P.S: Why are you building Dual and Single SIM variants of the kernel?
Myself5 said:
IIRC the Xperia XZ Premium got shipped with multiple touchscreens.
I can assure you mine is doing that, and I can provide you multiple other instances where it happened. I've been trying to use my XZP as a DD for around 2 months and had that issue nearly daily when DT2W was enabled. (Mind you, that was shortly after release though, so it's been a while).
See above.
There is nothing that was "ported". Both devices have the code for Doubletap to wake in the kernel. It's a single matter of replacing a "false" with "true". None of that is standard code btw, so isn't it interesting that Sony put effort into adding Doubletap to wake just to disable it then?
P.S: Why are you building Dual and Single SIM variants of the kernel?
Click to expand...
Click to collapse
Thanks for the clarification. Would it be possible for us to determine what our touchscreen manufacturers are? In your case, tap to wake is pretty glitchy. But, in @Beetle84's case, he appears to have little/no issues. It would be nice to see if different touchscreen manufacturers are at play here.
We have so much choice now on our A20.
A20 ROMs available for Q
1. Stock
2. GSIs
3. Ultimate Q
4. Ultimate Q S10+port
5. Ultimate Q S20 ports
6. Z-Rom
7. Infinity OS v1
Kernels
1. Stock
2. Minker 14.6 (Magisk 19.3)
3. Quantum v1
4. Quantum v2 (Magisk 19.3)
5. UltimateQ_v1
What ROM do you use?
Vote for your kernel here
https://forum.xda-developers.com/galaxy-a20/development/a20-kernels-available-q-t4143357
Infinity ROM
However, when Ultimate Q S20 gets updated to port 7, I will move back to it.
I like roms that balance functions with debloating
Roms like Zrom are heavily debloated and are very smooth
Infinity rom is debloated and smooth
S20 port is slightly debloated and smooth. Every Samsung function works on S20 port. Link to PC, SmartSwitchBackUp, Samsung Cloud Restore, Project to PC screen, game plugins, Battery Statistics in DeviceHealthCare etc,Galaxy store etc. These functions are usually not on the other roms. Adding them from apkmirror or apkpure does not work. They simply refuse to function correctly once added even to the root folders.
I'm currently in Ultimate QZrom of shumway66. but still it has problems in audio of games. I wanna try to GSI but I am afraid to do it
argonax said:
I'm currently in Ultimate QZrom of shumway66. but still it has problems in audio of games. I wanna try to GSI but I am afraid to do it
Click to expand...
Click to collapse
Test out Ultimate Q s20 port 6. It is stable. The one you installed was a Test rom.
Or try out Infinity Rom. No hiccups so far apart from the camera that can be fixed by replacing 2 files and rebooting the phone.
Roydpeter said:
Test out Ultimate Q s20 port 6. It is stable. The one you installed was a Test rom.
Or try out Infinity Rom. No hiccups so far apart from the camera that can be fixed by replacing 2 files and rebooting the phone.
Click to expand...
Click to collapse
What files should I replace to fix the camera?
*
DawilHerrera said:
What files should I replace to fix the camera?
*
Click to expand...
Click to collapse
There is a zip file in the Telegram channel. It was sent by Top. I will see if i can upload it here.
10 votes
Anyone updated to rebase on (Australian) July update A205YNDVU5BTG1?
Worthwhile or not?
jajk said:
Anyone updated to rebase on (Australian) July update A205YNDVU5BTG1?
Worthwhile or not?
Click to expand...
Click to collapse
I haven't used stock for ages
@physwizz Neither have I but rebasing your preferred ROM over the top of a later stock ROM gives you a later modem, bootloader etc. that may have some improved qualities....... or not. All the partition updates you don't get from custom ROMs.....
So I am asking if anyone has updated to A205YNDVU5BTG1 and found anything good, bad or indifferent? Certainly the modem needs a helping hand to get better reception quality / range....
jajk said:
@physwizz Neither have I but rebasing your preferred ROM over the top of a later stock ROM gives you a later modem, bootloader etc. that may have some improved qualities....... or not. All the partition updates you don't get from custom ROMs.....
So I am asking if anyone has updated to A205YNDVU5BTG1 and found anything good, bad or indifferent? Certainly the modem needs a helping hand to get better reception quality / range....
Click to expand...
Click to collapse
Are you going to try it?
argonax said:
I'm currently in Ultimate QZrom of shumway66. but still it has problems in audio of games. I wanna try to GSI but I am afraid to do it
Click to expand...
Click to collapse
I'm using gsi it working perfectly so far CRdroid 6.9 is mine but MTP isn't working at it only works in recovery
gasg said:
I'm using gsi it working perfectly so far CRdroid 6.9 is mine but MTP isn't working at it only works in recovery
Click to expand...
Click to collapse
Which kernel?
Try Eureka
physwizz said:
Which kernel?
Try Eureka
Click to expand...
Click to collapse
MinhKer_Q-V14.7_Pro_fixed_Magisk20.4-A20
gasg said:
MinhKer_Q-V14.7_Pro_fixed_Magisk20.4-A20
Click to expand...
Click to collapse
Try eureka
physwizz said:
Try eureka
Click to expand...
Click to collapse
I did and when I change to file transfer it reboots everytime
gasg said:
I did and when I change to file transfer it reboots everytime
Click to expand...
Click to collapse
You might need to factory reset
physwizz said:
Try eureka
Click to expand...
Click to collapse
I used eureka and google seems to crash, also some apps/games become unresponsive and crash. You experienced this?
Tia for the reply
janjaninja said:
I used eureka and google seems to crash, also some apps/games become unresponsive and crash. You experienced this?
Tia for the reply
Click to expand...
Click to collapse
no
How? Mine google and certain apps always crash, dont know what the problem is, already tried rebooting,reflashing, reset. I only encountered problem with eureka, any other kernel is good.