Database Users

H918 WETA ROM 4.9.4 + Magisk 12.0 bootlooping

Hello there, I've been using the V20(H918) for a little while now and was running WETA Rom 4.8.5 with Magisk 11.0. When Magisk 12.0 released after rebooting and being on for a minute or 2 my phone would suddenly go back to the T-mo splash screen as if it were soft rebooting and then would repeat this process. I thought it might have been a download or flash issue so I tried wiping and doing a fresh install but if I ever restarted the device the same issue would appear. I've tried selecting or deselecting a majority of the options in the aroma installer for WETA but nothing seems to work. The rom seems to work fine with SuperSU installed so I'm thinking it might be something about the way my phone is set up but I haven't been able to pinpoint exactly what it is and I really would like to use Magisk for the hide feature. Based on the thread it doesn't seem like there should be any issues and I'm unable to ask my question directly in the thread. I'm not very experienced with these kinds of things so I'm sorry if I'm not being specific enough or if the solution is obvious. Thanks for anyone's help and time with this issue!

survivingarch said:
Hello there, I've been using the V20(H918) for a little while now and was running WETA Rom 4.8.5 with Magisk 11.0. When Magisk 12.0 released after rebooting and being on for a minute or 2 my phone would suddenly go back to the T-mo splash screen as if it were soft rebooting and then would repeat this process. I thought it might have been a download or flash issue so I tried wiping and doing a fresh install but if I ever restarted the device the same issue would appear. I've tried selecting or deselecting a majority of the options in the aroma installer for WETA but nothing seems to work. The rom seems to work fine with SuperSU installed so I'm thinking it might be something about the way my phone is set up but I haven't been able to pinpoint exactly what it is and I really would like to use Magisk for the hide feature. Based on the thread it doesn't seem like there should be any issues and I'm unable to ask my question directly in the thread. I'm not very experienced with these kinds of things so I'm sorry if I'm not being specific enough or if the solution is obvious. Thanks for anyone's help and time with this issue!
Click to expand...
Click to collapse
alot of people have this problem with 12.0 flash the 11.0 and dont update

survivingarch said:
Hello there, I've been using the V20(H918) for a little while now and was running WETA Rom 4.8.5 with Magisk 11.0. When Magisk 12.0 released after rebooting and being on for a minute or 2 my phone would suddenly go back to the T-mo splash screen as if it were soft rebooting and then would repeat this process. I thought it might have been a download or flash issue so I tried wiping and doing a fresh install but if I ever restarted the device the same issue would appear. I've tried selecting or deselecting a majority of the options in the aroma installer for WETA but nothing seems to work. The rom seems to work fine with SuperSU installed so I'm thinking it might be something about the way my phone is set up but I haven't been able to pinpoint exactly what it is and I really would like to use Magisk for the hide feature. Based on the thread it doesn't seem like there should be any issues and I'm unable to ask my question directly in the thread. I'm not very experienced with these kinds of things so I'm sorry if I'm not being specific enough or if the solution is obvious. Thanks for anyone's help and time with this issue!
Click to expand...
Click to collapse
Im currently running weta rom with magisk 12.0 on my h918. However there are 2 possible differences between yours and mine. 1) you are not in the latest version of weta rom 4.9.4. 2) you are probably flashing the stock kernel that comes in the weta aroma installer. Try with konvergent or another kernel other than the one from weta rom. (as soon as i flashed the weta kernel my phone was experiencing the dame thing yours did , then after i flashed konvergent back it came back to normal)

jinkerz9430 said:
Im currently running weta rom with magisk 12.0 on my h918. However there are 2 possible differences between yours and mine. 1) you are not in the latest version of weta rom 4.9.4. 2) you are probably flashing the stock kernel that comes in the weta aroma installer. Try with konvergent or another kernel other than the one from weta rom. (as soon as i flashed the weta kernel my phone was experiencing the dame thing yours did , then after i flashed konvergent back it came back to normal)
Click to expand...
Click to collapse
Did what you said and everything seems to be running smoothly, thanks very much for your help! Hoping a more updated kernel that doesn't force SuperSU and works with magisk comes out soon!

