signal problems - AT&T Samsung Galaxy S II Skyrocket SGH-I727

So just today I updated my skyrocket to cm-10.1-20130526-NIGHTLY an it didn't say anything about updating radios or anything of the sort every thing seems to be running just fine but now i show no service almost anywhere I go but most of my txt will send but every few or so will come back saying cannot send at the moment. then if I retry/ move around it will send never had this problem before with existing NIGHTLY rom's. any insight or help would be greatly appreciated. My whole family has at&t has no signal problems.
phone info:
kernel version
3.0.72-cyangenmod-g5d26b2d [email protected] #1
baseband version
i727UCL13
Android version 4.2.2

Read the thread dude. Gawd.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 4 Beta

Related

Dropped calls?

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

Terrible Search Button Bug

Hello,
I have been experiencing a bug where the phone acts as if there has been a long press of the search button (and the appropriate dialog comes up) when I have not touched the search button at all! (I am not pressing it by accident, it will do this while sitting on a table untouched). When it happens, the search button is not lit up (as if it were pressed), and none of the other buttons can be pressed, nor can anything on the screen, other than responding to the dialog. This can last two to four seconds (it's REALLY annoying). What's worse is that this can happen up to once a minute sometimes!
I've discovered that this happens only when I have 3g data turned on. When data is off, or when on wifi only, it does not occur.
Is anyone else having this problem, and (hopefully) has found a fix? I did do a search (both on Google and in here). I discovered a Google forum where people talk about experiencing the problem (a Google employee chimes in with questions) but no solution as of yet. I was hoping to find something about this in Xda, but as stated, couldn't find anything Though this person may be talking about the same problem:
http://forum.xda-developers.com/showthread.php?t=1069765
Here is the link for the Google forum:
http://www.google.com/support/forum/p/Google+Mobile/thread?tid=49e8ca84071d51a4&hl=en
Since it only happens when 3g data is turned on, could it be my radio image? Or something else? Any help or thoughts would be greatly appreciated! My current running specs below:
Nexus S
Android Version 2.3.3
Baseband version NO DGSXKD1
Kernel Version 2.6.35.7-g1 d030a7 [email protected] #1
Mod Version Cyanogenmod-7.0.3-NS
Build Number GRI40
Model number GT 19020A (originally bought from a Telus Store) currently running on Bell Mobility
Rooted, bootloader unlocked
I was about to post this exact thread! I am having the same issue with my NS i9020a running stock unrooted 2.3.4. I to have noticed a link between data connection type and the issue occuring. One theory i read said that static charge may be to blame?... but that didn't seem right to me....
Anyway... I would also love some more info on this subject of anyone has any input. I bought my phone off ebay less than a week ago, and if the issue is hardware i am going to have to file a claim with paypal...
Sent from my Nexus S using Tapatalk
This is exactly what I posted in a separate thread. However, I'm not sure about the 2G / 3G changing.
I'll experiment.
Which radio are you using - seems like this was at least temporarily related to my switch to KD1 ?
Sent from my Nexus S using XDA Premium App
I reflashed radio KB3 and problem , at least for now is not happening. It was almost making the phone unusable this am earlier before changing radio
??!
Sent from my Nexus S using XDA Premium App
How can I find what radio I am using? Also, How long have the two of you had your devices? Is this issue something that manifested after you changed something on your phone (thus indicating it is not hardware related) or has it always been there? Thx, and i hope we can get this sorted out.
Cheers
Settings > About. Then look for Baseband version
I've had about three or four weeks. Not sure unless this radio change theory is correct
Sent from my Nexus S using XDA Premium App
jcrompton said:
Settings > About. Then look for Baseband version
I've had about three or four weeks. Not sure unless this radio change theory is correct
Sent from my Nexus S using XDA Premium App
Click to expand...
Click to collapse
Baseband Version
NO DGSXXKD1
Kernel version
2.6.35.7-ge382d80
[email protected] #1
Build number
GRJ22
Please update as to whether the radio change is a permanent fix. Thx.
Cheers
Edit: I am assuming that this (NO DGSXXKD1) is the KD1 radio that you switched to and are theorizing may be the culprit...it is also something that all three of our devices have in common. I am eager to see if changing the radio permanently fixes your issue.
I'm on a Telus 9020a radio KB3 and i have the same problem.
Not sure at this point what the deal is! But changing from the upgraded radio KD1 back to KB3 has up to this point solved the issue. Maybe six or seven hours without the phantom search firing.
????
Sent from my Nexus S using XDA Premium App
Currently there is no stock 2.3.4 for the i9020a. The no xxxxkb1 is a result of forcing the update from the t version. Since the a version uses didn't frequencies, I'm not sure about it's reliability.The ota has yet to be released and this tells me that our phone has something different
I see this issue also however I get it more when using gps. I have my phone vent mounted and I am suspecting heat might be the issue
Sent from my Nexus S
Matridom said:
Currently there is no stock 2.3.4 for the i9020a. The no xxxxkb1 is a result of forcing the update from the t version. Since the a version uses didn't frequencies, I'm not sure about it's reliability.The ota has yet to be released and this tells me that our phone has something different
I see this issue also however I get it more when using gps. I have my phone vent mounted and I am suspecting heat might be the issue
Sent from my Nexus S
Click to expand...
Click to collapse
Interesting, I don't know what was done to my phone before it was in my possession but when I received it it was running stock 2.3.3 and on first boot after setup i received a popup notifying me that there was a system update available. I selected install and it did its thing and now I have 2.3.4. Is there a way to revert the device back to the software it is supposed to have on it?
Cheers
Sent from my SCH-I500 using Tapatalk
Hey guys, got the Sprint Nexus S 4g just this last Friday. Phantom search button presses and long presses started up soon after. Still going on now. Have not been able to narrow down culprit as far as 3G/4G/Wifi go. Running completely stock everything:
Android 2.3.4
Baseband D720SPRKD8
Kernel 2.6.35.7ge382d80 [email protected] #1
Build Number GRJ22
Just thought I'd add my stat to the growing list.
Sophos1 said:
Interesting, I don't know what was done to my phone before it was in my possession but when I received it it was running stock 2.3.3 and on first boot after setup i received a popup notifying me that there was a system update available. I selected install and it did its thing and now I have 2.3.4. Is there a way to revert the device back to the software it is supposed to have on it?
Cheers
Sent from my SCH-I500 using Tapatalk
Click to expand...
Click to collapse
I'm on my phone so it's as little hard to link. In the general section there is a thread to a stock nandroid backup with the kb3 modem.
Sent from my Nexus S
I've now been about 9 or 10 hours after switching back to KB3 - no more issues yet! Pretty strange huh?
Sent from my Nexus S using XDA Premium App
Finally got my device rooted and switch to the KB3 radio.... it's has been a few hours and I have yet to experience the search button bug. I'm crossing my fingers that you found the solution! Thx.
Sent from my Nexus S using Tapatalk
Ok. So it's now been almost 24 hours. No repetitive firing of the search button on my Nexus S since flashing back to the KB3 radio.
Beware anyone experiencing this should not flash to the KD1 radio. I have a 9020a device. I assume it is Canadian since it had ATT 3G bands prior to any mention of ATT devices.
I think they are all a bit different when it comes to hardware which baffles more when I read on a Google forum post about a T-Mobile device that was stock Ann's doing this.
Sent from my Nexus S using XDA Premium App
Where to dowload KB3 radio image? (And advice)
Hey jrcompton,
Wow, that's great news! I tried a bunch of things, including going back to stock 2.3.3 via ROM manager (am now on 2.3.4, as I was prompted almost immediately for an OTA upgrade), and the bug still persists. It seemed after returning to stock that the issue didn't present itself until after installing certain apps (Dialer 1, Handcent, Extended Controls) but after removing them, am still seeing the bug. Was thinking that maybe it was these apps and uninstalling still let some trace and another factory reset might be necessary, but your results give me hope! As it is, on mobile data the bug can present itself several times in a minute! (Making the phone almost unusable).
All that being said, any chance you could share where I could download the KB3 radio? I did search and was only able to find a thread with mostly Tmobile users, and was thinking that the radio in that thread might not be the right one. I'm on Bell, so sounds like the radio that you're using would be right for me (since your phone uses AT&T bands).
Also, never flashed just a radio before, and am a little nervous. I know that there are a ton of threads with instructions, but I hope it's ok if I ask a couple questions. I'm assuming that I download the image, and put it in my ANDROID-SDK-TOOLS directory, then just (in command prompt from that same directory) type "fastboot flash radio *********.img (with the phone in bootloader, and connected via usb). And that I should NOT disconnect, power down, touch, or even look at phone during process, and make sure that PC doesn't power down, reboot, etc. If all of that is correct, do I need to wipe/factory reset or anything else beforehand or afterwards?
Thanks so much in advance, and so glad that you've at least had 24 hours bug free!
If this works for me as well, will post in the Google help forum thread as well.
I just downloaded the zip from here ( http://forum.xda-developers.com/showthread.php?t=975105
[RADIOS] 01/Mar XXKB3 (GRI54): Basedband (radio) only updates) and installed via CWM... worked like a charm
Cheers
Sent from my Nexus S using Tapatalk
If this worked for you guys then that's great, but do you have any suggestions for a NS4G user? I realize we don't have our own subforum but up until that happens, we have to have our questions fielded here. I'm still getting the search button going nuts on me issue. have tried data off/only wifi and still doing it. Wondering if I just got a defective unit...
Sophos1 said:
I just downloaded the zip from here ( http://forum.xda-developers.com/showthread.php?t=975105
[RADIOS] 01/Mar XXKB3 (GRI54): Basedband (radio) only updates) and installed via CWM... worked like a charm
Cheers
Sent from my Nexus S using Tapatalk
Click to expand...
Click to collapse
Hey Sophos1 (or anyone else who might know),
My Nexus is now running the following:
Android Version: 2.3.4
Baseband Version: NO DGSXXKD1
Kernel Version: 2.6.35.7-ge382d80 [email protected] #1
Build number: GRJ22
Model number GT 19020A (originally bought from a Telus Store) currently running on Bell Mobility
Would the KB3 radio that you downloaded for your phone work for mine? Also, just for confirmation, will I be ok following the steps that I listed above? Lastly, what's the worst that can happen if I flash the incorrect radio? Would I still have the opportunity to flash the correct radio (or reflash stock including the correct radio) via fastboot?
Thanks so much guys!

SMS "Pending" Problem

Hey everyone, just wanted to say that even though I have very little posts here, I have been following this forum for a long time now and I have gotten a lot of great info from everyone on XDA. Finally started to contribute now that I am getting more and more knowledge of the devices.
I couldn't seem to find a post on this so I thought I would post it...
I use Handcent for text messages, and since the majority of my friends use Verizon, I have "delivery reports" enabled so I can see if they do get delivered. Recently, starting last night and today whenever I sent a text it would stay in the pending phase for a very very long time and sometimes took a reboot or another text message sent to have them go through. Odd thing is, I can make phone calls or do anything else that requires data service. Past 2 hours or so it has been fine but since then I have flashed to a different radio. I am using the leaked radio, but the New CDMA/Old LTE combo.
Here are some things that may be useful:
ROM: Vanilla Bean 1.2
Baseband Radio: 1.16.00.0402w_1 (New CDMA/Old LTE - Radio Posted in Vanilla Bean Thread)
Kernal: 2.6.32.21_bamf_4.3a
Software: 1.13.605.7
Has anyone else experienced something like this? I tried the leaked radio with new CDMA and LTE but since I don't get 4G in my area yet, it caused more issues of signal going in and out constantly.

[Q] Installing V21Y 2.3.4 Update and corrupting cell connection

I flashed back to the lg provided Gingerbread this week and then upgraded to 2.3.4 using their tool. Could not get over the bloatware so ended up upgrading to ICS. I now have Eagles Blood up and running, everything is great, but I can only make Wifi calls. Every time I make or receive a call over Cell towers it's a loud clicking noise that both parties can hear.
I've tried multiple ROM's and re-installs(Hellfire/Eagleblood) with CM and AOSP versions and nothing resolves this, so I finally called Tmobile thinking maybe a cell tower reset would work.
I made it to level 2 tech support and this is a "known issue" with "incomplete" 2.3.4 patches. They basically read me a service bulletin explaining my exact issue, but the warranty is broken and they simply direct me back to the LG upgrade tool.
Has anyone else been able to recover cell tower calls on any ROM or did my G2x just become a tablet when not using GrooveIP?
TIA
As far as I know from lurking on the G2x forums, only stock Gingerbread and a rooted version of stock Gingerbread are available. I don't think any third-party ROMS have call audio working. The reason is that the official update changed the baseband.
Jlloyd97 said:
I flashed back to the lg provided Gingerbread this week and then upgraded to 2.3.4 using their tool. Could not get over the bloatware so ended up upgrading to ICS. I now have Eagles Blood up and running, everything is great, but I can only make Wifi calls. Every time I make or receive a call over Cell towers it's a loud clicking noise that both parties can hear.
I've tried multiple ROM's and re-installs(Hellfire/Eagleblood) with CM and AOSP versions and nothing resolves this, so I finally called Tmobile thinking maybe a cell tower reset would work.
I made it to level 2 tech support and this is a "known issue" with "incomplete" 2.3.4 patches. They basically read me a service bulletin explaining my exact issue, but the warranty is broken and they simply direct me back to the LG upgrade tool.
Has anyone else been able to recover cell tower calls on any ROM or did my G2x just become a tablet when not using GrooveIP?
TIA
Click to expand...
Click to collapse
By updating the ROM with LG's update tool to 2.3.4, u also updated the baseband, and if u read around the forums here for the G2x, you can easily find that none of the custom ROMs work with the new baseband because of compatibility issues, you can only use ROMs that are based off of the official 2.3.4 update but there arent any yet.
Although im quite surprised tech support said it was a known issue, i wonder how many other people have called having this problem because they dont read around.
Anyways, hope this helps clear things up
Sent from my LG-P999 using XDA
thanks for the quick responses. I read the ROM install instructions multiple times, but did not read about the underlying baseband since I was running Weapon G2x gingerbread with no problems and thought the 3 wipes recommended prior to the install would take me back down to a clean phone.
Appears I have a tablet till the updates are released.
Also, Tmobile tier 2 support had a KB item on this issue, but it was caused by earlier versions of the software update failing prior to completion and causing the SIM card/network errors.
Jlloyd97 said:
I flashed back to the lg provided Gingerbread this week and then upgraded to 2.3.4 using their tool. Could not get over the bloatware so ended up upgrading to ICS. I now have Eagles Blood up and running, everything is great, but I can only make Wifi calls. Every time I make or receive a call over Cell towers it's a loud clicking noise that both parties can hear.
I've tried multiple ROM's and re-installs(Hellfire/Eagleblood) with CM and AOSP versions and nothing resolves this, so I finally called Tmobile thinking maybe a cell tower reset would work.
I made it to level 2 tech support and this is a "known issue" with "incomplete" 2.3.4 patches. They basically read me a service bulletin explaining my exact issue, but the warranty is broken and they simply direct me back to the LG upgrade tool.
Has anyone else been able to recover cell tower calls on any ROM or did my G2x just become a tablet when not using GrooveIP?
TIA
Click to expand...
Click to collapse
All EB ROM's based on ICS are not compatible with the latest March bandbase.
You can downgrade to v21e July 2011 baseband if you want to use other ROMs.
Sent from my LG-P999 using xda premium
kesara said:
You can downgrade to v21e July 2011 baseband if you want to use other ROMs.
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
I don't want to seem lazy, but man, I've been looking all around for the "downgrade" baseband thread, where is it?
[email protected]
mustangtim49 said:
I don't want to seem lazy, but man, I've been looking all around for the "downgrade" baseband thread, where is it?
[email protected]
Click to expand...
Click to collapse
There isn't one. You use the same kdz method that ppl are using to update to v21y. just switch the 21y.kdz with 21e.kdz when using the method.
cricketAC said:
There isn't one. You use the same kdz method that ppl are using to update to v21y. just switch the 21y.kdz with 21e.kdz when using the method.
Click to expand...
Click to collapse
Yes
Sent from my LG-P999 using xda premium
Jlloyd97 said:
thanks for the quick responses. I read the ROM install instructions multiple times, but did not read about the underlying baseband since I was running Weapon G2x gingerbread with no problems and thought the 3 wipes recommended prior to the install would take me back down to a clean phone.
Appears I have a tablet till the updates are released.
Also, Tmobile tier 2 support had a KB item on this issue, but it was caused by earlier versions of the software update failing prior to completion and causing the SIM card/network errors.
Click to expand...
Click to collapse
Just look for the rooted version of the new update in the dev section by Kwes. Your phone will be fine then.
Sent from my LG-P999 using xda premium
Yup having the same issue with my friends phone. Someone mentioned downgrading the baseband, the only way I know how to do that is by using the tool that helps you unbrick the phone. please correct me if im wrong or have any idea what ive just said
What exactly is the benefit of the new march 2012 baseband (other than breaking custom ROM compatibility at this point)? Looking for apples-to-apples comparisons of a custom ROM running with old baseband and new baseband (other than broken cell voice calls).
A similar ordeal happened for Virgin Mobile's Optimus V line, where a new baseband came out, everyone jumped on it, but it caused occasional random reboots and no apparent benefits, and couldn't be downgraded. Eventually devs had to apply fresh LG released kernel source code & recompile kernel for new baseband to be stable.
Whyzor said:
What exactly is the benefit of the new march 2012 baseband (other than breaking custom ROM compatibility at this point)? Looking for apples-to-apples comparisons of a custom ROM running with old baseband and new baseband (other than broken cell voice calls).
A similar ordeal happened for Virgin Mobile's Optimus V line, where a new baseband came out, everyone jumped on it, but it caused occasional random reboots and no apparent benefits, and couldn't be downgraded. Eventually devs had to apply fresh LG released kernel source code & recompile kernel for new baseband to be stable.
Click to expand...
Click to collapse
As much as I miss ics, the new baseband pretty much fixes everything. Battery lasts forever, GPS lock right now and I've seen accuracy to 3ft. No random rebooting. Fast, smooth, dripping butter everywhere. Other than that, no real reason to flash it.
[email protected]

Weird Issue Call Drop using custom ROMS In the Middle of Conversation

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....

Categories

Resources