Database Develop

Bootanimation.zip question

Is there a size constraint ? I'm working on making my first one ... and having some issues . Trying to sort out the issue .
Sent from my SCH-I500 using XDA App

The max screen resolution is 480x800.
I have seen 480x854 work on my phone, but not 490x810. Also, the 60fps doesn't work as a framerate, 24fps and 30fps do.
I'm playing around with the image size on the original GalaxyS boot animation to fill the screen, and that's what I've found.
Good luck, and be sure to post it up so we can see when you're done.

Supposedly, there is a 3MB limit per folder, not sure if this is true or not. Also, make sure the zip doesn't have compression, it should be created in store mode.

imnuts said:
Supposedly, there is a 3MB limit per folder, not sure if this is true or not. Also, make sure the zip doesn't have compression, it should be created in store mode.
Click to expand...
Click to collapse
That might be the issue .. I'm using winrar to zip . What do I use to zip in store mode ?
Sent from my SCH-I500 using XDA App

Okay I got it zipped in store mode .. and its booting now ..but its soooo choppy . My preview in Photoshop is super smooth . My zip size is like 3.8 , could sheer size be causing it to bog down ?
Sent from my SCH-I500 using XDA App

me too...
I'm having trouble with the ones I created too. I rendered them in Vegas pro and they work but really slow. I encoded them at 30fps and the images are 480 x 800. I uploaded the one i made if any body wants to try.
edit: the are like 35mb so i don't size is the issue...
http://dl.dropbox.com/u/10712645/bootanimation.zip

Same here . Mine is superslow . I have more animation to add . But don't want to go on until I know how to boot properly
Sent from my SCH-I500 using XDA App

I'll give it a shot...flash it or replace it thru root explorer?
Sent from my Froyo'd Fascinate via Tapatalk

replace it.

I have also been playing with boot animations using pictures from a 8 meg canon camera and from frame captures of 720p video. My biggest one is 55.7meg and runs perfectly at 29fps. i currently have that are built from vids running one being the 55.7 meg and another at 52.4 meg runnin 29fps. Then I have multiple other smaller ones with frame rates running as low as 12fps because they are built as slide shows. It is true that the aspect ratio for the sf is 480 x 800, but when you resize your pictures make sure to maintain the 480 as stated above. Some of my frame shots from vids ran off in size turned out to be 480 x 640 and the boot wouldnt run right till i plugged those exact dimensions into the desc file. One hint i can give is after you resize your images to the correct res. go ahead and compress them too. helps them load faster. Then zip in store mode and have fun. Takes me about 15 minutes average to build one depending on the source.

All4TheFam said:
I have also been playing with boot animations using pictures from a 8 meg canon camera and from frame captures of 720p video. My biggest one is 55.7meg and runs perfectly at 29fps. i currently have that are built from vids running one being the 55.7 meg and another at 52.4 meg runnin 29fps. Then I have multiple other smaller ones with frame rates running as low as 12fps because they are built as slide shows. It is true that the aspect ratio for the sf is 480 x 800, but when you resize your pictures make sure to maintain the 480 as stated above. Some of my frame shots from vids ran off in size turned out to be 480 x 640 and the boot wouldnt run right till i plugged those exact dimensions into the desc file. One hint i can give is after you resize your images to the correct res. go ahead and compress them too. helps them load faster. Then zip in store mode and have fun. Takes me about 15 minutes average to build one depending on the source.
Click to expand...
Click to collapse
would you be down to assist me on mine? i have hit a brick wall and and pretty much just moved on to other projects. I have practically no animation exp though , so im sure that plays a factor .. haha . what i want it very simple .

¿¿Image compression on Optimus 2X??

Hi everyone.
I whant to know, if optimus 2x have any type of image compresion, yes, that compression sometimes reduces the image quality, and produces a blurry, and crap images.
SGSII i think doesn't have any type of compresion due the image size is arround 2-4Mb.
But i dont know about Optimus 2X, and maybe if have image compresion, we can modify that to have better quality images.
Excuse my bad english and thanks.

