Related
So....i Tried out treble and even though performance was'nt really the best...arrow OS pie and pixel dust pie Werke the 2 Roms i liked the most....so i decided to ask in the Forums who would like to port either
Is anyone actually Viewing this?
Did you try before, with mtk was easy, but in Snapdragon it's harder, I tried with the ROMS from Redmi Note 3 Pro, since both have the same processor could boot up
I tried but the screen gets dark and never booted, maybe with the correct vendor files but since I don't own a PC it's impossible for me
realthrash said:
Did you try before, with mtk was easy, but in Snapdragon it's harder, I tried with the ROMS from Redmi Note 3 Pro, since both have the same processor could boot up
I tried but the screen gets dark and never booted, maybe with the correct vendor files but since I don't own a PC it's impossible for me
Click to expand...
Click to collapse
I did....lets say it wasnt a good decision...
Some random said:
I did....lets say it wasnt a good decision...
Click to expand...
Click to collapse
I had to reflash EVERYTHING ( including stock kernel...for some weird reason )
But you know...I could potentially try and contact pixel dust/arrow os team.....or when I wanted to pixel experience team....right?
realthrash said:
Did you try before, with mtk was easy, but in Snapdragon it's harder, I tried with the ROMS from Redmi Note 3 Pro, since both have the same processor could boot up
I tried but the screen gets dark and never booted, maybe with the correct vendor files but since I don't own a PC it's impossible for me
Click to expand...
Click to collapse
I just realised I f***ed up because I followed wrong instructions....could you give me a "Tutorial" or how you flashed it?
Some random said:
I just realised I f***ed up because I followed wrong instructions....could you give me a "Tutorial" or how you flashed it?
Click to expand...
Click to collapse
https://forum.xda-developers.com/android/software-hacking/guide-port-64-mtk-roms-t3555933
I couldn't find the link, but you can try with this one, it's similar
Why didn't I just think about compiling a ROM from source?
Some random said:
Why didn't I just think about compiling a ROM from source?
Click to expand...
Click to collapse
Failed.....no PC access
Like I said, you can't compile those ROMs from source simply because there is no source. Whatever you get out of the compiler will crash and burn, be incompatible, or be a GSI.
iH8Ecchi said:
Like I said, you can't compile those ROMs from source simply because there is no source. Whatever you get out of the compiler will crash and burn, be incompatible, or be a GSI.
Click to expand...
Click to collapse
What about installing the rom...from a device with identical specs?
Some random said:
What about installing the rom...from a device with identical specs?
Click to expand...
Click to collapse
That's called porting. For example you can port RR from the Redmi Note 3 using Chippa_a's LOS 16 as base.
Problem is, in most cases you will have a combined set of bugs from both ROMs.
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:
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.
thank to derfelot he's a cool guy he help me a lot :good:
because of the nfc chip were different this cause kernel to wake or even random reboot
all you need to do is go to turn off nfc setting first [rooted need] go to
/vendor/lib/modules
and delete or rename file call pn553.ko
restart done
nfc will not work :good:
picture of cpu spy https://ibb.co/PjV135Z
Thanks for sharing! Previously i did try remove everything related nfc in /system which didn't work out for me, Now my SOV36 finally go deep sleep!
tq so much bro, its weird when phone run hotter
Does this also solves the random reboots?
yes nfc also cause reboot
my phone can't unlock bootloader . i cant't root
Been using this fix for 2 weeks on my SOV36 running Bliss ROM and I'm glad to say this resolved the random reboots.
I'm curious now, so in the original JP roms in the same /vendor/lib/modules, there are some files that got the same name as in any global and custom roms, but there's one file that's got "NFC" in the name, also has the .ko extension too. I wonder if we name that .ko file from the JP ROM to pn553.ko and put it in the global/custom roms, would NFC work? I haven't try it for myself lmao
you can't deferlot from xda said that chipset is different the only way is to build new kernel from source
ah that's a shame, but at least the random reboots are gone lmao thanks for the follow up!
Wangan_Beginner said:
ah that's a shame, but at least the random reboots are gone lmao thanks for the follow up!
Click to expand...
Click to collapse
I can have a crack at making a build for the Japanese variant with the correct kernel driver, but I don't know yet when I will have the time.
i7u
derf elot said:
I can have a crack at making a build for the Japanese variant with the correct kernel driver, but I don't know yet when I will have the time.
Click to expand...
Click to collapse
Damn it's the legend him/herself?? for real tho i personally rarely use the NFC (like, probably only twice a year, not that many place to use it in my country anyway lol) so I definitely not gonna push you to make it work, but I won't restrain you either lmao
derf elot said:
I can have a crack at making a build for the Japanese variant with the correct kernel driver, but I don't know yet when I will have the time.
Click to expand...
Click to collapse
how about if i debloat app NFC on /system/app/NfcNci/NfcNci.apk?
because i have ubl No, so i can't root my phone
is it solve a deep sleep problem?
charly.novianto said:
how about if i debloat app NFC on /system/app/NfcNci/NfcNci.apk?
because i have ubl No, so i can't root my phone
is it solve a deep sleep problem?
Click to expand...
Click to collapse
you can with temp root by j4nn
Hi everyone,
I've bought the same phone (SOV36 from AU), and I have the problem of reboots. I can't afford now a new phone, and I would like to know how to fix it... But I'm not expert. Would you be kind enough to explain me what I have to do exactly?
I've this build number (I don't know if it could be useful) : 47.2.A.11.228
Thank you so much in advantage.
Inviato dal mio G8341 utilizzando Tapatalk
TEK023 said:
thank to derfelot he's a cool guy he help me a lot :good:
because of the nfc chip were different this cause kernel to wake or even random reboot
all you need to do is go to turn off nfc setting first [rooted need] go to
/vendor/lib/modules
and delete or rename file call pn553.ko
restart done
nfc will not work :good:
picture of cpu spy https://ibb.co/PjV135Z
Click to expand...
Click to collapse
Can you please tell me how to root xperia Xz1
This file was not found in the modules directory of Android 11 system
jackeyloveno1 said:
This file was not found in the modules directory of Android 11 system
Click to expand...
Click to collapse
just flash this done :
(Shared) Updated POP-KERNEL (4.4.267) For G8431/2 and XZ1 AU
download (.267) 1 May 2021 **SOV36-AU NO NFC support download (.267) 1 may 2021 ***G431-G432 Download (.261) pixel 2 (kernel fork) 21 april 2021 Device still have heating ? : completely get rid of nfc files relate in vendor folder in root...
forum.xda-developers.com
Can I just replace all files related to the NFC?
Hi,
Anyone install dual boot windows yet? I tried using QEMU but it runs really slow and not really useable.
Thanks.
kong1708 said:
Hi,
Anyone install dual boot windows yet? I tried using QEMU but it runs really slow and not really useable.
Thanks.
Click to expand...
Click to collapse
AFAIK no one has done it yet with significant success.
Even if successful, hardware has to be shared or better splitted for two different systems. So performance will surely be decreased.
It_ler said:
AFAIK no one has done it yet with significant success.
Even if successful, hardware has to be shared or better splitted for two different systems. So performance will surely be decreased.
Click to expand...
Click to collapse
Do you think we could DualBoot Chrome os instead? Or even an ARM version of Windows?
Amanpreet2000 said:
Do you think we could DualBoot Chrome os instead? Or even an ARM version of Windows?
Click to expand...
Click to collapse
I really don't know, as I do not own this device myself and am not interested in dual boot option.
Pre-requirements would be to implement a dual boot feature to boot system(s) from different partitions.
I could not find such a feature implemented for your device yet.