Related
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.
There is a similar thread in the Captivate section (posted by sixstringsg) so I thought I would bring one here. The purpose of this thread is to encourage people to make KANG builds of CM7&9 and provide a place for them to post links to their builds. KANGS may include code that is not fully tested or they may simply be clean, up-to-date builds straight from the repo... and thus, are lightly supported if at all. If you build KANGS... post them in this thread.
I have been building these KANGS (they really call them UNOFFICIAL's now ) for my wifes phone for a while now and thought it time to post some for you guys. I recently dropped CM7 in favor of taking the wife up to CM9. Most of the builds are "clean"... meaning that I haven't cherry picked any of the changes awaiting approval in gerrit HERE
If you are coming from a Samsung ROM wipe everything. If you are coming from CM7 or another ICS ROM, at least wipe cache, dalvik, and system. You may get away with not wiping data (I do mostly).
Flashing this KANG is an open admission that you hate your phone and are intent on bricking it. I accept no responsibility for any damage that you inflict upon your phone. Kangs from Androtransfer.com WILL download using the phones browser, but you may have to rename the file .zip from .htm before you flash. If you use Firefox or Opera for downloading it, it works properly. For some reason the stock Android browser and Chrome don't parse the link correctly.
Latest KANG... download from here
Flash the 4/29 gapps with CM9. Download from here
If you want to start building CM9 for epicmtd... GO HERE
...more to come later. I will add info about cherry picking, etc...
Once you have your build environment configured, here are a couple of things that I do.
Open the local_manifest.xml (located in .repo folder) adding the following line...
<project name="koush/proprietary_vendor_samsung" path="vendor/samsung" remote="github"/>
This will sync all the samsung proprietary files and basically allow you to make builds for a phone you don't have.
For the epic, I have added these lines...
<project name="CyanogenMod/android_device_samsung_epicmtd" path="device/samsung/epicmtd" remote="github"
<project name="CyanogenMod/android_kernel_samsung_victory" path="kernel/samsung/victory" remote="github"/>
This syncs the kernel source as the kernel is built in-line and is not prebuilt.
<project name="EpicCM/epictools.git" path="epictools" remote="github" revision="ics"/>
Currently epictools allows you to turn off the backlight of the capacitive buttons unless they are pressed. Could be nice if you are watching a movie in bed on your phone.
More details... HERE (github.com/epicCM)
Cherry picking details... coming soon
FIRST!
What's different in that build?
Sent from my SPH-D700 CM9 ANDROID 4.0.4
Zeinzu said:
What's different in that build?
Sent from my SPH-D700 CM9 ANDROID 4.0.4
Click to expand...
Click to collapse
My guess would be nothing... we have unofficials in the gnex forum... that the guy does just to get it out to people quicker... nothing special just faster than their build bot.
Zeinzu said:
What's different in that build?
Sent from my SPH-D700 CM9 ANDROID 4.0.4
Click to expand...
Click to collapse
That build is clean (no cherry picks) built with latest merges from the cyanogenmod ics branch.
so... unofficial "nightlies"?
Thanks for putting this up op
Sent from my SPH-D700
I updated OP to clarify why I posted this thread. Just as you said... to prevent 30 different threads of people posting KANG builds... this will be the ONE.
Since KANGs are ever changing, there is no reason to update the OP as the Kanger will post a link to his latest KANG near the end. We have the same type of threads going in Captivate and Crespo.
If this thread is deemed "not welcome" than by all means delete it. As I see it, interest in the epic is waning. I am merely trying to encourage.
This is intended as a KANG thread... not a thread for my specific kang. It is not the same as the beta 3 version. There have been merges since that ROM was built. Can I name them all? Nope.
lownox said:
This is intended as a KANG thread... not a thread for my specific kang. It is not the same as the beta 3 version. There have been merges since that ROM was built. Can I name them all? Nope.
Click to expand...
Click to collapse
OK to clarify you are saying this is newer than Beta 3 as it has merges not yet incorporated in the official CM9 thread and if anyone else makes a Kang they should just add it in a post? That part won't work. It will make it hard to find individual Kangs. If you can't maintain the OP with others' Kangs then I can stick in links, if everyone thinks this thread is useful and adds something for the Epic community.
Sent from my SPH-D700 using xda premium
I am happy to update the OP with links if other people start making KANGS. Most of the time they will be posting their builds to some central location and people reading the thread can simply follow the link, see what the latest build date is, and choose to download it or not.
My page, for example, says that if the build is anything other than a "clean" build I will note what has been cherry picked. Cherry picks aren't always stable and sometimes they even cause problems. Since there are no "nightlies" for CM9 epicmtd... Kangs are a way to be able to run the latest merged changes and maybe some cherry picks.
In my next build, I will include some cherry picks. All the forums here seem to run a little bit different. I really wasn't expecting the bit of harshness I got here. I guess I took for granted that everyone knew about Kangs (or Unofficial) builds and what they were.
legit rom!
A lot gets merged everyday. merged changes are here.
review.cyanogenmod.com
I am currently making a build with the following cherry picks... It will be building for a while. So TO BE CLEAR... will be a build with all current merged changes and four cherry picks associated with 2 overall changes...
Electrion beam animation
Option to adjust navbar glow animation duration
Here are links to the picks in gerrit. Take a look.
http://review.cyanogenmod.com/#/c/12959/
http://review.cyanogenmod.com/#/c/15578/
http://review.cyanogenmod.com/#/c/16183/
http://review.cyanogenmod.com/#/c/16184/
lownox said:
A lot gets merged everyday. merged changes are here.
review.cyanogenmod.com
I am currently making a build with the following cherry picks... It will be building for a while. So TO BE CLEAR... will be a build with all current merged changes and four cherry picks associated with 2 overall changes...
Electrion beam animation
Option to adjust navbar glow animation duration
Here are links to the picks in gerrit. Take a look.
http://review.cyanogenmod.com/#/c/12959/
http://review.cyanogenmod.com/#/c/15578/
http://review.cyanogenmod.com/#/c/16183/
http://review.cyanogenmod.com/#/c/16184/
Click to expand...
Click to collapse
I don't see cm7
Sent from my SPH-D700 using Tapatalk 2
lownox said:
[...]I really wasn't expecting the bit of harshness I got here. I guess I took for granted that everyone knew about Kangs (or Unofficial) builds and what they were.
Click to expand...
Click to collapse
Each device forum on XDA operates as it's own community. We have regulars. We have standards. We have issues we've ironed out throughout the device's lifetime.
"Kang" has generally been used to refer to stolen or leaked coding. Up until recently, it had been more of an insult to call someones rom a "kang." Terms like "unofficial" or "variant" likely would have been greeted with less suspicion. But, more specifically, you should always have a well stated OP with a clear purpose. Starting a thread by saying something like "here I will be posting official cm9 roms with no changes and any one can feel free to post theirs" is never a good idea. Especially since things can become gray-area when talking about CyanogenMod source.
Basically, you need a well-stated and well formatted OP defining what it is you're sharing and how it differs from the CM9 and CM7 threads we already have here.
The only thing I noticed is the phantom vm notification
Sent from my SPH-D700
I would like to add my 2 cents, or five, or ten, on this subject, and this being a public forum, there's nothing stopping me.
I don't really see how this thread is any different than a thread in the theme forum that has links to various theme's threads.
When I saw this thread it had been up for a while, so I didn't see how the OP was initially laid out, therefore I cannot speak on that matter, but I can say this: I feel that in its current state, the OP perfectly states the intent and design of this thread. Also, on a personal note, I'm very glad its here.
I won't say that interest in epic development is waning, but there's really no arguement that compared to a few months ago, there isn't near as much going on.
I also hope that this will encourage more devs to try their hand at ICS and CM based ROMs. I would love to see some slim ics or codename android jumpin off in this forum.
I really enjoy the epic forum and community, especially now, our forumm is well monitored and tight knit. But I also enjoy seeing new developers and new dev teams adding to the variety in our forum. This will never happen if we keep jumping on newcomers with a hostile attitude. I'm not saying anyone means to do so, but it does come off that way from time to time. This is my perspective, a member of this community for over a year, so imagine how someone new would take it.
I would like to personally extend my grattitude and a warm welcome to the epic community to the OP.
I'm sure most of us, if not all appreciate your presence.
Sent from my SPH-D700 using xda premium
Welcome to the Epic community OP:thumbup:
Sent from my SPH-D700 using xda premium
For those who followed the CM9 beta3 development cycle, we posted many test builds and received much helpful feedback toward improving beta3. We will soon post beta4-pre builds in the same fashion. Additionally, Team Epic is working on fixing some poor code quality issues in preparation for enabling official CM9 nightly builds in order to make this a more automatic process.
It seems many of the posters here are missing the latest Epic development news. If you follow +Epic CM and +CyanogenMod on Google+ you will know stuff often before it hits XDA.
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
I haven't been able to follow the D2 consolidation, then subsequent breakup by device again, but saw that apexqtmo commits on the CM12.0 branch are pretty infrequent. There was a commit on April 3rd, which makes me think it might actually be alive.
So my question is: Does CM12.0 build for apexqtmo currently? (I haven't updated my build environment since 4.4, so can't quickly test...don't really want to spend the effort if the answer is already a known "no")
(Obvious follow-on from somebody would be "if yes, what works/doesn't work?")
scotte9999 said:
I haven't been able to follow the D2 consolidation, then subsequent breakup by device again, but saw that apexqtmo commits on the CM12.0 branch are pretty infrequent. There was a commit on April 3rd, which makes me think it might actually be alive.
So my question is: Does CM12.0 build for apexqtmo currently? (I haven't updated my build environment since 4.4, so can't quickly test...don't really want to spend the effort if the answer is already a known "no")
(Obvious follow-on from somebody would be "if yes, what works/doesn't work?")
Click to expand...
Click to collapse
The short answer is 'yes', but there's some pretty big caveats.
The bare CM12 trees for apexqtmo are rather broken, and even TeamApexQ's repos currently audio is broken, but it does build. CM12.1, the answer is currently 'no'.
Magamo said:
The short answer is 'yes', but there's some pretty big caveats.
The bare CM12 trees for apexqtmo are rather broken, and even TeamApexQ's repos currently audio is broken, but it does build. CM12.1, the answer is currently 'no'.
Click to expand...
Click to collapse
Thanks for the info. Sounds like more than a quick weekend project (I was hoping it was "It works except we need to update the vold configuration" or something easy). I think I'll let the wife live with CM11 for awhile longer then.
Shame because it doesn't look like any of the lollipop builds are being updated at all. I wanted to get my feet wet with building them, but this is probably more than a starting project.
Development Forums are for developers to share their work and post their Roms and Mods.
Questions belong in the Q&A section.
Thread has been moved to correct section, please pay attention to XDA rules.
Removed For Lack of Initial TimeLine Knowledge And To Not Step On Toes
Reserved..
What's the point of this? Why you're sharing the ROM without my permission? Couldn't you just create a post in the LineageOS 12.1 thread with the link (instead creating the new thread - what I was going to do soon..-)?
At this point I'll release LineageOS 14.1 as-is tonight (and yes, I'll create my own thread - which was the initial idea.. -) because people doesn't seems to be able to wait for it.
Thanks for sharing my work (can we also say steal?) without my permission :good:
---------- Post added at 09:59 AM ---------- Previous post was at 09:46 AM ----------
btw,
12.3. Re-releasing other's works as your own is forbidden. The code that you release into the wild must have something beyond minor aesthetic changes that makes it better than the last. As this can be subjective, kang reports will be reviewed on a case by case basis. If you feel that your code has been kanged, please contact the Dev Relations team (listed below) if you cannot solve the issue amicably via PM. Please understand that you will be asked to provide evidence to substantiate your claim;
Click to expand...
Click to collapse
Rortiz2 said:
What's the point of this? Why you're sharing the ROM without my permission? Couldn't you just create a post in the LineageOS 12.1 thread with the link (instead creating the new thread - what I was going to do soon..-)?
At this point I'll release LineageOS 14.1 as-is tonight (and yes, I'll create my own thread - which was the initial idea.. -) because people doesn't seems to be able to wait for it.
Thanks for sharing my work (can we also say steal?) without my permission :good:
---------- Post added at 09:59 AM ---------- Previous post was at 09:46 AM ----------
btw,
Click to expand...
Click to collapse
Let me just clear the air here. Fisrtly, one cannot "steal" something that is openly, publicly and freely available on github. In regards to the legal mumbo jumbo you posted, makes 0 sense to me and means nothing, since that is not the case we have here. I never once re-released anything, nor said anything about taking credit for the work you did. I simply put the rom together from open source materials, just as anyone in the world can /could do and released something that was not built and released. Big differences there. Now, had I hacked your github and started building and releasing your private folders, then what you are talking about would be on par with what you are posting. Long story short, I found the source, built the rom and tested it. I then uploaded the Rom and was in the middle of making this Main post when I came across your cm12.1 post mentioning 14.1. I then tagged you out of mutual respect for your work and personal feelings so that I would make sure that I wasn't stepping on your toes. I now know your feelings and that I am stepping on your toes. Because I have respect for you and your work, I have no problem deleting this thread and the Rom. Just didn't make sense to me at the time that somebody had done all that work and released no rom, so I thought I would be nice and help people out. The better thing to maybe have done, for the benefit of others confusion, is to make the 14.1 thread ahead of time, even if it's blank until release. Silly one would have to read hundreds of pages of cm12.1 stuff to get the gist of what's going on with unrelated 14.1 stuff. I do Apologize for any confusion on my part and any bad feelings you may now harbor. The Rom is your work and now that I know the timeline of things, I'll back off and let you handle it. I will be focusing on getting out more recoveries to compliment your rom. The recovery kernel is built using your sources but the device tree for it was fully made by me, so no confusion there. Again, sorry for basically beating you to the punch of your own release. Like I said, had I not read the cm12.1 posts, I never would have had a clue to any of this. Hopefully you can accept my apologies, move forward and be friends...
PizzaG said:
Let me just clear the air here. Fisrtly, one cannot "steal" something that is openly, publicly and freely available on github. In regards to the legal mumbo jumbo you posted, makes 0 sense to me and means nothing, since that is not the case we have here. I never once re-released anything, nor said anything about taking credit for the work you did. I simply put the rom together from open source materials, just as anyone in the world can /could do and released something that was not built and released. Big differences there. Now, had I hacked your github and started building and releasing your private folders, then what you are talking about would be on par with what you are posting. Long story short, I found the source, built the rom and tested it. I then uploaded the Rom and was in the middle of making this Main post when I came across your cm12.1 post mentioning 14.1. I then tagged you out of mutual respect for your work and personal feelings so that I would make sure that I wasn't stepping on your toes. I now know your feelings and that I am stepping on your toes. Because I have respect for you and your work, I have no problem deleting this thread and the Rom. Just didn't make sense to me at the time that somebody had done all that work and released no rom, so I thought I would be nice and help people out. The better thing to maybe have done, for the benefit of others confusion, is to make the 14.1 thread ahead of time, even if it's blank until release. Silly one would have to read hundreds of pages of cm12.1 stuff to get the gist of what's going on with unrelated 14.1 stuff. I do Apologize for any confusion on my part and any bad feelings you may now harbor. The Rom is your work and now that I know the timeline of things, I'll back off and let you handle it. I will be focusing on getting out more recoveries to compliment your rom. The recovery kernel is built using your sources but the device tree for it was fully made by me, so no confusion there. Again, sorry for basically beating you to the punch of your own release. Like I said, had I not read the cm12.1 posts, I never would have had a clue to any of this. Hopefully you can accept my apologies, move forward and be friends...
Click to expand...
Click to collapse
Hi,
Yes, you're completely right there (my bad): you can't actually steal something that is public in the web (I'll try to keep my future work in private repos until it's stable then). I was just really pissed off to see someone shared the ROM that I was working on (so hard for almost 6 months) in a new thread without even waiting for me to allow you or something. But whatever, no offence here (I accept your apologies) and as I previously said (telegram) thanks for understanding my decision and thanks for deleting the ROM. I'll try my best to get stable 14.1 working as fast as possible and I'll release it once it's ready. If people really wants to try the beta of LineageOS 14.1 I'll create an special post in the 12.1 thread with all the stuff later.
About the recoveries I know you just used my kernel tree, I was talking about the device tree/vendor tree you used to build 14.1 (which are the ones I've been working on this months).
Regards and sorry for the confusion.
Hey Rortiz2.
Rortiz2 said:
If people really wants to try the beta of LineageOS 14.1 I'll create an special post in the 12.1 thread with all the stuff later.
Click to expand...
Click to collapse
That would make sense. If you do not want to publish your ROM yet fire at least a non-open beta to get the ROM faster and more stable. Let me know if I can support you here in any way.
I would love to be able to test lineage 14.1 on this device, I have been using 12 on it since it released