2-4 meg for an 8meg photo is surely still using compression. As without compression that would be closer to the 7-8 meg size. I took a picture last night on my O2X of the clouds and that was about 2.5 meg.

stevvie said:
2-4 meg for an 8meg photo is surely still using compression. As without compression that would be closer to the 7-8 meg size. I took a picture last night on my O2X of the clouds and that was about 2.5 meg.
Click to expand...
Click to collapse
Thanks for the info my friend!!
So... we can reduce the image compresion, to obtain more quality??
Where i can find that file?
Thanks again.

choose super fine in image quality, then u can get the least compression for jpeg.
Sent from my LG-P990 using XDA App

[Q] Panorama app the use 8 megapixels?

I´ve been trying several apps, but it appears that all those I´ve tried were not taking every single picture before stitching them up in 8 megapixels..
How i know that? I took a wide shot with only 2 pictures. The resolution was below what you get taking a single photo in 8 megapixels.. Shouldnt the resolution be doubled or 50% higher than a single photo?
So, do you know any apps that does that?

I think the photos are smaller so that the cpu can handle the near real time processing. 8mp frames stitched together will be too much to handle.

Well, are there any apps that take pics in8 megapixels but take longer process to stitch the pics together?

Im reviving this thread cause by now there should be more answers.. So anyone knows an app that does use the 8 mp when taking the panorama picture

[Q] Average size of a single Zeo shot?

Hi guys! Would like to ask what's the average size of a single zoe shot? The total file size of the 20 sequence pics + the 3 seconds video.
Hope somebody answers this.

Riyal said:
Hi guys! Would like to ask what's the average size of a single zoe shot? The total file size of the 20 sequence pics + the 3 seconds video.
Hope somebody answers this.
Click to expand...
Click to collapse
1st example: 38,8 MB (40.739.272,00 bytes)
2nd example: 24,3 MB (25.503.183,00 bytes)
3rd example: 26,9 MB (28.287.652,00 bytes)
4th example: 27,7 MB (29.063.263,00 bytes)
Each the sum of 20 pictures plus 1 video. From these 4 examples, taken at different conditions, comes an average of approx. 30 MB. Hope I could help.

Thank you! Indeed a great help to me

Themes / Apps / Mods s21 ultra 108mp raw

