Database Users

[REF]Which devices have ANT+ hardware - Hardware Hacking General

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

Related

Hi everyone,
To be able to have a full ICS Rom we need new compatible Adreno 200 libs!
Xperia X10 mini / X10 MiniPro / X8 have the same Chipset Qualcomm MSM7227 (CPU: 600 MHz ARM 11 / GPU: Adreno 200).
Exist a lot of devices with that Chipset: see here
MSM7227
These devices are GSM cousins of the Snapdragon chips, for example they include OpenGL ES 2.0 engine and Adreno 200 included.[6]
Popular phones using these processors:
MSM7227 600 MHz (ARMv6);[7] LG Optimus Me, Samsung Galaxy Fit, Samsung Galaxy Mini, Samsung Galaxy 551, LG Optimus Chic, ZTE Blade, HTC Legend, Mytouch 3G Slide, HTC Gratia, LG Optimus One P500 GSM, ViewSonic ViewPad 7, Samsung Galaxy Europa, Sony Ericsson Xperia X8 (SE Shakira), HTC Aria, Palm Pixi GSM, OlivePad VT-100, HTC Wildfire S, Alcatel OT-990, Micromax A70, LG Optimus chat L-04C, Huawei Pocket WiFi S II S41HW, Huawei Ideos X3, Huawei Sonic U8650, Sony Ericsson Xperia X10 Mini, Sony Ericsson Xperia X10 Mini Pro, Garmin & Asus M10, WellCom A88, Coolpad W706, Garmin & Asus A10.
MSM7227 Turbo 800 MHz (ARMv6);[7] Samsung Galaxy Gio, Samsung Galaxy Ace, Odys Space, LG Optimus Net, LG Optimus Hub, ZTE Skate, HTC ChaCha, HTC Salsa, Huawei smart bar S42HW, Coolpad 7260.
Click to expand...
Click to collapse
The idea is to request to Qualcomm to provide new libs for MSM7227 (armv6) like they provide to QSD8250 (armv7)...
Please join us in Qualcomm Developer Network site to request them these new libs here: MSM7227
Thanks

I'm supporting this initiative/request to qualcomm.
Is there another way for us to get the libs?

kIERO's said:
I'm supporting this initiative/request to qualcomm.
Is there another way for us to get the libs?
Click to expand...
Click to collapse
Well i do not think so!
I do not see mobile manufacturers (samsung, sony, ...) invest for old device, this is why we request directly to Qualcomm...
Sent from my X10 Mini Pro using xda premium

superb Idea.

DanielFran said:
Hi everyone,
To be able to have a full ICS Rom we need new compatible Adreno 200 libs!
Xperia X10 mini / X10 MiniPro / X8 have the same Chipset Qualcomm MSM7227 (CPU: 600 MHz ARM 11 / GPU: Adreno 200).
The idea is to request to Qualcomm to provide new libs for MSM7227 (armv6) like they provide to QSD8250 (armv7)...
Please join us in Qualcomm Developer Network site to request them these new libs here: MSM7227
Thanks
Click to expand...
Click to collapse
And there you see why the hype about the release of a set of BINARY drivers is highly overrated. Open Source driver code or bust.

I support this request and strongly believe qualcomm will support the volunteer developers.

freexperia project do not abandon the xperia x8

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.

I'm having a hard time trying to figure out which are the devices on the market supporting or not supporting neighboring cell info. and to the extent what sub-features (e.g. PSC (primary scrambling code) or cellid, and e.g. RSSI (received signal strength)) is apparently available in the supported devices:
android.telephony.NeighboringCellInfo
they are particularly important for cell tower based *location estimation*
there are various apps which allows you to query neighbor cells e.g.
Netmonitor
https://play.google.com/store/apps/details?id=com.parizene.netmonitor
GSM Signal Monitoring
https://play.google.com/store/apps/details?id=com.signalmonitoring.gsmsignalmonitoring
what is often mentioned is
http://wiki.opencellid.org/wiki/Android_library#Mobile_devices
Samsung (all devices): getNeigbouringCells () is not supported at all and always returns an empty list.
Click to expand...
Click to collapse
do your personal experience suggest that this is true?
could post your own personal observations on your particular devices and the neighbor cellinfo capabilities?
kindly state device manufacturer/make, model, o/s (e.g. GB 2.3, ICS 4.03, JB 4.3, KK 4.4 etc) as the later os has new api which to an extent supersedes this rather old but could be deemed universal api
Thanks much!

to start off
I've an old Sony (Erisson) Xperia Arc S (ICS 4.0.3) and an even older Sony Xperia X10 (GB 2.3) - they supports NeighboringCellInfo with PSC (primary scrambling code) and RSSI. however it can't get the cellid of neighbor cells.
Do you have a newer Sony device, does it support neighbor cells?
while I've 2 Samsung Galaxy S4 devices an I9505 (KK 4.4) and I9506 (JB 4.3), none of which provides neighbor cells

