Develop Bugs

[ROM] [LP 5.1.1] Validus Unofficial Hardened Updated June 17

Rom updated to LP 5.1.1 on June 17. All latest features included:
My Changes:
1. Thermanager values fixed to prevent flickering and low charging. There is ZERO flickering.
2. Camcoder mike low recording sound fixed
3. VOLTE enabled (if and when your carrier implements it). If you go to Network, you'll see Volte enabled; also in phone test menu, you will see VOLTE flag enabled
4. WIFI background scanning disabled - better battery life
5. GSM Network is handled by System, as opposed to Modem
6. Shady IPs cleaned thought the rom
7. Kernel with Overclock, Voltage, Screen Color and TWRP integrated.
9. All usual hardened features in kernel (see original description below)
Download: http://forum.xda-developers.com/devdb/project/dl/?id=13068
Do a clean flash, since this is LP 5.1.1
_______________________________________________________________________________________________________
Rom updated March 20. Over 800 downloads in 8 days and 6 "thanks you". Thanks...
Some changes: sound control in kernel which allows to compensate for low camera mike recording (use Trickster mode or similar app); wifi background scanning is disabled - better battery life; latest validus and cm changes
DOWNLOAD LINK: http://forum.xda-developers.com/devdb/project/dl/?id=11628
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Here is the latest Validus LP compiled from sources on March 11. Latest CM changes including FM Radio
Changes:
1. Kernel with all ciphers, hashes, random number generation enabled
2. SeLinux disabled, Tomoyo security enabled
3. 256 bit encryption with increased key length and 5000 iteration, as opposed to weak 2000
4. Latest CM and Validus changes including black interface and changing keyboard theme based on app color
5. Black Contacts fixed (now white text on black background)
6. Led lights normal brightness fixed
7. TWRP 2.8.X integrated into kernel
DOWNLOAD LINK: http://forum.xda-developers.com/devdb/project/?id=8646#downloads
Install:
1. Be on Kitkat at least, rooted and with recovery
2. Enter recovery, wipe System/Cache/Data
3. Flash the rom
4. Flash data from your previously saved Lollipop rom (optional, but works on my device)
5. Reboot and enjoy
Credit: Validus Team, Slimroms, AOSP, Cyanogenmod, Omniroms
Warning: I am not responsible for death and destruction resulting from flashing this rom. You are on your own.
Kernel Source: https://github.com/HonamiZ1/kernel_sony_msm8974
XDA:DevDB Information
Validus Lollipop Unofficial, ROM for the Sony Xperia Z1
Contributors
optimumpro
Source Code: https://github.com/Team-Validus/android
ROM OS Version: Lollipop
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Unlocked Bootloader
Based On: AOSP Cyanogenmod
Version Information
Status: Testing
Created 2015-03-12
Last Updated 2015-06-17

Screen Shots
Screen shots added.

For those who are interested in encrypting the data partition. Remember, there is no longer any visible slowdown. What you need to do before or after encryption is to enable "Disable HW overlay" in Developer Options. There is a catch, though: this won't stick after reboot unless you implement an init.d script that will take care of this.
Here is the script : http://d-h.st/QIiE
Download the script by using the blue button (unless you want their ridiculous exe. download manager)
Put the script into /system/etc/init.d with at least 750 permission and reboot. You will see that Disable HW overlay option is ticked by default.
Also, I recommend ADB shell encrypting, as opposed to doing it from Security menu for several reasons: first with ADB you are not limited by 16 characters, you can use a passphrase that you can remember and no one can break; second, in Security menu, encryption will use your pin password (which is short) to encrypt. Remember, you only need a long passphrase to boot, and if your rom has "soft reboot", you don't need to enter password at all. Here is how to do it:
1. Go to Security menu and enable Pin/Password/Pattern or None. Your screen password could be short, as it is independent from boot password.
2. Next, pick a long boot password. You need to convert it into hex: just use this site https://www.online-toolz.com/tools/text-hex-convertor.php for conversion. Now, copy your hexed password (for future pasting).
3. Next, go to Developer Options and enable ADB; Root for ADB + APPS
4. Connect your phone to your computer
5. Open Terminal and type "adb shell" without quotes and press enter
6 Then type "su" also no quotes and press enter
7. Now type the following without quotes: vdc cryptfs enablecrypto inplace password HERE PASTE YOUR ACTUAL HEXED PASSWORD and press enter. Remember, don't type HERE PASTE YOUR PASSWORD, instead paste your hexed password there.
8. After you press enter, your phone will reboot and start encrypting. In a few minutes, you will get another reboot and a prompt for boot password. Here, enter your actual password (not the hexed one). Your phone will boot and you can check in the Security options that your phone is encrypted.
Enjoy.

Can u tell what the bugs?
Sent from my C6903 using XDA Premium 4 mobile app

meliacentrum said:
Can u tell what the bugs?
Sent from my C6903 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
CM bugs....

Do Google Services work on this build?

Gonna try it but I assume they might crash as with the other hardened builds
---------- Post added at 07:04 PM ---------- Previous post was at 07:01 PM ----------
Has this got the landscape rotation sys ui crash bug

shingers5 said:
Gonna try it but I assume they might crash as with the other hardened builds
---------- Post added at 07:04 PM ---------- Previous post was at 07:01 PM ----------
Has this got the landscape rotation sys ui crash bug
Click to expand...
Click to collapse
Encryption has nothing to do with gapps crashing. The only thing that could be related is android_logger=n in kernel. I guess gsf can't log your every key stroke without that function in kernel. So, any other lp kernel would do. I may recompile the kernel with that option on.

Good compilation
My previos ROM was RR. Trying this. Data was restored from RR is normal.
I like this Validus ROM
All what I want is included + Black Theme (Default)

Xprivacy works? Can't nmake it work on cm12( asks kernel modification)
Sent from my TegraNote-P1640

Instruction for Encrypting Data Partition
See post #3 on how to encrypt your data partition without any visible slowdown.
http://forum.xda-developers.com/showpost.php?p=59392722&postcount=3

ggs2 said:
Xprivacy works? Can't nmake it work on cm12( asks kernel modification)
Sent from my TegraNote-P1640
Click to expand...
Click to collapse
The only two roms that work with Xposed Xprivacy from start are my versions of Resurection Remixed and Slim LP (remember, I have SElinux disabled in my kernels). So, if you want those, flash Resurection, then install your favorite apps including Xposed and Xprivacy, then backup the data. Then do a clean flash of Validus, then flash Xposed binary (before rebooting), then restore Data from Resurection and reboot. It works. If you look at screenshots I posted, you will see I have Xprivacy working.

I actually like thia ROm and the default theme too. Been using since flashing and gapps work. Had a few issues but flashed banks gapps and they worked fine

Does this have low LED bug? Can't see LED... tried xposed that works though:
optimumpro said:
The only two roms that work with Xposed Xprivacy from start are my versions of Resurection Remixed and Slim LP (remember, I have SElinux disabled in my kernels). So, if you want those, flash Resurection, then install your favorite apps including Xposed and Xprivacy, then backup the data. Then do a clean flash of Validus, then flash Xposed binary (before rebooting), then restore Data from Resurection and reboot. It works. If you look at screenshots I posted, you will see I have Xprivacy working.
Click to expand...
Click to collapse

ggs2 said:
Does this have low LED bug? Can't see LED... tried xposed that works though:
Click to expand...
Click to collapse
Led is fixed, unless you use a different kernel.

optimumpro said:
Encryption has nothing to do with gapps crashing. The only thing that could be related is android_logger=n in kernel. I guess gsf can't log your every key stroke without that function in kernel. So, any other lp kernel would do. I may recompile the kernel with that option on.
Click to expand...
Click to collapse
Do I understand correctly that gapps will not work here? Could the missing module be shipped and downloaded as 'ko' file or does it have to be compiled in?

steveeJ said:
Do I understand correctly that gapps will not work here? Could the missing module be shipped and downloaded as 'ko' file or does it have to be compiled in?
Click to expand...
Click to collapse
I don't use Gapps, but another user a few posts above said they worked...

optimumpro said:
Led is fixed, unless you use a different kernel.
Click to expand...
Click to collapse
Doesn't work. if i restore data from RR in validus, i end up in bootloop even though I have only installed Xposed/Xprivacy in RR..
Can't use RR because LED is tooo low.
Would keep an eye, till the time validus by itself can support Xprivacy (if it does !)
Thanks...

ggs2 said:
Doesn't work. if i restore data from RR in validus, i end up in bootloop even though I have only installed Xposed/Xprivacy in RR..
Can't use RR because LED is tooo low.
Would keep an eye, till the time validus by itself can support Xprivacy (if it does !)
Thanks...
Click to expand...
Click to collapse
Did you follow directions in my other post? Did you install xposed and xprivacy in Resurection? I have validus with data restored from Resurection and xposed and xprivacy work fine.

optimumpro said:
I don't use Gapps, but another user a few posts above said they worked...
Click to expand...
Click to collapse
gapps seem to work so far!
I'm currently trying to mount the sdcard which is ext4 formatted. I can mount it manually via the shell, but vold won't notice any of that. I guess I need to figure out how to persistently change /fstab.qcom file.

[Rom] Updated February 9: AOSP Jaguar Honami OFFICIAL-HYPERTOOL 5.4

