Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
The Safari scaling issue is infuriating when looking for wallpapers. You simply can't look for them in your iPad because they're compressed to hell and scaled down to 1024x1024, you have to look for them on a computer, then transfer them to your iPad. I hope they fix this.

False. The story is only about how Safari renders the image, now how it is downloaded. Safari may scale the image down but it will download the full image with the proper res.
 
Which makes it even more ridiculous, since the full-size images are being sent, using more data, but the user gets no benefits.
When it works as it was intended the user does get a benefit: Stabler and more responsive Safari.

It's just that it is done in a very poor manner now on the iPad 3. That will change.

But the scaling itself will not go away. The size limit might be raised for the iPad 3 but there will still be a limit that, once surpassed, triggers the scaling.



Michael
 
When it works as it was intended the user does get a benefit: Stabler and more responsive Safari.

It's just that it is done in a very poor manner now on the iPad 3. That will change.

But the scaling itself will not go away. The size limit might be raised for the iPad 3 but there will still be a limit that, once surpassed, triggers the scaling.



Michael

thats true but its inconsistent. If the rule applies to JPGs they should apply to uncompressed and bigger images like PNGs as well
 
Of course the charging indicator says 100% when it's really in the upper 90s, because people don't want it to (accurately) drop to 99% as soon as they unplug the device and start discharging the battery. It's going to say 100% for some time into discharge.
 
thats true but its inconsistent. If the rule applies to JPGs they should apply to uncompressed and bigger images like PNGs as well

You don't know the reasoning for that, though.

