[Q] "No Service" dropouts, even after Hard Reset - ONE Q&A, Help & Troubleshooting

Hi All,
I am just wanting others' input, to be sure that my thinking is clear.
I was having issues with my phone connection constantly dropping to "No Service" over the last week or so. I have been running CM11s Stock, with TWRP and Franco r19/20 (at whatever stage it was happening). Every time I got away from my wireless networks at work or home, the LTE/H+ signal would be there when I jumped in my car. However, once I got to my destination - whether it was 3 minutes or 45 minutes away, I would turn the phone on to show "No Service." Infuriating, as restarting it made no difference, and I had to use *#*#4636#*#* to turn off and on the radio.
Sick of doing this, I did a hard reset, then I re-flashed 33r by adb. This wiped everything on the phone (AFAIK), so I have started fresh with no data corruption. I installed Philz Touch Recovery, rooted, then installed Franco r21.
The damned thing is still doing it!
I tried flashing another modem, but the problem is still there as of 10 minutes ago.
So, I am thinking that it is either:
1. The SIM / Carrier - SingTel Optus (AU) - Spintel SIM
2. Franco Kernel, though nobody else is experiencing this in the Franco thread
Is my thinking right here? Have I missed something along the way?
Thanks.

AJ RIMMER! said:
Hi All,
I am just wanting others' input, to be sure that my thinking is clear.
I was having issues with my phone connection constantly dropping to "No Service" over the last week or so. I have been running CM11s Stock, with TWRP and Franco r19/20 (at whatever stage it was happening). Every time I got away from my wireless networks at work or home, the LTE/H+ signal would be there when I jumped in my car. However, once I got to my destination - whether it was 3 minutes or 45 minutes away, I would turn the phone on to show "No Service." Infuriating, as restarting it made no difference, and I had to use *#*#4636#*#* to turn off and on the radio.
Sick of doing this, I did a hard reset, then I re-flashed 33r by adb. This wiped everything on the phone (AFAIK), so I have started fresh with no data corruption. I installed Philz Touch Recovery, rooted, then installed Franco r21.
The damned thing is still doing it!
I tried flashing another modem, but the problem is still there as of 10 minutes ago.
So, I am thinking that it is either:
1. The SIM / Carrier - SingTel Optus (AU) - Spintel SIM
2. Franco Kernel, though nobody else is experiencing this in the Franco thread
Is my thinking right here? Have I missed something along the way?
Thanks.
Click to expand...
Click to collapse
I've had random drop outs as well (over the past week/week and a half).
I have franco r19, not saying that is what it is as my signal is there most of the time but reading your post that's the only thing I see that is similar (I am on T-Mobile).
Haven't tried anything to fix it as it doesn't happen very often maybe once a day or two.

I'm on AK and also having these issues. I thought it was the network so I went to tmobile and the lent me a loaner (Alcatel) and it worked just fine until I went back after 6 hours. From what I understand on the OnePlus forums, it can be software related.

I went out for a while just now, and it has done it again. It appears to be happening after the switch from wifi to phone data.
This is what I noticed:
If I leave a place with WiFi, and the phone switches back to phone data, that is when it drops service. Phone radio appears turned off, but in diagnostic mode it still shows as turned on.
When I re-establish the phone data service, it stays connected to phone data for the time I am away (just now it was about 2 hours).
When I leave the office in a couple of hours, it will drop the service again.
I just reflashed Franco's latest kernel to see if it makes a difference. If it doesn't help, I may try stock and see what that does.

I have the same problem, tried several different basebands as well as kernels. Always the same issue, either dropping service altogether or not being able to use mobile data.
---------- Post added at 05:54 PM ---------- Previous post was at 05:51 PM ----------
Reading the oppoforums for find 7, they seem to have similar issues.

I have the same issue, frequent-ish drop outs when on mobile data and travelling in the car/tram etc. Had no such issues on my previous Nexus 4.
Two guys at work have the same phone and are having the same issues so does seem like an issue with the oneplus one software.
I'm personally running latest franco and slimkat but the others at work are running CM 11s...
All of us are on Telstra.

I have frequent drops as well. Luckily they are usually short ones.

stratmetal said:
I have the same issue, frequent-ish drop outs when on mobile data and travelling in the car/tram etc. Had no such issues on my previous Nexus 4.
Two guys at work have the same phone and are having the same issues so does seem like an issue with the oneplus one software.
I'm personally running latest franco and slimkat but the others at work are running CM 11s...
All of us are on Telstra.
Click to expand...
Click to collapse
I'm on Spintel (Optus). Mine was good today. No issues at all.

