yashsingh1/xdaforums huggingface dataset:
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] kk9999gada:
New Build 20210104

Download:

arm​

arm64​

Changelog:

Same as Build 20201214, Plus

December 2020 Security Patch

Fix Safetynet

Added Local Terminal

Update qcom.power (from Loony Kernel Beta)

(arm64) zRAM 1GB for 2GB variant.

Notes:

Some apps like SBI YONO / Lite still doesn't work / detect root. In other case, try your luck using Magisk Hide.

This arm64 build should be more stable than previous 20201214 build. (Atleast for 3GB variant). Try lk_preempt.zip if you get reboots. (Might not work for everyone)

In case, Safetynet doesn't pass in future, use "MagiskHide Props Config" module.

SELinux: Permissive (In case someone wants to know)

My new builds will be uploaded here from now.
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] Entodoays:
Just in case someone else wishes their device to pass Safetynet: I had to clear the data for Play Store and Play Services before the Store showed my device as certified.
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] manjaroid:
I've been using the Props Config module. So these recent builds don't require it?
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] kk9999gada:
Yes, Props Config module is not required in this build.
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] manjaroid:
Well at least that way you can store just about anything you want. And flash ROMs from it too, I reckon. A few years ago before my G4 Plus I had a Moto G and spent a small fortune on a fast SD card that was mostly aggravation. I gave up on it and haven't used SD cards since. So that the card wouldn't go to waste I put it in my wife's LG phone and there hasn't been any problems using it as external storage. I don't know what that means except different memory cards in different phones yields different results.

Since your earlier post it occurs to me that custom ROMs probably aren't using Motorola's camera API if the license isn't open. Which would explain why Moto Camera's image quality seems better with stock Nougat or Oreo. I wonder if the Moto Camera app can't access memory cards because of something like that. Just guessing.
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] Entodoays:
At the moment, if you enable the fingerprint sensor as a sleep button, it functions exactly like the power button. That is, if you long press the fingerprint sensor, it brings up the power menu instead of turning off the screen. It frequently happens that if I press the FP sensor for a tad too long, instead of locking the phone, the power menu shows. Is there a way to stop this behaviour? I would like the FP sensor to lock the screen, but not open the power menu on long press.
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] kk9999gada:
In current implementation (Lineage Actions), it acts just like a power button. It is unlikely to change in future builds because the previous implementation (Moto Actions) was causing issues in arm64. For consistency, I am using Lineage Actions in both arm and arm64 builds. However, you can just tap fingerprint sensor instead of long press, in order to lock screen.
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] Entodoays:
I simply have to become used to not pressing too long.

On another note Moto Camera on stock ROM you could double twist, when the camera is open, to switch cameras. With this custom ROM this doesn't happen. Mentioning it just to point it out. It's actually easier to simply tap the camera switch icon.
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] kk9999gada:
New Build 20210113

Download:

arm​

arm64​

Changelog:

January, 2021 Security Patch

Kernel updates from LOS16 (Thanks to Deivid21)

(arm64) Fixed some crashes in background.

Notes on Safetynet:

This build passes Device Certification in Play Store without Magisk and shows "Device is Certified."

Safetynet can also be tested using Magisk Manager's in-built "Check Safetynet" feature.

Some apps like SBI Yono, SBI Lite, etc still doesn't work or detect root. Even Magisk Hide won't help, due to the security measures implemented into the apps.

In future, if this build doesn't pass Safetynet, try using "MagiskHide Props Config" module.

Ignore, Safetynet Test app in Play Store. It no longer works. (I also tried it on my other non-rooted device.) (May be Google pulled a new safetynet trigger)

Edit:

6. Safetynet Test app is working again now.
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] Entodoays:
There is a bug in the alarm volume setting. If you set it to the lowest possible volume above zero (my preferred volume) it doesn't ring.
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] zitronenmelissa:
it works for me, try changing the alarm tone. If you hear it, try changing volume again. If it works you can change back to your preferred
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] Entodoays:
It seems that the clock app alarm volume does not correspond to the volume in Android settings. There seems to be a difference of one step. When the volume is set to 1 in clock, it corresponds to zero in Settings at least on my phone.
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] kk9999gada:
Thanks for reporting. I checked on my device too and I can confirm this issue. Although, not a big issue, I'll see what I can do in next build.
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] Myers99:
After installing this rom my wifi conection keeps disconnecting even though I have tried multiple wifi connections. And with my previous rom it was working so I can only presume there's an issue with this rom
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] kk9999gada:
Strange, WiFi is working fine for me. Take logcat while connecting to WiFi and then post it there in a text file.
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] Entodoays:
Would it be possible to enable Screen Mirroring to Miracast displays? The stock ROM didn't have this, but it was possible to cast to a Google Chromecast. This means that the device is, in theory, capable of screen mirroring. On other devices, under Settings > Connected Devices > Connection preferences > Cast, there's an option to search for wireless displays and this enables discovery and screen mirroring to Miracast screens like some Smart TVs.

I don't know what this entails, but it would be great if it could be implemented.
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] kk9999gada:
I had planned to include WFD (Miracast support) in the previous update but it was crashing as soon as it was getting connected to it. Since, I don't have much experience in building ROMs, I dropped the idea about adding it, there are a lot of things to take care for, while adding WFD support. We don't have official support, so, it becomes even harder.
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] Myers99:
After using this rom for some time, now it seems to be stable. When I said the wifi connection wasn't stable I had just flashed this new rom, but now it's working fine. Maybe it needed take its time as it's the very first time I'm using this rom.

I'll keep using it as I found it very balanced in means of powersave and performance (it doesn't heat as much as others and it is not lagging so far too) and if I find any issues I'll let you know.

Thanks for the support!
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] Entodoays:
May I suggest a minor improvement?

The Dark theme setting under Settings, Display reads "Device theme".

View attachment 5194341

I think it would be clearer if it read "Dark theme" or "Dark mode".

Device Theme doesn't describe the setting well IMO.
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] kk9999gada:
Thanks for suggestion.

I guess (may be), thats how ROM developers wanted. I can't do anything regarding to that and also the ROM is not being maintained anymore, only Security Patches are being updated. Also, I am still new in development. So, even I can't do anything.
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] Myers99:
For some reason I can't launch Gmail. This is what is on the log:

time: 1611239945747

msg: java.lang.AbstractMethodError: abstract method "java.util.Collection java.util.Map.values()"

stacktrace: java.lang.AbstractMethodError: abstract method "java.util.Collection java.util.Map.values()"

at aeej.d(PG:1)

at aefl.b(PG:3)

at nmr.attachBaseContext(Unknown Source:3)

at android.app.Application.attach(Application.java:212)

at android.app.Instrumentation.newApplication(Instrumentation.java:1121)

at android.app.LoadedApk.makeApplication(LoadedApk.java:1061)

at android.app.ActivityThread.handleBindApplication(ActivityThread.java:5897)

at android.app.ActivityThread.access$1100(ActivityThread.java:201)

at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1657)

at android.os.Handler.dispatchMessage(Handler.java:106)

at android.os.Looper.loop(Looper.java:193)

at android.app.ActivityThread.main(ActivityThread.java:6724)

at java.lang.reflect.Method.invoke(Native Method)

at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:495)

at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:858)
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] kk9999gada:
Gmail is working perfectly for me.

Which version of of ROM are you using? arm or arm64?
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] Myers99:
I'm using arm64.

I have a moto g4 (non plus) + 2gb ram + 16 gb of storage

Should I install arm instead?
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] kk9999gada:
No, I am using arm64 and gmail is working for me, like it should. Don't know what's wrong with your gmail.
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] Myers99:
Could you send me the link of the rom you are using? I am asking because I'm using the oldest version which was uploaded by lCrD512 and not the one's in the comment section. Maybe this is causing this issue. I think I am outdated
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] kk9999gada:
You could've found it yourself by going one only page back. Anyways, here it is:

