Digma Plane 7594 3G stretched image problem - General Questions and Answers

On my Digma Plane 7594 3G tablet I have a problem with stretched (or compressed, depending on screen orientation) image.
"dumpsys display | grep DisplayInfo" (adb) output:
Code:
mDisplayInfos=
PhysicalDisplayInfo{600 x 1024, 60.0024 fps, density 1.33125, 426.386 x 149.411 dpi, secure true, appVsyncOffset 1000000, bufferDeadline 16666000}
mBaseDisplayInfo=DisplayInfo{"Встроенный экран", uniqueId "local:0", app 600 x 1024, real 600 x 1024, largest app 600 x 1024, smallest app 600 x 1024, mode 1, defaultMode 1, modes [{id=1, width=600, height=1024, fps=60.0024}], colorMode 0, supportedColorModes [], hdrCapabilities [email protected], rotation 0, density 213 (426.386 x 149.411) dpi, layerStack 0, appVsyncOff 1000000, presDeadline 16666000, type BUILT_IN, state OFF, FLAG_SECURE, FLAG_SUPPORTS_PROTECTED_BUFFERS, removeMode 0}
mOverrideDisplayInfo=DisplayInfo{"Встроенный экран", uniqueId "local:0", app 600 x 960, real 600 x 1024, largest app 960 x 928, smallest app 600 x 568, mode 1, defaultMode 1, modes [{id=1, width=600, height=1024, fps=60.0024}], colorMode 0, supportedColorModes [], hdrCapabilities [email protected], rotation 0, density 213 (426.386 x 149.411) dpi, layerStack 0, appVsyncOff 1000000, presDeadline 16666000, type BUILT_IN, state ON, FLAG_SECURE, FLAG_SUPPORTS_PROTECTED_BUFFERS, removeMode 0}
I guess there is a problem with "app 600 x 960, real 600 x 1024" (in mOverrideDisplayInfo).
Is it possible to change "app" values to math "real" values (if that's the problem)?

Related

[REQ] Adjusted autobrightness app/hack

Could someone write either
1) Autobrightness adjuster (to set which values autobrightness uses),
or
2) Make a modified autobrightness file with the following values,
Sensor = Brightness
10 = 50
160 = 60
225 = 70
320 = 80
640 = 115
1280 = 145
2600 = 185
10240 = 255
Thanks.
P.S. This is for the latest OTA or, preferably, for myn rls2 rom.
Anybody?
----------

[YeahPad A13 AllWinner] Wrong Display driver (Display is moved by 1 cm from left)

