Related
I've been a regular reader of these forums since researching my first Android purchase. Over this time I have seem many new ROM projects born. I would like to argue that many of these projects are so similar that they are pointless.
I'm calling out anyone whoever made a new Hero/HTC-Sense ROM. Seriously. When you saw the 10 other Hero guys out there, what made you think it was better to release your own flavour instead trying to participate in an existing project?
I've taken a look, and as far as I can tell, there should only be 3 non-factory ROM projects:
- CyanogenMod, because of the effort Steve goes to stay 100% legal and teeter on the bleeding edge of Google's source code
- 1 Hero/Sense UI ROM, because we actually only need 1, why don't you guys work together, sheesh
- 1 Blur rip-off ROM, because goodness knows there are going to be people who actually think it's a great idea
Just because Android is based on Linux, doesn't mean we have to make all the same mistakes that has dogged and doomed Linux from the beginning. We don't need to splinter into a billion different distributions, at least not yet. Looking at the feature lists for many of these similar ROMs, the only thing that is different is additional locales or small bug fixes, hardly worth the effort of repackaging. /sigh
*end nerd rage*
i doubt they end. its their project, they build it how they like it and they share it. people do not have to download it. there are many reasons why they release their own, they have more freedom to do what they want. in past rom devs work together then they split up due to differences. working together is all fine and good but this isnt a utopian world haha, people have different opinions on how to move forward with a project.
just because you dont want to download and try different builds dont mean they should stop
jokeyrhyme said:
I've been a regular reader of these forums since researching my first Android purchase. Over this time I have seem many new ROM projects born. I would like to argue that many of these projects are so similar that they are pointless.
I'm calling out anyone whoever made a new Hero/HTC-Sense ROM. Seriously. When you saw the 10 other Hero guys out there, what made you think it was better to release your own flavour instead trying to participate in an existing project?
I've taken a look, and as far as I can tell, there should only be 3 non-factory ROM projects:
- CyanogenMod, because of the effort Steve goes to stay 100% legal and teeter on the bleeding edge of Google's source code
- 1 Hero/Sense UI ROM, because we actually only need 1, why don't you guys work together, sheesh
- 1 Blur rip-off ROM, because goodness knows there are going to be people who actually think it's a great idea
Just because Android is based on Linux, doesn't mean we have to make all the same mistakes that has dogged and doomed Linux from the beginning. We don't need to splinter into a billion different distributions, at least not yet. Looking at the feature lists for many of these similar ROMs, the only thing that is different is additional locales or small bug fixes, hardly worth the effort of repackaging. /sigh
*end nerd rage*
Click to expand...
Click to collapse
I understand how you feel, but isn't that what this site is for? If we only had those three ROM's, then this would be a very boring site. I personally like when people take other ROM's and tweak it to their liking. I don't have a clue on how to cook ROM's, but others do, and they might make one that fits my needs. Just my opinion though....
jokeyrhyme said:
I've been a regular reader of these forums since researching my first Android purchase. Over this time I have seem many new ROM projects born. I would like to argue that many of these projects are so similar that they are pointless.
I'm calling out anyone whoever made a new Hero/HTC-Sense ROM. Seriously. When you saw the 10 other Hero guys out there, what made you think it was better to release your own flavour instead trying to participate in an existing project?
I've taken a look, and as far as I can tell, there should only be 3 non-factory ROM projects:
- CyanogenMod, because of the effort Steve goes to stay 100% legal and teeter on the bleeding edge of Google's source code
- 1 Hero/Sense UI ROM, because we actually only need 1, why don't you guys work together, sheesh
- 1 Blur rip-off ROM, because goodness knows there are going to be people who actually think it's a great idea
Just because Android is based on Linux, doesn't mean we have to make all the same mistakes that has dogged and doomed Linux from the beginning. We don't need to splinter into a billion different distributions, at least not yet. Looking at the feature lists for many of these similar ROMs, the only thing that is different is additional locales or small bug fixes, hardly worth the effort of repackaging. /sigh
*end nerd rage*
Click to expand...
Click to collapse
As a regular reader you should know that there are about 5 different versions of Hero floating around to base off of. There are 2 different versions of blur. There is also pulse, donut, cupcake, and variations on them.
Hero includes: Tattoo (a specialized mix of donut and sense), the sense ui merged with magic, the official release Hero, the non-official beta Hero, and the Sprint Hero. (And if you ever read the threads, we do all work together) There are also multiple opinions on BFS and a2sd, which allows for variations.
Blur has both a Hero and a Cyanogen based version, depending on which way they decided to go to get the supporting files for the main system.
The rest are obvious, and I don't feel like going into that much detail.
If we all followed your beleif, updates would take twice as long and not have nearly as many features. Rather than Drizzy, JustAnotherCrowd, Cyrowski, and myself all waiting for the one day we all have 2 hours to meet on google talk, share files, and build an update... JAC relelases an update, Cyrowski writes a new boot image, I restructure the way a2sd operates, and Drizzy comes along and adds in some new apps he restructured to work on that build. Some people choose to stop somewhere along the path and stick to that ROM, others go all the way down the road. If there were only one update, most Devs would spend half the day just telling people how to disable, remove, or add the feature they integrated.
I just dont see how less is more in this case. If you don't like all the updates, do what I do. I have the ones I actually read followed, and I only ever take a quick glance at the first page of posts before checking those. If I miss anything important, it is only ever by a day. If it's that important, it inevitably gets bumped to the first page long before it becomes so old that I surely learned it somewhere else.
*end informed response*
twistedumbrella said:
*end informed response*
Click to expand...
Click to collapse
Hehe.
Okay, I get that there's a matrix of every possible version of Android against every different sort of UI (ie Hero+Donut, Blur+Cupcake, etc). My shortlist is obviously too short. But it's difficult to pick out, for example, the best Hero ROM. And I can see the same thing happening with Blur as it becomes more and more in vogue.
Watching 3 different Hero versions, you might decide that ROM A almost perfectly suits your needs except for the bug that only got fixed in ROM B. And ROM C has both the features and the bug fix, but has an ugly custom UI somewhere. So then you think to yourself "why don't I just make package D?". The only way you'll know anything for sure is to spend time trying out however many different ROMs knowing very well that there's a chance you'll be forced to compromise. The only differences between many of these ROMs seems to be the Android version, pre-installed applications and custom kernels.
I know I came off fairly irate and impetuous in my original post. But when you can see all these talented developers producing so many different forks and reproducing so much effort, it can be very frustrating for an enthusiastic end user.
twistedumbrella said:
As a regular reader you should know that there are about 5 different versions of Hero floating around to base off of. There are 2 different versions of blur. There is also pulse, donut, cupcake, and variations on them.
Hero includes: Tattoo (a specialized mix of donut and sense), the sense ui merged with magic, the official release Hero, the non-official beta Hero, and the Sprint Hero. (And if you ever read the threads, we do all work together) There are also multiple opinions on BFS and a2sd, which allows for variations.
Blur has both a Hero and a Cyanogen based version, depending on which way they decided to go to get the supporting files for the main system.
The rest are obvious, and I don't feel like going into that much detail.
If we all followed your beleif, updates would take twice as long and not have nearly as many features. Rather than Drizzy, JustAnotherCrowd, Cyrowski, and myself all waiting for the one day we all have 2 hours to meet on google talk, share files, and build an update... JAC relelases an update, Cyrowski writes a new boot image, I restructure the way a2sd operates, and Drizzy comes along and adds in some new apps he restructured to work on that build. Some people choose to stop somewhere along the path and stick to that ROM, others go all the way down the road. If there were only one update, most Devs would spend half the day just telling people how to disable, remove, or add the feature they integrated.
I just dont see how less is more in this case. If you don't like all the updates, do what I do. I have the ones I actually read followed, and I only ever take a quick glance at the first page of posts before checking those. If I miss anything important, it is only ever by a day. If it's that important, it inevitably gets bumped to the first page long before it becomes so old that I surely learned it somewhere else.
*end informed response*
Click to expand...
Click to collapse
twisted your roms are always the most polished and daily functionable
i appreciate your input on these forums as well as drizzys and jac's
im glad there are multiple possibilities so i can see which one runs the best for my intended uses
party a may use their phone for internet texting and facebook
when party b may use their phone for calls email and business
party A is using XXXHerorom that runs his needed functions the quickest and most efficient way possible
party b is using XXXherorom that runs his needed functions the quickest and most efficient way possible
jokeyrhyme said:
I've been a regular reader of these forums since researching my first Android purchase. Over this time I have seem many new ROM projects born. I would like to argue that many of these projects are so similar that they are pointless.
I'm calling out anyone whoever made a new Hero/HTC-Sense ROM. Seriously. When you saw the 10 other Hero guys out there, what made you think it was better to release your own flavour instead trying to participate in an existing project?
I've taken a look, and as far as I can tell, there should only be 3 non-factory ROM projects:
- CyanogenMod, because of the effort Steve goes to stay 100% legal and teeter on the bleeding edge of Google's source code
- 1 Hero/Sense UI ROM, because we actually only need 1, why don't you guys work together, sheesh
- 1 Blur rip-off ROM, because goodness knows there are going to be people who actually think it's a great idea
Just because Android is based on Linux, doesn't mean we have to make all the same mistakes that has dogged and doomed Linux from the beginning. We don't need to splinter into a billion different distributions, at least not yet. Looking at the feature lists for many of these similar ROMs, the only thing that is different is additional locales or small bug fixes, hardly worth the effort of repackaging. /sigh
*end nerd rage*
Click to expand...
Click to collapse
I don't agree and don't understand your frustration. You use what you want to use, let other people make their own decisions.
I happen to prefer Enomther's roms because they are more customizable in terms of what is included on the rom through the expansion pack and expension pack setup. I don't like arbitrary modifications as I prefer to have my phone close to vanilla Android but have performance improvements added. But going by your opinion it should not exist. Who are you to determine which rom's are pointless? I really don't understand the fuss. Different people have different preferences. If you prefer limited/no choice get an iPhone.
Unfortunately each Rom runs differently on each phone. My friend has the blurry screen problem while I dont. He can only run a few selected roms some of which doesn't do what he wants to do. I have gone though about 30 different roms before settling on one and quite frankly I think its pretty fun. I am on the bleeding edge of. techology.
I wish I would make a Rom. I have so many ideas for one.
The concern about multiple builds makes sense, but other folks have mentioned that different builds fix different things.
I've tried many of the Hero flavors, but sadly (unless I simply missed it) none of them have fully gotten bluetooth to work. I prefer using bluetooth for calling, and so far only Cyanogenmod's roms seemed to be able to nail this on the head. It's what I've been using for quite some time, and has proven to be the quickest and most stable.
It would be great if they all worked on just one version of the Hero rom, but it won't happen. Just imagine how many more are going to pop up when the official SenseUI shows up for the Saphire.
Eh
I completely disagree with the OP. Everyones needs are different and having a build thats just right for you is a luxury that you wouldn't get on most other types of phones. I really don't see an issue with having multiple builds even if they are fairly similar. Its not like we are wasting development time, there is no downside. Some may argue it makes it harder for users to find a good rom, but the bottom line is anyone who is flashing their android phone has an interest in technology and is going to enjoy trying out different builds. And once you've tried a few builds you get a pretty good idea of what your looking for in your ideal build making it much easier to choose. Using your Linux example, between work and home I use 3 different distributions everyday, the reason being each has strengths that make it ideal for specific applications, its not a problem or a mistake, its simply not everyones needs are the same.
Even for the novice like me it is not too hard to make sense out of what is available. I never liked when people do not read full thread before posting a question. Is it a problem of impatient generation or just a simple laziness? IDK.
Also, it has been a exiting jorney for me to learn everything about my phone and tremendous possibilities. Fear of bricking and yet the desire to try new stuff.
There are useful bits and pieces in almost every thread except yours, sorry to say that. There is nothing that can replace user's feedback and their own disoveries that are not necessarily coming from devs or people remotely in the field of android development.
Cease the proliferation of similar ROMs!
Click to expand...
Click to collapse
I also disagree with this thread. More choice is better for everyone!
Also if there are 2 similar roms, as a user rather than a dev you can still take the bits you like from both and make it your own.
jokeyrhyme really? have you made any roms or customized anything for your personal use? if so did you like it? if not, how come you didnt make one custom rom? is it because you dont know how or just rely on others to do it for you? there are soooooo many ppl with different "styles, perceptions and ideals" that one extra rom might be their next rom of choice!! whats wrong with a larger amount of variety? who gives you the right to try and call everyone out when they are the ones spending the time to learn, make and fix all the bugs for everyone when it started off for them selves?!?!? this thread is a joke and is taking up space in development. request for it to be moved to the trash or general. which ever is easiest.
WTF?
Ok at this point i'm kinda getting sick of this whole android forum. Way to much fighting, ignorance, complaints like damn who gives a **** (sorry just vex) who does what or doesnt do what or makes what or doesnt make what. If you dont like something...move onto the next. I mean those who alert the devs/cookers (whatever you choose to call them ) to issues with the rom only for the betterment of the rom are in the right. But when i see dumb **** like "this person's rom does this and that" i get pissed..just reflash that rom sit down shut up and think about that little life of yours that obviously is worthless since you can spend time downing people's work and yet you can make a rom or troubleshoot a rom on your own. Y'all need to relax yourselves find **** that works for you and stick wit hit. If it aint what you want..move on silently. dont fault the creator just move the hell on. Dont post dumb threads like this and most off DONT SAY ****!!! it's these very same forums dedicated to development of our devices that make our devices that much more amazing so dont flood the forum with dumb ****!!!. Show respect to our developers, give em props for taking time out of their lives to make our android experience benificial and super amazing.
I also disagree with OP's sentiment. I'd rather there be as many ROMs as possible than to have my choice restricted to a handful.
And daeshawn you're right, some people are so rude and unappreciative. I just ignore the douchebags and try to contribute as positively as I can.
I completely understand what you're saying. These forums can be really overwhelming at first. But honestly, I enjoy switching between different builds of Android just to see what they're like. Some people want APPS2SD, some don't. Some people want to split FAT32/EXT3/Swap, some don't. There are simply too many combinations for a small set of ROMs to handle.
sigh..... guess well never find the middle of the tootie pop
If a middle ground were to exist it could go something like this:
Everyone can do whatever they want as far as their ROMs go. Perhaps, for new people who might otherwise be overwhelmed with choices, the Q&A (if it doesn't already) could link to a few long-running, stable ROMs that typically accomplish the very basics. And once people get a chance to try those, figuring out what you want becomes a little simpler and the tons of threads start making some coherent sense.
It's like "which is better, Cyanogen's rendition or Enom's" and the answer, for a lot of people, is that it depends. There might be similarities and both ROMs ultimately accomplish a lot of the same things (root, A2SD, compcache, linux swap, etc.) but preferences remain. I like one, you like another. There's no reason both developers, each of whom presumably likes their own, can't go on making what they want to make and offering it out there. More over, the experienced users are already aware of the alternatives.
It's really newbies that might find the choices overwhelming.
As for reinventing the wheel with every ROM, many threads already provide credit to a variety of developers, so clearly the work gets around. Just because they all do it at their own leisure and in the order of their choosing doesn't mean the developers are living in closed bubbles. Maybe the colab work that needs to be done is already being done even if it's not obvious. More over, even if two ROM cookers decide to both implement similar changes apart from each other, the choice to do so is totally in their court. Their time and their money and their brains.
There is kind of, for me, a question of stability. I have a fair confidence, for example, that Cyanogen is not going to drop Android development entirely any time soon and his ROMs will continue to exist with updates and bug fixes. Other developers share this sense of stability, but it's not an all around type of thing. There are ROMs out there now that are interesting because they are cool and new, but will they still be maintained a year from now is another question entirely. And I think that's a legitimate concern and reason for wanting at least a few long-lasting ROMs. Because, essentially, if 5 devs work on something and one gets bored, there's still 4 left. Conversely, if there's only one dev and he/she decides they're done, now what?
Just my $.02
I've no issue with the number of roms.
however, what is missing is a simple resource that lists them and a summary of features.
trying to wade through all the post to see what does what is a total ball ache. I think this is more the problem than the number of roms.
An up to date one pager that showed the current status of what was available would be perfect.
Well, I totally deserve all the hate this thread has brought my way.
*bows head in shame*
I agree that if there was ever a place to test out dozens of difference features, then this is that place. So it's totally appropriate to have as many different ROMs as there are demands for different features and such.
I do think more could be done to draw new users towards stable and long-term projects, as has been suggested by sleepykit and moa77. Maybe that's really the solution I was after. An update to the listing or something perhaps?
Sorry about being a poohead, I'll be good now.
*hugs all round*
PS. I changed the topic title to be less evil and more open.
This may be irrelevant and this thread will probably be closed, but Ive had a few while Im looking for a new rom and it lead me to a question.
WHY DONT ALL THE DEVELOPERS WORK TOGETHER TO CREATE THE ULTIMATE ROM?
Im sure on of the ultimate answers would be based off of preference etc. but if we would all unite towards one specific goal, not only would we have more solid builds... but we would have more versions (lite, etc) but more themes, faster updates, etc.
I mean ive used this site for a couple years with different phones and we all seem to want the same thing. Speed, reliability, better battery life, etc. So why dont we conference, put our individual talents to use, create specific focuses and put together something Google themselves need to compete with.
I know a lot of the devs here already work together and I have no problems with the way things are... nor am I trying to disrepect any of the hard work you all have contributed. I was just thinking out loud.
Comments?
There is a similiar Thread already:
http://forum.xda-developers.com/showthread.php?t=572788
this is not a development topic. this belongs in q&a
We ARE working together, but we want to create ROMs for different purposes.
'ultimate' is pretty subjective.
it's easy to see all the different, seemingly random threads about different roms and mods and assume there's no teamwork involved, but really, it's just different people trying different things and when one works well most others adapt it. otherwise, everyone has a different 'ideal rom' anyways.
it's a fairly darwinian approach, but it works pretty well. you COULD try to get everyone to organize and work on one idea, but i think we can save that for companies like htc, motorola, huawei, samsung, google, etc.
besides, anyone who follows this or other android dev sites for more than a couple weeks knows which devs to kep an eye on.
what i feel is the ultimate rom, you don't think is the ultimate rom...
the ultimate ROM for me is feature lite, and fast.
despisedIcon said:
the ultimate ROM for me is feature lite, and fast.
Click to expand...
Click to collapse
And I like fast and feature heavy. Best of everything. :-D
All of your responses is exactly what I mean... Lets say for example, the devs focused on the fastest, most stable and lightest rom as a base. then moved on a way to easily create or modify a theme.
from there, we could move on to different versions... like a hero or blur, etc.
ultimately, every user is going to pick there favorite programs, so maybe we develop a way to easily choose which programs you want included before you flash the rom and voila...
i mean, im sure im making this sound easier than it might be, but with clear and open communication/ exchanging ideas and coming to a reasonable base... the possibilities are endless.
users could focus on the aesthetics like icons, themes, widgets, etc.
ALL WE NEED IS A SOLID BASE...
sure, there are some talented individuals accomplishing this on their own and thats all fine and understandable. I just know that with the power of many over one... a lot more could be accomplished easier, more deliberately and effectively.
Each dev could have a specialty that they focus on...
1. Themes
2. Troubleshooting
3. Speed/ Framework
4. Battery Life
5. The list goes on...
Create an FTP for everyone to access and we could show Google exactly what theyve been hoping for... which is developers alike coming together for the greater good... again, this is just my opinion, but im glad ppl are leaving their input
and with the choosing of apps example... my idea is, if there were a lite version and an ftp or somewhere to host a list of signed apks that you could choose via checkmark, click download and it would automatically save them to a special folder on the sd card. then, the lite version could have a script that auto runs during the initial boot to install directly from this folder on the sd card.
I guess im just trying to create simplicity for the newbs and the devs or veterans that have been on the site and are tired of flaming or answering the same question.
I say, we streamline this process, create simplicity through orginization and leave more room for progress...
Ok, well thats all i have for now... I mean, I have a lot more ideas, but we'll see where this goes...
It's HTC / Google's fault for releasing different models of the same phone, as most blog publishers are oblivious to the difference and post news under the *insert adverb here* title 'htc magic donut'
Well michael this thread did prove one very important thing. That even if your a senior member on this website you dont know jack. First cyan knows the nines and round here noone can really improve his stuff but him. Hence the reason he wont do his own hero rom. They lag no matter what. Sure you can take out all the widgets cut some fat off rosie. Well hell at that point just theme a donut rom. Running the heros and blurs r fun on g1 and mytouch. But if u ever actually pick up a hero phone or blur phone and test them.... u would see a huuuuuuuuuuuuge dif in performance. So basicly the guys know their crap. All of them. and they do work together. Read a drizzy post. Or other dev post. They always thank whoever for help. And if you want your ultimate rom follow cyan he will make it eventually.
Michaelr219 said:
This may be irrelevant and this thread will probably be closed, but Ive had a few while Im looking for a new rom and it lead me to a question.
WHY DONT ALL THE DEVELOPERS WORK TOGETHER TO CREATE THE ULTIMATE ROM?
Im sure on of the ultimate answers would be based off of preference etc. but if we would all unite towards one specific goal, not only would we have more solid builds... but we would have more versions (lite, etc) but more themes, faster updates, etc.
I mean ive used this site for a couple years with different phones and we all seem to want the same thing. Speed, reliability, better battery life, etc. So why dont we conference, put our individual talents to use, create specific focuses and put together something Google themselves need to compete with.
I know a lot of the devs here already work together and I have no problems with the way things are... nor am I trying to disrepect any of the hard work you all have contributed. I was just thinking out loud.
Comments?
Click to expand...
Click to collapse
You my friend are a pure genius, the problem is users ignorant and ROM makers naturally have low self-esteem. You see, take a guy like Haykuro he built the foundation for the first ROMs on the sapphire. Now he's fizzled out. BUT in the beginning he was the ****... Sure in every ROM maker's thread you will find credits etc. but that's all just ass kissing... You see, NO ROM MAKER DON'T MAKE ****! The only thing they get is an EGO BOOST! Who doesn't like an Ego boost? Developers at Google, HTC etc. Because they make $90,000+ a year doing what they do and they have normal lives with a wife and kids ideally... As for ROM makers on XDA they are either A) former workers at Google, HTC etc. who have grudges against their former employers OR B) they never got a real job working for a high end corporation like Google, HTC, etc. and ended up bumming it on XDA hoping one of their "fans" will buy they a lap dance... OR C) They are rich as **** and just love doin this **** for the hell of it because they like making ROMS, getting credit and most importantly, recognition and they ASS kissed constantly by people they don't even know... So there you have it in a nutshell with this kind of mix of developers, the ULTIMATE ROM is simply not possible... I certainly doubt I will never see it in my day or if we all go in 2012... If anyone does come up with something even slightly close to the ULTIMATE ROM I bet it will be Cyanogen or my man Dwang. Eugene was on the right track but he lost it when he turned out to be a SNiTcH AKA BIATCH of all ROM makers! But for real I love all ROM makers on XDA regardless of their motives or intentions, they spice up my life and hook my phone up and that makes them the ****. All of their work is appreciated obviously...
Wolfyy7 said:
You my friend are a pure genius, the problem is users ignorant and ROM makers naturally have low self-esteem. You see, take a guy like Haykuro he built the foundation for the first ROMs on the sapphire. Now he's fizzled out. BUT in the beginning he was the ****... Sure in every ROM maker's thread you will find credits etc. but that's all just ass kissing... You see, NO ROM MAKER DON'T MAKE ****! The only thing they get is an EGO BOOST! Who doesn't like an Ego boost? Developers at Google, HTC etc. Because they make $90,000+ a year doing what they do and they have normal lives with a wife and kids ideally... As for ROM makers on XDA they are either A) former workers at Google, HTC etc. who have grudges against their former employers OR B) they never got a real job working for a high end corporation like Google, HTC, etc. and ended up bumming it on XDA hoping one of their "fans" will buy they a lap dance... OR C) They are rich as **** and just love doin this **** for the hell of it because they like making ROMS, getting credit and most importantly, recognition and they ASS kissed constantly by people they don't even know... So there you have it in a nutshell with this kind of mix of developers, the ULTIMATE ROM is simply not possible... I certainly doubt I will never see it in my day or if we all go in 2012... If anyone does come up with something even slightly close to the ULTIMATE ROM I bet it will be Cyanogen or my man Dwang. Eugene was on the right track but he lost it when he turned out to be a SNiTcH AKA BIATCH of all ROM makers! But for real I love all ROM makers on XDA regardless of their motives or intentions, they spice up my life and hook my phone up and that makes them the ****. All of their work is appreciated obviously...
Click to expand...
Click to collapse
LOL... thank God for the internet. Id read some of the debates youve had in other threads and they got me laughing. Im on the fence, because Im not one to take sides, but not only are you funny... but I actually agree with you on this. I mean, just one thread above me I have some guy telling me that I dont know what Im talking about. For one, Im not claiming to know all there is to know about these phones... or Id be working for Google making the big bucks... and two, he only reiterated things Id already disclaimed.
I didnt start this thread to get flamed, but opinions are like a**holes, everyone has one.
I realize that most of my ideas wont see the light of day, because without the cash or proper credit, people wont work together unless they "get theirs"
A lot of these devs work their @$$es off and receive "tips" or donations purely because they love what they do and I respect that sincerely.
However, the idea that working "together" to create the ULTIMATE rom is possible. Devs asking for tips, help, or using work that one already accomplished isnt what im referring to. It would take moderators, coordinators, infrastructure, hierarchy, etc... To those that see the light of what im talking about, thank you... to the rest, thanks anyway
rossmoore81 said:
Well michael this thread did prove one very important thing. That even if your a senior member on this website you dont know jack. First cyan knows the nines and round here noone can really improve his stuff but him. Hence the reason he wont do his own hero rom. They lag no matter what. Sure you can take out all the widgets cut some fat off rosie. Well hell at that point just theme a donut rom. Running the heros and blurs r fun on g1 and mytouch. But if u ever actually pick up a hero phone or blur phone and test them.... u would see a huuuuuuuuuuuuge dif in performance. So basicly the guys know their crap. All of them. and they do work together. Read a drizzy post. Or other dev post. They always thank whoever for help. And if you want your ultimate rom follow cyan he will make it eventually.
Click to expand...
Click to collapse
Read my words carefully... I am aware of what has gone on here on this site. I acknowledged that a lot of developers work well together. Unlike you, im not giving specific credit to any one or two individuals. We all know who has hit the brick and mortar with the foundations that have been set. A lot of those individuals communicate regularly.
I was nearly drawing into the fact that with technology, they could all (those who are willing, of course) conference regularly, establish agendas, specific tasks, and create a template. One that has been re-worked inside and out by each of their hands till there isnt any input that one individually could produce. From there, the focus objective could be the bigger picture like compatible themes, updates, easier installs, more features, etc.
I know im repeating myself to a degree, but I want to make sure the image is clear. There are a lot of devs doing the same thing, for some of the same reasons. But us users all come here for the SAME reason. To take our toy/ pride and joy/ project/ whatever you wanna call it... to the next level. To make it better than it was out of the box, to see the realms that it is truely capable of.
So rather than seeing some devs running into similar problems with their roms individually or simultaneously... One of two things would happen, either A: Solve it immediately once and for all or B: Catch the bug before it was even released. Hopefully my words inspire some of you. If not, keep up the great work.
Lol - cracking read
Hi,
I see that we have many many roms and 2 types of Sapphire (32B and 32A)
Now I have an idea to help users to install and change rom easierly.
Please read all idea before replying. Some ideas relate to others.
1. All developer should make 2 choices : 32A rom or 32B rom
2. 32B rom have data/app_s. Running system application on flash memory is more stable and faster than running on ext partition sdcard
3. Recovery should have new feature : Wipe data except data/app_s
Amon_RA should add this feature in his recovery.
4. Developers should remove his own theme, 3rd application (which can download from market), moded application ... from rom, rom will be more stable and smaller
5. If developer want share his theme or moded application or add new feature, he should share extend update in an update_extend.zip on his topic. I suggest him to use 1 folder on sdcard and command *.sh file
If you used iPhone, you will see that moded FW of iPhone OS doesn't include theme, extend application (which can download from Appstore). Why can't we do that? I think almost people just want to find a stable rom without theme, without extend application
Some good ideas
+1 from me
Moar standardization pleez
Sounds like the OP is ill-informed, and wants an iPhone.
funbacon said:
4. Developers should remove his own theme, 3rd application (which can download from market), moded application ... from rom, rom will be more stable and smaller
Click to expand...
Click to collapse
i've seen a few of these in the dream forum.
the developer releases the rom as a base package. ie. rom only, no (or very few customisations).
then add on packs are released to add 3rd party apps and customisations.
eg. http://forum.xda-developers.com/showthread.php?t=538456
this developer has released 4 different roms. each one comes as a base rom that is rooted, and each rom also then has an expansion pack.
themes are then installed as separate downloads.
the post is also very clearly laid out. i wish more developers took the time to create such understandable threads.
Isn't this request cramping developer's style?
Yes that is what you may want. But at the end of the day, they are doing it out of their enjoyment. It's their project and they have free reign on what they do and when they do it. Out of shear good will developers share. Its not up to us to make requests on how things should be. Our roles is to be supportive and grateful for their contributions.
That's not to say your ideas aren't valid... perhaps just not entirely feasible.
ice_prophecy said:
Isn't this request cramping developer's style?
Yes that is what you may want. But at the end of the day, they are doing it out of their enjoyment. It's their project and they have free reign on what they do and when they do it. Out of shear good will developers share. Its not up to us to make requests on how things should be. Our roles is to be supportive and grateful for their contributions.
That's not to say your ideas aren't valid... perhaps just not entirely feasible.
Click to expand...
Click to collapse
Good Say My friend
seems like a pretty simple request. but what was said earlier has merit as well, since it is really the developer's choice since its done for free.
but yeah, some sort of options like Enthomer is nice. But then again those updates made by AmonRa and Cyanogen is awesome as well. Fast, stable and useful.
Oh, and I strongly support the part on the way the threads are made. some are really easy to follow up on for change logs and stuff, some are messy.
funbacon said:
If you used iPhone, you will see that moded FW of iPhone OS doesn't include theme, extend application (which can download from Appstore). Why can't we do that? I think almost people just want to find a stable rom without theme, without extend application[/B]
Click to expand...
Click to collapse
Search the board (and the Android Market) for MetaMorph which does exactly that.
+1
well, although 'm not a dev, but as users this idea is pretty workable. at least we had lesser unneccesary thread and will look more neat and tidy. thats what make xda more professional and classy. way to go devs. +1 to the idea.
thanks.
OP, good idea, but not everyone may think like you, including the DEVs. There is nothing wrong with what you are stating, but it has been mentioned before that different DEVs want to work on different things; some people want to be unique.
One more thing, can you please not use the word should so much, please?
My wife uses it all the time..."you should clean this" " you should go here" " you should say this". thanks.
ice_prophecy said:
Isn't this request cramping developer's style?
Yes that is what you may want. But at the end of the day, they are doing it out of their enjoyment. It's their project and they have free reign on what they do and when they do it. Out of shear good will developers share. Its not up to us to make requests on how things should be. Our roles is to be supportive and grateful for their contributions.
That's not to say your ideas aren't valid... perhaps just not entirely feasible.
Click to expand...
Click to collapse
Agreed. Although some of the requests are somewhat reasonable, it's up to the devs to decide what they want to do with their free time and they are dedicating so much of it to making such great contributions to begin with.
We're not paying for the dev's services, so i dont think we have much pull on how they design their ROMS (nor should we)
I think if you want a specific ROM a specific way. YOU should be learning how to code and cook ROMS for yourself.
OzJD said:
Sounds like the OP is ill-informed, and wants an iPhone.
Click to expand...
Click to collapse
Read and lol'd. This is probably pretty close to the truth.
Well I for one salute the OP for finally taking a stand and telling the devs what we really want. After all it is all about ME and what I want and they should bloody well be grateful that I even bother to tell them what is wrong with their work, and they should fix it faster. I am a busy guy and can't be bothered to figure out this stuff for myself....
If any of that even vaguely resonates with you... here is a very small clue, completely free of charge...
The devs do this work for their own reasons. Some do it for the challenge, some do it for fun, some do it because they want something different, some do it for the glory. However, they all share it and make the results of their hard work available for the benefit of us end user types. Many even provide free support and hand holding, answering the same questions over and over.
You can politely ask for things to change. If you structure your request well enough and it makes sense, some devs may see the benefit and change. Others will not. Trying to dictate standards of documentation, presentation, features, or packaging just is not going to work, and quite frankly why should it. They are not doing it for you, you are just benefiting as a side effect of them being willing to release their work.
I am sure if you were willing to pay regular software developer rates for a particular feature set, you could find folks willing to accommodate you. Unless you are willing to do that, consider that you already get far more than you pay for.
rydr1 said:
OP, good idea, but not everyone may think like you, including the DEVs. There is nothing wrong with what you are stating, but it has been mentioned before that different DEVs want to work on different things; some people want to be unique.
One more thing, can you please not use the word should so much, please?
My wife uses it all the time..."you should clean this" " you should go here" " you should say this". thanks.
Click to expand...
Click to collapse
I'm Vietnamese and my English is not good. I just know saying " you should do something" is better than saying "you have to do something" or "you must to do something"
ice_prophecy said:
Isn't this request cramping developer's style?
Yes that is what you may want. But at the end of the day, they are doing it out of their enjoyment. It's their project and they have free reign on what they do and when they do it. Out of shear good will developers share. Its not up to us to make requests on how things should be. Our roles is to be supportive and grateful for their contributions.
That's not to say your ideas aren't valid... perhaps just not entirely feasible.
Click to expand...
Click to collapse
So I guess we should also stop giving developers suggestions and bug reports, because who wants to fix bugs for enjoyment? I disagree quite a lot with your post; it is in fact our role to make requests. How are ROMs supposed to get better without the input of its users? You completely contradict yourself by saying that we should not "make requests" but we should "be supportive," because by making requests, you are being supportive. By trying to better the project, you are being far more supportive than a silent user.
It's not like funbacon's suggestion has malicious intent. Neither is he trying to dictate what devs should and should not do. You don't have to agree with all of his points, but dismissing the whole thing because of one point, or the fact that he referenced the iPhone, is stupid. It's a suggestion, which most of you have said is a good idea, yet don't think it should be incorporated because... of the vocabulary used? Or maybe it's some other reason, but I have yet to see another valid reason.
Will this work in practice? That's another discussion. But I believe having some standards and general guidelines will be immensely helpful and make it simpler to try different ROMs.
Rydr1, you need counseling. Or a divorce.
bjtheone said:
Well I for one salute the OP for finally taking a stand and telling the devs what we really want. After all it is all about ME and what I want and they should bloody well be grateful that I even bother to tell them what is wrong with their work, and they should fix it faster. I am a busy guy and can't be bothered to figure out this stuff for myself....
If any of that even vaguely resonates with you... here is a very small clue, completely free of charge...
The devs do this work for their own reasons. Some do it for the challenge, some do it for fun, some do it because they want something different, some do it for the glory. However, they all share it and make the results of their hard work available for the benefit of us end user types. Many even provide free support and hand holding, answering the same questions over and over.
You can politely ask for things to change. If you structure your request well enough and it makes sense, some devs may see the benefit and change. Others will not. Trying to dictate standards of documentation, presentation, features, or packaging just is not going to work, and quite frankly why should it. They are not doing it for you, you are just benefiting as a side effect of them being willing to release their work.
I am sure if you were willing to pay regular software developer rates for a particular feature set, you could find folks willing to accommodate you. Unless you are willing to do that, consider that you already get far more than you pay for.
Click to expand...
Click to collapse
So... all the developers here make ROMs for themselves, but are nice enough to post it for everyone else to use?
Wow, haha. What a distorted view you have there. (Most?) developers aren't as selfish as you think they are. Developers make ROMs so the people who visit this forum can benefit from them, or at least that's the general reason. Why do you think they release updates often to fix bugs or add new functionality, or address issues and suggestions brought up by users?
Or, if I were to look at it from your point of view: users are just tools that devs use to make their ROM better.
Yeah, no. You shouldn't think so lowly of devs here. They should be appreciated, you know.
1.I will say that i've had android since day 1 and funbacon was around at that time to. helping and making changes himself to certain roms and apks etc...and helped other people, so he shouldnt be treated as a noob that doesnt know what he is talking about or that he is whining because that is not the case.
2. He made a suggestion that has to do with development and posted in the correct spot and he still hears **** from it? when there are people posting in deveoplment forums that has nothing to do it " what rom is the best, or what phone should i buy" and they dont get as much **** as your handing to someone that made a DEVELOPMENT suggestion and a good one. in the correct section. so people shouldnt be downing him for his work/suggestions
p.s funbacon...nice to see you around again
funbacon said:
I'm Vietnamese and my English is not good. I just know saying " you should do something" is better than saying "you have to do something" or "you must to do something"
Click to expand...
Click to collapse
No, funbacon, you took it wrong. Im just kidding about using that word. there is nothing wrong with you using it, there is something wrong with my wife using it.
I was just adding a little fun to the thread.
Is it me or does it seem like most of the devs are shying away from cornerstone? Yeah, they have nightly cornerstone build, but it's completely unsupported and, according to the devs, is just for fun.
Why are the devs so hesitant to include cornerstone in their builds?
Lack of experience, first time most devs have seen ics, more work, etc.
Yeah its cool and has great features but there isn't an uproar by the users to have it now.
There is a lot of desire for this damn feature, but most of the threads are by people who don't look for the original threads.. etc. I agree though, most devs probably want to fix ICS first THEN work on extra features. IMO though, this multi-task feature should have been a big update for tablets.
goodintentions said:
Is it me or does it seem like most of the devs are shying away from cornerstone? Yeah, they have nightly cornerstone build, but it's completely unsupported and, according to the devs, is just for fun.
Why are the devs so hesitant to include cornerstone in their builds?
Click to expand...
Click to collapse
I'm interested as well, though I can understand some hesitation. I had heard that it has been a WIP for a while, I don't believe it's a close to a finished product yet. IIRC there was just a big code rewrite for it and the window swap feature isn't included currently. It's a shame really, I think the majority of the development is going to be with onskreen for a while until they can put out a stable code base. Either way, there are nightlies now.. its only been a few days.
goodintentions said:
Is it me or does it seem like most of the devs are shying away from cornerstone? Yeah, they have nightly cornerstone build, but it's completely unsupported and, according to the devs, is just for fun.
Why are the devs so hesitant to include cornerstone in their builds?
Click to expand...
Click to collapse
You would think that if cornerstone requires so much work why not do it from the start instead of slapping it in after all the bugs are ironed out then breaking evreything.
Oh and i wil be ssticking with the cornerstone roms even with all the bugs. Of which there arent many... if you count a text file one bug report.
Mostly i think it will be the people who like a challenge and dont mind if your tablet reboots or you are typing on the keyboard and the virtual kbd is up.
I personally love it and CM9 together it's like a damn hallmark card.
Sent from my Transformer using Tapatalk
its not a feature everyone wants and how many versions with onskreen do we really need? kinda boring if they all do it. although i personally think its the best feature on my tf ive used!
early days and i know jcarrz1 thinks its a cool feature but from what was said it would be done as a seperate rom from Frozn........ IF he does it and IF asus ever get his charger back to him lol.
Exactly what is the difference between the EOS and CM9 roms with cornerstone at the moment? I'm going to flash one of them over the weekend to play with cornerstone, but I'm not sure which to use now..
I am willing to bet that the new tablets coming out this year will have something like cornerstone, but probably much much better.
Windows 8 is coming to tablets. Windows itself is a multitasking OS due to the "windows".
Android will come up with something of their own too, they have no choice.
This reason alone is enough for me to ditch my dual core tab and get a more powerful one later on.
(because I know this is coming)
And no, tablets have not hit a plateau at measly 1.2ghz dual core. You won't convince anyone with that other than your grandmother.
asdfuogh said:
Exactly what is the difference between the EOS and CM9 roms with cornerstone at the moment? I'm going to flash one of them over the weekend to play with cornerstone, but I'm not sure which to use now..
Click to expand...
Click to collapse
Go with EOS + v9 gapps. A lot more stable and a lot less bugs. The onscreen keyboard even goes away when you plug into the dock.
goodintentions said:
Go with EOS + v9 gapps. A lot more stable and a lot less bugs. The onscreen keyboard even goes away when you plug into the dock.
Click to expand...
Click to collapse
Weird cause for me I had lots of crashes with eos. Although I do agree about the dock. Cool I will check it out.
Sent from my Transformer using Tapatalk
I personally prefer waiting for an official Google solution (in Jelly Beans?), but maybe if cornerstone is incorporated in one of the common ROMs I'll try it just for fun.
i'd wager most of the devs are just chefs.
Sent from my SGH-I897 using xda premium
goodintentions said:
Is it me or does it seem like most of the devs are shying away from cornerstone? Yeah, they have nightly cornerstone build, but it's completely unsupported and, according to the devs, is just for fun.
Why are the devs so hesitant to include cornerstone in their builds?
Click to expand...
Click to collapse
Currently?
I would love to support it. I really would.
However in its current state, cornerstone introduces a wide range of bugs.
There are only so many hours in a day I can dedicate to rom development, and unfortunately cornerstone doesn't make the cut.
-- solarnz,
Lead developer and founder of Team Eos.
solarnz said:
Currently?
I would love to support it. I really would.
However in its current state, cornerstone introduces a wide range of bugs.
There are only so many hours in a day I can dedicate to rom development, and unfortunately cornerstone doesn't make the cut.
-- solarnz,
Lead developer and founder of Team Eos.
Click to expand...
Click to collapse
From what I understand, the cornerstone source is a mess? Anyone have any examples of what is wrong with the cornerstone source and why it conflicts with Android in such a way?
If it is so messy, then it would seem some of our better devs here could (if motivated) write their own windowed overlay, similar to but not based on Onskreen. That way the code would be much cleaner, but it would only be a matter of time to devote, which I have high suspicions that the better devs here have very little of..
If anyone follow Steve Kondik on Google+,
He made this comment about cornerstone
Steve Kondik - Running this on my 10.1 right now. Definitely needs a bit of a tune-up, but lots of potential and I look forward to having it in CM9
Click to expand...
Click to collapse
This was a reply to his Cornerstone comments.
Not sure if this Dianne Hackborn is part of the Conerstone dev team or not
Dianne Hackborn - Okay, let me please please beg you not to do this. I can guarantee you this introduces all kinds of application compatibility issues. We work really hard to give our developers a consistent environment where their apps will operate correctly across all the devices Market runs on, not being impacted by negative reviews from bad devices that they should not have to deal specially with.
If you start making your own distributions of Android behaving in such fundamentally different ways, I suspect we are going to need to start doing things to prevent you from impacting our app ecosystem. I'm not sure what, but I could imagine things such as restricting how users can interact with Market apps on these devices (not allowing reviews or such).
We have let a lot of things in this area slide -- for example to be allowed to include Market on your device you are supposed to fully pass CTS. However, if you start really diverging from the core Android platform (I would argue this takes you well into the realm of a fork rather than a customization) then some deep issues are going to come up about how we handle these custom builds.
We have been putting a lot of thought and work for a number of years into how to let Android applications run on increasingly diverse and dynamic screens. Doing this correctly, without impacting our app developers in a negative way, is a really challenging problem. I also think it is something that needs to be done at the mainline platform level, not as a customization, because doing it right is going to require new well defined interfaces with applications for them to interact with it, possibly starting with just a facility they need to use to opt in to it.
Click to expand...
Click to collapse
baseballfanz said:
If anyone follow Steve Kondik on Google+,
He made this comment about cornerstone
This was a reply to his Cornerstone comments.
Not sure if this Dianne Hackborn is part of the Conerstone dev team or not
Click to expand...
Click to collapse
Diane Hackborn is part of the Google team
Does this mean that 'open source' Google doesn't like people diverting from their source too far? She says cornerstone alters the way Android OS functions..cornerstone is almost another fork on the source tree than a customization on the Android OS (wow) I had no idea it was that involved..and apparently, Google does not like cornerstone (or at least some of the higher-ups that work for Google).
So exciting
http://www.androidpolice.com/2012/0...rnel-source-code-including-that-of-the-one-v/
EDIT: http://dl4.htc.com/RomCode/Source_and_Binaries/doubleshot-gb-crc-2.6.35-f3a1982.tar.gz
Sent from my DoubleShot Lite using Tapatalk 2
ac3theone said:
so exciting
http://www.androidpolice.com/2012/0...rnel-source-code-including-that-of-the-one-v/
sent from my doubleshot lite using tapatalk 2
Click to expand...
Click to collapse
yyyyyyyyyyeeeeeeeeeeeeeeeeeeeeeessssssssssssssssssssssssss
Soo.... Does anyone think we could see some pure AOSP action now? Or someone could update the kernel for CM7? As you will see in general someone -whom I suspect is not alone - would love an AOSP ROM on our HTC Doubleshot.
Maybe this kernel isn't that good as we suppose...
Nusferatu said:
Maybe this kernel isn't that good as we suppose...
Click to expand...
Click to collapse
Well.... What did u expect? we don't have an ICS ROM in our future that we have been made aware of, and it is truly great news as this is something that has made many a dev stray away from this device - now we might be able to get CM7 stable - and others to work off of CM7 such as blahblah
Good news nevertheless
We need to get CM7 STABLE ASAP
We may be late in the running, but that doesn't mean we still can't get merged into the main tree
Nusferatu said:
Maybe this kernel isn't that good as we suppose...
Click to expand...
Click to collapse
Its worse than you thought... The source code was released a really long time ago. This is just an updated kernel, so the real reason for lack of development isn't because the source code wasn't available. :/
michaelmab88 said:
Its worse than you thought... The source code was released a really long time ago. This is just an updated kernel, so the real reason for lack of development isn't because the source code wasn't available. :/
Click to expand...
Click to collapse
Updated source is awesome though. Tried to get it earlier and couldn't - can't on shift and will be working straight until Friday afternoon so won't have a chance to try again for a few days.
Any percieved lack of development is due to people not putting any effort into it - everyone who cries about a lack of development should do something about it instead of waiting for someone else to do so.
Why come here if you don't want to get into dev, worse, come here and complain about yourself not doing anything? Kinda silly.
Whenever I see people complain about a lack of development I wonder why they would basically make fun of themselves? It gives me a laugh at their expense...
Sent from a digital distance.
Yeah i just got the source downloaded because it matches the new ota I'm running now, I've never seen what a dual core source looks like, or if I'll even be able to compile a kernel for this device, I've only compiled a few for the EVO shift, which was straight forward with a little help from my boy drob...who knows o may get it to boot ha-ha.......nope I fudged something in my toolchain It's broke....again.....LOL
Sent from my myTouch_4G_Slide using Tapatalk 2
strapped365 said:
Yeah i just got the source downloaded because it matches the new ota I'm running now, I've never seen what a dual core source looks like, or if I'll even be able to compile a kernel for this device, I've only compiled a few for the EVO shift, which was straight forward with a little help from my boy drob...who knows o may get it to boot ha-ha
Sent from my myTouch_4G_Slide using Tapatalk 2
Click to expand...
Click to collapse
http://dl.dropbox.com/u/62701184/arm-eabi-4.4.3.zip
That link is for the toolchain you need, i've been hosting it on dropbox for a while until I get it over to a more permanent host.
I can walk you through it later if you want.
I have it written up on how to set up your linux environment and make changes, including versioning instructions, just haven't found the time to polish off a part of it and add it to the dev reference yet.
Got a whole space reserved for the how to from start to finish on making kernels for the doubleshot, and i've already walked people through it with no kernel dev experience so if you've done it for another device it'll be a cakewalk.
I'm eating breakfast now and gotta run out to another job, and going straight from there to dodgeball practice, then work again tonight and from there right to the job i'm about to do again tomorrow this time, so tomorrow night i'm doubtless going to sleep - maybe as early as saturday evening I could go through it with you on IRC if you are interested.
Otherwise I hope to have that in the dev ref next week, work permitting.
Blue6IX said:
http://dl.dropbox.com/u/62701184/arm-eabi-4.4.3.zip
That link is for the toolchain you need, i've been hosting it on dropbox for a while until I get it over to a more permanent host.
I can walk you through it later if you want.
I have it written up on how to set up your linux environment and make changes, including versioning instructions, just haven't found the time to polish off a part of it and add it to the dev reference yet.
Got a whole space reserved for the how to from start to finish on making kernels for the doubleshot, and i've already walked people through it with no kernel dev experience so if you've done it for another device it'll be a cakewalk.
I'm eating breakfast now and gotta run out to another job, and going straight from there to dodgeball practice, then work again tonight and from there right to the job i'm about to do again tomorrow this time, so tomorrow night i'm doubtless going to sleep - maybe as early as saturday evening I could go through it with you on IRC if you are interested.
Otherwise I hope to have that in the dev ref next week, work permitting.
Click to expand...
Click to collapse
I might have my little one on Saturday night so that maybe a no go for then, the tool chain I currently have is 4.4.1, because anything newer for the speedy breaks a ton during the compile.....I changed some commands around for ****s and giggles and got a zimage in arch/arm/boot so I split it with the ota ramdisk and I'm just gonna try....if that goes south I'll setup your tool chain....thanks blue your like the DoubleShot dictionary....
Also I'm gonna grab one of your kernel zips for test flashes if that's ok
Sent from my myTouch_4G_Slide using Tapatalk 2
Blue6IX said:
Updated source is awesome though. Tried to get it earlier and couldn't - can't on shift and will be working straight until Friday afternoon so won't have a chance to try again for a few days.
Any percieved lack of development is due to people not putting any effort into it - everyone who cries about a lack of development should do something about it instead of waiting for someone else to do so.
Why come here if you don't want to get into dev, worse, come here and complain about yourself not doing anything? Kinda silly.
Whenever I see people complain about a lack of development I wonder why they would basically make fun of themselves? It gives me a laugh at their expense...
Sent from a digital distance.
Click to expand...
Click to collapse
Hey I'm not complaining, and I am working on it! I just have to balance between school and work and learning how to build cm7/cm9 from source.
You can check out a little bit of what I've been working on github.com/mafischer
michaelmab88 said:
Hey I'm not complaining, and I am working on it! I just have to balance between school and work and learning how to build cm7/cm9 from source.
You can check out a little bit of what I've been working on github.com/mafischer
Click to expand...
Click to collapse
Lol no worries my friend, was a general comment and not aimed at you in particular, just a perspective I wanted to put out there and you were the first opportunity to do so.
I still haven't found the time to get git set up and learn how to use it - that whole life getting in the way of living thing. Given you have git going that makes you a more responsible dev then I in my book -
@ strapped: all my work available is a contribution to the open source community at large, and the members of XDA in particular. If any of it can be useful, especially as a teaching tool, I wholeheartedly encourage it!
Sent from a digital distance.
Where did all of you come from?
Never knew there was this many people working on the Doubleshot in the background...
gtmaster303 said:
Where did all of you come from?
Never knew there was this many people working on the Doubleshot in the background...
Click to expand...
Click to collapse
I've been here since i preordered my doubleshot... I just haven't had time to work on much of anything, so there's no point in advertising to the community that I'm gonna work on things that may or may not ever get finished. I don't want to spread false hope or anything.
I am however, graduating in may; I'm going to be working over at walmart isd for a summer internship, and I should have more time on my hands once school is over!
How integrated is the Sense stuff into the kernel? As I understand it, we've had trouble removing the Sense underpinnings from the operating system to get it working with things such as Sixaxis. I'm aware that this is entirely a lack of understanding on my part.
I would quite love to get involved in building a ROM myself, perhaps even setting up CM9 from scratch. I just have no idea how to get started. I've mucked around with custom kernels and embedded linux (not android) devices in the past, but I'm not sure how that knowledge would apply to this system. I also have no history of proper programming languages or anything like that. I'm vaguely familiar with how to compile things with the ARM toolchains.
I'm also a tad nervous about bricking the device by writing to a memory location that I really shouldn't be touching.
Kanerix said:
How integrated is the Sense stuff into the kernel? As I understand it, we've had trouble removing the Sense underpinnings from the operating system to get it working with things such as Sixaxis. I'm aware that this is entirely a lack of understanding on my part.
I would quite love to get involved in building a ROM myself, perhaps even setting up CM9 from scratch. I just have no idea how to get started. I've mucked around with custom kernels and embedded linux (not android) devices in the past, but I'm not sure how that knowledge would apply to this system. I also have no history of proper programming languages or anything like that. I'm vaguely familiar with how to compile things with the ARM toolchains.
I'm also a tad nervous about bricking the device by writing to a memory location that I really shouldn't be touching.
Click to expand...
Click to collapse
Sorry for quoting the whole post just to address one thing, but in regards to sixaxis I'm sure it's a safe bet that if one were to simply replace the stock bluetooth stack with the one kornyone used for cm7 in my bulletproof rom it would work fine, and I doubt much other, if any modification would be necessary.
I haven't had time to try, and truthfully i'd rather build my own so am kinda intentionally not trying - I am more interested in the project then just jumping into a solution.
It really depends on what you are trying to do - some sense things can be replaced with relatively little effort, other things are so interwoven it would take considerable effort and time to unravel, reverse engineer and implement a new solution.
A lot of people have been working on different parts of unravelling sense since back in august, and around the middle of that month we got s-off and really started digging in.
There is a considerable knowledge base lurking here to address this kind of stuff if people make it known they are working on things - dig back through the history of the device here at XDA and you can catch a glimpse of it and get some direction on who you can approach when you hit a roadblock, depending on what kind of roadblock it is.
It's better for us as a community to have that kind of knowledge out on the public forum, but there's much more here then what face value suggests.
I've been trying to get that kind of stuff and a general 'start here' knowledge base built in the developers reference stickied here in dev, reading through that would be a good place to start getting oriented on devving for the dubleshot.
I just go through some crazy work cycles and sometimes can't be around much for a time here and ther, so my contributions come in groups and gaps.
Sent from a digital distance.
michaelmab88 said:
I've been here since i preordered my doubleshot... I just haven't had time to work on much of anything, so there's no point in advertising to the community that I'm gonna work on things that may or may not ever get finished. I don't want to spread false hope or anything.
I am however, graduating in may; I'm going to be working over at walmart isd for a summer internship, and I should have more time on my hands once school is over!
Click to expand...
Click to collapse
It doesn't matter whether or not you finish. Status updates would be nice though. At least that way people can know what you're up to, and they may even be able to help you and vice versa.
No one here is demanding an ETA or even a completion at all. We're all in for the fun of it.
Either way I think I can safely speak for everyone when I say, we're excited to see what you got cooking
Blue6IX said:
Sorry for quoting the whole post just to address one thing, but in regards to sixaxis I'm sure it's a safe bet that if one were to simply replace the stock bluetooth stack with the one kornyone used for cm7 in my bulletproof rom it would work fine, and I doubt much other, if any modification would be necessary.
I haven't had time to try, and truthfully i'd rather build my own so am kinda intentionally not trying - I am more interested in the project then just jumping into a solution.
It really depends on what you are trying to do - some sense things can be replaced with relatively little effort, other things are so interwoven it would take considerable effort and time to unravel, reverse engineer and implement a new solution.
A lot of people have been working on different parts of unravelling sense since back in august, and around the middle of that month we got s-off and really started digging in.
There is a considerable knowledge base lurking here to address this kind of stuff if people make it known they are working on things - dig back through the history of the device here at XDA and you can catch a glimpse of it and get some direction on who you can approach when you hit a roadblock, depending on what kind of roadblock it is.
It's better for us as a community to have that kind of knowledge out on the public forum, but there's much more here then what face value suggests.
I've been trying to get that kind of stuff and a general 'start here' knowledge base built in the developers reference stickied here in dev, reading through that would be a good place to start getting oriented on devving for the dubleshot.
I just go through some crazy work cycles and sometimes can't be around much for a time here and ther, so my contributions come in groups and gaps.
Sent from a digital distance.
Click to expand...
Click to collapse
I've been trying to go through the dev reference that you posted and track down as much scattered information as I can, but I'm still not quite sure what I'm doing. Alas.
Regarding bluetooth: would the gingerbread stack be compatible with ICS?
gtmaster303 said:
It doesn't matter whether or not you finish. Status updates would be nice though. At least that way people can know what you're up to, and they may even be able to help you and vice versa.
No one here is demanding an ETA or even a completion at all. We're all in for the fun of it.
Either way I think I can safely speak for everyone when I say, we're excited to see what you got cooking
Click to expand...
Click to collapse
Well what I'm currently up to is making a stable version of cm7 for the doubleshot. I have made lots of progress as far as learning all the tools necessary to compile android from source, which is a relatively simple task. The not so simple part is trying to put together like a puzzle, the source code from other devices. I've hit some roadblocks and I'm currently asking some devs for help, but while I'm at it I guess I can ask for help here on xda.
michaelmab88 said:
Well what I'm currently up to is making a stable version of cm7 for the doubleshot.
Click to expand...
Click to collapse
Yeehaaa!