• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[ROM][10.0.0_r41]LineageOS 17.1 for Moto E5 (nora) + Recovery [64Bit]

Search This thread

froggeroo

Member
Sep 19, 2021
15
0
Thank you for your hard work! Im having a "video recording/playback" issue. Camera seems to record, a file is generated, but then when I open that file theres no image, just the audio. Anyone with similar problem?

Yes, I have a similar problem. I can record videos, but the files generated from it are significantly too long (tens to hundreds of hours). Whenever I boot my phone I initally just get a screen showing "N/A" and after booting it initially always shows the date and time from when I first installed/booted up the rom. I suspect at least the first and last issue might be connected and the device/system somehow fails to keep the correct time at all levels and thus adds a lot of needless hours to the video file because one part of the system tells it it is whatever time it actually is and the other is stuck a couple days behind, making the resulting video several days long even though it's just a couple seconds.

Edit: audio and video also seem to be split, with one showing at the very beginning and one at the end. This is why I also think my problem might be the same as OP's as they only hear the audio (video might also be split).

Edit2: The issue of does not occur when setting the camera app to not record audio. Videos are appropriately short in that case.
 
Last edited:

froggeroo

Member
Sep 19, 2021
15
0
After fiddling around with it a bit more, this is what I believe is happening: When you record a video, the audio and video recording parts rely on two different variables/timekeeping mechanisms. The audio portion seems to rely on a time that is stuck around the time of the last boot up of the phone, while the video portion uses the correct time. If I boot up my phone at around 8:00 and record a five second video at 10:00, the audio portion registers an audio recording starting at 8 that lasts five seconds. Thr video portion registers a video recording at the actual 10:00 that also lasts five seconds. Those two parts are then smooshed together resulting in a video that is nominally two hours and five minutes long. The first five seconds of the video only have audio, the last five only video and everything in between is dead space that is inaccessible, only the first and last five seconds can actually be played back.
 

canolucas

Member
Nov 26, 2012
19
4
I am able to boot to the TWRP img using "fastboot boot xxxx.img", however touchscreen is not working so I cannot press anything. I can only use the phone buttons, but only to lock the screen, so I had to remove the battery to force shutdown and restart the phone.
 

Korin67

Senior Member
Feb 24, 2018
225
96

rogal104

Member
Sep 30, 2021
5
1
I have xt1944-2, my touch screen doesnt work too, but I compiled kernel with changes to nora_defconfig:
Code:
CONFIG_TOUCHSCREEN_ILITEK_CHIPSET=y
CONFIG_TOUCHSCREEN_ILI9881H=y
CONFIG_TOUCHSCREEN_FOCALTECH_MMI=y
and it works now

attaching patched boot.img
you flash it using
Code:
fastboot flash boot boot_nora_touchfix.img

found issues so far:
-lte doesnt work
-video recording files come out broken when uptime is more than few hours(example: my uptime is 10:47:00, when I record 2s video with sound and when i play it, it appears like its 8h 30min long), same as #81, #82
 

Attachments

  • boot_nora_touchfix.img
    11.8 MB · Views: 17
Last edited:

Korin67

Senior Member
Feb 24, 2018
225
96
I have xt1944-2, my touch screen doesnt work too, but I compiled kernel with changes to nora_defconfig:
Code:
CONFIG_TOUCHSCREEN_ILITEK_CHIPSET=y
CONFIG_TOUCHSCREEN_ILI9881H=y
CONFIG_TOUCHSCREEN_FOCALTECH_MMI=y
and it works now

attaching patched boot.img
you flash it using
Code:
fastboot flash boot boot_nora_touchfix.img

found issues so far:
-lte doesnt work
-video recording files come out broken when uptime is more than few hours(example: my uptime is 10:47:00, when I record 2s video with sound and when i play it, it appears like its 8h 30min long), same as #81, #82
I have xt1944-6. I do not have touch screen issue but I also have lte issue (may have video recording issue, I do not use it). We have RR and crDroid for nora now. I am very much interested in issues you have may or may not happen there, especially lte issue. I still have lte issue with crDroid. Solving the lte issue is my main objective now. Waiting for your another report.
 

