Just wanted to say thank you so much for maintaining this device. Been using the device tree for crdroid
[ROM][OFFICIAL][RIVER][NIGHTLIES] LineageOS 17.1
- Thread starter erfanoabdi
- Start date
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.
Do you care if I post your AFH link to Moto G7 Telegram as many avid users there also?
Thank you! I had the same issue and turning off the hardware acceleration fixed it for me as well!
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. Furthermore, as 17.1 updates progress, Tasker usability is deteriorating: can no longer mount /system as writable, can no longer turn WiFi on/off. Almost as annoying as Bluetooth issues, camera cannot save to SD card. Doesn't tell you, just never saves your photos. Why even have that option if it can't do it? Just to screw with people and lose their photos? Couple of other minor OS issues, like LineageOS updates fail and have to be re-downloaded and re-installed.
Also tried Havoc-OS, which I believe is based on LineageOS. Unfortunately, same issues. Shame. LineageOS 16.0 is missing features that I really like in LineageOS 17.1 and Havoc-OS. Admittedly, 16.0 has some annoyances itself, but at least everything works: Bluetooth doesn't randomly fail, Tasker can control WiFi, camera can save to SD.
D
Deleted member 10134073
Guest
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.
Last edited by a moderator:
so im on stock andorid 10, is there any advatnages to go for Lineage or Pixel ROM? better battery maybe? better photos? any?
Unfortunately, in the few weeks since reverting back, I have encountered twice when Bluetooth disconnected and needed to be manually connected. Dark mode, which I prefer, is barely partially functional. Most apps, particularly widgets, aren't doing dark mode at all. I have that annoying double Privacy Guard plus Android security settings, and the always-on Privacy Guard notification about apps not having access to personal data.
On the positive side for 16.1, camera photos to SD card works again (unlike 17), which is critical to my backups--I don't use my Google account for that. Tasker has access to WiFi again, whereas on 17 it has recently lost access (yes, I checked all the permissions), and SmartStay+ works again (defunct facial detection app). Both are critical to my configuration. Screen actually times out again, whereas on 17 it stayed on all the time.
So couple of annoyances going back to 16.1, but huge functionality benefits over 17 upgrade for me. YMMV.
Thank you. Your instructions helped me a lot. (I almost missed step 0) After hard bricking the phone following other instructions, I was able to install LineageOS successfully on moto G7 river (XT1962-1) I did run into some errors, but in the end everything seems to work fine. I do want to mention that it's IMPORTANT to have an active sim card installed and have the phone connected to a carrier network (and update the carrier settings in Google play store.- No need to login ) before flashing Lineage. I learned the hard way that there was NO LTE (4G) connection, no wifi calling and very poor signal after my first installation. Had to do it all again and it all works great. (including WIFI calling) I'm on Verizon btw. Hope this helps someone!
About to install for the first time. Any concept of "stable" builds to install vs. nightly which could be seen as bleeding edge with more potential to run into issues? I definitely want my first experience to be a smooth one. The only options for download I see currently are from the 17th, 10th, 3rd, and 27th, all nightlies.
If it's nothing but nightlies, should I start with the oldest since that presumably has had the most usage and I don't see any reports of troubles here?
Related question: Does the updater update you from nightly to nightly? And since the nightlies in actuality appear to be weeklies, does that mean I could use the updater weekly? Or going back to my original question, does the updater have some notion of "stable" builds and those are less frequent, sort of akin to android security updates.
If it's nothing but nightlies, should I start with the oldest since that presumably has had the most usage and I don't see any reports of troubles here?
Related question: Does the updater update you from nightly to nightly? And since the nightlies in actuality appear to be weeklies, does that mean I could use the updater weekly? Or going back to my original question, does the updater have some notion of "stable" builds and those are less frequent, sort of akin to android security updates.
I have been using this ROM since it was originally released and I keep it up to date with the weekly releases. I have zero issues with Bluetooth.
In fact, I think this is an awesome ROM. Thanks for keep developing it!
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.
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.
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.
Thank you. Your instructions helped me too
TWRP/ROOT and Lineage all working fine. Slight ROM freeze of 2-3 secs sometimes but bearable to me.Edit: Device - Moto G7 - XT1962-6
Last edited:
Hi, by this manual flash you mean. Flash Stock ROM/Copy partitions and then flash Lineage or simply flash Lineage over existing Lineage?
Last edited:
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.
Thanks for sharing your experience. I just did my update and had the same experience, except I just boot into twrp from adb rather than permanently installing it though. Updating was more seamless than I feared it could be though... It updated just fine and then I just had to boot into twrp and install the magisk zip. Magisk modules were in tact after reinstalling magisk itself though.
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
23
Moto G7
Code:/* * 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. */
Introduction:
This is the Official Lineage OS 16.0 thread for the Motorola Moto G7, codename river.
Join our Moto G7 Development Telegram Group!
How to Install:
Please follow the instructions on our Official LineageOS Wiki page here.
IF YOU ARE COMING FROM STOCK AND WANT TO INSTALL CUSTOM ROMS FOR FIRST TIME, INSTALL "Copy Partitions Zip" FROM POST #2
If you don't follow these instructions, please don't expect support here. We also don't support 3rd party addons (Magisk/XPosed/Dolby/Viper/etc.), so please don't seek support if you use these.
Notes:
- Official Lineage OS builds will not pass CTS/SafetyNet -- due to the AVB flag's "red" status. (Magisk works fine with SafetyNet patcher modules, though is not supported.)
Download:
XDA:DevDB Information
river-lineageos, ROM for the Moto G7
Contributors
erfanoabdi, SyberHexen
Source Code: https://github.com/LineageOS
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
Based On: LineageOS
Version Information
Status: Nightly
Created 2019-11-16
Last Updated 2020-08-09644
I flashed mine in almost the same way. So far loving LOS 16 w/ pico gapps
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".
Coming from stock it is automatically on slot A. Slot B on my device is blank because I clean flashed motos latest firmware.
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) 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 recovery (TWRP will load on slot B automatically)
Slot automatically changes to B on reboot (B was set to active during LOS install; slot A is set to inactive so it doesn't boot anymore)
6.5) check active slot in Reboot menu - set to A
7) Flash opengapps zip (use the arm64 version)
fastboot -w
7.5) Flash magisk zip (optional, only if you want root)
I left out root this time.
8) Reboot system on slot A
Boot system (no slot choice B is the only active slot).
My only gripe is that updates through the LOS updater menu take like 30 minutes. They finish fine but half an hour is that normal?3Hello,
I have received this week my new phone : Moto G7 (river) (xt1962-5)
And, as a lot of people here, it took me a lot of tries and error messages to manage to just install LineageOS 16.0 + Gapps.
The LineageOS official procedure never worked for me.
Here are my learnings :
My phone came with the stock OS (build PPO29.80-29) on slot A.
It automatically installed a Motorola OTA update (build PPO29.80-66) on slot B.
So at that point both slots were populated. (This is a pre-requirement)
Then I unlocked the bootloader.
The slot B is the one I wanted to install LineageOS because this is the slot with the most up to date secondary partitions (like /vendor /radio)
Here is the only procedure I could repeat without any bugs/error messages :
* Boot to bootloader
* "fastboot --set-active=a"
* "fastboot boot twrp-3.3.1-2-river.img" (temporay boot of TWRP on slot A)
* format /data
* Reboot to bootloader
* "fastboot boot twrp-3.3.1-2-river.img" (temporay boot of TWRP on slot A)
* Wipe /data /cache /system (will apply automatically to slot B)
* "adb sideload lineage-16.0-20200207-nightly-river-signed.zip" (will apply automatically to slot B)
* Reboot to recovery slot B (LineageOS recovery)
* Install update : "adb sideload open_gapps-arm64-9.0-pico-20200207.zip" (will apply automatically to slot B)
* Stay inside the LineageOS recovery and do a factory reset
* Reboot
* Enjoy
The only thing I missed is that I was not able to do a backup of the stock ROM, so I will not be able to update secondary partitions (like /vendor /radio) in the future.
