Following instructions from here I pulled the boot ramdisk (uRamdisk) off the first partition of the internal mmc of my NC and unpacked it.
Inside I found initlogo.rle. This is a bootsplash that appears before the boot animation.
I want to see what this is an image of. There seems to be two screens before the boot animation and I was wondering which one this is. (I'm guessing the grey 'n', but I want to confirm that.)
I found this thread on creating a new initlogo.rle and this thread on converting initlogo.rle to png. I went through the steps and the end result was a garbage image file. I double-checked that my process was correct by running it on the user-created initlogo.rle in this thread and it worked perfectly.
My question is does anyone have any idea or perhaps could point me in a direction about what format the initlogo.rle that comes with the NC could possibly be?
If I hexdump the user-created initlogo.rle it's very obviously an rle as hexdump displays data in 2-byte columns. The first and every other column after is usually a small number (the count) while the second and every other after is some larger value (the RGB value). If I hexdump the NC's initlogo.rle it's obviously not in the same format.
There's no obvious header in the file (which is how this type of RLE should be) so I'm assuming it hasn't been compressed with something like gzip and the first four bytes look correct; 0xffff 0x0000, meaning 65535 black pixels which is what you'd expect for an image with a black background.
I know this is an incredibly insignificant issue, but it's nagging me.
Thanks for any help.
I don't have a NC and this is likely a really oversimplified / stupid thought. However, I'll throw it out there anyway. Since Windows BMP are often RLE encoded, what happens to the file if you rename it BMP and then try to open with an image viewer?
epakrat75 said:
I don't have a NC and this is likely a really oversimplified / stupid thought. However, I'll throw it out there anyway. Since Windows BMP are often RLE encoded, what happens to the file if you rename it BMP and then try to open with an image viewer?
Click to expand...
Click to collapse
It doesn't work.
Whether I open it up in MS Paint or Gimp the file is reported as corrupted or broken. The reason probably being the lack of a proper BMP header in the file. Also my understanding is there are different flavors of RLE and the BMP header, in part, defines what flavor of RLE it is.
And you might then think that maybe the NC's initlogo.rle is a different flavor RLE as well. The problem there is there's no header on these files, so whatever application is decoding the image to then display it must assume what format the file is in.
Maybe there's a command somewhere in init.rc or elsewhere that passes some kind of parameter to define what type of format the initlogo.rle is. I'll have to go digging.
Did some investigating as I'm trying to add a boot logo to CM7 for the Nook Color.
The stock initlogo.rle is 600x1024, with the format:
Short, little endian: number of pixels with the following color
Byte: red value, 0-255
Byte: green value, 0-255
Byte: blue value, 0-255
(repeats until end of file)
Pixels are filled starting at the top right, moving by columns down and to the left. The resulting image is attached.
Related
Procedure To Edit The Internet Globe Button Manila Files
(No more solid white blank buttons)
7d3f1247_manila - Globe Unselected
3f00cd2f_manila - Globe Selected
What:
With this procedure you will be able to select any graphics or highlight color you want to use for both the selected and non selected states of the Internet globe button.
How:
There are no special tools required other than Manila Editor 0.2 and a graphics program that can work with png files. You will need to know how to use both of these programs though.
Advantages:
The biggest advantage over editing either 27c65cbd_manila or InternetPortal-en-US.xml would have to be speed. When I tried that way on my Fuze it would take well over 5 seconds to load every time I scrolled to the Internet tab. Sometimes almost double that on a fresh boot. Second advantage would be that this *should* work on any device that uses those 2 files, where the xml edits are different files for different devices. Which leads to the third advantage of not needing special install instructions for theme makers. Edit the manilas and drop them in with the rest.
Other Info:
(Just skip this part if you don't care about the why and scroll down to the instructions.)
I have literally scoured these forums and the Internet for days trying to find information on editing not only the Internet globe manila files, but the other 7+ files that just don't work right with Manila Editor. Most theme makers know of these files. Mostly what I found was a lack of information and more questions than answers. The only other procedure I could find at all for converting manila files gives better results than using Manila Editor but it's very complex for the average user requiring command line tools. Even so the author, (Chainfire) has written a damn near fool proof tutorial so if anyone is interested you can find the thread HERE. Unfortunately even that procedure would not handle the problem manila files properly and quits with the following message.
Reading file: 5c01b59c_manila
Error: file is not QTC format
For reference, this is the list of files that I know of at the moment with this problem, and all return the same error except for 7d3f1247_manila. (More on this file to come.)
7d3f1247_manila - Globe_Unselected (512x256) 28.5k
3f00cd2f_manila - Globe_Selected_D (512x256) 64.5k
40ec2415_manila - Small Avatar_D (64x64) 2.5k
2f411611_manila - Exclamation Point_D (256x256) 32.5k
4d97cac6_manila - Add Contact_D (256x256) 32.5k
54e0759d_manila - Contact Avatar_D (256x256) 32.5k
400b663e_manila - You Tube_D (64x64) 2.5k
55cc771a_manila - Selection Highlight Bar (512x256)64.5k
5c01b59c_manila - Contact Avatar2_D (256x256) 32.5k
The first oddity I noticed when using Manila Editor on the Globe file (3f00cd2f_manila) is no mater what size my graphic was before running it through, it always came out to be approximately 125k. Since the stock file was roughly half that size I knew something was really wrong. The other glaring anomly with most of the files is they show up as duplicated (side by side) images when viewed with M.E. so I figured that somehow all of this must be connected.
I am not a programmer by any stretch but I know just enough to get me into trouble most of the time. Anyway I loaded both files into Notepad++ and turned on hex view to see what was so different. The header of both files were similar but not exactly the same so I copied chunks of the problem file from below its header and pasted it into the good manila at the same address location. What it produced was a repeating pattern on the top left corner of the stock green button but every other row was white. I don't know why but the fact that the image repeats in M.E. as well and the file being double the size made me think to cut the image in half and try to see if M.E. would accept it. It did and I was elated to finally see an image on my phone other than than the big white rectangle.
I had an image that was really distorted but it wasn't difficult at this point to see what was going on by the way it was distorted. I was able to get a perfect button on my next try by creating my image on a 256x128 canvas and then scaling it to 512x128. It looks really bad and stretched out at this point but after processing with M.E., the phone will compress back to it's original aspect and it looks just perfect. I use The Gimp as my image editor and just save as a png file with the default settings.
Now that I Finally had a working selected globe image I wanted to change the static globe as well. (7d3f1247_manila) This was a whole new battle but at least I had something to work from this time. There are some significant differences in this file compared to the selected globe. First, it looks perfect when you extract it using M.E. which led me to believe that this would be easy. I couldn't find much info on this particular manila and I think I know the reason why. Either people are replacing both images via the xml workaround, or they are just concerned with getting the highlight the right color on the selected image. Either way, when I tried to do a 1:1 replace in M.E I got to see the wonderful white rectangle again. At this point I had finally gotten all the tools working from the post I mentioned before and decided to try this file using that procedure as it should return better results if it did work. It worked perfectly but I still wanted to get it to work using M.E as most people are not going bother with a long drawn out procedure.
After playing around some I found that if I scaled the 512x256 image to 256x256 it worked perfectly. The up side is the file size is half of the stock image. The down side is the resolution is obviously cut in half. It's really not a show stopper but using the other method does produce perfect results. Not completely satisfied yet I tried some more images at different resolutions to see what happened. The 480x240 image I had from one of the globe mods that are floating around produced a white rectangle. I then decided to try another unscaled image that was almost completely transparent and it worked without a hitch. Now that I was completely confused I went back and tried the original 512x256 that produced the white and it did so again. It wasn't until I switched to another tab and back again that it finally showed up correctly.
So what does it all mean? Hell if I know but at least the scaled 256x256 method seems to work every time without any problems and its fast to boot. The long procedure would be the best method of them all but probably not worth the effort for most. As far as the other problem files go I guess I'll try and work them out too unless someone else more capable picks up the ball and runs with it. The selected globe was the particular image that stuck in my craw and got me started on this.
Instructions for 3f00cd2f_manila - Globe Selected:
1. Create your image at a size of 256 x 128 exactly how you want it to look on your device.
2. Scale it to a size of 512 x 128 and save it. You will have to "unlock" the aspect ratio lock in most graphics programs. This will distort your image badly but do not fret. Yet.
3. Fire up Manila Editor as usual and use your new image. Now you can fret as you wait to see if this works or not.
4. <-- I hope
Instructions for 7d3f1247_manila - Globe Unselected:
1. Create your image at a size of 512 x 256 exactly how you want it to look on your device.
2. Scale it to a size of 256 x 256 and save it. You will have to "unlock" the aspect ratio lock in most graphics programs.
3. Fire up Manila Editor as usual and use your new image.
General Notes:
If you don't want to mess with any of this and like what's in the screen-shots attached, you can install the cab or just unpack the zip into your windows directory on your device. As always, please back up your files before adding new software.
Notes concerning 7d3f1247_manila:
This procedure *should* work if done as stated. If you use the alternate method I linked to in the info section above you don't have to scale the image and will get a higher resolution image. I have successfully used a non scaled image before with Manila Editor but it goes white on first load after a reboot then somehow clears up. With the scaling method I've yet to see the dreaded white rectangle. Read the info section for more information.
More Information:
Manila Editor 0.2.0
Editing Manila
Manila 3D Porting
Pixel Perfect TF3D ***
Manila Fine Details
Cheers,
Eidolen
*Disclaimer*:
Obviously I can't test this on every device but I can't think of any reason why this wouldn't work on any TF3D enabled device. If this doesn't work for you, feel free to post here or contact your congressman. (Where applicable) If this helps anyone please be sure to drop in and say hi.
There is some real development going on about this subject over on the pixel perfect thread. If you are just looking for a quick fix then what I posted above is still relevant but you might want to keep an eye out for a *real* fix as I doubt it will take them long once they sink their teeth into it.
I believe they already figured out that you can patch the header on the problem files to correct the payload size which should work also. If you are not so technically inclined then the method posted here still works flawlessly for me and should for you as well.
I've added a picture that might help if the directions above were confusing at all, so it might help clear it up. You can find the link to the Pixel Perfect thread right above this post.
Cheers,
Eidolen
Hi all, i am trying to work on a theme for the Droid X. Can anyone tell me why some of the images open in photoshop incorrectly and more to the point how to fix them?
I cant post a link apparently to the image or a http link since i'm new but
You can view the image here. http:/ / dl.dropbox.com/u/6769503/8bit.jpg
Is there a setting or something I can change in PS to open these correctly?
Thanks for your time.
KraYzeE
krayzee said:
Hi all, i am trying to work on a theme for the Droid X. Can anyone tell me why some of the images open in photoshop incorrectly and more to the point how to fix them?
I cant post a link apparently to the image or a http link since i'm new but
You can view the image here. http:/ / dl.dropbox.com/u/6769503/8bit.jpg
Is there a setting or something I can change in PS to open these correctly?
Thanks for your time.
KraYzeE
Click to expand...
Click to collapse
What is the original file extension? .png?
I had this same problem with some .png files wich had transparency in windows image viewer, but not in photoshop.
My solution was to open it in Paint.net and save it, rewriting the original image. Please be sure to set the transparency correct whilst saving in paint.net.
Download Paint.net
Thanks for the reply, yes it was a PNG, ill try paint.net but i would really like to use Photoshop. I cant understand how it can mess up the transparency and anti alias like that.
Update: Paint.net does indeed open the file correctly... so while i do now have a solution. I would still like to find out why Photoshop (both CS4 & CS5) open it incorrectly ?
Well technically 8 bit pngs are indexed images with a varying amount of colored pixels and then varying amount of transparent and semi transparent pixels so some programs might not like this. I would recommend gimp over ps as its similar but doesn't have this issue.
Sent from my HERO200 using XDA App
that image actually seems correct, can you post an image of the alpha channel? then we will know if photoshop is not reading the file correctly
As one poster said, it's because the images is indexed. If you do Image > Mode > RGB, it will un-index it. I must warn you though, PS is HORRIBLE with indexed images. Use GIMP/Paint.NET to un-index it to save yourself a headache
JAguirre1231 said:
As one poster said, it's because the images is indexed. If you do Image > Mode > RGB, it will un-index it. I must warn you though, PS is HORRIBLE with indexed images. Use GIMP/Paint.NET to un-index it to save yourself a headache
Click to expand...
Click to collapse
Ahh but then you lose the 8 bit optimization, even running optpng will not put it back to index png cause it will ossy optimize it. So just use gimp.
Thanks for the replys guys.
Here is an example image.
http:/ / dl.dropbox.com/u/6769503/btn_circle_pressed.png
If you open it in PS, you will see what i mean, changing it to RGB does not change the image. I can open it correctly it Fireworks, then save it without making any changes, and then i am able to open it in Photoshop correctly.
This will do for now in case anyone else runs into this issue. The file size isn't too much bigger this way, so it will work for now.
Thanks again to all that helped.
http://dl.dropbox.com/u/1631008/btn_circle_pressed_fixed.png
Here's the image fixed, it was indexed... all I did was open it up with osx Preview and save it again. Or you can try this gimp they all talk about but I think it's overkill to switch to another program just because 1 or 2 images are weird, especially after you paid for your copy of Photoshop.
DBBGBA said:
http://dl.dropbox.com/u/1631008/btn_circle_pressed_fixed.png
Here's the image fixed, it was indexed... all I did was open it up with osx Preview and save it again. Or you can try this gimp they all talk about but I think it's overkill to switch to another program just because 1 or 2 images are weird, especially after you paid for your copy of Photoshop.
Click to expand...
Click to collapse
Thanks for your help. I don't have OSX and i absolutely cannot get used to Gimp. but opening it in adobe fireworks and saving it again right away does the trick, so although it's a pain, its simple to do.
If anyone ever figures out a way to directly open these types of files in Photoshop i'd be glad to know.
Cheers
KraYzeE
krayzee said:
Thanks for your help. I don't have OSX and i absolutely cannot get used to Gimp. but opening it in adobe fireworks and saving it again right away does the trick, so although it's a pain, its simple to do.
If anyone ever figures out a way to directly open these types of files in Photoshop i'd be glad to know.
Cheers
KraYzeE
Click to expand...
Click to collapse
Yes that works but your removing the indexing. Android uses indexed pngs wherever possible because this saves space and resources, if you changed every file in the android system to rgba your phone would be noticeably slower.
If you change it to rgba and then run optipng on it you'll see it will not index cause it can only lossy optimize, but if you set the mode to index and then optimize it you'll notice then file will be considerably smaller with little or no image quality loss. So in short your removing a vary important optimization feature of the android system.
If your looking for a quick image conversion tool try image magick, this will allow you to write scripts to convert them png24/32 to png8 and back whole folders at a time.
well as we do with video it's always better to work with uncompressed, high res images. Then when everything is done and set in stone we compress and optimize without loosing too much image quality.
If i had to start a theming project I'll probably do the same, convert everything to high res, work on it then compress to a more optimized format.
DBBGBA said:
well as we do with video it's always better to work with uncompressed, high res images. Then when everything is done and set in stone we compress and optimize without loosing too much image quality.
If i had to start a theming project I'll probably do the same, convert everything to high res, work on it then compress to a more optimized format.
Click to expand...
Click to collapse
Yeah for video thats fine, but in theming and specifically for this file gimp will allow you to work on the indexed file and you literally can not tell the difference with the indexed file being atleast 50% smaller. Maybe this would make sense with an image that has alot of quality or is high res but in this instance it a loss of time and added steps when the same could be accomplished with industry standard tools.
Hi, I need help with a boot animation I am making. I followed all the instructions for it and its still not working. I just get a black screen during boot where the animation was supposed to happen.
This is for my Nexus 1 btw running CM 6.1.1. the boot animation is basically a siege tank from Starcraft 2 setting up and then packing up again.
I placed the zip in /system/media
Each png is 180x135.
Can someone please look at the zip and see what I am doing wrong? it would REAAAAAALLY help.
More than likely your missing an empty line at the end of your desc.txt, common problem.
Added extra line , didn't work
I added the extra line at the end of desc.txt and its still the same result. Ugh.... I have uploaded the new revised zip.
One problem that i had run into is that i was not zipping them in the least compressed format. make sure that you use fast(minimal) compression.
Compression
Yeah, I tried it both ways with WinRar and 7-Zip and made sure it was set to "Store" as the minimal to no compression option.
Here is my suggestion. This is the desc.txt file i use for all mine and it works fine. Change the resolution in the file and try using that one.
Desc
heres the bootanimation.zip with a changed desc.txt file
YES!!!!!!!!!! ^.^
ianreecej said:
Here is my suggestion. This is the desc.txt file i use for all mine and it works fine. Change the resolution in the file and try using that one.
Click to expand...
Click to collapse
OMG Thank You!!!! It works perfectly now. I don't know what happened before. Now I am going to try to mess with the resolutions to see if I can get everything bigger and cleaner.
Do you by chance know if there is a limit to the size of the boot animation? I made it 8mb because I wanted to keep it lean and fast. If its around 25 mb, will that affect performance?
demoneyes905 said:
OMG Thank You!!!! It works perfectly now. I don't know what happened before. Now I am going to try to mess with the resolutions to see if I can get everything bigger and cleaner.
Do you by chance know if there is a limit to the size of the boot animation? I made it 8mb because I wanted to keep it lean and fast. If its around 25 mb, will that affect performance?
Click to expand...
Click to collapse
No Problem. The limit is really the space on your internal memory as far as i know. If you can fit it on there it should be fine. I know for myself with a droid incredible i can go to about 20 megabytes but that is only again due to my limited internal memory. If you were to move some apps to the sd card etc you can probably free more space.
Drop me a PM if you have questions or need a hand anytime.
Just had a look at your desc.txt and the problem was that all the info was on one line instead of seperate lines for each string of info
-RES +FPS
-NUMBER OF PLAYS + NAME OF FILE ( EACH FILE NEEDS ITS OWN LINE AND PLAY COMMAND)
-EMPTY LINE
Hope this helps you shed some light where you had your hiccup.
Also I found its the fps and image size that affects the animation.
If you have a high quality animation (KB/MB not res size) and a high fps it will struggle to render the images and result in sluggish playback. Try optimizing your images to squeeze that little bit extra out.
dully79 said:
Just had a look at your desc.txt and the problem was that all the info was on one line instead of seperate lines for each string of info
-RES +FPS
-NUMBER OF PLAYS + NAME OF FILE ( EACH FILE NEEDS ITS OWN LINE AND PLAY COMMAND)
-EMPTY LINE
Hope this helps you shed some light where you had your hiccup.
Also I found its the fps and image size that affects the animation.
If you have a high quality animation (KB/MB not res size) and a high fps it will struggle to render the images and result in sluggish playback. Try optimizing your images to squeeze that little bit extra out.
Click to expand...
Click to collapse
Thanks bro for your advice. I had the same problem.
GOAL: Set my own picture that appears when connect it to PC.
I delete default pictures in
Code:
./system/media/screensaver/authors/
I copy to this folder my own images. Change permissions. But if I connect nook to computer I get black screen. Somebody do that?
(main screensaver work good)
That screensaver system on the Nook is overly complicated and poorly implemented.
In many cases where it screws up it falls back on a fallback image.
The very specific fallback is the Brontë sisters.
The more general fallback is the /system/media/screensavers/authors folder.
If you want to keep your life simple, just delete all the contents of that folder and
put in a copy of your own screensaver in there (named anything).
I delete all content of this folder.
I only have blank /authors/ folder
I copy my own pictures. (same I have in media/screensaver)
Still have only black screen, when connect it to PC.
Sorry, I'm confused. Do you mean the popup that says "USB Mode"?
That only covers the center of the screen, the rest should be whatever was there already.
That image is /res/drawable-mdpi/ic_dialog_usb.png in framework-res.apk
no no, i mean the whole screen background. -the screensaver activated few minutes after i connect nook to PC.
Default it show the writers photo.
After I delete it from ./system/media/screensaver/authors/ it show only black screen.
Oh, screensave while USB mounted on a PC?
What exactly do you have in /system/media/screensavers/authors/
Are you sure that the images are good?
Just put one PNG in that directory and make sure that it's not screwed up.
There is also the screensave directories on /media and on /sdcard/My Files
The .PNG is the problem, i think.
In normal screensaver folder /media/screensaver/ i have .JPEG and work it.
Either should work.
I use only PNGs.
So, I use .PNG,.GIF images, but don't work. - I got black screen.
Images have correct dimension. I don't know where is problem.
I have no idea what is going on here.
All screensavers must have their own named directory.
Delete all that junk and put one PNG in
/system/media/screensaver/authors/whatever.png
This should be the only file in this directory.
Notice /system/media/screensaver vs. /media/screensavers
Go into settings and make sure that you have authors selected as your screensaver.
Sorry nothing work.
Code:
For full understanding
1. Connect NST to PC
2. Wait until it show USB conected
3. Lock screen by back button
4. That picture I mean
I don't understand at all what you mean.
If you take a Nook, plug it into a PC a popup appears, "USB Mode".
While that popup is up, no button, even the "n" button, has any effect.
If you are using Button Saviour or something to go back, that's another matter.
Then you are completely screwing up the internal state of the Nook.
Why would you want to do a "back" operation while the Nook is mounted on a PC?
Press the bottom button, not the "n".
Than you see the different screensaver. (default).
The button only lock screen imidiatly. -after period time it auto lock
Do you mean the power button on the back of the Nook?
Yes
Change the permission of the image and make it "rw-r--r--". I got mine to work after I did that.
dxcore35 said:
So, I use .PNG,.GIF images, but don't work. - I got black screen.
Images have correct dimension. I don't know where is problem.
Click to expand...
Click to collapse
For what it's worth (I know, this thread is so old), it was possible to change the default Bronte image screensaver by just putting my preferred image in the ./system/media/screensaver folder as the "default.png" file, after I renamed the original. No need to make a new folder, or delete anything from the authors folder, just swap out the existing default.png in ./system/media/screensaver with the image file of your choice (within the proper size/format ratios). In Settings, my screensaver is set to use ./media/screensaver/dontpanic/dontpanic.jpg. The dontpanic.png file was just converted from the dontpanic.jpg file into dontpanic.png and renamed default.png and dropped into ./system/media/screensaver folder.
Kromz said:
For what it's worth (I know, this thread is so old), it was possible to change the default Bronte image screensaver by just putting my preferred image in the ./system/media/screensaver folder as the "default.png" file, after I renamed the original. No need to make a new folder, or delete anything from the authors folder, just swap out the existing default.png in ./system/media/screensaver with the image file of your choice (within the proper size/format ratios). In Settings, my screensaver is set to use ./media/screensaver/dontpanic/dontpanic.jpg. The dontpanic.png file was just converted from the dontpanic.jpg file into dontpanic.png and renamed default.png and dropped into ./system/media/screensaver folder.
Click to expand...
Click to collapse
I did the same thing (with the same pic, LOL). For good measure, I also swapped out bronte from the Authors folder, and set my screensavers to Authors. That was actually my main reason for keeping my Nook rooted -- I needed my scrensaver!
Renate NST said:
Sorry, I'm confused. Do you mean the popup that says "USB Mode"?
That only covers the center of the screen, the rest should be whatever was there already.
That image is /res/drawable-mdpi/ic_dialog_usb.png in framework-res.apk
Click to expand...
Click to collapse
This is a really old thread but I just found the answer to a question I posted recently in the line quoted directly above! But......where is the "res" directory?? I'm using Root Browser and don't see it at all.
(I can also confirm that changing the permissions of the "default.png" [or a renamed "Bronte_Sisters.png"] as described earlier in this thread works like a charm. Sure looks better than that black screen!)
.apk files are actually zip files.
/res is a directory inside the .apk file.
To change normal (not foo.9.png) images you just need a zipper.
framework-res.apk has all the little icons and stuff.
Screensavers and power down screens are elsewhere.
Hi All,
I had a previous post entitled "Extracting Both Images from P9 Dual Camera": http://forum.xda-developers.com/p9/help/extracting-images-p9-dual-camera-t3465877. The help I received was excellent and so I thought I'd expand on the question.
I am successfully able to produce a "Bokeh" image from the P9, which would seem to indicate that this image does have depth coordinates embedded in it at least at one point in time. Does anyone know how to extract these depth coordinates from the image in a usable form, such as a matrix? I know one user (ScareIT) suggested Huawei may use steganography to embed the depth coordinates, but after using iSteg (a Mac steganography platform) it does not appear that the image has any hidden coordinates once it is transferred from the mobile device to the desktop.
As always, any help would be highly appreciated.
Best,
Josh
As I wrote on the other thread, the depth information is not hidden anywhere, it's just appended to the end of the file, after all valid JPEG data chunks. The JPEG image actually contains two; one is the processed image with the "bokeh" effect, the other is the original (colour) image that is used to re-apply the "bokeh" effect when editing from the Gallery app. If you take an app like JPEGSnoop and walk through the valid JPEG data chunks, you'll notice that the file is actually larger than what JPEGSnoop shows you. Look at the file in a Hex editor at that offset, and you'll see that the depth information is stored with reduced resolution and 8 bits per pixel, but without any compression whatsoever. This part of the file also contains additional information, such as the selected "aperture", the point of focus, which effect (if any) is applied to the out-of-focus areas, and so on. It should be fairly easy to write an application that can extract this additional information, though it's probably not very useful.