Android Auto: Something Went Wrong (Google Play Services)

I recently acquired a Nexus 6P.
TWRP is properly installed as the Recovery - twrp-3.2.3-0-angler
First thing I did with the device was flash the latest Android 8.1 Oreo version to it - angler-ota-opm7.181205.001-abb36a2f
I then installed Lineage OS 15.1, Open G Apps 8.1 (nano), and SU
From there I've done nothing but struggle with bugs and quirks. The device has been re-imaged several different times, with different variations of the above setup, and one of the main things I need to get working (Android Auto) keeps failing. Does anyone have any idea why Android Auto keeps pulling up the error "Google Play Services doesn't seem to be working right now"
All of the suggestions I've found online have failed. Screenshots have been provided for the version info and error. I've already cleared the data caches and tried to re-install and re-flash the device.

I got pissed and went back to JUST the stock OTA for testing/verification. With the stock rom there are no issues. Seems like Lineage OS 15.1 on the Nexus 6P has some bugs to work out. A fully functional stock phone is better then being frustrated.
If anyone can confirm I'm not crazy or explain what I missed while troubleshooting that would be awesome.

GTF696 said:
I got pissed and went back to JUST the stock OTA for testing/verification. With the stock rom there are no issues. Seems like Lineage OS 15.1 on the Nexus 6P has some bugs to work out. A fully functional stock phone is better then being frustrated.
If anyone can confirm I'm not crazy or explain what I missed while troubleshooting that would be awesome.
Click to expand...
Click to collapse
Try magisk as root method insted of su...
Other than that, cant think any other solution

GTF696 said:
I recently acquired a Nexus 6P.
TWRP is properly installed as the Recovery - twrp-3.2.3-0-angler
First thing I did with the device was flash the latest Android 8.1 Oreo version to it - angler-ota-opm7.181205.001-abb36a2f
I then installed Lineage OS 15.1, Open G Apps 8.1 (nano), and SU
From there I've done nothing but struggle with bugs and quirks. The device has been re-imaged several different times, with different variations of the above setup, and one of the main things I need to get working (Android Auto) keeps failing. Does anyone have any idea why Android Auto keeps pulling up the error "Google Play Services doesn't seem to be working right now"
All of the suggestions I've found online have failed. Screenshots have been provided for the version info and error. I've already cleared the data caches and tried to re-install and re-flash the device.
Click to expand...
Click to collapse
I got error when installed lineageos15.0 on twrp 3.2.3 , suddenly automatic restart. Can you help me dude ?

Need help getting LineageOS to be stable (15.1 UNOFFICIAL, hltevzw, TWRP 3.3.0)

