Database Users

how to calibrate/align touchscreen

could anyone help me how to align the touchscreen manually? i found a thread somewhere where it says that calibrating the touchscreen has 5 coordinates. i dont know which one goes where and the values of each. i tried the suggested values on that thread but it seems to be a bit misaligned when i reach the top part of my touchscreen. what im asking is how the x and y value of each coordinate contribute to the alignment of the touchscreen. help much appreciated.

For screen:
Start;Setting;System;Screen. Then click on (align screen)
For touchscreen:
Some of the older version of FTouchFlo has a calibrate.exe after installation (I think alpha4 has it)

what i was askin was manually, meaning, editing the registry value on calibrationdata. i wanna know how each value affect the alignment of the screen. there are 5 coordinates on that registry key, so i wanna know how each affect the calibration.

Lapdock resolution is off?

Strange situation. I got the lapdock a few days back from the sale and I'm running Darkside w/ Fruitcake 2.3.5 webtop. I plugged it in, everything works (although by god it boots slowly) except the desktop doesn't go to the edge of the screen. There's a black margin around the display that my mouse cannot reach. The displayed screen is smaller than the actual LCD screen.
I had tried fastboot wipe webtop and reinstalled fruitcake with no improvement. I had also tried webtopmod1 and the issue persists.
Any ideas?

maybe lcd density settings can/are messing with it? just throwing that out there.

I had the same issue on my hacked webtop. I resolved it by editing my /etc/X11/xorg.conf file.
Towards the bottom are "Screem sections". These define possible choices for screen layouts. In my file, the second of these Screen sections has an Identifier "Screen HDMI". In this, you can set the mode and virtual screen size. Set these both to 1366x768.
You obviously need root, and a way to edit the file. Once edited, reboot (clsing and opening the dock does not restart X).
Original:
Code:
Section "Screen"
Identifier "Screen HDMI"
Device "Tegra HDMI"
Monitor "HDMI"
Option "ARGBHWCursor" "false"
DefaultDepth 24
SubSection "Display"
Depth 24
# Uncomment to override the preferred resolution chosen by UseEDIDModes
Modes "1280x720"
ViewPort 0 0
# Defaults to the size of the chosen mode
Virtual 1366 1024
EndSubsection
Corrected:
Code:
Section "Screen"
Identifier "Screen HDMI"
Device "Tegra HDMI"
Monitor "HDMI"
Option "ARGBHWCursor" "false"
DefaultDepth 24
SubSection "Display"
Depth 24
# Uncomment to override the preferred resolution chosen by UseEDIDModes
# Modes "1280x720" Orig
Modes "1366x768"
ViewPort 0 0
# Defaults to the size of the chosen mode
# Virtual 1366 1024
Virtual 1366 768
EndSubsection
There might be better ways, but this worked for me.
NOTE: The virtual line need not exist at all per the comments

That was amazing! Thanks. It was way above my head and I'm glad someone can fix it.

Does this change work for the entertainment center also?
My webtop fits the lapdock screen just fine, but when I use the entertainment center, video is squished horizontally leaving 2 black vertical stripes on the sides.

exwannabe said:
I resolved it by editing my /etc/X11/xorg.conf file.
Click to expand...
Click to collapse
Is there a way to edit the xorg.conf file right on the phone? Or do you adb copy it to a pc, edit it, and copy it back?

J252 said:
Is there a way to edit the xorg.conf file right on the phone? Or do you adb copy it to a pc, edit it, and copy it back?
Click to expand...
Click to collapse
I am happy using vi in a terminal, but I assume that there are many text editor apps available.
I would caution you to be carefull though. Make a copy of the file first.
I have never used the entertainment center. so can not help you. If is is still 'droid though (and not a webtop flavor), this will not have an affect.

In my case when this happens, I fix it with a simple StartX command on LXTerminal.
However, ever since I went to Fruitcake 2.3.5 Webtop, the screen res change problem hasn't happened again.
Cheers!
Rayan

Lapdock resolution is off??
Hi Everyone...I hopeI am not bothering anyone, even though I haven been reading lots of post with no luck about this issue... I am experiencing this same issue with the lapdock, it does not run at fullscreen, there are black bars all around.
I am running stock firmware 2.3.6 with webtop version WT-1.2.0-110_OLY-6 // Also the only modification I've done to the phone is that I root it...
One strange thing is that when switching to the entertaiment center it work at fullscreen! but not in webtop...
I already tried modifing the xorg file using Root Browser with same results, I've also use startx command from lxterminal but it keeps not showing at fullscreen.
I am still afraid of using webtop from fruitcakes as I am afraid to ruin the phone (n00b....reallly n00b)....so I would like to know if anyone has any other thoughts before testing with fruitcake?