https://xdaforums.com/t/rom-9-0_r44...oject-athene-unofficial.3889942/post-84285691
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] Myers99:
I still need to install gapps, right?
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] kk9999gada:
Yes.
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] manjaroid:
0104 was nearly perfect, 0113 not so much. No random restarts with either and that's terrific progress.

With the 0113 ARM64 release Moto Camera crashes and won't start. The ROM was dirty flashed over 0104 which bundled Moto Camera if I recall correctly. Uninstalled Moto Camera and re-flashed 0113 a second time and it appears no camera at all is bundled. Moto Camera from Play store crashes as before so I installed the Snap apk and it runs fine.

Experiencing weirdness with fingerprint logins not seen with 0104, but I'm still trying to determine if it's temporary. Yesterday and today it's fine after enrolling a fresh set of prints. However, when the sensor was previously bugging out Keepass2Android hung the phone a couple times when attempting fingerprint auth, and that was a first.

0113 is also missing the terminal app in the Developer options menu that was added back in 0104. Termux is far better anyway so might as well leave it out.
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] kk9999gada:
Thanks for pointing out, I didn't even realized that, Terminal was missing in my previous build.

Regarding Moto Camera, I have no idea why its crashing. May be, due to safetynet fixes. But, Snap Camera is already included in ROM.

Is fingerprint working fine now?
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] Myers99:
It worked like a charm! My Gmail is back now. I'll try to keep up to date if you keep releasing newer versions. Really thanks!
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] manjaroid:
Until recent builds with the Pixel coral fingerprint, I've always had to use Props Config to pass SafetNet and best results have been with the fingerprint for Pixel 2. I've tried a couple Moto fingerprints (G5 & G6 I think) without passing, as well as the athene:7.0 fingerprint in the ROM itself minus Props Config, but only Pixel 2 from Props Config worked for me. I don't mind trying it again with this build if it helps identify problems.

However, with your 0104 build and its Pixel coral fingerprint, Props Config was removed and I had no problem passing SafetyNet and Play Store certification. Same for the 0113 build. The difference being Moto Camera starting and running on 0104 but not 0113.

Anyway, I think before experimenting beyond trying Props Config it's probably time to flash the ROM clean. I can't do that right away but I'm happy to report back asap.

My fingerprint sensor is doing well for the past couple days including biometric access to Keepass2Android.
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] kk9999gada:
Don't clean flash. Try this flashable version of Moto Camera. Its working.

arm64:

https://sourceforge.net/projects/nemesisteam/files/MODs/Moto-Camera/List-N1/Marshmallow-6.0-Nougat-7.1-Oreo-8.1.0-Pie-9/ARM-64/MotoCamera_v11.1_arm64_20200626.zip/download

Flash this fix for Local Terminal from here:

https://xdaforums.com/t/rom-9-0_r44...oject-athene-unofficial.3889942/post-82797519

So, you had problems with Keepass2Android in previous builds?
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] manjaroid:
Sorry, I saw your posts and links after scrubbing the phone tonight. Long story short, Moto Camera (from Play Store) works with 0104 but not 0113. But I discovered a new problem with Termux on both builds.

Before deciding to start clean, the first and easiest thing to try was Props Config and a different fingerprint, but Termux wouldn't start and crashed the same way as Moto Camera. This put me in the mood to clean so I formatted and flashed 0113 along with Open Gapps and Magisk. Termux and Moto Camera were the next apps installed and neither would start.

Next I did the same with 0104, etc. Moto Camera started and works normally but Termux still crashes. With earlier AOSiP builds there were problems with Termux although it was running fine for me at the time. Dig back a few months in this thread and you'll find comments about it.

No, Keepass2Android never hung the phone before until build 0113. Normally jumping to the password field is the next step if biometric access doesn't work for whatever reason. It doesn't take much to interfere with print reading but I've always considered that normal. So fingerprint auth is never guaranteed but it seemed extra peculiar with this latest build.

