At&t on a3000 issue - OnePlus 3 Questions & Answers

I've been having issues with calling, such as when I go to call someone, sometimes they can't hear me, but I can hear them, and other times, I can't hear them but they can hear me. I notice I switch from lte or lte+ to h or h+, mostly h+. Could that be the problem? Could it be not selecting the right wcdma or umts band? Im at a loss to solve this problem. I've tried changing and modifying apns and preferred bands, in the hidden menu and in the sim card menu. I've also tried both stock and custom roms. Anyone else have this issue? I'm currently using rr remix nougat rom.
EDIT: I found out something interesting. I tried throwing my phone in 3g and making a call and it worked with no problem, surprisingly it didn't freeze the phone dialer. Will do more tests.
EDIT 2: OK, after attempt after attempt, I completely wiped the phone, like formatted EVERYTHING, multiple times/changed file systems back and fourth, then adb side loaded oxygen os with stock recovery. And after the phone booted, I noticed a sound issue, but I flashed a stock audio zip. Then.... Walla no issues, radio is more smooth, calls now work when received or made, the switch from lte or lte+ to h or h+ is now smooth asf. I will post again if to have problems.

i experience the same thing, it changing to h+ is normal b/c att does not have LTE over voice, so it will automatically goto h+ when making a call. It could be a number of things, it could be ur coverage location or it could just be a bug in the phone or just att, I work at att so i know its not perfect, i always seemed to have more issues with custom roms though

I haven't noticed it being better or worse on stock or custom roms, thanks for your imput though.

Something to try would be to get a prepaid sim from another carrier and drop it into sim 2. Do some test calls from the alt carrier and see if the same problem exists. If it does then it's possibly a hardware issue. If the issue seems to to clear up on the alt carrier then it's possibly AT&T.

I've heard others say its at&t, and even the store people said its a known issue with the one plus 3 and other unlocked phones

Related

can't make or place calls, but SMS and data is fine

