• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!
Search This thread

iRant

Member
Dec 11, 2012
43
21
Perth
##This is still a work in progress. I will keep improving the formatting and adding more clarification on what this means. If there is anything that doesn't make sense, please ask ##

There are now many devices shipped with ANT+ support enabled, many more which have the hardware but it is not enabled, and then a selection of ROMs which do or don't allow you to use the ANT+ hardware. Since CM11 M10, CyanogenMod has announced they have started adding ANT+ support, so my intention is to extend this to all maintained devices with ANT+ hardware. This is a place to record new phones that have ANT+ hardware, and WHAT THAT HARDWARE IS. This is information taken from device teardowns (https://www.ifixit.com/Teardown) or product marketing (http://www.slideshare.net/jjwu6266).

Turning on ANT+ is exactly the same across all phones that have the same ANT+ chip (generally a combo wireless chip also responsible for Wi-Fi, Bluetooth, Bluetooth LE etc). This is why recording exactly which wireless chip a phone has is the only useful information here**. If ANT+ has been enabled for another phone that has the same chip as yours, then there is no modifications required to port the ANT+ code to your phone.

** and possibly Bluetooth stack, but this is only for some chips and only varies in limited cases.

What is ANT/ANT+
http://www.thisisant.com/developer/ant-plus/ant-antplus-defined/

It's an ultra low power wireless technology allowing your phone to talk to other devices, and even if they are only powered by a coin cell battery, it can last years.

What I am talking about here is adding ANT, as this is the wireless technology. ANT+ is the interoperability layer that uses ANT communication. As ANT+ is the brand/consumer visible terminology, I will continue to (incorrectly) use that in describing the wireless tech.

No it is not the same as Bluetooth Low Energy, and no it is not reasonable to simply switch to BLE sensors.

Which chips support ANT+
There are standalone ANT chips, which are generally not included in phones, as well as SoC options: http://www.thisisant.com/developer/components/

Most of the following information is gathered from the ANT source on GitHub: https://github.com/ant-wireless

ANT+ USB
Android has support for using an ANT+ USB stick (USB Host or USB Open Accessory), but we are not concerned with that here.

ANT+ Certified Mobile Phones/Devices
The list is maintained by ANT Wireless here: http://www.thisisant.com/directory/filter/~/60/~/~/

WCN3680 Qualcomm
ANT firmware loaded at factory, no firmware patch required