hello i'm nosidam although you can refer to me as nosi or idam for short, at any rate it has come to my attention that for over two year's individuals much like myself that are into high resolution photography have been wanting access to the raw resolution of the hundred and eight megapixel (108mp) sensor and countless have tried but unfortunately to the best of my knowledge to no avail, for the past few months i've been working on just that and recently completed the project. the hundred and eight megapixel (108mp) sensor with raw resolution has been unlocked the only dilemma now is making it possible for other's to do it, my method required a very custom language and architecture emulation in order to make it possible and unfortunately the very language and architecture as you could surmise from the necessity for emulation was derived from custom harware and wasn't designed to be utilized in conjunction or substitution for commercial applications or software, additionally unfortunately the language is behind a wall of confidentiality obligation due to what it's used in and for so as you can imagine that means i can't simply distribute it openly although i am working on another project to make it possible utilizing commercially accessible and viable software that can be distributed so that it'll be available for disclosure although until then despite not being able to currently share something distributable i can actually show you the results and comparisons and results of my tests as well as give you some interesting statistics lol.
project C.I.A.R.A. - Google Drive
drive.google.com
that should be a link to a google drive folder that has various comparison photos, i've never posted on here before so i don't know if the attached image's will be fully viewable in their respective resolution or if they'll be compressed or not as of such you should be able to download and view the images without any compression from google drive also i tried drop box but it's uploading was spotty and slow despite having fiber gigabit internet and they only offered two gigabytes, so google drive being much faster and consistent without random pauses for uploading in addition to boasting a free ten gigabytes was a clear winner lol,
the phone's default hundred and eight megapixel (108mp) sensor photo is the file labeled:
"20230516_175804"
it's resolution is twelve thousand by nine thousand (12,000x9,000) with a standard dynamic range and is a jpeg file that has been compressed down from what should have been an absolute minimum of a hundred and eight megabytes (108mb) down to just thirty one point seventy six megabytes (31.76mb) which is a minimum compression in file size of seventy point fifty nine percent (70.59%) so as you can imagine it becomes something similar and or closer to being akin to that of a hot mess so to speak, you'll usually see over sharpening occasionally to help accommodate for a lack of quality to give "perceived quality" and seemingly a lack of dynamic range(potentially from the compression or justcthe onboard post processing) as well as artifacting... which personally i do understand why they would do such a thing, people would run out of memory substantially faster if each photo was over a hundred megabytes minimum but honestly if i'm spending one point four thousand dollars on a phone then i'd like access to everything the camera has to offer therefore even if it's hidden behind advanced settings i think we should at least have the choice, although unfortunately even the twenty one ultra with all of it's very state of the art power and processing especially at release still struggles to handle that amount of information and memory so i have to wait between photo's because the phone gets very hot and also starts to stutter or freeze a bit, utilizing the full potential of the sensor is slightly unstable but still possible and i think they should allow it could to be enabled with a disclosure that it's a potentially unstable and experimental setting but instead it's full potential has remained behind close doors so to speak (os lockdown and software lockouts) well i'm working on making the raw one hundred and eight megapixel(108mp) sensors raw potential commercially available i'm also working on a professional mode in my own functional language which will allow much more fine precision control.
now for the moment of truth, the file named:
"20230516_175938"
is twelve thousand by nine thousand (12,000x9,000) in resolution and has a file size of one hundred and sixty nine point fifty four megabytes(169.54mb) with a seemingly high dynamic range(either that or the standard dynamic range has been impacted by the onboard post processing and compression) so just by the file size differential i'm quite certain that you can ascertain that it's actually going to retain all of it's quality lol it's fifty six point ninty eight percent(56.98%) higher in file size than the bare minimum hundred and eight megabytes(108mb) standard, overall it's file size in comparison to the phone's default version is five hundred and thirty three point eighty two percent(533.82%) higher meaning that the phone's image is only eighteen point seventy three percent(18.73%) the size of the raw file quality one, which is a mind-numbingly substantial difference lol and personally i will always take higher quality and larger file sizes over low quality smaller file sizes, i haven't gotten an s23 ultra yet but if i do you can be sure that i'll endeavor to unlock it's two hundred megapixel(200mp) sensors potential, it's my opinion that if these sensors exist in our phones then we should be allowed to fully utilize they're capabilities and potential lol.
i created some very easy comparison crop out photos from each image that have been cropped(not resized) to the standard 1440x3200(WQHD+) resolution of these screens, the first screen shot is a WQHD+ comparison cropped from the default one hundred and eight megapixel(108mp) photo and is named:
"IMG_20230520_133504"
and is very clearly compressed by the aforementioned percentage whereas the WQHD+ comparison taken from the raw quality version is named:
"20230516_221938"
and is very clearly not compressed and retains all of it's raw quality potential.
on a sidenote i'd like to extend special thanks to M0nK_101 for suggesting a variety of sharing services such as drop box and google drive at my request to share the comparisons lol.
^.^
if you have any questions or concerns feel free to let me know.
with that said i'd like to thank you for potentially taking the time and patience to read this i appreciate it.
^_^

So like any update? Will it work on other devices using samsung sensor?
like Redmi 10 pro using hm2

Inzamam567 said:
So like any update? Will it work on other devices using samsung sensor?
like Redmi 10 pro using hm2
Click to expand...
Click to collapse
affirmative unfortunately thus far i have not yet found an unofficially distributed commercially accessible means to unluck the 108mp sensors raw quality potential outside of my project C.I.A.R.A emulation although rest assured i'm still currently working on it also i'll elaborate compatability details when a publicly distributable prototype is viable lol.
^_^

Is this just an app or an entire OS?

neither it behaves in certain ways like an application although ultimately it's custom hardware software emulation that allows the internal onboard sensor algorithms responsible for compression and file formatting to be sidestepped so to speak.
^_^

I see, very interesting! So I would Hage to hook the camera module up to another board in access it from there? Or will it be possible to use the phone itself?

indeed and negative you could utilize the phone itself.
^_^