 Okay, this is a very exciting moment for me and actually for the whole signature marketing, we're very glad to be here. We're going to know this guy's signature marketing style, which is simply mind-blowing and amazing. So in my presentation I will give a quick overview of what signature marketing is, what we aim for, how we do it, and this will all be in the various official level and so that everyone can be impressed. We'll have another session tomorrow, I think, with more technical bits that you can enjoy and also feel free to come to me at anytime and see all the questions I'll be able to answer. Okay, so during this presentation I will be talking about some of the things. I'll start with the introduction of signature marketing. And then I'll talk about these parts of signature marketing and opportunity. Signature marketing is all about continuity, giving back what you do and receiving new things that you can actually achieve. So this is a very big thing for us and that's why we like to come to community events. This is simply amazing actually. Then I'll talk a bit about technical-based signature marketing in various official levels so everyone will be able to actually understand what I will be talking about. And then sometimes questions are an extra. In my presentation, questions are a big part of it. I really want you to ask what I really feel like and I'll be glad to answer. So without further ado, let's start. So why this signature marketing? I'm not sure how many of you heard of it. So I usually like to do something where I ask people to put their hands up if they ever heard of Signature Marketing. Oh, wow. Okay. So for those of you who ever heard of it, how many of you could use it? That's actually quite a bit. Okay, thanks. And so for those of you who don't know it, Signature Marketing feels a hole in the Android ecosystem which is an open source after market distribution. So for example, if you see the Linux ecosystem, you have several distributions made by commercial vendors like Ubuntu, Red Hat, etc. And you see several of which are independent like Art Linux, Game 2, etc. And we think of ourselves as one of the first Art Linuxes of Android. And it's a very exciting opportunity to actually support the platform which gives you the opportunity to use more than any devices. We are actually working on any devices every single day. So we provide the latest and basically quick version of Android to pretty much every device out there. And this is something that is really big because many devices are stuck in version 5.2.1.2.1. I'll talk a little bit about this later. And well, it's a great platform for developers to do this like we have lots of users who are really, really into the same amount of light to contribute back, etc., to try to do the same. And I think in the final parallel with Artcon, it's at the same mindset. So it's something that developers do for developers and uses them for performance. Okay. So one question that people ask us all the time is why do you do this? I mean, Android is open source. Why are you actually adding it to it? Well, this is a tweet from Andrew Ruby. He's the vice president of Mobile at Google. And he said that the definition of open is this. And then this is a set of commands that can be used to actually build the Android open source project. The thing is, is it really open? Can you actually build it? And the answer is yes, of course, you can build this. If you have a Nexus S, if you have a Nexus 1. Okay. The question is, what about the others? Most people don't have these devices, so there's a wide market out there. And those people are kind of left out of the open Android experience. So this is one of our biggest reasons. So chances are your devices aren't supported, of course. So we add support for it. And some people use Samsung just because they are like being in control of their devices. You may have heard recently that carriers are introducing statistics applications in their mobile devices. And these statistics applications, basically, they will gather your SMS stats like who you contact, when you have calls, etc. And for me personally, I feel like this is something that I am not one. I am not one of the people to know actually what I do. So I like to be in control of my device with many users who like this. Others simply enjoy the extra features that they provide. We have a very open mindset into what goes into the Samsung web project. So many users like using open VPN, which is not available in Spark Android. Others just like, you can meet them on the browser, etc. So we have a wide set of features and we offer them to the community, just in the form of Samsung. So another question that people ask us all the time is, it's not quite supported. And one thing that I also like to do is actually use the same show of hands. And I'll ask you to also show some brand of devices. And if you want them, put your hand up and keep it up until the end of the slide. So any mind on the ZDE, I mentioned ZDE is not very popular here. Huawei, LG, quite a bit of hands. Sony Ericsson, I mentioned this is pretty big. And HTT, so given this brand you support many more, but actually from this brand you support nearly all the devices that they offer. And some people also ask us, but my device isn't supported. And we say, well, we are welcoming contributors all over the time. And actually, I want to share you amazing statistics which have been going on since the last year on this time in general project. And since last year, we have nearly multiplied by 10 our device count. So we previously supported like eight devices, and now we are operating 80, which is simply amazing, including the dynamic of the work of all the people involved in this project. And that's the introduction. This leads me to part two, and most important, the community. So Sanjima is a giant, giant community. Remember that this is an open source project made by volunteers. So we have 7,000, 5,000 users, these amazing parts. And these are users that actually choose to report their statistic. So we expect that there are much more like we wouldn't like to share their statistics with other people. And maybe we have no idea. Maybe it's double this. Maybe it's ten times this. We have no idea actually, but this number alone impresses us a lot. And we have several volunteers around that make the whole Sanjima experience better. So we have around 40 permanent developers, and these people are not paid to work on Sanjima. What they do is they invest their free time. They give all their efforts to the community. And basically there are several kinds of developers in Sanjima. There are ones who simply maintain devices. So when new versions are out, they will try to make the devices work with them. There are others who actually continue to go for a platform. And there are others who actually fulfill more administrative goals, like coordinated developers and emerging changes in and etc. And we also have amazing people who are liaised into the community. And these people will talk to the users, which is something that developers usually suck at. And everyone knows that. And they do an amazing job of actually talking to the public relations part of companies, of users, posting forums, etc. And there's another thing about Sanjima, which is we have a rich amount of information spread around all of our websites and all around our infrastructure. And one of them is the Wiki. The Sanjima Wiki is simply standing if you are an Android platform developer, because it will give you not only instructions on how to fill Sanjima, but also you can learn a lot from Android from there, about your advice. So imagine that you actually want to change your advice to run Sanjima. This would be the place that you would want to go. In Sanjima, it's usually pretty easy. And I'm pretty sure around here some people will help you. You can come to me too. Wiki shows in very simple steps what you can do to actually change your advice to Sanjima. And please do visit. The site is very simple. It's wiki.Sanjima.com. Additionally, we have these support forums. And these forums will answer all the questions and all the problems that you have. We are one. If you have suggestions, if you just want to chat with someone about the subject, feel free to go back to the forum.Sanjima.com. And lots of activity around Sanjima happens over IRC channels. And we usually work on free note. And this is how you do the channel. So you can feel free to join us over at Sanjima. We would love to have you and to actually explain and answer all your questions. So from a community point of view, we give back a lot to the community. So we provide stable runs for many devices. We have many people coming to us saying, well, thanks. You have extended my device lifetime by a lot because you are providing the latest version while my original manufacturer is providing 2.0 or 2.1. And this is great for us. And also, obviously, the chance to be involved in a project. So pretty much we have users who flash. We have actually deals. And this means that every night we have automated releases. And these are usually pretty stable. However, sometimes we can be broken. That's what they are for us to detect what is happening, what we broke in our recent changes. So if you want to actually check out one of our tools or releases, we use our neural network. It's really easy to get in. It's .cm, so .cm. And we have this huge work track we're going on also. So there are some people I would like to talk to. Because they are really, really important in how Sanjima works. In particular, the work track is maintained by only one guy. And this is a huge amount of work. And he deserves a lot of respect actually. We also receive a lot back from the community. So basically, from every event that we go, we get lots of people coming to us and actually asking how they can put you back. Saying that's how much they like Sanjima. People are really enthusiastic about it and they love it. It really governizes us and gives us motivation to continue. And I understand that the Bangalore user group is really, really huge. So anyone here from the Bangalore user group? Okay, great. So we receive a lot of other party suggestions. So like I said, we just test them every night. And this comes from all the process of actually giving back to the community and receiving this as an answer. And recently we have been getting quite a lot of attention from OEMs. We have been contacted by several of them because Sanjima is now in a point where we have lots of users. So it's kind of significant. And we see lots of applications which have problems with Sanjima trying to actually solve those problems. Even last week, there was this Netflix, two weeks ago, I don't remember, and it fixed the fact that only Sanjima devices. And for us, it's amazing to have a billion dollar company actually looking into community projects and trying to support those users. And the same is happening with companies like Sanjima, Gailch, Electronics, Sanjiris, and many others who are contacting us at the moment. Okay, so Sanjima is a very technical group of people. So we have this whole infrastructure going on, to support all these devices. It's not easy. There are many different plans. I'll talk a bit about our infrastructure and how we actually do what we do and how we solve most of our problems. So most of it's Sanjima, Gailch, everyone can go there and actually check our source. And for our kids, you are welcome to do it. Many people do it for commercial reasons or you guys are just going to change something. Also, we use repo for repository management, the same as Android, and we just get it for code reviews. Now, let me tell you a story about code reviews. Previously, we used Vitalikon, we just accepted patches from everyone. And you can understand how this would work with two or three devices. But if you grew up to 80, I could make a parallel with that and the traffic here in Bangalore. It's a giant mess. So basically what we did was introducing code review and our quality went up a lot. So we ended up breaking the tree much less and actually adding many more people contribute back. It's much easier to manage and contribute. So even if I don't enjoy the later, if you have an open source project, I really recommend actually doing code reviews because it's simply amazing tool. And we have this... I'm not sure how many of you have actually tried to compile and try it. Show of hands, please. So, compiling Android takes quite a bit of time. If you have a really fast machine, you can do it in like 10 minutes, maybe. Most people will do it in like 25. And we do night previews. So we build for every device, we build every single night. And this process takes us all around 24 hours. So we are really hitting the clock time for the night preview. And as you can imagine, building releases manually for 8 devices is completely out of question. This would be very out of prone. We have done it in the past. All of our development was like this before. So we decided to actually automate the whole process. And we have this build cluster which was gently donated to us. We are in the process of setting it up because we had some problems developing the last release. But everything will go as planned, I hope. And we have several servers serving the website, making farms, and several people who maintain them. And this is all of me at the airport. So I think it's technically fantastic. And we have our own mirror network in get.cn. And it's really hard to manage how much traffic Bandit actually gets pulled from our servers after releases and during night release. People maintaining these are actually doing an awesome job. So one of those things that sets us apart in the Android community in regards to open source building is that we offer the same experience for all devices. You can see in this picture we have low resolution devices, medium resolution devices, tablets, and high resolution phones. But this is a result of our efforts to actually share the same tree for all those devices. And this is something that is working in the industry. Because if you go and check the repositories of, for example, TI or Qualcomm, what will happen is actually TI is quite good at it. But if you check Qualcomm, you'll see that it's pretty much every device, every board revision will have a different specific tree. And this is something that I think sets us apart in this specific field. Because we can share all the improvements made by one. Imagine that you want to improve some device, all of the others will get the benefit. And this is something that is amazing for us. So we have a single development which will do all. So we have every single platform, training, going to use support. We support OMAC, OMAC4, OMAC3, Tag2, pretty much all the Qualcomm processes out there. We are always having support for more. And the hybrid support is really hard. So this is something that we'll talk a bit more in the other talk, the technical one, because it's more appropriate. It's a really technical subject. And well, basically, like I said, this trend of using different branches and different trees for each device leads to problems. And you may not know it, but this is also for performance. So when Google drops a new source field like a G-Gerber or something, you get delayed upgrades because we have heard of, sorry, this is not an OEM, is where when some source code for different kinds of G-Gerber drops, it will, at the point, it will be compatible with all the devices. And this is why your devices are excellent to get upgraded. Between other reasons, there are also carrier models, et cetera. And one of the reasons is it's really hard to make any separate trees. So in San Diego mode, we have several main difficulties. And one of our biggest ones is dealing with closed source drivers, okay? So we end up using lots of binary blogs. And this is a kind of interesting topic, actually. And the problem with this is we can actually communicate with G-Gerber because we don't know how it works, okay? So basically this industry is very close traditionally. And only OEMs have access to the source code, okay? And the documentation and how it works. Okay, so usually what we do is pretty much every hardware vendor has an open source development work. And that's what they deliver to OEMs is very close to their development works, okay? So we end up basing our drivers in these reference implementations plus some reverse engineering that we do on our own, okay? And this effort is made possible by a platform that makes called our forum. NTI makes the maximum and then the table, et cetera. And these are actually amazing resources and a lot of them exist without them, okay? And yeah, sometimes, like I said, you need to reverse engineer a lot. And this is not exactly the right time to discuss it, it will take you like an hour. So I'll leave it at that for the next talk and I'll really go to the point of this reverse engineering topic. So another question that people ask us about is the same engine model. Can you contribute back? Yeah, sure. We have things to do for pretty much everyone around. So how many of you are developers? Okay, well, so for you, is there anything that you don't like about Android and that you think that this would change? Like, imagine maybe even a small change like the placement of something or the way something works. And yeah, if you don't like it, you can just delve into our source code and actually change it and contribute back. This is how we get most of our patches. We have lots of users and even core developers who start to contribute out of frustration because they didn't like something and they ended up contributing back and they got focused to actually contribute more because if you ever contribute to an open source project, you know that it's something that you get addicted to very easily because it's a really nice experience to interact with the whole community. And sometimes people come up with amazing ideas. So we have this new Unlock screen for Cyanogen Mod 7.1 and this came in like two weeks before release and because this guy, well, I want this, I will have this then and he came to us and thought we'd guide him through the process and well, now it's in full plan in Cyanogen Mod so this is how we get lots of our changes. So for non-developers out there, we also have several things that need done. Especially in countries such as India, we have really important translations and if you speak a language other than English, you can actually contribute back and the community appreciates your efforts very much. And sometimes people look at Android and they say, okay, I'm a user specialist guy and I can actually see that this makes no sense at all. So this should work in a totally different way. And sometimes people come to us and say, look, here's this idea, do you want to implement this workflow for your application to work better and be considerate and sometimes we improve Android and Chrome. And for people who want to actually contribute, feel free to join us and free know that Cyanogen Mods slash step and, sorry, dash step and we'll be able to guide you through the whole process and actually help you contribute all your changes back in. So how do you do this? It's really easy, okay? So if you saw a tweet from Andy Rubin, our system is basically the same but you may feel bad because it's easy for someone to actually start doing some involvement, okay? So you just need to actually use Ripple to actually start your project then you can sing it, okay? Everything you see here is in our wiki much more recommended. This is a very average version and you will see a complete instruction for your specific device on our wiki. And using Ripple, it's really easy. Just start the branch, using the repository you want to modify then you enter your most awesome mod and you actually do something with it and then you contribute back and then the whole thing starts with the review process and something, recently I started being able to review batches that go into the same general source code and it's something that I've learned a lot with like working with other people you can get a real grasp of how our project management feels and it's a skill that pretty much everyone should have in a corporate setting so sometimes people think open source only allows you to learn technical skills but it doesn't teach you how to interact with others how to actually get skills that are very useful in a corporate setting, okay? So yeah, contributing is back so the community is what makes the end great and I see here an opportunity to actually make all of you guys see those things and actually be part of it so we look like people actually come to us and contribute in time and believe this is okay if you want to do that but we like people to become part of the whole experience to actually enjoy the whole feeling around the community and this is what makes the end great So we will start with part four which is your question What are the process you use to choose what device gets added or if you have a priority order or if you go by popularity how do you decide which device gets added when? Okay, the question was what is our criteria for any devices if it's high popularity or any other method and the answer is no we don't actually have a popularity that is a big thing Like I said, we are an open source project so we have no commercial motivations at all so of course we like having many users and we like to have as many as possible but for a long time in terms of our policy for having devices was we added those that we personally bought and this is still the case for many phones now we have many original manufacturers so again sending us some devices to actually put CMI and this is great because it gives us much a wider area to work on for example when I started working on the HTC Desire it was my main phone at the time so pretty much everyone who tried to call me wouldn't be able to do it because the device was working all the time but at the moment we have several people we're doing batches so if someone comes to us and says that well I have this device ready we don't have a specific commercial plan or a defined schedule to actually add some specific device if someone gets it and starts developing on it they will be able to add it to our tree we don't want to explain right at all we won't be able to come and contribute to our device tree One of your slides showed that my question is has it ever happened that an OEM has taken one of your mod bring it over it and release it for normal customers not for keys the normal release I won't tell names but yes that has happened this has happened in several cases we have seen features that were in say engine mod and they are very very closely implemented in their stock runs and there are others who take some platform support from us like when going from Freud to G.J. Webb and well there are several cases that I could mention but yeah that has happened in the past I expected to continue to happen but that's good I mean some of the companies who take things from us actually continue things back so this is something that we want it's something that's actually happening in open community the license allows for it and it's there for people to take so many just change we are pleased how do you pay your bills as a most efficient model how do you pay your bills how do you pay for what where do you get the money from to kind of run your pay all your developers we don't pay our developers it's not a commercial or it's not even a non-profit organization it's not an organization at all it's just a group of people who got together in the community and actually continue things on their free time so most of us have their jobs and well most people are resting but we are contributing to same demand basically that's how we do it in the beginning somebody told me that I told us you would be coming up with an upgrade analysis so what challenges do you see in making that happen if you want to okay first of all I think everyone took the two months thing to literally it was more of a you see places like Engage who are very sensationalists and as soon as it was posted they were like okay in two months we'll have to find willies that was a tweet that said something like if you read between the lines and you are working on this please leave us alone for now because we are really focused that was basically the end so yeah but to answer your question our biggest challenge at the moment is supporting hardware like between as many people think that the main problem in supporting devices is in the kernel well it's not the kernel is something that is always open source it's very easy for us to actually interact the problem lines in the glue between the framework and the hardware and the kernel and many hardware vendors hold these hardware interface layers and basically it's where most of them implement their secrets so it's understandable that it closes but this is the biggest problem for us because if people follow the API of those hardware instruction layers things will just work but then there is another problem sometimes people don't follow the API and we have to do other things which I'll talk about tomorrow in the other talk but when they do follow them sometimes it happens that glue just drops a new release and this is the case next to the package so I think pretty much every hardware instruction layer except for as a competitive player, lights sensors, pretty much all the others change so for each platform that we support we need to have hardware support for them and you can expect some devices to come up early I believe we have ICS almost fully running with 3D exploration radio technology working mobile data etc with 3D and because it's very close the hardware is very close to the Galaxy Nexus so the hardware support is already there so we can expect the only four line-up devices to be the first line-up to be supported and for the others we already know Qualcomm and NTVA and STIX to provide their hardware interface layers and implementations and when we have that we can expect the other devices while we don't we are trying to do competitive layers but it's an extensive work we have done it for some of them but the others are really hard like graphics and hardware compositing etc guys we're going to make this the last question please follow what I'll pretend outside, we have a break coming up so this is the last question thank you yeah, could you say a word about your association with Samsung can you speak a bit further? we have heard about your association with Samsung how is that going on and what we can expect from the future there's no actual association with Samsung so there is an understanding between us they incentivize us and communicate closely with some of our developers and this was before as most of you know Samsung and STIX on reports for Samsung but this was way before you worked there and the fact that you worked there changes nothing basically so our relationship with Samsung is we have a very close relationship with our developers so we share a lot of experience the same with Sony ARIX and LG and we think that this kind of synergy that we create between OEMs and bugs is really important it helps us a lot back in some way okay so how are you guys different from Samsung firmware sorry how are you guys different from Samsung firmware which is another leading provider of firmware have you heard about Samsung firmware what? Samsung firmware I'm not sure it's another firmware for Samsung I'm not sure about the actual word like Samsung firmware it's a separate firmware for Samsung okay okay I don't know I don't work with Samsung devices so there are some things that are specific to some devices basically my experience in device specific things and vendor specific things lies with the HTC desire and basically the old Sony ARIX we can talk to you we can discuss it in the way and for all the others who can ask questions during this session also come talk to me please we might have to ask okay thank you