Database Users

Cyanogen Conspiracy Theory

Just a thought:
The manufacturer of an Android device only has to support android updates for that devices for a limited period of time. It is in their interest and the interest of the cell carriers, that each handset has a limited lifespan.
Cyanogen's (and others) rom's are pro-longing the life of handsets by allowing users to bypass the limits on a device's supported android versions imposed by the manufacturers and cell carriers.
E.g. say if HTC decide not to release an official Android 2.0 or higher version rom for the existing HTC G1. The only possible way for users to have such a rom, would be if a member of the community rolled their own and made it available.
This is really only a conspiracy theory, but maybe the manufacturers / cell carriers have spotted the above issue and started pressuring Google to halt community roms. Google needed an excuse to do so, and used the distribution of closed applications in the roms!
Just a thought.....

donster80 said:
Just a thought:
The manufacturer of an Android device only has to support android updates for that devices for a limited period of time. It is in their interest and the interest of the cell carriers, that each handset has a limited lifespan.
Cyanogen's (and others) rom's are pro-longing the life of handsets by allowing users to bypass the limits on a device's supported android versions imposed by the manufacturers and cell carriers.
E.g. say if HTC decide not to release an official Android 2.0 or higher version rom for the existing HTC G1. The only possible way for users to have such a rom, would be if a member of the community rolled their own and made it available.
This is really only a conspiracy theory, but maybe the manufacturers / cell carriers have spotted the above issue and started pressuring Google to halt community roms. Google needed an excuse to do so, and used the distribution of closed applications in the roms!
Just a thought.....
Click to expand...
Click to collapse
yeah that is good point but i think the limited hard where the g1 is whats going to kill it. i have been 3 through 3 already

We really don't need more threads on this, this has already been brought up in multiple threads.

Google's solution to Android fragmentation coming in 'Froyo'

One of the largest problems currently facing Google's Android operating system is the great degree of fragmentation due to the many different products that manufacturers and carriers have brought to the market. As it stands now, there are four different versions of Android software on various handsets: 1.5, 1.6, 2.0, and 2.1. The reason for this can be attributed to the inevitable differences in hardware, third party software (such as HTC's Sense UI), and the carrier or manufacturer's capacity to update their products.
Currently released Android phones ordered by their supported Android version so far include the following:
* 1.5: HTC Hero, T-Mobile Pulse, LG GW620, Motorola Cliq, Motorola Backflip, Samsung Behold, Samsung i7500, Samsung Moment
* 1.6: HTC Dream, HTC Magic, HTC Tattoo, Motorola Devour, Sony Ericsson Xperia X10
* 2.0: Motorola XT800
* 2.1: Google Nexus One, HTC Legend, HTC Desire, Motorola Droid, Samsung i5700
This large degree of platform fragmentation finds users and developers unable to take advantage of newer features and bug fixes that the latest release holds. For example, users without Android 2.0 or higher are left without Exchange support and new UI improvements, among other things. Taking note of these critical problems, Google will tackle the issue head on by taking their software into their own hands for their next Android release.
Named "Froyo", Google's next Android version will be detached of the usual set of first party applications and core components that currently populate the OS. Instead of bundling those applications with the operating system, Google will instead make them available through the Android Market for download. This is currently how updates to Google Maps are handled on Android.
This new approach will apply to both Android applications and system components. So for example, if Google brings a new update to the virtual keyboard or email application, all one would have to do is download the update directly from the Market as it instantly becomes available. No longer would users have to wait for their carrier or manufacturer to make it available for download.
Also reported is that Google is finishing up most of the core work required for Android and will soon be shifting development to consumer features and applications. Developers should be getting finalized APIs and frameworks as Froyo arrives, so they can instead focus on making applications faster and easier with greatly matured tools for the OS.
Source - http://www.neowin.net/news/google039s-solution-to-android-fragmentation-coming-in-039froyo039

Bootloader for ARC / Xperia models

