4 ms·
This isn't a hardware capacity issue. The Snapdragon has a 1 GHz CPU very similar to the Cortex A8, an Adreno 200 GPU broadly comparable to an SGX 535, and the
by ajross 15y ago
This isn't a hardware capacity issue. The Snapdragon has a 1 GHz CPU very similar to the Cortex A8, an Adreno 200 GPU broadly comparable to an SGX 535, and the same 512MB of DRAM that all the other phones of its generation have.
Its UMTS radio wouldn't make the cut on today's store shelves, and its camera sucks. But fundamentally this is about planned obsolescence. Google doesn't want to have to pay to maintain the driver stack and QA infrastructure for an old phone.
- edderly 15y agoBoth the Nexus S and Nexus GS use an SGX540 which is fair jump in GPU performance.
- ajross 15y agoA fair jump, but not a huge one. The Adreno 200 is an ES2 part with acceptable performance. I'd be very surprised if there were serious performance problems under ICS, but obviously without having seen the software we can't say.
- bonzoesc 15y ago> This isn't a hardware capacity issue. The Nexus One has 512MB of internal storage. The Nexus Galaxy has 32GB of internal storage. If ICS weighs in at much more than 400MB and has the stellar (read as: "perfunctory") MicroSD support we've come to expect from Android, it'd be about as enjoyable as a fart in a spacesuit on a Nexus One.
- ajross 15y agoThat's a good point. They may not be able to fit the standard image. But if that's the only issue, then expect Cyanogenmod et. al. to have this fixed within weeks. Running real filesystems on the sdcard has been routine in the AOSP community since forever.
- sliverstorm 15y agoI don't know about you guys, but I'm a little blown away that ICS could come in close to 512MB. That sounds like bloat to me.
- rryan 15y agoAre new features bloat? Code doesn't take up zero space, you know.
- bonzoesc 15y agoiOS 5 ZIP-compressed install files are 700MB each, a 500MB Android wouldn't be terribly surprising.
- Xuzz 15y ago(Encrypted and then compressed, however, so it's essentially the same as the uncompressed size.)
- obtino 15y agoJust to clarify what you're saying here: Are you saying that simply because a file is encrypted, that it'd be equivalent to the uncompressed size? There are a fair few modes of encryption (such as CFB, OFB and CTS) out there which ensure that the encrypted data is the same size as the input data. Even if Apple uses a mode which requires padding, the padding should not be so large as to increase the size of the iOS image to the size that you are suggesting.
- tesseract 15y agoEncrypted data is not very compressible. Compression algorithms exploit statistical regularities in the bitstream, whereas the whole point of encrypting something is to get a result with no statistical regularity whatsoever. If you compress first and then encrypt, you can then get smaller file sizes than the input, because the compression algorithm can work on the plaintext.