Related

[Q] Sporadically drop data connection

I got my vzw gs3 on Oct 1. Within the same day I had it wiped and put on AOKP jelly bean rom. Essentially since i've had the device, i continue to have issues where the phone drops data completely. This isn't an issue of cycling between 4G/3G, as even if I disable LTE, I still have problems where 3G drops and I have no data at all, after about 30 seconds, data comes back.
I came from an vzw OG Droid 1, and still living in the same house, I never had any data issues like this on that ancient phone. So I'm confident it's not the area I'm in the or the towers, and has to be a hardware or software issue.
Has anyone else experienced complete data drops on the S3? Is there any solution?
I've searched around and it seems I'm not the only one. For example, https://community.verizonwireless.com/thread/777654.
I've tried a battery pull, pull out the SIM card, turn the phone on, do another battery pull, put the SIM back in, and turn it on.
I've also tried flashing different modems, from here http://rootzwiki.com/topic/34053-of...zon-sgs3-sch-i535-odin-or-recovery-flashable/, to no avail. The problem never got better, only worse.
I535VRLF2 - Original modem that came with the device
I535VRLHE - Didn't help
I535VRLI5 - Didn't help
I535VRLJ1 - Made it worse
I535VRLK1 - Latest modem leak, going to try now.
The last resort option I'm going to try is flash back to complete stock and see if I still get issues.
xneuromancer said:
I got my vzw gs3 on Oct 1. Within the same day I had it wiped and put on AOKP jelly bean rom. Essentially since i've had the device, i continue to have issues where the phone drops data completely. This isn't an issue of cycling between 4G/3G, as even if I disable LTE, I still have problems where 3G drops and I have no data at all, after about 30 seconds, data comes back.
I came from an vzw OG Droid 1, and still living in the same house, I never had any data issues like this on that ancient phone. So I'm confident it's not the area I'm in the or the towers, and has to be a hardware or software issue.
Has anyone else experienced complete data drops on the S3? Is there any solution?
I've searched around and it seems I'm not the only one. For example, https://community.verizonwireless.com/thread/777654.
I've tried a battery pull, pull out the SIM card, turn the phone on, do another battery pull, put the SIM back in, and turn it on.
I've also tried flashing different modems, from here http://rootzwiki.com/topic/34053-of...zon-sgs3-sch-i535-odin-or-recovery-flashable/, to no avail. The problem never got better, only worse.
I535VRLF2 - Original modem that came with the device
I535VRLHE - Didn't help
I535VRLI5 - Didn't help
I535VRLJ1 - Made it worse
I535VRLK1 - Latest modem leak, going to try now.
The last resort option I'm going to try is flash back to complete stock and see if I still get issues.
Click to expand...
Click to collapse
I live in a place where 4G is rough and work in a place where no 4G and 3G was rough.
J1 seemed OK at first, once it settled it got bad, flashed K1 and seems to be holding strong, will have to try over a few days and see.
Sent from my SCH-I535 using xda app-developers app

Signal Dropouts

hey!
I have a problem with my One Mini. I have constant signal dropouts. Phone calls stop after a second, also losing data-connection all the time and always seeing the message "Preparing SIM-card".
It feels like my phone having problems with some mobile-cells. Usually I have to try to call someone 3-4 times, and after 3-4 attempts I can talk normally without getting interrupted after 1-2sec - like my phone found the correct cell or something like this.
I tried
- my second (O2) sim-card
- put some tape on top of the sim-card (solved this problem for people with different phones)
- put some signal-tweaks in my build.prop
- changed network mode (WCDMA/GSM/LTE...)
but nothing helped.
I am on O2-Germany for many years and never had those problems, my One S was working fine (before it got bricked )
Had the same problem last month in France...
anyone else having this problem? could this be kernel-related? I'm using JMZ`s kernel. But I guess this is more a radio-problem, or?
theodorius123 said:
hey!
I have a problem with my One Mini. I have constant signal dropouts. Phone calls stop after a second, also losing data-connection all the time and always seeing the message "Preparing SIM-card".
It feels like my phone having problems with some mobile-cells. Usually I have to try to call someone 3-4 times, and after 3-4 attempts I can talk normally without getting interrupted after 1-2sec - like my phone found the correct cell or something like this.
I tried
- my second (O2) sim-card
- put some tape on top of the sim-card (solved this problem for people with different phones)
- put some signal-tweaks in my build.prop
- changed network mode (WCDMA/GSM/LTE...)
but nothing helped.
I am on O2-Germany for many years and never had those problems, my One S was working fine (before it got bricked )
Had the same problem last month in France...
anyone else having this problem? could this be kernel-related? I'm using JMZ`s kernel. But I guess this is more a radio-problem, or?
Click to expand...
Click to collapse
I haven't had this issues, in fact, I went camping last weekend and most of the time I was able to get 1 bar when everyone else didn't have service at all. I'm using the AT&T variant on AT&T with the WWE DeOdexed Stock ROM and Jmz's Kernel 09-04-13. I attached a picture of my kernel, baseband, build, ect. I'd suggest making a backup and restoring your phone to stock to see if it's a software issue.

