I have been discouraged from the Froyo ROMs for a while due to the problem with calls being dropped but then suddenly they aren't dropped. I really like the Froyo ROMs though so I decided to try it again and the first day I experienced it yet again on CELB 3.6. It only happened a couple of times then 3.7 was released and I flashed that and it happened again on the first call LOL. I then started looking through things in the settings and under the mobile data setting I turned on National Data Roaming, since then I have been on several calls ranging from 20 minutes to an hour and have yet to experience this problem since turning data roaming on, some of these calls were in areas that I know for certain I had the dropped and reconnected calls happen before. Maybe some others may want to try this out and see if it helps you as well. Hope this helps some people that have experienced this as well.
Has anyone else tried this yet? And if so, has it made any difference for you as well?
happens to me all the time. kaos froyo, tazz froyo, celb froyo, nonsensikal froyo. Only at my house tho. i have 3 bars there. not sure whats going on there but i have learned to live with it. Wont be long till we are on 2.3 anyway. deal with it for a month. by the new year kaos should have a completley functional 2.3 rom. maybe without camera, but still fully functional.
I've been messing around with the national data roaming for about a week now. When I have national data roaming enabled it doesn't happen, if I turn it of it does. Try enabling it and see if it makes a difference for you too. It's located under settings>wireless & networks>mobile networks
will enable it and see if it happens tonight.
Same here, after enabling it I have had no stopped call issues. Its been about a week, so far so good
Good information, I think I'm gonna try it, but first does this affect my billing at all? I'm on my parents plan and don't want to give them a heart attack if I incur extra charges
Scott586 said:
Good information, I think I'm gonna try it, but first does this affect my billing at all? I'm on my parents plan and don't want to give them a heart attack if I incur extra charges
Click to expand...
Click to collapse
It shouldn't but that would depend on what your plan is. If you have a nationwide plan with unlimited data and no roaming charges then it won't. I'd suggest checking on your plan first. Just a thought though lol.
CondemnedSoul said:
It shouldn't but that would depend on what your plan is. If you have a nationwide plan with unlimited data and no roaming charges then it won't. I'd suggest checking on your plan first. Just a thought though lol.
Click to expand...
Click to collapse
I also have this problem happen on non-Verizon based ROMs such as RCMix.
The call says it's dropped, but the person on the other end can hear everything that's going on.
Then the phone rings you back, but in reality, they were hearing everything going on around you in the meantime.
I almost lost my girlfriend because of it. Immediately flashed away from said ROM. Had the same problem with Froyo ROMs.
May switch to a CM ROM now, if this is a serious fix. Thanks very much for this.
I was hoping this would be a fix - I upgraded to CELB 3.9 a couple of days ago, and turned on National Data Roaming.
Tonight I had the same behavior - temporary call drop and reconnect along with the same symptoms that usually accompanies it (speakerphone mode toggles off, phone vibrated, yada yada).
Confirmed through examination of the (uncompressed) SYSTEM_TOMBSTONE file in /data/system/dropbox/ that yes, the usual cause is present: segfault crash of the "rild" process.
Rats! I was hoping this might provide a fix... but apparently not for me.
bftb0
bftb0 said:
I was hoping this would be a fix - I upgraded to CELB 3.9 a couple of days ago, and turned on National Data Roaming.
Tonight I had the same behavior - temporary call drop and reconnect along with the same symptoms that usually accompanies it (speakerphone mode toggles off, phone vibrated, yada yada).
Confirmed through examination of the (uncompressed) SYSTEM_TOMBSTONE file in /data/system/dropbox/ that yes, the usual cause is present: segfault crash of the "rild" process.
Rats! I was hoping this might provide a fix... but apparently not for me.
bftb0
Click to expand...
Click to collapse
Sorry ut didn't work for you.... so far now im at 3 weeks without it happening to me
I have still had this temporary dropped call problem occur just as frequently on CELBFroyo 3.6 with this "fix". And most of the time I'm in my apartment on the phone for hours when it happens, and it sometimes happens more than once during these extended phone calls.
Just as has been described before: the phone looks and acts like the call was dropped, I can hear nothing but the other person can hear everything, and then after several seconds everything is back to normal.
Oh well. Thanks for the suggestion, though.
Very interesting to hear others have been having this problem. I had thought it was due to my bluetooth earphone, because it used to happen to my wife on her old earphone with a standard cell phone. However, last night I lost my earphone and the same problem occurred while on speakerphone. Although annoying, most of the time I just deal with it. I just installed radio version 2.42.01.04.27 hoping it might help. Various versions of CELBFroyo (currently using 3.9) have done it. I will let you all know if this helps and keep checking back on this string to see if anyone else finds a fix.
farmdoc said:
Very interesting to hear others have been having this problem. I had thought it was due to my bluetooth earphone, because it used to happen to my wife on her old earphone with a standard cell phone. However, last night I lost my earphone and the same problem occurred while on speakerphone. Although annoying, most of the time I just deal with it. I just installed radio version 2.42.01.04.27 hoping it might help. Various versions of CELBFroyo (currently using 3.9) have done it. I will let you all know if this helps and keep checking back on this string to see if anyone else finds a fix.
Click to expand...
Click to collapse
Seems like its touch and go now. Works for some but not for others. I haven't had it happen to me in 3 weeks now but this hasn't worked for some others where some it has. Im using the new sprint radio now, I don't know if maybe it has anything to do with what radio you have too? I just flashed this radio about a week and a half ago though. Before that I was on the older verizon radio... not the one from july ota though... the previous one.
sent from the depths of hell
CondemnedSoul said:
Seems like its touch and go now. Works for some but not for others. I haven't had it happen to me in 3 weeks now but this hasn't worked for some others where some it has. Im using the new sprint radio now, I don't know if maybe it has anything to do with what radio you have too? I just flashed this radio about a week and a half ago though. Before that I was on the older verizon radio... not the one from july ota though... the previous one.
sent from the depths of hell
Click to expand...
Click to collapse
If I recall correctly, it has been seen on multiple radios. ( Have you seen this thread? )
bftb0
bftb0 said:
If I recall correctly, it has been seen on multiple radios. ( Have you seen this thread? )
bftb0
Click to expand...
Click to collapse
Thanks for the leads to the other threads. I had not seen them.
I have not had a chance to test with the current radio installed (2.42.01.04.27), but plan to tonight. Is there a newer radio for the Eris? Looking at the version numbers of some I have seen referenced would make me believe that there are newer ones. Where do you download these?
farmdoc said:
Thanks for the leads to the other threads. I had not seen them.
I have not had a chance to test with the current radio installed (2.42.01.04.27), but plan to tonight. Is there a newer radio for the Eris? Looking at the version numbers of some I have seen referenced would make me believe that there are newer ones. Where do you download these?
Click to expand...
Click to collapse
AFAIK, this is the most recent radio and is currently what I'm using:
http://forum.xda-developers.com/showthread.php?t=853868
roirraW "edor" ehT said:
AFAIK, this is the most recent radio and is currently what I'm using:
http://forum.xda-developers.com/showthread.php?t=853868
Click to expand...
Click to collapse
Thanks! BTW what is AFAIK?
farmdoc said:
Thanks! BTW what is AFAIK?
Click to expand...
Click to collapse
You're welcome! AFAIK = As Far As I Know
Related
Does it happen to you?
You are talking on a call (on your Froyo'ed Eris), and you feel your phone vibrate twice; you can't hear the other party, so you look at your screen, and sure enough, it says "call lost" (or similar). So you go to redial, but then after a few seconds, you realize: the other party is still on the line!
If you were using the speakerphone toggle, it will have been turned off.
I really don't yak on my phone much, so the fact that I've seen it a few times leads me to think it is pretty common.
My phone has been solid as a rock since Drop Day (Nov 6th), and I never experienced this on 1.5 or 2.1 stock, or any 2.1 dev ROMs, but I've seen it on both Tazz V6 and Kaos V29.
Has it happened to you?
bftb0
[SIZE=+1]Edit 2/15/2011 - A very likely fix for this problem has been identified. See this post:[/SIZE]
http://forum.xda-developers.com/showthread.php?t=956091
Edit 9/14/2010 - see diagnostic information in post #27
bftb0 said:
Does it happen to you?
You are talking on a call (on your Froyo'ed Eris), and you feel your phone vibrate twice; you can't hear the other party, so you look at your screen, and sure enough, it says "call lost" (or similar). So you go to redial, but then after a few seconds, you realize: the other party is still on the line!
If you were using the speakerphone toggle, it will have been turned off.
I really don't yak on my phone much, so the fact that I've seen it a few times leads me to think it is pretty common.
My phone has been solid as a rock since Drop Day (Nov 6th), and I never experienced this on 1.5 or 2.1 stock, or any 2.1 dev ROMs, but I've seen it on both Tazz V6 and Kaos V29.
Has it happened to you?
bftb0
Click to expand...
Click to collapse
I believe with Froyo it auto reconnects dropped calls, this happens all the time to me and I actually like it.
the vibrations are in your settings
one buzz = call connected
two buzzs = call dropped
jrozga said:
I believe with Froyo it auto reconnects dropped calls, this happens all the time to me and I actually like it.
the vibrations are in your settings
one buzz = call connected
two buzzs = call dropped
Click to expand...
Click to collapse
I poked around a little and couldn't find any mention of it as an official feature of 2.2; do you have a link?
Does it seem to happen to you about as frequently as you were getting plain ole' dropped calls on 2.1 or 1.5, or more frequently?
bftb0
Never had a call dropped =\ can't say, sorry.
this happens to me all the time
im on tazz v8 froyo
I get one buzz then the lost call sound but after like one or two seconds i can hear the person on the other side
It happens frequent
carycooke said:
this happens to me all the time
im on tazz v8 froyo
I get one buzz then the lost call sound but after like one or two seconds i can hear the person on the other side
It happens frequent
Click to expand...
Click to collapse
Does it happen more frequently than the rate at which you used to get dropped calls when you were on 2.1 (or 1.5) ROMs?
I don't know whether it is a bug or not - if jrozga is correct, then it should happen about as often as plain-ole dropped calls occurred with 1.5 or 2.1 ROMs. (Or maybe to be fair, as often as dropped calls occur with stock 2.1 phones with the July 2010 OTA - they have the same radio as most rooters are using)
I still haven't found anything on line from "official" sources that mention that this is expected behavior in Android 2.2 phones. The last time it happened to me, I questioned the other party on the line, and they said "I heard one buzz for about half a second". (They were on a land-line, so it eliminates their end of the connection as the source of the trouble.)
That's a little bit bizarre if they heard the first of the two vibrations on my Eris - it means my Eris had decided that the call had terminated even though it had not. That alone inclines me to believe it is a bug, not a feature.
bftb0
I get it on about every call since installing 2.2
Sent from my FroyoEris using XDA App
I'm running celb 2.1 and today made a phone call in a poor signal area and still made it all the way thru without dropping or anything is it a radio problem per chance?
tburns said:
I get it on about every call since installing 2.2
Sent from my FroyoEris using XDA App
Click to expand...
Click to collapse
That's exactly why I think it is a problem with the current batch of developer 2.2 (Froyo) ROMs.
As I said, I don't make that many calls, so I don't really know how often it happens - but given that it has happened to me a couple of times now (given the small amount of calling that I do), it makes me think it is not just a signal reception issue.
Which ROM and Radio firmware are you using BTW?
I've used kaos for about a month and been on celb for almost a week and have not had such an issue. I use my phone frequently for work, too. I have had the current radio from the july update since a week after it was available.
Sent from my ERIS using XDA App
Bump.
We now have 15 people on XDA (in the Eris forums) reporting the symptom:
bftb0: Tazz V6; Kaos Froyo V29 [Froyo]
jrozga: (unknown) [Froyo]
carycooke: Tazz V8 [Froyo]
tburns: ??? [Froyo]
mcook1670: "All Froyo ROMs" [Froyo]
punkxdead: CELB [CyanogenMod]; CELB Froyo [Froyo]
Macrodroid: Kaos & Tazz [Froyo]
droiderisuser: ??? "2.1"
danwguy: CELB 2.7 cyamogenmod 5.0.8-DS firmware 2.1-update1 [CyanogenMod]
pablocasiano: WW4.6, KaosFroyo V29
crax0r: KaosFroyo V29
tjthebest: CELB 2.8-CM5.0.8
mistaj: CELB 2.8-CM5.0.8
npong: CELB 2.8-CM5.0.8
mflane: CELB 2.8-CM5.0.8
Some of them say "it happens all the time"
And 10 more people over in the AF Eris forum reporting the same oddity - on different Froyo/AOSP ROMs:
erisuser1: Tazz V6; Kaos Froyo V29 [Froyo]
snozzcumber: Kaos Froyo V?? [Froyo]
TJTHEBEST: CELB 2.9 [CyanogenMod]
MrBojenglz: Buufed v???
BlueDC2: CELB v?, Kaos V?
rick311:
BellaSkye: Kaos V32
Kaessa: Kaos V32
tpatnoe: Kaos V30
rc346: Kaos V34
funkyfender: "CM6"
john58543: KaosV30
So far, only one user has said "this also happened to me on a 2.1 ROM" - droiderisuser
[ Edit ]: At least two people have reported this on older radios, and and also on non-Froyo (but CyanogenMod ROMs)
If it happens to you, and you have the SDK set up on your PC, and it is convenient to do so, try to make a note of the time when it happens, and then when your call is complete, dump a "logcat" to your PC, and post up the log during that same minute here.
Code:
C:\blech> [B][COLOR=green]adb shell logcat > strange_call_reconnect.txt[/COLOR][/B]
[I](wait about 30 seconds and then hit ^C (Control-C) )[/I]
I've had it happen on all Froyo roms. I work for the FDOT so I'm on the highway 8 hours a day. I don't know if its the phone changing towers or what. I always have a good signal because the towers are next to the highway. Not sure what it is but its annoying
Sent from my ERIS using XDA App
Houston, we have a problem.
TJTHEBEST over on AF indicates he experienced the same problem using an older radio firmware on CELB
I have not found any evidence to support or deny jrozga's claim that this is a Froyo "feature", rather than a bug. I'll try to poke around a little and see if I can find anything further.
bftb0 said:
Houston, we have a problem.
TJTHEBEST over on AF indicates he experienced the same problem using an older radio firmware on CELB
I have not found any evidence to support or deny jrozga's claim that this is a Froyo "feature", rather than a bug. I'll try to poke around a little and see if I can find anything further.
Click to expand...
Click to collapse
I also had this problem with CELB with the 2.41.04.02.02 radio. I switched to CELB Froyo after it 'matured' (hoping to resolve it) and still had the issue. I have since switched to KaosFroyo v29 and the latest "July" radio. The issue is still present.
BTW Heres a quote from my post in the CELB Froyo thread awhile back:
punkxdead said:
I have had this problem with ErisLightningBolt and CELB Froyo, (and KaosFroyo when I tested it). I never had this issue in a Sense based ROM (PlainJane), only in the AOSP/Cyanogen based ROMs. I live in a city with great 3G coverage and never experience the issue while at home, however I travel alot for work. When driving through rural areas it happens to me all the time. My call "ends" screen goes away, phone beeps and vibrates (like when you end a call), audio drops out, 5 secs later, screen comes back, call resumes. The caller on the other end always assumes I had another call/call waiting beep, etc. I believe the phone is switching from 3G to 1x in the process causing this, but I can't be certain. I have been patiently searching/working to find a solution but to no avail. Just thought I'd post since I'm finally hearing of others with this issue.
Click to expand...
Click to collapse
Never happens to me, and I make phone calls about twice per day.
punkxdead,
Thank you for that detailed report. Very useful information
Turns out that TJTHEBEST from AndroidForums experienced the problem on 2.1 CELB, which is not Froyo - but I guess it is a CyanogenMod build. That further corroborates your experience.
So far, nobody has reported this in a Sense-based ROMs. I'm a little fuzzy on the genealogy of the kernels in the various roms, although I suppose the problem could also be occurring in "rild" or it's supporting libraries.
It's not a show stopper by any means, but it is annoying; it would be nice if we could figure out how to get it fixed, since it seems to appear in lots of different dev ROMs.
If you are able to do the 'logcat' thing to see if we can find some more info, please give it a try; I will do likewise.
bftb0
punkxdead said:
I also had this problem with CELB with the 2.41.04.02.02 radio. I switched to CELB Froyo after it 'matured' (hoping to resolve it) and still had the issue. I have since switched to KaosFroyo v29 and the latest "July" radio. The issue is still present.
BTW Heres a quote from my post in the CELB Froyo thread awhile back:
Click to expand...
Click to collapse
I can confirm the 3g to 1x theory. This has happened twice on my phone, several times on my wifes since,we loaded tazz v8. It also happens on kaos. Not on any of the 2.1 roms ive used. Each time, the phone,is,in the 1x data state. I've had it on speaker amd watched this happen each time. When 3g comes back, so does the,other caller. I think it may have something to do with network selection in froyo.
I have recently changed mine from automatic to home only... So far, no bug yet (only been a couple of days, though..).
Sent from my Froyo Eris using XDA App
Macrodroid said:
I can confirm the 3g to 1x theory. This has happened twice on my phone, several times on my wifes since,we loaded tazz v8. It also happens on kaos. Not on any of the 2.1 roms ive used. Each time, the phone,is,in the 1x data state. I've had it on speaker amd watched this happen each time. When 3g comes back, so does the,other caller. I think it may have something to do with network selection in froyo.
I have recently changed mine from automatic to home only... So far, no bug yet (only been a couple of days, though..).
Sent from my Froyo Eris using XDA App
Click to expand...
Click to collapse
Hmmm. Interesting. I think EVDO (3G) and CDMA Voice are mutually exclusive (simultaneously, anyway - a fundamental technical limitation of the way EVDO is implemented as an overlay in CDMA networks). I suppose it could be that if the ROM thinks that the voice call has ended, the "3G" icon appears right away. So it's not too surprising that you would see something changing in the display at the moment the call is "temporarily lost".
bftb0
bftb0 said:
Hmmm. Interesting. I think EVDO (3G) and CDMA Voice are mutually exclusive (simultaneously, anyway - a fundamental technical limitation of the way EVDO is implemented as an overlay in CDMA networks). I suppose it could be that if the ROM thinks that the voice call has ended, the "3G" icon appears right away. So it's not too surprising that you would see something changing in the display at the moment the call is "temporarily lost".
bftb0
Click to expand...
Click to collapse
I'm not really sure what the network option really would do. I do know that froyo isn't an eris os, so maybe it's something related to how it interacts with our phones... Either way, i'm waiting to see if the bug comes back on home only. Still love froyo, regardless!
Sent from my Froyo Eris using XDA App
Not sure if this helps but I have an Eris and pre Froyo when I was using Plain Jane I believe it was not sure precisely but It was a 2.1 rom for sure I had this happened to me quite frequently. So I would assume it is not just a 2.2 issue.
So I've done a lot of searching and haven't really found anything definitive. I've found that with some roms I'll lose GPS signal after a certain amount of time (say 10-30 minutes) and have to turn GPS off and back on or reboot the phone. I saw something about flashing a different radio may make a difference. Kinda just wanted to see other peoples thoughts on the issue or if maybe there is something else I can do before I go flashing a different radio.
Currently running CELB 4.1 and baseband 2.42.01.04.27 and I have the issue.. I've had it with most of Tazz's roms as well. KaosFroyo is the only one Ive used that I've never seen the issue with, but I'm really diggin CELB right now and this is the ONLY issue I've got with it.
Have you tried GPS status in the market? I know it will help you lock in a signal, so it would make sense that it would also help keep your GPS locked in.
Bayhill Jacket said:
Have you tried GPS status in the market? I know it will help you lock in a signal, so it would make sense that it would also help keep your GPS locked in.
Click to expand...
Click to collapse
I have now.. I did the reset and download options in the program. Too bad this isn't something I can quickly test. I'll report back with the results. Thanks!
I have noticed this as well. Last time it happened to me it was 4:30 in the morning, and the "GPS lost" message came up about 180 seconds before I had to make two freeway changes in an area I'd never been before. (CELB 3.9 and same radio as your case). Fortunately for me I had reviewed the route, so I more or less knew what to do.
If I recall correctly, it has always happened after the Nav app had been running for a fair bit of time - at least 30 minutes or more.
However, I don't know if it is something about the root ROMs or not - I started using rooted ROMs back in March or so, so I really don't have a tremendous operating baseline on stock 2.1 ROMs to compare it to. Maybe it is a problem there, too!
If I recall correctly, the last time it happened, I just pulled up GPS Status and asked it reload the aGPS state (without exiting the Nav app), and the Nav app seemed to gracefully recover.
Annoying? Yeah. I don't know what can be done about it, though - like the "undead calls" problem, it happens so infrequently that it is hard to know whether or not a ROM change actually fixes the problem.
bftb0
I had the same problem with every 2.2 rom I used GPS with. I decided to go back to 2.1 because I have been needing GPS alot more often lately but I havent tested it out since I made the switch. I'll try it out today and report the results tonight.
This same thing seemed to happen on the 2.1, CyanogenMod 5 based ELB by Conap as well. If it is happening with all of the 2.2 ROMs, I wonder if it's just a CyanogenMod issue?
See http://forum.xda-developers.com/showthread.php?p=6812308#post6812308 (this was not the only person reporting it, if you search that thread.)
I really don't think it's ALL 2.2 CM roms though. I've gone on 7 hour car trips with Kaos Froyo without a single drop.. to and from. I've seen another theory somewhere around here about it being certain hardware revisions that act this way with certain software builds. At lease we've got a thread dedicated to this issue now.. maybe we can get something figured out.
Still don't know if the GPS status program helps.. I left navigation turned on for a bit sitting in my house and it stayed connected for the half an hour I left it, just don't think that's gonna be an accurate test with not moving around and all. If it doesn't work I will try a different radio.. I saw somewhere one guy had good luck with a specific older version radio. If that's what it comes down to I'll try.
I have been having issues with the GPS working on both of my phones while using 2.2 roms. I switched to 2.1 a few days ago and I used the GPS on my way to work this morning and didnt have any issues. I also had to flash Senseable a couple of months ago while on a road trip because I was tired of loosing the GPS signal every half hour. It may be a CM thing.
Im having the same issues as well. Haven't found a fix yet..
I've had this issue, after I flashed KaosFroyo(v36), and XTR(4 i think). I recently unrooted using Flashback21 v1 and flashed with the radio included. I have gone back to xtr 5 now and have had no lost gps in over a week. Don't have a clue as to why. hope it helps someone.
deadbot1 said:
I've had this issue, after I flashed KaosFroyo(v36), and XTR(4 i think). I recently unrooted using Flashback21 v1 and flashed with the radio included. I have gone back to xtr 5 now and have had no lost gps in over a week. Don't have a clue as to why. hope it helps someone.
Click to expand...
Click to collapse
give us another update. is the gps problem still fixed for you? Thanks!
I have flashed the radio directly with the verizon zip file that is around and I still get inconsistent results But it always drops a signal eventually in about a 1/2 hour
Jrocker23 said:
I have flashed the radio directly with the verizon zip file that is around and I still get inconsistent results But it always drops a signal eventually in about a 1/2 hour
Click to expand...
Click to collapse
I've seen it on several ROM's as well. From what i've messed with, it doesn't seem to be dependent on the autokiller memory preset, radio firmware, or amount of overclocking i'm doing. It doesn't seem to be dependent on how many programs are running either. I usually have nav and pandora running while i'm in the car, and sooner or later, the gps poops out.
I feel like it seems to happen less, now that i'm back to using the on-demand governor. but that could just be in my head.
I've had to go back to a 2.1 rom because of it. Its very annoying when the goa signal gets lost right before the exit ramp.
Sent from my Eris using XDA App
Im thinking of going back to a 2.1 rom as well...
I have also seen the same results on any 2.2 or higher rom. I have since returned to XTRRom 5.0 and have not had a single problem with GPS on any of my jogging runs. I definitely think it is a CM thing. At least on my phone.
Using kaosfroyo v39 and I flashed that sprint phone radio on my eris and haven't had any gps issues. In fact, just the opposite. Mine would lock up before the v39 and the radio flash
I flashed that radio as well and today not one issue at all. Will test more tomorrow
I'm using the 2.42.02.10.29 sprint radio and still seeing it drop out.
Sent from my GSBv1.1 using XDA App
haganme said:
I'm using the 2.42.02.10.29 sprint radio and still seeing it drop out.
Sent from my GSBv1.1 using XDA App
Click to expand...
Click to collapse
Today I even flashed back to the July 2010 version (2.42.01.04.27). the gps dropped out almost every 5 minutes while i was driving around. that's the worst i've seen. So i flashed back to the 2.42.02.10.29 sprint radio again. I haven't seen very good navigation performance on the v1.1 gingershedbread overall, actually. my position on the gps nav doesn't update very often, although it seemed like the voice instructions were still pretty well timed as usual.
So, I got a Rezound last week, kind of hoped that it would still have GB on it, but found out it had that recent ICS build on there. I didn't think much of it until a couple days ago...
First, I think I know the answer already, but since I have this "leaked build", I'm guessing there's no going back to stock GB? What was upgraded besides the ROM (baseband, firmware, etc)?
Second, people are saying that when I talk, it starts out at normal volume, then sounds like I'm holding the phone about 2 feet in front of me while talking (in other words sounding very distant), and coming back... Now, the only person who has actually described the problem is my dad, who has a Thunderbolt. My wife has an Inc2, and has not mentioned any problems, however she may not know what to listen for, as well as others, etc... I've also tried disabling 4g and using 3g only. I am wondering if this is some kind of radio issue?
Third, the bluetooth doesn't seem to have a lot of range. I have a couple bluetooth devices I use often. The first one is a Panasonic KX-TG6581 cordless phone which utilizes bluetooth on the handset to be used as an extension to the cell phone. On previous phones I got whole house coverage (I live in a single level 3000sq ft home). On the Rezound it disconnects at the ends of the house... I also have a Turtle Beach headset equipped with bluetooth. It seems to work fine when initially calling or getting a call, but then there's there's this weird static (kind of sounds like old dial up negotiating tones?). I wonder if this is because of bluetooth 3.0, but not ruling out the headset and rf/bluetooth interference
Last, even running with the extended battery, unless I shut off mobile data altogether when at home (which I should probably be doing anyway, but coming from other 4g phones I never noticed until now), I can stare it for 5 min and watch the percentage dropping. On wifi, not too bad. Just worried if I'm in 4g all day with no wifi will the extended battery last, say 12 hrs? I have no problems keeping it on AC power when at home.
Hope I didn't sound too noobish LOL... thanks for any suggestions.
diehardbattery said:
So, I got a Rezound last week, kind of hoped that it would still have GB on it, but found out it had that recent ICS build on there. I didn't think much of it until a couple days ago...
First, I think I know the answer already, but since I have this "leaked build", I'm guessing there's no going back to stock GB? What was upgraded besides the ROM (baseband, firmware, etc)?
Second, people are saying that when I talk, it starts out at normal volume, then sounds like I'm holding the phone about 2 feet in front of me while talking (in other words sounding very distant), and coming back... Now, the only person who has actually described the problem is my dad, who has a Thunderbolt. My wife has an Inc2, and has not mentioned any problems, however she may not know what to listen for, as well as others, etc... I've also tried disabling 4g and using 3g only. I am wondering if this is some kind of radio issue?
Third, the bluetooth doesn't seem to have a lot of range. I have a couple bluetooth devices I use often. The first one is a Panasonic KX-TG6581 cordless phone which utilizes bluetooth on the handset to be used as an extension to the cell phone. On previous phones I got whole house coverage (I live in a single level 3000sq ft home). On the Rezound it disconnects at the ends of the house... I also have a Turtle Beach headset equipped with bluetooth. It seems to work fine when initially calling or getting a call, but then there's there's this weird static (kind of sounds like old dial up negotiating tones?). I wonder if this is because of bluetooth 3.0, but not ruling out the headset and rf/bluetooth interference
Last, even running with the extended battery, unless I shut off mobile data altogether when at home (which I should probably be doing anyway, but coming from other 4g phones I never noticed until now), I can stare it for 5 min and watch the percentage dropping. On wifi, not too bad. Just worried if I'm in 4g all day with no wifi will the extended battery last, say 12 hrs? I have no problems keeping it on AC power when at home.
Hope I didn't sound too noobish LOL... thanks for any suggestions.
Click to expand...
Click to collapse
if you have leaked ics (3.11.605.22) on your phone, you won't be able to return to stock gb.
how about re-flashing the leaked ics to see if the radio, bluetooth, and battery issues can be fixed.
Did the phone come brand new with leaked ics or did you buy it used
diehardbattery said:
Second, people are saying that when I talk, it starts out at normal volume, then sounds like I'm holding the phone about 2 feet in front of me while talking (in other words sounding very distant), and coming back... Now, the only person who has actually described the problem is my dad, who has a Thunderbolt. My wife has an Inc2, and has not mentioned any problems, however she may not know what to listen for, as well as others, etc... I've also tried disabling 4g and using 3g only. I am wondering if this is some kind of radio issue?
Click to expand...
Click to collapse
Funny you say that as I have people telling me that now and I'm stock gb. Maybe I need to take my Rezound in.
Sent from the HTC Rezound of Akuma
taptaptouch said:
Did the phone come brand new with leaked ics or did you buy it used
Click to expand...
Click to collapse
Well, the ad did say "never used", but I find that hard to believe since the leaked rom was on it... so I would say used
qudwis said:
if you have leaked ics (3.11.605.22) on your phone, you won't be able to return to stock gb.
how about re-flashing the leaked ics to see if the radio, bluetooth, and battery issues can be fixed.
Click to expand...
Click to collapse
When I got the phone, we did the sale inside a VZW store, the salesperson turned it on, and it was at the Welcome to Android screen... Thought it looked like ICS but wasn't 100% sure (should have double checked, I know)... even the rep didn't check... So, I'm guessing it was a fresh flash? Of course, not knowing exactly where it originally came from... don't know if that would make a difference?
diehardbattery said:
Well, the ad did say "never used", but I find that hard to believe since the leaked rom was on it... so I would say used
Click to expand...
Click to collapse
did you try returning?
qudwis said:
did you try returning?
Click to expand...
Click to collapse
You mean to the seller? No, I bought it off Craigslist so I think I'm stuck with it. Doubt I would have any recourse at a VZW store... not 100% sure about a replacement since the tech will want to know software version, etc...
diehardbattery said:
You mean to the seller? No, I bought it off Craigslist so I think I'm stuck with it. Doubt I would have any recourse at a VZW store... not 100% sure about a replacement since the tech will want to know software version, etc...
Click to expand...
Click to collapse
fry the phone an tell them it dont turn on!!
Don't fry it. It sounds like with some patience and care the phone can be functioning great
Sent from my HTC Rezound with Tapatalk
buckifvr said:
Don't fry it. It sounds like with some patience and care the phone can be functioning great
Sent from my HTC Rezound with Tapatalk
Click to expand...
Click to collapse
Wasn't planning on frying it LOL... but what about the patience and care... should I start by reflashing? Is there anything else to try or look for at this point?
diehardbattery said:
Wasn't planning on frying it LOL... but what about the patience and care... should I start by reflashing? Is there anything else to try or look for at this point?
Click to expand...
Click to collapse
Pull battery, hold down volume down + power. What hboot and radios do you have?
Sent from my ADR6425LVW using XDA
HBOOT is: 2.21.0000
Radios are: 1.22.10.0310r/1.22.10.0300r
Also forgot to mention that I'm getting this SMS every time I power down and boot the phone...
900080001007: //MIM:android:31110LO 0 30 OK.Sending a lot of IM's? Call *611 to add a CDM messaging bundle if you have not signed up for one!
I'm on unlimited so I don't understand this LOL
diehardbattery said:
HBOOT is: 2.21.0000
Radios are: 1.22.10.0310r/1.22.10.0300r
Click to expand...
Click to collapse
Your not on the latest ICS leak. Your on an earlier leak. I suggest at this point installing the latest RUU.
Sent from my ADR6425LVW using XDA
nosympathy said:
Your not on the latest ICS leak. Your on an earlier leak. I suggest at this point installing the latest RUU.
Sent from my ADR6425LVW using XDA
Click to expand...
Click to collapse
Okay.. I'm a bit confused. Were there earlier leaks that would just let you install on a stock phone? I'm not rooted and saw that it was S-ON when I was in the bootloader?
Is the latest ICS the one that was released around 3/17? I just want to make sure I got the right one here...
diehardbattery said:
Okay.. I'm a bit confused. Were there earlier leaks that would just let you install on a stock phone? I'm not rooted and saw that it was S-ON when I was in the bootloader?
Is the latest ICS the one that was released around 3/17? I just want to make sure I got the right one here...
Click to expand...
Click to collapse
Yeah there have been a few leaks. The older ones didn't run so well and didn't have the updated radios or hboot. The RUUs are supposed to be run on a locked phone. They are signed releases from HTC. Yes it was leaked around 3/17. I am on it as are many others and it runs fine.
Sent from my ADR6425LVW using XDA
looks like u just need to flash 2.01.605.11 ruu and you will be stock non-rooted
http://www.scottsroms.com/downloads.php?do=file&id=76
Okay, I flashed with what I think is the latest leak. All bootloader info is the same except I have a radio of 1.22.10.308r is this the latest now?
Still having the same issues.... guess I'm stuck till the official ICS comes out so I can get a replacement?
.... will not be anything that is resolved here. It is a problem with the firmware for ICS.
I was talking to somebody at sprint today while I was there and showing them my device and asking if there will be any issues caused by having a virgin mobile ROM on the device. The lady explained to me that they are exactly the same, get the same reception, same update packages, and work on the same network, etc., etc.... All of this was known to me to some extent, but wanted to hear it from somebody at the company... and told me that the only problem they are having is with ICS in general is that there have been data/radio issues with the Galaxy Nexus line as well ever since it released on their network a few weeks ago.
Furthermore, she explained that this was a known bug/issue and that she knew for a fact that an update would be coming with a fix and that it was being worked on right now.
The reason I wanted to share this was because I have seen a lot of misinformation floating around about 1.) having a virgin mobile ROM on your device and 2.) virgin mobile ROM causing data issues - which is not the cause of the issue as I mentioned just now.
Just want you all to be aware of this in case you were thinking having this software and firmware on your device would cause any issues with your billing, your contract, etc. Simply put - it will not. Virgin mobile is owned by sprint, they run on the same towers, same network, and info of accounts is stored in the same place. You could literally walk into a sprint store to pay your bill for your virgin mobile account.
All is well. All is safe. An update will come to fix the data issues, keep your eyes peeled for it folks. We are not given source code for radios, etc., so unfortunately that needs to be fixed on the carrier/manufacturer end - and as I said, it will be fixed and they are working on it. Sit tight.
Hope this cleared up any misconception floating around.
So, you don't really know how to fix it then? Forgive me for being a little confused, but your title is slightly misleading.
Oh man, you have no idea how much I was freaking out about the billing. Thanks man. (Y)
xHausx said:
So, you're don't really know how to fix it then? Forgive me for being a little confused, but you say there is a problem with the firmware and then say that there is nothing wrong with it?
Click to expand...
Click to collapse
yeah, i can see the confusion there....
re-worded, i would say it appeared to me that people thought there were data issues because of being on a virgin mobile ROM. The point I am trying to express is that the problem is the firmware, not because the ROM is for the virgin mobile 3D - if this same firmware was released for "official sprint RUU" where your banner said "sprint" they would still be having the same issues. Ex.: the lady at sprint said the galaxy nexus was having the same issue.
If that makes sense.
If not, not sure how else I can explain it.
It seemed people were crediting the problem to the fact that there device is attached to virgin mobile - this is not the case.
EDIT*** lol, nice ninja edit haus - you gotta be quicker than that roffle
xHausx said:
So, you don't really know how to fix it then? Forgive me for being a little confused, but your title is slightly misleading.
Click to expand...
Click to collapse
I thought it was the ROM side that is giving the PRL/Data roaming and all the other network problems. Not the firmware. I say this because people have posted that they flashed the firmware, flashed the VM ICS ROM. Then went back to a GB ROM (MeanROM, MIUI, etc) and they had everything working, even though they were on the leaked firmware. But if you flashed that firmware, chad and another dev found a fix, they are going to release it sometime soon.
thread: http://forum.xda-developers.com/showthread.php?t=1638225&page=30
Punk9 said:
I thought it was the ROM side that is giving the PRL/Data roaming and all the other network problems. Not the firmware. I say this because people have posted that they flashed the firmware, flashed the VM ICS ROM. Then went back to a GB ROM (MeanROM, MIUI, etc) and they had everything working, even though they were on the leaked firmware. But if you flashed that firmware, chad and another dev found a fix, they are going to release it sometime soon.
thread: http://forum.xda-developers.com/showthread.php?t=1638225&page=30
Click to expand...
Click to collapse
after half a day of having flashing back they determined the problem to be gone??
......
the issues being caused by the firmware are not constant, and apparently are rather random from what I have read. a perfect example is my own device... no issues with new firmware until today (day 3) of having it, even tho many people reported issues after just a couple of hours.
I'll talk with chad and see what he is cooking up... I havent talked to him a whole lot this weekend.
sent from ICEvo
I've been saying that the roaming problem (if it truly exists outside of people's self affirming observations) only exists on this ROM due to ICS and the lack of roaming options on the rom itself. The radios do nothing to mess up roaming. This is all due to it being a TEST rom that we flashed. It's absurd to think that there is a perfectly functional rom sitting around with no bugs if the only leak we can get is a Virgin Mobile version. We have a beta rom and beta radios, and we should realize that's what we signed up for when we flashed it in the first place.
retnuh730 said:
I've been saying that the roaming problem (if it truly exists outside of people's self affirming observations) only exists on this ROM due to ICS and the lack of roaming options on the rom itself. The radios do nothing to mess up roaming. This is all due to it being a TEST rom that we flashed. It's absurd to think that there is a perfectly functional rom sitting around with no bugs if the only leak we can get is a Virgin Mobile version. We have a beta rom and beta radios, and we should realize that's what we signed up for when we flashed it in the first place.
Click to expand...
Click to collapse
this is true... but again, what is your explanation of the galaxy nexus having the same issue, and the fact that a sprint rep was entirely aware of the issue and that is was being worked on and would come in an update?
and surprise, but any new technology is "beta" ..... whether it is an official release or not. it is the price you pay for cutting edge technology.
sent from ICEvo
So in essence this means that the firmware in the new radio update, which is necessary/part of ics to run on phones is the heart of the data, sms, etc. issues people are having?
There are some differences between how the ROM interacts with the both radios but so far it looks like everything can still be made to work.
If you're having issues with roaming try opening up the build.prop and change 'persist.radio.voice.dom.roam=0' to 'persist.radio.voice.dom.roam=1', and then use setprop to reset it. I haven't been able to test it yet but I'm fairly certain that will bring back roaming.
raptoro07 said:
So in essence this means that the firmware in the new radio update, which is necessary/part of ics to run on phones is the heart of the data, sms, etc. issues people are having?
Click to expand...
Click to collapse
from what the lady explained to me, yes it is... intermittent data loss is a bug within the new firmware for ICS
my point here is that it has nothing to do with your ROM being intended for a virgin mobile 3D. it is because of a bug within the firmware for the radios.
as i said, sprint rep explained this to me, and seemed very confident in the way she explained it - confirming it as a known issue, and also knowing that it would be fixed soon because it was being worked on and said it would be serviced as a firmware update.
sent from ICEvo
You think a sprint tech in the store is an authority !!
For one thing, many may not care, you lose VPN capabilities. Which I need and want and has nothing to do with ICS. Flashed back to GingerBread an it's still gone.
You may also lose the ability to properly update the PRI when new ones come out with official ICS.
It is not just a banner issue.
I'm not in a roaming area to confirm roaming issues but I believe folks when they say they can no longer roam on th 3G. I never touched my default roaming settings and it always worked fine. You may be right that roaming is only ICS issue. But it smells like it's way more than that by folks reports. And quite believable given the phone half believes it's on Virgin Mobile.
It is the PRI which manages routing that is not correct. And different folks will get different issues depending on their location.
I don't think chad and friends would be working so hard to fix it if it was such minor issue and I trust them more than some sprint sales person.
Like was stated above. There are two kinds of people. Those with issues and those with no issues, YET !!
And please FIX the broken subject.
This all reeks of a panic due to us not understanding the new tech in the build we have. These issues may be a side effect of the ICS ROM or could just be issues with the way ICS interacts with the radios. The only information we have is hearsay, and people tend to overestimate effects of things when they don't know what they're looking for.
We get what we deserve for flashing beta radios and a beta rom, tbh. We accepted any possible problems by flashing these and we have nobody to blame but ourselves for not researching first.
"issues" is a vague word. whats to say a person's issue is due to ICS, the radios, or anything else in particular?
The new radios made me gain 20 pounds. There's no information showing that the radios did or didn't cause this. Yet here we are proverbially attributing all these issues to one thing or the other, when in reality WE DO NOT KNOW what is causing these problems.
retnuh730 said:
This all reeks of a panic due to us not understanding the new tech in the build we have. These issues may be a side effect of the ICS ROM or could just be issues with the way ICS interacts with the radios. The only information we have is hearsay, and people tend to overestimate effects of things when they don't know what they're looking for.
We get what we deserve for flashing beta radios and a beta rom, tbh. We accepted any possible problems by flashing these and we have nobody to blame but ourselves for not researching first.
Click to expand...
Click to collapse
People here are not stupid. Most do backups before they try something.
I restored a backup and lost capabilities I had.
I reflashed every every sprint RUU, Reflash Hboot 1.40, restored back up and things are not the same.
If you flashed that freeza patch your phone has it's feet in both Sprint and Virgin Mobile and it's not good.
Yes, we know we screwed up. And some of us would like it fixed before we get more surprises of what does not work correctly.
xHausx said:
There are some differences between how the ROM interacts with the both radios but so far it looks like everything can still be made to work.
If you're having issues with roaming try opening up the build.prop and change 'persist.radio.voice.dom.roam=0' to 'persist.radio.voice.dom.roam=1', and then use setprop to reset it. I haven't been able to test it yet but I'm fairly certain that will bring back roaming.
Click to expand...
Click to collapse
What is the "setprop" an ADB command? Do you have to use it. I edited the build.prop how you said reset the phone and nothing changed. I am roaming and cannot connect to data. My phone's data works fine when in a coverage area, but obviously not when roaming. I never did any kind of firmware update. Hope that helps.
retnuh730 said:
I've been saying that the roaming problem (if it truly exists outside of people's self affirming observations) only exists on this ROM due to ICS and the lack of roaming options on the rom itself. The radios do nothing to mess up roaming. This is all due to it being a TEST rom that we flashed. It's absurd to think that there is a perfectly functional rom sitting around with no bugs if the only leak we can get is a Virgin Mobile version. We have a beta rom and beta radios, and we should realize that's what we signed up for when we flashed it in the first place.
Click to expand...
Click to collapse
This leak isn't a beta, its release keys...
sent from my nocturnaled ics 3vo
powduh09 said:
This leak isn't a beta, its release keys...
sent from my nocturnaled ics 3vo
Click to expand...
Click to collapse
+1 this is a direct pull of the ruu for the upcoming vm evo 3d
Sent from my PG86100 using Tapatalk 2
to anyone that hasn't seen it already, if you flashed this firmware, chad is working on a fix over that this thread
http://forum.xda-developers.com/showthread.php?t=1638225&page=41
xHausx said:
There are some differences between how the ROM interacts with the both radios but so far it looks like everything can still be made to work.
If you're having issues with roaming try opening up the build.prop and change 'persist.radio.voice.dom.roam=0' to 'persist.radio.voice.dom.roam=1', and then use setprop to reset it. I haven't been able to test it yet but I'm fairly certain that will bring back roaming.
Click to expand...
Click to collapse
successfully implemented this. Hope this solves the no roaming issue. Thanks
Visionikz03 said:
successfully implemented this. Hope this solves the no roaming issue. Thanks
Click to expand...
Click to collapse
How were you able to do this? I'm trying to research a little on setprop.....but still not fully understanding it
Sent from my PG86100 using xda premium
So I just wanted to share something really weird and ask if anyone has ever seen anything like it before.
I recently flashed the last AOKP update, and my phone was running phenomenally. I went out last night and my battery died because I forgot to charge it... No biggie. Got home, turned it on, no signal. Odd, since I have pretty decent service in the area. After doing the usual troubleshooting of cycling airplane mode, I tried pulling the battery and sim. That also didn't work. I went into settings to check my APNs, and instead of the usual menu, I saw only 4 options. The option to select APNs wasn't even there. The last one said "Set CDMA..." something. I forget the rest. Wish I had remembered to take a screenshot. In "About Phone", my baseband was blank. Tried reflashing back to LC5 radio. Still nothing. Did a full wipe and reflash of the ROM, and that got me back in business. Right now, all is well. I was just unaware that a phone could magically switch over to CDMA, even if there is no CDMA radio in an i777.
Any thoughts on the cause?
EDIT:
ROM: Task's AOKP 4.14
Kernel: Stock
Radio: UCLL6 when issue started. Now on UCPLC5
Not an issue that's related to the rom, as far as I know. Unless others have reported this issue and I've missed it. If you do a full wipe and re flash as you've done and don't install any programs for a good 24 to 48 hours, and nothing of the sort happens again, odds are it has something to do with an app you installed. Unless your service provider maybe was experiencing problems at the time.
Phalanx7621 said:
Not an issue that's related to the rom, as far as I know. Unless others have reported this issue and I've missed it. If you do a full wipe and re flash as you've done and don't install any programs for a good 24 to 48 hours, and nothing of the sort happens again, odds are it has something to do with an app you installed. Unless your service provider maybe was experiencing problems at the time.
Click to expand...
Click to collapse
No, definitely an anomaly. Not something that anyone else has reported. I called AT&T to verify if there were any issues in the area or with my account, and everything checked out. I haven't downloaded a new application in months. I restored from TiBu right after reflashing and everything is still good. Like I said, not trying to report it or anything; just looking for thoughts.
You meant APN and baseband NEVER come to live? If that's the case, then I haven't heard or read any report about it.
If it's up and running like normal AFTER 5 minutes, then it's has been reported many many times last week.
votinh said:
You meant APN and baseband NEVER come to live? If that's the case, then I haven't heard or read any report about it.
If it's up and running like normal AFTER 5 minutes, then it's has been reported many many times last week.
Click to expand...
Click to collapse
No... More like APN and baseband were completely fine for almost a week, and then it suddenly stopped working while I was asleep.
nycmalu said:
No... More like APN and baseband were completely fine for almost a week, and then it suddenly stopped working while I was asleep.
Click to expand...
Click to collapse
Well, that's new to me.
Reflash with clean installtion?
I know none of us want to factory reset but some cases, we have to.
This is odd but in no way, shape, or form can a i777 transform its hardware to support CDMA
Sent from my Galaxy Nexus
Pirateghost said:
This is odd but in no way, shape, or form can a i777 transform its hardware to support CDMA
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Yes I do agree. ....this is so strange that im putting my phone under 24/7 surveillance. No way I wanna see my phone transformed to CDMA
Hehe....:what:
Sent from SGH-S959G
Pirateghost said:
This is odd but in no way, shape, or form can a i777 transform its hardware to support CDMA
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
This is what I thought. I have a feeling that since AOKP is based of CM, there is code built in to support both CDMA and GSM. Somehow, the software glitched, and made the switch.
nycmalu said:
This is what I thought. I have a feeling that since AOKP is based of CM, there is code built in to support both CDMA and GSM. Somehow, the software glitched, and made the switch.
Click to expand...
Click to collapse
I did confirm your theory. ...playing around to prduce same problem and yes ...very true. ....will play with logcat on next time to save and shoot to CM Team:screwy:
Sent from SGH-S959G
samprocat said:
I did confirm your theory. ...playing around to prduce same problem and yes ...very true. ....will play with logcat on next time to save and shoot to CM Team:screwy:
Sent from SGH-S959G
Click to expand...
Click to collapse
I don't know how you did it, but I'm glad you were able to reproduce the issue. At least I know I'm not crazy.
nycmalu said:
I don't know how you did it, but I'm glad you were able to reproduce the issue. At least I know I'm not crazy.
Click to expand...
Click to collapse
Yes this prop is built in rom just can't find the way to trigger this with log cat on......just need some more playing till this occurre again
Sent from SGH-S959G