Htc G1 3 in 1 headphone adapter - G1 General

Hey guys i.d.k. if you've already found a way past this or figure this out period but just thought i'd add this...
Anyway, i bought 3 in 1 headphone adapter the other day and it didn't work due to the cupcake update...So i was messing with it and figured out if you plug in the actual headphones(t mobile ones) into the adapter you can then use your regular headphones or for me i can now hook it up to my car....cause i guess if you already have the headphones it would be kinda useless....anyway just thought i'd mention that i think of might of saw someone already say this in the archive though...

Download the headset toggle widget, it will make your headset work

I don't know if you're rooted (it sounds like you may be using the standard Cupcake build), but several of the more popular roms have addressed this bug. I know Cyanogen's roms fixed this a while ago.

I have a 3 in 1 with latest cyanogen, mine works fine

Related

Problem with jasjar

Since imates support is terrible ill post my issue here to see how i should proceed.
I got my jasjar in a few days ago and its never worked right. The speakers and mics on the phone would cut in and out and sometime not work at all. Ive had to use a bluetooth headset (the wired headset port also works) mostly because I *need* a phone for work. I mate told me to flash the device with the recent firmware (also does anybody have a link to a one more recent than on imate site?) cause I might be missing files but that didnt help.
Is the phone just broken? In which case ill have to keep having to putup with imates crappy support to try and get an rma
Im still a little cheesed about the frequency difference for 3G in the us

Bluetooth and HTC touch problems

Does anyone else have a problem with their Bluetooth and HTC touch? I have tried 2 motorola and a LG BT headset and no one can hear me, but I can hear them. I tried pairing and repairing. I deleted it and added it as a new device. I have even tried the BT with another phone and it works with that phone with no problems, so I know it's my phone. I even tried a hard reset. Does anyone have a solutoin to this problem? I have the latest ROM update from HTC's website for a Bell HTC touch. My motorola headset was working fine, but I think after the latest Bell ROM update it stopped. Does anyone else have this problem or can anyone suggest a solution? thanks. paul.
my jawbone did this but my plantanics 510 fine
My jawbone works fine but there's a problem using hands free connection with my '05 range rover. The phone and the truck connect but then the connection is dropped. My buddy has a motorola razor and his phone works great w/my truck. It appears to be my phone that's the problem. Any suggestions on this?
Thanks so much.
jarmijo said:
My jawbone works fine but there's a problem using hands free connection with my '05 range rover. The phone and the truck connect but then the connection is dropped. My buddy has a motorola razor and his phone works great w/my truck. It appears to be my phone that's the problem. Any suggestions on this?
Thanks so much.
Click to expand...
Click to collapse
This thread is 7 months old...
What ROM are you running?
I am running the NFSFAN 6.5 rom V11 and have he same issue with a motorola BT headset.
edit: i just noticed that the initial question was about a newer ROM update and bluetooth, but ill leave my initial reply here, cuz i often look for solution in old posts, so if this can help anybody :
NFSFAN 6.5 rom V11 and bluetooth
i dunno, but my bluetooth stuff somehow works with the 6.1 update, if you cant find any working solution within an hour, id suggest using a "well tried and tested" ROM version, like the 6.1
i stopped picking the "latest and greatest" in cars, devices, apps, or O.S. for the last two years, and been living a whole lot happier since.
about my 6.1 bell mobility ROM and bluetooth :
i like to tweak my weapons alot, my htc touch has a 6.1 ROM update, and i use bluetooth everyday, and it KINDA works well, enough for me anyway...
listening to mp3 and flv everyday on the transit,
then switching at work on the audio dongle adaptor on the pc,
using an pair of sonorix bsh-100 ( foldable stereo headset + optional plug-in mike)
to me the thruth is that bluetooth is a ****ty technology, i love it, and it's well taught,
but the developpers quickly code ****ty interfaces to it.
my settings all work from htc touch to dongle, but i often have to connect the touch to the headset like up to 3 times, where it tells me its connected, but isnt, when i hear the beep, it means it actually IS.
same at work, connect sometimes once, twice, even four, it eventually connects.
it's isnt button wear off or bad contact, its just the code is ****.
i rented a SUV that had bluetooth, tried connecting my phone, worked first time, a week later we rented the same SUV model, and for the whole trip i wasnt able to connect at all... back at the rental we tested the SUV with the clerck htc touch ( nice coincidence ) it worked right away.
i want to add here that whenever i try to connect through bluetooth, it usually works the first time.
my point is, bluetooth creators did a fine innovative job, but werent supported by developpers.
test your bluetooth phone alot with friends owning bluetooth accessories, youll detect behaviors after a while, and will learn to know its "demons" !
a bluetooth everyday user
V13 seemed to fix the issue
Just upgraded to V13, seems like BT works a lot better.
A bit on my history with BY, I just upgraded from a motorola V710, had a Moto Q for a few months too. Never had any issues with BT using the same Motorola BT earpiece, and varouis others through the last 5 years or so. Always worked like a champ, this was my first experience with BT issues.