Hi all,
My problem is that my Galaxy S3 (i747M) cannot make or receive phone calls*, but I can send or receive most SMS**, and my LTE data is fine***. I've tested to ensure it's not my account with Rogers, or my SIM card. I took my SIM card and put it in two other phones, and both worked just fine (one Rogers, one Telus). Putting their SIMs into my phone and the same problem as with my own SIM in my phone. I have unlocked my S3 using the 4.2 trick, but I didn't have this problem back then. I'm assuming this isn't causing me issues now.
I used asterisks because each of the above has some additional details:
* I cannot reliably make and receive phone calls. For example, I can try calling the same phone number (home) 10 times, and it may only go out once. From my home phone I can try calling my cell phone 25 times and only get through once. Every time my calls out fail, it either sits at "Dialing..." for 30 seconds before ending in "Call Ended 0:00" or just immediately drops the call without the 30 seconds of "Dialing...".
** Most of the time I can send and receive SMS from any other cell phone. Occasionally a message won't send out even though I have 4/5 signal bars. Resending the message works. Not sure if this is related to my issues with calling.
*** LTE data is fine (using LTE APN). Switching away from LTE to just 4G/H+ and data is a bit spotty. Sometimes it connects, sometimes it doesn't. LTE always connects just fine.
I've tried all sorts of flashing and reflashing:
- problem started when I was on S3Rx 4.0, but I never thought much of it because most calls went through fine
- problem got worse when I was on Lollipop (CyanideL), progressively so
- used Odin to flash stock NF2 (downloaded from Sammobile site), was no different than when I was on Lollipop (CyanideL)
- used Kies to flash stock N__ (forgot exactly which one), still no different
- flashed different bootloaders and modems
- while in stock NF2 firmware, went into *#2263# and made sure it was set to Automatic.
So any ideas what problem this is? I just find it extremely odd that calls almost always fail, yet SMS and data aren't a problem. Of course, when my SIM is in another phone (Nexus 5 on Telus, Galaxy S5 on Rogers) I was able to do everything without any problems: calls, SMS, and data.
Thoughts as to what this could be? Is this a hardware issue? If it's software, what could it be? My warranty's out and I'm willing to flash anything or pop the phone open (already have to make sure antenna isn't disco'd).
Thanks!
Have you tried the fob1 firmware? It's the latest kk release for the Canadian s3.
Yup, that's the firmware I'm currently on. Downloaded it from SamMobile, flashed via Odin. I'm literally running the stock firmware right now, no root, only TWRP as recovery so I can more easily flash any modems or bootloaders (vs using fastboot).
OK, so further to this issue, I contacted Rogers technical support. Spent about half an hour on the phone with the tech, went through a few things:
1. He reset my voice account, didn't help
2. Had me search in the "Network Operators" list, no networks ever show up
3. Had me use my old phone (Nexus S, network unlocked) to ensure that it's not my account. All tests with the Nexus S went fine.
4. Had me test different network bands. Bingo!
The phone can place and receive calls when I set the network mode to 2G only (or GSM only). 3 out of 3 calls came in, 3 out of 3 calls went out. Then again later we tested incoming and outgoing calls, still on the 2G network.
So technically problem solved, but realistically not really. I am able to get voice, text, and data (solved!), but I'm paying for a LTE data package and should at least be getting 3G mad.
Any idea why my phone would be working on the 2G network and not on the other ones (3G, H+, LTE)?
This is crazy but the baseband and modem are one fob1? I know you said you flashed a stock rom but it may be worth checking.
My niece is using an unlocked bell s3 on Rogers and she has no problem with voice, data, or text when setting the network to wcdma only or wcdma/LTE.
Yes! Both Baseband (modem) and bootloader are the same. I just downloaded Phone Info (Samsung) to check this, and they both report being FOB1.
Now here's something that's irking me quite a bit. I only just discovered this and do not know if it is of consequence to my problem: I have no PDA or CSC version and Latest Firmware is reporting "Not Found" in the Firmware tab of Phone Info. I've attached a screenshot so you can all see what I mean. Is that normal?
Is phone running a custom rom?
That's right, I just restored a NANdroid of CyanideL (5.1.1).
So this also happens on a stock fob1 rom too?
I am almost tempted to say it may be a hardware issue.
That's right. This happens with a custom ROM (e.g. CyanideL, 5.1.1) as well as a stock ROM that's been freshly flashed via Odin (FOB1, 4.4.2). When flashing with Odin, I'm doing a full wipe via TWRP. Wiping /data partition as well.
I'm inclined to believe this is also a hardware issue, but it just seems bass ackwards in that I can get everything (minus LTE) working while on 2G, but I lose voice access if I move up beyond 2G. I could understand if I couldn't get any voice, SMS, or data, but that going down to 2G solves all my problems... it just seems weird!
Can you try the phone on another carrier? This would probably be the final test you could do. Sounds like you have tried everything.
Yup, tried that earlier on, when I tested my SIM card in some friends' phones (one on Rogers, one on Telus), and while doing that also tested their SIM cards in my phone. With their SIM cards in my phone, the same problem happens as when I'm using my own SIM card.
Gah! It's frustrating, but something I can live with for now until I can get a new phone. I just still can't get over the "everything's fine" on 2G, but moving up to 3G or beyond and I completely lose voice. A colleague of mine has the same phone and the same plan, bought only a month or two before I bought mine. He's got no problems at all with LTE and voice. Although he was on the unofficial CM 12.1 nightlies (5.1.1), I don't think that would have any perceivable difference than when I was on CyanideL 15.x (also 5.1.1).

Can't place or receive calls; LTE data and SMS works fine

