Database Users

Universal & A2DP

Hello Guys,
Does any of you happen to know if HTC Universal supports A2DP (for Stereo Bluetooth headset), and if it does not support it, can it be patched WITHOUT flashing the whole ROM?
Thanx in advance!
Cheers

Yep the latest qtek rom adds A2DP, I am using it with the new nokia HS-12w

Thanx ice
Hello ice_coffee,
Thank you for your reply, I know now that it does support it (hardware wise), but do you happen to know if I can enable that without having to reflash the whole ROM, I use Orange ROM and I have some stuff that I dont want to lose (not data, I am talking about apps), so do you have any idea if I can just (some way) add this feature?
My 2nd question would be how long would you be able to listen to music before the battery goes dead?
Cheers Mate!
ice_coffee said:
Yep the latest qtek rom adds A2DP, I am using it with the new nokia HS-12w
Click to expand...
Click to collapse

I would be interested in this as well.
I have tried VJvolubilis and also btaudio.zip but both only work for a few seconds and then voice speed dial kicks in and the audio stops :-(
Stu..

Anyone know of an Android build w/ following working?

Anyone know of an Android build w/ these working?
-bluetooth (connects to car's hands free automatically w/sound coming out from car's speaker)
-camera w/flash (5MP)
-compass
-youtube w/o green line
-3G
I've tried several builds already but seems like none of them have all these working.......
your input will be much appreciated! Thanks

Try and provide feedback please:
[BUILD][29.09.2010][FroyoStone Sense - V3.1][Kernel: darkstone]
http://forum.xda-developers.com/showthread.php?t=747492

thanx! can't wait to try it tonite

euro_e93 said:
thanx! can't wait to try it tonite
Click to expand...
Click to collapse
it has premature flash too...
Is there really a sense build without that problem I wonder...

memin1857 said:
Try and provide feedback please:
[BUILD][29.09.2010][FroyoStone Sense - V3.1][Kernel: darkstone]
Click to expand...
Click to collapse
I've read some posts that this build still has premature flash problems

oh....... not good news.......

euro_e93 said:
oh....... not good news.......
Click to expand...
Click to collapse
I will now try Core_Droid_V0.4R and tell you if it has the same problem too...
It claims not... but we'll see...

Terabite7 said:
I will now try Core_Droid_V0.4R and tell you if it has the same problem too...
It claims not... but we'll see...
Click to expand...
Click to collapse
Yeah at last a build yhat totally works , wifi , flash , everything...
A bit customized but not a prob...

COOL! i'll try it out tonight

euro_e93 said:
Anyone know of an Android build w/ these working?
-bluetooth (connects to car's hands free automatically w/sound coming out from car's speaker)
-camera w/flash
-compass
I've tried several builds already but seems like none of them have all these working.......
your input will be much appreciated! Thanks
Click to expand...
Click to collapse
Hyperdroid

Well I cant tell you that bangsters 1.4 has everything that you want working but it has one problem: BT works for transfering files and also connects to car's hands free automatically w/sound coming out from car's speaker to listen to the music in your car but it does NOT work to make phone calls trhu BT
So technically this build works for everything that you want because you did not mention to make phone calls thru BT

jmmmmm said:
Hyperdroid
Click to expand...
Click to collapse
nope, BT won't autoconnect

sorin129 said:
Well I cant tell you that bangsters 1.4 has everything that you want working but it has one problem: BT works for transfering files and also connects to car's hands free automatically w/sound coming out from car's speaker to listen to the music in your car but it does NOT work to make phone calls trhu BT
So technically this build works for everything that you want because you did not mention to make phone calls thru BT
Click to expand...
Click to collapse
haha............i meant make calls thru BT

added a couple things in my post

Terabite7 said:
Yeah at last a build yhat totally works , wifi , flash , everything...
A bit customized but not a prob...
Click to expand...
Click to collapse
just found out camera's 3MP & youtube has green line..... but aside from that everything works It's a great build so far!

Feedback
Working well. Fast, reliable, good!
FroyoStone Sense - V3.1][Kernel: darkstone]
2.14.50.xxx radio
Stock WM ROM
Only problems so far:
-Occasional lag when waking (only with wifi on? testing)
-Occasional "upload freeze" of 3G/H (only when switching from wifi to 3G/H?) Easy fix by switching data off & on
-Camera flash timing
-After taking pic, grey translucent window with small missed call icon pops up
-Light sensor doesn't seem to be working
-Notification window "sticks" - e.g. I get K9 notification, open notification window, touch K9 icon - icon disappears and K9 opens *behind* the notification window which stays open
-Slight crackling/clipping in earpiece during incoming calls
None of these are deal breakers by any stretch! This build is great so far. I'm going to try updating to hastarin r7.1 to see if it helps at all...
Ryan
:edit: oops meant to post in FroyoStone thread...

