Did a search on this and didn't see anything about it, but after flashing to the 2+ ROMs, I've had a pretty bad echo on my end whenever my voice gets much above a whisper. I didn't have this issue on 1.5 and it disappears when I go back to 1.5. Anyone else have this issue or have any idea how to fix it? - other than the obvious 'go back to 1.5' fix
I had this also. If you update to Damage's new rom 2.05 based on the Sprint leak, it is no longer there.
bernard_photography said:
I had this also. If you update to Damage's new rom 2.05 based on the Sprint leak, it is no longer there.
Click to expand...
Click to collapse
have you tried fresh's new ROM? does it have the echo for you also? i'm using it right now and still have the problem. will check out damage's. thanks!
LOL Echo has nothing to do with what rom you're using.
obannvi said:
LOL Echo has nothing to do with what rom you're using.
Click to expand...
Click to collapse
Then why does it reliably disappear when I switch back to any of the 1.5 ROMs and reappear when I go back to 2.1?
p.s. went to damage's most recent ROM and echo disappeared!
jadambpharm said:
Then why does it reliably disappear when I switch back to any of the 1.5 ROMs and reappear when I go back to 2.1?
p.s. went to damage's most recent ROM and echo disappeared!
Click to expand...
Click to collapse
Its called a placebo affect.
obannvi said:
Its called a placebo affect.
Click to expand...
Click to collapse
You're right, obviously, because you're some kind of scientist, right? Point is, it works now.
And it would be placebo effect. You should come take my research methods class
jadambpharm said:
You're right, obviously, because you're some kind of scientist, right? Point is, it works now.
And it would be placebo effect. You should come take my research methods class
Click to expand...
Click to collapse
Actually, no im not a scientist. I worked for a large wireless telecom company for many many years and I know the ins and outs of how a call is made and how echos work and react when they aren't echo cancelled via the echo canceller in the central office.
obannvi said:
Actually, no im not a scientist. I worked for a large wireless telecom company for many many years and I know the ins and outs of how a call is made and how echos work and react when they aren't echo cancelled via the echo canceller in the central office.
Click to expand...
Click to collapse
So you're telling me that it's entirely impossible for something --completely-- on my end that causes me to hear myself a split second after I say something?
jadambpharm said:
So you're telling me that it's entirely impossible for something --completely-- on my end that causes me to hear myself a split second after I say something?
Click to expand...
Click to collapse
Yes. What happens is the call goes through the switching center then goes through an echo canceller to cancel out any echo. Unfortunately, this doesnt happen all the time. When an echo happens that means there are too many calls setup on the switch thats is switching that particular cell site you're connected too. usually it will go away after a few, but sometimes the echo stays and the only way to get rid of it is too start the call over...
obannvi said:
Yes. What happens is the call goes through the switching center then goes through an echo canceller to cancel out any echo. Unfortunately, this doesnt happen all the time. When an echo happens that means there are too many calls setup on the switch thats is switching that particular cell site you're connected too. usually it will go away after a few, but sometimes the echo stays and the only way to get rid of it is too start the call over...
Click to expand...
Click to collapse
Dude... i CURRENTLY work for AT&T and IBM (I know right?) and i can tell you that after being with a telecom company for so long you don't know what you're talking about... Thank you, come again!
Related
at&t 8525 owner, here.
So, I've had this issue for a little while now after I flashed Shadow TE ROM. But it's continued since then... so here's the issue:
I go into work and turn the phone onto vibrate. After I leave work, I switch back to sound on (ring & vibrate). Even though the icon shows the sound is back on, it's not. It only vibrates. It acts as if the speaker is still asleep.
So for awhile I'd have to reset my phone every day to get it working again until I realized I can go into sound settings / notifications and I find that the phone's jumped back to the default ringtone and more than that, I have to literally push PLAY to test the sound in order for the speaker to "wake up" if you will. Then the phone's fine until the next day.
Ok so back to present:
I got fed up and thought it was Shadow TE. So I flashed CRC's v9.2 ROM. Still had the same speaker issue! I was advised to flash a shipped rom.... which I did.... and flashed CRC's v11. Issue still remains.
I've searched the board and could only find one other person make mention of this a couple years ago and no one ever addressed it. Does anyone have any suggestions? I'd appreciate it greatly.
Same problem here with a custom Titan ROM. Installed the same software as every other ROM that I've used so the problem must be in the ROM somewhere.
nonegiven said:
Same problem here with a custom Titan ROM. Installed the same software as every other ROM that I've used so the problem must be in the ROM somewhere.
Click to expand...
Click to collapse
Could be... but why does no one else seem to have this issue? Wouldn't there be tons of people replying here?
I did find that instead of switching it to vibe when I arrive at work, I switch it to silent... and SOMETIMES when I go back to Sound it works ok for a few hours but then it goes back to silent without warning so I miss calls and texts a lot. Might as well force the sound back on through Notifications Menu anyway. I'm SO getting away from Windows Mobile ASAP.
As soon as the Blackberry Bold is released here in the US, I'm buying it.... unless something about it disappoints me, in which case I'll settle for the iPhone 3G. The Bold can't come soon enough.
Who would like to claim this Hermes when I'm through with it? What are you willing to pay?
Try making sure that your ringers are in the windows\rings folder. Saw it somewhere else and it seems to be working.
nonegiven said:
Try making sure that your ringers are in the windows\rings folder. Saw it somewhere else and it seems to be working.
Click to expand...
Click to collapse
Hmm... I tried putting them in, like, 4 places... but none of them seemed to be that location. I'm doing it now and I'll test tomorrow. Thanks for the tip.... i hope it works.
cozbaldwin said:
Hmm... I tried putting them in, like, 4 places... but none of them seemed to be that location. I'm doing it now and I'll test tomorrow. Thanks for the tip.... i hope it works.
Click to expand...
Click to collapse
Sorry to report that this didn't help.
C'mon AT&T... release the Bold.... let's get this thing released already...
cozbaldwin said:
Sorry to report that this didn't help.
C'mon AT&T... release the Bold.... let's get this thing released already...
Click to expand...
Click to collapse
Don't know what to tell you then. Make sure you're not running any 3rd party software.
Well, thats it, I actually can't pick up my phone when I get a call. I can push the green pick up button as many times as I want, but it wont respond, and I end up having to call people back. Anyone else with this issue? (phone info in sig)
I am only going to take a guess and say that you have a lot of programs that run in the background.
Maybe try not using auto rotate.
I agree with Neobbs although when I first read the subject, I thought maybe you needed to work out more....
Same problem here. I can have the phone in my hands looking at it straight up when the phone rings and the phone goes black for about 5 seconds (or about 2 rings) and then the caller id comes up and I start hitting the call/talk button to answer. It goes to VM eventually and me hitting the green button ends up bringing up the recent call list. Auto rotate is disabled, but I do have weatherbug, open home, caller lookup and IM running in the background. Oh... and I have the transistions/animations enabled. That's all i can think of. I'll try removing the caller lookup app to see if it eliminates the problem.
hi,im running rc33 stock rom on bronze tmo g1 in singapore..it happened many a times,even on a cold boot up..wonder what is the actual problem here,mine is not rooted at all..
screamsoflust said:
hi,im running rc33 stock rom ....wonder what is the actual problem here,mine is not rooted at all..
Click to expand...
Click to collapse
why in the world would you do that? (j/k)
bhang said:
why in the world would you do that? (j/k)
Click to expand...
Click to collapse
huh?what do you mean?
screamsoflust said:
huh?what do you mean?
Click to expand...
Click to collapse
he means.. why would you not root your G1???
I think it's a good, fair and valid question.
Do you have installed a customer ring tone ? if yes, choose original ring tone and try again.
I had the same problem when I started using my phone. I dunno what changed but the prob. has disappeared or I got used to hold the pickup button down for a bit longer automatically. I got the feeling that this helped the issue.
My phone is RC33 not rooted... and to answer you question: I've tried but I'm still fighting with my XP to accept the USB driver.
Guess again!
neoobs said:
I am only going to take a guess and say that you have a lot of programs that run in the background.
Maybe try not using auto rotate.
Click to expand...
Click to collapse
mine does the same randomly. Straight after a factory reset.
nothing installed, and my G1 is not rooted (yet).
has anyone found a solution for this problem?
Using RC33 with weatherbug running in the background, but it occurs with it installed and without it installed
I swear, the G1 must be the worst phone ive ever used
can't wait for the touch pro 2 now...
google can't release polished software if their lives depended on it.. selling a beta phone is just bs
n3rdftw said:
has anyone found a solution for this problem?
Using RC33 with weatherbug running in the background, but it occurs with it installed and without it installed
I swear, the G1 must be the worst phone ive ever used
can't wait for the touch pro 2 now...
google can't release polished software if their lives depended on it.. selling a beta phone is just bs
Click to expand...
Click to collapse
Yep, must be terrible if about 4 or 5 people have this problem out of the thousands who have bought it....
I've never had any of these problems, but im guessing they're (probably) firmware related.
Meltus said:
Yep, must be terrible if about 4 or 5 people have this problem out of the thousands who have bought it....
I've never had any of these problems, but im guessing they're (probably) firmware related.
Click to expand...
Click to collapse
most probably just call back and arent bothered to find out how to fix it on xda
anyways, when you say firmware related, what did you mean?
I installed JF 1.42, and before that, his earlier versions, and way before that my phone started out with RC18, which I then rooted. Would it be linked to that? I've wiped my phone like a dozen times, but the problem is reoccurring perhaps once or twice a day, out of about 30 phone calls a day
additionally, although this may be linked to t-mobiles ****ty service, have you guys noticed a large increase in dropped calls?
I use my phone in both austin tx and houston, and in both locations, about every 10 calls is dropped, I dont know if its just the horrible service they have, or when I move from a location with 3g to edge.
With the new radio, the dropped calls have reduced in number, but still occur randomly
Also, one more thing, and a little off topic, but this has been bothering me,
Is there anyone to get a SMS application that allows me to type using a numpad or something similar on the screen? or at least, have spell correct, cause chompsms' keyboard is way too small to use one handed and still have legible messages, unlike the iphone where the errors would be auto corrected
n3rdftw said:
most probably just call back and arent bothered to find out how to fix it on xda
anyways, when you say firmware related, what did you mean?
I installed JF 1.42, and before that, his earlier versions, and way before that my phone started out with RC18, which I then rooted. Would it be linked to that? I've wiped my phone like a dozen times, but the problem is reoccurring perhaps once or twice a day, out of about 30 phone calls a day
additionally, although this may be linked to t-mobiles ****ty service, have you guys noticed a large increase in dropped calls?
I use my phone in both austin tx and houston, and in both locations, about every 10 calls is dropped, I dont know if its just the horrible service they have, or when I move from a location with 3g to edge.
With the new radio, the dropped calls have reduced in number, but still occur randomly
Also, one more thing, and a little off topic, but this has been bothering me,
Is there anyone to get a SMS application that allows me to type using a numpad or something similar on the screen? or at least, have spell correct, cause chompsms' keyboard is way too small to use one handed and still have legible messages, unlike the iphone where the errors would be auto corrected
Click to expand...
Click to collapse
I'm in austin, tx too and I also get the black screen of death almost every time I get an incomming call so maybe it is a location based thing? My g1 is rooted and I have over 70 apps installed and I'm not about to uninstall them 1 by 1 to see which one could be causing it. In the past, rings extended was said to be the one causing the problem but I don't have that installed.
Also, there have been enough requests for t9 and auto correct with chomp, I'm sure it will be in the upcomming updates
Im running Haykuro now and haven't had a single incident so far. Also, I have 73 (yes, seventy-three) MB of free system memory as I moved pretty much EVERYTHING to the SD card. In return, my phone is unable to boot without my SD card... which is a bit strange.
Anyone had this yet? Basically after flashing EVERY version of Damages 2.1 roms and Flipz 2.0d, I seem to have this odd issue where I loose all sound input and output. I noticed first when I was using Flipz, but a wipe and flash of DC 2.05 did the same thing. Weirdest part is, that it's fine for a while after a reboot, then suddenly happens and won't work until another reboot. My only thought is for some sort of software conflict or something, but right now my Hero is basically unusable as a phone since noone can hear me and I can't hear them.
Thoughts? Lil Help?
S
sfox said:
Anyone had this yet? Basically after flashing EVERY version of Damages 2.1 roms and Flipz 2.0d, I seem to have this odd issue where I loose all sound input and output. I noticed first when I was using Flipz, but a wipe and flash of DC 2.05 did the same thing. Weirdest part is, that it's fine for a while after a reboot, then suddenly happens and won't work until another reboot. My only thought is for some sort of software conflict or something, but right now my Hero is basically unusable as a phone since noone can hear me and I can't hear them.
Thoughts? Lil Help?
S
Click to expand...
Click to collapse
I have the exact same issue. Very strange and rare. So the occasional reboot fixes it but annoying at times.
sfox said:
Anyone had this yet? Basically after flashing EVERY version of Damages 2.1 roms and Flipz 2.0d, I seem to have this odd issue where I loose all sound input and output. I noticed first when I was using Flipz, but a wipe and flash of DC 2.05 did the same thing. Weirdest part is, that it's fine for a while after a reboot, then suddenly happens and won't work until another reboot. My only thought is for some sort of software conflict or something, but right now my Hero is basically unusable as a phone since noone can hear me and I can't hear them.
Thoughts? Lil Help?
S
Click to expand...
Click to collapse
I have come across the same today on the 2.05 revision. It started this afternoon, since I have had to reboot 5 times. The latest was only about an hour or so apart. When I make calls, I do not hear any sound, no ring tone, not the other person. Also adjusting the ring volume with the volume keys does not make any sounds. Even on my bluetooth headset I do not get any sound. No rings on incoming calls, no speaker phone ... absolutely nothing. This has become a huge issue an I'm going back to my 1.5 image at this point.
Actually, reading through threads about both ROMS, I'd say there are quite a few people starting to encounter this problem...has anyone with this issue gone back to 1.5 to see if it goes away then?
S
just a note, the people on the other end when making a call can't hear anything either but the call does go through. i had to use the g/f BB to call and my buddy thought it was his phone. I'm so mad because I thought this was a done deal but looks like I gotta go back to 1.5
+1 same issue on Fresh 2.0d
When it happened it affected incoming and outgoing calls, earpiece, speakerphone, microphone -- the works. Person on other end could not hear anything either. Fixed with reboot.
me and my coworker both have this issue with our heroes, he couldn't stand it and went back to fresh 1.1 and it went away
I still get the issue once a day, full reboot solves the issue.
I cant seem to pinpoint when it happens, it just happens.
it started with the first fresh 2.0 and then continued with every 2.1 i have tried
i couldn't find a post in this forum relating to a fix for this, unless someone can prove me me wrong and i hope someone does
+1 same issue on Fresh 2.0d and DCv1
Same as others, a reboot will fix it but by that point you just missed a call.
Or if the sound goes out you might miss a few calls from not being able to hear the phone ring.
yes it is a very large issue. im about to run some tests and i will find out what causes it. hopefully i will have a solution tonight for everyone but its going to be hard.
also the issue effects all sound on the phone and pegs the cpu pretty bad. you cant adjust sound lvls or hear anything from either speaker at all.
im afraid the problem will lie in the boot.img with a driver for sound. because dc2.0r2 did have this issue and also has an incomplete boot.img we may have to deal with no trackball. anyways ill report back asap
Avalaunchmods said:
yes it is a very large issue. im about to run some tests and i will find out what causes it. hopefully i will have a solution tonight for everyone but its going to be hard.
also the issue effects all sound on the phone and pegs the cpu pretty bad. you cant adjust sound lvls or hear anything from either speaker at all.
im afraid the problem will lie in the boot.img with a driver for sound. because dc2.0r2 did have this issue and also has an incomplete boot.img we may have to deal with no trackball. anyways ill report back asap
Click to expand...
Click to collapse
Thanks. You're speaking greek to me as far as the boot.img and all that but if you have an idea of what's going on I'm all ears on fixing it. If there is any sort of info we can provide just let us know.
Im here to help as well, If you need any testers I am willing to do what ever is needed! Anything to fix this problem!
Related?
10chars
http://forum.xda-developers.com/showthread.php?t=657244
Click to expand...
Click to collapse
DroidDhakan said:
Related?
10chars
Click to expand...
Click to collapse
Of course it is,its the fix(hopefully) for it
Hey guys, today I basically re-did the fresh 2.0d rom (Freshly installed), uninstalling some apk from it. Mostly the HTC widgets... I installed Launcher.apk to have a droid like dock.
I am having an issue though, when ever i try and send an mms, I get an error which says "Generic network error". Is the Mms apk not fully supported in this rom?
XxsydenxX said:
Hey guys, today I basically re-did the fresh 2.0d rom (Freshly installed), uninstalling some apk from it. Mostly the HTC widgets... I installed Launcher.apk to have a droid like dock.
I am having an issue though, when ever i try and send an mms, I get an error which says "Generic network error". Is the Mms apk not fully supported in this rom?
Click to expand...
Click to collapse
You are on Sprint, correct? Mms.apk (the one included in fresh) is fully working, no issues at all. Assuming you didn't replace it with something else then it should be fine.
Try updating your profile and prl a couple of times (do profile, then prl, then profile, then prl) and see if it works itself out.
flipzmode said:
You are on Sprint, correct? Mms.apk (the one included in fresh) is fully working, no issues at all. Assuming you didn't replace it with something else then it should be fine.
Try updating your profile and prl a couple of times (do profile, then prl, then profile, then prl) and see if it works itself out.
Click to expand...
Click to collapse
Thanks Flipz, I appreciate the feed back, yes I'm on sprint. Using chompSMS, which to my understanding uses Mms.apk as it's middle man.
Anyways i'll update and get back to you on it. And no i didn't replace it.
EDIT: Also tested it using the default messaging app.
Sorry to double post but apparently that did nothing, I'm beginning to think I should factory reset it.
XxsydenxX said:
Sorry to double post but apparently that did nothing, I'm beginning to think I should factory reset it.
Click to expand...
Click to collapse
You could try flashing fresh on top of itself first without a wipe to see if that helps. If not then go ahead and try doing a data wipe. There haven't been any data issues reported and it's been out for quite some time.
flipzmode said:
You could try flashing fresh on top of itself first without a wipe to see if that helps. If not then go ahead and try doing a data wipe. There haven't been any data issues reported and it's been out for quite some time.
Click to expand...
Click to collapse
Ok it's fixed, I did the profile and pri update a last time just to be sure and it worked.
Ok, now that one bug is down, here is another. When I end a call at times it doesnt make the "BEEP" notifying me the call has ended, (-usually- when i use the end call button on the touch screen) When the beep doesn't sound i instantly know the bug has appeared since I've had it so many times. This bug wont allow me to dial anyone out, or does it? I'm not sure. Why? Because no sound comes out of my speakers. At all, even the tones for adjusting volume.
XxsydenxX said:
Ok it's fixed, I did the profile and pri update a last time just to be sure and it worked.
Ok, now that one bug is down, here is another. When I end a call at times it doesnt make the "BEEP" notifying me the call has ended, (-usually- when i use the end call button on the touch screen) When the beep doesn't sound i instantly know the bug has appeared since I've had it so many times. This bug wont allow me to dial anyone out, or does it? I'm not sure. Why? Because no sound comes out of my speakers. At all, even the tones for adjusting volume.
Click to expand...
Click to collapse
That's actually a known bug with this leak and affects all roms based on it. It's some type of conflict with HTC music. You can check here for a possible fix: http://forum.xda-developers.com/showthread.php?t=657244
Oh great thanks for the help again, In the future i will keep in mind to search the forums better.
Edit: -Odd, I dont even use the music player-
XxsydenxX said:
Oh great thanks for the help again, In the future i will keep in mind to search the forums better.
Edit: -Odd, I dont even use the music player-
Click to expand...
Click to collapse
I've also heard theories that it's related to contacts sync happening. Honestly I've never once had it happen to me, but a lot of people have.
flipzmode said:
I've also heard theories that it's related to contacts sync happening. Honestly I've never once had it happen to me, but a lot of people have.
Click to expand...
Click to collapse
Just like a tootsie-pop.... THE WORLD MAY NEVER KNOW.
I've had this horrible Echo ever since I rooted my phone (4 months or so). I don't hear it but people on the other end hear themselves. I've searched and the only thing I've seen suggested is turning the in-call volume down and that doesn't help either. I've tried several different roms and nothing.
I don't believe I had this problem until I rooted. If the only way to fix the echo is to un-root I'll just get a different phone. It's too boring without root.
Thanks for the help,
did you try *228?
Rooftop-Special said:
I've had this horrible Echo ever since I rooted my phone (4 months or so). I don't hear it but people on the other end hear themselves. I've searched and the only thing I've seen suggested is turning the in-call volume down and that doesn't help either. I've tried several different roms and nothing.
I don't believe I had this problem until I rooted. If the only way to fix the echo is to un-root I'll just get a different phone. It's too boring without root.
Thanks for the help,
Click to expand...
Click to collapse
Can you let us know what ROM/version your running? I know that this problem was much more pervasive across the 2.1 ROM's that folks first rooted too. After going to the 2.2 roms..myself and my family have had no real issues with it. I will say that if you go into an area with 1x coverage vs 3G, I have seen it pop back up but I chalk that up to a coverage issue.
Right now im running Vanilla Tazz 26 but this has been going on with multiple roms, including kaosfroyo V39.
I haven't been able to perform *228 since I've rooted. It never gives me a dial pad when I dial *228. I've always chocked this up to being rooted. Should I be able to perform *228 as I did without root?
I know these are nOOb questions, I really appreciate the help.
Rooftop-Special said:
I haven't been able to perform *228 since I've rooted. It never gives me a dial pad when I dial *228. I've always chocked this up to being rooted. Should I be able to perform *228 as I did without root?
I know these are nOOb questions, I really appreciate the help.
Click to expand...
Click to collapse
Yeah you can still *228. The dialpad is an option when you push menu inside of a call.
Sent from my KaosGingerbread using XDA App
playpolo4life said:
Yeah you can still *228. The dialpad is an option when you push menu inside of a call.
Sent from my KaosGingerbread using XDA App
Click to expand...
Click to collapse
I've always tried pressing menu when I've dialed *228 in the past and nothing. This time I held menu and up comes the keyboard. I was able to update my roaming. I'll see if that fixed the problem. I'm keeping my figures crossed.
Thanks again, I really appreciate it!
Still have the echo. Any other ideas?
Thanks,
i have had to flash a different radio in the past to get rid of an echo. i was running the july radio and had to get the older hero radio posted in the "all radio" thread. be careful when flashing radios, charge fully, etc. also, please post in q&a section next time since your post is not about developing. thanks! hope this helps.