Submitting improvement suggestions to WM5 and HTC dev team - 8525, TyTN, MDA Vario II, JasJam General

I seem to have found good contacts in both the WM5 and HTC development teams, and get fast answers to questions well explained.
You guys are smarter, and sometimes outdo the capabilities or willingness of these dev teams to support us users (remember the A2DP patch for the Prophet).
But nevertheless I would like to compile a brief list list with serious bugs or improvement requests to both teams, and see what they suggest. The bugs you experienced might not happen to other users, so we should carefully think about what to request.
But I think we can all agree on the A2DP out of range non-automatic reconnection issue (only manual). Since the HFP (handsfree) profile re-connects on the Tytn, A2DP re-connection should be achievable also. Any other suggestions please?

Making bluetooth work with Seat, Audi, Parrot, etc, carkits !!!
It continues to connect and reconnect over and over again.
Very irritating.
See also postings in this forum and that of Parrot.

Related

Challenge for you.

Hi first thing I will say is this is not for XDA but for SPV E200. I am aware this is an XDA forum but after seeing some of the things you guys have been able to do with the XDA ROM/OS I thought I would ask if anyone in here could help with this problem due to the similarity of the devices and the fact that they are made by the same company, HTC.
I have posted this originally in a Modaco forum for Smarphones but noone is technically capable enough to help.
If you could read the link below and reply if you think you are up to the challenge of hacking the SPV to get rid of this extremely annoying "complete lack of bluetooth range in headset mode" problem.
http://smartphone.modaco.com/viewtopic.php?t=110234&sid=13ac8d9e1da40bc14a4bbff5aeb015e1
Starfury
Come on there must be someone out there?
Advice
Hi,
It is really hard to come up with something because I have no idea about your device
Try to contact your brand reseller and ask him for system updates, or check forums that are dedicated to your device for such updates. System updates can usually resolve such issues in 70% of cases
Try to minimize 3rd party software usage and check your devices again
Try Pocket Bluetooth Tools (both versions; check for url at xda-dev frontpage)
Try to change your coat/case/cover because it might have BT radio frequency reducing effect
The hardware is HTC, just like the XDA.
The reseller is Orange and they are bringing out the C500 to replace it as they have given up on the E200.
Orange have no intention on bringing out any more fixes for the unit.
All I need is for the power to be increased in the bluetooth transmitter when it is in headset mode.
Finding right upgrade
What I propose to you is to check different upgrades:
http://www.msmobiles.com/news.php/2210.html
http://web.orange.co.uk/yourphone/spv2/promo.html?id=SPVE200_ROMCodeUpgrade
http://www.mtekk.com.au/browse/page657.html
... all of them claim about BT functionality improvements
They all have better functionality as in they work with more headsets, but none of them increases the range.
I am on the latest Orange E200 UK release currently. I have scoured the web for a fix and found nothing, hence my last ditch attempt to see if someone can hacl the phone.
What about the rest E200 users
t12345uk said:
I am on the latest Orange E200 UK release currently. I have scoured the web for a fix and found nothing, hence my last ditch attempt to see if someone can hacl the phone.
Click to expand...
Click to collapse
And what about other e200 users? Do they have the same problem?
You don't need any hack. If you use your BT headset in BT discoverable mode, then BT radio works at a maximum transmission rate, if in usual BT on mode, then BT transmission is adjusted to the environment (bonded devices)

Will this be the answer to all our bluetooth problems ?

