I'm running 4.3 rooted on ML2, stock ROM. Within the last week I started experiencing a strange problem - after every single phone call made or received, I lose all network connection for about ten seconds. I get the circle with the line through it. Going into settings shows actual connection drop, not just the icon. Then, the connection reappears. I've made no modifications since rooting it in April, nor do I recall removing or freezing any apps any time recently. Powering down and/or removing the battery has done nothing to help.
Any ideas what would cause this? I can't find any threads here, or through a google search, discussing this problem. Any help is appreciated.
Update - same problems when running in safe mode.
Well, this seems to have been a local network problem, as the issue has magically disappeared. Nothing exciting to report.
fullboogie said:
Well, this seems to have been a local network problem, as the issue has magically disappeared. Nothing exciting to report.
Click to expand...
Click to collapse
Remove SIM card and clean?
Yep - did every trick in the book. Even reflashed via Odin to be sure I didn't have a corrupted radio file. It just started working again. I"ve seen the same problem reported in other parts of the country, apparently the result of something AT&T was doing to the network.
Related
after updating to froyo using the official OTA EPE54B - > FRF85B - > FRF91 my GPS will no longer lock on in the Google Maps application.. its pretty frustrating has anyone else experienced this and/or found a solution? I feel if it was a widespread issue their would be a big post about this already but I wasn't able to find much when searching the forums any help or advice would be most appreciated!
I have the same problem. I made a thread before but no one responded. Here's what I posted before:
Whenever I use the navigation feature in Maps, it gets stuck on "Searching for GPS." I've left it like that overnight and nothing happened. The entire time, the GPS icon in the notification bar is blinking. I've downloaded the GPS Status app and it can't seem to be able to find my location either.
I've tried wiping everything, installing different roms, reinstalling the radio but nothing seems to be able to fix the problem. Navigation worked fine before. This problem just popped up out of nowhere. I've tried it when I'm outside, in different cities, but that hasn't helped.
Click to expand...
Click to collapse
I also went back to 2.1-update1 to use the older version of Maps but that still didn't help. I've tried searching for others with the same problem but no one seems to have found a solution yet. I don't think it's a hardware problem though since people with different phones have reported the same problem.
I actually had the same problem with my previous phone which was the milestone (aka Droid) and the problem just randomly resolved itself.. so for sure I agree it can't be a hardware bug just wondering where the problem could be coming from then since by your findings it doesn't seem to be OS specific since your able to reproduce it on 2.1 as well.. and your also saying a factory reset doesn't fix the problem, so that rules out 3rd party apps.. I read on some other forums that some ppl had similar problems with the G1 and some people reported a battery pull as a temp fix. I tried it but it doesn't seem to make a difference.. have you tried this? also is the problem intermittent for you? or has it just stopped working and you haven't been able to lock on since?
just did a factory reset and still the same thing
no one has anything I could try to attempt to resolve this issue ?
Happened to me. Fixed itself in about 4 days.
Sent from my Nexus One using XDA App
im having the same problem since FRF50... my gps is slooooow and inacurate... ive tryed everithing, changing radios, several wipes, flashing all kinds of roms and backups... still the same...
when im in my house, the blue triangle appears at my neighbors house!
When I first got my phone the GPS wouldn't seem to get a fix (OTA FRF91, totally stock), but it essentially fixed itself. I took it outside and let it sit for 5 minutes trying and it eventually did get a fix, and now it gets fixes quickly like you'd expect. I should note that when I got to to make the first fix I had cell tower assist turned off.
Happened to me in FRF83. Went back to CM5.0.8. Started working again. I am on CM6.0 RC1 (based on FRF91) and it is working without a problem.
hayden1987 said:
I actually had the same problem with my previous phone which was the milestone (aka Droid) and the problem just randomly resolved itself.. so for sure I agree it can't be a hardware bug just wondering where the problem could be coming from then since by your findings it doesn't seem to be OS specific since your able to reproduce it on 2.1 as well.. and your also saying a factory reset doesn't fix the problem, so that rules out 3rd party apps.. I read on some other forums that some ppl had similar problems with the G1 and some people reported a battery pull as a temp fix. I tried it but it doesn't seem to make a difference.. have you tried this? also is the problem intermittent for you? or has it just stopped working and you haven't been able to lock on since?
Click to expand...
Click to collapse
I've tried that too. I've had the problem for almost two months now but I never had it before. It's really starting to get annoying since none of my other apps can detect my location either [weather,news]. I hope it just magically works again some day like it did for everyone else.
could this possibly be faulty hardware? should I try sending it in for a swap??
Settings -> Location & Security
Make sure that "Use wireless networks" is checked.
I was having a similar problem.
Hi everyone,
I have encountered a really annoying issue with my HTC One. It is a completely new replacement unit, and ever since I started using it I've had problems with the reception. In the beginning it only lost reception for a short while, and then regained it. Now however, the loss of reception is almost always followed by an immediate reboot, and after this reboot the phone often will not allow me to enter any pin at all. It will just show a "no reception" symbol in the status bar and subsequently reboot again after a minute or so. This boot loop continues until the phone actually allows me to input the pin again, after this the phone will work fine for awhile until this looping business starts anew.
I've actually tried a whole lot of different roms and radio versions in order to try to solve this issue, but to no avail. I've also used an RUU to reset my phones firmware from the very beginning, but the problem still remains. I've also tried to swap sim cards, no luck with that either.
I've tried to check the logs after these reboots, and the only things that seem to have anything to do with this are the lines: "failure to start external modem" and "MDM common shutdown".
Am I out of luck here? Is there anything I can do in order to try to fix this myself?
I'm afraid that if I hand it in for repairs the shop won't actually experience anything wrong with it, since this happens so randomly, and just send it back to me with a service fee.
Help is much appreciated!
Anyone? I've made a logcat log of the error tagged-messages that occurs right before a restart:
i.imgur.com/z5srdT3.jpg (I'm not allowed to post image-links since i don't have enough posts)
Bump.
So, since the 5.1.1 update I've been experiencing this bug, where the phone keeps loosing the connection to the mobile network completely randomly here and then, though when it cuts off it immediately comes back after a millisecond. This has been happening for a couple of days, I tested to reboot and seems the issue remains. Do you guys have any idea of what I can try to do before doing a complete reset to the phone?
Big Poppa Nexus said:
So, since the 5.1.1 update I've been experiencing this bug, where the phone keeps loosing the connection to the mobile network completely randomly here and then, though when it cuts off it immediately comes back after a millisecond. This has been happening for a couple of days, I tested to reboot and seems the issue remains. Do you guys have any idea of what I can try to do before doing a complete reset to the phone?
Click to expand...
Click to collapse
try a different radio.
Same here, but has happened since I bought the mobile, through it is not too annoying.
Looking for help on this one. Every 3-5 days my Ultra gets into a state where no voice can be heard by either myself or the person on the other phone when a call is made or received, but I can hear the ring tone if I'm calling prior to the person answering, and my phone rings as normal if someone calls me. But when answering the call it's just silence on both sides. A reboot fixes this only for it to happen again 3-5 days later, requiring another reboot.
At first I assumed it was a corruption of the rom I had installed, so I flashed back to my stock image with Odin, including a fresh VOD CSC install. Unfortunately, it's still happening after this. Speaking as an engineer, it's unusual but not unheard of for a device to have a hardware issue of this type and it be rectified each and every time with a reboot, that would normally point to a software/firmware error of some sort. However, the fact it's continuing to happen after a completely fresh re-flash of stock Android suggests my worst fears that it is hardware. I could try some things, like not installing Magisk or even re-locking my bootloader, but I don't believe either would be a factor. I only used Magisk for rooting and don't install additional modules. I've also ruled out the sim card or sim slots by swapping to an e-sim, only for it to still happen.
Anyway, any suggestions would be welcome, especially if you have suffered something similar. There is an easy fix, which is to schedule a reboot every morning at around 3am, but I'd sooner not have to do this before working out what the underlying cause is.
I don't have a solution for you but I just wanted to share that I am having the same issue. But I'm not using Magisk and not unlocked, or rooted. The only thing I did was flash stock Samsung and disable some bloat.
I was having the issue the other night (for the second time) when calling my carrier (AT&T) about an order. I just assumed it was them at first. I disabled wifi calling (after them not hearing me several times) then tried again and it worked.
Were you using wifi calling at the time? I haven't been able to reproduce the issue yet so I don't know if disabling wifi calling had anything to do with it working.
Just to clarify, you say you're using Magisk but you're not unlocked or rooted? That isn't possible, but perhaps you just worded it wrong and you meant you're not using Magisk.
Funny you should mention Wifi-Calling, when it happened a few weeks back I force closed Wifi calling in an attempt to track down any potential services that might be causing the problem. And when I did that the calling started working again without a reboot. I thought I'd tracked it down and thought I'd test it again once it happened again a few days later, I would then freeze wifi-calling (something I never use) which would hopefully stop it ever re-occurring. However, the second time I force stopped wifi-calling it didn't fix the issue.
Beefheart said:
Just to clarify, you say you're using Magisk but you're not unlocked or rooted? That isn't possible, but perhaps you just worded it wrong and you meant you're not using Magisk.
Funny you should mention Wifi-Calling, when it happened a few weeks back I force closed Wifi calling in an attempt to track down any potential services that might be causing the problem. And when I did that the calling started working again without a reboot. I thought I'd tracked it down and thought I'd test it again once it happened again a few days later, I would then freeze wifi-calling (something I never use) which would hopefully stop it ever re-occurring. However, the second time I force stopped wifi-calling it didn't fix the issue.
Click to expand...
Click to collapse
I missed a word when I first replied. I added "not" to Magisk but you must have seen it before I fixed it.
I've had many work meetings (on phone) since then and haven't had it pop up. I haven't changed anything and even have wifi calling back on, so I'm at a loss.
OK, traced this to possibly be linked to the attached logcat. Any suggestions?
Also, contrary to my claim in the opening post, the dial tone can only be heard sometimes.
An additional oddity, whilst the fault is occurring (prior to a reboot), voice calls on WhatsApp work fine.
Perhaps a form of modem fault?
I give up on this. I flashed the stock VOD rom in Odin and relocked the bootloader to take it as close to stock as possible (minus the knox flag being tripped which is unavoidable at this point) and it still showed the issue after a couple of days. I've also disabled Bluetooth at a service level to no avail as I thought it might be a glitch with that.
It's clearly a hardware issue that will only be resolved with a logic board replacement. Which currently aren't available.
One good thing is that a full reboot isn't required to fix it, a soft reboot seems to do it. So I've got a link to do that on my home page, only takes 10-15 seconds.
Beefheart said:
OK, traced this to possibly be linked to the attached logcat. Any suggestions?
Also, contrary to my claim in the opening post, the dial tone can only be heard sometimes.
Click to expand...
Click to collapse
Hi, sorry to re-open this old topic. My S21 has the same problem from the beginning, but I have the stock rom. Did you get this log using *#9900# tool? Which log level did you use? Which file is the attached one? BTW, I'm almost sure that it's an hardware failure, did you solve it? Thanks
nrg84 said:
Hi, sorry to re-open this old topic. My S21 has the same problem from the beginning, but I have the stock rom. Did you get this log using *#9900# tool? Which log level did you use? Which file is the attached one? BTW, I'm almost sure that it's an hardware failure, did you solve it? Thanks
Click to expand...
Click to collapse
I'm afraid not, I ended up selling it as parts or repair a few weeks after that post.
Beefheart said:
I'm afraid not, I ended up selling it as parts or repair a few weeks after that post.
Click to expand...
Click to collapse
Thanks anyway, I will try to bring mine to the repair center.
Hey all! New here. I just soft bricked my phone, i woke up to it not booting. I tried various fw in Odin, but no success. This is my day to day use phone, I don't have anything else, so I'd like to make it work again ASAP, hopefully without factory reset.
Hi
what manipulation did you do to get there before flashing a lot of stuff in odin?
I've been just pressing the buttons all around, then I read about Odin, so I tried it. Now my battery died, let's see if I can get to wipe the cache...
Update: no success. Is there a way to get it into recovery? the old volume up+bixby doesn't seem to work.
Sometimes its because the recovery itself is error so that button combination is not working..
Charge your battery until full, then factory reset it with odin, let see if that works
But before you do that make sure you download correct fw that match your phone model. dont try all fw available there, make sure you download fw for SM N950F..
Well it worked and it broke again... Back to square one.
Your infos are kinda vague.
Did you modify your phone and it got triggered by user-action, or did it hit the fan by itself?
I think it was a suicide attempt, I never flashed before, only major thing was just a battery change in a samsung service last summer. It's weird, because since last time it turned on again, but seems like the wifi didn't want to communicate, plus as I look back, sometimes it restarted when I touched the wifi or some random setting. Somewhere else I read that it could be a motherboard failure.
fzoli469 said:
I think it was a suicide attempt, I never flashed before, only major thing was just a battery change in a samsung service last summer. It's weird, because since last time it turned on again, but seems like the wifi didn't want to communicate, plus as I look back, sometimes it restarted when I touched the wifi or some random setting. Somewhere else I read that it could be a motherboard failure.
Click to expand...
Click to collapse
This was happening to me too before my phone just started bootlooping to recovery
Well it's been a few months, so a little update: it still reboots sometimes all out of nowhere, but now I have a different problem: tried to log into a mcdonalds app and it says it detects a security issue. Not that i'll cry over it, but definitely interesting. Anyway, I really think this is some sort of hardware issue related to wifi, because every time it started rebooting, about one out of two times i was turning the wifi on or off. Also sometimes the wifi just wasn't available or working, strengthening my thought. As I read on other threads, this is probably some manufacturing/serial issue, that just happens to come forth after all these years. Probably the last time I bought a Samsung...
fzoli469 said:
Well it's been a few months, so a little update: it still reboots sometimes all out of nowhere, but now I have a different problem: tried to log into a mcdonalds app and it says it detects a security issue. Not that i'll cry over it, but definitely interesting. Anyway, I really think this is some sort of hardware issue related to wifi, because every time it started rebooting, about one out of two times i was turning the wifi on or off. Also sometimes the wifi just wasn't available or working, strengthening my thought. As I read on other threads, this is probably some manufacturing/serial issue, that just happens to come forth after all these years. Probably the last time I bought a Samsung...
Click to expand...
Click to collapse
Try changing build prop, ro.config.tima to 0