[Q] Network Signal In and Out with Reboots

I searched and did not see anyone else experiencing this issue. I have a Black 32 GB stock rooted. It worked fantastic for about 2 weeks and then all of a sudden I noticed the following:
Day 1: No SMS received. I was on WIFI and had network signal in the notification bar but did not receive SMS that were sent to me.
Day 2: No Cellular Signal. I looked at the APN and it had disappeared. I attempted to add it again and reboot the phone and it wouldn't add. The phone began rebooting on its own and continuing with a bootloop after running for about 10 seconds it would reboot again. It did this throughout the day. I called Google and they had me do some soft and hard resets. After the soft reset the phone would connect right after startup then disconnect after 2 seconds and reboot itself. I hard reset the phone and relocked the bootloader and reinstalled factory recovery and it is still doing it.
Google has given me authorization for an exchange but I was just wondering if anyone had any ideas because I'd rather not be without a phone for 2 weeks.
BTW I am on Straight Talk
I had a similar issue
I had a similar issue. After a month of functioning normally, my Nexus(rooted using CFroot, stock ROM, T-Mobile) lost the ability to get reception. First, it showed network signal, but cell access was not functional. A few hours later, bars dropped to zero, and it seemed like I could only get reception in the strongest signal areas. I would get signal sporadically when driving, but never when I was stationary. The phone never had problems with rebooting though.
After spending a day trying to fix it, factory reset, relock, flashing a factory image, I called Google, and they warranteed the phone.
nebrando said:
I searched and did not see anyone else experiencing this issue. I have a Black 32 GB stock rooted. It worked fantastic for about 2 weeks and then all of a sudden I noticed the following:
Day 1: No SMS received. I was on WIFI and had network signal in the notification bar but did not receive SMS that were sent to me.
Day 2: No Cellular Signal. I looked at the APN and it had disappeared. I attempted to add it again and reboot the phone and it wouldn't add. The phone began rebooting on its own and continuing with a bootloop after running for about 10 seconds it would reboot again. It did this throughout the day. I called Google and they had me do some soft and hard resets. After the soft reset the phone would connect right after startup then disconnect after 2 seconds and reboot itself. I hard reset the phone and relocked the bootloader and reinstalled factory recovery and it is still doing it.
Google has given me authorization for an exchange but I was just wondering if anyone had any ideas because I'd rather not be without a phone for 2 weeks.
BTW I am on Straight Talk
Click to expand...
Click to collapse
flmz said:
I had a similar issue. After a month of functioning normally, my Nexus(rooted using CFroot, stock ROM, T-Mobile) lost the ability to get reception. First, it showed network signal, but cell access was not functional. A few hours later, bars dropped to zero, and it seemed like I could only get reception in the strongest signal areas. I would get signal sporadically when driving, but never when I was stationary. The phone never had problems with rebooting though.
After spending a day trying to fix it, factory reset, relock, flashing a factory image, I called Google, and they warranteed the phone.
Click to expand...
Click to collapse
It just seems so much like a software issue as opposed to hardware that it surprises me they are willing to warranty it... but I guess I'm not the expert.
How long did it take you to get your replacement phone?
nebrando said:
It just seems so much like a software issue as opposed to hardware that it surprises me they are willing to warranty it... but I guess I'm not the expert.
How long did it take you to get your replacement phone?
Click to expand...
Click to collapse
I got a replacement phone pretty quickly. The phone shipped the day after I ordered the replacement, but YMMV.
Why do you think it was a software issue? The problem persisted after I switch back to a factory image. The replacement phone, running the same software does not have the same issue.
flmz said:
I got a replacement phone pretty quickly. The phone shipped the day after I ordered the replacement, but YMMV.
Why do you think it was a software issue? The problem persisted after I switch back to a factory image. The replacement phone, running the same software does not have the same issue.
Click to expand...
Click to collapse
That makes sense that it was a hardware issue. I guess it could be a faulty radio or something. I'm glad to hear you got your device shipped so soon. Did you end up having to pay shipping?
I ran a nexus 5 for about 4 days and went through two of them both having issues holding a signal. Both phones would start with LTE and then drop to 2g go to 3g and then 4g back to no bars and then 2g and 3g. I was stock all the way and I wish the nexus 5 worked better. It could be a software issue as when I took the OTA to 4.4.2 it became worse. All the areas I was in while this happened were areas that were supposed to be strong for 4g and LTE.
That said I I need a phone that is a bit more reliable even though I'm on T-Mobile. I switched to the LG G2. It has a better antennae and doesn't keep bouncing between modes when in various areas.

