Database Users

Any way of preventing screen rotate to portrait ?

Just wondering if there is a registry hack that stops the screen from automatically rotating and displaying in portrait mode when you flip the screen round ?
i.e. it should stay in landscape mode no matter if the screen is facing in/out or otherwise.
You can do it manually by clicking on the screen rotate icon, or going into Settings > Screen > Orientation, so I figure there must be a reghack to put it permanently into Landscape ?
tia

Ok, i've found the key at least which shows what mode is currently in use:
This is Landscape (Right-handed) mode:
HKEY_LOCAL_MACHINE\System\GDI\Rotation
Angle 0x5A (90)
HideOrientationUI 0x0 (0)
LanscapeMode 0x1 (1)
The question is, how do I stop those being overwritten or change it so when it's in Portrait mode, it actually uses those settings ?

gaspx: I'm an odd fellow. I'd written you a long post about basically:
rotation is achieved at OS level, and driver level, so althought it's possible to be notified of the screen being rotated, intercepting it would require, AFAIK, some fairly substantial low level code or a reg key I'm not aware of.
But then I remembered my work on the Universal Voice Command/External Key issue in another thread. I've written a test program called VJElectrify, which contains a hack called ClamHack. And I just tried clamhack, and amongst its other side effects, yes, it does allow you to prevent the system forcing a rotation. So system stays in landscape if you open in laptop mode, or rotait into portrait mode. You then manually choose your rotations.
VJElectrify isn't finished yet, still a lot more research to do, but yes, it is possible to prevent it Keep an eye out for when VJElectrify is released.
Anyone else know another way to do this? I can't think of any relevant reg settings.
V

Heh heh, I knew it probably wouldn't be as simple as a reg hack.. cheers for the reply Vijay, i'll keep a watch on your website for the forthcoming VJElectrify..

gaspx said:
Ok, i've found the key at least which shows what mode is currently in use:
This is Landscape (Right-handed) mode:
HKEY_LOCAL_MACHINE\System\GDI\Rotation
Angle 0x5A (90)
HideOrientationUI 0x0 (0)
LanscapeMode 0x1 (1)
Click to expand...
Click to collapse
Thats just the keys where the current state is stored.
the key you need is HKLM\Services\ScreenRotate (you can change the ShowIcon value here to enable/disable the today icon)
Ive tried just renaming the ScreenRotate but that failed then i tried changing the dll name stored in the key, after all if it cant find the dll surlly it'll stop the rotations.
NOPE, i know the dll rename is working as the icon failed to appear, but the auto rotates continue to happen, it must be OS, it must be!!
.....the search continues

Ive tried just renaming the ScreenRotate but that failed then i tried changing the dll name stored in the key, after all if it cant find the dll surlly it'll stop the rotations.
Click to expand...
Click to collapse
I did that as well.. sorry, should've mentioned it in my original post, but I had the same idea as you! - the screenrotate.dll just seems to be tied to the icon in the systray. sigh.
Have to wait patiently for the VJClamhack to be released..

The clam hack has, by design, side effects - it disables part of the system OS, which conveniently disables screen rotation detection and some other stuff on the hinge. However, the bugger refuses to enable hardware keys with lid closed.
Because clamhack is quite a big sledgehammer for a nut, I'm a little worried about putting it out - however, I've never seen any negative sideeffects, only positive
V

Load DinarSoft MemMaid on your Universal.
Just as you can delete Startup Items, you can also delete Start Up Services. I believe I saw a service related to screen rotation in there.
I don't have my Universal for another week (getting replaced), but I do recall seeing that in there.
As always, perform a backup in case you can't "add" it back in.

I don't think that Rotation service helps, I tried it a bit earlier, since it seems to be an obvious target.
V

However, the bugger refuses to enable hardware keys with lid closed.
Click to expand...
Click to collapse
Thats OK, i don't need to use hardware keys when it's closed -- I figure this is part of a bigger problem you're looking at..
ust as you can delete Startup Items, you can also delete Start Up Services. I believe I saw a service related to screen rotation in there.
Click to expand...
Click to collapse
Yeah, I think that was the one Carnivor and myself had found.. we just prevented the service starting manually by bodging the registry key, but all it does is stop the little screen rotate icon from appearing.. thanks though

