So I just flashed rooted gingerbread from droid-life, and everything is working fine (well, not everything, but can't complain) the only serious problem I'm having is that my in-call volume is nearly unhearable. I have the in-call volume turned all the way up, but whether I'm using it regularly or have it on speakerphone, it makes no difference, I can't hear a thing out of it unless I'm in a completely quiet room.
I've already tried reflashing it once (did factory reset and cache wipe) and then doing a factory reset from the privacy menu once, and neither one made any difference. Has anyone here had a similar experience with it? Any suggestions?
Tl;dr flashed rooted gingerbread, now I can't hear my calls.
I had this bug (as well as a few other people on here) as well, but it was fixed by rebooting the phone normally.
I had the same issue but only during the initial activation call. All calls after that were at normal volume.
Maybe another activation call could fix this. Just dial *22899. If not I'd try another factory reset or reinstall the rom.
Tried many different methods to getting around this "low-volume" output, and rebooting was the only way. Even after a factory reset, just before I hit the activation screen - I pulled the battery and restarted the phone, and the issue went away.
Haven't had a problem since, so it's probably no big deal.
Restarting it normally fixed it, thanks guys!
Should've thought of that myself though, I feel stupid x_x
Side note, it wouldn't restart properly until I pulled the battery, which I found rather weird. Hope that doesn't happen again D=
Sent from my DROID2 using XDA App
Related
I had this problem when I installed a leaked version of 2.1 on my eris! No sound, and can't hear who is on the other end. Have to reboot in order for x to act like a phone. This happening to anybody else?
Sent from my DROIDX using XDA App
Theres no known issue that ive heard of with people losing their sound completely.. are you currently using either of these 2 options:
Double-tap to Silence -or- Smart Profile -Face Down to Vibrate
if so that may be the cause. These 2 are know to cause problems with both ringtone sounds and other issues. The only fix is a complete wipe to factory defaults.
Another thing it could be is... are you using a restore program to restore all you apps after upgrading to froyo?? does this program also restore system settings?? Maybe it faulted some settings.. If so, then do a factory reset and dont use that program.
just my 2 cents.
Same problem Here!
It only works for the first call. The next one will have no sound. Have to restart the phone to use it again.
The problem persists even if I use it in 2G only mode
This has happened to my phone only twice. It's like the earpiece goes out. The rest of the phone works fine though. Only solution I've found is rebooting.
I have had my desire he for a week now.
Though everything is fine, I'm having problems with the sound. It was working fine before but after a day or two it would randomly stop. After doing a hard reset to set factory defaults the sound would then work again.
Today the sound has stopped working again...
What is causing this? Could the phone be faulty or is it an app causing this?
The sound was working fine this morning but now there is no sound whatsoever.
All installed apps were previously used on my HTC desire & HTC hero and never did I receive any problems.
Anyone else had any similar problem or what may be causing this?
I need an answer soon guys. I just spoke to vodafone customer services regarding the sound problem. They are saying it's faulty and needs to be repaired.
However I'm sure it does not need to be repaired as doing a simple factory reset will fix the problem.
Could an app cause this issue and stop the sound working?
When I make a phone call, the loudspeaker works fine...
Why is loudspeakers/phone calls working for sound but system sounds/alarms/SMS/music or even videos have no sound.
If I was to do a reset it would then work again.
Anyone have any suggestions before I return the phone for repairs?
Taking the phone in for repairs is the last thing I wanna do.
I know this won't help, I have had issues when the Bluetooth dropped off while listening to Music (A2DP). At first I was re-booting the phone and the problem was solved, then I decided to switch off/on my Bluetooth device and phone connection and it worked okay. However on a couple of occasions the phone has mysteriously gone into "Silent Mode" and I have no idea what caused it?
This is most strange, does restarting your phone also fix the problem or do you always have to do a reset?
I've not heard of this problem before...
Does the sound stutter before it goes off and does the phone lag at all??
I really couldn't tell you but I thought I'd respond anyway before you take it for repair..
Also have you tried setting all sounds to zero and then back to max again...does that work??
Wonder if volume locker app would stop this, or at least it should tell you if the sound settings have changed and then revert them back....just a thought.
hello guys just to confirm you are not the only one with that problem out there... restarting the phone works for me though try that! but yes its definetley a bug i have also had the proximity problem, wifi doesnt work and heep of other stuff so ill be returning the handset in the next couple days!
either way good luck with yours!
rixsta said:
This is most strange, does restarting your phone also fix the problem or do you always have to do a reset?
I've not heard of this problem before...
Does the sound stutter before it goes off and does the phone lag at all??
I really couldn't tell you but I thought I'd respond anyway before you take it for repair..
Also have you tried setting all sounds to zero and then back to max again...does that work??
Wonder if volume locker app would stop this, or at least it should tell you if the sound settings have changed and then revert them back....just a thought.
Click to expand...
Click to collapse
Thanks for your reply. I had to do factory default twice on it to get the sound back.
Funny enough just now I held down the power button to restart the phone.
It then restarted and the sound is now working!
I do not know if it will stop working again or how long it will take for it to stop working again.
I will keep you all informed.
At the moment all I can say is the battery is terrible.
It was 75% this morning and now it's around 25% and it's only been around 2 hours...
Do you find the phone to be laggy??
rixsta said:
Do you find the phone to be laggy??
Click to expand...
Click to collapse
I did at first find it very laggy, especially when browsing through pictures, it was sluggish and would take ages to load the pictures.
Now, after enabling the USB Debugging setting, it was a smooth as butter.
Sound is still working! Battery is now 18% when it was 80% this morning!
And another person with the same problem.
I am helping my friend with his DHD and today he announced that his phone has a similar issue (and he says that the small speaker - for making calls - is working). He is on a stock rom, but his phone was originally from 3.
Do you know of any custom ROMs with sence which don't have this issue?
Do you think it would be a good idea to contact HTC about that - who tried?
Do you have fast reboot on? If you do try disablin that and do a restart of the phone. Maby that helps
flippy said:
Do you have fast reboot on? If you do try disablin that and do a restart of the phone. Maby that helps
Click to expand...
Click to collapse
Thanks for advice, but it didn't work . Even tried taking out the battery. Do you know if it's possible to monitor your hardware components in Android?
Hey guys, im on my pc, and im literally watching my phone press the return button really quickly, constantly for a few seconds at a time. I know theres a topic about the back button but im not sure if its the same issue, im running Cm7 with Honity, and I dunno what to do, ill be using my phone and suddenly it will spaz out and continuously hit back until were on home, then just keep pressing it!
I am running stock, unrooted 2.3.2. I also occasionally have this issue. I have not really been able to reliably reproduce this issue. Sometimes it happens middle of the day, sometimes towards the end of the night after the phone has been in use all day. Other times I can go days without having an issue. I had chalked it up to a quirk of my phone, but it is nice to see other people having the issue too.
Hopefully it is a firmware/software error and not something physically wrong with the phone. I would have to have to send it in for repairs.
i tightened the 6 screws on the back of the phone and i stopped having that issue. try and see if it will work for you
Yeh your not alone.
I have done a factory reset and not experienced the issue as of yet, its been 2 days, however if it should happen again i will try tightening the screws a bit.
Back button issue
There are a few longer threads in this forum about the back button issue on the Nexus S -- for some people the back button doesn't work at all, and for others it turns on all by itself. There were a few replies from a Google employee (ryguy) who said it would be fixed in an upcoming OTA update, etc. but some reported having problems AFTER getting 2.3.2 when the problem didn't exist before. There are also other reports of tightening the screws on the back of the phone, which haven't tried but seemed to improve things for people whose back button WASN'T working at all.
For my phone around 2-3 weeks after buying it I had the back button come on all by itself. I fixed it by doing hard resets, as suggested on an earlier thread that deals with this issue (it's like 10 pages long but has the complete story of everyone's experience and fixes with this issue). Anyway, the point is for me after the first hard reset the problem persisted, so I did it a few more times (like maybe 5 times) and now it's gone.
There are some people who tried a hard reset (factory settings restore) and the problem still persists but I think that you have to do as many hard resets as possible (like, over and over and over) until the problem disappears. I'm rooted so I did a Nandroid backup first, then did 5 hard resets through Clockwork Recovery (select the "Wipe User Data" option), and after five hard resets I just flashed by backup and I was back to where I was, minus the back button issue. You don't have to be rooted, of course, to do this, but if you are, doing that ROM Manager backup allows you to quickly reinstall everything to the exact way it was after you're done with the five or 10 hard resets or whatever.
If you're unrooted you can power off the phone, then turn it on while holding the Up Volume button. This boots you into Bootloader mode and you can navigate around to do a factory reset. Or, if you are rooted and have ROM manager, you can use ClockworkMod Recovery like I did (see other threads on how to use these programs).
Anyway, hope this helps - TC
Samsung Nexus S with root access
Stock Android 2.3.1
I'm having some serious issues with my phone. This morning the battery was suddenly drained completely, don’t know why yet. Then after charging the phone a bit and rebooting it, it constantly goes into driving mode and starting the voice command application. The most strange thing however is that when I choose to power off the phone, it shuts down but then automatically reboots.
I know I should try factory reset, but anyone else had this problem?
(I have original firmware and the phone isn't rooted)
EDIT:
Doing a hard reset seems to have solved the problem.
Maybe your power button is broken (constantly pressed)? Did the phone get wet?
I have not heard of this. I've heard of bootloops and the phone rebooting when trying to power off but thats usually due to custom roms and people flashing over other custom roms which causes conflict. I think factory reset may be the only option. However, with the Galaxy S there used to be a way to get into safe mode. I beleive you'd hit the menu button as soon as you saw the Galaxy S boot logo. I haven't heard of a safe mode yet for SGS2 but perhaps someone can confirm if its available in this model?
If you can still get into settings of the phone when its on, I'd try going into Settings > Applications > Manage Applications and clearning data for voice commands
It almost seems as though your phone is registering home button being clicked thereby turning voice mode on and also turning it back on after a power off.
delinne said:
I'm having some serious issues with my phone. This morning the battery was suddenly drained completely, don’t know why yet. Then after charging the phone a bit and rebooting it, it constantly goes into driving mode and starting the voice command application. The most strange thing however is that when I choose to power off the phone, it shuts down but then automatically reboots.
I know I should try factory reset, but anyone else had this problem?
(I have original firmware and the phone isn't rooted)
Click to expand...
Click to collapse
Hi,
I was have exactly same problem, reset don't resolve my issue.
Solution was to replace my phone.
Thanks for the help, gonna try factory reset first. But this doesn't look like a software problem, so probably gonna need to replace it
delinne said:
Thanks for the help, gonna try factory reset first. But this doesn't look like a software problem, so probably gonna need to replace it
Click to expand...
Click to collapse
Well this is a strange problem. Is it possible a bread crumb got under your buttons? Or some case is so tight it is pressing on some buttons?
Don't have a case around it, but the power button isn't stuck I think because wouldn't the menu for shutting down the phone etc. appaer constantly? And if it's something under the buttons then it is just bad design, had the phone only a couple of weeks.
delinne said:
Don't have a case around it, but the power button isn't stuck I think because wouldn't the menu for shutting down the phone etc. appaer constantly? And if it's something under the buttons then it is just bad design, had the phone only a couple of weeks.
Click to expand...
Click to collapse
I had the same problem mate. And that was exactly what I thought, I actually started a thread on this problem about 2 weeks ago. Was really strange, people told me to take it back. But What I did was factory reset on the phone. Which still didn't completely solve my problem. So I left the battery out the phone over night. The most annoying thing was, the screen kept turning on, like something was being pressed, can't have been the middle button, because the menu would have come up, it didn't do that. And then to make matters worse the tap to speak driving mode kept coming up.
I then took out the battery and left it out over night. Put it back in, in the morning. Charged it up. Didn't do it again.
Hope that helps. Try it.
Ok thanks, I will try it. It is really a strange problem as you say. After the factory reset the problem showed up again but not as often as before. Also after upgrading to latest firmware today, according to the battery monitor android OS is using 45%, that looks really strange to me.
I don't really have a clue why these things started happening, but they have, and they're very annoying.. So basically from one night to the next morning, I noticed my phone started doing some..out of the ordinary..things. These are what I've noticed so far:
* Vibrates (twice I think?) upon answer a call, which I think it only used to be once.
* Vibrates every time you take your face away from the sensor and the screen comes back on
* Plays a completely different song for my ringtone, even though I've verified the settings 1000 times.
I've booted into recovery, wiped everything, and did advanced restore to restore each thing, one at a time, to find out where the problem was...it was in data.
Has my lack of checking app permissions finally caught up to me, and now some dev who thinks he's cool is screwing with my phone, or could it be something different?
Any help? I don't wanna completely wipe this thing, but I might end up having to :[
Do you have an active profile?
Profile can override your notification settings.
Sent from my HTC Panache / Darkside CM7.2 using xda premium.
I had the same thing happening, I had the do a full wipe and restore
It was the profile, haha. Thanks a ton for the help. I was messing with profiles earlier, but I didn't realize I'd actually changed it from the default.
if you recently just flashed the rom and havent done major changes.
The simplest way to figure your problem is to do a full data wipe, cache!
and re-flash and then you can see whether if it'll vibrate again!!