Develop Bugs

AD-Logger

hello,
i am using a very simple AD-converter to measure voltages (circuit based on LTC1290). Till now i used old DOS-Laptops in the field to get and store the measurements. The connection went over the serial port by using the DTR, RTS and CTS lines and the 'port commands' of the io-system.
At the moment i am thinking about a change to a xda.
I need a 'clock', a 'send data' line and a 'receive data' line. They must be switched between zero and at least 3Volts.
Can anybody tell me wether this is possible with a xda ?
- Jan -

Yeah, i would presume you can use the serial lines, although I don't think there is a clock.

You could probably use one of the serial control lines as a clock, and another one as data in and one as data out. The +5V for the thing could also be spuulied by the XDA. You will most likely not get the 50 kilosamples/second the 1290 supports, but that's likely not to be what you want anyway.

thank you Peter Poelman,
yes, a sample rate of 50kilosamples/s is not my goal.
Meanwhile i found this general page about serial communicaion with Palm's: palm serial manager with a very general statement in the 'serial hardware section':
Some devices also have a configurable DTR (data terminal ready) signal. Normally, the DTR signal is always high.
Click to expand...
Click to collapse
Ok - some devices can manipulate the DTR-line - but which ? can the XDA ?
According to this page it seems not possible with the standard palm-os modules and routines to manipulate the the RTS line. I can only get status information about the DTR and CTS line - i am new to pda/xda programming i dont know very much about hardware architecture and but maybe someone her has some hints.
- Jan -

USB Host mode

ADMIN EDIT:
adq is also a member here, direct link to his site about this:
http://adq.livejournal.com/95689.html
for dev's a patch is available to patch the kernel to enable this
It looks that one there are some guys that succeed to use the USB in host mode on an Android device ....
issue 738 on code.google http://code.google.com/p/android/iss...ummary%20Stars
Implementing the USB on the Go feature on a phone, will allow you to
conect to the phone:
- regular keyboards - imagine how easy you enter contacts, edit notes
and other text information into your phone when you go to home / work
and connect the keyboards from the computers you are using there.
- regular mice
- flash drivers, card readers, external hard drives, foto camera
- printers - so you can easily print the photos you make wit the built
in camera, and office documents you edit from the phone.
- scanners
- monitors (with a USB-to-VGA adapter, like the HTC Advantage X7510
does)
- WiFi cards
- USB ethernet cards - this would be an imensely great feature.
Because with propper software you can test an ethernet port (ping,
etc), even test UTP cables - like the expensive Fluke devices do. Just
imagine how convenient is to test a network without taking the laptop
with you and without buying expensive network testing tools.
- TV Tuners
- another phone that will stay in "slave mode"
- web camera - maybe it's a silly idea, but hey, why not?
- pen tablets
- USB hubs - so you will be able to connect all the above peripherals
to the phone in the same time.
Click to expand...
Click to collapse
for HTC Hero
http://adq.livejournal.com/
This guy succeed to attache a real keyboard, a real mouse that is used as a trackball and a external USB storage device!!
Also he is using a battery USB hub to resolve the charging needs of some of the devices.....
how to create the cable , and some tests for Motorola Droid...
http://www.tombom.co.uk/blog/?p=124

Whoa, nice find. I didn't think this was even possible. I've been telling anyone who asked about it to keep dreaming. My bad.

yes..I also wanted to do this since I bought my first WM phone .... someone else tried this ?

instead of creating that patched cable do you think that a battery hub like this one that can change the gender of the USB, can be use instead ?
http://www.everfast.com.hk/catalog/usb-hub-battery-charger-usb-hub-4-ports-p-138.html
PS: it has also battery based charging capabilities

That's an interesting thought, although I don't have anything near the technical knowledge of this type of thing to say for sure. Your guess is as good as mine.

craig0r said:
That's an interesting thought, although I don't have anything near the technical knowledge of this type of thing to say for sure. Your guess is as good as mine.
Click to expand...
Click to collapse
i'd say it should work with this. but i am afraid we'll have to wait until someone actually implements this somehow...
can someone pleeeease implement this somehow?

Keep in mind that If i read this correctly, this patch will disable usb device mode (i.e. wont be able to access the sd card as a mass storage device anymore and HTC Sync will be disabled as well).
Edit: At least for the time being. The dev seems keen on getting the device-mode/ host-mode drivers to cooperate.

