It appears that a couple of people tried flashing the Pixel 2 XL system.img onto the Essential PH-1, and was able to boot it, and have (almost) everything working:
https://forum.xda-developers.com/es...ashed-img-pixel-2-xl-opm2-171026-006-t3805921
This didn't used to be the case when the PH-1 was on 8.0. The people there mentioned that they went directly from having official Essential 8.1 June firmware installed and just flashing the Pixel system.img. All it took from that point on was a data wipe and it (allegedly) booted (almost) flawlessly. Some folks there also mentioned that Pixel 2's Android P DP3 system.img booted successfully as well.
@phhusson thoughts?
It boots the same right after oreo or P. There is no mobile data, so no calls or text. I fixed the camera, which was the other bug. I tried flashing my phones vendor images and modem over top of this and it still doesnt fix it. Must be in the system some place. I may try to swap out some lib, or hw files. Then maybe look at the build prop
i have done thins as well...boots flawlessly but as stated, no service or wifi for me...how was the camera fixed?
BakedTator said:
i have done thins as well...boots flawlessly but as stated, no service or wifi for me...how was the camera fixed?
Click to expand...
Click to collapse
I kept a folder of all camera related lib files from our Android p stock, then after booting this, i just used trial and error till i got the camera working. I am certain i could replicate but until we fix the no service probs i stopped messing with it. Just wasnt worth it. I moved on to flashing as many treble gsi's as i could. They all work mostly except for play store issues.
it also works on the Leeco Pro 3 X7272/720
Everything works. Except for call sound
tsongming said:
it also works on the Leeco Pro 3 X7272/720
Everything works. Except for call sound
Click to expand...
Click to collapse
Flash Pixel2XL's A/B system.img to A-only LePro3 directly???
qqzwc said:
Flash Pixel2XL's A/B system.img to A-only LePro3 directly???
Click to expand...
Click to collapse
System A only
However, unless this file has been updated you are better off following the GSI instructions in my signature.
or here: https://forum.xda-developers.com/le...nstall-gsi-t3843142/post77636477#post77636477
Related
Which one do you guys recommend the most?
I'm on stock Oreo (soak 4) and I'm curious about PE.
What can you guys tell me about it?
Pixel Experience!! Because it gives you some pixel like features. And I've noticed that stock ROMs usually have problems with Root!! When I had rooted my device the camera had stopped working. I tried everything but the only way to get it to work was uninstalling magisk!
S4xk said:
Pixel Experience!! Because it gives you some pixel like features. And I've noticed that stock ROMs usually have problems with Root!! When I had rooted my device the camera had stopped working. I tried everything but the only way to get it to work was uninstalling magisk!
Click to expand...
Click to collapse
But how am I getting sure that don't ruin my IMEI or persist in the process of trying Pixel Experience?
eder5jga said:
But how am I getting sure that don't ruin my IMEI or persist in the process of trying Pixel Experience?
Click to expand...
Click to collapse
Just make sure you backup those partitions on TWRP preferably on an external drive for safekeeping. Or if you loose them there's a guide here on xda that allows you to restore it but you'll end up getting your internal storage wiped in the process. I'd rather advice you to backup system, data( if you want ), persist, efs, and maybe even oem (for when you use treble ROMs in future).
Fingerprint Scanner Null after Pie ROM Flash - Custom ROM won't fix. Stock Only
Ok, the story.... Moto G5+ retail, running 8.1 Oreo, Bootloader Unlocked, rooted using Magisk 16.7 and was able to backup my Stock Oreo ROM once rooted, or I'd be dead in the water.
So wanting to stay ahead, I tried my hand at RR v7's Pie version, which, after some troubleshooting, was able to install successfully; but I don't much care for the google bar and other hard-coded "pure android" features. Same thing with Pixel Exp. Not to mention that Pie disallows call recording among a few other things Google decided to stifle its customers with. Deal breaker. So - moving on...or back for that matter.
I proceeded to download RRv6, which is btw running nicely on a 2nd G5+, same GApps, installs perfect except - FingerPrint Reader is not acknowledged. Period. No Security settings, No RR Config to access it, Nada. No matter what ROM I flash outside of the StockROM I backed up, it won't recognize the fp reader upon boot up. Whether I clear Dalvik/Cache, All DATA, do a full Wipe, DATA WIPE, REPAIR, FORMAT, nothing allows me to install RR v6.0 or any other flavor, Oreo or Pie, even while trying a dirty flash over Stock Oreo on this Moto G5+. Tried with several SD Cards, downloading fresh zip files from RR. I even went so far as to image the working G5+, then copy into the 2nd G5's SN folder, and do a restore, just loops - even after repairing the partition. I managed to work around that, Restored the image, but still no FP recognized by the initial Google startup/setup. It's almost as if the phone's been "firmwared" or "tagged".
Any ideas what could be lingering from Android Pie that would survive a F2FS/exT Format? Because something updated some kind of firmware on the phone during a Pie ROM flash, that now won't let me go back to anything below Pie, with a working fingerprint reader. The only difference between the G5 that works and this one is the working one has never seen Android 9. And it's staying that way til we come up with a way to hack the google crap.
Any help would be - awesome to say the least.
Thanks for looking.
Hello,
The issue with fingerprint is that after flashing stock Oreo ROM it replaces some files related to fingerprint sensor.
Hence all the newer custom ROM builds use the Oreo firmware related files. Hence it worked on the Pie ROM.
RR v6 would be still using the old nougat firmware hence you need to flash a file for it work. Which will replace the fingerprint related files for Nougat Stock firmware:
https://androidfilehost.com/?fid=1322778262904029634
In case you want to revert the changes and use Pie ROMs:
https://androidfilehost.com/?fid=1322778262904029635
sharan.nyn said:
Hello,
The issue with fingerprint is that after flashing stock Oreo ROM it replaces some files related to fingerprint sensor.
Hence all the newer custom ROM builds use the Oreo firmware related files. Hence it worked on the Pie ROM.
RR v6 would be still using the old nougat firmware hence you need to flash a file for it work. Which will replace the fingerprint related files for Nougat Stock firmware:
https://androidfilehost.com/?fid=1322778262904029634
In case you want to revert the changes and use Pie ROMs:
https://androidfilehost.com/?fid=1322778262904029635
Click to expand...
Click to collapse
That would make sense if PHONE1 manifested the same thing. But I went from StockOreo to RRv6-Oreo w/out losing anything and having to flash any FP Firmware. I used the RRv6 Official from 18-0911. Which is what's been leading me to believe there's something awry with this 2nd G5. I wonder is it possible PHONE2 has some slight firmware variance that is simply ignoring during the RR flash? Anyway, I'll give this a shot. this is TWRP flash, not fastboot, yes? Just being clear as I'm not proficient at this just yet.
Thanks Sharan!
DJScribe said:
That would make sense if PHONE1 manifested the same thing. But I went from StockOreo to RRv6-Oreo w/out losing anything and having to flash any FP Firmware. I used the RRv6 Official from 18-0911. Which is what's been leading me to believe there's something awry with this 2nd G5. I wonder is it possible PHONE2 has some slight firmware variance that is simply ignoring during the RR flash? Anyway, I'll give this a shot. this is TWRP flash, not fastboot, yes? Just being clear as I'm not proficient at this just yet.
Thanks Sharan!
Click to expand...
Click to collapse
Yeah, give it a try. And yes it's to be flashed via TWRP.
[SOLVED]
sharan.nyn said:
Yeah, give it a try. And yes it's to be flashed via TWRP.
Click to expand...
Click to collapse
Sweet! I had to reflash from scratch as for some reason it wouldn't let me update the ROM already running. But once I re-flashed RRv6-8.1, then flashed FP, it's now back. You rock Sharyn - nice work!
Now if only we found a way to cleanup that Pie - hate the perpetual time stamp, search bar and inability to record voice. Which is why I'm staying on Oreo til further notice. I know it was Google who took it away on v9.
Thanks again Shar!
:good::victory:
DJScribe said:
Sweet! I had to reflash from scratch as for some reason it wouldn't let me update the ROM already running. But once I re-flashed RRv6-8.1, then flashed FP, it's now back. You rock Sharyn - nice work!
Now if only we found a way to cleanup that Pie - hate the perpetual time stamp, search bar and inability to record voice. Which is why I'm staying on Oreo til further notice. I know it was Google who took it away on v9.
Thanks again Shar!
:good::victory:
Click to expand...
Click to collapse
Crap - so turns out this solution was short-lived. FingerPrint Scanner is back to inactive and FPzip isn't fixing it. Only StockOreo brings it back. Tried a plethora of ROMs from Nougat to Oreo, nothing but Pie and stock Oreo. Symptoms say it's the ROM, but a ROM that is currently working on the 1st G5 won't work either. Still looking for solutions, anyone...
By no bad means I just wanted to express a funny discovery in just words... Its project Terrible
I never had issues with it but other custom rom users sometimes seem to misunderstand the way it works and then one must feel Terrible
@darfri I cannot figure out how to get sim recognized and lte working fine on a gsi on my pixel XL .
So far on GSIs on Android 9 and 10 everything works fine except data/lte and sim is unavailable unless you use a vendor image from the past and even then I have not been able to figure out exactly which vendor.img to use. I got data/lte working and sim recognized on some vendors but then I get system ui crashes that happen every few minutes.
Sent from my marlin using xda labs app
flash713 said:
@darfri I cannot figure out how to get sim recognized and lte working fine on a gsi on my pixel XL .
So far on GSIs on Android 9 and 10 everything works fine except data/lte and sim is unavailable unless you use a vendor image from the past and even then I have not been able to figure out exactly which vendor.img to use. I got data/lte working and sim recognized on some vendors but then I get system ui crashes that happen every few minutes.
Click to expand...
Click to collapse
I see you are dealing with image files, it makes me wonder - have you tried backing up all with Titanium and twrp, move results to external device, reflash stock os to both slots, format data partition? The backups are easy to gradually restore in Titanium. But you might want to try robustly restoring the data partition backup image to see if your issue might be gone and you can continue where you left off
Hello Friends
I have experimented with flex1911's camera and finaly succeded to make flashable zip of Huawei camera for Treble GSI roms.
Camera has only been tested on Havoc 2.9 ROM for now and everything is working.
Feel free to try it on other ROMs and report.
Installation:
Flash Treble Pie GSI (fastboot)
Flash TWRP recovery (fastboot)
Flash Camera (TWRP)
Big thanks to flex1911 and Phie, without their work this would not be possible.
Download:
https://mega.nz/#!U8InwYLS!K0zpjYdNSzC6iX8XkzUVvM0IG_dssfAagfowo1BudgI
Thanks for the zip:good:
aand since you also got a P9 running havoc 2.9 gsi, may I ask you whether bmgr backupmanager works for you, if you can access all apps in play store (ie whatsapp) or pass safetynet with any Magisk version higher than 19.3? That are the remaining issues I have using this rom, aside from wifi hotspot and network signal indication.
I've seen this thread from @Hami_Do over at the P10 lite forums and thought maybe we can do something similar and collect fixes for hi3650 specific issues on gsi roms.
https://forum.xda-developers.com/p10-lite/how-to/gsis-manual-fixes-hi6250-devices-t3936745
What totally works on the P9 as well is their offline charging animation fix.
And what also makes quite a difference is the 'Hwcomposer' fix, which basically brings stock-like smoothness and screen quality on gsi, and even seems to save some battery.
I doubt their zip works on hi3650 devices but I've collected the files from vendor and the trick does work on our devices too, but it's not yet flashable. Maybe you want to help.
BlurryUi workaround in phh treble app needs to be checked (debug.hwui.profile=true) and disable hw-overlays in developer option toogled few times to get it started.
lo_ol said:
Thanks for the zip:good:
aand since you also got a P9 running havoc 2.9 gsi, may I ask you whether bmgr backupmanager works for you, if you can access all apps in play store (ie whatsapp) or pass safetynet with any Magisk version higher than 19.3? That are the remaining issues I have using this rom, aside from wifi hotspot and network signal indication.
I've seen this thread from @Hami_Do over at the P10 lite forums and thought maybe we can do something similar and collect fixes for hi3650 specific issues on gsi roms.
https://forum.xda-developers.com/p10-lite/how-to/gsis-manual-fixes-hi6250-devices-t3936745
What totally works on the P9 as well is their offline charging animation fix.
And what also makes quite a difference is the 'Hwcomposer' fix, which basically brings stock-like smoothness and screen quality on gsi, and even seems to save some battery.
I doubt their zip works on hi3650 devices but I've collected the files from vendor and the trick does work on our devices too, but it's not yet flashable. Maybe you want to help.
BlurryUi workaround in phh treble app needs to be checked (debug.hwui.profile=true) and disable hw-overlays in developer option toogled few times to get it started.
Click to expand...
Click to collapse
I have not tried backup manager. Whatsapp is not in play store. Not passing safetynet, and Magisk is version 20.1.
For those fixes i think it would be best to ask guys on original thread can we use their stuff as a base and than start making those fixes one by one.
I have not really tried to fix all that stuff couse this is my backup phone. We can try for sure.
So for a start I came up with a quick& dirty playstore fix.
Booted emui, compared its reported features and plainly copied everything over that was missing from havoc report. Result is attached. Copy to /system/etc/sysconfig chmod 644, clear playstore data and reboot. All apps will appear. Also no fc anymore when trying to access nfc/bluetooth settings from menu. Backup manager still fails though
Also found an app in Playstore that can show the real network signal values on gsi despite the OS failure. Network Cell Info Lite https://play.google.com/store/apps/details?id=com.wilysis.cellinfolite&hl=de
Maybe we can debug and look what it does differently from @phhusson implementation to fix it
[
lo_ol said:
Thanks for the zip:good:
aand since you also got a P9 running havoc 2.9 gsi, may I ask you whether bmgr backupmanager works for you, if you can access all apps in play store (ie whatsapp) or pass safetynet with any Magisk version higher than 19.3? That are the remaining issues I have using this rom, aside from wifi hotspot and network signal indication.
I've seen this thread from @Hami_Do over at the P10 lite forums and thought maybe we can do something similar and collect fixes for hi3650 specific issues on gsi roms.
https://forum.xda-developers.com/p10-lite/how-to/gsis-manual-fixes-hi6250-devices-t3936745
What totally works on the P9 as well is their offline charging animation fix.
And what also makes quite a difference is the 'Hwcomposer' fix, which basically brings stock-like smoothness and screen quality on gsi, and even seems to save some battery.
I doubt their zip works on hi3650 devices but I've collected the files from vendor and the trick does work on our devices too, but it's not yet flashable. Maybe you want to help.
BlurryUi workaround in phh treble app needs to be checked (debug.hwui.profile=true) and disable hw-overlays in developer option toogled few times to get it started.
Click to expand...
Click to collapse
TNX BRO for your great work
but can you explain more ? how to this?
HTML:
phh treble app needs to be checked (debug.hwui.profile=true)
and this attachment file just flash frm twrp and done?
Phh treble app is in settings menu, on any phh based gsi rom I guess. Just scroll down a bit? Checking the option just sets the property. You can also add the line to build.prop or use an init script as well. It's not a flashable zip, files need to get copied over either via adb or root explorer. A good app to notice the difference is cpu-z. If it's text is always sharp like in the screenshot, it's working and if it comes up blurry, it's not
Thanks for the zip for gsi.
@lo_ol on gsi phh app no choice that !
What copy exactly to fix blurry ? Can explain more and simply , thanks ^_^
edint3000 said:
Hello Friends
I have experimented with flex1911's camera and finaly succeded to make flashable zip of Huawei camera for Treble GSI roms.
Camera has only been tested on Havoc 2.9 ROM for now and everything is working.
Feel free to try it on other ROMs and report.
Installation:
Flash Treble Pie GSI (fastboot)
Flash TWRP recovery (fastboot)
Flash Camera (TWRP)
Big thanks to flex1911 and Phie, without their work this would not be possible.
Download:
https://mega.nz/#!U8InwYLS!K0zpjYdNSzC6iX8XkzUVvM0IG_dssfAagfowo1BudgI
Click to expand...
Click to collapse
anyone tryed this on android 10 gsi?
reynard1 said:
anyone tryed this on android 10 gsi?
Click to expand...
Click to collapse
I tried to boot Havoc 3.0 but it bootlooped. So no.
edint3000 said:
I tried to boot Havoc 3.0 but it bootlooped. So no.
Click to expand...
Click to collapse
expressluke roms bootloop on p9 ,idk why but im working on it
you can use phh version
Is there any camera fix for aosp 10?
photos can't be saved to SD, it says that the SDCard is ful when it runs on HAVOS 2.9
Anyone got this working for android 10 phh-based roms?
shyvanna said:
Anyone got this working for android 10 phh-based roms?
Click to expand...
Click to collapse
I'd like to know too
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.