Re: Lets talk about the Iphone 5
Posted: 2012-09-24 02:25am
The screen is a pretty normal size; is it just the apple ears that make it long? Or is this just an assumed problem?
Get your fill of sci-fi, science, and mockery of stupid ideas
http://bbs.stardestroyer.net/
Did iOS 6 help them say yes too?Phantasee wrote: I've been texting a dozen girls trying to get a date for tomorrow night.
Thirding that, if I haven't already. A noticeable increase of responsiveness overall.Stark wrote:All the corners of my phone are burred and scratched from dropping and the screen is fine. What is 'probability'? :v
Like phant, bizarrely the iOS6 update makes my old GS perform much better than 5.
The iPhone 5 has an aluminum back, and the front screen seems to be fit much better than the 4 and 4S glass fronts and backs.Sky Captain wrote:Since several of my friends have broken screens of their iphones from minor drops I have no plans to buy such expensive and fragile device. In my hands it would not last very long given that I recently managed to accidently crack screen of my Samsung B2100 thats supposed to be nearly indestructible.
I'm going to say yes.Borgholio wrote:Did iOS 6 help them say yes too?Phantasee wrote: I've been texting a dozen girls trying to get a date for tomorrow night.
It's taller than the previous models. I had a chance to handle one today, and it seems acceptable to me. The entire screen is still within my thumb's range of motion (not that this was an issue), and it's not too tall to be weird. I think they did it just right: make the phone taller, not wider. That's the problem with cafeteria tray sized Androids. Too damn wide for one hand or my pocket.Stark wrote:The screen is a pretty normal size; is it just the apple ears that make it long? Or is this just an assumed problem?
Water is another enemy. Even just this summer alone my phone accidently got into water, mud and sand multiple times. Luckily my B2100 can take it. I can't even count how many times I have dropped it hard. On one occasion it fell from a scaffolding at construction site from a third floor level and crashed on concrete floor hovever no major damage only few minor scratces. This summer I broke the screen, it happened at metal music festival when I tripped in moshpit, fell backwards with my phone in back pocket and three other guys also tripped and landed on me. Ground was asphalt end there were some gravel on it. Apearently a few hundred kg of pressure was enough to crack the screen hovever I got it cheaply replaced. A smartphone in such an accident likely would be wrecked beyond repair.Phantasee wrote: The iPhone 5 has an aluminum back, and the front screen seems to be fit much better than the 4 and 4S glass fronts and backs.
I've dropped my 3GS a couple dozen times, and once managed to chip the edges of the glass on gravel, but no shattering. I think it was a better design, and I think Apple learned their lesson from the 4 in designing the 5.
There's a drop test video out there that shows a 5 beating an SIII, but I haven't seen it myself.
There's also the anecdotal evidence of my father to consider: he has demolished several phones, running them over, losing them under the lawn while laying sod, dropping them all the time. We got him a 4 in an Otterbox, and the phone has nary a mark on it. If its a serious problem for you, there are solutions.
You need three antennas to do it right now on a CDMA+LTE network, and the iPhone 5 only has two. See AnandTech.Executor32 wrote:CDMA data during a call still isn't possible on any Verizon phone that I know of. LTE data, on the other hand, works just fine during calls, though you obviously have to have LTE coverage at your location. I have direct experience with it on my Galaxy Nexus, but as far as I know every 4G LTE Android phone on Verizon can do it, too. It may be because they all use separate radio chipsets for CDMA and LTE, but I'm not sure.
That's why when I got my GNex, I made it abundantly clear that I would do all the setup myself. The Verizon rep was shocked when I just up and factory reset my old phone while waiting for her to unbox the GNex, she'd assumed I'd want her to manually transfer my contacts to it from my Droid 2 using their computer. She had no fucking clue that Google contacts are stored in the cloud and synced with any Android device I sign in on, reinforcing my opinion that most Verizon reps only learn whatever marketing blips they've been told by Verizon about any particular phone/OS, and don't bother to learn a damn thing more.Dalton wrote:Just picked up my 5 and already irritated, but only because the AT&T rep did the setup for me instead of letting me do it myself. Had to reset the phone to get my iCloud restore going.
Water and blunt trauma are entirely different threats to appliances, and they're not comparable. A well-sealed phone (with no headphone jack because it's some paleolithic thing) can still be totally destroyed by a short drop, which is what everyone is talking about.Sky Captain wrote:Water is another enemy. Even just this summer alone my phone accidently got into water, mud and sand multiple times. Luckily my B2100 can take it. I can't even count how many times I have dropped it hard. On one occasion it fell from a scaffolding at construction site from a third floor level and crashed on concrete floor hovever no major damage only few minor scratces. This summer I broke the screen, it happened at metal music festival when I tripped in moshpit, fell backwards with my phone in back pocket and three other guys also tripped and landed on me. Ground was asphalt end there were some gravel on it. Apearently a few hundred kg of pressure was enough to crack the screen hovever I got it cheaply replaced. A smartphone in such an accident likely would be wrecked beyond repair.
When there will be a smartphone awailable that offers similar or better abuse resistance then I probably will consider an upgrade.
iOS 6 Maps uses Apple's own custom data while iOS 5 and earlier use Google's. In many places the mapping and point-of-interest data is inferior or entirely lacking. Transit routing is gone, too.chitoryu12 wrote:Exactly what's wrong with Maps? I have a Maps app that came with my iPhone 4, which I mostly use for checking satellite imagery as opposed to following directions. Never had a problem with it, though.
There is another story out there about the fact that Apple has heard the feedback and is looking to hire... twenty new guys to match Google Maps.Business Insider wrote: This Fall, Apple will remove the default Google Maps app from its iPhone and iPad operating system, iOS, and replace it with its own in-house designed app.
Apple is going to make its own maps using data from third-parties like TomTom.
After speaking with a pair of Googlers about this, we wonder if Apple may have bitten off more than it can chew.
Read more: http://www.businessinsider.com/to-do-wh ... z27XgRpsoI
One big reason: Google has 1,100 full time employees and 6,000 contractors working on its mapping products. Those 7,000 people do all sorts of granular work.
One source reminds us Google has "street view drivers, people flying planes, people drawing maps, people correcting listings, and people building new products."
Excluding its retail army, Apple only has 13,000 employees in total.
Is it really ready to increase that number by 53%?
Yeah, who cares about music, audiobooks, or just listening to anything interesting you might have recorded, Apple Way is Best Way.Stark wrote:Water and blunt trauma are entirely different threats to appliances, and they're not comparable. A well-sealed phone (with no headphone jack because it's some paleolithic thing) can still be totally destroyed by a short drop, which is what everyone is talking about.
It's like saying tri-wheel bike offers the same quality as car. Oh, well, if you only need to cover 50 metre distance, maybe it does. But, Google needs 1000 employees to cover whole world (slowly). Apple at best with 50 can cover big US cities to same quality, equivalent of 50 meter distance, but hey, it's not like they have a lot of buyers outside of metropolises anyway.Stark wrote:There's no direct relationship between employee numbers and quality. Making Maps actually fucking work doesn't require 5000 guys and if they get 95% quality with a smart team, who cares?