Aim: To connect my HTC Touch to my laptop and to seamlessly use it as a headset for talking on Skype - i.e. use the cellphone microphone for input and the cellphone speaker for audio output.
Note: I know that there are bluetooth headset per se that may be paired with a PC, but I would like to know how to use my existing phone with this and understand whether this is technologically possible.
I am both interested in opportunities of bluetooth or wi-fi methods for connecting. In addition, you may supply info for software or hardware tools, but software fine tuning is preferred.
Thank you in advance for your assistance.
As far as I can clarify I want to use my mobile:
a) as a bluetooth connected headset
and
b) as a bluetooth connected microphone
Are those implemented in the bluetooth profiles which are running on my mobile phone? (or on any other phone).
In general it would be possible based on technology, hence there are bluetooth headsets with integrated microphones. But are the needed profile extensions on the bluetooth protocols implemented by the mobile phone vendors such as HTC?
In other words, is the protocol stack extended by the chip vendor of the bluetooth chip inside the HTC - probably not HTC itself? And is the protocol stack implemented into the operating system - Microsoft mobile 6.1 by either HTC or Microsoft?
i'd like this on my kaiser too..
just looking around still.
I to all,
i have found a Zypad wrist pc that have the following characteristics:
- Operating System Standard platform supports Windows CE 5.0 or Linux based on Kernel 2.6
- Display 3.5" TFT touch-screen with automatic contrast adjustment via ambient light sensor
- Wireless Bluetooth, Wi-Fi 802.11 b/g
- GPS Integrated GPS receiver and antenna
- Audio Stereo speaker and headphone jack for external headset to support multimedia applications
- Expandability Mini Secure Digital memory slot and USB ports (master & device)
- Accelerometer Tilt and Dead Reckoning System allows operators to determine whether or not the user is moving (GPS supplies the position)
- Keyboard Backlit buttons
Here the datasheet: View attachment 519821
The problem is that the touch screen is broken and I try to fnd a way to change or upgrade the ROM in order to use it in enother way.
So how can I cook a new ROM for it?
Thanks in advance .
No one can help me?
As I am a new user I can't post on specific thread so I post here my test
I installed Spirit PAK ver 01 07 and after turn on all device in my Nexus S I tried apk
Here some photos of test with stock ROM 2.3.4
It can be useful for developmetn ....
http :// imageshack.us/photo/my-images/27/dscf0009hc.jpg/
http :// imageshack.us/photo/my-images/18/dscf0011js.jpg/
http :// imageshack.us/photo/my-images/825/dscf0012su.jpg/
result : Signal are instable and no sound (
If can I help in some other way ....
The technical is in the next post.
Thanks for posting publicly. I prefer open discussion so that everyone can benefit and contribute.
I created my main thread in a forum dedicated to discussing apps, but didn't realise it was under a dev forum and thus users with less than 10 posts couldn't post. I wonder if I should create a 2nd thread...
You can't post full URLs either so here they are:
http://imageshack.us/photo/my-images/27/dscf0009hc.jpg/
http://imageshack.us/photo/my-images/18/dscf0011js.jpg/
http://imageshack.us/photo/my-images/825/dscf0012su.jpg/
BTW, screenshots are great !
The short answer is I don't think the Nexus S is capable of receiving or transmitting FM, but I would never say never without hard proof.
I've been asked a few times over the last several months, and if I recall correctly, every time I've Googled the issue I found no evidence that anyone has EVER made FM work on the Nexus S.
I think my app is probably the closest it will get. It WILL manipulate the FM registers over HCI and it will look like it works, to some extent. But no audio, not even static, will be heard.
And there will be no indications of reception, like a more or less steady RSSI reading on strong channels, and RDS data.
Samsung manufactured this phone, and it seems to be a derivative of the Galaxy S. The Galaxy S, like the Nexus S, has an FM/BT/WiFi combo chip from Broadcom. The stock Galaxy S supports FM, but via a dedicated Silicon Labs FM chip, which the Nexus S does not seem to have. (BTW, the FmTwoO app also works on Galaxy S.)
AFAICT it's not possible to use the Broadcom chip for FM on the Nexus S. The antenna and audio connections are to the Silicon Labs chip and not to the matching pins on the Broadcom chip. If the Nexus S PCB/circuitry is reasonably similar to the Galaxy S, then it probably won't work on the Nexus S either.
There are two Samsung devices that I've been trying to help owners get FM working on. that have a Broadcom chip, but no other chip. Thus far we've had no success with either the Galaxy Tab, or the Spica i5700. There are two problems:
(1) The RSSI signal strength shows strange values and may jump around. I think this is due to no antenna connection and/or some FM RF power pins may not be connected.
(2) No analog audio output has been achieved, not even static, despite trying the 8 or so Audio Methods my app currently supports, and ALSA as well.
(2) might be fixable if I ever achieve digital audio transfer or even direct audio to BT headsets within the chip.
But (1) might only be fixable with much investigation and soldering etc.
Sorry... I'd love to find out I'm wrong about this.
Other info for BCM4329 chip :
http :// www . datasheetdir.com/BCM4329+download
in these datasheet we can read
Code:
Host Interface support
- Host Controller Interface (HCI): High-speed UART
-Audio: PCM
- FM Control: HCI and BSC (I2C-compliant) ports
- FM Audio: Stereo analog input and output, bidirectional
I2S, and PCM ports
In schematic we can notice BT and wifi use same ant , FM has dedicated one ....
But SPI / I2C / I2s are the same of BT and WIFI so it's possible to comunicate with FM part in chip with no problem ....
Code:
FMHost Interface: High-speed UART, I2C for control
.....
if not mistaken spirit apk use only HCI .... not I2C !
magicko said:
Code:
FMHost Interface: High-speed UART, I2C for control
.....
if not mistaken spirit apk use only HCI .... not I2C !
Click to expand...
Click to collapse
All devices that uses the combo chip for Bluetooth support the HCI UART interface. That can be accessed via the BT stack or directly by reasonably standard and common methods.
I don't know what fraction of devices can use the other interface, but some don't. I believe the Galaxy Tab schematic showed a digital connection to the Wolfson audio chip...
The next issue would be accessing the interface, and I think that would require a device driver. If I wanted to support multiple devices and kernels by this method I'd have to create multiple device drivers.
So even if possible, I think the work required would be excessive.
But if somebody can figure this out, I'd be happy to hear about it.
EDIT: A digital audio connection MAY not be as hard as I envision, at least for some devices.
IF the ROM supports a digital / "SCO" connection to the chip, it might be possible to call an audio API to set this up.
I haven't worked with these SCO connections yet, so I don't know how easy or feasible it is, but I'll try to find out.
Hi mikereidis, I don't want flooding to be able write on developers section, as well be superfluous create a new topic on the DroidX tree so I would write here...
I tried the latest SpiritFM version on DroidX CM7. Several times I was able tune to the pre-programmed frequency and receive audio using FM_launch method. In most cases, I only get noise. To get the sound the speaker/headphones button should on and then off. Without such manipulation sound does not appear.
The big problem is that your program give low radio sensitivity. This is not a hardware problem because stock FM program allows 15 radiostations on the my area.
I also tried FM_launch2 but without success.
Here is the catlog with FM_launch, and then FM_launch2. I'm also ready to provide any logs or make any test if it helps you improve SpiritFM for Motorola phones.
evgenln said:
Hi mikereidis, I don't want flooding to be able write on developers section, as well be superfluous create a new topic on the DroidX tree so I would write here...
I tried the latest SpiritFM version on DroidX CM7. Several times I was able tune to the pre-programmed frequency and receive audio using FM_launch method. In most cases, I only get noise. To get the sound the speaker/headphones button should on and then off. Without such manipulation sound does not appear.
The big problem is that your program give low radio sensitivity. This is not a hardware problem because stock FM program allows 15 radiostations on the my area.
I also tried FM_launch2 but without success.
Here is the catlog with FM_launch, and then FM_launch2. I'm also ready to provide any logs or make any test if it helps you improve SpiritFM for Motorola phones.
Click to expand...
Click to collapse
Thanks for the log evgenln. I'll let you know what I find.
Some other people have enabled audio by toggling speaker/headset. It would be a hack, but perhaps I can create an option that toggles it automatically. But it would be better if I figure out what's happening, and fix it right.
Regarding signal strength: My guess would be that there is a function call required to enable the FM antenna, and that you are receiving without an antenna. I'll try to find out.
But since the headphone cable is the antenna, it's possible this is related to audio issues.
evgenln said:
I tried the latest SpiritFM version on DroidX CM7. Several times I was able tune to the pre-programmed frequency and receive audio using FM_launch method. In most cases, I only get noise.
Click to expand...
Click to collapse
It appears something has broken horribly for Texas Instruments FM chips. I can confirm the same errors you are having on my HTC Legend.
I can trigger the errors when I switch headset to speaker, and I'm not sure why yet.
Most phones have Broadcom chips, but I still don't understand why I haven't seen this problem before; it seems to go back at least a month.
Regardless, I've found a workaround that I hope will also work for you. If you deny SuperUser privileges to the app it will use hcitool instead of the daemon. It will consume more CPU/power when RDS is working and the screen is on though.
So, open the SuperUser app and select Spirit FM Radio and press Forget.
Then restart the app and when SuperUser asks for permission, select Deny and Remember.
Let me know, thanks !
I will determine the root cause and a fix.
Here's a preferable workaround for TI chip devices (and reason I wasn't seeing this issue).
This operation is useful for Broadcom based devices on CyanogenMod also because CM tries to use hcitool to set FM volume, so this can avoid some interference:
Remove or rename the hcitool binary. During audio switching, CyanogenMod (and likely some derivative ROMs) calls hcitool for some reason. This causes problems in the daemon mode.
The downside to this is that the CM FM app won't work.
I do this:
adb remount
adb shell mv /system/xbin/hcitool /system/xbin/hcitoo
My app can still use "hcitoo" if needed.
mikereidis said:
I do this:
adb remount
adb shell mv /system/xbin/hcitool /system/xbin/hcitoo
Click to expand...
Click to collapse
I tried this but without success. Still have on and then off the speaker/headphones button to get the sound.
In the attached files logs for the stock FM applications running on stock moto 2.2 and for the current SpiritFM on CM7.
evgenln said:
I tried this but without success. Still have on and then off the speaker/headphones button to get the sound.
In the attached files logs for the stock FM applications running on stock moto 2.2 and for the current SpiritFM on CM7.
Click to expand...
Click to collapse
OK thanks, I'm looking now.
To respond to your PM about Regional Band Russia frequency steps, it works OK for me as 100 KHz.
It's harder to see now though because the frequency up and down buttons have been removed in favor of the graphic thumbwheel. If you carefully nudge the thumbwheel you can see frequency move 0.1 MHz at a time, while for North America it's 0.2 MHz and odd frequencies.
The frequency step for seek might have a problem; it's done by the chip and there may be a problem there.
evgenln said:
I tried this but without success. Still have on and then off the speaker/headphones button to get the sound.
In the attached files logs for the stock FM applications running on stock moto 2.2 and for the current SpiritFM on CM7.
Click to expand...
Click to collapse
I've started a new thread here that should work for people with less than 10 posts: http://forum.xda-developers.com/showthread.php?p=15607830
Technically it's in a paid app forum and it's technically for the paid Unlocker (converts free app to paid app), but unless some moderator decides it's a really bad idea it's open for discussion of the free app also.
Is there a way to get BT 4.0 LE things working with this phone, I mean i know there might be some hardware limitations but i thought all the radio's (inc BT) were SDR (software defined radio) ? Has anyone been able to pull it off, or is there some hw tweak (or adapter) that would allow this phone to communicate with BT 4.0 LE devices? (ie. tile, etc...).
Now i understand that the stock ROM lacks all support for this but what about Emmanuel U's new KK 1.4 ROM for instance? Would just a new ROM give you added functionality (BT 4 LE) or are we pretty much stuck with due to HW chip (sorry if this is seemingly a stupid question but I thought all the radios' were software defined - and therefore be upgraded via firmware to the latest standards?
steve_77 said:
Is there a way to get BT 4.0 LE things working with this phone, I mean i know there might be some hardware limitations but i thought all the radio's (inc BT) were SDR (software defined radio) ? Has anyone been able to pull it off, or is there some hw tweak (or adapter) that would allow this phone to communicate with BT 4.0 LE devices? (ie. tile, etc...).
Now i understand that the stock ROM lacks all support for this but what about Emmanuel U's new KK 1.4 ROM for instance? Would just a new ROM give you added functionality (BT 4 LE) or are we pretty much stuck with due to HW chip (sorry if this is seemingly a stupid question but I thought all the radios' were software defined - and therefore be upgraded via firmware to the latest standards?
Click to expand...
Click to collapse
I don't use BlueTooth, but it seems to me that if a new standard was to be supported firmware-wise, it would have to show up in the device tree, and those things are usually very static (because things tend to blow up if the device tree gets modified too much).
If a radio update was available, it would have to be by someone who really knows what they are doing (i.e. the original development team). I think Emmanuel U advised someone before to not flash the radio. He probably has his reasons behind that one, and would side with his opinion.
This makes logical sense as i surely don't want to brick my device, by messing with the device tree. So definitely thank you for the advice.
Hopefully if someone ever figures it out (and its reliable) they'll post on the board here.
Thanks again
The Qualcomm MSM8260 platfrom was still Snapdragon S3. It wasn't until Snapdragon S4 that Bluetooth and WiFi were packaged on the SoC.
The Doubleshot uses a Broadcom BCM4329 for its secondary radios. It is most definitely not capable of SDR functionality.
This has been a little lockdown project for myself.
DISCLAIMER: I am not responsible for ANY distractions caused by the shiny new interface, or any bricking of peoples tablets caused by flashing a custom ROM!
For those who don't know, MBUX is the new UI design language that Mercedes uses in the W205 models and up.
I decided to have a go at porting the interface to my MTCE tablet, using assets pulled from reverse engineered cluster firmware for the W213 E class.
Currently, this application works as a new home launcher, being the exclusive application running on the device. There is no way to browse other applications currently (I need to integrate that into the interface), however, it decodes data from CANBUS, and displays a TON of information!
Limitations currently (Early developement)
1. Volume controls and brightness doesn't work. We are bypassing the stock headunit canbus decoder box! (Reasons below)
2. The app will crash on first launch due to USB permissions
Current data shown on interface
1. Fuel data (Consumption per second, Average + Current MPG)
2. Transmission status for 722.x transmissions - Gears, oil temp, Torque converter status and more
3. Climatronics data (Get to see interior and exterior temps, as well as current fan speed, AC work load, Refrigerant pressure, flap statuses)
Future additions
1. Sending track data to Instrument cluster display - full name supported, as well as play duration
2. Phone support on IC display (Show current caller name, as well as call duration)
3. LOADS more sensor data - I have full access to every module on the cars as well as all the messages on canbus and their containing data!
4. Possible 0-60 lap timer?
5.
Why bypass the stock canbus box?
1. The stock decoder box with headunits spam data to the instrument cluster. I've reverse engineered the cluster protocol in these cars, so i can display a lot more text on the display!
2. The stock decoder box triggers the headunit to force show the reverse screen when the car is in reverse. I want the app to be in control of what happens, not the headunit.
3. The arduino required for this project talks to BOTH Canbus C and B, so no need for the headunits own box (Which i found out was filtering data)
What you'll need to try it
1. Malysk ROM installed (Root is required to run it, and Malysk has WIFI ADB debugging enabled for ease of development!)
2. Arduino Uno with 2x CANBUS shields (We will bypass the Headunits own canbus box for our own!
3. Suitable wires for running the Arduino to the 2 CAN systems on the car (see below)
Installation
1. Connect your Arduino to CANBUS C. I have 2 wires running to behind the instrument cluster. These plug into the 2 green wires on the cluster harness (Green is CAN L, Green+White is CAN H):
2. Connect your Arduino to CANBUS B. I have 2 wires running to the hub connector, accessible by removing the panel on top of the driver's pedals. (Brown is CAN L, Brown+Red is CAN H)
3. Connect your Arduino to a laptop, and upload the code found in UNO_CODE in the code repository
4. Connect the Arduino to the headunit with a USB cable.
5. Compile and upload the APK to the headunit, and choose "MERCEDES UI" as your new home screen.
6. Enjoy!
Code repository: https://github.com/rnd-ash/MBUX-Port
Ha - you the man.
First project Ive come across for my car.
However couple of Qs.
1, what is this project for, just to display car info with MB launcher?
I know this is good but without normal control of headunit apps there's not much point.
Could you not easily achieve the same with torque and a similar launcher thats similar
.
2nd. My px5 has a built in canbus, no way to bypass or disable it. Could it still work with the limitations / further research?
Does this have to be run on malaysk rom. Can it not be run as an app or on Hal9ks?
Anyway fantastic news and well done for having a go. Let me know if I can test anything for you.
203 or 211?
Currently, it's still in early stages! But I've been documenting it all on twitter: https://twitter.com/rndashm/status/1286652539337940992?s=19
You can disable canbus. If your using the factory harness (big black thing with loads of wires going out of it), what I did was to simply tape up the male canbus pins on the headunit, so they don't make contact
And as for using existing canbus. No you have to use a dedicated shield. The MTC headunits seem to filter a ton down by the time the Android OS connects to the MCU controller, so there is hardly anything useful there to see. Not to mention that same onboard MCU controller spams canbus with messages for the instrument cluster display from power on, and can't be turned off. Hence I had to bypass that as well in order to render text on the instrument cluster display (I plan to show track names playing on the AUDIO page and, if you have the telephone page, allow you to dial a contact from there! (Ive done this with a prototype project on my GitHub account called W203-Canbus).
For now, I don't think you can test anything as such but I suggest you get some wires ready for both can B and can C, and buy an Arduino Uno and 2x canbus shields
Great Job !!!
I was desperately looking for CANBUS related info for my use case on a mercedes car (2009 W164) where i receive very limited CANBUS info and found this thread.
Comparing folks with Audi/VW/SKODA where they are able to see pleanty of info (AC, Parking Sensors, door open etc) with my situation on a mercedes vehicle made me mad for not able to have those info available.
Keep up
Thx, Alexis
Thanks!
I'm making a series showing how I'm building the whole interface FYI - you can see all the interface progress as I'm designing the system:
@UKSFM99 how's it going, it's been a while since you posted these... ?