Related
Hello, whevever I try to put a wallpaper from my storage card via gallery or file explorer, Andriod forces me to crop the picture. It will only go crop to a max size of about 1/3 of the picture making the end result blurry. How can I turn this off or be able to select the wallpaper without cropping it? Sorry if this gets asked often but, i've been searching for a while now with no solution.... Thanks in advace!
PurpleSmurfLlama said:
Hello, whevever I try to put a wallpaper from my storage card via gallery or file explorer, Andriod forces me to crop the picture. It will only go crop to a max size of about 1/3 of the picture making the end result blurry. How can I turn this off or be able to select the wallpaper without cropping it? Sorry if this gets asked often but, i've been searching for a while now with no solution.... Thanks in advace!
Click to expand...
Click to collapse
Size them appropriately and use a png format before putting them on the phone.
All of them are in WVGA res. Most are also png.
PurpleSmurfLlama said:
All of them are in WVGA res. Most are also png.
Click to expand...
Click to collapse
Your home screen is WVGA resolution "per screenful". Given that you have 5 screens side by side, it actually needs a wallpaper that is wider than a single screen. Google it and you will find a lot of wallpapers for the N1 that are 960x800 so it looks like you need a wallpaper that is sized to be twice as wide as the portrait WVGA size...
I think I had a similar issue, and I couldn't find any mention of it.
It might be you are having the same problem.
That box you see when selecting a wallpaper is resizable. I had no idea at first, I only moved it around. It should be documented somewhere, but it isn't.
Press and drag near one of the borders of the box. Then you can expand it to the whole image.
If you already know of this, then just ignore me. But I was shocked to find out
Clarkster said:
I think I had a similar issue, and I couldn't find any mention of it.
It might be you are having the same problem.
That box you see when selecting a wallpaper is resizable. I had no idea at first, I only moved it around. It should be documented somewhere, but it isn't.
Press and drag near one of the borders of the box. Then you can expand it to the whole image.
If you already know of this, then just ignore me. But I was shocked to find out
Click to expand...
Click to collapse
lol, I could see how that would make a difference
Clarkster said:
I think I had a similar issue, and I couldn't find any mention of it.
It might be you are having the same problem.
That box you see when selecting a wallpaper is resizable. I had no idea at first, I only moved it around. It should be documented somewhere, but it isn't.
Press and drag near one of the borders of the box. Then you can expand it to the whole image.
If you already know of this, then just ignore me. But I was shocked to find out
Click to expand...
Click to collapse
Yes this is my issue, but.... the picture cropper will only go the entire width of the photo but not the entire height. Hence, 1/3 of the picture.I do understand it's resizeable.
PurpleSmurfLlama said:
Yes this is my issue, but.... the picture cropper will only go the entire width of the photo but not the entire height. Hence, 1/3 of the picture.I do understand it's resizeable.
Click to expand...
Click to collapse
That's to maintain the proper aspect ratio (800 high by 960 wide, I believe) to allow the background to scroll.
You might be able to find a third-party gallery app that would allow you to set a "portrait" sized wallpaper, but I don't believe that is a feature of the current Gallery.
Alright, well I do have some pictures that are 1200x1600 somewhere on my SD card. Just no where near as much as my other grahics. I have roughly 2,400 pictures total and about 2,350 of them are in WVGA res.... So this is a MAJOR inconvience.
PurpleSmurfLlama said:
Yes this is my issue, but.... the picture cropper will only go the entire width of the photo but not the entire height. Hence, 1/3 of the picture.I do understand it's resizeable.
Click to expand...
Click to collapse
Ok, I see. Then like mentioned before, your images are not the correct size. Since the Android scrolls the wallapper as you slide from screen to screen it needs to be much wider.
The Nexus is 480x800. But the wallpaper needs to be 960x800.
Yes, but you see.... I'm using LauncherPro, and it gives me the option to stop the wallpapers from moving sideways when scrolling screens. Therefore, I only need them in WVGA resolution. It's not like the picture is going to be strectched because it will always stay in place. If only this option was able to be turned off.....
Well..i need to learn something from the devs..!
i like to have my lcd density at 180-190 instead of original 240!
so the question is that if can someone make some fixes about this beacuse when you change the lcd density some games are not fitted well on screen also the dialpad too..and the keyboard become so small...!
its a little request if that can be fixed..or teach me how to make it work!
HD2 at lcd density 167 had original size keyboard,right oriented dialpad on screen..and all games was fitted well on screen!
thank you all guys!
P.S if the thread is not in the right place please moderators remove this elsewhere!!
(Example...try playing FAST AND FURIOUS 5 with 180 lcd density and see the screen size)
Hi, what you do mean by density? Do you mean resolution? Or the threshold when you press the screen???
Sent from my LG-P990 using XDA Premium App
xxdoggyxx said:
Hi, what you do mean by density? Do you mean resolution? Or the threshold when you press the screen???
Sent from my LG-P990 using XDA Premium App
Click to expand...
Click to collapse
hi there..i mean resolution!
you can change it on system/build.prop and change the line where it says lcd density:240 and set on 240 whatever you want and reboot device..!mine is 190!if you dont like it just change again the line to 240 which is the stock resolution...its simple!
Oh, haha.
Anyway, off-topic: where to download fast five for android?
Mine is on 161, the reason of 161 instead of 160 is the notification bar, with setting of 160 it will not go fullscreen, but 161 would.
About small keyboard button issue, I compile my own keyboard from 2.3 gingerbread source a 2.3 stock keyboard, with a larger define on the keys, works well now on my 2X.
About some games are not "resize" to take the different LCD density issue, try install Spare Parts from market, Un-tick "Run in compatibility mode", reboot it "should" help, this is needed on many older/not multiple resolution ready apps.
when changing the density to 161 or 180 the notification bar gets all corrupted, am i the only one having this? i'm on CM7 19
[EDIT] typo, was on 170, but is this normal?
svceon said:
when changing the density to 161 or 180 the notification bar gets all corrupted, am i the only one having this? i'm on CM7 19
[EDIT] typo, was on 170, but is this normal?
Click to expand...
Click to collapse
I am stock ROM 10a, no such problem (corrupted).
I am sure 160, 161, 180, 200, 220, 240 works, the catch on non 161 and 240(default) is the notification do not extent to full width, which is actually common and known issue of mdpi/sdpi/hdpi issues.
can u plz post an image to show how it corrupted?
to increase resolution on webtop
edit xorg.conf file (/osh/etc/X11/xorg.conf)
Code:
Section "Screen"
Identifier "Screen HDMI"
Device "Tegra HDMI"
Monitor "HDMI"
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
EndSection
change line Virtual to eg
Code:
Virtual 1920 1080
and from a terminal execute
Code:
xrandr -s 1920x1080
Does that resolution work with the dock?
Sent from my NINJATRIX
I tested it with multimedia dock and fullHD TV
error
something to the tune of "size not in available modes"
i'm using the hdmi hack, no dock
aaron.a said:
error
something to the tune of "size not in available modes"
i'm using the hdmi hack, no dock
Click to expand...
Click to collapse
Make sure you use a resolution your tv/monitor supports. Technically you should be able to set the res from the little monitor icon on the top of the screen.
For more flexibility you can comment the virtual mode out and write several resolutions in modes like : Modes "1920x1080 1680x1050 1280x800" and so on. Than use the xrandr command for different monitors/tvs
Lapdock?!?
How about the Lapdock? I have a strange problem in lapdock, where when I try to change the default display resolution (on the settings icon inside webtop) it does nothing at all, and my screen stops being full screen (i get black straps on the monitor edges).
Should I change this line to make my screen defaults to lapdock native display resolution of 1366x768?
Code:
# Uncomment to override the preferred resolution chosen by UseEDIDModes
Modes "1366X768"
ViewPort 0 0
And still alter the other line as well for when i plug my phone on my Full HD TV?
Code:
# Defaults to the size of the chosen mode
Virtual 1920 1080
Thanks in advance.
this requires the webtopmod? not able to run xrandr.
this is from a-trix.net site right?
Hi,
If I change the resolution to full HD and if I try the webtop on a HD Ready TV, will it work ?
Thank you.
Ronaldo_9 said:
this is from a-trix.net site right?
Click to expand...
Click to collapse
yes I first publish on that forum
-JFK- said:
Hi,
If I change the resolution to full HD and if I try the webtop on a HD Ready TV, will it work ?
Thank you.
Click to expand...
Click to collapse
You can obtain different configuration changing xorg.conf file
a desktop at fullHD resolution that scroll on HDready resolution
or a desktop at fullHD scaled on another resolution
for reference
http://www.x.org/releases/current/doc/man/man5/xorg.conf.5.xhtml
i got it going. an error on my part. i added an additional line for my resolution instead of adding it inside the quotes
thanks for sharing you're knowledge's =D
can you elaborate please, is this done inside webtop? cause i searched my /osh folder with root explorer and there's no etc folder in it
I get xrandr: not found.
Point me the right way please?
<edit> Would this be a path issue?
^^^^^^^^^^^^^^^^^^
Same
Sent from my MB860 using XDA App
CaelanT said:
I get xrandr: not found.
Point me the right way please?
<edit> Would this be a path issue?
Click to expand...
Click to collapse
The same to me!
And I am needing the webtop for videos.
But...
One thing that I realized, for pictures and musics the resolution its ok, but for videos not. Why?
xrandr appears to be in /usr/bin so that shouldn't be an issue.
Code:
# which xrandr
/usr/bin/xrandr
#
My issue is that when I run xrandr (and this is on a Photon, not an Atrix) is that it comes back with "No display".
John Kotches said:
My issue is that when I run xrandr (and this is on a Photon, not an Atrix) is that it comes back with "No display".
Click to expand...
Click to collapse
Solved this, also set up the adas user to pull up @ 1920x1080 automatically on login by updating .profile.
Regards,
Sorry for my english..
when I switch from an app with black screen (notification bar xda app etc etc) to a bright one.. Like whatsapp I see a strange thing... There is less contrast for 0.5sec then contrast is perfect and all is normal...
I don't know if you understand what I mean...
Is this normal? Or is a fault display?
Happens with stock and cyano... Full brightness and at lowest brightness...
thx for the replay
drigerott said:
Sorry for my english..
when I switch from an app with black screen (notification bar xda app etc etc) to a bright one.. Like whatsapp I see a strange thing... There is less contrast for 0.5sec then contrast is perfect and all is normal...
I don't know if you understand what I mean...
Is this normal? Or is a fault display?
Happens with stock and cyano... Full brightness and at lowest brightness...
thx for the replay
Click to expand...
Click to collapse
Thermal throttling is normally given as the answer to this.
Thanks for the fast replay... Then I must change my device? Or it'snormal
drigerott said:
Thanks for the fast replay... Then I must change my device? Or it'snormal
Click to expand...
Click to collapse
Its normal, but there are ways to change the way it does it, I am not an expert but if you root you can start to cange values. Search for thermal throttling values and you will hit a good thread about.
Yes I have root.. But I didn't understand.. For thermal throttle you mean cpu? Or even the display?
cause I don't have problem with multitask or other.. Only this strange problem that image quality is not perfect when switching to dark image to bright one.. But for less then a second.. But is frustrating and strange
drigerott said:
Yes I have root.. But I didn't understand.. For thermal throttle you mean cpu? Or even the display?
cause I don't have problem with multitask or other.. Only this strange problem that image quality is not perfect when switching to dark image to bright one.. But for less then a second.. But is frustrating and strange
Click to expand...
Click to collapse
as i said i am not an expert, but if you search in this forum you will find other threads that will give you information on which files to modify and how to do it...
gregbradley said:
as i said i am not an expert, but if you search in this forum you will find other threads that will give you information on which files to modify and how to do it...
Click to expand...
Click to collapse
ok i found some 3d about termal throttle and is not my problem.. i tried different mod but nothig...
i uploaded a video to show my problem ...
see the contrast change?
is not brightness...it's contrast that changes...
Yes, a have this effect too. I`ve changed brightness values at system/etc/sysmon.cfg, to a maximum values, after that screen doesn`t changing brightness when device is more hot, but this effect like in this video, is still exists! This contrast shading are not a termal throttling, this is something else, i don`t know exactly what it is.
i'm not alone then...
with cyanogenmod is so more evident...
tomorrow i'll turn on another one in my shop and see if is all xperia t like this...
anyway if some other has this strange problem, plz post here ^^ (maybe is a software fault)
Maybe a refresh issue?
when i scroll a page on black background with white txt.. the txt becomes greysh... if you scroll slowly remains white... happens to you too?
drigerott said:
Maybe a refresh issue?
when i scroll a page on black background with white txt.. the txt becomes greysh... if you scroll slowly remains white... happens to you too?
Click to expand...
Click to collapse
I don`t think it`s a refresh rate, but maybe i`n wrong.
And, yes, i have the same issues, and the screen is shading and becomes bright again all the time. Especially this happening when i try to open something or to enter at one of the bookmarks of phone menu, and when the phone "thinking", screen is shading, but then it becomes brighter again. I`m reaaly don`t know what it ies, but it`s not because of a thermal, 100%! I already changed the values of a brightness. I`m sure that all Xperia T phones are with the same issues, it`s bacause of a something in soft.
It has nothing to do with gpu.
Here is data sheet for AS3676 - www1.futureelectronics.com/doc/AUSTRIAMICROSYSTEMS/AS3676.pdf
And here is what DLS is from the data sheet -
8.4.9 DLS - Dynamic Luminance Scaling Input
The pin GPIO1/DLS can be used for dynamic backlight scaling input. Dynamic backlight scaling is used to reduce the power of the backlight especially when showing dark picture contents on the display. The control unit to operate DLS is the display processor sending a PWM signal to the AS3676 and in parallel changing the display content to compen- sate for a reduced brightness backlight.
DLS can be turned off in /system/etc/pre_hw_config.sh -
echo 0 > /sys/class/leds/led_1-lcd/use_dls
echo 0 > /sys/class/leds/led_2-lcd/use_dls
Is it save to turn DLS off ?
Sent from my LT30p using xda app-developers app
peetr_ said:
It has nothing to do with gpu.
Here is data sheet for AS3676 - www1.futureelectronics.com/doc/AUSTRIAMICROSYSTEMS/AS3676.pdf
And here is what DLS is from the data sheet -
8.4.9 DLS - Dynamic Luminance Scaling Input
The pin GPIO1/DLS can be used for dynamic backlight scaling input. Dynamic backlight scaling is used to reduce the power of the backlight especially when showing dark picture contents on the display. The control unit to operate DLS is the display processor sending a PWM signal to the AS3676 and in parallel changing the display content to compen- sate for a reduced brightness backlight.
DLS can be turned off in /system/etc/pre_hw_config.sh -
echo 0 > /sys/class/leds/led_1-lcd/use_dls
echo 0 > /sys/class/leds/led_2-lcd/use_dls
Click to expand...
Click to collapse
great find.. any way yesterday i turned on 5 new xperia t in my shop and all do like mine... that is DSL like peetr say..
but the annoying thing is that on cm10 (that all the ui is gray/dark) DSL is too much visible...) now i'll try to disable it.. i'll report if works
EDIT: still the same..
I don't get how to turn DLS off, what value should i change to turn it off ?
Sent from my LT30p using xda app-developers app
you must edit the file in /system/etc/pre_hw_config.sh
with root explorer or similar and change thise line: (0 instead of 1)
echo 0 > /sys/class/leds/led_1-lcd/use_dls
echo 0 > /sys/class/leds/led_2-lcd/use_dls
0 instead of 1 , and what should i set instead of 2 ? 0 too ?
And, is this save ???
Sent from my LT30p using xda app-developers app
Finally, this will have effect or no?
Because maybe we all have this issue.
Sent from my LT30p using xda premium
all xperia t works like i posted in the video (infact i tried 5 new xperia t all the same)
but that mod is not working.. for me is still the same..
DennisDD78 said:
0 instead of 1 , and what should i set instead of 2 ? 0 too ?
And, is this save ???
Sent from my LT30p using xda app-developers app
Click to expand...
Click to collapse
this is stock
echo 1 > /sys/class/leds/led_1-lcd/use_dls
echo 1 > /sys/class/leds/led_2-lcd/use_dls
change in to this:
echo 0 > /sys/class/leds/led_1-lcd/use_dls
echo 0 > /sys/class/leds/led_2-lcd/use_dls
but i see no difference..
Attached below is a zip containing two folders AFG and BFG each contains a modded libmmcamera_imx179.so each modified to increase maximum exposure time to 64secs test each see which one increases max expo time
Some instructions and results would be awesome.
Kindly explain the mod in detail and how to use it.
Tagtag123 said:
Some instructions and results would be awesome.
Kindly explain the mod in detail and how to use it.
Click to expand...
Click to collapse
Copy the lib to /system/vendor/lib/ set rw-r-r permission
Open some camera 2 app check if max exposure time is now 64sec
As I said there are two libs see which one works I do not have a nexus 5 so I did not test it
None work.
I copied and set the permissions rw-r-r
Tried L camera and camera fv5, max exposure is still 0.8s.
Would be super cool, if you could make it work.
Hmmm need to find the line count value.
The Maximum Exposure Times is Calculated (Frame Length * 1000000000 / pixel Clock) * Maximum Line Count .
The Maximum Line Count value is what they limit when searching for this value its supposed to be after the maximum analog iso value . I tested this on the nexus 6p LG G4 and one plus 2.
So in Nexus 5 Case it's 3440 x 1000000000 / 260000000 resulting in 13230.76923076923 this number is rounded up to 13231 giving the minimum exposure time
Given we know the Max Exposure time is 866975130 we div it with 13231 it gives us 65526.04716196811 so round down the value to just 65526 so the value range we looking for is between 65525 and 65535 its a 32 bit int hex value .
The two libs I had modified where values just after max analog gain and before . Attached 200mhz zip with pixel clock clocked down from 260 MHz to 200mhz to make sure there are no decimals to see what value.
You can run dumpsys media.camera > /sdcard/dump.text after typing su command in terminal to see if max exposure changed as well as min
defcomg said:
Copy the lib to /system/vendor/lib/ set rw-r-r permission
Open some camera 2 app check if max exposure time is now 64sec
As I said there are two libs see which one works I do not have a nexus 5 so I did not test it
Click to expand...
Click to collapse
defcomg said:
Hmmm need to find the line count value.
The Maximum Exposure Times is Calculated (Frame Length * 1000000000 / pixel Clock) * Maximum Line Count .
The Maximum Line Count value is what they limit when searching for this value its supposed to be after the maximum analog iso value . I tested this on the nexus 6p LG G4 and one plus 2.
So in Nexus 5 Case it's 3440 x 1000000000 / 260000000 resulting in 13230.76923076923 this number is rounded up to 13231 giving the minimum exposure time
Given we know the Max Exposure time is 866975130 we div it with 13231 it gives us 65526.04716196811 so round down the value to just 65526 so the value range we looking for is between 65525 and 65535 its a 32 bit int hex value .
The two libs I had modified where values just after max analog gain and before . Attached 200mhz zip with pixel clock clocked down from 260 MHz to 200mhz to make sure there are no decimals to see what value.
You can run dumpsys media.camera > /sdcard/dump.text after typing su command in terminal to see if max exposure changed as well as min
Click to expand...
Click to collapse
None of the camera apps work with the 200mhz lib.
Tagtag123 said:
None of the camera apps work with the 200mhz lib.
Click to expand...
Click to collapse
Try this one
defcomg said:
Try this one
Click to expand...
Click to collapse
Doesn't work, I get a green line on the bottom of the viewfinder. The viewfinder preview moves from left to right in the form of two images. Images clicked are bands of what seems to be corrupted data.
The exposure is still 0.8s in l camera and camera fv5
Tagtag123 said:
Doesn't work, I get a green line on the bottom of the viewfinder. The viewfinder preview moves from left to right in the form of two images. Images clicked are bands of what seems to be corrupted data.
The exposure is still 0.8s in l camera and camera fv5
Click to expand...
Click to collapse
Screenshot also make a dumpsys it could be that the 0.8s is hardcoded in the apps
defcomg said:
Screenshot also make a dumpsys it could be that the 0.8s is hardcoded in the apps
Click to expand...
Click to collapse
Clicked Pic:
https://goo.gl/photos/Zxuio384yRr2sV5HA
Screen record:
https://www.youtube.com/watch?v=zGfkE85WU2A
Lcamera source:
https://github.com/PkmX/lcamera
Dumpsys:
https://gist.github.com/utkarshns/9bab3dbed3c6b461f641d4a6f900c5af
Open to any testing, or even a live hangouts testing session.
Waiting for good news,. i think 4sec is good enough,...
There are two res arrays in the preview res I set the clock to 50mhz and the other folder two both res if max expo is still 0.8 its hardcoded in libmmcamera_sensor_modules.so I will need that lib
defcomg said:
There are two res arrays in the preview res I set the clock to 50mhz and the other folder two both res if max expo is still 0.8 its hardcoded in libmmcamera_sensor_modules.so I will need that lib
Click to expand...
Click to collapse
Trying both libs, will revert asap.
utkarshnarain at gmail dot com, for live testing
PFA: stock libs
Tried both . so files and got moving bands in viewfinder and a completely banded image on clicking the picture.
Tagtag123 said:
Tried both . so files and got moving bands in viewfinder and a completely banded image on clicking the picture.
Click to expand...
Click to collapse
And still capped to 0.8s? On both
defcomg said:
And still capped to 0.8s? On both
Click to expand...
Click to collapse
Yes, both Lcamera and Camera FV5 say the same thing.
Tagtag123 said:
Yes, both Lcamera and Camera FV5 say the same thing.
Click to expand...
Click to collapse
Check dumpsys if its 866975130 also I said copy to /system/vendor/lib make sure there isn't another libmmcamera_imx179.so in system/lib/
defcomg said:
Try this one
Click to expand...
Click to collapse
defcomg said:
Check dumpsys if its 866975130 also I said copy to /system/vendor/lib make sure there isn't another libmmcamera_imx179.so in system/lib/
Click to expand...
Click to collapse
Libs found in system.
Dumpsys coming
defcomg said:
Check dumpsys if its 866975130 also I said copy to /system/vendor/lib make sure there isn't another libmmcamera_imx179.so in system/lib/
Click to expand...
Click to collapse
dumpsys: bothres
https://gist.github.com/utkarshns/8060a25c3b545b6ea88dce442c30a721