I have an SM-N900V (Note 3, Verizon variant, hltevzw).
Detailed timeline:
- I flashed it back to firmware OB6 using Odin 3.09.
- I rooted it using ArabicToolApp.
- I used this tool to unlock the bootloader
- I installed a build of LineageOS 14.1 for hlte
- It didn't recognize the SIM so I did a dirty flash of this build of LineageOS 15.1 for hltetmo on top (hltetmo actually has different hardware than hlte, and the correct one for SM-N900V)
- Messed around with the APNs until it recognized and connected to Verizon's network. I DO have functioning SMS and LTE data, but I have not tested phone calls yet
- Messed around some with SuperSU in system- and systemless-mode. Bricked my device more times than I could count, then unbricked over and over using SuperSU's impeccable installer. Messed around with this quite a bit
- Also messed around with Xposed some. The OS is too unstable to run Xposed Installer correctly, so I uninstalled it
- Removed SuperSU, installed Magisk. Phone now passes SafetyNet
So, my phone now runs 8.1 and a Lineage build from 9 days ago. Cool. But, if I was satisfied I wouldn't be making this post. There are multiple instances of the same kind of "app freeze" - App screen freezes, sometimes it'll go completely black. Interactivity doesn't work, obviously, the app is completely frozen. Hold Back to kill doesn't work (Application Killed toast shows, but nothing happens). ANR (when it comes up) Close doesn't work. Home button works and brings me away from the app, but it's still there. Swipe away in Overview doesn't actually kill the app. Even in App Info, Force Stop doesn't work. The app is forever frozen. Tapping the icon from the launcher no longer does anything, it doesn't even bring up the app. The app is permanently crashed and inaccessible until a reboot.
Issues:
- Sometimes when booting the phone will not recognize the SIM until a reboot. As in, "No SIM" message and everything
- Sometimes it will get stuck at boot, I have foxy-boot installed, so I can see the logs. I don't remember what it was all about, if it comes up again I'll update the post
- Google Chrome sometimes crashes when trying to download a file. I've gotten my phone to self-host before, but this issue always seems to come back, and when it does Google Chrome ALWAYS crashes when trying to download a file. App Freeze
- Netflix installs and logs in but freezes at the "can't connect to service (-9)" message. App Freeze
- Certain apps like NativeScript Playground get stuck at the splash screen. App Freeze
- Xposed Installer did this when opening the Settings, whether Xposed was installed or not. App Freeze
- F-Droid also sometimes crashes, although it's somewhat arbitrary, I can't reproduce it reliably. App Freeze
I have tried reflashing the ROM, flashing Xposed uninstaller, reinstalling Magisk, none of it seems to work. I have TWRP 3.3.0 so I can do pretty much anything that doesn't involve the SD card (the SD card is probably broken in hardware, it's so read-only that Android and TWRP both can't write to it at all, but they can both read the same half-broken filesystem).
I fear that this OS is just too unstable for the phone and there's nothing I can do. I sincerely hope this is not the case.

Try other ROMs or perform a clean installation.
Make sure you are on PL1 bootloader/modem.
Currently using Resurrection Remix v5.8.5 Nougat because it was the last Android version for this device with working Bluetooth calls but if you don't use that feature you could use their Pie version as well.
RR ROMs are solid and work extremely well.
Do a clean installation via TWRP if you go this route.

