Very stumped on this issue, went and spent 3 hours at sprint store and they have no idea whats wrong. We tried all tech support possible from soft to hard resets. Phone will look like it sent the SMS but never really sends it. IT recieves fine and MMS is fine as well. Phone calls and LTE perfect. Sprint suggested two towers are down in the area but seems to look like its only my phone effected. Any help is appreciated.
Have you tried a third party app like handscent?
---------- Post added at 11:43 AM ---------- Previous post was at 11:35 AM ----------
You may need to flash the full odin version of android to fully get back to factory. Have you tripped knox on the phone yet? A full wipe of all your internal and external storage is recommended too.
Related
After two weeks of use the accelerometer stops working and auto rotation from portrait to landscape stop working .. i reboot the device and nothing - factory reset/hard reset wipe out all data nothing the accelerometer is not working.
Any one else with this problem and please give a solustion.
thanks!
Im in the same boat. I've tried reboots, resets, and apps to no avail.
---------- Post added at 08:04 AM ---------- Previous post was at 07:33 AM ----------
I just fixed mine by hitting it on my knee in the middle of my N5. Some people here are doing the same thing:
https://productforums.google.com/forum/#!topic/nexus/hmVdHAYKobw
Worth a try. Worked for me.
Same issue here. See my rant lol
http://forum.xda-developers.com/showthread.php?t=2663634
This is why you have warranty...
mortenmhp said:
This is why you have warranty...
Click to expand...
Click to collapse
Some of us don't so that's why I'm looking towards fixing the problem since I know I'm not the only one and I doubt the issue is defective devices.
neriamarillo said:
Some of us don't so that's why I'm looking towards fixing the problem since I know I'm not the only one and I doubt the issue is defective devices.
Click to expand...
Click to collapse
Shame. Anyway, a good rule of thumb is that if full flash of factory images and a full wipe without restoring any backups doesn't fix it, it isn't a software problem.
so basically here's the issue... I haven't rooted my s5 ..yet...i bought this phone 07/16/14 ...however i noticed since the last two weeks i've been missing calls .. meaning the phone doesn't ring on the receiving end...at all...i don't know if its a tower issue ...but i have another S5 user in my home thats on my account and has no issue receiving calls ...i did everything from calling customer service and did the phone reset #whatever# ...also reset the profiles and all ...even to the point of going to the repair store (sprint) and their saying is not a phone issue but a tower issue (...really :roll eyes: ) so how come the other device in my home isn't having the same issue....so my plea to the gr8 ppl of XDA what other suggestions can you advise me ?
thanks in advance.
My wifes s5 lost call volume and speaker volume within the first week. We made them replace it. If a factory reset and a prl update has not done it, than force the.. it is a hardware issue and dont take no for an answer. The volume has nothing to do with the towers. Turn the phone full blast and have them call it. Have the other s5 there and trade calls to prove the point. Dont take no for an answer is the important thing.
---------- Post added at 09:41 PM ---------- Previous post was at 09:40 PM ----------
Let us know how it works out.
This should probably be under Q/A or general....as for the issue its probably hardware related, try updating to the latest version of stock android for the S5 (if possible).
Sent from my SM-G900P using XDA Premium 4 mobile app
Ok u guys understand that if the phone is rooted the Warranty Is Now Void.
I work for sprint. I root all my devices.
And honestly im tired of the network issues. But if u modify your phone. In any way. We will not exchange it. Fortunately for most, sprint employees dont know how to check or verify if the phone has been modified.
But just remember. Modified = No warranty.
Or wait the 2-4 weeks for samsung to replace it. IF they dont catch your modded system.
Rant over. Hahahahah
Thats correct. I am not advising that he root his phone as that will not help the issue. He is Definatly dealing with a hardware problem. I have seen several similar posts as well as what i experienced. The only way to correct this is to get a replacement.
Follow up
i've done some field testing on my part to verify if there is a hardware issue vs signal issue...here's what was done ...from my home where i origially have the problem where my phone is the only S5 that is not able to recieve calls....so i drove about 4-5 miles away from home and i was able to recieve calls...i can't take the phone to the repair sprint store because they're 5-6 miles and when they do their testing there...the calls go through..
Have you tried to update profile via the sprint app. Sorry i was under the impression you were missing all youe calls due to phone not ringing.
*Sigh* - less than 24 hours and it appears to be broken. Phone popped up with an update this afternoon (UK unbranded handset) and all installed fine. Now, camera won't start and just gives a "Warning camera failed" error... I've tried all guides online (clear cache partition, clear camera app data, remove SD card etc but no luck) did a full factory reset and camera worked for less than 30 mins and failed again. I really hope I can have it swapped for a new one, I'll be so annoyed to accept a repair on something so new. I'll contact the retailer tomorrow, but in the meantime back to my HTC One M8....
Anyone else had the same issue?
Nope. But my wife did get this message in a few apps that haven't been updated for marshmallow's new permissions. Is that what your seeing or are you talking about when just trying to open the camera from the shortcut
I bought mine yesterday and camera failed today. Took it back and got it replaced. In Australia.
Yes, I have this issue with a new S7 only 3 days old. It worked for a little while, but doesn't work anymore. I have tried all the techniques above too. Hey @seedubya, I am in Sydney and on Telstra. How did you get it replaced? Did the replacement work OK?
It's a common fault, Samsung are aware of it and are replacing the units no-questions-asked.
BTW: I have tried the info at http://recomhub.com/blog/galaxy-s7-and-galaxy-s7-edge-how-to-fix-camera-failed-problem/ - but it didn't help. I have been online with Telstra for an hour and a half trying to fix this.
---------- Post added at 11:38 AM ---------- Previous post was at 11:37 AM ----------
knightnz said:
It's a common fault, Samsung are aware of it and are replacing the units no-questions-asked.
Click to expand...
Click to collapse
Ah - tks for that. Will go and get it replaced then.
Go to settings - backup and reset - reset settings
try that to fix the camera failing.
*Note*
This will reset all of your phones settings, wifi pass words and so on. This is NOT a factory reset, Just a settings reset.
Someone mentioned a work around on another thread. Go to Settings > Display and disable Smart Stay, reboot your phone and try the camera again. This worked for me and the problem hasn't come back, although I hope Samsung fix the issue as I use the Smart Stay feature!
fix
https://www.youtube.com/watch?v=H04T4cNHzU8
Try this
https://youtu.be/3OqW4Jahvu4
maddave said:
Yes, I have this issue with a new S7 only 3 days old. It worked for a little while, but doesn't work anymore. I have tried all the techniques above too. Hey @seedubya, I am in Sydney and on Telstra. How did you get it replaced? Did the replacement work OK?
Click to expand...
Click to collapse
Telstra are obligated to replace it. Dont let them tell you otherwise. I got mine from harvey norman.
mandroid717 said:
fix
Click to expand...
Click to collapse
These are the same steps posted everywhere else but with video.
Also containing the end-all-be-all tech support statement "this should work"
So when it doesn't work, what do we do?
Hi everyone
Not quite sure where to start so I will go from the beginning.
I purchased a OPO almost 18 months ago now and since I received the phone I rooted it and originally flashed OxygenOS but found that that ROM drained my battery in hours, so then I installed Cyanogen OS 12.0(-YNG1TAS213) and found that almost everything worked perfectly. After a while I noticed that whenever I was in the car and went through an area that didn't have any carrier service I would need to reboot my phone in order to get my data to work again. I have put up with this because it hasn't been that much of an issue to me. (I mention this because it might be related to the issue I am facing now)
In the last couple of days my phone has gone from working fine to hardly working at all, until yesterday my phone just wouldn't connect to my carrier network at all and I kept getting a message come up as a notification saying 'Selected network (3 UK) unavailable'. When this happened I tried rebooting the phone, aeroplane mode off and on, clearing Cache and Dalvik Cache in TWRP and nothing helped. Yesterday evening after backing up my important data on the phone I went back into TWRP and did a factory reset.
After switching my phone back on again and setting it up as a new device I can now connect to my network, sort of. I don't get anything better than the shaded signal icon (worst signal strength), if I move around my house for example I lose service and if I go back to the same spot where I did have signal and flick aeroplane mode off and on again, probably about 40% of the time I get signal again.
A friend of mine is pretty good with this sort of stuff and has sorted previous phones for me but he lives 200+ miles away and can't really help. He thinks however that its likely to be the modem. I don't really know what to do so if someone can help instruct me as to how I can update the modem or suggest so other fix that would be awesome.
Thanks in advance.
Matt
Try flashing a new modem. There's a thread on it. There is no best modem, what works for you may not work at all for others, grab a couple, try one per day till you find one for you.
This always fixed that for me
Sent from my A0001 using Tapatalk
---------- Post added at 07:36 PM ---------- Previous post was at 07:35 PM ----------
Oh just read the bottom, download one (it's a zip), flash through twrp just like a rom
Sent from my A0001 using Tapatalk
Sorry I am completely new to dealing with modems. This may sound like a dumb question but does any modem work on any phone and its performance is based on what network you're using?
rikta said:
Try flashing a new modem. There's a thread on it. There is no best modem, what works for you may not work at all for others, grab a couple, try one per day till you find one for you.
This always fixed that for me
Sent from my A0001 using Tapatalk
---------- Post added at 07:36 PM ---------- Previous post was at 07:35 PM ----------
Oh just read the bottom, download one (it's a zip), flash through twrp just like a rom
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Nope modems are phone specific. You need a OnePlus modem.
Performance can vary based on location and carrier. You're best off trying a few, then remembering which is best for your. Modems aren't rom dependant, any OnePlus modem should work with any OnePlus rom. Some are made for different versions of Android though, I usually start with the most recent and work back.
Start here:
http://forum.xda-developers.com/oneplus-one/general/ref-oneplus-one-modem-collection-t2858734
Edit: this might have been part of the reason oxygen drained your battery too. If you've got the wrong modem your phone spend all day trying to negotiate a mobile connection. This kills your battery.
Sent from my A0001 using Tapatalk
Hey guys, just wondering if anyone has an explanation for this.
I have T-mobile Samsung Galaxy S7 G930T and had working root for quiet some time until one day some apps started to crash. So I thought I would try clearing app cache and rebooting. Thats when the phone fell into a bootloop and got stuck on the Tmobile logo. I was able to boot up with factory reset but still would fall into bootloop again when restarted. So I redid everything by going back to stock and reroot. Now everything seems to work fine but I was just wondering why that happened? I mean its not like I'm getting bootloop while rooting but all of a sudden after its been working fine for quiet some time. I wouldnt want it to happen again since its a hassle setting up everything.
I am on the latest PIA firmware and could it be google and samsung security are catching up? I think there were rumors where your google accounts could be blocked for rooting which seems highly unlikely. Many are also rooted on PIA firmware but I havent heard of anyone mentioning this. Anybody care to explain to this noob?
Same thing happened to me, I just did a factory reset. But it's happened a total of 4 times now over a period of a month and a half. It sucks having to reset my phone so often, and it's hard to imagine that this is a problem that everyone's dealing with. Which root method did you use? Does anyone know what causes this?
Morganmachine91 said:
Same thing happened to me, I just did a factory reset. But it's happened a total of 4 times now over a period of a month and a half. It sucks having to reset my phone so often, and it's hard to imagine that this is a problem that everyone's dealing with. Which root method did you use? Does anyone know what causes this?
Click to expand...
Click to collapse
That sucks. If it happened to me 4 times I would have stayed on stock haha. It hasnt happened to me again since last root, at least not yet. I did the engboot with princecomsy odin. Hopefully it wont happen again. Are you on the latest PIA firmware? I havent heard of any other instances other than you so it definitely isnt a common problem.
No, you accepted a security policy update notification. Disable it. Please search, there is an exact same thread with solution. Re-do everything, do not accept security policy update that pops up.
---------- Post added at 01:50 PM ---------- Previous post was at 01:48 PM ----------
http://forum.xda-developers.com/tmobile-galaxy-s7/help/phone-wont-boot-google-play-crashes-t3433088