Related
Phone is stock and not rooted.
This is extremely strange. I'm on Vodafone in the UK and I had installed the 7.0.1 update a few days ago. All was running fine.
Anyway, the Play Store issue had me confused, so instead of uninstalling updates, I decided to hard reset.
Did that and from that moment on the Sim card seems to have gone into a fit of turning itself off and on every 1-2 seconds.
I have reset a number of times and have now installed the 7.1.1 update, along with a hard reset and nothing has changed.
I have tried an EE Sim in the phone and this works fine. My voda sim I put in a Galaxy S 7 and that seemed fine too.
Yet when it is put back into my phone, it goes mad.
I only run one sim and have tried with SD Card in/out.
I am tempted to call it a faulty sim and go and get a new one, but thought I'd check here first.
Any experiences or ideas?
TIA
The plot thickens...a bit.
When I insert 2 vodafone sims, it works fine. Both sims are stable and I can make/receive calls as per normal.
As soon as I remove the one of the sims, it carries on as per usual constantly activating and deactivating sim.
Some more info...
Upon a hard reset the sim is stable and I can see data connection. I follow through the initial startup screen and skip as much as I can skip. Again, remains stable.
The last screen I get to is IZ location or something (can't remember) and asks whether you want to enable for h/w acceleration. I have tried this both on and off.
As soon as you click finish and it goes to the home screen for the first time, the sim immediately begins to fluctuate showing both signal bars empty, then one, then one with signal, then repeat.
Viewing from the dual sim settings page, you can see the sim activate, say it's vodafone, the disable as if it had been removed.
About as strange as it gets!!
Right, resolution in the hope that it helps someone else
After trying every conceivable way to sort this, it was time to downgrade.
Went back to B10 package from the German site:
http://www.ztemobile.de/support/downloads/?product_id=2100
Will install everything and upgrade to Nougat again...possibly!
Yep, just been through the exact same thing. I had to go back to b10, whatever you do don't factory reset in-between updates back to 7.1.1.
Don't do anything in fact, just upgrade.
I ended up losing my great battery life because of this, I wish I'd left alone.
Good luck.
Mike
Make sure you have OEM unlocking disabled in developer options. It was required to be on for the original sideoaded B10.
Sent from my ZTE A2017G using Tapatalk
Ranny99 said:
Make sure you have OEM unlocking disabled in developer options. It was required to be on for the original sideoaded B10.
Sent from my ZTE A2017G using Tapatalk
Click to expand...
Click to collapse
I was trying to look for discrepancies between the B10 6.0.1 and the 7.0.1 but there were too many.
I'm quite tentative about moving off MM to nougat after the shenanigans the other day.
I had a similar problem when I made the first upgrade to 7.0.
My primary (French Prixtel) SIM would turn on/off constantly - and was basically unusable... however a UK EE Sim was fine - when either run alone or in the 2nd SIM slot.
I tried my wife's Prixtel SIM in the A7 - it was fine ... tried my SIM in the wife's Honor 8 ... and it was fine ....!!
I tried downgrading back to MM B10 - my SIM still didn't work anymore - back to 7.0 .. the same.
Finally I reported my SIM to Prixtel as non-working - and they replaced it FoC ... and the new one works fine.... also after the recent upgrade to 7.1.1.
Looloup said:
I had a similar problem when I made the first upgrade to 7.0.
My primary (French Prixtel) SIM would turn on/off constantly - and was basically unusable... however a UK EE Sim was fine - when either run alone or in the 2nd SIM slot.
I tried my wife's Prixtel SIM in the A7 - it was fine ... tried my SIM in the wife's Honor 8 ... and it was fine ....!!
I tried downgrading back to MM B10 - my SIM still didn't work anymore - back to 7.0 .. the same.
Finally I reported my SIM to Prixtel as non-working - and they replaced it FoC ... and the new one works fine.... also after the recent upgrade to 7.1.1.
Click to expand...
Click to collapse
I tried multiple vodafone sims and had the same problem. Like you both Voda sims worked fine in other phones.
I would have gone the local Voda store, but they were...let's say 'challenging' to say the very least!
Good to know that other providers are affected too
You have this problem because you most likely have unlocked your bootloader. ZTE know about this problem, the only way to solve this is to go back to marshmallow, lock your bootloader then go back to the nougat build.
Hello!
I have trouble with my One plus 6 t receiving text messages. I receive them a day late, all coming through at the same time in a bulk of messages the next day. I changed my sim card so T mobile doesn't seem to be the cause of it. Are these problems because I rooted my phone? If so what is the solution? Thank you!
My 6T is also rooted and at one point I has service issues (on Verizon) I tried all my mods one at a time till I figured out witch mod caused it and I was shocked to find out it was my substratum themes messing with something. Once removed all was grand. Hope this help. Go one by one through any mods in place disabling them see if it helps.
666syco said:
My 6T is also rooted and at one point I has service issues (on Verizon) I tried all my mods one at a time till I figured out witch mod caused it and I was shocked to find out it was my substratum themes messing with something. Once removed all was grand. Hope this help. Go one by one through any mods in place disabling them see if it helps.
Click to expand...
Click to collapse
The problem is that I have a lot of apps...Did you disable them one by one? And also I realise that I receive the delayed messages 1 day after so it's not easy to check. So the problem comes from the fact that my phone is rooted? Also when I use the camera my phone closes sometimes, like 30 sec after...Very weird. Does all this come from the rooting? Never heard of this problem before.
Yes I did dilisabled one at a time and rebooted after each one. And for text delay who is your carrier I'm on Verizon and mine was delayed for a hour or so till I figured it out I'd quick text my self hi from my own number and hit home to close the messages app out so I could time the reply time.
This helped me also.
https://forum.xda-developers.com/on...st-cell-signal-to-max-force-ca-t3905939/page1
Are you using stock messenger or one from Play store?
Google messaging. I use the stock dialer and contacts I'd rather the Google but there all but the same better dark mode on the stock. Phone completely stock other then the unlocked bootloader and magisk 19.3
KaM1KaZ3 said:
Are you using stock messenger or one from Play store?
Click to expand...
Click to collapse
I am using Google messenger app yes. Can that be the problem?
Wijanyc said:
I am using Google messenger app yes. Can that be the problem?
Click to expand...
Click to collapse
I don't think so, I've been using Google messenger since I got this phone without issues whatsoever!
Wijanyc said:
I am using Google messenger app yes. Can that be the problem?
Click to expand...
Click to collapse
Try turning off battery Optimization See if that helps, Could be just a delay with your signal... Had that happen before, I had full signal but everything was delayed.
I have similar issue to receive delayed messages after the latest Open Beta 12. Stock message app on unrooted 6T.
Sent from my ONEPLUS 6T using Tapatalk
Hi guys, i get a similar problem after update my phone to renovate ice version, even my network was refreshing a lot.
I use t-mobile and i contact customer service and they did a reset network and also I'm back to stock rom and everything it's working perfectly.
So i say bye bye to magisk and twrp
alcoholer said:
Hi guys, i get a similar problem after update my phone to renovate ice version, even my network was refreshing a lot.
I use t-mobile and i contact customer service and they did a reset network and also I'm back to stock rom and everything it's working perfectly.
So i say bye bye to magisk and twrp
Click to expand...
Click to collapse
Hello,
So the problem comes from the fact my phone is rooted? Yesterday it was impossible to take a video correctly for example my phone was shutting of every 30 seconds, and the mobile phone network bar disappeared, then came back and so on, like if I was losing the network every 30 seconds. I'll try to do a video of this
Wijanyc said:
Hello,
So the problem comes from the fact my phone is rooted? Yesterday it was impossible to take a video correctly for example my phone was shutting of every 30 seconds, and the mobile phone network bar disappeared, then came back and so on, like if I was losing the network every 30 seconds. I'll try to do a video of this
Click to expand...
Click to collapse
This is not normal. I've been rooted for months and do not have these problems. There is something else wrong
Just being rooted wouldn't be the issue. Sometimes it's honestly as simple as resetting your network settings. As for camera issues have you modified your camera in any way, possibly added a magisk module or something that isn't compatible with our phones, outdated modules can sometimes cause issues as well. It's hard to pinpoint but rooting isn't the issue as these phones were designed for rooting. It's something else entirely. You said your on T-Mobile, was it branded T-Mobile? They like to put their own bloated apps on phones that could probably cause issues too. This is why I went straight to the actual company. You get more up to date and their warranties better than tmobiles. Without knowing what's on your phone I can just speculate. But no just rooting and unlocking bootloader isn't causing this issue
Frosthaxx said:
Just being rooted wouldn't be the issue. Sometimes it's honestly as simple as resetting your network settings. As for camera issues have you modified your camera in any way, possibly added a magisk module or something that isn't compatible with our phones, outdated modules can sometimes cause issues as well. It's hard to pinpoint but rooting isn't the issue as these phones were designed for rooting. It's something else entirely. You said your on T-Mobile, was it branded T-Mobile? They like to put their own bloated apps on phones that could probably cause issues too. This is why I went straight to the actual company. You get more up to date and their warranties better than tmobiles. Without knowing what's on your phone I can just speculate. But no just rooting and unlocking bootloader isn't causing this issue
Click to expand...
Click to collapse
I bought it from One plus directly, not T mobile. I resetted the network settings a lot of times and it still does the same thing. I noticed it happens more when several applications are opened, like when I watch a youtube video and do something at the same time. But even after closing youtube app and all my other apps, it does the same thing. On magisk I have: Busybox for Android, Energized protection, Google product sans, IOS 12.1 emoji, systemless hosts, viper4android, youtubevanced.
I've noticed that being on WiFi causes phone network issues (e.g., phone calls going straight to voicemail, text messages being delayed). This is with WiFi calling disabled, and a non-rooted phone. Really not sure what's going on here, especially because when it happens, my network signal is just fine. But if I disable WiFi, the delayed texts come in immediately. Super annoying.
This is on T-Mobile, latest beta (I think version 11).
adobrakic said:
I've noticed that being on WiFi causes phone network issues (e.g., phone calls going straight to voicemail, text messages being delayed). This is with WiFi calling disabled, and a non-rooted phone. Really not sure what's going on here, especially because when it happens, my network signal is just fine. But if I disable WiFi, the delayed texts come in immediately. Super annoying.
This is on T-Mobile, latest beta (I think version 11).
Click to expand...
Click to collapse
I do not see this wifi call option on my one plus 6t.
I have these options: "turn on Wi-Fi automatically" , "Smart Wi fi switcher", "scanning always available", nothing else
Wijanyc said:
I do not see this wifi call option on my one plus 6t.
I have these options: "turn on Wi-Fi automatically" , "Smart Wi fi switcher", "scanning always available", nothing else
Click to expand...
Click to collapse
It's in an overly annoying menu to find lol. Settings -> Wi-Fi and Internet -> SIM & Network -> SIM 1 (T-Mobile (for me)) -> then under Enhanced Communication you'll see "Wi-Fi Calling"
adobrakic said:
It's in an overly annoying menu to find lol. Settings -> Wi-Fi and Internet -> SIM & Network -> SIM 1 (T-Mobile (for me)) -> then under Enhanced Communication you'll see "Wi-Fi Calling"
Click to expand...
Click to collapse
Oh ok yes found it! All right I hope this is the solution, I let you know!
Wijanyc said:
Oh ok yes found it! All right I hope this is the solution, I let you know!
Click to expand...
Click to collapse
Nope, it still doesn't work. Also the youtubevanced app disappeared, I am not able to use it anymore, don't know what is happening with my phone
I have this issue where I cannot receive mms messages! Anyone else experience this or have a fix
had the same problem. My APN Settings were not correct. Check & fix these
I reset my APN Settings and have wiped storage / cache for all messaging apps. Anything else I can try?
OP6T on Verizon. I had no issues with texts until Android 10 beta. I did a clean install of the Stable release of Android 10 and still having the same issue receiving mms texts.
My OP6T on Verizon was working fine with Android 9 and Google Messages. I updated to Android 10 during the initial release (before the pause). After that nothing worked for MMS or group SMS until I did a full wipe and reinstall of everything. Now I can get MMS and group SMS, but only with the OnePlus Messages app. Every other messaging app fails to download messages.
I found a fix!
After getting no help from Google or OnePlus, I went back to Verizon and had them get me a brand new SIM card. I'm not sure what changed, the APN settings all look identical to my old one, but it fixed the issue. I can receive MMS on any apps now without any issues. (on 10.0.1 anyway)
Bandalo76 said:
I found a fix!
After getting no help from Google or OnePlus, I went back to Verizon and had them get me a brand new SIM card. I'm not sure what changed, the APN settings all look identical to my old one, but it fixed the issue. I can receive MMS on any apps now without any issues. (on 10.0.1 anyway)
Click to expand...
Click to collapse
Very interesting! I had thought about doing this but kept talking myself out of it.
Going to request a new one now!
THANK YOU! New SIM installed and everything is back to normal! So glad to have Google Messages back!
Glad it worked for you! I just wish I could figure out exactly what the problem was so OnePlus and Google could stop finger pointing at each other.
Well, updated to 10.3.0 this morning, and this issue has returned. Looks like it's back to the OnePlus messaging app.
New sim fixed it for me
Bandalo76 said:
Well, updated to 10.3.0 this morning, and this issue has returned. Looks like it's back to the OnePlus messaging app.
Click to expand...
Click to collapse
I updated to 10.3.0 and MMS stopped working for me as well. I went to Verizon, got a new sim and it started back working. I have a T-mobile converted to International.
emimbs said:
I updated to 10.3.0 and MMS stopped working for me as well. I went to Verizon, got a new sim and it started back working. I have a T-mobile converted to International.
Click to expand...
Click to collapse
I've already replaced this SIM once. I can't go buying a new SIM every time OnePlus updates their software. It bugs me that OnePlus and Google both just point fingers at each other over this problem.
Bandalo76 said:
I've already replaced this SIM once. I can't go buying a new SIM every time OnePlus updates their software. It bugs me that OnePlus and Google both just point fingers at each other over this problem.
Click to expand...
Click to collapse
I had this same issue and had done the same thing to get it working again (got a new SIM from Verizon). After this 10.3.0 update, it came back. I sent a message in to OnePlus yesterday and today I heard back. They asked if I could try clearing system cache. I did, then reinstalled Google Messages, and the issue seems to be resolved. I'm not sure if it's a permanent fix or not, but I'll keep testing it for the time being. I'm interested to see if the issue returns after the next OOS update in January, as clearing the system cache once a month is a workaround, not a fix.
If anyone else tries clearing the system cache, please let me know whether or not it works for you and I'll send on to OP. Here are the directions from the OP rep with a little clarification:
Power off the device
Press and hold volume down + volume up + power buttons
The device will boot into recovery mode or into Fast Boot mode
If it boots into Fast Boot, tap Recovery Mode or use the volume up/down buttons to scroll to Recovery Mode and use the power button to select
If a keyboard pops up, enter your device's PIN/password
Select language
Select Wipe data and cache > Wipe cache
Tap Yes when asked "Cache will be wiped, continue?"
Now Reboot system from "Reboot" option
mason-johnson said:
I had this same issue and had done the same thing to get it working again (got a new SIM from Verizon). After this 10.3.0 update, it came back. I sent a message in to OnePlus yesterday and today I heard back. They asked if I could try clearing system cache. I did, then reinstalled Google Messages, and the issue seems to be resolved. I'm not sure if it's a permanent fix or not, but I'll keep testing it for the time being. I'm interested to see if the issue returns after the next OOS update in January, as clearing the system cache once a month is a workaround, not a fix.
Click to expand...
Click to collapse
Unfortunately, this didn't fix my issue. Uninstalled Messages, rebooted, cleared the cache, rebooted again, then reinstalled Messages, and still can't receive MMS.
Works just fine with OnePlus' messaging app though.
I'm about done with this. A used Pixel 3 XL may be calling my name here soon.
Bandalo76 said:
Unfortunately, this didn't fix my issue. Uninstalled Messages, rebooted, cleared the cache, rebooted again, then reinstalled Messages, and still can't receive MMS.
Works just fine with OnePlus' messaging app though.
I'm about done with this. A used Pixel 3 XL may be calling my name here soon.
Click to expand...
Click to collapse
Just make sure it's a used pixel from google or you will be dealing with a locked bootloader. I myself just switched from a vzw pixel 3xl to the OnePlus 6t. At least I now have the option to try to fix any issues.
mason-johnson said:
I had this same issue and had done the same thing to get it working again (got a new SIM from Verizon). After this 10.3.0 update, it came back. I sent a message in to OnePlus yesterday and today I heard back. They asked if I could try clearing system cache. I did, then reinstalled Google Messages, and the issue seems to be resolved. I'm not sure if it's a permanent fix or not, but I'll keep testing it for the time being. I'm interested to see if the issue returns after the next OOS update in January, as clearing the system cache once a month is a workaround, not a fix.
If anyone else tries clearing the system cache, please let me know whether or not it works for you and I'll send on to OP. Here are the directions from the OP rep with a little clarification:
Power off the device
Press and hold volume down + volume up + power buttons
The device will boot into recovery mode or into Fast Boot mode
If it boots into Fast Boot, tap Recovery Mode or use the volume up/down buttons to scroll to Recovery Mode and use the power button to select
If a keyboard pops up, enter your device's PIN/password
Select language
Select Wipe data and cache > Wipe cache
Tap Yes when asked "Cache will be wiped, continue?"
Now Reboot system from "Reboot" option
Click to expand...
Click to collapse
No luck
Furious this update ****ed things up again. The last thing I want to do is fight the mall and a Verizon store for a new sim, but it appears I have no choice.
Same issues here too after the update to 10.3.0. Worked very well with Android 9. What changed??? I have tried all this as well as adding information for MMS to the APN settings where the MMS data was missing. Nothing has worked. I am headed to Verizon this afternoon to get a new SIM and try that. Both my wife's and my phones are in the same boat. No joy here! Good to know that I am far from the only one. I love my phone though, but annoyed at the lack of support for this so far.
mrmuhles said:
Same issues here too after the update to 10.3.0. Worked very well with Android 9. What changed??? I have tried all this as well as adding information for MMS to the APN settings where the MMS data was missing. Nothing has worked. I am headed to Verizon this afternoon to get a new SIM and try that. Both my wife's and my phones are in the same boat. No joy here! Good to know that I am far from the only one. I love my phone though, but annoyed at the lack of support for this so far.
Click to expand...
Click to collapse
Mine corrected the issue on its own. I'm not sure but messages from Google is working for me. I'm on TMO converted.
New sim and all is well again. Pathetic "fix" but thankfully they're free.
All of a suddennim not getting mms messages in OnePlus messaging app now..
Now what do I do
i fixed this on multiple 7 pros by editing apn from internet to internet.fi
fi because my carrier is finnish.
i myself dont have this issue on my 6t
Hello all,
I've been using my Axon 7 since 2016, and I'm still hapy with it. Recently, a weird bug has cropped up which I can't figure out. When I call some phone numbers, the phone doesn't ring at all. It goes straight to 'Call ended'. I've tried my SIM in another phone and it works just fine. So it seems to be the phone, not the provider. It happens to a select few phone numbers. The vast majority of phones I call are completely fine. LTE + data is completely untouched too.
About two years ago, I moved from stock to LOS 15. Today, I updated to crDroid 9 (from this forum). That did not solve the issue. I then updated the modem with the one from @raystef66 (v1.30B01), which didn't fix the issue either.
It's worth noting that these phone numbers still worked when I first moved to LOS. Only this year, a few months ago, problems started to arise.
Some info about my phone:
ZTE AXON 7 A2017G
Android 9/crDroid 5.12 w/ sec patch feb 2021, vendor sec patch july 2018
Baseband .2.0.1.c8-00024-....
Kernel 3.18.140-Baddar-RC1.2
How would I go about solving this issue?
Cheers,
Qopzeep
I found the solution. For other people in the future also struggling with this, this is how I solved it:
Go to Settings
Tap Network & Internet
Tap Mobile network
Toggle 'Enhanced 4G LTE Mode' off
After toggling it off, all numbers are reachable again. What a strange bug. Is this Android/crDroid or my provider?
Anyway, I hope this helps someone else.
Cheers,
Qopzeep
So the title pretty much states the problem. After the last update of MIUI 12, my Redmi Note 7 went crazy.
All of the calls that I get (incoming) are shown as "Unknown number" or "Anonymous". Even if I have that number saved in my address book, it just doesn't decode it.
Another problem which has risen with this update is calling without country prefix. Before this update I could enter number with local code (number 8) which would look like 8-6234567. Now if I dial number in such format, the call automatically ends without any further information. It doesn't even start to dial it, just cancels the call. I must specifically put in number with the country code so it looks like +370-6234567. This is very annoying and I should note that before the update this worked without any issues.
Things I've tried:
Flashing older version of MIUI (didn't help, tried 11.0.3 and MIUI 10). I guess something was changed deeper with this update.
Forcibly enabling VoLTE with special code *#*#86583#*#*. This helped with the number prefix issue, I can call using local prefix again, however issue of "Unknown number" on incoming calls still persist.
Clearing app cache, enabling all storage permissions on Contacts and dialer app didn't help as well
Perhaps anyone has had similar issues and found the solution?
A short Google search. Maybe it help
https://c.mi.com/thread-3208259-1-0.html
joke19 said:
A short Google search. Maybe it help
https://c.mi.com/thread-3208259-1-0.html
Click to expand...
Click to collapse
I have tried all of the following steps, sadly they didn't work. I think if it was such "top level" issue like app cache or some settings, fresh flash of an older version MIUI would have helped, but it didn't.
tauriuxx said:
I have tried all of the following steps, sadly they didn't work. I think if it was such "top level" issue like app cache or some settings, fresh flash of an older version MIUI would have helped, but it didn't.
Click to expand...
Click to collapse
Sorry, no idea. I use xiaomi.eu long time and never had this bug. With customers roms was it a bug by Google phone and contacts with permissions.
Alright so I have managed to solve this issue, although solution was very interesting. After tedious work of many re-flashes which didn't work, uninstalling apps and stuff I decided to test other SIM cards as the last resort, to make really sure that the phone has an issue.
After putting in another SIM, to my surprise everything worked perfectly. No issues with "Unknown caller", no problem with dialing numbers without country prefixes and so on.
This gave me clues that perhaps the phone itself isn't broken, but the SIM card is. I tested a few other SIM's just to be sure and all of them worked flawlessly. Therefore I just went to my provider and asked them to replace my SIM card. They did it in a few minutes and it was absolutely free.
And this worked. Now my phone works as it was working before. I've never faced such issue with SIM card and I still don't know if it was a coincidence or did the MIUI 12 update change something in the SIM firmware and it broke, because it was absolutely good before the update.
TLDR: I replaced my SIM card because apparently it was faulty (I know it is strange but that happens I guess).
Hi..All
I also got same problem after SIM change, actually I switched on the VoLTE in SIM setting.
the solution for me is (GO TO SETTING>SIM Card & mobile networks>select your prefered SIM>TURN OFF VoLTE) by doing this my problem has been solved.