[Moto E5 Guides, News, & Discussion] mrbox23:
I think those patches are applied at source code level. meaning it would be in a future release. My camera works running Resurrection Remix, on xt-1921-3 try copying motorola.hardware.camera.imgtuner@1.0.so from stock /system/lib/hw to /vendor/lib/hw, making sure to keep permissions same as others in vendor/lib. im willing to read logs, does your att run lineage? if so, does bluetooth work?

I make custom scripts and have a custom build.prop, for example this.....

resetprop 'media.camera.ts.monotonic' 0

resetprop 'persist.camera.HAL3.enabled' 1

resetprop 'audio.deep_buffer.media' true

Those three lines are saved to a file called mediafix.sh in /data/adb/service.d to be ran at boot. it helps with media and camera issues. As well as a one line file called led-chg.sh

echo battery-charging > /sys/class/leds/charging/trigger

Which turns on the light, otherwise never used, in front of phone when charging.

I think it's important to use a/the real fingerprint from an e5 device along with other properties. To get the best out of the hardware and least error messages during boot. I go through logcat/dmesg and attempt to fix what's broken, like the camera on lineage(works without trouble on rr remix btw). I used hidepropsconf module at first and a sprint fingerprint, but later began using the one found in info.txt of firmware zip.

ill post my work in progress build.prop(hosting it with new vendor and boot images on gdrive) which noticeably improves overall performance and lends to less log errors, or lags and crashes.

I find the vendor/boot firmware here(oldest 2018) https://mirrors.lolinet.com/firmware/moto/james/official/Metropcs/ to work best. Audio is completely a loss though. My speaker is blown now and no Bluetooth unless running stock, not even the headphone jack works. All sound comes from the one speaker, even with headphones plugged in I'm at a loss :( with that issue. :(

I also modify the boot image. turns out the 1921-3(possibly others?) uses the sdk26 8.0 android ld(library config) instead of the ld.config.27.txt that matches its sdk level. in fact if i try to force the 27 lib config, the gray/black screen comes back. it boots up, i know because my charger light comes on, but no screen. Anyhow i change the os level in boot config to 8.1.0, this gets me to where i am now with only bluetooth(mixerpath/lib issues i suspect) and a couple missing ui features due to what i imagine originate from missing whitelists in /system/etc/permissions xml files.

Another thing of note is how i spoof the mac adress for wifi, this(and other things) is done by modifying the kernel command line config in boot.img. my second e5 play xt-1921-3 has a broken screen, and serves exclusively as a wifi-repeater, captive-portal, and ssh server/tunnel. i spoof the busted screen wifi mac, with an old device mac address that is still registered on xfininity wifi network. it repeats that connection to my other devices. very efficiciently at that. with 3+MiB/s average. it took some hacking but after i found out the oem partition on this device can be formatted, and removed from the ramdisk/system all together, without consequence(not to lineage, bootleggers, or rr remix that is) and be re-purposed to whatever else. its roughly 700MB in size perfect for a debian chroot with my custom wifi repeater and misc servers. running in its own dedicated internal(FAST)partition. This device, and its kernel level mac spoofing with the now almost phased out WCNSS qualcom configurable wifi firmware, is incredible. the busted screen one has been on every day non stop functioning as a repeater, router with captive portal, and dhcp service, for almost two months. it automatically connects to wifi, kills the android zygote/system server, kills its backlight and starts up a hotspot and sshserver/captive portal, all without cell service, and without any interaction.

Anyway, new mpcs files up soon.....