A couple of days ago, my speakerphone stopped working in my phone. Music will not play out loud, ringtone will not play, alarm clock will not play, etc...
I was on the Virtuous ROM but just changed over to MIUI to see if it was a ROM issue...
but same problem, no sound. I assume my only solution is to go to Verizon and have them look at it. The phone is a remanufactured from Assurion (says on the sticker under battery)
Obviously, my phone is rooted and what not. Where can I find the default rom that comes with this phone, and how do I unroot so the Verizon techs cannot see that the phone has previously been rooted?
Thanks in advanced!
Here's instructions on how to fully go back to stock, S-on and all.
http://rootzwiki.com/index.php?/top...tock-from-AlpharevX-INCREDIBLE-2-(vivow)-ONLY
You might be able to get away with just a stock rom and hide/uninstall SU. If you want to try that, look for AndyBone Stock in the dev forum. It will look like stock on the outside, but there will be clues that it's not if a tec knows what to look for.
snapple112 said:
A couple of days ago, my speakerphone stopped working in my phone. Music will not play out loud, ringtone will not play, alarm clock will not play, etc...
I was on the Virtuous ROM but just changed over to MIUI to see if it was a ROM issue...
but same problem, no sound. I assume my only solution is to go to Verizon and have them look at it. The phone is a remanufactured from Assurion (says on the sticker under battery)
Obviously, my phone is rooted and what not. Where can I find the default rom that comes with this phone, and how do I unroot so the Verizon techs cannot see that the phone has previously been rooted?
Thanks in advanced!
Click to expand...
Click to collapse
Try tapping on the speaker on the outside of the phone. Worked on my wife's inc1
Sent from my Incredible 2 using xda premium
Related
ok, i am really hoping someone can help me out here. so ever since froyo came out i have been having weird call problems, i will be on a phone call and randomly it will mute me. the mute button won't be activated and the only way to fix the problem is to toggle the speakerphone on/off. now i have tried several roms (syndicate, bonsai, ace) and they all have the same problem. i recently tried ace and it worked fine for a couple of days and then suddenly it did it this morning. i have also swapped out my phone and it still does it!
some people suggested playing with the voodoo sound options and none seemed to work.
if anyone has had this issue or knows of things i could try i would appreciate it extremely. this problem is driving me insane (along with all my friends who it constantly happens to while on the phone with me.)
thanks!
Moved to Q&A.
It could be a manufacturer defect? Does it happen on stock?
thegnargnarshredder said:
It could be a manufacturer defect? Does it happen on stock?
Click to expand...
Click to collapse
Only for about a day. I could try it longer. Wouldn't swapping the phone like I did cover a phone defect though?
This use to happen to me back on the DK28 build even DI18 I think but haven't seen it since official EB13 and even on EC05 now. That's weird. Did it start all of a sudden or has it been an ongoing problem? When did you get your phone? Oh wow you said it's a new one? Refurbished? WHen you got your new phone did you restore a backup from your old phone or start fresh?
phynias said:
ok, i am really hoping someone can help me out here. so ever since froyo came out i have been having weird call problems, i will be on a phone call and randomly it will mute me. the mute button won't be activated and the only way to fix the problem is to toggle the speakerphone on/off. now i have tried several roms (syndicate, bonsai, ace) and they all have the same problem. i recently tried ace and it worked fine for a couple of days and then suddenly it did it this morning. i have also swapped out my phone and it still does it!
some people suggested playing with the voodoo sound options and none seemed to work.
if anyone has had this issue or knows of things i could try i would appreciate it extremely. this problem is driving me insane (along with all my friends who it constantly happens to while on the phone with me.)
thanks!
Click to expand...
Click to collapse
p3dr0maz said:
This use to happen to me back on the DK28 build even DI18 I think but haven't seen it since official EB13 and even on EC05 now. That's weird. Did it start all of a sudden or has it been an ongoing problem? When did you get your phone? Oh wow you said it's a new one? Refurbished? WHen you got your new phone did you restore a backup from your old phone or start fresh?
Click to expand...
Click to collapse
i started fresh, except for a couple apps i restored settings for. but i didn't restore any system stuff. this happened right after froyo update for me. at first i thought it was a voodoo thin, but ive tried genocide with the updated voodoo, plus how can i be the only one having this problem. it makes no sense to me.
i guess i could try stock, but i mean i really don't want to run stock....ugh.
---oh new phone was straight from sprint about a week ago.
This is happening to me as well. I'm stock rooted froyo with all stock apps still in place. Very annoying. I never had this issue before the froyo update.
Anyone know of a fix for this yet?
I'm about to take a B.F.H. and "fix" the phone. My epic is doing this on every call I recieve or make.
Anyone have any ideas? I can't deal with this much longer. Really want to smash the phone. Guess I'll unroot and take it into bb or sprint...
iTbagdUrMac said:
Anyone have any ideas? I can't deal with this much longer. Really want to smash the phone. Guess I'll unroot and take it into bb or sprint...
Click to expand...
Click to collapse
yeah i got a new phone and it made no difference. good luck though!
I recently rooted my wife's g2 and installed CM7.1-rc1 on it.
She quickly realized that the phone's sound didn't work unless she put it on speaker.. The guide I followed should have set s-off as well and when I start into hboot (or whatever the recovery mode is called) i do see a message at the top about s-off..
I've installed both the 7.1rc-1 and the latest nightly release and they both have this problem.
After doing this I've also installed the latest radio which appeared to install just fine.. I downloaded the latest radio from here: http://forum.xda-developers.com/showthread.php?t=970809
Version 12.56.60.25_26.10.04.03
In About phone->Baseband version it now lists 12.56.60.25U_26.10.04.03_M
I wasn't able to find much else in the forums about this problem except for an incredible s and a wilfire.. It may be related to S-Off but i'm not sure exactly what to check. There are so many guides on how to root I just picked one that seemed easy, I can't even remember which one it was.. I obviously have root access just fine since I am able to install roms with no problems, I just can't get in call sound to work without turning on the speaker phone..
Note that the sound worked fine before rooting but I am not sure it worked with the stock version rooted since I only had that on here for a few hours and didn't make any calls.. Perhaps I should go back to stock and see if it even works there... Any suggestions before I do that?
Also, the original guide I used was basically the same as the one here: http://forum.xda-developers.com/wik..._Vision#VERIFY_.28using_.22gfree_verify.22.29
Reading through that tutorial I found how to verify s-off, superCID and sim lock off.. according to the output all of those things are correct:
Code:
# ./gfree_verify
gfree verify_cid returned:
@CID: 11111111
OK
gfree verify_secu_flag returned:
@secu_flag: 0
OK
gfree verify_simlock returned:
@SIMLOCK= 00
OK
# start ril-daemon
#
Edit -- Since i posted this I have reverted back to the original sense 2.2 rom (the one that came with the phone) and I still have this problem.. This is the rooted version, I have not de-rooted/s-on'd the phone yet.
Just to clarify, only the incoming volume doesn't work and only if speakerphone is off.. I've played with all the different volumes on the phone with no luck.. The mic works fine as the other person can hear me whether speakerphone is on or not.
Adding screenshots of the boot screen if that helps.
Just a status update..
I have since unrooted s-on'd the phone putting it back to the factory settings and i still have this problem.. Ironic that this could be a hardware problem when it happened literally right after the whole root process and what not.. At least it should still be under warranty so I'll be calling htc either tomorrow or monday if they aren't available by phone on weekends.
My wife is still going to blame me for this but I'm not sure what else I can possibly do.. Perhaps the customer service person will have an idea what can be causing this.. I have played around with headphones and car mode. With headphones on I get sound from the headphones just fine.. If i turn on speakerphone while i have headphones plugged in the sound does not come out the speaker on the phone (just my headphones) which means it doesn't appear that my phone thinks there are always headphones plugged in -- otherwise speakerphone wouldn't turn on.
My only other option to returning it is just tell my wife to always use speakerphone, which she won't like for sure.
mwolfe38 said:
Just a status update..
I have since unrooted s-on'd the phone putting it back to the factory settings and i still have this problem.. Ironic that this could be a hardware problem when it happened literally right after the whole root process and what not.. At least it should still be under warranty so I'll be calling htc either tomorrow or monday if they aren't available by phone on weekends.
My wife is still going to blame me for this but I'm not sure what else I can possibly do.. Perhaps the customer service person will have an idea what can be causing this.. I have played around with headphones and car mode. With headphones on I get sound from the headphones just fine.. If i turn on speakerphone while i have headphones plugged in the sound does not come out the speaker on the phone (just my headphones) which means it doesn't appear that my phone thinks there are always headphones plugged in -- otherwise speakerphone wouldn't turn on.
My only other option to returning it is just tell my wife to always use speakerphone, which she won't like for sure.
Click to expand...
Click to collapse
got same problem on my HTC HD2... warranty is over I think.. more than 1year.. guess i will need pay for it to repair. =/
this might help
Hey I'm not sure if you've fixed your problem yet but I had kind of the same problem with my rooted HTC g2.....I tried everything to fix it and then finally I remembered that I had froze the "car home" app using my backup pro. I felt like the biggest jackass in the world but after I unfroze it all my sound was back to normal. Hope this helps you out but either way everybody can get a laugh thanks to my stupidity :-D
The fact that your headphones work and your small speaker does not suggests that this is a hardware issue. I would look up the hardware guide for this phone and see where you can find a new speaker, it may just be as simple as that!
I dont think it's a hardware problem, or it's just a super coincidence but after rooting my desire z with 2.3.3 android to CM7 2.3.7 i'm also unable to VOL UP or VOL DOWN during the call !
Also would appreciate if someone helps.
Prancuzas said:
I dont think it's a hardware problem, or it's just a super coincidence but after rooting my desire z with 2.3.3 android to CM7 2.3.7 i'm also unable to VOL UP or VOL DOWN during the call !
Also would appreciate if someone helps.
Click to expand...
Click to collapse
Did you do a full wipe before flashing the ROM? Not wiping when moving between ROMs can cause a lot of random bugs.
yeah, i did!
although i used Clockwork
Now i've been reading that there are better recoveries for whipping stuff..
I use same Radio 12.56.60.25U_26.10.04.03_M. And i am able to install all roms without issues. BUT! Yesterday i updated to latest US MIUI and i lost sound in phone speaker and MIC. After plugging in headphones i was able to hear from headphones, and use internal phone mic. Try to flash some clean rom like virtuous g-lite or sense 2.0.0. Or if u want to use CM, try to flash other kernel.
There is an issue with a lot of Android devices where the OS thinks the headphone is being plugged in and unplugged on its own.
I have rooted 4.0.4 AOKP and it still occured.
Search for this FREE application (no ads) to fix it: Wired Headphone Routing Fix
dmwoods said:
There is an issue with a lot of Android devices where the OS thinks the headphone is being plugged in and unplugged on its own.
I have rooted 4.0.4 AOKP and it still occured.
Search for this FREE application (no ads) to fix it: Wired Headphone Routing Fix
Click to expand...
Click to collapse
Tried the app and I still can't hear the person on the other side. I really wished it worked. Or maybe im using it wrong or something..
When activating the camera on stock rom, rooter stock rom or custom rom the camera will lock up the phone, screen will turn off and a battery pull must be done to get the phone rebooted. Doesn't seem to matter the rom. Still the same effect.
Back story:
So my sister in law came to visit with her nice new shiny sgsII (t989). She got it from her friend who happens to be a tmobile salesmen in Seattle. She was told that the camera didn't work cause he downloaded something. But took it anyways (since he is her friend and she got it for free).
I thought I'd take a crack at it. Tried a factory reset. Same issue. Found that it was stock 2.3.5 and NOT rooted. Thought maybe a new camera app would fix it thinking the app would hook into the os/hardware and not the default camera.apk.... Same deal.
Last step I tried before coming here was to install a custom 2.3.6 ROM. It got to the standard camera screen but with nothing coming from the camera (black screen) and locked up before needing a battery pull.
I've come to the conclusion that her friend either tried to flash a different cameras firmware on the t989 or dropped it in the toilet OR BOTH!
What do you guys think the issue is?
Why would he want to flash different camera firmware?
I'm stumped. She is here on vacation and that phone is her camera.
da_dragon2k3 said:
When activating the camera on stock rom, rooter stock rom or custom rom the camera will lock up the phone, screen will turn off and a battery pull must be done to get the phone rebooted. Doesn't seem to matter the rom. Still the same effect.
Back story:
So my sister in law came to visit with her nice new shiny sgsII (t989). She got it from her friend who happens to be a tmobile salesmen in Seattle. She was told that the camera didn't work cause he downloaded something. But took it anyways (since he is her friend and she got it for free).
I thought I'd take a crack at it. Tried a factory reset. Same issue. Found that it was stock 2.3.5 and NOT rooted. Thought maybe a new camera app would fix it thinking the app would hook into the os/hardware and not the default camera.apk.... Same deal.
Last step I tried before coming here was to install a custom 2.3.6 ROM. It got to the standard camera screen but with nothing coming from the camera (black screen) and locked up before needing a battery pull.
I've come to the conclusion that her friend either tried to flash a different cameras firmware on the t989 or dropped it in the toilet OR BOTH!
What do you guys think the issue is?
Why would he want to flash different camera firmware?
I'm stumped. She is here on vacation and that phone is her camera.
Click to expand...
Click to collapse
how does one flash a camera firmware?
So this happens on every camera app?
Don't know how one would flash the camera firmware. It was an educated guess. From the info I was told "he downloaded something and now the camera doesn't work" is the only thing I could conclude from that.
On the Samsung Vibrant people would use alternative modified camera.apk or use custom kernels to get the front facing camera working but never seen of anyone changing firmware before.
I have tried technically 4 different apps. one from the stock rom, 2 from the market. PUdding camera and the other I don't recall off the top of my head. They both did the same thing. Which brings me to believe it is either the driver (which could be fixed by a different kernel) or the hardware. Come to think of it, it wasn't rooted when she got it. So I doubt he flashed anything. Unless he odin'd something....
Just got done talking the the previous owner. Turns out all he did was installed some official Google apps from the market place when this happened. Doesnt seem like he did anything wrong. He told me of two other issues that started at the same time as this one. Video playback will reboot the phone and web video reboot as well.
Got a workaround for the video playback: installed mx player and set it to render A/V in software mode. Not the best solution, but it works.
Online videos crash. IE any site with heavy flash. Updating flash didnt solve it nor an uninstall/reboot/reinstall.
That's where I'm at. 1 step forward 2 steps back...
Hate to do this, but..
Bump
Hey people,
I'm having an issue with the large speaker on my E4GT.
It was working when I received it and here's what I've done since...
Factory Reset via settings
Flashed it to Boost Mobile w/stock ROM no sound
Rooted stock ROM via ODIN no sound
Flashed to Calk's 3.0 via SD and Rouge CWM no sound
Flashed Calk's bare ROM converter via SD & Rouge CWM no sound
To fix I have tried
Viciously banging my headphone jack w/ Beats Studios
Apks such as Volume+
Wiping everything via Rouge CWM & Reflashing ROM
Can someone please help me out?
Great me too
I just had this happen on my phone, and I'm not sure I know exactly when it started because I put my phone in vibrate mode quite often. I believe I last heard sound from my speaker on Monday. Now I hear nothing, be it phone calls, texts, or music. Sound from the earpiece is fine. Sound also works with headphones.
I was using ParanoidAndroid when I noticed the problem. A factory reset didn't help, nor did a revert to stock or CM9.
Any suggestions? I don't have insurance so I'm guessing a trip to the Sprint store is not an option.
I would say take it into a full service sprint store and have them have a go at it (flash stock rom prior). my guess is the speaker itself may be blown. the speaker for the E4GT is real easy to remove and replace and is a normal repair part kept in stock.
accrajoe said:
Any suggestions? I don't have insurance so I'm guessing a trip to the Sprint store is not an option.
Click to expand...
Click to collapse
Still take it to a sprint store ( find a corporate full service store, if you need help locating one send me a pm ) . As long as the phone isn't damaged beyond economical repair ( broken screen, liquid damaged, run over by a car), the repair will cost you 35$.
Thanks for the recommendation Rossk. However, seeing as the disassembly of the phone seems easy enough, I was thinking of switching out the speaker myself.
I didn't bother though, as I never believed it was a hardware issue. I had been trying to fix it by flashing only ICS and JB roms, so I figured I'd try a stock GB rom, and now it works.
What a relief. I would have hated to have some repair guy bust open my phone unnecessarily and fail to fix the problem.
Hey guys, anyone else have the problem of the microphone not working unless the speakerphone is on?
Basically if I am on a call the other person cannot hear me unless I turn my speakerphone on. I did a full factory reset and it's still not working. It's running 5.0.1.
Anyone have this problem or have any ideas? Thanks guys.
mmerlina said:
Hey guys, anyone else have the problem of the microphone not working unless the speakerphone is on?
Basically if I am on a call the other person cannot hear me unless I turn my speakerphone on. I did a full factory reset and it's still not working. It's running 5.0.1.
Anyone have this problem or have any ideas? Thanks guys.
Click to expand...
Click to collapse
Did this start happening on 5.0.1? Are you using any Xposed modules? Maybe try to ODIN back to bone stock KK and see what happens.
jcip17 said:
Did this start happening on 5.0.1? Are you using any Xposed modules? Maybe try to ODIN back to bone stock KK and see what happens.
Click to expand...
Click to collapse
Hey sorry for the delayed response here been crazy the past day.
So basically I was running whatever version of android came on the phone originally for the longest time because root was "right around the corner"! So eventually I got sick of waiting and upgraded to 5.0.1 with the OTA update. The phone worked fine for about a week on that version.
Then just suddenly I was not able to use the microphone unless the phone was on speakerphone. Bluetooth devices also worked. I even tried a factory reset, same thing.
So I went to the verizon store and it's under warranty, the new one should be arriving at my shop momentarily. I just have to ship this one back.
Oh and to your other question.. no I was not running any Xposed modules. I didn't do too much fiddling around with the phone because I was just waiting for root for the longest time.
mmerlina said:
Hey sorry for the delayed response here been crazy the past day.
So basically I was running whatever version of android came on the phone originally for the longest time because root was "right around the corner"! So eventually I got sick of waiting and upgraded to 5.0.1 with the OTA update. The phone worked fine for about a week on that version.
Then just suddenly I was not able to use the microphone unless the phone was on speakerphone. Bluetooth devices also worked. I even tried a factory reset, same thing.
So I went to the verizon store and it's under warranty, the new one should be arriving at my shop momentarily. I just have to ship this one back.
Oh and to your other question.. no I was not running any Xposed modules. I didn't do too much fiddling around with the phone because I was just waiting for root for the longest time.
Click to expand...
Click to collapse
Typically it would be best to test the mic making a sound recording and play it back. If it doesn't work, it's a hard ware issue. If it works there would be a connection issue.
samsung_pro_blackbird said:
Typically it would be best to test the mic making a sound recording and play it back. If it doesn't work, it's a hard ware issue. If it works there would be a connection issue.
Click to expand...
Click to collapse
this may sound dumb and you didn't mention it but did you change your case. I remember some of the cases were not aligned with the mic hole. I had to drill the case and make a new hole that was aligned with the mic.