Database Info

how to change resulotion on tf700?

hi
I want to change the resolution to 1280*800 in order to play asphalt 8. ( I don't understand it 1.8 quad processor is not enough)?
I have zombie rom and over clock it to 1.8
thank u!!!!:good:

bennnnnn said:
hi
I want to change the resolution to 1280*800 in order to play asphalt 8. ( I don't understand it 1.8 quad processor is not enough)?
I have zombie rom and over clock it to 1.8
thank u!!!!:good:
Click to expand...
Click to collapse
Choose that resolution in the installer?
or open a terminal emulator session and type the following:
Code:
su
wm density 160
wm size 1280x800
to reset
Code:
su
wm density reset
wm size reset

re
sbdags said:
Choose that resolution in the installer?
or open a terminal emulator session and type the following:
Code:
su
wm density 160
wm size 1280x800
to reset
Code:
su
wm density reset
wm size reset
Click to expand...
Click to collapse
I did it - the fonts do change to small ones, but it written bad size when I entered wm size 1280x800

bennnnnn said:
I did it - the fonts do change to small ones, but it written bad size when I entered wm size 1280x800
Click to expand...
Click to collapse
Did you type it correctly?
Works fine here....

[GUIDE] [ANDROID WEAR] [ADB] Changing DPI on the Gear 2

This won't work if your Gear 2 is still running Tizen, sorry.
The original DPI on Biktor's Android wear for Gear2 is 280. I found that changing it a little improves everything a lot.
Here is how you do it :
1) Enable USB debugging on your watch and connect it to you PC.
2) Start ADB
3) If for whatever reason, you want to know what your current DPI is, type this : adb shell wm density
4) To change DPI, type this : adb shell wm density 200 (yeah, I suggest 200 for Gear2, but the choice is yours)
The screenshot on the left is with DPI 200, the one on the right with original 280 DPI.
Enjoy

The perfect dip is 240 .
Tried and no blurry icon , max graphics interface

Gabri™ said:
The perfect dip is 240 .
Tried and no blurry icon , max graphics interface
Click to expand...
Click to collapse
Thanks, I will try it

Works great on Ticwatch e as well. Thanks!

[RK3188] Android 4.4.2 resolution in custom builded ROM

Hi guys,
I need your expertise on a problem I'm facing : I have a custom Android developpement board with the Rockchip RK3188 microprocessor, based on the Radxa Rock Pro. I have the full source of the kernel and of Android 4.4.2 that is working with my device.
I'm using a 1024x600 LVDS screen and I'm trying to get that exact resolution from Android.
If I check my framebuffer configuration with:
Code:
cat /sys/devices/platform/rk-fb/graphics/fb0/disp_info
I have my 1024x600 exact resolution:
Code:
win0:disabled
xvir:320
xact:320
yact:240
xdsp:320
ydsp:240
x_st:10
y_st:10
x_scale:1.0
y_scale:1.0
format:ARGB888
YRGB buffer addr:0x00000000
CBR buffer addr:0x00000000
win1:enabled
xvir:1024
xdsp:1024
ydsp:600
x_st:200
y_st:20
format:ARGB888
YRGB buffer addr:0x98258000
overlay:win1 on the top of win0
That is also my only fb mode:
Code:
# cat /sys/devices/platform/rk-fb/graphics/fb0/
U:1024x600p-0
BUT, Android is outputing at 1280x720. If I go to a website like http://www.webpagefx.com/tools/whats-my-browser-size/, I see that I'm in 1280x720.
Also, if I try to change my resolution using an app (like NOMone Resolution Changer) or a "wm size" command in adb, the result is that it's using 1024x600 IN the actual 1280x720 which result in a smaller WM than the screen (I have black bars at the bottom and at the right). Changing the overscan thing change nothing.
I tried to search the whole RK3188 kernel for 720p and switched every 1280x720 to 1024x600 in the code: no change
I tried to search in the Android source for any settings but didn't find anything usefull yet. All my search on XDA, Google and everythings doesn't answer my question. I know that, for certain devices using U-Boot, I can edit the script.bin/fex file, but I don't have that kind of file and the RK3188 is not using U-Boot.
If any of you have any idea, it would be great!
Thanks
Jonathan

[Info] RM3&3S Display accepts renders up to 5k

As the title says, you can use the adb wm size command to change the resolution, higher.
On most phones the resolution shipped is the highest available.
The RM3&3S ship stock 1080p but easily go up much higher.
Personally i recommend 1440x3120
wm size 1440x3120
In an su terminal or adb by pc.
This brings the display up to current phones resolution! (2k)
Enjoy!
As for performance and battery life, there is no noticeable NEGATIVE impact. However, when screen recording or streaming your screen, it can lag if your connection cant support the higher resolution. Native screen recording should be unaffected.

SilentDevGuy said:
As the title says, you can use the adb wm size command to change the resolution, higher.
On most phones the resolution shipped is the highest available.
The RM3&3S ship stock 1080p but easily go up much higher.
Personally i recommend 1440x3120
wm size 1440x3120
In an su terminal or adb by pc.
This brings the display up to current phones resolution! (2k)
Enjoy!
As for performance and battery life, there is no noticeable NEGATIVE impact. However, when screen recording or streaming your screen, it can lag if your connection cant support the higher resolution. Native screen recording should be unaffected.
Click to expand...
Click to collapse
wow nice
anyone has tested this ?
I have downloaded the DevCheck app and under HARDWARE tab > Graphics > Resolution, it is shown as 2340 x 1080. Does it mean that on adb I have to type wm size 3120x1440 instead ?
Thank you

SilentDevGuy said:
As the title says, you can use the adb wm size command to change the resolution, higher.
On most phones the resolution shipped is the highest available.
The RM3&3S ship stock 1080p but easily go up much higher.
Personally i recommend 1440x3120
wm size 1440x3120
In an su terminal or adb by pc.
This brings the display up to current phones resolution! (2k)
Enjoy!
As for performance and battery life, there is no noticeable NEGATIVE impact. However, when screen recording or streaming your screen, it can lag if your connection cant support the higher resolution. Native screen recording should be unaffected.
Click to expand...
Click to collapse
I have tried changing the resolution yes the screen changed to a smaller icon etc but the problem is the below area is not responding to touch for example, the soft button; back, home and app manager does not work when touched.

On mine
lius90 said:
I have tried changing the resolution yes the screen changed to a smaller icon etc but the problem is the below area is not responding to touch for example, the soft button; back, home and app manager does not work when touched.
Click to expand...
Click to collapse
On mine it works without issue at all and I can touch all the way up to 5k no problem, can you tell me your device model and rom?
Not to be rude or offend you but it is 100% user error on your side, the resolutions are accepted, and tested on A11 and A10 multiple devices. Also the icons smaller and all that is just based on DPI, resolution is the resolving power.

lius90 said:
wow nice
anyone has tested this ?
I have downloaded the DevCheck app and under HARDWARE tab > Graphics > Resolution, it is shown as 2340 x 1080. Does it mean that on adb I have to type wm size 3120x1440 instead ?
Thank you
Click to expand...
Click to collapse
No, use 1440x3120 it matters what order the numbers are in.

Thankyou

Thank you. For the display to work properly, you also need to change the pixel density. We enter three commands in adb:
wm size 1440x3120
wm density 640
reboot
Increased clarity even in games! See screenshots...
Source: https://lumpics.ru/how-change-screen-resolution-on-android/#helpgood
Disable nubia red magic 3 animated boot splash screen on phone boot and reboot, save your zip, download my zip and replace via total commander
bootanimation.zip
shutdownanimation.zip
File path:
system/media/theme/bootup
system/media/theme/shutdown
Here is a program Easy DPI Changer root for those who have root rights:
Easy DPI Changer [Root] - Apps on Google Play
Make your screen yours
play.google.com
In the "Density" field, enter the DPI, and in the "Resolution" field, enter the width and length. After changing each parameter, click "Apply" in its block to save the new values. They will apply after a reboot.
I played around with this screen resolution and returned to standard resolution!

Change Resolution in Android VM

Hello,
We're working on Android S in a virtualized environment (Running via QEMU emulator).
How do we change the resolution from the source code ? .
Also, how does
wm size AxB (where A and B are resolution numbers) work in the background from the adb shell ?
Click to expand...
Click to collapse
Which place in the source code do we look for to change the resolution ?
The host is an Ubuntu Setup, and we're using QEMU 6.
Attached screenshot is how we run the Android VM.

You change Android's screen resolution and/or density by editing it's "build.prop" file.
Example:
Code:
adb shell wm size 1080x1920
and then
Code:
adb shell wm density 390
BTW:
Resolution is defined as the following on Google's developer portal:
The total number of physical pixels on a screen. When adding support for multiple screens, applications do not work directly with resolution; applications should be concerned only with screen size and density, as specified by the generalized size and density groups.
And screen density:
The quantity of pixels within a physical area of the screen; usually referred to as dpi (dots per inch). For example, a "low" density screen has fewer pixels within a given physical area, compared to a "normal" or "high" density screen. For simplicity, Android groups all actual screen densities into six generalized densities: low, medium, high, extra-high, extra-extra-high, and extra-extra-extra-high.

xXx yYy said:
"build.prop"
Click to expand...
Click to collapse
what's the build.prop value ?

xXx yYy said:
You change Android's screen resolution and/or density by editing it's "build.prop" file.
Example:
Code:
adb shell wm size 1080x1920
and then
Code:
adb shell wm density 390
BTW:
Resolution is defined as the following on Google's developer portal:
The total number of physical pixels on a screen. When adding support for multiple screens, applications do not work directly with resolution; applications should be concerned only with screen size and density, as specified by the generalized size and density groups.
And screen density:
The quantity of pixels within a physical area of the screen; usually referred to as dpi (dots per inch). For example, a "low" density screen has fewer pixels within a given physical area, compared to a "normal" or "high" density screen. For simplicity, Android groups all actual screen densities into six generalized densities: low, medium, high, extra-high, extra-extra-high, and extra-extra-extra-high.
Click to expand...
Click to collapse
I can change the resolution, while running the image.
with
adb shell > wm size 1920x1080 or something like that.
but, what i want to achieve is, writing a C/C++ code, which can help me change the resolution to whatever i feel like within the minResolution and maxResolution limits of the screen.
something like,
./screen_reso 1920 1080 (passing 1920 1080 as command line arguments or even inside the code)