Related
Is there a way to tell if you dropped a call? I drop one a week but idk if its my friend with his new headset or what. Is there a way to tell? Before lately I don't think I've had a dropped call in 2 mo since I had my cappy. Last few weeks I've been running ultimate rom v 5 something. Before cognition 2.6 and above. All help is appreciated. And how often do you guys drop calls? And this is inside my house. Lots of windows. Oh and one more thing. I have noticed texts coming a minuet before or during the few drops if I remember right. But I have also texted myself and had some1 text spam me on the phone and nothing happened.
Thx
Sent from my GT-I9000 using XDA App
???
Sent from my GT-I9000 using XDA App
JJ133169 said:
Is there a way to tell if you dropped a call? I drop one a week but idk if its my friend with his new headset or what. Is there a way to tell? Before lately I don't think I've had a dropped call in 2 mo since I had my cappy. Last few weeks I've been running ultimate rom v 5 something. Before cognition 2.6 and above. All help is appreciated. And how often do you guys drop calls? And this is inside my house. Lots of windows. Oh and one more thing. I have noticed texts coming a minuet before or during the few drops if I remember right. But I have also texted myself and had some1 text spam me on the phone and nothing happened.
Thx
Click to expand...
Click to collapse
Unfortunately, I can't help with a method to see what calls have been dropped.
I have been experiencing dropped calls since upgrading to the official ATT 2.2 build. In the last week I've had almost all of my 'long' calls drop on me. Looking at my call log, it appears that anytime I have a call that lasts >20 minutes it gets dropped.
Lots of dropped calls here too after 2.2 (Cognition 4 & 4.1). Rarely had A problem before.
Sent from my SAMSUNG-SGH-I897 using XDA App
Yes. I am running the stock ATT 2.2 rom. Loaded it the day it came out. Since then, I have had several (8 - 10) dropped calls. Before that, none. I am fairly sure it is my phone because it can occur reguardless of who I am talking to or what time of day. Length of the conversation doesnt seem to matter either.
I am experiencing this as well. Frequent dropped calls recently.
Thanks guys. This helps, my gf just got a captivate, 11XX build with 2.2 pre-installed. So I'm going to root it and either put in a new modem or a new ROM all together because she likes it but doesnt due to "lack of signal" and "dropped calls" so sounds to me like the KB1 modem isnt all that good....
Another question here, JW in keis can you go from 2.2 stock to 2.1 stock? or does it not let you downgrade ? ( I know you can with oden, Just wondering if there is a AT&T supported way of downgrading...?)
since i flashed the ugjl2 modem i haven't had any more problems
kingmurry said:
since i flashed the ugjl2 modem i haven't had any more problems
Click to expand...
Click to collapse
What ROM and kernel are you running with that modem??
thanks!
if it's happened after a flash, you may be running an incompatible modem.
Me and my girlfriend, both on our stock froyoed Captivates, constantly have calls dropped by our phones since the upgrade. We have both done a factory reset and rooted after the upgrade. Any help or explanation is appreciated.
Also, her random shutdowns unfortunately continue...
Sent from my SAMSUNG-SGH-I897 using XDA App
ruger94 said:
What ROM and kernel are you running with that modem??
thanks!
Click to expand...
Click to collapse
firfly 2.6 suckerpunck #59
I recently flashed the stock rom that is rooted with hsupa and sideloading enabled onto my Inspire, and over the last 2 days I've noticed that sometimes when I try to make a call, my phone just hangs up. It's weird, because text and data works perfectly fine, it's only when I make phone calls. Anyone else notice this problem with a rooted rom, stock or not?
sliderocket22 said:
I recently flashed the stock rom that is rooted with hsupa and sideloading enabled onto my Inspire, and over the last 2 days I've noticed that sometimes when I try to make a call, my phone just hangs up. It's weird, because text and data works perfectly fine, it's only when I make phone calls. Anyone else notice this problem with a rooted rom, stock or not?
Click to expand...
Click to collapse
Yep, happens to me all the time. Internet doesn't always work either. I "fixed" the problem by setting it to GSM only mode. Now I only have EDGE internet.
brandon827 said:
Yep, happens to me all the time. Internet doesn't always work either. I "fixed" the problem by setting it to GSM only mode. Now I only have EDGE internet.
Click to expand...
Click to collapse
Are you on the same rooted stock rom, or something different? I don't seem to remember having this problem when I was just on pure stock AT&T with no root. Somewhat annoying, as I'll have to place a call 3 or 4 times to get it to go through, but what's really annoying is that it is so sporadic I can't gauge when it'll happen!
sliderocket22 said:
Are you on the same rooted stock rom, or something different? I don't seem to remember having this problem when I was just on pure stock AT&T with no root. Somewhat annoying, as I'll have to place a call 3 or 4 times to get it to go through, but what's really annoying is that it is so sporadic I can't gauge when it'll happen!
Click to expand...
Click to collapse
I've noticed this at multiple times, but haven't been able to narrow down what's causing it. I was running Revolution 1.15, and I think it started when I applied the .16 performance patch. It got so bad last night I couldn't make/receive calls for hours. I did a full wipe an reinstalled 1.15 and all has been well the last 24 hours. I just flashed the 2.1 patch but we'll see what happens. Note: Not only can you not make calls when this is happening you won't be able to receive calls either. It does appear to most often happen when bouncing between networks (HSDPA, UMTS, Edge, etc)
homeslice976 said:
I've noticed this at multiple times, but haven't been able to narrow down what's causing it. I was running Revolution 1.15, and I think it started when I applied the .16 performance patch. It got so bad last night I couldn't make/receive calls for hours. I did a full wipe an reinstalled 1.15 and all has been well the last 24 hours. I just flashed the 2.1 patch but we'll see what happens. Note: Not only can you not make calls when this is happening you won't be able to receive calls either. It does appear to most often happen when bouncing between networks (HSDPA, UMTS, Edge, etc)
Click to expand...
Click to collapse
Man, I'm glad I'm not the only one having this problem. I thought my phone was defective at first, and now I don't feel so crazy anymore. My sister was furious with me, I had to pick her and her boyfriend up from DIA yesterday to take her to Copper Mountain to snowboard with my girlfriend and myself, and she called me 4 times and I didn't receive a single one. I wonder if it has anything to do with HSUPA being enabled on the phones, but at this point I'm just ready to give up root and go back to stock. I don't make tons of calls, but I'd like to be able to when I need to, and for my phone to not hang up on me in the middle of one. I have noticed though it's particularly bad for me when I'm on bluetooth.
I was also having those problems
I am using Revolution 4G 2.1. I'm in the process of trying to get the problem figured out. Stock rooted rom had problems for me because you couldn't set it to GSM only, and that's the only way I've found to make the phone reliably work as a phone.
If anyone can figure it out, I'd love to know what causes it. I've been poking around myself, but haven't come up with anything worthwhile. I suppose I'll flash a different rom and try that.
Sent from my Desire HD using XDA App
Anyone found any clue as to why this happens? I've searched the dev forums but nobody seems to mention this, which makes me wonder if most people have this problem.
Sent from my Desire HD using XDA App
I have never had this problem. Running a rooted stocker.
Sent from my Desire HD using XDA App
It happened to me again last night. Still had data but lost the ability to make/receive calls. I switched network to GSM only, the data switched to EDGE, and i was able to make/recieve calls. Turned back to GSM/WCDMA, no calls. Rebooted, no calls. Turned back to GSM only, calling functionality returned. I did another full wipe, installed AR 2.1, sound fix, apache 1.6 kernel, and calling is restored when connected to HSDPA/WCDMA. Has been working fine for the last 12 hours. I'll keep you updated. I don't know why it's doing this, and it doesn't make sense as to why a wipe would fix it. The first time this happened I was runing the stock radio. Last night when it happened i was running the recommended radio in the AR thread (M2). I've now switched back to stock this time...let's see what happens
Edit: I am also glad to know I'm not the only one having these issues...maybe someone a LOT smarter than I am can figure it out. It's annoying to have to have a slow data connection to have a reliable voice connection. The last Android I had (LG GW620 Eve), also did this from time to time, but I just blamed it on the fact that it was a POS. My voicemail actually went like this "This is Greg. I probably have no idea you called me just now, so please leave a message and I'll get back to you"
Edit: mike1986 (android revolution developer) just chimed in in his thread and stated these issues should be fixed in version 3.0 set to be released soon. Is anyone else that's having these problems NOT running Revolution?
sliderocket22 said:
I recently flashed the stock rom that is rooted with hsupa and sideloading enabled onto my Inspire, and over the last 2 days I've noticed that sometimes when I try to make a call, my phone just hangs up. It's weird, because text and data works perfectly fine, it's only when I make phone calls. Anyone else notice this problem with a rooted rom, stock or not?
Click to expand...
Click to collapse
I had this problem when I first rooted (running Inspire 4G Stock Rom w/Root, HSUPA, and Sideloading from the development section) I installed Android Revolution 2.1 and it went away.
I know from my captivate days that sometimes a ROM just hiccups and a fresh flash can fix the issues. I don't know if this is the same with HTC, but it's all android so It's plausible.
I upgraded using the LG tool and everything went fine. Setup the ROM from scratch and all was well but then I kept having these issues so I shelved the G2X and went back to Sensation UNTIL T-mobile released what I thought would be a newer official build.
The fact that they are putting out V21E as the official GB build is downright sad and pathetic. After many months of promising an update they can't even get a release out there that's not busted. I know it is possible but it seems only HTC and perhaps Samsung know how to write software...my old Droid Incredible, friends Evo 4G and now Sensation are rock solid and everything just works. Samsung Nexus S and Galaxy variants also just mainly work.
I had these issues for the 24 hours I used the G2X with V21E - I got fed up and stopped using it but I'm sure there are others.
- Several times phone rang/vibrated due to incoming call so I answered the call which worked BUT the phone kept vibrating like it was still ringing even while I'm talking to the other person. Only solution is to hang up call and call back. Doesn't happen every time but happened quite often.
- Bluetooth is buggy as hell. Sometimes a device that's paired won't connect unless I powercycle the BT on the phone.
-- I was listening to music once with A2DP headset and a call came in. I answered the call and everything was great. I hung up the call and now no BT audio would come through the headset or even the phone speaker no matter what I did. Turn off BT/turn on, etc. Only solution was to powercycle
--Later on was using the phone, connected my paired A2DP headset to the G2X and almost instantly the phone screen turned off and it locked up. Had to pull the battery
- Weird issue with apps like (edit: Google's podcast app not HTC) Listen. Will play for a while and then all of a sudden stop playing and nothing I can do will get it to play again unless I uninstall/reinstall the app. Never happened on Froyo or CM7.
- Gets very warm - battery app showed the temp being well over 35 degrees celcius most times I looked and I wasn't even using the phone much.
- Was using the Google reader to read articles and all of a sudden the phone started slowing down and then it just froze with the screen on. Nothing I did would get a response from it. Power + vol up didn't work. had to pull the battery.
I mean this is freaking ridiculous. I have the Sensation setup with the exact same apps, launcher, settings, everything and I have ZERO issues. This is simply crappy software and LG should be ashamed.
FWIW, CM7 latest nightlies I never had ANY of these problems but A2DP doesn't work on CM7 so can't use it daily. Once A2DP starts working on CM7 I might give it another shot.
I'm definitely done with LG for a while.
mobilehavoc said:
- Several times phone rang/vibrated due to incoming call so I answered the call which worked BUT the phone kept vibrating like it was still ringing even while I'm talking to the other person. Only solution is to hang up call and call back. Doesn't happen every time but happened quite often.
Click to expand...
Click to collapse
This happens a lot in Stock Froyo for me. Sad to hear it's not fixed in GB!
Lightning Blue said:
This happens a lot in Stock Froyo for me. Sad to hear it's not fixed in GB!
Click to expand...
Click to collapse
Weird, I had reboots and SOD problems in Froyo but otherwise I had NO other issues in Froyo - when the phone wasn't rebooting or turned off it worked perfectly. This GB build has way more problems for me than Froyo.
Solid here..... Not a bad update imo
Same here I haven't experienced any of these problems, not even in Frito either. The update overall has done it all for me. I would try reinstalling the update again if I were you
Sent from my LG-P999 using XDA App
Those of you with problems should try doing a Factory Reset.
Sent From My G2x Running CM7
moshe22 said:
Those of you with problems should try doing a Factory Reset.
Sent From My G2x Running CM7
Click to expand...
Click to collapse
I did, note how I said I set it up from scratch. There is BOUND to be issues with this because the kernel is the same as froyo - many of the problems were caused by the kernel and since that hasn't changed, how would the issues be fixed? CM7 might fix issues because it's a different kernel.
My phone is now freezing up!!! WTH! Three times since the update in less than 12 hours. I wanted to call Tmobile customer service to cancel my Value Plan i switched to a day earlier but couldn't. I had to remove the battery and reset the phone before making my call.
I told them I didn't want to spend $200 for the migration fee and then be stuck in a new 2 year contract with this G2X phone and pay a $200 if I leave that Value Plan contract or spend full price on a phone to replace this junk. I went back to my 1500 mins, unlim text, 5 gb data for $79.99 plus %15 discount on that. The person I spoke with was surprised this new update was having issues. She knew this phone had bugs because her friend had this phone. She also knew they took it off their website and just brought it back with Gingerbread.
She said she will make a note in my account to give me a full upgrade credit because I am on my second phone and I told her that I was going to leave to Sprint! Hopefully my phone wont cause me to smash it before the Samsung Hercules comes out on Sept 26.
grenademasta said:
My phone is now freezing up!!! WTH! Three times since the update in less than 12 hours. I wanted to call Tmobile customer service to cancel my Value Plan i switched to a day earlier but couldn't. I had to remove the battery and reset the phone before making my call.
I told them I didn't want to spend $200 for the migration fee and then be stuck in a new 2 year contract with this G2X phone and pay a $200 if I leave that Value Plan contract or spend full price on a phone to replace this junk. I went back to my 1500 mins, unlim text, 5 gb data for $79.99 plus %15 discount on that. The person I spoke with was surprised this new update was having issues. She knew this phone had bugs because her friend had this phone. She also knew they took it off their website and just brought it back with Gingerbread.
She said she will make a note in my account to give me a full upgrade credit because I am on my second phone and I told her that I was going to leave to Sprint! Hopefully my phone wont cause me to smash it before the Samsung Hercules comes out on Sept 26.
Click to expand...
Click to collapse
Looks like I'm not the only one.
I just got T-Mobile to send me a replacement G2X on Thursday so will see if I have same issues. At this point I truly believe I have a hardware issue.
Sent from my thumbs to your eyes using a Sensation 4G
I can't help to think that theres some app people are installing that's causing some of these issues. My phone has been perfect in operation, but froyo was great too.
People need to understand that the tegra 2 has some compatibility issues as well with some apps.
Uninstall everything 3rd party, use the phone for a day and see what probs you have.
Sent from my LG-P999 using XDA App
I've had issues after a factory reset and not installing anything. Further I'm not keeping a phone that limits the apps I can install. I've got the same exact set of apps on my Sensation and it works perfectly. Its not like I have a ton of apps either, just the ones I need.
Sent from my thumbs to your eyes using a Sensation 4G
No problems so far. I love GB. My bluetooth now syncs with my radio which it wasn't doing with Froyo.
i've had none of these issues. i have had issues like this in the past with a bad flash.
Well I'm getting a replacement G2X that either will come with the update (doubt it) or I'll use OTA to get the update so if after that it doesn't work. I give up.
mobilehavoc said:
I'm definitely done with LG for a while.
Click to expand...
Click to collapse
OK.
I hope you have better luck with your new phone. The Sensation is a piece of garbage according to many. It is all up to luck apparently. It is weird how some have no issues and some have continual issues.
I'm starting to think I have bad hardware too, I'm having more problems with GB than I did with Froyo!
What did you tell them to get a warranty exchange? I was thinking of calling and just overwhelming them with info.
Just worried the replacement device could be worse!
I can't adjust the damn touch key brightness. It is making me crazy. Also the screen is not as responsive as it was with Froyo.
and of course the battery still sucks, but apparently android is a flawed system that just sucks battery for no reason at all. I hope the google/android folks get their stuff together one of these days. I really miss my HD2 battery life. You would think a bigger battery and newer operating system would be more efficient, but crappy battery life seems to be the norm. The tmobile guber that sold me my phones assured me I would get the same life out of the battery, but he was very wrong.
Lightning Blue said:
I'm starting to think I have bad hardware too, I'm having more problems with GB than I did with Froyo!
What did you tell them to get a warranty exchange? I was thinking of calling and just overwhelming them with info.
Just worried the replacement device could be worse!
Click to expand...
Click to collapse
They make you go through troubleshooting so I just answered their questions and she said, fine we'll send you a replacement. Just tell them you have a G2X that has been rebooting/turning off and that even after the update it still happens. That's what I did.
mobilehavoc said:
Looks like I'm not the only one.
Click to expand...
Click to collapse
Nope you're not the only one. My G2x today decided for the first time to freeze while I was using it. Plus with this update I get less signal than I had before.
This phone and how tmobile handled it in my situation left a foul taste in my mouth forcing me to switch to Sprint and the HTC EVO 4G. So far its been a happy switch, my phone hasn't locked up, no reboots, doesn't overheat and battery lasted me about 30 hours with moderate use (web browsing for about 30mins, 1hr phone call, and about 2hrs overall on xda) also had WiFi on plus Bluetooth.
Sadly I lost 4G data since Sprint doesn't have any 4G towers in my area yet. But @ $110 a month for unlimited everything and no data throttling it was a good move, plus nice to have signal while at home. WiFi calling worked whenever it felt like so it was no more reliable than plain cell service.
Sent from my PC36100 using XDA App
So my thunderbolt has been overall great but i have this problem where if someone calls me they cant hear me but i can hear them and i can hear myself in my own speaker. is it a setting problem? i also flashed the latest radio for GB on the Infected Synergy Rom.
mistersikee said:
So my thunderbolt has been overall great but i have this problem where if someone calls me they cant hear me but i can hear them and i can hear myself in my own speaker. is it a setting problem? i also flashed the latest radio for GB on the Infected Synergy Rom.
Click to expand...
Click to collapse
I've literally had that same issue on almost every device I've used on Verizon and Alltel at some point. Some areas it's happened a lot in, other almost never. I'm hesitant to say it's the device because of my experience. I think it's something quirky with the network. For me, if I just call them back it works fine. It used to happen almost every time I called my Mom. Second call was a charm though. Then it mostly stopped... about the time she got off that damn Motorola and onto a BlackBerry... but it still happens occasionally.
yeah =[ ive never had this problem though and its constantly doing it because i was originally on cm7 but it started to i flashed another rom and it worked for a couple of calls at first but now no calls go through and im afraid to call verizon since im rooted but idk what to do =[ thanked you btw
mistersikee said:
yeah =[ ive never had this problem though and its constantly doing it because i was originally on cm7 but it started to i flashed another rom and it worked for a couple of calls at first but now no calls go through and im afraid to call verizon since im rooted but idk what to do =[ thanked you btw
Click to expand...
Click to collapse
eh.... I've called them with issues on both my rooted HTCs. It's never been a problem. I've talked to guys there about their rooted Androids. If they tell you to do this or that, either play super-stupid or BS your way through it and get them to put a work order out to check out things on their end. If that doesn't solve it, then it's time to go back to stock and exchange some hardware or something.
i was just experimenting and it turns out after like 25 secs they could hear me but im still lost on why
Hi so I was wondering if this has happened to anyone else. Today my phone was in an area that it always has 4G and signal and for some reason I went to use the phone and for about three minutes it had no signal and data. I rebooted the phone and everything is fine now and this is the first time this has happened on stock everything(Waiting til ICS). Glitch?
oh snap
could it be the dreaded LOS???
Yeah actually it's happened to me about three times. Twice in the Phoenix area with full 4G and once in the Yuma area, edge only.
What it's this you speak of Shabby?
Sent from my SGH-T769 using XDA
was a huge deal on the epic 4g touch, official they never resolved it.. there was a fix done via the kernel though that allowed it to be fairly non-existent. first time ive ever heard of a gsm samsung having issues like this tho, its usually just the cdma phones that get kicked in the nuts
http://community.sprint.com/baw/thread/76962?start=0&tstart=0
as you can see that is a rather long thread. the good news is i believe they did end up patching it for gb to where it didnt happen, however on their leaked ics build we have it seems they "forgot" that patch
Yea well hopefully ICS will come out for this phone and if not by the time the GS3 comes out I will switch even if i have to pay full price! lol I think this problem happened twice for me so far...