Surfing the web, I noticed that Widcomm just launched a new BT development kit for the PPC/Phone Edition (That's the one we have!).
You can find information here:
http://www.widcomm.com/Products/bluetooth_comm_software_btce.asp
This is what they got to say about it:
NEW!
BT-PPC/Phone Edition leverages current BTW-CE/PPC features and includes the following profiles (GAP, SDP, SPP, GOEP, OPP, FTP, SYNC, DUN, HSP, HFP & PAN).
Key features of this product:
Addition of WAN connectivity features
Implement cellular connectivity
Manage audio traffic routing to headset
Display radio signal strength (RSSI) on screen
Implement power management scheme (enable WAN connectivity while PPC is off/sleep)
Initial release OMAP platform
I am extremely interested to know if anyone knows where to find an installable app for our XDA's. The fact that they say that an initial release is only for the OMAP platform makes me optimistic, because I think this is part of the XDA architecture. Can someone confirm this?
Best regards,
Bastian
Correction
I've just found out that the XDA is based on OMAP (Texas Instruments), but that the XDA2 is based on XSCALE (Intel).
So, we may be out of luck..........................
Anyone??
I'm giving it another shot to put it on top of the list, because I'd be really interested to know this.
-Bastian
being that it's a development kit i would put in in hacking it forum since there are more developers who read it plus fewer people post there so your post will not be out of the main theadlist that fasten and forgotten
Thanks
Thanks for your tip. I'll put it there also.
Regards,
-Bastian
Bastian look this, is interesting (it is in spanish)
http://www.pcdemano.com/phpBB2/viewtopic.php?t=3982
Thanks
Yep, I knew that trick already, but obviously it would be more elegant if we all had one standard BT solution from Widcomm which works 100%. This is a ripped version from the IPAQ, and not something taylor made for the PPC-PE, which is what Widcomm just announced.
-Bastian

answering machine (without recording, I have read others)

Well from reading other threads I learned that an answering machine software is not possible due to lacking ability to record from the radio audio output (on most phones, possible on univ?).
Well then how about not recording, but automatic pickup and sending prerecorded audio? Would that be possible? Like in: someone calls my phone->software picks up and plays back prerecorded message to caller "I'm in a meeting, please call back at 5pm" ->software hangs up.
Possible or not? Who would be willing to write something like this?
I think there's the same issue - the phone audio path is seperated from the PDA audio path. Read Odeean's posts on TAPI and his frustrations. However, the http://teksoftco.com boys seem to have hinted that this may in fact be possible anyway.
It may be possible I suppose, by writing specific drivers, but I don't think any of us have ever tried I guess.
V
We'll keep you updated with what can be done altough the system is not built to support this kind of features. Firstly because in the US recording audio on phone conversation is ilegal so MSFT doesn't supports this and onestly i don't see HTC being able to offer this kind of support.
Also what Vijay outlined is correct... but we have a few more ideas that we are curently testing...as i said we'll post it if we succeded.
Cheers,
Raul
i believe that it is not a hardware limitation.
The sound from the gsm is not analogue. It passes through the OS somehow, otherwise how is the audio transmitted to the bt hfree?
I don't believe that the transmition of audio (from gsm) to the bt hfree is done only by hardware.
Please comment
andrew_sh is making a good point there. Maybe something can be done by "faking" bluetooth data input?
We have a working answering machine on Himalaya.
See last ROM from TofClock...
Good point made by Andrew. A new bluetooth headset driver or a fake one might do the trick. Cross your fingers guys.
The OS has evolved since Himalaya and HTC has restricted access to drivers by creating a locking mechanism and also the signing process is a hop to pass.
Guys, from my understanding and a poll I've run:
http://forum.xda-developers.com/viewtopic.php?t=40100&highlight=telephone+poll
it doesn't seem like many people have succeeded in recording calls, and those that have are generally using the Himalaya only. The gigabyte can, but it has custom hardware.
We've discussed spoofing the bluetooth audio path before by using a dummy driver and receiver, but mamaich has stated that the audio path for the bluetooth is in hardware only, and seperated from the interceptable paths in the OS.
Rain (for those who don't know, is one of the genii at http://teksoftco.com) - if you have any new ideas, may I ask you to PM me?
Odeean, Mamaich and I have had numerous discussions about this and I'd be interested to know how your research is going. I read that you guys have experience at low level audio driver work (great work on the speakerphone btw!), and I think that might be a good way to go. There is certainly some OS control of the audio path (speakerphone, mute, headset<>bluetooth etc), so I've thought about this way...
V

What's the problem with Hero based ROM's and BlueTooth?

Hello.
Before you tell me... I already searched the forum and I can see many posts about the problems with BlueTooth in the Hero based ROM's, but none of these posts I read (I could have missed some, of course) say what the problems are exactly, so I don't know if it can be a problem for me or not.
The only things that I need from BT are connection to the Parrot CK3000 handsfree on my car, and to send/receive files over BT. Ocassionally I will use the Magic as a 3G modem, but I can do it through USB if not working through BT.
Are these BT features affected by these BT problems on Hero based ROM's?
Thanks in advance.
Not sure if this applies to all hero roms but in the 'jacxheroskiv' rom the problem is a missing shared object (just a missing file in the filesystem)
http://forum.xda-developers.com/showpost.php?p=4479554&postcount=96
Hi There
At the moment Bluetooth is problematic on all hero roms for the sapphire or otherwise. Audio head sets (wireless headphones) seem to work ok but everything else doesn't. So unfortunately your car kit won't work. (I have the same one, it pairs but the audio is garbled) File sharing on the other hand is a problem for all the androids so far (There is an app on the market that provides the functionality but it's not as elegant as it could be) so don't expect that to work on hero roms. I haven't tried Bluetooth tethering because WiFi tether works so well. Perhaps someone else could comment.
Now for the difficult part...
So far as I can tell a willing developer, correct me if I'm wrong, could make the Bluetooth work if the source code for the hero was made available (should be available in a few months if the recent release of the sapphires source code is anything to go by) There seem to be quite a number of people who need this functionality so I'm sure one of the rom cookers will get to it but unfortunately there is no way to know exactly when. For this reason I've decided to stick to the ion roms for now. In any event, Touchflo/Sense UI will be made officially available for the magics in due course...for a price of course
On another note any support financial or otherwise is greatly appreciated by the developers so if you want to encourage a particular functionality a few bucks and a friendly message will go a long way. Please remember though that the developers do this kind of thing for the love of it and provide no explicit support for their roms. Any and all risk is taken upon yourself but in most cases caveats will have been picked up by someone before hand.
Sorry if I've mentioned some things you already knew but I thought to add some info applicable to other newcomers.
Enjoy hacking!!
Thanks both.
I guess I'll have to use a non-Hero ROM then. As for the BT file transfer, I've seen at least one Cupcake ROM with it enabled and available as an option in the BT menu. I don't know what ROM it was though, I think I saw it in a Youtube video.
P.S.: I noticed that this thread was moved to "Sapphire general", sorry for put it in "development", I did it for it was related to Hero ROM's. Thanks mods for move it.
A2DP works for my Sony Ericsson HBH-DS205 - music streams flawlessly.
However, the call feature does not work - is this another common bluetooth problem with the HEROs?

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