WEBVTT - TechStuff takes a bite out of Ice Cream Sandwich 0:00:00.280 --> 0:00:02.920 Brought to you by the reinvented two thousand twelve Camray. 0:00:03.160 --> 0:00:08.840 It's ready. Are you get in touch with technology with 0:00:09.000 --> 0:00:17.560 tech Stuff from how stuff works dot com. Hello everyone, 0:00:17.600 --> 0:00:20.200 welcome to tech stuff. My name is Chris Poulett, and 0:00:20.239 --> 0:00:22.560 I'm an editor at how stuff works dot com. Sitting 0:00:22.600 --> 0:00:25.959 across me as always his senior writer, Jonathan Strickland, I 0:00:26.160 --> 0:00:29.520 just got parole. I'm just twenty five years old. I'm 0:00:29.520 --> 0:00:35.240 your ice cream man, so you better look out for me. Uh. 0:00:35.360 --> 0:00:37.640 That didn't sound like a scooter crunch to me. No, 0:00:38.400 --> 0:00:42.159 we're gonna talk today about ice cream sandwiches, but not 0:00:42.240 --> 0:00:45.440 the tasty, chilly treat that can give you an ice 0:00:45.479 --> 0:00:48.320 cream headache. Oh no, this can give you a headache 0:00:48.360 --> 0:00:52.160 of a totally different nature. That's just that's just guess 0:00:52.159 --> 0:00:55.200 work by me. I was actually used it yet. Um. 0:00:55.240 --> 0:00:57.600 Now we're talking about the latest build as of the 0:00:57.640 --> 0:01:00.800 recording of this podcast, the latest build of Andrewid's mobile 0:01:01.280 --> 0:01:04.640 or Androids operating system. It is a mobile operating system. Uh, 0:01:04.680 --> 0:01:08.440 it would officially be Android four point Oh yes, ice 0:01:08.480 --> 0:01:11.480 cream sandwich. Yeah. If you are not familiar with the 0:01:11.520 --> 0:01:14.160 Android operating system, this is, of course the smartphone and 0:01:14.200 --> 0:01:18.600 tablet operating system that Google produces. Uh and ever since 0:01:18.840 --> 0:01:21.440 they got out of alpha and beta, they've named their 0:01:21.520 --> 0:01:31.800 various builds after tasty desserts. So we had cupcake, doughnut, Claire, froyo, gingerbread, 0:01:32.200 --> 0:01:39.080 and honeycomb up to now honey Yeah, fantastic. So the 0:01:39.200 --> 0:01:41.720 nice neat thing about ice cream sandwich to me or 0:01:41.800 --> 0:01:44.559 what I think? It's kind of interesting is that? Okay? 0:01:44.600 --> 0:01:48.320 You you remember when Honeycomb debuted, right, and there was 0:01:48.440 --> 0:01:52.280 some excitement, but there was also some grousing because Google 0:01:52.360 --> 0:01:55.320 already has a bit of a black eye about all 0:01:55.360 --> 0:01:59.480 the different versions of Android that are out on the market, right, yeah, there, Well, 0:01:59.520 --> 0:02:02.360 it depends on what phone that you have, too, because 0:02:02.400 --> 0:02:05.400 some of them, uh is is it easy to find 0:02:05.400 --> 0:02:07.880 a good deal on an Android phone? But you'll find 0:02:07.880 --> 0:02:10.560 out in a lot of cases that you are one 0:02:10.760 --> 0:02:15.919 or more versions of the operating system behind the cutting edge. Um, 0:02:15.919 --> 0:02:18.519 and a lot of people were finding uh, you know, hey, 0:02:18.520 --> 0:02:21.280 I got Android and it turns out that it's not 0:02:21.400 --> 0:02:25.320 as the phone isn't as robust and can't handle as 0:02:25.320 --> 0:02:28.440 advanced in operating system. So people are out there with 0:02:28.560 --> 0:02:31.640 a variety of different kinds of phones UH running a 0:02:31.720 --> 0:02:35.480 variety of different operating versions of the Android operating system. 0:02:35.800 --> 0:02:38.080 So like this, this is one of the things that 0:02:38.120 --> 0:02:42.760 really differentiates Android from iOS and Apple's approach because Apple 0:02:43.040 --> 0:02:47.400 is in charge of of UH creating the hardware and 0:02:47.440 --> 0:02:50.840 the software. So it's a marriage between hardware and software 0:02:50.840 --> 0:02:53.360 where the hardware is going to support the software because 0:02:53.520 --> 0:02:56.040 it was designed to do so from the ground up, 0:02:56.120 --> 0:02:58.240 and vice versa. The software is designed to work on 0:02:58.280 --> 0:03:01.800 that hard to to optimize for that hardware. So Apple 0:03:02.160 --> 0:03:04.120 in a way, you know their system. It means that 0:03:04.160 --> 0:03:06.640 you don't have as much choice. Really, you have the 0:03:06.760 --> 0:03:09.519 latest iPhone that you can purchase, or you can purchase 0:03:09.560 --> 0:03:13.560 an iPhone that's usually a generation or maybe two generations older. 0:03:14.160 --> 0:03:16.640 But but they're all iPhones. You know, it's all gonna 0:03:16.720 --> 0:03:20.160 have the form factor that is common across that generation 0:03:20.200 --> 0:03:22.720 of hardware. You know you're not gonna find any variation 0:03:22.760 --> 0:03:26.400 beyond that. But but it does mean that and you 0:03:26.440 --> 0:03:30.120 know you're less likely to be outpaced by the operating 0:03:30.160 --> 0:03:34.520 system at least significantly. I mean, older versions of the 0:03:34.520 --> 0:03:37.960 iPhone are not able to run the current version of iOS. 0:03:38.440 --> 0:03:43.160 But because contracts come up and usually two years in 0:03:43.320 --> 0:03:46.920 the United States, the think thinking processes. Well, you're not 0:03:46.960 --> 0:03:49.920 gonna be you know, left behind for very long because 0:03:49.920 --> 0:03:51.800 once your contracts up, then you can upgrade to the 0:03:51.880 --> 0:03:54.320 latest hand set and you'll be able to use the 0:03:54.400 --> 0:03:58.880 latest operating system. Google it's different because Google does not 0:03:59.200 --> 0:04:04.120 create right now, it's own hardware. It even though there 0:04:04.200 --> 0:04:08.040 is the the possibility that Google will purchase Motorola Mobility 0:04:08.080 --> 0:04:10.280 and so maybe in the future we will see that happen. 0:04:10.400 --> 0:04:12.520 Right now, that's not the way it works. The way 0:04:12.520 --> 0:04:17.560 it works is that various handset manufacturers across multiple countries 0:04:17.600 --> 0:04:22.680 and carriers are creating devices that run Android. So some 0:04:22.800 --> 0:04:25.679 of those devices can run Android up to a certain point, 0:04:25.680 --> 0:04:28.680 but beyond that they aren't capable of running Android because 0:04:28.760 --> 0:04:32.120 the operating systems resource demands are greater than what the 0:04:32.200 --> 0:04:35.920 hardware can provide. So, for example, some of the earliest 0:04:35.960 --> 0:04:39.240 Android phones that came out had an upper limit of 0:04:39.520 --> 0:04:42.440 Android one point six. They couldn't go beyond that. Now 0:04:42.480 --> 0:04:45.960 we're talking about Android four in this podcast, so you 0:04:46.000 --> 0:04:49.160 can see that you would be left far behind. So 0:04:50.240 --> 0:04:54.000 because multiple manufacturers are making these handsets, they're coming out 0:04:54.040 --> 0:04:56.719 all the time. You know, an iPhone a new iPhone 0:04:56.720 --> 0:05:01.760 comes out in general between twelve and eighteen months as scene. Uh, 0:05:01.800 --> 0:05:04.880 a new Android phone comes out every couple of weeks, right, 0:05:04.920 --> 0:05:07.920 it seems like so well, especially right now as at 0:05:07.960 --> 0:05:10.839 the time we're recording this podcast, we've had some very 0:05:11.000 --> 0:05:15.800 high profile device is released in the last two weeks. Yeah. Yeah, 0:05:16.240 --> 0:05:18.840 So in that case, you could go out purchase your 0:05:19.000 --> 0:05:23.080 brand new Google phone with it's with the highest running 0:05:23.080 --> 0:05:25.240 operating system that you can get at on that phone 0:05:25.240 --> 0:05:27.400 at that time, and then two weeks later you can 0:05:27.440 --> 0:05:29.920 find out that there's a new phone that's just been 0:05:29.960 --> 0:05:33.280 released that even makes the one you just purchased. Look. Uh, 0:05:33.400 --> 0:05:36.480 you know, well it may not look pathetic. That would 0:05:36.480 --> 0:05:39.279 be going too far, but it may Yeah, it may 0:05:39.279 --> 0:05:41.599 not have as it may not be as fully featured 0:05:42.160 --> 0:05:45.480 as the newest phone. So that can be very frustrating. Well, 0:05:45.880 --> 0:05:48.320 Google's have a lot of criticism directed to it because 0:05:49.120 --> 0:05:51.880 directed at it, I guess I should say that because 0:05:51.920 --> 0:05:55.160 it had, you know it, it had created this this 0:05:55.240 --> 0:05:57.719 operating system where there were so many different versions out 0:05:57.720 --> 0:05:59.920 there on the market. Not all of this is Google's fault. 0:06:00.040 --> 0:06:04.479 It that it created something that we call fragmentation, where 0:06:04.520 --> 0:06:07.200 you know, you could have three or four people all 0:06:07.279 --> 0:06:09.719 with Google devices, getting a room together and realize that 0:06:09.880 --> 0:06:12.120 no two of them are running the same version of 0:06:12.160 --> 0:06:14.880 the operating system. And then you get on top of that, 0:06:14.920 --> 0:06:17.680 you've got things like you've got the ability of carriers 0:06:17.720 --> 0:06:21.839 to overlay their own um you user interface on top 0:06:21.920 --> 0:06:25.560 of the Android operating system, and it makes the fragmentation 0:06:25.560 --> 0:06:29.320 even greater. Well, then when Google released Honeycomb, which was 0:06:29.400 --> 0:06:33.560 a tablet operating system, it was designed optimized for tablets, 0:06:33.600 --> 0:06:37.279 not for smartphones, they got even more criticism because now 0:06:37.320 --> 0:06:41.680 you have a smartphone operating system and a tablet operating system, 0:06:41.839 --> 0:06:45.039 both of which Android. Yeah, so now the fragmentation is 0:06:45.080 --> 0:06:49.240 even worse. Well, ice Cream Sandwich moves to help resolve that, 0:06:49.800 --> 0:06:53.080 and that ice Cream Sandwich is bringing together the operating 0:06:53.080 --> 0:06:56.479 system of the tablet and the smartphone. They ideally the 0:06:56.480 --> 0:07:00.640 ice Cream Sandwich operating system build of Android will equally 0:07:00.720 --> 0:07:04.600 well on tablets and smartphones and we will start to 0:07:04.600 --> 0:07:09.279 to have a resolution of this fragmentation. And just in 0:07:09.320 --> 0:07:12.520 case you guys are curious, yeah, there are Android tablets 0:07:12.560 --> 0:07:15.160 that are on the market that actually run older versions 0:07:15.160 --> 0:07:18.440 of the Android operating system, versions older than than Honeycomb. 0:07:19.040 --> 0:07:22.320 So there are some versions out there where uh, they're 0:07:22.360 --> 0:07:25.360 running the smartphone operating system on a tablet and people 0:07:25.560 --> 0:07:27.600 were complaining about it. They said, you know, this really 0:07:28.040 --> 0:07:30.280 doesn't feel like a tablet operating system, and that was 0:07:30.440 --> 0:07:33.440 that's why Honeycomb was, you know, Google's answer to that. So, well, 0:07:33.440 --> 0:07:36.200 this is the optimized one. And now ice Cream Sandwich 0:07:36.200 --> 0:07:39.800 is taking everything they've learned from designing smartphone operating systems 0:07:39.800 --> 0:07:42.680 and tablet operating systems and combining it into a single package. 0:07:43.320 --> 0:07:45.760 So in that way, it's similar to Apple's approach with 0:07:45.800 --> 0:07:51.640 iOS UM and in another comparison to iOS and I 0:07:52.040 --> 0:07:55.520 know that I've well, I've read criticism lately about how 0:07:56.080 --> 0:07:59.480 uh Android stands alone and shouldn't necessarily be compared to iOS. 0:07:59.560 --> 0:08:02.520 But it's it's inevitable that it would draw these comparisons 0:08:02.520 --> 0:08:06.800 because they are the two leading operating systems for smartphones 0:08:06.840 --> 0:08:11.080 and tablets at the moment um. Uh. They they have 0:08:11.160 --> 0:08:14.640 said to that UM ice Cream Sandwich is designed to 0:08:14.680 --> 0:08:19.000 be more user friendly, uh and easier for people who 0:08:19.040 --> 0:08:22.600 are not familiar with smartphone and tablet operating systems to 0:08:22.840 --> 0:08:26.360 get in. UM. You know, one of the the strong 0:08:26.440 --> 0:08:29.320 points of Android is that it is more open and 0:08:29.360 --> 0:08:32.840 it has a lot of advanced features that UM the 0:08:32.880 --> 0:08:37.800 iOS UH doesn't have or didn't have up until iOS five. UM. 0:08:37.840 --> 0:08:41.800 But at the same time, UH, some people have criticized 0:08:41.800 --> 0:08:44.680 it for being so complex that newbies can't jump in 0:08:44.720 --> 0:08:47.640 and use it. UH ice cream sandwich is supposed to 0:08:47.920 --> 0:08:50.840 uh to help with that. UM. One of the features 0:08:50.880 --> 0:08:55.400 I I think that people will really like, especially new people, 0:08:55.440 --> 0:08:58.760 as the face recognition for the unlocking of the phone. Yeah, 0:08:58.760 --> 0:09:01.160 that's kind of cool. The idea here is that, yeah, 0:09:01.240 --> 0:09:03.719 you face unlock, you hold your phone up to your 0:09:03.760 --> 0:09:05.920 face and they're, you know, assuming that your phone has 0:09:05.920 --> 0:09:10.600 a front facing camera, which the the Google Nexus, which 0:09:10.640 --> 0:09:13.480 is the what they're talking there. That was the phone 0:09:13.520 --> 0:09:16.559 they featured, uh ice cream sandwich. When when Google was 0:09:16.600 --> 0:09:18.400 actually talking about ice cream sandwich, that was the phone 0:09:18.400 --> 0:09:20.920 they were using. Was Uh, it's a Samsung phone, as 0:09:20.960 --> 0:09:24.320 I recall, and UM, so they would it has a 0:09:24.360 --> 0:09:26.120 front facing camera. You hold it up to your face 0:09:26.120 --> 0:09:29.319 and assuming that you're in a well lit area where 0:09:29.320 --> 0:09:31.960 the camera can actually detect the contours of your face, 0:09:32.360 --> 0:09:35.559 it will unlock your phone. Once the facial recognition software 0:09:35.720 --> 0:09:39.520 verifies that it's you. Now. This does raise some questions, Yeah, 0:09:39.920 --> 0:09:44.040 like could you fool the facial recognition software by holding 0:09:44.080 --> 0:09:47.440 up a picture of someone? And like the person who 0:09:47.480 --> 0:09:49.520 owns that phone, if you hold up a picture of 0:09:49.559 --> 0:09:52.000 that person to the camera on the phone, would the 0:09:52.040 --> 0:09:55.320 picture be enough to fool the facial recognition software, because 0:09:55.360 --> 0:09:57.880 we have seen that happen in other devices that have 0:09:57.920 --> 0:10:02.280 facial recognition software. I rememb ended specifically of some vending 0:10:02.280 --> 0:10:07.320 machines in Japan that sold cigarettes, and the cigarettes, you know, 0:10:07.880 --> 0:10:10.640 there's an age limit you have to be a certain 0:10:10.679 --> 0:10:14.480 age in order to purchase cigarettes legally and so, but 0:10:14.640 --> 0:10:17.240 they found and they, in order to get around that, 0:10:17.320 --> 0:10:19.160 you know, have so that kids would not just walk 0:10:19.240 --> 0:10:22.439 up to the cigarette machine and buy cigarettes, they included 0:10:22.480 --> 0:10:26.199 a camera that would use some facial recognition software not 0:10:26.320 --> 0:10:30.000 to identify someone, but to determine if that person was 0:10:30.080 --> 0:10:33.600 old enough, just looking for specific kind of features and saying, 0:10:33.640 --> 0:10:36.200 all right, well, this is someone who is clearly has 0:10:36.280 --> 0:10:39.839 some years under their belt, so they can smoke if 0:10:39.880 --> 0:10:45.480 they want to. Don't don't smoke kids anyway. Uh. They 0:10:45.640 --> 0:10:47.640 it was discovered that if you just took a picture 0:10:47.640 --> 0:10:50.240 of an old person held the picture up to the camera. 0:10:50.520 --> 0:10:52.720 It would fool the camera and you could purchase as 0:10:52.720 --> 0:10:57.240 many you know, smokes as you wanted. Kids don't smoke, don't, 0:10:57.679 --> 0:11:01.280 don't do it anyway, So the question is, could the 0:11:01.280 --> 0:11:05.319 facial recognition software on this this Google device be fooled 0:11:05.360 --> 0:11:08.840 by a picture? Also, what what if? What if you? 0:11:09.000 --> 0:11:11.959 What if you have an identical twin? Could the identical 0:11:11.960 --> 0:11:14.199 twin pick up your phone and then unlock it using 0:11:14.320 --> 0:11:17.280 his or her own face? Also, for those of us 0:11:17.320 --> 0:11:20.199 with zz top like facial hair, what happens if we shave? 0:11:20.600 --> 0:11:23.000 Are we no longer able to access our phone? Does 0:11:23.040 --> 0:11:26.160 it say I don't recognize you, go away for six 0:11:26.200 --> 0:11:29.360 months and come back and try again. Well, he's got 0:11:29.440 --> 0:11:33.719 legs and he knows how to use them. Nice. But 0:11:33.720 --> 0:11:36.240 but even even if that does happen, even if it 0:11:36.240 --> 0:11:38.360 gets to a point where let's say it's too dark, 0:11:38.720 --> 0:11:41.400 just a simple scenario, it's too dark for it to work, 0:11:41.640 --> 0:11:43.760 you can still unlock your phone using one of the 0:11:43.760 --> 0:11:47.760 more traditional ways, like the finger swipe type stuff where 0:11:47.760 --> 0:11:49.760 you have to draw a pattern or whatever. You can 0:11:49.800 --> 0:11:52.480 still do that. So it's not like you're going to 0:11:52.559 --> 0:11:55.920 be bricked out of your phone because you ended up, 0:11:56.120 --> 0:12:00.160 you know, changing your face around. I remember my need 0:12:00.240 --> 0:12:03.280 of that Muppet machine that would you were to pull 0:12:03.320 --> 0:12:05.040 you pull the nose off and put on another one. 0:12:05.080 --> 0:12:06.760 You know, you can actually do that. At the Center 0:12:06.760 --> 0:12:10.199 for Puppetry Arts, they have a puppet thing where you 0:12:10.200 --> 0:12:15.040 can change out eyes and noses and mouths. It's awesome. So, 0:12:15.200 --> 0:12:18.080 um yeah, that's a pretty cool feature. The facial recognition. 0:12:18.080 --> 0:12:23.680 I agree. Also, voice recognition technology has become really important 0:12:23.720 --> 0:12:28.720 with Google. Now. It's interesting because this this this leads 0:12:28.760 --> 0:12:33.080 to comparisons with Apple's Siri and Siri. And when I 0:12:33.080 --> 0:12:36.520 say Apple's Sirie, Apple actually purchased the company that created Siri, 0:12:36.679 --> 0:12:40.680 but you know they're incorporating it into iOS um Now. 0:12:40.720 --> 0:12:44.000 Siri is has got a sense of humor and a 0:12:44.040 --> 0:12:48.320 personality sort of. I mean, it's artificial, but it's there. 0:12:48.400 --> 0:12:53.160 It's been programmed in minds, artificial to your your personalities, artificial. 0:12:54.840 --> 0:12:56.600 I felt I thought it was felt a little plastic, 0:12:56.960 --> 0:13:01.439 but uh, they the Google Voice version. There are ways 0:13:01.440 --> 0:13:05.360 where you can operate your phone through using just voice commands, 0:13:06.040 --> 0:13:08.640 just like you could with Siri. But there's not that 0:13:08.760 --> 0:13:12.480 sort of personality that quirky since there and it's not 0:13:12.559 --> 0:13:15.679 as it's not as deeply integrated as it is with 0:13:15.800 --> 0:13:19.120 Apple's product, but you can do a lot of that 0:13:19.160 --> 0:13:21.280 stuff on your Google phone. One of the things I 0:13:21.280 --> 0:13:25.000 thought was kind of cool though, is that with Android 0:13:25.320 --> 0:13:32.080 ice Cream it has real time speech to text UH recognition, 0:13:32.120 --> 0:13:34.079 So if you hold up the phone and you're talking 0:13:34.120 --> 0:13:37.600 into it, you'll see your your words start to appear 0:13:37.679 --> 0:13:41.000 on the screen as you're talking. Now, with older versions 0:13:41.040 --> 0:13:43.720 of Android, what would happen is you would you would 0:13:43.760 --> 0:13:46.200 activate your phone, you turn on the little microphone icon, 0:13:46.360 --> 0:13:48.959 and you would speak into your phone. You would stop speaking, 0:13:49.320 --> 0:13:51.360 you would get a little loading page as it was 0:13:51.400 --> 0:13:54.520 sending the data to the cloud to be analyzed. The 0:13:54.520 --> 0:13:56.760 cloud would send the data back down and then you 0:13:56.800 --> 0:13:59.240 would see the result and it would be whatever you 0:13:59.280 --> 0:14:02.840 said in full. So if you're dictating a fairly long email, 0:14:03.559 --> 0:14:05.760 then you're not going to get a chance to actually 0:14:05.880 --> 0:14:10.280 see what's coming up until you're done. Now, with ice 0:14:10.320 --> 0:14:12.959 Cream Sandwich, what's doing is it's doing real time streaming, 0:14:12.960 --> 0:14:15.280 so it's streaming the data up as it's receiving it, 0:14:15.480 --> 0:14:17.920 hitting the cloud, analyzing it, and sending it back down 0:14:17.920 --> 0:14:20.560 while you're still talking. So you could be dictating a 0:14:20.640 --> 0:14:23.040 very long email and you're gonna start seeing it appear 0:14:23.080 --> 0:14:25.320 after you start talking. Now, that might actually be distracting 0:14:25.360 --> 0:14:28.240 for someone, but it's also a way to say like 0:14:28.280 --> 0:14:32.560 you can review what you're saying immediately. They also highlight 0:14:32.600 --> 0:14:37.240 words or underlining words that uh that have a lot 0:14:37.280 --> 0:14:40.800 of hominems, especially with depending upon the way you speak. 0:14:41.800 --> 0:14:46.080 So if I say a word and uh, and you 0:14:46.120 --> 0:14:48.280 know it's the way I say that word, maybe I 0:14:48.320 --> 0:14:51.480 get a little mush mouth syndrome going or something, but 0:14:51.560 --> 0:14:53.240 I say the word in such a way that sounds 0:14:53.280 --> 0:14:57.680 like another word. If Google is not sure of the 0:14:57.720 --> 0:15:01.320 word you said based upon its contact and your pronunciation, 0:15:01.600 --> 0:15:03.520 you'll get this little underline under it, and if you 0:15:03.560 --> 0:15:06.720 click on the word, it'll give you multiple words to 0:15:06.840 --> 0:15:09.880 choose from that are hominems of whatever it was you said, 0:15:10.600 --> 0:15:13.640 so you can pick the correct word for that particular context. 0:15:14.440 --> 0:15:16.760 So that's kind of cool that, you know, it's not 0:15:16.840 --> 0:15:19.320 just going to put in one word when you said 0:15:19.360 --> 0:15:23.920 something else. Oh, they're they're Jonathan. Yeah there you go. No, No, 0:15:24.040 --> 0:15:28.600 they're Jonathan. There their castle. Uh. So you don't get 0:15:28.600 --> 0:15:32.360 that because you still haven't seen that movie. Um, but Yeah, 0:15:32.440 --> 0:15:34.200 that that that was one of the features I thought 0:15:34.240 --> 0:15:36.360 was really cool. The facial recognition was neat, the voice 0:15:36.360 --> 0:15:39.640 recognitions neat. Uh. There's a lot of other things that 0:15:39.680 --> 0:15:42.720 they've they've included with this update to the operating system. 0:15:42.760 --> 0:15:45.800 The camera now has some added functionality. Yeah, that you 0:15:45.800 --> 0:15:48.160 can you can edit a lot. You have a lot 0:15:48.200 --> 0:15:51.520 more capacity to edit photos, and you can edit stuff 0:15:51.560 --> 0:15:53.760 like the simple things like removing red eye and that 0:15:53.800 --> 0:15:55.920 kind of stuff and cropping photos. But you can also 0:15:56.440 --> 0:15:59.920 do like the hipster layers where you make things look 0:16:00.160 --> 0:16:06.520 posters and stuff and yeah, you're so hip. Apparently Jonathan 0:16:06.560 --> 0:16:09.080 doesn't like that. But you can also do panoramic shots 0:16:09.160 --> 0:16:11.800 where you hold the camera up and you start taking 0:16:11.840 --> 0:16:14.440 a photo and you just you pan to the left 0:16:14.520 --> 0:16:16.960 or to the right, or even I guess across the 0:16:16.960 --> 0:16:21.120 sky if you wanted to, and you you wait until 0:16:21.120 --> 0:16:22.880 you get all the way to where you want to end, 0:16:23.280 --> 0:16:26.880 and then what will happen is that the ice cream 0:16:26.880 --> 0:16:29.200 sandwich has software in it that will allow it to 0:16:29.280 --> 0:16:32.880 stitch together all the various pictures that you've just taken 0:16:32.920 --> 0:16:35.160 by slowly panning. You don't have to do anything the 0:16:35.200 --> 0:16:37.880 camera's doing at all. Uh, and it will stitch it 0:16:37.920 --> 0:16:40.920 together into a panoramic photo. That's pretty cool. Yeah, no, 0:16:40.960 --> 0:16:43.520 it's pretty neat. And also it has the features that 0:16:43.560 --> 0:16:45.480 we've come to expect with a lot of the most 0:16:45.520 --> 0:16:50.200 recent digital cameras and smartphones, like tap to focus. If 0:16:50.200 --> 0:16:54.760 you've gotten multiple, uh, multiple things in a frame, you 0:16:54.760 --> 0:16:57.560 can tap one of them to to tell the camera 0:16:57.720 --> 0:16:59.680 this is what I actually want to take a picture of. 0:16:59.720 --> 0:17:02.960 This Their stuff is kind of background and that's helpful, 0:17:03.040 --> 0:17:05.280 and of course like digital zoom and that kind of stuff. 0:17:05.720 --> 0:17:08.600 Um oh, and apparently the shutter speed is there's like 0:17:08.640 --> 0:17:11.760 no delay or very little lag between when you hit 0:17:11.800 --> 0:17:14.960 the camera and when the photos taken, which is that's 0:17:15.000 --> 0:17:17.280 that's fantastic. Yeah, I have I don't know, have you 0:17:17.320 --> 0:17:20.320 ever used a phone that had a camera where there 0:17:20.400 --> 0:17:23.480 was like a noticeable delay from when you tried to 0:17:23.480 --> 0:17:25.600 take a picture to when the picture was taken. On 0:17:25.680 --> 0:17:27.879 my phone, it takes about a second, and that can 0:17:27.960 --> 0:17:30.760 be that can be enough for it to mess you up, 0:17:32.600 --> 0:17:35.440 but it's enough. It's long enough so that you can 0:17:35.600 --> 0:17:38.960 miss a moment you were trying to capture, or more frequently, 0:17:39.000 --> 0:17:41.119 in my case, i'll take a photo think that the 0:17:41.119 --> 0:17:43.040 photo has been taken, start to move the camera and 0:17:43.040 --> 0:17:45.160 that's when the camera takes And that's so I mean, 0:17:45.240 --> 0:17:48.720 I I'm a victim of my own impatience there. But 0:17:49.280 --> 0:17:52.720 this is uh with ice cream sandwich, they've really optimized 0:17:52.760 --> 0:17:55.840 the camera software so that it'll take that photo much 0:17:55.960 --> 0:17:58.359 more quickly. Now, some of that's also going to depend 0:17:58.400 --> 0:18:01.600 on the hardware. And again we said Android can be 0:18:01.720 --> 0:18:04.920 used across multiple kinds of hardware. So sometimes you'll you'll 0:18:04.920 --> 0:18:09.040 come across an Android handset that might take phenomenal photos, 0:18:09.359 --> 0:18:11.119 and you might come up with another one where the 0:18:11.119 --> 0:18:15.200 photos just look grainy and just there's the low resolution 0:18:15.240 --> 0:18:17.920 where they just don't they just don't look good. And 0:18:17.960 --> 0:18:22.200 some of that is due to the hardware limitations. So 0:18:23.240 --> 0:18:26.640 even though the software supports it, unless the hardware is comparable, 0:18:27.040 --> 0:18:31.119 you could still have a less than ideal experience. Uh 0:18:31.280 --> 0:18:34.760 So some other stuff that they've included an ice cream sandwich, 0:18:35.160 --> 0:18:38.280 there's anything else in particular you want to talk about. 0:18:38.400 --> 0:18:40.600 I was just gonna start hitting some of the other features, 0:18:40.600 --> 0:18:42.679 but if there's one or two that you really like, 0:18:42.800 --> 0:18:48.280 we can focus on those. I see what you did there. Um, 0:18:48.320 --> 0:18:50.040 I think one of the ones that I've seen most 0:18:50.080 --> 0:18:53.879 people interested in is Android Beam. Ah yeah, beam is 0:18:53.920 --> 0:18:57.080 pretty cool. Yeah, Now, I mean immediately when I saw 0:18:57.160 --> 0:19:02.560 that basically, Android Beam gives you the ability to um 0:19:02.800 --> 0:19:07.359 uh give people information from your phone when it's in 0:19:07.440 --> 0:19:10.760 proximity to another one. And the the demo I saw, 0:19:10.800 --> 0:19:14.800 they actually had the two phones touch, yeah, which reminds 0:19:14.840 --> 0:19:18.800 me of Bump. Yeah. It also reminded me of squirting. Yeah, 0:19:19.080 --> 0:19:23.919 the old the old Microsoft Zoom. So so you you 0:19:24.000 --> 0:19:27.479 might say, well that, you know, we've had that for 0:19:27.520 --> 0:19:29.600 a while, you know, that's that's I hear that on 0:19:29.720 --> 0:19:32.520 from both sides when somebody else introduces a feature, Oh, 0:19:32.720 --> 0:19:36.680 you know a sirie. Oh Android, We the Android people 0:19:36.680 --> 0:19:42.480 have had that for years, cut and paste. Yeah, well, 0:19:42.520 --> 0:19:44.920 but an Android Beam. You know, I thought of Bump 0:19:44.960 --> 0:19:46.840 and I thought, well, you know that's not something. In fact, 0:19:46.920 --> 0:19:50.560 Bump is you know, cross platform. Yeah, however, this is 0:19:50.640 --> 0:19:53.120 this is more than just that. Though. You can transfer 0:19:53.280 --> 0:19:57.520 all kinds of files um with Android Beam, and they've 0:19:57.520 --> 0:20:00.399 built it into the API so that developers can create 0:20:00.440 --> 0:20:03.439 applications that take advantage of this. So here here's some 0:20:03.560 --> 0:20:06.600 examples that you could use this this technology. Let's say, 0:20:06.600 --> 0:20:10.720 all right, basic example, I I am listening to a 0:20:10.920 --> 0:20:15.639 song on on a Pandora or something like that, and 0:20:15.680 --> 0:20:18.199 the Pandora's built in the API where I can actually 0:20:18.240 --> 0:20:21.320 share my playlist with someone else or my station with 0:20:21.359 --> 0:20:24.720 someone else. And Chris has the same kind of He 0:20:24.760 --> 0:20:26.960 has a phone that also has this capability. Right now, 0:20:27.040 --> 0:20:29.560 by the way, Google Nexus is the only phone that 0:20:29.600 --> 0:20:31.680 can do this because you have to have near field 0:20:31.680 --> 0:20:35.080 communication yeah built into it, and yeah and yeah. But 0:20:35.160 --> 0:20:38.840 as we see more NFC phones come out from using Android, 0:20:38.880 --> 0:20:41.600 then I'm sure we'll see this used in various handsets, 0:20:41.840 --> 0:20:45.200 and hopefully it will be completely compatible across all handsets, 0:20:45.240 --> 0:20:47.840 so that way I'm not limited to just other people 0:20:47.880 --> 0:20:50.280 who own the same type of phone that I do. Alright, 0:20:50.320 --> 0:20:52.560 so let's say that I've got this song or this 0:20:52.600 --> 0:20:54.760 playlist playing and I want to share it with Chris, 0:20:54.760 --> 0:20:56.600 and I hold it up to his phone, and then 0:20:56.640 --> 0:20:59.960 now his his Pandora has access to the same playlist 0:21:00.080 --> 0:21:04.360 the same station that I have created. That's a simple application. 0:21:04.480 --> 0:21:06.040 Or the one that I saw in the demo was 0:21:06.040 --> 0:21:08.040 that I was, you know, someone's watching a YouTube video, 0:21:08.359 --> 0:21:10.080 they hold their phone up to someone else's phone, and 0:21:10.119 --> 0:21:12.760 now the second phone picks up and and is able 0:21:12.800 --> 0:21:15.880 to watch that YouTube video at the same time. But 0:21:16.000 --> 0:21:18.680 let's let's say let's put it into a game and 0:21:18.800 --> 0:21:21.440 say that you've got a game on your on your 0:21:22.000 --> 0:21:24.640 your phone. That is, let's say it's a role playing game, 0:21:25.119 --> 0:21:27.000 and it's a role playing game where it's essentially a 0:21:27.040 --> 0:21:30.280 massively multiplayer role playing game, but you know, with limited 0:21:30.680 --> 0:21:34.080 interaction with other characters. And then I hold up my 0:21:34.119 --> 0:21:37.679 phone to your phone, and our characters meet and exchange 0:21:38.119 --> 0:21:40.960 stuff so that we each of our characters comes out 0:21:41.200 --> 0:21:45.000 stronger than they were before. And that that's kind of 0:21:45.000 --> 0:21:47.240 a cool little feature that you could you could build 0:21:47.240 --> 0:21:51.560 into a game using this um this this technology. Now 0:21:51.600 --> 0:21:54.199 there's other stuff too. You know, you can transfer notes 0:21:54.320 --> 0:21:57.360 and you can do all sorts of things. It's it's 0:21:57.359 --> 0:22:01.240 a neat way of being able to to manage data 0:22:01.320 --> 0:22:04.639 without having to set up an email or or some 0:22:04.720 --> 0:22:08.280 sort of foul sharing service. Um it makes it really 0:22:08.359 --> 0:22:13.200 quick and simple. And because it's using near field communication, 0:22:13.880 --> 0:22:17.000 it's it's secure in the sense that you don't have 0:22:17.040 --> 0:22:19.840 to worry about you know, you're transferring this across a 0:22:19.960 --> 0:22:24.000 public WiFi hotspot or something. It's you know, unless someone's 0:22:24.200 --> 0:22:27.159