Texts? Do mean SMS messages with stock app? What about 3rd party Android messages APK?. I tested this rom for less than hour and went back to xiaomi.eu
Anyone else is experiencing this? I searched this, but could not find anyone else with this issue...I'm surprised no one has yet realized that you can't receive texts on any of the GSIs.
Receiving texts only works for about a minute after a fresh boot and then stops working.
It works fine for me.Anyone else is experiencing this? I searched this, but could not find anyone else with this issue...
This rom is my daily driver in the last 2 weeks and i haven't notice this issue.Anyone else is experiencing this? I searched this, but could not find anyone else with this issue...
After dirty flash (data backup restore), one may need to use TWRP/Advanced/File manager to remove /data/user_de/0/com.android.providers.telephony/databases/mmssms.dbI'm surprised no one has yet realized that you can't receive texts on any of the GSIs.
Receiving texts only works for about a minute after a fresh boot and then stops working.
I just finished installing Havoc 2.0 and SMS works fine. VoLTE is not enabled. Cam2API is not getting enabled. Battery gets drained very fast.It works fine for me.
I know some roms has issues that make sending and receiving sms takes 6 minutes until it starts working.
On miui it has to do with volte being enabled.
On some treble roms it too takes long time but I can't remember in which combination.
I am using the havoc 2.0 and I sent a test sms to myself and it took only 2 seconds to receive and my uptime is 6 days and 22 hours
Never flashed Havoc. It may be a good idea to ask Havoc-related question in respective thread.I just finished installing Havoc 2.0 and SMS works fine. VoLTE is not enabled. Cam2API is not getting enabled. Battery gets drained very fast.
I had sound issue system-wide after playing with various magisk modules. Had to reflash xiaomi.eu and phh-treble from scratch to get rid of it.I am experiencing cracking sounds in SoundCloud app after flashing the fixes in OP. This issue didn't appear before I flashed the fixes. Are anyone facing the same issue?
Read here: (this is the current rom combination I'm using right now)I just finished installing Havoc 2.0 and SMS works fine. VoLTE is not enabled. Cam2API is not getting enabled. Battery gets drained very fast.
Hmm, I was sure that I didn't install any magisk module that altered the sound system.I had sound issue system-wide after playing with various magisk modules. Had to reflash xiaomi.eu and phh-treble from scratch to get rid of it.
Thank you Sir!Hmm, I was sure that I didn't install any magisk module that altered the sound system.
I flashed xiaomi.eu, then GSI, then the fixes. After using my phone for a while, I realized that I didn't mount /vendor when I was flashing your fixes, so I reflashed it with /vendor mounted.
Maybe it's just SoundCloud app's fault, I've done some search and found out many people also have this problem. I still have no idea why it was working before I flashed the fixes though.
By the way, thank you for your time on this tutorial and the fixes :good:
Did you have a chance to check if deleting /data/user_de/0/com.android.providers.telephony/databases/mmssms.db helps?All my text related tests have been done on clean flashed installs to ensure nothing else could get in the way.
I formatted all of /data... There is nothing there.Did you have a chance to check if deleting /data/user_de/0/com.android.providers.telephony/databases/mmssms.db helps?
Can you see correct smsc via *#*#4636#*#* menu?
Has anyone updated to this build?Build 109 released with January security patch
https://github.com/phhusson/treble_experimentations/releases/tag/v109
Yes. Any specific issue with it?Has anyone updated to this build?
Did you install Gapps or Magisk at first time?My Max 3 hangs after I flash the treble image. It sits on the boot screen for about 30 seconds, turns off and then repeats in a loop while never actually loading the treble rom. Was wondering if anyone was using the newer image to see if that maybe was the issue. But if you got it up and running then I must be doing something wrong.