Using HD2 Headset remote with Android ROM

Searched but can't find an answer.
How does every one else dealing with this situation? Is there a work around to make the remote button work with different Android builds?
Would it work if I use a matching OEM headset? For example, get the OEM EVO headset to use with EVO based build?

what is it ur specifically trying to do
hey what is it u wanna do bc I have the desire build and I use the headphones that came with my hd2 to control my music thats about it u can do with it and u know the basic use it to talk and what not but even than u have to have winamp installed on ur phone which u can get from the android market for free or it also works as a music controller on the htc music on android idk if it works for the other builds tho, hope this helps

Try the headphone come with iphone, it,s work!

silvscorp said:
How does every one else dealing with this situation? Is there a work around to make the remote button work with different Android builds?
Click to expand...
Click to collapse
What are you talking about? Headsets have been working properly almost since the start of Android porting.

Fedr0 said:
What are you talking about? Headsets have been working properly almost since the start of Android porting.
Click to expand...
Click to collapse
I think he means for controlling music. It may be a non-sense build issue. My original HD2 headset buttons don't work for skip forward, back or play/pause. This is on Bangsters V1.5. My bluetooth headset does work for these functions though. When I used desire builds the headset buttons would work, but only if the screen was on.

trmacdonal said:
I think he means for controlling music. It may be a non-sense build issue.
Click to expand...
Click to collapse
That's strange, I've never had that problem and I never use Sense builds. This with the screen either on or off, it doesn't make any difference.

Anyone solved this problem after NAND builds were released?
Somehow I managed to get my headset working just after flashing new build, but next morning I found no music control from headset whatsoever. Really annoying this is because I use them a lot when I go to work or enywhere else :/

npocmo said:
Anyone solved this problem after NAND builds were released?
Somehow I managed to get my headset working just after flashing new build, but next morning I found no music control from headset whatsoever. Really annoying this is because I use them a lot when I go to work or enywhere else :/
Click to expand...
Click to collapse
yes me too and I have found any solution the call/answer button enable only Voice Recognition and the (next/back) button enable nothing
@npocmo: I think that dosent work with the desire HD build portage. Did you tried with a nand Desire ?

i flashed MDJ's CyanogenMod 7 v. 2.6 [A2SD+][GRH78C][RMNET][Kernel: MDJ S10.4 OC] and face the same problem.
is there any solution?

wow this thread is so old !! has anyone found the solution ? i flashed [Feb 02][DL DesireZ v3.4][DL Data2SD/Ext4 v2.7][Nand/SD/MAGLAR] yesterday and have the same problem, the remote doesn't do anything other than make the music player go crazy. solution please ? should i try with another android build ?

I have the same problem with this build!

actually these devs were saying that it was infact gingerbread who wasnt supporting the headset controls.. but now most of them do.. only thing you can do is thoroughly search the build thread to make sure that they work before flasshing them unto your phone so you know exactly what your getting into

Try changing kernel to gauner

Yes, the problem on kernel mdj.If you change kernel on to gauner it will works.

soberlam said:
i flashed MDJ's CyanogenMod 7 v. 2.6 [A2SD+][GRH78C][RMNET][Kernel: MDJ S10.4 OC] and face the same problem.
is there any solution?
Click to expand...
Click to collapse
I changed the kernel and it working

Can someone explain how to fix it? I did not understand..
I have on my Leo's -= MDJ CyanogenMod 7 v. 2.6 [+ A2SD] [GRH78C] [RMNET] [Kernel: MDJ S10.4 OC]. Excuse my English but I'm Italian

Anyone can help me?

mylove299 said:
I changed the kernel and it working
Click to expand...
Click to collapse
so can i use NAND MDJ but use gauner kernel ?

How do I change only the kernel? without losing data?

where can i get gauners kernel please

Is There Any Fix for the Bluetooth Voice Dialing Crash Issue?

