Bluetooth ble 4.0 and Android, I'm lost! - Android Studio

I am using a hm-10 to connect to my Android test application. Unfortunately, is a big struggle compared to the hc-05 device. Anyway. The "samplegatt" does not work, either with my device or for whatever reason. So I found a different blog that explains the sample must be modified:
(the dumb forum won't allow me to post a link)
ayh tee tee pee android-er.blogspot.com/2015/12/connect-hm-10-ble-module-to-android.html?showComment=1454055306623#c9017603593836048433
So after the modifications, THAT won't work either. It's not the first one, just the most recent.... I have tried so many example applications from google searching, I have saturated my efforts. I KNOW the module can work with my phone, from using a ble test application from play store (that I can't seem to find company website or track down the source code for).
I was hoping to know if anyone else struggled with this, and if you can advise me on how / where to get a working sample application.

It turns out, the new changes for sdk version 23 require all types of permission changes in the code, since someone decided it was a good idea to enable gps location in order to use bluetooth. I had to change my target sdk back to 22 and the samples started working.

Related

On-Device App Install and Maybe Bluetooth

I had some issues with the ADB commands for preparing my rooted Nook Color for on-device app install (primarily due to microcrap's 64-bit Vista) so I found a very easy method.
In the Market, there's an app called "Sqlite Editor" from the folks who make "Root Explorer" - it's about $3.07 US$ but I bought it anyway.
With this [AFTER A BACKUP!] I was able to directly edit the settings.db (sub category SECURE) and change the following:
'install_non_market_apps' from the default value of 0 to 1 and following a SAVE and REBOOT I can now install directly from my SD Card.
While I was doing this, I find a large number of additional entries including (are you ready for this???) bluetooth_on!
Dare I do this???
I also posted this in Mobileread's excellent Nook Color Forum and I was thinking that may we should also acknowledge them as a great forum for our beloved Nooks!
docfreed said:
While I was doing this, I find a large number of additional entries including (are you ready for this???) bluetooth_on!
Dare I do this???
Click to expand...
Click to collapse
LOL...If only it were this easy.
I had no issue with installing apps from the sd card after rooting/installing mkt and gapps.
Depends on How You Rooted..
I'm not certain but some rooting methods have market/gapps built-in, some don't. I used Autonooter (after upgrading to 1.01) and market & Gmail just appeared - I never had to install anything else.
If you used Autonooter then you wouldn't have to do anything to be able to install non market apps. Maybe just toggle the setting in Nook Tools if anything.
docfreed said:
While I was doing this, I find a large number of additional entries including (are you ready for this???) bluetooth_on!
Click to expand...
Click to collapse
Its NOT that simple, its been turned on in the kernel & custom ones built for it with nothing.
If you see the "salting nook" posts so much as been done trying to get it to work, most expect something ground breaking to come from actually looking at the pins on the chip it self an connection through the MoBo.
Amd sold faulty quad cores as triples so it could be that the chip/Mobo cant do it. Could be a easy hardware mod but TBH so much deep thought an attempts have been seen in IRC i dont see a "virtual fix" anytime soon.
But that said im an idiot so could be 475% wrong
Yeah, I tried toggling Nook Color Tools per the instructions - never seemed to work for me. Anyway, it appears to be just a one-shot adjustment any way it's done (at least till we get FroYo) so I'm happy.
Merry XMAS everyone
docfreed
sqlite not working for me
Purchased Sqlite, when trying to install, exits without loading apps. Any suggestions? Rooted with older booker and then re-rooted with pre 1.01 autonooker. Thanks. -
I have a kernel and u-boot that enables the bluetooth portion of the module and sets up an rfkill device. hciattach will detect it as a TI Bluetooth module and will load one of the TI bluetooth firmware scripts, but then complains about a missing socket or something. It sounds like a software error more than anything that might be wrong with the hardware.
What this means is that the Bluetooth part of the WiFi module isn't just left disconnected and the link to the CPU is working. But we don't know if the antenna is set up to share between wifi and Bluetooth or if the hardware is otherwise missing something that would keep it from working.
If you have experience with getting TI WiLink Bluetooth working in Android or Linux, or know someone who does, PM me or join us on Freenode channel #nookie. We're really close!

Nexus 7 - WiFi Ad-Hoc fix for wpa_supplicant?

Update March 25, 2013:
Solved!! The folks over at Thinktube Inc. have developed a fix and submitted it to CyanogenMod and AOSP for merging into their code:
http://b-real.org/2013/ad-hoc-ibss-m...h-cyanogenmod/
http://www.thinktube.com/android-tech/46-android-wifi-ibss
Essentially the EASIEST solution is to ROOT your phone, and install the CyanogenMod nightly as of March 25 or later (note: you will have to wait until the nightly is actually BUILT, since as of today it is not ready yet).
I have not tested this solution out myself, however others within this thread have confirmed it working.
Please if anyone develops a easier patch or a step-by-step for people who do NOT want to use CyanogenMod, post and I will update the OP
Cheers!
WiKiD24
-------------------------------------------------------
Update Oct 9, 2012:
- Nexus 7 v4.1.2 did not add Wi-Fi Ad-Hoc Support with the stock update from Google.
To do: Check if any WPA-Supplicant changes previously tested in v4.1.1 now work in 4.1.2
- Workaround (Recommended): Bluetooth Tethering to Nexus 7 Tablet (via Bluetooth DUN Profile). "BlueVPN" from Google Play Store.
Tested successfully on many Nokia Symbian phones (N7, E71, E72), and others.
However, many applications on Nexus 7 Tablet do not support it (without fixes from the developers)
Confirmed working applications:
- Pulse
- Google Chrome
- Dolphin Browser
- Facebook
- Ebuddy
- Youtube
- Others (I am too lazy to add them all)
Confirmed NOT working applications:
- Gmail
- Email
- Google Search
- Google Play Store
- Dropbox
- Words with Friends
- Scramble with Friends
- Others (I am too lazy to add them all)
More details can be found here: http://forum.xda-developers.com/showpost.php?p=29763582&postcount=27
Issue: Sometimes the phone/tablet do not connect (randomly), due to issues with either the phone or the tablet.
To resolve: Turn on and off bluetooth on phone, Turn on & off bluetooth on tablet. Try again. If does not work, reboot phone and tablet and try again. Should work.
-Workaround: Android Phone to Nexus 7 Tablet (via "FoxFI" App on Phone, "FoxFi Addon" App on Tablet, or via "PDANet", or via "Wireless Tether App")
http://forum.xda-developers.com/showpost.php?p=29763582&postcount=27
- Workaround: USB Tethering ANY Phone to Nexus 7 Tablet (via "PPP Widget" App on Tablet, requires rooted Nexus 7)
http://forum.xda-developers.com/showpost.php?p=32431103&postcount=51
- Workaround: Windows WiFi Laptop Tethering to Nexus 7 Tablet
http://www.youtube.com/watch?v=klHzMyYFGeQ
-------------------------------------------------------
Hi All,
I've just recently gotten a Nexus 7 and need to be able to enable Ad-Hoc wifi on the tablet.
I also own a Asus TF101 and previously had the same problem however there was a fix for that.
The solution was to replace the wpa_supplicant file in the /system/bin folder, however I do not know the code to change it.
If anyone has the technical know-how, they would be able to reverse-engineer it and apply the same fix.
http://forum.xda-developers.com/showthread.php?t=1370955
http://szym.net/2010/12/adhoc-wifi-in-android/
http://www.slatedroid.com/topic/2752...less-hotspots/
http://www.olsr.org/?q=olsr_on_android
http://hostap.epitest.fi/gitweb/gitw...upplicant.conf
I posted a possible solution in QnA section. Thread title is similar to this one. Check it out. Doesn't involve any coding. Prime had a similar issue on a few firmware updates. This was solved for us(before Asus came around to enabling it themselves) by adding in a wifi supplicant file and renaming an older one. Then setting permissions on the new file. Here is the link to that thread. There's a good chance it will work without the file needing to be modded. It came from a galaxy tab LR something and worked fine on prime. Its worth checking out.
http://forum.xda-developers.com/showthread.php?t=1438297
thanks for the tip and I tried it out, which is essentially the same type of solution but it didn't think work as there is no wpa_supplicant2 file in the nexus 7.
http://forum.xda-developers.com/showthread.php?t=1777413
here's some more useful information for enabling ad hoc:
http://szym.net/2010/12/adhoc-wifi-in-android/
http://www.slatedroid.com/topic/27522-howto-connect-to-ad-hoc-wireless-hotspots/
http://www.olsr.org/?q=olsr_on_android
http://hostap.epitest.fi/gitweb/git...ob_plain;f=wpa_supplicant/wpa_supplicant.conf
I'm doing what I can right now to try and enable it.
Some more experienced android users whom know what they're doing would be better than me trying it out, though!!
Did any of those sources of information get you any closer to enabling ad-hoc?
Just FYI that Nexus S "ad hoc enabling file" doesn't work on NS with Jelly Bean.
nexususer0101 said:
Did any of those sources of information get you any closer to enabling ad-hoc?
Click to expand...
Click to collapse
None yet, I need some help to do so. There is a file called "wpa_cli" that I need copied from another device, because I can't find it on the internet.
If anyone could find it in their "/system/bin" folder and attach it to this tread, I could certainly try it.
I've also requested the same thing in the Q&A forum here: http://forum.xda-developers.com/showthread.php?t=1793437
Bumping; I have the same condition. I'm in Italy and bought an internet package for my laptop--I'm sharing it with all my other devices but the N7 doesn't see the adhoc connection. Like OP said, I had a Transformer TF101 and remember flashing a file to fix it.
Thanks in advance.
Just an FYI: Also checked my GNex for a wpa_cli and came up empty.
Just wanted to give quick update, i have not been able to find anyone to help me and also my life is kinda hectic right now... Hopefully someone will be able to pick up where I left off, in the meantime my nexus 7 is pretty much useless to me until resolved.
One more "me too".
I'm here to share my sympathy to everyone else's pain as I have a nexus 7 that I can't connect to my phone's adhoc Hotspot. I have also posted my query in Android Central, but no one seems to have been able to know a fix as of yet. (topic can be found here: Android Forums at AndroidCentral.com > Google Nexus 7 Tablet Forum > Nexus 7 Rooting ROM's & Hack's > *** CONNECTING TO Adhoc WiFi WITH THE NEXUS 7 ***)
As I said in that thread.. not being able to connect to phones hotspot makes my beautiful nexus 7 feel like a handicapped tablet.
wikid24 said:
Just wanted to give quick update, i have not been able to find anyone to help me and also my life is kinda hectic right now... Hopefully someone will be able to pick up where I left off, in the meantime my nexus 7 is pretty much useless to me until resolved.
Click to expand...
Click to collapse
I haven't seen any reports/posts of people checking out or trying what I mentioned in post #2..lol. on prime we had this exact same problem. Then we found the supplicant file to replace one we had and then adhoc tethering worked after that. You only need to be rooted to do this as you need to rename a file and insert new supplicant in there and set permissions. You can always backup and rename original file. So if it doesn't work, you can easily revert back to stock file. I have a feeling this new file will work. Just haven't tried myself yet as I haven't brought tablet outdoors yet to need tethering. I might eventually see if it works if no one else does.
Look at the thread I linked in second post and you will see prime owners had exact same problem and we solved it. It worked for the transformer 300 also. Will likely work for nexus 7 also. The file is, in a sense, universal.
demandarin said:
I haven't seen any reports/posts of people checking out or trying what I mentioned in post #2..lol. .
Click to expand...
Click to collapse
I have tried. It does not work -- WiFi refuses to turn back on with this new supplicant file. And yes, I made sure to follow your instructions exactly as described in the procedure.
With the N7, there is no such thing as a wpa_supplicant2 file originally in /system/bin (only the one without the '2' exists in the N7 which is the one running the show here, I know this for a fact as when restoring this file, the WiFi in the N7 becomes functional again). So I tried this same file you provide both with and without the '2', with no better results.
I suspect that only a developer that knows what he's doing would be able to come up with a new wpa_supplicant file specifically tweaked for the N7 (as opposed to using one that did the trick for the Prime or for the Xoom or whathaveyou).
Thanks for the suggested idea though... anything else you think we should try?
rdelfin said:
I have tried. It does not work -- WiFi refuses to turn back on with this new supplicant file. And yes, I made sure to follow your instructions exactly as described in the procedure.
With the N7, there is no such thing as a wpa_supplicant2 file originally in /system/bin (only the one without the '2' exists in the N7 which is the one running the show here, I know this for a fact as when restoring this file, the WiFi in the N7 becomes functional again). So I tried this same file you provide both with and without the '2', with no better results.
I suspect that only a developer that knows what he's doing would be able to come up with a new wpa_supplicant file specifically tweaked for the N7 (as opposed to using one that did the trick for the Prime or for the Xoom or whathaveyou).
Thanks for the suggested idea though... anything else you think we should try?
Click to expand...
Click to collapse
They likely will implement it through a future update. Hopefully that's sooner than later. Ill ask motley, kernel developer.
I toyed with this for a while...
If you install Power Controls (Power Controls) you can add a button that turns on the Wifi Hotspot.
Problems:
you cant change any settings in current settings UI
Appears to be default "Android_AP" SSID and whatever the default password is (i dont recall if this is a random code or not)
Its a start!
Demented-Idiot said:
I toyed with this for a while...
If you install Power Controls you can add a button that turns on the Wifi Hotspot.
Problems:
you cant change any settings in current settings UI
Appears to be default "Android_AP" SSID and whatever the default password is (i dont recall if this is a random code or not)
Its a start!
Click to expand...
Click to collapse
Could you explain exactly what this does? I didn't understand what it is being implied with this being a start? with this you can actually connect to adhoc?
idk if anyone has looked...but has anyone looked into editing the Wifi-Direct api to make adhoc networks visible in there? Since wifi-direct is made for p2p connections. it's android.net.wifi.p2p.WifiP2pManager info about it is here http://developer.android.com/guide/topics/connectivity/wifip2p.html like I said...don't know if it's much help
I also wanted to post a quick reply, since I've been an insomniac yesterday.
From my previous posts I posted this link here as well, I edited the wpa_supplicant.conf file from the /system/etc/wifi folder and modified with the following settings, however I don't think that it even reads the wpa_supplicant.conf file either. Can anyone either confirm or deny that the wpa_supplicant.conf file is being used on the N7??
-------------------
update_config=1
ctrl_interface=wlan0
eapol_version=1
ap_scan=2
fast_reauth=1
network={
ssid="Bondphone"
mode=1
frequency=2412
key_mgmt=NONE
wep_key0="1234567890123"
wep_key1=1234567890123
wep_tx_keyidx=1
priority=3
auth_alg=SHARED
}
------------------------
wikid24: I don't know if N7 (or my NS) reads this file but it definitely reads /data/misc/wifi/wpa_supplicant.conf. Only problem is that I can't turn wifi on after ANY change in this file. Sometimes even if I revert my backup file, wifi won't launch and I must delete it to make wifi working again.
I found this thread on XDA
http://forum.xda-developers.com/showthread.php?t=1806937
It is edited wpa_supplicant file for Asus Transformer but it allows me to turn on wifi even on NS. But it doesn't show me any ad hoc networks. Maybe with non-stock kernel...?
And I also found ad hoc patch for source code of older version of wpa_supplicant. But I'm not able to try if it is possible to apply it on JB version too.
http://szym.net/android/wpa_supplicant-ibss.patch
jenda.69 said:
wikid24: I don't know if N7 (or my NS) reads this file but it definitely reads /data/misc/wifi/wpa_supplicant.conf. Only problem is that I can't turn wifi on after ANY change in this file. Sometimes even if I revert my backup file, wifi won't launch and I must delete it to make wifi working again.
I found this thread on XDA
http://forum.xda-developers.com/showthread.php?t=1806937
It is edited wpa_supplicant file for Asus Transformer but it allows me to turn on wifi even on NS. But it doesn't show me any ad hoc networks. Maybe with non-stock kernel...?
And I also found ad hoc patch for source code of older version of wpa_supplicant. But I'm not able to try if it is possible to apply it on JB version too.
http://szym.net/android/wpa_supplicant-ibss.patch
Click to expand...
Click to collapse
jenda, I think you may have solved a big piece to the puzzle!!
You can copy the file to another directory, and THAN you can open the file! I noticed I had all my pre-saved wifi addresses in this file!
If someone can please copy the "/data/misc/wifi/wpa_supplicant.conf" file to another directory, modify it, than overwrite the old file, it should work!! *fingers crossed*
(unfortunately I am busy for a few days, don't know if I'll be able to make the change for a while)

ANT+ on the Nexus 5

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:

[Q] [WP8.1] share gps location over bluetooth

is it going to be possible? anybody know?
Do you mean continuously (as in, use the phone as a Bluetooth GPS speaking a protocol like NMEA)? I don't believe it's built in, but you could probably write an app to do it (the BT interface is, I think, available to app developers). There might even already be such an app.
Do you mean one-time (like the way you can send your location in an SMS, but via Bluetooth instead)? Nothing I know of comes to mind, so you'd probably need an app for that too. That one seems less useful, though; most devices that have BT either already have their own GPS (or otherwise know approximately where they are anyhow) or are trying to track their own motion and would want continuous updates.
GoodDayToDie said:
Do you mean continuously (as in, use the phone as a Bluetooth GPS speaking a protocol like NMEA)? I don't believe it's built in, but you could probably write an app to do it (the BT interface is, I think, available to app developers). There might even already be such an app.
Do you mean one-time (like the way you can send your location in an SMS, but via Bluetooth instead)? Nothing I know of comes to mind, so you'd probably need an app for that too. That one seems less useful, though; most devices that have BT either already have their own GPS (or otherwise know approximately where they are anyhow) or are trying to track their own motion and would want continuous updates.
Click to expand...
Click to collapse
continuously, sharing GPS location with another device over Bluetooth. I wish I could write an app like that but I can't program
thanks for the answer gd2d, I hope its possible. I also hope that the ability/app is not limited to having to be active and not running in the background (ie get a text, respond to it and lose your location)
p.s. No app "currently" exists,,,,, at least from what I've searched in the store
BTW, WP8.1 isn't out yet, or even in public pre-release. We know some of the features that will be added, but not all of them. To the best of my knowledge, this isn't on the known list. Anyhow, WP8.1 won't release for probably another few months, even in preview form (though I could be mistaken).
GoodDayToDie said:
BTW, WP8.1 isn't out yet, or even in public pre-release. We know some of the features that will be added, but not all of them. To the best of my knowledge, this isn't on the known list. Anyhow, WP8.1 won't release for probably another few months, even in preview form (though I could be mistaken).
Click to expand...
Click to collapse
I know, I am just curious, with all the SDK info that is out I thought somebody might know something

[NST/G] R.I.P. WeatherACE for the Nook Simple Touch

Another one bites the dust.
It took awhile for Wunderground's API to actually die, but it finally did and I used my last data point yesterday. None of the other APIs in the app (OpenWeatherMap, Norwegian MET, Yahoo) have worked for awhile. I tried the obvious with OWM and N-MET, getting new API strings, decompiling the app, replacing the APIs and stitching it all back together. But no joy. The data structures in the new APIs are probably different and that's way beyond me. The jiggered app ran, but it was unable to gather data from anywhere (other than what my location is).
Too bad. Nothing left like it, AFAIK.
Yeah, I'm bummed. Weather Ace was one of the few apps that had nice widgets appropriate for the eInk screen.
scotte9999 said:
Yeah, I'm bummed. Weather Ace was one of the few apps that had nice widgets appropriate for the eInk screen.
Click to expand...
Click to collapse
I came across this: https://f-droid.org/en/packages/org.jsharkey.sky/
It works, which is rare for something so old, but the widgets are butt-ugly on the NST
Looks like I'll be researching changing colors, etc. So far it looks like the icons could be easily replaced, but the most offensive part is the widget background which is a 9-patch png (of course...).
The WeatherACE developer is a nice fellow but it would be ridiculous to contact him over this. So we move on.
nmyshkin said:
I came across this: https://f-droid.org/en/packages/org.jsharkey.sky/
So we move on.
Click to expand...
Click to collapse
Indeed. I spent some time yesterday exploring web-based widgets, thinking we could just point the browser at a URL, but most widgets use HTTPS and Javascript, neither of which are the strong suit of the NST, even with Opera Classic instead of the native browser.
Did this work?
disTrck33 said:
Did this work?
Click to expand...
Click to collapse
Depends on what "this" is.
I eventually wrote my own weather widget app for the NST/G: https://forum.xda-developers.com/nook-touch/themes-apps/app-nst-weather-widget-t3946270
This works.
nmyshkin said:
I came across this: https://f-droid.org/en/packages/org.jsharkey.sky/
It works, which is rare for something so old, but the widgets are butt-ugly on the NST
Looks like I'll be researching changing colors, etc. So far it looks like the icons could be easily replaced, but the most offensive part is the widget background which is a 9-patch png (of course...).
The WeatherACE developer is a nice fellow but it would be ridiculous to contact him over this. So we move on.
Click to expand...
Click to collapse
Link said USA only . There is a weather app that can be used for Europe which uses yr.no site for data. It runs on my tablet and should work with Android 1.5+. Nothing special but good enough. Might require some customization to e-ink display though. That needs to be checked.
SJT75 said:
Link said USA only . There is a weather app that can be used for Europe which uses yr.no site for data. It runs on my tablet and should work with Android 1.5+. Nothing special but good enough. Might require some customization to e-ink display though. That needs to be checked.
Click to expand...
Click to collapse
Didn't remember the US restriction, but all of the potential apps I looked at back then looked terrible on the NST or required network location. That is why (shameless promotion...) I eventually worked up my own Weather widget/app just for the NST. It lacks many bells and whistles but will work for any locale that OWM has stations. And, if I say so myself, looks pretty good on the NST.
nmyshkin said:
Another one bites the dust.
It took awhile for Wunderground's API to actually die, but it finally did and I used my last data point yesterday. None of the other APIs in the app (OpenWeatherMap, Norwegian MET, Yahoo) have worked for awhile. I tried the obvious with OWM and N-MET, getting new API strings, decompiling the app, replacing the APIs and stitching it all back together. But no joy. The data structures in the new APIs are probably different and that's way beyond me. The jiggered app ran, but it was unable to gather data from anywhere (other than what my location is).
Too bad. Nothing left like it, AFAIK.
Click to expand...
Click to collapse
The app is not dead.
I working on adding more weather sources. Atm, the app has 5 weather sources worked correctly - NOAA (USA only), OpenWeatherMap, Norwegian MET (yes, its back to work again, I switched WeatherACE to the their new API), Weatherbit.IO (new weather sources that added to WeatherACE in last build 1.12.30) and Forecast.IO (they are not provide new keys atm). Currently I working on 2 more weather source.
As for Wunderground, they were bought by IBM. The lowest price for weather data from IBM is around of $10000 per year, for a limited set of data. They also provide some weather API for people that provide them data from personal weather stations, but its just current and few days weather and no hourly data forecasts...
So, please check the app again.
mycodefab said:
The app is not dead.
I working on adding more weather sources. Atm, the app has 5 weather sources worked correctly - NOAA (USA only), OpenWeatherMap, Norwegian MET (yes, its back to work again, I switched WeatherACE to the their new API), Weatherbit.IO (new weather sources that added to WeatherACE in last build 1.12.30) and Forecast.IO (they are not provide new keys atm). Currently I working on 2 more weather source.
As for Wunderground, they were bought by IBM. The lowest price for weather data from IBM is around of $10000 per year, for a limited set of data. They also provide some weather API for people that provide them data from personal weather stations, but its just current and few days weather and no hourly data forecasts...
So, please check the app again.
Click to expand...
Click to collapse
No, it's not dead. In fact, I run it on most of my devices. I really appreciate the clean-looking widgets and I would recommend it to anyone looking for a good weather app with widgets.
Sadly, in the context of this forum, it is "as good as" dead since the old version that would still run on Android 2.1 can't connect to any of the weather services any longer
I'm sorry if Google-bots picked up this posting and are making it seem like the app is non-functional. I've edited the post title so that maybe in the future that will be corrected.
nmyshkin said:
No, it's not dead. In fact, I run it on most of my devices. I really appreciate the clean-looking widgets and I would recommend it to anyone looking for a good weather app with widgets.
Sadly, in the context of this forum, it is "as good as" dead since the old version that would still run on Android 2.1 can't connect to any of the weather services any longer
I'm sorry if Google-bots picked up this posting and are making it seem like the app is non-functional. I've edited the post title so that maybe in the future that will be corrected.
Click to expand...
Click to collapse
Hmm... What version of WeatherACE you use on the old device? Its too bad that I didnt used VCS (version control system) in the time (like I do it now). But I still have backups of source code of some really old versions of the app. The oldest is 1.6.2, then 1.7.4, 1.80, etc.
Not sure if Google will allows me to make it (uploading to Google Play will not be possible for sure), but I could try at least. If everything depended on me, the application would continue to support android 2.1 (or 2.3 was in the very first version, I don't remember exactly). Unfortunately, Google constantly demands to gradually raise the minimum API, and with it, support for older devices decreases.
mycodefab said:
Hmm... What version of WeatherACE you use on the old device? Its too bad that I didnt used VCS (version control system) in the time (like I do it now). But I still have backups of source code of some really old versions of the app. The oldest is 1.6.2, then 1.7.4, 1.80, etc.
Not sure if Google will allows me to make it (uploading to Google Play will not be possible for sure), but I could try at least. If everything depended on me, the application would continue to support android 2.1 (or 2.3 was in the very first version, I don't remember exactly). Unfortunately, Google constantly demands to gradually raise the minimum API, and with it, support for older devices decreases.
Click to expand...
Click to collapse
And I completely understand that. It's why I said in post #3 that it would be silly to contact you about this. I still remember how promptly and helpfully you responded to a question I had about more recent versions of the app I was running on my tablet. But restructuring an app that, in Android terms, is nearly an archaeological artifact, is not, I'm sure, a simple matter.
In any case, it looks like this version (1.4.4) is earlier than anything you may still have source code for.
nmyshkin said:
And I completely understand that. It's why I said in post #3 that it would be silly to contact you about this. I still remember how promptly and helpfully you responded to a question I had about more recent versions of the app I was running on my tablet. But restructuring an app that, in Android terms, is nearly an archaeological artifact, is not, I'm sure, a simple matter.
In any case, it looks like this version (1.4.4) is earlier than anything you may still have source code for.
Click to expand...
Click to collapse
Seems like the last version that support Android 2.1 and 2.2 is version 1.7.4 and I have sources for it. The changes log for 1.7.4 has mention about such fixes "Hotfixed crash on devices with android 2.1 - 2.3.X for weather alerts"." The version support WeatherACE API for external apps/widgets/early verions of tasker plugin, weather alerts and Forecast.IO source.
Luckily, there is a place where you can get almost any version of this app https://4pda.ru/forum/index.php?showtopic=511055&st=0 The last spoiler in the start post has links to my posts with most of the versions of WeatherACE. So, if you will have time, please try 1.7.4 from the post https://4pda.ru/forum/index.php?s=&showtopic=511055&view=findpost&p=32402422
If 1.7.4 will work for you. I could try to build it from the sources I have. In case it will build correctly, it will not be so hard to update support for OpenWeatherMap and Norwegian MET.NO weather sources. Probably I also could add support for Weatherbit.IO.
mycodefab said:
Seems like the last version that support Android 2.1 and 2.2 is version 1.7.4 and I have sources for it. The changes log for 1.7.4 has mention about such fixes "Hotfixed crash on devices with android 2.1 - 2.3.X for weather alerts"." The version support WeatherACE API for external apps/widgets/early verions of tasker plugin, weather alerts and Forecast.IO source.
Luckily, there is a place where you can get almost any version of this app https://4pda.ru/forum/index.php?showtopic=511055&st=0 The last spoiler in the start post has links to my posts with most of the versions of WeatherACE. So, if you will have time, please try 1.7.4 from the post https://4pda.ru/forum/index.php?s=&showtopic=511055&view=findpost&p=32402422
If 1.7.4 will work for you. I could try to build it from the sources I have. In case it will build correctly, it will not be so hard to update support for OpenWeatherMap and Norwegian MET.NO weather sources. Probably I also could add support for Weatherbit.IO.
Click to expand...
Click to collapse
That would be amazing. Unfortunately I get a 404 error when I try to download the app. I always get the error on that site. Not sure if you have to be logged in or what. I'll keep searching for the correct version.
nmyshkin said:
That would be amazing. Unfortunately I get a 404 error when I try to download the app. I always get the error on that site. Not sure if you have to be logged in or what. I'll keep searching for the correct version.
Click to expand...
Click to collapse
Please try http://mycodefab.com/files/WeatherACEv1v7v4.apk
mycodefab said:
Please try http://mycodefab.com/files/WeatherACEv1v7v4.apk
Click to expand...
Click to collapse
Thanks so much. I tried this version on two NSTs, one with Network Location enabled and the other without. It works on both to the extent I can judge without any weather data being fetched. No sudden crashes or odd behavior. The map at the initial setup is blank, but that was the case in 1.4.4 (something to do with e-ink and the assumptions for default themes, I guess). Anyway, the map does not matter if you can type in your own geocoordinates which is what I did on the device without Network Location.
So this looks like a good candidate.
nmyshkin said:
Thanks so much. I tried this version on two NSTs, one with Network Location enabled and the other without. It works on both to the extent I can judge without any weather data being fetched. No sudden crashes or odd behavior. The map at the initial setup is blank, but that was the case in 1.4.4 (something to do with e-ink and the assumptions for default themes, I guess). Anyway, the map does not matter if you can type in your own geocoordinates which is what I did on the device without Network Location.
So this looks like a good candidate.
Click to expand...
Click to collapse
OK, thanks. In case you have DarkSky API key (the app know it as Forecase.IO, it was an old name of the DarkSky API) please use it with the version 1.7.4, the app version support the weather source. Once purchased by Apple, DarkSky (Forecast.IO) no longer give out free keys. But any old keys continue to work atm, as far as I know.
Building a new version with updated support for weather sources will take some time. As usual, most problems in the case are not related with app itself, but with other libraries. For example, a library that provided map does not support Android 2.1 anymore, so probably I will need to completely remove map from the app. Google libraries related with analytics and ads - also does not support old android versions anymore. I will work on it this weekend.
nmyshkin said:
Anyway, the map does not matter if you can type in your own geocoordinates which is what I did on the device without Network Location.
Click to expand...
Click to collapse
You need GPS.
nmyshkin said:
So this looks like a good candidate.
Click to expand...
Click to collapse
OK, seems like its done http://mycodefab.com/files/WeatherACEv1v7v4v2.apk Hope it will work, because I dont have Android 2.1 devices to test. In case of problems, I will try to find something.
The version support 2 weather sources - OWM (open weather map) and Norwegian MET.NO.
Limitations:
1. Removed weather map and adding locations via map. I cant find any android weather libraries that support Android 2.1 devices.
2. Removed ads for same reason.
3. Weather icons limited to the small set of icons inside the app + 1 custom icon set.
As for custom icon set, its mostly same as for latest versions of WeatherACE, just a bit different directory for images. Directory is "Android/data/mycodefab.aleph.weather/files/custom/icons/". It use same format as for the latest versions. So, for example, for "clear sky in day" condition it will use "d_100.png" file, "clear sky in night" will look for "n_100.png" file, "overcast" will use "d_104.png", etc.
In case the version of the appt will start, but not show the weather after weather info update, please get to Menu->Settings->Advanced->Weather Sources. Here you could see Active weather sources on the top. Tap on it. Uncheck OpenWeatherMap and Norwegian MET, tap OK. Enter Active weather sources again. Set check OpenWeatherMap and Norwegian MET, tap OK. It will recheck availability of sources for existing locations and will update the weather info.
mycodefab said:
OK, seems like its done http://mycodefab.com/files/WeatherACEv1v7v4v2.apk Hope it will work, because I dont have Android 2.1 devices to test. In case of problems, I will try to find something.
Click to expand...
Click to collapse
I tried the app on both devices (with and without Network Location). Unfortunately it does not want to run
There is immediate funny business as the package shows in the file manager as a generic "package" icon rather than the app icon. Also, the package name (and generic package icon) are displayed in the launcher rather than the app icon and name.
I've attached a section of a logcat for trying to open the app. I don't know whether it has information that is helpful.
It may or may not have any bearing on what you have done, but as you're already going way beyond any expectations, I would suggest that leaving the app alone except for fixing the weather sources would be more than enough. I can understand your desire to have things "right". I have that same problem , and I do appreciate it, but maybe without so many changes there would be a better chance of the app still working, which is what it did even now, except for the access to weather sources. Of course, it's probably not that simple.
Thanks for your efforts.

Categories

Resources