Just wanted to say thank you so much for maintaining this device. Been using the device tree for crdroid
Just wanted to say thank you so much for maintaining this device. Been using the device tree for crdroid
Weeklies in conjunction with lineage for as long as my river keeps chugging along and I never upload before making sure it at least boots for me first. I gotta say for the price I paid I'm really loving the performance I'm getting out of this device.
Weeklies in conjunction with lineage for as long as my river keeps chugging along and I never upload before making sure it at least boots for me first. I gotta say for the price I paid I'm really loving the performance I'm getting out of this device.
Start EDIT 2:
I got it working. Googling, I found this thread with a suggestion to turn off "Tethering hardware acceleration" found in "Developer options." Other suggestions in this thread did not work including to reset wireless settings (which I did).
I still have issues with my VPN but this may be specific to the app and unrelated to the tethering issue. At least, tethering my PC through my phone now, I can VPN from my PC to my network and ping/ssh to clients in that network.
END EDIT 2
I believe I just ran into this issue in which the phone is unable provide internet to another device by tethering (USB, wifi, or bluetooth) and just making the attempt disrupts data on the phone. I can get data on the phone back if I turn off tethering and then toggle data off and on.
I first observed this behavior on the july 12 build. I am uncertain if I used tethering on the june 14 build but booting to the june 14 build now, I have the same issue.
I don't use tethering frequently, but I do rely on having the ability to do so when needed so I'd like to revert back to 16.
Is there any issue with reverting to lineage-16.0-20200325-nightly-river-signed.zip on the slot that currently has the june 14 build on it?
EDIT looks like reverting to 16 is not possible without factory reset/wiping data. Also my carrier/account allow tethering and when testing just now on an recently updated ios device tethering works just fine.
EDIT 1 another possibly related symptom is that my strongswan split tunnel vpn will connect as usual (when using my carrier LTE data), but the app that uses the vpn does not pass data. I do not lose data access for other apps in this case.
Anybody else having Bluetooth issues with LineageOS 17.1 on Moto G7?
Ever since installing, my Bluetooth occasionally drops connection to car stereo or laptop. Have to manually reconnect or sometimes restart Bluetooth or phone. Two of my Bluetooth speakers now have issue where they connect then immediately drop. Fixed that with Tasker Profile to force connection after it first sees affected speakers.
I finally gave up on LineageOS 17.1 and reverted back to 16.0. Tired of loosing Bluetooth connections. Tired of Bluetooth not working and having to restart it. ...
About the time of you June post about bluetooth troubles, I was having more trouble than "normal." There were a few updates that seemed relevant to bluetooth shortly after that so I updated and removed/redid all my past bluetooth connection configs. After that it has been closer to "normal." I have had at least one unexplained disconnect since then; however, I believe I just redid the connection and it hasn't occurred again. I have yet to get a logcat after one of these events to submit with a bug report.
Regarding the SD card, others have pointed out that AOSP/googles support of using a SD card is poor. I tried it anyways and learned that I should not trust google/android for anything important. It works well enough to get by, it can be a fun toy, but all the talent that lineageos developers have x 1000 isn't enough to fix google's turds.
Installation Guide Lineage OS 17.1
0) install copypartions.zip
1) Put the phone in bootloader mode
1.2) Connect phone to PC with a USB cable.
1.3) In a Command prompt window, run "fastboot getvar all".
1.4) Make slot A the active slot "fastboot set_active a".
1.5) Boot TWRP "fastboot boot twrp.img" (use the file name on your PC for the TWRP img file)
1.6) check active slot in Reboot menu - set to A
Format data in TWRP
Wipe /system, /data, & cache (not internal storage)
2) check active slot in Reboot menu - set to B
3) Reboot to bootloader and Boot TWRP "fastboot boot twrp.img" [be sure to be on slot b]
4) Flash lineage zip
4.1) Flash twrp installer zip [this is important!]
4.2) Reboot to bootloader from TWRP.
5) fastboot -w (this will wipe your userdata partition)
6) Boot to system
7) When in system run enable rooted debugging in developer options
on your computer type adb root
and adb disable-verity
8) Reboot to twrp and install gapps of choice..
9) Reboot to system
for root:
10) reboot to TWRP
11) Backup Boot
12) reboot to system, install Magisk Manager APK
13) Run Magisk Manager, [install] (next to magisk not installed), [select and Patch a File] choose the TWRP backup of Boot, Magisk manager will save the pached boot file in your downloads
14) Pull the patched boot named magisk_patched.img on your PC
15) Reboot to bootloader and run fastboot flash boot magisk_patched.img (ignore not signed error)
16) reboot
In the event you're motivated to try 17+ again in the future:
About the time of you June post about bluetooth troubles, I was having more trouble than "normal." There were a few updates that seemed relevant to bluetooth shortly after that so I updated and removed/redid all my past bluetooth connection configs. After that it has been closer to "normal." I have had at least one unexplained disconnect since then; however, I believe I just redid the connection and it hasn't occurred again. I have yet to get a logcat after one of these events to submit with a bug report.
Unfortunately for me with moto devices (not just the mg7) and lineageos, "normal" consists of redoing my bluetooth connection settings after every update. For some reason my vehicle does not like it when I update and usually refuses to connect to a saved connection config after an update. That might explain why I don't observe the issue as frequently as you have.
EDIT: I also "reset" my wireless connections (which includes bluetooth) when I was trying to figure out why tethering had stopped working. Settings, advanced, reset options, reset wi-fi, mobile & bluetooth.
Regarding the SD card, others have pointed out that AOSP/googles support of using a SD card is poor. I tried it anyways and learned that I should not trust google/android for anything important. It works well enough to get by, it can be a fun toy, but all the talent that lineageos developers have x 1000 isn't enough to fix google's turds.
I just did my first OTA update today and Magisk+Modules did not carry over to the other slot. They were originally installed on Slot B, but when the device switched to A, it wasn't installed. That goes for all of my boot image mods, like TWRP. It was replaced with the stock LineageOS recovery. I don't know if it will do the same thing on another OTA update that switches the slot again, but we will have to see what happens next week.If I've got magisk installed, is it safer to uninstall magisk prior to letting the OTA install? Is there a better/safer way? I've read that in some cases, magisk survives the OTA, in other cases, a bootloop results, and I think I've also seen that magisk just gets lost. My phone is encrypted if that matters (didn't really intend that, but oh well). I can back up all my stuff with Titanium but if there's any risk of hosing myself by applying OTA's with magisk there, it's probably simple enough to run the magisk uninstaller, then take the OTA, then reinstall magisk. And my assumption is that uninstalling magisk would make the OTA "happy" if it would be "unhappy" with magisk present.
On my old stock + magisk phone, I just avoided OTA's entirely because I didn't want to run the risk of having to set up my phone again and possibly lose something in the process. I'd like to become confident enough in the process that I no longer avoid OTA's. So any input to help me in that regard would be awesome.
FWIW I have LineageOS for microG. Hope it's okay to ask about that variant here. I'm not sure where else I'd ask.
Installation Guide Lineage OS 17.1
0) install copypartions.zip
1) Put the phone in bootloader mode
1.2) Connect phone to PC with a USB cable.
1.3) In a Command prompt window, run "fastboot getvar all".
1.4) Make slot A the active slot "fastboot set_active a".
1.5) Boot TWRP "fastboot boot twrp.img" (use the file name on your PC for the TWRP img file)
1.6) check active slot in Reboot menu - set to A
Format data in TWRP
Wipe /system, /data, & cache (not internal storage)
2) check active slot in Reboot menu - set to B
3) Reboot to bootloader and Boot TWRP "fastboot boot twrp.img" [be sure to be on slot b]
4) Flash lineage zip
4.1) Flash twrp installer zip [this is important!]
4.2) Reboot to bootloader from TWRP.
5) fastboot -w (this will wipe your userdata partition)
6) Boot to system
7) When in system run enable rooted debugging in developer options
on your computer type adb root
and adb disable-verity
8) Reboot to twrp and install gapps of choice..
9) Reboot to system
for root:
10) reboot to TWRP
11) Backup Boot
12) reboot to system, install Magisk Manager APK
13) Run Magisk Manager, [install] (next to magisk not installed), [select and Patch a File] choose the TWRP backup of Boot, Magisk manager will save the pached boot file in your downloads
14) Pull the patched boot named magisk_patched.img on your PC
15) Reboot to bootloader and run fastboot flash boot magisk_patched.img (ignore not signed error)
16) reboot
If you update with lineage updater you will lose magisk / twrp
The best method to keep these is the manual flash / update method.
Flash lineage zip + twrp.zip
Reboot recovery
Flash magisk + gapps zip
Reboot system
I assume that by manual flash they mean flashing Lineage over lineage. Like said before, get the updated Lineage Zip and flash that, along with the other zips in the aforementioned order. You shouldn't need to flash copy partitions again. I'm pretty sure you only need to do that once when you begin flashing custom roms.Hi, by this manual flash you mean. Flash Stock ROM/Copy partitions and then flash Lineage or simply flash Lineage over existing Lineage?
I just did my first OTA update today and Magisk+Modules did not carry over to the other slot. They were originally installed on Slot B, but when the device switched to A, it wasn't installed. That goes for all of my boot image mods, like TWRP. It was replaced with the stock LineageOS recovery. I don't know if it will do the same thing on another OTA update that switches the slot again, but we will have to see what happens next week.
I assume that by manual flash they mean flashing Lineage over lineage. Like said before, get the updated Lineage Zip and flash that, along with the other zips in the aforementioned order. You shouldn't need to flash copy partitions again. I'm pretty sure you only need to do that once when you begin flashing custom roms.
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
I had the same issue. It's not the size of the partition, its the order the software is installed and the reboots done during the process. I joined the telegram group for the G7 and found some very helpful information related to the installation of LineageOS 16.0 on the G7. Here are the steps for a clean flash.
Very important - Flash the copy-partitionsAB.zip to replicate the slot A and slot B layout.
- Clean flash:
1) Put the phone in bootloader mode
1.2) Connect phone to PC with a USB cable.
1.3) In a Command prompt window, run "fastboot getvar all".
1.4) Make slot A the active slot "fastboot set_active a".
1.5) Boot TWRP "fastboot boot twrp.img" (use the file name on your PC for the TWRP img file)
1.6) check active slot in Reboot menu - set to A
2) Flash lineage zip
3) Flash twrp installer zip
3.5) Format data while in TWRP.
4) Reboot to bootloader from TWRP.
5) fastboot -w (this will wipe your userdata partition)
6) Reboot to TWRP recovery (it should be installed when you flashed the twrp-installer zip)
6.5) check active slot in Reboot menu - set to A
7) Flash opengapps zip (use the arm64 version)
7.5) Flash magisk zip (optional, only if you want root)
8) Reboot system on slot A
The G7 is my first A/B slot device and I struggled with the configuration. TWRP recovery is part of the boot partition. Installing the lineage zip, then the TWRP installer zip seems to be the required order. Then, rebooting TWRP from the installed image works to install OpenGApps. The active slot is very important, too. Many times during my installation ordeal, I would think that slot a was active, but it was slot b. I installed the copy-partitions zip when we were made aware of no bootloader on slot b a few weeks ago.
Good luck.