Hey guys, just unwrapped my new N5x and popped in my sim card. Yet for some reason I can't make or receive any calls!
Calls to me go straight to voicemail, and when making an outgoing call it either immediately says call ended or after a while says network unavailable.
The strange thing is that the entire time I'm connected to LTE (full bars) and data works fine (I can use chrome), and I can even send and receive SMS!
It's been like this straight out of the box. I reset the network settings, then factory reset the device, then upgraded to 6.0.1, rinsed and repeated with no luck.
Probably related: I tried setting the phone from LTE preferred to 3G or 2G but it still says connected to LTE. Even did it manually from the *#*#4636#*#* and nothing changed.
I'm using HOT Mobile in Israel and the American version of the phone. All bands are here are supported.
Any thoughts on how to proceed?
Do US specifc models of phones normally work fine in Israel?
I know I had these symptoms when I managed to accidentally swap my UK model to use USA bands. Only potential difference is that I don't think SMS worked for me.
If someone more knowledgeable knows where the "Network settings reset" pulls values from and to, that might help.
Or which partition holds the data that makes a US phone a US version and an EU phone an EU version (assuming it isn't hardware), we could potentially flash stuff.
Yeah they do. I have a friend with a 5x and his phone is working fine. :/
Check your apn settings, re add them again to test.
Maybe your network do not support lte calls, try it on 3g. This was my solution even thought my network supported volte and worked on s6 but not on my 5x.
I see you tried the 3g option, my problem was another app causing the conflict between lte and 3g. Able to source for another spare sim to try?
I deleted the apn settings - no luck. tried 2 different service providers and same results with both
I havnt installed anything yet and wiped the phone to be sure. Could a stock app be causing the conflict? How can I check?
did you try having your friend put his sim in your phone and yours in his to see if it works?
Yep - he's on the same service provider that I am. Didn't work. Also tried a Sim card from a different service provider.
Here is a solution if you still need it http://forum.xda-developers.com/showpost.php?p=64023143&postcount=10

Help improve Verizon compatibility

The OP3 does work on Verizon, however there are some "issues" that can probably be easily fixed by someone who knows what they're doing (aka not me).
So far I can confirm 1X/3G (eHRPD) works. I have to enable data roaming for data to work, but I can make/receive calls, sms, mms, and cellular data.
I've also been able to force a connection to LTE by placing the phone into "LTE Only mode". However, when I do this sms, mms and calls don't work (only data works).
For some reason the phone defaults to 3G rather than 4G even though it can use both.
3G/4G data, sms, mms and calling are working, they just aren't working together.
I have done a lot of testing on ,apns and build.prop edits but I have not made any progress.
My personal theory is that the phone is defaulting to a US Cellular APN which then attaches to Verizon's network as a roaming partner.
I really need some help from the community to get this thing working right. Any help would be much appreciated.
I just wanted chime in and say I'm also on VZW and considering picking up an OP3. From reading your other thread, as long as I have XLTE/Band 4, I should be able to at least get some use out of the phone, correct?
The idea of unlocking Band 13 sounds like a fun challenge I'm willing to try!
@notjaykay I tried to unlock b13 but the nvram would reset after boot. Here's the link http://forum.xda-developers.com/showthread.php?p=67648238
I haven't tried to get LTE working, but I've been using Verizon on my OP3 for a week now. Most of the time I use Verizon only for SMS, MMS, and calling, but on several occasions when I don't have T-Mobile LTE signal, I switch to Verizon SIM for data, too. I only get 3G in this case, but it does work pretty well (albeit slow, at 3G speeds). I'm also interested in somehow getting the phone to play nicely with Verizon's LTE.
What about "telephony.lteOnCdmaDevice=1"
In build. Prop
george241312 said:
What about "telephony.lteOnCdmaDevice=1"
In build. Prop
Click to expand...
Click to collapse
I just made this change but I don't get Verizon LTE signal at my house, so I'll have to wait until I'm at work tomorrow to actually test it.
That build.prop edit will not get you LTE. I suggest using this app https://goo.gl/620Kc7 and setting it to "LTE Only". You may have to toggle the "turn radio off" option. Be patient and it will work. What you will find is that when in LTE only mode you will only get LTE data. I do all my calls and SMS/MMS using my Google voice number so I don't need traditional voice/sms services. However this is the point of this thread. For some reason the op3 defaults to ehrpd (3G) rather than LTE. Until volte gets working (doubt that will be anytime soon) we will reply on CSFB (circuit switch fallback) for voice and text. Not ideal but a lot better than what we have now.
I did find this folder with a .mbn file in the OSS firmware folder which shows volte config specifically for Verizon (check the attached screenshot)
Thanks for the info, @cdkg. I wasn't optimistic about the build.prop change having an effect, but it was an easy enough thing to try just in case. Unfortunately, in my case, LTE-only is out of the question, at least for now. I'm leaning toward porting my number to T-Mobile to give them a real try for a couple months anyway. However, if this whole compatibility with Verizon <=> OP3 thing ever gets totally worked out, I'd probably come back to Verizon.

Verizon branded M8 on T-Mobile

Hello and thanks for reading,
I'm currently a T-Mobile subscriber, but I'm using an unlocked Verizon HTC One M8.
The phone is currently rooted has S-Off and Super CID.
The problem I have is that my data connection seems to constantly drop randomly.
Whether I'm on a call, sending or receiving group messages / MMS, or simply browsing the web.
I have to switch on airplane mode at least 20+ times a day to obtain a data signal.
My cellular network type is consistently on EDGE.
I CANT SEEM TO GET ANY 4G OR LTE.
Can someone point me in the correct path to fix the issue.
I used to have this issue, until I activated T-Mobile bands that are originally deactivated by Verizon from the factory. Maybe this was a huge coincidence, but I had the exact same problems until I did this. Also flashed LolliGPE at this time.
You can use CDMA tool to achieve this. There are numerous guides on how to do this on XDA, feel free to send a PM if you need more explanation or w/e.
Also, it wouldn't hurt to factory reset from stock recovery to correct any potentially corrupted NV items.
What I've found work good is install custom rom like viper one then enter your T-Mobile mms settings then use the app called 4g switch n click the drop down n select WCDMA n should be getting a constant four bar
Sorry for such a late reply, I am currently using ViperROM and still have troubles.
I've flashed several different roms all were affected, I've tried numerous firmware and radio's none have worked.
I'm not sure how to block CDMA network keys from functioning, care to elaborate a bit?

Occasionally unable to receive or make calls on XZ2c

Hi!
I am occasionally unable to receive or make calls on my XZ2c. Specifically, sometimes (say, every few days) people report to me I cannot be contacted although I am in a place where I have good reception. And, in such cases, if I try to make a phone call myself, I cannot. Even more specifically, the caller in these cases hears no ringing and no typical carrier voice message that my phone is off or that I cannot be contacted for the moment; while, when I try to call, nothing happens for a few seconds and then the phone app stops stops trying.
A restart always solves the problem.
Also, it may be the case - but I am not sure - that this happens after the phone has briefly lost reception (for example, in my office, because I exit the elevator, or in my home, as I have a blind spot in the courtyard). This seems to me to be the case based on a few observations but, again, I am not sure about it.
Otherwise, the phone works impeccably, but since I missed a few crucial calls recently this has started to bug me. (Needless to say, my two mostly retired phones, the XZ1c and the OG Pixel, do not have this problem when used in the same environments.)
Any suggestions, please?
I have the same issue - and reboot suddenly resolves it. I've tried to ask over Sony forums, but no reply yet. It bugs me also, but it would be quite hard to report it to Sony service center, as I cannot reproduce the issue myself. (although I think they are aware of the issue) It's a bit strange that my XZ2C has reception problems where my Z5C used to work...
landsome said:
Hi!
I am occasionally unable to receive or make calls on my XZ2c. Specifically, sometimes (say, every few days) people report to me I cannot be contacted although I am in a place where I have good reception. And, in such cases, if I try to make a phone call myself, I cannot. Even more specifically, the caller in these cases hears no ringing and no typical carrier voice message that my phone is off or that I cannot be contacted for the moment; while, when I try to call, nothing happens for a few seconds and then the phone app stops stops trying.
A restart always solves the problem.
Also, it may be the case - but I am not sure - that this happens after the phone has briefly lost reception (for example, in my office, because I exit the elevator, or in my home, as I have a blind spot in the courtyard). This seems to me to be the case based on a few observations but, again, I am not sure about it.
Otherwise, the phone works impeccably, but since I missed a few crucial calls recently this has started to bug me. (Needless to say, my two mostly retired phones, the XZ1c and the OG Pixel, do not have this problem when used in the same environments.)
Any suggestions, please?
Click to expand...
Click to collapse
It would help if you would report what carrier you guys are suffering the problem on and whether volte is enabled and if you have tried more toggle options of which networks to fall back on to make sure you receive calls, there is a way to manually set it to fall back all the way to GPRS 1.5 G manually haha my carrier supports that and i was once deep in the forest and still recieved a 1g call haha. It is not enough coverage on weak signal for 2g or edge calls.
In some cases inside big city where they ONLY have either LTE or WCDMA ON THE NETWORK, then YOU MUST either force it to use LTE only, or wcdma only. That way it does not jump back and forth and miss call. Some big cities i set it to lte only and even in basement or in skyscraper it is always full bars. So it just depends which tower types are in your home area.
ehBrY said:
It would help if you would report what carrier you guys are suffering the problem on and whether volte is enabled and if you have tried more toggle options of which networks to fall back on to make sure you receive calls, there is a way to manually set it to fall back all the way to GPRS 1.5 G manually haha my carrier supports that and i was once deep in the forest and still recieved a 1g call haha. It is not enough coverage on weak signal for 2g or edge calls.
In some cases inside big city where they ONLY have either LTE or WCDMA ON THE NETWORK, then YOU MUST either force it to use LTE only, or wcdma only. That way it does not jump back and forth and miss call. Some big cities i set it to lte only and even in basement or in skyscraper it is always full bars. So it just depends which tower types are in your home area.
Click to expand...
Click to collapse
It's Telenor Hungary, no VoLTE or other "magic" involved. There was a previous thread, which discussed the same issue. Actually I posted it to talk.sonymobile.com also, but please see the attached screenshot - it shows the actual issue. Telenor Hungary shows up as "emergency calls only", while Telekom HU and Vodafone HU seems to be fine. Sometimes switching airplane mode on/off solves the issue, sometimes it's a reboot which makes me able to make/receive calls again. But forcing 2g/3g/lte does not have an effect for me.
viktor1983 said:
It's Telenor Hungary, no VoLTE or other "magic" involved. There was a previous thread, which discussed the same issue. Actually I posted it to talk.sonymobile.com also, but please see the attached screenshot - it shows the actual issue. Telenor Hungary shows up as "emergency calls only", while Telekom HU and Vodafone HU seems to be fine. Sometimes switching airplane mode on/off solves the issue, sometimes it's a reboot which makes me able to make/receive calls again. But forcing 2g/3g/lte does not have an effect for me.
Click to expand...
Click to collapse
If this is the case, it is the SIM cards identification is not consistent to the network tower. Maybe the carrier has updated sim card version if you ask them. If it is emergency calls only logically its the network not authenticating your account based on sim card. It may be sensitive to the phone hardware. I have heard some people on other phone models hadd to ask carrier to provide even old version of their sim card instead of new ones. Try that.
ehBrY said:
If this is the case, it is the SIM cards identification is not consistent to the network tower. Maybe the carrier has updated sim card version if you ask them. If it is emergency calls only logically its the network not authenticating your account based on sim card. It may be sensitive to the phone hardware. I have heard some people on other phone models hadd to ask carrier to provide even old version of their sim card instead of new ones. Try that.
Click to expand...
Click to collapse
Thanks, I'll give it a try today and ask them to replace sim card. Hopefully it will solve the other appearance of this issue also: whenever I have full bars and talking (usually late night driving home to parents, in a well-covered area), audio quality degrades in seconds - at least on my side - and other party is not able hear anything I say. After disconnecting - if I'm able to do so, and phone app does not get stuck with "call disconnecting" message - I'm not able to make/receive new calls, as only the outline appears of signal strength bars. After restart everything works perfectly. Strange, isn't it?
viktor1983 said:
It's Telenor Hungary, no VoLTE or other "magic" involved.
Click to expand...
Click to collapse
Ironically - or maybe not - I am not that far away. I am on Orange Romania. When I search for networks I get essentially the same picture -
Thanks, I will try the SIM trick as well, maybe it helps. I may even go as far as jumping carriers, in fact.
ehBrY said:
If this is the case, it is the SIM cards identification is not consistent to the network tower. Maybe the carrier has updated sim card version if you ask them. If it is emergency calls only logically its the network not authenticating your account based on sim card. It may be sensitive to the phone hardware. I have heard some people on other phone models hadd to ask carrier to provide even old version of their sim card instead of new ones. Try that.
Click to expand...
Click to collapse
Got my sim card replaced, now waiting for the issue to pop up again. (or hopefully not) Actually the guy at carrier said my "white" simcard (about a year old) was a problematic one, replaced it with a new. I don't know if this could be true, but hopefully it'll solve the problem.
ehBrY said:
If this is the case, it is the SIM cards identification is not consistent to the network tower. Maybe the carrier has updated sim card version if you ask them. If it is emergency calls only logically its the network not authenticating your account based on sim card. It may be sensitive to the phone hardware. I have heard some people on other phone models hadd to ask carrier to provide even old version of their sim card instead of new ones. Try that.
Click to expand...
Click to collapse
It seems that replacing the sim card solved the issue, thanks for the hint! I would have never ever thought that a sim card issue may cause such a problem.
I have exactly the same issue and have already a new sim, which doesn´t do the trick for me....any other ideas how to solve this?
no VoLTE or anything like that. T-mobile as carrier
cryss83 said:
I have exactly the same issue and have already a new sim, which doesn´t do the trick for me....any other ideas how to solve this?
no VoLTE or anything like that. T-mobile as carrier
Click to expand...
Click to collapse
No longer have this problem with recent firmwares. The sim change did not solve the problem for me.
landsome said:
No longer have this problem with recent firmwares. The sim change did not solve the problem for me.
Click to expand...
Click to collapse
Thank you for the feedback.
With the recent firmware you mean 52.0.A.8.50 on android9? Do you use stock rom or a custom rom?
cryss83 said:
Thank you for the feedback.
With the recent firmware you mean 52.0.A.8.50 on android9? Do you use stock rom or a custom rom?
Click to expand...
Click to collapse
No, it's the past 4 or 5 firmwares.
cryss83 said:
Thank you for the feedback.
With the recent firmware you mean 52.0.A.8.50 on android9? Do you use stock rom or a custom rom?
Click to expand...
Click to collapse
What an irony! After updating to the latest fw some 2-3 days ago, it's happened again, the first time in some 4 months.
Nooo... I just got my replacement phone today and so i installed all the latest firmwares.... I still have high hopes i won't be affected again.
Has anyone any idea how many phones are affected this way... Can't be all of them otherwise there would have been a flood of threads about that.
Maybe some prior models of this series...
cryss83 said:
Nooo... I just got my replacement phone today and so i installed all the latest firmwares.... I still have high hopes i won't be affected again.
Has anyone any idea how many phones are affected this way... Can't be all of them otherwise there would have been a flood of threads about that.
Maybe some prior models of this series...
Click to expand...
Click to collapse
Did you test different firmware regions?
Maybe your mobile network provider and the baseband aren't compatible (bug).
And did you report Sony that the bug is in the newest firmware?
No i've just used the original settings since i am still in warranty time
But that's why i've asked before if the others were experiencing this issue only with their stock or even with custom roms / fw.
cryss83 said:
No i've just used the original settings since i am still in warranty time
But that's why i've asked before if the others were experiencing this issue only with their stock or even with custom roms / fw.
Click to expand...
Click to collapse
Changing regions doesn't need an unlocked bootloader.
MartinX3 said:
Changing regions doesn't need an unlocked bootloader.
Click to expand...
Click to collapse
For that, do you mean to change the settings in the play store or which settings are you referring to?
cryss83 said:
For that, do you mean to change the settings in the play store or which settings are you referring to?
Click to expand...
Click to collapse
Just use xperifirm and newflasher to apply a different region.
But remove the userdata.sin if you don't want a full wipe.

Categories

Resources