What books or references are "must haves" for me to get started. I have zero programming experience, but I want to contribute to the android dev community instead of just consuming. I know I could probably find what I need for free online somewhere, but I prefer the structure of a textbook or something similar. Suggestions?
Cyanogen would reccomend starting with app deving and then learning basics about android. Then you'll have enough knowledge to make a decent rom
A drop of Chuck Norris's semen was placed on the IPhone. We now have the Htc Evo.
Application development is a good place to start, except that you have no programming experience. Doesn't mean you can't learn though! developer.android.com is a good place to start, but it kind of assumes you know a little something about software development. As for other resources, I'm not sure what kind of books are out there about Android. However, Android development is essentially in the Java language. You could start with a good general Java programming book, of which there are many.
That said though, there are lots of other ways to contribute. Just learning more about it (not necessarily at a developer level) and offering help to people who need help here on XDA counts as contributing! There are also things you can do around ROM development (which doesn't necessarily involve programming), theming, or any number of other things. It's just a question of where your interests and talents lie.
bkrodgers said:
Application development is a good place to start, except that you have no programming experience. Doesn't mean you can't learn though! developer.android.com is a good place to start, but it kind of assumes you know a little something about software development. As for other resources, I'm not sure what kind of books are out there about Android. However, Android development is essentially in the Java language. You could start with a good general Java programming book, of which there are many.
That said though, there are lots of other ways to contribute. Just learning more about it (not necessarily at a developer level) and offering help to people who need help here on XDA counts as contributing! There are also things you can do around ROM development (which doesn't necessarily involve programming), theming, or any number of other things. It's just a question of where your interests and talents lie.
Click to expand...
Click to collapse
+1 thanks!
Head First Java, 2nd Edition is supposed to be a good place to start. I picked it up a few months ago when I wanted to read up on it myself, but haven't had time to get into it.
Sent from my blah blah blah blah
Hello, I was wondering if someone can steer me the right direction in terms of starting development.
I have no previous programming/development experience whatsoever. I am a somewhat computer nerd but never found the time to get into the developing arena.
Now that I am out of college and have A LOT of time on my hands I want to focus on this because I would absolutely love developing.
I need to know EVERYTHING there is to know about developing for android; for apps and creating roms. What books I need to buy to get everything down? What programs or tutorials? I am very serious about this, someone please help me and tell me all there is to know about accomplishing this goal and where to begin.
Thanks, much appreciated!
Since you mentioned you have no programming experience.. There's three important coding styles you need to master for android.. XML, Java and C/C++. The best way is to write some beginner programs available on the Internet.
In addition to coding, you need to become comfortable with the linux tool set. If you don't already, running a linux distribution will help you learn the environment. I suggest Ubuntu, debian, or gentoo.
I don't mean to make this sound intimidating.. but developing isn't an overnight thing.. a lot of people on these forums learn as they go but have a decent amount of experience with one of these aspects. Many of us are CS or EE/ECE students or grads..
Sam's Teach Yourself Android Development in 24 hours is the book i've been messing with for a couple weeks, very helpful. I got it as a pdf
In the Chef Central -> Android forum of this site, cyanogen has a stickied thread that you need to read.
I was wondering what resources are out there to become a DEV and make my own ROM's. I have googled it a little bit and not really found anything worth while so far. I did run across a good book but its not going to be published for another 2 months. Does anyone know of any tutorials? Books? How to guides?
There are plenty of kitchens right here on xda. And remember when you search on google add on xda to whatever you are searching. I had a bunch of bookmarks for this but never backed them up. Sorry buddy.
Sent from my BAD A$$ EPIC TOUCH 4G
I didn't think about using the term kitchen when searching. I will give that a shot. Thanks.
Sent from my SPH-D710 using Tapatalk
bdpatch said:
I was wondering what resources are out there to become a DEV and make my own ROM's. I have googled it a little bit and not really found anything worth while so far. I did run across a good book but its not going to be published for another 2 months. Does anyone know of any tutorials? Books? How to guides?
Click to expand...
Click to collapse
I would read google's documentation on Android, learn Linux commands, and also learn java. This is a good start. If you use kitchens, you are not dev'ing. After this, reading the cyanogen wiki will teach you some of the less "official" deving methods.
Edit:
Links
First go here and learn all of it. (weeks of hard work and dedication)
http://linuxcommand.org/index.php
Then go to a local library and pick up a recently published book on java programming and learn it. (weeks of hard work)
Then learn all of this (more weeks of hard work)
http://developer.android.com/guide/index.html
Then learn all of this (more weeks of hardwork)
http://www.freeyourandroid.com/index.php
Finally get involved with Cyanogenmod
Becoming a dev is a huge commitment, it is why professional devs are paid so well.
Sent from my SPH-D710 using Tapatalk
kingsway8605 said:
I Becoming a dev is a huge commitment, it is why professional devs are paid so well.
Sent from my SPH-D710 using Tapatalk
Click to expand...
Click to collapse
I'm just curious, how much do devs usually make and who actually pays them?
Sent from my SPH-D710 using Tapatalk
Sn1per 117 said:
I'm just curious, how much do devs usually make and who actually pays them?
Sent from my SPH-D710 using Tapatalk
Click to expand...
Click to collapse
I said professional devs. The hobbyist devs on xda usually are doing it because they enjoy doing it and picked up the skills over the years. But it isn't any easier and that is why the behavior on the forums sometimes annoys them. As far as professional devs who work for a company like Samsung, they make between 50,000-100,000 a year.
As far as independent professional devs, Paper camera has sold over 1,000,000 apks at 2 dollars a pop, do the math.
Sent from my SPH-D710 using Tapatalk
I say make a couple of apps first and learn how Android works. Then move to themeing, then make kernels, then roms
Sent from my Epic™ 4G Touch
kingsway8605 said:
I said professional devs. The hobbyist devs on xda usually are doing it because they enjoy doing it and picked up the skills over the years. But it isn't any easier and that is why the behavior on the forums sometimes annoys them. As far as professional devs who work for a company like Samsung, they make between 50,000-100,000 a year.
As far as independent professional devs, Paper camera has sold over 1,000,000 apks at 2 dollars a pop, do the math.
Sent from my SPH-D710 using Tapatalk
Click to expand...
Click to collapse
Devs dont get 100% of their sales
Sent from my Epic™ 4G Touch
Here's where I learned my skills, this determines on what you're trying to develop. Most roms here, with the exception of source builds don't require much actual programming experience since they are closed source, primarily they have small tweaks like de-odexing, XML mods, etc.
Hands-On | 90% - 90% of my skills have come from hands-on experience and learning as I go along. For example, say I'm writing an app for the very first time. (Don't start with an app unless you've practiced with the platforms language first) As I went along on my first app I learned an incredible amount about android developing by reading developer.android.com and SO as I went along and came across something I wasn't sure about. Ditto kernel development, years ago I started with no knowledge and then bam I'm half a pro . Also, I knew nothing about ASP.NET/MVC/C# about a month ago, now it's kinda fluid to me.
School(Computer Science) | 8% - Yeah, it costs all that money for 8% or less. There can be some unique challenges in a software program, but almost everything you do in school is either so off the wall simple or has no real world application. I also think they spend too much time teaching by the syntax of the language, when really you should group them. Syntax is *mostly* trivial, it's better to group languages. Example: learn the Object Oriented Style (Perl, PHP, C++, Java, C#) which should give you a decent foundation in all those languages. Then learn the Procedure-Oriented Style (C, PHP, Perl, Cobol, BASIC (eww)). Then learn the rising in popularity Functional-Style (F#, SQL (mostly, this ones an exception since you often won't write many SQL scripts save for basic queries), Erlang, Haskell, C#). Notice: I listed some languages in multiple categories as the styles of programming are concepts, and some languages support either concept.
Co-Workers | 2% - Sometimes you learn by asking a co-worker or another developer. It's not how I did it primarily, but I know others who work best and learn best working in a team.
So to recap:
If you're trying to learn software programming itself I suggest starting with common scripting languages which are very easy to learn (HTML, XML (this will help for android), PHP). Then move on to some OOP languages (Java (Android*), C++). Then if you plan on working with kernel source code you should work with C and familiarize yourself with the procedure oriented style. Java is by far the easiest first language to learn OOP because of the wide-range of libraries available (to do almost anything) and the JRE, which gives you a nice garbage collector so you don't have the worry of memory management and freeing objects manually like you do in C/C++, etc.
If you just want to bake a rom with minor adjustments or a closed-source rom, I suggest you learn how to create themes first, as many of those concepts will help in baking a rom. And if you have questions this is a development community last time I checked, although sometimes it doesn't seem like it. So ask questions, ask other developers (I used to get questions ), ask on the board (if you follow the rules), ask on StackOverflow, etc. Don't be a nuisance to other developers though, I had someone that constantly blew up my phone nonstop all hours of the day asking silly silly questions. I don't mind questions, but i'd be spending time with my GF and my phone would explode with 20 questions that I already answered 20 times each
Also, some books may not be bad if you have absolutely no idea about programming whatsoever. But nowadays, you can find anything in a book on the internet. The benefits of a book is they include all their source code (usually) and can motivate you more since they give you projects and challenges. I had one Java book, and it drove me crazy because nothing was standardized. Instead of using the Java HashMap methods, or the Java Stack methods they wrote their own APIs for everything it drove me crazy :O
bbedward said:
Here's where I learned my skills, this determines on what you're trying to develop. Most roms here, with the exception of source builds don't require much actual programming experience since they are closed source, primarily they have small tweaks like de-odexing, XML mods, etc.
Hands-On | 90% - 90% of my skills have come from hands-on experience and learning as I go along. For example, say I'm writing an app for the very first time. (Don't start with an app unless you've practiced with the platforms language first) As I went along on my first app I learned an incredible amount about android developing by reading developer.android.com and SO as I went along and came across something I wasn't sure about. Ditto kernel development, years ago I started with no knowledge and then bam I'm half a pro . Also, I knew nothing about ASP.NET/MVC/C# about a month ago, now it's kinda fluid to me.
School(Computer Science) | 8% - Yeah, it costs all that money for 8% or less. There can be some unique challenges in a software program, but almost everything you do in school is either so off the wall simple or has no real world application. I also think they spend too much time teaching by the syntax of the language, when really you should group them. Syntax is *mostly* trivial, it's better to group languages. Example: learn the Object Oriented Style (Perl, PHP, C++, Java, C#) which should give you a decent foundation in all those languages. Then learn the Procedure-Oriented Style (C, PHP, Perl, Cobol, BASIC (eww)). Then learn the rising in popularity Functional-Style (F#, SQL (mostly, this ones an exception since you often won't write many SQL scripts save for basic queries), Erlang, Haskell, C#). Notice: I listed some languages in multiple categories as the styles of programming are concepts, and some languages support either concept.
Co-Workers | 2% - Sometimes you learn by asking a co-worker or another developer. It's not how I did it primarily, but I know others who work best and learn best working in a team.
So to recap:
If you're trying to learn software programming itself I suggest starting with common scripting languages which are very easy to learn (HTML, XML (this will help for android), PHP). Then move on to some OOP languages (Java (Android*), C++). Then if you plan on working with kernel source code you should work with C and familiarize yourself with the procedure oriented style. Java is by far the easiest first language to learn OOP because of the wide-range of libraries available (to do almost anything) and the JRE, which gives you a nice garbage collector so you don't have the worry of memory management and freeing objects manually like you do in C/C++, etc.
If you just want to bake a rom with minor adjustments or a closed-source rom, I suggest you learn how to create themes first, as many of those concepts will help in baking a rom. And if you have questions this is a development community last time I checked, although sometimes it doesn't seem like it. So ask questions, ask other developers (I used to get questions ), ask on the board (if you follow the rules), ask on StackOverflow, etc. Don't be a nuisance to other developers though, I had someone that constantly blew up my phone nonstop all hours of the day asking silly silly questions. I don't mind questions, but i'd be spending time with my GF and my phone would explode with 20 questions that I already answered 20 times each
Also, some books may not be bad if you have absolutely no idea about programming whatsoever. But nowadays, you can find anything in a book on the internet. The benefits of a book is they include all their source code (usually) and can motivate you more since they give you projects and challenges. I had one Java book, and it drove me crazy because nothing was standardized. Instead of using the Java HashMap methods, or the Java Stack methods they wrote their own APIs for everything it drove me crazy :O
Click to expand...
Click to collapse
My school must have a great compsci program because they focus on good programming styles and not syntax. There is no reason to start with any language besides java if your goal is to develop Android. And while I agree with your learning as you go approach, it would be a mistake and overwhelming imo for someone to jump into Android development without having a basic understanding of Linux, java, and Android. My advice given was for helping op to become an Android dev, not someone who posts roms. They are not always the same thing.
Sent from my SPH-D710 using Tapatalk
bbedward said:
Here's where I learned my skills, this determines on what you're trying to develop. Most roms here, with the exception of source builds don't require much actual programming experience since they are closed source, primarily they have small tweaks like de-odexing, XML mods, etc.
Hands-On | 90% - 90% of my skills have come from hands-on experience and learning as I go along. For example, say I'm writing an app for the very first time. (Don't start with an app unless you've practiced with the platforms language first) As I went along on my first app I learned an incredible amount about android developing by reading developer.android.com and SO as I went along and came across something I wasn't sure about. Ditto kernel development, years ago I started with no knowledge and then bam I'm half a pro . Also, I knew nothing about ASP.NET/MVC/C# about a month ago, now it's kinda fluid to me.
School(Computer Science) | 8% - Yeah, it costs all that money for 8% or less. There can be some unique challenges in a software program, but almost everything you do in school is either so off the wall simple or has no real world application. I also think they spend too much time teaching by the syntax of the language, when really you should group them. Syntax is *mostly* trivial, it's better to group languages. Example: learn the Object Oriented Style (Perl, PHP, C++, Java, C#) which should give you a decent foundation in all those languages. Then learn the Procedure-Oriented Style (C, PHP, Perl, Cobol, BASIC (eww)). Then learn the rising in popularity Functional-Style (F#, SQL (mostly, this ones an exception since you often won't write many SQL scripts save for basic queries), Erlang, Haskell, C#). Notice: I listed some languages in multiple categories as the styles of programming are concepts, and some languages support either concept.
Co-Workers | 2% - Sometimes you learn by asking a co-worker or another developer. It's not how I did it primarily, but I know others who work best and learn best working in a team.
So to recap:
If you're trying to learn software programming itself I suggest starting with common scripting languages which are very easy to learn (HTML, XML (this will help for android), PHP). Then move on to some OOP languages (Java (Android*), C++). Then if you plan on working with kernel source code you should work with C and familiarize yourself with the procedure oriented style. Java is by far the easiest first language to learn OOP because of the wide-range of libraries available (to do almost anything) and the JRE, which gives you a nice garbage collector so you don't have the worry of memory management and freeing objects manually like you do in C/C++, etc.
If you just want to bake a rom with minor adjustments or a closed-source rom, I suggest you learn how to create themes first, as many of those concepts will help in baking a rom. And if you have questions this is a development community last time I checked, although sometimes it doesn't seem like it. So ask questions, ask other developers (I used to get questions ), ask on the board (if you follow the rules), ask on StackOverflow, etc. Don't be a nuisance to other developers though, I had someone that constantly blew up my phone nonstop all hours of the day asking silly silly questions. I don't mind questions, but i'd be spending time with my GF and my phone would explode with 20 questions that I already answered 20 times each
Also, some books may not be bad if you have absolutely no idea about programming whatsoever. But nowadays, you can find anything in a book on the internet. The benefits of a book is they include all their source code (usually) and can motivate you more since they give you projects and challenges. I had one Java book, and it drove me crazy because nothing was standardized. Instead of using the Java HashMap methods, or the Java Stack methods they wrote their own APIs for everything it drove me crazy :O
Click to expand...
Click to collapse
This is great info thank you. I have linux experience and I have made a couple of hello world apps but nothing extensive. It looks like maybe i should start with a little theming or something like that. I know html and can read through XML. I think i will try and find some Java tutorials or books to get me going there. Know of any guides on theme's?
kingsway8605 said:
My school must have a great compsci program because they focus on good programming styles and not syntax. There is no reason to start with any language besides java if your goal is to develop Android. And while I agree with your learning as you go approach, it would be a mistake and overwhelming imo for someone to jump into Android development without having a basic understanding of Linux, java, and Android. My advice given was for helping op to become an Android dev, not someone who posts roms. They are not always the same thing.
Sent from my SPH-D710 using Tapatalk
Click to expand...
Click to collapse
My schools good too I'm not saying its all syntax but its a lot of write your code readable in the professors style. I've learned more in 3 months on the job than 2 years of school. I've learned way more from self teaching tho.
And for app development Linux knowledge isn't really necessary since you can develop android apps on any platform, but Java and OOP styles is necessary knowledge.
Sent from my SPH-D710 using Tapatalk
bdpatch said:
This is great info thank you. I have linux experience and I have made a couple of hello world apps but nothing extensive. It looks like maybe i should start with a little theming or something like that. I know html and can read through XML. I think i will try and find some Java tutorials or books to get me going there. Know of any guides on theme's?
Click to expand...
Click to collapse
What you should start with greatly varies with what you want to develop
Sent from my SPH-D710 using Tapatalk
bdpatch said:
I was wondering what resources are out there to become a DEV and make my own ROM's. I have googled it a little bit and not really found anything worth while so far. I did run across a good book but its not going to be published for another 2 months. Does anyone know of any tutorials? Books? How to guides?
Click to expand...
Click to collapse
Read and follow this information from Cyanogen himself
http://forum.xda-developers.com/showthread.php?t=667298
jerdog said:
Read and follow this information from Cyanogen himself
http://forum.xda-developers.com/showthread.php?t=667298
Click to expand...
Click to collapse
Thank you for the link. I got lots of stuff to start reading through now. I also found this book: http://www.barnesandnoble.com/w/xda...7854?ean=9781119951384&itm=1&usri=android+rom
It should hopefully be a good one as well when its published.
bdpatch said:
Thank you for the link. I got lots of stuff to start reading through now. I also found this book: http://www.barnesandnoble.com/w/xda...7854?ean=9781119951384&itm=1&usri=android+rom
It should hopefully be a good one as well when its published.
Click to expand...
Click to collapse
It will be - I know the guys who've put it together.
The nvidia shield tv, the most powerful android device available, which has root, twrp, and custom roms available, along with tons of support keeps failing to get its own proper forum. The discussion page we currently have is unacceptable. There is tons of people doing development on other sites as well that have no proper place to post it. Please everyone, take a few minutes a day, and request that we get a proper forum added for this device.
http://forum.xda-developers.com/showthread.php?t=1660354
I agree. Thank you for taking the time to remind us about this.
More than anything, this device is missing developer support. It seems that a lot of people didnt want to see this happen. Google for one, with the restrictive OS, how easy it could have been to include an option to switch between regular Android and the mode thats been stripped of or had so many classic Android functions hidden. It blows my mind the hdmi blocks, drm, and other capabilities that get removed for the sole purpose of corporate greed. I know I'm not supposed to rant here, so consider this a rally to Nvidia TV owners to let others know how awesome of a device this could be and so hopefully the user/developer base can grow and get some proper treatment from the cable companies and others who refuse to support powerful devices like this
You guys ha e to remember 2 things
1. We are mainly a mobile device forum.
2. It would not take much for a modded TV to be blocked.
Also a forum will not bring developers. People develop for devices they get and many have no interest in android TV and see them like 3d screens. A fad that will fade away after some time.
zelendel said:
You guys ha e to remember 2 things
1. We are mainly a mobile device forum.
2. It would not take much for a modded TV to be blocked.
Also a forum will not bring developers. People develop for devices they get and many have no interest in android TV and see them like 3d screens. A fad that will fade away after some time.
Click to expand...
Click to collapse
Why do other Android TV devices have a proper forum then? Maybe devs would take the device seriously, if XDA took the device seriously. I would understand that argument if it wasn't proven to be untrue with the various other forums that have been created for other tv boxes.
- Nexus Player (Android TV)
- Amazon Fire TV (Fire OS - Even more limited than Android TV)
- Mad Catz Mojo
- Ouya
Just to name a few...
I'm not trying to start a problem. It just seems like we're presented with a different argument ever other day stating why the device doesn't have or deserve a proper forum. Not too long ago, the argument was the lack of interest. Then it was the lack of development, even though we currently have custom AOSP and CyanogenMod ports, Root, TWRP and Ubuntu.
If you search for the device in the device search, you will find not one, but two separate "places" to create topics for this device. One isn't a forum. It's just a list of threads that use the shield-tv tag. If a thread is created here, it will actually post in the Android Development and Hacking > Miscellaneous Android Development forum.
The other is a sub-forum of Android TV and Stick Computers. It isn't a proper forum and it is also buried. The device isn't listed in devdb, so there's no way to add projects.
There is active interest in the device and there are a ton of users. At the moment we're using nVidia's website/forums, but we'd prefer to use XDA. Why not give in to demand? You could make a lot of XDA users happy.
zelendel said:
You guys ha e to remember 2 things
1. We are mainly a mobile device forum.
2. It would not take much for a modded TV to be blocked.
Also a forum will not bring developers. People develop for devices they get and many have no interest in android TV and see them like 3d screens. A fad that will fade away after some time.
Click to expand...
Click to collapse
The joke is on you and I don't care that my response will get on your nerves. You were better off keeping it hush hush than to fail at manipulative excuses.
zelendel said:
You guys ha e to remember 2 things
1. We are mainly a mobile device forum.
2. It would not take much for a modded TV to be blocked.
Also a forum will not bring developers. People develop for devices they get and many have no interest in android TV and see them like 3d screens. A fad that will fade away after some time.
Click to expand...
Click to collapse
@ 1. So just because the shield is tied to a wallsocket and uses an external screen it is not entitled to a forum? That's a rather peculiar argument....?
@ 2. I don't think you understand the Nvidia Shield Android TV, it is just as moddable as any Android device...
And last but certainly not least you claim people don't have interest while we have proved this by the community development for the device so far. BTW the interest in the device might be bigger than you think. For instance on the Nvidia forums there are already over 10k comments in the shield tv subsection, this is over 25% of the shield portable's total comments and over 20% of the shield tablet's total comment. Considering the device is only available for a short period and is only available in the US, this means public interest is huge!
So in other words, please come up with better arguments or just add one device forum, how much harm can it possibly do?
That would be a game changer for this thing.... ... I'm in!!!!!!!!!!
Look guys. I'm just offering up ideas. The mods don't add the forums the admins do. You have asked in to proper forum and now it's up to them. They may or may not decide to give it a forum. Why or why not is their choice.
As for your statements. Just ask Linus what he thinks of Nvidia? Not the best to work with on an open source project.
The 10k posts? While might seem alot is not a whole lot on a site that sees that many every few hours.
If interest is deemed bug enough then it will get a forum. If not then it won't. No point in making thread after thread about it really.
didn't know..
XDA is some kind of mafia... I thought it's free and open, really sad.
They have proper forums for the Moto 360! A watch forum??? Give me a break. Android wear is even more restrictive then Android TV!
I think XDA admins have a bug up there arse about Nvidia. Pure and simple. If it was AMD they would already have everything.
Stop defending them.
I too, would like to register my interest for such a forum.
While I am a newcomer, I would like to register my support for this movement too. It would be nice to have singular outlet to use.
zizika said:
XDA is some kind of mafia... I thought it's free and open, really sad.
Click to expand...
Click to collapse
XDA is a privately owned, membership based site.... Just to correct you.
And the Admin here decide things like forum sections.
Perhaps they'll add a full section, perhaps not. Getting angry about it isn't going to help at all.
As said, if developers are actually holding back work because of a lack of a full forum, they are only making you guys suffer. Seems a little backwards.
Let's remain respectful everyone, please.
Darth
Forum Moderator
The Nexus Q has it's own forum here and NOT the Nvidia Shield Console? That's just stupid.
zelendel said:
Look guys. I'm just offering up ideas. The mods don't add the forums the admins do. You have asked in to proper forum and now it's up to them. They may or may not decide to give it a forum. Why or why not is their choice.
As for your statements. Just ask Linus what he thinks of Nvidia? Not the best to work with on an open source project.
The 10k posts? While might seem alot is not a whole lot on a site that sees that many every few hours.
If interest is deemed bug enough then it will get a forum. If not then it won't. No point in making thread after thread about it really.
Click to expand...
Click to collapse
I knew somebody was gonna say something like this. Linus Torvalds made that comment about Nvidia years ago while thwy were developing software for proprietary devices. Nvidia has already made it known how thwy feel about their Android devices. "Once you buy it its yours" and all the drivers and images are provided on their developer website so.... I still manage to find what Im looking for anyway so I can really not care very much less but this really seems like a major shrug off for some ridiculous and arbitrary reasons. Im surprised
ElwOOd_CbGp said:
I knew somebody was gonna say something like this. Linus Torvalds made that comment about Nvidia years ago while thwy were developing proprietary processors. Nvidia has already made it known how thwy feel about their Android devices. "Once you buy it its yours". I still manage to find what Im looking for anyway so I can really not care very much less but this really seems like a shrug off for some ridiculous and arbitrary reasons and Im surprised
Click to expand...
Click to collapse
And it still holds true. Due to lack of any proper documentation it is really difficult to develop for these devices. Why do you think only a few even use their stuff and they had to look at other options. Yeah it's users. Do what you will with it. Doesn't mean they will help you along with it.
zelendel said:
And it still holds true. Due to lack of any proper documentation it is really difficult to develop for these devices. Why do you think only a few even use their stuff and they had to look at other options. Yeah it's users. Do what you will with it. Doesn't mean they will help you along with it.
Click to expand...
Click to collapse
All the more reason for hackers to teach them a lesson? How many manufacturers post steps to unlock bootloader on their own website and encourage tinkering with their ROMs making most all source code available? Sounds more like someone has an axe to grind and doesn't care how juvenile it may look. I personally can't wait for more ROMs to get released (including CMs) while making those who want to curb down the development, look foolish. I am half surprised discussion about evil nVidia is not banned already
,
loonix said:
All the more reason for hackers to teach them a lesson? How many manufacturers post steps to unlock bootloader on their own website and encourage tinkering with their ROMs making most all source code available? Sounds more like someone has an axe to grind and doesn't care how juvenile it may look. I personally can't wait for more ROMs to get released (including CMs) while making those who want to curb down the development, look foolish. I am half surprised discussion about evil nVidia is not banned already
,
Click to expand...
Click to collapse
More then you think. Why do you think Qualcomm devices are so popular among modders? Because there is all the proper documentation for working with the chip. Same reason that mediatech and exynos chip are not popular. As for unlocking the bootloader. Heck most oem show you how to do it.
As for CM. I would wish that on my worst enemy.
Now if people want to develop for it then do it. Having a forum or not will not bring more or less development.
I'm amazed that this is even an argument. A forum that generates revenues from page views doesn't want its users to have a place to view one of it's valued devices. Baffling really. Someone definitely is bitter about something. What harm is there in creating a section?