[OFFICIAL] LineageOS 18.1 for the Moto G7 Plus

Search This thread
I have to change my launcher to restore functionality that was integrated in the OS previous version, right?

Doesn't seem right to me.
I was just giving you the suggestion you know they took it out probably because they had the reasons but I'm just giving you an easy way to fix it which it's the launcher from havok custom ROM and you can get it in a magisk module and all I got to do is flash it boom you're good then you ain't got to worry about it and I'm not saying this about you but most people on the lineage thread or pansies and don't want to do anything about anything you got to learn somehow they just want somebody to fix their stuff for them open source non-paying jobs is what these developers have plus they have families and take care of stuff and I just do this as a hobby and it envelops most of my day so what you want to jump down the rabbit hole grab you a Linux distro and start cracking
 

yasen6275

Member
May 6, 2020
20
5
Flash a rom that does...and copy the overlay pertaining to the function you need from /system/product/overlay/ directory to external card flash next rom then use twrp file manager to place the overlay in the same directory then set permissions 755 in twrp.... Boot run su terminal #cmd overlay list this will list all overlays on phone with stars next to what's currently used... Then to enable/disable type from su terminal #cmd overlay enable nameofoverlay.apk
Use disable instead of enable for disabling... Sometimes a reboot is needed to apply.....that's low level intro easy just follow the steps and as always back up first...this will modify system...if you don't want it permanent create a magisk module to inject the overlay systemlessly....
If I need to do something so complicated to restore something that was part of the ROM in Los 16, I might better learn myself to build my own ROM.

I though that tag [OFFICIAL] is connected to some standards about not breaking functionality. Starting to reconsider that believe.
 

yasen6275

Member
May 6, 2020
20
5
I was just giving you the suggestion you know they took it out probably because they had the reasons but I'm just giving you an easy way to fix it which it's the launcher from havok custom ROM and you can get it in a magisk module and all I got to do is flash it boom you're good then you ain't got to worry about it and I'm not saying this about you but most people on the lineage thread or pansies and don't want to do anything about anything you got to learn somehow they just want somebody to fix their stuff for them open source non-paying jobs is what these developers have plus they have families and take care of stuff and I just do this as a hobby and it envelops most of my day so what you want to jump down the rabbit hole grab you a Linux distro and start cracking
Thanks for the attempt to help me. I highly apriciate it. Story if my frustration seemed aimed at you. It was not.

I'm using Linux for more than 10 years, so I'm not afraid of rabbit holes. What I'm afraid of is that I get myself in yet another Foss project plagued die"developers have families and take care of stuff " mentality. From my experience with that mentality, projects either get over it or die. Especially when we talk about removing functionality. Obviously I was wring about that Los is old enough to get over it.
 

yasen6275

Member
May 6, 2020
20
5
V
Is the vibration working in your case?
As was your initial question , my case is without vibration anywhere but on keyboard. Now when you are more "precise", I have tried vibration on calls(working) and notifications(not working). Anything I'm missing?

PS for completion I tried to turn off vibration on typing. That works.
 
Last edited:
  • Like
Reactions: maciocho

npjohnson

Senior Member
May 3, 2014
1,550
2,241
St. Augustine, FL
Upgraded using adb sideload, everything working fine, except for Wi-Fi that won't connect. Got this in the logs, any ideas?

4-04 11:04:21.368 19578 19578 I wpa_supplicant: wlan0: CTRL-EVENT-REGDOM-CHANGE init=USER type=COUNTRY alpha2=CA
04-04 11:04:23.606 19578 19578 I wpa_supplicant: wlan0: Trying to associate with SSID 'Guest'
04-04 11:04:23.606 19578 19578 W wpa_supplicant: wlan0: WPA: Failed to select authenticated key management type
04-04 11:04:23.606 19578 19578 W wpa_supplicant: wlan0: WPA: Failed to set WPA key management and encryption suites

UPDATE: my router was offering WPA2 and WPA3. I disabled WPA3 and phone is able to connect.
UPDATE #2: Problem is fixed with April 6th release.
Fixed. Update to newer build.
 

blarrgh1

Member
Jun 25, 2020
5
0
upgraded from 17.1 to 18.1 by following the guide and the only issue i'm having it is whever i try to use camera I get an error 'open camera eorror id =0'
 

Top Liked Posts

  • 1
    But the diference from stock to Lineage? How much?
    Didn't notice any difference. Check stock yourself if possible, on lineageos 18.1 it is 2.1 from 3.9 GB on average.
    Hope that this helps
  • 5
    lineage-os-logo.png

    Moto G7 Plus

    Code:
    - Your warranty is now void.
    - You have been warned.
    - Use at your own risk.

    Introduction:
    This is the Official Lineage OS 18.1 thread for the Moto G7 Plus.

    Downloads:
    Please follow the install instructions in your device's Wiki page linked below exactly, and make sure your device's firmware matches the required firmware listed.
    If you don't follow these instructions, or use 3rd party add-ons (like Magisk) please don't expect support here.

    Known Bugs:
    • None.
    • Find any? Report them according to this guide.
    Notes:
    • The only supported GApps package at the moment is MindTheGapps, linked on our Wiki page about gapps.
    Kernel Source: https://github.com/LineageOS/android_kernel_motorola_msm8998
    2
    I think I found a problem but not sure if it is build problem or A11.
    There us no option to kill app with long press of back button.
    We removed that feature for a number of development based reasons, sorry.
    1
    Does this reasons apply to mere mortals? ;)

    Let's hope no, because I find it quite useful.
    1
    Upgraded using adb sideload, everything working fine, except for Wi-Fi that won't connect. Got this in the logs, any ideas?

    4-04 11:04:21.368 19578 19578 I wpa_supplicant: wlan0: CTRL-EVENT-REGDOM-CHANGE init=USER type=COUNTRY alpha2=CA
    04-04 11:04:23.606 19578 19578 I wpa_supplicant: wlan0: Trying to associate with SSID 'Guest'
    04-04 11:04:23.606 19578 19578 W wpa_supplicant: wlan0: WPA: Failed to select authenticated key management type
    04-04 11:04:23.606 19578 19578 W wpa_supplicant: wlan0: WPA: Failed to set WPA key management and encryption suites

    UPDATE: my router was offering WPA2 and WPA3. I disabled WPA3 and phone is able to connect.
    UPDATE #2: Problem is fixed with April 6th release.
    1
    Install shady launcher and it has per app kill switch when you long press icon in recents
    I have to change my launcher to restore functionality that was integrated in the OS previous version, right?

    Doesn't seem right to me.
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone