I bought my S4A in the year of release. At that time, Android 4.2 was state of the art, but 4.2 had no BT4.0, BT LE or ANT+ support. The S4 neither had BT4.0, BT LE or ANT+ support, because it was also release with Android 4.2.
With the release of Android 4.3, android was able to handle BT4.0, BT LE and ANT+. Since samsung released official firmware based on Android 4.3 the S4 can handle those, but the S4A can only handle BT4.0 and BT LE.
We know that the S4 and S4A differ in display or camera. But what about the radio chips? As far as i know, S4 comes with a combochip which includes Bluetooth (BT<=4.0, BT LE) and also the ANT+ funcitonality. What about the radio chip in S4A ? Is this the same like the one in S4 chip?
Has any of the developers tried to bring ANT+ in the S4A up and running? Maybe this is just a question of driver optimization?
Im running cm-12-20150121-NIGHTLY-jactivelte.zip and installed the ANT+ Radio Sercive and the ANT+ Plugin from the Playstore but this was for nothing.
Does ant+ work on a S4 with CM rom?
You can enable Developer Options: system - about - multiple tap Build number. Back in System Options a new item appear. Under this menu a selection between runtime Dalvik or ART can be done. This is certainly not the same as ANT+. Perhaps other developer options offers tweaks of interest.
Not sure if this is yet implemented in CM12.
http://www.thisisant.com/business/opportunities/mobile
I9295 has the same chipset as I9505, so logically speaking if I9505 has ant+, it should work on our device with some files / patches from I9505 unless some additional patch to the kernel is required.
I do not have a ant+ device, so cannot test. If interested you can try the super Wizcyan ROM that has those files along with the ant+ (Gear manager) apps in the addon package. Additionally you could try with ktoonsez kernel for (I9505) ported by spegelius ( KT-SGS4-KK4.4-TW-eur-01.12.2015.zip)
At the moment i cant test other roms on my S4 Active.
For now, everbody can test ANT+ on ones own device, ANT+ equipment is not needed to bring the radio chip up. All you have to do is to install the following apps from the playstore:
1. ANT Radio Service (without this, ANT+ wont work; i think its the backgroundservice for ANT+)
2. ANT+ Plugins Service (API for 3rd party apps ?)
3. ANT+ Plugin Sample or ANT+ Heart Rate Grapher
First install 1. and 2.
Then use 3. to use the ANT+ radio chip. If those apps cant find ANT+-Hardware in the phone, the message "ANT Adapter not available. Built-in ANT hardware or external adapter required." will be shown.
This message will not come up if the kernel or whatever is tweaked fine and ANT hardware is ready to use.
I did some investigation and it looks like CM (or the most of custom roms) do not support ANT(+) out of the Box, no mather if its S4, S5 oder other ANT+-ready phones, but stock roms do since Android 4.3
The sources of ANT(+) are available here under the Apache Licence:
github.com / ant-wireless
Why is this not implemented in the Cyanogenmod mainline Code?
Is there a custom rom based on modified original S4 Kitkat stock rom in v4.3 or newer to test ANT+ on the S4 A?
And what about the original Samsung source codes?
The modifications for ANT must be in the original Samsung S4 Source code, because the /system/app/ANTRadioService.apk is included in the source package (open the note just right of the downloadable zip to see the files list)
opensource. samsung. com/reception/receptionSub.do?method=search&searchValue=GT-I9500
In the S4 A sourcecode the ANT.apk is missing (open the note just right of the downloadable zip to see the files list)
opensource. samsung .com/reception/receptionSub.do?method=search&searchValue=GT-I9295
Sorry for the broken links but at the moment i just have under 10 posts.
I started a general feature request in the CyanogenMod Forums under http:// forum.cyanogenmod. org/topic/104511-missing-ant-support/
You have to remember that OEM roms are not open source.
Of course, but why do you advert?
Do you because i asked for a modified stock rom?
LayerEight said:
We know that the S4 and S4A differ in display or camera. But what about the radio chips? As far as i know, S4 comes with a combochip which includes Bluetooth (BT<=4.0, BT LE) and also the ANT+ funcitonality. What about the radio chip in S4A ? Is this the same like the one in S4 chip?.
Click to expand...
Click to collapse
http://forum.xda-developers.com/hardware-hacking/hardware/ref-devices-ant-hardware-t2879990
S4 has a BCM4335, no info on the S4 Active (I can't find any)
JASONRR said:
I9295 has the same chipset as I9505, so logically speaking if I9505 has ant+, it should work on our device with some files / patches from I9505 unless some additional patch to the kernel is required.
Click to expand...
Click to collapse
See http://forum.xda-developers.com/hardware-hacking/hardware/ref-devices-ant-hardware-t2879990 the Application Processor chipset has no impact on the radio chip, and ANT+ support.
LayerEight said:
I did some investigation and it looks like CM (or the most of custom roms) do not support ANT(+) out of the Box, no mather if its S4, S5 oder other ANT+-ready phones, but stock roms do since Android 4.3
The sources of ANT(+) are available here under the Apache Licence:
github.com / ant-wireless
Why is this not implemented in the Cyanogenmod mainline Code?
Click to expand...
Click to collapse
CM does implement this (it's in the OnePlus One at least), but that is for a Qualcomm radio. The S4 uses a Broadcom part, which uses a different stack and not included in that source.
Looking at a really old version it says
As of the 4.2 build, chips using Vendor Specific Bluetooth HCI messaging for ANT packets (wl12xx and bcm433x) are not currently supported by this release. However, chip vendors may provide build support for their own products if you inquire with them.
Click to expand...
Click to collapse
while the latest just says
Before you begin, talk to your chipset vendor to ensure your chip is ANT capable, and to obtain ANT enabled firmware as well as any other chip-specific customizations you may require.
Click to expand...
Click to collapse
but I don't see BCM code in there.
It would be good to know which radio chip is in the S4 Active, but my guess is that it is one that does not support ANT+ (why else would Samsung have enabled ANT+ in the S4 and every flagship since, but not the S4 Active).
iRant said:
http://forum.xda-developers.com/hardware-hacking/hardware/ref-devices-ant-hardware-t2879990
S4 has a BCM4335, no info on the S4 Active (I can't find any)
See http://forum.xda-developers.com/hardware-hacking/hardware/ref-devices-ant-hardware-t2879990 the Application Processor chipset has no impact on the radio chip, and ANT+ support.
Click to expand...
Click to collapse
I9295 has the same bcm4335 and identical files as I9505 in system/vendor/firmware as well as the same properties as I9505 in build.prop [ro.chipname=apq8064]
JASONRR said:
I9295 has the same bcm4335 and identical files as I9505 in system/vendor/firmware as well as the same properties as I9505 in build.prop [ro.chipname=apq8064]
Click to expand...
Click to collapse
The ro.chipname doesn't look like it's associated with the radio chip, but if it is the same part, these Android patches from Garmin will be part of the puzzle: https://android-review.googlesource.com/#/q/I12f27c8b13fae8685412851f2b0cac2152bec330
Still missing the github.com/ant-wireless piece for connecting it to the ANT Radio Service, but it's a good starting point for any devs.
Edit: Sorry, i took to long with this post. Have not seen Post #11 and #12.
iRant said:
http://forum.xda-developers.com/hardware-hacking/hardware/ref-devices-ant-hardware-t2879990
S4 has a BCM4335, no info on the S4 Active (I can't find any)
Click to expand...
Click to collapse
I also searched for this information, looked on several fixit sites, but i couldnt find.
iRant said:
See http://forum.xda-developers.com/hardware-hacking/hardware/ref-devices-ant-hardware-t2879990 the Application Processor chipset has no impact on the radio chip, and ANT+ support.
Click to expand...
Click to collapse
This is very interesting. Thank you.
iRant said:
CM does implement this (it's in the OnePlus One at least), but that is for a Qualcomm radio. The S4 uses a Broadcom part, which uses a different stack and not included in that source.
Looking at a really old version it says while the latest just says but I don't see BCM code in there.
Click to expand...
Click to collapse
Yes! Seems that ANT+ was taken out of some devices which got it in CM11 in the past.
iRant said:
It would be good to know which radio chip is in the S4 Active, but my guess is that it is one that does not support ANT+ (why else would Samsung have enabled ANT+ in the S4 and every flagship since, but not the S4 Active).
Click to expand...
Click to collapse
A possible reason why the S4 Active (and possible S4 mini, S4 zoom, S4 LTE+?) is NOT ANT+ ready might be: As a manufacturer you have to certify your peace of hardware if you want a ANT+ labeled product. This certification is not for less, you have to pay for and i think, the S4 derivates are not inportant enough for Samsung to certify this phones.
Please note my thread in the ANT+ forums:
http://www.thisisant.com/forum/viewthread/4552/
Ok, i did more investigation. This is what i found:
I checked my S4 Active with CM12 Nightly installed. In /system/vendor/firmware are files for:
A300_* files (dont know for what they are)
bcm2079xB4_* (NFC Chip)
bcm4335_murata.hcd
bcm4335_prepatch.hcd
bcm4335_semco.hcd
bcm4335.hcd
vidc_1080p.fw
Bingo. I think we have a bcm4335 inside and it looks like S4 active comes with the same BT-Chip like S4.
For more research, im download the image files from sammobile from S4 4.4.2, S4 Active 4.4.2 and brand new: There is a 5.0.1 version for the rusian market for the S4 I9500.
LayerEight said:
Please note my thread in the ANT+ forums: http://www.thisisant.com/forum/viewthread/4552/
Click to expand...
Click to collapse
I (arrgh) posted some info (not really an answer) on that forum. My understanding is that the main reasoning for the certification is ensuring that the ANT+ interoperability is maintained (someone's ANT+ bike computer/phone will talk to everyone else's ANT+ heart rate strap), and getting listed in the product Directory - which is the responsibility of the ANT+ apps, not the ANT phones. Getting ANT working is the first step anyway!
LayerEight said:
Bingo. I think we have a bcm4335 inside and it looks like S4 active comes with the same BT-Chip like S4.
Click to expand...
Click to collapse
Nice work. I'm not 100% convinced, but it sure looks promising! I updated the Phones with ANT+ Hardware list.
iRant said:
I (arrgh) posted some info (not really an answer) on that forum. My understanding is that the main reasoning for the certification is ensuring that the ANT+ interoperability is maintained (someone's ANT+ bike computer/phone will talk to everyone else's ANT+ heart rate strap), and getting listed in the product Directory - which is the responsibility of the ANT+ apps, not the ANT phones. Getting ANT working is the first step anyway.
Click to expand...
Click to collapse
Thank you for this information, this ANT+ Product Certification subsite is new for me and gives me a more detailed view of the ANT+ certification process. The most of the questions i placed in the official ANT forums get answered there. Especially this information is essential:
http://www.thisisant.com/developer/ant-plus/certification-faq/category/253/
In what situations is a product sample not required?
At this time we do not require samples for the following product types:
1. Mobile platforms (i.e. smart phone, tablet etc). These products typically only require the review of the ANT communication so the test tool report is sufficient
2. Software apps (mobile app or other software which is downloadable and upgradable online).* These typically do not require samples because these types of products can be easily corrected in the field.
Click to expand...
Click to collapse
But there is also this information:
I have certified my mobile device, but we are planning to upgrade the Android OS. What is required in this situation?
For an OS upgrade, we recommend the stand alone 1000 packet slave burst test for self validation.* An Android version update should have no direct impact on ANT performance.* If the phone passes the simple regression test, there is no need to recertify the phone model.
Click to expand...
Click to collapse
In a strict sense, the point is, that S4 is ANT+ certified (and could get a custom rom with ANT+ Support immediately) while for example the S4 Active is not certified. It's not the chip which is certified, but the hole piece of hardware.
For now, this is all theory and i agree: first of all, one should get ANT running.
Nice work. I'm not 100% convinced, but it sure looks promising! I updated the Phones with ANT+ Hardware list.
Click to expand...
Click to collapse
Nice! You could update the initial post of your ANT thread with the information, that supported phones cold possibly identified by the installed drivers. With this information, people might check their phones for a potential ANT capability.
For now, i can confirm that S4 Active comes definetly with BCM4335.
I downloaded the official Samsung firmware from sammobile.com and extracted the images. I can find BMC4335 firmware files in /vendor/firmware folder.
Ill see if i can check S4 Zoom and also S4 LTE+
Just uploaded a new version of the super WizCyan ROM with the addon package. Have done some porting from S4 and got to a point where ant+ demo & ant+ sampler apps both search for devices, but since I do not have a ant+ device am unable to test the connection.
You could give it a try if you would like to. The ROM is a slimmed TouchWiz stock with only basics & include active display & lockscreen notifications while some of the bloatware is in ghe addon package that includes the gear manager & ant+ apps.
LayerEight said:
At the moment i cant test other roms on my S4 Active.
For now, everbody can test ANT+ on ones own device, ANT+ equipment is not needed to bring the radio chip up. All you have to do is to install the following apps from the playstore:
1. ANT Radio Service (without this, ANT+ wont work; i think its the backgroundservice for ANT+)
2. ANT+ Plugins Service (API for 3rd party apps ?)
3. ANT+ Plugin Sample or ANT+ Heart Rate Grapher
First install 1. and 2.
Then use 3. to use the ANT+ radio chip. If those apps cant find ANT+-Hardware in the phone, the message "ANT Adapter not available. Built-in ANT hardware or external adapter required." will be shown.
This message will not come up if the kernel or whatever is tweaked fine and ANT hardware is ready to use.
Click to expand...
Click to collapse
If what you have said is correct then yes S4 Active has ANT+ hardware as I have got both ANT+ Plugin Sample & ANT+ Heart Rate Grapher apps searching for devices and state no devices found
Wow, this sounds amazing! Thanks so much for your effort.
Since i posted this "how to check if ANT+ is functional"-guide, i found out, that there is a easier and probably safer way.
Please go to https://github.com/ant-wireless/ANT-Android-SDKs/tree/master/ANT_Android_SDK/Tools and install Android_ANTSupportChecker_1-2-0.apk. This app will run an ANT+ selftest. It will show you if everthing is implemented fine. Can you upload a screenshot of this app please?
Ill test your rom with some ANT+ hardware in the next days.
LayerEight said:
Wow, this sounds amazing! Thanks so much for your effort.
Since i posted this "how to check if ANT+ is functional"-guide, i found out, that there is a easier and probably safer way.
Please go to https://github.com/ant-wireless/ANT-Android-SDKs/tree/master/ANT_Android_SDK/Tools and install Android_ANTSupportChecker_1-2-0.apk. This app will run an ANT+ selftest. It will show you if everthing is implemented fine. Can you upload a screenshot of this app please?
Ill test your rom with some ANT+ hardware in the next days.
Click to expand...
Click to collapse
Here it is
Edit: replace the attached apk in /system/priv-app of the ROM package before install to enable/disable ant radio in airplane mode (will work only on clean install OR if you erase data for settings provider after initial setup)
Related
Does anyone know which FM Radio chip the Note has ?
My guess is a Silicon Labs dedicated FM chip, as is in the Galaxy S and S2 models. Perhaps it's accessible via /dev/fmradio.
If you call 5" a tablet, I think this Note may be the first major manufacturer tablet with officially supported FM radio. There are some esoteric Chinese tabs that support FM, and the original Dell Streak 5" has FM, but was never officially supported.
Can someone try the FM TwoO app and report if it works ? : https://market.android.com/details?id=ca.gc.crc.fmtwoo
I am also very interested to know if my FM app runs on this device, rooted or not: https://market.android.com/details?id=com.mikersmicros.fm
Thanks !
Someone has sent me debug logs (Thanks !) so I don't need any more. This device does have a Silicon Labs FM chip, and it appears that my app is working, although the emailer didn't say. He set Menu->Settings->Audio->Method to "Samsung2". It's possible "Samsung" would also work on a stock device.
Other than my curiousity about FM TwoO working, my question is answered. I'm tempted to close this thread, since I'm not here to try and promote my app, but I'll leave it open for now at least, should anyone want to discuss FM on this device, as appropriate for a Q & A forum. (?)
BTW, I get the impression that the Samsung FM app is better than other stock FM apps. It supports RDS, and I think AF, and on this device at least it seems to support recording, which I'm not sure any other FM app does.
hello
as i was already searching for any alternative FM Radio app that does not stream from the internet as there are millions and millions of streaming apps out there it was impossible for me to find them in the android market.
I liked the alternative radio app for my old Windows Mobile Device.
Now i own a Galaxy Note and tried the two apps
FM TwoO and Spirit FM Free.
It finds Radio Stations etc. But i get no sound from both apps.
I think i tried every possible sound setting.
I have Root on my Device but everything else is stock.
Is it supposed to not work on the Stock rom or can i help you with something like a debug output so your app can work on this device?
Just tell me
beowulf6 said:
hello
as i was already searching for any alternative FM Radio app that does not stream from the internet as there are millions and millions of streaming apps out there it was impossible for me to find them in the android market
Click to expand...
Click to collapse
Hi. There are almost no alternative FM apps for Android because Google refused and still refuses to provide an API. Just about every phone and chip manufacturer does FM differently and keeps their methods secret so it requires reverse engineering, which is very difficult and time consuming.
The CyanogenMod and MIUI ROMs have their own FM apps (for some devices only). FM TwoO works on some Galaxy S/S2 stock ROMs. My app Spirit tries to work on as many ROMs and chips etc. as feasible.
Now i own a Galaxy Note and tried the two apps
FM TwoO and Spirit FM Free.
It finds Radio Stations etc. But i get no sound from both apps.
I think i tried every possible sound setting.
I have Root on my Device but everything else is stock.
Is it supposed to not work on the Stock rom or can i help you with something like a debug output so your app can work on this device?
Just tell me
Click to expand...
Click to collapse
Finding stations etc. is the first obstacle. I'm happy to hear this works OK.
Sound is always the second obstacle; so many phones do this differently, even otherwise somewhat similar phones as Galaxy S and S2.
If the Audio Methods Samsung and Samsung2 don't work, we need a new Samsung3 method I guess. I think the S2 has the same issue. If I examine the stock FM app, and perhaps some logs, I should be able to determine what needs to be done.
Can you do this ? :
- Start the stock FM app, run for a few seconds, then stop it.
- Start my app, then send me logs with Menu->Help->EM Logs. In the email text please put "Galaxy Note" before pressing Send.
BTW, the stock S2/Note FM app seems pretty good, so I don't think you are missing too much from alternative apps at this time.
Also, I think my app may "work", more or less, if you start it while the stock app is running. I think the apps can co-exist simultaneously, but there are probably a few issues.
hello and thanks for your response.
You are right. The stock radio app is a lot better then the stock radio app on my windows mobile phone was. But still i dont like for example the really short textfield where the RDS text is written when the phone is in portait mode because most of the text is missing. It is better in landscape mode.
And of course alternatives are always good.
Your app works good when i keep the original radio app running in the background. (but i think the reception quality seems to be a bit worse with your app even on the same frequence. But i should test this more)
But it crashes as soon as i press the headphone/speaker button. Only a restart helps then to get rid of the stock radio-app and to get the radio working again.
i have send you a log file. hope it helps and keep up your work.
From my thread here: http://forum.xda-developers.com/showpost.php?p=21233829&postcount=2043
For Samsung Galaxy S, S2, Note, S3 etc:
Very experimental support for stock and stock derived ROMs with the Samsung Proprietary API. Works OK on my Galaxy S with Darky ROM Extreme Edition 10.2.
- Enable Settings->Debug->SA Proprietary.
- Restart the app.
http://www.mediafire.com/file/a12sm7m13smbjub/Spirit_FM_Radio_v120110.apk
- The Audio->Method is best set to the default of CyanogenMod, but might also work on Samsung, or even None or GalaxyS ALSA as a last resort.
Next release I'll re-enable the recording code and I think it will work on the Note, but might also work on Galaxy S/S2 devices.
If it works or not, please send me a log, best with SU/root:
Select Menu->Help-EM Logs, wait a few seconds, enter "Note" in the email text and press send.
I wish I could afford one of these Notes...
New release posted here: http://forum.xda-developers.com/showpost.php?p=21353990&postcount=2057
Jan 13: http://www.mediafire.com/file/52jo7vwy63576da/Spirit_FM_Radio_v120113.apk
Another shot at Samsung Proprietary support for Galaxy S2 / Note class devices, in addition to Galaxy S devices w/ FM.
As before, enable Settings-Debug->SA Proprietary and restart. SU/Root should not be needed.
Regards,
Mike.
At least one person reports this working on a a Galaxy S2. Please let me know, positive or negative.
I could REALLY use some help testing my FM app on a Note or S2 with a stock or stock derived ROM on which the stock FM app works.
I can't afford one, US/Canada versions have no FM anyway, and Samsung's Remote Test Lab seems just about useless.
The Remote Note I tried started the Feb 26 Market version of my app in the Proprietary FM API mode OK, so I think it's close to working, but that API requires an earphone/antenna plugged in, and the test device doesn't have that. And I can't get the debug logs or shell access either.
There's a Feb 28 version linked here: http://forum.xda-developers.com/showpost.php?p=23059662&postcount=2357
For a few weeks now, my app works on my Galaxy S with stock derived Darky ROMs using the Samsung API, and un-rooted.
Thanks !
Hey i just installed Spirit UI on galaxy s2 i9100G
am running on Rom jellyBam
app opens fine , i selected S2 dig. all i hear is noise
i live in egypt its ont on reg list
what should i do ?
mikereidis said:
I could REALLY use some help testing my FM app on a Note or S2 with a stock or stock derived ROM on which the stock FM app works.
I can't afford one, US/Canada versions have no FM anyway, and Samsung's Remote Test Lab seems just about useless.
The Remote Note I tried started the Feb 26 Market version of my app in the Proprietary FM API mode OK, so I think it's close to working, but that API requires an earphone/antenna plugged in, and the test device doesn't have that. And I can't get the debug logs or shell access either.
There's a Feb 28 version linked here: http://forum.xda-developers.com/showpost.php?p=23059662&postcount=2357
For a few weeks now, my app works on my Galaxy S with stock derived Darky ROMs using the Samsung API, and un-rooted.
Thanks !
Click to expand...
Click to collapse
I just downloaded. Will report soon.
Sent from my revived Galaxy Note
The first results are positive. I just listened to fm radio for about 15 minutes. It works through headphones and the speaker. But as far as I can tell the.reception seems to be somewhat worse than with the stock fm radio.
Phone is a N-7000 with stock ICS , rooted, PhilZ kernel. Are there any specific tests I should conduct?
Sent from my revived Galaxy Note
Mikereidis's post has almost one year, looking at the Spirit FM thread OT, Galaxy Note is supported since (at least) november afaik.
Hitch3ns said:
Hey i just installed Spirit UI on galaxy s2 i9100G
am running on Rom jellyBam
app opens fine , i selected S2 dig. all i hear is noise
i live in egypt its ont on reg list
what should i do ?
Click to expand...
Click to collapse
9100g is off topic here.
If it's the Unlocked version and you're a customer, then email me or post on the Q&A thread in my sig for info.
If it's the Unlocked version and you're NOT a customer, then please go away, I don't help pirates.
This thread is ancient. I've had a Note for at least 7-8 months now and it's fully supported, and will be supported by the coming Spirit2.
Please see my main thread: http://forum.xda-developers.com/showthread.php?p=13379669
I will now close this thread, thanks...
Hello,
As It's difficult to search for "ANT+" in the forums, sorry if this issue has already been addressed
And now some extra keywords to ease the search: ant, ant+, antplus, ant_plus, antwireless, ant_wireless
This is a thread to summarized all the facts about ANT+ and the Nexus 5 I have found so far:
HARDWARE: BCM4339. The Nexus 5 has this chip which provides WiFi, BT and presumably ANT+. It's also present in the Galaxy Note 3 which reportedly has ANT+ capabilities.
DRIVER: The required driver source can be found here: https://github.com/ant-wireless . Once compiled it generates a module (libantradio.so) and two apk (AntHalService.apk, ANTRadioService.apk).
SOFTWARE: There are several apps with ANT+ enabled, but for testing purposes the ANT+ demo can be used.
To be able to test ANT+ I have the Nexus 5 and ANT+ capable hardware (HRM, cadence sensor, etc), the ANT+ Demo in google play but I'm missing the driver.
I know I need a kernel with module loading enabled (for example this modified stock: http://forum.xda-developers.com/showthread.php?t=2514765) but I don't know howto to compile the ANT+ module.
Can someone generate the driver as per the instructions in https://github.com/ant-wireless/ANT_in_Android or explain me how to do it?
I'm on a linux host, I have a rather limited experience in compiling stuff but I'm not afraid of learning something in the process!
Thanks!!
very interested in the results. thank you for your work on this
interested
Subscribed.
I am also interested in this as I have my phone and Garmin Forerunner watch with me when I run so if I can just carry my phone and get the same data that would be awesome!
If no one else takes this on, I'll see about looking into it later. Keep in mind though that I'm not a developer of any sort but am comfortable with compiling kernels. I have an ANT+ HRM from my Motoactv that I'd like to use.
Ok,
So far I haven't able to compile stock kernel. I'm trying with NDK GCC 4.7 without success: http://forum.xda-developers.com/showthread.php?p=47577117
But I've investigated in other fields. I've downloaded S4 and Note3 ROMS with ANT+ support to have a look at the files.
S4 CRASH_ROM_V11: http://forum.xda-developers.com/showthread.php?t=2322619
Note3 BoBCaTROM_V2.0: http://forum.xda-developers.com/showthread.php?t=2498687
This is want I've found so far:
There are three system apps: AntHalService.apk, ANTRadioService.apk and ANTPlusPlugins.apk. These two latter can be found in google play. The first app is the one that "informs" the system that the device is ANT+ capable (as stated in the ant_wireless git). I've tried to install this apk manually but fails due to certificates (samsung).
S4, Note3 and Nexus5 have all different revisions for the bcm433x firmware but they all have an "ANTLockUsed" string in it (hexdump). Is it related to ANT+ or the ANTenna? Incidentally, the wisol firmware revision doesn't have this string.
The rest of the files related to ANT+ are for the com.dsi.ant.antradio_library (etc/permissions and framework files).
I can't find any ANT+ related module (ant*.so, libant*.so). Thus, is it already compiled in the kernel or not needed at all?
I've uploaded all these files in case anyone wants to have at look them.
Subscribed. ANT+ support would be awesome for all the athletes out there.
I'm a big supporter of ANT+. I wish I knew more about Android to help on this side. I have a blog that documents a lot of hacking projects related to ANT+.
If the Nexus 5 could access ANT+ it could be an amazing cycle computer potentially.
I work a bit with a SOC from Nordic. The way it works for BLE is that it compiles and downloads a soft protocol. I'm wondering if this is how the Boardcom chip works too. My reasoning is in the github:
Additionally, in Android 4.2, the Bluetooth stack switched to Bluedroid (from BlueZ) and this existing ANT implementation for chips using Vendor Specific Bluetooth HCI messaging for ANT packets (wl12xx and bcm433x) is currently not compatible, until somebody is able to do the work for the different bluetooth stacks. The chip vendors may provide build support for their own products if you inquire with them.
Click to expand...
Click to collapse
So it sounds like, because ANT+ and BLE are so similar, they upload a new stack to the chip which enables it. However, this stack is not in the wild.
kwakeham said:
So it sounds like, because ANT+ and BLE are so similar, they upload a new stack to the chip which enables it. However, this stack is not in the wild.
Click to expand...
Click to collapse
That makes sense as I wasn't able to find any more files related to ANT+ (directly not by looking into the source code).
However, I'm very stubborn and I want ANT+ in the nexus :silly:
First of all: It still doesn't work, but so far I've learnt a few things.
First I copied the Note3 files (attached) related to ANT+ (root needed, remember to chmod 644):
/system/app/AntHalService.apk (modified to strip samsung certificates)
/system/etc/permissions/com.dsi.ant.antradio_library.xml
/system/framework/com.dsi.ant.antradio_library.jar
/system/vendor/firmware/bcm4335_A0.hcd (renamed to bcm4335c0.hcd to max nexus5 firmware name. Backup old one first!!)
Upon reboot I also installed from google play the rest of ANT+ app required.
ANT radio service: https://play.google.com/store/apps/details?id=com.dsi.ant.service.socket
ANT+ Plugins: https://play.google.com/store/apps/details?id=com.dsi.ant.plugins.antplus
ANT+ Demo: https://play.google.com/store/apps/details?id=com.dsi.ant.antplusdemo
When using the ANT+ Demo App it doesn't warn about anything missing (good!!) but when searching for the HRM I have it just fails (bad!!). It fails with either firmware (nexus or note). In any case dmesg doesn't so any info related to ANT+.
To summarize:
The previous files are needed so that androids "knows" ANT+ hardware is present, but
Something else needs to be modified. As stated by kwakeham probably the bluetooth stack.
I have no android or coding skills (or any skills at all ), but with this information I hope someone can have a look at the modified bluetooth stack of either S4 or Note3 to port those changes to Nexus5 :fingers-crossed:
I'm very confident because XDA is a great place with lots of wonderful people, fully capable of implementing ANT+ in the Nexus5.
They've done much harder things!!
Is it true that Bluetooth 4.0 can only connect to one device at a time? So, if we wanted to monitor heart rate on the phone and listen to music via bluetooth headphones, this would not be possible unless we used an ANT+ heart rate monitor, correct?
Cleanskinned said:
Is it true that Bluetooth 4.0 can only connect to one device at a time? So, if we wanted to monitor heart rate on the phone and listen to music via bluetooth headphones, this would not be possible unless we used an ANT+ heart rate monitor, correct?
Click to expand...
Click to collapse
Close but not quite.
A BT4 HR strap will only allow one device to connect to it at a time but the phone can connect to multiple BT devices at the same time. ANT+ lets an infinite number devices to connect to a single HR strap, so like your phone stashed in your pocket and a running watch on your arm. ANT+ would also allow you to read data from hundreds of sensors, though that would be more useful for a trainer at a spin class or something lol.
Exactly, and to verfy that I just connected two Bluetooth 4.0 devices with my Nexus 5. My Pebble and the fitbit Flex from my girlfriend, both worked fine simultaneously.
Btw, windows has a limit of 7 connected Bluetooth devices at a time, but that's not caused by the Bluetooth specification.
Sent from my Nexus 5 using xda app-developers app
Hello,
Still no success.
I've been looking into the source code of both S4 and Note3 opensource kernels for android version 4.3, but due to lack of coding skills I just have no idea of what to search.
The source code of bluetooth stack from these kernels and the one for nexus5 seem completely different thus it's hard to draw any conclusions. The only thing clear is that running a "grep" search into the code for "ant+", "antplus", "ant_wireless" (or similar) doesn't show any results.
It seems someone is working on having ant+ on the google editon S4: http://forum.xda-developers.com/showthread.php?t=2542922
Let's hope his work can be reused for the nexus5.
PS. I don't have enough posts yet to ping him back to this thread but I will try to use the files he has attached.
usu4rio said:
It seems someone is working on having ant+ on the google editon S4: http://forum.xda-developers.com/showthread.php?t=2542922
Let's hope his work can be reused for the nexus5.
PS. I don't have enough posts yet to ping him back to this thread but I will try to use the files he has attached.
Click to expand...
Click to collapse
That's me. I've found you looking for some info to help me out.
The main issue I'm facing is the AntHalService.apk from the vendors(Samsung,Sony) is the 3.0.0 and there were 2 updates already.
I compiled the 3.1.1 but I can't run it as a system app.
Regarding the Nexus 5, I guess that since S4 got ANT+ activated on 4.3, something in the updated radio probably activated it, and as you mentioned, no .so modules on the system.
Maybe analyzing the ANTHal code deeply might bring up some light on this.
Btw, you're Brazilian or Portuguese or Spanish? (due to your nickname)
If so, we can add each other on G+ and progress on talks to see if we can bring some light to the athlete droiders out there...
Worst case scenario you can use an USB Ant+ Stick with an OTG cable. (what I am going to do while I research for this.... )
Oh, btw, Galaxy S3 also had the hardware but Samsung never activated it...
ADD
AdrienC said:
That's me. I've found you looking for some info to help me out.
The main issue I'm facing is the AntHalService.apk from the vendors(Samsung,Sony) is the 3.0.0 and there were 2 updates already.
I compiled the 3.1.1 but I can't run it as a system app.
Regarding the Nexus 5, I guess that since S4 got ANT+ activated on 4.3, something in the updated radio probably activated it, and as you mentioned, no .so modules on the system.
Maybe analyzing the ANTHal code deeply might bring up some light on this.
Btw, you're Brazilian or Portuguese or Spanish? (due to your nickname)
If so, we can add each other on G+ and progress on talks to see if we can bring some light to the athlete droiders out there...
Worst case scenario you can use an USB Ant+ Stick with an OTG cable. (what I am going to do while I research for this.... )
Oh, btw, Galaxy S3 also had the hardware but Samsung never activated it...
Click to expand...
Click to collapse
i have a Galaxy S4 but i want to change it for Nexus 5
i hope it works
following
HI to all
I'm interesting on this too and I'm waiting how advance this to buy an nexus 5
You will try to ask on thisisant forum. there are developers from ant+ and offer some news about phones sometimes.
Waiting news, best regards to all.
Guys, I've got a message from @fcastillousfq and I think it might be of your interest my response:
fcastillousfq said:
Hey, I saw the post about getting a USB accessory for the Nexus 5 to be able to use ANT+ as a last resource, I've been searching online and can't find any for Android, only for iPhone. The only one I've found was huge and it's not for sale yet.
Could you provide me a link or the name of the accessory so I could buy it?
Thanks!
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
Sure, it the Suunto Movestick Mini + OTG Cable
Then you have to install:
https://play.google.com/store/apps/details?id=com.dsi.ant.usbservice
https://play.google.com/store/apps/details?id=com.dsi.ant.service.socket
https://play.google.com/store/apps/details?id=com.dsi.ant.plugins.antplus
https://play.google.com/store/apps/details?id=com.dsi.ant.antplusdemo (for testing)
https://play.google.com/store/apps/details?id=com.dsi.ant.antplus.grapher.heartrate (for testing)
And you're set. It's pretty easy!!
ps: forget to mention that you can use regular size ant+ usb sticks, as the one from Garmin, but I preferred this one as it's smaller.
With a bit of DIY you can make something smaller.
Thanks for the info! I'm going to look into it and probably buy it.
I'm also considering the Viiiiva, which acts as a bridge between all my Ant+ devices and Bluetooth 4. The bad thing is that there's no android app yet, in the mean time, the USB one will suffice.
Sent from my Nexus 5 using xda app-developers app
AdrienC said:
That's me. I've found you looking for some info to help me out.
The main issue I'm facing is the AntHalService.apk from the vendors(Samsung,Sony) is the 3.0.0 and there were 2 updates already.
I compiled the 3.1.1 but I can't run it as a system app.
Regarding the Nexus 5, I guess that since S4 got ANT+ activated on 4.3, something in the updated radio probably activated it, and as you mentioned, no .so modules on the system.
Maybe analyzing the ANTHal code deeply might bring up some light on this.
Btw, you're Brazilian or Portuguese or Spanish? (due to your nickname)
If so, we can add each other on G+ and progress on talks to see if we can bring some light to the athlete droiders out there...
Worst case scenario you can use an USB Ant+ Stick with an OTG cable. (what I am going to do while I research for this.... )
Oh, btw, Galaxy S3 also had the hardware but Samsung never activated it...
Click to expand...
Click to collapse
Sorry for the delay.
Yes! spanish :good:
Unfortunately I don't use G+ (or facebook or in fact any other so-called social network). I will try to be active here so we can achieve the desired ANT+ support.
Tomorrow I will have a look at the ANT+ files you compiled (posted in the other thread) and I will compare the results with the ones provided by samsung (which I somehow managed to installed but don't really know if are working or not). I will add a post with the steps I followed to make it work.
AdrienC said:
Guys, I've got a message from @fcastillousfq and I think it might be of your interest my response:
Sure, it the Suunto Movestick Mini + OTG Cable
Then you have to install:
https://play.google.com/store/apps/details?id=com.dsi.ant.usbservice
https://play.google.com/store/apps/details?id=com.dsi.ant.service.socket
https://play.google.com/store/apps/details?id=com.dsi.ant.plugins.antplus
https://play.google.com/store/apps/details?id=com.dsi.ant.antplusdemo (for testing)
https://play.google.com/store/apps/details?id=com.dsi.ant.antplus.grapher.heartrate (for testing)
And you're set. It's pretty easy!!
ps: forget to mention that you can use regular size ant+ usb sticks, as the one from Garmin, but I preferred this one as it's smaller.
With a bit of DIY you can make something smaller.
Click to expand...
Click to collapse
I also have the LARGE garmin usb stick. I successfully used it with the Razr (910xt), but if only we could make use of the internal ANT+ hardware it would be soooo convinient
usu4rio
PS. As a "last resort" I'm planning to contact Carlo Pescio, the creator of Sportablet (http://www.sportablet.com). If I were able to use the internal ANT+, I would definitively buy his software (https://play.google.com/store/apps/details?id=com.carlopescio.uploader). I hope this doesn't sound as extortion ... too much :angel:
[Challenge] Why is "because X phone won't work with Gear Manager" acceptable?
I find this hard to believe and a slightly lazy answer to a common problem. There is obviously code in the APK that refuses to work on any non-Samsung device. Dozens of threads exist with people offering up the entire Gear APK catalog, some trying to get it to work on Nexus & and others.
fOmey and others have reverse engineered the entire ROM, but no one has figured out a way to "fix" one single app to allow it to work with all phones?
Is this not a work-in-progress somewhere? It's certainly not in any thread I have found.
What are the limitations to such a venture? Has it been tried? Is there a copyright issue? What reason has this not been attempted?
Our community has done some amazing things over the years and this site is the go-to place for rooting and hacking. There has to be one sole out there willing to give this a shot.
I am, by no means, a programmer or coder. I would take this up, but I do not have the skillset. Best I can do is go through XML files and the like hoping to find "if X=Z then A" and remove it.
Ultimately this would give us the missing companion to null_ that allows notifications and interactivity (i.e. Music player controls, etc)
So-- any takers?
I have a Nexus 5, even with the app fully running, I can only get the phone call part to work - talk/listen/incoming caller contact name
The way to get around unsupported device is with the GearManagerStub apk
I've had a bit of a search through most of the code, and from what I can tell all the apks are included so can only conclude there must be something in tw framework. Or I missed something...
http://forum.xda-developers.com/showthread.php?t=2549058
Brendo said:
even with the app fully running, I can only get the phone call part to work - talk/listen/incoming caller contact name
Click to expand...
Click to collapse
This is not helped by the app. I have mine tethered to an iPhone 3gs(not by choice) and it works fine with no software at all.
styz said:
This is not helped by the app. I have mine tethered to an iPhone 3gs(not by choice) and it works fine with no software at all.
Click to expand...
Click to collapse
To load the gear manager app, it is.. You simply connected your gear via bluetooth.
The gear manager app pushes notifications to the gear.
Without the GearManagerStub.apk it fails to load, its depends on this particular app.
It's pretty simple actually - and the same reason Sense doesn't run (well) on non-HTC devices. Samsung's got a huge proprietary framework on their phones that their proprietary apps expect to be in place and depend on. So plopping Gear Manager on a phone that doesn't have the expected underlying s/w causes it to fail or deliver bits and pieces of functionality. Someone could probably figure out which pieces of Samsung's framework need to be in place but if there are a ton of them adding useless bloat (outside the Gear functionality) wouldn't it be easier just to use the Gear with a Samsung phone? And the design point Samsung's chosen (dependency on proprietary Samsung code on the phone for the Gear to work) pretty much tells you that, at least for now, they are happy with restricting Gear sales to owners of Samsung devices. Hell, the SGS4 GPe doesn't even support the Gear.
Just a personal thought, at $299 (I know, it was 30% less at T-Mobile) the Gear's a questionable investment (AKA: a "play thing") as it is. Accepting that key features (of the few provided) are missing to get it to work on a non-Samsung phone seems like a great garage project but not a very good use of $299. Just my opinion of course.
BarryH_GEG said:
It's pretty simple actually - and the same reason Sense doesn't run (well) on non-HTC devices. Samsung's got a huge proprietary framework on their phones that their proprietary apps expect to be in place and depend on. So plopping Gear Manager on a phone that doesn't have the expected underlying s/w causes it to fail or deliver bits and pieces of functionality. Someone could probably figure out which pieces of Samsung's framework need to be in place but if there are a ton of them adding useless bloat (outside the Gear functionality) wouldn't it be easier just to use the Gear with a Samsung phone? And the design point Samsung's chosen (dependency on proprietary Samsung code on the phone for the Gear to work) pretty much tells you that, at least for now, they are happy with restricting Gear sales to owners of Samsung devices. Hell, the SGS4 GPe doesn't even support the Gear.
Just a personal thought, at $299 (I know, it was 30% less at T-Mobile) the Gear's a questionable investment (AKA: a "play thing") as it is. Accepting that key features (of the few provided) are missing to get it to work on a non-Samsung phone seems like a great garage project but not a very good use of $299. Just my opinion of course.
Click to expand...
Click to collapse
I am purchasing home automation items and bluetooth adaptors for my vehicle so I don't think of this as a toy. I consider it a great step forward.
fOmey said:
...Without the GearManagerStub.apk it fails to load, its depends on this particular app.
Click to expand...
Click to collapse
I installed the stub and the gearmanager apks and it still gave me a 'unsupported device' message. *sadface*
therealduckie said:
I am purchasing home automation items and bluetooth adaptors for my vehicle so I don't think of this as a toy. I consider it a great step forward.
Click to expand...
Click to collapse
Just because you can doesn't mean you should. Why would an underpowered device with a 315mAh battery, 512MB of RAM, and a 1.63" display be the best "tool for the job" you described? Especially when it requires a host in near-by proximity for the majority of its functions? It's great what people are doing with the Gear outside the mission Samsung released it for but, like I said before, you're talking about parlor tricks more for sport than serving a function unachievable by better means; some of which are more practical. And if you're trying to use the Gear while driving, especially if you've shrunk the DPI with a launcher, good luck. It's hard enough using the basic functions and S Voice while driving without ending up in another lane. I'm not criticizing everyone's ingenuity and cleverness just pointing out how impractical some things can appear when you take in to account what the Gear really is; a shamefully low-spec, low functionality Android "phone" with a tiny screen that happens to have a wrist band.
BarryH_GEG said:
It's pretty simple actually - and the same reason Sense doesn't run (well) on non-HTC devices. Samsung's got a huge proprietary framework on their phones that their proprietary apps expect to be in place and depend on. So plopping Gear Manager on a phone that doesn't have the expected underlying s/w causes it to fail or deliver bits and pieces of functionality. Someone could probably figure out which pieces of Samsung's framework need to be in place but if there are a ton of them adding useless bloat (outside the Gear functionality) wouldn't it be easier just to use the Gear with a Samsung phone? And the design point Samsung's chosen (dependency on proprietary Samsung code on the phone for the Gear to work) pretty much tells you that, at least for now, they are happy with restricting Gear sales to owners of Samsung devices. Hell, the SGS4 GPe doesn't even support the Gear.
Just a personal thought, at $299 (I know, it was 30% less at T-Mobile) the Gear's a questionable investment (AKA: a "play thing") as it is. Accepting that key features (of the few provided) are missing to get it to work on a non-Samsung phone seems like a great garage project but not a very good use of $299. Just my opinion of course.
Click to expand...
Click to collapse
That's why this is a challenge
Im intrigued.. I want to figure this out, I prefer to use AOSP. Iv been forced to go back to TouchWiz since owning a gear.
I might have to do some more digging around.
therealduckie said:
I installed the stub and the gearmanager apks and it still gave me a 'unsupported device' message. *sadface*
Click to expand...
Click to collapse
Depends how you do it? I moved the apk to system/app and then had to install it (so that it was in data/app as com.whatever as it looks for apk based on that name). May not need it in system app anymore
Which phone?
---------- Post added at 11:08 AM ---------- Previous post was at 11:07 AM ----------
fOmey said:
That's why this is a challenge
Im intrigued.. I want to figure this out, I prefer to use AOSP. Iv been forced to go back to TouchWiz since owning a gear.
I might have to do some more digging around.
Click to expand...
Click to collapse
Do you know how much touchwiz is in google edition roms? Does gear fully work with ge roms?
Brendo said:
Depends how you do it? I moved the apk to system/app and then had to install it (so that it was in data/app as com.whatever as it looks for apk based on that name). May not need it in system app anymore
Which phone?
---------- Post added at 11:08 AM ---------- Previous post was at 11:07 AM ----------
Do you know how much touchwiz is in google edition roms? Does gear fully work with ge roms?
Click to expand...
Click to collapse
Sadly I was able to test extensively using GE, although I did find all the initial APK's installed & completed successfully.
I didn't get a chance to pair up completely, the base keeps randomly rebooting (nothing related to the gear). This could be due a modified gearmanagerstub.apk on the GE base, I'm not entirely sure.
I could easily upload a version of the stub APK, you can give it a go on your nexus ?
EDIT: GearManagerStub.apk : From KitKat Google Edition (i9505) & (Uninstall existing GearManager.apk before testing).
BarryH_GEG said:
Just because you can doesn't mean you should. Why would an underpowered device with a 315mAh battery, 512MB of RAM, and a 1.63" display be the best "tool for the job" you described? Especially when it requires a host in near-by proximity for the majority of its functions? It's great what people are doing with the Gear outside the mission Samsung released it for but, like I said before, you're talking about parlor tricks more for sport than serving a function unachievable by better means; some of which are more practical. And if you're trying to use the Gear while driving, especially if you've shrunk the DPI with a launcher, good luck. It's hard enough using the basic functions and S Voice while driving without ending up in another lane. I'm not criticizing everyone's ingenuity and cleverness just pointing out how impractical some things can appear when you take in to account what the Gear really is; a shamefully low-spec, low functionality Android "phone" with a tiny screen that happens to have a wrist band.
Click to expand...
Click to collapse
Gear, with null_, requires no host. It can also connect to bluetooth enabled devices other than a phone.
I was motivated but this: http://daisyworks.net/btgarage.html
It's brilliant and exactly what i have needed for years.
Other interesting links:
http://www.smarthome.com/android_apps.html
http://www.instructables.com/id/Home-Automation-using-Arduino-Android-Phone/
Fact is, this is not a toy when something like null_ is used. It offers a great deal more functionality in a much smaller and more portable/handy package.
Your bias against the device is obvious so it begs the question: why are you here? Just to raise your post count and stir drama in an otherwise peaceful sub-group? Or, do you own it and you are so disappointed that you refuse to see its potential?
Either way, your negativity will not sway me or change my mind. I know it has potential and I plan to use it fully. The fact that it has a wristband is a feature and a plus.
Oh, and I don't consider something that has multiple times the computing power of the original Apollo moon landings "low specs". <3
fOmey said:
To load the gear manager app, it is.. You simply connected your gear via bluetooth.
The gear manager app pushes notifications to the gear.
Without the GearManagerStub.apk it fails to load, its depends on this particular app.
Click to expand...
Click to collapse
Maybe i wasn't clear in my post. I was responding to the phone call portion of the gear. Even without the software installed it still allows the phone calls to be taken and shows the contact information on the watch just like it did on the g4s with the app. All i was saying is that he commented that he was only able to get the phone portion working with the app and i was explaining that you can do that without the app.
fOmey said:
EDIT: GearManagerStub.apk : From KitKat Google Edition (i9505) & (Uninstall existing GearManager.apk before testing).
Click to expand...
Click to collapse
Tried it. Same result. 2 gear manager apps still refuse to install - music and weather (I believe because they reply on specific apps?). Nfc setup connection still works. App still works, but no details get sent to watch. Perhaps tw framework hooks in and serves data to gearmanagerstub, then stub sends to manager, which sends to watch?
---------- Post added at 11:48 AM ---------- Previous post was at 11:47 AM ----------
styz said:
Maybe i wasn't clear in my post. I was responding to the phone call portion of the gear. Even without the software installed it still allows the phone calls to be taken and shows the contact information on the watch just like it did on the g4s with the app. All i was saying is that he commented that he was only able to get the phone portion working with the app and i was explaining that you can do that without the app.
Click to expand...
Click to collapse
Yes, from what I understand, the Bluetooth headset part is the only 'generic' part of the watch. It receives data just like a car headset when it displays contact info etc
Just installed that STUB with both the 1.5 and 1.2 GM and both still showed me a 'device not supported" error message.
I spent about 2 hours with Samsung one night and they told me it had to do with baseband version...or that mine was a 4.1 baseband (even though I am running CM 10.2 with 4.3 OS).
Perhaps there is a lockout on older baseband versions?
This is an SG3 phone, by the way.
therealduckie said:
Just installed that STUB with both the 1.5 and 1.2 GM and both still showed me a 'device not supported" error message.
I spent about 2 hours with Samsung one night and they told me it had to do with baseband version...or that mine was a 4.1 baseband (even though I am running CM 10.2 with 4.3 OS).
Perhaps there is a lockout on older baseband versions?
This is an SG3 phone, by the way.
Click to expand...
Click to collapse
How did you install? Try deleting; move to system/app; installing from system/app
Brendo said:
How did you install? Try deleting; move to system/app; installing from system/app
Click to expand...
Click to collapse
Sorry, I should have been more clear...
I installed them both fine. It's when i try to pair the Gear that I get that message.
therealduckie said:
Sorry, I should have been more clear...
I installed them both fine. It's when i try to pair the Gear that I get that message.
Click to expand...
Click to collapse
Did you delete the touchwiz launcher off your gear ? That will cause a unsupported device error also.. learnt this the hard way !
Brendo said:
Tried it. Same result. 2 gear manager apps still refuse to install - music and weather (I believe because they reply on specific apps?). Nfc setup connection still works. App still works, but no details get sent to watch. Perhaps tw framework hooks in and serves data to gearmanagerstub, then stub sends to manager, which sends to watch?
Click to expand...
Click to collapse
If you can narrow down which two of those APK's dont install, I can try figure out why.. First step on getting this working is simply identifying what exactly is not working and why.
Once we can get gearmanager running on other branded phones, I'm confident the notifications may work.. or atleast the "more notifications".
fOmey said:
Did you delete the touchwiz launcher off your gear ? That will cause a unsupported device error also.. learnt this the hard way !
Click to expand...
Click to collapse
I'm using Nova Launcher as my launcher on my phone. TouchWiz doesn't even load on boot, that I am aware of.
fOmey said:
Did you delete the touchwiz launcher off your gear ? That will cause a unsupported device error also.. learnt this the hard way !
Click to expand...
Click to collapse
Really? I still have tw on my gear :s
If you can narrow down which two of those APK's dont install, I can try figure out why.. First step on getting this working is simply identifying what exactly is not working and why.
Once we can get gearmanager running on other branded phones, I'm confident the notifications may work.. or atleast the "more notifications".
Click to expand...
Click to collapse
I still have to install all the extra apks manually
- SAMusicProvider_signed.apk
- SAWeatherProvider_signed.apk
have been using this rom since a month without problems and i got the "P" version of i9100 with nfc included, but obviously it not working with this rom. i'm thinking about of the implemetation on kernel of this option for i9100P users like me. i have been reading about that in xda, and i found this thread:
http://forum.xda-developers.com/showthread.php?t=1822447
but, its not continuous or seems to be stopped.
could be this feature implemented someday?
i think i found the driver of nfc chipset ,https://android.googlesource.com/ke...7456ef92735a1257c95eac44/drivers/misc/pn544.c
Edray said:
have been using this rom since a month without problems and i got the "P" version of i9100 with nfc included, but obviously it not working with this rom. i'm thinking about of the implemetation on kernel of this option for i9100P users like me. i have been reading about that in xda, and i found this thread:
http://forum.xda-developers.com/showthread.php?t=1822447
but, its not continuous or seems to be stopped.
could be this feature implemented someday?
i think i found the driver of nfc chipset ,https://android.googlesource.com/ke...7456ef92735a1257c95eac44/drivers/misc/pn544.c
Click to expand...
Click to collapse
The main problem is handling the fact that some of the NFC stuff behaves VERY badly if put into a device that doesn't have the hardware.
No one ever figured out a way to get it added to the P without either having a separate build or breaking the non-P I9100.
Although with the new infrstructure for "unified" device builds, this might now be possible.
As an FYI, the I777 (which REQUIRES a different build due to having different call audio, touchkeys, and a few other things) has NFC. The main blocker on the P was not wanting to create yet another build.
and it will be not possible a flashable zip with NFC enabler, and a script like superSU for not being erased by the updates?
thanks for your reply:good:
Edray said:
and it will be not possible a flashable zip with NFC enabler, and a script like superSU for not being erased by the updates?
thanks for your reply:good:
Click to expand...
Click to collapse
We don't do separate flashable ZIPs and stuff like that. Our build system doesn't support it, among other things.
One more in the request
I join to the kind request for this feature. As you know, NFC is now of use for payment and ID (to enter your office, for example), so I hope it makes sense for you to consider the effort and risk of creating a separate version in a near future. I can't adopt any ROM wo NFC unless I carry additional ID/VISA cards (2 more in my crowded wallet).
bajajel said:
I join to the kind request for this feature. As you know, NFC is now of use for payment and ID (to enter your office, for example), so I hope it makes sense for you to consider the effort and risk of creating a separate version in a near future. I can't adopt any ROM wo NFC unless I carry additional ID/VISA cards (2 more in my crowded wallet).
Click to expand...
Click to collapse
Sorry, but adding NFC to the I9100P won't help you here.
AOSP is missing HCE support for any device with an NXP NFC chipset. Until that changes, the I777/I9100P will not be payment capable even if NFC is added for P builds.
I just found out that the HTC One M7 has hardware support for ANT+. I downloaded the ANT+ Enabler app from the play store and now my fitness apps detect my ANT+ HRM. Is there any work being done to incorporate this into any of the current ROMS?
Thanks
+1 for amt+ maybe HTC have to pay royalty to Garmin if they enable it
CyanogenMod picked up the ANT+ repositories (for the OnePlus One), so someone just needs to turn it on in the M7.
There's no royalty as the code is open source on the ANT Wireless GitHub.
Edit: Actually its only that simple for the M8. M7 needs some more work for the Broadcom chip. I will try and get some information up.
http://forum.xda-developers.com/hardware-hacking/hardware/ref-devices-ant-hardware-t2879990