yashsingh1/xdaforums huggingface dataset:
[Nextbit Robin] blackuriel:
@npjohnson

I used MindTheGapps for arm64.

Chrome would crash or refuse to load any page.

Some other users at the beginning of this thread also reported similar problems. It seems that for some switching to Chrome Beta resolved the problem.
[Nextbit Robin] npjohnson:
no weird!
[Nextbit Robin] namikiri:
Gave it another try, 18.1-20210809 is still buggy, can't save files from messaging apps. I guess it's a scoped storage problem, how do you fix that?
[Nextbit Robin] GoldenChaos:
Was recently given a Nextbit Robin for testing/tinkering and I really like the design of this device.

However, I'm experiencing Chrome and other related apps not working :( no version of Chrome is working for me. Firefox is the only browser that doesn't immediately crash, which is less than ideal.

How can I help troubleshoot these issues?
[Nextbit Robin] Clashing Plaids:
Looks like activity has nearly died off on this forum--is 18.1 still being actively supported for our aged Robins? After the last couple weeklies I'm experiencing really bad battery drain, and a hot phone. I did a factory reset last night, with minimal install of apps, and then charged to 80% and let it sit overnight. This morning the battery was at 4%. This had not been a problem in the past, so either the battery deteriorated pretty suddenly (it is a 6 year phone, of course) or there's a problem with recent builds. Any insights?
[Nextbit Robin] npjohnson:
Yeah I support it still.

I don't see drain like that with mindthegapps?
[Nextbit Robin] Raiz:
I think your battery deteriorated (just as mine did), there is a thread talking about how to change the battery. And some users successfully fixed their battery issue.
[Nextbit Robin] Clashing Plaids:
Thanks. Yes, I used MindTheGapps, so it's likely the battery has dropped off the cliff. Oh well, it was a good run--thanks for keeping ether alive!
[Nextbit Robin] Mchasard:
No way to get 19.1 version for our device?
[Nextbit Robin] npjohnson:
Nope, 3.10 kernel lacks BPF which is mandatory for S. It would be thousands of commits to back port.
[Nextbit Robin] Mchasard:
Thanks for the answer...pity I believed that it could be done ...
[Nextbit Robin] Mchasard:
So our device will stay under android 11 ... No update possible?
[Nextbit Robin] Raiz:
No update possible unfortunately

It represents too much work, and Nolen (npjohnson) maintains other devices too.
[Nextbit Robin] Mchasard:
No new more update since October 2022 ?
[Nextbit Robin] npjohnson:
the update literally went live an hour ago?
[Nextbit Robin] mb1kid:
ok thank you
[Nextbit Robin] Mchasard:
Sorry I didn't see any update....
[Nextbit Robin] Mchasard:
I retrieve robin as daily driver phone cause the screen of my main phone is broken ...really pleasent to use even its a little slow...sometimes there's some reboot...someone encountered such issue?

Thanks in advance
[Nextbit Robin] Mchasard:
Hi I have found the function to turn off the screen double clicking on the above bar ....but there's no function to awake the screen ....is there another way instead of the power button?
[Nextbit Robin] Mchasard:
I encountered some.issues to awake my device with power button ....sometimes its very long and the device seems to reboot the.process could.be very long...anybody got.same.issues?
[Nextbit Robin] npjohnson:
Sounds like you have some sever hardware issues/damage?
[Nextbit Robin] Mchasard:
I don't know really ...strange cause I didn't use this phone a lot ...I retrieve it recently but i always updated it as possibly... So I'm the only to get such issues?
[Nextbit Robin] npjohnson:
It doesn't happen for me.
[Nextbit Robin] Mchasard:
Thanks for your feedback and you're under this lineageos version?

And you don't have any reboot?
[Nextbit Robin] npjohnson:
Yes and yes
[Nextbit Robin] Mchasard:
Strange same device same version but so much issues for me ...

Thanks for your precision's
[Nextbit Robin] npjohnson:
Hey all, I am moving and therefore the unofficial update server/wiki will be down for a few days. Likely Wednesday, Friday at the worst.