The X10 has an issue with the Bootloader being protected by Marlin DRM.
There is no obvious reason and no clear benefit to end users or the general public. Most likely a precautionary measure to ensure SE applications work as intended and to assist with purchases of games, music, updates to Android firmware (often mistakenly called ROM's) and features Sony Ericsson have not explained in any level of detail or even stated that it exists as part of their obligations and your rights to know as the consumer.
According to the W3C.
What are some potential invasions of privacy?
1. User authentication - current PKI protocols limit the degree of anonymity -- we need to know who are you so we can sue you if you infringe
2. Usage tracking for fraud prevention
OK. Now you have just purchased a Sony Ericsson Android phone and all your social network contacts from any social media site can be merged with your phone book, backed up into Google's Gmail and shared beyond any one or all of these service's. The man controlling 'everything' that happens on your device is SE.
The phone at core capability is able to run Ubuntu / Debian Linux, Windows, iPhone and emulate everything you might wish to or choose to. Thanks to this 'feature' in the form of the Marlin DRM and Seacert broadband bootstrap implementation being present on these phones... it isn't going to happen.
With the Xperia models, the entire operating system is virtualized on boot and impossible to modify the behavior of the boot loader, due to a very high grade encryption system, provided by Inter Trust.
Unlike HTC, Motorolla, Samsung (who own a stake in the Marlin DRM but choose not to use it for snooping or destroying the main purpose of Android phones) for that matter most other Android phone manufacturers, allow the boot loader to be modified without too much effort and load a custom bootloader for multiple firmwares.
e.g; Gingerbread 2.3.2 is the default o/s shipped with Sony Ericsson apps, you want to keep this but also load Honeycomb, or Gingerbread 2.3.3, a modified vanilla o/s without things like timescape and unnecessary apps that do nothing for saving battery life.. it's your phone and you should be able to have this choice, in fact the reason Android is open source, is stop one company from forming any kind of monopoly.
So what should DRM so for us?
Are there general requirements from the concept of free flow of information?
* avoid unnecessary use restrictions, respect fair use
* universal service --- equal and fair access right
* support variety of licensing options
* make it easy for users to act lawfully
* seamless operation, interoperability of DRMS
* Support Information Search(engines)
* make licensing easy to reduce transaction costs
* secure operating environment: integrity and availability of content
* avoid bottlenecks and monopolies when standardizing (production and distribution)
Conclusion:
* copyright laws give free hand to those who develop DRMS
* Only few compulsory requirements from Law, but Guidelines can be derived from Law
* when hesitating, think in terms of free flow of information
Now back on over in Android world at Google HQ...
On 24 September 2009, Google issued a cease and desist letter to the modder Cyanogen, citing issues with the re-distribution of Google's closed-source applications within custom firmware.
Even though most of Android OS is open source, phones come packaged with closed-source Google applications for functionality such as the application store and GPS navigation.
Google asserted these applications can only be provided through approved distribution channels by licensed distributors. Cyanogen complied with Google's wishes and is continuing to distribute this mod without the proprietary software.
He has provided a method to back up licensed Google applications during the mod's install process and restore them when it is complete.
The exact same principle can be done with SE closed source apps and SE do provide the source code for their firmwares as part of the open source license. Anyone withing to check this out can simply head over to http://developer.sonyericsson.com/wportal/devworld/technology/android/ and start developing straight away. The source code, test keys and everything you need is either there or linked from there back to the places you need to be.
Semcboot security algorithms are not required and serve no benefit. The day that SE stop's supporting updates for this device, the same as they did with the Xperia X10 at 2.1 Eclair, your phone will be useless and stuck with older versions of Android.
If this is acceptable and your not bother by having no bootloader mod's, a hack to be able to change firmware that may someday soon be blocked and privacy issues built in as a matter of due course that you were not even correctly informed of, except for via a specialist forum (your looking at it), then good luck with your Arc, Neo or Play.. and I suspect that there is the real rationale here - Play.
Marlin DRM exists in the PlayStation 3 for the market and guide as it does in the PSP and also will in the Xperia Play. SE became rather unhappy when the master cryptographic key to the PS3 was discovered and distributed on mass over the internet (I have a t-shirt with the codes printed...) as it bypassed their protection ad allowed among other things, pirated games to play and unauthorized content to loaded, custom operating systems etc..
Sony Ericsson watched carefully at HTC and thought about how best to implement all of their technology in an extremely secure manor and this is the result. It may actually benefit end users, so far Sony have yet to state their side of the story and will be looking forward to seeing posts on anything relevant in this thread, for anyone interested in the subject and for anyone thinking of buying an Arc.
Wish I had of known this information before I purchased my x10 but is it such a perfect world?

Isn't the X10 hackable?
This forum here has tons of custom roms for the X10
http://forum.xda-developers.com/forumdisplay.php?f=617
Sorry for the stupid question. I'm new to SE and considering an Xperia arc.

yoyohere2 said:
Isn't the X10 hackable?
This forum here has tons of custom roms for the X10
http://forum.xda-developers.com/forumdisplay.php?f=617
Sorry for the stupid question. I'm new to SE and considering an Xperia arc.
Click to expand...
Click to collapse
No it is not. We cannot get a newer Linux kernel with new feature hooks that support functions like tether and hotspot and speed or security improvements. All the roms just overlay newer Android on top of the older kernel.
Other phones have been fully hacked and can get a newer kernel to support the newer Android without any mismatched functions. The devs here have to work hard retrofitting Android.
Sent from my X10a using XDA App

well the X2 wasnt hacked yet

This thread shows how to root a X10.
http://forum.xda-developers.com/showthread.php?t=711907
So the xperia arc and xperia x10 can be rooted?

Geohot recently announced that he bought a Xperia x10 and will be first in cue for the Xperia play. Keeping his success in mind I've got a good feeling about it.
http://www.youtube.com/watch?v=dXxw71oxjxs

[REF]Which devices have ANT+ hardware

##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
Amazon, Fire Phone
HTC, One (M8)
Motorola, Moto G 4G (http://forum.xda-developers.com/moto-g/general/ant-moto-g-4g-maybe-t2875420)
Motorola, Moto X
Nokia, Lumia Icon (http://en.wikipedia.org/wiki/IEEE_802.11ac)
OnePlus, One: Stock (since CM11S 38R)
Samsung, Galaxy Mega 6.3
Sony, Xperia M2: Stock (certified)
Sony, Xperia Z Ultra: Stock (certified)
Xiaomi, Redmi 1S: Stock (http://www.gizmozone.in/unlock-unwritten-features-xiaomi-smartphone/)
Xiaomi, Redmi Note 4G (http://en.miui.com/thread-43935-1-1.html)
Xiaomi, Mi4
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
Acer, Aspire V Nitro laptop
Acer, Aspire V13 laptop
LG, Nexus 5X (https://www.ifixit.com/Teardown/Nexus+5X+Teardown/51318?revisionid=HEAD#s112148)
OnePlus, Two (https://www.ifixit.com/Teardown/OnePlus+2+Teardown/45352#s100455)
MT6595
BRAND, PRODUCT NAME: ROMS
Alcatel, One Touch D820 (http://www.gizmochina.com/2014/07/18/first-mt6595-mobile-phones-with-amazing-specs/)
Coolpad, Dashen F2 (http://www.gizmochina.com/2014/07/1...-will-be-the-first-to-use-the-mt6595-chipset/)
IUNI, U3 (http://www.gizmochina.com/2014/08/07/iuni-u3-to-be-released-on-august-26/)
Lenovo, Vibe X2 (http://www.gizmochina.com/2014/09/17/snapshots-lenovo-vibe-x2-the-sandwich-cellphone/)
Meizu, MX4 (http://www.gizmochina.com/2014/09/02/review-the-meizu-mx4-is-a-dream-come-true/)
Mogu, M7 (http://www.gizmochina.com/2014/09/0...chipset-goes-on-sale-for-1399-rmb-228-10-usd/)
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
Apple, Apple TV 3rd gen
Apple, iPhone 4S
Apple, iPad 3
Asus, Nexus 7
Google, Glass (http://www.techinsights.com/teardown.com/google-glass/ Confirmed: http://au.alibaba.com/product/1743558555-Wireless-LAN-Wifi-Module-WM-BN.html)
HTC, Sensation XL
Kindle, Fire HD 2013
Ouya, Ouya
Samsung, Galaxy Beam
Samsung, Galaxy Nexus
Samsung, Galaxy Note
Samsung, Galaxy Pocket
Samsung, Galaxy Tab 10.1
Samsung, Galaxy Tab2
Samsung, Galaxy S2
Sony, Xperia S [LT26i]: Stock (certified)
Sony, Xperia acro S: Stock (certified)
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
Apple, Apple TV 3.2
Apple, Apple Watch (http://www.ifixit.com/Teardown/Apple+Watch+X-ray+Teardown/41323 )
Apple, iPhone 5
Apple, iPhone 5c
Apple, iPhone 5s
Apple, iPad 4
Apple, iPad Mini
Apple, iPod Touch 5th gen
Google, Project Tango Tablet
Samsung, Galaxy S3 [i9300]
Samsung, Galaxy S3 Mini [i8190]
Samsung, Galaxy S5 Mini
Samsung, Galaxy Note 2
Samsung, Galaxy Note 10.1
Samsung, Gear Fit (https://www.ifixit.com/Teardown/Samsung+Gear+Fit+Teardown/24029)
Samsung, Gear Live
Tesco, Hudl
Xiaomi, Mi3, Stock (http://www.gizmozone.in/unlock-unwritten-features-xiaomi-smartphone/)
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
HTC, HTC One
Samsung, Galaxy S4: Stock [Android 4.3 and up] (certified)
Samsung, Galaxy S4 Active (maybe: http://forum.xda-developers.com/gal...-s4-active-t3008891/post58619104#post58619104)
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
HTC/Google, Nexus 9 (https://www.ifixit.com/Teardown/Nexus+9+Teardown/31425)
Samsung, Galaxy S5: Stock (certified)
Xiaomi, MiPad (http://en.miui.com/thread-24179-1-1.html)
BCM4356
BRAND, PRODUCT NAME: ROMS
HTC, One (M9) (https://www.ifixit.com/Teardown/HTC+One+M9+Teardown/39166)
Motorola/Google, Nexus 6 (https://www.ifixit.com/Teardown/Nexus+6+Teardown/32877)
BCM4358
BRAND, PRODUCT NAME: ROMS
Huawei/Google, Nexus 6P (https://en.wikipedia.org/wiki/Comparison_of_Google_Nexus_smartphones)
Samsung, Galaxy S6: Stock (certified) (http://www.slideshare.net/jjwu6266/introducing-samsung-galaxy-s6)
Samsung, Galaxy S6 Edge: Stock (certified) (http://www.slideshare.net/jjwu6266/introducing-samsung-galaxy-s6)
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
Barnes & Noble, Nook Color
Blackberry, Z10
HTC, Legend (http://www.dcrainmaker.com/2010/07/behind-scenes-of-team-htc-columbia-and.html)
Motorola, Droid X
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
Nexus 10 (from ANT+ Enabler list https://play.google.com/store/apps/details?id=com.z2software.antplus)
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.

## 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

## 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.

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.

Trespassing said:
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.
Click to expand...
Click to collapse
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).

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)

Xiaomi Redmi 1S
Now I'm running CM11 (11-20141201-UNOFFICIAL-armani) on Xiaomi Redmi 1S and flasheable zip for standard OnePlus One CyanogenMod, works for Redmi 1S.
rubensa said:
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)
Click to expand...
Click to collapse

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)

anybody know how to obtain bcm20715 proprietary binaries,used by lg g watch bluetooth

Update for the S4 Active: It generally supports ANT+.

I have a Nexus 6 and it looks like they have a BCM4356 chip (from searches). I haven't been able to activate it so I'm not sure if it supports ANT+
My Firmware folder shows this though:
BCM4354A2
BCM20795_firmware (NFC)
** Uodate** Just downloaded this and this is the result:
https://github.com/ant-wireless/ANT-Android-SDKs/tree/master/ANT_Android_SDK/Tools
Still can't get it to work though.

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+.

I thought it's a thread about hardware compromised by devices included in NSA ANT (http://en.wikipedia.org/wiki/NSA_ANT_catalog).
Such an unfortunate technology naming. ^.-

oneplus one is ok
oneplus one with Exodus 5.0.2 is working very well with Garmin ANT+ heart rate monitor (belt)

ehhh there are some ant apps in play store, u might find an device list there also?
Sent from my GT-P3110 using XDA Free mobile app

My xiaomi redmi 1s has ant+ hardware

Moto G 2013
No ANT+
LG, G Watch: BCM20715
Motorola, Moto G (1st gen 2013)
Click to expand...
Click to collapse
I think this is incorrect. On my xt1032, if I flash the file located at http://forum.xda-developers.com/moto-g/general/ant-moto-g-4g-maybe-t2875420 (intended for the Moto G 4G), I can pair with a Garmin HR monitor and pick up its signals. Tested on CM12.1

iRant said:
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.
Click to expand...
Click to collapse
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

dan74 said:
Hello iRant, did you manage to get ANT+ working on your Galaxy Nexus using the internal BCM4330?
Click to expand...
Click to collapse
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

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

[Q] Field Testing app Frequency Locking

I am looking at field test tools and many say they can do RAT, band, frequency locking.
For example, even a small company like this:
http://www.azenqos.com/
New compatible phones: Google (LG) Nexus 5 (with LTE PCI Cell Locking and more), Samsung S5 (beta), Sony Xperia Z1 compact, Sony Xperia M, Sony Xperia E, Sony Xperia J, Motorola G. Please contact us for exact model/firmware number and further details.
My question is how can I get these kinds of features? There is nothing in the official Android SDK that I can find. Is this something NDK related?
Any help or guidance would be appreciated. I've been googling for a while now.
Thanks in advance.