1.6 stopped headphones

after the 1.6 update i can no longer use my headphones. i was able to use them with toggle headset widget before. anyone know how i can fix this?
anyone have a solution, i cant listen to music
Me too
I'm having this exact problem. It was odd; when i first installed 1.6 the headphones flicked on and off for all of 5 minutes and then stopped working fully. I have the standard usb to 3.5 converter that came with the phone, and it seems to work in another device.
I tried a couple of fixes that had been suggested to people having a similar problem when they had upgraded to cupcake but neither of these worked.
Halp would be appreciated
What radio version you guys have?
First thing i read on your reply was about cutting throuats and spreading cheese which totally threw me...
Anyway, am using CyanogenMod 4.1.999, and if i'm right in thinking radio and baseband are the same thing..... 62.50s.20.17H_2.22.19.261
I just updated to the latest mod 4.1.9999 and still it won't recognise the headset. It is the original one that came with my G1.
Have searched fairly extensively and can't find anything.
Any pointers or suggestions would be very useful.
theres an app called sound route switcher, its updated and i heard it works, but i dont have a credit card, wish someone would update headset toggle widget

LiquidAUX Bluetooth Car Kit & 2.1 ROMs

This isn't supposed to be some sort of complaint or anything, but was just wondering if anyone had any suggestions/ideas why my K33428US LiquidAUX Bluetooth Car Kit stopped working with ANY 2.1 ROM (FRESH & Damage)
it worked great with 1.5 but honestly I am not rolling back now, will just have to use the headphone jack for now.
At first I thought it was an issue with AD2P in general but then i started to see posts where people had success with it, so now i am disappointed.
Glod said:
This isn't supposed to be some sort of complaint or anything, but was just wondering if anyone had any suggestions/ideas why my K33428US LiquidAUX Bluetooth Car Kit stopped working with ANY 2.1 ROM (FRESH & Damage)
it worked great with 1.5 but honestly I am not rolling back now, will just have to use the headphone jack for now.
At first I thought it was an issue with AD2P in general but then i started to see posts where people had success with it, so now i am disappointed.
Click to expand...
Click to collapse
I have the same kit and i can connect just fine...but with 2.1 I have to manually connect it everytime but going into settings.

Bluetooth A2DP issues w/ 2.1