I've never seen a dedicated thread on this but I've seen people make off-hand comments about this issue from time to time. I think it started happening in Tytung R9 and higher kernels.
I am using a BlueAnt T1 Bluetooth headset. It pairs just fine and I can use it generally without any issue.
The problem comes when I use voice dialing to initialize a call from the Bluetooth headset. It connects to the phone and I get the normal Android "Speak now...." I speak my command "Call <person> on <service>...." It states the command back like normal and then _as soon as_ it switches to the phone app (eg, com.android.phone process) it locks up the phone and the only way to recover is to pull the battery.
If, instead, I go to the phone app, find the person, and call them that way (even with Bluetooth paired) it _always_ works without any problems. This isn't a long-term solution for me because I need to use voice dialing when I'm in my car.
Now that GPS looks to be fixed and CLK data over PPP is much more stable, this Bluetooth issue is the last thing standing between me and treating the HD2 as my full-time native Android phone (currently I tinker on the HD2 but use my Nexus One as my daily driver).
I've tried multiple different ROMs, from HyperDroid-CM7, HyperDroid-GBX, Typhoon CM7, and Nexus-HD2-Gingerbread. They all have the same issue though Nexus-HD2 appears to be worse than the others (that is, the problem happens more often there).
I've used the infamous audio.conf update as well as the various no-wonk and libaudio patches and none of them help this issue.
Anyone else experienced this and have any feedback on how you overcame it?

I have the same kind of problem and tried a lot of different ROMs - not help.
I tried Blueant ST3, Motorola t305.
Phone book copied to blueant very well, but voice dial has same simptoms like yours - even if phone does't hang sound goes away from phone permanently(needs reboot). Is there any other ROM which works well with bluetooth hadsfree?
Any one?
P.S. Looks like it is real problem, but non of developers pay attention to it - they just don't have handsfree maybe

Ι think that sense roms doesnt have this issue.But unfortunatelly they have other issues...

clio94 said:
Ι think that sense roms doesnt have this issue.But unfortunatelly they have other issues...
Click to expand...
Click to collapse
I've not actually tried a SENSE-based ROM but I understand from my research that they don't have the BT issue. Maybe it's possible to look into their architecture to understand what is different.
I expect that it's something in the kernel....

This is a very common issue. if it helps, BTvoice command works Fine in Froyo.. at least CM6 (I tested).

svet-am said:
I've not actually tried a SENSE-based ROM but I understand from my research that they don't have the BT issue. Maybe it's possible to look into their architecture to understand what is different.
I expect that it's something in the kernel....
Click to expand...
Click to collapse
I think it is not the kernel, same kernel will crash in CM7 but no in CM6. I think the problem is related to the libaudio.so and other libs in system/lib.

robrob777 said:
This is a very common issue. if it helps, BTvoice command works Fine in Froyo.. at least CM6 (I tested).
Click to expand...
Click to collapse
are the Froyo-based builds still being maintained. I ask that from the perspective of "could I just use a Froyo build as my daily driver instead?"

svet-am said:
are the Froyo-based builds still being maintained. I ask that from the perspective of "could I just use a Froyo build as my daily driver instead?"
Click to expand...
Click to collapse
I'm using it as my daily driver (CM6), I came back just bc of the calling issues in Gingerbread.
the build that I'm using has not been updated since Jan 7, however I applied around 10+ patches and now it works as good as the new builds.

I just tested again voice command.
No problems
During the voice command call I can switch from BT to speaker to audio piece, back to BT etc, no problems. Audio doesn't crash after call.
And no 60ma battery drain. it is around 5ma after the call with BT on.

robrob777 said:
I just tested again voice command.
No problems
During the voice command call I can switch from BT to speaker to audio piece, back to BT etc, no problems. Audio doesn't crash after call.
And no 60ma battery drain. it is around 5ma after the call with BT on.
Click to expand...
Click to collapse
just for clarity for other folks reading this thread, I assume that you're talking about a Froyo-based ROM.

i just verified the problem exists in MIUI as well. I tested MIUI since it's allegedly a "clean room" type of build environment.

svet-am said:
just for clarity for other folks reading this thread, I assume that you're talking about a Froyo-based ROM.
Click to expand...
Click to collapse
Yes, I tested successfully in a Froyo based ROM.
I went back for a moment to CM7 and tested...sound couldn't return to the phone after calling with BT, also during the call I was not able to switch to speaker phone like I do in the froyo based ROM.

Tested with Tytung 1.9G Froyo - BT works just fine in all ways. Just need to keep GPS off(when not used) to avoid 60 ma current draw.
Tytung says BT Voice dail is just GBread problem.

zcdg said:
Tested with Tytung 1.9G Froyo - BT works just fine in all ways. Just need to keep GPS off(when not used) to avoid 60 ma current draw.
Tytung says BT Voice dail is just GBread problem.
Click to expand...
Click to collapse
It works fine on my Nexus One on Gingerbread, so I don't see how it can be a "gingerbread problem." If it was a "gingerbread problem" other devices would be seeing this as well.

