Every time I connect the phone to my car/home charger it makes that water droplet sound. My car charger seems slightly loose and do not want to buy a new one since they consistently get like that all the time. Any way to disable it? My issue is that while playing music through bluetooth, the constant sound interrupts the music which is totally obnoxious.
It's disabled in Omega ROM which I use so I imagine there isn't an option for it. If you don't want to install mods/roms you could maybe just mute all your notification sounds while playing music in your car.
try this settings-sound- disable touch sounds
Yeah i plan on rooting my phone and installing custom roms. How is omega? Stable? I've just been waiting for developers to get an understanding of the phone.
The stock based Omega (currently v7) couldn't be more stable and fixes a few things Samsung haven't gotten around to yet. Nothing to worry about.
Related
The last few weeks I've been using the headphones now since I'm back to working out. However, it seems at random, that the next track button stops working. When it stops working, the Play/Pause button actually skips to the next track.
I use mine a lot and can say that this has never happened to me.
Well, then I hate you. I am gonna file this as an issue due to being rooted I suppose... Won't matter soon anyways as I need to find me a good set of jogging headphones.
I run into the same problem if I use my actually comfortable headphones instead of the crappy huge buds that can't fit in my ear. These have no controls on them and when using Pandora, it will just skip until I reach the 6 skip per hour limit and then it will still do crazy random things like open my notifications and stuff. I have since gotten some even better headphones and rooted (CM Nightlies) and it no longer happens. I think it is a poorly designed headphone connector that catches random signals, but thats just my opinion.
jeremycindy07 said:
I run into the same problem if I use my actually comfortable headphones instead of the crappy huge buds that can't fit in my ear. These have no controls on them and when using Pandora, it will just skip until I reach the 6 skip per hour limit and then it will still do crazy random things like open my notifications and stuff. I have since gotten some even better headphones and rooted (CM Nightlies) and it no longer happens. I think it is a poorly designed headphone connector that catches random signals, but thats just my opinion.
Click to expand...
Click to collapse
Hmm, thats an interesting thought. I have been using the stock music player, but am now running CM6 RC1 and have not tested it again, so I'll see how that goes and report back...
So, now that I am running CM6, the headphone buttons do not work at all, and I assume it is because of the different music player being used. Anyone know how I can install the stock HTC Music Player?
I'm curious if anyone has had any issues with using bluetooth calling in a car. With my SGS1 (Verizon US Fascinate), when I hang up a call via bluetooth in my car, bluetooth on the phone will crash and disconnect from the car. The phone will freeze for a few minutes, then I have to disable and re-enable bluetooth for it to re-connect to the car. I've talked to a few others who have had the same issue with my same phone, but I guess not many people use this feature or have this bug? I would like to know if anyone with an SGS 2 uses bluetooth calling via car and if they have any issues.
I'm also curious about the minor things Samsung does in their ROMs which never made sense to me. The primary one is the "charge complete" notification. I charge my phone at night while I sleep and in the middle of the night (every night), I get a notification beep telling me the phone is charged. It also turns on the VERY bright AMOLED display which lights up the entire room. Also, my girlfriend's Samsung phone will die in the middle of the night if it's not charged and will blast the shutdown animation and sound VERY loud.
Samsung does little things that are a bit irritating at times and I'm curious if they've improved with their new phone.
Thanks in advance to anyone who can help answer these questions.
DeezNotes said:
I'm curious if anyone has had any issues with using bluetooth calling in a car. With my SGS1 (Verizon US Fascinate), when I hang up a call via bluetooth in my car, bluetooth on the phone will crash and disconnect from the car. The phone will freeze for a few minutes, then I have to disable and re-enable bluetooth for it to re-connect to the car. I've talked to a few others who have had the same issue with my same phone, but I guess not many people use this feature or have this bug? I would like to know if anyone with an SGS 2 uses bluetooth calling via car and if they have any issues.
I'm also curious about the minor things Samsung does in their ROMs which never made sense to me. The primary one is the "charge complete" notification. I charge my phone at night while I sleep and in the middle of the night (every night), I get a notification beep telling me the phone is charged. It also turns on the VERY bright AMOLED display which lights up the entire room. Also, my girlfriend's Samsung phone will die in the middle of the night if it's not charged and will blast the shutdown animation and sound VERY loud.
Samsung does little things that are a bit irritating at times and I'm curious if they've improved with their new phone.
Thanks in advance to anyone who can help answer these questions.
Click to expand...
Click to collapse
interedsting thread. one thing keeping me off the sgs2 was the sgs 1 faults...
I have a delay when pressing the home button.. it's not as instant as the back button. did the original sgs have that problem too?
Alright, I have a Droid 2 (actually my second one; both have had this problem), although it's not really a model-specific issue.
When I'm walking with the phone in my pocket and listening to headphones, the phone will occasionally think that the headphones have come unplugged when they haven't. This causes it to pause, and I have to take the phone out and unpause it.
Is there any way to disable the 'pause on headphone disconnect' feature? I understand that this is a hardware issue, but there is really no reason for it to pause, as the headphones are still connected.
The phone is rooted and Liberty ROM 3 v2.0 is installed, but the issue occurred when the phone was stock, too.
zomgjesus said:
Alright, I have a Droid 2 (actually my second one; both have had this problem), although it's not really a model-specific issue.
When I'm walking with the phone in my pocket and listening to headphones, the phone will occasionally think that the headphones have come unplugged when they haven't. This causes it to pause, and I have to take the phone out and unpause it.
Is there any way to disable the 'pause on headphone disconnect' feature? I understand that this is a hardware issue, but there is really no reason for it to pause, as the headphones are still connected.
The phone is rooted and Liberty ROM 3 v2.0 is installed, but the issue occurred when the phone was stock, too.
Click to expand...
Click to collapse
That can only be changed by modifying your ROM...
Just bought a second hand GS3 from ebay, the screen had a small crack but otherwise was meant to be OK. I put Foxhound ROM on (I'm just used to having to upgrade the rom) and am finding that the sound will work fine after a restart, but then, after it has gone to sleep all sound will stop working.
I've tried clean wipes/formats etc. and also checked all relevant settings I could find (including turn off all sound in accessibility, what an odd option).
I've tried two ROMs and three kernels.
I've tried searching google and xda for hours but haven't found anything that wasn't related to the headphone port; this affects both speaker and headphone, although when the headphone is in and the sound has died I can hear some strange static noises when it's meant to play sound, could be interference or a clue.
I've dismantled the phone and inspected for damage, nothing obvious. While dismantled I tried applying pressure to the speaker flex cable and various other IC's to no effect.
It really seems like a software glitch since it only happens when the device goes to sleep;
You can turn the screen off and unlock within 3 seconds and it will be OK.
If you wait 5 seconds with the screen off - boom, no sound.
Any ideas? Is there some deep idle sleep setting that kicks in after 3 seconds I can disable or some way to log audio errors or... something?
Thanks
defroster said:
Just bought a second hand GS3 from ebay, the screen had a small crack but otherwise was meant to be OK. I put Foxhound ROM on (I'm just used to having to upgrade the rom) and am finding tht the sound will work fine after a restart, but then, perhaps after it has gone to sleep once or twice (never more than a few minutes unless I'm plying a game, in which case it stays on just fine) the sound, all sound, will stop working.
I've tried clean wipes/formats etc. and also checked all relevant settings I could find (including turn off all sound in accessibility, what an odd option).
Any ideas?
Click to expand...
Click to collapse
May Be The Phone Was Damaged, Try Stock ROM
i'm downloading a different ROM now but it takes hours (rural australian phone lines...)
same result with a different ROM =/ I've fixed many phones, computers etc before but not sure what to investigate here, guess i'll dismantle it and see.
A second rom and kernel same result.
Seems to lose sound as soon as it goes to sleep (screen off), really seems like a software problem but can't find any other reports on this phone similar.
Help!
Anyone?
Looks like a software problem but can't say where you can look.. If kernel is not the cause..
Maybe hardware after all..
sent from here, there, somewhere!!
The only way I can imagine it being hardware is if it's heating an audio ic during boot to make a connection and then when sleeping it cools and the connection is lost. It's a long shot but if it's software why is it not happening to anyone else? No weird software installed or anything.
defroster said:
The only way I can imagine it being hardware is if it's heating an audio ic during boot to make a connection and then when sleeping it cools and the connection is lost. It's a long shot but if it's software why is it not happening to anyone else? No weird software installed or anything.
Click to expand...
Click to collapse
Does the sound still work through headphones (after the sound stops working)?
Sent from my GT-I9300 using Tapatalk 2
no, it doesn't seem to be headphone jack related.
the only thing I changed (aside from the rom) that I can think of that MAY have done something is some network setting for my carrier (vodafone .au) - there was an option in foxhound rom or something, but I can't for the life of me remember what it was called, I googled it at the time to see what it was but have since lost the browser history, it was some feature of the phone network that stops sending requests to the network when the phone is sleeping or some such... I'm really grasping at straws there though.
can't seem to find a stock rom for Australia either?
updated OP with more info, sorry for the bump, i'll let this die if no-one's got any ideas.
defroster said:
no, it doesn't seem to be headphone jack related.
the only thing I changed (aside from the rom) that I can think of that MAY have done something is some network setting for my carrier (vodafone .au) - there was an option in foxhound rom or something, but I can't for the life of me remember what it was called, I googled it at the time to see what it was but have since lost the browser history, it was some feature of the phone network that stops sending requests to the network when the phone is sleeping or some such... I'm really grasping at straws there though.
Click to expand...
Click to collapse
I think you are talking about fast dormancy toggle.. But I do not think it will cause any problems.. Also as you have already done factory resets an app should not be a problem..
I can only think of hardware faults..
sent from here, there, somewhere!!
yes i just finally remembered it and tried disabling, you're right, no difference.
I'm having trouble figuring out how hardware could be the culprit though, since it's triggered by the screen off for more than 3 seconds, there's something in software causing it.. but you're right, why does it persist over a wipe then? argh!
Downloaded stock rom, problem remains
Hello. Picked up an Xperia X a couple months ago and have been generally happy with it, though I'm having some bluetooth issues ranging from annoying to infuriating that are preventing me from really enjoying this phone. Hope some of the gurus here can provide a some guidance on what I can do to fix or workaround these issues.
1. After some period of time listening to music/podcasts/whatever, the phone will automatically drop the volume by half and display the message:
Listening to sounds above the current volume level may permanently damage your hearing.
That's fine and dandy, but I'm controlling the volume through the bluetooth device, and the result is that it drops to a volume so low I can no longer hear it, and while it's a simple thing, it's infuriating every time it happens. Based on prior searches, I know this is a built-in "feature" and I know it's been part of the Xperia phones for a while, but is there any way to disable this behavior? I have my phone rooted, so root-level apps, Xposed modules, etc. are all on the table. This is my number one complaint with the phone, so would really appreciate any help here. Note: to clarify, I want to stop this *behavior*. I've found other discussions about killing similar warning messages, but nothing about how to prevent it from actually lowering the volume.
2. When connected to my car through bluetooth, I don't get metadata from the phone (AVRCP?). Bluetooth problems in general appear to be widely reported for Android 7.1.x on this phone, but most people seem to complain about being unable to pair their device at all. I can pair it fine, but I don't get metadata. However, prior to upgrading to 7.1 (while still on 6.0) metadata worked, and when running OmniROM 7.1.2 on this phone metadata also worked. So, it seems to be a problem with this particular version of the stock ROM for this phone.
Any ideas on how I can fix that? Again, maybe an xposed module or something that I've overlooked? or could I maybe swap out the bluetooth stack from OmniROM, which works fine? This is a much lesser annoyance than the above, but still interested in any suggestions.
3. Finally, this is a more subjective issue, but does anyone else have problems with bluetooth performance in general with this phone? On my last two phones, I kept my phone in my left pocket and played through a bluetooth headphones with the receiver on my right ear with generally no problems, other than the occasional hiccups that seem to affect every android device (at least every one I've used). With the Xperia X, however, trying to play with the phone in my left pocket skips so horribly that it's completely unlistenable. Moving it to my right pocket helps somewhat, but it's still flaky - turning my head sideways such that the receiver is over my shoulder causes skipping. I have to move my phone up into my jacket pocket in order for it to play (mostly) reliably.
Does anyone else have problems like this? Again, I never hard this problem with either of my two previous phones on the same set of headphones (have similar, but not as severe, issues in my car as well). I *did* have this same problem with OmniROM as well, and I have the problem with and without a case, so it seems hardware related, but if the bluetooth hardware was truly this bad I would expect to have seen more discussion about it. So, just wondering - is this just me, or do other people have this problem as well? I know it's unlikely, but any suggestions to improve this? Ie., possible to increase the bluetooth transmitter power or something like that?
Thanks, all. Sorry this turns out a little long, just wanted to properly explain. Looking forward to any suggestions.
I can confirm that on my XX Bluetooth signal is also weak, I have same issues at least with two Sony headsets (SBH60 and SBH80). Also with Bluetooth AptX receiver for my (home) audio it is quite similar, just walking behind corner from direct visibility and audio is choppy...
1. This error message appears very rarely, for me, not every 30 minutes. I have this phone for 1 year now and I encountered the warning 5-6 times.
2. Idk
3. True, Im pretty dissapointed by the bluetooth strenght. Also, the WiFi is super weak too. Very dissapointing.
This also happens on the Tablet Z, where I have external speakers connected. Nannytech run amok.
Replying to old thread, but got just new bluetooth headset and noticed also very poor bluetooth performance on my xperia x. Distance between phone and headset cant exceed half a meter, or music starts stopping and skipping. Even with my ancient backup phone, Iphone 4s, distance can be meters... Very poor desing from Sony.
Bluetooth in general eventually drove me away. Only got midling performance at best, but whatever chip or driver or whatever they were using also had performance issues with custom ROMs. Never found a single ROM not based on stock that worked 100% correctly with bluetooth, and given podcasts and music is probably about 90% of what I use my phone for (combined with Sony ending even security updates long ago at this point), that was a pretty big problem for me.
Ended up buying a Pixel 3a to replace it. My main concern about the 3a is that I wish it was a little bit smaller (really my concern with almost every well-spec'ed phone these days), but the bluetooth in that phone is solid. Longer range and better strength than any other bluetooth device I've ever used. Extremely happy with it.