got my Ameo last Friday, here's my first feedback:
- receiving phone calls is different: there is no vibrating alarm, so you have to either rely on the shipped headset (cable) or on a bluetooth headset
- even if you plug the headset into the socket the device will make a noise when it receives a call, unless you set the phone volume off completely
- you cannot hang up call with the little button on the head set: it is in your pocket and you listen to some music over the headset (cable), you receive a call and push the button of the headset, you take the call, but you cannot end it on your own, either pull out the device and press the button on screen or wait until other end has hung up
- battery power depends heavily on use: from more than two days with aggressive power saving features enabled (min. brightness, no wifi, no bt, no gps, ca. 1h phone calls) to under 2 hours when everything is turned on and the device is connected to internet via 3G and acts as a router for laptop (in this mode I was trying to recharge the device via USB cable, but the energy consumption of the device was higher than what my MacBook Pro had to offer via USB)
- device does not support the DUN profile, if you want to use it with your laptop you have to use the PAN profile (not working for Macosx out of the box, but I am still trying)
- VueFlo feature is amazing, though sometimes response is not instant
- multimedia features successfully tested (with tcpmp): Divx+AAC, ogg, mp3, streaming media via wifi
- multimedia features missed: realplayer, flash player
- I hope that screen resolution will be changed in the future, as everything seems a little bit to large on that screen
- keyboard: never used, the keyboard and the device together form a quite bulky combo that doesn't fit into the pocket of my jacket and the keyboard is quite heavy too
- speed: much better though I have the feeling that either SPB Pocket Plus or Pocket Informant slowed the device down a little bit, have to investigate this further
that all for now,
Urfin
Related
A2DPtoggle (www.teksoftco.com) is about the most perfect program we can wish to control our Bluetooth stereo headsets. Unfortunately it has one major drawback. It sucks the battery dry, even when you are not listening to music. I mean, seriously power hungry, my battery does not last a day (and no, it is not the battery, if I remove the software my battery live about doubles).
This leaves the question to you readers. do you know an alternative program that can switch audio between speakers and headphone. It is too much trouble to go into the bluetooth settings each time to click the profile on and off.
suggestions would be appreciated
are you trying to to listen to audio through bluetooth headphones or a bluetooth headset.
bluetooth stereo headphones
I use QuickMenu, which brings a Windows desktop-like Start menu to WM, and has a built-in bluetooth control. http://www.freewareppc.com/utilities/quickmenu.shtml
Note this does not allow you to toggle a2dp and mono, just bt on/off, but its no big deal for me since I can control that from my headset.
try blue music 2
try blue music 2 software
you have to pay for it
but it works great for me
it has today plug in to switch BT on/off & divert to headphone
i have regular BT headphone not stereo but it looks like it should work as it uses WM bluetooth setting interface
PhoneAlarm also has a BT toggle feature that is on the today screen, and offers a lot more if you want profiles, etc.
Is there a BT toggle that can be assigned to a hard key (via a .lnk)? I would like to avoid looking at the screen and just hitting a button to turn it on.
phonealarm
any free app to try? incase it is not working ?
Hi all,
after I've spent hours and hours of trial&error trying to get my BA to have A2DP, here's what I've found out:
1. Problem
My BA (tried all WM5 & WM6 ROMs) has always had the skipping problem, but much worse than it is usually described. Usually people say it skips a bit every some seconds, but with mine it was like 1/3rd of a second music, 2/3rds no music and so on.
I eventually found out that with the BitPool setting set to 20, the skipping was down to "normal" level, at least one could identify the piece of music that was played. Anyway, you'll see that BitPool=20 is not exactly pushing sounds to your headset that the word "quality" can describe in any way.
2. WIDCOMM stack
Then I tried the WIDCOMM/BroadCom stack posted by helmi_c here. That one actually delivered great A2DP quality, but has a major problem: HeadSet/HandsFree just doesn't work. I've tried every patch out there, even flashed back to WM2003SE, but to no avail. I guess the people who developed the stack just never got around to capture the phone "start call"/"end call" events. Although there an option that the headset profile always stays connected. Here are the reg settings:
Code:
[HKEY_LOCAL_MACHINE\Software\WIDCOMM\Plugin\HandsFree]
Code:
"AudioSetupDll"
Here, I tried "MkSpk_PCM_Routing.dll", "HTC_PCM_Routing.dll" and "SD_PCM_Routing.dll", there wasn't any difference between them. Don't waste your time.
Code:
"AudioPreferences"
Pretty simple: 1 = Handle phone calls in the headset, 2 = Handle all audio in the headset. 3 = both. Can't remember that 2 ever worked as it should have.
Code:
"AudioHandling"
Now this is a bit more difficult.
I know that 16 means that the option "Handle all audio to the headset" is enabled and thus shown in the Advanced preferences for any (mono) headset.
Value 1 means the headset icon (which looks like old-fashioned headphones and appears in the top bar, not only in the phone app) is enabled. I can't remember now if that also meant that the connection between the PPC and the headset is kept in an idling state or if value 8 was good for that.
Anyway, if AudioPreferences is set so that the connection to the headset is always connected (constant, silent noise in the headset), then you can actually hear the phone calls in the headset and speak through it. But the audio still stays in the device too, which means both speaker and microphone of the PPC are active, too. Annoying, to say the least.
3. Solution with MS Stack
Eventually, I couldn't stand using a BT headset for music but then having to grab the Blue Angel by hand when a phone call came in, so I decided to go back to the MS stack. And then, after hours of searching and flashing (even copied files from other ROMs and cooked my own ROMs), a great fortune find came my way. I had set the btuart flags to 4 (just to see if it would make any difference) and then I found this MSDN article, which is only available in Japanese (could someone translate?), but it gave me enough information to add this value:
Code:
[HKEY_LOCAL_MACHINE\Software\Microsoft\Bluetooth\device]
"DefaultMtu"=dword:800
And alas, it worked! I got a fine stream of HQ A2DP to my headset! Now I'm down to "normal" skipping, which I yet have to fix (don't know if I ever will), but at least it's not as crappy "quality" as it has been.
Summary
If you have extreme skipping with A2DP, these settings might help:
Code:
[HKEY_LOCAL_MACHINE\Software\Microsoft\Bluetooth\device]
"DefaultMtu"=dword:800
[HKEY_LOCAL_MACHINE\Software\Microsoft\Bluetooth\Transports\BuiltIn\3]
"flags"=dword:4 (or 5)
Then reboot.
Now there is only one problem left (and I'm inclined to see it as a problem of the crappy no-name headset I've got): from time to time (sometimes after 10sec, sometimes after 10min) the headset suddenly plays white noise instead of the music. Whenever I push either the forward or backward button, the music continues normally (so I currently use TCPMP because it does not support AVRCP). Has anyone else had this problem? The noise is very disturbing, because it is much louder than the music (I can still change the volume of the noise with the volume control buttons). I'm not sure if it is the SBC codec of WM5/6, possible causes could be:
1. SBC codec messes up and is reinitialized upon the AVRCP message
2. SBC codec/A2DP/AVDTP sends a packet or encoding that is unsupported by my headset and the headset reinitializes when you push a button
3. headset somehow looses track of the BT encryption and cannot decode the music anymore (although I think I had disabled the encryption and it didn't go away)
Regards,
Stefan
WOW great job I will try it out I have the problem when listen to music howerver with the btIO V0.6 help me on that I just enable AudioGWCC before connect the BT headset it will send out the music ALMOST properly however it will stop less than a second every 10 sec (actually randomly) however still not acceptable for me it too often
I use Jabra BT320s with Xplode rom http://forum.xda-developers.com/showthread.php?t=342142
Now I was actually able to fix the most annoying "music turns into noise" problem using the file from http://forum.xda-developers.com/showpost.php?p=1104981&postcount=59
Great
@touchu: If you were using sentence delimiters (those funny dots and commas), maybe I would be able to understand your problem. Anyway, I don't know what you mean by btIO V0.6 and I don't know the AudioGWCC option you mentioned. I just use "Bluetooth Settings", tap&hold on my headset and choose "Set as Wireless Stereo". For skipping issues there are hundreds of other threads.
Stefan
seidler2547 said:
Hi all,
3. Solution with MS Stack
Eventually, I couldn't stand using a BT headset for music but then having to grab the Blue Angel by hand when a phone call came in, so I decided to go back to the MS stack. And then, after hours of searching and flashing (even copied files from other ROMs and cooked my own ROMs), a great fortune find came my way. I had set the btuart flags to 4 (just to see if it would make any difference) and then I found this MSDN article, which is only available in Japanese (could someone translate?), but it gave me enough information to add this value:
Code:
[HKEY_LOCAL_MACHINE\Software\Microsoft\Bluetooth\device]
"DefaultMtu"=dword:800
And alas, it worked! I got a fine stream of HQ A2DP to my headset! Now I'm down to "normal" skipping, which I yet have to fix (don't know if I ever will), but at least it's not as crappy "quality" as it has been.
Regards,
Stefan
Click to expand...
Click to collapse
Thank you so much for this fix. After much trial and error myself, this is all I needed to do to make my new Motorola S9 headset work with my BA. I experience zero skips as long as I stay within the limited range of the BA (within 1 meter if the BA is in front of me, 2 if it is behind me). Point of information, this headset is a behind the head style and my neck/head seems to decrease the range significantly.
seidler2547 said:
Hi all,
3. Solution with MS Stack
Eventually, I couldn't stand using a BT headset for music but then having to grab the Blue Angel by hand when a phone call came in, so I decided to go back to the MS stack. And then, after hours of searching and flashing (even copied files from other ROMs and cooked my own ROMs), a great fortune find came my way. I had set the btuart flags to 4 (just to see if it would make any difference) and then I found this MSDN article, which is only available in Japanese (could someone translate?), but it gave me enough information to add this value:
Regards,
Stefan
Click to expand...
Click to collapse
http://translate.google.com/transla...arch?q=KB831722&hl=en&rls=com.microsoft:en-us
Google translates it fairly well.
After almost 2 years (i think), my trusty Sony BT10CX bluetooth stereo headbuds have finally started to short out on one side, on the receiver side. I plan on cracking open the case and soldering the connection back, but first i needed a replacement so i wouldn't be without a headset any longer then necessary (nothing kills unnecessary conversation like having headphones on, whether you are playing something through them or not, people assume that you can't hear them....)
After browsing the war-torn aisle of headphones at my local fry's electronics store, my only real choices were the $130 sony bt15?? or the $99 JVC set that i walked out with (and a dualshock controller for the ps3 to make GTA4 a bit more feeling when slamming pedestrians in to walls). The Sony packaging had no mention of expected battery life expectancy, which made me wary. I did a quick google check (don't we all love 3G?) on the battery life, and it came back up to 6 hours of music playback. The selling poilnt of my original sony headset was the "up to 11 hours music playback." THe JVC has marked on the packaging 11hours use/ 100 hours standby, so i figure if i can get 8 hours of steady use, it' be on par with what i was accustomed to, but with a few more bells and whistles.
The JVC is roughly the same size as my old sony headset, but has full media player control/support (tested with pocket music 5.06 and windows media player, and has a2dp and avrcp), and voice command working via the call button. The onboard volume control is independant of the player or the phone itself, but that seems rather standard these days. Sound quality with the supplied headphones is awesome. The bass hits and the trebles are clear. I do like the fact that you can use any 3.5 headphones with it or use the double ended cable supplied to hook it into a aux port if needed.
Using the headset for a phone call works ok ("it sounds like you are on speakerphone"), but nothing to write home about (it does have the headset and handsfree profile).
The only con i see with this unit is it has it's own charging stand instead of a simple usb charger. I know that there are other setups out there had have this feature, but have read some issues about sound quality or volume, which this unit doesn't.
Sidenote -- pocketmusic is a resource hog. i remember it used to lag out my wizard. it runs fine on the kaiser, caveat if you feel the need to multitask(i have issues using it, activesync, and replying to a sms simultaniously).
just my 2 cents though.....
I have a Motorola S9 bluetooth headset which worked perfectly with my blackberry 8900. I'd have the phone in my pocket, go to the gym and listen to music, it would work great.
But on my Nexus one, ever since I got it in Febuary, any rom i've ever been on (enomther, cyanogen), the audio skips repeatedly if I don't keep the phone like half a foot away from the headset (which is impossible unless I strap the phone to my upper back or something). It will cut out for 1-10 seconds and then return for a second and then go out again, and then be steady for 20 seconds and then do it again, it's very random but VERY frequent..I've never been able to go a full minute without skipping.
I've also had to have my nexus one replaced at one point, and this was a problem on both models, so I don't think I just got 2 defective nexus ones in a row.
Also I have paired the S9 bluetooth with my PS3 and again with the blackberry and it works perfectly with both.
Is there any reason or does the nexus one just have a weak bluetooth reciever?
I'm using the Sony Ericsson MW600 bluetooth headset and I found that the bluetooth range is better than my laptop. Audio doesn't skip even if I am ~10 m way.
I have some Sony ones (the neckband BT ones, not sure of the model) and they only seem to skip if there is heavy EM interference, or if the battery is low and there is something in the way. This was the same with a Nokia E71 (which IMHO had the best radios on a handset I've used), so I think its a headset problem rather than a phone problem. But saying that, I primarly use this combo with the phone in the chest pocket of an ACU jacket, so it only has about 30cm to travel.
I use my Nexus with the S9, and it works great. I often leave the phone playing on my desk at work, while I got to the printer etc. No probs, until about 40 foot away...
Sent from my Nexus One using XDA App
Compared to my old iPhone i found it was a little weaker too.
I think you have a second defective unit. My first n1 had the same problem. Since the n1 share the wifi and bluetooth on the same chip, you should notice also some weakness in the wireless signal as well. At least that is what I found.
I would never get full bars on my wireless even standing next to the router. The bluetooth was worse, I couldn't keep my phone more than an arms length to get the bluetooth working.
I returned it and got a replacement
Hope this helps
Well I don't have problems with weak wifi signal. I can be pretty far from the wifi and get great signal. Also for voice calls the plantronics explorer Bluetooth headset I use works great. Its just the a2dp streaming on the s9 that are giving me problems.
Have you tried turning Wi-fi off while using the BT for streaming?
Blue tooth dropouts- sometimes fix
On my N1, both a Jawbone Icon and a Samsung headset will have fluctuating media sound frequently. The sound will vary in volume or skipping up to once a second, giving a very unpleasing experience. The distance to the phone can be one foot or 15 feet with the same results.
I finally correlated this to either turning on or connecting the headset after the media had begun playing, or coming back into range while the media was already playing.
I found that I could get clear sound by exiting the media, then restarting the media while the headset was already connected.
I have trouble also with going out of range, then returning into range, but the media connection not restoring, just the phone connection.
Solutions I found for this on the web were:
- set master=true in /system/etc/bluetooth/audio.conf (worked for me)
possibly also:
- turn off wifi
- carry bluetooth device and nexus on same side of your body
- use bluetooth only for media (not phone)
When I get in my car my phone connects to my stereo automatically and all and all the A2DP functions work great. Only thing is I normally keep my phone on vibrate, and multimedia sound off so I don't accidentally make noise in an inappropriate place. The problem with this split setting for sound in android is I can't just bind the two and either put my phone with audio on or off generally. Is there a way to turn off multimedia sound with I connect to my stereo and turn it back off when I disconnect? My old wm phones did this no problem.
thanks!
julienrl said:
When I get in my car my phone connects to my stereo automatically and all and all the A2DP functions work great. Only thing is I normally keep my phone on vibrate, and multimedia sound off so I don't accidentally make noise in an inappropriate place. The problem with this split setting for sound in android is I can't just bind the two and either put my phone with audio on or off generally. Is there a way to turn off multimedia sound with I connect to my stereo and turn it back off when I disconnect? My old wm phones did this no problem.
thanks!
Click to expand...
Click to collapse
Check the app "car dock settings"
axion68 said:
Check the app "car dock settings"
Click to expand...
Click to collapse
Perfect. Only problem is I use a generic phone holder and usb power supply... how does it know its docked?
*edit* solution might be found... the same people who make car dock settings have bluedock 3 which does the same using the bluetooth profile (similar to Advanced Audio Manager once combined with "car dock settings")
I also found Toggle Settings|Profiles Lite which might work... I will try them all and report in case anyone ever asks the same question and falls on this thread
**second edit, reporting on the apps**
Toggle Settings\Profiles Lite works great. It takes up about 1mb ram rather than 150k compared to car dock settings and another 100k for bluedock 3, but its a free all-in one package that is MUCH more powerful and versatile. With the lite version you get 3 "Rules", I used one to make my car settings based on connecting and disconnecting from my stereo.It allows me to change just about anything on connect\disconnect and lets me create two other rule sets I could want (and as many as I want if I pay for the full version). I strongly recommend this app to anyone and everyone who wants to have automated location\connection\event\time based actions. The only down side is it takes about 15 seconds for the bluetooth to register as being connected (so be patient), but I think this is part of android because wifi-related events are instant.