So, I have searched all over these forums, and cannot find a difinitive answer or solution. I have problems with A2DP when connecting w/ the BT in my car, since installing a 2.1 ROM (currently DC 2.09.01). When connected, the music plays about twice as fast as it should, then slows down, then speeds up again. Conversley, Android 1.5 worked fine. There has been a lot of talk of BT issues, but it doesn't appear there are any solutions. Am I correct, or has someone found a solution? THanks.
ZenEXP works if you dont mind switching.
I have had those problems occasionally with all 2.1 ROMs I have tried. Usually, if I pause and then unpause it solves the problem. Sometimes I have to do it more than once.
I'm currently running ZenEXP and I've had the problem a few times, but it has been significantly less than with other ROMs. However, AVRCP hasn't been working with ZenEXP, whereas it has worked on other 2.1 ROMs, such as DC.
So, with the unrooted stock Sprint 2.1 software, A2DP works?
The Darchdroid ROM actually fixes this problem! I had the exact same problem as you with playing audio in my 2010 Mazda 3 and Darchstar's ROM fixed it for me, it's the only ROM I have found so far that fixes the bluetooth
I have a problem with my bluetooth headset when I'm playing music, the music stutters alot, I almost have to hold my phone a certain way with very little movement in order for it to play decently. Any solutions on that problem?
I have a problem with my bluetooth headset when I'm playing music, the music stutters alot, I almost have to hold my phone a certain way with very little movement in order for it to play decently. Any solutions on that problem?
Click to expand...
Click to collapse
Turn off/disconnect headset while playing music fixes studdering for me in settings under bluetooth for the connected device. Disconnect the ' phone' while playing. Haven't really tested this on anything but my kenwood head unit.
-------------------------------------
Sent via the XDA Tapatalk App
here's a reply I received from HTC support:
Hello, I understand that you have had issues with your bluetooth since the update for your Hero. With the update, the entire bluetooth stack was updated, and thus some bluetooth devices that previously worked are unfortunately no longer compatible. While we have not heard any information about nor made announcements about any upcoming patches to address this, it is not at all out of the realm of possibility. Otherwise, you may want to try a different bluetooth headset. I do apologize for any inconvenience you may have experienced. If you have any other questions, feel free to contact us again. You can find additional support at support forums at community.htc.com. There is also a customer satisfaction survey for you to take if you are interested. Philip HTC Technical Support www.htc.com www.twitter.com/htc
Bluetooth Stack?
So is it possible for one of the developers on this site to rewrite the bluetooth stack or copy the old one from 1.5 that worked?
I have a Panasonic TH12 bluetooth home phone that worked fine before 2.1. I recently bought an AT&T bluetooth phone and it does the same thing. Will pair but not connect.
aschlect said:
Hello, I understand that you have had issues with your bluetooth since the update for your Hero. With the update, the entire bluetooth stack was updated, and thus some bluetooth devices that previously worked are unfortunately no longer compatible. While we have not heard any information about nor made announcements about any upcoming patches to address this, it is not at all out of the realm of possibility. Otherwise, you may want to try a different bluetooth headset. I do apologize for any inconvenience you may have experienced. If you have any other questions, feel free to contact us again. You can find additional support at support forums at community.htc.com. There is also a customer satisfaction survey for you to take if you are interested. Philip HTC Technical Support www.htc.com www.twitter.com/htc
Click to expand...
Click to collapse
I have to call BS on this. (Not on the post, on the reply)
Why would any company not support legacy hardware as simple as Bluetooth. Especially since most devices aren't even Bluetooth v3/v4 standard yet. And Bluetooth 2.1 is 1. Not very old and 2. What 90% of Bluetooth device still manufactured are! and its been around since 2006!
I honestly can't believe a company is going to just say "Oh its to old" instead of fixing their crap. as far as I know v3/v4 is fully backwards compatible to 2.1 because they include "Classic Bluetooth" protocols!
Not to mention I doubt the hardware in our phone is even capable of v4 stuff. I'll have to do some more research on what BT chip is in the phone. Utter BS.
Either Phillip or HTC is a moron.
CDMA Hero Specs for BT:
Supported Profiles: HSP 1.1, HFP 1.5, A2DP, AVRC, (OPP, PBA)
version 2.0+EDR / possibly upgradeable to 2.1+EDR, plus OPP and PBA profiles
2.1 FULLY backwards compatible to v1. Meaning HTC built the crappiest BT Stack allowable by law to say it includes it. May as well have not bothered.
Someone could probably redo things with AOSP and a newer bluez stack.
Kcarpenter said:
<snip>
2.1 FULLY backwards compatible to v1. Meaning HTC built the crappiest BT Stack allowable by law to say it includes it. May as well have not bothered.
Someone could probably redo things with AOSP and a newer bluez stack.
Click to expand...
Click to collapse
Yeah, I just bought a BT USB adapter so I could exchange files and synch and stuff. I got it to work ONE time and all it did was pass 200 of my contacts to my phone from my PC. Like it was just waiting to upchuck on me. After that, nothing.
There's three hours of my life and $8.99 I'll never get back.
Bluetooth is pretty much the #1 complaint that users have been posting on the Sprint Community Forums (here's the HTC Hero section). Nearly all of those complaints say that Bluetooth now doesn't work at all or just plain sucks on the stock 2.1 Sprint/HTC release. Which probably also means that any ROM here based on 2.1 stock will also suck it up bad with Bluetooth compatibility. Known problem, no one has done anything about it yet. It sounds like AOSP ROMs don't have this issue, so at least that's good.

Categories

Resources