Do you guys do it by eye from the default android interface (94%-42% pictured below), or is there some other method/app you use?
If by eye, what would you say the screen on time was on my attached screenshot?
At the screen before that one (with the small graph at top, and listing of apps and usage percentages on the rest of the screen), click on the Display line, and it'll show the "Time on".
Hellò,
I would like to know why some contact pictures are showed in full screen while other, with same size and resolution are displayed very small.
I have assigned 3 picture with same size and resolution to 3 of my contacts but only one of them, when called (or when he calls me) the display shows the picture in full screen mode.
Does this happen to you also?
I don't want to use any application for full screen caller, I don't like it..
thanks for help
fausto
I bought two separate Droid Bionic phones new via a vendor on, and fulfilled by, Amazon and it had some display problems. I noticed it in the stock rom, recovery and cyanogenmod. The second had the same problems in the stock room. Both have been returned. Verizon checked that the first phone was clean. I did not bother checking the second. (I had both phones at the same time, so they couldn't have sent me the same phone twice.)
There were two issues. First, there was a faint large rounded rectangle of a slight dimness that was very visible with certain content (some black screens like settings) and hard to see, but definitely still there, with other content (netflix, when sliding the home screen and its background). It did not change between landscape and portrait. This was about half the width (short-side) and three quarters of the height (long side).
The second issue was that in some screens, you could see lines of pixels of slightly varying color. For example, a black screen would have lines of slight color in bands. This was most noticeable in the settings and would rotate with the screen to remain on the bottom of the screen.
Should I try a third from another seller? Or is this a matter of you-get-what-you-pay-for and I should go look for something else?
BUYER BEWARE: I don't know how Samsung handles burn-in. I created an overlay for WatchMaker that effectively turns off every pixel for a minute or two each hour (similar to what pixel shift does).
------------------------------------------------
I lucked into exploiting a bug/glitch that somehow tricks or circumvents the 15% OPR limitation in dim mode. What I end-up with is considerably brighter, and much more useable/readable.
Using WatchMaker and Tasker, create a task to run every 5 minutes throughout the day. Every 5 minutes (or 10 or whatever you choose, just needs to be higher than watch's screen off time), re-send the currently selected WatchMaker face to your Watch. It might take a cycle or two to sync, but you'll end-up with the default WatchMaker brightness (which doesn't appear to be adjustable) in dim mode.
My blue/orange/red watchfaces (some with @ 45% OPR) are now readable in dim mode. Uses maybe 1-1.5% extra battery per hour (I have brightness set to 4 out of 10). App "I'm Alive" works great to keep your watch always on (and active), but is a huge battery drain in the 8-10% per hour range in my tests. The Tasker trick above actually allows your watch to go into inactive/dim mode.
NOT A GUARANTEE AGAINST BURN-IN!!!
Here are the overlays I use in WatchMaker. It would be the top/last two layers in your design. The first I set the X coordinate to {dm}, which shifts the image 1 pixel right each minute. The second I set the Y coordinate to {dm}, which shifts the image 1 pixel down each minute.
I really can't see these pixels, although they may show on large white parts of your watch.
The images are a 630x630 square at 364 DPI (for the 1.4" 45mm Galaxy Watch 3). Each row has 1 pure black pixel every 60 pixels, and I alternated so to maximize the space between pixels to not be noticeable. The second image is rotated 180 degrees so you can use both in order to "turn-off" each pixel for 2 minutes each hour.
One more layer of protection would be to lengthen your minute hand all the way to the edge and it will then, presumably, change the color of every pixel for a few minutes each hour as it rotates around.
The images are below (they're just mostly transparent!). Hover around with the cursor to find GWBurnIn1.png and GWBurnIn2.png
More tips:
Rotate watch faces at least every 12 hours to reduce chance of burn-in (GW3 WatchMaker max is 3 hours, FYI, but you need to control this from Tasker, anyway, to select different watches at different times on different days)
Alternate between light/colored faces and dark/black faces. Even better, use paint.net (free download for PC) to create the inverted color version of the watch face. But in most cases the inverted face will probably be ugly as sin.
A couple battery drain tips: Don't use WatchMaker default rotation commands for the minute-hand, use {dm}*6. In dim mode, the hand only moves every minute, anyway, but the default rotation is adjusted for seconds which could cause it to constantly engage cpu to calculate. Similarly, you might not want to use the continuous second-hand {drss} rotation.
Note: The second-hand does not disappear in dim mode even if set to bright only. Use the below code for the Opacity of the second-hand. This makes the second hand invisible after the watch has been active for 15 seconds. It will come back, for 15 seconds (or whatever you choose) when you interact with your watch again.
{c_elapsed} >=15 and 0 or 100
How do you write the Tasker task to change the watch face in watchmaker? Thanks for help
Would like to know this as well...
mib1800 said:
How do you write the Tasker task to change the watch face in watchmaker? Thanks for help
Click to expand...
Click to collapse
There are two steps. First, a "sub-task" to set a Tasker variable. In the below scenario, I'm rotating 25 watchfaces for the week. It's iterating the variable +1 every 8 hours, until 25 then back to 0.
with trigger/event set from 12AM every 8 hours
1) Variable set.....Name "%WMwatch" and To 0 and "If %WMwatch" eq 25
2) Variable add....Name "%WMwatch" and Value 1 and Wrap Around 0
Second step. Set the watchface. You need to use the Tasker Watchmaker plugin. The action is "WM Change Watch". The trigger event you want to set to every 5 minutes (or 2, or 10 minutes or whatever). I use 5 minutes and the battery drain is completely negligible.
1) Configuration: choose your watchface...and use the IF function %WMwatch EQ 1 (and then a different watchface for 2, and 3, and so on).
That's it. Kind of hard to explain, but if you guys are familiar with Tasker you should be able to figure it out. This hack is still working for me, and I love it.
I just got the ROG Phone 3.
With the Screenshot and the Screen Recorder functions, is there a way to crop the image?
On my previous phone I could screen capture a portion of the screen by drawing a square around it. It was handy to cut out an ad or unwanted part of the image.
Similarly, I could select the area of the screen that I wished to record. This again helped for the same reasons.
The ROG Phone 3 seems to only allow the whole screen to be captured or recorded (unless I'm missing something?).