This is the Official Jaguar rom for Honami, which is based on AOSP with some flavors from Slim and Dirtyunicorn. The main difference from other roms is the emphasis on security and multiple features. With that in mind , let's see what Jaguar has to offer:
1. Hardened Kernel, modified M5 built with UBERTC 6.0; hardened rom built with HYPERTOOL 5.4
2. CPU overclocked to 2572 and GPU to 600
3. All ciphers enabled in kernel instead of just a few
4. Hardened/Fortified Bionic and Libs
5. Fstack protection strong to resist buffer overflows
6. Many System apps and processes are made read-only, to reduce elevation of privilege
7. Selinux replaced with Tomoyo and Yam security
8. Disc encryption, keymaster to 256 bit AES instead of 128
9. Latest TWRP with working brightness and ability to decrypt Data
10. Random number generation mixed hardware/software, as recommended by Linus Torwalds
11. Options to randomize host on every boot
12. Option to have a separate password for lock screen and boot
13. Qualcomm's Time Services disabled due to leaking on early boot. Instead, Timekeep is ported from Nougat (time set locally without Internet or GSM signal)
14. WIFI Background Scanning disabled to prevent leaking
15. Internet disabled for both WIFI and Data until Afwall is set and activiated (Afwall included in download, install as regular app)
16. The phone is VOLTE ready and you have all network options available in Cell menu (not just LTE/WCDMA/GSM)
17. GRsecurity features, such as Sidechannel implemented
18. Some Pax Security Features
19. Option to deny USB connection: denied always; denied when locked; and allowed always
20. Hardened webview with Google and other "interesting" IPs removed
21. Prevention of bruteforcing screen pin: the phone will reboot upon 3 unsuccessful attempts
22. Perfect_Event_Paranoid ported from Grsecurity: now third party apps can't use other apps including system to elevate privileges
23. Camera hardware button works to focus, take pictures and start video recording
24. Option to disable writing to Tombstones (a lot of private info is dumped there if there is a crash)
25. Option to disable continuing writing of logcat
26. Option to disable device cameras: back; front, both or none
27. Always latest Google Security Patches
28. Always latest Code Aurora Security Patches
29. Changes ported directly from Google Android Gerrit, so most of those in MM and even N are in this rom
30. About 80% of kernel changes are ported into Jaguar kernel from 3.10 and 3.18 (not Sony AOSP 3.10, but Linux/Google/Code Aurora one)
31. Rom is odexed to significantly increase boot speed (under 30 seconds) and application start
32. Many more security features ported from Linux and Copperhead OS
33. Sony Timekeep
34. DNS Encryption, as well as the choice of multiple DNS providers
Other features include: Stereo Sound; Layers Theme Engine; Native Call Recording with interface integrated in Dialer with no restrictions; Privacy Guard; Native Wakelock Blocker; Native Black List; Global Menu; Slim Recents; Traffic Indicators; Advanced Reboot; Slim Pie; CPU Info on Screen; Ram Bar in Recents; Open source Superuser included and integrated in Settings; True Offline Charging with Screen Off; Kernel Adiutor included (unzip and install as a normal app) and integrated in Settings; FM Radio and Recording plus more
Things users need to know to have smooth experience:. These are not bugs, but rather an explanation of some features
1. If you want to do data encryption, keep in mind that unlike Android, Jaguar uses 256 bit encryption. If you were encrypted on other roms, you won't be able to decrypt. So, wipe encryption and then re-encrypt on Jaguar. Also, keep in mind that if you ever did factory reset on official TWRP 3+ for honami, your data partition is screwed and have to be resized to enable encryption. This has nothing to do with the rom, but rather with the official TWRP itself. Fastboot my unofficial TWRP 3.0.2, which, by the way has working brightness, as well as ability to decrypt and mount data
2. Jaguar contains a script running on early boot, which cuts the internet access to both WIFI and Data until Afwall is running. This is done to prevent leaking, as well as having all your internet traffic routed through some interesting number of servers, including this IP: 26.147.196.22. So, install Afwall and activate it, otherwise, no Internet for you
3. If your system language is different from English and you want to make changes in Phone/Cell Network settings, switch to English first, make the changes and then return to your language. The changes you made will hold. If you try to make the changes in your language, you will have com.android.phone crash. Localization takes time and is virtually impossible to implement in Jaguar, which is a one-person-rom
4. Qcom Time Services daemon is disabled to prevent leaking. That means that you have to set Time/Zone to automatic to get it directly from your carrier. Otherwise, you won't have the correct time on reboot. Forget it. Sony TimeKeep is now setting the correct time on reboot and without the Internet, even in Airplane mode
5. Dnscrypt: in Settings/Security you have a new feature allowing the use of different dns providers (all encrypted), instead of your provider's default one. In Afwall, you must allow access to 'apps running as root'. Otherwise, no internet
6. Supersu is no longer bundled with the rom. Activate Developer settings and enable builtin root there. Open source Superuser is now included. Activate root choices within the app
7. If you use Gapps, they must be flashed right after the rom and before reboot. If you reboot even once, you will have multiple Gapps f/c due to incorrect permissions
Download: All updates and change logs are in Post #3 now
Instructions:
YOU MUST HAVE LATEST STOCK LP 5.1.1 FLASHED ONCE ON YOUR DEVICE. Otherwise, you may experience hardware (mainly Gps problems). If after the official LP 5.1.1, you downgraded to any other official stock version, you must reflash stock LP 5.1.1
1. Have TWRP (fastboot my unofficial version), unlocked bootloader and root.
2. In TWRP, wipe data/factory reset, then wipe System/Data/Cache/Dalvik
3. Flash the rom
4. If you use xposed, flash the latest installer. Xposed no longer works and will never work with roms that incorporate Nougat security features. Xposed used a security hole that was closed by Google. Bye bye Xposed...
5. If you want Gapps, flash them before any reboot. Otherwise, you will have multiple problems due to permissions.
6. Reboot, install Afwall and Kernel Adiutor as normal apps; activate Afwall to have Internet
7. Enjoy the rom, say thank you, donate or do both
Warning: If your device and/or anyone in the immediate vicinity dies, don't blame me: it is all China and Russia's fault. :laugh:
Credit: CM, AOSP, Slimroms, DU, Copperhead OS, Myself5 (kernel)
UPDATED KERNEL SOURCE: https://forum.xda-developers.com/devdb/project/dl/?id=23107 . Don't flash. This is not kernel, but rather sources to compile kernel
Kernel Sources: https://github.com/AOSP-Argon/android_kernel_sony_msm8974
XDA:DevDB Information
Jaguar Rom , ROM for the Sony Xperia Z1
Contributors
optimumpro
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Unlocked Bootloader
Based On: AOSP, Slimroms, DU
Version Information
Status: Stable
Current Stable Version: 6.0
Stable Release Date: 2016-02-09
Created 2015-08-29
Last Updated 2017-02-09

Update on Further developemnt
February 16. I broke my Z1 screen again and I am not in the mood for after market screens. And I am sick and tired of Sony crappy treatment of development community.
I am now looking at Lenovo Zuk Z2 or Z2 pro. Both excellent phones with the latest CPU and made out of metal and glass by Motorola which they bought from Google a couple of years ago. Zuk is friendly to developers and their blobs don't dumb down camera and they don't seek to "unify" bugs for all their devices. I no longer wish to support a fat bastard corporation that can't make a good phone, but thinks that just by putting their logo on the phone would make it worth $700.
RE Jaguar. I will continue to maintain Jaguar mainly with security patches... for a while, but my main work will be concentrated on Zuk. There is a lot of work to be done cleaning Android N and implementing security and other features from Jaguar...