alt236 said:
Keep in mind that If i read this correctly, this patch will disable usb device mode (i.e. wont be able to access the sd card as a mass storage device anymore and HTC Sync will be disabled as well).
Edit: At least for the time being. The dev seems keen on getting the device-mode/ host-mode drivers to cooperate.
Click to expand...
Click to collapse
Yeah, it shouldn't be too hard to implement a software switch.

On the other blog they propose this cables :
http://www.brightonnet.co.jp/english/product/other/bbm-wireel.html
http://www.overstock.com/Electronic...d=123620&fp=F&ci_src=14110944&ci_sku=12436069
http://cgi.ebay.com/Micro-USB-Host-...Accessories?hash=item3a57229ee9#ht_5104wt_939
PS : I would like to buy one of this cables
PS2: I see on that e-bay link that this is already working on various linux powered mobile devices.

Hi, thanks for posting this here
Yeah, I'm just reading how the OMAP USB drivers implement the software switch just now to see how best to do it; right now looks like three drivers - two actually implementing the host/device mode, and one stub mediating which one is actually active.
I'm hoping to have something along these lines working next week.

thats great news mate will u posting your cabel guide to also this should be added i think to the custom roms (or at least a option the the kitchen tool)

There has been some progress:
http://adq.livejournal.com/
http://groups.google.com/group/android-kernel/browse_thread/thread/b871a27624f69b85

is it still not ready to be implemented even in experimental ROMs?

How should I install that? From Recovery? Like a Rom

is there any update on this? I would love to be able to read my SDCARD on my digital camer just by linking in with a usb cable

USB devices not detected by USB HOST
I am developing application to detect my printer by NOVO 7 Paladin(Android 4.0).
By USB HOST CONTROLLER application(which is available in market) the printer/mouse/keyboard is detected. But in my application(Written in java) these devices are not detected
With the reference of below link this application is developed
developer.android.com/guide/topics/usb/host.html
My Code Sample
mUsbManager = (UsbManager)getSystemService(Context.USB_SERVICE);
HashMap<String, UsbDevice> foundDevices = mUsbManager.getDeviceList();
Iterator<UsbDevice> iterator = foundDevices.values().iterator();
if (foundDevices.size()>0)
{String old = textv.getText().toString();
textv.setText(old +" foundDevices ");
}

External Touchscreen Development

Hello,
Currently i'm working on a personal project to integrate my GS3 into my car display and audio. Well this was easy with the help of a MHL or Allshare Cast Dongle.
My next goal was to install a 4 wire resistive touchscreen on my car display and use it as an external touchscreen control. I bought a 7" 4 wire resistive touchscreen with a USB module build around the CYPRESS CY7C63723C chip. I hooked up the touchscreen with OTG to test if there any initial reactions from my GS3, needless to say there wasn't any (no surprise there).
After a little digging around I came up with the conclusion that I need to create a custom "Input Device Configuration Files" for my touchscreen based on the following links
http://source.android.com/tech/input/touch-devices.html
http://source.android.com/tech/input/input-device-configuration-files.html
My initial question before I start plugging away with some codes is how would I name the files, the documents states "Input device configuration files are located by USB vendor, product (and optionally version) id or by input device name." How would I find the product ID or the input device name for the touchscreen? I'm sure this can be done thru terminal or something but I am new to android development so cut me a little slack here
Also if you know of any Input device configuration files dealing with touchscreen please post it.

Anyone?

hechen said:
Anyone?
Click to expand...
Click to collapse
You would probably be better served asking this on one of the more general hacking sub forums. Here, you're just going to get people who are familiar with the S3. There, you may find someone who has done something similar on another phone.

hechen said:
Anyone?
Click to expand...
Click to collapse
Any resolution with this?
I have been pondering the idea as well, but have no coding or hacking experience to go off of.
Would love to hear about the progress for this project and maybe a writeup of parts and procedures so far.

[Q] Tap triggers swipe (aka sensitive screen)

Some people over at the fairphone.com forum reported a "sensitive" screen. They try to tap on a button (or link) and instead of triggering the button the fairphone starts scrolling. My fairphone also shows this behavior and I tried to find out why. Well, after trying for some time I realized that the shorter I tap on the screen the more likely it happens in a swipe/scroll.
So I enabled the "pointer position" option within the developer tools and shot two screen shots. In the first screenshot I tap for round about 500ms whereas in the second screenshot I tried to tap as short a possible. Like you would click with mouse. It show the error pretty obvious. Any ideas how to adjust that?

