Related
I really had a bad day (past 2-3 days actually) my kaiser has lost sound, cant hear anything, no calls, no music, no system "bleeps", I did hard-reset, flashed diffrent rom, diffrent radio w/e
so its dead, well sound is...dead....
sux
but on the bright side, its a company phone
and since i need my phone, I got a new one.....company paid
got a touch cruise, great phone btw
wish my kaiser could have waited to fail untill diamond was out....
but, maybe someone have a bright idea on how to fix the sound?
cheers
Can't think of anything else; all the things i was going to suggest you have already tried maybe someone with a little more experience than me might be able to help.
Good luck though.
did someone flash their phone to another rom?
ChumleyEX said:
did someone flash their phone to another rom?
Click to expand...
Click to collapse
Did someone forget how to read?
he said he flashed his radio,,, wonder if it was just not a combatible radio
CUSTEL said:
Did someone forget how to read?
Click to expand...
Click to collapse
It may be a stupid question, but still ...
Did you installed SRS WOW HD?
I lost sound when I installed this program.
Uninstalled it, rebooted, everything back to normal.
ash057 said:
he said he flashed his radio,,, wonder if it was just not a combatible radio
Click to expand...
Click to collapse
errrm, no, I have had the radio for a long time, and I reflashed the stock rom with default radio to check..
I flashed the new radio AFTER I got the problem, I have used same radio for 4-5 months with no issues at all.
pinx said:
It may be a stupid question, but still ...
Did you installed SRS WOW HD?
I lost sound when I installed this program.
Uninstalled it, rebooted, everything back to normal.
Click to expand...
Click to collapse
No, if you read my post you would see that I have done hard-reset and flashed new rom (stock) after I started to have this problem, and I still have it
Sameproblem
Hi, I've got the same problem here.
I flash to NoThrills Dutch (WM6.1) about a month ago..
Everything worked fine.
No problems at all
At one moment (yesterday) my phone rang. I pressed the green butten. The call was accepted but no sound. I hungup. Called the person back, no sound.
After that happend all sound was lost (speaker, windows media, coreplayer, etc, etc)
Then I performed a softreset. sound was working again. I called someone. Everything was ok. Then I hungup. and the sound was gone again.
So I performed a Hard reset.
Sound was OK till I accepted a call.. and the problem started all over again.
Then I performed a Radio ROM flash. I've tried the following versions:
KAIS_Radinly_1.27.12.11_CustomRUU
KAIS_Radinly_1.64.08.21_CustomRUU < This was my default radio after nothrills update.
POLAR_Radinly_1.58.21.23_CustomRUU.
This didn't solve the problem.
Any suggestions?
Keep in mind that before the problem occured I didn't perform any (rom)updates nor have I installed any software lately.
I perform a softreset every 2 days normally.
CUSTEL said:
Did someone forget how to read?
Click to expand...
Click to collapse
You're killn me here
sjoukes said:
Hi, I've got the same problem here.
I flash to NoThrills Dutch (WM6.1) about a month ago..
Everything worked fine.
No problems at all
At one moment (yesterday) my phone rang. I pressed the green butten. The call was accepted but no sound. I hungup. Called the person back, no sound.
After that happend all sound was lost (speaker, windows media, coreplayer, etc, etc)
Then I performed a softreset. sound was working again. I called someone. Everything was ok. Then I hungup. and the sound was gone again.
So I performed a Hard reset.
Sound was OK till I accepted a call.. and the problem started all over again.
Then I performed a Radio ROM flash. I've tried the following versions:
KAIS_Radinly_1.27.12.11_CustomRUU
KAIS_Radinly_1.64.08.21_CustomRUU < This was my default radio after nothrills update.
POLAR_Radinly_1.58.21.23_CustomRUU.
This didn't solve the problem.
Any suggestions?
Keep in mind that before the problem occured I didn't perform any (rom)updates nor have I installed any software lately.
I perform a softreset every 2 days normally.
Click to expand...
Click to collapse
I also have the same problem and have been experiencing it on a number of rom/radio combinations. I have now flashed back to stock bootloader/rom/radio to see if it happens again - it did happen when I was just on stock rom/radion but using hard-spl.
There seems to be a few people now with this problem Unfortunately nobody of any particular knowledge to help fix it. Lots of people are making noises about incompatible radios but I know for a fact that I have been using compatible radios and still getting the problem. If it does it again now it will go back to HTC, but at a bit of a loss as to what is going on.
Yep, happened again.... hard resetting now again to see if happens on 'bare' device!
captainsensible2002 said:
I also have the same problem and have been experiencing it on a number of rom/radio combinations. I have now flashed back to stock bootloader/rom/radio to see if it happens again - it did happen when I was just on stock rom/radion but using hard-spl.
There seems to be a few people now with this problem Unfortunately nobody of any particular knowledge to help fix it. Lots of people are making noises about incompatible radios but I know for a fact that I have been using compatible radios and still getting the problem. If it does it again now it will go back to HTC, but at a bit of a loss as to what is going on.
Click to expand...
Click to collapse
Yesterday I've flashed the nothrills rom twice. First time no luck. the second time everything functioned OK...
I hope it will stay working this time. If not it's back to HTC with the phone..
I am having the same issue starting 2-3 weeks ago. I am also having trouble with all phone functionality in general. The SMS, Phone call, internet. They all work intermittently. Sometimes it work but most of time it doesn't work. Now I am so frustrated that I am planning to take the phone back to vodafone to see whether they can replace mine.
Who here has had the issue that is using MSVC or S2U2, or both?
Hey everyone, watch http://forum.xda-developers.com/showthread.php?t=392606
for a similar discussion.
I think it's going to end up being S2U2.
H
It happened to me on the ATT Death Beta and I do not use S2U2...
Reverted back to L26 V4 Vanilla and all is well again...
I've tried most every ROM available on XDA with most every radio in the last 6 weeks (I used the compatible ones). I even went back to AT&T 6.0 ROM/radio. No luck. Unfortunately I probably can't return it to HTC as I bought my Tilt on ebay and unlocked it to use with T-Mobile... I don't use S2U2 and actually have very vague idea what it is.
I am seeing this on my stock AT&T ROM and Radio, but I am hard spl'd. This also popped up on me about 2 - 3 weeks ago and I can't shake it no matter what ROM I try, even stock.
It seems today I am good but I am not running anything on here - no HTC Home, no MS VC, no S2U2.
I am going to put MS VC on first and go ahead through the weekend to see what makes me break.
Not good news that people WITHOUT S2U2 are seeing this exact problem. I was hoping that was it.
Just to confirm, we have users that:
1.) Do NOT use S2U2
2.) Do NOT use MS VC
3.) DO have the problem where the phone will suddenly stop making sounds. Calling people, they cannot hear you, you cannot hear them. Only a soft reset helps and only then for a short while.
Can someone confirm they meet all of these criteria? If not, do we have people that hit 2 out of 3?
H
1.) Do NOT use S2U2
2.) Do NOT use MS VC
3.) DO have the problem where the phone will suddenly stop making sounds. Calling people, they cannot hear you, you cannot hear them. Only a soft reset helps and only then for a short while.
1.) Check
2.) Check
3.) Check.... But the soft reset doesn't help...
Here's the deal.
I had CyanogenMod 5.0.6 installed, and two days ago I installed Froyo.
It was smooth sailing until today evening when I try to call someone and hear dead space, although the phone indicates that the other party picked up.
It worked just fine a few hours before, nothing changed.
I reboot it, just in time for an incoming call which I take.
I haven't been able to make a call anywhere (including voicemail) except, for some strange reason, to google voice (and it appears I am able to call anything through google voice "to place a call, press 2").
I tried flashing the 2.1 radio and going back to CyanogenMod 5.0.6, but that didn't help.
I then flashed the update to 2.2 again, but it's the same deal.
What's going on, and what should I do now? I got the phone 5 days ago, rooted and unlocked the bootloader and now, of course, have no warranty so I can't really send it in.
It appears that the Froyo update isn't at fault here.
Please help...
It appears that the problem fixed itself. I woke up to find everything working purrfectly. I don't get it - was there a problem with AT&T yesterday night or something?
Hey guys,
I updated my SGS to Froyo 2.2 yesterday and it all went smoothly (at least I thought it did). i used Odin to flash the Froyo 2.2 update and it did. Everything was going fine and I rooted the SGS and applied the one click lag fix (via the OCLF app).
The problem lies with answering incoming calls. When someone calls me it disconnects the call before it comes up on the screen, and shows a no-service icon. This then disappears after a few seconds and the phone returns to its "normal" state as if the phone call never took place. i then get a call reminder text from my carrier (Orange) which says I have a missed call from whoever rang me.
I have searched for hours and not come up with anything useful so I am really hoping you guys will be able to shed some light on the situation.
Thanks for your time,
Charles
I just have updated my mobile from 2.2.1 to 2.3.4, i used this forum tutorial - http://forum.xda-developers.com/showthread.php?t=1139050
I have issue - my phone is turning off for no reason, you know i don't have lots of apps only fb,twitter,skype and 'advanced task killer'
actually when I am doing Skype video calls, writing SMS or anything else my phone just changed to 'black screen' every couple hours and afterwards my Samsung turning off with sound. To turn on I need take battery off and then into back then he allow to turn on...
before I updated I had little bit similar situation, my phone had 2.2.1 version and i didn't have black screen, but my phone just had 'freezing' for 10 sec or more...
what's problem for? what's your suggestions ? thank you a lot.
Ed
I have this issue as well, although it doesn't happen as much since I upgraded to gingerbread. I did have it happen once the other day. I was listening to music and I needed to make a call and when exiting the music app, it froze. It then went black and I had to take battery out and put it back in. It's annoying if you got a otterbox case on it with two layers. I had heard updating to gingerbread stops this but so far I don't think it's 100%. I use my phone as my alarm and one time it went dead with a full charge and I was almost late for work.
Let me know if you figure something out.
what can say experts about our issue ?
I will take some day my mobile to repair centre.. it's sad if couple of people have same issue and nobody can tell us the problem reason.
Try to flash a custom kernel and see if it the problem is still there
can you tell me or give information what's is 'flash custom kernel' ?
I have also encountered this problem, very frequently if i may add.
the problem actually first occured a few months ago, after i updated my firmware to gingerbread.
In my case the phone does not freeze, the screen wont turn on or respond to any gestures (hardware/capacitive button won't too), however any running process still runs, in specific i can still recieve phone calls, or at least hear the ringer.
I know of many other people that encountered this problem, all came from different ROMs (MIUI, SH 3.5 and up, Stock, PilotX etc..) and i, for one, can say that in the past two-three weeks it atarted appearing a few times a day.
So - does anyone have any ideas for the nature of this BUG??
BTW I use the i9000t which i own for over 7 months now.
Same problem
Hi, I have the same problem here.
and have seen this myself on stock roms too.
It doesn't happen very often (only once on my phone for now) but it is getting me pissed off as no one knows the nature of this BUG.
could it be a problem with the latest 2.3.4 version ? or an update of one of the applications?
I don't have too many apps on my phone only skype and 2-3 games.
the only thing I can think of right now is that all people who had this bug had skype on the phone but I don't really think it's from that.
Hi, And-roid if u ll update to 2.3.4 your mobile will working deffo better, i suggest you update your mobile to 2.3.4
Hey eddys, i have 2.3.4 for over two months now, and the problem just go worst...
Hi eddys,
I have the 2.3.4 (and my brother and sister in law have it too with a stock rom).
this is happening on all roms and all kernels...maybe a problem with the 2.3.4?
I don't know but it is very weird, no one has an answer for this....
edit:
just checked this with my phone supplier and of course they have no idea what so ever about this bug.
come to think of it they didn't even know how to fix my brother in laws "problem" when the 3G internet didn't work (settings-->wireless and network-->mobile network--> check the V on Use packet data ) so no surprise there.
Anyone???
Maybe theres another forum that this problem should be posted at??
I have this bug too, but only while tethering. I've found a solution to the tethering related crashes - after you start tethering, go to the SuperUser settings, and disable root permissions for android wifi tether. Your phone shouldn't crash anymore.
hey zyczu,
unfortunately, I do not use tethering at all, do you suggest i should disable ALL root permissions?
This bug is really getting on my nerves!!!
Everything else, but this, is working great...
Since upgrading my i9000m to 2.3.3 through Kies, my phone has exhibited similar symptoms 3 times: freezing, not responding to touch etc.
The first time I had pulled the battery when it did this, but the 2nd time I had just put the phone down a minute or 2 earlier so display was off so didn't notice it(about 2 weeks ago). And the 3rd time(today), I was using it at the time, and so started taking off my rubberized case, only to have it restart before I got the chance to pull the phone back off.
Startup took much much longer than normal, which I recall the startup was similar during the 2nd "freeze & reboot". For some reason today, I randomly though maybe its an OTA update so I checked "Settings..About Phone" and found my kernel version listed as:
Code:
2.6.35.7-I9000UGKG3
[email protected]#2
I have no idea what it was before, but September 8th was 2 days ago... It is possible it said that before today's restart but no idea. I have a PIN on my SIM so when starting up have to enter PIN for it to work, but on these auto restarts I never got asked for my PIN so it could have restarted other times too without me noticing(ie. middle of night).
Hmm, mine used to something similar when I would leave Bluetooth on but would move out of range of a paired device. After a few minutes it would just shut down or stop responding. Haven't had that issue since moving to Milkys rom.
hi guys, i just used this tutorial http://androidadvices.com/how-to-up...0-to-stable-gingerbread-xwjvh-2-3-3-firmware/
first I installed 2.3.3 XWJVB then 2.3.3 XWJVH
just doing step by step...
my phone was working fine 2days then i had same issue and then I changed to original SAMSUNG battery and it's working perfect.
try this..
p.s. what kind of batteries you have 'original' or 'non-original' ? thank you
madmigs:
I did not notice the kernel version ive had before, however i took my phone to a service center today, and for what i can see i have the same version as you do, take aside the i9000t instead of i9000m...
eddys:
Ive been using different batteries orig/non-orig on and off, although since ive noticed it hurts performance i stopped doing that, do you suggest that this might be the cause of the problem?
If so, the factory wipe i just did (formatted the internal SD card) should do the trick.
try reading this it helped me since i turn the wi fi off when i go out
http://androidforums.com/samsung-galaxy-ace/312084-randomly-turning-off.html
Are you guys experiencing turn-off issue while phone is in the locked state. I mean you locked the screen and then after a while when you picked it up for unlocking it was powered off. If anyone has this issue, then I found a solution. Just let me know
my turning off issue went back and it's getting every time more annoying, I don't know what to do...
Everything was running perfect on the phone. I Installed ICS couple of weeks ago and 3 days ago In installed LP6 kernel. Today I was flipping through my contacts and all of a sudden the screen flickered and turned off, the phone remained on.
I rebooted, took battery out for 10 min..No luck. I flashed stock GB thinking ICS might have messed up something but no LUCK. I can call myself phone rings fine and I can see it operating fine except the screen is always off. I inserted JIG to get to download mode, and I did, but screen remained off. Did the screen just crapped on me all of a sudden ? I bought it from mobilecityonline.com You guys think I can arrange to ship it to Samsung international(im in US) for fix or there is something I can try first ?
Help appreciated.
daraj said:
Everything was running perfect on the phone. I Installed ICS couple of weeks ago and 3 days ago In installed LP6 kernel. Today I was flipping through my contacts and all of a sudden the screen flickered and turned off, the phone remained on.
I rebooted, took battery out for 10 min..No luck. I flashed stock GB thinking ICS might have messed up something but no LUCK. I can call myself phone rings fine and I can see it operating fine except the screen is always off. I inserted JIG to get to download mode, and I did, but screen remained off. Did the screen just crapped on me all of a sudden ? I bought it from mobilecityonline.com You guys think I can arrange to ship it to Samsung international(im in US) for fix or there is something I can try first ?
Help appreciated.
Click to expand...
Click to collapse
Sounds weird... So, once you flashed stock GB and there is no root, cwm or cfw installed it should be no problem to give it to your local service point. Sounds like a hardware issue for me.
Thats my fear. Now I have to deal with Samsung UK
Should be no problem as long as you are on stock rom and binary counter is at 0.
Good luck mate.
Sent from my GT-N7000 using xda premium