Before attempting an install of this ROM, I researched and followed Haykuro's instructions and my first attempt worked without issue. That being said...
I've searched plenty on the issue I'm curently having and posted twice in the existing "Unwatermarked HERO thread", but have not seen any information regarding this problem yet other than 3 - 4 other people having the same problem. Quite possibly it's not overly common.
It was pointed out that this issue existed in a previously released "H" cooked ROM and was later solved by Haykuro himself :
metasage said:
Ack.. it's back. I was experiencing this in the early Haykuro 4.0-5 builds.
Haykuro fixed it several builds later. I never did find out what the problem/solution was.
Issue:
http://code.google.com/p/sapphire-port-dream/issues/detail?id=89
Click to expand...
Click to collapse
The problem seems to be the amp/preamp for the mic which is causing distortion due to its being overdriven (think electric guitar distortion). If the incoming preamp signal level is too high, it raises the noise floor causing the signal to noise ratio to decrease hence the distortion (in RF anyways). After unzipping the hero-signed.zip file and poking around a bit (I by no means claim to be a developer), I found a file that seems might control these settings under /system/etc/AudioPara4.csv. I could be wrong and would appreciate someone who understands the inner-workings of the hardware/software interface control giving their 2 cents and possibly pointing me in the right direction.
The ROM is aesthetically beautiful and mostly usable. I appreciate all who worked so hard to bring it to its current usable state (props to Haykuro and others whom I may not know of). The main thing holding me back is this one issue as it prevents any use of the phone call functionality. Any serious questions, opinions or insight are greatly appreciated.
Aloha,
bg
I'm having this problem... I can hear people just fine... there is some static but its not too bad...but people on the other end think I'm a soloist for a heavy metal band who added distortion even to his phone...
maubig said:
Before attempting an install of this ROM, I researched and followed Haykuro's instructions and my first attempt worked without issue. That being said...
I've searched plenty on the issue I'm curently having and posted twice in the existing "Unwatermarked HERO thread", but have not seen any information regarding this problem yet other than 3 - 4 other people having the same problem. Quite possibly it's not overly common.
It was pointed out that this issue existed in a previously released "H" cooked ROM and was later solved by Haykuro himself :
The problem seems to be the amp/preamp for the mic which is causing distortion due to its being overdriven (think electric guitar distortion). If the incoming preamp signal level is too high, it raises the noise floor causing the signal to noise ratio to decrease hence the distortion (in RF anyways). After unzipping the hero-signed.zip file and poking around a bit (I by no means claim to be a developer), I found a file that seems might control these settings under /system/etc/AudioPara4.csv. I could be wrong and would appreciate someone who understands the inner-workings of the hardware/software interface control giving their 2 cents and possibly pointing me in the right direction.
The ROM is aesthetically beautiful and mostly usable. I appreciate all who worked so hard to bring it to its current usable state (props to Haykuro and others whom I may not know of). The main thing holding me back is this one issue as it prevents any use of the phone call functionality. Any serious questions, opinions or insight are greatly appreciated.
Aloha,
bg
Click to expand...
Click to collapse
could this help you out: here
Next time please post in the correct thread/forum. Thank you.
xidominicanoix said:
could this help you out: here
Click to expand...
Click to collapse
I've seen that thread, but it claims to make the phone louder. My problem is the ROM's interfacing with the microphone making the callers voice loud and distorted. Does this mod also allow you to reduce volume from its current state? Guess I'll just try it anyway, I've got time to kill.
Thanks for the reply!
Is it intermittent, often reproducible, or 100% of all calls?
ckrest said:
Is it intermittent, often reproducible, or 100% of all calls?
Click to expand...
Click to collapse
Its on every call using the Hero ROM. People tell me it sounds like I'm yelling into the phone and its VERY distorted. Which makes it unusable. ION and all other builds are fine.
This describes my problem exactly...
http://code.google.com/p/sapphire-port-dream/issues/detail?id=89
so I know Haykuro has fixed it b4 on another build.
I love the hero build but this issue and force closes r to much right now until this issue is resolved I'm going back to cyans mod.
jmotyka said:
I love the hero build but this issue and force closes r to much right now until this issue is resolved I'm going back to cyans mod.
Click to expand...
Click to collapse
Force closing is not the prob I'm having, but I'm willing to help you as much as I can with your problem. I can tell you what steps I took to get the install working in a mostly stable condition. Just let me know.
Using 8GB class 4 w/2 partitions (FAT32 1st and ext2 2nd). Using 500MB for ext2.
maubig said:
Force closing is not the prob I'm having, but I'm willing to help you as much as I can with your problem. I can tell you what steps I took to get the install working in a mostly stable condition. Just let me know.
Using 8GB class 4 w/2 partitions (FAT32 1st and ext2 2nd). Using 500MB for ext2.
Click to expand...
Click to collapse
Try using one of the sound mods, you are correct about that file.. Replace it.
ckrest said:
Try using one of the sound mods, you are correct about that file.. Replace it.
Click to expand...
Click to collapse
Many thanks for your vote of confidence! I pulled (using adb of course) the 3 .csv audio files used in /system/etc on the HERO build (AudioPara_TMUS.csv does not exist in this build):
AudioPreProcess.csv
AudioFilter.csv
AudioPara4.csv
Then pushed those same files I extracted from H's ION build I'm using regularly (which I love; thanks Haykuro again its my favorite build so far!) back to HERO's /system/etc and it seems much more tolerable now. Will need to keep testing but I think that did it. Thanks again man. I havent looked at Meltus thread on increasing audio (http://forum.xda-developers.com/showthread.php?t=517745) in depth before today, but it now helped me to understand a little more what I was dealing with. Thanks to all (Meltus's thread included) who pointed me in the right direction. Will update later after more testing. It's 12:37am here in the 50th state so my test calls will have to wait till tomorrow.
Aloha!
maubig said:
Many thanks for your vote of confidence! I pulled (using adb of course) the 3 .csv audio files used in /system/etc on the HERO build (AudioPara_TMUS.csv does not exist in this build):
AudioPreProcess.csv
AudioFilter.csv
AudioPara4.csv
Then pushed those same files I extracted from H's ION build I'm using regularly (which I love; thanks Haykuro again its my favorite build so far!) back to HERO's /system/etc and it seems much more tolerable now. Will need to keep testing but I think that did it. Thanks again man. I havent looked at Meltus thread on increasing audio (http://forum.xda-developers.com/showthread.php?t=517745) in depth before today, but it now helped me to understand a little more what I was dealing with. Thanks to all (Meltus's thread included) who pointed me in the right direction. Will update later after more testing. It's 12:37am here in the 50th state so my test calls will have to wait till tomorrow.
Aloha!
Click to expand...
Click to collapse
I fixed the AudioPara_TMUS.csv problem by just copying the AudioPara4.csv to AudioPara_TMUS.csv all errors went away and have better quality audio, but I am not on hero.
neoobs said:
I fixed the AudioPara_TMUS.csv problem by just copying the AudioPara4.csv to AudioPara_TMUS.csv all errors went away and have better quality audio, but I am not on hero.
Click to expand...
Click to collapse
After some testing, it seems that replacing those files fixed my mic problem. Now the earpiece is too amplified lol. I'll have to try that today neoobs, and see the result. Just glad I'm on the right track now. Thanks for everyone's input. GREATLY appreciated!
Aloha-
Related
Hey guys!
Alright so I'm having a new issue with my G1 thats truly driving me nuts. Pretty much the long and short of it is that the volume of my earpiece during calls is really quiet.
I did a few things to try and fix it:
Tried switching builds (Haykuro's to the Dude's Build)
Tried a clean wipe
Disabled App2SD
Downloaded Volume Control
Anyways so I was hoping someone else who might have had a similar problem figured something out to fix it. Help? Please? : )
I only had this problem with the dude's earlier builds but I just connect/disconnect it to a bluetooth device and the speaker sound would be loud again.
I never experienced the sound issue in jf1.5 though.
Alright well after much poking and fixing I finally decided that the problem had to rely in the hardware. So I called up tmobile and their sending me a new one.
Tried out your tip though Dr and still no luck for me.
As a side note, Tmobile tech support gets really funny when you mention root.
TS: Have you checked out androidcommunity.com?
Me: Oh ya! Is that the place where you get that root app or whatever from?
TS: Get what?
Me: I think its called root?
TS: .....not sure what that is....
Info in my sig. I was on a previous version of CM (4.2.12.2, iirc) and had no problems. It did run sluggish, but was guessing it was due to my class 2 sd card and using swap/ext/fat32 on it.
I repartitioned my card to all fat32 and loaded 4.2.13 yesterday. It runs much faster, much more responsive than before.
Now, when on a call, it sounds like it's breaking up, like I have bad signal every once in a while. When it would do it, I checked and had 3G and 3-4 bars. I was at my house, where I've never had problems before. This happened both with just the my3g and on a BT headset. Initially I thought it was where I was in the house, but it happened no matter where I went.
I searched and found a thread titled "Background noise" talking about improved call quality. I can't post a link because I'm a no0b, but here's the info, with attached filename Audio-mic-gain-fix.zip:
scheng said:
Is there any way to reduce the background noise of the Magic on the voice call? Will it be improved by updating the latest radio?
Click to expand...
Click to collapse
sombionix said:
You can try this. It has improved my call quality a lot. Follow these instructions using terminal app.
*unzip the files using astro or file manager of your choice*
Open terminal emulator
Type - su (enter)
Type - mount -o remount,rw /dev/block/mtdblock0 /system
Type - mkdir /sdcard/mic
Type - cp /system/etc/* /sdcard/mic
Type - cp /sdcard/download/*.csv /system/etc/ (or whatever directory you unzipped to)
Type - reboot
Click to expand...
Click to collapse
sombionix said:
Are you rooted with a modified ROM? If so, many people have complained about poor call quality, distortion, etc. This file has fixed this problem in many cases. The *'s stand for 'files'. If you call out an * in a command it pulls all files in that directory. However, another example would be *.csv, which would only pull .csv files, or whatever file extension you put after the *. Sorry, hopefully that makes sense.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Since the file is named audio mic gain fix, it seems this is more for the mic gain, not the ear speaker.
Am I having the problem this is intended to fix?
Thx!
If you're having a problem with your ear piece (speaker), I don't think the mic-gain file will help with your situation. The mic-gain file was intended to improve call quality via the microphone. Some users were claiming that the people they were calling said they could hardly hear them or that there was distortion and background noise.
I don't believe there have been any reported issues with the ear piece using any Cyanogen ROMS, but I could be wrong. Sounds more like a hardware issue. One way to test is to downgrade to a previous ROM and see if you still have the issue. If so, more than likely, its a hardware problem.
Good luck!
That's kinda what I figured. I'll continue using it to see if I still have probs. If so, I'll try a different ROM.
thx for the infoz.
This might not help but I had the same problem when updating from 4.2.5 to 4.2.13. It was fine on 4.2.5 and had a little background noise frequently. But once I upgraded to 4.2.13 calls were horrible all the time, the person could barely hear me. I decided to do a warranty exchange and unrooted it. Calls were fine once I was on stock 1.6, still had some background noise but not on all calls.
Got my replacement the next day, rooted straight to 4.2.13 and had no problems cept for the background noises every now and then.
I have a MyTouch3G as well.
Weirdkid said:
This might not help but I had the same problem when updating from 4.2.5 to 4.2.13. It was fine on 4.2.5 and had a little background noise frequently. But once I upgraded to 4.2.13 calls were horrible all the time, the person could barely hear me. I decided to do a warranty exchange and unrooted it. Calls were fine once I was on stock 1.6, still had some background noise but not on all calls.
Got my replacement the next day, rooted straight to 4.2.13 and had no problems cept for the background noises every now and then.
I have a MyTouch3G as well.
Click to expand...
Click to collapse
Maybe I'm misunderstanding, but are you saying that you exchanged your phone to fix your problem? I highly doubt that the Cyanogen ROM you had installed caused a hardware problem. Could have possibly caused a glitch if you didn't install it correctly. However, you should have just wiped everything and tried again. Or, if you were really feeling up to it, started from scratch by unrooting in fastboot with the SAPPIMG.nbh, then rooting again with the recovery image and ROM of your choice.
fwiw, I did a wipe, reformated the sdcard, and a fresh install of CM 4.2.13.
I have a feeling it was just poor reception at the time. I don't talk on the phone that often, but used it today for about 5 mins and it seemed fine. I was riding in a car and background noise was loud (my buddies arguing over steroids & McGwire, lol), but the guy on the other end had no probs hearing me.
Glad to hear you got it fixed.
Sorry, I guess that was out of context. That was @Weirdkid, stating that I didn't do an upgrade like he did. I haven't touched it since yesterday, I wanted to let roll to see how it plays out.
sombionix said:
Maybe I'm misunderstanding, but are you saying that you exchanged your phone to fix your problem? I highly doubt that the Cyanogen ROM you had installed caused a hardware problem. Could have possibly caused a glitch if you didn't install it correctly. However, you should have just wiped everything and tried again. Or, if you were really feeling up to it, started from scratch by unrooting in fastboot with the SAPPIMG.nbh, then rooting again with the recovery image and ROM of your choice.
Click to expand...
Click to collapse
Not quite, I was already getting static every now and then even before root(I thought I could live with it). It was just a little glitch I guess and that pushed me to get an exchange. After the unroot and back to Donut, the glitch with all calls getting low quality was gone but still getting minor static noise every now and then(just like before). Sorry for the confusion.
Okay, so I continued to have poor call quality and 3 calls were dropped. I went back, did a full wipe, no swap/ext, and reloaded CM4.2.13 and had the exact same problems.
I decided to load Dwang's rom and no longer have the problem of dropped calls and/or poor call quality.
cougar694u said:
Okay, so I continued to have poor call quality and 3 calls were dropped. I went back, did a full wipe, no swap/ext, and reloaded CM4.2.13 and had the exact same problems.
I decided to load Dwang's rom and no longer have the problem of dropped calls and/or poor call quality.
Click to expand...
Click to collapse
Yeah, I stopped using Cyan's ROM when the 4.2.10 release came out. Great ROM, just seemed to have increasing issues after 4.2.9. You should try the Super D rom. Fastest and most stable ROM I've run, hands down.
http://forum.xda-developers.com/showthread.php?t=613809
Thanks for the the recommendation, I was looking at that one, but haven't changed my SPL. No reason, just haven't ventured down that road yet.
I've been looking at the 10mb ram hack, searching for pros/cons, but just see people using it and no full explanation of it.
Is there any real benefit to it, and what does it actually do?
cougar694u said:
Thanks for the the recommendation, I was looking at that one, but haven't changed my SPL. No reason, just haven't ventured down that road yet.
I've been looking at the 10mb ram hack, searching for pros/cons, but just see people using it and no full explanation of it.
Is there any real benefit to it, and what does it actually do?
Click to expand...
Click to collapse
Not a problem. Also, if you have a mt3g, you don't need to upgrade your SPL to run the Super D rom. Aside from that, just make sure you have the correct radio, then do a full wipe and flash the ROM.
In regards to the 10mb ram hack, it definitely increases system speed and performance. So that would be your 'pro'. However, the ram hack is created by pulling 10mb of ram that would normally be used for graphical processes, and instead applies it to your operating system. The con would be a decrease in 3d game performance. So, if you play a lot of 3d games, then I wouldn't recommend the 10mb ram hack. If you don't, then use it. Currently, the only Super D rom you can download that doesn't have the ram hack is the 1.6.6 beta, which as of right now is fairly stable. However, If you are considering switching to this rom, just wait a couple days, the developer has announced that he is releasing the 1.7 stable version this week. I'm assuming he will have two separate downloads. One with the ram hack, and one without.
Btw, I didn't see your phone setup before my last post. You DO have the correct radio to run the Super D rom. So, all you have to do is a full wipe and flash the rom.
Nice! I forgot I was reading the page in the Dream/G1 section...I got this one how I like it, so I'll roll with it a few days and keep an eye out for Super D 1.7.
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
Dear,
I have this issue all the time , it seems that it happens on all Android Builds and i always use the volumeup workaround (volume up then volume down).
Is their any way to change the default volume value.
I haven't got that problem.
You should ask your problem in your build's thread, as it's build-related
hrockh said:
I haven't got that problem.
You should ask your problem in your build's thread, as it's build-related
Click to expand...
Click to collapse
Four of my friends have TMOUS everyone have different version and they all have the same problem.
can you tell me your HD2 information ................
zaidsa3sa3 said:
Dear,
I have this issue all the time , it seems that it happens on all Android Builds and i always use the volumeup workaround (volume up then volume down).
Is their any way to change the default volume value.
Click to expand...
Click to collapse
I wish I had your problem, but then again whats loud to one could be soft to another, is your problem in call? or is yours the speaker is too loud? (Ringer volume)
If its the ringer volume, then I want your problem!
I have sensitive ears but my EVO in-call speakers are too low. The externals are really good though.
from my EVO using XDA app.
jacoballen22 said:
I have sensitive ears but my EVO in-call speakers are too low. The externals are really good though.
from my EVO using XDA app.
Click to expand...
Click to collapse
Wanna rip your acdb files from etc/firmware so I can try it on my soft spoken HD2?
AngelDeath said:
Wanna rip your acdb files from etc/firmware so I can try it on my soft spoken HD2?
Click to expand...
Click to collapse
Lol idk about that..i just remember someone showcasing their hd2 to me and making fun of my EVO cause they had a faster phone with a bigger sd card and they could run android on it..
from my EVO using XDA app.
PPl. my problem is as follows :
1- make a call set the incall - volume to min
2- end the call
3- make a new call you will notice that the volume is still to high ( but the incall volume bar shows that your volume is min.
did you get my points
i tried 70% of the builds with different radio version and i still have this porblem
zaidsa3sa3 said:
PPl. my problem is as follows :
1- make a call set the incall - volume to min
2- end the call
3- make a new call you will notice that the volume is still to high ( but the incall volume bar shows that your volume is min.
did you get my points
i tried 70% of the builds with different radio version and i still have this porblem
Click to expand...
Click to collapse
Got the exact same problem! I wish there was a solution to this as everything else is running flawlessy ([RAM] darkstone SuperRAM FroYo v1.5 [kernel: Hastarin custom])
Guys, I've also been having this same volume problem across three different Android builds. It seems it's NOT an isolated case. There are dozens of posts across dozens of bulletin boards. Here are just three such examples:
http://code.google.com/p/android/issues/detail?id=2973
http://code.google.com/p/android/issues/detail?id=10660
http://androidforums.com/htc-hero-sprint/23885-your-call-volume-too-loud.html
I really hope we can get some of the ROM devs to look at this, because the phone is virtually unusable for me with this present problem.
Thanks!
BillTheCat said:
It seems that our troubles can be solved by finding and editing startup.txt, but I'll be buggered if I can find where the heck it is.
Click to expand...
Click to collapse
Startup.txt is in the Android folder, for SD builds only. I've had a look in build.prop (the first place that comes to mind for this kind of thing) but it's not in there either.
johncmolyneux said:
Startup.txt is in the Android folder, for SD builds only. I've had a look in build.prop (the first place that comes to mind for this kind of thing) but it's not in there either.
Click to expand...
Click to collapse
Thinking that the reference in that post was for WM, I edited my post to remove it. But nevertheless, the problem remains, and it's really troubling. The phone is barely usable in this condition. Makes me want to <gasp!> go back to WM until it's sorted out.
Got the same problem, with any android build, to me it's a major issue, that makes me switch back to winmo, actually there's a kind of "workarround", even if you have your volume @ min, try getting it one step higher, it will actually become less loud; dunno mebbe it has been mentioned, anyways, it seems not too many ppl actually care about this...
this is the only build that have this problem fix
[Feb 01][DL DesireZ v3.4][DL Data2SD/Ext4 v2.6][Nand/SD/MAGLAR]
http://forum.xda-developers.com/showthread.php?t=913597
romka.t said:
Got the same problem, with any android build, to me it's a major issue, that makes me switch back to winmo, actually there's a kind of "workarround", even if you have your volume @ min, try getting it one step higher, it will actually become less loud; dunno mebbe it has been mentioned, anyways, it seems not too many ppl actually care about this...
Click to expand...
Click to collapse
Dear we know this work around but we need a real fix for this problem.
zaidsa3sa3 said:
this is the only build that have this problem fix
[Feb 01][DL DesireZ v3.4][DL Data2SD/Ext4 v2.6][Nand/SD/MAGLAR]
http://forum.xda-developers.com/showthread.php?t=913597
Click to expand...
Click to collapse
If you are talking about fix posted in this thread it's not working with diffirent roms (tested on Ginger v2.7 and MDJ kernel)
crow6 said:
If you are talking about fix posted in this thread it's not working with diffirent roms (tested on Ginger v2.7 and MDJ kernel)
Click to expand...
Click to collapse
I tried the build and it is working but i tried to use the fix in another builds and it didn't work
i have this problem, too
I'm install all last ROM but problem remain
saap said:
i have this problem, too
I'm install all last ROM but problem remain
Click to expand...
Click to collapse
I have too..
I don't know if this is any sort of a clue to devs who might be looking on here, but it seems that the problem is the OS is changing volume levels triggered by some event, probably an incoming call.
I've come by this observation after installing a volume widget where I observed the volume setting changing to go higher. Perhaps there's a bug where the OS is not differentiating between the speaker and the earpiece.
Hope that's a clue for you tech guys out there to look at what might be going on "under the hood". This is a really annoying problem and nearly makes the system unusable, and it's a shame.
HI,
Firstly this started 5wks ago out of the blue.
My problem is I cannot hear a voice from an incoming call!
I can be heard on both incoming and outgoing calls
It has worked on a couple of occasions for a few seconds but is very distorted and sometimes you can hear them faintly in the background for a few seconds.
Works fine on speaker and headphones.
I’ve tried numerous roms clean installs, swapping kernels …blah blah blah
I’m at a complete loss and its driving me friggin crazy!!
I have a Logcat of me making a call.
I’m hoping that someone will be able to decipher and point me in the right direction.
From what I see its routing audio to speakerphone and not handset??
I don’t know if this the correct way to post a log…if not go easy on me…
Any help will be greatly appreciated.
+Thanks for taking the time to look.
As you've tried everything else - did you also try another radio?
Dr_Grip said:
As you've tried everything else - did you also try another radio?
Click to expand...
Click to collapse
Hi,
the only other radio I have tried Leo_RADIO_2.14.50.02 and sadly the same.
Just about to install Dorimanx new rom + kernel v1.6 (Fingers crossed)
Thanks for taking the time to reply...
EDIT: Installing new rom+kernel has made no difference.
a3r0n1 said:
Hi,
the only other radio I have tried Leo_RADIO_2.14.50.02 and sadly the same.
Just about to install Dorimanx new rom + kernel v1.6 (Fingers crossed)
Thanks for taking the time to reply...
EDIT: Installing new rom+kernel has made no difference.
Click to expand...
Click to collapse
Weird idea: flash a stock HTC WinMo ROM to rule out hardware error.
Thread closed
Dr_Grip said:
Weird idea: flash a stock HTC WinMo ROM to rule out hardware error.
Click to expand...
Click to collapse
Considered that as a last resort.
Haven’t yet looked into it, was hoping that I din't have to go down that road.
I’m assuming that there is a fare amount involved in doing so?
Cheers
Edit: Installed WinMo NRG Energy rom and have the same problem!
I'm now assuming that this is unfortunately a hardware issue
Thanks Dr_Grip for input - Appreciated
Thread closed