rogal104

Member
Sep 30, 2021
5
1
I have xt1944-6. I do not have touch screen issue but I also have lte issue (may have video recording issue, I do not use it). We have RR and crDroid for nora now. I am very much interested in issues you have may or may not happen there, especially lte issue. I still have lte issue with crDroid. Solving the lte issue is my main objective now. Waiting for your another report.
I still have touch screen and lte issues with RR and CrDroid, but my kernel patch doesnt work there(wont boot)
 
Last edited:
  • Like
Reactions: Korin67

froggeroo

Member
Sep 19, 2021
15
0
-video recording files come out broken when uptime is more than few hours(example: my uptime is 10:47:00, when I record 2s video with sound and when i play it, it appears like its 8h 30min long), same as #81, #82

Hey there, after observing the issue a bit more, it looks like for me the time that is being added to the video is more or less precisely the time the device has been in sleep mode/display turned off (detailed description here https://forum.xda-developers.com/t/...ction-remix-for-moto-e5.4337565/post-85700181) Maybe you can check if it's the same for you, to narrow the issue down a bit.
 

Korin67

Senior Member
Feb 24, 2018
225
96
Since the links are down, I am trying to build this one from sources, the build is successful, but when I flush it it it doesn't work (stuck at bootloader).

Here is my manifest:
Code:
<manifest>
  <project path="device/motorola/james" remote="github" name="HyperTeam/android_device_motorola_james" revision="lineage-17.1"/>
  <project path="device/motorola/msm8937-common" remote="github" name="HyperTeam/android_device_motorola_msm8937-common" revision="lineage-17.1"/>
  <project path="kernel/motorola/msm8937" remote="github" name="motoe5/android_kernel_motorola_msm8937" revision="twerk-X"/>
  <project path="vendor/motorola" remote="github" name="HyperTeam/proprietary_vendor_motorola" revision="lineage-17.1"/>
  <project path="system/qcom" remote="github" name="LineageOS/android_system_qcom" revision="lineage-17.1"/>
</manifest>

Here is how I init'ed my repo:
Code:
repo init -u https://github.com/LineageOS/android.git -b lineage-17.1
I tried to do the build with ForkLineageOS, but since 10.0.0_r53, ForkLOS is no longer building (sources incompatible link)

Then I just renamed everything in devices/motorola/james to nora (including the folder itself).
Then breakfast nora -> brunch nora

The build is successful, but it just doensn't work.
I am guessing that the kernel is not compatible with 10.0.0_r53, I am not sure how to make a 10.0.0_r41 build.

Do you still continue this build project? I found a device tree for nora (no need to modify james tree). I want to try myself but my PC is only equipped with 8GB RAM. Just waiting someone else would try.


Edit: Okay, I tried with 8GB Ram PC. As is anticipated the build stopped (due to the shortage of RAM ). The error message is like this:

[ 97% 91920/94153] //frameworks/opt/net/wifi/service/proto:wifi_service_proto tu
Picked up JAVA_TOOL_OPTIONS: -Xmx6g
[ 97% 91923/94153] //frameworks/opt/net/wifi/service/proto:wifi_service_proto ja
Picked up JAVA_TOOL_OPTIONS: -Xmx6g
09:18:06 ninja failed with: exit status 137
 
Last edited:

Korin67

Senior Member
Feb 24, 2018
225
96
Okay, guys
My project of build LOS17.1 with my low-end PC was first failed. But, by adding swap I could manage to build it. It boots, so show the link. If you are interested in newer build, download it. It is a bit smaller in size than OP's 20210406 build, but it boots.
It seems very few (or almost no) people watch this thread. I will keep quiet from now on.

 
  • Like
Reactions: Gorilla Daddy

Top Liked Posts

  • There are no posts matching your filters.
  • 6
    ap_resize.php


    LineageOS is a free, community-built, aftermarket firmware distribution of Android 6, 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. Linked below is a package that has come from another Android project that restore the Google parts. 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 out Gerrit Code Review.



    What's working :

    • Audio
    • Bluetooth
    • Camera
    • Display
    • Encryption
    • Face unlock
    • GPS
    • RIL (VoLTE calls, SMS, Data)
    • Sensors
    • Video Playback
    • Wi-Fi



    Known issues:
    • You tell me the rest :confused:




    Report bugs:
    • DO NOT Report bugs if you're running a custom kernel or you installed Xposed
    • Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
    • If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
    • Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues.

    Code:
    What is your--
    LineageOS version:
    LineageOS Download url:
    Gapps version:
    
    Did you--
    wipe:
    restore with titanium backup:
    reboot after having the issue:
    
    Are you using--
    a task killer:
    a non-stock kernel (Ignore):
    other modifications:
    
    Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:

    DO NO POST BUGS WITHOUT LOGS AND PROPER STEPS TO REPRODUCE THE ISSUE


    Follow Instructions Carefully otherwise you will get error :


    • fastboot boot recovery-twrp64-nora.img (ONLY BOOT IT!! TOO BIG TO FLASH!)
    • Wipe -> ADVANCED -> Format Data - type yes
    • Wipe -> ADVANCED -- select system + vendor -> SWIPE TO WIPE
    • reboot bootloader
    • fastboot flash recovery nora-rec.img
    • fastboot boot nora-rec.img
    • Factory reset
    • Flash ROM, Gapps 10 arm64 pico together (Download Gapps from downloads section)
    • Done-Reboot Now
    • Enjoy the clean Rom



    64bit Downloads:
    ROM:

    Moto E5 (Nora) XT-1944
    TWRP RECOVERY: twrp-nora-bootonly.img
    LOS RECOVERY: nora-rec.img

    GAPPS: Gapps 10 arm64


    Source code:
    ROM:
    https://github.com/ForkLineageOS/android
    KERNEL: https://github.com/motoe5/android_kernel_motorola_msm8937/tree/twerk-X



    CREDITS:
    LineageOS
    Team Hyper
    CAF

    Special thanks to @amaterasushen for helping make this possible :highfive:


    DONATIONS:

    Please consider donating if you enjoy my work. It will be used for server expenses, Ty
    Paypal donation link: https://www.paypal.me/brickjungle

    XDA:DevDB Information
    LineageOS-Nora, 64BIT ROM for the Moto E5

    Contributors

    whodat711, karthick mostwanted, JarlPenguin, amaterasushen, wiktor140
    Source Code: http://github.com/LineageOS

    ROM OS Version: Android 10
    ROM Kernel: Linux 3.x

    Version Information
    Status:
    Alpha
    4
    I manage to successfully install this ROM even though I deviated slightly from the instructions. I did the following:

    fastboot boot recovery-twrp64-nora.img
    Wipe -> ADVANCED -> Format Data - type yes
    Wipe -> ADVANCED -- select system + vendor
    reboot bootloader
    fastboot flash recovery nora-rec.img
    fastboot boot nora-rec.img
    Factory reset
    reboot to bootloader
    fastboot boot recovery-twrp64-nora.img
    Copied the Lineage and OpenGapps zips to the internal memory and flashed via TWRP without errors
    4
    Moto E5 XT1944-4
    Catching perfectly Congratulations to those who created this rom Just a few bugs Whatsapp does not record videos when sending status (incompatible file error) The screen recording function does not work (even if installing another recording application, it will not work) Other than that, this rom is perfect, I will not change it, I just hope you update it and remove these bugs
    2
    Hello,

    i have installed this ROM a few days ago and mostly have had no issues. thanks for making the ROM. I have been having one big problem. somtimes when i get a call, the screen wont wake up and i cannot wake it with the power button, missing the call. sometimes it does work. anyone else experincing this issue? im not sure what to do. i have secure boot enabled and also the pin to scramble when unlocking the phone.
    Could you please upload the ROM, I will try to rebuild it. Also what device do you have, is it 1944-2?
    2
    Can anyone please re-upload the ROM & TWRP RECOVERY?
    gDrive is giving me page-not-found error

    Thanks