Related
LineageOS is a free, community built, aftermarket firmware distribution of Android 7.1.1 (Nougat), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std_disclaimer.h>
/*
* 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.
*
*/
LineageOS 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. You will need to provide your own Google Applications package (gapps). LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit our Gerrit Code Review. Your changelog is whatever was merged into gerrit.
Important information:
This thread is for LineageOS builds for jfltexx (GT-I9505). The following will not be supported here:
Custom kernels
Mods
Xposed
We don't support Xposed and any logcat which includes a Xposed module will be ignored. You're kindly invited to not report bugs if you:
Flashed a custom kernel
Installed or did mods from untrusted sources
Installed SuperSU
Modified system files
Installation
First time flashing LineageOS 14.1 on your device, or coming from another ROM?
Download the zip(s)
Install a compatible recovery
Perform a nandroid backup of your current ROM (Optional)
Wipe data/factory reset
Flash CyanogenMod
Optional: Install the Google Apps addon package
Reboot
Other issues?
Before posting in this thread, make sure of a few things:
You used the search function of the forums.
If you are the only one having a problem. Boot into recovery, wipe data/factory reset, reflash the rom/gapps and nothing else. Boot up and see if the problem persists.
Make sure your post is relevant to this thread.
Logs! You can use this: https://play.google.com/store/apps/details?id=com.tortel.syslog
Downloads
https://www.androidfilehost.com/?w=files&flid=141380
Source:
https://github.com/LineageOS
https://github.com/dkati/lineageOS-jf-nightly
Google Apps:
OpenGApps (choose ARM, 7.1, nano)
The LineageOS team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!
XDA:DevDB Information
Unofficial LineageOS 14.1 for the Galaxy S4 I9505, ROM for the Samsung Galaxy S 4
ROM OS Version: 7.1.x Marshmallow
ROM Kernel: Linux 3.4.x
XDA:DevDB Information
[ROM][7.1.1][UNOFFICIAL] LineageOS builds [Jan 07][jfltexx], ROM for the Samsung Galaxy S4
Contributors
side
ROM OS Version: 7.x Nougat
Version Information
Status: Testing
Created 2017-01-07
Last Updated 2017-01-20
reserved
reserved again
Amazing work as always,already downloading for further testing , thanks @side!
Enviado desde mi GT-I9505 mediante Tapatalk
ROM OS Version: 6.0.x Marshmallow / is not 7.1.1 ?
Bodala said:
ROM OS Version: 6.0.x Marshmallow / is not 7.1.1 ?
Click to expand...
Click to collapse
Just a typo
side said:
Just a typo
Click to expand...
Click to collapse
Side mate, you need to get out more !
Seriously, congratulations on another rom... Soon all S4 threads belong to you!
I wanted to buy a newer S device because of not many rom choices compared to my previous Xperia but you side are a star here. Good luck with development and best wishes for 2017. If you want a tester just tell me what to do.
Camera: works fine, both image and video,
Wifi and HotSpot: works fine, Bluetooth unable to test, I have no other devices,
Antutu Score: 41157
So far switching camera modes sometimes crashes the app.
prohibeat said:
I wanted to buy a newer S device because of not many rom choices compared to my previous Xperia but you side are a star here. Good luck with development and best wishes for 2017. If you want a tester just tell me what to do.
Click to expand...
Click to collapse
If you want many ROMs then do not buy another Samsung. Their closed sources and locked bootloaders make ROM development kinda hard.
Thank you @side
Is this not a optimized build ? Or we just moved here from optimized cm14.1 ?
Sent from my Pixel using Tapatalk
Manula Sameera' said:
Is this not a optimized build ? Or we just moved here from optimized cm14.1 ?
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
It's not optimized. It's Unofficial nightly. No edits at all. Optimized will come soon
Buff99 said:
Side mate, you need to get out more !
Seriously, congratulations on another rom... Soon all S4 threads belong to you!
Click to expand...
Click to collapse
I prepare the manifests when I am home and building through TeamViewer mate. No worries about my social life
side said:
I prepare the manifests when I am home and building through TeamViewer mate. No worries about my social life
Click to expand...
Click to collapse
Do you need any assistance with testing? I can perform tasks/tests and send logcats if it helps you to troubleshoot anything.
prohibeat said:
Do you need any assistance with testing? I can perform tasks/tests and send logcats if it helps you to troubleshoot anything.
Click to expand...
Click to collapse
You can always post logs here and report bugs
@side LineageOS Short YouTube Overview
ok @side, first of all I'm occasionally getting 'silent calls' that persist until a reboot. Do you need a log for that or you already know how to solve it?
Nice one, @side will deffo give this a run for a couple of days
"Flash CyanogenMod", that copy/paste in the instruction. Anyway, thanks a lot for the job you do for our beloved S4.
Edit : "The CyanogenMod team" too
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 6.0.1 Marshmallow, which is designed to increase performance and reliability over stock Android for your device.
Read This * Your warranty is now void.
* I am 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 me for messing up your device, I will laugh at you.
Important Notice!Root is now disabled by default on CyanogenMod 13. To enable it go to Settings>Developer Options>Root access and set to Apps only or Apps and ADB.
Features
-Gesture wakes up
-Best Screen-On-Time of 4:15 hrs to 4:30 hrs among current roms with fp.
-Bluetooth (send and receive files, Bluetooth headset normal)
-Camera (camera, video, HDR normal)
-Call (then call the normal)
-SMS (send and receive normal)
-Infrared is normal
-Support fast charge
-Integrated flat theme
-No YouTube video freezes
-Smooth and fast.
-Working infrared ( pre installed letv remote app) and fingerprint.
-Decent battery backup.
-All the customisations.
-No 'Idle Phone' battery drain.
-Working Fingerprint sensor.(For now data needs to be restored from stock EUI).
DownloadsROM: https://drive.google.com/file/d/0B02Z9EXjik9aMDlrS21EVU9GalU/view?usp=drivesdk
GApps: http://opengapps.org/
TWRP(3.0.3): https://twrp.me/devices/letvle1s.html
Installation Instructions
1. TWRP 3.0.3 should be installed.
2. Fingerprint data backup form stock rom should be made via TWRP ( refer video tutorial attached in the end of the post.)
3. Reboot to recovery ( TWRP)
4. Wipe>Advanced wipe and select Data, Cache, System and Dalvik Cache and swipe to wipe.
5. Flash cm-13.0-20161203-UNOFFICIAL-X500.zip
6. Flash GApps.( ARM64, android 6, any package)
7. Restore the fingerprint data.
8. Wipe Caches.
9. Reboot.
Tip: Don't forget to calibrate your battery using Battery Calibration ROOT app from play store every time you flash a new ROM.
XDA : DevDB Information
CyanogenMod 13 ROM for Le 1S.
ROM OS Version: 6.0.x Marshmallow
Source: http://bbs.ydss.cn/forum.php?mod=viewthread&tid=719830&extra=page=4&filter=author&orderby=dateline
Contributors:
Bule.
Credits:
Bule(For making ROM), Shavi suri(For installation tutorial).
Is this built from source specifically for the Le 1S or is it just another modified pre-built ROM originally built for another device?
Also, a ROM built on the 3rd of December is pretty old, I'll have to look on some other sites to see if this is something that was announced elsewhere ages ago and not worth getting enthused about.
i request you to provide the sources.
Nameless One said:
Is this built from source specifically for the Le 1S or is it just another modified pre-built ROM originally built for another device?
Also, a ROM built on the 3rd of December is pretty old, I'll have to look on some other sites to see if this is something that was announced elsewhere ages ago and not worth getting enthused about.
Click to expand...
Click to collapse
Cm has already shut shop
Sent from my ONE E1003 using Tapatalk
reversegear said:
i request you to provide the sources.
Click to expand...
Click to collapse
Kernel : https://github.com/lbule/android_kernel_Letv_X500
Device tree : https://github.com/lbule/android_device_Letv_X500
Credit : Bule
---------- Post added at 09:04 AM ---------- Previous post was at 09:02 AM ----------
Nameless One said:
Is this built from source specifically for the Le 1S or is it just another modified pre-built ROM originally built for another device?.
Click to expand...
Click to collapse
Source compiled
Unable to flash this in my le 1s x507 5.8.19s . I tried twrp 2.8.7 and 3.0.3 both everytime show error "system have non-content after ota update".
Plzzz help
bring lineage os
love4chat said:
bring lineage os
Click to expand...
Click to collapse
Here,
https://forum.xda-developers.com/leeco-le-1s/development/rom-lineageos-13-x500-7-9-t3567752
reversegear said:
Here,
https://forum.xda-developers.com/leeco-le-1s/development/rom-lineageos-13-x500-7-9-t3567752
Click to expand...
Click to collapse
i meant the lastest one would be nicer ie 14.1
love4chat said:
i meant the lastest one would be nicer ie 14.1
Click to expand...
Click to collapse
Have patience buddy.. there are only few devs are working on our device..
already 14.1 is under development.
reversegear said:
Have patience buddy.. there are only few devs are working on our device..
already 14.1 is under development.
Click to expand...
Click to collapse
thats great news
reversegear said:
Here,
https://forum.xda-developers.com/leeco-le-1s/development/rom-lineageos-13-x500-7-9-t3567752
Click to expand...
Click to collapse
Hmm, with the ROM in the quoted link, under Bluetooth the default device name showed as "Redmi Note 2" which suggests to me that this isn't built from source for this device but is a modified ROM built for the Redmi Note 2 which is rather disappointing. I would like to think that the LineageOS 14.1 ROM is truly being built from source for the 1S but I don't believe it for a moment.
At least this ROM image isn't full of Chinese garbage.
Nameless One said:
Hmm, with the ROM in the quoted link, under Bluetooth the default device name showed as "Redmi Note 2" which suggests to me that this isn't built from source for this device but is a modified ROM built for the Redmi Note 2 which is rather disappointing. I would like to think that the LineageOS 14.1 ROM is truly being built from source for the 1S but I don't believe it for a moment.
At least this ROM image isn't full of Chinese garbage.
Click to expand...
Click to collapse
Yes. the op in that link has mentioned PORT in the title..
if you are interested testing LOS 14.1(Built from source) let me know via PM.
reversegear said:
Yes. the op in that link has mentioned PORT in the title..
if you are interested testing LOS 14.1(Built from source) let me know via PM.
Click to expand...
Click to collapse
I didn't see the title when following the link but now that you mentioned it the PORT in the title is clear.
If any one have le 1s related problem and solution or any one want to try new rom or kernal asap then all of u are welcome in our group on telegram so plz join with us
Requriemt
1. Download telegram from play store
2. Just click below link
https://telegram.me/LeSuperGroup
Thanks all of u
LineageOS 15.1 (Beta v1.01)
for Moto E5 Play (james)
Boost Mobile/Virgin Mobile/Sprint Variants
LineageOS 15.1 is a free, community-built, aftermarket firmware distribution of Android 8.1.0 Oreo, which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project (AOSP) with extra contributions from a myriad of developers and enthusiasts within the Android community. LineageOS can be used without need of having any Google application installed. LineageOS does still include various hardware-specific code, which is slowly being open sourced.
LineageOS Source Code: https://github.com/LineageOS
LineageOS Changelog: https://www.cmxlog.com/15.1
LineageOS Gerrit Code Review: https://review.lineageos.org/#/q/status:open
Kernel Source Code MSM8920: https://github.com/MotorolaMobilityLLC/kernel-msm/releases/tag/MMI-OCP27.91-23
This is a LineageOS 15.1 build based on Project Treble. More specifically, it is based on XDA Recognized Developer @phhusson's Phh-Treble and his ARM32 Vanilla GSI. Because the Moto E5 Play is officially supported by Project Treble, I have taken the vanilla GSI and made it bootable for our device. Along with a modified kernel from the stock Android 8.0.0 OS, I've compiled a TWRP flashable Lineage 15.1 custom ROM for the james. This vanilla ROM is very much bare-bones -- no GApps, no SU addon, etc. -- and is likely chocked full of bugs at this time. So, without further ado.....
DISCLAIMER: Your warranty is hereby null, void, and held for naught. By proceeding further, you are assuming full responsibility for any good or bad consequences which may result from flashing this ROM. While I have installed and tested this ROM on my own device, and can confirm boot up and basic functionality, I cannot yet elaborate on bugs and other types of instabilities. This is truly a work in progress at this point. So, to sum it up, FLASH THIS AT YOUR OWN RISK. I am hereby absolved of any liability from bricked, damaged, or otherwise inoperable devices.
SPECIFICATIONS:
Android Version: 8.1.0
Build: OPM2.171026.006
Kernel Version: 3.18.71
Security Patch Level: June 5, 2018
Build Date: June 26, 2018
LineageOS API: llama (9)
STATUS: Beta
Created: Thu, July 29, 2018 15:00:00
REQUIREMENTS/INSTRUCTIONS:
1. First and foremost, an unlocked bootloader is necessary;
2. TWRP custom recovery installed and force encryption disabled. Please visit @CodyF86's thread on how to do this, and please be sure and hit the THANKS button if you used his work;
3. Download the ROM zip from the below download link and store it on external device storage;
4. Boot your device into TWRP recovery;
5. Select Wipe, and swipe to perform a factory data reset. Now, select Wipe and then Format Data, and follow all prompts to commence formatting;
6. Reboot Recovery (often necessary to ensure proper mounting of /userdata after formatting the partition;
7. Select Install, navigate to the location of the ROM zip, and swipe to commence installation;
8. Reboot System (1st boot up can take around 3 minutes or more);
NOTE: This vanilla ROM does not include GApps so, if you want GApps, visit https://opengapps.org/ and download a package of your preference. If installing GApps, simply flash the package during the above installation process after Step 7, then Reboot System.
BUGS:
Working:
RIL
Bluetooth
WiFi
Not Working:
Camera
Please properly report bugs, with submission of a bug report if you know how. If not, please give a clear and concise explanation of the bug. NOTE: Please DO NOT report bugs if you are running modifications such as Magisk Modules, Xposed Framework, etc. This makes it nearly impossible to pinpoint, troubleshoot and fix bugs and instabilities. Also, please know that I am not a ROM maintainer for Project Treble or LineageOS. So, while I will do my best to resolve bugs and provide some bug fixes and updates, please do not ask for ETAs. I work 55+ hours a week at Motorola Mobility, LLC., so I don't always get a lot of free time.
THANKS & MENTIONS:
Thanks to @SuperR. for his awesome Windows Kitchen;
Thanks to @CodyF86 for breaking ground and building TWRP for the james;
Thanks and credits to @phhusson for his Phh-Treble Vanilla GSIs;
Thanks to the entire LineageOS team;
DOWNLOAD LINK:
LineageOS 15.1 (Beta v1.01): https://drive.google.com/open?id=1TPl879IQvVH2ajYG6ZJ2kobp_rMgRfE5
Guys please provide feedback and feel free to contribute on this. I have more custom ROMs on the way such as ResurrectionRemix, PixelExperience, and AOSP-Extended. But I don't have a lot of free time to maintain ROMs, so I'm going to need help ironing out bugs and compiling patches.
Hum that's weird, wifi works for me on Moto E5
For camera, I have the fix pending for two months, I just haven't committed it yet -_-'
Thanks so much for commenting. After wiping the Dalvik/ART & /cache, WiFi is now working. I'll keep my eyes open for your pending camera commit.
Update: WiFi,, Bluetooth and RIL appear to be functional. Over the next few days I'm in hopes that user feedback will provide me with more insight as to bugs & instabilities.
this boots fine on e5 plus after flashing e5plus-noverity kernel and magisk as for ril data and all i cant tell you until i fix my sprint e5plus modem files messed them up by accidently flashing a differnt e5plus rom will report back more when i manage to completly fix my phone
allenjthomsen said:
this boots fine on e5 plus after flashing e5plus-noverity kernel and magisk as for ril data and all i cant tell you until i fix my sprint e5plus modem files messed them up by accidently flashing a differnt e5plus rom will report back more when i manage to completly fix my phone
Click to expand...
Click to collapse
Ok thanks @allenjthomsen. Yeah there seems to be many of us in the same boat -- patiently waiting for Motorola Mobility to either release or "leak" some factory images for the Moto E5 series devices. I'm actually drafting a baseband radio thread now for the James, compiling a TWRP flashable installer to restore radio/modem firmware and reset the network config to factory default. I know of a couple of devs over at Android Central that may can dump baseband partitions for your device. Also, please provide me with your Baseband Version. Thanks...
I have a bootable Android 9.0-DP3 ROM for the James. Lots of stuff broken, so I'm going to get it more stable, implement a working GApps package, etc. before posting it. Going to try and get our camera app working on this ROM also, maybe see if I can talk @phhusson into sharing his fix. Hint hint
i can dump files if needed and btw i tried your lineage os and i couldnt get data but got signal and camera crash other than that it ran great on my replacement E5 Plus Sprint model
allenjthomsen said:
i can dump files if needed and btw i tried your lineage os and i couldnt get data but got signal and camera crash other than that it ran great on my replacement E5 Plus Sprint model
Click to expand...
Click to collapse
Thank you for your feedback. I have a camera fix underway. As far as data connectivity I've had some issues myself, so I'm dissecting that issue too.
I have the same problem with the camera with GSI roms on a motorola e5 plus (rhannah). I get the impression that Motorola has something not standard in its handling of cameras of this family of devices
What DPI is this device? 320dpi right?
nachoxda79 said:
What DPI is this device? 320dpi right?
Click to expand...
Click to collapse
Yes. 320dpi (xhdpi); 1280 x 720 resolution
MotoJunkie01 said:
Yes. 320dpi (xhdpi); 1280 x 720 resolution
Click to expand...
Click to collapse
Thanks dude.
@MotoJunkie01 Hey, if you get a second pm me. I got your rom to boot on the g6 play by switching kernels, so I decided to compile a treble rom myself and I can compile it successfully, but the rom won't boot...clang seg faults like 30 times trying to compile it, so I think that is the actual issue, but wanted to bounce a few things off of you. No worries, thanks.
CodyF86 said:
@MotoJunkie01 Hey, if you get a second pm me. I got your rom to boot on the g6 play by switching kernels, so I decided to compile a treble rom myself and I can compile it successfully, but the rom won't boot...clang seg faults like 30 times trying to compile it, so I think that is the actual issue, but wanted to bounce a few things off of you. No worries, thanks.
Click to expand...
Click to collapse
I tried to PM you but sending failed. I'll get on my PC and login through the browser. I think my messaging settings are preventing the PM from sending.
Thanks for your work. Would this Lineage ROM work for the T-Mobile variant of the E5 Play (XT1921-3)?
konradsa said:
Thanks for your work. Would this Lineage ROM work for the T-Mobile variant of the E5 Play (XT1921-3)?
Click to expand...
Click to collapse
Not likely. There's no real danger in trying it because my installer does not flash sensitive partitions, but only /system & /boot. While I don't perceive any chance of bricking your device, it would be at your own risk. You would be better off flashing your device with a Treble GSI. While this ROM is technically based on a Project Treble GSI, I done some mods to the stock boot image and compiled the installer from porting. Hence, the ROM should not be characterized as a GSI itself. By the way I do have firmware for the xt1921-3, which I will be posting in my Moto E5 firmware thread over the next couple days.
my model is moto e5 play (XT1920-15)
my model is moto e5 play (XT1920-15) , will it work also my codename is not james. also how we can backup stock rom. before trying dont we need stock rom for this phone , so we can be secure.
rehannasim said:
my model is moto e5 play (XT1920-15) , will it work also my codename is not james. also how we can backup stock rom. before trying dont we need stock rom for this phone , so we can be secure.
Click to expand...
Click to collapse
I can only confirm compatibility with the xt1921-5. But before trying it, as you have correctly noted, it is crucial to have a suitable backup of your /system and /boot partition, just in case anything goes wrong. Most times, backups are made using a custom recovery such as TWRP. However I'm not familiar with your variant and therefore do not know of a working TWRP for your device. I will check my firmware archive and see if I can find a package for your model.
Update; unfortunately, at this time I cannot find firmware or custom recovery for your variant. I would urge you to post under the Q&A thread and ask if any members have your model.
Please note: I no longer maintain this ROM as my phone screen has cracked and I've moved on to a different device. Bgncm will probably continue to maintain it for mi8 as its similar to his other devices. Thanks for those that supported in the past and perhaps we will meet again in the future on a different device.
LineageOS is a free, community built, aftermarket firmware distribution of Android 12, which is designed to increase performance and reliability over stock Android for your device.
LineageOS 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. You will need to provide your own Google Applications package (gapps). LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
Base source code is available in the LineageOS Github repo. And if you would like to contribute to the project, please visit our Gerrit Code Review.
GPL compliance:
Device tree source code: https://github.com/LineageOS/android_device_xiaomi_dipper
Kernel source code: https://github.com/LineageOS/android_kernel_xiaomi_sdm845
Compatibility:
Compatible with Xiaomi Mi 8
Builds are based off the Xiaomi's Android 10 firmware.
Recommended firmware is latest MIUI stable firmware.
LineageOS Downloads
download.lineageos.org
Notice:
No custom kernels are supported in this thread. Only stock kernel and official builds will be supported. No bug reports if that's not the case.
Installation:
Reboot to recovery
Format /system, /data and /cache
Install MIUI firmware
Install LineageOS zip package
Install a Google Apps package of your choice.
Important notes:
* Required * firmware version must be based on MIUI *-based builds.
Formatting data (all user data is wiped, including internal storage) is a must if MIUI was previously installed and device was encrypted.
All LineageOS team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!
@infrag
Thanks for keeping up the support for this device!
Excellent work!
Even though I would have preferred a version without Gapps (either Vanilla or microG).
Amazing news! Thank you
Nice, I was waiting for LOS 19
Thanks!
I'm now in lineageos 18.1 and can flash this directly, or first flash miui and then flash this
minax007 said:
@infrag
Thanks for keeping up the support for this device!
Excellent work!
Even though I would have preferred a version without Gapps (either Vanilla or microG).
Click to expand...
Click to collapse
No gapps build now in OP.
zhangzy said:
I'm now in lineageos 18.1 and can flash this directly, or first flash miui and then flash this
Click to expand...
Click to collapse
Upgrades from lineage-18.1 have not been tested by myself yet. If you want to upgrade I'd suggest wait till official builds roll out.
Can i flash this without format data? cz dipper is my daily driver and it's gonna take a long time for doing backup
running good, battery life is so-so
there is no google feed. Bug or there is something to activate?
cazkiller said:
Can i flash this without format data? cz dipper is my daily driver and it's gonna take a long time for doing backup
Click to expand...
Click to collapse
I'd wait a bit longer before flashing a daily driver with this...
infrag said:
I'd wait a bit longer before flashing a daily driver with this...
Click to expand...
Click to collapse
it's done, booting LOS19 without format data and everything is work. OTA support on this rom sir?
Thanks!
I'm use 18.1 and waiting for OFFICIAL LineageOS 19.0 Upgrade.
Without Gapps Included.
Hi! Sorry to ask if it is a stupid question, does this make the phone rooted? thanks
Barabba11 said:
Hi! Sorry to ask if it is a stupid question, does this make the phone rooted? thanks
Click to expand...
Click to collapse
not by default
running good
Thanks
couplefly said:
Thanks!
I'm use 18.1 and waiting for OFFICIAL LineageOS 19.0 Upgrade.
Without Gapps Included.
Click to expand...
Click to collapse
Official builds wont include gapps.
I only included them in the first un-official builds as I cant find a flashable gapps build thats reliable at the moment to recommend.
infrag said:
Official builds wont include gapps.
I only included them in the first un-official builds as I cant find a flashable gapps build thats reliable at the moment to recommend.
Click to expand...
Click to collapse
Yes, i am waiting for Official builds NOT include gapps.
I like LineageOS because it doesn't include gapps.
Naked is beautiful.
couplefly said:
Yes, i am waiting for Official builds NOT include gapps.
I like LineageOS because it doesn't include gapps.
Naked is beautiful.
Click to expand...
Click to collapse
Yup it is, but majority of us install gapps for all day to day needs, having both options will always be great
couplefly said:
Yes, i am waiting for Official builds NOT include gapps.
I like LineageOS because it doesn't include gapps.
Naked is beautiful.
Click to expand...
Click to collapse
Just look above and you will see that @infrag has also uploaded a version without GApps.
mattcri said:
not by default
Click to expand...
Click to collapse
how can I activate root? Is it easy to do? thanks
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?