I'm really pleased about performance and stability with both January builds. And both easily pass SafetyNet and certify with Play Store without Props Config. I saw that Snap came with both releases so I beg your pardon for saying earlier today that "no camera at all" was bundled.
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] kk9999gada:
Its fine. No Problem.

I added Fingerprint AuthSecret HAL in build 0113. So, may be due to this reason fingerprint behaved differently and enrolling them again fixed it.

However, Termux is working for me. I take logs using Termux only. Is it crashing while doing something?
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] Entodoays:
I'm using the latest ARM build and Moto Camera works well.
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] manjaroid:
Makes sense and I agree that new enrollments showed no signs of trouble.

Termux is unable to start after a new installation. I just tried reinstalling (0.105 from F-droid). Briefly there's a command prompt symbol in the status bar that vanishes after a few seconds. Try starting it a second or third time shows an error "Termux keeps stopping" with the option to close the app or copy crash log URL. Same with Moto Camera when it wouldn't start.
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] manjaroid:
Still running the 0104 build and Termux works fine by going back a version to 0.104.
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] kk9999gada:
Didn't knew until now that, I was using an older version of Termux from Play Store. No one ever mentioned before what version of Termux they were using. So, I just thought they were using it from Play Store. Just downloaded 0.105 version from F-Droid and its crashing, but 0.104 is working fine.
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] manjaroid:
I saw an article last week about Termux going missing at Play Store. Don't understand the exact details, but apparently Google turned a screw that disagrees with how Termux is built. Probably not a coincidence the newest one crashes on phones emulating Pixel.
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] mnnc:
Can't reboot the phone when the battery is at about 50% because the system shuts down immediately after is back on (it barely shows the home screen). Every attempt to turn it on ends up shuting down again. It only stops when i plug the charger at the boot screen animation. I'm pretty sure it's some issue with the Loony Kernel, because the same happened when i was using the oreo stock rom with LK installed. Is there some kernel tweaking that could fix this annoyance?
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] daktary:
Hello guys,

I'm still running AOSiP-9.0-Pizza-athene64-20200115.zip version without problem.

Since one year I never updated my rom so I'm now lost between new versions

Wich one can I use to dirty flash my rom without loosing any data or config?

Thanks
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] kk9999gada:
New Build 20210207

Download:

arm​

arm64​

Changelog:

February, 2021 Security Patch

Re-added Local Terminal (was not there in Build 20210113)

(arm64) Fixed Moto Camera from Play Store (accidently broke in Build 20210113)

Minor Tweaking and Optimization

Notes and Tips:

Avoid using any custom tweaks or playing with kernel settings. It will only make device more unstable, especially arm64 version.

This build passes Device Certification in Play Store without Magisk and shows "Device is Certified."

Safetynet can also be tested using Magisk Manager's in-built "Check Safetynet" feature.

Some apps like SBI Yono, SBI Lite, etc still doesn't work or detect root. Even Magisk Hide won't help, due to the security measures implemented into the apps.

In future, if this build doesn't pass Safetynet, try using "MagiskHide Props Config" module.

February, 2021 Security Patch Details from LOS16:

Implemented:
============
CVE: References: Type: Severity: Updated AOSP versions:
CVE-2021-0302 A-155287782 EoP High 8.1, 9, 10
CVE-2021-0305 A-154015447 EoP High 8.1, 9, 10
CVE-2021-0314 A-171221302 EoP High 8.1, 9, 10, 11
CVE-2021-0325 A-174238784 RCE High 10, 11
RCE Critical 8.1, 9
CVE-2021-0326 A-172937525 RCE Critical 8.1, 9, 10, 11
CVE-2021-0327 A-172935267 EoP High 8.1, 9, 10, 11
CVE-2021-0328 A-172670415 EoP High 8.1, 9, 10, 11
CVE-2021-0329 A-171400004 EoP High 8.1, 9, 10, 11
CVE-2021-0330 A-170732441 EoP High 9, 10, 11
CVE-2021-0331 A-170731783 EoP High 8.1, 9, 10, 11
CVE-2021-0333 A-168504491 EoP High 8.1, 9, 10, 11
CVE-2021-0334 A-163358811 EoP High 8.1, 9, 10, 11
CVE-2021-0336 A-158219161 EoP High 8.1, 9, 10, 11
CVE-2021-0337 A-157474195 EoP High 8.1, 9, 10, 11
CVE-2021-0338 A-156260178 DoS High 10, 11
CVE-2021-0339 A-145728687 EoP High 8.1, 9, 10
CVE-2021-0341 A-171980069 ID High 8.1, 9, 10, 11

