Related
Hey everyone. im from the Hero CDMA forum. i have made audio fix patches for the hero that fixed the audio loss for 2.1 roms.
I recently ended development for the audio fixes because the issue began to rise in people with stock heros. but with that aside, i will create a fix for eris users if enough of you have the problem. i believe i have seen 7-8 people with it. anyways leave a comment telling me you have the issue, when it happened, what roms cause it, and what your software builds are, and what roms dont cause the issue. thanks for the cooperation and i hope i can help
Hey Avalaunchmods!
Thanks for the help with this! I am running the Aloysius (Coincidentally a Hero port):
http://forum.xda-developers.com/showthread.php?t=663893
Audio usually cuts out for me when I am receiving a notification. It will kind of stutter/jitter and then continue to play.
one of my custom ringtones cut out on an incoming call once, but only once. so it may have only been a fluke. hadnt happened before or after.
ivans .8
alexhendershott said:
Hey Avalaunchmods!
Thanks for the help with this! I am running the Aloysius (Coincidentally a Hero port):
http://forum.xda-developers.com/showthread.php?t=663893
Audio usually cuts out for me when I am receiving a notification. It will kind of stutter/jitter and then continue to play.
Click to expand...
Click to collapse
I get the same using VanillaDroid ROM.
Thanks for the help!
I have had this problem pop up intermittently, but with increasing regularity (up to 2-3 times daily at its worst). The sound profile and volumes remain unchanged, but sometimes for no apparent reason, all audio drops. If I get a call, there is no ringer. If I get a notification, there is no audible alert. If I place/answer a call, the earpiece/speakerphone are silent, and the other party doesn't hear me. The rest of the phone's functions still work, and vibrate still works, but there is no audio from any apps or OS functions until I reboot the phone.
As for particular triggers, I haven't found any yet. I had been running ivan's 0.8t2, but have downgraded to his older 0.5.4 to see if the problem is fixed. So far it hasn't popped up, but it's only been a few days.
Thanks again for your willingness to help. I'll be sure to let you know if I see the problem resurface.
I know the fix is only possible in rooted phones, but I wanted to chime in and let you know that a lot of people on 2.1 leak v2 non-rooted are having this issue, so you can see some of the symptom reports in these threads on androidforums:
http://androidforums.com/htc-droid-...en-phone-goes-silent-multiple-times-week.html
http://androidforums.com/htc-droid-eris/57804-calling-problems.html
thenestor said:
I know the fix is only possible in rooted phones, but I wanted to chime in and let you know that a lot of people on 2.1 leak v2 non-rooted are having this issue, so you can see some of the symptom reports in these threads on androidforums:
androidforums.com/htc-droid-eris/66298-phone-useless-when-phone-goes-silent-multiple-times-week.html
androidforums.com/htc-droid-eris/57804-calling-problems.html
Click to expand...
Click to collapse
I have a non-rooted phone and I have the same issues...
If by audio problems, you mean no sound via ringtones, notification or voice over the ear piece, then I have experienced it with Ivan's 08T2. I've had it happen about three times. I did a reboot and it corrected it.
another Aloysius user here, and yep, audio problems out the wazoo. good thing I text mostly.
alright this got moved to general?
i though this would fit in development haha.
anyways ill get on a fix i believe. ill put it somewhere. not dev..
I've had audio issues, but the only thing that seems to cause it for me us getting a force close on any program that is currently playing audio, such as a music player or (worse) an alarm clock.
I've never had audio just randomly cut out on me, but it definitely all stops working after such a force close
I'm having the same audio issues. I'm currently on VanillaDroid v1.0. I experienced the issue on the eris21official-root ROM as well. It usually happens after I use the camera to snap a few pictures. If I don't use the camera, it is pretty stable. Let me know if you need any further information.
Avalaunchmods said:
alright this got moved to general?
i though this would fit in development haha.
anyways ill get on a fix i believe. ill put it somewhere. not dev..
Click to expand...
Click to collapse
Thanks ..... I don't think I have had these problems (but maybe I have and just didn't realize it) but its nice nowing there is a fix out there and people like you are out there using your time to create fixes
I i use it ..... i will "buy your time back"
Avalaunchmods said:
Hey everyone. im from the Hero CDMA forum. i have made audio fix patches for the hero that fixed the audio loss for 2.1 roms.
I recently ended development for the audio fixes because the issue began to rise in people with stock heros. but with that aside, i will create a fix for eris users if enough of you have the problem. i believe i have seen 7-8 people with it. anyways leave a comment telling me you have the issue, when it happened, what roms cause it, and what your software builds are, and what roms dont cause the issue. thanks for the cooperation and i hope i can help
Click to expand...
Click to collapse
Avalaunchmods,
Since the Droid Eris kernel code was made available from HTC, have you been able to make any further progress fixing the audio loss bug for the Eris and Hero?
Right now the only solution we know of is to replace the phone. (Those of us who have gotten warranty replacements have not had the problem resurface.)
But even if the problem is related to certain hardware, it seems like there might be a way to fix the kernel's *reaction* to the problem, so that the phone doesn't become unusable.
Having the problem too.
Happened on Evil Eris and Ivans.
Any update on this? I am having the same issue on both CyanogenEris v1.1 and ELB-Cyanogen.
i am having this issue as well, running Ivans Eris_Official 1.0 Alpha. Experienced this issue on the 0.82t also. No audio from the phone's earpiece (speakerphone wont work either) when a call comes in, or if i try to call them back. have to reset the phone and then it works. I'm running setcpu at 710 now, but i wasn't on 0.82t so probably not the culprit.
My software version stats, in case it matters -
Firmware - 2.1
Baseband - 2.42.00.04.12
Kernel - 2.6.29oc [email protected]#26
Build # - 2.36.605.1 CL1165907 release-keys
Software - 2.36.605.1
PRI - 2.11_002
PRL - 51739
Eri - 5
*double post oops*
hi..i'm havin this issue too!
I'm on a froyo rom now. I was on an xtr rom when I noticed this problem. Tried to flash a new rom to get rid of it and it's still there. I can use the phone for a few hours and then the only way i can answer calls is through speakerphone.
Model Number-FroyoEris
Android Version-2.2
Baseband-2.42.00.04.12
Kernel - 2.6.29 [email protected]#3
build number-kaosfroyo v13
HEEELLLLPPPP!!!!
Audio Problem
I've had this problem every since the 2.1 update. My wife and I both had it (we both have a Eris) on unrooted phones. I rooted to ErisLightning and still had it, switched to Tainted Vanilla, and now I'm on Lightning Bolt. My wife is on Droid Does Pink and we've had the problem with every single rom. Sometimes when we receive or make calls, the phone will go completely mute. We can't hear the other person and they can't hear us. We can't hear a ring tone if calling someone either.
I use Google Voice and I sometimes get ghost voicemails. It will save the entire length of the voicemail, but it will be completely mute. Even if I restart and re-open GV it's still mute.
For now, we're just rebooting whenever we have this problem. Seems to be the only way to get audio back.
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.
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
Hello gentlemen!
First of all, I want to thank neobuddy and everyone that he worked with on the ICS Passion ROM. I find it excellent and have been using it for the past week or so.
I do have a slight issue, though, and as I am not yet familiar with mobile development, I am not sure if the problem stems from my hardware or the software. I bought this Vibrant used, though in excellent condition. As soon as it arrived, I rooted it and installed ICS Passion on it. Therefore, I never actually used the stock software, and that is why I am unsure if this issue stems from the ROM or from the phone itself.
Anyway, my problem is that sometimes during a call, my voice will cut in and out very frequently. This occurs with various people and in various places, so it doesn't have anything to do with signal strength. I can hear the other person just fine. It also seems to only occur when I receive a call. Once I hang up and call the person back, they seem to be able to hear me just fine.
I suspect that this has something to do with one of the following:
1) Sound filtering and normalization. The way that the software handles the data that it receives from the microphone. If it was the microphone itself, I would expect this issue to be much more consistent.
2) Which network the phone uses during phone calls. I've gathered that H is for data transfer and 3G is for phone calls (for the most part). Is it possible that ICS Passion somehow fails to switch to the proper network when a call is received? This seems unlikely as I searched through the ICS Passion thread in the dev forum, but couldn't find an issue similar to mine.
Any insight would be appreciated, although I suppose if no one can help out I can just flash the stock and see if the problem persists. If it does, then I can only assume it's the phone.
Thanks!
try v 10 or v 10.6
Mute and then unmute your call. We've had this problem since cm7
Sent from my SGH-T959 using XDA App
bfranklin1986 said:
Mute and then unmute your call. We've had this problem since cm7
Click to expand...
Click to collapse
Sweet, good to know, thanks. Do you know of a more permanent solution?
LDKnight said:
try v 10 or v 10.6
Click to expand...
Click to collapse
I'm afraid to upgrade to v10 because some people have been experiencing issues with their phones rebooting several minutes into the call. I may try it anyway, though.
Do you know if your problem is with incoming calls only?? That's where the issue seems to be, that the mute/unmute fixes. I put 10 on about a week ago, and am loving it. Put 10.5 on yesterday, and 10.6 today, so they are working on it. I think 10.6 might have fixed it for me, so I'm so happy. Thought Bionix was going to be the end of the line, I tried a couple of gingerbread roms, and had issues!
ProfessorKazuki said:
Sweet, good to know, thanks. Do you know of a more permanent solution?
I'm afraid to upgrade to v10 because some people have been experiencing issues with their phones rebooting several minutes into the call. I may try it anyway, though.
Click to expand...
Click to collapse
Been on v10 for a week and have not had the reboot problem. I've heard 10.6 has some problems but yeah the mute/unmute bug isn't that bad you get used to it
Sent from my SGH-T959 using XDA App
kenrb said:
Do you know if your problem is with incoming calls only?? That's where the issue seems to be, that the mute/unmute fixes. I put 10 on about a week ago, and am loving it. Put 10.5 on yesterday, and 10.6 today, so they are working on it. I think 10.6 might have fixed it for me, so I'm so happy. Thought Bionix was going to be the end of the line, I tried a couple of gingerbread roms, and had issues!
Click to expand...
Click to collapse
That's what it seems like. I have not had a single "you sound like you're underwater" issue for outgoing calls.
Thanks for the responses, everyone. I'm glad to find out that the problem isn't with the phone because I can't afford to replace it for a while. I guess I'll just wait a bit and hope that these slight issues get resolved in a more stable iteration.
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?