Hello everybody, I have YeahPad A13 (All Winner A13, 1.0GHz, Cortex-A8; GPU: Mali) after hours of searching found suitable rom, becouse other for this model deosn't event boot up, on other touch screen isn't working and display positioning is correct. Found 2 Roms with working touch screen on both display is moved by about 1cm from left, touch screen is in right position.
Is it possible to move display by 1cm back?
Extracted IMG file and there are many settings for Display and it driver, maybe any body knows what to look for?
COMMON _SYS_CONFIG100000:
[lcd0_para]
lcd_used = 1
lcd_x = 800
lcd_y = 480
lcd_dclk_freq = 33
lcd_pwm_not_used = 0
lcd_pwm_ch = 0
lcd_pwm_freq = 18000
lcd_pwm_pol = 1
lcd_if = 0
or some display drivers
[ctp_para1]
ctp_used = 1
ctp_name = "Gt811-TS",
ctp_twi_id = 1
ctp_twi_addr = 0x5d
ctp_screen_max_x = 800
ctp_screen_max_y = 480
ctp_revert_x_flag = 0
ctp_revert_y_flag = 1
ctp_exchange_x_y_flag = 1
ctp_int_port = portG11<6><default>
ctp_wakeup = portB03<1><default><default><1>
ctp_reset = portB03<1><default><default><1>
;ctp_io_port = portG11<6><default>
and so on
Click to expand...
Click to collapse
I would glad any help
Is it possible to move display by 1cm back?
Extracted IMG file and there are many settings for Display and it driver, maybe any body knows what to look for?
COMMON _SYS_CONFIG100000:
[lcd0_para]
lcd_used = 1
lcd_x = 800
lcd_y = 480
lcd_dclk_freq = 33
lcd_pwm_not_used = 0
lcd_pwm_ch = 0
lcd_pwm_freq = 18000
lcd_pwm_pol = 1
lcd_if = 0
or some display drivers
[ctp_para1]
ctp_used = 1
ctp_name = "Gt811-TS",
ctp_twi_id = 1
ctp_twi_addr = 0x5d
ctp_screen_max_x = 800
ctp_screen_max_y = 480
ctp_revert_x_flag = 0
ctp_revert_y_flag = 1
ctp_exchange_x_y_flag = 1
ctp_int_port = portG11<6><default>
ctp_wakeup = portB03<1><default><default><1>
ctp_reset = portB03<1><default><default><1>
;ctp_io_port = portG11<6><default>
and so on
Click to expand...
Click to collapse
I would glad any help
Bump* Added video if it would help
Pihas said:
Hello everybody, I have YeahPad A13 (All Winner A13, 1.0GHz, Cortex-A8; GPU: Mali) after hours of searching found suitable rom, becouse other for this model deosn't event boot up, on other touch screen isn't working and display positioning is correct. Found 2 Roms with working touch screen on both display is moved by about 1cm from left, touch screen is in right position.
Is it possible to move display by 1cm back?
Extracted IMG file and there are many settings for Display and it driver, maybe any body knows what to look for?
COMMON _SYS_CONFIG100000:
I would glad any help
Is it possible to move display by 1cm back?
Extracted IMG file and there are many settings for Display and it driver, maybe any body knows what to look for?
COMMON _SYS_CONFIG100000:
I would glad any help
Click to expand...
Click to collapse
the same thing with my windad 7 plus, i guess that the issue can be fixed if you change lcd_x = 800 for lcd_x = 752, actually i dont know how extract and repack img from manufacturers but if this works it will be helpfull if you can do this for me for my enjoy7+ tablet on this rom cm-10-20121023-UNOFFICIAL-rk2918.zip or on the original firm http://www.msi.com/service/download/firmware-18964.html
actually i dont know how it works
i hope this can be helpfull for you
thanks

[Q] [WM] 6.5.x taskbar height

Hello all,
Actually, this message should be posted in WM Dev&Hacking, but I'm a noob with less than 15 postings.
Does anyone know, how to change the top taskbar height in WM 6.5.x? Via the registry, programmatically (manipulating HWND) or even hacking ROM/Kitchen?
The initial height is 36px which is not enough for me. I don't care about icons, since they are replaced.
Wast I've done:
1. Searched the registry for '36' (decimal). No entries.
2. Tried the following code:
Code:
HWND h1 = ::FindWindow(NULL, _T("Desktop"));
::MoveWindow(h1, 0, 64, 480, 576, TRUE);
HWND h2 = ::FindWindow(_T("HHTaskBar"), NULL);
::MoveWindow(h2, 0, 0, 480, 64, TRUE);
There is a gap between the taskbar and the desktop not-painted.
Regards,

[TEST] Possible phantom touches fix