Android 5.0, Lollipop rollout: Xperia Z3 & Xperia Z3 Compact from today 16.03.2015
As promised way back in October 2014, Sony is now starting to roll out an upgrade to Android Lollipop for users of its existing Z3 and Z3 Compact devices.
Announced today in a blog post, it says that other Z Series products will start to get the upgrade in about two weeks. For now, it’s only Z3 and Z3 Compact devices for users in Nordic and Baltic countries, but a wider European release is expected shortly after.
the upgrade hit first devices in the Nordics and Baltics, continuing to further markets, for more Xperia Z Series products, starting in around two weeks time* – we’ll share the latest here, as it happens.
After blending Google’s first Lollipop release with our Sony software, some of the goodies include;
•Fresh, streamlined looks – based on Google’s material design, but retaining our minimalistic approach to interface and application design
•New look notifications and lock screen – with fully customizable settings, so you only get the information you really need
•Multi user profiles and guest mode – making it easy for family and friends to use your device, or the creation of dual environments for work and play…
•Android for Work – not only are business-ready Xperia smartphones and tablets unique devices for work – with waterproof form factors, great battery life and productivity features – they will now also be part of the Android for Work ecosystem
•Better storage control and customization – with the option to easily move applications from internal memory to SD card – giving you more control over your content, particularly useful for devices with slightly less space
Be sure to follow the blog and @SonyMobileNews for all the latest as our rollout continues.
*Timing and availability may vary by market and/or carrier
Source> http://blogs.sonymobile.com/2015/03...lollipop-rollout-xperia-z3-xperia-z3-compact/

Please search, there is a lollipop ? thread already
Thread closed

The Sony Xperia Z2 and Z3 devices are both amongs one of Sony's best smartphones ever that they has released. By signing this petition, we will all let Sony take action and update our precious Z2 and even Z3 devices to Android Nougat!
But what about Vulkan API support???
Anything is possible, and we will prove to Google and Sony that having the minimum requirements for software to work correctly, is plain garbage, and that Vulkan API can be left out for them, because it's not like the Vulkan API is a necessity for Nougat in order to run correctly.
ANYMORE QUESTIONS WILL BE BROUGHT UP FROM THE COMMENTS ONTO THE OP AND ANSWERED HERE.
SIGN THIS PETITION NOW!: http://bit.ly/2eEwqN5
Thanks!

I Just Want A Stable 7.0 Build For Z2

Man i think this is impossible. Qualcomm completely left the development of the SD800/801 and if Sony update our devices without permission of Google, they will be in a big trouble. To me, this is impossible.

You are totally right Little Snevil. I also think that official update it's impossible because Qualcomm processor.
Enviado do meu D6503 através de Tapatalk

Well, MAYBE it is possibile to get android 7.0 on snap 801. Just look http://www.techtimes.com/articles/1...coming-soon-geekbench-benchmark-hints-yes.htm

This is sad, but change.org never has been listed by Google or Sony, like happen with z1 and marshmallow, Xperia L and kit kat, Xperia sp and kit kat. The true is Google and Sony never listen to users, only look the sales, and for those is better for him sale the new and forget the old

what i can say in that?

@Brandon Nel
Having a petition is a good idea, and I am not against it.
But there are two questions I would like to raise before proceeding to sign the petition:
1. Our Z3 and Z2 has been released for 24 and 30 months already, this already exceed the normal aftermarket support for Android devices (usually it goes among 18 to 24 months). Although you might say there has been rule breakers recently (for instance the Xperia Z that has almost 36 months of follow up upgrade), but however there are also some far below standard devices (eg Xperia C, which has no android upgrade since release). After all, Qualcomm, Sony and any other companies still have to make money for R&D and make a living, right? So I am thinking that shouldnt we live with what we are having now (AOSP 7.0)?
2. Shouldnt Qualcomm the company you should challenge against? Vulkan and OpenGS are featured in the chipset which is manufactured by QC, not Sony!

We should petition Qualcomm & Google instead of Sony.. Sony tried their best to bring Nougat through their Beta program for Z3.
But due to the lack of chipset updates from Qualcomm and the Vulkan API requirement set by Google, so many devices have been abandoned from the update even though they are fully capable to run N. This includes Z2 & Z3.
So in this case, either Qualcomm has to release update to our chipset or we have to force Google to remove mandatory Vulkan API requirement.

i need to pls make stable nougat..........................

artsfreaky said:
i need to pls make stable nougat..........................
Click to expand...
Click to collapse
Then sign the petition and prey
Sent from my Sony D6503 using XDA Labs

Paste a link to the petition on Twitter Sony and Sony News

//This is purely an opinion, might be treated as sarcasm, but it is an opinion
1. Nougat is bad for me, it is uglier and security is even worse because of getting more strict.
2. It is nearly impossible to push this through, because now you need to actually HAVE that VulkanAPI support in order to get a cert from google to use gapps(Noone will use Vulkan straight away, because of fragmentation, but well, three billion devices run java, now three billion devices will have to run Vulkan as well and if not, they'll die)

Any effort is worthwhile haha. This should be shared in the Z3 forums!

Well, Sony published AOSP for Xperias. This might mean something, maybe they will be able to somehow get that cert.

Did you see this :
Sony is not to blame for leaving the Xperia Z3 off the Android Nougat list
http://www.xperiablog.net/2016/08/3...ng-the-xperia-z3-off-the-android-nougat-list/
All devices with SD 800/801 will not updated to Android N 7.0 , Because of Qulacomm .

Alaa | Google Android said:
Did you see this :
Sony is not to blame for leaving the Xperia Z3 off the Android Nougat list
http://www.xperiablog.net/2016/08/3...ng-the-xperia-z3-off-the-android-nougat-list/
All devices with SD 800/801 will not updated to Android N 7.0 , Because of Qulacomm .
Click to expand...
Click to collapse
Not because of Qualcomm, but because of Google. They made Vulkan obligatory for getting certs. No one is going to use it from day one of Nougat anyway, because fragmentation, they want to push APIs, but Nougat isn't like 99% of Android right now. Although it might be handy when it reaches higher shares due to Vulkan's performance.