yashsingh1/xdaforums huggingface dataset:
[Moto E (2020)] Cyb3rSl4v3:
I think this was caused by-

set_values defined as long(int) instead of uint32_t in platform_set_voice_volume in

...audio/hal/msm8916/platform.c

I figured it out by running across a comment/commit linked to this https://github.com/fredldotme/andro...mmit/f7d003f1b9c8e4082f3878955ed23c28b318c706

might be fixed already, but I debugged it in an old tree from last march after I had some other difficulties building a current 18.1 tree. I also have managed to get a lineage-19 ginna rom built, though it doesnt actually manage to transition to bootanimation yet. Though I figured out grabbing pstore/ramoops from twrp, and diffing 18.1 vs 19 is where I'm at there. I think maybe I'm having a keymaster-4 kind of problem, perhaps something weird where my 130k soong step build failed with 3000 steps to go, for no apparent reason, then on a rerun it seemed to skip about 2700 of those before producing the nonworking build without vbmeta.img in the usual place. I'll probably go back to focusing on an up to date 18.1 build and leave the bleeding edge to people who know much more what they're doing. But I did learn a lot along the way, and I'm pretty pleased I managed to fix that annoying in-call volume problem. (also somewhat workaroundable for me by changing an 84 to a 75 in mixer_paths.xml)
[Moto E (2020)] Cyb3rSl4v3:
So, the problem I was referring to with my uptodate 18.1 home build is that I was/am seeing selinux disabled. I first verified that I am seeing the same problem on Electimon's builds here. Then, I just went to the effort of flashing stock firmware including relocking the bootloader, seeing it ok with stock, then unlocking again, reinstalling 20210621-HOMEMADE per this this thread*, and it also shows selinux disabled in lineage trust.

Now, the possibly funny thing is, I wonder if selinux might not be actually enabled and enforcing, and it's actually selinux that is causing the bug of lineage trust saying it is disabled. What makes me think that is possible is this from logcat-

02-24 04:41:37.004 967 967 E SELinux : avc: could not determine enforcing mode: Permission denied

This is after these initial selinux logcat messages (adding some context above in case it's relavent) (these are from my build before the reflash/relock/re-unlock/0621 trial of seeing the same behavior. I can provide that logcat if needed)

Of course I'd love to simply open an adb root or su terminal shell and type something like 'getenforce', but I don't seem to have those options available.**

...

Spoiler content hidden.

...

* (I used twrp-3.5.0_10-1-ginna (as I was using a year ago) because when I tried 3.5.2_10-0 (a few days ago before the relock) it seemed to crash/goblack after a first <1sec display of it's ui. )

** the next funny thing is that I just discovered that my debian bullseye system was running with selinux disabled and selinux-utils (and others) not installed. Apparently this fact has escaped my attention/memory-retention in the last couple years of using debian. It certainly will make me feel more comfortable using a phone without it but, if it's supposed to be enabled, I'll make the attempt to figure out why it's not. I can certainly imagine this could perhaps explain why my own rom builds wouldn't have a working selinux, but it seems like it can't explain the reflash-stock-relock-20210621 showing selinux disabled with the above logcat stuff.
[Moto E (2020)] Cyb3rSl4v3:
a couple further thoughts/datapoints/theories on my selinux problems-

- further below in the logcat (not included in above snippet) are clear avc denials, (that don't seem to cause any problems with the phones operation that i've yet noticed) e.g. -

Spoiler content hidden.

Also, this particular phone (my 2nd of 2 I believe identical models I have) did go through a hardish/EDL/QUSB__BULK/lolinet/blankflash/qboot unbrick cycle after a perhaps foolish attempt to flash my first 19 homebuild immediately after unlocking it. I'll write up that little saga in another thread if anyone else asks about unbricking from edl/qusb__bulk mode. But I've been seeing the same selinux disabled issue in my other phone that never went through that.

Also, and this is my current leading theory (but not at all confident in), I wonder if the fact that I do my bootloader unlocking in the middle of the stock firmware's phone-home initial update cycle might somehow be leaving parts of the system in a bad state that does not get sufficiently overwritten by the adb sideload 'flashing/installation' method. I.e. is that formatting all the relevant filesystems, or just unzipping stuff on top of whatever is there, perhaps leaving some of what was there previously behind?. And this is because I have to let it start 'phoning home' to do the update in order to get the 'allow oem unlocking' developer option to not be greyed out. I.e. I suppose I could try a relock/reunlock cycle where I let the stock os update to its hearts content before re-unlocking the bootloader and installing lineageos, and ?maybe somehow? that might be the issue here?
[Moto E (2020)] Cyb3rSl4v3:
Well, I tried another relock/stock/re-unlock/0621 cycle letting stock update all it wanted before installing and that didn't help, though I did grab full logcats from both stock and 18.1/210621. I noted that there doesn't really seem to be an official way to check selinux status in stock, though google play protect seemed perfectly happy, in 0621 as well even though lineagetrust was notifying about selinux.

I'm fairly content to not care about selinux much for some time (perhaps till after I can test with 19 rom, or other people report problems). But I can provide the logcats and some other notes. I did notice some issues with /cache in twrp before/after copypartitions and 0621

Unable to find partition for path '/cache'

next I think I'll try finally giving orangefox a go after another relock/unlock and see if that happens to get it working. If not I'll probably just adjust lineage trust to not complain about selinux for the timebeing.
[Moto E (2020)] Cyb3rSl4v3:
fyi, orangefox didn't make a difference. Part of the reason I finally tried it was hoping it would make my first magisk install go easier, and unfortunately it didn't do that (I'll mention issue in the ofox thread). But I did manually install magisk to get su (because lineage just isn't that nice anymore), which, while not managing to get adbroot to work, did let me adb shell, su, and type 'getenforce', which confirmed my theory- selinux is actually enforcing, but somehow something else (selinux itself?) is causing lineagetrust to not be able to correctly detect that selinux is enforcing, and then buggily claims it's not rather than more correctly claiming it was unable to find out. Oh well, perhaps I'll run across the answer in time as I continue to delve deeper into the massive threatsurface of the many many gigabytes of code that factor into my phone's OS ;)
[Moto E (2020)] Cyb3rSl4v3:
I'm glad I at least managed to throw the word 'think' in there. Upon further experimentation, it seems the issue wasn't the signed/unsigned/32/64bit integer stuff, but just the fluencetype change in the commit I linked to. I think further improvements can be made, as the in call volume range that can now be adjusted (on my XT2052-6) does not seem as full as the stock firmware. I'll keep trying things, perhaps poking around the stock vendor stuff and seeing if anything looks different from the github/motoe7 repo I'm building with.

Also I did notice

hardware/qcom-caf/msm8996/audio/hal/msm8916/platform.c has

#define AUDIO_PARAMETER_KEY_FLUENCE_TYPE "fluence"

instead of fluencepro which I just got working like this (as per the above linked patch similar to this one)-

Spoiler content hidden.
[Moto E (2020)] iChAbdulHaseeb:
@Electimon

Sims are not working

Sims I tried after flashing

Verzion - No SMS, No MMS, No Calls

US Mobile - No SMS, No MMS, No Calls

AT&T - SMS Work, MMS Work, No Calls

T Mobile - SMS Work, MMS Work, No Calls
[Moto E (2020)] Electimon:
Can I get a logcat for each?
[Moto E (2020)] Cyb3rSl4v3:
It seems my selinux reported as not enforcing issue is most simply fixed by changing (a single bit of source code in) line 101 of

android_device_motorola_ginna/init/init_ginna.cpp at lineage-18.1 · motoe7/android_device_motorola_ginna

Contribute to motoe7/android_device_motorola_ginna development by creating an account on GitHub.

github.com

from

chmod("/sys/fs/selinux/enforce", 0640);

to

chmod("/sys/fs/selinux/enforce", 0644);

Which seems safe enough to me. I had traced the logcat message to extern/selinux/libselinux pulled in by android.os.selinux java library used by lineage-sdk/lineagetrustinterface (used by packages/apps/lineageparts(trust)).

I don't understand init_ginna.cpp really (magisk ref in comments??). I'm also guessing there may be a different fix here that somehow involves the lineagetrust stuff not needing that world readability permission bit, perhaps related to the more recent su/magisk related linux perms/capabilities/selinux/security stuff. But it's not clear if other people are seeing this issue like I am? I definitely think I see it with Electimon's posted builds as well as my own (before the above 1 bit fix). (boostmobile/walmart xt2052-6 (2 of them))
[Moto E (2020)] iChAbdulHaseeb:
@electimon, @RohanHasabe8 , betaxab

Echo in call while using the speaker. I tried to extract audio files from the Stock moto E ROM but the issue does not solve any idea how i can remove echo.
[Moto E (2020)] petitpetitpom:
Lineage link in OP is dead, reup please?
[Moto E (2020)] AldairDoe:
https://build.lolinet.com/file/lineage/ginna/lineage-18.1-20211005-HOMEMADE-ginna.zip
[Moto E (2020)] fddm:
Index of /android/ginna/

1pwn.ixmoe.com
[Moto E (2020)] makaholic:
Do you know if this ROM is still being supported with latest security updates?
[Moto E (2020)] :
Yep it is the lastest supported for this rom on ginna. if you want a higher patch you can build lineageos yourself and cherry-pick up some commits of lineageOS moded
[Moto E (2020)] darkpower_4:
Mine doesn't have fingerprint working is that normal? And how do get the selinux to enforce? I need fingerprint working. Maybe a tut on how to fix selinux. Should I reflash?
[Moto E (2020)] Mckye96:
This rom works great on my phone, even with my limited romming knowledge. What I'd love to see next is A12-13 running on this phone. One issue I've noticed from time to time is the random reboots. While I don't use this device as my main phone, id still note this issue as some others may run into this at some point
[Moto E (2020)] fddm:
I think the random reboots are from the custom kernel in newer builds, but I don't know how to debug it without uart.
[Moto E (2020)] Dung Beetle 600:
I can't connect to wifi with this rom. When I go into setting it can clearly see my roter but when I try to connect, it fails. Any advice on how to fix? Everything else works great so far.
[Moto E (2020)] AldairDoe:
did you flashed a custom kernel?
[Moto E (2020)] Dung Beetle 600:
No. I did install magisk at one point but the wifi was broken before I did that.
[Moto E (2020)] AldairDoe:
Hmm thats weird. do you have a logcat?
[Moto E (2020)] ike8:
For those experiencing intermittent reboots, I found that changing the Performance Profile will affect reboot frequency (Settings > Battery > Battery saver and performance > Performance Profile).

When I use the Balanced profile, I get reboots every few days. The Performance profile causes reboots several times a day. Two weeks ago, I switched to the Power Save profile, and I have not had a reboot yet.
[Moto E (2020)] fddm:
This started when the kernel was changed from 4.9.206 to 4.9.227, builds before the HOMEMADE tag was added use the older kernel iirc. I think it was updated to support changed hardware in some newer units. Maybe check /sys/fs/pstore/ or /data/dontpanic/ for a console ramoops log that might tell us why it's crashing.
[Moto E (2020)] The_badboyXD:
This rom is for xt2155-5
[One (M9) Q&A, Help & Troubleshooting] narimanas:
something was tried to write and now nothing charges the phone, gives nothing to do, not even in recovery nor in download mode, what do you do? who can help
[One (M9) Q&A, Help & Troubleshooting] narimanas:
Who can tell you what to do? Have already discarded the phone
[One (M9) Q&A, Help & Troubleshooting] Goneamin:
first- you must change status to unlocked, and after changes- flash recovery twrp & ROM

but, you can try flash stock firmware, but its not simple to found needed your phone
[Off-topic] fzzyrn:
Pretty simple. Do you have any newbs in your forum that like asking questions to the general populace as a sort of a poll (how many times have you flashed your rom) especially without actually adding a poll to the thread? I find it slightly annoying, because nobody answers to those sometimes, and it just sits there, and 0 reply threads make me jumpy.

Also, they tend to make like 5 polls at a time.
[Off-topic] DaveShaw:
No, not in Kaiser... The only Polls are for user feedback, normally created by the mods.

But, I do think we should have a Poll for this thread :) :)