It could be that PNGs took too much to scale. Or perhaps that PNGs can have transparency where JPG cannot. Or maybe even that a PNG can be rendered more easily being lossless (not that it couldn't be the opposite--just showing how Apple likely considered all the options).


Michael
 
Safari is scaling down large images for what should be fairly obvious: it has only 1GB of RAM. An 80 Megapixel image, regardless of whether it's a PNG, GIF or JPEG, decodes to the same size: 240MB (3 bytes per pixel, one each for the red, green, and blue channels).

That's almost a full 1/4 of all of the RAM on the iPad, for one picture! Of course, photo apps that don't downscale the image will necessarily use that much RAM to view it, but this can be allowed since you can generally trust the images already on your device.

Safari has to contend with image bombs. For example, using pixelmator, it is possible to create an 18250 x 18250 white (or other solid colored) image, which compresses down to a 1MB PNG file, yet decodes to nearly 1GB. If mobile safari naively decoded this image at it's full resolution from a malicious website, Safari, and possibly all of iOS would crash in a rather predictable manner, which may be able to be exploited to run arbitrary code.

In other words, down scaling images is a security measure! Now, Safari could be written to downscale the images less extremely on the iPad 3 (probably 5 Megapixel images would be okay), but it has to be done.
 
Last edited:
Wirelessly posted

Expecting a mobile device (even one with 1GB of RAM) to be able to render 10-80 MPixel images is a little nuts. Even if we ignore the download bandwidth, the GPU itself doesn't have the memory or the bus throughput needed to render such a large image to framebuffer.

As for the battery, I think the meter is wildly inaccurate for iOS 5.1 on the iPad 3. Apple will need to calibrate it better in the 5.1.1 update that is soon to follow.

iPhoto can load and edit images up to 18(i think) megapixel image. Autodesk's SketchUp application can draw and export an image up to 100 megapixels.

I can see it scaling down an image in the browser itself, somewhat of a thumbnail. But when viewed in it's native state(such as www.domain.com/images/stupid.jpg) it shouldn't be scaled down. It's more then capable of doing so, so there should be an option of doing so.
 
Way to ignore all the built-in applications and the thousands of applications on the AppStore. But hey, if Safari is really the only application you use, then I understand where you're coming from.

I'm fairly certain the signal strength was because the math wasn't as accurate...people make mistakes you know. In terms of software, we call it a bug.

Of course people make mistakes. Consistently, Apple's mistakes tend to show their products better than they really are ;)
 
Well of course it has a major flaw right out-of-the-box! This has always been apples tactic.
They release a product, everybody rushes to buy it, they make sure that it has a major defect, the jailbreakers jailbreak instantly, Apple finds out how they are doing it, they Patch the exploit and people are left with the choice : fix it or live with a broken product.

Apple does this only so they can keep up the illusion that jailbreaking your device is harmful. They want to make sure that people who jailbreak how a lesser user experience and those who do not.


This is all 100% planned out by Apple. Just look back on every single one product they have ever had, it's a pattern and if you don't see it you must be blind.
 
Most webpages are coded to be 800-1000 pixels wide. In-line images are scaled by the developer to fit within this width restriction. The new iPad screen is 2048 pixels wide. If the ipad user wants content to fill the screen then it must be 2x up-scaled. It is logical for Safari emulate a lower-resolution screen.
Of course if images are down-scaled, then reup-scaled then perhaps there is a problem.
 
Yesterday I ran the iPad off a 12v accessory outlet charger (in an airplane, but a car would be the same). The iPad was active the entire time, set to about half brightness. Although the iPad showed that it was charging, the charge level actually depleted further a couple of percent over that time. The accessory outlet charger might be a lower output than the AC adaptor charger, but it couldn't be much less or the iPad would not have indicated that it was charging.

So this is different.
 
The Safari scaling issue is infuriating when looking for wallpapers. You simply can't look for them in your iPad because they're compressed to hell and scaled down to 1024x1024, you have to look for them on a computer, then transfer them to your iPad. I hope they fix this.


If you just search for 2048x1536 backgrounds. Then find the ones you like and save them to photos. You can't preview them in safari at full res but one you save them you can.

----------

Well of course it has a major flaw right out-of-the-box! This has always been apples tactic.
They release a product, everybody rushes to buy it, they make sure that it has a major defect, the jailbreakers jailbreak instantly, Apple finds out how they are doing it, they Patch the exploit and people are left with the choice : fix it or live with a broken product.

Apple does this only so they can keep up the illusion that jailbreaking your device is harmful. They want to make sure that people who jailbreak how a lesser user experience and those who do not.


This is all 100% planned out by Apple. Just look back on every single one product they have ever had, it's a pattern and if you don't see it you must be blind.

Except that every single iOS device is jailbreakable. They will fix it in a patch then it'll get jail broken again. The reason apple misses these things is (1) they assume everyone will just charge it overnight like there testers. Or (2) they don't have that many testers of the device in real world, they're afraid someone might leave it at a bar or something.
 
If you just search for 2048x1536 backgrounds. Then find the ones you like and save them to photos. You can't preview them in safari at full res but one you save them you can.

Ehm wallpapers should not be 2048x1536, they have to be 2048x2048. Because they need to fit both landscape and portrait.

Also, just save the photo in safari, and watch in fullsize inside the photos app.

Good test here to check wallpapers. They dont display right

http://fiftyfootshadows.net/2012/03/19/retina-ipad/
 
It's one thing to be scaling down images, maybe mobile hardware can't really handle massive massive images that well - but they should, at the very minimum, scale to at least the screen's full resolution. It's insane that the device is downscaling everything to half that, especially when the high resolution is their main selling point.
 
I'd like to report an issue I'm experiencing that I'm surprised no one has reported yet:
On my AT&T iPad 3 in Denver, CO (no LTE service) it will occasionally lose its connection to the network and never reestablish it.

This typically happens while driving somewhere with changing network conditions. The "4G" network indicator next to the "AT&T" network name will disappear, and I have waited up to twenty minutes for it to reestablish before forcing it.

To reestablish, I can reboot the iPad or go into cellular data settings and disable cellular data and re-enable it, then it reconnects until it gets disconnected again.

To prevent this, I can disable the LTE option on cellular data and it doesn't seem to drop the connection anymore.

I'm guessing it's happening because we don't have LTE service here, so when the network conditions get too poor for "4G" service, it tries to establish a new connection (2G, 3G or LTE) and since there's no LTE, it just never stops trying for LTE... Or something. :)

