Develop Bugs

Annoying sound problem

Hello. I have a problem with sound in my kaiser with Android. I tried 2 systems [Cynanogen mod 6 (Froyo) and Myn's Warm Donut], 4 radios (from 1.71 to 1.65) and 2 kernels. Sound never appeared. Why?

what zimage or nbh you using if you are using a older one it might have problems

Did you mean kernel? the newest from this page:
http://it029000.massey.ac.nz/vogue/files/?C=M;O=D

it may be that you have muted the media volume in settings.

No. I don't have any sound. Not only media. When someone calls to me, I cannot hear him too and this person cant hear me too.

Audio issue
I have the same problem. I tried different builds and nothing helps. Any suggestions??

Just a thought, but have you tried flashing a stock rom, then flashing to nand again? Flashing a stock rom clears the entire nand, leaving no possibility of stray bits of data left from custom roms.

I have to say, I get the same thing, but with a slight variation. Sound works for me up until i make at least one call (but could happen before that). Once I make that call, either during the call, or after, the sound is gone. I too had myn's donut, and then frayo, and both times, the exact same problem. I will try to flash the stock rom, and then back to android, but it is a problem that I also share.
This is my first post on xda, so please be nice!

<refresh>.

Mu_aawiyah said:
I have to say, I get the same thing, but with a slight variation. Sound works for me up until i make at least one call (but could happen before that). Once I make that call, either during the call, or after, the sound is gone. I too had myn's donut, and then frayo, and both times, the exact same problem. I will try to flash the stock rom, and then back to android, but it is a problem that I also share.
This is my first post on xda, so please be nice!
Click to expand...
Click to collapse
Yeah, flashed it back to a the most recent stock rom, and then back to andriod.. how works perfectly. Sorry i didnt tell you guys earlier.
I think it was to do with the radio thingy-ma-jig. I flashed it with winmo 6.1 from htc website, and then back again.
Now i'm runnying frayo.

I flashed the newest stock rom from htc site too, then 1.65 radio, but it didn't help :/

Wagierek said:
I flashed the newest stock rom from htc site too, then 1.65 radio, but it didn't help :/
Click to expand...
Click to collapse
That is most likely because you didnt flash it right. take the .nhb from it, plug it into your sd card and flash it from sd. try that.

I'm not stupid. I always flash anything like that-not via CustomRUU-because I have damaged my USB socket and now my Kaiser cannot be recognized by computer.
PS: Today when I booted my Kaiser, next to ANDROID word, I saw "handset status changed to 1". When I rebooted, it didn't show. What's this?

Wagierek said:
I'm not stupid. I always flash anything like that-not via CustomRUU-because I have damaged my USB socket and now my Kaiser cannot be recognized by computer.
PS: Today when I booted my Kaiser, next to ANDROID word, I saw "handset status changed to 1". When I rebooted, it didn't show. What's this?
Click to expand...
Click to collapse
Well, with regards to how I got it fixed (the detailed explanation), i flashed it with a custom winmob rom initially, but surprisingly, the same problem i had with android was happening with the winmob. I could make a call after reboot, but after that call, the sound completely died, and the camera did not work. So i tried to flash with the latest stock rom. I've uploaded the actual roms i used on my public drop box folder here => "i tried posting the link, but because i'm new, it wouldnt allow me...pm me"
I am not a professional on flashing, rather i am a beginner. My tytn 2 is a european T-mobile version. I tried to flash it, it did it half way...then stopped! I tried to do it again, but then it just said "...loading..." and would not go past it. But when i booted to my custom rom, it was still there, but the problems had gone. I guessed that it flashed the radio, and nothing else.
When i then went to android, it worked perfectly.
That was my journey.
I hope that helped... maybe.

Unfortunately, it didn't help.
Any other ideas?

I solved mine by changing radio ROM,but i lost sound and camera in windows,any ROM that fit both android and windows???

What version did you flash?

1.65.14.06

Me too!
I flahsed froyo last night and didn't test after makng calls. I'm having the same issue (lose sound after a phone call). I followed the sticky guide and sim unlocked the radio before flashing (which I think I had already done before). I will try changing radios when I get home to see if this resolves the issue and post my results.
Update: I flashed 1.71.09.01 on my ATT Tilt and this fixed the issue. Now sound and camera work great. Phone runs faster also!

[Q] Can't answer calls on LeeDroid 3.0.3?

I updated to 3.0.3 yesterday and since then I haven't been able to answer calls.
android.phone keeps crashing
any ideas?

What did you install on top of it/what did you delete from it?
'Cause if that was a general bug with the ROM, it'd be all over the thread...

I have revolution HD theme installed on top
i can make calls but can't answer them

I'd go for a reflash of the ROM without flashing the theme. If the problem disappears, you have your reason right there

I get that problem when I flash ports to my phones. Usually the ROMs built for the actual device have less problems. I generally stick with those.

I had that problem with the stock ROM during the final bits of its life. I had to wait like half a minute for the touchscreen to start responding. It would work fine then.

Download the latest version of the theme, the FC problem with phone.apk has been fixed.

airsick said:
I get that problem when I flash ports to my phones. Usually the ROMs built for the actual device have less problems. I generally stick with those.
Click to expand...
Click to collapse
Dude, LeeDrOiD HD isn't a port...

MIUI problem

I have a problem with MIUI rom. Some days ago, my phone suddenly had FC, now, my phone run really slow and laggy... If I turn off the screen, my phone won't wake up, only four button in the bottom light up.
I wiped everything in CMW (system,data, and cache, also sd-card) but it doesn't work.
The fresh install had the same issues
I have this problem only with MIUI rom
any help

You probably need to provide more info on the issue. What version of MIUI are you running? Have you tried a fresh download of the ROM?

zandroid said:
You probably need to provide more info on the issue. What version of MIUI are you running? Have you tried a fresh download of the ROM?
Click to expand...
Click to collapse
i have tried from 1.8.5 to 1.9.2.
it's very weird
this guy has the same problem with me, maybe he can explain better than me
http://forums.miui.us/showthread.php?3740-Display-won-t-wake-from-sleep
Hey guys, I flashed 1.819 yesterday and everything was going great. The ROM ran smoothly and I was having no issues at all. When I woke up the next morning my display would not turn back on. Every time I tried to turn on the display the soft lights would light up but the display remained unresponsive. The phone still seemed functional as I could hear e-mail and sms notifications coming through.
When I rebooted my phone it was abnormally slow.. mounting the sd card and syncing seemed like it was taking forever and the launcher was very jittery.. if I let my display time out it would not come back on and I'd be forced to pull the battery and try again.
I performed a full wipe through clockwork recovery (everything, including wiping system,data, and cache in 'mounts and usb') and reinstalled 1.819. The fresh install had the same issues.. if I let my display time out I wouldn't be able to turn it back on. I thought I was having some wonky hardware issue but after flashing my previous sense rom and everything is working perfectly.. so I'm pretty much scratching my head here. My phone was kickass for one day and became allergic to MIUI overnight!
Click to expand...
Click to collapse

Have you tried using a different kernal such as Tiamat or JD's Kernal?
May want to try that. I had good luck with Miui and Tiamat (ran it for a week)

PacerguyDon said:
Have you tried using a different kernal such as Tiamat or JD's Kernal?
May want to try that. I had good luck with Miui and Tiamat (ran it for a week)
Click to expand...
Click to collapse
i have tried both

Does this happen immediately after you flash? Or are you installing applications to get back to your preferred setup and then seeing the performance problems?
If it's the latter, I'd run the rom alone and see if it runs normally. Then install your applications individually until you encounter issues.

ttupa said:
Does this happen immediately after you flash? Or are you installing applications to get back to your preferred setup and then seeing the performance problems?
If it's the latter, I'd run the rom alone and see if it runs normally. Then install your applications individually until you encounter issues.
Click to expand...
Click to collapse
immediately after the flash. I don't install any other apps

since we are talking about MIUI issues. I am running the latest version of MIUI with the JDKernal.
The camera has color distortion lines when I take a picture. The picture comes out fine but when taking it the image shows the distortion. It did not do that before so I can only assume its something with the camera in the ROM.
Anyone else see this?

spiderj said:
since we are talking about MIUI issues. I am running the latest version of MIUI with the JDKernal.
The camera has color distortion lines when I take a picture. The picture comes out fine but when taking it the image shows the distortion. It did not do that before so I can only assume its something with the camera in the ROM.
Anyone else see this?
Click to expand...
Click to collapse
Try different kernel
Sent from my Incredible 2 3D using XDA App

tenchu_712 said:
immediately after the flash. I don't install any other apps
Click to expand...
Click to collapse
tenchu, your signature says you are not English or American. Are you running the MIUI.us ROM on your incredible 2 in English - and not another language?
.....just a thought.

Camera/Light/Led Problems

Hello everybody.
I'm new here as you can see, and pretty new to the world of android.
I've searched but I couldn't find any s specific answers for my questions.
I started off with a stock Desire and rooted it and installed CM7, one of the earlier ones I think.While I was at this I changed it from s-on to s-off.
Things were fine for the first two months untill my phone started to go down hill.
MY camera flash first stopped working, and then my flash light all together.
Then then camera, headphone jack, and lastly the ability to change to headphone mode when something was plugged into the jack.
I've updated to the newest cm7 build and even tried a nighlty build.
Earlier today I wiped everything an installed MildWild ROM.
I'm still experiencing all the same problems. Can anybody help me fix any of the above problems? The most important being the camera
Summary/Phone Stats
Rooted:
S-off
running 2.3.7
2.6.35.14_r3stable Kernal
32.48.00.32u_5.11.05.14 Baseband
Any replies would be appreciated.
Thanks.

Try to go back to stock and if persists, then it's probably a hardware fault.

stankyou said:
Try to go back to stock and if persists, then it's probably a hardware fault.
Click to expand...
Click to collapse
I'll have a go of that tonight and see. Thanks

[Q] mic doesn't work with calls

Calls worked until I installed cm10.1 nightly. Now I can't be heard unless i turn on speaker phone. Sound is still crap but at least I can make a call.
I have tried a few nightly's and now I'm on the people's rom 3.14. (Loving tpr by the way). I doubt it is a hardware issue based on other reports and the fact it was fine until the custom roms.
I still use my phone as a phone from time to time and need it to work or I have to go back to stock.
Thanks

Could have been a bad flash / download
Did you check the md5sum?

leftcranium said:
Calls worked until I installed cm10.1 nightly. Now I can't be heard unless i turn on speaker phone. Sound is still crap but at least I can make a call.
I have tried a few nightly's and now I'm on the people's rom 3.14. (Loving tpr by the way). I doubt it is a hardware issue based on other reports and the fact it was fine until the custom roms.
I still use my phone as a phone from time to time and need it to work or I have to go back to stock.
Thanks
Click to expand...
Click to collapse
Let me make sure I'm understanding you correctly:
Your mic was working fine until you flashed the CM10.1 nightly. Afterwards, the other person could only hear you when you were on speakerphone.
You switched to TPR 3.14. This switch did not fix the mic problem.
You're thinking that switching back to stock (presumably unrooted) will fix this issue.
Please correct me if any of the above is incorrect.
If he issue isn't hardware-related, I'd bet it has to do with the kernel. Let me ask you the following:
Which CM10.1 nightly did you install? Did you see any other issues in the CM10.1 thread which might indicate problems with the nightly you flashed?
What kernel did you use while on CM10.1? I know that the newer kernels (3.4.y verses the old 3.0.y) have had issues and are just recently getting stable.
As CNexus asked,did you check the md5sum for the TPR Rom you flashed?
When you flashed TPR, did you do a full system wipe, or only a Factory Reset (data) wipe? I believe since you were coming from a 4.2.2 Rom (CM 10.1) to a 4.1.2 Rom (TPR), you should do a full system wipe. Some remnants of the CM10.1 kernel/system files could still be there, messing up the mic.
I would think re-flashing TPR (after checking the md5sum) with a full system wipe would fix your issue, but answering these questions would help us diagnose the problem better.

topherk said:
Let me make sure I'm understanding you correctly:
Your mic was working fine until you flashed the CM10.1 nightly. Afterwards, the other person could only hear you when you were on speakerphone.
You switched to TPR 3.14. This switch did not fix the mic problem.
You're thinking that switching back to stock (presumably unrooted) will fix this issue.
Please correct me if any of the above is incorrect.
If he issue isn't hardware-related, I'd bet it has to do with the kernel. Let me ask you the following:
Which CM10.1 nightly did you install? Did you see any other issues in the CM10.1 thread which might indicate problems with the nightly you flashed?
What kernel did you use while on CM10.1? I know that the newer kernels (3.4.y verses the old 3.0.y) have had issues and are just recently getting stable.
As CNexus asked,did you check the md5sum for the TPR Rom you flashed?
When you flashed TPR, did you do a full system wipe, or only a Factory Reset (data) wipe? I believe since you were coming from a 4.2.2 Rom (CM 10.1) to a 4.1.2 Rom (TPR), you should do a full system wipe. Some remnants of the CM10.1 kernel/system files could still be there, messing up the mic.
I would think re-flashing TPR (after checking the md5sum) with a full system wipe would fix your issue, but answering these questions would help us diagnose the problem better.
Click to expand...
Click to collapse
I think you have the symptoms correct.
I did a data wipe but not a factory reset before each rom install.
I started with this rom
cm-10.1-20130303-NIGHTLY-d2spr.zip
I tried 3/13, 3/24 and 3/27 before trying TPR3.14.

leftcranium said:
I think you have the symptoms correct.
I did a data wipe but not a factory reset before each rom install.
I started with this rom
cm-10.1-20130303-NIGHTLY-d2spr.zip
I tried 3/13, 3/24 and 3/27 before trying TPR3.14.
Click to expand...
Click to collapse
Yeah, a full system wipe might be the ticket. Let us know if that works.

I'm Back Baby
I tried a system wipe and a rooted stock rom. This didn't work. I then tried the LJ7_Stock_with_count_reset16 rom and my sound was ok. I cleaned out the mic hole with a pin and bam sound was like normal. I'm now back on TPRGS3.14 and everything is good. I think I had 2 issues but possibly only 1. messed up mic from multiple flashes and crap in the mic hole. I guess checking for a physical problem even as small as a mic debris is an easy first step.
thanks for the suggestions