Hello
I noticed exactly this behaviour on my Fairphone, too.
That's why I started a thread on the official Fairphone website 22 days ago.
I'm not allowed to post direct links here, so I can give you only the head line here:
"Hyper-sensitive-touchscreen"
And on german Fairphone Freunde forum there's also a thread about this problem
Key-Word:
"Empfindlichkeit-des-Touchscreen"
So far, there is not very much response on these threads, but it seems that not all the handsets are affected, because not all of the answers confirmed the problems. One of the guys on fairphone website sent a request to the support team, a few days ago. Maybe he can forward the answer he gets... I'll ask him in his own fairphone thread - "Sensibility-and-reboots"
Unfortunately my phone broke after just one day, so I'm waiting for a replacement now and can't really offer a solution here...
But during the few hours, my phone worked, I entered the engineering mode (by typing *#*#3646633#*#* in the standard dialler app) and there were many options to manipulate the tuochscreen.
Maybe the more experienced guys here in the forum can work out a solution to solve the problem?!
Thank you in advance!

I have the same "hypersensitive screen" issue
Before I was used to briefly and lightly tapping/touching the screen, but with my Fairphone that often gives a scroll signal.
My developer crosshair option shows short lines, the touchpanel behaves as if I first tapped a few centimers away and then a split second later it registers where I actually touched the screen.
I had to learn to firmly tap and hold, otherwise I couldn't select anything on the screen.
It seems a sofware patch for the touchpanel is needed.
-----------------------------------------------
Fairphone FP1
Caju (v.1.1)

Touchscreen settings
I am copying this from the Fairphone forum, for future reference:
My settings, as copied from engineering mode:
tpd_em_log = 0
tpd_em_log_to_fs = 0
tpd_em_sample_cnt = 16
tpd_em_auto_time_interval = 10
tpd_em_pressure_threshold = 0
tpd_em_debounce_time = 0
tpd_em_debounce_time0 = 1
tpd_em_debounce_time1 = 4
tpd_em_spl_num = 1
tpd_em_asamp = 1
NOTE: Do NOT change any of the values (in this case, under Settings). I do not know what they do, really, and how your device might react! I just report mine, for your comparison.
Just FTR, my device works fine!
Any values different from yours? Then I would suggest reporting the issue to FP while including the link to our discussion here, and on the Fairphone forum. If we can narrow down the source of the problem to be caused by some settings, and not your environment or your specific devices hardware malfunctioning, @benkxda could report this to FP in his next mail.

boondiordna said:
I am copying this from the Fairphone forum, for future reference:
My settings, as copied from engineering mode:
tpd_em_log = 0
tpd_em_log_to_fs = 0
tpd_em_sample_cnt = 16
tpd_em_auto_time_interval = 10
tpd_em_pressure_threshold = 0
tpd_em_debounce_time = 0
tpd_em_debounce_time0 = 1
tpd_em_debounce_time1 = 4
tpd_em_spl_num = 1
tpd_em_asamp = 1
NOTE: Do NOT change any of the values (in this case, under Settings). I do not know what they do, really, and how your device might react! I just report mine, for your comparison.
Just FTR, my device works fine!
Any values different from yours? Then I would suggest reporting the issue to FP while including the link to our discussion here, and on the Fairphone forum. If we can narrow down the source of the problem to be caused by some settings, and not your environment or your specific devices hardware malfunctioning, @benkxda could report this to FP in his next mail.
Click to expand...
Click to collapse
I already put a link on fairphone.com to this XDA thread. Thanks for telling! Well, my settings looks identical to yours. I also played around with them. I have no idea if touch screens nowadays need deboucing or sth like that. So I changed these settings a bit...without improvement though. I am also wondering what tpd_em_log is. It is put to 0. I put it to 1 hoping there is some log written somewhere....but i could not find where unfortunately.

Hey there,
I have the same problem and no solution. But here is my input on that issue. Maybe it helps Fairphone when they investigate that issue, maybe not.
hanzano said:
Well, after trying for some time I realized that the shorter I tap on the screen the more likely it happens in a swipe/scroll.
Click to expand...
Click to collapse
I realized the same thing. BUT in addition, I figured out that it has also something to do with how soft you touch. If I try and touch my screen very very gently, I can reconstruct that behaviour every time. If I press a bit harder, it works better.
I attached a screenshot where I did soft touches, and you see a lot of wiggeling especially in the botom row

Yesterday I was annoyed by this issue. I was a bit in a hurry and the Fairphone touchscreen did not react properly
So I just debugged in Android Studio and this is what I logged:
Code:
12:07:48.874 MotionEvent.ACTION_DOWN: 300.44363, 485.4943
12:07:48.886 MotionEvent.ACTION_MOVE: 293.13342, 499.09888
12:07:48.901 MotionEvent.ACTION_MOVE: 293.45657, 497.48178
...
12:07:49.168 MotionEvent.ACTION_MOVE: 293.45657, 497.48178
12:07:49.183 MotionEvent.ACTION_MOVE: 291.2037, 497.48178
12:07:49.198 MotionEvent.ACTION_MOVE: 290.46213, 497.48178
...
12:07:49.403 MotionEvent.ACTION_MOVE: 290.46213, 497.48178
12:07:49.406 MotionEvent.ACTION_UP: 290.46213, 497.48178
12:07:49.406 event.getDownTime: 566
I tapped for 566ms. Pretty obvious that from ACTION_DOWN to the first ACTION_MOVE there is a big delta of ~14px (is it really pixel?) in y-direction.

Hey there,
probably this does not help anyone, but just for the sake of documentation: due to my headphone-jack issue, my fairphone got replaced by a new one. Now it seems that my sensitive screen issue is gone.

I don't know about how many sources you guys have, but if you have the kernel sources, someone could try to implement a filter (and enable debugging logs in the kmsg ofc) so touches under 400ms (just a value for explanation) are only getting registered as touches, but not as movements. However, this could also have some downsides (pretty fast swipes for example), therefore a sysfs option would be a nice idea
But this would at least be a workaround.

Hyst said:
Hey there,
probably this does not help anyone, but just for the sake of documentation: due to my headphone-jack issue, my fairphone got replaced by a new one. Now it seems that my sensitive screen issue is gone.
Click to expand...
Click to collapse
Hmm, ok.Would you mind doing another sreenshot like you did already? Just in order to see the difference.
laufersteppenwolf said:
I don't know about how many sources you guys have, but if you have the kernel sources, someone could try to implement a filter (and enable debugging logs in the kmsg ofc) so touches under 400ms (just a value for explanation) are only getting registered as touches, but not as movements. However, this could also have some downsides (pretty fast swipes for example), therefore a sysfs option would be a nice idea
But this would at least be a workaround.
Click to expand...
Click to collapse
That is what I also had in mind. I already had a look at Xposed framework trying to find out how to "intercept" global touches. With a normal Android Service it is unfortunately not possible at least what I have read so far.

hanzano said:
That is what I also had in mind. I already had a look at Xposed framework trying to find out how to "intercept" global touches. With a normal Android Service it is unfortunately not possible at least what I have read so far.
Click to expand...
Click to collapse
Xposed is a genious piece of work, however, this should be done via kernel.
Maybe @benkxda could have a chat with Fairphone about that?

hanzano said:
Hmm, ok.Would you mind doing another sreenshot like you did already? Just in order to see the difference.
Click to expand...
Click to collapse
no problem. Here you go!
As far as I am concerned I did the same thing. small fast touches.
although sometimes there is a long line, overall a lot less wiggeling.

Hyst said:
no problem. Here you go!
As far as I am concerned I did the same thing. small fast touches.
although sometimes there is a long line, overall a lot less wiggeling.
Click to expand...
Click to collapse
That looks much better than beforehand. I believe the red lines are not of interest. These just seem to be estimations. I had a look into Android source code com.android.internal.widget.PointerLocationView. The VelocityTracker has an Estimator which is drawn in light red. The MediaTek development tool seems to do it similar. So I would only count the green lines.
But I still think that this is not perfect either. I checked with my old Samsung Galaxy Ace and the Android location pointer which really gives points, no line at all when tapping shortly.

laufersteppenwolf said:
Xposed is a genious piece of work, however, this should be done via kernel.
Maybe @benkxda could have a chat with Fairphone about that?
Click to expand...
Click to collapse
I absolutely agree with you that this should actually be done on kernel/driver level. But I have no idea about Android's kernel structure or any driver layer at all. I used the Android SDK though. And unfortunately MediaTek is not giving all sources for the FairPhone
Where exactly do you expect touches to be evaluated and "forwarded" to Android? Do you have some example code of other phones probably? I am just interested how this works in software.

hanzano said:
I absolutely agree with you that this should actually be done on kernel/driver level. But I have no idea about Android's kernel structure or any driver layer at all. I used the Android SDK though. And unfortunately MediaTek is not giving all sources for the FairPhone
Where exactly do you expect touches to be evaluated and "forwarded" to Android? Do you have some example code of other phones probably? I am just interested how this works in software.
Click to expand...
Click to collapse
Sorry for the late answer, haven't seen you post
Well, kernel sources are quite easily structured, you've got the drivers, in there you find the input drivers, in which you also find the touchscreen drivers. in there are several drivers, you then need to find the correct one (in my case it's THIS file). In there are all functions to make your touchscreen work. This device also has a filter for "ghost" touches, just search for it inside this file
So, if you have located the driver of your device, you can there all needed stuff, such as the filter I mentioned

