Related
My droid would use whatever BT headset (stereo or not) for the phone when my headphone jack was also in use (to use car stereo) for audiobook player.
I have new Fascinate and I swear it did the same until I rooted it. Regardless, it will be close to a deal breaker if I cannot find a solution to this.
Even if the headset indicator is ON, the sound still goes to the headphone jack, RIDICULOUS
In my opinion, plugging into headphone jack should only take over media type output (music, audiobook player, video) and LEAVE PHONE ON BLUETOOTH. We should at least be able to chose this behavior in a setting.
So is this a Samsung screwup? do other Samsung devices behave this.
How hard would it be for a dev to build an app to FIX this on Fascinate.
I thought I was the only one with that situation... I would love to know the answer/fix, however I have a feeling someone will be by soon to move this to the general forum...
I actually wanted the opposite. Overall, I liked how bluetooth was handled on my old chocolate and was surprised by the differences in eclair. I expected my bluetooth to be able to grab all audio, regardless of what apps were running. For instance I wanted to use my BT with a fring call. Seemed sensible!
Anyway, I went searching, and the prevailing opinion was that bluetooth was locked up until Froyo (and tightly tied to actual calls).
Does anyone know if audio is handled in a gracefully way in current AOSP or CM?
Swyped w/ XDA App. When in doubt, mumble.
soba49 said:
I actually wanted the opposite. Overall, I liked how bluetooth was handled on my old chocolate and was surprised by the differences in eclair. I expected my bluetooth to be able to grab all audio, regardless of what apps were running. For instance I wanted to use my BT with a fring call. Seemed sensible!
Anyway, I went searching, and the prevailing opinion was that bluetooth was locked up until Froyo (and tightly tied to actual calls).
Does anyone know if audio is handled in a gracefully way in current AOSP or CM?
Click to expand...
Click to collapse
I believe that my Droid 1 behaved my desired way on 2.1 and 2.2, can't remember if I used this way on 2.0...
I was assuming this was a 'problem' on Fascinate or Samsung, not android OS in general.
I thinj its a problem with fascinate. I was driving for 5 hours last week and I had bluetooth connected to my garmin and used one of those cassette thingies to play music from my fascinate. Sometimes I were able to talk without unplugging the headset.
Another reason I suspect its fascinate is cuz when I use my old blackberry headphones I have unplug and replug to use it for conversations.
Btw whats good stereo heaphones with mic that works with the fascinate?
Sent from my SCH-I500 using XDA App
I have a friend with a Vibrant and his apparently does NOT have this problem, so I am wondering if a Bluetooth file from his system might work on my phone.
There are 3 BT files in system dump:
BT OPP
BT services
BT test mode
so is one of these the file that would determine what path audio would take in any given situation? (e.g. headphone jack occupied while BT headset connected, desired paths media>headphone phone>BT)
I REALLY need to fix this before my 30 days are up or phone probably going back.
I got my hopes up when I discovered the 'secret menu', but I don't see any setting in there that seems appropriate.
I've tested with the superclean 0.7 DL30 rom and this same problem still exists
Please let me know if anyone finds a solution.
[email protected] said:
i've tested with the superclean 0.7 dl30 rom and this same problem still exists
please let me know if anyone finds a solution.
Click to expand...
Click to collapse
stupid ass samsung friggin morons!
It looks like this is a problem on other Samsung Galaxy S phones as well, see a thread and app someone made in the Epic forums.
http://forum.xda-developers.com/showthread.php?t=842571
it is just the phone app
this problem is extremely frustrating. if i have headphones plugged in the mic works just fine. the mic is only turned off when i use an AUX cable. It would be nice to be able to drive and not have to worry about unplugging the AUX cable everytime I wanted to use my phone.
I downloaded the Epic app they made over there but all it did was hard lock my phone with my first test. I dug into the code but I'm a wee bit over my head so I'll hit up the books and see if I can't work with the guy who made the Epic one to see about getting it working with our phone.
This was with the .7 superclean DL30 rom, I'd love for someone else to try one of the other DL30 roms and see if they have any better success.
I contacted the author of the app and he replied back stating he had a buddy with a fascinate test it and it worked fine and that it might be an issue with the busybox version included with the .7 superclean 2.2 rom I was running and that it relied on busybox having the pidof command. Later tonight I'll dig into this a bit more and post back hopefully a fix and instructions on hwo to ensure this is working
I got this working http://forum.xda-developers.com/showthread.php?t=842571
The Froyo version works just fine on the original DL30 leak and on rubiks .3 DL30 but does NOT work on DL30 super clean .7 or .9. In .7 I got a hard lock that I had to do a battery pull to fix and in .9 the app ran and looked like it worked, but the audio routing did not change as expected.
All credit to cicada, I did nothing more than test it
I have not tested this on any 2.1 ROMS
thande said:
I got this working http://forum.xda-developers.com/showthread.php?t=842571
The Froyo version works just fine on the original DL30 leak and on rubiks .3 DL30 but does NOT work on DL30 super clean .7 or .9. In .7 I got a hard lock that I had to do a battery pull to fix and in .9 the app ran and looked like it worked, but the audio routing did not change as expected.
All credit to cicada, I did nothing more than test it
I have not tested this on any 2.1 ROMS
Click to expand...
Click to collapse
I am on original DL30 leak and did NOT work for me... at least with Ambling Book Player. Not sure if it matters what app we are using to play media file. It shouldn't, but this whole problem should not exist. SAMSUNG morons!
Ok so i tried with my Rubiks DL30 ROM installed. The app opens up, no FCs or bricks or anything, but it doesn't work. I had my wife call me when i was driving, I picked up and she said she could hear me but I still couldn't hear her. I'm assuming that the car's mic is functioning but it still doesn't fix the issue. Is there a bluetooth adapter out there i can stick in the aux jack? Well i guess the first question should be, can the phone handle having two BT devices connected at the same time? i.e. hands-free calling and BT audio adapter
I'd say maybe try another full wipe and re-flash. I've switched over to the superclean EB01 roms, currently on 2.3 and hasn't had any issues with this working on 2.1, 2.2 or 2.3. I did have 2.2 initially not function with this tool, similar to what you reported above with it looking like it was working but not actually doing anything but a full wipe and reflash did the trick.
ok... thanks, at least you've run into that problem so i'm willing to give it another go. I'm currently on SC 2.4 so i guess i can be your guinea pig
I'm on SC 2.4 currently and had it stop working on me again. At work now but I'm going to try setting the app off and then back on, I have had to do that sometimes when flashing as the files get overwritten. This was working properly in SC 2.3
Hey man, thanks for the updates and info... you're really like the ONLY person that's giving me any hope on this. I thought the compatibility issues were busybox related? So I don't see why it wouldn't work on SC2.4
Would someone please fix this on Fascinate... ? pleeeeezzzzzz
Today I finally loaded all my PSX and N64 ROMs from my N1 to my GTab, and then started to play.
I first noticed the problem with FPSE when I went into settings. There would be fairly loud "pops" from the tablet, and it seemed to happen at irregular intervals. It continues to happen while I'm in settings, although when I go back to playing it's fine again. The same problem with N64oid: only in settings.
I'm fairly sure it's the speakers (what else could make such a noise?!) but what puzzles me is that even with all volumes muted it doesn't stop.
It wouldn't be such a problem of it weren't so loud, as it almost sounds like the speakers will explode.
Anyone else running VeganTab GE with the same problem? Would you be able to try replicate it if you have either FPSE or N64oid?
I noticed the same thing the other day when I was in connectbot trying to fix my build.prop
I had the same issue running 5.1 and now I am stuck at the viewsonic boot screen after trying to install vegan ge rc-1.
It also seemed to pop with the original viewsonic ui and I had an elocity before this and it did the same thing. I think it is a android issue but I am a noob and know nothing!!
I couldn't get fpse to work on my last Rom will try later today and see if I can replicate.
Sent from my Desire HD using XDA Premium App
Oooo, sounds like your flux capacitor blew.
Would anyone know of a reason why Plants vs Zombies would not work properly on a rooted thunderbolt?
I played the game last night on a stock Thunderbolt. After I rooted it this morning it continues to go into a loading screen as if i hit the home screen and jumped back into the game.
I'm rooted and it works for me although the game will randomly shut down while I'm in the middle of playing
Sent from my ADR6400L using Tapatalk
I have no problems with it (so far at least).
dionysos803 said:
Would anyone know of a reason why Plants vs Zombies would not work properly on a rooted thunderbolt?
I played the game last night on a stock Thunderbolt. After I rooted it this morning it continues to go into a loading screen as if i hit the home screen and jumped back into the game.
Click to expand...
Click to collapse
Have you tried clearing the data? (yes you will lose your progress I believe, but it might work.) If not maybe reinstall it and see if that may fix the problem. Haven't had any problems with it over here so not sure. What rom/kernel/OC speed (if any) are you running?
das bamf 1.6 (just received a replacement TB). So after i rooted it i jumped back to restore point via clockwork. The whole thing appeared to have no problems, but i know of a few minor things wrong with it that were not like this before the replacement. I've tried over clocking it to see if that could fix the problem but still not success. Also I've tried the das bamf 1.7, i've cleared all the cache and so on. Ive uninstalled and reinstalled the game a few times
Damn, sorry, not sure what is wrong. I'm running BAMF 1.7 Remix, and it's working fine for me. Maybe try redownloading it, I highly doubt it was corrupted when downloading, but then again, stranger things have happened
I'm having no issues on Slayher's latest release of CM7.
me too.
I'm having major problems playing plants vs zombies also.
I start the game up and then I can't set the phone down... I try... but my hands instantly reach down and pick the phone back up.
I have a very similar problem with the game hex defense.
I'm running DAS BAMF 1.6 as is my girl friend and she is experiencing the exact same problems.
I can't get the app to run at all on my TB.
Running Liquid Thundersense. (thinking of switching ROMS.. still looking for that magic combo that won't randomly reboot 4 times a day while i'm at work)
Well I managed to get it going...I guess that since I took one of my backed up roms from ky original TB and restored it on a new one it some how caused a conflict with select apps. I went back, flashed an all new das bamf Rom from scratch and every thing is now working on my phone.
PS what a pain in the ass it was since I didn't have a titanium back up of all my stuff. 4 hours later I finally had everything re-downloaded. The birch is I still haven't had ti3 to re-set up my home screens.
Sent from my ADR6400L using XDA Premium App
In the past month, I have had 3 different Dell Streaks due to unrelated RMAs (Had 1 for 6 months that stopped charging due to a hardware connection damage; the next one permanently shut down soon after I received it) so I am trying to avoid having to call Dell for another replacement if it isn't just my phone which has the following problem:
Certain games are causing the phone to shut down, flash the buttons 3 times, and reboot. This problem happens consistently when I play Death Worm Free so I will use that as a test app though it has happened while playing other games as well.
Software config:
To diagnose the problem, I have tried playing Death Worm Free on my phone after correctly flashing to 351, 353, and 354. On all ROMs, the game crashed the phone even when I had not installed any other apps from the market.
The game is reasonably fun so you won't be dissappointed, but I don't want to call for a replacement just to have the same problem... so I ask:
can anyone download Death Worm Free from the market and install it and play for longer than 20 minutes without it crashing the phone? (I would link to it but I can't... not allowed... noob forum member). Note: nothing besides games are crashing the phone. It may be heat or it may be a problem running graphics intensive apps.
It would be a great help for me. If you do help me and install the game and play it, please let me know whether it crashed your phone also or if you played successfully and what ROM you are using. Also, any alternative suggestions?
Use Navigator every time you go anywhere. If it's the phone dying under pressure, that should trigger it. If it works perfectly then the problem is likely the game.
Sounds like the problem I had. Even long phone calls could trigger it. I just got my replacement yesterday.
Update; I reflashed to 353 (the latest ATT stock that came with the phone in question) and I am again stuck with an older version of swype (yet nobody in this forum has compared the swype versions in each Dell build) but the games are slightly more resilient. I wish I knew... can anyone answer: if I install a custom ROM like streakdroid, can I reinstall my 353 stock rom in case I still want to use a RMA (and have it unrooted?)?
Yes you can revert from a custom ROM to a stock ROM. Unless there are AT&T apps that you use for a stock ROM I suggest BB 351.
Radimus’s Universal Guide to Flashing a ROM – MUST READ if you want to flash a ROM or upgrade (or revert to stock)
marvin02 said:
Yes you can revert from a custom ROM to a stock ROM. Unless there are AT&T apps that you use for a stock ROM I suggest BB 351.
Click to expand...
Click to collapse
What is BB 351? The stock build? I alread posted that the games were crashing the phone with that build. People seem happy with build 354 so I will stick with that once anyone answers my question about whether it is my phone that is crappy or streaks in general that cannot handle the game.
I have a windshield cradle for my Amaze, and I run a cassette adapter down to my radio. This seems unrelated, but you'll see why I mention it...
I know about the echo problem in non-stock roms (maybe just non-sense roms? Haven't tried any sense based roms other than the stock one.)
I have used CM10, 10.1, 10.2, etc... I lived with the problem, it wasn't too terribly bad. UNLESS I tried using my phone over my car stereo, set up as described above. The echo was HORRIBLE to the person on the other end.
So I've gone to a debloated stock rom, and now the call is crystal clear while in the dock. "Ok," I said to myself, "I just need to wait until KitKat is finished, it'll fix the echo problem."
When KitKat (both CM11 and Evervolv 4.4) was relased, I tried them both. The echo, when in the cradle, was WORSE than before!
My question is this: could there be something else different between sense-stock-based-roms and all the rest that would cause this? I'd like to use KitKat, but until this echo issue is resolved I must stay with the stock. Not a horrible fate, I like stock. Especially debloated and tweaked with custom launchers, etc. But the main reason I'd like KitKat is that I heard it emulates the SecureElement chip in the NFC, allowing us to make mobile payments via Google Wallet. I've not heard if anyone's tried it or not, it was just a rumor I heard somewhere.
So, any ideas?
DarkMatter_74 said:
I have a windshield cradle for my Amaze, and I run a cassette adapter down to my radio. This seems unrelated, but you'll see why I mention it...
I know about the echo problem in non-stock roms (maybe just non-sense roms? Haven't tried any sense based roms other than the stock one.)
I have used CM10, 10.1, 10.2, etc... I lived with the problem, it wasn't too terribly bad. UNLESS I tried using my phone over my car stereo, set up as described above. The echo was HORRIBLE to the person on the other end.
So I've gone to a debloated stock rom, and now the call is crystal clear while in the dock. "Ok," I said to myself, "I just need to wait until KitKat is finished, it'll fix the echo problem."
When KitKat (both CM11 and Evervolv 4.4) was relased, I tried them both. The echo, when in the cradle, was WORSE than before!
My question is this: could there be something else different between sense-stock-based-roms and all the rest that would cause this? I'd like to use KitKat, but until this echo issue is resolved I must stay with the stock. Not a horrible fate, I like stock. Especially debloated and tweaked with custom launchers, etc. But the main reason I'd like KitKat is that I heard it emulates the SecureElement chip in the NFC, allowing us to make mobile payments via Google Wallet. I've not heard if anyone's tried it or not, it was just a rumor I heard somewhere.
So, any ideas?
Click to expand...
Click to collapse
An echo when going through your car stereo is something I've experienced on every ROM on every device I've ever owned. It isn't a problem per say with the Amaze, it happens with my best friend's iPhone too. This is why most folks use Bluetooth earpieces while driving. I have no experience myself with a cradle (my stereo allows me to pair directly to my phone), but my friends that have used them in their vehicles have all had reverberation issues regardless of the device used. I hope this helps.