Recently I've been trying to create some nice boot animation and down animation for my HTC One.
My problem is the both the boot and the down animation look pretty laggy.
So obviously something went wrong with the FPS.
I set the FPS at 30, and with about 1200 frames the animation should end in about 40 secs (I know it is a little long. Trying to get over myself).
But it actually took about 100 secs to finish (OMFG!!!!!!!!!)
That means the FPS actually dropped to just about 12 instead of 30.
At first I thought it was because the pictures are too big to be handled nicely by the phone .
So I did some compression to the pictures (keeping the resolution at 1920x1080 of course), telling myself there really wouldn't be that much noticeable differences on a 4.7" screen.
At last the size of most frames are about 80kb, and some frames with more black color just about 20kb, only a few relatively vibrant frames are about 150kb.
It turned out there is no difference at all, still laggy, still 100 secs!
Then I thought maybe it is because of those 1000+ frames, but theoretically, I think that is not the cause.
If it can run 100 frames at 30 fps flawlessly, why not 1000?
I thought it might be due to the relatively high resolution (though every frame had been compressed).
Finally, by deleting about 80% of the frames and setting the FPS at 10, I was able to make the animation acceptable.
So does anyone have the same problem with FPS?
Is it because of the 1920x1080 resolution that makes it hard to obtain high FPS?
Or it could be modified by changing some mysterious settings?
I find when I set my minimal cpu frequency too low the bootanimation lags. Stock 348Mhz should work and is lagless for me.
Sent from my HTC One using xda app-developers app
Tw1tchy said:
I find when I set my minimal cpu frequency too low the bootanimation lags. Stock 348Mhz should work and is lagless for me.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Can you share your boot animation file, so I can compare the exact difference
Tw1tchy said:
I find when I set my minimal cpu frequency too low the bootanimation lags. Stock 348Mhz should work and is lagless for me.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Do you use an app to set the cpu frequency?
Here is what I have learned while making these. If you keep the full resolution (1080x1920) the animation will usually always lag and be slow unless its under 50 frames. Sometimes I have found for a slightly longer animation (over 50 frames up to about 400) that you separate your frames into folders of 30 frames per folder. Also, if you take the animation and reduce it's resolution to half (540x960) it will still look acceptable and run smoother. The last thing, I know the file format .png is the suggested format to use and of better quality... But I get better results using jpegs, probably because they are compressed more.
The main thing to take away from this, every animation is different and will need something done to it a little differently than the last one you made. It's more of a "turn the knob slowly" each time and try it out. Slow, but gives you best results.
Crackanug said:
Here is what I have learned while making these. If you keep the full resolution (1080x1920) the animation will usually always lag and be slow unless its under 50 frames. Sometimes I have found for a slightly longer animation (over 50 frames up to about 400) that you separate your frames into folders of 30 frames per folder. Also, if you take the animation and reduce it's resolution to half (540x960) it will still look acceptable and run smoother. The last thing, I know the file format .png is the suggested format to use and of better quality... But I get better results using jpegs, probably because they are compressed more.
The main thing to take away from this, every animation is different and will need something done to it a little differently than the last one you made. It's more of a "turn the knob slowly" each time and try it out. Slow, but gives you best results.
Click to expand...
Click to collapse
Yeah, thanks. reducing the resolution does help improve the smoothness.
Really took me a lot of time trying to make it perfect.
batongxue said:
Yeah, thanks. reducing the resolution does help improve the smoothness.
Really took me a lot of time trying to make it perfect.
Click to expand...
Click to collapse
Great to hear! It usually is a trial and error process, a little time consuming but worth it in the end.
Related
Good day to all of you. I would like to tell you my vision for Arc S improvements. Firstly in Gaming. MUST support GB ROM PLEASE!
In-Gaming there should be at least:
- Screen Resolution adjuster: ARC S is way better in 640X480 Resolution (MUST SUPPORT FIT TO SCREEN SO NO BLACK AREAS). Most apps will run at 30FPS stable or more (Dead Trigger, Subway Surfers, etc)
- Screen Resolution for apps: This will set your selected games to run at most at least 640X480 instead of 854X480. (MUST SUPPORT FIT TO SCREEN SO NO BLACK AREAS)This app will set your games resolution to desired resolution when launch.
- More Kernels that you can made to make further improvements or ask DoomLord's or Wedgess permission to continue their GB kernels or ICS or JB.(If existing)
This is my vision. Thanks for taking time to read this. Good day. I don't mean any harm if you think that.
I see your point, however I seriously doubt changing resolution from 854x480 to 640x480 gives any major performance boost (I have no idea, where are you taking it from).
Secondly, fitting the image with size of 640x480 to 854x480 screen will just end up quite stretched.
Well if you have such a vision you can start by learning Android programming and development instead of sitting there and telling the whole world your vision.
僕のLT18iから送られてきた
Someguyfromhell said:
I see your point, however I seriously doubt changing resolution from 854x480 to 640x480 gives any major performance boost (I have no idea, where are you taking it from).
Secondly, fitting the image with size of 640x480 to 854x480 screen will just end up quite stretched.
Click to expand...
Click to collapse
I tried it. Since The time I used SJB rom Subway Surfers since it lags massively on JB. I had an 26 FPS on normal 20 on Heavy. But when I set res to 640X480 the FPS increase to 33-38 FPS which is great. So it worked that well. But the resolution won't fit the whole screen. It will be stretched but not much. In Emulators epsxe normally on Arc S Crash Team Racing has 54/60 on Selecting character on Adventure mode. While I gained more speed when reducing to 640X480. I can run it at 60/60 at 640X480. Thanks for noticing my idea since I don't have any money to go to oher devices. This Arc S was originally an Arc (secondhand) given to me by aunt. Then I swap to Arc S.
Hey, everyone! I'm looking for the best way to change the resolution of the G3. I used an app that supposedly does it, and it did, but it bugged out every boot to where it would go back from 1080 to 2K, though it would think it's 1080. I know 2K is awesome, but not only can you just about not notice the difference, but game performance are GREATLY increased!! Battery life may be much more improved as well due to using less GPU power. I had frame drops on PPSSPP playing Monster Hunter in 2K but at 1080, it was always locked at 30fps. Heroes of Order & Chaos I think had worse frame drops but I hadn't gotten the chance to try it yet. Can I change the actual screen resolution, and not the DPI alone, through the build.prop file or something?
https://play.google.com/store/apps/details?id=com.nomone.resolution_changer
Pfeffernuss said:
https://play.google.com/store/apps/details?id=com.nomone.resolution_changer
Click to expand...
Click to collapse
I tried that app, and used the G2 preset. It made the status bar look funny (the icons became too big for the bar) and I didn't notice any performance improvements.
Professor Jones said:
It made the status bar look funny (the icons became too big for the bar) and I didn't notice any performance improvements.
Click to expand...
Click to collapse
That, in a nutshell, is what you get when you artificially "lower the resolution"
I know that LG implemented a dynamic framerate to help save battery. I was wondering how is the global framerate of cm12 decided? is it baked into the kernel or the system? if so is there any boot script that determines this sort of thing?
If possible id want to experiment with different framerates (above 30 and below 60) and see the effect on battery. - ive already dropped my phone down to simulate 1080p and take some stress off the GPU/CPU (reduces a lot of lag)
If i could drop framerate to 45 or so it should help save some more battery.
Maybe in the future if any of this works we can create our own dynamic framerate (or maybe can be integrated into xposed framework) for saving battery etc. 30fps may be choppy at times but something like 45fps should only be noticable on really fast animations that cover a large portion of the screen.
LOGMD said:
I know that LG implemented a dynamic framerate to help save battery. I was wondering how is the global framerate of cm12 decided? is it baked into the kernel or the system? if so is there any boot script that determines this sort of thing?
If possible id want to experiment with different framerates (above 30 and below 60) and see the effect on battery. - ive already dropped my phone down to simulate 1080p and take some stress off the GPU/CPU (reduces a lot of lag)
If i could drop framerate to 45 or so it should help save some more battery.
Maybe in the future if any of this works we can create our own dynamic framerate (or maybe can be integrated into xposed framework) for saving battery etc. 30fps may be choppy at times but something like 45fps should only be noticable on really fast animations that cover a large portion of the screen.
Click to expand...
Click to collapse
This would be best posted in the Cyanogenmod 12 Official Forum Thread for LG G3 where CM12 developers frequent, since most of us here are rookies or have little to no experience at android programming
As they title said I tied to find out but am at a loss in trying to find out exactly what is happening when we use the HQ mode in the camera app.
In night scenes it seems to produce a better photo but the shutter speed is the same. One plus have not really said what they have changed since the HD to HQ update so wondered if anyone could let me know ? Is it an extra stop in exposure maybe ?
Just watch this video:
https://www.youtube.com/watch?v=md3Ow6AEwLU
(HD recently got renamed to HQ)
Mine still says HQ
Sent from my ONEPLUS A3000 using XDA-Developers mobile app
jdawgg21 said:
Mine still says HQ
Click to expand...
Click to collapse
It used to be hd then they changed it to hq
AcmE85 said:
Just watch this video:
(HD recently got renamed to HQ)
Click to expand...
Click to collapse
Thanks for the video but it didn't really answer my question as it was only a comparison.
That video just compared the 2 options of HD (which has slightly changed since they renamed it to HQ) and HDR. It does not explain what kind of post processing happens apart from staying it used a de noise filter. I wonder what "exactly" is happening with exposure, contrast, saturation etc when you use this HQ mode ?
If anyone knows that would be really helpful.
Crap. I read it wrong. I thought it said HQ recently got changed to HD. And does anyone elses HQ lag like crazy?
Sent from my ONEPLUS A3000 using XDA-Developers mobile app
jdawgg21 said:
Crap. I read it wrong. I thought it said HQ recently got changed to HD. And does anyone elses HQ lag like crazy?
Click to expand...
Click to collapse
Not suffering any lag on mine however I am not rooted and complete stock ? How about you ?
ipmanwck said:
Not suffering any lag on mine however I am not rooted and complete stock ? How about you ?
Click to expand...
Click to collapse
Mine is rooted and running the Elemental Kernel. So I guess that's probably it.
Sent from my ONEPLUS A3000 using XDA-Developers mobile app
@jdawgg21 Nope, that's not it.
When using HQ in lowlight, it automatically reduces shutter-speed even more compared to the already lower speed in auto-mode.
Lower shutter-speed = lower framerate
1/30s = 30fps
1/10 (mostly when using HQ) = 10 fps
When others say they don't see the lag, it must only mean they did not test this in the same lighting conditions as you did.
It "lags" here too and so does it on every device which will use 1/10 or even lower shutter speed which shows you a real-time preview of what the image will approximately look like when taking the shot.
AcmE85 said:
@jdawgg21 Nope, that's not it.
When using HQ in lowlight, it automatically reduces shutter-speed even more compared to the already lower speed in auto-mode.
Lower shutter-speed = lower framerate
1/30s = 30fps
1/10 (mostly when using HQ) = 10 fps
When others say they don't see the lag, it must only mean they did not test this in the same lighting conditions as you did.
It "lags" here too and so does it on every device which will use 1/10 or even lower shutter speed which shows you a real-time preview of what the image will approximately look like when taking the shot.
Click to expand...
Click to collapse
Finally a sensible answer. Thanks man. I had been asking around and Juan Bagnel said it's probably doing something like a dslr de noise function so what you said makes sense I have only used it indoors with artificial light so probably had no lag but so is what is displayed on the screen if it is leggy is representative of the shutter speed ?
I have heard from a Carl Pei interview that the camera is the reason for the phone having 6gb of ram because it snaps 4 photos at the same time we snap one photo. The phone then automatically chooses the best one photo of those four photos. I reckon that is also a probable answer due to the lag you are experiencing.
Skickat från min ONEPLUS A3003 via Tapatalk
markusviktorius said:
I have heard from a Carl Pei interview that the camera is the reason for the phone having 6gb of ram because it snaps 4 photos at the same time we snap one photo. The phone then automatically chooses the best one photo of those four photos. I reckon that is also a probable answer due to the lag you are experiencing.
Click to expand...
Click to collapse
No, this is not the answer for the "lag". Why doesn't it lag in good lighting then?
I already gave the correct explanation for this.
As an example: I don't know if you have experience with the OnePlus One. It also started lagging much heavier in lowlightconditions due to the low shutter-speed.
Eventually, Sultan released his modded camera hal which forced the camera to not go below 1/30s on the shutter-speed.
The result was a perfectly fluid viewfinder regardless of the lighting conditions.
I am only talking about the fluidity of the viewfinder here. (Shutter-speed and video-framerate is a whole different story not to be mixed-up here...)
I've seen this interview too,
but I don't agree with him that it takes the best of these 4, instead I think that it somehow combines them into one.
This often results in more blurry pictures, even in good lighting!
Check this video I did on this issue:
http://www108.zippyshare.com/v/KidtanPE/file.html
As you can already see in the video, all images were taken without HQ or HDR. You can clearly see this when taking a picture and quickly swiping to the gallery.
For an instant, you will see the unprocessed picture which quickly changes as processing is being applied! Sometimes to the worse though :/
This gets more pronounced the more the ISO level goes up on a shot.
I was holding my phone as steady as possible and you can see that the shots which are displayed first look sharp before postprocessing.
So how can this be explained when, as Carl says, "the camera takes the best out of 4 shots"?!?
I first thought that in HQ mode, the camera is doing Dynamic Denoise
Grainy pictures are a thing of the past with Dynamic De-noise, which takes several photos and compares them to reduce noise and improve clarity.
Click to expand...
Click to collapse
Source
However GSMA review says that the Denoise function gets activated automatically when there is minimum handshake and is not dependent on modes.
A few other things I have noticed.
1) On 3.1.x the noise suppression was very aggressive, almost like a water paint effect. On 3.2.x, the photos are more natural. Still less noise that normal mode.
2) The minimum shutter speed in HQ mode is 1/10 while without HQ it is 1/17
3) RAW is disabled in HDR as well as HQ modes. This makes me think that the HQ (like HDR) is using multiple snaps to filter noise that is Dynamic denoise. If you quickly switch image preview after clicking a pic, you can see the transition from normal to HQ happening. This is definitely not normal noise reduction.
ungeeked said:
This makes me think that the HQ (like HDR) is using multiple snaps to filter noise that is Dynamic denoise. If you quickly switch image preview after clicking a pic, you can see the transition from normal to HQ happening. This is definitely not normal noise reduction.
Click to expand...
Click to collapse
This is exactly what I said in my post right above yours and it even happens when HQ and HDR are disabled.
Check the linked video. I bet this is what you mean.
I hate this behavior, often faces are smoothed out because of this, even in perfect lighting conditions.
Hi, it seems the HQ mode does not generate RAW file, someone He checked?
manu.mr64 said:
Hi, it seems the HQ mode does not generate RAW file, someone He checked?
Click to expand...
Click to collapse
A raw file is a photographic negative without any processing applied to it.
So even when the app would generate a raw file in HQ mode,
it would not look any different than the raw file created with HQ disabled.
My best bet is that the app is saving its resources for the HQ postprcessing,
thus completely skipping the raw part intentionally.
AcmE85 said:
A raw file is a photographic negative without any processing applied to it.
So even when the app would generate a raw file in HQ mode,
it would not look any different than the raw file created with HQ disabled.
My best bet is that the app is saving its resources for the HQ postprcessing,
thus completely skipping the raw part intentionally.
Click to expand...
Click to collapse
OK understand, thank you very much
Hey guys,
So just wondering has anyone noticed and pros / cons when switching the display resolution from WQHD ( 2560 x 1440) to HHD (1920 x 1080)?
Ive switched to it back and forth several times, and so far I really cant see any difference. The screen quality / crispness seems to be the same. Also I noticed that when i have FHD selected the device obviously seems to run a little faster / snappier.
Incase you don't know what I'm referring to its in Settings>Display>Screen Resolution.
Hmm the only place I can change that is by turning on a power saving mode, I don't see any screen resolution in the settings otherwise (on Canadian N930W8).
stevierayvaughan said:
Hmm the only place I can change that is by turning on a power saving mode, I don't see any screen resolution in the settings otherwise (on Canadian N930W8).
Click to expand...
Click to collapse
Thats strange I have it as a stock option in settings...
I tried it once and didnt like how the LCD density increases significantly. It also doesnt play nice when setting a custom LCD density via a root app or through adb.
I've noticed no improvements with quality, performance, and even battery life. Setting the res to anything but WQHD actually somehow drains more battery and causes performance issues.
To ellaborate on the tricky LCD density issues, I thought I could set the res to 720p and the LCD density to my usual (420 down from stock 560), but having the density to 420 on WQHD and then changing it to 720p essentially erases the set density, and then things get a little funky when trying to re-change the density. Doing so causes some weird glitches since the density of 420 on 720p is based on the resolution, so it actually makes the density much bigger compared to stock density on 720p, and then setting the density to the proportionate number based on calculating the difference causes the entire Ui to seize up and crash. The same effect you would get where if you set the density below 300.
imatts said:
I tried it once and didnt like how the LCD density increases significantly. It also doesnt play nice when setting a custom LCD density via a root app or through adb.
I've noticed no improvements with quality, performance, and even battery life. Setting the res to anything but WQHD actually somehow drains more battery and causes performance issues.
To ellaborate on the tricky LCD density issues, I thought I could set the res to 720p and the LCD density to my usual (420 down from stock 560), but having the density to 420 on WQHD and then changing it to 720p essentially erases the set density, and then things get a little funky when trying to re-change the density. Doing so causes some weird glitches since the density of 420 on 720p is based on the resolution, so it actually makes the density much bigger compared to stock density on 720p, and then setting the density to the proportionate number based on calculating the difference causes the entire Ui to seize up and crash. The same effect you would get where if you set the density below 300.
Click to expand...
Click to collapse
Ok thanks for the great answer! Guess ill stick to WQHD! Just thought it might offer some benefits.
been testing this and found that it does not get warm when switched down
and to the eye same amazing screen
imatts said:
I tried it once and didnt like how the LCD density increases significantly. It also doesnt play nice when setting a custom LCD density via a root app or through adb.
I've noticed no improvements with quality, performance, and even battery life. Setting the res to anything but WQHD actually somehow drains more battery and causes performance issues.
To ellaborate on the tricky LCD density issues, I thought I could set the res to 720p and the LCD density to my usual (420 down from stock 560), but having the density to 420 on WQHD and then changing it to 720p essentially erases the set density, and then things get a little funky when trying to re-change the density. Doing so causes some weird glitches since the density of 420 on 720p is based on the resolution, so it actually makes the density much bigger compared to stock density on 720p, and then setting the density to the proportionate number based on calculating the difference causes the entire Ui to seize up and crash. The same effect you would get where if you set the density below 300.
Click to expand...
Click to collapse
phame said:
Ok thanks for the great answer! Guess ill stick to WQHD! Just thought it might offer some benefits.
Click to expand...
Click to collapse
Sorry, but my findings are almost the opposite, I even made a thread in discussion forum to regard the change to FHD to other users.
FOR ME, switching to FHD has improved the responsiveness of the UI (graceui) considerably, and I do not see the "LCD density increase" (btw.: what should that be? i guess DPI?? then switching to FHD would be a DEcrease...)
Also, I'm almost sure that this must lead to battery improvement too. simple because cpu und gpu have less work to do calculating the lesser amount of screen-pixels to draw! This might be slight, but should be there!
The other problems you mention are because you are playing around with density mods, are you using xposed? I use the lower FHD resolution now for a week, and I do not have ANY problem with it!!! And trust me, I use this phone the whole day long and have many programs and communication tools installed.
everything works as it should!
TML1504 said:
Sorry, but my findings are almost the opposite, I even made a thread in discussion forum to regard the change to FHD to other users.
FOR ME, switching to FHD has improved the responsiveness of the UI (graceui) considerably, and I do not see the "LCD density increase" (btw.: what should that be? i guess DPI?? then switching to FHD would be a DEcrease...)
Also, I'm almost sure that this must lead to battery improvement too. simple because cpu und gpu have less work to do calculating the lesser amount of screen-pixels to draw! This might be slight, but should be there!
The other problems you mention are because you are playing around with density mods, are you using xposed? I use the lower FHD resolution now for a week, and I do not have ANY problem with it!!! And trust me, I use this phone the whole day long and have many programs and communication tools installed.
everything works as it should!
Click to expand...
Click to collapse
This was the case both on root/unroot using standard adb shell wm debsity xxx and in-settings res.