Dave
[Off-topic] fzzyrn:
BRILLIANT!!!

I don't think you can do it after you start the thread though, unless you're a moderator.

We get these semi-polls about once or twice a week. I guess i can't complain too much, then.
[Off-topic] galaxys:
Not too many in Hermes forum...probably since they are reduntant and then get flamed!!
[Off-topic] TheChampJT:
I think when you go into "Go Advanced", it gives you an option to add a poll.

But, the Vogue forum is so slow, which suprises me from the popularity of it. Usually get threads about, "HELP!!!!! Where is the stylus."
[Off-topic] hotrod101:
I just keep seeing more and more of them popping up. I don't answer them but it is kind of annoying as most of them are not serious. If a poll was created by a member because he was going to use the results when making decisions about a new app he was creating or updating, then that is fine and would deserve to be taken seriously.
[Off-topic] fzzyrn:
when i "go advanced" the option to for a poll is not there, so i guess that its a missed opportunity.

I try not to flame them, so i just leave them alone. It just messes with my mind to see unanswered threads (yep, i'm a tech support guy)
[Off-topic] TheChampJT:
HA!!! I knew I saw it somewhere! Goto "Thread Tools" at the top, without editing a post, and there you can choose to add a poll.
[Moto E (2020)] Electimon:
LineageOS is a free, community built, aftermarket firmware distribution of Android 10 (Q), 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.

Known issues:

You tell me

Instructions :

1. Boot into twrp

2. Advanced -> ADB Sideload -> Swipe

3. adb sideload copy-partitions.zip

4. Go back into sideload mode

5. adb sideload lineage.zip

6. Wipe Data

7. Reboot to bootloader

8. fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img

Downloads :

https://build.lolinet.com/file/lineage/ginna/

Source Code: https://github.com/motoe7

ROM OS Version: LineageOS 17.1

ROM Kernel: Linux 4.9

Version Information

Status: Stable

Credits:

Electimon - The entire device bringup

Rohan Hasabe - TWRP bringup, helped with device bringup

betaxab - Gave devices, helped with TWRP and device bringup

2/6/2021:

Fixed random crashes - https://build.lolinet.com/file/lineage/ginna/lineage-17.1-20210206-UNOFFICIAL-ginna.zip
[Moto E (2020)] Electimon:
hi yes please do

adb logcat > logcat.txt

and send me the logcat.txt after around 10 seconds of it running
[Moto E (2020)] Electimon:
i've fixed the random crashes.

2/6/2021:

Fixed random crashes - https://build.lolinet.com/file/lineage/ginna/lineage-17.1-20210206-UNOFFICIAL-ginna.zip
[Moto E (2020)] Cyb3rSl4v3:
Confirmed (so far, but I'm optimistic). Also I'm quite happy to report that mobile data is now working for me as well (maybe just a reinstall would have fixed?).

The most glaring (new?, not sure) issue/bug now is that speaker output doesn't seem to work except during calls. If I plug in headphones I do get output. Jacksensing failure could be an explanation?

Then after that, I'm getting the sense that the microphone level/gain is not good. Testing by leaving a vmail on my moto-g-2015 the level of the audio on the message seems too low. That is seperate from the longstanding issue I have had with the moto-g-2015/lineage output level. Long ago there was a known issue with a mixer_paths.xml workaround, though I've just lived with seeming lower, but barely tolerable, level since then. I've always planned on going full aosp rebuild with removing whatever softvol max limits are in place whereever. But the mote-e-2020 definitely doesn't have that problem (side by side comparison of same vmailbox checking). But it does seem with this rom the mote-e-2020 has too low mic/gain level. Seems like there could be a standardized testrig used for lineageos qa that could report expected decibel levels/metric on the devices wiki so people know what to expect.

In any event this update will definitely let me get to more serious testing.

Also worth noting, I did the upgrade by repeating the install steps. I noticed that on the copy partitions sideload it ends with an error after doing a lot of partitions fine, then ending with vendor(_b) "dd /dev/block/dm-2: write error: no space left on device". I think that may have happened on my initial install and I just ignored it, and it doesn't seem to matter (yet, afaict).
[Moto E (2020)] Electimon:
Ok, can you post a logcat while trying to play audio? Thanks
[Moto E (2020)] Cyb3rSl4v3:
also, perhaps canceling what I said about in-call output levels, I discovered I'm only getting audio during calls with headphones(jack or usb) or when speakerphone is on. I.e. what I was interpreting as good in-call audio output level in non-speakerphone mode seems to really be a not very loud speakerphone mode output. And interesting to note that the default(?remembered?) setting after installing the rom is speakerphone-on. And to what I mentioned about the mic level, I tried a set of bluetooth earbuds with mic and left equivalent voicemails, and it was clear the bluetooth mic was at standard level, while the phone mic was quite low. That led me to want to try the same test with the default soundrecorder app, but curiously it seems unable to record from (this) bluetooth mic, getting input from the phone mic even when earbuds are connected. I noted the bt/dev settings have on/off for 'phone calls' and 'media audio'. Maybe it's just not supported by these earbuds/headset. I'll check 18.1 when I go back next. Though the mic level on the recorded audio there sounded acceptable compared to the low in-call voicemail test.

Also, is there any difference and a way to install the lineage-17.1-20210207-0753-ginna-25.zip. I'm testing with 0206-UNNOFFICIAL.
[Moto E (2020)] Lahpyrcopa:
Not gonna lie, super excited about this! I never thought that this device would gain traction on XDA due to it being a very low budget device but boy am I glad it's getting some love.
[Moto E (2020)] Lahpyrcopa:
I'm having some trouble here. I can flash Lineage no problem in TWRP the phone just won't boot. So then I try to follow the instructions exactly and get this...

So my moto e booted into Lineage unexpected (I didn't think it would). Nevertheless I'm going to share the command lines I followed since some suggest they failed and I find that strange since Lineage is thus far working.

V:\Everything Android\platform-tools>fastboot devices

ZY227J63CQ fastboot

V:\Everything Android\platform-tools>fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img

Rewriting vbmeta struct at offset: 0

Sending 'vbmeta_a' (8 KB) OKAY [ 0.001s]

Writing 'vbmeta_a' OKAY [ 0.016s]

Finished. Total time: 0.049s

V:\Everything Android\platform-tools>fastboot devices

ZY227J63CQ fastboot

V:\Everything Android\platform-tools>adb sideload copy-partitions.zip

serving: 'copy-partitions.zip' (~47%) adb: failed to read command: No error

V:\Everything Android\platform-tools>adb sideload lineage-17.1-20210206-UNOFFICIAL-ginna.zip

adb: sideload connection failed: closed

adb: trying pre-KitKat sideload method...

adb: pre-KitKat sideload connection failed: closed

V:\Everything Android\platform-tools>adb sideload lineage-17.1-20210206-UNOFFICIAL-ginna.zip

Total xfer: 1.00x

V:\Everything Android\platform-tools>fastboot devices

ZY227J63CQ fastboot

V:\Everything Android\platform-tools>fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img

Rewriting vbmeta struct at offset: 0

Sending 'vbmeta_a' (8 KB) OKAY [ 0.001s]

Writing 'vbmeta_a' OKAY [ 0.015s]

Finished. Total time: 0.023s

V:\Everything Android\platform-tools>

Also, about half the internal storage is apparently taken, I must've done something wrong in the flashing process?
[Moto E (2020)] Lahpyrcopa:
Also not getting audio from speakerphone, just headphones. I cannot comment on calls as I'm not using the device as a phone.
[Moto E (2020)] Cyb3rSl4v3:
This morning my first recompile from source finally finished (took a solid couple days and an impressive swap storm on an 8G system (and cough 18G of swap used that I saw. perhaps mka -j 2 will help (default -j left 4 massive java processes running, metalava something or other)). I'll post more as I progress. I had to comment most of device/motorola/ginna/libshims/Android.mk to get it to compile. I was guess/expecting wifi tethering not to work, it seems to say no sim / phone service, though I had let my plan lapse.

But the cool thing is that I do now get speaker out. Another issue is that the recovery.img doesn't want to flash (preboot verification failed, I'll see if I can still reflash twrp next). And now that I've verified I can can compile moto-e-2020/17.1 (after having gotten moto-g-2015/17.1, with CPU_SSE42=false and JAVA_TOOL_OPTIONS=-Xmx6g, kept for e-2020), I'll go try 18.1 again to see if I can get it built without gapps (though I did recently renotice a /d/gapps app on f-droid). I had an issue with libllvm_android/LegalizeIntegerTypes there on my last attempt, but perhaps a fresh start (and reposync) will help me there as it did on 17.1 (which I'm quite optomistic I'll be happy enough with if need be soon enough).
[Moto E (2020)] Cyb3rSl4v3:
also, I discovered that MotoBootLogoMaker from another xda thread does work (on linux/debian/mono to boot), and while I haven't tried replacing the untrusted/orange unlocked bootloader warning yet, I was able to extract that image with the tool, so I'm hopeful it can be replaced (perhaps excepting the small 'N/A' rendered font text which could perhaps be obscured by some whiter pixels in a custom logo/splash/background, or maybe the font/color is tweakable with that tool too).
[Moto E (2020)] Lahpyrcopa:
Damn, it must take a very beefy machine to operate on android to take days to compile the system.

Well like I said before I only really need the headphone jack working for audio and that creepy message that Moto gives about having an unlocked phone that can't be trusted is absolutely hilarious 😂. Look, I get it Motorola if you read this, you don't want to be liable for jack all nor do any of these even bigger empires. Just tone the scare tactics down a smidge so I can breathe!

To the developer, thanks for your effort. I thought that given the price of the device no one would bother with it.