[Q] Weird behaviour on 3G or LTE

Hello,
I'm asking for some help to diagnose my call problems on UMTS.
First of all, three things happened recently, and let's assume that they happened roughly at the same time:
I dropped my Nexus 5 on concrete shattering the screen completely;
Google released Lollipop which some people believe has problems with 3G and LTE;
I'm using a rather old SIM card manually cut to fit micro-SIM dimensions.
About two days after receiving my Nexus 5 back from guys servicing it (new LCD screen) I had a telephone conversation that was disconnecting once every minute or two. There was no problem recalling though. The same day later I noticed that dialer app says "Emergency calls only" which was pretty weird. I was on Cyanogenmod 11, some recent nightly back then.
My first guess - revert to earlier nightly via TWRP. It didn't help - I was still on emergency calls only and nobody was able to call me. However, I could browse Internet without any problems on 3G.
Second guess - clean flash stock 5.0.1. It didn't help too, however calling went back on for some time (several minutes) before breaking back to "Emergency calls only".
Third guess - buy a starter SIM and check if it works. It did at first but stopped after an hour or so.
Fourth guess - bring the phone back to guys servicing the LCD to check antennas. I've left it for two days. It was opened and antennas checked. Everything was fine, not even a bent flex.
For all this time when on 3G/LTE data transmission worked flawlessly. I could download Google Maps, browse the Internet, whatever. It's just the very basic phone function that acts weird - as if I wasn't registered to a network. Everything seems to work fine on 2G, except for very rare disconnects (once per two, or three days).
So, considering it's pretty weird I'm seeking for help - could it be possible that after hitting concrete something broke down on the motherboard that results in such weird behavior? Or is, perhaps, my retro-SIM dying? Any ideas? Maybe flashing a well-tested radio ROM? Diagnostic apps?

[Q] 3G not connecting after screen change

After flashing CM12 on my nexus 5 (D821). I flashed the 20 jan Nightly and everything was working fine untill i update to the 22nd jan nightly when my 3g simply stopped connecting or had very spotty signal, i didn't give it much thought at first thinking it was a nightly problem but after one week i reflashed stock lollipop, locked the bootloader, even tried kit-kat and the problem is still there. Before flashing cm 12 2g/3g/lte switching was working perfectly for about one year.
So utill now: i flashed different stock rom's, different kernels, radios, custom roms and nothing worked. When i tried switching the sim with another one from the same network, 3g worked on the other phone so i doubt that the sim is defective, but on my nexus i had the same connectivity issues. I also played with the *#*#4636#*#* menu and managed to get 4G working again but only in CDMA mode and I cannot receive any calls or texts, but the internet connection is working, 3G also connected at some point but the signal was very poor.
I am lost now, and also desperate because edge is too slow for anything. What confuses me though is that this seems to be a software issue since the cause was me flashing a different ROM but all the signs point to a hardware issue.
Can anyone plese give me a second opinion? Is there any fix for this? (Also i recently went to my network's service to replace my screen assembly, could also this be an issue? the issue appeared about 2 days after getting it back from them, also about the same time i flashed cm12)
Thank you for your time.
Also another thing i just noticed:
I opened my phone's back cover and the writing on the frame covering the motherboard says D820 and in the bootloader my phone shows as D821. Is this common for every D821 model?
I started to wonder if i got all my components back from the phone service... Although it's highly unlikely that they mingled with the motherboard since everything that i had on my phone was still there (custom ROM and all my personal info) maybe they switched the antennas...
Is the antenna connected?
Im going with disconnected antenna as well.

Categories

Resources