Related
I hope this is in the right place if not I apologize. Anyways I was running AOSP v0.9 and this morning I turned off data to conserve battery life. After that my phone will only connect to 1x and it is always roaming. It seems to realize that it is supposed to be on USCC it even says USCC in the status bar. So I called customer service and they told me to do a *228 and from what I hear this is really bad for anyone running ASOP then I did it anyways and it connected me to verizon so I disconnected the call and am still stuck roaming and with no 3g. Then I decided to switch back to MIUI and I'm still having the same problems. Another weird note, if I set my network to automatic it kills my connection but if I put it on home only I am roaming. Any ideas guys.
Sent from my SCH-I500 using XDA Premium App
This is the same issue I posted earlier that I haven't resolved yet. I am getting the verizon thing when I dial *228 as well. It is really frustrating because the phone is virtually unusable for data now. Hopefully we get it figured out. I'll let you know if I come up with anything.
Sent from my SCH-I500 using XDA App
OK so after doing some research, it looks like this issue can happen if you disable your data (using a toggle, such as the ones in the notification bars of some roms), and then flash a new rom or kernel or something with the data off. It looks like it wipes the APN? Anyone know if this sounds like what may be the issue or how we might go about fixing it?
Well I just got off an hour long call with tech support they think it is an issue with the radio and want me to do an exchange since I bought it less than thirty days ago. So I don't know maybe I should just cancel this and get a new phone with a new carrier. Maybe something with 4g. But I love this phone so I don't know what I'm going to do. Keep me updated if you find a fix.
Swyped on my Mesmerize using XDA Premium App
Check the Showcase AOSP thread. I managed to find a little trick that fixed our phones suffering from the same issue. Its worth a shot on yours.
add144 said:
Check the Showcase AOSP thread. I managed to find a little trick that fixed our phones suffering from the same issue. Its worth a shot on yours.
Click to expand...
Click to collapse
Tried your method and nothing. Kind of running out of ideas here. Any radio/modem I should need would be in the ROM right? I have gone as far as to flash all the way back to DI14 and can't get this thing to work. Still can't figure out how it even happened in the first place.
Well I figured it out for me anyways. Call US cellular and they will give you a new phone under warranty. I'm on mine now. It is back to 2.1 and stock but it works!
Sent from my SCH-I500 using XDA App
bsbokc said:
Well I figured it out for me anyways. Call US cellular and they will give you a new phone under warranty. I'm on mine now. It is back to 2.1 and stock but it works!
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Just got mine working about 10 minutes ago. Call USCC tech and they said that for some reason I was no longer "provisioned" for 3G service so they fixed it. I know our issues were a little different. Glad we're both up and running again. Now lets see if I can do something else to screw this up . . . . .
JayRHamlin said:
Just got mine working about 10 minutes ago....Now lets see if I can do something else to screw this up . . . . .
Click to expand...
Click to collapse
Amen to that I spent 4 hours on the phone with them yesterday and they couldn't fix it. So the actually brought me a new phone to my work. I couldn't believe they would do something like that.
Sent from my SCH-I500 using XDA App
Wow now that's service. I have to say US Cellular has hands down the best customer service I have ever had to deal with. Store, tech support, billing. Everything.
Sent from my SCH-I500 using XDA App
JayRHamlin said:
Now lets see if I can do something else to screw this up . . . . .
Click to expand...
Click to collapse
Well it only took me about three hours I tried flashing a new kernel with an app I downloaded from the market can't remember the name but of course everything went to hell. Since I don't have a computer it took me 2 days to find one and get it flaked to stock in odin now my speaker doesn't work oh well maybe in another couple of days I can flag it again. Maybe I should just quit screwing worth it but it's just to much fun lol.
Sent from my SCH-I500 using XDA App
Getting tried of watching my phone reboot. If going back to stock would resolve the issue I would do it. I called big red today and the pinhead I spoke to acted like it was the first time anyone had called about the TB rebooting on it's own. I'm looking at going to a different phone. I really think at this point it is a software issue that they need to correct. Just like with most businesses things are not addressed until they become a problem. So my thought is we should set a date when every one calls in to report their rebooting phones. We do this every week until we get a resolution. Anyone with me?
Wait... You are rooted and getting reboots? Are you on gb? Did you root or install your rom properly? What kernel?
Stock I had no issues. Non-Gb I've had mostly no issues... Some kernels less reliable than others, of course. But to be honest it sounds more like a user issue than a tb issue
Sent from my ADR6400L using XDA App
Sent from my ADR6400L using XDA App
Are you near a Verizon store? Verizon is usually very easy to convince that you need your phone replaced. (Although I think they will only replace it with the same model. But I'm not sure.) My Thunderbolt never reboots on its own but I know it is a problem that many Thunderbolts are experiencing, so maybe yours (and many others) is/are defective. I'm 99% sure if you go into a Verizon store and tell them that it randomly reboots all the time, they'll replace it for you.
I reverted back to stock and haven't had a single reboot or loss of data on three days. Just sayin'.
Sent from my ADR6400L using XDA App
I have read posts where people who are not rooted are getting reboots after they took the update. Have never had an issue with my phone until I took the update. Am going back to stock for a week or so to see if that clears things up.
Funny how VZW is changing their stance on it, almost as if it never has happened. About a month ago I went into a store and they told me that Im not the only one experiencing problems and that there will be a fix within 2 months.
I called VZW tech support and they told me that no one else is having reboots.. . . . I dont get it.
Try flashing your radios, I put both of mine to .6 and the reboots stopped.
(there is a thread in teh development forum, with the packages)
Can you specify what you mean when you say "both"? I have been getting reboots too - approximately 1 per day - but is there a process to flash each radio independently?
Sent from my ADR6400L using XDA App
sethschmautz said:
Can you specify what you mean when you say "both"? I have been getting reboots too - approximately 1 per day - but is there a process to flash each radio independently?
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
No, but each flash has two radios
Sent from my ThunderBolt using XDA Premium App
Silvus said:
Try flashing your radios, I put both of mine to .6 and the reboots stopped.
(there is a thread in teh development forum, with the packages)
Click to expand...
Click to collapse
Any issues with tethering or gps using the old radios?
Sent from my ADR6400L using XDA App
Silvus said:
Try flashing your radios, I put both of mine to .6 and the reboots stopped.
(there is a thread in teh development forum, with the packages)
Click to expand...
Click to collapse
I still had reboots with both at .6, currently trying cdma.7/LTE.6.
Sent from my ADR6400L using Tapatalk
It is a hardware issue,that's where the few pricked phone came from,my original bolt had the reboot loop on stock but no one seems to want to hear that,it is a series of phones having the trouble and they are or have replaced most of them,as far as most of the other reboot go that is self made misery by not following directions or not reading to find the fix, this bolt I have now has no reboot issues and it has a mat finish to it,the other one and a few I have seen that had issues had a smooth glossy finish.
Sent from my ADR6400L using XDA Premium App
satseaker said:
It is a hardware issue,that's where the few pricked phone came from,my original bolt had the reboot loop on stock but no one seems to want to hear that,it is a series of phones having the trouble and they are or have replaced most of them,as far as most of the other reboot go that is self made misery by not following directions or not reading to find the fix, this bolt I have now has no reboot issues and it has a mat finish to it,the other one and a few I have seen that had issues had a smooth glossy finish.
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
I would love to think its a hardware issue, but my phone was solid from day one. Then I took the update and get these random reboot.
Sent from my ADR6400L using XDA App
It is not a hardware issue. It is a problem with the update and how certain phones installed it. Verizon is in the process of making a new update and has been working on it with HTC for a little while now & expect to have it going out this month. For some reason the software does not talk to the towers properly with some models & the hardware does not get the proper info which causes the reboots. Exactly how to tell which phones are affected, I don't know. My friend is trying to find out for me.
I can say that I ran my phone with rooted stock & moved up to the rooted update when it was available which I am still on and I have not had any issues at all besides the low recorded video audio which the update seems to have fixed for me.
My phone is:
Rooted stock & radios w/update
Adrynelynes 4.47 Kernal
I am telling you what HTC said they admit that a certain series is defective hence the snappy replacement. Just cause one Rom works and another doesn't isn't always the Roms fault,ever had a CPU that would run one OS and not another or RAM that worked fine on xp but not win 7 once the defective hard hits its limit it will fail. I have seen hardware work fine overclocked and the exact same hardware crash with half the settings,or a motherboard run suse fine but put Windows on it and it dies a week later. I didn't say they all were defective just one series of them and when they did the update a lot of the phones started to fail and some didn't,so does that tell you hardware or software,if one can run fine and the other fails its either a bad flash or bad hardware. Take your pick
Sent from my ADR6400L using XDA Premium App
I didn't do the update over the air on my other bolt, I downloaded it from HTC and it killed the phone,but the same download is on this phone and it works just fine,not one reboot, and its still stock and not rooted. The other one was dated Dec
10 and this one is dated Feb 11, I would just about guess they tweaked the update to weed out the bad phones faster,makes sense to me.
Sent from my ADR6400L using XDA Premium App
satseaker said:
I am telling you what HTC said they admit that a certain series is defective hence the snappy replacement. Just cause one Rom works and another doesn't isn't always the Roms fault,ever had a CPU that would run one OS and not another or RAM that worked fine on xp but not win 7 once the defective hard hits its limit it will fail. I have seen hardware work fine overclocked and the exact same hardware crash with half the settings,or a motherboard run suse fine but put Windows on it and it dies a week later. I didn't say they all were defective just one series of them and when they did the update a lot of the phones started to fail and some didn't,so does that tell you hardware or software,if one can run fine and the other fails its either a bad flash or bad hardware. Take your pick
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
I wasn't aware of HTC stating there was some defective hardware. Never saw any references to it. If thats the case then glad they acknowledged it.
It's definitely not a hardware issue. Its a radio/ signal issue. Verizon does know about it, and is working on getting a new update out there. I know this, for a fact.
Sent from my ADR6400L using XDA App
jett2314 said:
I have read posts where people who are not rooted are getting reboots after they took the update. Have never had an issue with my phone until I took the update. Am going back to stock for a week or so to see if that clears things up.
Click to expand...
Click to collapse
My TBolt is not rooted and before the update I had no problems at all but after the update the random reboots started. Battery life is acceptable but could be allot better.
Called Verizon yesterday and they acknowledge the problem and actually said HTC is aware of the problem and are working on it but have no expected date as to when it will be fixed. I believe it is definitely is a software issue and will be fixed when the official Gingerbread is released. Just my 2 cents.
So I just got a Nexus S 4g on Monday and my dad and I already rooted the phone and have been trying different roms. He actually rooted it and swapped out the stock rom before I even knew I was getting it.
So with both of the roms I have tried, whenever i recieve an incoming call the speakerphone automatically activates and I have to manually turn it off.
We already tried reflashing the rom and we have also tried replacing a lib***.so file (forget which one) and neither fixed the problem. I cant find any sort of setting for this.
Anyone else having this problem? Is there a fix available that someone can guide me? Very new to Android so I'm still learning the tricks of flashing etc.
Just curious...did you test the phone before it was rooted.
Sent from my PC36100 using XDA Premium App
I received the phone on monday evening and my dad had the phone all day and routed it etc.
I never handled the phone with the stock rom. Its not too big a deal since I don't use it for much calling but a fix would be greatly appreciated.
Sent from my Nexus S 4G using XDA App
webhead1994 said:
I received the phone on monday evening and my dad had the phone all day and routed it etc.
I never handled the phone with the stock rom. Its not too big a deal since I don't use it for much calling but a fix would be greatly appreciated.
Sent from my Nexus S 4G using XDA App
Click to expand...
Click to collapse
Well it seems like you don't know if this problem has always existed or if it is a result of flashing a custom rom. Best bet would be go back to completely stock and see if you still have the problem.
Sent from my PC36100 using XDA Premium App
Just flashed the new miui rom and it fixed the problem. Now I just have to redo my launcher lol.
Sent from my Nexus S 4G using XDA App
I'm having the same problem running a stock version of Android.
I started to have the same problem few days ago and my phone is all original stock, ,,
my wife just started experiencing this today. completely stock nexus s. we may try uninstalling the last few apps that had updates and see if we can trace it to one of those.
edit: are any of u using go sms (specifically version 3.66)? other users are complaining that recent update is causing this issue. im sending my wife a backed up version i have of 3.65 to see if its resolved
edit 2: rolling back to 3.65 did not resolve the issue, but rolling back to 3.64 did. good thing i have appmonster pro.....
I just started to have this problem today too. I did try to activate GoogleVoice yesterday but the calling issue did not begin until today. Running MATR1X v.6 and CM7 nightly #83. Didn't have this problem during stock.
Go sms's latest update is the culprit. The August 29 th update is responsible. Just uninstall that and put some other sms app.
Should solve it, It fixed my phone.
it happened to me twice yesterday, I answer the phone the screen went black and the sound routed to the speaker..can't go back to turn it off during the call as the screen has nothing. (stock rooted)...will uninstall GoSMSPro and see how it goes
If anyone needs/wants the 3.64 version of GO SMS, dm me you're email addy. (i'm assuming this would be ok on XDA since the app is FREE in the market?)
They (GoSMS) just released an update 3.66 to fix the problem
vennstrom said:
They (GoSMS) just released an update 3.66 to fix the problem
Click to expand...
Click to collapse
Its still exists on 3.66. My wife was using this version and it had the problem. We had to roll back to 3.64 before it went away.
u were right, Go SMS was the issue, they released an update today and solved the problem!
cheers everyone!
Glad I saw this thread... my G2 started doing this after not changing the ROM in months, at least now I know what caused it. I got my Nexus S yesterday and haven't answered any calls without the headset yet, lol, so I thought it was just my G2.
So I've been an atrix 2 user for a few months now and its a great phone...Its rooted and I just updated it with the latest ota update and kept the root and all of that good stuff. But one problem that I have been having with my phone for the past month or so is that my phone will heat up like CRAZY! Then restart and then it wont let me use it. The power button doesnt let me turn the phone on...nothing. The only way I can wake my screen is by putting the power chord in and that just lights it up it doesnt let me use the phone. It shows that everything is functioning in the background I still receive messages and my apps update ect. but I cant use me phone. It goes through this cycle for about an hour then completely kills my my battery after it runs its course. I have no idea whats wrong with my phone. Can anyone help or have any suggestions? Anything would be appreciated!
Sounds to me that you need a new phone. Is it through att? You may need to do a warranty exchange.
Sent from my SAMSUNG-SGH-I997 using xda premium
Yes it is from AT&T I had to do the same thing with my original Atrix, but I traded up for the atrix 2
That doesn't sound good... the OG Atrix had a couple problems with that but I've never experienced it on the A2. You should try for a warranty exchange... look at the noob thread and flash the fxz, apply the OTA update and then take it to AT&T.
Yeah I think thats what I'm going to end up doing...this especially happens when I'm listening to music on my phone it loves to freak out on me. I'm just starting to have my doubts about Motorola because my original Atrix gave me problems and I so desperately hoped that it would be fixed in this version. Is it just bad luck I got 2 phones from motorola that both freak out on me? or is it me?
I'd say bad luck.
I've had 4 A2's and, while none of them were perfect, none of them had overheating problems.
Sent from my MB865 using Tapatalk
drummerkid_167 said:
Yeah I think thats what I'm going to end up doing...this especially happens when I'm listening to music on my phone it loves to freak out on me. I'm just starting to have my doubts about Motorola because my original Atrix gave me problems and I so desperately hoped that it would be fixed in this version. Is it just bad luck I got 2 phones from motorola that both freak out on me? or is it me?
Click to expand...
Click to collapse
My A2 is my first Motorola. I have an htc and two samsung phones and my A2 is by far more stable than any of my previous phones. I would say you have just gotten two bad phones. Do what you want to but i would stick with Motorola. Just giving my two cents.
Sent from my SAMSUNG-SGH-I997 using xda premium
Try cpu master pro and change governor to ondemand.
It works on my a2.
The major problem for me now is sometimes signal dissapear.
Sent from my MB865 using Tapatalk
kojitabe said:
Try cpu master pro and change governor to ondemand.
It works on my a2.
The major problem for me now is sometimes signal dissapear.
Sent from my MB865 using Tapatalk
Click to expand...
Click to collapse
Interesting if the problem is the governor...
Also for a free way to change the governor use ROM Toolbox (free) and go to CPU Sliders.
Sent from my MB865 using Tapatalk
I really appreciate all the feedback from everyone, what I did so far is that I flashed the stock FXZ file back to my phone then updated and seems to be working like a charm buy I still think its too soon to say how its really doing. Instead of second guessing myself I think Im going to get a fresh A2 today hopefully and I won't have any problems like this again! Thanks to all the help from everyone!
Sent from my MB865 using XDA App
drummerkid_167 said:
I really appreciate all the feedback from everyone, what I did so far is that I flashed the stock FXZ file back to my phone then updated and seems to be working like a charm buy I still think its too soon to say how its really doing. Instead of second guessing myself I think Im going to get a fresh A2 today hopefully and I won't have any problems like this again! Thanks to all the help from everyone!
Sent from my MB865 using XDA App
Click to expand...
Click to collapse
I would also take a good a good look at the apps you use, some apps leave themselves running and take some good resources, and can cause your phone to overheat because of this. take a look at the resources in use from settings --> applications, go to the running apps tab, do this when the phone is hot and see what apps are taking a good bit of resources. Just a thought, as I have had this issue before, not on the exact phone I am on now, since I found the offending app and did not reinstall it the last time I got a replacement of this phone.
I wish I could check it when my phone gets hot, but when it gets to that point my phone boots me out. Not letting me touch it at all :/
Sent from my MB865 using XDA App
Apparently the systempanel app (paid version in the market) can identify which apps were running when your phone rebooted, won't tell you whats causing it but may get you close. I dunno how to use th app very well though but I heard good things.
Sent from my Motorola Atrix 2 with AT&T 4G
I've started having this problem today as well. Two days ago I noticed a very quick drop in battery level to almost nothing after going below 50%. Same thing yesterday and today. Today was the first day that I noticed the severe overheating.
I'm using the SCv5.1 ROM. I've been using it for about a month without trouble, but any chance that's the cause? I'd love to not need to return the phone to ATT.
The only time I experienced these symptoms was after restoring an AtrixBlaze ROM.
Flashed back to stock w/root, then OTA. Restored a backup of RebelROM. No problems since. Was very concerned for a day that it had some how damaged the phone.
I've been through Iphone, Palm Pre and HTC, this phone beats them all except for WebOS which was the software on the Pre. That was an amazing OS with a lot of potential.
Sent from my MB865 using Tapatalk
Using Jimbridgman's advice above, I looked at some of my apps. I had been using Green Power Premium (paid) and it just updated a few days ago. I disabled it and have not had an issue since, but I have yet to go through an entire power cycle.
I bought my Atrix 2 in India yesterday. Everything works like charm except the earpiece. The voice I get from the other party is so shrill that I need to keep my phone away from my ear to understand what they are saying . There are 4 settings in all to change the voice quality of the earpiece but it seems they are of no use. On the last setting, I can even hear my own voice from the earpiece. Also, when I tap my phone around the 3.5mm jack area, I hear a sound that makes me feel that something is loose inside. Is it a known issue or a bug or its just me who’s facing this? What’s the way out? Thanks in advance.
I apologize if these questions were asked before, but I could not find anything that helped through searching.
Both my wife and I are having issues with the signal on our phones. We get drops and a weird noise occasionally occurs (a weird gargle sounding noise or something like a fax machine). I'm running the latest Ultragen, and she's running the latest AntonX Barebones. I just find it weird that both phones do the same thing.
So, the question is, do all these ROMs use the same modem? Could switching to a different modem help solve the issues I'm having? How do I find out which ROM uses which modem? There's nothing listed in the phone's "about" section of which modem is being used.
Any feedback would be awesome!
About phone>baseband. That will tell you what modem your running. Fb's got thread for modems in the Dev section.
Try some and see if it fixes it. I've never had that issue and don't remember anyone else having it either.
Thanks, Hechoen! I'll check out FB's thread and just do some trial & errors. I'll definitely post back with my findings just in case anyone else runs into this issue.
I forgot to mention that I'm on T-mobile; although I doubt it is carrier related since both phones are having the same problem and I'm in Chicago, where the signal is strong.
For what it's worth I guess TMOB and MetroPCS are in the process of merging. Some people on are having strange issues. So if this has started recently I'd call TMOB and *****. Also try going back to stock on both phones for a few days. If it still does it then call TMOB and ***** some more. LOL Good luck.
I didn't know they started implementing that... I'm definitely gonna *****! LOL Thanks for the heads up!
Sent from my SGH-T959V using xda app-developers app
Sound like an interesting proposal for them to merge if they could only get their four g up and.running it would be great
Sent from my SGH-T889 using Tapatalk 2