So one of the best apps on Windows Mobile, Griff, is about to die. The developer doesn't want to continue with it. I suggested that he make it open source and let the community take over, rather than let it die. He told me to post an inquiry here and see if there was any interest from the community.
Do any of you developers want to take over? Some more info on Griff:
http://www.planetgriff.com/galleria.php
http://www.planetgriff.com/index.php
The thread where the developer asks me to post here to possibly find someone to take over an open source project:
http://www.planetgriff.com/forum/viewtopic.php?p=1528
For those who don't know, this is the best mobile music making/sequencing app on the market. It has won plenty opf awards. It's virtually unchanged since 2000 (except for adding support for additional resolutions) and still today is better than anything on the iPhone.
I'm hoping there is someone out there who will take over this project and make it continue to be the best app out there as we move onto capacitive screen devices and devices that don't have a d-pad.
If you know of a better place to post this, please post it there...
Hmm Im not really into music making on my phone but It looks like a good piece of software
Im not a developer but I CAN do this
~~~~~BUMP~~~~~~
(lol hope it helps)
Hrm... very very interesting indeed! This would blend my personal life (writing music), professional life (development) and my hobbies (big focus on PDA's and WinMo for the last 4+ years) very well.
I'd be interested in joining a group to do this - I couldn't take it over alone (there just isn't enough time).
What language / libraries are used?
I was a C/C++ programmer at one time. Today I'm mainly enterprise Java with a smattering of other stuff. I've also designed quite a bit as well (project plans, UML, ROI, yada yada yada corporate stuff).
I run our corporate builds and manage developer assignments / team coordination - so out of the box I can pledge to help with source code management and developer support / project coordination. These are easy for me as I do 'em all day every day. Besides active development, as well
I'd like to see a few people express interest and I think I'd be willing to jump in with both feet here - especially if it migrated to a freeware kind of system.
~Eric
Oh please someone take this over and make it COOL. It has potential but the UI is so unintuitive. I been doing pro audio for years and years and years and I had to drop the idea of killing time with this app.
B-to-the-IZUMP
Griff is easily one of the best applications for music production on windows mobile and indeed any mobile platform.
Im not a dev but i write music... i would be happy to get involved with this project somehow.
i do have some experience with programming but my code would probably be buggy as hell
I am personally very interested in this. only demoed the thing but found it really, really brilliant.
I can't promise I will have much free time for it, but I will be more than happy to give all the support I can.
I can do sourceforge, github, C/C++ also for Windows Mobile, C# for what matters. I can also do a lot of other things that probably don't apply in this context
cheers,
Aldo
bloody hell.. I didnt even know such an app existed.. thanks for sharing.. now who is going to take it over.
devices that don't have a d-pad.
Click to expand...
Click to collapse
you mean 500+$ phones.
Edit: Just excited to see offers of contribution
You might be late on your ESP payment, looks like service is down and giving you erroneous insight.
Click to expand...
Click to collapse
fixed now, sry.
*bow* thank you, I'm still optomistic that a project like this can come together and resurrect a great piece of paid software into a community-driven piece of open source and freeware.
~Eric
And I didnt heard of this software before now?
Greetings and what a piece of software.
I'm a producer myself and have been looking for a software as this, looks awsome.
I'm not a developer but hoping that someone here will take over this fantastic project.
Haven't used Griff in a few years, but I'd would LOVE LOVE LOVE to see this project brought current.
Wow
This looks like something that could blend so well into an HD2.....and give Intua Beat Maker (iPhone), a very good run for the money.
I looks like it just needs a home start and a drum pad section, and it matches the best iPhone has to offer.
I hope someone takes this and runs with it.
please make it happend!
Greywolf_Ghost said:
Wow
This looks like something that could blend so well into an HD2.....and give Intua Beat Maker (iPhone), a very good run for the money.
I looks like it just needs a home start and a drum pad section, and it matches the best iPhone has to offer.
I hope someone takes this and runs with it.
Click to expand...
Click to collapse
that would be nice
So here's what I know so far - Griff is primarily a single developer project with ~ 300 cpp/.h files based on the MFC framework. There's a couple of people who write plugins for it.
So, I'm in if Daniel (the developer / code owner) decides to go open-source with the project. Looks like we have several SMEs and testers ready to go - anyone interested in contributing with the coding? I can go it alone, but life has its time constraints
~Eric
eknutson said:
So here's what I know so far - Griff is primarily a single developer project with ~ 300 cpp/.h files based on the MFC framework. There's a couple of people who write plugins for it.
So, I'm in if Daniel (the developer / code owner) decides to go open-source with the project. Looks like we have several SMEs and testers ready to go - anyone interested in contributing with the coding? I can go it alone, but life has its time constraints
~Eric
Click to expand...
Click to collapse
I don't now much about coding, but I do own Visual Studio 2008 (was planning on getting into it) and I would be happy to try. I do make a lot of music on the PC though (using Cubase) so I could definitely contribute some ideas at least.
I would definitely be willing to help with the coding too provided someone can help me out when I get stuck.
awesome SD!
~Eric
Neither I was aware about this application. Thanks for bringing it to my attention.
I play the guitar and the piano myself and occasionally I do some home-recording with Cubase although it is just a hobby. But still, I have a few ideas and knowledge about the music-tools available out there.
Playing around with Cubase is not my only hobby - I am also fond of programming. Unfortunately I hardly know any C++ at all since I am old "Basic"-user and now I am programming (both for desktop and Windows Mobile) in the .Net enviroment with C# and VB.Net.
So I doubt I could help with programming but I could indeed help with beta-testing (since I know the "logic" and way of thinking normally used by a programmer).
Just to summarize, I am ready to give a helping hand.
Hello everyone,
I am a new android user and just had my first foray into the jungle of flashing and ROMS. If you look at my one only other post, you will see that it didnt go well, mostly because of my own doings. I went through several bricks; hard, soft and medium I went through them all. I spent the whole day at work with a bright blue crap back-up phone thinking how I was going to replace my practically new SGS4G.
However when I returned home, I searched through the variety of insightful and extremely helpful threads started by ingenious developers, experienced android users and fellow noobies such as myself and found that this forum is composed of some of the most intuitive and adaptive technological minds who are willing to lend aid to their fellow forum members (such as myself) who are not as adept with their android phones.
I have been having a tough time these past few weeks; I just transferred to a new school in a new country and I have been struggling in several classes. My android phone is probably my only highlight these past few months as it is my first android phone. When it got bricked, it was the cherry on top of my crap pudding that I've been engorging myself on.
But here I sit today, using my phone as though nothing had ever happened. I wish I could thank all of the people whose posts helped guide me through this mess, but the fact of the matter is that it was not the work of an individual that got me through this, but the work of an amazing community whose members look out for one another.
So with all my heart, thank you xda developers, members, and followers for the great service you have provided myself and the multitude of others on this forum.
You'r Welcome!
Go learn some java and develop a customized android system for us. Fix the resource hogging issues and such then I'll love you forever. Doing that would definitely repay xda. xD
Jokes aside, glad you had a nice experience.
Seconded. The level of willingness to help in this community is unrivaled. I went through quite a few trials myself learning to root and everyone here was more than helpful.
Sent from my SPH-D700 using I Tapatalk
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.
I was thinking long long time before I finally came to a conclusion to write this, rather frustrated, post. Believe me, it is not easy to put it together with clear mind and intention to not to offend or be prejudicial.
A major part of XDA is spinning around custom ROMs ... a f*cking MAJOR part..... giving custom ROM developers feeling that it is actually a legitimate place to offer, or more precisely market, their so called "inventions"...
While I am a member of XDA only a short time, I can imagine what spirit was once behind this server. Spirit of sharing knowledge, progress. There are still lot of members, who live up to this spirit, but there is also a lot, who are just "selling" their product for "THANKS" buttons, and of course DONATIONS.
There is nothing wrong with thanks or donations, should they support an effort that leads into more community education and involvement. My concern is heading more in direction of so called ROM gluers.... Guys, who don't actually develop anything at all, just collect work of other people, glue it together and then release it under some bombastic name like: "Project Saturndancers: Timelapse IV".... and the all greedy flash junkies are flashing, in frenzy of having something more on their mobile than they already paid for.
And then comes the bitter morning, the wake-up where some features are not working the way they should, some not at all. And the reply of the "all-mighty" developer ? Read the OP -- I guarantee nothing, you flash on your own risk....
Agree, we all flash on our own risk. But if it is so, then it would be at least fair, if so called "ROM Developers" end up the marketing of their own semi-products, promising "Awesome sound" "Unparalleled performance" "Superior battery life" and other rather qualitative measures.
If such praxis continues, XDA is just changing from a developer server in some sort of whore-house.
ondrejvaroscak said:
While I am a member of XDA only a short time, I can imagine what spirit was once behind this server. Spirit of sharing knowledge, progress.
Click to expand...
Click to collapse
You are absolutely correct. Way back years ago, while Windows Mobile 5 was around on PDAs, XDA started up for this exact purpose. We had many amazing people with intricate knowledge of how the operating system and devices were all put together. They shared their work and knowledge with others and it was a place all about learning.
But many years have passed, times have changed. Every man and his dog has a smartphone nowadays. It's become easy for people to zip up other mods together and release their "own". But as you say, when it comes to providing support or working out issues, they sometimes don't have the knowledge to do this. But in saying this, there are MANY skilled developers who come up with amazing work, and put in countless hours in providing and supporting their work. All for people to modernise or improve their smartphones, and not be charged anything for the service.
But even back in the early days, we had "ROM Kitchens" where anyone could cook up a Windows Mobile ROM with features they wanted, and they then posted their ROMs on XDA. Each was customised to how they wanted.
Nowadays, it's just down to the sheer number of Android users, that we're seeing this explosion of ROMs.
All I can suggest is you only use the ones you are interested in, and simply not use or look at the others. At the end of the day, they are doing no harm. if they are (for example bricking devices), then we will intervene.
the_scotsman said:
You are absolutely correct. Way back years ago, while Windows Mobile 5 was around on PDAs, XDA started up for this exact purpose. We had many amazing people with intricate knowledge of how the operating system and devices were all put together. They shared their work and knowledge with others and it was a place all about learning.
But many years have passed, times have changed. Every man and his dog has a smartphone nowadays. It's become easy for people to zip up other mods together and release their "own". But as you say, when it comes to providing support or working out issues, they sometimes don't have the knowledge to do this. But in saying this, there are MANY skilled developers who come up with amazing work, and put in countless hours in providing and supporting their work. All for people to modernise or improve their smartphones, and not be charged anything for the service.
But even back in the early days, we had "ROM Kitchens" where anyone could cook up a Windows Mobile ROM with features they wanted, and they then posted their ROMs on XDA. Each was customised to how they wanted.
Nowadays, it's just down to the sheer number of Android users, that we're seeing this explosion of ROMs.
All I can suggest is you only use the ones you are interested in, and simply not use or look at the others. At the end of the day, they are doing no harm. if they are (for example bricking devices), then we will intervene.
Click to expand...
Click to collapse
Not to be wrong understood, I don't say that everybody is like this. There are of course great people around here. And of course I agree, it's at the end everybody's decision, with whom to bake the cake