About android touchscreen

by Anson » Mon, 10 Nov 2008 17:19:03 GMT


Sponsored Links
 Hi all:

We use a resistance touch screen .

the touch screen 's raw input driver will return some ABS_EVENT, and
BTN_TOUCH input events,
but the value of ABS always too big, and for some reason, the touch screen
must re-calibrate.

Our solution is like this:
we ues touchscreen library such as tslib, to convert this big ABS value to a
suitable value for the application use,
and some times , we need calibrate the touch screen, for this , we also can
use tslib's calibrate application.

You can run a daemon under your system, it read from raw input interface
provides by driver, and inject to android input interface , such as
/dev/input/event0.

ps: may be some modify of android code is needed, for prevent android
eventHub compete with you daemon.








--~--~---------~--~----~------------~-------~--~----~
unsubscribe: [EMAIL PROTECTED]
website: 



About android touchscreen

by Sean McNeil » Mon, 10 Nov 2008 17:54:06 GMT


 I have submitted patches to Google which adds support of a 
/system/etc/pointercal (aka. tslib) file for translating coordinates. I 
didn't add ts_calibrate into the phone, however. That would be nice to 
have so you can calibrate the screen on 1st install.







--~--~---------~--~----~------------~-------~--~----~
unsubscribe: [EMAIL PROTECTED]
website: 


Sponsored Links


About android touchscreen

by Anson » Tue, 11 Nov 2008 15:18:05 GMT


 pointercal only can create by ts_calibrate ?

If you wann't to calibrate the screen on 1st boot, you may should add
ts_calibrate program into your system,
and modify the init.rc to support 1st booting salibrate ?

ps: how can i patch my work to android code base(the git base)?









--~--~---------~--~----~------------~-------~--~----~
unsubscribe: [EMAIL PROTECTED]
website: 



About android touchscreen

by girish » Tue, 11 Nov 2008 16:32:46 GMT


  have integrated tslib ts_calibrate and fbutils in android filesyste. After
android is up, i try to run tslib binary but it shows up fb for fraction of
sec and goes off. It exits with invalid memory access. fbuilt does a mmap
and i guess android is not allowing it to have it. looks like android has
plugged in mmap interface, need to check.

--Girish SG

On Tue, Nov 11, 2008 at 9:17 AM, Anson <[EMAIL PROTECTED]> wrote:


--~--~---------~--~----~------------~-------~--~----~
unsubscribe: [EMAIL PROTECTED]
website: http://groups.google.com/group/android-porting
-~----------~----~----~----~------~----~------~--~---



About android touchscreen

by ajay » Thu, 11 Dec 2008 06:35:54 GMT


 Hi
    Where can I get your patches?
    I would like to use your patches to test the touch screen of my
Board ( Arm -11 , SMDK6400)

Thank you
Regards
Ajay







--~--~---------~--~----~------------~-------~--~----~
unsubscribe: [EMAIL PROTECTED]
website: 



About android touchscreen

by Elvis Dowson » Tue, 28 Apr 2009 23:45:18 GMT


 Hi Sean,
           Can you provide me a link to these patches, please? I am
working on a port of android-2.6.29 to the Overo TI OMAP 3503 platform
and working on the touchscreen issue right now.

Best regards,

Elvis




--~--~---------~--~----~------------~-------~--~----~

-~----------~----~----~----~------~----~------~--~---



Other Threads

1. Why can't I post

I really don't understand why I have not been able to post. I have decided
to start my own group. Thanks for the great reads, and I hope nobody treats
u as I have been treated.

sent on location from my Motorola Droid

--

2. Creating DEMO and FULL versions

I have a couple of apps for which I have 2 different versions.  Code
executes conditionally based on R.string.isDemo.  Everything works
great until it's time to publish to the Market.  The Market
(understandably) requires different package names.

So, here's what I started doing - I develop the FULL version in
Eclipse and test it.  When I'm done, I make a copy, import that into
Eclipse and refactor it to change the package name.  When I try to
install to my dev phone, I get the following error:

"Re-installation failed due to different application signatures."

OK, so I understand what's going on here, but my question is this- if
I publish this version to the Market, will it require users to
uninstall and reinstall their copies?  That's not exactly a seamless
process and I don't want the users' databases to be deleted, either.

I really don't want to maintain two versions by adding/testing the
same code in two different projects.  That is a formula for mistakes
and oversights.  Is there some other way?

Maybe when I export the Signed App Package, everything will be fine?

--

3. Android, send me logs! - code library for detecting force-close and sending logs

4. Display images

5. java.lang.IllegalArgumentException: Illegal character in query when using posting data to a url

6. Will TCP Sockets work over cellular network?

7. Eclair's opencore does not compile