Anyway, I hope they fix this, but since we don't have LTE anyway just disabling it in the control panel works as a fix for now. Though, honestly, I'm going to try to find out if I can exchange my AT&T model for a Verizon model because AT&T's network continues to prove to be slow and unreliable. AT&T has billboards all over the place advertising the nation's fastest 4G network and new LTE service and devices, but Denver is not one of their LTE markets. I feel lied to and misled.
 
Last edited:
Safari is scaling down large images for what should be fairly obvious: it has only 1GB of RAM. An 80 Megapixel image, regardless of whether it's a PNG, GIF or JPEG, decodes to the same size: 240MB (3 bytes per pixel, one each for the red, green, and blue channels).

That's almost a full 1/4 of all of the RAM on the iPad, for one picture! Of course, photo apps that don't downscale the image will necessarily use that much RAM to view it, but this can be allowed since you can generally trust the images already on your device.

Safari has to contend with image bombs. For example, using pixelmator, it is possible to create an 18250 x 18250 white (or other solid colored) image, which compresses down to a 1MB PNG file, yet decodes to nearly 1GB. If mobile safari naively decoded this image at it's full resolution from a malicious website, Safari, and possibly all of iOS would crash in a rather predictable manner, which may be able to be exploited to run arbitrary code.

In other words, down scaling images is a security measure! Now, Safari could be written to downscale the images less extremely on the iPad 3 (probably 5 Megapixel images would be okay), but it has to be done.

^^ This is the real reason.

In any case you still get retina scaling for the text and any vector art. Webpages aren't just made of Ultra-megapixel JPEGs.

Ps - Android's browser also resizes the images, there's really not much option on mobile devices. http://code.google.com/p/android/issues/detail?id=4827 (actually seems to do a worse job at it too)
 
Last edited:
Ah ha...

That makes sense...

I found that my iPad stays at 100% for a lot longer than any other percentage so this is most likely true.

Not a big deal, just a quick software fix.
 
Safari is scaling down large images for what should be fairly obvious: it has only 1GB of RAM. An 80 Megapixel image, regardless of whether it's a PNG, GIF or JPEG, decodes to the same size: 240MB (3 bytes per pixel, one each for the red, green, and blue channels).

That's almost a full 1/4 of all of the RAM on the iPad, for one picture! Of course, photo apps that don't downscale the image will necessarily use that much RAM to view it, but this can be allowed since you can generally trust the images already on your device.

Safari has to contend with image bombs. For example, using pixelmator, it is possible to create an 18250 x 18250 white (or other solid colored) image, which compresses down to a 1MB PNG file, yet decodes to nearly 1GB. If mobile safari naively decoded this image at it's full resolution from a malicious website, Safari, and possibly all of iOS would crash in a rather predictable manner, which may be able to be exploited to run arbitrary code.

In other words, down scaling images is a security measure! Now, Safari could be written to downscale the images less extremely on the iPad 3 (probably 5 Megapixel images would be okay), but it has to be done.

Are you currently seeing anyone? ;)

You explained this very well. It's a feature.

Does the first generation iPad run the same version of Safari, and if so, does the Safari code have switches to let different hardware downscale differently? You've explained how even 1 GB of memory could be overwhelmed maliciously or accidentally by image-heavy and "heavy-image" websites. Imagine how that would affect the iPad 1 with 256 MB memory.

The company I used to work for came out with a new logo, and they wanted all of us to include the logo in our email signature. They sent out an example signature for us to copy and modify with our own details. Unfortunately, the example used a large GIF file that was about 50KB, but displayed the size of an icon. Every email showed a 50 KB attachment with a full-screen resolution picture of the logo. 50KB may not sound like much, but this was a few years back. Our email provider gave each user only 80 MB storage space before warning about the mailbox being almost full, and at 100 MB, you couldn't receive any new messages. It was a nightmare. That little signature icon was Retina before its time.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.