This is where you get the latest update
March 21. New release:
1. March Security patches
2. New Superuser
3. Updated kernel
Download: https://forum.xda-developers.com/devdb/project/dl/?id=23814
____________________________________________________________________________
February 9. New release:
1. February Security patches
2. DNS_Crypt (in settings/security)
3. Seccomp (secure computing implemented in kernel)
4. Open Source Superuser integrated
5. Silent SMS notification enabled
6. 1440p profile in camcorder added
If you enable Dnscrypt and you use Afwall, allow internet to apps running as root...
If you prefer closed source Supersu, just flash the zip...
Download: https://forum.xda-developers.com/devdb/project/dl/?id=23069
____________________________________________________
January 20. Good News! Time service completely fixed. Qcom's crappy and creepy service taken out and replaced with Sony open source TimeKeep ported from MM/N. No connection to the internet needed. Everything is done locally on the device. TWRP has also been modified to set the correct time on boot.
The wayTimeKeep works is that before the shut down, it saves the properly set time and on reboot restores it (after the down time calculation). TWRP also reads that value on boot. For those who have encrypted data: the correct time in TWRP will be set after you enter boot password and data is decrypted and mounted.
Download Rom: https://forum.xda-developers.com/devdb/project/dl/?id=22743
Download TWRP: https://forum.xda-developers.com/devdb/project/dl/?id=22742
___________________________________________________________________________________
January 5. New release with January security patches and more. Also back is qcom time domain.
Download: https://forum.xda-developers.com/devdb/project/dl/?id=22428
You may flash dirty if on a previous release. Otherwise, fresh install (read directions)
P.S. This build included an experimental kernel. So, if you have any problems, flash the stable version in fastboot (unzip the file first): https://forum.xda-developers.com/attachment.php?attachmentid=3995799&d=1483894575
__________________________________________________________________
December 13. Stereo Sound is here. This is based on Dontbelive mode, but it is just clean stereo sound (ear piece and loud speaker), no bass or any other ridiculous "improvements" that do nothing, but distort. And as a result, just a clear stereo sound for games, videos, songs etc...
Just flash the zip in TWRP and reboot. Remember, this is not a rom, but a stereo-sound mode to flash on top of Jaguar...
After installing this, you have to make one call to recalibrate the sound. Otherwise, you may have distortions in the ear piece....
Download: http://forum.xda-developers.com/devdb/project/dl/?id=22080
Credit to Dontbelive...
___________________________________________________________________________________
December 9: New release to include:
1. December Security Patches
2. Signature spoofing feature (cherry-picked from Omnirom)
3. USSD should work now
Download: http://forum.xda-developers.com/devdb/project/dl/?id=21987
__________________________________________________________________________________
November 16. Kernel with DirtyCow fix. Download and flash in recovery. This is not for fastboot.
Download: http://forum.xda-developers.com/devdb/project/dl/?id=21563
___________________________________________________________________
November 10. Rom updated to include November Security Patches+. I have also removed Supersu, as the rom has a built-in root manager. However, if anyone wants to install Supersu, you can easily flash it in recovery
Download: http://forum.xda-developers.com/devdb/project/dl/?id=21427
________________________________________________________________________________
October 10. Kernel-no-overclock.
Unzip and flash in fastboot.
Download: http://forum.xda-developers.com/devdb/project/dl/?id=20848
_________________________________________________________________________________
October 9. Updated Kernel, which includes:
1. Updated higher frequency voltage
2. Improved Prima/Wifi driver
Your CPU variant may require voltage adjustment in Kernel Adiutor for new frequencies. Try to give a load for CPU and if you have freezing or random reboots (which you shouldn't), adjust higher 3 by +10/20. This latest kernel achieves 40000+ antutu score with Ondemandplus with temperature rising to about 58 at the highest load...
Note that some CPU/GPU variants just won't go to 2803 for CPU or 600 for GPU
Instructions: Unzip boot.img and flash in fastboot: fastboot flash boot boot.img or use various apps to install without fastboot
Download: http://forum.xda-developers.com/devdb/project/dl/?id=20838
__________________________________________________________________________________
October 8. Rotating Home Screen: if you want your home screen rotate like on a tablet, flash the attached file in recovery and reboot. So, when you set display to rotate, home screen will be included
__________________________________________________________________________________
October 5. New release:
1. Kernel overclocked to 2803: experimental, I have used it for 10 days without problems
2. October security patches from Google and Code Aurora
3. Over 80 commits from Google Master Gerrit which included changes to bionic, art, frameworks and system
4. Updated Afwall
5. Maybe more
This rom is now about 40% Nougat. One of the side effects: Xposed framework no longer works, but getting rid of it and instead using Privacy Guard is almost as good. Don't forget, Xposed is an exploit, which provides hooks for good and bad things.
Rom Download: http://forum.xda-developers.com/devdb/project/dl/?id=20788
Afwall/Kernel Adiutor Download: http://forum.xda-developers.com/devdb/project/dl/?id=20787
You can flash dirty if on a previous release
_________________________________________________________________________________
September 8. Rom updated to include:
1. September Google security patches
2. Latest Code Aurora patches https://www.codeaurora.org/projects/security-advisories
3. MPdecision is permanently disabled due to interfering with other hotplug and CPU frequencies. Default is MSMdecision, but you can pick several others in Kernel Adiutor
4. CPU overclock and underclock removed: no benefit whatsoever
5. More hardening ported from 3.18, 4.1 and 4.4 kernels: https://android-review.googlesource.com/#/q/hardened,25 You won't find those in any rom custom or stock. This is from 3.18-4.4 kernels and it has nothing to do with Sony AOSP. That's why it works...
6. About 70-80 commits from Android Master Branch. Folks. This is no longer a lollipop rom
7. PXN security feature implemented, which takes advantage of special instructions on ARMv7 to prevent unprivileged execution. See here: https://android-review.googlesource.com/#/c/265892/
8. Further integration of VOLTE
9. Kernel Adiutor: author has decided to go with Mobile Ads/Adview/Adbanner. So these were removed...
10. Camera: improvements to camera wrapper (missing entries), as well as some modifications in /frameworks/av/camera, so, you have a sharper picture. See photo attached, although, XDA reduces pictures... . This was taken with Open Camera. Not the crappy Sony Open Camera, but the fully open source one, with many features including several focusing modes: https://f-droid.org/repository/browse/?fdfilter=open+camera&fdid=net.sourceforge.opencamera. Tell me bootloader locked stock camera is better. It is not...
11. Maybe more...
WARNING: you need to do one thing after flashing the rom: flash the latest stock baseband. BASEBAND ONLY. If you don't, you will only have LTE: no H+/H/2G. This is a one-time procedure and is due to Volte implementation. You can either use FlashTool to flash stock baseband or a Partition Backup App (from Googleplay or elsewhere) to backup and restore your modems. With FlashTool, first flash the rom, then reboot, then flash the latest baseband. With Partition Backup, first, backup your modems, then flash the rom, then restore modems and reboot. You have been warned. I don't want to hear cries: where is my 3G!
Download Rom: http://forum.xda-developers.com/devdb/project/dl/?id=20287
Download Afwall/Kernel Adiutor: http://forum.xda-developers.com/devdb/project/dl/?id=20282
You may flash dirty if on a previous release. Otherwise, clean flash...

1st! Thanks @optimumpro
Sent from my Xperia Z1 using Tapatalk

Downloaded and flashed so far great ROM but 1st issue I noticed I believe data is turned off at ROM start up so setting up Google etc... Is hard without WiFi other than that ultra smooth and really fast great work. @optimumpro I don't suppose you know how to get OK Google everywhere to work do you on all ROMs I have tried its never there
Hope to see FAB in recents in next build if possible though as the remove recents is kinda small and the hover notifications kind of cover over it
Sent from my Xperia Z1 using Tapatalk

Is there still a bug when you turn Bluetooth off and on and it changes the Bluetooth MAC address? (as well as the same WiFi MAC for every device)

danny19901 said:
Downloaded and flashed so far great ROM but 1st issue I noticed I believe data is turned off at ROM start up so setting up Google etc... Is hard without WiFi other than that ultra smooth and really fast great work. @optimumpro I don't suppose you know how to get OK Google everywhere to work do you on all ROMs I have tried its never there
Hope to see FAB in recents in next build if possible though as the remove recents is kinda small and the hover notifications kind of cover over it
Sent from my Xperia Z1 using Tapatalk
Click to expand...
Click to collapse
Data is off by default on first boot only to prevent the phone from connecting before you set it up (firewall etc.). Just turn it on and it will stay on despite reboots. Ok Google? Oh, that's too complicated for me.

matcho13579 said:
Is there still a bug when you turn Bluetooth off and on and it changes the Bluetooth MAC address? (as well as the same WiFi MAC for every device)
Click to expand...
Click to collapse
Not sure about bluetooth, but wifi mac is fine.

The ROM is one of the best i have tested..
There are 2 ways to get superuser: Developer option and supersu

jos_031 said:
The ROM is one of the best i have tested..
Click to expand...
Click to collapse
Totally agree with you.
I was also able to set my WiFi MAC without any problems.
The layers thing is also a very good alternative.
My Z1 is now really hot, I hope it will calm down after some days of use.
@optimumpro: Keep on with this good mix [emoji3]

schickel said:
Totally agree with you.
I was also able to set my WiFi MAC without any problems.
The layers thing is also a very good alternative.
My Z1 is now really hot, I hope it will calm down after some days of use.
@optimumpro: Keep on with this good mix [emoji3]
Click to expand...
Click to collapse
Tweak cpu voltages and governors. You should not have any overheating. Also, don't put any stress on cpu while the phone is charging. Phones are not designed to be used while on a charger: they only get current from the battery, unlike laptops, so, when you are on charger and using the phone, you stress the battery and cpu.

Does everything work with this rom? modem, camera and recharge while the phone is off?

dejawho said:
Does everything work with this rom? modem, camera and recharge while the phone is off?
Click to expand...
Click to collapse
Yes everything seems to be working great modem, camera etc...
Prime Red Dark Layers Theme is really nice I tried Scarlett but has Playstore changelog no text bug
Oh I have xposed installed also for flat style status bar, always correct, force expanded notifications this ROM is by far the best ultra quick
1 big question just noticed how come colour picker tint overlay is still in the dialer ? I thought this was removed in 5.1.1 ? As you can see with the red overlay (This is my very Old Number)
Sent from my Z1 using Tapatalk

I noticed that when I get a call, the phone has to switch back to GSM signal. If I don't have GSM listed in the preferred network types, I could not be reached on the phone - goes straight into a busy tone... Anybody else experienced this?

caki25 said:
I noticed that when I get a call, the phone has to switch back to GSM signal. If I don't have GSM listed in the preferred network types, I could not be reached on the phone - goes straight into a busy tone... Anybody else experienced this?
Click to expand...
Click to collapse
This is a normal behavior. Your phone is a GSM phone. Now, if your carrier provides voice over 3g, then your phone will swith to 3g/H+ from LTE. If you have Volte (voice over LTE), it will stay on LTE. In most of the world there is no Volte yet, so, if your data is LTE, then when you get a call, the phone switches to 3g/H+. If your carrier does not provide calls over 3g (2g only) and you are on WCDMA/LTE, then you won't receive any calls. In that case you should switch to GSM/WCDMA/LTE.
Again, as I have already said, that's the behavior on all roms. Other roms just don't have the options in cell menu that this rom has and changing networks in phone test menue does not stick on reboot. So, you have to know what you are doing...

optimumpro said:
This is a normal behavior. Your phone is a GSM phone. Now, if your carrier provides voice over 3g, then your phone will swith to 3g/H+ from LTE. If you have Volte (voice over LTE), it will stay on LTE. In most of the world there is no Volte yet, so, if your data is LTE, then when you get a call, the phone switches to 3g/H+. If your carrier does not provide calls over 3g (2g only) and you are on WCDMA/LTE, then you won't receive any calls. In that case you should switch to GSM/WCDMA/LTE.
Click to expand...
Click to collapse
I guess I managed to jump too hastily again ... it does make sense of course, and I should have noticed that before. The default setting threw me off I guess, since that was without GSM and when my boss tried to reach me, he just got a busy tone anyhow, thank you so much for the explanation and this wonderful ROM. I just can't move away from Layers anymore

caki25 said:
I guess I managed to jump too hastily again ... it does make sense of course, and I should have noticed that before. The default setting threw me off I guess, since that was without GSM and when my boss tried to reach me, he just got a busy tone anyhow, thank you so much for the explanation and this wonderful ROM. I just can't move away from Layers anymore
Click to expand...
Click to collapse
"Default setting". That's my fault, I shouldn't have assumed that everyone has voice over 3g. I will change this in the next release, but your selection GSM/WCDMA/LTE should stick after reboot.

Thanks for a great ROM! Will this be your main ROM from now on?
Do you recommend to use the kernel defaults or do you have other settings for voltage, governor etc. that you recommend?

This is a really good ROM! Good job @optimumpro! :good:
The feature I really miss from your unofficial DU ROM is the ability to block System Wakelocks. I have serious wakelocks on my phone due to Play services and I don't like Xposed too much (compromises security and drains battery).
Could you add this feature? Thanks!

OK starting to get Random Reboots but I think it's my kernel settings as I had no issues at all except when screen waked up wouldn't let me unlock for a little while so I altered few things fixed that problem now I get random reboots
Sent from my Z1 using Tapatalk

Paranoid Android 6.0.3 - Geehrc (discontinued)

disclaimer :THIS IS UNOFFICIAL PORT
We are launching brand spanking fresh. All new features. New team members. New everything and we have made sure that everything that we are releasing has been polished to our best.
The main features and enhancements that you will probably end up noticing are our custom Quick Settings tile reordering functionality, floating window support, immersive mode, the new on-the-spot interface and CM Theme Engine. There's much more to come, so sit tight!
Feature highlights
Floating mode
Immersive mode
On-the-spot controls
Quick settings re-order
Paranoid OTA (Updates)
Battery styles
Advanced power dialog
Quick pull-down
Theme engine
BUGS:NFC (i hope fix it in few days)
First Boot Time may 10 minute
Download
AOSPA
Changelogs
As we're getting back into the thread game, keeping up with threads and updating them as per changelogs can be too hectic given our schedule. However, very detailed changelogs always go up on our Google+ page, follow us for constant updates!
Instructions & requirements
We highly recommend you to follow these instructions very carefully. Users usually tend to skip a few steps and eventually fall in trouble. Are you with me? Good. Let's get this train going.
Just a few things to keep in mind first -
If you're coming from another ROM / Stock, your system data (not internal storage) will have to be wiped. This includes apps, accounts, messages, call logs etc.
There's been some users complaining about different GAPPS variants messing up installs and causing a ton of issues. Upon investigating it seems OpenGapps Mini/Nano and Banks GAPPS work best.
Understand that Paranoid Android is a custom ROM and it might lead to addiction as it's relatively good. We shouldn't be accused of anything just incase your cat starts drinking wine. Things get a little woozy in the Paranoid World.
Some brain might be involved if things go wrong. Not a lot though, as much to solve what's 1+1.
Okay let's get to the main bit -
Once you have all the required files - boot into recovery and wipe the bananas out of your device. Get into the wipe menu and wipe data, system, cache and dalvik cache (basically everything except Internal Storage).
Once wiped, get into the "Install from zip" menu and select the ROM zip. (pa_bacon_6.x...). Once added to the install queue, TWRP will ask you if you want to add more zips into the queue - Click on "add more zips" and select the GAPPS package.
Swipe the bar on the bottom to flash/install zips. Once both zips are done installing - Reboot into system and set-up your device, do not do anything else.
Once you're done setting up your device - well that's when you're done. One thing though - Make sure you DO NOT INSTALL any other zip in the same queue as the ROM & GAPPS. Meaning, do not flash anything like a kernel or a root package while installing the ROM. We recommend you do that AFTER you're done setting up your device.
Important / Useful links
GAPS
SuperSu
As always, we listen to what you have to say. Help us make PA better by submitting good bug reports possibly with a log attached. Learn how to take logs HERE. Submit bug reports and we'll try to iron out issues as soon as possible - it really helps a lot.
Cheers and #StayParanoid!
Device Source :device-kernel-vendor
Special Thanks
@xboxfanj HE IS REALY PERFECT MAN. THX FOR EVERYTHING
@Kevinjoa
XDA:DevDB Information
Paranoid Android 6.0.3 - Geehrc (discontinued), ROM for the LG Optimus G
Contributors
metrixx02
Source Code: https://github.com/AOSPA
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.4.x
Based On: AOSPA
Version Information
Status: Beta
Beta Release Date: 2016-07-31
Created 2016-07-30
Last Updated 2016-10-28

Screenshots
Screenshots

Reserved

cool, i will become an official tester of this ROM and will shall present bugs, errors and i will sending Logcats. Sorry for my bad english.✌

OK first, when you record a note voice, audio heard saturated. second: when you open often the camera and you spend to other applications can get a time when no longer opens and need to restart the phone. third: the ROM should bring a file manager by default

Ronaldj25 said:
OK first, when you record a note voice, audio heard saturated. second: when you open often the camera and you spend to other applications can get a time when no longer opens and need to restart the phone. third: the ROM should bring a file manager by default
Click to expand...
Click to collapse
i m looking some small fixes i hope looking next time ur issues could u send me log ?

Could you say is that rom have wakelock problem too ?

JacubSKY said:
Could you say is that rom have wakelock problem too ?
Click to expand...
Click to collapse
yea i know have small wakelock issues but amplify solve it

PA 6.0.1 Review
First: Thank you for your work :good:. First I tried the Kevinjoa CM 13, but it has a lot of soft reboots, so I moved here.
1) Installation: Before you beginn, you need TWRP (for e975), which you have to install via ADB (USB + PC) ask Dr. Google about that. Additional to PA you need GAPPs (I choose mini-Version) and it is useful to have chainfires SuperSU.zip (UPDATE-SuperSU-v2.76-20160630161323.zip). All 3 zips can be installed via twrp.
2) Limitations:
I use PA-Version pa_geehrc-6.0.1-20160730 since Aug 10th (2016). I don't have any reboots or something. Everything ist running smothly.
What is working:
- Wifi
- Mobile Data
- Camera
- Phone
- Bluetooth
- GPS
What is NOT working:
- NFC (there seems to be no option to activate it) I love NFC!
- IPv6 **
- Bluetooth sometimes has trouble to connect (Garmin forerunner + Pioneer headset)
- Mobile Data (HSDPA): Whatsapp + Mail is not working, while signal messenger and Chrome are working
** I had to disable IPv6 with "IPv6 Disable Tool", otherwise I encountered problems with mail, etc. I have native IPv6 for internet and the ipv6-stack seems to be the problem: "Socket timeout: failed to connect to server". Update: This is related to my mailprovider (hosteurope.de), which has a workaround.
The version seems to be battery draining, my phone was empty after less than 12 hrs. I will look to the reason.
OK guys, I will continue on this post.
Regards
Garmintroll
Update: I moved to resurrection remix, because oft Bluetooth and mobile data trouble.