terminator911 said:
Try other ROMs or perform a clean installation.
Make sure you are on PL1 bootloader/modem.
Currently using Resurrection Remix v5.8.5 Nougat because it was the last Android version for this device with working Bluetooth calls but if you don't use that feature you could use their Pie version as well.
RR ROMs are solid and work extremely well.
Do a clean installation via TWRP if you go this route.
Click to expand...
Click to collapse
I did a clean installation of RR 6.0.0 (Android 8.1) and it works a lot better than LineageOS did, with even more configuration options. I really really hate Pie and its gesture-based gimmicks (Screw you Google for copying more of Apple's bad design decisions), so I assumed Oreo would be more stable, but the ROM I installed still has crashing apps. Google Chrome still won't download most things (I've gotten it to download before), trying to change the accent color crashes the 'LineageOS Settings' app, and F-Droid is seriously messed up, but most other things are stable, including the Verizon network which required no pesky APN setup.
I'm on the OB6 bootloader/modem, is that a problem? I doubt that would be an issue, but I can always back up and reflash via Odin. The cool thing is that I installed a patch to TWRP which backs up /data/media along with everything else, after installing the custom ROM. So, really, I can do anything and be perfectly fine. There's, AFAIK, no way to ruin the phone unless something exploits the eMMC brick bug.
If there's another ROM you'd recommend me install, I'd be happy to try it out. I would really like to have a stable OS on here, where Chrome will work and download files. I'd also love Camera2 API since the phone has the chip for it (Snapdragon 800), but none of the ROMs I have support it and there's been no discussion online other than some years-old threads with no answers. I know there have been some articles online listing Note 3 as a phone that'd support Camera2 API with a software update. Would updating the bootloader/modem do anything on that front?

I would upgrade to PL1 bootloader/modem for your device. This is what I have and have had 0 issues. I'd recommend you trying the Samsung Internet browser over Google Chrome; it's much better in my opinion.
You can find the modem here:
https://androidfilehost.com/?w=files&flid=160694
As far as ROMs are concerned you can either try the Nougat version of RR which is what I am currently using as my daily driver with no issues at all including Bluetooth calls:
[ROM][HLTE\TMO\CHN][OFFICIAL]*** Resurrection Remix N 5.8.5 ***[13.03.2018]
https://forum.xda-developers.com/ga...-resurrection-remix-n-v5-8-3-vanilla-t3615227
See here to check whether or not your phone has the Camera2 API capabilities; if not use OpenCamera.
https://www.androidexplained.com/camera2-api-support/

terminator911 said:
I would upgrade to PL1 bootloader/modem for your device. This is what I have and have had 0 issues. I'd recommend you trying the Samsung Internet browser over Google Chrome; it's much better in my opinion.
You can find the modem here:
https://androidfilehost.com/?w=files&flid=160694
As far as ROMs are concerned you can either try the Nougat version of RR which is what I am currently using as my daily driver with no issues at all including Bluetooth calls:
[ROM][HLTE\TMO\CHN][OFFICIAL]*** Resurrection Remix N 5.8.5 ***[13.03.2018]
https://forum.xda-developers.com/ga...-resurrection-remix-n-v5-8-3-vanilla-t3615227
See here to check whether or not your phone has the Camera2 API capabilities; if not use OpenCamera.
https://www.androidexplained.com/camera2-api-support/
Click to expand...
Click to collapse
Excuse me but custom ROMs don't have "the Samsung Internet browser". Additionally the modem shouldn't cause app crashes (if it does, correct me please).
I might try the Nougat ROM. Bluetooth calls don't matter to me, but stability does. I just kinda really like Oreo and all its customization options but it may be too new for this old phone from 2013. It still works as a phone though, Messages and phone calls work fine, so I may just deal with it.
I use Open Camera, and I've tried multiple Camera2 API enablers. The phone has a Qualcomm Snapdragon 800 and the necessary links (in hardware, between the camera/other things) to support Camera2, but nobody seems to have tried it. Probably because the Verizon Note 3 is really locked down, and can only be rooted on a special version of the samsung ROM, and can only be bootloader-unlocked via the eMMC brick bug... There are Magisk modules for Camera2 on Exynos-based devices, but none for the Verizon Note 3 AFAIK.

I just found out that RR 7 officially supports `hltetmo`, but RR 6 doesn't. That's kinda sad, I hate Pie, but I might try it...

I've had the SEPL stuff before, that's the one that can't be rooted. I suppose I didn't consider upgrading again after I unlocked my bootloader. I'll try SEPL1 firmware again, but with a custom ROM...

You can install the Samsung browser from the Play Store. Again, highly recommended.
As far as SEPL1 just update the modem to it; that shouldn't cause any issues but it will ensure your SIM is recognized and data works with the latest ROMs. That is one requirement you will see listed on all of these ROMs.
Not sure which one you are trying to install but here are all the Resurrection Remix versions:
Nougat:
https://forum.xda-developers.com/ga...-resurrection-remix-n-v5-8-3-vanilla-t3615227
Oreo:
https://forum.xda-developers.com/galaxy-note-3/development/rom-resurrection-remix-n-6-0-0-t3748689
Pie:
https://forum.xda-developers.com/galaxy-note-3/development/rom-resurrectionremix-v7-0-0-t3894244
If you don't care about Bluetooth audio during calls then you can safely use Oreo and Pie options.

terminator911 said:
You can install the Samsung browser from the Play Store. Again, highly recommended.
As far as SEPL1 just update the modem to it; that shouldn't cause any issues but it will ensure your SIM is recognized and data works with the latest ROMs. That is one requirement you will see listed on all of these ROMs.
Not sure which one you are trying to install but here are all the Resurrection Remix versions:
Nougat:
https://forum.xda-developers.com/ga...-resurrection-remix-n-v5-8-3-vanilla-t3615227
Oreo:
https://forum.xda-developers.com/galaxy-note-3/development/rom-resurrection-remix-n-6-0-0-t3748689
Pie:
https://forum.xda-developers.com/galaxy-note-3/development/rom-resurrectionremix-v7-0-0-t3894244
If you don't care about Bluetooth audio during calls then you can safely use Oreo and Pie options.
Click to expand...
Click to collapse
Yeah but, data and calling worked fine on the LineageOS and RR roms, so there's no reason to update the modem.
Besides, I flashed SEPL1 6 times using Odin (multiple times by flashing, rebooting directly into download mode and flashing it once more) and it doesn't want to update. Still on OB6. On the latest (official Pie) RR rom, data worked on first boot but doesn't work anymore (I'm going to mess around with the data settings until it works), but I have no reason to believe that my phone needs a modem update to function.
I did, many times, make calls to various phone numbers and they all worked flawlessly. SEPL1 is therefore not needed if that's all it does.
And I do know about all the Resurrection Remix versions: One is Nougat from their archive, one is the Oreo version I had installed just yesterday before flashing Pie, and the other one is Pie which is now officially supported.
I am currently working on getting RR7 to work, it's only crashed a few times, and I don't even remember what those times were (I think it was using the Back button in Overview/Recents at the same time as the Overview button?)

When updating modem via Odin you have to pull the battery and don't let it reboot the phone for it to stick (disable that option in Odin) and flash it again and then reboot. If you look at the ROM threads for anything newer than Android v5 they all recommend updating to the latest bootloader & modem for your device which in this case is PL1. This can be to prevent crashes/no signal /no SIM, etc...
Are you dirty flashing these ROMs? I have never experienced any crashes with any of the RRs on my phone but I always do a clean install and make sure to also delete the "Android" folder on my SD Card via TWRP after doing the "Advanced" wipe and deleting everything listed there except for the External SD Card.

terminator911 said:
When updating modem via Odin you have to pull the battery and don't let it reboot the phone for it to stick (disable that option in Odin) and flash it again and then reboot. If you look at the ROM threads for anything newer than Android v5 they all recommend updating to the latest bootloader & modem for your device which in this case is PL1. This can be to prevent crashes/no signal /no SIM, etc...
Are you dirty flashing these ROMs? I have never experienced any crashes with any of the RRs on my phone but I always do a clean install and make sure to also delete the "Android" folder on my SD Card via TWRP after doing the "Advanced" wipe and deleting everything listed there except for the External SD Card.
Click to expand...
Click to collapse
"pull the battery and don't let it reboot the phone for it to stick (disable that option in Odin) and flash it again and then reboot"
So...
- Reboot phone into Download mode
- Pull battery while in Download mode
- Flash thingy
- Reboot back into Download mode
- Flash thingy again
? That will be very difficult to do with my dodgy charging cable that doesn't like being repositioned...
I do that without pulling the battery, but I could try it with.
I'm downloading the full SEPL stock image to flash. Once that's done, I'll flash it, reflash TWRP, restore my backup, and see if the baseband has updated.
And no, never dirty flashed the ROM. Always completely wiped data, system, cache and everything. I always backup first. I currently have 3 backups: Lineage OS (before installing RR), RR6 (Oreo), and RR7 (right now before that stock image I'm going to flash).
My external SD card is nonfunctional and read-only with some trash files from the previous phone.

I flashed the stock SEPL ROM. Baseband still didn't change. Restored from backup, SIM now works. Network is detected, SMS and data both work reliably on all reboots.
I will mention that I did brick my phone by using Odin to erase the eMMC, but I fixed that from TWRP, and now everything works flawlessly. There are still some app crashes, but most things are very stable. Camera2 API still nonexistent, which is sad because I got used to it on my old phone, but I shouldn't hope for it.

Android 10 GSI

Note: Make sure your phone is decrypted and do not turn on the secure boot feature where you need to put in your pattern to boot system!
So as I'm currently without a PC and can't restore the stock images I wanted to share the best method for using Android 10 I've found.
Get the latest phh gsi image v210 is what I used.
Get the latest Lineage OS GSI 17.1 image.
Get the Trinity v2 kernel (beta is what I used).
Get the latest Android 10 pico or nano gapps from opengapps. (I used nano)
Boot to recovery and factory reset.
Install phh gsi IMG to system. When finished don't reboot. (I do this to keep security patches as up to date as possible)
Install LineageOS IMG (DIRTY FLASH).
Install Trinity Kernel to Boot
Reboot system
(Optional once you fully boot you can reboot recovery and flash the f2fs zip from Arter Kernel then reboot recovery and wipe data. When you reboot system you may freeze during setup just reboot by holding the power in until the phone restarts. It will finish setup this time.)
Reboot recovery and flash gapps. If you get error 70 resize the system partition. It will work after resizing once or twice.
When it boots you can do your traditional setup.
Reboot recovery and Install Magisk v20.3.zip
Reboot system and Install Magisk Modules Busybox for Android NDK and Magisk Hide Props Config.
Install terminal app of choice following Reboot
Type su in terminal and hit enter
Type props in terminal and hit enter
Change the fingerprint to Razer Android v9 and Reboot following the prompts.
Congratulations you now have LineageOS Android 10 and are passing safetynet.
Notes:
You can Install v4a if you want.
I highly suggest installing the l'speed module from Magisk as it stabilizes the freezing/kernel.
You can also Install EdXposed and the beta for GravityBox Q ... Still passing safetynet.
Logo++ will fix your Razer logo on the rear of device.
Bluetooth works fine as does everything I've tested.
Downloads needed:
Latest phh GSI for AOSP Android 10
Latest LineageOS 17.x GSI Image
Trinity Kernel (v2)
Magisk v20.3
Pico or Nano GAPPS from OpenGapps
Optional:
V4A (requires the Magisk Module Audio Modification Library)
EdXposed Riru - Core (Magisk Module)
EdXposed - Sandhook Beta / Canary (Installed from manager)
EdXposed - Latest Manager (do not use Taichi)
GravityBoxQ Beta (gives you a lot of customization like the battery icon in statusbar)
Logo+
LSpeed Module for Magisk (lspeed-master.zip)
F2FS_FSTAB.zip from ArterKernel Thread
***Note*** this isn't flawless but when using the LSpeed Magisk Module it's very close**"
**"" LineageOS Freezes every now and then where the AOSP GSI doesn't but I can't get the AOSP to pass safetynet***

Screenshots
Note I changed the font to Comfortaa via Magisk Font Changer Module

SafetyNet

Magisk modules I personally use. Ignore older versions of the same module.

Change the fingerprint to Razer Android v9 and Reboot following the prompts.
Click to expand...
Click to collapse
Will game booster work in cortex app?

I'm on T-mobile, and with every 10 Gsi I've tried, I've installed the required ims.apk. Unfortunately, I can only send sms, not recieve. Do you not have this problem?

Can you receive text messages through LTE? I can't seem to get it to work on T-mobile.

Reznor7 said:
I'm on T-mobile, and with every 10 Gsi I've tried, I've installed the required ims.apk. Unfortunately, I can only send sms, not recieve. Do you not have this problem?
Click to expand...
Click to collapse
Try moving the ims.apk to /vendor/overlay and see if that works.

Generic123. said:
Can you receive text messages through LTE? I can't seem to get it to work on T-mobile.
Click to expand...
Click to collapse
Generic123. said:
Try moving the ims.apk to /vendor/overlay and see if that works.
Click to expand...
Click to collapse
I've re-imaged my phone too many times already, losing countless hours going back to stock when the GSI doesn't work. I'll let someone else give it a shot.

Reznor7 said:
I'm on T-mobile, and with every 10 Gsi I've tried, I've installed the required ims.apk. Unfortunately, I can only send sms, not recieve. Do you not have this problem?
Click to expand...
Click to collapse
Reznor7 said:
I've re-imaged my phone too many times already, losing countless hours going back to stock when the GSI doesn't work. I'll let someone else give it a shot.
Click to expand...
Click to collapse
No doubt I'm through with flashing back to stock countless times.....so over it
Wish I had more time and knew more about Android to bake us up a solid AOSP ROM for this phone. Great hardware to work with here and like I've said before I can't believe there is not one Dev in this community to pick this phone up as cheap as it is and get something going

JDBarlow said:
No doubt I'm through with flashing back to stock countless times.....so over it
Wish I had more time and knew more about Android to bake us up a solid AOSP ROM for this phone. Great hardware to work with here and like I've said before I can't believe there is not one Dev in this community to pick this phone up as cheap as it is and get something going
Click to expand...
Click to collapse
I feel like it's the nature of ROM developers sticking to the devices they have. They are currently developing for other phones, and don't want to have to move/develop for a new phone, nor do they have the time to develop for another phone. To be fair, we are not completely in the dark; f(x)THaxxorX seems to be working on patched versions of popular GSIs that are more suited for the hardware of the RP2:
f(x)THaxxorX said:
What my real plan is to make patch into the GSI Sources before Building it.. Those patches include voLTE fix and other features. Integrate APTX coming from Razer GSI system.img.. and many more..
Click to expand...
Click to collapse

Generic123. said:
I feel like it's the nature of ROM developers sticking to the devices they have. They are currently developing for other phones, and don't want to have to move/develop for a new phone, nor do they have the time to develop for another phone. To be fair, we are not completely in the dark; f(x)THaxxorX seems to be working on a patched version of popular GSIs that are more suited for the hardware of the RP2:
Click to expand...
Click to collapse
Oh nice!
I'll try to contain myself and be a little more patient
So true, I can just imagine the time spent to be a developer for so many devices that are out there!
Happy Valentine's Day

Ugh. I don't know why I keep trying. SMS doesn't work over LTE on TMobile using this method either. OP, your profile says you're on TMobile. Have you solved this problem somehow?

Reznor7 said:
Ugh. I don't know why I keep trying. SMS doesn't work over LTE on TMobile using this method either. OP, your profile says you're on TMobile. Have you solved this problem somehow?
Click to expand...
Click to collapse
Are you still trying to use a Q GSI? If you are willing to go back to a Pie-based GSI, installing ims.apk and moving the apk to "/vendor/overlay/" works every time for me.

Generic123. said:
Are you still trying to use a Q GSI? If you are willing to go back to a Pie-based GSI, installing ims.apk and moving the apk to "/vendor/overlay/" works every time for me.
Click to expand...
Click to collapse
From my experience, Pie ROMs have issues with the fingerprint scanner reliability, and media in a lot of games seems to have buffering issues as it frequently cuts out.

Reznor7 said:
From my experience, Pie ROMs have issues with the fingerprint scanner reliability, and media in a lot of games seems to have buffering issues as it frequently cuts out.
Click to expand...
Click to collapse
I have the same problems on ArrowOS(the fingerprint sensor problem is pretty rare. The speaker issue is really annoying, but it only happens at low volumes), but I guess it depends on how much you're willing to take. If you want to keep to use Q GSIs, our best option is just to wait for patched GSIs by f(x)THaxxorX that might be coming out at some point(Soon™).

Reznor7 said:
From my experience, Pie ROMs have issues with the fingerprint scanner reliability, and media in a lot of games seems to have buffering issues as it frequently cuts out.
Click to expand...
Click to collapse
I think the speaker itself might have issues as I even had this issue with Android 9 GSIs, from what I remember. At first I suspected buffer-related issues but after some testing it doesn't seem to be the only issue. Setting the media volume to at least 50% would allow most of the audio to get out of the speaker, but at max volume the speaker can be really loud (to the point that I feel the speaker could be potentially damaged) so I usually set it to at most 80% when I need to place the phone a bit far from where I am.
Also, I haven't gotten aptX working on Android 10 GSIs due to a strange null pointer dereference bug which would crash the entire Bluetooth stack. Only SBC works as intended. As I noticed that the author of gjf_bt Magisk module (which adds aptX libraries as well as SBC tweaks) recently blacklisted Android 10 and onwards, I think the issue might have more to do with the Android 10 system itself.

Hey! Can anyone confirm if LDAC is working on this? I have never rooted a phone before just doing it to enable LDAC. Also, does this OS support setting for Refresh rate?

I love Lineage OS 17, but I noticed that I don't receive text messages anymore. I could receive text messages when I first flashed it, and after a couple of hours, I could not. Then, I could send messages and I could send and receive calls. I could use data. I could not receive text messages. Is there a fix for this problem? I tried using Lineage 16, but I still could not receive text messages. I am back to stock, for the moment. Does anyone know how to fix this? I'm using AT&T service.

Lorelily said:
I love Lineage OS 17, but I noticed that I don't receive text messages anymore. I could receive text messages when I first flashed it, and after a couple of hours, I could not. Then, I could send messages and I could send and receive calls. I could use data. I could not receive text messages. Is there a fix for this problem? I tried using Lineage 16, but I still could not receive text messages. I am back to stock, for the moment. Does anyone know how to fix this? I'm using AT&T service.
Click to expand...
Click to collapse
It's a known issue, and unfortunately there is no reliable fix yet.

How to update LineageOS 17.1 microg to newer build?

I am running LineageOS 17.1 (ver. 0.2.11.202414 ) with microg on my oneplus 6T.
I am totally happy with it except that sometimes my nfc is not working on my yubikey but with this i can life.
My main problem i have with updates to newer builds. They are released every week and under settings->system->advanced->updater I can see the builds that i could download and install. Also the OS is reminding me that i should update to newer versions.
I did it once and I softbricked my phone and i dont understand why...
On the LOS guide the steps mentioned are these:
Open Settings, navigate to “System”, then “Updater”.
Click the Refresh Icon in the top right corner.
Choose which update you’d like and press “Download”.
When the download completes, click “Install”. Once the update process has finished, the device will display a “Reboot” button, you may need to go into the Updater menu in Settings, “System” to see it. This will reboot you into the updated system
This is for shore not working with my version and microg variant.
How should i proper update my OS to a newer build version?

Does nobody have a hint for me?

marsxxl said:
Does nobody have a hint for me?
Click to expand...
Click to collapse
Maybe try asking in the Lineage thread.

marsxxl said:
I am running LineageOS 17.1 (ver. 0.2.11.202414 ) with microg on my oneplus 6T.
Click to expand...
Click to collapse
The updater had issues originally. Although since you are using microg, you might have issues anyways. Now it would probably work if you were using a stock version of Lineage. Personally I still just use TWRP to update.
I have a guide here: Installing Lineage, it covers updating.
The only time I ran MicroG for any length of time was Omni, but it was still updated the same way.
You should be able to just flash the new build in recovery, flash the TWRP installer, reboot to recovery, flash Magisk if you use it, reboot to system. Since at this point, most modules will cause problems if flashed in TWRP.
I don't know how old your phone's firmware is, but there was a point in there LOS started checking for the updated firmware, so you maybe forced to update too. It should check before it flashes anyways. So just know if it errors out, you'll be updating everything. Be prepared to backup and clean install if you have to.

Thank you a lot @OhioYJ !
I was able to do the Update
If someone is interested in the NFC problem that I have, i will post it here:
https://forum.xda-developers.com/t/nfc-not-working.3945659/#post-84280433