svet-am said:
It works fine on my Nexus One on Gingerbread, so I don't see how it can be a "gingerbread problem." If it was a "gingerbread problem" other devices would be seeing this as well.
Click to expand...
Click to collapse
Yes you are right. It is just what Tytung said(i asked in his thread). Probably he meant GB for HD2....Soon or later they will figure it out i think...
For now will use Froyo 1.9G....

tytung said:
I don't have any Bluetooth headset.
AFAIK, some people have the sound issues, e.g. causing the phone app FC, since using Gingerbread 2.3.4.
But it doesn't affect all people, I don't know why.
No solution so far. To use Gingerbread 2.3.3 instead if you are one of them.
Click to expand...
Click to collapse
I finally found Tytung's exact quote as to why he won't look into the issue. It can be seen in context over here: http://forum.xda-developers.com/showthread.php?t=905060&page=524#
So, it might not be Froyo that's the fix but rather older versions of Gingerbread as well.

i have found a workaround fix for this bug.I tried it in tytung`s v2.9 rom and in dorimanx cm7 light rom with driztee v2 libaudio file.For bt voice commands i am using cyberon voice commander because google app doesnt support yet greek language
i connect my bt headset (motorola h300) and then i use super bt mono froyo free app https://market.android.com/details?id=com.steven.supermonofroyofree&feature=search_result to send audio to bt headset.
After pushing the bt headset button cyberon voice starts and i can give the command i want.After giving the command, audio goes back to the phone (you will hear a beep from phone speaker).The weird thing is that the audio is in extremely low level for hearing music but when you receive a call it is in normal level.
If i close super bt mono froyo app,audio returns to phone in normal level.
But if i accidentally (after i close the app) push the button for voice bt command,audio will disappear.
If the app is on and you receive a call,all audio will go again to bt headset and to return it to phone speaker after end call, i push bt headset,cyberon voice starts and i dont give any comand.After cyberon ends,audio goes back to phone with low level for media hearing.
Sure this isnt the perfect solution,but the important thing for me is that with this way,audio is not go away and i can give bt voice commands.
Also i tried bt mono app http://forum.xda-developers.com/showthread.php?t=950472 and it have a little different behaviour.I cant start from bt headset cyberon voice comander,but only from the phone and after giving a command,audio returns to bt headset if you have enable the setting "restart after call".So i think it maybe be helpful to people who want to have audio all time in a bt carkit.

Tested all 2.3.3 from Tytung - last working with r8.3 kernel. r9 and up not working.
So NexusHD2 v2.5 NAND(GB 2.3.3) with r8.3 latest working with BT voice dial ROM.

zcdg said:
Tested all 2.3.3 from Tytung - last working with r8.3 kernel. r9 and up not working.
So NexusHD2 v2.5 NAND(GB 2.3.3) with r8.3 latest working with BT voice dial ROM.
Click to expand...
Click to collapse
thanks for that follow-up and testing. I was wondering if whether or not it might be a "fault" in the VoiceDialer.apk or even in the Phone.apk. I have been using my Nexus One for daily stuff. I might try replacing VoiceDialer and/or Phone.apk in a newer ROM (eg AOSP 2.3.5 or so) with the old version and see if it works.

Ive wondered about this as it is to me the last issue I have with my HD2. Here is a search link for some entries in Tytungs rom & kernal thread...
http://forum.xda-developers.com/search.php?searchid=86308155
Also here is a comment from the man himself...
http://forum.xda-developers.com/showpost.php?p=15996942&postcount=5953
and here is a post in reply that talks about the same issue being replicated using Bluetooth...
http://forum.xda-developers.com/showpost.php?p=15997234&postcount=5956
Some more chat about the sound issues...
http://forum.xda-developers.com/showpost.php?p=16113973&postcount=6045
Another thread with logcats on it...
http://forum.xda-developers.com/showthread.php?t=1060486

Bluetooth Bug in CM11 by ED300

Can anyone pls provide a fix for Bluetooth in CM11 by @ED300. BT turns on but unable to pair it with any headphones or BT speaker or car stereo.

Ask ED or change the rom ?

GuestStar said:
Ask ED or change the rom
Click to expand...
Click to collapse
I tagged it him so that I could get a reply but seems of no use.
I have tried other roms but this seems to be the most stable rom atleast for me. The N roms lags on 1GB model after few days.