QCA61x4 Qualcomm
QCA61x4 is a single chip BT/WLAN/ANT+ combo solution (https://www.intrinsyc.com/bluetooth-on-intrinsyc-open-q-805-development-kit-apq8084/)
QCA6164, QCA6174

WL12xx Texas Instruments
(aka WiLink 6.0, WiLink 7.0) WL1271, WL1273, WL1281, WL1283
Requires firmware loaded through script

WL18xx Texas Instruments
(aka WiLink 8.0)
WL1831, WL1833

BCM433x Broadcom
BCM4330, BCM4331, BCM4334, BCM4335, BCM4339
May require firmware loaded through script

BCM435x Broadcom
BCM4354, BCM4356, BCM4358

CG29xx ST-Ericsson

MediaTek (SOC)
MT6630 (http://www.thisisant.com/news/media...ortunities-for-connected-lifestyle-health-an/)
MT6595 (http://www.mediatek.com/en/products/mobile-communications/mobile-chipsets/smartphone/mt6595/)
MT6795 (http://www.mediatek.com/en/products/mobile-communications/mobile-chipsets/smartphone/mt6795/)

Other considerations
ANT+ and Bluetooth Low Energy concurrently
Not all chips can support ANT+ and BLE at the same time. On early chips (which didn't ship with BLE enabled, such as the WiLink 6/7 or BCM4330) the firmware for both gets loaded in to the same space - so if you want to run BLE you can't run ANT+, and vice-versa.

Bluetooth Stack
On the chips where ANT+ firmware is patched on at run time (and possibly others), the communication with the chip is through the Bluetooth stack. This means the Bluetooth stack the device runs will impact how ANT+ support is added. There are at least these stacks to deal with:
  • BlueZ, This was the standard (from Linux) Android stack until Android 4.1.
  • Bluedroid. The standard Android stack since Android 4.2.
  • BTIPS. Texas Instruments proprietary stack.

WCN3680
BRAND, PRODUCT NAME: ROMS

If you are running standard CyanogenMod (not the "official" CM 11S on OnePlus One), you should be able to add ANT+ support to your device by sideloading the flashable zip attached to this post.

QCA6164
BRAND, PRODUCT NAME: ROMS
  • Lenovo, G40 Laptop
  • Lenovo, G50 Laptop
  • Lenovo, Flex 3 Laptop

QCA6174
BRAND, PRODUCT NAME: ROMS

MT6595
BRAND, PRODUCT NAME: ROMS

BCM4330
Note that the AzureWave AW-NH660 contains the BCM4330: https://www.ifixit.com/Teardown/Ouya+Teardown/14224
Note that the Murata SWB-B42 module houses a BCM4330: https://www.ifixit.com/Teardown/Samsung+Galaxy+Nexus+Teardown/7182
Note that the WM-BN-BM-04 module houses a BCM4330: http://au.alibaba.com/product/1743558555-Wireless-LAN-Wifi-Module-WM-BN.html
Note that the source to build the Xperia S has been released by Sony.
BRAND, PRODUCT NAME: ROMS

BCM4331
BRAND, PRODUCT NAME: ROMS
  • Apple, Airport Extreme 5th gen
  • Apple, Macbook Pro 2011
  • Apple, Mac Mini 2011

BCM4334
Note the Murata KM2323011, 339S0205 and 339S0171 modules are based on the BCM4334
BRAND, PRODUCT NAME: ROMS

The iPhone 6/6+ houses a Murata 339S0228 module, and the iPad Air 2 houses a Murata 339S02541; which may be built on a BCM433X chipset.

BCM4335
BRAND, PRODUCT NAME: ROMS

BCM4339
BRAND, PRODUCT NAME: ROMS
Note that the Murata Type ZP and 1CK modules are based on a BCM4339: http://wireless.murata.com/eng/products/rf-modules-1/wi-fi-bluetooth.html
  • Apple, iPod Touch 3rd gen
  • LG, Nexus 5
  • LG, G3
  • Samsung, Galaxy Note 3: Stock (certified)

BCM4354
This is in a Murata KM4220004 module: https://www.ifixit.com/Teardown/Samsung+Galaxy+S5+Teardown/24016
Chip discovered from: http://www.slideshare.net/jjwu6266/introducing-samsung-galaxy-s5
BRAND, PRODUCT NAME: ROMS

BCM4356
BRAND, PRODUCT NAME: ROMS

BCM4358
BRAND, PRODUCT NAME: ROMS

WL1271
BRAND, PRODUCT NAME: ROMS
  • Microsoft, Kin Two
  • Motorola, Droid
  • Motorola, Droid 2
  • Motorola, Droid Bionic
  • Motorola, MOTOACTV
  • Nokia, N8
  • Sony, Xperia X8: Stock (certified)
  • Sony, Xperia x10 mini pro: Stock (certified)
  • Sony, Xperia x10 mini: Stock (certified)

WL1273
BRAND, PRODUCT NAME: ROMS

WL1281
BRAND, PRODUCT NAME: ROMS
  • Fujitsu, Arrows Tab LTE


WL1283
BRAND, PRODUCT NAME: ROMS
  • Blackberry, PlayBook

WL1285
BRAND, PRODUCT NAME: ROMS
  • Motorola, Droid RAZR
  • Motorola, Droid 4

WL1831
BRAND, PRODUCT NAME: ROMS
Note that the Murata Type WT modules are based on a WL1831: http://wireless.murata.com/eng/products/rf-modules-1/wi-fi-bluetooth/type-wt.html
  • Motorola, Moto 360

WL1833
BRAND, PRODUCT NAME: ROMS
Note that the Murata Type WM modules are based on a WL1833: http://wireless.murata.com/eng/products/rf-modules-1/wi-fi-bluetooth.html

CG29xx
BRAND, PRODUCT NAME: ROMS

Unknown (ANT+ Certified)
Last update: 17 September 2014

The latest list is available at https://www.thisisant.com/directory/filter/~/60/~/~/

Without a teardown, it is still possible to discover the chip manufacturer by getting the ANT+ firmware version from the ANT Support Checker app by ANT Wireless when running the stock ROM.
AOV - Texas Intruments
AUM - Broadcom
AVN - Qualcomm
??? - MediaTek

BRAND, PRODUCT NAME: ROMS
  • Sony, Xperia E3: Stock (certified)
  • Sony, Xperia Z3 Tablet Compact: Stock (certified)
  • Sony, Xperia Z3 Compact: Stock (certified)
  • Sony, Xperia Z3: Stock (certified)
  • Samsung, Galaxy Alpha: Stock (certified)
  • Sony, Xperia C3 Dual: Stock (certified)
  • Sony, Xperia C3: Stock (certified)
  • Samsung, Galaxy Tab S 10.5-inch: Stock (certified)
  • Samsung, Galaxy Tab S 8.4-inch: Stock (certified)
  • Sony, Xperia T3: Stock (certified)
  • Samsung, Galaxy Tab4 8.0: Stock (certified)
  • Samsung, Galaxy Tab4 10.1: Stock (certified)
  • Samsung, Galaxy S5 ???LTE-A: Stock (certified)
  • Samsung, Galaxy W: Stock (certified)
  • Samsung, Galaxy Note 3 Lite: Stock (certified)
  • Samsung, Galaxy TabPRO 12.2: Stock (certified)
  • Sony, Xperia T2 Ultra: Stock (certified)
  • Samsung, Galaxy Note 3 Neo: Stock (certified)
  • Samsung, Galaxy TabPRO 8.4: Stock (certified)
  • Samsung, Galaxy TabPRO 10.1: Stock (certified)
  • Samsung, Galaxy NotePRO 12.2: Stock (certified)
  • Sony, Xperia Z2 Tablet: Stock (certified)
  • Sony, Xperia Z2: Stock (certified)
  • Sony, Xperia Z1 S: Stock (certified)
  • Samsung, Galaxy Grand 2 (LTE): Stock (certified)
  • Sony, Xperia Z1 Compact: Stock (certified)
  • Samsung, Galaxy J: Stock (certified)
  • Garmin, Monterra: Stock (certified)
  • Samsung, Galaxy Note 10.1 (2014 Edition): Stock (certified)
  • Sony, Xperia Z1: Stock (certified)
  • Sony, Xperia SL: Stock (certified)
  • Sony, Xperia ray: Stock (certified)
  • Sony, Xperia pro: Stock (certified)
  • Sony, Xperia neo V: Stock (certified)
  • Sony, Xperia neo: Stock (certified)
  • Sony, Xperia mini pro: Stock (certified)
  • Sony, Xperia mini: Stock (certified)
  • Sony, Xperia ion LTE: Stock (certified)
  • Sony, Xperia ion HSPA: Stock (certified)
  • Sony, Xperia arc S: Stock (certified)
  • Sony, Xperia arc: Stock (certified)
  • Sony, Live with Walkman: Stock (certified)
  • HTC, HTC Rhyme: Stock (certified)
  • Sony, Xperia active: Stock (certified)

Also

No ANT+
  • LG, G Watch: BCM20715
  • Motorola, Moto G (1st gen 2013)
  • Nexus 7 2nd gen: WCN3660
  • Nexus 4: Muratta SS2908001

Please do not add any "I want ANT+ in X" posts.
 
Last edited:

iRant

Member
Dec 11, 2012
43
21
Perth
## Saved for instructions on how to discover if a device has ANT+ (including a list of other wireless chips, so you know if it doesn't). ##

How to check if you're phone has ANT hardware:

4 options:
1. Look at the hardware. Open up your phone, remove the metal shields, and see if one if the chips listed above...or look at a teardown on sites like https://www.ifixit.com/Teardown
2. Check the firmware files. For example, look at the file names in /system/vendor/firmware like done at http://forum.xda-developers.com/showpost.php?p=58619104&postcount=13
3. Check from an app. This only works if your phone is ANT enabled, but you can get the firmware version by running https://github.com/ant-wireless/ANT...SDK/Tools/Android_ANTSupportChecker_1-2-0.apk
4. adb shell command line. This is not a definitive answer, but it can help. Useful commands:
a. getprop and looking at something like ro.hardware
 
Last edited:

iRant

Member
Dec 11, 2012
43
21
Perth
## Saved for instructions on how to build an ANT+ enabled ROM from source ##

Using CyanogenMod as an example, it should be possible to add ANT+ to any phone built from AOSP source.

CyanogenMod already has source code for building for devices with Qualcomm radio chips, and the device config simply needs to be updated. I have managed to build an ANT+ enabled ROM completely from source for a Broadcom chip (should also work with the TI chips), which requires patching the Bluedroid Bluetooth stack. This was based on the source Garmin pushed to the AOSP Gerrit (https://android-review.googlesource.com/#/q/owner:"James+Bootsma"+status:open) but ANT Wireless now has the source on their GitHub (eg. https://github.com/ant-wireless/pla...mmit/75f70267404c0209bc20a6c627c11ebcd527d228) which would have made things easier.

I only have a Galaxy Nexus with a Broadcom part, so I am building CM11 and need to deactivate BTLE to add ANT+ as the BCM4330 only supports one. I took the firmware patch file that adds ANT instead of BTLE from a Sony Xperia S, which is using new Bluetooth functionality, so I get BT enable issues (which will be fixed if I find a newer patch file). This won't be a problem with the Broadcom wireless chips in newer phones.

I will publish my source and work through turning on ANT in as many phones as I can, but I am unable to test. If there is anyone with any of the phones above, who is doing a ROM build from source and would like to add ANT+, let me know and I can prioritise that device.
 
Last edited:
  • Like
Reactions: sushijames

Trespassing

Senior Member
Jun 5, 2012
162
46
Taunusstein
Just search installed system apps for ANT-Service ;)

By the way: my former former former Sony Ericsson Neo V was ANT+ enabled, too. Z1 as well ;)

Von meinem Sony Xperia Z1 gesendet. Mit Hirn.
 

iRant

Member
Dec 11, 2012
43
21
Perth
Just search installed system apps for ANT-Service ;)

By the way: my former former former Sony Ericsson Neo V was ANT+ enabled, too. Z1 as well ;)

Von meinem Sony Xperia Z1 gesendet. Mit Hirn.

Most of the phones listed above won't have any ANT service, as (even though they have the hardware) they haven't had the software support added.

The Neo V and Z1 are already included above. They were both released with ANT+ support stock (and ANT+ certified, so are also easily found by looking in the ANT+ Product Directory).
 

rubensa

Member
Feb 3, 2011
30
5
Espiniella
Xiaomi Redmi 1S

Used ANT Checker to identify Chip on Xiaomi Redmi 1S

Built-in firmware: AVN1.01B04

So, It's a Qualcomm chip (not surprise as phone has Qualcomm Snapdragon 400 MSM8228 SoC)
 
  • Like
Reactions: iRant

LayerEight

Senior Member
May 5, 2013
55
22
SHA
Seems that S4 Active also comes with BCM4335.

The firmware files for BMC4335 are included in CM12 roms (and possibly Stock roms, ill verify this)
 
  • Like
Reactions: macbek

Jeimygirl

Senior Member
Mar 25, 2010
463
98
Jax

Attachments

  • Screenshot_2015-03-05-11-47-44.png
    Screenshot_2015-03-05-11-47-44.png
    125.1 KB · Views: 2,591
Last edited:

iRant

Member
Dec 11, 2012
43
21
Perth
As I just added to post #3: if there is anyone with any of the phones above, who is doing a ROM build from source and would like to add ANT+, let me know and I can try and get you a patch to enable ANT+.
 

dan74

Senior Member
Mar 21, 2007
52
0
Bucharest
I only have a Galaxy Nexus with a Broadcom part, so I am building CM11 and need to deactivate BTLE to add ANT+ as the BCM4330 only supports one. I took the firmware patch file that adds ANT instead of BTLE from a Sony Xperia S, which is using new Bluetooth functionality, so I get BT enable issues (which will be fixed if I find a newer patch file). This won't be a problem with the Broadcom wireless chips in newer phones.

I will publish my source and work through turning on ANT in as many phones as I can, but I am unable to test. If there is anyone with any of the phones above, who is doing a ROM build from source and would like to add ANT+, let me know and I can prioritise that device.

Hello iRant, did you manage to get ANT+ working on your Galaxy Nexus using the internal BCM4330? I'd dearly love to find out - Last January I've retired my old Galaxy Nexus as a "bike computer" and it did work very well in this role for these 2 years using a Suunto ANT+ USB adapter connected via an USB OTG cable, but the phone's micro USB connector finally failed on Saturday due to wear & tear. The phone is otherwise still working great (even charging the battery via the same micro USB connector!) so I'd very much like to keep using it as my bike computer if at all possible. I'm also using CM11 (cm-11-20150626-SNAPSHOT-XNG3CAO1L8).

Many thanks in advance!
Dan
 

iRant

Member
Dec 11, 2012
43
21
Perth
Hello iRant, did you manage to get ANT+ working on your Galaxy Nexus using the internal BCM4330?

Hi Dan,

My GNex doesn't come out much anymore as the USB connection is a pain to get working, including with a charger for me.

I ran in to problems with newer CM versions as they use Bluetooth (or maybe it was WiFi...) functionally that was added in the BCM4330 patch, which made it hard to find a suitable ANT+ enabled patch. I don't remember if I found something. If there is a suitable patch, it would likely be from a phone with a slightly newer Broadcom part (BCM4334?)...or the Recon Jet if you can access the patch file (older Android version, but still using the older radio chip)

No specific help from me on this, sorry
 

iRant

Member
Dec 11, 2012
43
21
Perth
Depending what bike computer app you use, just go with an older version of CM and you can build with the Xperia S patch and the source from the ant-wireless Github. I'm assuming there is an implementation available to work with the Bluedroid Bluetooth stack - it's been a long time since I've looked at this
 

Top Liked Posts