Hu Guys,
I have an HTC TyTN and I cannot get the A2DP to work properly with with Jabra BT620s headset.
My ROM versions and other details are listed below in the sig.
If all others who are having problems with A2DP on their Hermes device please post below with their ROM details. I will then pass the info onto HTC when I speak with them.
Hey Syphon
I have been tracking this problem all over the intenret
Its the major deciding factor for me in purchasing this device
Its not just your device. Other people are reporting similar problems. Connection problems, bad quality, jumpy sound
I noticed in another forum you said you where in contact with HTC over this
If the HTC uses the BT A2DP stack from Microsoft then we are f#!ked then i dont think there is much HTC will do about it
Anyway Please be sure to keep us informed on how that goes
cam05 said:
Hey Syphon
I have been tracking this problem all over the intenret
Its the major deciding factor for me in purchasing this device
Its not just your device. Other people are reporting similar problems. Connection problems, bad quality, jumpy sound
I noticed in another forum you said you where in contact with HTC over this
If the HTC uses the BT A2DP stack from Microsoft then we are f#!ked then i dont think there is much HTC will do about it
Anyway Please be sure to keep us informed on how that goes
Click to expand...
Click to collapse
Well, this is my worry too. The WIDCOM (?) stack is supposedly MUCH better and MS have apparently really dropped the ball with theirs. The question is why would HTC switch? If you have a perfectly good stack already where is the need to switch? From what I understand the new MS one doesnt do anything that the WIDCOM one doesnt nor does it do anything better!!
do you know which implementation is in the Hermes?
cam05 said:
do you know which implementation is in the Hermes?
Click to expand...
Click to collapse
I thought it was the WIDCOM version, but it seems I may well be wrong.
I hope it is! Then atleast HTC might do something about it
If its the MS stack they'll just push it over to MS and say we have to wait for them like o2
Have you heard anything back from HTC Support yet?
not as yet.
confirmed the Hermes has the highly incapable Microsoft BT A2DP stack HTC you f'ing idiots
Complete f'ing idiots
I am going to put a jihad on HTC bunch of f'ing idiots
Why NOW? What possible reason would they have to revert to the MICROSOFT STACK ?
cam05 said:
confirmed the Hermes has the highly incapable Microsoft BT A2DP stack HTC you f'ing idiots
Complete f'ing idiots
I am to put a jihad on HTC bunch of f'ing idiots
Why NOW? What possible reason would they have to revert to the MICROSOFT STACK ?
Click to expand...
Click to collapse
How did you find this out? If it's true then I guess we are stuffed, unless MS and HTC sort their act out and fix this.
I reported this issue a week ago: please check my findings.
http://forum.xda-developers.com/viewtopic.php?t=57504&start=0&postdays=0&postorder=asc&highlight=
just read your thread. I see someone said their pantronics works fine...I also heard somewhere else that the tytn is kind of picky about what it works with. I may order up a plantronics to see if I can get it to work as mt bt620s is just not working at the moment.
i used to have an O2 XDA Atom before... A2DP sucked big time on it... crackling noise.. skipping... what not :lol:
now i'm using Dopod 838 Pro (HTC Hermes for south asia) and it works nicely for me... no skipping...(unless ur bt headset is low on battery) and no freaking crackling noise runs smooth. so far so good. i just pray that it doesnt go bad.
i'm using the i-Tech S38 Clip Stereo Headset (A2DP).
my rom, radio etc details found in my signature.
Is it me or does it seem the HERM100 models have newer ROMs on them?
Or are the variances due to the vendors applying their customisations etc?
I dont know but thats an interesting question!
I also encounter such problem. However, when I compare with my QTEK 9100 (AKU2.3 ROM), I found one of registry may cause the problem which shown as below:
HKEY_LOCAL_MACHINE/SOFTWARE/Microsoft/Bluetooth/A2DP/Settings/UseJointStereo (Dword:1)
QTEK 9100 (AKU 2.3 ROM) don't have this registry but TyTH have. Now I know how to fix it:
Method 1:
Simple deleted it.
Method 2:
Change the Value to 0
Also you can add a new registry to improve the quality:
HKLM\Software\Microsoft\Bluetooth\A2DP\Settings
Add : BitPool [Dword : 48] Maximum is 58
After the above mentioned change, bluetooth music work fine.
Hope it can help.
sas90850 said:
I also encounter such problem. However, when I compare with my QTEK 9100 (AKU2.3 ROM), I found one of registry may cause the problem which shown as below:
HKEY_LOCAL_MACHINE/SOFTWARE/Microsoft/Bluetooth/A2DP/Settings/UseJointStereo (Dword:1)
QTEK 9100 (AKU 2.3 ROM) don't have this registry but TyTH have. Now I know how to fix it:
Method 1:
Simple deleted it.
Method 2:
Change the Value to 0
Also you can add a new registry to improve the quality:
HKLM\Software\Microsoft\Bluetooth\A2DP\Settings
Add : BitPool [Dword : 48] Maximum is 58
After the above mentioned change, bluetooth music work fine.
Hope it can help.
Click to expand...
Click to collapse
Interesting, I do not have my headset with me at the moment but after work and the gym I will give this a go. You are a good man for posting that info
I will let you know how I get on with it. Cheers dude.
@sas90850:
hmmm... the UseJointStereo value has been linked to monophonic vs. true stereo output to bt stereo headsets on some HTC devices. However, on others (like my 8125) this key is ignored.
Do you still get true stereo when this value is set to zero?
The BitPool value is absolutely one to play with when addressing this issue on the TyTn though. I was able to crank up my 8125 to the point where extreme breakup occured.
Sleuth255 said:
@sas90850:
hmmm... the UseJointStereo value has been linked to monophonic vs. true stereo output to bt stereo headsets on some HTC devices. However, on others (like my 8125) this key is ignored.
Do you still get true stereo when this value is set to zero?
The BitPool value is absolutely one to play with when addressing this issue on the TyTn though. I was able to crank up my 8125 to the point where extreme breakup occured.
Click to expand...
Click to collapse
Yes. True Stereo Output. The quality is same as QTEK 9100. Please note that TyTH also use AKU 2.3 ROM.
after a major set back with Hermes this morning.... used the A2DP for almost an hour plus this evening.
this morning, since last nite, my dopod 838 pro (hermes) starting behaving weirdly. freeze every now and then.. none of the plugins or other software, not able to install/function properly. and finally, this morning on the way to work, was listening mp3 on A2DP and while i was in transit from one train to another... hermes automatically went on a soft reset. once it came back to life, i found that i'm not able to access my mp3 library on the microSD using WMP10. was able to access the microSD thru the file explorer though.
no clue what so ever even to the dopod customer support and service personnel. all they did is do soft-reset, do u hav enuff free memory, do hard-reset (the usual stupid SOP).
i gave up on taking help from dopod people and tried investigating on my own.... found that the microSD's FAT is having some probz. some lost file chains. did a format.. and vola... WMP10 able to read the mp3 on the microSD like a charm!. and from the past 3 hours the device very much alive and kicking without weird behaviour.
no clue.. on why the microSD got screwed up like that. :lol:
oopz.. sorri.. my posting went off the topic... a bit.... hmm quite a lot actually :lol: :lol:
@sas90850
Ok we are getting somewhere...The "UseJointStereo" setting has partially fixed it. I have listened to a few songs without any major glitching. Just a skip or two, but nowhere near the scale I was seeing before. I am going to see how it goes. If there are any more problems I will try out the BitPool setting.
You sir are a good man! This has definitely made things a lot better.
Related
I am sending back my Jabra BT800 because it has a 9 second delay before it answers the phone! :evil:
I also can not get the caller ID to work. :evil:
I have the Asia WME2003 SE from here.
What BT head set, that has a caller ID screen that works with the XDAII, is best in your opinion?
Bump
Anyone?
Same is here
Akono series from Sony Ericsson do the trick. However they handle the id in erratic ways, sometime the number is shown, sometimes the name, sometimes nothing. Looks like they also behave different when the number is in the SIM card of the phone.
:?:
THANK YOU
Thank you, thank you, THANK YOU.
Are you sure???
Looking Glass:
Which Akono headset have you tried? The one available to me is the HBH-660, but before I plop down a lot of money, I wanted to be sure you got it working with the iMATE PPC (XDA II).
I had tried the Jabra BT800, and although it worked fine as a "basic" bluetooth headset, like everyone else, I could not get the caller ID function to work. I will admit that it had MUCH LESS static/crackle than my Jabra BT200.
So let me know which Akono you have tried, and confirm that you got it to work with the XDA II (not IIs, JAM, Mini, III, etc... just the "old" XDA II/iMATE Pocket PC).
Thanks!
-Kevin.
I will reconfirm in a few days.
I too experienced the same with the BT800. Great quality sound but the Caller ID will not work and it can take up to 9 seconds to answer a phone after I pushed the button.
I just bought the hbh-200 for $60 http://cgi.ebay.com/ws/eBayISAPI.dll?ViewItem&category=20347&item=5756190707&rd=1
I will reconfirm this in a day or two.
They have a new HBH-662 that will have a power display and display how long the phone call was as well as caller ID like the HBH-660. Talk time is the same.
I went with the HBH-200 because I could just look at the part that is clipped to my shirt to see who is calling and leave the ear piece in. I am hoping I can make calls based upon the caller ID list as well. I am still worried I will break the wire though.
Dewild,
Please keep us updated on your results. If the model you have receives Caller ID on an XDA II/Imate PPC, I would assume the HBH-660 would work also.
Anxiously awaiting your test results...
Thx.
-Kevin.
Dewild1,
Forgot to ask in my previous post...
Are you currently running Pocket Bluetooth Tools, if so, what version 1100 or 1012?
Thanks.
-Kevin.
BT HS
I actually canceled that order... I did more research and it seems that 2.02 and 2.06, even Sin's version, does not support BT hands free.. Hands free mode is needed for the caller ID functions and other functions.
Yes, Sin's ROM does have a sort of hands free but in my opinion, there is NO BT head sets or any other device that is truly hands free that works with 2.02 or 2.06 or any mix or anything else.
Now the problem with that is,,, only the speaker works on the BT head set or any other device.. (I have only tested it on Jabra BT800 and ANYCOM HS-880, and I have read of others having the same experience)
NO Mic on the BT device. The Mic and phone on the XDAII are still going at the same time as well and if you keep your XDAII tucked away or in a pouch, you could here them but they can not hear you.. Or you could put the XDAII in front of you and talk into it and have your BT head set on.... Then you would be looking REAL COOL! :shock: :lol: 8)
Benefits of Sin's reg addition for Hands free are, the caller ID DOES work and when I push the button on the BT800, it answers almost instantly.. Not with the 9 sec delay while in HeadSet mode.
When you add the reg Key under, Hkey_localmachine, Software, Microsoft, Bluetooth and, (if your using Resco), highlight Bluetooth, Click on it and add just a plain Key of exactly "HandsfreeProfileOn", it is the same as adding Sin's hands free cab.
Now I would love to here from someone who has a BT SD card and see how it works.. I am tempted to buy a backpack to make this work and use a CF BT card if it works.. (There is no BT-Mem card combo,,, only WiFi-Mem combo cards that I know of)
I STRONGLY think this is a hardware driver issue!!!
Use 2.20.. IT WORKS
2.20 did the trick.. Seems ok..
No SD problems or other BS I read about
Hi Dewild1,
Excuse my ignorance, but I lost you on your last post regarding Sin's ROM, etc... what is SIN's rom? I did a global search and couldn't find anything on that. Am I missing something?
Thanks.
-Kevin.
Ignore previous post ... if you're referring to Sin's Wm2003SE merge. For my purposes, that's too much work and risk just to get caller ID on the headset. <sigh>.
-Kevin.
ROM
The only way to get caller ID to work and get Hands Free profile to work was to go to ROM version 2.20 of the translated to English from Chinese..
It seems stable, I have no SD card problems and the speed is good.
http://forum.xda-developers.com/viewtopic.php?t=13714&start=0
I used the extended ROM from the Dr.s
http://forum.xda-developers.com/viewtopic.php?t=16880&start=0
You can use http://spritesoftware.crmdesk.com/answer.aspx?id=63&back=browse.aspx#p17 to simplify the upgrade process. Make sure you have nothing paired in the BT manager first.
The God, mamaich, said that I should stay with 2.06 for it is more stable but I already updated to 2.20 and all is well... I hope it stays that way. :shock: :roll:
I just wish these DAM manufacturers and fricken resellers like HTC and O fricken 2 would support their dam products.. It should not be so [email protected]^@^ing difficult to get features that most FREE or almost free, cheap little phones have.. I mean we have the most complex, "advanced", powerful phone in the world right? But the free phones with BT that they give you with a one year contract, actually WORK, have BT voice dial, HAVE NO BUGS OR PROBLEMS! That is just not right. We pay a lot of money for a phone that needs to be hacked to make it work right...
It takes us, a combined group of people, to try and make the dam phones work right.. It is their job and they suck!
With that said, I would like to spend some time to say;
FU#* YOU O2, IPAC, and all the rest....
And a DOUBLE F#$K YOU TO HTC, Broadcom-Widcomm and Microsoft!!!!
I have spent a lot of time making things work right. If they would support their products, I could of spent my time on other things... They raped me!
Just arrived from USA a used phone Deutch T-mobile SDA with Windows 2003, unlocked with multilanguage support. Unlucky is without Wifi... Can I add it?
With ad upgrade to WM5 I will fix ?
thanks
no. and never ask stupid questions. if there is no wi-fi radio chip, you`ll never make it work by flashing any new rom. even if it was wm325.32525.3252 of the year 242325)
T-Mobile SDA with WM2003 is not HTC Tornado. And it really does not have wifi.
sp3dev said:
no. and never ask stupid questions. if there is no wi-fi radio chip, you`ll never make it work by flashing any new rom. even if it was wm325.32525.3252 of the year 242325)
Click to expand...
Click to collapse
This doesn't seem like a stupid question if you take the time to think about it. My recall of the wiki says that the SDA is the Tornado, so it should have wifi.
If a person didn't know better and was sure they had a Tornado they might think it was crippled do to lack of software/drivers. So they would ask.
So we look at
[email protected] said:
T-Mobile SDA with WM2003 is not HTC Tornado. And it really does not have wifi.
Click to expand...
Click to collapse
So my guess is that he's probably got an Amadeus. If you can't be helpful, you should just be quiet or go attend some remedial social skills class or something.
Crazynfunny:
Does your phone have a hump for an antenna on the top? Or is it smooth?
The T-Mobile SDA/Tornado pics I have seen usually show the hump. The HTC Amadeus doesn't seem to have a hump and looks exactly like the Qtek 8300 (also a Tornado)?
I guess the only real way to be sure what you've got is to look at the bootloader.
If it does indeed say it is a Tornado, look for a newer ROM that includes radio and everything, because it should have wifi. If it doesn't, it's not Tornado.
Trust me he has a Hurricane. I have the same and i found out the hard way.
Bricked e few SDA's until i figured out that it was a hurricane.
Yes i know i should have read better everywhere and i should have been more patient. ;-)
Exitao said:
This doesn't seem like a stupid question if you take the time to think about it. My recall of the wiki says that the SDA is the Tornado, so it should have wifi.
If a person didn't know better and was sure they had a Tornado they might think it was crippled do to lack of software/drivers. So they would ask.
So we look at
So my guess is that he's probably got an Amadeus. If you can't be helpful, you should just be quiet or go attend some remedial social skills class or something.
Crazynfunny:
Does your phone have a hump for an antenna on the top? Or is it smooth?
The T-Mobile SDA/Tornado pics I have seen usually show the hump. The HTC Amadeus doesn't seem to have a hump and looks exactly like the Qtek 8300 (also a Tornado)?
I guess the only real way to be sure what you've got is to look at the bootloader.
If it does indeed say it is a Tornado, look for a newer ROM that includes radio and everything, because it should have wifi. If it doesn't, it's not Tornado.
Click to expand...
Click to collapse
I have been having a lot of distortion problem with my Vox. So help me out. Currently I am using 4.1.13.60_03.18.90.
Kindly vote and tell your experience with different versions.
I never had any problems with 03.10.90! But then again my state is fairly good covered (Saxony). I think only like 2% of the area is not covered with GSM (and lately more and more with EDGE too)!
I plan on giving a thorough test of all the later versions once I re-assemble my mobile. I also noticed high distortion on 4.1.13.60_03.18.90 immediately after flashing. I am led to believe this was a small reason my ear piece failed, the distortion and higher volume 'popped' in and it would no longer function properly, heck, it could also have been since it was quite old too.
Anyways, for good measure I will be reverting to 4.1.13.47_02.98.90, I never had issues with the radio shipped from the factory and coverage was no problem. I suggest you downgrade before any hardware has a chance at being ruined.
h4waii is true. I have installed several radios and I have found 4.1.13.47_02.98.90 the best especialy for areas with weak signals.
h4waii said:
Anyways, for good measure I will be reverting to 4.1.13.47_02.98.90, I never had issues with the radio shipped from the factory and coverage was no problem. I suggest you downgrade before any hardware has a chance at being ruined.
Click to expand...
Click to collapse
I read your thread that you are reassembling your phone. I hope you will put a video guide for others too. That will be very useful.
I was reading through forum and I came across a post in which he had said that he pulled out the battery and put it after a few hours and things were back to normal. Well I tried it and I dont know what is the logic but it worked. Still echos on high volume but other reception distortion is gone.
Can radio damage your phone? Mine was shipped with v4.1.13.54_03.10.90.
@frauhottelmann
You have cooked a lite rom and it is not with latest XIP. Why you and Gonzo are not updating their Roms. Lefab also not working on WM6.1 Rom. Only one working is Hikey, and he does not have a thread here. I requested him in post but he refused by saying their are already too many roms here. Is it possible to hope that one of you will bring a clean Rom with latest XIP. New XIP is much faster.
i use v4.1.13.60_03.18.90
I have never noticed this distortion you mention
I can tel you why I never did continue cooking. There are three reasons:
1) I simply got tired. It is in fact a quite annyoing process. Espacially working on a 96dpi ROM, everytime you fixed something another problem turns up.
2) I experimented with OSs on my computer (from XP to Vista to Server 2008 to Vista and in the end of the week back to XP - the switching back is due to hardware problems) lol And cooking under anything else then XP is not quite safe and I experienced more problems under Vista!
3) Nobody ever requested a new updated Lite ROM (at least until now ^^) because people usually just download the stuff and don't report back unless there is a problem (you get sick of that too!)
Hey I will have time next week, so I will probably make Lite 3.0 with new XIP...the problem is that I don't have the Sys and OEM folders anymore, so I will have to start from scratch...
frauhottelmann said:
I can tel you why I never did continue cooking. There are three reasons:
1) I simply got tired. It is in fact a quite annyoing process. Espacially working on a 96dpi ROM, everytime you fixed something another problem turns up.
2) I experimented with OSs on my computer (from XP to Vista to Server 2008 to Vista and in the end of the week back to XP - the switching back is due to hardware problems) lol And cooking under anything else then XP is not quite safe and I experienced more problems under Vista!
3) Nobody ever requested a new updated Lite ROM (at least until now ^^) because people usually just download the stuff and don't report back unless there is a problem (you get sick of that too!)
Hey I will have time next week, so I will probably make Lite 3.0 with new XIP...the problem is that I don't have the Sys and OEM folders anymore, so I will have to start from scratch...
Click to expand...
Click to collapse
Hmmm you are quite right about the feedback thing. If you work hard on something it no one appreciates it obviously it hurts.
Well atleast I will wait for your new rom. I hope you do something about java. Add jebed or provide link to cab for you new rom.
I did tried your rom, I would have kept it but new XIP is much faster so I had to switch.
@tipu2185;
While a radio in itself can't really damage your hardware, issues caused by it can. Such as high distortion and crackling, this can ruin a speaker. With the right software, hardware can be destroyed.
I've already re-assembled the Vox after replacing both the vibrate motor and the inner ear piece. It's fairly straight forward. I didn't bother to take any pictures as there is a service manual which indicates step-by-step how to do this.
h4waii said:
@tipu2185;
While a radio in itself can't really damage your hardware, issues caused by it can. Such as high distortion and crackling, this can ruin a speaker. With the right software, hardware can be destroyed.
I've already re-assembled the Vox after replacing both the vibrate motor and the inner ear piece. It's fairly straight forward. I didn't bother to take any pictures as there is a service manual which indicates step-by-step how to do this.
Click to expand...
Click to collapse
Can you link to that service manual. I might need it later some time.
Tipu2185,
How are you finding this radio version so far? Have yor initial problems gone?
2frustrated said:
Tipu2185,
How are you finding this radio version so far? Have yor initial problems gone?
Click to expand...
Click to collapse
Yes it is working fine now
Where?
I want to installl Radio v4.1.13.60_03.18.90, but I can't find it anywhere. Anyone care to provide a download link?
Thanks!
DUTCH said:
I want to installl Radio v4.1.13.60_03.18.90, but I can't find it anywhere. Anyone care to provide a download link?
Thanks!
Click to expand...
Click to collapse
check the wiki in first two sticky threads. It is there
tipu2185 said:
check the wiki in first two sticky threads. It is there
Click to expand...
Click to collapse
I searched for 20min and finally found it! http://forum.xda-developers.com/showthread.php?t=402778
Thanks!
So, XDA guys, when is a grouping for the new Palm Treo Pro gonna be setup?
WOW, i think this will be the KING OF DEVICES for now !
Some pictures: http://www.engadgetmobile.com/2008/08/20/palm-treo-pro-unboxing-and-hands-on/
Ik hope the XDA developers will find a working CAB-file for voip calling over wifi AND 3G, and by using the internal speaker.
The Treo Pro is manufactured by HTC, by the way. So i hope this will help.
if i were you i'd ask it in this forum
About xda-developers.com
Anything to do more with the site than with the phones. Feature requests, announcements, praise, moaning, etc.
Yep, it's going to be made by HTC. This device will ROCK!
http://www.tgdaily.com/content/view/39009/149/
Palm Treo Pro Forum
As it is produced by HTC, maybe the first step is to get a forum for it on XDA Developers ?
See the unboxing video: http://mobilitytoday.com/articles/palm_treo_pro_unboxed.html
This is the next God device.
Palm have the design right but in the past years they just seemed to pop out the same devices over and over. I'm glad to see Wi-Fi, GPS and power at last.
You can tap yourself in the back this time, you really deserve it!
http://blogs.zdnet.com/mobile-gadgeteer/?p=1387
"It looks like HTC made the Palm Treo Pro. I think this is great news for the Treo Pro buyer because HTC is a proven player in the touch screen Windows Mobile market. Another thing is that the excellent resources at XDA Developers may be able to support customizations of the device for those who like to tweak things."
up
and one more for the palm treo pro forum
O.K. I had the possibility to make a test with this device !
I can confirm: this is really the KING DEVICE for now ! It has a really perfect size in your hands. Less PDA and more smartphone (but with all PDA functionalities)
But bad news too: As it is produced by HTC voip calling has the HTC/Fring bug: it uses the speaker on the back and not the earspeaker which should be
Voip calling over 3G didn't work too: you can dial a number, you can pick up the other line and there is a connection, but the line is DEAD, no sound both connections
For testing I used this files: http://voipguides.blogspot.com/2008/05/voip-sip-client-for-windows-mobile-6.html
Has anyone else Pre-ordered they Treo Pro? I just ordered mine this week and can't wait for shipping. I have heard over on Treocentral that someone has already received the device. I am hoping that America side starts shipping next week!!
I have my Treo Pro for a few days now, I really hope there will be an XDA forum for the Treo Pro (850).
Meanwhile, I've started a new website with tips and tricks: http://www.treoprotricks.com
oVan said:
I have my Treo Pro for a few days now, I really hope there will be an XDA forum for the Treo Pro (850).
Meanwhile, I've started a new website with tips and tricks: http://www.treoprotricks.com
Click to expand...
Click to collapse
Another vote for a Treo Pro forum.
Mine shipped overnight on UPS to Chicago - just got tracking number!
i bought my treo pro yesterday and im pretty happy with it
there were several things i would have made in a different way like a mini-usb connector instead of an micro-usb one but at least its some standarized connector
still mini usb would be more practical
a seperate forum for the treo would be nice
right now i am fighting with the installations of my progs
most of the times an current version of software will solve problems with the 320*320 screen
one kind of program i am still looking for is a replacement for novii remote
i was hoping to be able to use the infrared port as a rc...
I just got mine a couple of hours ago, am enjoying playing with it. I too hope they start and Treo Pro forum...will be helpful.
als long as there is no new forum for this phone i will keep posting interesting stuff i find out about my treo pro here
one very annozing thing i found out was:
- while listening to music with the screen off i heard short interruptions which after i checked it occured exactly every minute
- to "fix" this you have to disable the screen saver (the clock and date display on the deactivated screen) in settings>system>power options (might be called slightly different but sorry i only have a german device)
this is a pity that you have to do this in order to listen to music without problems
but it annoyed me after a while that much that i finally can live with that
I have really enjoyed playing this this new toy this weekend (the heck with the homework!)
Anyway, a couple of things and maybe one of you can help me out. I so wanted to use UL but when I installed I can't see all of the configuration pages and there are no scroll bars for me to scroll down to finish the configuration. Very Frustrating.
Also I tried the RealVGA cab and it messed up my today screen really bad, plus it made everything so tiny I couldn't read it with out my reading glasses, not good for me. So that didn't work.
Also there is a huge lack of themes for the Treo, I never realized the huge difference between this and a regular 240x 320 screen.
Anyway for right now I am using Home++ Floyd Base Theme, and using SecondToday to run my WeatherPanel and FaceContacts.
So far I am liking this new toy...I am getting use to the keyboard but I will get there and I love the screen! I was actually outside today in the sun and could see it and read my emails!
MDANavymom said:
...(the heck with the homework!)...
Click to expand...
Click to collapse
^^exactly my thoughts too today
i also must admit that its a bit frustrating to see how many programs have problems with 320*320...
the good thing is that everything i need is available in a version which runs smoothly most of the times(except tomeraider3 which has graphic bugs and the search only works with the softwarekeyboard -.-)
i als might add that the audio skip problem occured to me while using mortplayer as my mp3 player app...
so far im still playing around with this little fella
what caught my attention was that the treo pro uses around 60mA of current while in my typical ebook reader setup(backlight dimmed to the max but stiil on)
this could mean a decent battery runtime but its hard to say after just 3 days
the first impression is rather positive though
ZonKnoZ said:
^^exactly my thoughts too today
i also must admit that its a bit frustrating to see how many programs have problems with 320*320...
the good thing is that everything i need is available in a version which runs smoothly most of the times(except tomeraider3 which has graphic bugs and the search only works with the softwarekeyboard -.-)
i als might add that the audio skip problem occured to me while using mortplayer as my mp3 player app...
so far im still playing around with this little fella
what caught my attention was that the treo pro uses around 60mA of current while in my typical ebook reader setup(backlight dimmed to the max but stiil on)
this could mean a decent battery runtime but its hard to say after just 3 days
the first impression is rather positive though
Click to expand...
Click to collapse
Hummm will have to check out the audio players...I hate to say it but I just don't use that or video players I do like You Tube, but for music and videos I have my Zune.
I am having a problem getting my skyfire reinstalled...am still trying to get the kinks out of that one, and I have sent a request to someone to try and get a couple of themes made for this here new toy...since I am completely helpless with anything graphic. I have some new Dexter wallpapers and want themes made out of them and I got some great Icons for it too..I NEED to get this UL issue resolved so I can get this thing looking good or as the kids would say "I need to pimp out my phone"
EDIT: Here are a couple of screen shots not done yet
GPS Working
So I fired up his baby this morning, to check out the GPS. I use to use an external bluetooth receiver with TomTom on my T-mobile Wing. Usually took at least 2 minutes to get a signal. I turn on the TomTom this morning used other GPS Com4 and it took under a minute to get a signal in my apartment!! Way cool! So now I need to find a reason to go driving and get some use out of this.
So I've made the leap from WM to Android with my shiney new HTC desire.
I've managed to pair and connect it to my Nokia CK-7W bluetooth car kit but the recipient complains of a terrible echo their end of their own voice. At my end it's fine.
I've tried adjusting the volume in the car with no effect. I'm guessing that their voice that's coming through my speakers is getting fed back into the microphone, causing the echo.
Anyone experienced anything similar or even better know of a solution??
It's worth noting that this was never a problem with my HTC Touch Diamond.
Thanks
Rob.
Sorry for not answering your question, but how did you manage to connect the desire to CK-7W, I've been trying but no joy .
Again help would be appreciated
It took a bit of fiddling and to be honest I can't remember exactly how I did it.
I definitely set it to discoverable, but it wouldn't find it at first. I believe I had to turn on or off FTP server in advanced settings.
To connect once paired you need to turn on BT on your HTC and press and hold the connect button on the ck-7w for at least a second.
If you get it working please test for echoing and report back
Cheers.
Rob.
same setup here, same echo..
Hi,
I have the same car kit, I have the same complaints. Terrible echo. It worked just fine with my previous phones (Kaiser lately).
Cheers,
A.
When I get chance I'll trawl the other android phone threads to see if anyone has come up with a solution.
Cheers for the reply rob, I'll hopefully get it 'paired' tomorrow & feedback regarding echo.
Rich
Same issue here. I have upgraded from a HTC TYTN II WM6.1 to the HTC Desire. After connecting via bluetooth to the Nokia car kit all of my calls suffer from bad echo at the other end. To combat this i have turned the speaker volume down as low as i can hear it which seems to help the other party. (My bluetooth pairing setup perfectly the first time)
I also recall that my TYTN II had exactly the same issue and i had to download a patch from HTC which fixed the issue fully. Maybe the Desire needs a patch from HTC.
Has this issue been submitted to them for consideration?
This has been a bad problem since view first came out. It seems to be worse on the windows devices but it can and does affect even Nokia phones and still not an upgrade from Nokia.
I ended up having to get new parrots for our company cars as the drivers gradually upgraded their mobiles.
-------------------------------------
Sent from my HTC Desire
I found this thread over on the Xperia X1 forum with a solution they found to work
(See post #4)
http://forum.xda-developers.com/showthread.php?t=478612
I must admit I did this exact tweek a few years ago on my old M700 to get it to stream music via bluetooth to my a2dp enabled car stereo and it worked a treat.
Basically the M700 identified itself as a "smartphone" which the stereo didn't like. So I changed the "Class of Device" (COD) to identify itself as a normal mobile phone which instantly solved the problem.
I don't know if an Android has a registry or if it is editable but if it is identifying itself as a smartphone and it could be changed to a normal mobile phone then it just may get rid of the echo.
Perhaps there is another place on here that this question is better suited?
neomagik said:
I found this thread over on the Xperia X1 forum with a solution they found to work
(See post #4)
hxxp://forum.xda-developers.com/showthread.php?t=478612
Click to expand...
Click to collapse
For those guys changing the device class from smartphone to phone helped. I'm not familiar with Android internals but in /system/etc/bluez/main.conf there's a section:
# Default device class. Only the major and minor device class bits are
# considered.
# Local device class
# 0x400000 - Service class: Telephony
# 0x000200 - Major class: Phone
# 0x00000C - Minor class: Smart phone
Class = 0x40020C
Click to expand...
Click to collapse
Would that help to to change it? I haven't rooted my desire (yet?). Would someone having the same problem and having a rooted device try changing the device class?
Hey aszeman,
What application did you use view the contents of that file? I can browse to it but can't open it.
If rooting is what it takes to change the value, I'll give it a try.
neomagik said:
Hey aszeman,
What application did you use view the contents of that file? I can browse to it but can't open it.
If rooting is what it takes to change the value, I'll give it a try.
Click to expand...
Click to collapse
I did not check it on the phone as I could not read the file, but I used a downloadable stock rom.
I run the RUU updater, checked with "filemon" where it temporarily extract content. From rom.zip I extracted system.img. From that with unyaffs I extracted the system content. Browsed that around, and found the bluez setting there. I'm still hesitating about the rooting as there I see some issues floating around bricking USB/BT/FM. If someone has already done the rooting he/she could give it a try to change CoD.
You're obviously more 'in the know' than I am about these things.
Am I right in saying that if my phone was rooted I could view and alter these files directly on the phone?
I'm guessing that there are not that many people who own an HTC Desire, CK-7W car kit and who have rooted their phone. I hope I'm proved wrong but if no-one comes forward soon we'll have to take the plunge.
neomagik said:
You're obviously more 'in the know' than I am about these things.
Am I right in saying that if my phone was rooted I could view and alter these files directly on the phone?
I'm guessing that there are not that many people who own an HTC Desire, CK-7W car kit and who have rooted their phone. I hope I'm proved wrong but if no-one comes forward soon we'll have to take the plunge.
Click to expand...
Click to collapse
This is my first Android phone. Zero experience. I'm just guessing and making assumptions, and I'd assume with root rights one can change that file.
So I've now rooted my phone and changed the Class = 0x40020C to Class = 0x000200 and guess what.....no change.
I also got in touch with some people in the HTC Hero forum who have a CK-7W and they confirmed that they have no echo.
I then requested if someone could post the contents of their bluez folder which is different to ours. I copied the files onto my device, rebooted and still no difference.
Then, just for a test, I deleted everything from the folder and rebooted. Again no difference but to be honest I was surprised that it still worked at all.
It must be using information from elsewhere but I'm damned if I know!
I have the same problem with the Nokia CK-7W carkit and an HTC Desire smartphone.
I've had the problem before with my Xperia X1 (like someone said earlier) but then the problem was fixable within the registry of the phone.
My HTC Magic is paired without any echos or other problems, but still the HTC Desire has an terrible echo for the other party.
The answer of HTC was "buy a newer carkit", but that is insane, the basics are the same and it is depending on the phone so...
Hello,
I have the same setup and guess what...the same problem. I've updated the SW today but still no change.
Good news, the DeFrost Froyo rom has completely eliminated the echo, at least for me anyway.
The problem still exists... And i don't want to root my phone and flash a new ROM on to it.
Me also !
neomagik said:
So I've made the leap from WM to Android with my shiney new HTC desire.
I've managed to pair and connect it to my Nokia CK-7W bluetooth car kit but the recipient complains of a terrible echo their end of their own voice. At my end it's fine.
I've tried adjusting the volume in the car with no effect. I'm guessing that their voice that's coming through my speakers is getting fed back into the microphone, causing the echo.
Anyone experienced anything similar or even better know of a solution??
It's worth noting that this was never a problem with my HTC Touch Diamond.
Thanks
Rob.
Click to expand...
Click to collapse
Incredible .. Ive also made the leap from WM tot Desire and have the same problem with my Nokia Carkit. !!
Can't find the solution anywhere !!
greeds Rob