[Q] Advice on how to follow CM9 Development - HTC Sensation

I asked this in another thread, but unfortunately wasn't able to get a response before it got buried.
I have had a tough time navigating the CM9 site, currently there is nothing as far as "Nightly" and Released builds for CM7 or CM9 released for the Sensation, even though I know there is an Alpha CM7 build out there.
I know both of these are far from release, but is anyone aware of threads, twitters, or websites alike where I can track the development of CM9?
Many thanks, XDA.
Edit: For clarification, this is barring the excellent "CM7 Bible" on XDA. Mostly looking for Outside sources and internal sources on CM9

twitter is a great resource for this, but the real news usually comes on google plus. add keyan mobli (our device's dev) to your circles, as well as steve kondik, who is the "boss" of cm. whatever you do, don't drive them crazy or ask for ETAs, it's quite irritating to them!

htcg2 said:
Whatever you do, don't drive them crazy or ask for ETAs, it's quite irritating to them!
Click to expand...
Click to collapse
I'm actually flabbergasted that people do that. Asking for ETA's on free software. *Shakes head.*

Related

[VOTE] We need a dev team around ICS, no?

Hi
These last days, and this is a joy, a few new/or not developers are beginning to create roms on ICS.
Each rom has a difference with others, and i noticed some roms has qualities that are not found on others, but need the advantages of some others.
A few users asked it before, i offer today with this thread (i hope this is not a mistake, and that it will remains clean), to vote. The target is to ask to our developers to create a sort of developing team, around a "unic" rom.
Their competences put in common should be awsome, don't you think?
If you want to help me to make this thread known by developers, do not hesitate to link it in your signature, by this way, dev in the development section could see the result of the vote, that i hope to be YES
Thx for your responses, and please take this thread clean
Want a good idea !
Google is doing this. Wait for the official release...
Sent from my Nexus S 4G using xda premium
It is called the CM team.... facepalm
FYI, Koush is an integral member of that team (not that they have been working on ICS as a team yet)
This is a terribly biased survey. Where's the option for "No, we'd like to see a diverse selection of Roms"
With all due respect, "Nope, i prefer lot of partially working roms" is a very suggestive option, that says you're critical of the current work, or just impatient.
Seriously dude, ics JUST CAME OUT. Teams will form, and work will get done in due time.
Patience, grasshopper.
Have you no humour?
If you say no, indeed it can be for other reasons..
In fact, the target is to reach an almost stable and fully functionnal BEFORE the official release...
after this, no need to have a team, on a official base, a dev can do something good alone.
As you like to call me grasshoper, and with all the due respect , i would like to call you embittered cod-fish.
Does it fit enough to you sir?

CyanogenMod for Galaxy R

We could possibly convince the CM team to cook CM for our device too. We need to request them in their forums.
Please add your requests to these threads.
http://forum.cyanogenmod.com/topic/39663-cm-for-galaxy-r-gti9103/
http://forum.cyanogenmod.com/topic/40719-please-port-cyanogenmod-to-galaxy-r-i9103/
http://forum.cyanogenmod.com/topic/30930-samsung-galaxy-r-z-gt-i9103/
http://forum.cyanogenmod.com/topic/37018-please-give-us-cyanogen-mod-for-samsung-galaxy-r-i9103/
I don't think it's gonna make much difference. None of mods/devs have ever answered to any of those threads.
I think that our guys will port it faster.
m.kochan10 said:
I don't think it's gonna make much difference. None of mods/devs have ever answered to any of those threads.
I think that our guys will port it faster.
Click to expand...
Click to collapse
The reason is the requests are too few for anyone to notice.
The Devs wont make a ROM for just 5 or 6 people. We need to have a mass request.
Let us give it a try
You may be right, It doesn't harm to try. But I don't think creating new threads is a good idea since we already have....nine of them. Opening new threads will just make mods pissed. We need to chose the one major thread - in section Unofficial Ports (that's the place for unsupported devices), and write there.
I agree with you 100%.
But the question is, which thread do we support?
From what I've seen, the cyanogenmod team won't just take on a new phone like that. Maybe after we have a stable unofficial port, but not til then. Look at how the huawei ideos 1850 progressed, it got a lot of attention after someone ported it for themselves, and now it has official CM. keep going guys but if you really want CM then I think it's better to help get AOSP for R than to spam CM forums...
Sent from my GT-I9103 using XDA App
I absolutely agree, that none gets cm just like that: "-please give us cyanogen!" "-Ok here you go"
(There are already nine threads - every new user seems to want to have his own thread Even I opened one in donators lounge )
Another example. I don't remember what it was for device, but users contacted directly one of cm devs and then created a donation thread, collected money and bought him a phone. Once they got CM development started for real.
I think the max what they can do for us is welcome a new developer from us with this device and let him do CM for R :/. Thats could happen with LG GT540 and there was a veeeeeeeeeeeeery big spam about CM for it.
+1
CM is the beast..
I guess after our device gets ICS it will step into the world of real dev'ing.
If someone has good experience with repos and AOSP + CM7 stuff please help me with my git repo here:
http://github.com/EmoBoiix3/android_device_samsung_galaxyr
Although we don't have many devs who own this device, it feels very nice that we have a couple of members who are willing to put their best efforts to port the ROM.
We could show our gratitude and support when they bring out the early builds by donating. Please show your support friends.
+1
Must need cm7
Sent from my GT-I9103 using xda premium
And regarding the ICS for our phone, I can sense some delay. Samsung leaks firmwares frequently during development. Probably because they know that we guys flash it and report bugs here. It would save them time on testing.
Couple of builds have leaked for Galaxy SII.
None for ours yet. Same with Optimus 2x. The users from O2x forum say that the OEMs are waiting for NVidia to release the sources.
We can expect ICS for i9103 in Q2
^^
thats a sad bit of news
ICS
Official ICS for SGR is due Q1 of 2012. I think only after release of the official rom, devs will start working
Good news as the first Tegra 2 device running Android 4 (ICS) will be on sale starting 15 Jan. 2012.
The device is Acer Iconia Tab A200 and it will be a milestone for a ICS port for all the other devices sharing the same CPU/GPU.
The original story here:
Acer Expands Popular Tablet Lineup With Iconia Tab A200, a Full-Featured HD Tablet at an Attractive $329 Price
What about CM?
Hello,
Is anyone still developing of the cyanogenmod for Galaxy R GT-I9103?
I'ld like to offer free allocation for your builds on cyanogenmod.su or any new domain you want!
I have over 1K users, who will be happy to test CM7 or CM9 builds, make bugreports and donate.
Maybe you know someone else who develops cyanogenmod, I'll be grateful for any response.
We have few devs that work on AOSP and CM7. Check these threads:
http://forum.xda-developers.com/showthread.php?t=1558637
http://forum.xda-developers.com/showthread.php?t=1548775
Yes , that's good . If someone in the CM team is good with kernels maybe they can help me
Defy-ing all limits.

[Q] CM9 on Motorola Defy is terrible

Previously I have had great joys with CM, however version 9 with build CM9-NIGHTLY-120308-Defy(hwa) is a complete piece of garbage.
The phone is over heating, freezing, rebooting and generally slow as a dog.
The phone is now rendered pretty much useless.
Has anyone had any luck with any of these builds. So far it looks like CM9 is far from ready for the Motorola Defy.
Is CM9 ready for any phone yet? I think you're expecting too much from an alpha build.
This is what happens when people flash alpha nightly roms and have no idea what they are doing.
speedyink said:
Is CM9 ready for any phone yet? I think you're expecting too much from an alpha build.
Click to expand...
Click to collapse
Thnaks for your reply. So it is still very early in the development stage? I upgraded to 120319 Nightly Build, which is much faster. Seems like most issues are ironed out, however there are still a few little glitches in regards to performance.
A short amount of time to pass for such an increase in performance though, kudous to the developer.
zelendel said:
This is what happens when people flash alpha nightly roms and have no idea what they are doing.
Click to expand...
Click to collapse
Thanks for your underlying tones of sarcasm and arrogance.
I was not aware of the moderator’s culture in XDA forums to contradict the entire purpose of having a Forum and a Mod. Your lack of support and helpfulness is quite deterring. I'll be sure to embrace for the next sarcastic comment from a mod in the near future.
Though, I do understand that your tiny position of power may have incited your god complex, corrupting you to a delusional belief that you have a higher purpose in this world, hence we’ll let this one slide.
Of course, you’ll probably delete this post out of embarrassment or anger, due to the fact that someone has questioned your role and general purpose in the forum.
damon79 said:
Thanks for your underlying tones of sarcasm and arrogance.
I was not aware of the moderator’s culture in XDA forums to contradict the entire purpose of having a Forum and a Mod. Your lack of support and helpfulness is quite deterring. I'll be sure to embrace for the next sarcastic comment from a mod in the near future.
Though, I do understand that your tiny position of power may have incited your god complex, corrupting you to a delusional belief that you have a higher purpose in this world, hence we’ll let this one slide.
Of course, you’ll probably delete this post out of embarrassment or anger, due to the fact that someone has questioned your role and general purpose in the forum.
Click to expand...
Click to collapse
Not at all. I find your post amusing. And the general purpose of the forum is for development not user support.
The whole point to nightlies is the fact that it is very alpha and unstable. So flashing them you should have expected issues. You gave no logcat to help trouble shoot any issues have. Even though on the CM site it states clearly not to post issues on nightlies due to it being alpha stage. So instead you come to a development forum and make a post calling it crap.
But I will close this up. As it serves no real point.

Development : Posting ROM issues in the first post?

I've happily owned a G2X for almost 7 months now, and have used a custom rom for essentially the entire time.
Prior to the G2X, i used the HTC HD2 - a Windows 6.5 phone that gained notoriety after having android ported to it through the hard work of developers.
However, one thing that I feel is truly missing from the development community here is what most HD2 devs did; that is, they disclosed the problems with their ROM in the first post of their threads.
So, rather than having to hunt through a 200+ page thread, not knowing what build people are referring to, in order to find out issues with a ROM, it would very much simplify the ROM selection process if devs would disclose known issues such as "non working camera" etc.
Obviously every issue cant be accounted for, but I think the big ones being posted would help clarify a lot of things.
Thoughts?
Edit:
For example, here's a link to one of tytung's HD2 roms (he's one of the more popular developers for the HD2):
http://forum.xda-developers.com/showthread.php?t=1434860
If you scroll down, you'll see he has a list of "working" and "not working" features.
Nobody has any interest in something like this?
Well the thing is all our rooms are based off stock,cm7, or cm9 in one way or another. So everyone knows of the known issues. If its a weird issue out of the norm its usually stated.
Sent from my Galaxy Nexus using xda premium
Reasoning above doesn't hold up, because each rom has things that are fixed or not fixed individually.
I'm not sure of the reasoning, and i guess different devs might have different reasons. Depending on their priorities and skill levels.
Of course if someone is cooking and theming and/or just vanilla compiling then maybe there's less reason (and perhaps more reason to deemphasize bugs?).
Anyways, i agree that an informative first post with a real change log and working and non working features is a very handy thing to have.
Sent from my LG-P999
kwes1020 said:
Well the thing is all our rooms are based off stock,cm7, or cm9 in one way or another. So everyone knows of the known issues. If its a weird issue out of the norm its usually stated.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
I don't think everyone knows the issues. In fact, if you're new to the community you certainly wont.
Stating the problems is what sparked a ton of competition in the HD2 dev community. The first guy to fix the camera, first guy to fix bluetooth powerdrain etc always got a ton of donations and a better rep. I just don't see that competition here at all.
I don't care about a custom bootloader image or some custom wallpapers. I care about the issues being fixed, and I would love to know which devs are the ones fixing them!
rkarsk said:
I don't think everyone knows the issues. In fact, if you're new to the community you certainly wont.
Stating the problems is what sparked a ton of competition in the HD2 dev community. The first guy to fix the camera, first guy to fix bluetooth powerdrain etc always got a ton of donations and a better rep. I just don't see that competition here at all.
I don't care about a custom bootloader image or some custom wallpapers. I care about the issues being fixed, and I would love to know which devs are the ones fixing them!
Click to expand...
Click to collapse
It really doesn't matter who fixed them, as long as they're fixed. It's not a competition over here. The devs here help each other, especially with ICS. If one of us has a fix for something, it's shared and we all get it. Majority of the people doing the reading that they're supposed to do know the issues that we have with this phone. It just comes down to, are you willing to read to get all of the facts?
Mr. Apocalypse said:
It really doesn't matter who fixed them, as long as they're fixed. It's not a competition over here. The devs here help each other, especially with ICS. If one of us has a fix for something, it's shared and we all get it. Majority of the people doing the reading that they're supposed to do know the issues that we have with this phone. It just comes down to, are you willing to read to get all of the facts?
Click to expand...
Click to collapse
Exactly. We don't do this for competition. We do this as a hobby and we all learn from each other. And even the best developers out there are still learning. If you think developers do this for money you are sadly mistaken, money is in app development not roms.
We all have families, kids, school, jobs and a real life. Therefore free time is hard to come by.
You can go to any development thread skim over the last two pages and have the known issues.
bluenote73 said:
Reasoning above doesn't hold up, because each rom has things that are fixed or not fixed individually.
I'm not sure of the reasoning, and i guess different devs might have different reasons. Depending on their priorities and skill levels.
Of course if someone is cooking and theming and/or just vanilla compiling then maybe there's less reason (and perhaps more reason to deemphasize bugs?).
Anyways, i agree that an informative first post with a real change log and working and non working features is a very handy thing to have.
Sent from my LG-P999
Click to expand...
Click to collapse
If you can't see the reasoning. Then I would like to see the roms you have posted that are not based on one of the bases I listed.
There is this thing called github that most of us use. If you want a "real" change log its there that you'll find it.
Sent from my Galaxy Nexus using xda premium
kwes1020 said:
You can go to any development thread skim over the last two pages and have the known issues.
Click to expand...
Click to collapse
The above isn't even remotely true.
Are you done speaking for all developers yet? I would guess each one can speak for themselves, don't you think?
kwes1020 said:
If you can't see the reasoning. Then I would like to see the roms you have posted that are not based on one of the bases I listed.
Click to expand...
Click to collapse
I guess your reading comprehension isn't very good. I explained why and how there may be differences. If your experience is mainly doing what I called "vanilla compiling" or theming then I guess I could see how you would generalize that all ROMs will be the same though.
kwes1020 said:
There is this thing called github that most of us use. If you want a "real" change log its there that you'll find it.
Click to expand...
Click to collapse
I'm not sure why you feel the need and give yourself the permission to get up on your high horse here. I'm aware of source control and I was using it and writing C code nearly 20 years ago although I'm not a programmer now nor was I then but thanks for informing me. I also note the lack of a git or other source control published in the first post of your ROM in the dev section. As I'm sure you know many (most?) other ROM's don't either in there.
Not sure what you're afraid of to be getting your back up. Nobody cares if you just barely learned how, or are an expert at, writing code. People will appreciate a community contribution regardless.
bluenote73 said:
The above isn't even remotely true.
Are you done speaking for all developers yet? I would guess each one can speak for themselves, don't you think?
I guess your reading comprehension isn't very good. I explained why and how there may be differences. If your experience is mainly doing what I called "vanilla compiling" or theming then I guess I could see how you would generalize that all ROMs will be the same though.
I'm not sure why you feel the need and give yourself the permission to get up on your high horse here. I'm aware of source control and I was using it and writing C code nearly 20 years ago although I'm not a programmer now nor was I then but thanks for informing me. I also note the lack of a git or other source control published in the first post of your ROM in the dev section. As I'm sure you know many (most?) other ROM's don't either in there.
Not sure what you're afraid of to be getting your back up. Nobody cares if you just barely learned how, or are an expert at, writing code. People will appreciate a community contribution regardless.
Click to expand...
Click to collapse
Well plainly you have not read the umpteen million threads regarding lg and nvidias lack of open source. If you want the source for any of the roms I've posted that are based off of a stock rom. My source is right there in the rom. Decompile it and look at it. Just like i decompiled it and modded it. You want the source for my cm/aosp based roms its on my github. Want the source for aokp? Its on github and gerrit.
People clearly appreciate my contributions in the android community. I'd say 1000s of downloads and being kanged countless times can prove that. And in case you haven't noticed their aren't many devs in the g2x community. And certainly hardly any of them are going to come answer a thread posted in the wrong section.
Lastly I am not on any high horse nor have I ever been. I have done more then my part to help and contribute to this community. When you post something constructive then you can try to bring your constructive criticism my way.
That is all have a good day. We will post our threads how we want to. Please learn to read a few replies and the answers are there.
Sent from my Galaxy Nexus using xda premium
kwes1020 said:
Well plainly you have not read the umpteen million threads regarding lg and nvidias lack of closed source. If you want the source for any of the roms I've posted that are based off of a stock rom. My source is right there in the rom. Decompile it and look at it. Just like i decompiled it and modded it. You want the source for my cm/aosp based roms its on my github. Want the source for aokp? Its on github and gerrit.
People clearly appreciate my contributions in the android community. I'd say 1000s of downloads and being kanged countless times can prove that. And in case you haven't noticed their aren't many devs in the g2x community. And certainly hardly any of them are going to come answer a thread posted in the wrong section.
Lastly I am not on any high horse nor have I ever been. I have done more then my part to help and contribute to this community. When you post something constructive then you can try to bring your constructive criticism my way.
That is all have a good day. We will post our threads how we want to. Please learn to read a few replies and the answers are there.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Pretty sure this response answers the OP's question far better than I ever could have. Thanks for demonstrating.

Unofficial CM10 - IMPORTANT - Please Read.

As im sure most of you all know, I have locked the Unofficial CM10 thread. It isnt because of one person or one event, but something that has been coming for a long time. I have been stressing myself with this build and making sure that everyone was happy and doing pretty much everything i could do, but it didnt seem to be enough. While i appreciate the feedback, it is very disappointing to release cm10.1 when pretty much no other phones have released it (due to the lack of source merged and changes necessary for jellybean 4.2.1) and have nothing but post after post of this doesnt work and this doesnt look right and this is running horrible and blah blah blah even after i made it absolutely clear time after time that there may be issues since there is alot of source changes that are missing. You would think that since i took the time to merge the needed changes and work tirelessly to make changes and get the changes merged into our device/kernel trees to get CM 10.1 built and IMO running nicely, there would be alot of positive feedback and alot of understanding from the community that there may be little issues here and there since not everything was completely merged in on the CM side, but that was not the case as everyone expects perfection right and nothing else. Anyways, with that said, Building CM10 was becoming more of a job instead of something fun that i loved to do. And believe me... I havent had nearly enough donations to be ok with considering this a job... Nor do i expect alot of donations and for those of you who have supported me, I greatly appreciate it. I WILL CONTINUE to build CM10 and posting new builds on my goo page found HERE. I will not however be unlocking the CM10 thread. So... If you like my work and like my builds, keep an eye on my goo page and download when you are notified there is an update. If you like the build, great... if not, flash something else.
scott.hart.bti said:
As im sure most of you all know, I have locked the Unofficial CM10 thread. It isnt because of one person or one event, but something that has been coming for a long time. I have been stressing myself with this build and making sure that everyone was happy and doing pretty much everything i could do, but it didnt seem to be enough. While i appreciate the feedback, it is very disappointing to release cm10.1 when pretty much no other phones have released it (due to the lack of source merged and changes necessary for jellybean 4.2.1) and have nothing but post after post of this doesnt work and this doesnt look right and this is running horrible and blah blah blah even after i made it absolutely clear time after time that there may be issues since there is alot of source changes that are missing. You would think that since i took the time to merge the needed changes and work tirelessly to make changes and get the changes merged into our device/kernel trees to get CM 10.1 built and IMO running nicely, there would be alot of positive feedback and alot of understanding from the community that there may be little issues here and there since not everything was completely merged in on the CM side, but that was not the case as everyone expects perfection right and nothing else. Anyways, with that said, Building CM10 was becoming more of a job instead of something fun that i loved to do. And believe me... I havent had nearly enough donations to be ok with considering this a job... Nor do i expect alot of donations and for those of you who have supported me, I greatly appreciate it. I WILL CONTINUE to build CM10 and posting new builds on my goo page found HERE. I will not however be unlocking the CM10 thread. So... If you like my work and like my builds, keep an eye on my goo page and download when you are notified there is an update. If you like the build, great... if not, flash something else.
Click to expand...
Click to collapse
you have a charachter flaw. you're a people pleaser. once you get over that and become a true asshole you will be much happier in life.
Dani897 said:
you have a charachter flaw. you're a people pleaser. once you get over that and become a true asshole you will be much happier in life.
Click to expand...
Click to collapse
Lol! So true!
Sent from my SGH-I997 using xda app-developers app
Just wanted to put my two cents in...I've been an avid user of the roms from this site for quite awhile now & have never felt the need to register because any issues I've ever had,I've been able to rectify with some searching or have been on roms that have clearly stated they were beta's & expected to have flaws. That being said...after watching what happened on your infuse board, I just wanted to let you know the fact that you're continuing to develop & keep our phones updated with the best features gave me the first true reason to register so I could say thanks...
Sent from my SGH-I997 using xda app-developers app
Thank You.
I don't blame Scott for having the thread closed, not one bit.
And Dani is correct, Scott's character flaw is only that he's missing the "asshole" gene that some tend to have.
Now on to the good part...
I'm getting back into the swing of things as far as porting and development goes. My first attempt is going to be a nearly pure AOSP build using Aries repos and some Maguro/Takju code base, with parts from the most recent CM10.1 base. I have an idea of what I want to incorporate, but it should be light and clean, with a smooth interface.
Scott, I will be in touch with you shortly on this, as I need to finish and finalize my SDK installs and get everything going correctly for a first build.
Just checked Scotts goo link. Can I safely assume the development continues? If so hallelujah the infuse lives on.
Sent from my SGH-I997 using xda app-developers app
Most of the people that posted just wanted insight on their issues. Personally, I posted there because I felt I wasn't getting any response in the Q&A thread.
I think we should learn from the miscommunication.
One of the bigger problems we faced was that the build thread was the most responsive place to get an answer, and the bugs people had weren't clearly documented somewhere (you can't tell someone to search 500+ pages, find a bug, match it to their build, etc) so they could find and know NOT to post about it.
Going forward, maybe we can have:
Build thread- keep updated on the status of the build
Bug thread- to review / report the current build bugs
Q&A thread- how do I rotate the screen, why is this doing that, etc
Thoughts?
hattrickinc said:
Most of the people that posted just wanted insight on their issues. Personally, I posted there because I felt I wasn't getting any response in the Q&A thread.
I think we should learn from the miscommunication.
One of the bigger problems we faced was that the build thread was the most responsive place to get an answer, and the bugs people had weren't clearly documented somewhere (you can't tell someone to search 500+ pages, find a bug, match it to their build, etc) so they could find and know NOT to post about it.
Going forward, maybe we can have:
Build thread- keep updated on the status of the build
Bug thread- to review / report the current build bugs
Q&A thread- how do I rotate the screen, why is this doing that, etc
Thoughts?
Click to expand...
Click to collapse
But Scott specifically asked multiple times not to post bugs on the 4.2/cm10.1 releases due to the fact that source is still being merged -cm said themselves that the 4.2 code would be buggy and that you probably wouldn't be able to build anything with it...for the most part Scott proved both of those wrong
However I do like the idea of the three threads
Sent from my HTC Holiday using Tapatalk 2
openwheelracing said:
Just checked Scotts goo link. Can I safely assume the development continues? If so hallelujah the infuse lives on.
Click to expand...
Click to collapse
scott.hart.bti said:
I WILL CONTINUE to build CM10 and posting new builds on my goo page found HERE. I will not however be unlocking the CM10 thread. So... If you like my work and like my builds, keep an eye on my goo page and download when you are notified there is an update. If you like the build, great... if not, flash something else.
Click to expand...
Click to collapse
Yes, he will keep developing, but don't expect to see updates on this forum, which is a shame. His CM10 thread was actually the only reason I got on XDA.
Thanks for the update, Scott. Don't let the drama llamas get you down
Sent from my SGH-I997 using xda app-developers app
hattrickinc said:
Most of the people that posted just wanted insight on their issues. Personally, I posted there because I felt I wasn't getting any response in the Q&A thread.
I think we should learn from the miscommunication.
One of the bigger problems we faced was that the build thread was the most responsive place to get an answer, and the bugs people had weren't clearly documented somewhere (you can't tell someone to search 500+ pages, find a bug, match it to their build, etc) so they could find and know NOT to post about it.
Going forward, maybe we can have:
Build thread- keep updated on the status of the build
Bug thread- to review / report the current build bugs
Q&A thread- how do I rotate the screen, why is this doing that, etc
Thoughts?
Click to expand...
Click to collapse
For the most part I agree with you. Its why I probably pissed a bunch of people off defending the late comers and those that just don't know about logcats and such.
However, it was stated multiple times by not just Scott but the more senior and knowledgeable members that the 4.2 was going to have problems.
I agree searching through 1000 plus posts can be a daunting task and maybe I just don't have a life but I've done it for every ICS/JB rom I've flashed.. But I was there at the beginning of that development so it made it easier. But you didn't have to read more than 2 pages between warnings for the 4.2.
I'm on Scott's side on this one.
If nothing else click on the op's profile and just read all their posts.
Personally I think only devs should be allowed to post on a dev thread but I don't see that happening anytime soon.
Sent from my SGH-I997 using xda app-developers app
I agree. I think there should be a minimum post count of 100 and a requirement to agree to a separate 'contract' to post in dev. threads. I read dev threads to find out what's going on in development not the rubbish that appears in most dev threads. The infuse forums have been fairly tolerant of this kind of thing. Other forums on xda, much less so.
Sent from my SGH-I997 using xda app-developers app
Changelog
I think another part of the problem is that very little actual development discussion happens here. It seems that people release their stuff here, and respond to bug reports, but that's about it. You can learn a lot about Linux by reading the archives of the Linux Kernel Mailing List (LKML). It's not quite the same situation here, learning about android is much harder (i have yet to find an android equivalent for the LKML)
Anyway, Thanks for continuing development! Will you be posting a change log between releases? I just like to know what I'm flashing ahead of time
Thanks,
woody
Scotts just released CM10.1 on goomanager 12/10 build go check it out
Sent from my SGH-I997 using xda app-developers app
Scott,
Glad to see you will be still be developing. Will there be some type of change log somewhere that we can view? I agree with some of the past. 500 pages of posts to read/search is alot. possibly a better brake down would have keep people posting in the correct places. Also with the 4.2 merge MY opionion would have been to make a separate thread as the last 4.1.2 was stable and really usable as its still my current daily. If the items arent merged maybe it isnt a good idea to even make a realease unless its to a few beta testers. That way 100s of people dont whine and complain about known or dumb issues.
Either way keeep up the good work.
Not sure how it would be accomplished, but a good idea would be to remove all posts from the cm10 thread and only scott could post in it (updates/changelog).
I have no idea how feasible that would be though.
Many thanks to scott
Hi scott, I never felt the need to comment in your thread because I never had any problems with your ROM.
But now I feel the need to comment here to express my gratitude for all the hard work that you have put into this ROM.
Your ROM is the first one that I tried, and also the best one I've seen/used. I'm VERY glad that you will continue your work for the Infuse.
Again, I thank you for your work, and I will be looking forward to future updates!
UnhoIy said:
His CM10 thread was actually the only reason I got on XDA.
Click to expand...
Click to collapse
This^
hovin1988 said:
Hi scott, I never felt the need to comment in your thread because I never had any problems with your ROM.
But now I feel the need to comment here to express my gratitude for all the hard work that you have put into this ROM.
Your ROM is the first one that I tried, and also the best one I've seen/used. I'm VERY glad that you will continue your work for the Infuse.
Again, I thank you for your work, and I will be looking forward to future updates!
Click to expand...
Click to collapse
And this^
I generally just read through the thread reading peoples issues if i ran into one rather than post. Issues were always sorted out if i kept reading. But thanks for all your hard work in creating roms, I know i'd be really bad off without them :good:
I think the communication and forum issues are simply a result of using a forum for "developer collaboration". Then to top it off, many are using tapatalk, which has the most useless search feature ever. I've heard the argument that a proper browser should be used, but many just won't.
As long as a forum is used for xda development, it will continue to be more like a ROM forum than anything else intended without ridiculous amounts of moderation (even judicious use of temp bans without warning).
Forums are good for arguing lol. Bugtrackers are good for tracking bugs, especially since they are easy to police. If you want feedback as well, make a special category for that. Duplicates and invalid reports can be easily identified and marked as such. For all other forums(general, q&a, accessories, etc.) a forum makes sense to me. For the development forum, a forum, IMO, makes little sense.
If the forum format is used in order to foster community, fine. You can expect a lot of drama, arguing, complaining, and everything else that goes along with it.
Just my opinion. I could be completely wrong.
Sent from my SGH-I997 using xda app-developers app lol

Categories

Resources