Has anyone figured this out yet?
Thanks

disallow screen rotation

Hello!
I need to write software that disallows any screen rotation on my Wizard.
How can I do it? I didn’t found any registry settings for this. The best way
that I see is hooking ChangeDisplaySettingsEx. But unfortunately, SetWindowsHookEx
doesn’t works on WM 5.0, at least it said on some topics. Please, give me any solution for this problem or example code to hook some API function.

wm5: [HKLM\System\GDI\Rotation]
Angle=dword:0
00000000 portrait
0000005a righthanded landscape
0000010e lefthanded landscape
then RegistryNotifyCallback will do

tanks a lot
I will try this way.
But I afraid it will be notified after screen rotation starting.
Adjusting this registry value in regedit tool did't help.
So I suppose this value is changing after rotation is done.

You can delete the start up service of ScreanRotate.
Go to HKLM/Services/ScreanRotate and delete it.
I think before you doing this,you can export it to a reg file

It's not bad idea.
but delete this key leading to system restart for apply
I just try to stop this service.

Not luck : (
This key not present in the registry storage.
I am under WM 5.0
Maybe you talk about some early system.

Hi hoblano, I'm experiencing the same problem, did you find a solution ?
thanks,
Scalposcarno

use task manager 2.7 and stop service...if you know it is service...
same way to stop kbd lights...btw,

I tried, but the result is the same as the one obtained by manually deleting the Screen Rotate voice within the services voices in the registry: avoiding the load of the service providing the icon on the task bar enabling the user to rotate the sceen one or more times by tapping on it.
I still don't understand ... at this point the most probable thing is that the service that rotate the OS screen when rotating by hand the HW screen, is invisible with respect to registry voices and to applications like Task Manager 2.7 or MemMaid. Apart from criticizing the constructor choice (why didn't they thought that someone should have been more comfortable using only one view mode ? e.g. landscape one), is there a way to obtain a list of core services and to avoid one of those to be loaded ? or, otherway, is there a way to intercept the event thrown when manually rotating the screen of the terminal ?
By the way, I'll have to do it with Java ...
thanks all

[Q] Lights driver for CM light sensor level

Hi,
I'm currently on a CM Build and the CM-Feature for changing light sensor levels is not working.
I know that this will make led notifications not work anymore.
But I would like to test how much this can improve my battery life.
Please don't tell me "turn auto backlight off to save battery" or "this will disable led notifications"... I'm aware of the pro's and con's and it is just a test for me...
So could someone please tell me which files I need to replace and where can I find them?
Thx in advance!

I'm also using the working lights lib...
LED notifications isn't that important for me.
The name of the file is different from rom to rom, so ensure you name it correctly and replace it in system/lib/hw.
Also don't forget to set the right permissons.

j4n87 said:
I'm also using the working lights lib...
LED notifications isn't that important for me.
The name of the file is different from rom to rom, so ensure you name it correctly and replace it in system/lib/hw.
Also don't forget to set the right permissons.
Click to expand...
Click to collapse
Thx. I tried this file. Renamed it, moved it with RootExplorer. Set Permission to rw-r--r--. Rebooted. edited light sensor levels with cyanogenmod-settings. taped save and apply. but it does not work. when i press reload current they are back to default values. alo tried reeboot after save and apply. But with the same result.
Is there anything I did wrong??

Did youu checked your pm? =)

Disable Proximity Detector HD2 (Android)

Having searched for months, I have now found a solution:
I. Install Android Sensor Box from the market, run it and identify the sensor: click the green leaf, click on the small file bottom left and read the sensor's name. For my HD2 it was CM3602 Capella Microsystems
Then install Hardware Disabler from the market: and find the same sensor's name, check the box next to it, exit and reboot. I had a problem with this but guessed is was 006 (NOTE: 000 is the touch screen - so don't press this)
When rebooting, keep on looking at your phone utill you get a pop up message asking to agree or not for disabling the hardware and for sure choose yes I agree.
(all this assuming your phone is rooted).
Regards
ANDREW

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