laufersteppenwolf said:
Sorry for the late answer, haven't seen you post
Click to expand...
Click to collapse
No prob
laufersteppenwolf said:
Well, kernel sources are quite easily structured, you've got the drivers, in there you find the input drivers, in which you also find the touchscreen drivers.
Click to expand...
Click to collapse
Ah ok, got it. In folder alps >> kernel >> drivers >> input >> touchscreen there are 68 files.
laufersteppenwolf said:
in there are several drivers, you then need to find the correct one (in my case it's THIS file).
Click to expand...
Click to collapse
Did you forget the link on "THIS" probably?
laufersteppenwolf said:
In there are all functions to make your touchscreen work. This device also has a filter for "ghost" touches, just search for it inside this file
So, if you have located the driver of your device, you can there all needed stuff, such as the filter I mentioned
Click to expand...
Click to collapse
Vielen Dank! Helps a lot

hanzano said:
Did you forget the link on "THIS" probably?
Click to expand...
Click to collapse
Ooops yeah, I did So HERE you go

Hello @Hyst
In the last week I was discussing with the support team pretty intensively about the touchscreen issue.
Now, they asked me to send them my phone, to see what happens on the device.
But, as I'm working abroad, its not that easy for me, to send it soon.
That's why I suggested, they should ask you, to get the IMEI of your old device - as you offered in the general thread.
Unfortunately Rick de Groot (the support guy) asked me again, to ask you for this number...
A little bit strange, but this is what I want to do now
Can you please send your old IMEI number and the RMA (repair form number) to this email:
<[email protected]>
That would be really great!
PS:
My Name is Florian W. if you want to quote me in your email.
Maybe this helps them to relate your email to my support request.
Thank you in advance!
Holzwurm86

Hi @Holzwurm86
sure thing. I've just send them an email.

Holzwurm86 said:
In the last week I was discussing with the support team pretty intensively about the touchscreen issue.
Now, they asked me to send them my phone, to see what happens on the device.
Click to expand...
Click to collapse
Good to see that there is still progress. The list of phones being affected gets bigger at the fairphone.com forum. If the engineers from Kwamecorp or Changhong need help like debugging or logging touches I am willing to help of course.

USB Accelerometer on Joying radio

Hi,
Sorry, I had already posted this on another section but I think this one is more appropriate and can't delete other post.
I have a Joying JY-NL124 android car radio, which does not have an accelerometer. I bought the Yocto 3d V2 http://www.yoctopuce.com/EN/products/usb-position-sensors/yocto-3d-v2 to see if I could get it to work with torque and other android apps for the track but although android sees the device the apps do not. I am not a programmer, but is there a way to get the apps to recognize an external accelerometer like some do for an external GPS?

Very interesting. I would like to know as well. It might also be usefull in navigation to get a faster direction orientation.

I was reading up on this again and this bit means someone with the know how would probably need to code something
The main advantage of this solution is that you don't need to install a driver to communicate with a Yoctopuce module, as the HID layer is always present. You only need to add our library, that we provide in source form, to your driving software for it to be able to directly talk to Yoctopuce modules.
Click to expand...
Click to collapse
Have you tried contacting them directly and asking if they can do this for you?

sinnedone said:
I was reading up on this again and this bit means someone with the know how would probably need to code something
Have you tried contacting them directly and asking if they can do this for you?
Click to expand...
Click to collapse
Uff, sorry for the late reply. Life has a way of getting in the way of interesting projects. I'm about to restart this project since I'm using the car a lot on the track. It's weird that the units don't come witha compass, gyroscope, accelerometer, etc, considering they are meant to be used in moving vehicles.

Definitely post up if you figure it out.
It would be nice to get it to work with Android as a whole. If that's the case you might need to talk to one of the ROM developers to see if it's something they can do ROM wise or even a custom kernel.(the kernel bit might be a little harder)

Did anybody get this right. It would be cool if these usb accelerometer could work in the apps

flash_xx said:
Hi,
Sorry, I had already posted this on another section but I think this one is more appropriate and can't delete other post.
I have a Joying JY-NL124 android car radio, which does not have an accelerometer. I bought the Yocto 3d V2 http://www.yoctopuce.com/EN/products/usb-position-sensors/yocto-3d-v2 to see if I could get it to work with torque and other android apps for the track but although android sees the device the apps do not. I am not a programmer, but is there a way to get the apps to recognize an external accelerometer like some do for an external GPS?
Click to expand...
Click to collapse
I'm very interested to understand whether this is possible as I am thinking about a similar setup. You tried the three Bluetooth tips in the roll up thread?
https://forum.xda-developers.com/an...roll-joying-2gb-sofia-mtcb-mtcd-tips-t3555249
"Bluetooth Tethering & BT Settings", "Difficult to pair BT devices" and "Modified stock bluetooth app to allow connection to all devices"
Have you tried external GPS for higher refresh rates or is the Head Unit gps refresh good enough for the track?
Bob

MX5DrIver said:
I'm very interested to understand whether this is possible as I am thinking about a similar setup. You tried the three Bluetooth tips in the roll up thread?
https://forum.xda-developers.com/an...roll-joying-2gb-sofia-mtcb-mtcd-tips-t3555249
"Bluetooth Tethering & BT Settings", "Difficult to pair BT devices" and "Modified stock bluetooth app to allow connection to all devices"
Have you tried external GPS for higher refresh rates or is the Head Unit gps refresh good enough for the track?
Bob
Click to expand...
Click to collapse
Sorry....USB not Bluetooth... Also discouraging. I was hoping USB would be an alternative to BT for track add-ons...

I too have an Android head unit and do track days, and have the exact same interest as you. I use Harry's Lap Timer. I have the Pumpkin AE0273B head unit. It too lacks the compass and accelerometer. I too found this to be a very unfortunate omission.
I have developed apps actually so I do know Android program to some degree (although I am sortof a hack, not a pro). I have apps on the Play Store (since I can't post links just search Play Store for developer JimRoal). I saw the Yocto stuff. When I get some time I will look into this some more.

Any update on this? Would also like to add a compass / accelerometer to my joying.

Also interested. But on a newer 10.0 unit. Something I am going to look into.

nFiniti said:
Also interested. But on a newer 10.0 unit. Something I am going to look into.
Click to expand...
Click to collapse
Sad that over 4 years after I first posted this we still don't have a unit with these features. I finally gave up and bought an AIM Solo 2 DL.
I'm looking for a newer radio though, since mine is older than this thread

Still waiting as well.

Looking forward for solution, we have also WIMOTION sensors in the market with sample android apk but I'm not a developser so, put things together is hard for me !

I think the hard job is try to mock the sensors in Android AS IF external accelerometer was factory embeeded (allowing apps to recognize it)

Nothing new about this project / idea ???

?? dead ???

mariodantas said:
?? dead ???
Click to expand...
Click to collapse
Once you've figured out how to modify the kernel, you should be good to go!
Another option could be sensor to serial over USB, via a compatible adapter, write an app and there you go. Of course it won't be standard Android though.

Drivers are here
https://elixir.bootlin.com/linux/v4.14.133/source/drivers/iio/imu/st_lsm6dsx
The problem is adding them to kernel !

You dont need to add them to the kernel. You will need to implement an Android HAL that can read the values of these sensors. Its not a trivial task but also not very hard if you have access to the source code