Hi Manoj, If the original screen resolution is 320x240 and touch pad size is 800x480, then the map relation is between 320x240 to 800x480.
Let me take my example. My device is samsung s5pc100-'smdkc100' with original screen resolution 480x272 and touch size 800x480. Then for some reason I need to change the screen resolution to 320x240 to make the display size looks smaller. So what I did is firstly I change the screen size in the related framebuffer config file where it defined the original 480x272 to 320x240. Then I got the issue that touch pad size is out of the new screen size. So I secondly changed the ABS size in s3c-ts.c from 800x480 to 533x424. (800*320/480=533 480*240/272=424). Then the touch pad size fitted the new screen size. It is a little bit strange that why your device changed orientation from horizontal to vertical since you swapped the 320x240. I'm going to test your case on my device and give your feed back. Jack 2011/5/24 Manoj Kumar <manoj...@gmail.com>: > Hi Jack, > > I did one more experiment i checked the original resolution and > original touchscreen config without any change > That is 320x240 and touch ABS_X=800, ABS_Y=480 > This also has touch shifted by 90 deg and the image comes to only 75 % > of the screen (which is i think ok considering the resolution) > > So i tried to change the touch to X=320, Y=240 in 320x240 res. and the > touch sensitive area decreased to top right corner of the screen > > Can u infer anything from this, i am kinda confused. > > thanks and regards > Manoj > > On May 24, 12:36 pm, "Jacky.Seraph Mun" <jackyser...@gmail.com> wrote: >> Hi Manoj, >> >> If you made it by changing in framebuffer device, you may also have to >> change the touch pad abs size accordingly. So you have to take a look >> at the driver of touchscreen, which is usually located in >> drivers/input/touchscreen/xxx-ts.c >> where it defined the touch pad abs size in the __init_xxx_probe() function. >> >> input_set_abs_params(ts->dev, ABS_X, 0, >> /*CONFIG_TOUCHSCREEN_SIZE_WIDTH*/, 0, 0); >> input_set_abs_params(ts->dev, ABS_Y, 0, >> /*CONFIG_TOUCHSCREEN_SIZE_HEIGHT*/, 0, 0); >> >> Then you need to change the the abs_x and abs_y according to the >> change in your screen resolution. e.g. if you screen resolution is >> changed from 320x240 to 240x320, your new touch width size should be >> old_TOUCHSCREEN_SIZE_WIDTH * 240 / 320 and old_TOUCHSCREEN_SIZE_HEIGHT >> * 320 / 240 for new height. >> >> Hopefully, it can solve your problem. >> >> Jack >> >> 2011/5/24 Manoj Kumar <manoj...@gmail.com>: >> >> >> >> >> >> >> >> > Thanks Jack, >> >> > I have seen the file where resolution is set and i have changed it >> > according to my screen (240x320), >> >> > but the problem is that the touch is still working assuming screen is >> > 320x240 (i.e. the touch is 90 deg shifted) >> > can u please help me with this, what else i should change so that >> > touch gets aligned to the screen >> >> > thanks >> > Manoj >> >> > On May 23, 10:01 pm, "Jacky.Seraph Mun" <jackyser...@gmail.com> wrote: >> >> Hi, >> >> >> You need to modify the file of the framebuffer in the kernel. You have >> >> to find the related framebuffer driver that is for your device and >> >> then change the screen resolution accordingly. And you don't need to >> >> consider the orientation. Android system will determine if it is >> >> landscape or portrait according to the screen resolution width and >> >> height returned from kernel framebuffer (Be portrait if width <= >> >> height, or landscape if not). You can grep more information about the >> >> orientation in this group. >> >> >> Jack >> >> >> 2011/5/23 Manoj Kumar <manoj...@gmail.com>: >> >> >> > hi, >> >> >> > i need to change the screen resolution to 240x320 and then >> >> > correspondingly the screen orientation from landscape to portrait. can >> >> > anyone please suggest which files have these settings in android >> >> > eclair 2.1. >> >> >> > i am using LTV350QV.c and default configuration in that is 320x240. >> >> >> > thanks >> >> > Manoj >> >> >> > -- >> >> > unsubscribe: android-porting+unsubscr...@googlegroups.com >> >> > website:http://groups.google.com/group/android-porting >> >> > -- >> > unsubscribe: android-porting+unsubscr...@googlegroups.com >> > website:http://groups.google.com/group/android-porting > > -- > unsubscribe: android-porting+unsubscr...@googlegroups.com > website: http://groups.google.com/group/android-porting > -- unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting
