Database Users

CONTRAST Adjustment

Hi all. Can anyone dir me to anywhere I can download apps for adjusting the screen contrast of xda2 (WM2005)? Thanx in anticipation.
bloggy

http://www.google.dk/search?hl=da&q=CONTRAST+Adjustment+wm2005&btnG=Google-søgning&meta=
?

Hi Rudegar. I had already googled it and seem not to get anything. Thanx for the concern anyway.
bloggy

Built in Contrast adjustment
I know there is a built in Contrast adjustment program in WM5. After doing some some registry tweak testing...basically me changing registry settings without any direction, I must have stumbled on something that activated a Contrast program icon.
When I ran it, there was a slider for screen contrast. I continued some more registry tweaks, but restored an old registry and lost the new Program Icon.
I don't know what registry setting it was that activated this, so if anyone knows how to activate it, please let us know!

Re: Built in Contrast adjustment
our screen driver (or maybe hardware) does not support contrast changing, so this is useless. Only backlight brightness can be changed.

I've discovered a registry key that seems to have _some_ control over not contrast, but gamma. You might be able to use it to get some results. Its located in HKLM/System/GDI/Gamma and it is a DWord called "Gamma Value"

Re: Built in Contrast adjustment
mamaich said:
our screen driver (or maybe hardware) does not support contrast changing
Click to expand...
Click to collapse
There is no hardware contrast support on himalaya, blueangel and universal, only the
brightness control via PWM duty period.

I'm not sure if it works on other devices, but on a Wizard, you can go to HKLM\ControlPanel\Contrast and delete the redirect key (if there is one) and create a new dword value named Group with value 0 and it will put a Contrast icon in Settings that has an adjustable slider....

works...
registry tweak brings contrast setting to control panel but that does nothing (since contrasting is not supported)

Auto brightness code

Hi Devs
I need some help to set my own auto brightness values. Attached is the framework can someone please help me find the code for auto brightness.
The frame work I am using can be found at the below link:
http://dl.dropbox.com/u/17206474/framework-res.apk
Regards,

lol so many views and no reply
no one know what should I do??? :s

I am also interested in this field.
I would start with a simple cronjob that reads brightness.
Do you know, where to read it?
background:
For the Motorola's there is some magic setting, boosting the backlight.
Would like to set it, if brightness is over a certain threshold and set back if it is below another level. Sounds easy ...

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?

[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

change the sensitivity of your touch screen

Hello all,
I have seen several reports in internet about screen sensitivity issue regarding s7 & s7e varients. some says that it is too sensitive, while some say its less.
In my case,afterinstalling a .4 mm 9H glass screen protector, my screen sensitivity became awfully down,it wont recognise my targus touch input pen anymore,unless i press the rubber tip really hard, also several misses of finger touch input too.
being so, i was thinking of removing the screen gaurd itself, but from my experience, i know that this can be adjusted by editing system files. again, i forgot ( since i dont play with roms much now a days) it, and last night i stuck upon my collection of android tweaks.. and find something interesting.
so i want to share it with you.
You need root access to do this tweak, as we are going to edit build.prop and touch screen calibration file.
1 ) go to system/build.prop , open it with some text editor, add these lines to it ( i prefer xplore filemanager, becoz it is cool and automatically set previous permissions)
ro.max.fling_velocity=16000
touch.pressure.scale=0.00000001
ro.min.fling_velocity=8500
windowsmgr.max_events_per_sec=290
ro.min_pointer_dur=9
2) save it back and then go to system/usr/idc and find the file named " ft5x06_ts.idc ". its the touch screen calibration file. open it as text ( some filemanagers require to rename it as .txt extension, if its so, rename and open it. then edit this line as
touch.pressure.scale=0.00000001
3) save and rename it back to " ft5x06_ts.idc " and set back permissions.
reboot your phone.. now ur phone have much more sensitive screen.
NB:- the normal touch.pressure.value is 0.015 for s7. ( as found in ft5x06_ts.idc file). we have changed it to a much smaller value of 0.00000001 , to make it more sensitive.
you can decrease that value further to make it more sensitive or you can increase that value to 0.100 or so to decrease sensitivity ( remember to add same value on build.prop and .idc file , to avoid conflicts.)
thanks all.. hope this will sort out your touch screen problem.

