Development [ROM][10.0][UNOFFICIAL] LineageOS 17.1

Search This thread

Electimon

Senior Member
Jan 9, 2016
100
179
1pwn.tk
Moto G7 Power
Moto E (2020)
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 :

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
Alpha Kane - 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
 

Attachments

  • vbmeta.img
    8 KB · Views: 17
  • copy-partitions-20200903_1329.zip
    2.2 KB · Views: 18
Last edited:

Cyb3rSl4v3

Member
Feb 4, 2021
12
0
Thanks to everyone who contributed to these bits, I'm hopeful that by the end of the year I will be using my new moto-e-2020 as my main phone to replace my aging moto-g-2015. I've got a couple first bugs/issues/showstoppers to report, but first I think it's important to note-

Finally I'm able to go to walmart (in the usa) and buy a sub $100 ($70) 'roid (boostmobile) phone (meeting some other criteria as well) which I can immediately install a (mostly?/sdks/tools) non-google-built os on. I erred a bit by doing lots of research (to avoid paying more for a moto g7) and forgetting that the moto-e-2020 is *not* at the moment on motorola's list of models their registered (free) dev program will give bootloader unlock codes for. However after thinking I was going to have to return the phone, I parsed the verbiage on their page and decided to just try 'fastboot oem get_unlock_data'. Then tried going through motorola's unlock code process. To my pleasant surprise, they did give me an unlock code. My next hiccup happened when I was disappointed to discover the 'allow oem unlucking' option was greyed out. I netsearched and found a similar samsung issue that was resolved on phones that hadn't been updated/activated by setting their date back a week. That didn't work here, but what did work was giving my new phone access to wifi and letting it start an update. After a few minutes, while it was still updating, the 'allow oem unlocking' was no longer greyed out, and the rest of the install was straightforward enough (getting used to a and b slots for recovery).

Anyway, as for the first glaring issues-

1) random reboots, seemed at first yesterday it would average less than 10 minutes of uptime and rarely an hour. Seems a bit better right now, I'm seeing if I can get some adb logcat output of interest. Let me know if there are other tests/logs I should do. I haven't yet tried the modded lineageos18. The image I used was lineage-17.1-20210119-UNOFFICIAL-ginna.zip.

2) mobile data won't work. I note that I first activated after installing this rom. I wonder if it would have helped to activate with stock android like I probably did long ago with my moto-g-2015. Note that it shows up as 't-mobile', however given my moto-g with boost showed up as 'sprint' and boost using sprint infra which merged with t-mobile recently...? My aboutphone:simstatus shows 'network:t-mobile', 'mobile network state:disconnected' (but mobile data enabled). If I uncheck automatic network selection, I can click on 'boost' by name on a list (that doesn't include t-mobile) and it will say 'connected' right away, but with no change I see otherwise. There was a weird thing with activation as an additional line, boost first charged me $20, then later charged me $30. And the confirmation sms for the activation happened hours later, but mobile data still isn't working.

3) I'd like to know if twrp is really necessary. I noticed a recovery.img in the download directory, guessing that might be the lineageos17.1 version I was happy to see available for my moto-g-2015. I'm guessing I could try it myself, but I would like to avoid brick-risky things.

4) I wonder if the 'your phone has an unlocked bootloader / can't be trusted' post unlock splash screen can be changed (with the same?) images that are available for the moto-g-2015 (that I read can be used on some other models as well). At least with the moto-e-2020 the splash has a black background.

Feel free to let me know if there are tests I can do or logs I can provide to help. Looks very promising, but not quite usable for me so far.
 

Cyb3rSl4v3

Member
Feb 4, 2021
12
0

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).
 

Cyb3rSl4v3

Member
Feb 4, 2021
12
0
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.
 

Lahpyrcopa

Member
Jan 27, 2021
22
1
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.
 

Lahpyrcopa

Member
Jan 27, 2021
22
1
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?
 

Lahpyrcopa