Not Implemented:
================
None

Not Applicable (platform source):
=================================
CVE: References: Type: Severity: Updated AOSP versions:
CVE-2021-0332 A-169256435 EoP High 10, 11
CVE-2021-0335 A-160346309 ID High 11
CVE-2021-0340 A-134155286 EoP High 10
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] Entodoays:
Since I installed this ROM, I never had a random reboot until last Saturday. I double-twisted the phone to open Moto Camera and the phone froze, then gut stuck vibrating and rebooted.

This morning I just got another reboot, this time while reading a news article in the browser.

Is there any way I can contribute to bug fixing? Anything like collecting logs and sending bug reports…
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] kk9999gada:
I didn't got such issues. There will be reboots in arm64 version if you're using 2GB variant of this phone. There is no fix available for reboots other than using arm version of ROM. But, the reboots should be less frequent on 3GB variant on my builds. Unless you are not changing some kernel settings using some kernel manager app.
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] Entodoays:
I'm using the ARM version of the ROM and my phone is the 2GB version.
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] kk9999gada:
I tried what you said in previous post on my phone and It worked normally for me. May be, you should try doing a clean flash.
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] txtsd:
Does VoLTE work in this build? My provider is Jio and it does not work without VoLTE support.
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] kk9999gada:
Jio VoLTE is working.
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] txtsd:
Works fine. ROM is smooth af too, unlike the stock ROM which would freeze intermittently all the time.
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] Entodoays:
On my Samsung Galaxy Tab 2 (SM-813) tablet, running LineageOS 16, wireless display was not working until recently. Trying to cast to a wireless display would restart Android (but not the system). A few weeks ago, LOS have merged a bug fix that made Miracast work on LOS16.

I wonder if this same fix could be applied somehow to the Moto G4+ or if this bug fix was device specific. I heard that the problem with wireless displays in Android 9 was due to some change Google had made in Pie that made Wireless display difficult to implement on custom ROMs.

I searched the changelog, but couldn't find the bug fix which I had noticed when I had installed the LOS update.

On a different note, shouldn't this thread be labelled [ARM64/ARM32] since both variants are being offered?
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] kk9999gada:
I have no idea on how to fix miracast. Also, I am new to development and learned compiling just 3 months back.

The Original Poster (OP) of this thread has left athene. So, can't change. This thread was meant for arm64 only. Since, its not worth creating a new thread because athene development is already dead, its better to post both architecture versions in this thread itself.

You can assume that, this phone has reached end of life(EOL), all experienced developers have left athene, and all these updates by jer196 and me are just Security Patch updates and minor tweaks.
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] manjaroid:
And it's much appreciated.

My G4 Plus keeps on keepin' on. Summer marks my 4th year of use and as long as you guys keep cranking out ROMs... Do I stay or do I go?
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] kk9999gada:
Its all upto you. ;)

Will try to update till I can.
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] Korin67:
Hello,

I tried to build the ROM after some break. I found that the source tree cannot be 'repo sync' due to the following change in LOS16.0. May I know how to escape from this problem? I commented out a line in default.xml. That did not work.

fatal: couldn't find remote ref refs/heads/lineage-16.0

android_external_chromium-webview:

fatal: couldn't find remote ref refs/heads/lineage-16.0
[Moto G4 Plus ROMs, Kernels, Recoveries, & Other De] arnipms:
no se puede descargar