Ok im starting to go crazy now. I had a galaxy nexus that was rooted and started getting dropped calls after 30min on the dot. I thought it was something i did to the phone so i went and got an S3. rooted with liquid smooth (stable) ROM and nothing else. Now im having the same problems. Got a new sim card and still having dropped calls after 30 min. Someone please help with this I am getting so frustrated with this. Im going to activate my untouched thunderbolt and see if it follows. I really dont wanna go back to a stock ROM on the S3 cuz i do not like the layout. Again any help would be great. Thanks.
mverzal said:
Ok im starting to go crazy now. I had a galaxy nexus that was rooted and started getting dropped calls after 30min on the dot. I thought it was something i did to the phone so i went and got an S3. rooted with liquid smooth (stable) ROM and nothing else. Now im having the same problems. Got a new sim card and still having dropped calls after 30 min. Someone please help with this I am getting so frustrated with this. Im going to activate my untouched thunderbolt and see if it follows. I really dont wanna go back to a stock ROM on the S3 cuz i do not like the layout. Again any help would be great. Thanks.
Click to expand...
Click to collapse
I think is a Samsung Radio issue... I don't use my SIII anymore because of it.
The S 3 radio isn't the best your location can compound the problem. I haven't experienced drop calls other than in the obvious dead zones.
I have heard the radio wasnt the greatest but 30 min exactly every time? Thats gotta be something different. Could the way i unlocked have caused this or the ROM that was installed caused this? When i had my nexus rooted, i didnt have any issues till i messed with the radio. The S3 i didnt touch the radio unless it was built into the ROM. Liquid smooth (stable).
AOSP ROMs isn't as good signal wise as the Touchwiz ROMs with few exceptions. You can test out other AOSP ROMs to see if you are having the same problems.
That was one of the reasons I went way from Liquid (and bluetooth). I'm on CleanRom 6 now, and have pretty good call quality and signal with the VRBLK3 radio. For some reason, the latest radio from 4.1.2 didn't play nice with my phone or location. If you want better signal, TW is the way to go.
So you also had 30 min dropped calls or close to it from Liquid?
mverzal said:
So you also had 30 min dropped calls or close to it from Liquid?
Click to expand...
Click to collapse
No, not exactly at 30 minutes. I would experience dropped calls in specific areas, like when I was driving. I also experienced more chopping sound quality with the latest radio. Flashed back to LK3 and it is much better.
Is it 30 minutes no matter what you are doing or where you are? If that is the case, I'd do a clean install of a TW rom with the radio and rpm of your choice and see if that helps.
Related
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.
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
I flashed the Goodness and the Wicked Sprint ports after hearing that they bump up dBm by -10 I was very sceptical thinking maybe it was just measuring incorrectly or differently giving scued numbers. While running Wicked yesterday I went to a restaurant and a local store were I struggle to get 3g and drop often. I had a bar of 4g ! and no drops I was going to restore a CWR nandroid of Beans7 to see if it was the Rom but I recently switched to TWRP and didn't have time to fool with it. Anyone know how this would be possible? I've flashed a lot of roms and never noticed any difference in dBm even though they were said to be tweaked.
Jugger naut said:
I flashed the Goodness and the Wicked Sprint ports after hearing that they bump up dBm by -10 I was very sceptical thinking maybe it was just measuring incorrectly or differently giving scued numbers. While running Wicked yesterday I went to a restaurant and a local store were I struggle to get 3g and drop often. I had a bar of 4g ! and no drops I was going to restore a CWR nandroid of Beans7 to see if it was the Rom but I recently switched to TWRP and didn't have time to fool with it. Anyone know how this would be possible? I've flashed a lot of roms and never noticed any difference in dBm even though they were said to be tweaked.
Click to expand...
Click to collapse
You are still using a verizon radio/firmware so go figure
x714x said:
You are still using a verizon radio/firmware so go figure
Click to expand...
Click to collapse
Yep running the Verizon blk3 modem and rpm, for anyone who doesn't know Sprint modems will do nasty things to your phone never flash them (any modems other than Verizons for that matter). I went back to CWR so the next time I get back to the restaurant or the hardware store I'll restore back to Beans and get some screen shots for comparisson. I'd run some speed tests but they always end up being all over the place I don't think it would prove much. Post my shots once I get them, there is supposed to be a new Goodness rom out tonight so I know what I'll be doing later Flashhhh Aaaaahhhh God I love this phone
[Edit] screenshots first two Beans 7 second two Wicked Sensation port. Taken from exact same spot in the store, Wicked kept 2-3 bars of 4g through out the store Beans 7 never got 3g and dropped completely twice had to airplane to regain signal.
Noticed 10dB listed increase in signal on Wicked Sensations compared to CleanRom. Don't know if it's just the way the signal is reported or real boost!
I have the strangest issue. I get disconnected from calls in the middle of conversation if I'm using any of these main custom ROMs.
Blaz3r
CyanogenMod 10
Blaze Tweaked ICS 2.2
But If I'm using a stock ICS ROM or "Android ICS 4.0.4 UVLH5 (Posted by tthaz777)" everything is very stable and no disconnects.
I have full bar with all the ROMs and get perfect data speed and everything else works fine. I'm using the same exact apps on the ROMs as I do on the stock, so I don't think it's related to a particular app. It seems as if TMobile scans the sessions at their network level and disconnects the call because my connection is not providing some information/call data they need. The disconnect can happen as fast as a few seconds or after a 10 minutes or so, just random.
Is anyone else experiencing this ?
I'm currently running below and everything is stable with no drop calls. Just can't figure out why this happens when install any other ROM. and Yes I always to do a full wipe before install.
Android ICS 4.0.4 UVLH5 (Posted by tthaz777) with merwin's scorched-kernel-t769-ics v1.0.29
Well the 4.0.4 thazz build should be pretty stable as its essentially stock. That being said my wife (who is INCREDIBLY picky on how her phone functions... I've yet to get her to try something not TW-based) has been using Tweaked since before it was even posted and uses her phone as a phone constantly (... lot's of out-of-state sisters that she's always yapping with) and has yet to report an issue. I am unclear why you would be having these issues with the particular specificity you are experiencing... especially if kernels are remaining consistent across TW-based builds anyway. Without me being able to recreate it on my end or a logcat taken during the premature disconnect on your end I'm at a loss. If nothing else, at least you found something that works for you, so I suppose it a could be worse.
Sorry for the troubles.
Not all stock apps or play store apps work with 4.1, I had the same problem when I let my battery app manage my data. It would wait to connect sometimes up to 20-30 secs later after waking to make a call. Check all your apps your using for compatibility, and when you wake your phone give it a sec before calling out. If your in a bad area the alternating of edge/3g/HSDPA+ doesn't help either. I stopped allowing my battery app data control and that solved 90% of my issues, sometimes it still does it but only when I'm in the boonies.
techclan said:
I have the strangest issue. I get disconnected from calls in the middle of conversation if I'm using any of these main custom ROMs.
Blaz3r
CyanogenMod 10
Blaze Tweaked ICS 2.2
But If I'm using a stock ICS ROM or "Android ICS 4.0.4 UVLH5 (Posted by tthaz777)" everything is very stable and no disconnects.
I have full bar with all the ROMs and get perfect data speed and everything else works fine. I'm using the same exact apps on the ROMs as I do on the stock, so I don't think it's related to a particular app. It seems as if TMobile scans the sessions at their network level and disconnects the call because my connection is not providing some information/call data they need. The disconnect can happen as fast as a few seconds or after a 10 minutes or so, just random.
Is anyone else experiencing this ?
I'm currently running below and everything is stable with no drop calls. Just can't figure out why this happens when install any other ROM. and Yes I always to do a full wipe before install.
Android ICS 4.0.4 UVLH5 (Posted by tthaz777) with merwin's scorched-kernel-t769-ics v1.0.29
Click to expand...
Click to collapse
LOL I am using T-Mobile service with this device, so if that's the case for you I would expect a few drops from time to time
On a serious note, drops can happen with full bars for a variety of reasons. Tower is overloaded (signal shows strong but can't connect/gets dropped), person you have called drops you (calling someone in NY that has AT&T? ), bad/faulty sim card (free to get checked and replaced), etc. No cell phone/ROM is drop call immune, even stock (and yes even those people using Verizon). FWIW, I haven't dropped a single call in over a month using Thomas' PA and Tweaked. That's pretty good considering that's including the holidays and I didn't go home this year.
Thanks for the replies guys. What drives me crazy is that I have absolutely no dropped calls when using the stock ICS ROM, but as soon as I load any of the ICS ROMs mentioned the voice call gets disconnected periodically. Same Location, Same Apps, Same Calling Number, nothing changes except the ROM.
I'm fairly technical and good at troubleshooting but not an expert in reading the Android Logcat and don't know what to look for in the log. I have loaded the UVLH5 radio after flashing the the custom ROMs to see if that might be the cause but same thing.... I wondering if I need to try an older Radio...
Like I said all is running great with Android ICS 4.0.4 UVLH5 (by tthaz777) + merwin's scorched-kernel-t769-ics v1.0.29 OC to 1728 but not knowing what's causing the drops is just driving me crazy....
To test I just load the ROM and then call one of the free news numbers (ABC News etc 650-293-9114) and put the phone on speakerphone, and yes I have tried varies other numbers... JUST WEIRD
Try finding an app of the app store to make logging easier like logcat or something. Then run the app and make a call. If it doesnt disconnect, restart the log. When it does disconnect, end the log and copy+paste it here. That is the only real way to find out whats up.
So the problem started again this AM and it's been fine since I flashed Android ICS 4.0.4 UVLH5 (by tthaz777). I hear the hang up tone and calls would just disconnect in the middle of conversation with perfect signal strength. Nothing new was added to the phone, so only way to fix it was to reflash it again from a nan backup.
This is driving me crazy. Attached is a short logcat from right before the call dropped, could one of you experts check it out and tell me if you see anything strange going on....
Thanks
techclan said:
So the problem started again this AM and it's been fine since I flashed Android ICS 4.0.4 UVLH5 (by tthaz777). I hear the hang up tone and calls would just disconnect in the middle of conversation with perfect signal strength. Nothing new was added to the phone, so only way to fix it was to reflash it again from a nan backup.
This is driving me crazy. Attached is a short logcat from right before the call dropped, could one of you experts check it out and tell me if you see anything strange going on....
Thanks
Click to expand...
Click to collapse
any chance you can put that on pastebin instead of a pdf? just post a link to it. It could be helpful to a dev as I see that some info is spread out to different pages and is cut off.
Also did you use an existing sim from a previous phone when getting this phone or did you get a brand new sim? I know various issues arise when using an old sim with this phone. My old sim had issues and wouldn't connect to wifi calling and it was only 10 months old.
anactoraaron said:
any chance you can put that on pastebin instead of a pdf? just post a link to it. It could be helpful to a dev as I see that some info is spread out to different pages and is cut off.
Also did you use an existing sim from a previous phone when getting this phone or did you get a brand new sim? I know various issues arise when using an old sim with this phone. My old sim had issues and wouldn't connect to wifi calling and it was only 10 months old.
Click to expand...
Click to collapse
Here's the pastebin link. Thanks
http://pastebin.com/SCBx2jNS
When I initially had the issue I ordered a new sim hoping it would resolved it and that didn't help, so I flashed ICS 4.0.4 UVLH5 (by tthaz777) which is pretty much the stock with bloatware removed and that resolved the problem and not a single dropped call for a month and it just started again. It's so weird as if Mobile is looking for something in the connection/session and forces a disconnect.
techclan said:
Here's the pastebin link. Thanks
http://pastebin.com/SCBx2jNS
When I initially had the issue I ordered a new sim hoping it would resolved it and that didn't help, so I flashed ICS 4.0.4 UVLH5 (by tthaz777) which is pretty much the stock with bloatware removed and that resolved the problem and not a single dropped call for a month and it just started again. It's so weird as if Mobile is looking for something in the connection/session and forces a disconnect.
Click to expand...
Click to collapse
Ordering a new sim doesn't mean getting a compatible sim. Have you taken the phone to a Tmo store and had someone check it out? They could've sent you another partially compatible sim for it. If I knew more about reading the logs I would love to help you out....
Gentlemen,
As the title suggests, I won't be taking long, I only have a quick question to make which I do hope it has a short and fast answer by you.
I'm no total ignorant when it comes to flashing, kernels , custom roms etc etc, I do know my way around.But I seem to have come to a dead end.
Just bought a Galaxy s3 , courtesy of verizon , second handed. The thing is, I plan on using it in Greece,
I've been reading a couple hundred posts about issues with GSM , data connections and whatever comes with it.I myself had a problem with being stuck at roaming after flashing cm 10.2 just tonight. I had to go back to stock 4.1.2 verizon to get signal back.
I hope you understand where im trying to land over here. Imagine this scenarion: Me, phone, Greece,non-stock based custom rom . Phone/text/data issues? What do you suggest? I come very confused...
St34lth said:
Gentlemen,
As the title suggests, I won't be taking long, I only have a quick question to make which I do hope it has a short and fast answer by you.
I'm no total ignorant when it comes to flashing, kernels , custom roms etc etc, I do know my way around.But I seem to have come to a dead end.
Just bought a Galaxy s3 , courtesy of verizon , second handed. The thing is, I plan on using it in Greece,
I've been reading a couple hundred posts about issues with GSM , data connections and whatever comes with it.I myself had a problem with being stuck at roaming after flashing cm 10.2 just tonight. I had to go back to stock 4.1.2 verizon to get signal back.
I hope you understand where im trying to land over here. Imagine this scenarion: Me, phone, Greece,non-stock based custom rom . Phone/text/data issues? What do you suggest? I come very confused...
Click to expand...
Click to collapse
For roaming on AOSP, see here if it happens again. You'll probably want to edit your APN settings for data if you already have the local sim for Greece. I don't know much more than that but you should be good there. Popping the sim in and selecting GSM should be enough for calls. Keep a TW rom on your phone in case you have issues cuz that will help you in a jam. If you aren't confident that your AOSP rom is 100% stable, which they usually aren't in some way, having a touchwiz rom like Cleanrom or Bonestock could be your alternative rom.
Almost got to the bottom of this, flashing a TW based rom is working perfectly as expected.
Thing is with AOSP based roms i only get verizon wireless as a carrier and a constant -120 dbm signal power.ALthough i can make calls, i cant text or get data.
St34lth said:
Almost got to the bottom of this, flashing a TW based rom is working perfectly as expected.
Thing is with AOSP based roms i only get verizon wireless as a carrier and a constant -120 dbm signal power.ALthough i can make calls, i cant text or get data.
Click to expand...
Click to collapse
That's even after switching to GSM in Wireless Networks?
Sent from my SCH-I535 using Tapatalk 4