Resolution to 1080 or 1224? - G3 Q&A, Help & Troubleshooting

I tried changing resolution to
1224 x 2176 520 dpi
1080 1920 480dpi
But I want two apps to work
LG Keyboard ( I really like it. Its better than all others)
LG Launcher (good but I can live without it)
I can make the other apps work fine but above two. Has any one successful in running any of the above apps on 1080 ?
I am on lollipop btw

I was finally able to change resolution to 1224 with LG Home, Swiftkey and LG keyboard and all apps working perfectly fine.
Here's what I did.
Changed resolution to 1224 x 2176 DPI 540 using Nomone resolution changer.
Then I used Rom Toolbox Lite to edit build.prop and changed LCD density to 540 as well.
Reboot.
Everything is working great.
Why I changed to 1224 x 2176.
LG G3 original resolution
1440 x 2560 = 3686400 pixels.
and
1224 x 2176 = 2663424 pixel (72% of 1440 x 2560) Huge performance boost.
You can also try
1920 x 1080 = 2073600 (56% of 1440 x 2560) Even better performance boost.
I couldnt find the right DPI settings for 1080. LG Home, Keyboard doesnt work fine. Other apps can work fine by appsettings(xposed module) though.

Related

Camera resolution fixed to 640 x 480

is it just me? i did search for the forum, but no one mention about it
when i use facebook for android ( 1.2 as i updated to newest version)
news feed---- camera button---- camera mode, the resolution size limited to 640 x 480 or 640 x 384 in widescren mode
it is not just happen in facebook , twitter, peep, they are the same...
is there any chance that release the limit?
640x480 is the limit for those sites.
If you want to have a bigger picture to keep on your phone then you could make the picture with the camera at high resolution and upload to those sites afterwards.

[Q] Turning off widescreen mode on the G2

considering every other camera phone you can change to aspect ratio (4:3) ie 640x 480 instead of 640x960 it is for work in reo propertys where every thing has to be documented and sent some where.
need to be able to for my work
and other phones can see below just not a tmobile version ?
http://sites.pruvan.com/certified-hardware/smartphones

Settings for BEST possible video recording quality?

Only had my Desire HD about 3 weeks, rooted last week, installed Lg Camera Pro.....but as I know absolutely ZERO when it comes to any kind of camera/camcorder stuff...what is the best setting for best possible video quality?
Options under video resolution are:
640 x 480
704 x 576
720 x 480
800 x 480
960 x 720
1280 x 720
Then I have video encoder options:
Default
H.263
H.264
MPEG4
Then: Video file Format
MPEG4
3GP
File size at the end of the recording is not an issue, as I have a big SD card and don't record to much video, but when I do record I want it to be the very very best possible.
Any help - very very much appreciated.
cheers
Matt
Hi matt
For me, the best possible video output is 800x480 with MPEG4 as format. Stable 50fps under bright place and still manage to maintain 20+ fps in low light. Recording in full HD is nice, but limited to 30fps at most and low audio bitrate. Also, try to adjust the sharpness to -1 or -2. It will improve the fps. There's also a thread for DHD camera guide I guess. For better compression, I choose the H.264 format.

[HACK] Reduce HDMI output resolution

I am looking for a hack that lowers my Samsung Ativ 500T HDMI output resolution.
I have a Picop LASER micro-projector by Microvision which is capable of displaying input sources having the following resolution:
WVGA 848 × 480 (native)
WVGA2 800 × 400
VGA 640 × 480
My Windows 8 device is capable of outputing:
1280 × 720
1786 × 1005
1920 × 1080
Connecting it to my PC (Ubuntu 13.10) I can make it work at both:
848 × 480 (16:9)
800 × 480 (16:10)
Now, this device has a VGA input, my PC has a VGA output and the Windows 8 device has a HDMI output which I convert to VGA with a few $ adaptor. I was wondering now if anyone here would know whether it would be possible to hack the HDMI output resolution of the tablet in order to get the micro-projector work and do not complain about a "Video not Supported"...

zenfone 2 dpi display issues