garmintroll said:
First: Thank you for your work :good:. First I tried the Kevinjoa CM 13, but it has a lot of soft reboots, so I moved here.
1) Installation: Before you beginn, you need TWRP (for e975), which you have to install via ADB (USB + PC) ask Dr. Google about that. Additional to PA you need GAPPs (I choose mini-Version) and it is useful to have chainfires SuperSU.zip (UPDATE-SuperSU-v2.76-20160630161323.zip). All 3 zips can be installed via twrp.
2) Limitations:
I use PA-Version pa_geehrc-6.0.1-20160730 since Aug 10th (2016). I don't have any reboots or something. Everything ist running smothly.
What is working:
- Wifi
- Mobile Data
- Camera
- Phone
- Bluetooth
- GPS
What is NOT working:
- NFC (there seems to be no option to activate it) I love NFC!
- IPv6 **
** I had to disable IPv6 with "IPv6 Disable Tool", otherwise I encountered problems with mail, etc. I have native IPv6 for internet and the ipv6-stack seems to be the problem: "Socket timeout: failed to connect to server".
The version seems to be battery draining, my phone was empty after less than 12 hrs. I will look to the reason.
OK guys, I will continue on this post.
Regards
Garmintroll
Click to expand...
Click to collapse
Thx ur commends .i know that bugs first i will said that battery issue is wakelock problem if could u flash Xposed u will use Amplify and solve this problem but absolutely I look at this problem first chance .I know u are not alone .NFC is really problem.i did Smal compiles from NFC but can't solve .I don't know what is the problem exactly but I contact my friend I hope fix it soon .ipv6 issue is device source problem i could not anything now.when I solve NFC and wakelock issue I will interest it .but not have any idea this problem.i m interesting AICP usually.but when I have free time I look .
I don't understand what do you mean ur 1. Comment but it is help for u.
I m useng twrp geehrc version 3.0 if u want I can upload it .every time I did full wipe and flash ROM+open gaps aroma +SuperSU (any version)+xposed+viper4ndroid .and not have any problem
But if u want use adb it is not problem can u do my steps but I don't recommend windows adb I use everytime Linux terminal and adb .so u can't usr aroma installer in adb but I hope open gaps stock is solve ur problem.
I did not upload last build s .I m really sorry basketbuild is going maintances .i bought yesterday one host and domain I m planning use h5ai system and upload my works to domain adres .when I will do this share it .
this work my hobby.i m interesting free times .i did not fallow this forum everyday because i m working robotic hands Project but if u want contact me using hangouts i hope help for u quickly than forum

pa 6.0.3 is up

How to enable hardware key backlight? Is there any option in the settings to configure it?

Working great on an old Sprint LG LS970 - thanks!
Question: Sprint/Ting 4G works, Sprint/Tello data does not work. Have attempted various APN editing tricks, but no dice. Any suggestions?

NFC
metrixx02 said:
pa 6.0.3 is up
Click to expand...
Click to collapse
Any news about NFC?

tdurack said:
Working great on an old Sprint LG LS970 - thanks!
Question: Sprint/Ting 4G works, Sprint/Tello data does not work. Have attempted various APN editing tricks, but no dice. Any suggestions?
Click to expand...
Click to collapse
Tello activate your phone as a modem APN works for me:
user ID: [email protected]
APN: mi.pamsn

[ROM][7.x][UNOFFICIAL][Z010D] LineageOS/OMS

