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.
Related
Hi,
I would like to request some testers who are currently running stock MIUI to test the stock kernel. Feel free to comment below.
Instructions:
- You should be on CWM
- Download zip
- Flash kernel
- reboot
- cross your fingers
What to check:
- WLAN -> see if it works
Source:
https://github.com/emceethemouth/kernel_cancro/tree/mi-stock
WLAN:
git://codeaurora.org/platform/vendor/qcom-opensource/wlan/prima/
blah blah blah
Wifi not working after flashing the kernel.
Armin_van_buuren said:
Wifi not working after flashing the kernel.
Click to expand...
Click to collapse
Hold on I'm uploading a new one.
Edit:
Attachment updated
Wifi doesn't work, everything else does.
alphoz said:
Wifi doesn't work, everything else does.
Click to expand...
Click to collapse
Ok thanks, seems MIUI still has no proper fix for it. Anyways will keep this thread posted for any updates. Thanks!
Gnome said:
Ok thanks, seems MIUI still has no proper fix for it. Anyways will keep this thread posted for any updates. Thanks!
Click to expand...
Click to collapse
Thanks to you, and all your hard work. I would also like to mention that the miband unlocking worked a lot better with your kernel than the MIUI stock one. Thanks again.
Wow. Thanks GNOME... Good to kernel for miui
Sent from my MI 3W using Tapatalk
Audahudi also build stock miui kernel. This also has same bugs, no WiFi, cit etc menu take while to open.
One bug I have doubt of is, whether all 4 cores work simultaneously. In my testing I saw most time 2 work, sometimes 3. Benchmarks also give scores like that. Also CPU performance control pro, which can set individual frequency of all cores could make 2 cores work together.
Any app you know which can monitor every core usage over period of time?
The 2nd bug is what I'm curious off, as I don't have WiFi lol.
Plus these miui kernel can be used in some custom Chinese KitKat ROMs. Iuni is 1 example, fiui I havent tested.
Gnome said:
Ok thanks, seems MIUI still has no proper fix for it. Anyways will keep this thread posted for any updates. Thanks!
Click to expand...
Click to collapse
Thanks for your hard work. But did you read this? https://github.com/MiCode/Xiaomi_Kernel_OpenSource/wiki/How-To-Use
I tried to compile kernel according to this instructions. Compilation through without problems. But kernel freeze while booting. I am not kernel developer, so don't have experience, how to debug it. If you find time, please can you try it?
Thanks
Pepe.II said:
Thanks for your hard work. But did you read this? https://github.com/MiCode/Xiaomi_Kernel_OpenSource/wiki/How-To-Use
I tried to compile kernel according to this instructions. Compilation through without problems. But kernel freeze while booting. I am not kernel developer, so don't have experience, how to debug it. If you find time, please can you try it?
Thanks
Click to expand...
Click to collapse
That happened to me when I did all that.
I found no solution, so I left it.
@Pepe.II you should see the issues section, I'm always there.
https://github.com/MiCode/Xiaomi_Kernel_OpenSource/issues/16
@Gnome
on what miui we should try stable or developer ?
Stable just to be safe.
Edit: @alexret, can you try the instructions on that misleading turorial but use my kernel source? Branch is mi-stable. I have a feeling it'll work
@Gnome anything with the bug I have doubt of?
@Gnome I tried to flash your kernel STX-MI-PRIMA-TEST-2015-06-24 from first post attachment.
Its only kernel, no modules included. This has a effect, that no modules are loaded while booting. When i try load module manually, it crashes with this message:
[email protected]:/ # insmod /system/lib/modules/wlan.ko
insmod: init_module '/system/lib/modules/wlan.ko' failed (Exec format error)
Please, can you compile kernel with modules? Thanks
@Me_Ashish_ its MIUIs kernel source, its incomplete it needs a lot of patches. And yes this kernel is just stock MIUI I added nothing to it just the opensource wlan from qualcomm w/c they claim works.
@Pepe.II thats the idea, the kernel should have it by default already, no need for the modules to be included in the package. The Modules are being built with the zImage-dtb itself, adding those modules to rhe zip package is very wrong. Adding it to the kernel package for CM Bases ROMs are just a work around, and I tell you know it wont work on stock MIUI ROM, unless you build MIUI from source and use my kernel source to be built with it.
Gnome said:
@Me_Ashish_ its MIUIs kernel source, its incomplete it needs a lot of patches. And yes this kernel is just stock MIUI I added nothing to it just the opensource wlan from qualcomm w/c they claim works.
@Pepe.II thats the idea, the kernel should have it by default already, no need for the modules to be included in the package. The Modules are being built with the zImage-dtb itself, adding those modules to rhe zip package is very wrong. Adding it to the kernel package for CM Bases ROMs are just a work around, and I tell you know it wont work on stock MIUI ROM, unless you build MIUI from source and use my kernel source to be built with it.
Click to expand...
Click to collapse
As far as I understand it, you did not compile drivers as modules but compile them as part of the kernel?. Ok. But why, when I look in to kmesg log (/proc/kmesg), I find not a single mention about the WLAN. That's weird. Are you sure, that WLAN part is compiled correctly?
@Pepe.II if Im building kernels wrong, by all means please guide me on how to build kernels correctly.
Well if I'm getting this kind of critisczm might as well stop this. Anyways thanks for all that tested, I'm dropping this.
Gnome said:
@Pepe.II if Im building kernels wrong, by all means please guide me on how to build kernels correctly.
Well if I'm getting this kind of critisczm might as well stop this. Anyways thanks for all that tested, I'm dropping this.
Click to expand...
Click to collapse
Sorry, I only asking, because I do not understand how you work with drivers. Prima WLAN you set as a module but I do not see any module in a flashable zip. You assume that your kernel will use modules from stock MIUI kernel?
I do not criticize, just asking. if this sounds like criticism, so it is due to my poor English and i am sorry.
Hi,
I will release here my updated "boot.img" files for the Xperia XA Ultra Dual Sim.
You must have an unlocked bootloader to flash with Fastboot.
You don't need to be on the same firmware as the boot image that you want to flash.
You have to flash SuperSu again from TWRP just after flashed new boot to avoid bootloop.
All boot images have "ro.secure=0" and "ro.debuggable=1" in default.prop file
and "forcencrypt" of internal memory switched to "encryptable" in fstab.mt6755 file.
The Fastboot command is:
fastboot flash boot NAMEOFIMAGE.img
Click to expand...
Click to collapse
Follow the guide from @Yooooomi to flash new firmware on your Ultra to avoid bugs and brick: https://forum.xda-developers.com/xa-ultra/how-to/flashing-xa-ultra-flashtool-t3551319
Releases:
12/28/2016: From 36.0.B.2.109 kernel sources and Ramdisk from 36.0.B.2.109 firmware.
https://mega.nz/#!cxI3SJaC!o-aqc2gUZufDJefKaxGRxRhekEq32B1bIDB3ROxyd7Y
04/01/2017: From 36.0.B.2.146 kernel sources and Ramdisk from 36.0.B.2.146 firmware.
https://mega.nz/#!VhwRQLqR!rOqEFWeOC3IQKl4aDw7P_v0U2wmZtBPXk_MSDJMEy9k
hi
Does anyone has tested this ROM?
probably is break my devise, possible if there unbreak?
thanks all.
twhhhco said:
hi
Does anyone has tested this ROM?
probably is break my devise, possible if there unbreak?
thanks all.
Click to expand...
Click to collapse
Hi, it's not a Rom just a boot.img for unlocked bootloaders with stock kernel built from Sony open source archive.
36.2.B.2.109 boot should fix the front camera not focusing after root.
After testing I found out that the boot does have problems
Which are:
1-Screen doesn't turn off completely, it stays at a very dark state which can be noticed in extreme low light conditions and if u turn the screen back on u will notice a a static on the screen and then it functions normally.
2-system brightness level meter doesn't work but third party apps can be used to change that.
Hope that helps and u come with even better boot in the future and thank u in advance.
klengjaua said:
After testing I found out that the boot does have problems
Which are:
1-Screen doesn't turn off completely, it stays at a very dark state which can be noticed in extreme low light conditions and if u turn the screen back on u will notice a a static on the screen and then it functions normally.
2-system brightness level meter doesn't work but third party apps can be used to change that.
Hope that helps and u come with even better boot in the future and thank u in advance.
Click to expand...
Click to collapse
Hi, thank you for the feedback. I don't have any unlocked Ultra (only have a unlocked XA F3112) so I can't test new releases or try to debug anything. I don't make any changes to the kernel source code, only build the kernel and repack it in a stock ramdisk with very small changes for root, nothing more. I hope that an user will be able to fix bugs.
rrvuhpg said:
Hi, thank you for the feedback. I don't have any unlocked Ultra (only have a unlocked XA F3112) so I can't test new releases or try to debug anything. I don't make any changes to the kernel source code, only build the kernel and repack it in a stock ramdisk with very small changes for root, nothing more. I hope that an user will be able to fix bugs.
Click to expand...
Click to collapse
These are the fixes you mentioned?
Nrsoto said:
These are the fixes you mentioned?
Click to expand...
Click to collapse
Yes it's the new boot who fix the front camera bug mentioned in my PM, as you can see in the comments it fix this bug but make an other bug You can flash it if your device is a dual sim. If you try it please say us if you have the same new bug.
rrvuhpg said:
Yes it's the new boot who fix the front camera bug mentioned in my PM, as you can see in the comments it fix this bug but make an other bug You can flash it if your device is a dual sim. If you try it please say us if you have the same new bug.
Click to expand...
Click to collapse
I will do it with f3213
Nrsoto said:
These are the fixes you mentioned?
Click to expand...
Click to collapse
For those who are struggling with the front facing camera, I finally solved it without installing any kernel or modify anything from the system. Downgrade to 36.0.A.1.111 (should be the one one with service unit exchange or smth like that). Had installed gapps stock (but I suggest u don't delete the Sony camera app - Instagram and Snapchat work perfectly fine) + xposed + adoptable storage.
As a final mention my devie is F3211
sexxualization said:
For those who are struggling with the front facing camera, I finally solved it without installing any kernel or modify anything from the system. Downgrade to 36.0.A.1.111 (should be the one one with service unit exchange or smth like that). Had installed gapps stock (but I suggest u don't delete the Sony camera app - Instagram and Snapchat work perfectly fine) + xposed + adoptable storage.
As a final mention my devie is F3211
Click to expand...
Click to collapse
Sorry, how did you do it, my cel no focusing camera frontal before unlocked boot loader , you device Does the same
Nrsoto said:
Sorry, how did you do it, my cel no focusing camera frontal before unlocked boot loader , you device Does the same
Click to expand...
Click to collapse
Here's step by step what I did, I hope it will work for your device too:
1. Go to xperifirm and download the 36.0.A.1.111 firmware (service unit exchange)
2. Create a bundle on the flashtool within the firmware folder
3. Flash it
4. Happy rooting!
There is however something I have to mention about this fw: you'll probably not receive any system updates
IF U ARE A SNAPCHAT USER install Snapchat before messing the system up with xposed
sexxualization said:
For those who are struggling with the front facing camera, I finally solved it without installing any kernel or modify anything from the system. Downgrade to 36.0.A.1.111 (should be the one one with service unit exchange or smth like that). Had installed gapps stock (but I suggest u don't delete the Sony camera app - Instagram and Snapchat work perfectly fine) + xposed + adoptable storage.
As a final mention my devie is F3211
Click to expand...
Click to collapse
Since you've mentioned snapchat allow me to ask. I'm on stock and I've just received the 36.0.B.2.109 update (hings are kinda slow in Egypt).
But no matter how many updates I get, snapchat quality is terrible on the front facing shooter. It's only good when it's really sunny. Other than that it's extremely dark to the point that sometimes you can't even recognize faces ! Have you ever run into that ? If yes or no what do you recommend ?
Talal Tango said:
Since you've mentioned snapchat allow me to ask. I'm on stock and I've just received the 36.0.B.2.109 update (hings are kinda slow in Egypt).
But no matter how many updates I get, snapchat quality is terrible on the front facing shooter. It's only good when it's really sunny. Other than that it's extremely dark to the point that sometimes you can't even recognize faces ! Have you ever run into that ? If yes or no what do you recommend ?
Click to expand...
Click to collapse
I had one bug with snapchat on the same firmware you are using but it was more app related rather than a camera quality issue. every time I opened sc the image would tend to get darker (not to mention the app itself was kinda slow) and the only fix I could find is moving the app back to internal storage (but again, this was an app bug). the only thing i can tell you is experimenting with other fws until you find one that could fix your issue, otherwise sorry but i have no idea.
sexxualization said:
I had one bug with snapchat on the same firmware you are using but it was more app related rather than a camera quality issue. every time I opened sc the image would tend to get darker (not to mention the app itself was kinda slow) and the only fix I could find is moving the app back to internal storage (but again, this was an app bug). the only thing i can tell you is experimenting with other fws until you find one that could fix your issue, otherwise sorry but i have no idea.
Click to expand...
Click to collapse
I've had this issue on all firmwares up until the one i mentioned. And yeah i didn't even use my external usage yet, so it seems that im having a different issues although we both got dark images. I would try different firmwares but I dont know what sony did to make the battery much better on the recent firmware. I'll try messing around till I find the culprit.
Thanks.
Buggy with f3216...please fix
Help Downgrading to .111
So I've download the .111 service exchange unit firmware from Xpefirm, and created a bundle to flash it through flash tool, this is what I get in the attachment. What wrong am I doing here ? This is my first time dealing with Xpefirm so please guide me on what do from here
Hi !
I've tested that because I really like root and it's works for me, but I have one problem with snapchat, when I try to connect I get this message :
I don't have xposed on this phone, just the root, and if I delete the root, it's the same problem.
Have you a solution for that ?
Thank you !
Pandawa3 said:
Hi !
I've tested that because I really like root and it's works for me, but I have one problem with snapchat, when I try to connect I get this message :
I don't have xposed on this phone, just the root, and if I delete the root, it's the same problem.
Have you a solution for that ?
Thank you !
Click to expand...
Click to collapse
By deleting root, I assume you tried to delete the root app not root access itself.
You have to go back to stock rom, install snapchat, log in, root your phone and never log out.
szucsi1996 said:
Buggy with f3216...please fix
Click to expand...
Click to collapse
Hi, how is it buggy? I would like to root my f3216, thx.
Aphex33 said:
Hi, how is it buggy? I would like to root my f3216, thx.
Click to expand...
Click to collapse
i think, don't do it!
edit: Brightness adjustment not working, ui very buggy, etc.
complied from https://github.com/therootlord/android_kernel_motorola_msm8953
not my code, just sharing because i keep seeing people complain about magisk mods
Features:
-F2FS bug fixed (can flash magisk modules on stock)
-not sure what else
Flash in twrp
TODO:
-kexec-hardboot
-disable force-decrypt
Stock NPS26.116-45 kernel zip: Link
This was my first kernel compilation, let me know if something isn't working
Extreme-Plus-Kernel-nrdgd-1.zip compiled on nov-18-2017 Link: Google Drive
UPDATE, just found out wifi doesnt work, sorry, been traveling and didnt think to test. everything else seems to work tho.
heres an older version of the kernel not compiled by me until i figure this out
UPDATE 2 - wifi fixed
Extreme-Plus-Kernel-nrdgd-2.zip compiled on nov-19-2017 Link: Google Drive
It boots with aex 7.x - to early to say more
Phazmos said:
It boots with aex 7.x - to early to say more
Click to expand...
Click to collapse
wifi doesnt work for me, let me know if its working on yours and which model you have if you can
until then check OP for older version of the same kernel
wifi fixed
Ae3NerdGod said:
wifi doesnt work for me, let me know if its working on yours and which model you have if you can
until then check OP for older version of the same kernel
wifi fixed
Click to expand...
Click to collapse
Didn't notice it was broken - us version here.
It booted, but was very slow and laggy, even did a system cache wipe....Then restoring the default boot.img had wifi not working....Just FYI for those who want to try...Do a backup
Is the only benefit to have magisk modules on stock rom? I have XT1806 rooted TWRP r9 Gladius Magisk 14.3 flashed this kernel but kept booting straight to recovery...had to do a full restore. I'm looking for custom kernels that provide speed and power benefits. Thanks
Would you mind sharing the build sequence/commands?
THERAJ12 said:
Is the only benefit to have magisk modules on stock rom? I have XT1806 rooted TWRP r9 Gladius Magisk 14.3 flashed this kernel but kept booting straight to recovery...had to do a full restore. I'm looking for custom kernels that provide speed and power benefits. Thanks
Click to expand...
Click to collapse
Just a note on kernels
I've tested many many kernels on many devices. When they are configured the same, performance/battery is about the same. Any difference was slight enough to be considered noise in the test methods. I always suggest to learn about kernel parameters then tweak it to the way you want. Any kernel will give more performance, or battery life, or anything between - all depends on how you configure it.
Ps - same device, same twrp, supersu instead of magisc, no problems. Except seems not compatible with ex kernel manager - it doesn't apply settings. I believe it doesn't set proper permissions to be able to write. But hey, it's young and a stockish kernel, hope to see more.
Phazmos said:
Just a note on kernels
I've tested many many kernels on many devices. When they are configured the same, performance/battery is about the same. Any difference was slight enough to be considered noise in the test methods. I always suggest to learn about kernel parameters then tweak it to the way you want. Any kernel will give more performance, or battery life, or anything between - all depends on how you configure it.
Ps - same device, same twrp, supersu instead of magisc, no problems. Except seems not compatible with ex kernel manager - it doesn't apply settings. I believe it doesn't set proper permissions to be able to write. But hey, it's young and a stockish kernel, hope to see more.
Click to expand...
Click to collapse
EXKM seems to work fine on AEX rom using the butterfly governor good battery life and smooth.
revengineer said:
Would you mind sharing the build sequence/commands?
Click to expand...
Click to collapse
i had to use his toolchain, and fix a few includes for it to work. im going to try different ones to try and figure out the lag, maybe thats not whats causing it but im new at this . been reading logs all day
smokinjoe2122 said:
It booted, but was very slow and laggy, even did a system cache wipe....Then restoring the default boot.img had wifi not working....Just FYI for those who want to try...Do a backup
Click to expand...
Click to collapse
yeah, sorry. new at this. dont know if @geneticengineer wants me passing his old kernels he hasnt posted around either. if you can find his afh, he has a really old one on there thats way faster. im still learning, im working on pulling the stock modules and kernel to make a back to stock zip rn actually will post soon if you keep using it, it speeds up a tiny bit lol
THERAJ12 said:
Is the only benefit to have magisk modules on stock rom? I have XT1806 rooted TWRP r9 Gladius Magisk 14.3 flashed this kernel but kept booting straight to recovery...had to do a full restore. I'm looking for custom kernels that provide speed and power benefits. Thanks
Click to expand...
Click to collapse
planning kexec hardboot and disable force decrypt when i get the hang of this.
Phazmos said:
Just a note on kernels
Ps - same device, same twrp, supersu instead of magisc, no problems. Except seems not compatible with ex kernel manager - it doesn't apply settings. I believe it doesn't set proper permissions to be able to write. But hey, it's young and a stockish kernel, hope to see more.
Click to expand...
Click to collapse
actually i think i missed something in defconfig that enables the secondary processor, im also going to switch toolchains, expect a new kernel in a few days
Here's a link to GeneticEngineer's AFH-hosted original kernel from the TWRP thread. I don't think he'll mind it being reposted in this thread. This should tide people over until you can iron out the bugs in your build.
https://www.androidfilehost.com/?fid=745425885120765462
Thanks for picking up the baton and running with it, incidentally. I did ask GeneticEngineer to create a thread for his kernel but perhaps he missed the message.
THERAJ12 said:
Is the only benefit to have magisk modules on stock rom? I have XT1806 rooted TWRP r9 Gladius Magisk 14.3 flashed this kernel but kept booting straight to recovery...had to do a full restore. I'm looking for custom kernels that provide speed and power benefits. Thanks
Click to expand...
Click to collapse
i actually get those weird reboot to recovery bugs all the time on this device and 2 things fix it, booting to bootloader and picking "start" or a full restore
I tried version 2. I still couldn't get it to pass Magisk SafetyNet. I also noticed that this kernel breaks fingerprint gestures.
bishop0114 said:
I tried version 2. I still couldn't get it to pass Magisk SafetyNet. I also noticed that this kernel breaks fingerprint gestures.
Click to expand...
Click to collapse
GeneticEngineer's original both passes SafetyNet and leaves fingerprint gestures functional on my otherwise stock single Sim EU version:
https://www.androidfilehost.com/?fid=745425885120765462
Loccy said:
GeneticEngineer's original both passes SafetyNet and leaves fingerprint gestures functional on my otherwise stock single Sim EU version:
https://www.androidfilehost.com/?fid=745425885120765462
Click to expand...
Click to collapse
Thanks. I tried it and still wouldn't pass SafetyNet. The fingerprint gestures worked though. I am running it on a secondary ROM. Maybe that is causing the issue?
Loccy said:
GeneticEngineer's original both passes SafetyNet and leaves fingerprint gestures functional on my otherwise stock single Sim EU version:
https://www.androidfilehost.com/?fid=745425885120765462
Click to expand...
Click to collapse
I've built a fully working stock kernel which has the needed commits for Magisk modules to work correctly and passes SafetyNet [emoji6]. Need to do some more updating (upstream) but I plan on posting it soon, probably new thread (Resurrected Kernel).
bishop0114 said:
Thanks. I tried it and still wouldn't pass SafetyNet. The fingerprint gestures worked though. I am running it on a secondary ROM. Maybe that is causing the issue?
Click to expand...
Click to collapse
A stock based kernel isn't gonna play well with custom ROMs, unless your secondary ROM is a stock ROM? I plan on creating one for cm-14.1+ based ROMs too.
Jleeblanch said:
I've built a fully working stock kernel which has the needed commits for Magisk modules to work correctly and passes SafetyNet [emoji6]. Need to do some more updating (upstream) but I plan on posting it soon, probably new thread (Resurrected Kernel). A stock based kernel isn't gonna play well with custom ROMs, unless your secondary ROM is a stock ROM? I plan on creating one for cm-14.1+ based ROMs too.
Click to expand...
Click to collapse
If you need someone to beta test it, let me know. It is the only reason I am not running stock.
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:
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?