I'm working on building an app, and some of the newer phones are starting to have built-in heart rate monitors.
But I really can't find anywhere on the internet on how to access this. Does anyone have any idea of how?
If it's a Samsung Device, you might want to try the Samsung S Health Service SDK.
What kind of phones are you looking at?
Related
I'd like to ask if someone knows if it's possible to pair a android wearable device (like a smartwatch) directly with google glass to get sensor informations like heart rate. Or is this just possible with a smartwatch being coupled with both devices? I didn't found any informative resources on this question...
Thanks for all answers!
Absolutely. Especially if your smartwatch will be Android, this can be done fairly easily.
Glass can connect to anything over Bluetooth!
This answer contains a full set of code that outlines exactly what you want.
I'm developing an Android application (only for Samsung Galaxy S4 at the moment) where I need to continuously monitor sounds from microphone in order to detect voices, and possibly how many people are speaking (I don't want to recognise what the people are saying, just detect that someone is speaking). How can I do it? The only way is through MediaRecord getMaxAmplitude()? But then How can I understand how many people are speaking? Thanks
I am an iPhone developer that is about to dive into the Android market. The price of the development phone (Nexus 1 - $530) is quite high, so I thought to myself, "Why not spend $10 more and get something like the Dell Streak?". I haven't read any particular reviews on that device, but for an iPhone user that just wants a dependable device to develop on - what is the best fit? Ideally I am looking for a device that matches the experience that most Android users have - is that even possible?
If you can hold off just a little longer you could get a Samsung Nexus S which is the latest Android phone and will be shipping with Gingerbread (2.3).
I would suggest taking a look into statistics of device frequencies.
Android website provides http://developer.android.com/resources/dashboard/screens.html and OS versions.
But there are lot of other stats on the web, e.g.:
http://www.enterra-inc.com/techzone/android_statistics/
http://blog.tweetdeck.com/android-ecosystem
etc.
Any normal consumer-marketed android device can be used for application development - a developer phone is only needed if you want to modify the android platform and underlying linux itself (something that may also be possible by finding a way to root a consumer device)
To match the experience of most users, you probably want a recent device co-branded as a "google experience" device, ie one that comes with Android Market and the other google apps, which are not at present available for devices without that "blessing".
I would take a look at getting a motorola droid or droid 2 since they hold most of the android market share. I think this would provide the ideal user experience. I think the Samsung Nexus S will probably be THE android phone to have, but I dont think most people will have it for sometime.
I am trying to do a demo on a android device, but the screen is too small so is kinda hard to do a demo let say in a meeting room with 12 people. Although I can pass the device around the table or just simple borrow or get more devices for the demo purposes.
I understand there are devies where you can buy special USB converter to do TV-out like in iPhone, and some specific devices on Android (e.g. Motorola Incredible?) But I have to demo on a specific device where it runs standard Android build.
I understand I can do it on Android emulator but the screen refresh rate is too slow, as it will send the wrong message to the audience that the app is slow. (Or there is a way to increase the screen refresh rate for emulator?) Furthermore the emulator doesn't support multitouch. (Or am I wrong?)
Not sure if anyone
You do not have many options.
You can use Droid#Screen, but the refresh rate on it is maybe 6fps. I am not aware of any other software projector that is faster.
You failed to mention the "specific device" that you are using, so I cannot comment on whether it has TV-out capability. The HTC DROID Incredible and the Samsung Galaxy S series support composite output -- I use the DROID Incredible for this purpose a fair bit. Most of the devices that have HDMI output only support it for certain built-in apps, such as the video player.
You can rent or purchase a device projector, like an ELMO. These are fairly expensive pieces of equipment purchased new, though I see a handful of used ones on eBay at interesting prices (though watch out -- many seem to lack the AC adapter).
If you can delay the demo several months, you may be able to use a Google TV.
And that's about it, AFAIK.
Or there is a way to increase the screen refresh rate for emulator?
Get a faster computer.
Furthermore the emulator doesn't support multitouch. (Or am I wrong?)
I am not aware of a way to simulate multitouch with an emulator, though I have not gone looking for a solution there.
If you have an Galaxy S3 Android mobile phone, you can use Mobizen. It's free and the screen refresh rate is relatively good. You can control you mobile phone from you computer using your mouse and your keyboard. It's working using USB, 3G or Wifi connection.
I have used this Android screencast tool: http://code.google.com/p/androidscreencast/ in past demos, but again the downside is the relatively slow refresh rate.
If you have a rooted device, you could try Droid VNC Server (it's on the market). The refresh rate isn't too bad, but I certainly wouldn't want to demo full motion video or an arcade game on it.
You could also get a webcam, rig it up with a tripod. Something like this. Downside is your hands will be in the way, maybe issues with lighting and/or focus. Upside is a decent refresh rate.
I am looking to write an Android app for a device that has not been released to the market yet, and so I will not have the hardware to test upon. I have created an AVD (Android Virtual Device) with as much information as is currently available on the web, so assume that this is as like the device as is possible to get.
However, does anyone have any tips or ideas to make the process of developing for this platform as easy as possible? My current apps have been for personal use on my own phone, so can test performance on the hardware etc. which is obviously not possible in this case. Any gotchas to watch out for (apart from the possibility of the device never being released..!!)
Just follow the SDK.
AVD behaves similar to a real device. I really can't think of something it behaved different on a device and on the AVD.
The only device that brought me trouble is the HTC Hero, first phone with HTC Sense. It didn't follow the SDK and they were calls that weren't there. Newer phones with HTC sense doesn't have this issue, as far as I can tell.