Member
Jan 27, 2021
22
1
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.
Also not getting audio from speakerphone, just headphones. I cannot comment on calls as I'm not using the device as a phone.
 

Cyb3rSl4v3

Member
Feb 4, 2021
12
0
Also not getting audio from speakerphone, just headphones. I cannot comment on calls as I'm not using the device as a phone.

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).
 

Cyb3rSl4v3

Member
Feb 4, 2021
12
0
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).
 

Lahpyrcopa

Member
Jan 27, 2021
22
1
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.
 

Cyb3rSl4v3

Member
Feb 4, 2021
12
0
clarifying a few points above-

- i had forgotten the twrp install step of via .zip (including magiskboot and ramdisk-recovery.cpio stuffs). I.e. I was just able to use the lineage171 recovery to install its build, but just not to install itself as twrp can (perhaps an a/b magisk thing, not sure maybe I saw that was a known thing until lineage adds that functionality? Perhaps I could reuse the twrp zip, or presumably better start building twrp from github now that I'm past the point of having a building lineage tree to use for that purpose)

- indeed MLBM can replace the orange bootloader unlocked splash/logo (which unlike moto-g-2015, is shown after a few milliseconds of the normal seperate logo image). But it doesn't look like there is a way (yet?) with MLBM to effect the 'N/A' text/font/color which remains (again, presumably obscurable if you put an area of white pixels over it on your custom replacement)

- my specific 17.1(and 18.1) build issue with device/motorola/ginna/libshims/Android.mk not-so-much-of-a-workaround-because-simdetection/calling-no-longer-works was a result of this-

"
FAILED: finishing build rules ...
Error: makefile error
Output:
ESC[1mdevice/motorola/ginna/libshims/Android.mk: ESC[31merror:ESC[0mESC[1m "libqsap_shim (SHARED_LIBRARIES android-arm64) missing libqsap_sdk (SHARED_LIBRARIES android-arm64)" ESC[0m
You can set ALLOW_MISSING_DEPENDENCIES=true in your environment if this is intentional, but that may defer real problems until later in the build.
ESC[1mdevice/motorola/ginna/libshims/Android.mk: ESC[31merror:ESC[0mESC[1m "libqsap_shim (SHARED_LIBRARIES android-arm) missing libqsap_sdk (SHARED_LIBRARIES android-arm)" ESC[0m
You can set ALLOW_MISSING_DEPENDENCIES=true in your environment if this is intentional, but that may defer real problems until later in the build.
ESC[1mbuild/make/core/main.mk:972: ESC[31merror: ESC[0mESC[1mexiting from previous errors.ESC[0m
"

At one point, still even earlier in noob mode, I guessed and tried treating (iirc) /vendor/{lib,lib64}/libqsap_sdk.so as perhaps missing device blobz, and/or went with ALLOW_MISSING_DEPENDENCIES=true. Maybe I'll try again now that I've otherwise got a successful build. I'm doing all this just using the 3 android_ repos from github.com/motoe7. Let me know if I should be using any of the other repos.
 

Cyb3rSl4v3

Member
Feb 4, 2021
12
0
I'm doing all this just using the 3 android_ repos from github.com/motoe7. Let me know if I should be using any of the other repos.

github.com/LineageOS/android_system_qcom seems to be the answer to my libshims/libqsap_sdk.so issue. I now have a build that at first glance at least is a good reproduction with the addition that speaker out now works for me. Still no in-call volume control. Though as I typed that I see that I seem to be getting crashes similar to what I first reported here but were fixed with the update build. I'll skim my logs a bit...
 

Cyb3rSl4v3

Member
Feb 4, 2021
12
0
and seeing the recent git commits and motog7/17.1/nightlies thread (and my log) it seems I can live without MotoActions for the timebeing. I may try toggling some of the recentish audiofx things at some point to see if that gets the in-call volume control working. Also, /d/gapps seems to not apply without root, but I'll try building 18.1 again.