Don’t panic when links in the OP don’t work, and your Updater app says something like “Can’t connect to server”. It is planned outage.

Thanks, see you on the other side!
[Nextbit Robin] npjohnson:
Hey y'all - Unofficial build server/download portal is back up.

It may be hit and miss tomorrow as I rewire everything, but everything /should/ be functional for now.

Thanks!
[Nextbit Robin] Mchasard:
Hi last update dated from 29/09...what about new version ? Normally each month
[Nextbit Robin] npjohnson:
Build queue got shuffled. It's later in the month now.

It'll come.
[Nextbit Robin] Mchasard:
Ok thanks for this feedback
[Nextbit Robin] freddd1:
Has anyone else had trouble with the fingerprint scanner no longer working as of the past year? I am trying to pin point whether it is a hardware or software failure.

LineageOS does not offer any settings in regards to the feature any more, as if the device does not have a fingerprint scanner.
[Nextbit Robin] npjohnson:
That's hardware failure sadly.

This sensor likes to die, or the ribbon cable short.

I've had it happen to two robins :(
[Nextbit Robin] freddd1:
Sadly I can not find any video or guide on replacing it. I have already opened up the device and replugged the power button and cleaned the surface to no avail.
[Nextbit Robin] Mchasard:
Am i the only guy to get hot issues ? The device could become very hot and freeze and could reboot often
[Nextbit Robin] npjohnson:
it's an msm8992 running fairly modern android, it didn't perform well on stock.

Sadly it's going to get hot.
[Nextbit Robin] Mchasard:
Is there other settings in order to make the device less hot?
[Nextbit Robin] npjohnson:
Not really. You can just use less intensive applications.
[Nextbit Robin] Mchasard:
But just YouTube under browser is enough to make it hot...
[Nextbit Robin] npjohnson:
Sorry, really not much I can do. Intense software eon underpowered hardware.
[Nextbit Robin] Mchasard:
Ok thanks for those explanations...
[Nextbit Robin] elalbatross:
Good morning! I just flashed this onto a Robin my buddy gave me. It was sitting in storage with a completely drained battery for years. On my first charge and run-through, I've got a whopping 1 hour of screen-on time (deGoogled).

I plan to use this as a very minimal device, but the processing power is nice for fluidity so I'm not too sure I want an underclocked kernel just yet (although it would keep the stupid 808 from melting off the PCB and causing bootloops like it's notorious for doing). All that said, should I roll back to an older version of Lineage to squeeze more battery life out of this thing? Or is battery life pretty consistent across versions?

The most battery intensive task I plan to have for this thing is streaming internet radio and downloading podcasts. It's rare that I'll be streaming video (for personal reasons, I'm dumbing down the phone so I can "touch grass"). The newer version of Android allows me to use apps that aren't supported otherwise, but I can make compromises if there's a significant difference in battery.

Any info is helpful. Thanks!
[Nextbit Robin] Mchasard:
Hi I don't see any update till ...the last one from 5th march ...is the project always open?
[Nextbit Robin] npjohnson:
official builds are dead.

Unofficials will carry on once a month.
[Nextbit Robin] Mchasard:
OK thanks for your reply...so unofficial build will be find in other way ?
[Nextbit Robin] npjohnson:
Yes, I will continue building new security patches for the unofficial
[Nextbit Robin] Mchasard:
OK thanks and the link will be at this same room? I suppose that it will stay lineageos 18.1
[Nextbit Robin] npjohnson:
Yes
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] npjohnson:
Moto G7

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

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.

river

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_sdm632
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] Norla-Ruiz:
:D
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] NTGDeveloper:
I've heard that some people, including myself, have had issues with upgrading to 18.1 on some devices because it results in a broken lock screen. Is this an issue with 18.1 on the G7? I just want to make sure before I upgrade.
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] Norla-Ruiz:
In my case, at the moment it is working well, I am still testing it.

You should try to report the bug:

"Find any? Report them according to this guide"
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] npjohnson:
Only on really really old devices like bacon , etc.
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] NTGDeveloper:
Thanks for letting me know. I decided to go with a clean flash anyway just because I think my encryption on my data partition was preventing boot and restoring from a 17.1 nandroid backup broke the system completely. So far, the ROM is very good and I'm happy that I'm now on Android 11!
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] PMDPhD:
I flashed this the other night and the ROM seems to be working well. I have a question about updating the Lineage OS recovery though. I am used to flashing via TWRP, but decided to go with the Lineage OS recovery this time. In TWRP if I want to update TWRP itself, I would download the twrp-XYZ-123.img to the device, and flash the image in TWRP. I cannot see this option anywhere in the Lineage Recovery UI. Do I have to do it in ADB like the initial install of the ROM? Is there another way to update the recovery? Is it even necessary to do the recovery update (I can't find a changelog for the Lineage OS Recovery on the lineage site), I don't want to bother with an ADB recovery flash every week if nothing is actually changing in the recovery image.
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] Droid4200:
Why aren't you using the .zip? Because the linage recovery doesn't do .IMG files I would guess. The .zip is on the twrp , also the .zip can be flashed with magisk
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] Droid4200:
One thing I'm starting to hate about 18.1 is they dropped the option to Kill App by holding back button in developer settings. This may actually be a deal breaker for me, I dont think I can make it without this feature.. Shiat!
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] PMDPhD:
I am very new to Lineage OS Recovery. Always used the .IMG files with TWRP. I don't know how to flash a recovery in Lineage Recovery at all, and could not find any instructions anywhere. I did not know I could flash a recovery as a .Zip. I also just realized that my initial question is kind of moot because there is an option in the built in updater in Lineage OS 18.1 to flash both the update and recovery, so my Lineage OS Recovery is already the latest version from 4-4-21, and I won't have to figure out how to flash it. Though it would be useful to know in general.
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] Droid4200:
Yes the zip makes it so much easier now. If you use the lineageos built in update process you will lose TWRP, download the zip and you can very quicky just reboot to recovery after a lineageos update, then install the twrp.zip . you will lose root so you just reinstall majisk(if you use majisk, it'll keep your modules and settings). There may be a twrp retain script, but I haven't messed with them yet, the reinstall of twrp and majisk is pretty fast (plus I'm used to doing it the old way, sort of like you with the .IMG)
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] TomOehser:
Mostly seems pretty good. Broke "LawnChair2" launcher, but, that seems to be a problem of LawnChair going dormant; Hyperion is working o-k so far as a replacement, with some hassles converting. The OK Google voice activation for Assistant still doesn't work and I can't find any fixes, but that was true on 17.1 also. I *hate* the zooming wallpaper effect, makes it very hard to exactly position wallpaper vs. icons. That is an Android 11 "feature" though, so no getting around it...
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] FoxShadow:
Hi there. I upgraded 17.1 to 18.1 recently. Seems working fine on first day until I installed vanced app (i think).

Now, every time the screen go off and when it back on, i see glitches and bad palette color. And can't fix it without a reboot (and then when the screen go off the screen glitches comes back)

Maybe is related with Vanced and microG, any one has this issue too?
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] TomOehser:
New issue - seems I get into a situation where the notification light and a notification sound are coming without any notifications - even if "use notification light" is disabled... mystified at what is doing this so far, trying to figure it out. Also, Lawnchair mysteriously seems to be working...
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] kelue:
The display glitches with the messed up color palette might be the same bug from 17.1. To fix that I had to change the Color mode from Saturated to Boosted and it stopped.

Settings > Display > Advanced > Color

Might be a different path in Android 11, though.

Basically if the inverted color thing happens again, going to that setting and switch it to a different Color type will reset the colors back to normal without restarting. After doing that once or twice it hasn't happened after. Again, on 17.1, can't speak to 18.1 yet.
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] omino:
Working fine after a week of daily use. Upgrade from 17.1 was simple by following the instructions.

The only issue I had was with Magisk. When I installed version 22.0 after upgrading successfully to 18.1, the device would get stuck on the LineageOS boot logo. After removing all modules using adb ("adb wait-for-device shell magisk --remove-modules", then boot the device), things got back to normal. Reinstalling the modules in Magisk did not create any more issues.

