I see an old thread from 2014 about others having issues. I didn't start having issues until several months ago and not sure why it's been acting up. Anyone know if there is a way to resolve it?
Related
Hey guys,
Here's my problem that has been getting progressively worse over the last few weeks. My phone is fully rooted with adb unlocked and I have had that done since I originally purchased the phone in June. I really had no issues no matter what Rom/Kernal I used until the last month and a half. Since then, my phone seems to have episodes where it will restart at random times whether on a phone call, on the net, or just idle. I've tried different kernals, undervolting, stock volt, and a hundred different roms with similar results. Anyone have any idea what to make of this? I have noticed that this DOES NOT occur while in Recovery or before getting to Android so I don't think it's a hardware issue. I always wipe data/cache/dalvik before using a Rom and I'm not a noob by any means. I have done everything that came to mind when initially troubleshooting this issue, but I'm out of ideas. Hopefully someone that's a bit more advanced than I am can come up with some possibilities. Thanks guys, I really appreciate any and all feedback!
sadly, it is a corrupted something issue. happened to me a couple months back. there is a whole thread on it down in q&a. no solution. unroot, and return. sorry to tell you this. sprint is usually pretty good about that stuff though.
sorry to write you this death notice...
My brother had the same problem with his Evo. Unrooted and it still had the problem. Had to return it under warranty.
My brother has a GNex. He is not as tech savvy as I am, so I try to help him out when I can (update his rom, troubleshoot issues, etc.). It's a bit difficult because I live in Texas and he goes to school in North Carolina. Long story short, he is having problems with his phone. He is having issues where the phone will not have any signal at all (literally can't make calls or text or anything). It is not the area he is in because I visited him and had zero issues with my GNex. His phone also says it is December 31, 1999. I found a few threads from a quick Google search describing similar issues, although it seems to be a variety of phones having the issue (I can't post links here yet because I am a 'new' user. If you want to see the threads I posted, this same message is posted at droidHive under Help/Galaxy Nexus and at DroidJunk under General Gnex Discussion). This must be some Samsung issue. He had the problem while running stock 4.0.2. Verizon sent him a ‘certified like new’ replacement and that was okay for a few days, then he had the issue again. I put him on Tranquil Ice 4.0.4 and that fixed the issue for a few days, then it came back. This has all been within the last couple of months.
Basically, I am wondering if anyone has previously heard of this and/or know how to fix it? All of the threads I noted above seem to have died and have not resolved the issue.
Thanks in advance for any feedback.
(in case you are wondering, I have a GNex running Junk with no serious issues and I'm loving it)
Just to update, my brother did a battery pull and everything seems to be working properly for the time being.
I'm still interested to know if anyone has more information about the problem described in the OP.
Hi All,
Any fix for [JB 4.2.2][Unofficial] CM10.1-M3 [03/05/2013] to force working Bluetooth headset? When I connect the device and try to make calls I hear only noise.
Thanks
They've been looking into it for several weeks (possibly months).
There is even a brainstorming thread on the issue, if you look.
I *think* they have come very close to a solution but not being a dev. I don't know if what they've managed to due in the last couple of days is relevant.
davidpartay said:
They've been looking into it for several weeks (possibly months).
There is even a brainstorming thread on the issue, if you look.
I *think* they have come very close to a solution but not being a dev. I don't know if what they've managed to due in the last couple of days is relevant.
Click to expand...
Click to collapse
Hopefully the issue will be solved soon. Because I don't want to use stock one.
I just got the phone. I have probably had it 2 weeks. It doesn't happen alot but every once in a while the phone seems to be getting clogged up. To the point where I couldn't manipulate the phone at all. I would have to wait a few minutes for the phone to catch up. I'm not running very many apps when it happens. I've had 3 different apps going and listen to music and it hasn't happened. Then other times I can be running one app and it starts to lag. It doesn't seem to have any kind of pattern. I was going to just deal with it as it only happens every one in a while. But today it froze so bad the phone restarted it's self. What app was I running when this happened? Feebly I was reading a news article. Hardly a process intensive app.
So my question is. Do you guys think I should get a new phone? Or I was thinking a factory reset could fix this?
Izbsleepy said:
I just got the phone. I have probably had it 2 weeks. It doesn't happen alot but every once in a while the phone seems to be getting clogged up. To the point where I couldn't manipulate the phone at all. I would have to wait a few minutes for the phone to catch up. I'm not running very many apps when it happens. I've had 3 different apps going and listen to music and it hasn't happened. Then other times I can be running one app and it starts to lag. It doesn't seem to have any kind of pattern. I was going to just deal with it as it only happens every one in a while. But today it froze so bad the phone restarted it's self. What app was I running when this happened? Feebly I was reading a news article. Hardly a process intensive app.
So my question is. Do you guys think I should get a new phone? Or I was thinking a factory reset could fix this?
Click to expand...
Click to collapse
If you are within your exchange time period, I would definitely go ahead and swap it out. If you are outside of that then I wouldn't because you will probably get a refurb if you do a warranty exchange through Verizon. The main question is, How time do you have left before you cant exchange it in the store....
Mine doesn't stutter at all even after running a ton of apps when I first got the phone. I read another thread just a few minutes ago that mentioned if you have any stutter or slow downs return it immediately. The original poster mentioned it was a night and day difference when he exchanged it.
Something I found odd with this phone. Is that it has the download Booster. Last I heard Verizon was taking that out of there phones.
I can confirm 100% issues with GPS on my AT&T Samsung Galaxy Note 4. I bought it Sunday (12/28/2014) and noticed instant GPS inaccuracies, teleporting, not updating correct route information, etc. I got home, OTA'd, tried again the next day, same issues. Took it into AT&T yesterday (12/30/2014), guy instantly swapped, I stood right there and showed him exactly what was happening on the brand new,fresh out the box phone. "Hmmm, I'd give it a couple of days to.....uhhh.....calibrate, then bring it back if it doesn't work." Screw that, wtf is going on? Why do a select few of us have the problem and why does it continue to happen to the same people?
In another forum, a guy took his back not 1, not 2 but 3 TIMES, same gps issues everytime......... Add me to the list of people who've had multiple phones and the same gps issues. SIM related????? Maybe? I can't have another phone, I absolutely love this thing.
Had a Note 2 for close to 3 years, not one GPS problem. Using the Otterbox Defender,tried with and without case.
Not experiencing this personally...
Might try the 'supposed' fix here and see if that helps you at all.
Orito said:
Not experiencing this personally...
Might try the 'supposed' fix here and see if that helps you at all.
Click to expand...
Click to collapse
Lucky you, I tried everything under the sun before I tried to get a new phone. I'm almost 98% positive it's a sim or AT&T software issue, most people started experiencing this after the update, I haven't had the phone long enough to know that information though.