I don't have that file. I'm running a stock S7, rooted, original ROM in all ways just like most everyone else. Mine is brands new and I've not made any other mods yet. Can you verify the filename and folder is correct?
Are there any other changes you may have made beforehand, that may have created that file? Did you try any of the touch screen calibration apps that I've seen online by chance?
I can try creating the file, what else is in its contents? Can you attach it here, or copy its contents to the screen here if short enough?
Great information, you're the only one writing about this yet. I appreciate it because I was looking for the same thing and I knew it was possible. I can confirm I've read similar on the Android developers website. There's tons of settings related to the touchscreen listed there, and the sensitivity setting you reference seems to be the most important.
I've seen other people reference adding that setting into build..prop. Have you heard that, or tried that by chance? Any feedback? On my S5, it didn't seem to make any difference regardless of what I set it to in the build.prop settings. Perhaps it's the same on the S7. Surprised I don't have the same file that you reference though...? Mine is Verizon. Yours?
---------- Post added at 09:54 PM ---------- Previous post was at 09:17 PM ----------
showlyshah said:
Hello all,
I have seen several reports in internet about screen sensitivity issue regarding s7 & s7e varients. some says that it is too sensitive, while some say its less.
In my case,afterinstalling a .4 mm 9H glass screen protector, my screen sensitivity became awfully down,it wont recognise my targus touch input pen anymore,unless i press the rubber tip really hard, also several misses of finger touch input too.
being so, i was thinking of removing the screen gaurd itself, but from my experience, i know that this can be adjusted by editing system files. again, i forgot ( since i dont play with roms much now a days) it, and last night i stuck upon my collection of android tweaks.. and find something interesting.
so i want to share it with you.
You need root access to do this tweak, as we are going to edit build.prop and touch screen calibration file.
1 ) go to system/build.prop , open it with some text editor, add these lines to it ( i prefer xplore filemanager, becoz it is cool and automatically set previous permissions)
ro.max.fling_velocity=16000
touch.pressure.scale=0.00000001
ro.min.fling_velocity=8500
windowsmgr.max_events_per_sec=290
ro.min_pointer_dur=9
2) save it back and then go to system/usr/idc and find the file named " ft5x06_ts.idc ". its the touch screen calibration file. open it as text ( some filemanagers require to rename it as .txt extension, if its so, rename and open it. then edit this line as
touch.pressure.scale=0.00000001
3) save and rename it back to " ft5x06_ts.idc " and set back permissions.
reboot your phone.. now ur phone have much more sensitive screen.
NB:- the normal touch.pressure.value is 0.015 for s7. ( as found in ft5x06_ts.idc file). we have changed it to a much smaller value of 0.00000001 , to make it more sensitive.
you can decrease that value further to make it more sensitive or you can increase that value to 0.100 or so to decrease sensitivity ( remember to add same value on build.prop and .idc file , to avoid conflicts.)
thanks all.. hope this will sort out your touch screen problem.
Click to expand...
Click to collapse
UPDATE -After digging around a bit, I found two idc files related to touchscreen settings in that same folder. They are named Synaptics_HID_TouchPad.idc and Synaptics_RMI4_TouchPad_Sensor.idc. Their contents reference "Input Device Configuration File for the Atmel Maxtouch touch screen" and "Atmel Maxtouch touch screen" respectively. All the standard touch screen settings are present, but specific to touch.pressure.scale, both are set to 0.0125. Again, slightly different, but this is a Verizon variant, I'm not sure what year it is. I know each touchscreen requires its own set of configuration settings, and it's not expected they would all calibrate and matchup to the same settings. It also wouldn't be the first time Samsung use different pieces of hardware in the same device, let alone the carriers might provide their own input and/or make those choices autonomously as well. What does yours list as the make and model of the touchscreen device? Do you have just the one file referencing touch screen, or are there multiple files like mine?
I'm not sure what specific touchscreen hardware is installed in my device. I know I could go check, but I'm feeling lazy and think I'll just modify them both and see what happens.
I'll provide updates as I learn more...

ya.. thats it.. every android device shd contain some sensor specific file for every sensor used. or lets say some configuration file.. and touch screen too..
btw.. that touch pressure scale is what u need to change.

why the hell does Samsung doesnt set it in 0.00001 in first place -_-
Has anyone else tried/working this workaround?
Not rooted here but will root if it works ^^

Velogr1992 said:
why the hell does Samsung doesnt set it in 0.00001 in first place -_-
Has anyone else tried/working this workaround?
Not rooted here but will root if it works ^^
Click to expand...
Click to collapse
It wont work ! That guy iz suck !

How much can we maximum decrease touch pressure scale value