Overall, a very good ROM. Thanks for the effort of creating and maintaining it.
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] Ossify:
I have an issue with "Do Not Disturb" schedules not turning off. They turn on fine but are still running the following day after the supposed end-time. I'm getting round it with Tasker, so it's not a big deal.

Thanks for maintaining the ROM and updating to version 11.
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] npjohnson:
much easier - Updater app in Settings, three dot menu, "Update recovery alongside OS"
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] FoxShadow:
Thank you! I will try that next time. I had to go back to 17.1 by now, that never happend to me on 17.1
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] kelue:
For me, if it happens, it happens shortly after booting, then a quick reset by changing the color setting will fix it, and it won't happen again until the next reboot. I noticed it happen once after plugging the charger in a minute or so after boot so maybe it's hardware related, I don't know.
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] gregbrooker:
hey everyone,

Was wondering if I can get some assistance.

New to adding a ROM to my Moto G7 and I'm not sure why it keep being unable to boot the phone after installing the OS.

If I install the ROM alone it boots.

If I try to install GApps it's unable to boot.

Can someone point to a guide known to work?

Method 1:

- fastboot flash boot twrp-3.5.2_10-0-river.img

- boot phone, copy ROM and Gapps to phone

- install ROM, try to install Gapps and get ERROR:1

- reboot to recovery again to install Gapps, it goes but phone boots to different Recovery and fails to load phone even after clearing data.

Method 2:

- Installed ROM on A, reflash recovery, reboot,

- Install ROM on B, reflash recovery, reboot,

- install GApps

- Phone boots to Recovery no matter how many times I reboot.

Tried guide here: https://wiki.lineageos.org/devices/river/install doesnt work

Also tried the steps here https://xdaforums.com/t/arm64-gapps-android-11-nikgapps-4th-apr-2021.3915866 (my method 2)

And a few other steps here and there. Even went back to stock twice and restart and it keeps failing.

Bootloader is unlocked and all that.

Any assistance would be great!
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] NTGDeveloper:
Here's a good guide that I found from a member on the G7 Telegram group.

How to flash Custom Roms on G7 River.{Noob Friendly}

I suppose you have a healthy RIVER running Android 10 stock , cool ! Let's get started. Prerequisites : 1] River , USB-C Cable and a PC. 2] ADB and fastboot installed (system-wide preferred) 3. Unlocked Bootloader 4] i] Rom - Rom.zip ii] Custom Recovery - recovery.img & recovery.zip [TWRP]...

telegra.ph

It worked perfectly for me, maybe you're missing the copy partitions step perhaps? Even if not, this worked for me, it probably will work for you.
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] gregbrooker:
I just tried this and it just take like 2o mins trying to reboot then went to recovery.

I'm returning to stock to start over again from scratch.

EDIT #1

Attempt #2

Following steps again.

ROM is flashing and says Flashing to Inactive slot: B, so A is currently active.

Should I be installing to a particular partition? A or B?

When I get to installing the GApps it says B is active, is this correct?

Edit #2

After 4 attempts all have failed.

From bootloop to all sorta errors.
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] npjohnson:
the wiki works fine.

Something must be getting crossed. Are you using arm64 MindTheGapps? And rebooting to recovery after flashing Lineage?
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] gregbrooker:
Hi,

I've tried multiple Gapps. so far if I flash ROM alone it works.

When Gapps are flashed it just takes a long time to boot then goes to Recovery or bootloop.

I'm following the steps exactly.

Are there are steps not on that guide? I just re-flashed stock rom again, I can give it another attempt.

Is that partition copy important? Don't see the use of that.

Should I be flashing to any particular partition, A or B?
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] npjohnson:
yes, it's very important.

follow the guide to a tee, and you'll be fine.

Make sure you're on the latest stock when you start too (Android 10)
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] archstar1982:
I recently ungraded clean installed.

There are few issue persists.

1, After waking a device the display color issue.

2, Google maps not getting locations. Somehow Google maps location service is not working properly. But Waze is working with no issue.

