Related
Before the galaxy s? Is there any hope for a pure gingerbread and it looks like the evo is off and running with it smooth as butter with a minor hitch with gps issues... not sure how that works, the galaxy s and nexus s are almost identical hardware wise.
Sent from my PC36100 using XDA App
Looks like a lot of their roms are AOSP (Android Open Source Project) based. This means they can take the direct source of Android and modify their roms to the Evo hardware. Correct me if I'm wrong but I don't believe anyone has built a good solid working rom for the Vibrant off of the AOSP source alone. We've been getting builds leaked from Samsung and modifying them to build the Vibrant roms you see now. I believe Team Whiskey is working on a AOSP rom and Cyanogen Mod is an AOSP rom that they are working on porting over to Vibrant. Master/Devs4Android released an AOSP clone. I believe someone else said they have Gingerbread working and they are just bug fixing at the moment.
gongonzabarfarbin said:
Looks like a lot of their roms are AOSP (Android Open Source Project) based. This means they can take the direct source of Android and modify their roms to the Evo hardware. Correct me if I'm wrong but I don't believe anyone has built a good solid working rom for the Vibrant off of the AOSP source alone. We've been getting builds leaked from Samsung and modifying them to build the Vibrant roms you see now. I believe Team Whiskey is working on a AOSP rom and Cyanogen Mod is an AOSP rom that they are working on porting over to Vibrant. Master/Devs4Android released an AOSP clone. I believe someone else said they have Gingerbread working and they are just bug fixing at the moment.
Click to expand...
Click to collapse
Thanks for the insight mate, appreciate it. Just interesting.
Sent from my PC36100 using XDA App
I would venture to say that the Evo is usually the first phone to have this stuff ported to it. It's a high demand phone to get the best ROM's on so it usually gets them first. Don't get me wrong, I love my Vibrant, and so does Team Whiskey so they're working on 2.3, they have it ported but it's experimental still, they'll let us know when it's working. But as far as CyanogenMod goes, they usually port to the Evo first.
Where is the download link for this rom? When I search "Evo 2.3" I don't get any vibrant roms.
Silly developers forgetting links
</sarcasm>
also keep in mind, once the Vibrant 2.2 source is put out the devs will have easier time porting 2.3 also
How's the battery life on this rom? Can I flash it with clockwork mod? Do I have to disable voodoo?
djquick said:
How's the battery life on this rom? Can I flash it with clockwork mod? Do I have to disable voodoo?
Click to expand...
Click to collapse
you have to flash mooseberrypie.zip in clockwork recovery first then enable voodoo or u'll soft brick it
boimarc89 said:
you have to flash mooseberrypie.zip in clockwork recovery first then enable voodoo or u'll soft brick it
Click to expand...
Click to collapse
Mooseberrypie is the best Rom for the Vibrant hands down. I hear they'll get honey comb running soon! haha brilliant.
Mooseberrypie bricked me. Anyone want to sign my Class Action Lawsuit petition? I have a lawyer, I promise
How is 2.2 source going to help with 2.3 code? That's like saying 2.1 source for our kernels helped us build a 2.2 build for our hardware.
eminembdg said:
also keep in mind, once the Vibrant 2.2 source is put out the devs will have easier time porting 2.3 also
Click to expand...
Click to collapse
Sent from my SGH-T959 using XDA App
Its funny when the witty comments just arent witty anymore.. i told my friend id get a bunch of trolls saying stuff like "does this wipe sd card" "do i need to disable voodoo"... its really old now, first person that ever did it got a chuckle... but i do agree that having 2.2 code prolly wouldnt help too much being its a porting...
Sent from my PC36100 using XDA App
What about my (soft bricked my pants joke )is that still good or?.....
simple answer is that its an htc phone, htc releases everything for their phones while samsung does not, though honestly I prefer my Vibrant to my G2
willsnews said:
What about my (soft bricked my pants joke )is that still good or?.....
Click to expand...
Click to collapse
Yes still good... and original
Sent from my PC36100 using XDA App
So we have been using the Mesmerize EC10 kernel in super clean... Does this release pave the way to a official release quality version of froyo for us? Pretty please devs?
http://ars.samsung.com/customer/usa...ID=2&PROD_SUB_ID=557&PROD_ID=690&AT_ID=364163
Sent from my SCH-I500 using XDA Premium App
bobloblaw1 said:
So we have been using the Mesmerize EC10 kernel in super clean... Does this release pave the way to a official release quality version of froyo for us? Pretty please devs?
http://ars.samsung.com/customer/usa...ID=2&PROD_SUB_ID=557&PROD_ID=690&AT_ID=364163
Sent from my SCH-I500 using XDA Premium App
Click to expand...
Click to collapse
ec10 source would...the official releases from sammy seemed to be followed by source a week or two later (or have been recently)
Hmm aren't the Mesmerize and Fascinate hardware identical? We couldn't use parts/all of this for something like Superclean?
If I had a twitter I would be spamming @SamsungJohn and the other Samsung accounts to release the source.... because until then this is (mostly) useless.
/sigh
I was hoping that we could grab some parts (most notably those that control sensor_server_yamaha) and fix some issues.
Well, I'll start hoping for the source.
As an aside, if this is mostly useless... what are the small uses it would have? Maybe I could actually be a productive community member for something =)
bobloblaw1 said:
/sigh
I was hoping that we could grab some parts (most notably those that control sensor_server_yamaha) and fix some issues.
Well, I'll start hoping for the source.
As an aside, if this is mostly useless... what are the small uses it would have? Maybe I could actually be a productive community member for something =)
Click to expand...
Click to collapse
the release isnt anymore useful then the leaks....its that samsung *usually* releases timely source code after a release...so this coming out...mean we're closer to source
Apparently they released source for the Mezmerize today.
I see all these devices getting ICS, hell even vibrant and captivate have a port, and the only 2 threads i saw that mentioned ICS being worked on, are no longer active in development, so whats the deal? ICS themes are cool and all but theme is a theme, i want the full ice cream goodness. Is there anyone currently working on a 4.0 ROM?
Yes, multiple devs are currently working on a port. I believe codeworx is getting very close.
Sent from my SAMSUNG-SGH-I777 using xda premium
Yes ours just hasn't been released yet
Sent from my SAMSUNG-SGH-I777 using XDA App
i'm not flaming although it will probably look like I am - why are people so impatient about ICS? I have never seen so many "where's ICS?" threads compared to the Gingerbread update, for example.
I agree however you can't blame android enthusiasts for being overly excited about the release of ics. Although gingerbread was a great release, ics is much more of a major release because of it basically merging gingerbread with honeycomb, making it unlike any other android release to date.
Sent from my SAMSUNG-SGH-I777 using XDA App
They're working on it with the I9100.
Personally, I'm waiting until there's a kernel source drop for the Linux 3.0.9 kernel for I9100 ICS - I'll start porting work then.
ICS ports based on 2.6.35 are interim hackjobs.
(yes, 3.6.35 was a typo)
Entropy512 said:
They're working on it with the I9100.
Personally, I'm waiting until there's a kernel source drop for the Linux 3.0.9 kernel for I9100 ICS - I'll start porting work then.
ICS ports based on 3.6.35 are interim hackjobs.
Click to expand...
Click to collapse
You mean 2.6.35.
Wrong. He means 4.6.35.
On topic. These ports are going to be like HP Touchdroids for a while I bet. Buggy.
nyydynasty said:
i'm not flaming although it will probably look like I am - why are people so impatient about ICS? I have never seen so many "where's ICS?" threads compared to the Gingerbread update, for example.
Click to expand...
Click to collapse
Because it's been a year since GB.
Not trying to sound impatient, I was following a couple deb's and saw that they had stalled/stopped development and couldn't find any other threads with active ics development. More curious to see if it's being worked on or waiting for my leaks
Sent from my SAMSUNG-SGH-I777 using xda premium
More leaks*
Sent from my SAMSUNG-SGH-I777 using xda premium
Mainly waiting for more leaks - It's luck of the draw whether a device's vendor-proprietary libraries will work with ICS or not.
They apparently got lucky with the I9000/Captivate, not so lucky with the I9100.
You have to keep in mind that it is EXTREMELY rare for there to be an AOSP device bringup to be completed in any reasonably functional form before an official vendor firmware for a given device (or at least a very similar device) becomes available.
cwc3 said:
Wrong. He means 4.6.35.
On topic. These ports are going to be like HP Touchdroids for a while I bet. Buggy.
Click to expand...
Click to collapse
Um, NO. Your wrong. 2.6.35 was a kernel for gb, and he was saying that all these ICS ports are coming with hacked gb kernels, they aren't even being released/leaked with the "real deal" ICS kernel.
Enzopreme said:
Um, NO. Your wrong. 2.6.35 was a kernel for gb, and he was saying that all these ICS ports are coming with hacked gb kernels, they aren't even being released/leaked with the "real deal" ICS kernel.
Click to expand...
Click to collapse
I'm fairly certain he was joking about my typo.
Entropy512 said:
I'm fairly certain he was joking about my typo.
Click to expand...
Click to collapse
If he was I apologize. If he was maybe next time leave an emoticon or a "lol" or something so we can know, there's just so many "know-it-all" noobs on this site as of late and its frustrating. Sorry for coming out of character everyone, #hijackover, #backontopic.
It looks like official CM9 builds are starting to come out again. . .
I tried to search for a definitive answer and came up empty. I know that we are not supposed to ask "when?" but I just wanted to confirm "IF" the HP Touchpad will be getting official CM9 Nightly builds.
I apologize if I should know this. . . I just couldn't find a definitive answer.
I am enjoying CM9 Alpha 2 right now. . . You devs Rock!!!
Jsorvik said:
It looks like official CM9 builds are starting to come out again. . .
I tried to search for a definitive answer and came up empty. I know that we are not supposed to ask "when?" but I just wanted to confirm "IF" the HP Touchpad will be getting official CM9 Nightly builds.
I apologize if I should know this. . . I just couldn't find a definitive answer.
I am enjoying CM9 Alpha 2 right now. . . You devs Rock!!!
Click to expand...
Click to collapse
Try here-
http://techerrata.com/browse/nightly_kangs/tenderloin
Yep... I know about the kangs. Just curious if official cm9 nightlies were in the future...
What are different between CM9 Alpha 2 ROM and kings ROM, it is come from different development group of people ?
hki_peter said:
What are different between CM9 Alpha 2 ROM and kings ROM, it is come from different development group of people ?
Click to expand...
Click to collapse
a kang, means stolen code. So it's a rom based on cm9 with tweaks. That's the short version.
Sent from my HTC Desire S using xda premium
Jsorvik said:
Yep... I know about the kangs. Just curious if official cm9 nightlies were in the future...
Click to expand...
Click to collapse
Dalingrin endorses these nightlies, thats official enough for me.
Sent from my DROIDX using Tapatalk
Safidk said:
a kang, means stolen code. So it's a rom based on cm9 with tweaks. That's the short version.
Sent from my HTC Desire S using xda premium
Click to expand...
Click to collapse
stolen code
If we are using kang rom it is safe ?
Kang doesn't mean stolen. You can't steal open source code...
Kang means it was compiled by someone that isn't part of the official team/the person who made the code & isn't officially supported. So like when people say "Self-Kang" it means that they made the code themselves, but it's not officially supported by CM.
[TSON] said:
Kang doesn't mean stolen. You can't steal open source code...
Kang means it was compiled by someone that isn't part of the official team/the person who made the code & isn't officially supported. So like when people say "Self-Kang" it means that they made the code themselves, but it's not officially supported by CM.
Click to expand...
Click to collapse
KANG does mean stolen code m8, it's a very old term, and it's not something specific to android or open source software.
I'll try to find a article for you.
Sent from my HTC Desire S using xda premium
This is from another forum:
This is the definition you would look for in Wikipedia Kang - A term used for stealing others intellectual property and claiming it as your own. (ie. When a developer uses another developer's work, and then publishes the end product as their own.)
Like building a cyanogen rom from source and making small edits and redistributing it. Not exactly as bad as it sounds like the definition suggests... sometimes, it it.
Sent from my HTC Desire S using xda premium
Or...why not just look here on XDA, in their WIKI, and see how XDA defines it?
http://forum.xda-developers.com/wiki/Glossary#Kang
Safidk said:
KANG does mean stolen code m8, it's a very old term, and it's not something specific to android or open source software.
I'll try to find a article for you.
Sent from my HTC Desire S using xda premium
Click to expand...
Click to collapse
As mentioned, you can't kang open source'd code.
You can, however, fail to attribute that code, and that's generally what kang'd refers to now.
[nothing personal, just incorrectly using kanged is starting to pet peeve me almost to the point of the rampant incorrect usage of bricked. using 'vector' by a layman (ie, non military tactician or graphic designer) to make things sound more sophisticated is a close 3rd]
Hey guys!
Yesterday I read an article about "CyanogenMod no longer delivers support for devices with snapdragons 1"
And as our device is a "cooper one", it seems we are not gonna make it..
Source 1: "CyanogenMod ya no entregará soporte para equipos con Snapdragon S1" - bitly.com/MCS7bU
Source 2: "CyanogenMod formally confirms ceased support for Snapdragon S1 devices past Gingerbread" - bitly.com/MCSGT5
And here is the official post of Cyanogenmod's Team (from Google+):
CyanogenMod 01/08/2012
CM 9+, N1 (and other S1 SoC)
The Nexus One, along with the other first generation Snapdragon devices (devices with the QSD8x50, MSM7x25, MSM7x27 and MSM7x27T SoCs), will not be supported beyond the CM 7.x (Gingerbread) branch.
We’ve been holding off on finalizing this, looking for ways that we could make this work and be happy with the release. Sadly, it never panned out, and we’ve decided that it’s time to stop our efforts.
The Nexus One in particular would have required a custom hboot to repartition the internal memory (which itself was limited to 512 MB, like most devices of that generation) and the proprietary libs available (from 2.3) would have required compromises in the CyanogenMod code that we are not willing to make. The wide variety of MSM7x2x(T) devices, on top of these problems, also have a complete lack of media libraries that are compatible with the new APIs introduced in ICS (video decoding and encoding, specifically). The pieces just aren’t there.
Does the capability to run ICS or Jellybean exist on these devices? Yes, with enough time, effort, and hacks it can be made to work. Do we feel the experience is worth all of that? No.
To measure our releases, we use the same subjective criteria as users do: “speed”, “jank”, “butter”, but also factor in user experience (UX) and other intangibles. However, beyond this is something that we can (and do) use as a ‘pass or fail’ mechanism, the Android Compatibility Test Suite. The CTS is used by device manufacturers to ensure that their changes to Android source do not break Android API, platform and other standards. This, in turn, brings stability to the Play Store for app developers. Breaking CTS would lead to a bad and inconsistent experience for app devs, which in turn would lead to a bad experience for you guys as users. If CyanogenMod was perceived to be blatantly violating CTS, developers could eventually blacklist CyanogenMod users from using their apps (or worse, Google could blacklist CyanogenMod from the Play Store altogether). No one would win by going down that path.
If, in the future, a solution is found that passes CTS, we will revisit the topic.
For users that are adamant about trying to run ICS and beyond, options exist. We are not going to recommend other builds however, as they are more than likely breaking CTS, and therefore our quality assurance standards as well. You can find them if you look in the usual places.
-The CyanogenMod Team
Edit The list of affected devices are as follows: blade, bravo, bravoc, buzz, c660, click, cooper, desirec, e510, e720, es209ra, espresso, hero, heroc, inc, legend, liberty, morrisson, motus, one, p500, passion, robym, s5670, supersonic, tass, u8150, u8220, z71, zero
Click to expand...
Click to collapse
Source: bitly.com/MCSZxf
So... What do you think ?...
Damnit...
Sent from my GT-S5830 using Tapatalk 2
How bout this? That is ICS
Shadow xD said:
How bout this? That is ICS
Click to expand...
Click to collapse
He means future support, that means future updates will take longer because now porting is needed to make it work.
The title is wrong.
You should say we won't get future support from Cyanogenmod.
AOSP still can be compile from source I guess.
Sent from my GT-S5830 using Tapatalk 2
galaxyace152 said:
The title is wrong.
You should say we won't get future support from Cyanogenmod.
AOSP still can be compile from source I guess.
Sent from my GT-S5830 using Tapatalk 2
Click to expand...
Click to collapse
How can I edit it ?....
EDIT>Go Advanced. Be more careful next time.
eagleeyetom said:
EDIT>Go Advanced. Be more careful next time.
Click to expand...
Click to collapse
ok, understood =/..
¬¬
We never had and never will have OFFICIAL CM9+ support. UNOFFICIAL builds are what we'll have to live on..
Is this just saying that we wont have official CM9/CM10 support (which we all knew)?
Or is it saying that we will no longer get support from them for CM7?
Sent from the cracked screen of my GALAXY Ace.
tomb20 said:
Is this just saying that we wont have official CM9/CM10 support (which we all knew)?
Or is it saying that we will no longer get support from them for CM7?
Sent from the cracked screen of my GALAXY Ace.
Click to expand...
Click to collapse
I think CM 7.2 cooper is the last rom they do for Gingerbread.....
I mean... No more Official Roms for Galaxy Ace
JuampyXnaker said:
I think CM 7.2 cooper is the last rom they do for Gingerbread.....
I mean... No more Official Roms for Galaxy Ace
Click to expand...
Click to collapse
We will get GB roms.
We just won't get official CM9/10 and support from them for the above.
Sent from my GT-S5830 using Tapatalk 2
Yup.. CM7.x is after which the support ends.
Cm7.3 ?
Sent from my GT-S5830 using xda premium
CoolCatGetHome said:
Cm7.3 ?
Sent from my GT-S5830 using xda premium
Click to expand...
Click to collapse
They've moved on from CM7, lol
King ACE said:
They've moved on from CM7, lol
Click to expand...
Click to collapse
Nope they are further developing cm7 for the devices wich dont get official cm9/cm10 support
Sent from my GT-S5830 using xda premium
CoolCatGetHome said:
Nope they are further developing cm7 for the devices wich dont get official cm9/cm10 support
Sent from my GT-S5830 using xda premium
Click to expand...
Click to collapse
That will be awesome as Gingerbread is best for the Ace.
ICS slows it down like hell!
galaxyace152 said:
That will be awesome as Gingerbread is best for the Ace.
ICS slows it down like hell!
Click to expand...
Click to collapse
agree, ICS+ was made for better devices than the ace.
Gingerbread works better for the ace.
tomb20 said:
Gingerbread works better for the ace.
Click to expand...
Click to collapse
and aosp GB works hell smoother.. even at this moment cm7 lags in front of aosp :silly::laugh:
cm7 may not see cm7.3 but it is alive for patches to existing system not further features
madman said:
and aosp GB works hell smoother.. even at this moment cm7 lags in front of aosp :silly::laugh:
cm7 may not see cm7.3 but it is alive for patches to existing system not further features
Click to expand...
Click to collapse
Yeah! I saw the quadrant for AOSP in Ace! It was some 2100 or something!