Related
I'm curious if others are seeing their EVO reboot with random use. It doesn't seem to be related to one specific application although it is hard to say if a background app is the cause. I will be using navigation or an Internet-based app, then the screen goes black and the phone reboots.
I originally thought it was due to rooting, but I'm seeing it on different ROMs. I've wiped the cache and data when flashing the new ROMs and I've tried running with limited apps loaded with my recent move to the OMJ ROM. Everything actually runs great with the exception of the reboots.
I'm posting the issue here since it doesn't seem to be ROM specific and I'm curious if it may be hardware related. Is there a tool that would allow me to easily catch a log of the potential error to seek further help? A point in the right direction would be greatly appreciated.
I'm running stock 2.2 no root, and with gps on my phone reboots in the middle of 911 calls. (Thank God I wasn't calling about an immediate emergency) but it happened twice, once when I called and the other when they called me back. After turning off GPS, it worked fine. I thought this was a bug in 2.1 before update1, I didn't receive the problem until the 2.2 update.
adb logcat might see an error, but I'm not really sure.
Seeing it here. Not Rom or application specific.
try a factory reset.
That's scary news about the reboots during 911 calls. I can't say that I tested that as a trigger for the reboot and I hope I don't have to in the near future. However, it makes me curious if it is related to the phone's interaction with the Sprint network. In your case your 911 call may have been a direct trigger whereas my reboots are seem indirect while I'm using my data plan.
One reason for my reboot was due to me getting the Error Code 67 "Your PCS Vision username and/or password may be incorrect" when trying to tether (USB or hotspot). Rooting allowed me to tether using 3rd party apps, but there may be the underlying problem with my account.
I also should have mentioned that the reboots happen with GPS on as well as off. I typically have it off to save battery life. I've also done factory resets each time I've changed or updated my ROM.
Thanks for the feedback and suggestions so far. I'll try logcat and continue to monitor the forum for advice. I'll also post back any answers I may find elsewhere.
Thanks again.
I had a reboot tonite, phone was just sitting on table off charger about 90% battery, and I heard the Sprint screen come on looked down and noticed phone was booting up....no idea why first time I've noticed this.
Stock froyo no root...unfortunately :'(
AzmatEQ said:
That's scary news about the reboots during 911 calls. I can't say that I tested that as a trigger for the reboot and I hope I don't have to in the near future. However, it makes me curious if it is related to the phone's interaction with the Sprint network. In your case your 911 call may have been a direct trigger whereas my reboots are seem indirect while I'm using my data plan.
One reason for my reboot was due to me getting the Error Code 67 "Your PCS Vision username and/or password may be incorrect" when trying to tether (USB or hotspot). Rooting allowed me to tether using 3rd party apps, but there may be the underlying problem with my account.
I also should have mentioned that the reboots happen with GPS on as well as off. I typically have it off to save battery life. I've also done factory resets each time I've changed or updated my ROM.
Thanks for the feedback and suggestions so far. I'll try logcat and continue to monitor the forum for advice. I'll also post back any answers I may find elsewhere.
Thanks again.
Click to expand...
Click to collapse
Correction... I meant to say that the reason I rooted (not rebooted) was to get tethering without running into the Error Code 67. I tried the various solutions posted for the Error Code 67, but nothing seemed to work. But I'm curious if this may be part of the underlying issue if my device reboots based on a faulty account configuration when using some aspect of the Sprint network.
sprink0281 said:
I had a reboot tonite, phone was just sitting on table off charger about 90% battery, and I heard the Sprint screen come on looked down and noticed phone was booting up....no idea why first time I've noticed this.
Stock froyo no root...unfortunately :'(
Click to expand...
Click to collapse
The exact same thing happened to me last night. I sent a text, switched to my GMail and then boom. Error message about failure to send an SMS then reboot. Stock unrooted FroYo.
I had reboots only when using Undervolted kernels.
Seemed to be triggered by GPS + Phone call.
Yes, I was also having this problem. Definitely GPS related. Usually it would happen only if I was using the GPS for a long amount of time (navigating) - so I imagine it may be conflicting with cellular data if I received a txt while navigating or something. Who knows.
It was driving me crazy because A. I got lost and B. It started rebooting constantly and would randomly get caught in a boot-loop. I even had the problem after wiping EVERYTHING (even my SD) and reinstalling various ROMs (I tried 5 different ones).
The only solution I found in the end was to find the latest radio and wimax updates, wipe, re-install those - and then install the ROM again.
GPS may be a symptom, but not a cause for me since I typically have GPS off. I find that it typically happens when I'm using a networked based app, like the web browser. Following your post I turned on the GPS, started the navigation app and found that my EVO rebooted after the same amount of time I was experiencing with GPS off.
The more I think about it, it does feel like I just assume that it will reboot after a certain amount of time passes (regardless of app). GPS and Internet are two uses where I will have the screen on for more than just checking email and etc.
Your reply gave me hope and I wiped, reset and reinstalled today. All seemed well and then... auto-reboot. This is driving me nuts. I'm seriously considering reverting back to stock to see if that stops it.
AzmatEQ said:
GPS may be a symptom, but not a cause for me since I typically have GPS off. I find that it typically happens when I'm using a networked based app, like the web browser. Following your post I turned on the GPS, started the navigation app and found that my EVO rebooted after the same amount of time I was experiencing with GPS off.
The more I think about it, it does feel like I just assume that it will reboot after a certain amount of time passes (regardless of app). GPS and Internet are two uses where I will have the screen on for more than just checking email and etc.
Your reply gave me hope and I wiped, reset and reinstalled today. All seemed well and then... auto-reboot. This is driving me nuts. I'm seriously considering reverting back to stock to see if that stops it.
Click to expand...
Click to collapse
Don't go back to stock. I did and it did not fix the rebooting problem. Now I have the rebooting problem and don't have root anymore. Out of the frying can and into the fire.
What's funny is that my phone went through a few days where it would randomly reboot, and this was before I rooted. When it rebooted for the second time in a meeting, I pulled the battery, and didn't put it back in until the meeting was over a few hours later. Don't know if that did anything, but it hasn't rebooted on its own since.
Sent from my blah blah blah blah
Having same issue and my theory is that its sd card related in my case at least... I think it might have to do with froyo netarchy based kernals found in most of the newer froyo roms combined with a slow sd card. (on hardware rev 2)... try flashing a 2.1 rom like fresh 1 or one of the 2.2 roms with an htc based kernal like the am evolution or cyanogen with snap5 or 7.11 (onyl 7based kernal ive tried so far, was panicking because i thought my evo was wrecked). those have both worked for me and i had that issue with 1.3 baked snack, fresh 3, evio and damage control. got random reboots when phone is totally idle, in use, charging or not. evio runs super smooth but the restarts...)
edit for spelling and update roms that gave me the reboot issue.
+1 for random reboots here... it is CERTAINLY more prevalent during GPS use, but I've gotten it without.
Fresh 3 + King BFS#4 got me in a bootloop requiring wipe reflash, standard baked snack 1.5+whatever kernel it comes with has been doing it.
I dig the battery life I was getting... but if undervolting is causing this... ugh.
I'm also getting the boot loop problem. Stock 2.2, all updates.
I've even done the hard reset.. twice!
I tried to follow it with LogCat, but reboot disconnects adb. I was thinking it was the SprintZone app. The P.O.S. app is doing all sorts of non-sense while booting, but eventually it'll reboot around the 11th time and freeze at the "htc EVO 4G" screen.
I wish we could get some resolve here D;
Random Reboots
Thanks for all the input and I'm sorry to hear that I'm not alone, but it is a bit comforting to know I'm not the only one that is frustrated.
I took gleax's advice and I dropped down to the stock 2.1 release found in the thread number 715915. (Sorry, the forum won't let me paste the link.)
I did the required wipes prior to installing the new ROM and I'm still seeing reboots. I now see the OTA update for Android 2.2 and I'm tempted to accept, then send the phone back to Sprint in the even this is a hardware issue. I'd prefer not to, but there doesn't seem to be a way to identify the issue and work towards a resolution. I've tried logcat, but the log seems to start clean after each reboot. That being the case, I don't know how to capture the log leading up to the reboot that would help identify the issue. Any suggestions on a logging tool and where to post to help several of us that are seeing this issue?
Gleax suggested this is may be SD related, so I bought a class 4 card in addition to dropping down to 2.1. I'll give that a shot and try another clean 2.1 install. I'll post the results here in the event they may help others. I'll likely give it a week before unrooting and seeking help from Sprint. I really need a usable device more than I need root access (although both would be ideal).
I had this problem on a very regular basis when I was running OTA 1.32, 2.1 android.. but since I rooted and went to SteelH's stock 2.2, no issues at all. Updated radios when I did that as well.
Hrm, I may have to try flashing to a stock build for awhile... it'll KILL me, but even fully wiping, new radios, cyanogen, still get crazy reboots.
I have tried to do a number of searches and am not finding any relevant information. If this is a known bug, please forgive me.
I am using a red MyTouch 3G Slide, running Cyanogen 6.1.1. I have already flashed back to engineering, down every wipe I see available, and then flashed back to C6.1.1, and the problem persisted. Unfortunately, I was not able to test for it while on the eng build; I'd rather avoid flashing back to that or any stock ROM (having trouble finding a untouched stock ROM, to be honest) but of course if that seems like a good place to start with trouble-shooting I can do it.
This is my first Android phone, and I don't know my way around everything, nor all the lingo yet.
The problem I am encountering is that, seemingly strictly on out-going calls, in some instances upon connection the person I am calling is greeted by heavy distortion of my voice. Switching to speakerphone and then back to handset resolves the issue for the duration of that call. To make things trickier, the contacts affected by this are ALWAYS affected by it; I have to switch to speakerphone and then back, and suddenly the call is crystal clear.
This has been verified with multiple independent contacts who do not know each other; they are not conspiring to prank me. Furthermore, I have noted the problem affects both land-line and mobile contacts. However, it does not affect all of my contacts.
This does not seem to affect incoming calls.
Any ideas?
Borteeo said:
I have tried to do a number of searches and am not finding any relevant information. If this is a known bug, please forgive me.
I am using a red MyTouch 3G Slide, running Cyanogen 6.1.1. I have already flashed back to engineering, down every wipe I see available, and then flashed back to C6.1.1, and the problem persisted. Unfortunately, I was not able to test for it while on the eng build; I'd rather avoid flashing back to that or any stock ROM (having trouble finding a untouched stock ROM, to be honest) but of course if that seems like a good place to start with trouble-shooting I can do it.
This is my first Android phone, and I don't know my way around everything, nor all the lingo yet.
The problem I am encountering is that, seemingly strictly on out-going calls, in some instances upon connection the person I am calling is greeted by heavy distortion of my voice. Switching to speakerphone and then back to handset resolves the issue for the duration of that call. To make things trickier, the contacts affected by this are ALWAYS affected by it; I have to switch to speakerphone and then back, and suddenly the call is crystal clear.
This has been verified with multiple independent contacts who do not know each other; they are not conspiring to prank me. Furthermore, I have noted the problem affects both land-line and mobile contacts. However, it does not affect all of my contacts.
This does not seem to affect incoming calls.
Any ideas?
Click to expand...
Click to collapse
That is a very strange issue. First step is to get CR_Mod OTA from the development section here, and flash that through clockwork recovery. See if it happens on that. CR_Mod is just the rooted stock ROM with wifi tether and superuser app, that's it. If it still happens there, then I would try getting a replacement SIM card from t-mobile, it MIGHT be a bad SIM, although that seems less likely.
Thanks mate! Actually, I'm running it on Wind Mobile in Canada. Currently a friend is borrowing the phone to test; if he encounters problems then I'll try the ROM you have suggested and report back, otherwise it's fresh SIM time. Thank you for responding.
I've been seeing this problem for a few weeks now, with several different ROMs, including the original rooted stock ROM now. In nearly all of my recent calls, I get disconnected one or more times with the message "Call disconnected" and a "Dismiss" button. I'm thinking that this is because of my EVO and not the other side, since usually if they accidentally hang up or something the call just ends without a message box. As far as I can tell, I have good reception (at least according to the bars), and this is happening at home, where I've not had the problem before.
Does anyone know what could be causing this? My wife's EVO is not rooted, and she does not seem to be having this problem. But then again, I've not had the problem until fairly recently either. I've tried updating my profile and PRL with each new ROM, but it doesn't seem to have made a difference. Anyone have any suggestions as to how to stop this from happening?
Go into the settings menu andbupdate both your PRL and your profile. That *should* help with reception related issues.
posting & replying via the XDA Premium app.
Unfortunately, I've tried both of those things. I just did some testing today, and it seems that my phone is unable to stay connected during a phone call for more than five minutes before disconnecting, even if I don't touch the phone and just leave it sitting on a table.
Any other ideas? As far as I know, I haven't ever flashed my radio away from its default (2.15.00.11.19), and I'm currently using the leaked stock gingerbread ROM (build number 4.12.651.1 CL41771 release-keys and kernel 2.6.35.10-gaa602b7 [email protected] #1).
Maybe it's time to unroot and contact Sprint?
You can try downgrading from 2.15.00.11.19 to 2.15.00.09.01. You can download it from http://www.mediafire.com/file/jyedjkp1bm5amwm/EVO_Radio_2.15.00.09.01.zip
Afterwards, go into recovery, wipe cache & dalvik cache then flash the zip. You will be taken to the radio update screen and appear to hang. don't worry or get impatient. After it is finished, you will reboot into recovery and see the words "clearing cache" at the top of the screen. Simply select reboot and then you will boot to your homescreen. The initial boot will take a tad longer since it will be rebuilding the dalvik.
Hmm... I'm hesitant to downgrade my radio because my wife has an EVO with the same radio version number and hers doesn't have this problem. Granted, she is not rooted...
I understand. I've downgraded and upgraded everything several times for testing purposes and troubleshooting purposes and have never had a problem. The only hing about flashing radios is patience and not to pull the battery. Anyway, you can always call Sprint and see if they can troubleshoot it for you from their end.
posting & replying via the XDA Premium app.
I would contact sprint @ 877-809-6696 (advanced tech supp). Ask them to push a full reprovision to your device. See if that helps any. I was having issues when when on the airave, I was unable to receive incoming calls. This corrected it. I did try all the other steps listed above without any success.
This is interesting. I unrooted to test things out before calling Sprint, and the problem went away. I was able to stay connected for an hour (where before I couldn't last longer than 10-15 minutes). Yay, fixed, right? So, I rooted again and didn't install any ROMs or anything, just rooted, and the problem came back.
So, I have a solution, but I don't like it very much because it means I need to stay unrooted. Anyone have any idea why simply rooting the phone with Unrevoked 3 (and doing nothing else) could cause calls to disconnect? I'd love to be able to root again, but I can't deal with a phone that randomly disconnects all the time.
I am interested in this as well as I am rooted using unrevoked and get disconnected as well. I do find that it mainly happens though talking to people who have service on AT&T.. Quite wierd. All I hear is a beep then disconnected. This happens when I first place a call and it rings once or twice then beep, disconnected...
This may not be related to rooting. I'm still communicating with Sprint about this issue, and along they way they replaced my phone entirely, and the problem is still happening. Very frustrating, but it makes it very clear that the problem actually has nothing to do with the hardware. I'm pretty sure there is some network configuration problem on their end now. I'm waiting to root my new phone until this issue has been resolved. It is killing me!
KingFunderberk said:
This may not be related to rooting. I'm still communicating with Sprint about this issue, and along they way they replaced my phone entirely, and the problem is still happening. Very frustrating, but it makes it very clear that the problem actually has nothing to do with the hardware. I'm pretty sure there is some network configuration problem on their end now. I'm waiting to root my new phone until this issue has been resolved. It is killing me!
Click to expand...
Click to collapse
So whats the final call on this ..?
Is it Rooting , Is it network .. i am too getting psyche with this .
I'm pretty sure it is not rooting. But I don't yet know for certain what it is. Sprint thought there might be something wrong with the antenna on my phone, but they had already replaced the phone, so I think that is unlikely. They gave me a femtocell range extender to use in my house. Basically, I plug it into my broadband connection, and it is like having a mini cell tower in my house, giving me a very strong connection. Sure enough, when connected to that, I haven't had any calls drop. However, my phone still sometimes doesn't connect to the femtocell and instead connects to some other tower for some reason. My wife's phone doesn't do this, so I still think there is something wrong with my phone. I may contact Sprint again about this. ...sigh...
What is your area some area evo don't work properly like on rahim yar khan in this time connection don't work properly some signal drop and some time up i sure after few day signal work properly then problems will be solve.
My phone EVO is doing this now as well. Has anyone heard/read a solution?
greg_99 said:
My phone EVO is doing this now as well. Has anyone heard/read a solution?
Click to expand...
Click to collapse
I am having the same issue, out of the blue. No problems up until a few days ago. I'm wondering if it is maybe an issue with a certain version of the Evo. I have a version 002. Thoughts?
Greg_99 any progress on what might be causing this issue?
I posted this in NilsP's Business GingerSense thread, but don't think it's a ROM issue, more of a Google Talk issue. Running the 2.0 version of that ROM.
The issue is where Google Talk shows all your contacts as Offline after a period of say five to ten minutes, maybe shorter than that. I'll be messaging someone, and after a few minutes when they haven't responded, I'll wake my phone and open GT. All the contacts are Offline. A simple sign out/sign in fixes that, and the usual contacts show Online or Away.I've noticed this all week, so I'm thinking it's a GT issue, but I've never had it happen before.
Don't want to have to sign out/in every time I want to use it. Cleared GT cache, fix permissions, multiple wipes of data/system/cache/boot/dalvik/user data before each ROM install, and haven't had this before now.
Thoughts?
EDIT: After playing, it happens when switching from 3G to WiFi and vice versa, so maybe it is a ROM thing...?
i'm having the same issue. noticed after my gingerbread OTA update from verizon.
Droid 2.
It seems to happen a few minutes after logging on.
I also have that issue with Gtalk. After some time all contacts appear to be offline, but only when I'm on data connection and not on wifi.
There is still no solution for this?
Cheers!
carapauzinho said:
I also have that issue with Gtalk. After some time all contacts appear to be offline, but only when I'm on data connection and not on wifi.
There is still no solution for this?
Cheers!
Click to expand...
Click to collapse
Me too. Anyone was able to do something?
Well I've since moved on, and haven't noticed it on other ROMs. Right now I just tested toggling Wifi on and off, and the contacts would appear offline, then come online once 3g or wifi connected.
I'm thinking in my case, it was that version of the ROM I was running at the time.
Sent from my ADR6300 using xda premium
Just a thought, check any task killers / managers and make sure talk is unchecked. I had the same problem a long time ago and ATK was the culprit. Haven't had the issue since and I have used almost every Rom possible at one point or another
Sent from my Incredible Stock+v2.6 Ginger Tiny
dragon droid said:
Just a thought, check any task killers / managers and make sure talk is unchecked. I had the same problem a long time ago and ATK was the culprit. Haven't had the issue since and I have used almost every Rom possible at one point or another
Sent from my Incredible Stock+v2.6 Ginger Tiny
Click to expand...
Click to collapse
True. Right after I rooted over a year ago, I had an issue with the alarm clock not going off intermittantly, and coincidentally I was using ATK at the time. After reading that ATK could be the issue, uninstalling it fixed the issue. Since then, I don't actively kill tasks, but I do have System Panel installed just in case.
I'm running Stock+ v2.6, and since moving on from v2.0 of NilsP's ROM where I had the initial issue, I haven't noticed/had the problem.
RMarkwald said:
True. Right after I rooted over a year ago, I had an issue with the alarm clock not going off intermittantly, and coincidentally I was using ATK at the time. After reading that ATK could be the issue, uninstalling it fixed the issue. Since then, I don't actively kill tasks, but I do have System Panel installed just in case.
I'm running Stock+ v2.6, and since moving on from v2.0 of NilsP's ROM where I had the initial issue, I haven't noticed/had the problem.
Click to expand...
Click to collapse
Hi,
Me and the other user are I9000 users. No task killers. We're trying to figure out if its a stock / custom ROM issue (since we're both using the same ROM), or some app forcing GTalk to sign out, or even a network problem (we both use the same mobile operator).
Thank you both for your input.
If you're on a stock ROM (you're both rooted right?), back up your ROM and flash another just to see if it happens in something different.
RMarkwald said:
If you're on a stock ROM (you're both rooted right?), back up your ROM and flash another just to see if it happens in something different.
Click to expand...
Click to collapse
Yes, we are.
The thing is that it seems to me that it happened only after XXVJR (meaning it happened to me in XXJVS and XXJVT, and now we're already at XWJVU, all these being Samsungs "leaks"), and I have a friend with XXJVS that works just fine.
I even tried flashing a stock ROM, to see if it happens again. Testing that one now.
Thanks for your advice.
Same problem here.
Although I have not tried it with stock non rooted phone...
I'm having the same problem on a stock rooted Motorola Photon. Very annoying to have to sign out and back in to see who's online. Hopefully someone comes to the rescue with a solution.
Hi,
The only thing I could find is that the problem is, indeed, NOT in the custom ROM's. It's google's problem.
The only way I could get by was with an alternative IM. And, for me, the better is Trillian (taking battery, performance, etc. in consideration.)
I updated my software which included an updated gtalk with video..so far so good.
crs77 said:
I updated my software which included an updated gtalk with video..so far so good.
Click to expand...
Click to collapse
Mine got better with one of those. But it ended up all the same.
DarkSorcerer said:
Me and the other user are I9000 users. No task killers. We're trying to figure out if its a stock / custom ROM issue (since we're both using the same ROM), or some app forcing GTalk to sign out, or even a network problem (we both use the same mobile operator).
Click to expand...
Click to collapse
I am having this issue too. I have had it since the beginning, when I had the preinstalled stock rom, I had it with all the other stock roms I flashed, I had it with all the versions of Talk I tried (those which supported video calls), I had it with all the other customs roms I tried (Simplicity, CyanogenMod, MIUI). I never used any task killer. For these reasons I am strongly convinced this is a Google Talk related bug.
Some more details about the problem:
after a few minutes after having logged in, contacts are shown offline on Android while they appear online on the desktop client;
despite their offline status I still receive messages from them and as soon as I answer only that contact appears online while the others keep being shown offline;
signing out and back in fixes the problem temporarily, but it happens again after a few minutes.
What surprises me is how come very few people seem noticing it or being annoyed by it? How come a huge bug like this has been out for so long and Google hasn't fixed it yet? All the posts I have seen reporting this problem on Google Talk Help Forum have been ignored.
Exact same problem with my I9100, Gtalk with video. Very annoying.
I have the SGS i777 (Samsung Galaxy S2 on AT&T), and just recently (since late February) started experiencing the same issue. When on WiFi, it doesn't appear to be an issue, only when not on WiFi, particularly if I have just recently turned off WiFi.
Other "friends" show me as "Away", so I am connected.
This is bone stock 2.3.6 Samsung official ROM (never rooted UCKK6).
I tried crawling a bit through the logs (aLogCat output), filtering for "[Tt]alk", but I can't make enough heads or tails about where the failure might be (not being an actual developer), other than lots of messages get created. I'll see if I can't figure something more useful out about it.
A hard reset with no apps installed has the same problem. Though I've noticed that the problem appears to get "worse" as the phone "ages" - namely, hard reset fixes the problem, but it slowly (over days) gets worse and worse.
Update: I have not noticed this issue at all since getting the official Samsung/AT&T ICS build (IML74K.CLE5).
Google Talk failing for toooo loooong
Hi there,
I'm a cyanogen 7.1 (stable) android user, and I just want to join myself to every other person who's affected by this issue.
I'll leave here some links to other places discussion exactly the same issue:
code.google.com/p/android/issues/detail?can=2&start=0&num=100&q=gtalk%20offline&colspec=ID%20Type%20Status%20Owner%20Summary%20Stars&groupby=&sort=&id=24242
You may check this thread: groups.google.com/a/googleproductforums.com/forum/#!topic/chat/6m0YqHoiIDg
Until now, I wasn't also able to find any clue to what the cause may be.
Starting to suspect that's something on Google's side, not android/rom itself.
Maybe something to do with our google accounts' settings?
Are there any news about this issue? I'm having the same problem.
Hey All,
So, I'm having a weird issue with my T-989. I get intermittent audio loss upon making and receiving calls. Refer to the following examples:
Call comes in; I swipe to answer..."Hello...Hello...Hello....-__-" I can not hear the person on the other end of the call and they are un able to hear me. I've asked countless people that call me on a daily basis on their experience when this happens. They say the call connects but no audio; they then get confused and hang up if I don't end the call my self. Normally I'm the one that ends the call now and I'll call back....sometimes I hear ringing and I know that it'll work ok.
Sometimes, the call log counter starts....but I hear no ringing, HOWEVER the person I'm calling is actually being called and tries to answer the phone...but because I don't hear the ringing...I don't even realize that the phone has established a connection.
Sometimes....everything works fine. I'll answer the phone and it'll work like a charm or I'll make a call and it'll work like a charm. Two hours later...same weird issue.
I wanted to know if people had similar problems.
It's getting increasingly annoying at this point. At first I thought maybe it was my service. Then I thought it was my ROM / Radio. Honestly, I know people who have the same service and plan as me.
Phone is running P.A.C 22.0.1
This issue happened on older versions of which I completed wiped and re installed newer versions of P.A.C; it happened on AOKP; happened on Paranoid Android.....
I'm guessing the only thing I haven't tried changing is the Radio that comes with each ROM.
I am on the T-Mobile Pre Paid Unlimited Talk / Text w/ 500mb Data plan. [I work in data centers, unlimited INTERWEBS!]
Anyone else have similar symptoms? I'll be getting the S4 soon, but I wanted to resolve this issue before hand because I'll be giving it to a friend.
Thanks in advance for any help! :victory::highfive:
I have been living that same issue for months, between several ROMs and kernels and radios. Ive learned to use this process......answer call, wait 3 seconds, then saying "hello". I know, its silly.
I have noticed its seems worse when answering calls from others running aosp (cm10)roms.
I've have not tried any touchwiz ROMs
Sent from my cm_tenderloin using xda premium
Waiting 3 seconds and then saying hello works? For me the issue happens when placing calls as well. I installed the newest P.A.C last night when I posted the OP, so far no problems. I'll update again if I have any issues moving forward.
What radio are you using?
Now - UVMC6
As I said, as of yet, I haven't had any issues. Let's see over the next couple of days....