Tired to re install the maps and clear cache and data on both Play and map but not successful.

Decided to rollback the older roms and Gapps now everything working fine.
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] Droid4200:
I downgraded back to 17.1 and don't see this option. is the "update recovery alongside OS" just a 18.1 feature? I want to go back to 18.1 but If I can't press and hold back button to instantly kill an app, or have an advanced reboot menu, 18.1 will not work for me(unless an app or xposed module will get hold back button to kill app). I did notice one thing though, an upgrade from 17.1 to 18.1 will remember advanced reboot and let me use it, but a clean install of 18.1 will not give an option to show advanced reboot. Can these features be put back onto 18.1 and are there plans to have them back? Two very useful feature removed for some reason.

Thanks for working on lineageOS with Moto River by the way.
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] npjohnson:
1. Change LiveDisplay Color profile to fix

2. Works fine for me. Weird.

Update recovery is an 18.1 feature, but on the G7, it's forced to one on all android versions, because it's A/B.

So you don't need to worry about that feature/

As for Advanced Reboot, it just moved out of dev options, it is in Settings, System, Gestures, Power Menu now. You can also search for it.

Kill app back button is gone, and unless someone reworks it it won't come back.
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] marcelfox:
I'm facing the same issues here. Google Maps doesn't get my location and others apps too.
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] npjohnson:
works here in google maps... what gapps are you using?
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] archstar1982:
Can you please tell me which device of Moto G7? There are multiple model on Moto G7.
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] archstar1982:
I am using MindTheGapps-11.0.0-arm64-20210412_124247.zip link provided from official Lineage OS.
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] mumalazo:
Has anyone managed to pass safetynet? if so, how?
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] omino:
Root with Magisk, then install SafetyNet Fix module from Magisk Manager.
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] indignor:
Hi greg, i had the same issue inicially.

This worked for me:

- When failed, i re-sideloaded copy partition, re-formatted data, re-sideloaded lineage

- After flashing lineage and before any system boot, the log says to reboot recovery to switch partition before installing other zip addons, right?

- Steps 4-5 was just to check that after flashing twrp lineage was still installed. I didn't want to risk installing mindthegapps without lineage installed

​

1) So, I go reboot -> recovery but the Lineage recovery comes up. (I was on temporary TWRP before, using "fastboot flash boot")​

2) From Lineage recovery I go advanced -> reboot to bootloader.​

3) On pc --> fastboot boot twrp.img (not fastboot flash boot)​

4) From there i just checked: reboot -> recovery to see if twrp or lineage would come up as recovery, (Twrp will ask if you're sure you want to reboot to recovery because there is no recovery, but there was... lineage came up again)​

5) From lineage recovery Repeated step 2​

6) Now you can just go Advanced -> Sideload and adb sideload mindthegapps (The 11.0-arm64 version) ​

7) reboot -> system​

​
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] Kiki B:
Great job on the ROM, my G7 Plus is running like clockwork. The built-in update process is very smooth too. And even the FM Radio app is working - but who needs that? ;-)

I may have found a small glitch (if it's not my system playing wild): as per the notification and clock display I have an alarm set, but I haven't. Setting one and turning it off again does not make a difference. Did anybody else notice this?

Anyway, I am as happy as a clam with the system. Thanks a lot for this!
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] Lemnefresh:
Just installed this, overall seems great. Thanks for the hard work. I have one weird issue I've noticed so far. When I try to use the Google setup to restore my apps, it says I need to grant Play Services a bunch of permissions. I do that, but for some reason I am unable to grant permission for SMS. I click grant permission, but it's like it doesn't save. If I get out and look again, it still says permission denied. I can't restore any apps without this. Any ideas? I'm on XT1962-1

EDIT: I wiped everything and installed Gapps again. Seemed to fix it
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] NTGDeveloper:
What GApps package did you install? Maybe this might have an affect? I doubt it though
[Moto G7 ROMs, Kernels, Recoveries, & Other Develop] Lemnefresh:
I must've messed something up the first time. I wiped everything and reinstalled Gapps and now everything works. Thanks!