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.
Related
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.
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-
Recently my phone started acting a little unusual. For instance, composed email weren't being sent out while syncing and a wipe and reflash seemed to fix it at first. This problem continued to get worse and at the same time, I started getting SD card ejected notifications seemingly without reason. Now it's to the point that my phone is completely unusable/useless. IF it boots all the way up, it will lock and then just go black. I have to remove the battery for some time to get it to turn on again. This includes loading the SPL and the Recovery interface. The ONLY way my fone will act semi-normal is if I remove the SIM card and boot it. Then eventually it will again just shut-off. I have reverted back to an older SPL with no luck (was using Haykuro's latest one until now). I have loaded multiple radio's with no luck (after reverting the SPL of course). I have tried multiple ROM builds, JF's, Cyanogens and Haykuro with no luck. This really sux. 4 month old fone and seems the radio might be fried. VERY disappointed in the quality. I hope I can get some help and warranty the phone. I am thankful I unlocked my old Blackjack and am able to use it for now. Just though I would share my tale of woe. I am not sure exactly what caused this. Maybe too much flashing? Not sure, but be aware; I feel like maybe I played too much with my phone. That last part REALLY sux cause I love my fone. I LOVE that I can play with it and install all of the great ROMs and themes. Anyway, best of luck to all you Dream owners. I hope I dont have to buy another one (cant afford it )
My fone is not bricked it just seems unstable in every way. Sad day 4 me
[UPDATE]
Before I made this post, I turned on the blue LED (holding trackball and power) and just let my phone sit there. Didn't really have a good reason to do so other than 'why not?'. Anyway, shortly after making this post, I couldn't just leave it alone so I picked up my phone again (I really do love it that much lol). While holding it and just thinking about my less and desirable situation, I noticed the back of the fone was warm like it is when you've been using it for some time. I couldn't help but think that the blue light was indicating that "something" was going on in the background so I just began pushing the buttons on the front and no specific way just randomly and all the sudden my fone rebooted. Sorry I can't say how long it was in "blue light" mode.
Now everything I had experienced and read concerning the "blue light" indicated the only way to get it out of this mode is to 1) remove the battery or 2) let the battery just die on its own. So you can imagine my surprise when the fone just rebooted. It booted up (no SIM inserted) and seem to be fine, but as I mentioned before, this had happened only to lock up and reboot itself. I just began using it as much as I could to see if it would fail again and it seemed to keep going fine so I thought "why not insert the sim again?" So...
With SIM inserted, the fone booted up fine. Again I began to put it through its paces and everything is good so far. Makes call (too late to have someone test call me), browses, downloads market, basically everything with no lockups and no reboots leaving all keys unresponsive. Damn I was happy! But not too much just yet. I'll let it keep going for sometime to make sure it's good, but I can't help but to think that putting my fone into "blue light" mode somehow "fixed" my fone fo lack of a better word. I am perplexed but pleased. Will update later after some decent testing time has gone by. I remain hopeful and regret my earlier comments regarding the fone's quality. I hope I remain regretful of this lol.
Interesting. Can you tell what EXACTLY was on the SDCARD when this happened?
lbcoder:
When this problem first happened on my phone I had folders containing my AppManager backups, ringtones, NES ROMS, camera pix and video files. It's the SD card I always have in there. I don't use apps2sd. I thought maybe there some problem with this card so I tried 2 other SDs I have with the same results; instability. I even tried a clean build with no SD card (as well as with and without SIM); all with the same results. I tried every possibly combination as a form of troubleshooting.
When I put it into blue light mode, the SD card that was installed contained DCIM (pix), appmanager, mp3s, video files, 2 different radios in .zip form (radio 1.22 and the sappire radio; neither with the name update.zip), .footprints folder, ime folder and that's about it. Did u have something in mind?
BTW, I wish I could edit the name of my thread to show there's an update...
The Blue LED has some other purpose and is simply not a "lock". That just seems silly and useless, especially since you'll find if you put it into this 'mode' it will drain your battery fairly quickly for a 'lock' mode (like 12 hours).
There's more than a 'lock' going on here...
I agree. It's doing something in the background other than just being a type of "lock". I'm don't want to claim that it fixed my phone because I have no idea what it's doing when that little blue lights is on. I am saying that it seems a little more than coincidental that my fubared fone (my feeling at the time) began to "magically" work after putting it into this mode and its subsequent reboot. I am really glad I did.
No amount of: fastboot erase "partition name", data wipes, radio/spl/rom flashing helped my fone. I was going to try and get warranty today, but now I don't need to. Back running ION and happy as h3ll! Maybe this will help someone else with a fone that refuses to function correct. Maybe it won't, but I definitely wanted to share my experience with it.
BTW, I was running Cyanogens 3.4 JF mod at the time this began. I understand some other people have had some similar issues as seen here:
http://forum.xda-developers.com/showthread.php?t=525306
These problems are very similar to what I was having, but mine seem irrecoverable even after flashing EVERYTHING. Just food for thought...
I wonder if it found one of those radios and did something with it?
For that thread, Cyanogen has stated that the main issue is in the kernel. The memory killer kicks in and kills essential processes thus result in a crash. He stated that he's looking into it and the fix will likely be in 3.4.1 or one of the iterations after that. I'm not sure if your suffering from the same thing though. None of them seem to have the same symptoms as you do.
hamshu said:
For that thread, Cyanogen has stated that the main issue is in the kernel. The memory killer kicks in and kills essential processes thus result in a crash. He stated that he's looking into it and the fix will likely be in 3.4.1 or one of the iterations after that. I'm not sure if your suffering from the same thing though. None of them seem to have the same symptoms as you do.
Click to expand...
Click to collapse
This is why I stay on Google Ion. It's clean, stable and fast. All these "optimized" builds seem plauged by bugs and quirks.
lbcoder said:
I wonder if it found one of those radios and did something with it?
Click to expand...
Click to collapse
Interesting thought. But it would have to have parsed the file and made a determination on its own as to whether or not it was a valid radio. Neither were named update.zip at the time. Also, I had already downgraded the radio to one of the versions that existed in file name radio_1.22.zip that was on the SD. That allowed me to downgrade the SPL without bricking because at the time I was running Haykuro's newest SPL (which I have since reflashed to my now functioning fone).
For that thread, Cyanogen has stated that the main issue is in the kernel. The memory killer kicks in and kills essential processes thus result in a crash. He stated that he's looking into it and the fix will likely be in 3.4.1 or one of the iterations after that. I'm not sure if your suffering from the same thing though. None of them seem to have the same symptoms as you do.
Click to expand...
Click to collapse
Actually I described pretty much the problem quoted below that is in the thread that I referenced earlier:
tearsphere said:
Can someone please help me..
I installed Cyanogen 3.4 when it got released a few days ago and it was running smoothly.. I think he is a genious. Just today my phone shut off on its own and I had to take the battery out and put it back in to get it to come back on.
Click to expand...
Click to collapse
So I guess it could be open to interpretation. I think Cyanogen does amazing work. I have great respect for him and all his efforts that have given us more functionality with our Dream fones. As I said, it's food for thought. I'm not drawing any conclusions as they would be based on conjecture.
I am intrigued by the blue light mode. I really wish we knew exactly what purpose it serves.
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
by request ill make an update.zip for audio loss for eris users.
im leaving for nashville tonight so i wont be doing any work this weekend.
so i need responses on this thread on what roms DO NOT cause audio loss.
please discuss and come to an agreement on the best rom for me to pull the kernel.
mods please do not move this as i will be updating soon with fix.
What is the fix for? I know on my phone sometimes I can't hear anything when making a call.
I run my own Rom and kernel on my phone so can you just supply the fixed files or tell what they are and I will pull from the zip
-------------------------------------
Sent via the XDA Tapatalk App
what audio loss?, I've tried every rom and havn't had this problem yet.. are you talking about the dreaded audio bug? I am famililar with that as im on a refurb now from that. pre root tho.
If you mean that ringtones go silent with no warning then ZenEXP-Eris Espresso ~Rev7~ does have the issue, EE 3.0 does not so far.
I had that problem big time with Ivan's Official but with JCase's Plain Jane I havent had the problem at all.
I have that issue with the cyanogen roms and ic3rom. But as far as I've noticed the zenEXP and damageR roms do not have this issue. At least for me anyway.
I'd really like to run cyanogenELB, but the loss of audio is a deal breaker.
Renocat said:
If you mean that ringtones go silent with no warning then ZenEXP-Eris Espresso ~Rev7~ does have the issue, EE 3.0 does not so far.
Click to expand...
Click to collapse
I'm experiencing audio loss, as far as loss of ringtone, on EE 3.0 for the last 2 days. Totally silent for every call coming in. I have rebooted, gone to a backup, not sure whats going on.
LiverpoolsNo9 said:
I'm experiencing audio loss, as far as loss of ringtone, on EE 3.0 for the last 2 days. Totally silent for every call coming in. I have rebooted, gone to a backup, not sure whats going on.
Click to expand...
Click to collapse
When i have had the issue before, going into to settings and resetting the rigntone worked. It would be set on default ringtone, not what I had assigned. I put it back to what i wanted and it would ring again. same thing with notifications
Can't Wait
I am using Ivans official and have had this problem a couple of times. When I place a call I hear nothing. The call goes thru on the other end but on mine its like the speaker just refuses to work. I have been wiping dalvik to temp fix the problem. Very annoying. Can't wait for the fix. Thanks in advance.
Using the rooted version of leak3 and also have the same problem with loss of audio. Reboot only way to resolve it.
-------------------------------------
Sent via the XDA Tapatalk App
Having the audio loss (go to make a call every once in a while and the phone is silent and I have to reboot) on Evil Eris 2.0.1. Also, the alarm sometimes does not go off.
Avalaunchmods said:
by request ill make an update.zip for audio loss for eris users.
im leaving for nashville tonight so i wont be doing any work this weekend.
so i need responses on this thread on what roms DO NOT cause audio loss.
please discuss and come to an agreement on the best rom for me to pull the kernel.
mods please do not move this as i will be updating soon with fix.
Click to expand...
Click to collapse
I know you say DO NOT CAUSE AUDIO LOSS, but it seems like a lot of people are letting you know about their audio loss.
Sorry, but I figure I will add to this since others are speaking about Evil Eris.
For me, I get the silent bug (meaning all audio stops working: email notification, text, volume, music, ringtone selector, alarm tone--<when SB happens and I am trying to select a ringtone or alarm tone I get a FC for HTC sound something another>>--)
I have had this with EE 2.0, 2.0.1, and 3.0. My wife however is still on 2.0.1 and has never had the silent bug issue.
Also, for me, I do not get the shutter sound in camera, meaning when you take a picture it makes that camera sound noise. This happens without the silent bug, just don't get sound.
On AF http://androidforums.com/htc-droid-eris/99973-found-what-causes-silence-lag.html this may or may not help you.
This seems to happen to me about every 24-26 hours.
And most importantly, THANK YOU for looking into this and trying to fix it!!!!!!!
edit: I wanted to clear up, I love Evil Eris! I mean no disrespect to this fantastic ROM or to Frame!!!
cabbie12 said:
I am using Ivans official and have had this problem a couple of times. When I place a call I hear nothing. The call goes thru on the other end but on mine its like the speaker just refuses to work. I have been wiping dalvik to temp fix the problem. Very annoying. Can't wait for the fix. Thanks in advance.
Click to expand...
Click to collapse
I'm have the same problem using Ivans official. Not sure but i think the problem starts when I'm using data and then receive a call. When I answer I hear nothing and when I try to call back I hear nothing. I just reboot to fix.
Just wanted to give an update.
I flashed Sushi last night http://forum.xda-developers.com/showthread.php?t=701544 and am still having the silent bug making me a strong believer that I have a hardware issue.
Somewhere I read someone is thinking it has to do with the proxy sensor. Today I had silence twice, that's 2 times in just a few hours, this has never happened before. Also, each time today happened within an hour of using the camera (and I still have no shutter sound with this ROM).
I failed to mention last night that I am on an old Radio 2.40.00.01.22
I am sorry if I sound like a post whore but I just want to give accurate observations.
Camera
Seems that every time I use the camera or open the camera to browse pics it seems to somehow trigger this problem. The only time I've ever had this problem was after using the camera.
cabbie12 said:
Seems that every time I use the camera or open the camera to browse pics it seems to somehow trigger this problem. The only time I've ever had this problem was after using the camera.
Click to expand...
Click to collapse
Yes, I am now thinking it has something to do with the camera. I just got the silent bug again, 3rd time today, this was after I used the camera this evening to test and see if the silent bug would happen. This time it took 90 minutes when before it seemed to happen within an hour.
I had identified the bug a while back, but no one took any interest.
http://forum.xda-developers.com/showthread.php?t=668693
I'm glad to see that more people are becoming aware of it. Hope someone finds a fix soon. The only ROM that I'm aware of that isn't having this issue is the original 1.5.
just asking
im not sure what this trouble everyone is having but im not having any problems besides mms needing the fix but other wize no other issues sound included
Well I assure you this issue is very real and very annoying. I wish I were lucky enough to not have to deal with it, but thats not the case. Can't wait till I don't have to deal with it anymore.
cabbie12 said:
Well I assure you this issue is very real and very annoying. I wish I were lucky enough to not have to deal with it, but thats not the case. Can't wait till I don't have to deal with it anymore.
Click to expand...
Click to collapse
im not sayin it aint happening just didnt know it was a wide spread thing thats all