how can i edit the height of softkey

hey all
as i found, we edit /system/build.prop as follow
change
qemu.hw,mainkeys=0 can enable softkey
change
ro.sf.lcd.density=240 we can change the resolution ratio
but when i change the value of ro.sf.lcd.density from 240 to 260 and reboot
the screen size of HD2 become ugly, font size are too big and cover one by one.
and the icon became more big too
which parameter can i change to fix this issue
all i want to do is resize the bottom navigation bar without changing anything else.
my current ROM is HD2 android [4.0.4][720p] NexusHD2-ICS-CM9-HWA V2.9a [NativeSD]
hope you guys can help me

I usually find mine in the settings & set it to around 24 so that it can be as small as possible

mengfei said:
I usually find mine in the settings & set it to around 24 so that it can be as small as possible
Click to expand...
Click to collapse
yes, but i try to find a usual method to config it out, many of ROMs doesn't give a UI support of this issue

OP, try to follow these instructions
http://forum.xda-developers.com/showthread.php?t=2227668

The density setting in build.prop changes every size onscreen not just the bottom like you need.
Sent from my SGH-T889 using xda app-developers app

[TIP] Adjusting DPI without root

How to adjust your DPI without root, I believe the current DPI is around 300 I could be wrong.
To adjust the DPI follow the steps below, THIS DOES NOT REQUIRE ROOT.
Open settings and scroll all the way down to About
Open Software Information
Tap the build number quickly a couple times till it says "You're now a developer"
Head back into the main settings page and open the new Developer Options
Enable USB debugging
Install ADB on your computer (there are plenty of tutorials out there if you don't know how)
Start ADB and check if you see your device by typing
Code:
adb devices
If you see your phone go ahead and type
Code:
adb shell wm density 250
Reboot your phone to apply the effects system wide.
250 is the DPI set which I think looks the best for me. Adjust how you like it
NOTE: IT WILL LOOK WEIRD AT FIRST, REBOOT YOUR PHONE!

This is a great method. Use it often. Couple more commands:
Code:
adb shell wm density reset (set to default)
adb shell wm size 1080x1920 (emulate whatever resolution)
adb shell wm size reset (set to default)

What Screen Resolution have you chosen?
Chinaphonearena said:
This is a great method. Use it often. Couple more commands:
Code:
adm shell wm density reset (set to default)
adm shell wm size 1080x1920 (emulate whatever resolution)
adm shell wm size reset (set to default)
Click to expand...
Click to collapse
I noticed in the pics from your review consisted of smaller icons. I am assuming you changed the DPI to 250. I would like to know if you have tinkered with your screen resolution as well. If yes can you show us some screenshots? Does that have any other benefits like battery performance and processing speed?

sanjeevopeth said:
I noticed in the pics from your review consisted of smaller icons. I am assuming you changed the DPI to 250. I would like to know if you have tinkered with your screen resolution as well. If yes can you show us some screenshots? Does that have any other benefits like battery performance and processing speed?
Click to expand...
Click to collapse
Yes, you're correct the dpi was changed. There's no performance gain I see. I do this so I can fit more on the screen at once within apps, while browsing etc... For me this is half the value of an HD device - you can shrink stuff down to fit 2x as much, but tiny text still remains comfortably legible.
This can also be done within terminal emulator. For me, not successful unless entering su.

nice way to adjust animations on your phone..its now fast without the animation by the way i need help i accidentally touch the Logger Buffer Sizes....its under settings..developer options...scroll down you will see. logger buffer sizes...now there are number to choose from..64k..256k...1m...4m...16m.... now would like to ask if what is your default value in your phone"? want to do default...whats the diffence it do when you change those settings 64...256...etc....tnx

pato2015 said:
nice way to adjust animations on your phone..its now fast without the animation by the way i need help i accidentally touch the Logger Buffer Sizes....its under settings..developer options...scroll down you will see. logger buffer sizes...now there are number to choose from..64k..256k...1m...4m...16m.... now would like to ask if what is your default value in your phone"? want to do default...whats the diffence it do when you change those settings 64...256...etc....tnx
Click to expand...
Click to collapse
Mine is 256k. That should be how much data is held in the logs.

thanks...got it...it just goes to default by itself when closing developer option......

This is pretty cool, is there an adb command to readout the density what ever it's currently set at?
I ended up at 390, it gives a nice 5x5 grid.

Thanx, work fine! A little notice: Asus Powermanagment end in force closed when you change the DPI. Went back to orig. 480 and it works, when you need it
And next big issue Swift key doenst work with changed DPI. When changed i saw only a few very!! big letters. Keyboard not useable.

Thanks OP!
The issue with swiftkey is well known and documented, just search Google for it (XDA says I don't have enough posts to post links yet). It looks like there's a fix, but it requires root. I switch to the Google keyboard and it works fine with modified DPI.
FYI, density setting of 460 is the lowest (stock is 480) that will keep the widget width taking up the whole screen for wide widgets. Makes everything a little sharper than stock, which was needed.

The hardware keys below the screen also stop working when the screen resolution is changed.

tasar said:
Thanx, work fine! A little notice: Asus Powermanagment end in force closed when you change the DPI. Went back to orig. 480 and it works, when you need it
And next big issue Swift key doenst work with changed DPI. When changed i saw only a few very!! big letters. Keyboard not useable.
Click to expand...
Click to collapse
ZenMotion touch gestures config also crashes.
As for swiftkey, you could probably use xposed appsettings to adjust its dpi/dp settings.

ziddey said:
As for swiftkey, you could probably use xposed appsettings to adjust its dpi/dp settings.
Click to expand...
Click to collapse
I have test it with AppSettings at first but no luck or i do something wrong. I have set DPI to 480 all other at default but same as before.

tasar said:
I have test it with AppSettings at first but no luck or i do something wrong. I have set DPI to 480 all other at default but same as before.
Click to expand...
Click to collapse
Try a different DPI. 480 is extreme and some apps simply won't work properly at such a high setting.

After doing this, how to revert to the original one???

dineshdotcom2000 said:
After doing this, how to revert to the original one???
Click to expand...
Click to collapse
adb shell wm density reset

Chinaphonearena said:
Try a different DPI. 480 is extreme and some apps simply won't work properly at such a high setting.
Click to expand...
Click to collapse
480 is original dpi

tasar said:
480 is original dpi
Click to expand...
Click to collapse
Tasar, I stand corrected. 480 it is.

Application settigs
Anyone having problems with some applications after using this mod? I am having issues with viber(photos sent wont open properly- always zoomed in and i cannot see the entire photo and no option to be zoomed out) and instagram as well. Hope anyone can help me with this. Thanks

Photo Studio pro the same problem, see only a quarter of the pic, cant zoom it to full. App settings doenst help

touch screen working with XY axis rotated at 90 degrees

After replacing the original LCD and touch screen the new one works , but the touches are not at the correct places. The touch screen is rotated at 90 degree of the LCD orienatation. So I need app that lock the xyz axis and they will not change with a change in the device orientation.
Please help!

bascho said:
After replacing the original LCD and touch screen the new one works , but the touches are not at the correct places. The touch screen is rotated at 90 degree of the LCD orienatation. So I need app that lock the xyz axis and they will not change with a change in the device orientation.
Please help!
Click to expand...
Click to collapse
Hello, did you find any solution? I've the same problem after replacing. Searcing web i see that there is the possibility to correct inverted axis editing the script.bin file. Today i've rooted the tablet but since now i've no found this file. Any idea? For root I used this procedure :https://forum.xda-developers.com/ze...g-twrp-rooting-asus-zenpad-10-t3612693/page31
The first with the scatter file and works very well .
The parameters to change (0->1 or 1->0) in the script.bin are :
ctp_revert_x_flag = 0
ctp_revert_y_flag = 0
ctp_exchange_x_y_flag = 0
I hope that someone expert could help us to find this file and how to edit.
Thanks to everybady in this forum for the help and the guides.
Ren

I just fixed someone tablet, but the fix is kinda wonky
If you already have root, then use a root explorer app to edit the file /system/build.prop
Look for a line that says
ro.sf.hwrotation=90
THen I've changed the value to 270, save, then reboot
What this does, if I understand correctly is rotate the screen 180 degrees, I have to disable auto rotate, but now the screen touches where it should touch, kinda of an alternative solution