Hi guys, I have the zenfone 2 ww version (ZE550ML) rooted.
Short version: received the system update notification and tried running it OTA but that failed, most likely due to root. So I decided to download the entire firmware build and manually flash. That seemed to go okay but it immediately caused some weird display driver issue. After doing google and threads on xda it seems like my DPI settings got screwed up. So by default my resolution or dpi results in very very small icons and text on screen.
I tried using the adb shell wm density command and editing build.prop (rebooting) to fix this but based on the output below the system isn't truly accepting the changes. This discrepancy is leading to some applications rendering badly. E.g) changing my display picture in whatsapp results in the app zooming the image to a humungous size and I can only crop a small section of the picture.
Output from adb shell wm density shows that no matter what I change the dpi to the phone registers the actual dpi as 320 instead of the normal 480. I did the command on a friend who has the exact same phone to get the different outputs. Does anyone know how to get the native dpi to register at 480 (3.0)?
I've tried re-flashing the firmware and using older versions..same issue.
Key differences evident:
Working zenfone 2
Display Devices: size=1
DisplayDeviceInfo{"Built-in Screen": 1080 x 1920, 60.000004 fps, supportedRefreshRates [60.000004], density 480, 403.0 x 403.0 dpi, appVsyncOff 7500000, presDeadline 12666666, touch INTERNAL, rotation 0, type BUILT_IN, state OFF, FLAG_DEFAULT_DISPLAY, FLAG_ROTATES_WITH_CONTENT, FLAG_SECURE, FLAG_SUPPORTS_PROTECTED_BUFFERS}
mAdapter=LocalDisplayAdapter
mPhys=PhysicalDisplayInfo{1080 x 1920, 60.000004 fps, density 3.0, 403.0 x 403.0 dpi, secure true, appVsyncOffset 7500000, bufferDeadline 12666666}
my zenfone 2
Display Devices: size=1
DisplayDeviceInfo{"Built-in Screen": 1080 x 1920, 60.000004 fps, supportedRefreshRates [60.000004], density 320, 403.0 x 403.0 dpi, appVsyncOff 7500000, presDeadline 12666666, touch INTERNAL, rotation 0, type BUILT_IN, state OFF, FLAG_DEFAULT_DISPLAY, FLAG_ROTATES_WITH_CONTENT, FLAG_SECURE, FLAG_SUPPORTS_PROTECTED_BUFFERS}
mAdapter=LocalDisplayAdapter
mPhys=PhysicalDisplayInfo{1080 x 1920, 60.000004 fps, density 2.0, 403.0 x 403.0 dpi, secure true, appVsyncOffset 7500000, bufferDeadline 12666666}
So it's clear his dpi settings are at 480 (density 3.0) and mine are locked to 320 (density 2.0) and this result is the same no matter what I change my display density to via build.prop or shell wm density.
Hi!
How are you getting those details?
BTW, based on your data, your friend has a density of 480 which i think belongs to ZE551 and not on ZE550. Correct me if I'm wrong.
And as you stated in "My Zenfone"
You are getting 1920x1080 resolution. So, i think you flashed wrong firmware.
551ML firmware on 550ML??
xgneilx said:
Hi!
How are you getting those details?
BTW, based on your data, your friend has a density of 480 which i think belongs to ZE551 and not on ZE550. Correct me if I'm wrong.
Click to expand...
Click to collapse
You are correct, after confirming the models etc.. it was a firmware mis-match on my part that started the entire mess. Realised that when my accelerometer was not working either.
adb shell dumpsys display
[email protected] said:
And as you stated in "My Zenfone"
You are getting 1920x1080 resolution. So, i think you flashed wrong firmware.
551ML firmware on 550ML??
Click to expand...
Click to collapse
Yes I did. I believe my errors started when I did the incorrect firmware build after the failed OTA. So that first build possibly changed my fastboot, boot, recovery images and I was under the wrong impression my model was the 550ML. It didn't help that the Regulatory Info in Settings|About reflected the model as the Z008D.
So once I restored the correct fastboot, boot and recovery images for the Z00AD and factory reset I was able to re-flash the correct firmware.
Everything works fine now. Thanks very much for chiming in.:good:

Categories

Resources