Related
I've put together a watch face that uses an animation control with 46 frames (each is 300x300 pixels in size), which I've then spreadout over the whole day (so each frame is displayed for 31 or 32 mins). I've then put on the usual watch hands and digital clock to complete it.
It looks fine when I preview in GWD and I can successfully build it and install it to my Gear S2. However, when I try and select the new face on my watch I see the preview picture followed by a black screen. After being unresponsive for a short period of time it switches to the preview picture of one of the built in faces and remains unresponsive. A quick reboot gets the watch running again, but it still doesn't let me use my new watch face.
Anyone seen this sort of problem before or got any suggestions on ways to get it running? After spending a reaosnable amount of time manually adjusting the timings for 46 frames of animation I'd really like to see this working.
Thanks,
John.
Just got a lg 360 camera and having a strange issue, it stops recording exactly 20 minutes in, this seems like an artificial limitation, but I can not find how to stop it.
I am using a 64gb sd card and the file size is 2.4gb (I realize on afat32 4gb will be the limit but expected it to simply create a new file at that point.)
Extrapolating out and rounding up that is 7.5gb an hour so the 3 hour long events I planed to record would take 22.5gb so disk space is not an issue....just this darn 20 artificial limit.
Any solutions (seems a common issue from searches but cannot find any fixes)
mrgreaper said:
Any solutions (seems a common issue from searches but cannot find any fixes)
Click to expand...
Click to collapse
This question is not really new. see here > https://forum.xda-developers.com/showpost.php?p=67111950&postcount=4
a solution is ,as i know, not available until now.
Tip: the record time seems to be a little longer, if you reduce the resolution.
see here->https://forum.xda-developers.com/showpost.php?p=67305581&postcount=23
But who wants to do that?
non-toxic said:
This question is not really new. see here > https://forum.xda-developers.com/showpost.php?p=67111950&postcount=4
a solution is ,as i know, not available until now.
Tip: the record time seems to be a little longer, if you reduce the resolution.
see here->https://forum.xda-developers.com/showpost.php?p=67305581&postcount=23
But who wants to do that?
Click to expand...
Click to collapse
Yeah since these will be viewed mainly in vr, resolution matters a lot more then usual...damn, gonna have to rig up a timer and hit record again every 20 minutes, sometimes developers make some absolutely bonkers decisions, personally i would of just had it auto create a new file and let the user decide when to hit stop.
(and that thread did come up in my searches i but i did not want to necro it)
Well today was the big test and tbh the camera failed it.
Ok so the first recording stopped after 20 minutes, no surprise there as i was expecting it.
I restarted the recording and it stopped after 12 minutes
I restarted the recording and it stopped after 4 minutes
I restarted the recording and it stopped after 2 minutes!
It was rather warm to the touch (even though the room we were recording in was fairly cold)
i let it call down for a couple of minutes and tried again... it stopped after 9 minutes so yep it was over heating
I tried to record again...22 seconds
I gave it about 10 minutes to cool down and tried again, it lasted 19 minutes
Then 1 minute recording time
I gave it 2 minutes cool down and it lasted 7 minutes
then 2 minutes recording time
I gave it another 2 minutes cool down and it lasted 8 minutes
This is where the battery failed
Now this was in a large, not chilly but not warm room, with plenty of space around it. full recording length about an hour 45 ish all done with the wifi turned off on the camera to conserve battery on 360 degree mode full resolution (assuming manual record uses full resolution) total file size pre-converting (which using thier desktop app is taking forever!) 11.6gb
to say i am not impressed is an understatement.
somebody else has reported a notification requester after restarting his record again. Recording was discontinued because overheating of cpu. See here for more information about that: post 12!
-> http://360camerasforums.com/index.php?/topic/1079-record-while-charging/
This seems to be a health protection of LG 360 cam firmware. Stop of recordings after 20 min or 4GB of size (because the capability of FAT32)
as you can see, it should be the same circumstance with Samsung Gear
-> http://www.threesixtycameras.com/best-360-camera-out-now/
non-toxic said:
somebody else has reported a notification requester after restarting his record again. Recording was discontinued because overheating of cpu. See here for more information about that: post 12!
-> http://360camerasforums.com/index.php?/topic/1079-record-while-charging/
This seems to be a health protection of LG 360 cam firmware. Stop of recordings after 20 min or 4GB of size (because the capability of FAT32)
as you can see, it should be the same circumstance with Samsung Gear
-> http://www.threesixtycameras.com/best-360-camera-out-now/
Click to expand...
Click to collapse
Yeah i get the feeling its early adopter symptoms and not something that is easily fixed (no amount of firmware updates is going to add cooling...unless it blows a capacitor and makes a hole, which may cause some unwanted side effects)
My 11gb 1 hour 35 minute 2k(not as impressive as that sounds, remember thats 2k for 360 degree so in reality much lower res then hd?) video is uploading to youtube, at the minute i can not share the link as one of my mates has asked the video remain unlisted until he has seen it.
It was a bleep to join the files together, everything i tried either did not work or wanted money, in the end i had to use a trial version of adobe premier cc 2017 (no idea what ill do next week, make a new adobe account most likely lol(in my defense if it was a one off charge i would pay it...£20 a month...nope dont have that kind of money) anyway, this took an hour and a half to join the files, but i loaded the result into the lg 360 desktop player and it worked perfectly
It should also be worth noting here for people that find this thread, the desktop application converted the videos a lot slower then my honor 8 smart phone.... i mean like 3 or 4 times slow and only one at a time. (my pc, being an i7 6700 with 16gb ram and a gtx 1080, should of had my phone dead to rights lol)
@mrgreaper
Normally a good video cut software has to render only the few frames between two parts of video. But all the costless software i know, will render the whole video again! This is absolutely unusable to save time!
maybe this could be interesting for you too:
1.) http://vidpromom.com/edit-360-video-theta-s-360/
2.) http://www.viar360.com/
3.) https://www.quora.com/What-is-the-best-360-degree-video-editing-software
you could test PowerDirector 15 of Cyberlink or VideoStich. Both are able to edit 360° video streams. You can get trials of both software!
Recently my screen has started developing strange shadows of apps that i use for longer time, like browsers, keyboard etc.
Even youtube after using for more than an hour or so give shadows on screen.
The issue is more persistent with the keyboard, as i am a heavy internet user (7-8 hrs online) and most of the time keyboard stays on the screen, the screen is showing me a persistent shadow of keyboard, initially just after using it for more than an hour the shadow is very clear and it stays even in the brightest apps and screens , later after sometime it starts to fade but never really goes away, its there always faintly.
What should I do?
Attached screenshots but i don't know if you guys can see them or not.
Edit : its on the screen (hardware)as screenshots don't have shadows, don't know if my screen is faulty
Screenshots are no good, take a picture of the physical phone screen instead.
Screen Burn-in Tool could help, it's designed for AMOLED, but it might end up having the same effect, and there should be no risk (except maybe some wasted time ).
nick_white said:
Screenshots are no good, take a picture of the physical phone screen instead.
Screen Burn-in Tool could help, it's designed for AMOLED, but it might end up having the same effect, and there should be no risk (except maybe some wasted time ).
Click to expand...
Click to collapse
Thanks but i think its better to get the screen replaced because the burn-in tool is a temporary solution, it again comes up after few hours and usually goes away in the morning as i don't use phone at night..
Also screen flickering is visible on very close inspection of some dark screens and checkered wallpapers
Hi all
Is there any way to even custom make a face with the watchmaker or the galaxy watch designer but keeping the hour and minutes hands fully bright as in full brightness when in AOD mode?
You see I just want to be able to check time on my motorbike when driving with a glance in fully sunny day and not looking for a shady place on the street:laugh:
Thanks
pamarakos said:
Hi all
Is there any way to even custom make a face with the watchmaker or the galaxy watch designer but keeping the hour and minutes hands fully bright as in full brightness when in AOD mode?
You see I just want to be able to check time on my motorbike when driving with a glance in fully sunny day and not looking for a shady place on the street:laugh:
Thanks
Click to expand...
Click to collapse
I think you can't control the brightness decreasing when the watch switches to AOD mode. I remember in Watchmaker there was a option to tune the brightness in AOD mode but it was never as bright as in normal mode.
What could help you is this app: Flaunt
It will keep your display on for 30 minutes but at a cost of battery life
clonednull said:
What could help you is this app: Flaunt
It will keep your display on for 30 minutes but at a cost of battery life
Click to expand...
Click to collapse
I will have to try that! In the meantime, I think I've exploited a bug/glitch on my Galaxy Watch 3. I can't show it in a photo because of auto light adjustments, but it looks at least 1.5-2X as bright as the dim limitation.
I set my brightness to 5, with auto brightness on and screen timeout at 5 minutes - seems to consumer about 1% extra battery per hour.
1) In WatchMaker, set screen timeout to default, and 70% OPR in bright mode (15% is all you can do in dim mode)
2) With Tasker on your phone, set up an event triggered by time (i.e. 8AM - 11PM) that repeats every 5 minutes
3) Use the WatchMaker plugin to send that same face to your watch.
It may take a cycle or two to sync up, but what it does is tricks or freezes the watchface in something substantially brighter than the 15% OPR, I'd assume maybe 70% of whatever it is in brightness.
The hour and minute hand still update every minute. In fact, you will see the now frozen second hand move for about 3 seconds every minute as the time updates. I might just drop the second hand if I can't figure out how to hide it selectively. As an added bonus, the refresh doesn't activate the face, it will flash and the hands update but it remains in dim mode.
I think you can disable the vibrate notification for a face change. It flashes quite quickly on refresh - 1-2 seconds. I wonder if there's a way to disable the "white" flash on refresh? Otherwise, I'm pretty happy with it for a more usable AOD with faces that are otherwise hard to see at 15% OPR.
WARNING: Don't forget about burn-in. I'm creating a mesh overlay (basically 1 pure black pixel per 11x11 square) that will "rotate" every minute to duplicate the burn-in protection. Instead of shifting pixels, it will black out very pixel once every hour or two. Then I also have a rotation of black/dark gray screens with an equal number of colored faces.
I just noticed that my Pixel 4 XL (currently has the newest Android 12/November patch) does not cycle between 60 and 90 hz anymore. I just noticed an unexpectated and new drain on the battery and finally found the culprit.
Yes, I checked developer options, the phone is NOT forcing 90hz. I checked with developer options (show refresh rate) and the phone is constantly, meaning 100% using 90hz, it never changes to 60. No matter what I do - Youtube, phone, scrolling, doing nothing, idling, homescreen, newspaper app, Audible - it matters not. It is constantly forcing 90hz WITHOUT having ever clicked the 90hz force toggle. This is putting a drain on the battery that is just unacceptable.
Can you guys confirm this?
Try clearing the system cache.
A factory reset maybe be needed after a major OTA firmware upgrade but there's no guarantee it will resolve it.
Updates tend to break things...
blackhawk said:
Try clearing the system cache.
A factory reset maybe be needed after a major OTA firmware upgrade but there's no guarantee it will resolve it.
Updates tend to break things...
Click to expand...
Click to collapse
The phone was - actually - already factor reset. After doing the Android 12 update, I factory reset it and gave it to a family member, that one set it up new. So it's not a "remnant" of Android 11.
Morgrain said:
The phone was - actually - already factor reset. After doing the Android 12 update, I factory reset it and gave it to a family member, that one set it up new. So it's not a "remnant" of Android 11.
Click to expand...
Click to collapse
I would re-flash with the latest full image, leaving the script intact (allowing the data partition to be wiped). This may be inconvenient but it's the only way you will know if there is a hardware issue with the phone. I'd also like to know what led you to the refresh rate. In other words, what made you look there. The stock battery monitor is not very good and even looking at system apps (screen, ambient display) you only get time and a percentage of the battery.
is the same on 12 and 11, i just installed 11 and is always 90hz
yes i can confirm, i had the same issue and i just boght my pixel 4 xl 10 days ago. updated to android 13 beta now and it still has the same problem. really weird but i think that google just decided that its best for google pixel 4 owners to have 90hz all the time now cause u know its "more common" now
Google changed how Smooth display works during the cycle of the phone. IIRC it was the same on A11 too. Basically the only time it goes 60hz is during battery saving mode & in some specific apps that prohibit it. It also disables it when HBM is on.
That doesn't make a lot of sense, you can save much more energy by just raising to 90hz for touch and animations and otherwise reduce to 60hz independently of the battery state.
I had the pixel 7 Pro for a while and can confirm that it works there as expected (60 for static content & no touch events, otherwise raises up to 120hz), just not for the pixel 4 XL.
This does seem like a bug to me and explains why battery life (SOT) got so much worse. I wonder if it's an intended degradation to get people to upgrade..
Fix it with adb, set minimal refresh rate
adb shell settings put system min_refresh_rate 1.0
adb shell settings put system peak_refresh_rate 90.0
Tested that, does not work either unfortunately. Display stays on 90Hz all the time
onemandivision said:
Tested that, does not work either unfortunately. Display stays on 90Hz all the time
Click to expand...
Click to collapse
Confirm you have extra dim disabled, and brightness 60%
Confirmed, does not make a difference
Out of nowhere it started working. The only thing I changed in between is brightness and extra dim, ending up with the same setting as before (full brightness, extra dim disabled). Didn't work straight away, but after leaving the phone for 5 minutes and picking it up again, I immediately noticed (display refresh rate setting was still enabled)
Thank you for your help, Hamid!
onemandivision said:
Out of nowhere it started working. The only thing I changed in between is brightness and extra dim, ending up with the same setting as before (full brightness, extra dim disabled). Didn't work straight away, but after leaving the phone for 5 minutes and picking it up again, I immediately noticed (display refresh rate setting was still enabled)
Thank you for your help, Hamid!
Click to expand...
Click to collapse
No problem, glad i helped!
Feel free to visit my optimization threads, it might help improve your battery life and performance.
One last remark: It didn't really work well at first, at least not as consistently as on the pixel 7 that I've tried. After some trial and error, playing around with various settings, the culprit seems to have the "increase touchscreen sensitivity" setting that I had enabled. Since turning it off, the switching between 60 and 90Hz is much better. Brightness and extra dim don't seem to play a role.
Battery life also seems to have improved a lot (now at ~50% at the end of the day compared to <20% before)