sensor

I am working on software in which I need to access the temperature sensors in the CPU and get control over them. I don't know much hardware interfacing; I just know how to interface with the mouse. I have googled a lot about it but failed to find any relevant information or piece of code. I really need to add this in my software. Please guide me how to have the control over the sensors using C or C++ or ASM. Without a specific kernel driver, it's difficult to query the temperature, other than through WMI. Here is a piece of C code that does it, based on WMI's MSAcpi_ThermalZoneTemperature

I'm running RPi with a USB Bluetooth dongle. When I use hcitool, I can discover the SmartTag device. But when I use gatttool, I cannot connect. It says "Host is down (112)". Here are my commands: $ sudo hcitool lescan LE Scan ... BC:6A:29:AB:DE:2B (unknown) BC:6A:29:AB:DE:2B SensorTag Checking for bluetooth adapters on my RPi I get: $ hcitool dev Devices: hci0 5C:F3:70:60:E6:1B Then, when I use the gatttool like this, I get: $ sudo gatttool -i hci0 -b BC:6A:29:AB:DE:2B -I [ ][BC:6A:29:AB:DE:2B][LE]> When I type connect, I get this: [ ][BC:6A:29:AB:DE:2B][LE]> connect Connecting... connect

How can I detect whenever the power cord is unplugged from electrical socket using JSR 256? You would add javax.microedition.io.Connector.sensor to the API Permissions tab of the Application Descriptor of the project properties. michael aubert From a quick look at the specifications of the JSR: (you might want to look for code examples, starting with Appendix D of the spec itself, the latest JavaME SDK, Sony Ericsson developer website, then google) As always, I would be worried about fragmentation in the diverse implementations of the JSR, but here's my first idea: import javax.microedition

getPower() returns the power in mA used by a sensor while in use: Now, I need to calculate how much battery is used by the registration of the sensor. Does he value returned by getPower() indicate the mAH (mA per HOUR) or something else? If yes, is there a way to get the battery mAH in order to calculate the % of battery used by the sensor? Something quite related has been discussed in Google groups not too long ago. You can find the full thread here for reference. A small excerpt from the last reply in that thread, which should answer your question more or less: (...) the battery capacity is

For my App I need to calculate the acceleration of my device in reference to true north. My idea was to calculate the device orientation to magnetic north and apply the declination to it to get the orientation to true north. Then I want to calculate the acceleration of the device and reference it to the orientation, but I do not know how I should do this. I would try to get the device orientation using SensorManager.getRotationMatrix() and SensorManager.getOrientation() . Then I get the declination by GeomagneticField.getDeclination() and apply it on the azimuth of the orientation values from

I'm trying to implement an arrow that uses the orientation sensor in order to point towards a specific location. Google Places implements this arrow in a ListView for each place it finds. I've managed to get the azimuth, but given a location, I don't know how to proceed to calculate the angle I need. Moreover, I need to make the conversions from real north and magnetic north. Does anybody have an example of such implementation? Thanks in advance. I solved it. float azimuth = // get azimuth from the orientation sensor (it's quite simple) Location currentLoc = // get location from GPS or network

I have been working on a small compass app the past couple of days, and have gotten the code up and running, but it seems that the compass reading is not accurate. After calibrating both phones, my first test that i found this in what that i simply held the phone against and flat surface looked at the reading then flipped it horizontally and put it against the same flat surface (a 180* turn) and the value did not change 180* it was closer to 240*. I then tested the reading vs a compass, at times the reading seemed to be close but at other points it was more than 50* off. I even tried to put my