Hi,
I am having issues with my dual SIM configuration on my Motorola moto one vision (motarola-kane) hw. xt1970-3
When I first installed and booted the device, everything worked fine for a few seconds, then I realized, that I couldn't do any phone calls or send SMS. In settings I have info about SIM1 and it is working no problem. SIM 2 on the other hand has "unknown" in all the places of where it should display info about sim card. Tried switching them around (thout maybe it is faulty slot), but the behavior is consistent. Only one card gets detected. I read about flashing the modem firmware, when people have had similar issued, but modem is working fine, because it works with one sim card. The issue remains after reboots, cold boots. Maybe I should add:everyting was working on the stock ROM. Is there anyone with similar issues? Thanks for Your feedback in advance.
Related
Hi everyone,
I recently bought the phone from T-Dimension and it's having some issues and I was wondering if anyone could help me out or if they've run into something similar. The issue is I can't seem to send/receive any calls and I can't send/receive any texts. The bizarre thing is it works for the first 45 seconds when I reboot but then locks me out straight after that. The phone is issued from Hong Kong and had Color OS on it but I flashed CyanogenMod onto it, here's some more information.
- The phone is connected to Amaysim, which runs of the Optus network I believe, so it's connected onto the mobile network just fine.
- The Micro-SIM card I'm using is brand new, it's put in correctly into the slot, meaning upside down facing towards the bottom of the phone, so that's fine.
- I've tested the SIM with other phones and it works perfectly fine.
- When it locks me after 45 seconds, it fluctuates from saying, "Call Not Sent" to just it being stuck on the dialling screen.
- After being locked out, I can't receive any calls either, I've tried calling the phone but nothing shows up.
- After being locked out, I can't receive any messages either, when I try to send a message it just stays stuck in sending, and if I restart the phone, it just says the text failed.
- I've contacted Amaysim Help Desk, and they say my problems lie with the phone being locked, and I'll have to contact the manufacturer to sort it out.
- I've also contacted my supplier, who seems to have trouble finding out the issue.
- APN settings are set correctly with my mobile carrier.
- Already done a factory reset, didn't fix the issue.
- Put the preferred network type to 3G under Mobile Network settings.
- I flashed CyanogenMod 11S using this tutorial from youtube, /watch?v=QDKOEtN9pbo and downloaded the cm-11.0-XNPH22R-bacon-signed.zip file.
Please can anyone help me with issue, sorry for long wall of text, I really want this phone to work!
Cheers,
You probably should flash another modem & then try.Here
http://forum.xda-developers.com/showthread.php?t=2824139
Sent from my One using XDA Premium 4 mobile app
LukaZilla said:
Hi everyone,
I recently bought the phone from T-Dimension and it's having some issues and I was wondering if anyone could help me out or if they've run into something similar. The issue is I can't seem to send/receive any calls and I can't send/receive any texts. The bizarre thing is it works for the first 45 seconds when I reboot but then locks me out straight after that. The phone is issued from Hong Kong and had Color OS on it but I flashed CyanogenMod onto it, here's some more information.
- The phone is connected to Amaysim, which runs of the Optus network I believe, so it's connected onto the mobile network just fine.
- The Micro-SIM card I'm using is brand new, it's put in correctly into the slot, meaning upside down facing towards the bottom of the phone, so that's fine.
- I've tested the SIM with other phones and it works perfectly fine.
- When it locks me after 45 seconds, it fluctuates from saying, "Call Not Sent" to just it being stuck on the dialling screen.
- After being locked out, I can't receive any calls either, I've tried calling the phone but nothing shows up.
- After being locked out, I can't receive any messages either, when I try to send a message it just stays stuck in sending, and if I restart the phone, it just says the text failed.
- I've contacted Amaysim Help Desk, and they say my problems lie with the phone being locked, and I'll have to contact the manufacturer to sort it out.
- I've also contacted my supplier, who seems to have trouble finding out the issue.
- APN settings are set correctly with my mobile carrier.
- Already done a factory reset, didn't fix the issue.
- Put the preferred network type to 3G under Mobile Network settings.
- I flashed CyanogenMod 11S using this tutorial from youtube, /watch?v=QDKOEtN9pbo and downloaded the cm-11.0-XNPH22R-bacon-signed.zip file.
Please can anyone help me with issue, sorry for long wall of text, I really want this phone to work!
Cheers,
Click to expand...
Click to collapse
Hey there fellow Aussie. See link provided by other member, it should fix you up.
Transmitted via Bacon
That modem actually proved to be worse for me.. Before I didnt have stable 3G connection.. that modem made my 4G connection worse too. The best, and most stable modem I have found thus far is in the latest nightlies. It is still very very very weak when it comes to 3G connectivity but its better than everything else I have tried. And believe me, I have tried pretty much every rom there is on this forum including XNPH22R, XNPH25R, MahdiRom, CyanHacker, and All the nightlys.
The only one I havent tried is Color OS because I am afraid it will lock my bootloader again.
It seems I have managed to solve it by myself. I have loaded factory image of 44S, preformed OTA upgrades and it seems the issue is gone.
The thread can be closed.
Hi, Last week I had my phone connected to power bank over night with "Sleep as Android" turned on. In the morning I got my wake up alert but I was unable to wake up my screen to turn it off... so I had to keep the power button down and shutdown the phone.
After that I have faced boot loop (phone worked fine previous evening).
I have tried rebooting phone couple of times but nothing worked so I have restored backup of last CM11s from TWRP (I was running on CM12 nightly during the crash). Phone booted up poperly and I thought everything is fine however after couple of hours I noticed my phone is asking me for my PIN so it has apparently rebooted. It appeared that it is rebooting every couple of hours and after every call (like 5 sec after call ended)...
I have tried restoring other backup but I was facing the same issue. I have done clean install of current CM12 nightly and got the same...
Facing that I decided to clean my phone completely... I have backed up all my data and did wipe and format of everything of everything I could from TWRP. Then via fastboot I have been tring loading YNG1TAS17L 64GB (from here) by flash-all.bat file. After loading bootloader I have received message <waiting for device> and my phone got hardbricked...
I managed to recover it using this guide.
Then I loaded TWRP again and installed COS 12.
On that point my phone started working stable but after a while I noticed that is started losing cell signal. Sometimes it was just for couple of seconds and sometimes it lost it for good (while tring to hardcode cell operator I was getting "error while searching for networks" and I was able to restore connectivity after couple of reboots).
I decided it could be radio/modem related so I have applied full firmware. No go. Loaded CM12 nightly - the same, loaded that modem from oxygen again - no go.
I have tried installing latest BlissPop, Mahdi ROMs and Oxygen and still facing the same issue.
Tested SIM card on other phone and it works fine, tested other SIM card on my OPO and still the same issue so it is phone related.
Getting the following in logcat during time phone is unable to connect to cell signal:
Code:
05-31 11:57:36.265 D/GsmDCT ( 2457): [0]isDataAllowed: not allowed due to - SIM not loaded and not NV subscription
05-31 11:57:36.265 D/GsmDCT ( 2457): [ApnContext:mms] getApnSetting: apnSetting=null
05-31 11:57:36.268 D/GsmDCT ( 2457): [0]isDataAllowed getRecordsLoaded=false
Anyone has any idea what could be a reason of this issue and how to fix it? At this moment everything is working fine except phone calls and Internet over network operator (Wifi works fine). Thanks in advance.
UP
Anyone has any idea? I believe I have narrowed the problem down a bit. It seems 2G/3G is affected only. As long as I'm in LTE range the connection is stable (that explains why I noticed the problem after few hours when I left home).
I have played a bit with hardcoding band and noticed that LTE is running stable (with GSM Signal Monitoring app). When switching to 3G it is dropping every couple of seconds. The strange thing is that 2G is sometimes affected and sometimes not... When switching LTE->2G it seems to be running pretty stable but when switching from 3G->2G it is acting the same way as 3G.
were you able to fix it?
I went through same experience except that I can barely connect to 4g, 3g 50% of time. Tried many radios but none worked.
spx2000 said:
were you able to fix it?
I went through same experience except that I can barely connect to 4g, 3g 50% of time. Tried many radios but none worked.
Click to expand...
Click to collapse
OP updated the post with how it was fixed. Sorry to bump the thread, but thought I'd inform spx that there was an update. Glad it worked out for you OP, I've saved this in case it ever happens to me, and good luck to spx. Hopefully someone puts this info in a sticky so others can try that if they are stuck too.
I fixed it by reflash raido of xnph52q found here. The zip contains more than the radio firmware.
http://forum.xda-developers.com/oneplus-one/development/rom-stock-rooted-xnph52q-t3025399
I flashed it before but it didn't work. The only difference is I used TWRP 2.8.6. I remember reading somewhere online that 2.8.7 has issue with OPO
artiwal said:
It seems I have managed to solve it by myself. I have loaded factory image of 44S, preformed OTA upgrades and it seems the issue is gone.
The thread can be closed.
Click to expand...
Click to collapse
Where is the 44S that OP used? I have something similar happening with my phone. I revived my phone from a hard brick and now it's not connecting to the cell network. Wifi works, IMEI shows when SIM is inserted, no EFS partition backup (I didn't know that was a thing to do until it was too late).
FWIW, my current build is KTU84Q and I'm running CM-11-20141008-SNAPSHOT-M11-bacon
This issue is driving me crazy.
For the past few months, every so often (semi-rarely), I would lose cell service and then the phone would say "No SIM" -- can't make calls, send SMS, etc. Then the problem would resolve itself on a reboot.
Last night, however, the "No SIM" issue happened and I couldn't resolve it on a reboot.
I've tried everything I can think of:
- Toggled airplane mode and every other easy OS setting I can think of
- Ejected and inserted the SIM card and cartridge multiple times
- Flashed a few different ROMs
- Flashed different modems/firmware multiple times
- Confirmed the IMEI is still intact
- Mucked around in the *#*#4636#*#* menu to no avail (after everything else failed)
I don't think it's a issue with the SIM card itself, as I already tried an older card I had; the problem persists. So I was wondering... is it possible the cellular radio has malfunctioned hardware-wise? Is this something that has happened to other users?
P. S. The Wi-Fi radio works fine, and I imagine Bluetooth does as well. It's just the cell radio that's problematic.
If there's a specific detail I forgot to mention, let me know and I will clarify. Thanks for reading.
FYI, I believe I fixed the problem. The solution was just maintenance/cleaning.
Pried off the back of the phone where the battery is for the first time; cleaned all the copper endpoints sticking out, as well as the antennae traces on the rear panel with alcohol. Stuck a piece of sticky paper on the back of the SIM caddie so it wouldn't move around in the slot so much.
That seems to have done it. Haven't experienced a "no SIM" message yet, but I'll post back here if it returns.
Since one week my Xperia Z5 Dual E6633 (running on a rooted Android OS 7.1.1) has some problems with the SIM-Cards.
If my phone uses one of the SIM-Cards, I have only access to the network for about 2 Minutes. After this, network connection is gone and the phone tries to access the network. After some time the LED flashes red and the phone reboots. But after that reboot, the phone still doesn't have any connection to the network. If I am switching on the Airplane-mode I can use WiFi without any issues. But if I switch off the airplane-mode, I do have the same problems as describet above. I also tried to "repair" the phone using Xperia Companion but it didn't work out for me. Still got the same problems.
I did not flash any data, didn't update the OS or something else. I tried to switch the SIM-Cards No.1 into tray 2 and No.2 in tray 1. Didn't help. Still get the same issues. Then I tried to just use one of the SIM-Cards. And I tried it in any way. Used SIM No.1 first in tray 1 then in tray 2. After this, I used SIM No.2 first in tray 1 then in tray 2. But nothing worked. Still had the same issues.
After nothing helped, I started from scrap, flashed a 32.4.A.1.54 FTF and rooted my phone again. After this, I tried everything again. But still no effort. My phone doesn't work with SIM Cards.
What can I do? Do you all think that this could still be a software-issue? If yes, what can I try to fix it?
THX for your help
Hey
Does anyone experience problems of phone having full signal and then dropping it.
The problem I'm experiencing is frequent dropout during calls and being unable to establish them afterwards.
I can send texts and use the internet one minute and the next the phone doesn't work and drops my calls as well as doesn't accept them.
I tried swapping SIMs, rebooting, flight mode, you name it. The phone starts working again after about five minutes.
Here is the error:
https://drive.google.com/file/d/1e6_D3RM6luCK_LWDQSmOq-gJmmxjQOd9/view?usp=sharing
I would really appreciate some help. I highly suspect that this started happening with one of the latest updates.
I'm on a vanilla 12.0.3 Global rom.
Cheers
DavidMarmon said:
Strange
Click to expand...
Click to collapse
Yup. I have it pinpointed to a software problem as the phone worked just fine until a couple of updates ago. I can't however work out what could cause it.
I'm currently trying toggling VoLTE and changing APN settings (APN had wrong settings but still worked). Maybe the combination of both could cause problem.
I have also found out that SMS and data connection works fine all the time. It's just the calling function that causes the problem. I can listen to Spotify all day and it will work but as soon as someone tries to call me the signal will drop and everything stops. When I call the same thing happens. The bars just drop to 0 and playback stops. It resumes right after and works fine as long as I don't try to call. If I do the same thing happens.
The issue resolves itself after 5-30 minutes or so and then everything works totally fine.
So yeah if I had a rooted phone I would definitely contribute this to faulty rom or a rogue app. But I don't have one so it should work fine.
I've managed to capture it on video (sorry for the shaky camera but it was hard to film using one hand):
https://www.youtube.com/watch?v=kxusuCwsiBc&t=2s
Reboots, flight mode, swapping SIM cards (using a brand new one), using a SIM in slot 1 or slot 2, heck both slots, VoLTE on or off... I have literally tried everything. Nothing changes. Placing the same card in my other phone is fine. The problem happens everywhere and not only in one place so it's not reception. Also it doesn't matter if I'm moving or not so it's not switching between towers.
Same prob
I have the same prob, and I also tried every thing even flashing lineage didn't help, did u manage to find solution????
fautsoops said:
I have the same prob, and I also tried every thing even flashing lineage didn't help, did u manage to find solution????
Click to expand...
Click to collapse
Sort off. I had to send it to a service center and they've returned my money as it was deemed irreparable.