Right now i couldn't say for sure it's working or not, but for couple of days i didn't face any phantom touches. I wanna share the idea to test it.
There's things that's need to be done:
1. Open "/system/build.prop" with editor ( root )
2. Add those lines ( paste )
touch.size.calibration=geometric
touch.size.scale=100
touch.pressure.calibration=amplitude
touch.pressure.scale=0.1
3. Save & Reboot
If some one else is has that issue, test it.
It's not working for me...
Forget to mentioned that screen sensitive reduced in system to 10 maybe it's matter
Sent from my GT-I9103 using xda premium
hey i have a new display with a major problem of randoom phantom touches i will test ur solution until tomorow and report if it works
btw i cant say what display it is it was a friend of mine who has changed the display maybe "asi" can tell me wich one it is
but thx for ur research
EDIT:
as for now the "phatches" (phantom touches) are gone with ur first config will test the second from now on
EDIT 2:
ive tested the second config and must say it runs a bit smoother than the first one and for my display i can say when u look a bit from the side i can see small squares a few mm in size and dont forget to remind the people who want to test this mod that they should check the file permission if it is 644
EDIT 3:
now i can say the phatches are gone on my phone i got none since yesterday and the second conf is truely a bit smoother thx for that maybe that work on other phones too if they have probs with phatches on an new screen
Gesendet von meinem GT-I9103 mit Tapatalk 2
Please test that config too. And i know that it's hw related, it's wouldn't be fixed fully. Just make it's more comfortable.
touch.deviceType = touchScreen
touch.orientationAware = 1
touch.size.calibration = area
touch.size.scale = 43
touch.size.bias = 0
touch.size.isSummed = 0
touch.pressure.calibration = amplitude
touch.pressure.scale = 0.0125
touch.orientation.calibration = none
Sent from my GT-I9103 using xda premium
If u provide a flashable zip, it ll be easier n helpful
Sent from my GT-I9103 using Tapatalk 2
It is possible to fix my softkeys back and menu keys working automatically wihtout any touch ...from this coding???
Sent from my GT-I9103 using xda app-developers app
sacfire said:
It is possible to fix my softkeys back and menu keys working automatically wihtout any touch ...from this coding???
Sent from my GT-I9103 using xda app-developers app
Click to expand...
Click to collapse
You should try for yourself
Sent from my GT-I9103 using xda premium
These settings should be input device-specific and should go into one of the idc files in '/system/usr/idc/'. What files are in those folder? Could you send me the list? Is there any sec_touchscreen.idc? What is the output of 'getevent -p' in shell?
the list of system/usr/idc is:
qwerty.idc
qwerty2.idc
none more...
output of getevent -p
add device 1: /dev/input/event5
name: "compass_sensor"
events:
REL (0002): 0000 0001 0002 0003 0004 0005 0006 0007
0008 0009
input props:
<none>
add device 2: /dev/input/event3
name: "mpu-accel"
events:
REL (0002): 0000 0001 0002
input props:
<none>
add device 3: /dev/input/event2
name: "light_sensor"
events:
REL (0002): 0009
input props:
<none>
add device 4: /dev/input/event1
name: "proximity_sensor"
events:
ABS (0003): 0019 : value 1, min 0, max 1, fuzz 0, flat 0, resolution 0
input props:
<none>
add device 5: /dev/input/event4
name: "sec_key"
events:
KEY (0001): 0066 0072 0073 0074 00d4
input props:
<none>
add device 6: /dev/input/event0
name: "sec_touchscreen"
events:
KEY (0001): 008b 009e
ABS (0003): 002f : value 0, min 0, max 9, fuzz 0, flat 0, resolution 0
0030 : value 0, min 0, max 30, fuzz 0, flat 0, resolution 0
0035 : value 0, min 0, max 480, fuzz 0, flat 0, resolution 0
0036 : value 0, min 0, max 800, fuzz 0, flat 0, resolution 0
0039 : value 0, min 0, max 65535, fuzz 0, flat 0, resolution 0
003a : value 0, min 0, max 255, fuzz 0, flat 0, resolution 0
LED (0011): 0008
input props:
INPUT_PROP_DIRECT
Gesendet von meinem GT-I9103 mit Tapatalk 2
What is it ?
Sent from my GT-I9103 using xda app-developers app
---------- Post added at 05:15 PM ---------- Previous post was at 05:14 PM ----------
What is file permition ? How to do ?
Sent from my GT-I9103 using xda app-developers app
Any updates?
Sent from my GT-I9103 using Tapatalk 2

Changing display defaultMode on android 10

Hi All!
Did search a lot about my problem and didn't find anything, sorry if I'm duplicating anyway.
My dumpsys reports that the Xperia XZ2P display has two modes but it doesn't seem to switch in any case and I couldn't find how to force it.
{"Built-in Screen
displayId 0"
uniqueId "local:129"
app 1080 x 1920
real 1080 x 1920
largest app 1080 x 1920
smallest app 1080 x 1920
mode 2
defaultMode 2
modes
[{
id=1
width=2160
height=3840
fps=60.000004
}
{
id=2
width=1080
height=1920
fps=60.000004
}]
colorMode 0
supportedColorModes
[0
7
9]
hdrCapabilities [email protected]
rotation 0
density 420 (386.366 x 384.0) dpi
layerStack 0
appVsyncOff 5833333
presDeadline 14333333
type BUILT_IN
address {port=129}
state ON
FLAG_SECURE
FLAG_SUPPORTS_PROTECTED_BUFFERS
removeMode 0}
mw size 2160x3840 makes 3/4 of the screen a touch dead zone and is a no-no.
can someone tell me where the defaultMode setting is saved or how to change it runtime?
and yes adb shell doesn't even allow to tail /system/build.prop or remount.
Thanks in advance!

Categories

Resources