Lineage is a free, community built, aftermarket firmware distribution of Android 7.x (Nougat), which is designed to increase performance and reliability over stock Android for your device.
Code:
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
Lineage is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. Lineage does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for Lineage is available in the Lineage Github repo. And if you would like to contribute to Lineage, please visit out Gerrit Code Review.
What's Working
Boots
RIL(CALL,SMS,DATA)
CAMERA
AUDIO
WIFI
BLUETOOTH
VIDEOS
FLASH
SENSROS
GPS
What's Not Working
LED Blinking.
Off charge doesn't work don't let your battery die always put it in charging mode when your battery gets to 5%
Install instructions:
Reboot into recovery (latest TWRP recommended).
Wipe Data, System,Dalvik Cache,Cache and install.
No wipes required if you're updating from a previous version of CM 14.0 (Cache and Dalvik Cache Wipe recommended).
Flash ROM + Gapps.
Reboot.
Read post 2 before reporting bugs.
Changelog.
Download links
Rom - https://sourceforge.net/projects/android-rom-ota/files/LineageOS/Z010D/
OMS(Substratum) - https://sourceforge.net/projects/android-rom-ota/files/LineageOS-OMS/Z010D/
More Roms - https://sourceforge.net/projects/android-rom-ota/files/?source=navbar
Gapps - opengapps.org
Note - This isn't my work main developer of this project is audahadi so leave a like and support.
DONATION IS NOT NECESSARY BUT IT'LL HELP TO PAY SERVER BILLS.
Donate via PayPal - [email protected]
Credits
audahadi
luk1337
luca020400
Source
Device Tree - https://github.com/audahadi/android_device_asus_Z010D.git
Common - https://github.com/audahadi/android_device_asus_qcom_common.git
Vendor - https://github.com/audahadi/android_vendor_asus_Z010D.git
XDA:DevDB Information
LineageOS, ROM for the Asus ZenFone 2
Contributors
ShadowReaper1, audahadi, luk1337, luca020400
Source Code: https://github.com/kernel-hut/android_kernel_asus_msm8916.git
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Marshmallow Bootloader/Modem
Version Information
Status: Testing
Created 2016-12-02
Last Updated 2017-12-09

Reserved
SOME RULES
PLEASE USE GIVEN SECTIONS ABOVE TO SORT EVERYTHING YOU HAVE IN YOUR MIND FOR EXAMPLE IF YOU WANT TO REPORT A BUG USE BUG REPORT SECTION ANY BUG REPORTS GIVEN IN THE COMMENT SECTIONS WILL BE IGNORED SAME GOES FOR EVERYTHING.
First Read The OP And Use The Search Box To Find Your Issue There's A Chance That Somebody Already Might Have Faced The Same Issue Before And Fixed It.
Bug reports:
Explain how to reproduce the bug and attach logcat and dmesg (if you had a random reboot, also attach last_kmsg). If you don't know how to get those, you can use this app. Please, do not report bugs if you use any kind of mods (like xposed) or third party kernel.
Frequently Asked Questions:
Q) How can I unlock Developer options?
A) Go to Settings > About phone, and press five times on Build number.
Q) How can I enable root access?
A) Go to Settings > Developer options > Root access, and enable it for apps, adb or both.
Q) How can I set '3G only' network mode?
A) Open dialer, dial *#*#4636#*#* , open first option "Phone Information", there you can set your preferred network mode.
Q) Why there's a small delay when I wake up the phone?
A) Go to Settings > Display & lights and disable prevent accidental wake-up.
Q) Why is wifi always on in battery stats, even when it was disabled?
A) Go to Settings > Location, press on the 3 dots (top right) > scanning > disable wifi.
Q) How do I update Gapps? (Also useful if you have Gapps related problems).
A) Reboot into recovery. Wipe System, Cache and Dalvik Cache. Install ROM + Gapps. Reboot.

Reserved
Marshmallow Bootloader/Modem
If you are using stock lollipop rom then you must flash any stock marshmallow rom before upgrading to CyanogenMod else it won't boot.

When you say ASUS PixelMaster Camera is not working does it mean that the camera features of the phone will not work, even after using 3rd party app?
Thinking of updating to cyanogenmod and sorry this will be my first time in rooting / flashing to custom roms.

rmatheist said:
When you say ASUS PixelMaster Camera is not working does it mean that the camera features of the phone will not work, even after using 3rd party app?
Thinking of updating to cyanogenmod and sorry this will be my first time in rooting / flashing to custom roms.
Click to expand...
Click to collapse
Fixed in next build.. Just hold on few more
Sent from my Zenfone Max using Tapatalk

audahadi said:
Fixed in next build.. Just hold on few more
Sent from my Zenfone Max using Tapatalk
Click to expand...
Click to collapse
can't wait for the next build. thank you very much for your awesome work!

DT2W
Hi. off screen gestures are working well. though, DT2W just like in the AICP ROM is not working.

looking forward for the camera fix missed the camera 360 already

Realized now that SMS is not working for me . Can't firm conversations at all, error. How to troubleshoot?

ekeluo said:
Realized now that SMS is not working for me . Can't firm conversations at all, error. How to troubleshoot?
Click to expand...
Click to collapse
Try to use other external messaging apps and read reserved post 2.

khiya said:
looking forward for the camera fix missed the camera 360 already
Click to expand...
Click to collapse
Camera Fixed

ShadowReaper1 said:
Try to use other external messaging apps and read reserved post 2.
Click to expand...
Click to collapse
I think this is useful.
The app you linked to doesn't work, fails on start. Used Matlog instead (had to manually enable storage access from settings)

Is it just me that cannot access my sdcard using the default file explorer of cyanogenmod? I could only access my internal storage

rmatheist said:
Is it just me that cannot access my sdcard using the default file explorer of cyanogenmod? I could only access my internal storage
Click to expand...
Click to collapse
yup. Cant access mine too. I use 3rd party file manager.

ShadowReaper1 said:
Camera Fixed
Click to expand...
Click to collapse
do I need to factory data reset/ wipe system to install 14.x? I'm already in CM13

khiya said:
do I need to factory data reset/ wipe system to install 14.x? I'm already in CM13
Click to expand...
Click to collapse
you have to. Wipe dalvik cache, cache, data, system and internal (optional). Our cm14 is not an update of our cm13. Hope it helps.

Is it ok to use custom kernel with this rom??
Can I use this rom with this custom kernel?
http://forum.xda-developers.com/zenfone2/general/kernel-reaper-t3468632/page6#post69918890

Build - 20161202
d2tw not work

ekeluo said:
I think this is useful.
The app you linked to doesn't work, fails on start. Used Matlog instead (had to manually enable storage access from settings)
Click to expand...
Click to collapse
Fixed: has to delete the SMS database, which changed location in Nougat. Working now!

Hi, there's a problem. I've accidently discharged my phone, when I plug usb to charge it, it's constantly turning on, then it realises that charge is 0% and it turns off. Again and again, on-off-on-off... I think it's a kind of firmware bug. How can I fix it? I even cant access TWRP. Only fastboot mode (up+power). The firmware is great, but now I cannot use phone

[kernel] Kernel 3.18 MOTO E5 [plus-LINUX] [NORA] #Correction#

