Related
So I had always heard that we would see CM development ramp up after the 2.2 source was out. I went over to http://cmsgs.com/mediawiki/index.php?title=Main_Page to see how things were going. This place is almost dead except for git updates and a little irc discussion. I was thinking it may just be because so few of the developers on XDA know about CMSGS. Well its a project to put AOSP builds of cyanogen on SGS phones like the Vibrant. If you dont know about the project head over and stur up some conversation, and maybe some code.
Forum http://cmsgs.com/phpbb/
Twitter http://twitter.com/#!/CMSGSTeam
Wiki http://cmsgs.com/mediawiki/index.php?title=Main_Page
Building for the Vibrant http://cmsgs.com/mediawiki/index.php?title=Build_CyanogenMod_for_Samsung_Vibrant#Setup_Directories
The code https://github.com/cmsgs
On a serious note, I think everybody really does know about Cyanogenmod (CM7) and if they had the capabilities and want to do so, they would be helping. I knew about CM before I discovered XDA. Somebody correct me if I'm wrong, but from my understanding, the reason CM7 is a slow going process right now is that the source to the drivers have not been released... That is unless the latest source release contains those...
ahronzombi said:
So I had always heard that we would see CM development ramp up after the 2.2 source was out. I went over to http://cmsgs.com/mediawiki/index.php?title=Main_Page to see how things were going. This place is almost dead except for git updates and a little irc discussion. I was thinking it may just be because so few of the developers on XDA know about CMSGS. Well its a project to put AOSP builds of cyanogen on SGS phones like the Vibrant. If you dont know about the project head over and stur up some conversation, and maybe some code.
Forum http://cmsgs.com/phpbb/
Twitter http://twitter.com/#!/CMSGSTeam
Wiki http://cmsgs.com/mediawiki/index.php?title=Main_Page
Building for the Vibrant http://cmsgs.com/mediawiki/index.php?title=Build_CyanogenMod_for_Samsung_Vibrant#Setup_Directories
The code https://github.com/cmsgs
Click to expand...
Click to collapse
Do you have a vibrant? Stupid question I know but its confusing when you have Nexus One and G1 on you signature. Anyhow how do you make a signature lol sorry? Well hopefully more people help the dev thats porting CM7.
A good CM6 isn't even out yet. Hence I see the purpose for it since the source code is out. Who cares about some broke ass CM7. We will have to wait months if ever the source code comes out for gingerbread on the vibrant. I see no point trying to port the CM7 to the vibrant at all. I do see a lot of sense to get a nice clean running CM6, hence the post is a good one.
BlackVision said:
A good CM6 isn't even out yet. Hence I see the purpose for it since the source code is out. Who cares about some broke ass CM7. We will have to wait months if ever the source code comes out for gingerbread on the vibrant. I see no point trying to port the CM7 to the vibrant at all. I do see a lot of sense to get a nice clean running CM6, hence the post is a good one.
Click to expand...
Click to collapse
We don't NEED source for CM7. Considering almost no phones have Gingerbread source, they wouldn't even be working on CM7 like they are if this was a deal breaker. You know the saying "don't knock it 'till you've tried it"? Maybe you should adhere to this as CM7 actually runs pretty well on the Vibrant already.
Now, to respond to the OP. I realize a lot of people were expecting some change in development speed for CM7 with the release of source, but there was no reason for this. Nothing has changed or should change. The source we have now is barely applicable if at all to CM7.
Honestly, though, if you look at the list of bugs, it's not that long or severe. The only real non-issue issue is the complicated installation, which they have no reason to improve until they're satisfied with the rom.
MWBehr said:
Honestly, though, if you look at the list of bugs, it's not that long or severe. The only real non-issue issue is the complicated installation, which they have no reason to improve until they're satisfied with the rom.
Click to expand...
Click to collapse
Can you point me in the direction or post a "how to" to the installation of CM7?
kaizasoshi said:
Can you point me in the direction or post a "how to" to the installation of CM7?
Click to expand...
Click to collapse
Go to the i9000 android development forums, it will explain everything.
Sent from my SGH-T959 using XDA App
Or go to the Vibrant General section for some more CM7 info..
@dumdidum on twitter said he ordered a Vibrant so Im sure he will help port it to the Vibrant once he receives it.
they already started adding the vibrant to the source the other day but i been running it fine from the i9000 plus what scrizz said for the modem and a toggle headset widget
BlackVision said:
A good CM6 isn't even out yet. Hence I see the purpose for it since the source code is out. Who cares about some broke ass CM7. We will have to wait months if ever the source code comes out for gingerbread on the vibrant. I see no point trying to port the CM7 to the vibrant at all. I do see a lot of sense to get a nice clean running CM6, hence the post is a good one.
Click to expand...
Click to collapse
I think thats a good place to start, i would prefer CM6over any existing vibrant rom (sorry not a insult to existing roms)
If their were any dev's that really wanted CM on their Vibrant it would have been done by now or there is something that is really holding them back. I don't know why anyone would want to lose functionality for a little extra speed. Side by side CM7 on the Nexus S is almost identical to the Vibrant running BionixV, why would you want to give up video codec's and a better UI for that? I would love to get Bionix V on my Nexus over CM or stock Gingerbread any day.
I use to see Cyanogen as a god of android back when I had the G1. His ROM was the ONLY thing I ever put on my G1.
I know that the Cyanogen team really only does a lot with HTC handsets since HTC is AWESOME with giving out the source to their drivers. And I was so hoping to see it on my Vibrant, but in all honesty I've given up the dream of seeing a stable build for the Vibrant.
Samsung don't play nice like HTC with what sources they release so I know it's tough for CM team go get a 100% stable rom for Vibrant.
The devs we have here that do make roms for our phones are the greatest. Team Whiskey, Team Einherjar, Eugene, Master... They all do such great work and also calaborate and make my Vibrant so awesome and sleek. So honestly I am not holding my breath for a stable and easy to install CM Mod ROM for our phones. Tho I would like to see one, I'm totally happy with the ROMS we do have to pick from..
Anyways, Good luck to all of you devs who are working on porting CM over or working on an actual CM ROM for our phones.
But for now, I'm loving those ROMS we do have.
Ill help as soon as I can get a new motherboard for my pc
Sent from my SGH-T959 using Tapatalk
Im working on building a update.zip from CM source, but i cant promise ill succeed as there isnt a lot of documentation for this device due to the lack of people working on this branch of cyanogen. If i get a flashable update ill post it, maybe that will inspire someone who can actually dev and not just build existing source code.
Okay this is where im stuck, its a documentation issue look at http://cmsgs.com/mediawiki/index.php?title=Build_CyanogenMod_for_Samsung_Vibrant#Configure_Build
when i get to lunch cyanogen_vibrant-eng i get this error
Code:
build/core/product_config.mk:190: *** _nic.PRODUCTS.[[device/samsung/vibrant/full_vibrant.mk]]: "build/target/product/full_base.mk" does not exist. Stop.
** Don't have a product spec for: 'cyanogen_vibrant'
** Do you have the right repo manifest?
Im sure its a simple config fix, if someone can figure this out and update the code or the wiki we may have fixed the one part of the build process that scares devs away. Im too stupid to fix this
Moved of: Samsung Vibrant > Vibrant Android Development
To: Samsung Vibrant > Vibrant Q&A
Please put your questions to: Vibrant Q&A
Ill b up and running soon working on a vibrant specific build once I'm completely done with ToXic 1.0 =3
Sent from my SGH-T959 using Tapatalk
Hey Guys,
I have been wondering why hasnt any dev(s) setup CI anywhere? I see tons of devs doing constant checkin and daily even hourly build on different roms however the end users are stuck with having to install SVN tools download the source compile and create a build? Cant we automate this process using continuous integration where we create a build script that upon each commit/checkin a build script is kicked off. Compiles the new rom zips/signs it and published it to a host somewhere that the end users (us) can just download? I am sure this would save a lot of headaches and time for everyone. Also at part of continuous integration you can also do things like setup build verfication sets (usually unit tests) to verify nothing was broken in the rom before a publish happens. This would also help to increase the quality and reduce bugs in each build.
Thoughts?
Nooooo don't post in Dev, you will be trolled. And yea nice idea btw.
Sent from my PG86100 using XDA App
Where the link at? Really wanna try it man
Sent from my super 3d running Viper RC1.3
while a nice idea .. but wrong section ..
Anyways back on topic. I think there is a script to do this burning don't think it would be as extreme as every commit. The problem is is that devs don't just make one commit at a time. It could be several in 1 min. If so it could overload the buildbot. Its better to keep it nightly to we can test more at one time and we make sure the devs make the edits they want.
Sent from my PG86100 using XDA App
clark44 said:
Off topic but really dude? I see you posting the same **** in every thread in the dev section that doesn't belong. Just because u have that recognized developer status doesn't mean u can go around ripping on users. I'm a dev to you don't see me trolling these threads. Don't reply to this just read it.
Anyways back on topic. I think there is a script to do this burning don't think it would be as extreme as every commit. The problem is is that devs don't just make one commit at a time. It could be several in 1 min. If so it could overload the buildbot. Its better to keep it nightly to we can test more at one time and we make sure the devs make the edits they want.
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
Appreciate the feedback Clark. I know for a fact you can configure each CI tool differently perhaps an hourly instead of commit based would be more ideal? The goal of my suggestion was really three fold. To reduce the bugs in each build, To implement unit tests in each build that could kick off to verify the build and functionality ensuring nothing got broken in the last series of commits and to get signed builds that are more stable out to the community faster. Rather than having to rely on the end user to figure out SVN. I notice there are tutorials on using SVN in here. Wouldnt that be in the wrong section too? What does that have to do with direct developing? SVN is merely version control? Anyways I believed my thread was directly target to development and all ROMs especially those that have team collaboration. I am sorry that if people dont agree and feel that I started this thread in the wrong forum. However I did want to make sure that it was visible to developers so that they would see it and possibly think it over as in the long wrong I believe it would make there lives easier. However I am sure the flaming will continue....
I think this is a horrible idea. If you don't have the ability to learn to checkout and export an svn repository, than you shouldn't be playing with an experimental nightly build. You see all the people who have issue's with STABLE builds because of stupid things like loading too many apps into memory? Imagine how many stupid questions would flood the nightly threads if there was an automated nightly build.
DeMiNe0 said:
I think this is a horrible idea. If you don't have the ability to learn to checkout and export an svn repository, than you shouldn't be playing with an experimental nightly build. You see all the people who have issue's with STABLE builds because of stupid things like loading too many apps into memory? Imagine how many stupid questions would flood the nightly threads if there was an automated nightly build.
Click to expand...
Click to collapse
This man knows what's up.
I am considering buying the SGS2 very soon. I am going to root it but here is my question. If I wait to get pushed the ATT update to 4.0 ICS do I have to flash back to stock just to root it? I want to wait for the stock push of 4.0 and just wipe off the bloatware and not have to worry about custom ROMs etc. Thanks for the help.
Currently running captivate with cognition 4.5.3 froyo.
Sent from my SAMSUNG-SGH-I897 using XDA App
Re: Root sgs2 after ATT update to ICS
Sent from my SAMSUNG-SGH-I897 using XDA App
You should be able to root after the update. But we don't know yet for sure.
Way too early to tell. You aren't going to see an official AT&T ICS OTA update for many months - if the Captivate is any indicator, not for at least a year.
Just wait for a Rom to be made , im sure one will be as soon as the sources are avail... I stopped doing the Ota upgrades when i realized its easier to just change the Rom.... So root... imo
Entropy512 said:
Way too early to tell. You aren't going to see an official AT&T ICS OTA update for many months - if the Captivate is any indicator, not for at least a year.
Click to expand...
Click to collapse
I'm hoping ATT/Samsung push it sooner because it's still one of ATT's highest end phones.
Of course, this is just wishful thinking.
Sent from my A500 using xda premium
Reading this thread, suddenly triggering me asking this question, I don't know why I haven't asked before: is there any ongoing development for ICS ROM?
I assume most of the custom ROMs surface in here are Gingerbread based OS.
votinh said:
Reading this thread, suddenly triggering me asking this question, I don't know why I haven't asked before: is there any ongoing development for ICS ROM?
I assume most of the custom ROMs surface in here are Gingerbread based OS.
Click to expand...
Click to collapse
No source for ics yet so there is no development. Look in general forum there is a sticky talking about it. There is also Cm9 but it's not fully working yet on our device.
Sent from my SGH-I777 using XDA App
eep2378 said:
No source for ics yet so there is no development. Look in general forum there is a sticky talking about it. There is also Cm9 but it's not fully working yet on our device.
Sent from my SGH-I777 using XDA App
Click to expand...
Click to collapse
There is development
Sent from my SGH-I777 using XDA App
eep2378 said:
No source for ics yet so there is no development. Look in general forum there is a sticky talking about it. There is also Cm9 but it's not fully working yet on our device.
Sent from my SGH-I777 using XDA App
Click to expand...
Click to collapse
Google did release ICS source codes about a month ago, I'm sure you know that.
Alright, so only CM dev. team currently working on this then.
Thanks
votinh said:
Google did release ICS source codes about a month ago, I'm sure you know that.
Alright, so only CM dev. team currently working on this then.
Thanks
Click to expand...
Click to collapse
That's base platform source for Nexus devices with not a single bit of source for anything specific to the I9100 or I777.
You really need to educate yourself on what source has and has not been released, and what that source means and is used for, before posting crap like this.
Basically, I could spend a few hundred hours trying to port the 2.6.35.x drivers for Samsung-specific items to a vanilla Linux 3.0 kernel - only to have a halfassed buggy release ready after Samsung releases official ICS with kernel source for the I9100, which can be ported to the I777 in a matter of a few hours of work.
The CM dev team is not working on ICS for the I777 either - to get anything even working on the I9100 they had to resort to something they almost NEVER do, which is an initramfs repack of a binary kernel. Getting an I9100 binary kernel to work properly on an I777 is simply not possible - you can repack the initramfs all you want, the audio routing code will be different and so will the touchkey mapping code.
The only ICS development that will occur on the I777 prior to I9100 kernel source getting released (or an I777-specific leak showing up) is some basic reverse engineering efforts (mainly focused in audio routing), since the library swap Hellraiser uses can't be done with ICS (depends on audio blobs extracted from an I777 device.)
Entropy512 said:
That's base platform source for Nexus devices with not a single bit of source for anything specific to the I9100 or I777.
Click to expand...
Click to collapse
Did i ever mention about Nexus devices which running ICS, ehhh?
You really need to educate yourself on what source has and has not been released, and what that source means and is used for, before posting crap like this.
Click to expand...
Click to collapse
Wowww!!!
Just posted once sentence and being tagged with "crap like this"? LOL
By reading my English, do you understand that I just said Google has released ICS source codes? Did you see I am saying Google has released ICS source codes for I9100 or this specific i777, huh? Did you read and understand or just premature assumption?
Or you are telling me that you never know Google has release ICS source code?
Basically, I could spend a few hundred hours trying to port the 2.6.35.x drivers for Samsung-specific items to a vanilla Linux 3.0 kernel - only to have a halfassed buggy release ready after Samsung releases official ICS with kernel source for the I9100, which can be ported to the I777 in a matter of a few hours of work.
Click to expand...
Click to collapse
Are you the one who create Entropy512 DD kernel? If yes, every minute you spent is well appreciated, left alone a few hundred of hours.
If so, yes, you seem to be very smart in Android field but in life, learn to grow up and act nicely, politely to others. Get some love, kiddo.
The CM dev team is not working on ICS for the I777 either - to get anything even working on the I9100 they had to resort to something they almost NEVER do, which is an initramfs repack of a binary kernel. Getting an I9100 binary kernel to work properly on an I777 is simply not possible - you can repack the initramfs all you want, the audio routing code will be different and so will the touchkey mapping code.
Click to expand...
Click to collapse
Again, I don't know who is working on what so I asked. One of the poster mentioned about CM, so I just repeat it.
If they currently do it, great.
If they currently do not do it, it's ok.
I am just asking, 'cuz in B&N NOOKcolor forum, a lot of XDA dev. is WORKING on ICS ROM from ICS source code that released a while a go.
I thought XDA dev. in this room will also do the same.
The only ICS development that will occur on the I777 prior to I9100 kernel source getting released (or an I777-specific leak showing up) is some basic reverse engineering efforts (mainly focused in audio routing), since the library swap Hellraiser uses can't be done with ICS (depends on audio blobs extracted from an I777 device.)
Click to expand...
Click to collapse
Good too know.
I've learnt something.
Thanks
votinh said:
Did i ever mention about Nexus devices which running ICS, ehhh?
Wowww!!!
Just posted once sentence and being tagged with "crap like this"? LOL
By reading my English, do you understand that I just said Google has released ICS source codes? Did you see I am saying Google has released ICS source codes for I9100 or this specific i777, huh? Did you read and understand or just premature assumption?
Or you are telling me that you never know Google has release ICS source code?
Click to expand...
Click to collapse
Another poster said we were waiting for source.
You replied to him saying Google posted source over a month ago. Thus implying that you thought that Nexus platform source would actually be sufficient on its own to get our device running ICS - it isn't, it's nowhere close.
I'm sick and tired of repeated "WHERE'S ICS? GOOGLE POSTED SOURCE OVER A MONTH AGO!" posts.
Entropy512 said:
Another poster said we were waiting for source.
You replied to him saying Google posted source over a month ago. Thus implying that you thought that Nexus platform source would actually be sufficient on its own to get our device running ICS - it isn't, it's nowhere close.
I'm sick and tired of repeated "WHERE'S ICS? GOOGLE POSTED SOURCE OVER A MONTH AGO!" posts.
Click to expand...
Click to collapse
"Another poster" I assume you meant "eep2378, one that posted right above my "crappy post"?
Firstly, if eep not getting itchy, why you?
Secondly, I don't know what he meant about ICS for Nexus, and even if he meant that, he didn't spell out so I thought he meant the general ICS source code. In his next sentence, he actually mentioned about CM team working on it, even not fully function, w/o waiting for this specific phone ICS source code, so I thought he meant they, CM team are using the general source code, just like XDA dev. in B&N NOOKcolor room.
Thirdly, and if eep irritated about my post, I apologize him.
Now back to you, let's square and clear up all confuse, hardness.
You're a talented kid, good, keep it up. If you know something, teach us, I'm sure a lot of others will learn from you and quietly appreciate.
Be socialize with people around you, in real life or in cyber.
To the ICS related questions, if you don't want to answer, DO NOT answer, there's no one forces you to do so. There is no point to irritate about it.
votinh said:
"Another poster" I assume you meant "eep2378, one that posted right above my "crappy post"?
Firstly, if eep not getting itchy, why you?
Secondly, I don't know what he meant about ICS for Nexus, and even if he meant that, he didn't spell out so I thought he meant the general ICS source code. In his next sentence, he actually mentioned about CM team working on it, even not fully function, w/o waiting for this specific phone ICS source code, so I thought he meant they, CM team are using the general source code, just like XDA dev. in B&N NOOKcolor room.
Thirdly, and if eep irritated about my post, I apologize him.
Now back to you, let's square and clear up all confuse, hardness.
You're a talented kid, good, keep it up. If you know something, teach us, I'm sure a lot of others will learn from you and quietly appreciate.
Be socialize with people around you, in real life or in cyber.
To the ICS related questions, if you don't want to answer, DO NOT answer, there's no one forces you to do so. There is no point to irritate about it.
Click to expand...
Click to collapse
Ok let me try to clear up some confusion:
1) Nexus source code has nothing to do with I9100 or I777
2) I didn't mention anything about ICS for Nexus because(see #1) and this is the I777 forum NOT Nexus(another reason why I didn't mention it)
3)I mentioned CM9 because(RIGHT NOW) its the only thing that even approaches getting ICS on I9100 forget the I777. And Even Codeworkx(OP for CM9 aka Dev) is WAITING for ICS SOURCE to drop FOR THE I9100.
Only then, as Entropy said, are we able to get it working on the I777
4)I'm not "itchy" or irritated in the least and there is no need for an apology. Having said that I am fairly tired of reading posts about ICS source code being dropped/when are we getting ICS?/ Can ICS run on my I777?, etc.
Finally, ICS source code dropped FOR THE GALAXY NEXUS!! What does that mean for us?? SEE #1!!
@Entropy, I responded to you in another thread(in Q&A) Porting Bezke ICS KP8(yeah I know another one lol) regarding comments you made on Captivate and I9000 kernels being similar but I9100 and I777 not sharing the same similarities.
I'm sure you never went back to that thread, but didn't want bother you via pm
---------- Post added at 04:01 PM ---------- Previous post was at 03:44 PM ----------
Nick281051 said:
There is development
Sent from my SGH-I777 using XDA App
Click to expand...
Click to collapse
For the I777? Where?
I don't want to sound ignorant, but Samsung always releases the kernel source along with the ROM?
First,I'm sorry for my poor English.I just have a question about the HWA of cm10.As we all know,we have the su660's kernel source code,but we still can't have the HWA.Once I used the defy which used the old kernel but still could have the HWA.I know the defy uses other phone's drives,so why the A4 can't?Lg su660 has the same CPU as A4.Maybe I shoule be patient,but I really want to use chrome.The chrome is so fast and beautiful,and I really love it.What's more,can epinter post a thread which introduce the progress of building the new kernel?
There are way too many threads/posts on this already, one more thread is really not needed.
Everybody wants HWA, everybody is impatient and pushy about it, and that only produces countereffects. Be patient, quit asking, it'll happen when it happens. Or give it a shot yourself. We all have the same resources available.
Thread closed in light of the above statement.
When the jb kernel sources came out i was hoping development would speed up and attis would release a cm 10.2 build with jelly bean kernel but instead the speed of development has remained the same when jb kernel sources were'nt released.
And DONT give me crap devs are trying their best and they will release it when they want to a lot of people like me were keen on seeing are builds in cm10 and other builds progress faster when kernel soources for jb finally came out all am asking is devs such as attis plz try and boot with jb kernel and update cm 10.2 soon so our community can become lively again THANKS.
Sent from my HTC Desire X using xda app-developers app
This post means you don't follow atis112'work on github, just go there and you will find your reply.
xpirt
Wohohoh,
it's not your lost-big-amount of time...
Delete, report as spam...
Sent from my HTC Desire X using xda app-developers app
Well, this is a rather useless post isn't it? All you're doing here is begging for new builds once again, and even being a tad rude.
I'm sure atis works on it when he wants to, and since we aren't doing anything (except for the beloved neXus PRIME and prototype-U - sorry if I forgot others -) it's way more than enough.
And you say, "don't give me that **** about ETA etc." (Not the exact quote) don't you? Now, that most likely means you have been in touch with people saying this to you, probably because you also posted words like these on other threads. People would think you would've learned from that, but from looking at this I draw a rather different conclusion. And that's something that makes me a little bit sad.
I know you're a fan of atis112, and I know you're not trying to be rude in any way by posting this, but don't you think there are better ways of stimulating him to do what he does (even) better? Try donating, or if you're short on money, try getting a closer look into the source code and see if you could help him with doing what he's doing so amazingly good at this point.
Sent from my awesome fridge
And I'd like to remember that atis112 is building CM for him, because he wants to have it, then if he share his work with us is another thing and we have to be happy as he is the only one who can bring it us.
xpirt
Thread Closed
These kinds of threads are not useful and often lead to flame/trolling. Therefore they are not allowed on XDA.