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

[Stranger Absolute]

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:



#

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.....​

 

[Tawsif999]

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

 

[Tawsif999]

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.

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

 

[Stranger Absolute]

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

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.

 

[Stranger Absolute]

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

but I'll check to see which one is missing in the kernel config to solve the problem

 

[7 de argentina]

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

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

 

[Tawsif999]

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

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]

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.

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.

 

[Stranger Absolute]

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

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.

 

[Stranger Absolute]

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.

 

[Tawsif999]

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.

 

[Stranger Absolute]

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.

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.

 

[masoko]

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....​

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?

 

[masoko]

Is it possible to root the img file via Magisk?

 

[Tawsif999]

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.

 

[Stranger Absolute]

Is it possible to root the img file via Magisk?

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.

 

[masoko]

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

 

[Stranger Absolute]

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

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.

 

[kenshinta]

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!

Was microsd using exfat or fat32?