Hello guys, I am creating this topic to solve a little problem that was happening with the Moto E5 nora.
Before I start talking about this problem, I will make it very clear in this thread that I am talking. And until the end of the last line of this post.
-------------------------------------------------- ---------------------------------------
## IMPORTANT DESCRIPTION ##
MAKING IT CLEAR to the site moderators and the developers of the ROMs I will be quoting here in this post.
I do not and will not, and am not taking these ROMs as my own. I am just solving a problem that to this day there has been no update or patch to fix the touchscreen problem, and that when I downloaded the ROMs I didn't get the touch. Just one, but... this patch is not well configured and some commands are missing in the kernel defconfig /I'm talking about touchfix/ and that is why it is giving problems in video recording or problems in the internet network.
This kernel image that I compiled, and this boot configuration (touch fix) of the rom (Lineage os 17.1) was not used on my boot. i used configuration to subscribe to the boot kernel of the ROMs to be able to boot.
repeating this again for all the ROMs mentioned here. I will not and do not want and am not taking these ROMs as my own. I am just solving this problem that was happening to me.
I am just sharing it with people who are having the same problem as me.
-------------------------------------------------- ---------------------------------------
ROM THAT WILL NOT BE INCLUDED HERE
CARBON-CR-8.0-PAX-UNOFFICIAL
PROBLEM THAT I NOTICED
it won't boot with the kernel that comes with it. And neither with this boot that I compiled.
I know what the problem is, but I won't mention it.
I forgot to mention, this boot is being tested by me. Because I edited its configuration when compiling. I am checking if there are any compilation errors or other problems that might happen in the future. Because of the editing I mentioned
The kernel source doesn't have any problems. Not that I know of.
So I will always update the boot.img when possible
I recommend backing up your sensors. because there are some active sensors in the kernel and I don't know if that can harm it or make it dead.
THIS KERNEL WAS TESTED ON MOTO E5 NORA XT1944-4
note: i only tested it on the xt1944-4, it may work... or not. Depends on the variant
VARIANTS XT1944 -1,-2,-3,-5,-4 -6.
####### WARNING #########
DON'T DO THIS IF YOU DON'T KNOW HOW TO GET OUT OF A BROKEN KERNEL
HAVE A BACKUP BOOT IMG OF THE KERNEL THAT IS WORKING PERFECTLY
SO THAT YOU CAN GET OUT OF THE BROKEN KERNEL
AND THEN JUST PUT IT BACK IN AND EVERYTHING WILL BE FINE.
########+++++########
How to upgrade this kernel
Simple, you can upgrade it via TWRP recovery or fastboot.
fastboot command:
#
Code:
flastboot flash boot boot.img
#
What is this kernel for?
Serves to fix the touch screen problem
Improved low memory kill ( I increased the value) (If you have the 1gb of RAM I had, and it won't go out for anything, I recommend switching vendors) ---> no need but because the kernel already does this.
The CPU governor is no longer interactive (is not needed in this kernel.) (Also... not stock. and yes custom.)
And the problem of prolonged recording or as we know ldk (has been fixed)
And others.
with recovery: (TWRP)
Go to install in recovery
Look for the folder where you left the boot, either on the memory card or on the USB stick.
And of course, choose the install image option so that the image you downloaded appears.
And where is this installation image option? Right when you select install on the home screen when you login. Right below it, it will be on the side of select storage. Just change it to install image .
Download the boot kernel img​
aicp nora =1
AospExtended v7.3 =2 (stable)
Arrow-v10.0 =3 (unstable)
crDroid Android 10.0 =4 (unstable)
DerpFest-10-Bare =5
ion-2.9.a-EOL-nora =6
lineageos_17.1 =7 (unstable)
Nusantara_LTS-10 =8 (recommended)
PixelExperience_nora =9 (stable)
PixelExperience_Plus_nora =10 (unstable)
PixelPlusUI_2.0_nora =11 (recommended)
Resurrection Remix-Q-8.7.3-nora =12 (unstable)
Xtended-Tribute-To-MartinCoulon-nora =13
Havoc-OS-v3.12-nora =14 (recommended)
in case no one understands the corresponding ROM name. just follow the corresponding boot number
Just look at the ROM name when you download it. When it is already in .zip and so you find the corresponding boot.
Why so many boot img?
Unfortunately, a single boot.img will not work for all ROMs. After that the system will not accept booting another build of the system.
-------------------------------------------------- ------------------------------------
When downloading, rename it to boot.img
THESE ROMS ARE ALL FROM XDA THAT ARE HERE FROM NORA
Kernel: plus-LINUX
Sources code: https://github.com/E5Series/kernel_motorola_msm8953-3.18
Compile: GCC aarch64 linux android 4.9 lineage 19.1
Compile 32bits: GCC arm linux androideabi 4.9 lineage 19.1
Unfortunately defconfig is not there in the sources, I had to remove it from the ROM in order to compile.
Just so someone knows where I got it from , in case you want to compile
----------------------------------------------------------------+----------------------------
problems, improvements and answers...​
This kernel is running very well on Android 11. well.. depending on which custom android 11 you run with it. it can run bad or good, it will just depend on which GSI build.
From my tests that I did, there are certain custom ROMs of the moto E5 that are not very well optimized or stable. I recommend you to use Havoc OS and Nusantara LTS ROMs. Why them?? From my tests they performed very well with the kernel. Remembering that you don't have to use them obligatorily. And just my guess for you don't have problems like some bugs in the ROM itself. I'm not guaranteeing you won't get bugs with those either.
Now you can use the ROMs you want now without touch problem.
And if there's a bug in the ROM I'm using, can I send it to you? Not really, remembering that I'm not the owner of these ROMs that I've sited here. If that happens, there is nothing I can do about it. I recommend that you get the developer of the ROM you are using to solve it himself.
Already on Android 12 it will not work very well because of the vendor. If you are going to use Android 12 you will have to look for a vendor for a specific compilation for it. I don't recommend you use the build of Android 10 that already comes in the ROM because it doesn't hold Android 12 as it will make it restart all the time.
recommend (default) (required) (alert)​I recommend that you use a swap for this kernel. I mean, don't use the swap itself from the rom. well, use a swap that take and that is more efficient. Let it really work. Because so out of nowhere. Recently I found out that roms swap doesn't work. Or it works, but not as swap or zram. I honestly don't really know what it's for. Leaving a warning for you about what I discovered. This will make the default for upcoming updates.​
The names of the ROM that were quoted here are not mine. I'm not sending them as mine and I don't want to and shouldn't.
Just a reminder.
Update for V2...​
update coming soon.....​

Thanks for your effort. I am giving the rom & other links here to make things easier for others. If you find any wrong link, please message me. And I can help you by testing things in my XT1944-6.
------------------------------------------------------------------------------------------------
Custom rom links for NORA according to the fixed kernel numbers by @Stranger Absolute -
ROM credits to the respective developers
1/AICP link
2/Aosp Extended link
3/Arrow OS link
4/CrDroid link
5/Derpfest link
6/ion OS link
7/Lineage OS link
8/Nusantara link
9/Pixel Experience link
10/Pixel Experience Plus link
11/Pixel Plus Ui link
12/Resurrection Remix link
13/MSM Xtended link
14/Havoc OS link
Twrp - link
7/Lineageos rom is also attached (Because of dead link in the thread).
Rescue & Smart Assistant Tool for emergency situation and rolling back to stock condition link

Stranger Absolute said:
Hi guys, I'm making this topic to solve a little problem that was happening with Moto E5 nora.
Before I start talking about this problem, I will make it very clear in this thread that I am talking about. And until the end of the last line in this post.
-----------------------------------------------------------------------------------------
##IMPORTANT DESCRIPTION##
MAKING IT CLEAR to the moderators of the site and to the developers of the ROMs I will quote here in this post.
I do not and will not, and am not taking these ROMs as my own. I am just solving a problem that to this day there has been no update or patch to fix the sensitive screen problem, and that when you downloaded the ROMs it wouldn't start. Just one, but... this patch is not well configured and some commands are missing in the kernel defconfig /I'M TALKING ABOUT touchfix/ and that is why it is giving problems with video recording or internet network problems.
This kernel Image that I compiled. I did not use the same boot kernel Image from such ROM to get in another. You have to subscribe to the boot kernels of the ROMs to be able to boot, this is for the people who patch the kernels. I recommend that you do this, otherwise you will boot infinitely.
Repeat this again for any ROMs that are mentioned here. I will not and will not and am not taking these ROMs as my own. I am just solving this problem that was happening to me.
I'm just sharing it with people who are having the same problem as me.
-----------------------------------------------------------------------------------------
ROM THAT WILL NOT BE INCLUDED HERE
CARBON-CR-8.0-PAX-UNOFFICIAL
PROBLEM THAT I NOTICED
it won't boot with the kernel that comes with it. And not with this boot that I compiled.
I know what the problem is, but I won't mention it.
I forgot to mention, this boot is under test by me. Because I edited its config when compiling. I am checking to see if there are any compilation errors or other problems that can happen in the future. Because of the edit that I added to it's config.
The kernel source doesn't have any problems. Not that I know of.
So I will always update boot.img when possible
I recommend to backup your sensors. because there are some active sensors in the kernel, and I don't know if it can hurt it or make it dead.
THIS KERNEL WAS TESTED ON THE MOTO E5 NORA XT1944-4
THIS KERNEL WILL ONLY WORK ON THE NORA
note: i only tested on the xt1944-4, it may work... or not. It depends on the variant
VARIANTS XT1944 -2,-3,-4, -6? I DON'T KNOW VERY WELL.
#######NOTICE#########
DON'T DO THIS IF YOU DON'T KNOW HOW TO GET OUT OF A BROKEN KERNEL
HAVE A BACKUP OF THE BOOT IMG OF THE KERNEL THAT IS WORKING PERFECTLY
SO YOU CAN GET OUT OF THE BROKEN KERNEL
AND THEN JUST PUT IT BACK IN AND EVERYTHING WILL BE FINE.
########+++++########
How to flash this kernel
Simple, you can flash it through custom recovery or TWRP or fastboot.
fastboot command:
#
fastboot flash boot boot.img
#
What is this kernel for?
It serves to fix the problem of the touch screen
Low memory kill improved (I increased its value) (If you have the 1gb of RAM that I had and you don't leave for nothing, I recommend switching vendors)
No but interactive (No need for this KERNEL.)(Also.. it is not stock. And yes customized.)
And the prolonged recording problem or as we know ldk(Got corrected)
And others..
No recovery: (TWRP)
Go to install in recovery
Look for the folder where you left the boot, either on the memory card or on the pendrive.
And of course, choose the install image option so that the image you downloaded appears.
And where is this install image? Right when you select install on the home screen when you sign in. Right below it will be on the side select storage. Just change to install image.
Boot img kernel;
aicp_nora =1
AospExtended-v7.3-nora =2
Arrow-v10.0-nora =3
crDroidAndroid-10.0-2 =4
DerpFest-10-Bare =5
ion-2.9.a-EOL-nora =6
lineageos_17.1 =7
Nusantara_LTS-10-nora =8
PixelExperience_nora =9
PixelExperience_Plus_nora =10
PixelPlusUI_2.0_nora =11
RROS-Q-8.7.3-20210920-nora =12
Xtended-Tribute-To-MartinCoulon-nora =13
in case no one understands the name corresponding to the ROM that will be downloaded from NORA's XDA. And that is not crashing with kernel boot.
Just look at the ROM name when you download it. When it already has it in .zip and that way you can find its corresponding boot.
Why so much boot img?
Unfortunately a single boot.img will not work on another ROM. After the system does not accept the boot of another system build. Only his. Removing GSI.
--------------------------------------------------------------------------------------
When downloading, rename it to boot.img
The numbers next to the ROM name correspond to the boot patch.
THESE ROMS ARE ALL FROM XDA THAT ARE HERE FROM NORA
Sources: https://github.com/E5Series/kernel_motorola_msm8953-3.18
Compile: aarch64-linux-android-4.9-lineage-19.1
Compile 32bits: arm-linux-androideabi-4.9-lineage-19.0
Unfortunately defconfig is not there in the sources, I had to remove it from the ROM in order to compile.
Just so someone knows where I got it from , in case you want to compile
The names of the ROM that were quoted here are not mine. I'm not sending them as mine and I don't want to and shouldn't.
Just a reminder.
Click to expand...
Click to collapse
Everything works fine except the inbuilt screen recorder.. Is it possible to fix that through kernel? Thanks again. Really appreciate your work. I can now install any rom without touch,sd card & video issues. I also had abnormal graphics and freezing problem in 3D games. Finally it is fixed

Tawsif999 said:
Everything works fine except the inbuilt screen recorder.. Is it possible to fix that through kernel? Thanks again. Really appreciate your work. I can now install any rom without touch,sd card & video issues. I also had abnormal graphics and freezing problem in 3D games. Finally it is fixed
Click to expand...
Click to collapse
Yes, it's possible. but, only if some line is missing in the config fo kernel. but this boot was to fix that, but I already knew that it couldn't solve it in some variants. oh.. and another thing. it might be because of the rom sometimes. if it's for the rom, there's not much to do. only the development of the ROM itself will be able to correct this error.
I noticed this error in a gsi (generic system). and of course, it's gsi. I already expected this to happen. but I expected it soon when I put the root in it but .. amazingly it only stays for a long period of time, and I thought it would work soon when I put the root. as it happened with the other kernel other than the one in the topic.
but it's like I told you, that in most cases it can be in the rom. already in 3d like games or edition.. they improved I would say. the intention was just to adjust the touch and that's it. only after I modified it. he got faster! with more performance. that wasn't the intention but that's what ended up happening. that's why it got better.

Tawsif999 said:
Everything works fine except the inbuilt screen recorder.. Is it possible to fix that through kernel? Thanks again. Really appreciate your work. I can now install any rom without touch,sd card & video issues. I also had abnormal graphics and freezing problem in 3D games. Finally it is fixed
Click to expand...
Click to collapse
but I'll check to see which one is missing in the kernel config to solve the problem

Tawsif999 said:
Thanks for your effort. I am giving the rom & other links here to make things easier for others. If you find any wrong link, please message me. And I can help you by testing things in my XT1944-6.
------------------------------------------------------------------------------------------------
Custom rom links for NORA according to the fixed kernel numbers by @Stranger Absolute -
ROM credits to the respective developers
1/AICP link
2/Aosp Extended link
3/Arrow OS link
4/CrDroid link
5/Derpfest link
6/ion OS link
7/Lineage OS link
8/Nusantara link
9/Pixel Experience link
10/Pixel Experience Plus link
11/Pixel Plus Ui link
12/Resurrection Remix link
13/MSM Xtended link
TWRP 64 bit is attached. If touch screen doesn't work in TWRP, use mouse via OTG. And if you have decryption problem in TWRP, use SD card & put files there.
7/Lineageos rom is also attached (Because of dead link in the thread).
Rescue & Smart Assistant Tool for emergency situation and rolling back to stock condition link
Click to expand...
Click to collapse
Hello how are you doing? I am a fan of custom roms, I have been trying to install lineage os on my moto e5 variant 3 for months, without success in getting the file, thank you and the creator of the post, what I have noticed is that the loading times in games are a bit slow, any way to fix it? It should be noted that I installed the root and dolby atmos, working correctly, greetings from Argentina

7 de argentina said:
Hello how are you doing? I am a fan of custom roms, I have been trying to install lineage os on my moto e5 variant 3 for months, without success in getting the file, thank you and the creator of the post, what I have noticed is that the loading times in games are a bit slow, any way to fix it? It should be noted that I installed the root and dolby atmos, working correctly, greetings from Argentina
Click to expand...
Click to collapse
I use hktweaks(updated version of kernel auditor) & I increase cpu,gpu speed to the maximum. Also select apply on boot.
Idk if this method really works or not. But I do it everytime. Anyways, if anyone wants an amazing gaming boot logo & boot animation, I can provide it.

Stranger Absolute said:
Hi guys, I'm making this topic to solve a little problem that was happening with Moto E5 nora.
Before I start talking about this problem, I will make it very clear in this thread that I am talking about. And until the end of the last line in this post.
-----------------------------------------------------------------------------------------
##IMPORTANT DESCRIPTION##
MAKING IT CLEAR to the moderators of the site and to the developers of the ROMs I will quote here in this post.
I do not and will not, and am not taking these ROMs as my own. I am just solving a problem that to this day there has been no update or patch to fix the sensitive screen problem, and that when you downloaded the ROMs it wouldn't start. Just one, but... this patch is not well configured and some commands are missing in the kernel defconfig /I'M TALKING ABOUT touchfix/ and that is why it is giving problems with video recording or internet network problems.
This kernel Image that I compiled. I did not use the same boot kernel Image from such ROM to get in another. You have to subscribe to the boot kernels of the ROMs to be able to boot, this is for the people who patch the kernels. I recommend that you do this, otherwise you will boot infinitely.
Repeat this again for any ROMs that are mentioned here. I will not and will not and am not taking these ROMs as my own. I am just solving this problem that was happening to me.
I'm just sharing it with people who are having the same problem as me.
-----------------------------------------------------------------------------------------
ROM THAT WILL NOT BE INCLUDED HERE
CARBON-CR-8.0-PAX-UNOFFICIAL
PROBLEM THAT I NOTICED
it won't boot with the kernel that comes with it. And not with this boot that I compiled.
I know what the problem is, but I won't mention it.
I forgot to mention, this boot is under test by me. Because I edited its config when compiling. I am checking to see if there are any compilation errors or other problems that can happen in the future. Because of the edit that I added to it's config.
The kernel source doesn't have any problems. Not that I know of.
So I will always update boot.img when possible
I recommend to backup your sensors. because there are some active sensors in the kernel, and I don't know if it can hurt it or make it dead.
THIS KERNEL WAS TESTED ON THE MOTO E5 NORA XT1944-4
THIS KERNEL WILL ONLY WORK ON THE NORA
note: i only tested on the xt1944-4, it may work... or not. It depends on the variant
VARIANTS XT1944 -2,-3,-4, -6? I DON'T KNOW VERY WELL.
#######NOTICE#########
DON'T DO THIS IF YOU DON'T KNOW HOW TO GET OUT OF A BROKEN KERNEL
HAVE A BACKUP OF THE BOOT IMG OF THE KERNEL THAT IS WORKING PERFECTLY
SO YOU CAN GET OUT OF THE BROKEN KERNEL
AND THEN JUST PUT IT BACK IN AND EVERYTHING WILL BE FINE.
########+++++########
How to flash this kernel
Simple, you can flash it through custom recovery or TWRP or fastboot.
fastboot command:
#
fastboot flash boot boot.img
#
What is this kernel for?
It serves to fix the problem of the touch screen
Low memory kill improved (I increased its value) (If you have the 1gb of RAM that I had and you don't leave for nothing, I recommend switching vendors)
The CPU governor is not interactive anymore (No need for this KERNEL.)(Also.. it is not stock. And yes customized.)
And the prolonged recording problem or as we know ldk(Got corrected)
And others..
No recovery: (TWRP)
Go to install in recovery
Procure a pasta onde deixou o boot, seja no cartão de memória ou no pendrive.
E claro, escolha a opção de imagem de instalação para que apareça a imagem que você baixou.
E onde está essa imagem de instalação? Logo quando você seleciona instalar na tela inicial ao fazer login. Logo abaixo, estará no lado, selecione armazenamento. Basta alterar para instalar a imagem .
Kernel img de inicialização;
aicp_nora =1
AospExtended-v7.3-nora =2
Arrow-v10.0-nora =3
crDroidAndroid-10.0-2 =4
DerpFest-10-Bare =5
ion-2.9.a-EOL-nora =6
lineageos_17.1 =7
Nusantara_LTS-10-nora =8
PixelExperience_nora =9
PixelExperience_Plus_nora =10
PixelPlusUI_2.0_nora =11
Ressurreição Remix-Q-8.7.3-nora =12
Xtended-Tribute-To-MartinCoulon-nora =13
Havoc-OS-v3.12-nora =14
caso ninguém entenda o nome correspondente à ROM que será baixada do XDA da NORA. E isso não está travando com a inicialização do kernel.
Basta olhar para o nome da ROM quando você baixá-lo. Quando já tiver em .zip e assim você achar o boot correspondente.
Por que tanto boot img?
Infelizmente, um único boot.img não funcionará em outra ROM. Depois que o sistema não aceitar a inicialização de outra compilação do sistema. Só dele. Removendo GSI.
-------------------------------------------------- ------------------------------------
Ao baixar, renomeie-o para boot.img
Os números ao lado do nome da ROM correspondem ao patch de inicialização.
ESSAS ROMS SÃO TODAS DO XDA QUE SÃO AQUI DA NORA
Fontes: https://github.com/E5Series/kernel_motorola_msm8953-3.18
Compilar: aarch64-linux-android-4.9-lineage-19.1
Compilar 32 bits: arm-linux-androideabi-4.9-lineage-19.0
Infelizmente o defconfig não está lá nos fontes, tive que removê-lo da ROM para poder compilar.
Só para alguém saber de onde tirei , caso queira compilar
The names of the ROM that were quoted here are not mine. I'm not sending them as mine and I don't want to and shouldn't.
Just a reminder.
Click to expand...
Click to collapse
I added Havoc OS to the list. At the request of Tawsif999. I'm glad you reminded me because I had forgotten . I took a while because I was testing the ROM. But it's there.

7 de argentina said:
Hello how are you doing? I am a fan of custom roms, I have been trying to install lineage os on my moto e5 variant 3 for months, without success in getting the file, thank you and the creator of the post, what I have noticed is that the loading times in games are a bit slow, any way to fix it? It should be noted that I installed the root and dolby atmos, working correctly, greetings from Argentina
Click to expand...
Click to collapse
I'm fine n.n! Thanks for the appreciation . In fact this problem itself is not from the kernel many times and from the ROM which is not very well optimized. And it depends on which game you are going to run if it takes with internet or offline, or if it's too heavy too.But if it is in the rom or in the vendor. Just remembering that the vendor is part of all this and it also has something that makes the system faster. I was playing brawl stars and I noticed that it improved a little when it is played in the native quality of the mobile, of course, there are still a few glitches when playing. But I noticed that it got better. Now in low quality it runs even smooth . But it's playable!
In short, there's not much you can do about these details as games for the kernel. Since this kernel is a bit old. In fact, this kernel was not supposed to be used in Android 10 ROM, but the 4.9 that runs better. With my knowledge you can go to kernel 4.9. some people will say no... But it does. Unfortunately, there isn't much to do since the config doesn't have a command that exists for that.

Remembering that the updates I sitei on the post will happen.
There will be three updates for the Kernel
V2,V3,V4 These updates are from the config that I edited.. so there will be. Post well will only arrive these updates in 3 months. Why that?? I need time to check if there are any errors or problems with such a config.
I say stay tuned for the next few months.

Bugs found (Kernel or rom issue)
I'm using lineage os and found a bug. After installing some particular(Not all) apps from playstore, they just crash while opening. For example, This app. I can't remember the other apps that crashed earlier. But why does they get installed if they are not compatible.

Tawsif999 said:
Bugs found (Kernel or rom issue)
I'm using lineage os and found a bug. After installing some particular(Not all) apps from playstore, they just crash while opening. For example, This app. I can't remember the other apps that crashed earlier. But why does they get installed if they are not compatible.
Click to expand...
Click to collapse
actually this bug is not because of the kernel, it's from the rom. The kernel doesn't interfere with these things. It's rare that this happens with the kernel. unfortunately i can't resolve this bug. Only the ROM developer himself can verify the problem that is causing it. I don't recommend you use Lineage os. There are some bugs in this rom that are not very user friendly.

Stranger Absolute said:
Hi guys, I'm making this topic to solve a little problem that was happening with Moto E5 nora.
Before I start talking about this problem, I will make it very clear in this thread that I am talking about. And until the end of the last line in this post.
-----------------------------------------------------------------------------------------
##IMPORTANT DESCRIPTION##
MAKING IT CLEAR to the moderators of the site and to the developers of the ROMs I will quote here in this post.
I do not and will not, and am not taking these ROMs as my own. I am just solving a problem that to this day there has been no update or patch to fix the sensitive screen problem, and that when you downloaded the ROMs it wouldn't start. Just one, but... this patch is not well configured and some commands are missing in the kernel defconfig /I'M TALKING ABOUT touchfix/ and that is why it is giving problems with video recording or internet network problems.
This kernel Image that I compiled, this boot config (touch fix) from the rom (Lineage os 17.1) was not used for my boot. You have to subscribe to the boot kernels of the ROMs to be able to boot, this is for the people who patch the kernels. I recommend that you do this, otherwise you will boot infinitely.
Repeat this again for any ROMs that are mentioned here. I will not and will not and am not taking these ROMs as my own. I am just solving this problem that was happening to me.
I'm just sharing it with people who are having the same problem as me.
-----------------------------------------------------------------------------------------
ROM THAT WILL NOT BE INCLUDED HERE
CARBON-CR-8.0-PAX-UNOFFICIAL
PROBLEM THAT I NOTICED
it won't boot with the kernel that comes with it. And not with this boot that I compiled.
I know what the problem is, but I won't mention it.
I forgot to mention, this boot is under test by me. Because I edited its config when compiling. I am checking to see if there are any compilation errors or other problems that can happen in the future. Because of the edit that I added to it's config.
The kernel source doesn't have any problems. Not that I know of.
So I will always update boot.img when possible
I recommend to backup your sensors. because there are some active sensors in the kernel, and I don't know if it can hurt it or make it dead.
THIS KERNEL WAS TESTED ON THE MOTO E5 NORA XT1944-4
note: i only tested on the xt1944-4, it may work... or not. It depends on the variant
VARIANTS XT1944 -1,-2,-3,-5,-4 -6.
#######NOTICE#########​
DON'T DO THIS IF YOU DON'T KNOW HOW TO GET OUT OF A BROKEN KERNEL
HAVE A BACKUP OF THE BOOT IMG OF THE KERNEL THAT IS WORKING PERFECTLY
SO YOU CAN GET OUT OF THE BROKEN KERNEL
AND THEN JUST PUT IT BACK IN AND EVERYTHING WILL BE FINE.
########+++++########​
How to flash this kernel
Simple, you can flash it through custom recovery or TWRP or fastboot.
fastboot command:
#
fastboot flash boot boot.img
#
What is this kernel for?
It serves to fix the problem of the touch screen
Low memory kill improved (I increased its value) (If you have the 1gb of RAM that I had and you don't leave for nothing, I recommend switching vendors)
The CPU governor is not interactive anymore (No need for this KERNEL.)(Also.. it is not stock. And yes customized.)
And the prolonged recording problem or as we know ldk(Got corrected)
Touchscreen issue has been resolved.
And others..
No recovery: (TWRP)
Go to install in recovery
Look for the folder where you left the boot, either on the memory card or on the pendrive.
And of course, choose the install image option so that the image you downloaded appears.​
​
And where is this install image? Right when you select install on the home screen when you sign in. Right below it will be on the side select storage. Just change to install image.​
Boot img kernel download
aicp_nora =1
AospExtended-v7.3-nora =2
Arrow-v10.0-nora =3
crDroidAndroid-10.0-2 =4
DerpFest-10-Bare =5
ion-2.9.a-EOL-nora =6
lineageos_17.1 =7
Nusantara_LTS-10-nora =8
PixelExperience_nora =9
PixelExperience_Plus_nora =10
PixelPlusUI_2.0_nora =11
Resurrection Remix-Q-8.7.3-nora =12
Xtended-Tribute-To-MartinCoulon-nora =13
Havoc-OS-v3.12-nora =14
in case no one understands the name corresponding to the ROM that will be downloaded from NORA's XDA. And that is not crashing with kernel boot.
Just look at the ROM name when you download it. When it already has it in .zip and that way you can find its corresponding boot.
Why so much boot img?
Unfortunately a single boot.img will not work on another ROM. After the system does not accept the boot of another system build. Only his. Removing GSI.
--------------------------------------------------------------------------------------
When downloading, rename it to boot.img
The numbers next to the ROM name correspond to the boot patch.
THESE ROMS ARE ALL FROM XDA THAT ARE HERE FROM NORA
Kernel: plus-LINUX
Sources code: https://github.com/E5Series/kernel_motorola_msm8953-3.18
Compile: GCC aarch64 linux android 4.9 lineage 19.1
Compile 32bits: GCC arm linux androideabi 4.9 lineage 19.1
Unfortunately defconfig is not there in the sources, I had to remove it from the ROM in order to compile.
Just so someone knows where I got it from , in case you want to compile
----------------------------------------------------------------+----------------------------
problems, improvements and answers...​
This kernel is running very well on Android 11. well.. depending on which custom android 11 you run with it. it can run bad or good, it will just depend on which GSI build.
From my tests that I did, there are certain custom ROMs of the moto E5 that are not very well optimized or stable. I recommend you to use Havoc OS and Nusantara LTS ROMs. Why them?? From my tests they performed very well with the kernel. Remembering that you don't have to use them obligatorily. And just my guess for you don't have problems like some bugs in the ROM itself. I'm not guaranteeing you won't get bugs with those either.
Now you can use the ROMs you want now without touch problem.
And if there's a bug in the ROM I'm using, can I send it to you? Not really, remembering that I'm not the owner of these ROMs that I've sited here. If that happens, there's nothing you can do about it. I recommend that you get the developer of the ROM you are using to solve it himself.
Already on Android 12 it will not work very well because of the vendor. If you are going to use Android 12 you will have to look for a vendor for a specific compilation for it. I don't recommend you use the build of Android 10 that already comes in the ROM because it doesn't hold Android 12 as it will make it restart all the time.
The names of the ROM that were quoted here are not mine. I'm not sending them as mine and I don't want to and shouldn't.
Just a reminder.
Update for V2...​
update soon....​
Click to expand...
Click to collapse
I'm running DerpFest-10-Bare-Beta-nora-20211212, and this kernel just solved the issue when dowloading stuff to my sdcard, the phone would reboot every time i tried to download something, so thank you very much!
Is it possible to root img file via Magisk?

Is it possible to root the img file via Magisk?

Issue-
If you use any custom rom in moto e5, it will make the games think that you're using a device better than moto e5. That's why the texture will be better. For this, the game will run laggy. But there is a fix. Use gl tools and configure your game. Use a template of 1gb ram device.
Next, the graphics glitch persists. In free fire, the shrink zone looks odd. When I'm close to the circle, I can't even understand if I'm inside safezone or not. But the op's kernel (plus-linux) works better than twerk-x, which is given inside every rom for nora. In twerk-x, the game was crashing for graphics glitch. Anyways, plus-linux can handle it better.
Let's see if it gets fixed in next kernel updates. Most probably, it's problem of custom roms.
As the op mentioned, I tried havoc os & surprisingly it is more stable than pixel experience.

masoko said:
Is it possible to root the img file via Magisk?
Click to expand...
Click to collapse
Hi, sorry... just saw your answer now. It is possible yes, I recommend that you do after the ROM flash. I say this because there are some ROMs that give infinite boot. But, don't worry, they are only two. It only happens when you flash the ROM together with the magisk zip. It rarely happens, but ... It happens.

Thanks for your reply, what are the instructions for installing your kernel on swap?

masoko said:
Thanks for your reply, what are the instructions for installing your kernel on swap?
Click to expand...
Click to collapse
I hadn't stopped to think about it , you can use a module for magisk that will solve the swap problem.
You can use the one I will leave here.
This module was downloaded from pling. From the pling site. And I know there are several of them. But they don't replace the swap and also this swap that comes in the roms you can't delete it either by terminal or file. I don't recommend anyone to use this swap that comes in the ROMs. Technically I don't know what they are good for.
This module provides 2 GB of swap which is already enough for the moto e5.

masoko said:
I'm running DerpFest-10-Bare-Beta-nora-20211212, and this kernel just solved the issue when dowloading stuff to my sdcard, the phone would reboot every time i tried to download something, so thank you very much!
Click to expand...
Click to collapse
Was microsd using exfat or fat32?