I have no clue what you're talking about. You just said it was working and you needed an SD card.
Start from scratch, wipe everything, follow the damn guide, and things will work fine.
Plus you're not even on the right thread, please go to the correct place
I am sorry, I did not want to bother you.I have no clue what you're talking about. You just said it was working and you needed an SD card.
Start from scratch, wipe everything, follow the damn guide, and things will work fine.
Plus you're not even on the right thread, please go to the correct place
flash stock, make a VoLTE call, return to lineage.I just got a warning email from T-mobile that my G7 Plus doesn't have VoLTE enabled. But that option is shaded out in LOS UI. What's wrong? How can I fix this? I am sure I have the US version of the G7 Plus that is supposed to support this. Is it vendor firmware issue? Do I have to flash something not taken care of in LOS?
Yes, you will need to wipe data.Where can I find the latest stock image? I assume this means I have to wipe out data partition then
Are these OK to use? https://mirrors.lolinet.com/firmware/moto/lake/official/TMO/
Found that on this reddit thread: https://www.reddit.com/r/LineageOS/comments/jyz3r9
Incidentally, I was going to try this modem flash idea, but I couldn't get fastboot flash to work at all. It would just not write to the phone no matter what. What happened to the fastboot mode option in the LOS recovery? At least my OnePlus 6T has it.
Dear guys, npj, should this also help on L19.1 when the Volte options are present and on but not working (not registered says the 3636 test)flash stock, make a VoLTE call, return to lineage.
It will work fine.
Yes.Dear guys, npj, should this also help on L19.1 when the Volte options are present and on but not working (not registered says the 3636 test)
I did try this again (on lineage 17/18/19 now) and none of them work for cricket/AT&T.
Zuba, this is a wild idea, but maybe worth trying. Pull the stock ROM vendor partition from the zip and flash it alone on your phone already running LOS.
i.e. fastboot flash --slot=all vendor vendor.img
My theory is that the LOS build for lake provides vendor. My OnePlus6t (fajita) LOS rom does not. I had to manually flash vendor from OP6T stock. If I'm right, the problem might lie in the LOS vendor partition. This is a fairly wild guess. It might break your LOS install, but you can easily fix it by reflashing LOS. I feel it's worth a shot and was going to be something I tried after stock ROM reflash (I plan to get around to it Monday).
For more background, see this post for fajita users: https://wiki.lineageos.org/devices/fajita/fw_update
Hmm, well of all things I did a TWRP backup of my phone before starting all of this a few days ago (moved the backup to my pc). When I tried to restore the backup it always failed. Then I excluded vendor and it worked. I'm currenlty still on that backup version, although it does have a few bugs now. I'm not even sure what vendor I'm running right now. I can send texts (but I think that is cuz I have the wifi option checked on?), but cannot make phone calls. I could attempt that method at some point, but not sure if I can get to that today.Zuba, this is a wild idea, but maybe worth trying. Pull the stock ROM vendor partition from the zip and flash it alone on your phone already running LOS.
i.e. fastboot flash --slot=all vendor vendor.img
My theory is that the LOS build for lake provides vendor. My OnePlus6t (fajita) LOS rom does not. I had to manually flash vendor from OP6T stock. If I'm right, the problem might lie in the LOS vendor partition. This is a fairly wild guess. It might break your LOS install, but you can easily fix it by reflashing LOS. I feel it's worth a shot and was going to be something I tried after stock ROM reflash (I plan to get around to it Monday).
For more background, see this post for fajita users: https://wiki.lineageos.org/devices/fajita/fw_update
They both include vendor. Your info is outdated.Not to be argumentative, more for my own clarity: why does fajita vendor firmware update include vendor and the LOS rom for it doesn't? Is it just whim of the developer or what?
Fantastic.Hey npjohnson. Did you see my latest reply in the 19.1 thread? Your advice completely worked for me on Tmobile!![]()
- Your warranty is now void.
- You have been warned.
- Use at your own risk.
In 18.1, you can change the default camera app just fine. If you install one, and double click power button, it will ask you which camera app to use, and if it should be default.Hi guys,
anyone knows if it's possible to change the default camera app? As you probably discovered, on Android 11 is not possible to set a different default application for camera. For example, if you want to take a picture from an app like sports tracker you must use motorola app. Any possibility to change the original app, setting open camera or another?
Could it be possible to substitute the original app before compiling the rom?
Nope, Lineage Recovery should be used on this device. Magisk will persist if you use the Updater app.Online Updates: 18.1 XT1965-2
Always reverts to Lineageos Recovery. Necessary to reinstall Twrp and Magisk. Any way around this ??
Can't do that here, we're A/B. It will tell you you can't do that if you try.
Nope, issue doesn't exist for us, that was a typo on 632-common, we use 660-common, my TMO SIM is still fine.Hi,
For many builds now my phone doesn't recognize the sim card after a reboot or an update- tray needs to be pulled out on each occasion. I've tried everything so far... Anyone else?
@npjohnson
I've seen this reported for moto g7 play and power, fixed two or one build back... Is this something that you can look at for the next update please?
Or maybe you can advise on a possible update of non-hlos.bin or such I should perform myself? Thanks in advance!SIM card not recognized after Lineage 18.1 update (#3451) · Issues · LineageOS / issues / android · GitLab
Expected Behavior I use Lineage OS for Microg...gitlab.com
I was able to make Google Pay work and SafetyNet pass just finenope - you can try magisk but I doubt it'll work.
Yes, you can OTA just fine!
I'll attach some examples that I shot with it, you can take extremely detailed pictures with both back and front cameras.Thank you for your suggestion koimr, I found out that the port of Moto Cam 2 that worked on my previous OS was made by Nemesis. So I looked for a version for Moto G7+ compatible with Android 11. Here it is https://sourceforge.net/projects/nemesisteam/files/MODs/Moto-Camera-2/List-N2/Android-11/ARM-64/ . I installed it via TWRP and it worked!
I've made some test shots with three cameras: Moto Cam 2, Pixel GCam you suggested and Open Cam. Moto Cam (which now does not offer a switch of HDR) and GCam (with HDR+ activated) give pretty close results in day light. Moto tends to render darker and punchier dark areas while GCam extends DRO for them so that shots get less contrasty and less colorful. Besides Moto files are 15-20% heavier than those by GCam, I think for keeping more color info in darker parts. Open Camera with HDR activated is another story. Sometimes it gives a pretty well balanced image while sometimes a lollypop HDR effect is too strong. In low light Open Camera renders too grainy image. My previous experience with Moto was positive. I could compare it to GCam later.
As for daylight shots, I attach unedited samples of two scenes. In both cases first comes Moto Cam 2 (default settings), then GCam (HDR+) and third Open Camera (HDR). You can see the variation.
There was a shocking moment in the first experience of GCam. I discovered that if you switch off the HDR+ mode, the app uses the second front camera, and you just have no choice to change it. I am unaware if this happens only with G7+ or it's a general feature. I tend to say it's a shame, as the image is limited to 1920 at its large side, and the quality of the oversharpened image is simply ridiculous. Welcome back to 1998. The last shot attached is an unedited GCam shot taken this way, with HDR+ off. I wonder if that could be fixed someway for G7+.