Database Users

What to do using unsupported Rom?

Hi,
What should I do if the rom I am using and really like has disappeared and now is unsupported?
I'm using an AOSP Froyo rom and I can't seem to find any others let alone one which everything works in.
Yes I'm using Cronos Froyo, and I'm an honest user who doesn't care much for xda forums politics.
I've read the comments that the moderators have written in the thread and whilst I understand what they have written, do end users really have to suffer because of a dispute between developers?
Yes I agree in principle that source should be released with the release, but don't other rom devs have a donators only beta testing section before general release for testing which also occurs before source code release? Feeyo as far as I'm aware takes no donations what so ever.
Also, I wonder if the xda moderators have consulted laywers about the GPL as it is a legal document and thus won't be as black and white as it seems. A lot of companies behave not dissimilarly to feeyo and survive the threat of any action.
Beyond this, hero users really owe a lot to feeyo for the couple of months before official 2.1 got released as he was the only dev to get 2.1 working properly with long lasting battery life.

plonkersaurus said:
Hi,
What should I do if the rom I am using and really like has disappeared and now is unsupported?
I'm using an AOSP Froyo rom and I can't seem to find any others let alone one which everything works in.
Yes I'm using Cronos Froyo, and I'm an honest user who doesn't care much for xda forums politics.
I've read the comments that the moderators have written in the thread and whilst I understand what they have written, do end users really have to suffer because of a dispute between developers?
Yes I agree in principle that source should be released with the release, but don't other rom devs have a donators only beta testing section before general release for testing which also occurs before source code release? Feeyo as far as I'm aware takes no donations what so ever.
Also, I wonder if the xda moderators have consulted laywers about the GPL as it is a legal document and thus won't be as black and white as it seems. A lot of companies behave not dissimilarly to feeyo and survive the threat of any action.
Beyond this, hero users really owe a lot to feeyo for the couple of months before official 2.1 got released as he was the only dev to get 2.1 working properly with long lasting battery life.
Click to expand...
Click to collapse
I believe he still releases in his forum - just do a google search

nope, it seems his account has been suspended on the domain, not good.

plonkersaurus said:
sing an AOSP Froyo rom and I can't seem to find any others let alone one which everything works in.
Click to expand...
Click to collapse
There's AOSP ROMs. Without even plugging my own, there's the Fusion project for a start.

Froyd and Fusion are Cyanogen based roms which I've tried and don't work so well for me.
I'd count them as Vanilla roms not AOSP

Dude. You might as well turn xda into thepiratebay.Breaking a software licence is illegal no matter if the software is proprietary or open source.
Sent from my HTC Hero using XDA App

plonkersaurus said:
Froyd and Fusion are Cyanogen based roms which I've tried and don't work so well for me.
I'd count them as Vanilla roms not AOSP
Click to expand...
Click to collapse
The only non AOSP thing about them is:
They include Google Apps
They include proprietary libs grabbed from the phone to make the phone work.
Guess what, that's what AOSP ROMs do too, the ones released here anyway, since they're largely unusable without Google Apps (Market, etc) and the libs needed to make the phone work.
If you want plain AOSP, you better have an ADP1, ADP2 or a Nexus One. There is no such thing as a pure AOSP Hero ROM.
What people mean when they refer to AOSP, is they yanked the git straight from Android and compiled it for X phone, adding in whatever apps along with the Google apps and the prop libs.
Cyanogenmod is also AOSP in that same sense. Only there's a ton of people working on the repo and fixing stuff that Android don't or haven't yet.
If you've run into a CM based ROM that doesn't work well for you then it's still down to the builder. Chances are if they made an "AOSP" ROM, it'd be even worse.

I'm actually a professional software developer.
The Hero community here, as it is, I would never contribute to, because I wouldn't want my work included into someone elses rom that they then take donations for (I would never ask for donations for my work) especially since there seems to be no pioneering development going on by themselves.
So I see feeyo as someone like me, but with a drive to get things working on the hero.
In my eyes he is a bit like a vigilante or I guess like Batman. What Batman does is illegal too you know.
Sometimes there is such thing as the lesser of two evils and the greater good.
He harmed no one doing what he did.

Hacre said:
The only non AOSP thing about them is:
They include Google Apps
They include proprietary libs grabbed from the phone to make the phone work.
Guess what, that's what AOSP ROMs do too, the ones released here anyway, since they're largely unusable without Google Apps (Market, etc) and the libs needed to make the phone work.
If you want plain AOSP, you better have an ADP1, ADP2 or a Nexus One. There is no such thing as a pure AOSP Hero ROM.
What people mean when they refer to AOSP, is they yanked the git straight from Android and compiled it for X phone, adding in whatever apps along with the Google apps and the prop libs.
Cyanogenmod is also AOSP in that same sense. Only there's a ton of people working on the repo and fixing stuff that Android don't or haven't yet.
If you've run into a CM based ROM that doesn't work well for you then it's still down to the builder. Chances are if they made an "AOSP" ROM, it'd be even worse.
Click to expand...
Click to collapse
Cyanogenmod roms change a lot more things than just needed to get android working properly and I'm not a huge fan of all the changes

plonkersaurus said:
Hi,
What should I do if the rom I am using and really like has disappeared and now is unsupported?
.....
Yes I agree in principle that source should be released with the release, but don't other rom devs have a donators only beta testing section before general release for testing which also occurs before source code release? Feeyo as far as I'm aware takes no donations what so ever.
.....
Beyond this, hero users really owe a lot to feeyo for the couple of months before official 2.1 got released as he was the only dev to get 2.1 working properly with long lasting battery life.
Click to expand...
Click to collapse
1... Switch to another ROM, or stick with what you have, they are your two options.
2... No, other devs do not have a "donators only beta testing section", and regardless if they did or not, I think you need to go and re-read all the info the mods have given about the GPL issue before adding your 2 pence worth.
3... I owe feeyo nothing. He may have produced ROMS, but contribute to the community he did not.
Sent from my HTC Hero using XDA App

plonkersaurus said:
I'm actually a professional software developer.
The Hero community here, as it is, I would never contribute to, because I wouldn't want my work included into someone elses rom that they then take donations for (I would never ask for donations for my work) especially since there seems to be no pioneering development going on by themselves.
So I see feeyo as someone like me, but with a drive to get things working on the hero.
In my eyes he is a bit like a vigilante or I guess like Batman. What Batman does is illegal too you know.
Sometimes there is such thing as the lesser of two evils and the greater good.
He harmed no one doing what he did.
Click to expand...
Click to collapse
Hahaha what. Being a developer doesn't mean you "get" the point of the GPL. Plenty of developers over at Microsoft don't "get" it. That doesn't make it any less valid.
In fact your entire post just screams "I do not understand open source development, what on Earth is wrong with people doing stuff themselves and hoarding it".
The "pioneering development" as you put it doesn't happen by individuals because it happens in groups. You know, lots of minds working towards a common goal.
Jesus on a bike.
EDIT: woah..
plonkersaurus said:
Beyond this, hero users really owe a lot to feeyo for the couple of months before official 2.1 got released as he was the only dev to get 2.1 working properly with long lasting battery life.
Click to expand...
Click to collapse
I missed this when I first read the OP. Hahaha no he wasn't. Battery life has to be one of the most done to death topics on these forums and do you know what? Your battery life is solely dependent on you the phone user, providing of course the developer or the cooker hasn't done something utterly retarded to the ROM that causes battery to run down.
Until Froyo was released, Cronos wasn't even a compiled ROM it was a precompiled Sense ROM and as such subject to all the whims of the HTC base that the rest of us were.
Oh and I don't owe him anything. Never used his ROM, never benefited from what he apparently gave back to the community (nothing). He owed me and whomever else asked him for it, source code, which happened to be the one thing he never once provided while being happy to make use of source code provided by others.

Hacre said:
Hahaha what. Being a develloper doesn't mean you "get" the point of the GPL. Plenty of developers over at Microsoft don't "get" it. That doesn't make it any less valid.
In fact your entire post just screams "I do not understand open source development, what on Earth is wrong with people doing stuff themselves and hoarding it".
The "pioneering development" as you put it doesn't happen by individuals because it happens in groups. You know, lots of minds working towards a common goal.
Jesus on a bike.
Click to expand...
Click to collapse
I didn't mention GPL anywhere in my post.
I mentioned that I wouldn't help this community due to the fact people would be accepting donations for what would be in part my work which I think is immoral.
That is what my post was about.
Plus I think you will find Linus wrote Linux by himself so individuals are capable of greatness.

plonkersaurus said:
Plus I think you will find Linus wrote Linux by himself so individuals are capable of greatness.
Click to expand...
Click to collapse
Re check your history. Linus did not write Linux by himself. He wrote the first kernel by himself. Linux wasn't truly born until he released it along with the source code and people started fixing it, writing drivers for it and writing coreutils/toolchains around it. It didn't approach anything like popular until it got x86 support and the kernel reached a level of maturity in the 2.0.x releases. Collaborative development/debugging. It's an amazing thing. Stunted quickly by the "I will not share" attitude that you're defending and supporting.
I am genuinely curious as to how you can guarantee that people will receive donations for your work. Or why you'd even care. My kernel source tree is used by others, I don't lose a wink of sleep over whether they get donations for their finished ROM or not, it doesn't matter.
Donations are just that, donations. They are not a fee. They are not someone taking someone else's work and then charging for it. They're something that an individual feels that they want to give to someone out of the kindness of their hearts as a thank you as well as the fact that donations are quite a rarity.
I got my first donation today. It'll buy me a few beers. It won't make me rich. I got it for my work on the kernel and my work on the Villain 2.2 ROMs. Have a guess how many people at Villain are now pissy that I got a donation and not the project itself. None. Have a guess how many GNU developers are now hand wringing themselves with pure fret because some guy got bought a beer for some work he did on their code. None.
You didn't have to mention the GPL in your post. The GPL is why these ridiculous threads keep springing up, it was the GPL and the failure to adhere to it, that got Feeyo canned.
People with your attitude toward community development have no place on these forums. Kindly take the door that has a Feeyo shaped hole in it.

plonkersaurus said:
I'm actually a professional software developer.
The Hero community here, as it is, I would never contribute to, because I wouldn't want my work included into someone elses rom that they then take donations for (I would never ask for donations for my work) especially since there seems to be no pioneering development going on by themselves.
So I see feeyo as someone like me, but with a drive to get things working on the hero.
In my eyes he is a bit like a vigilante or I guess like Batman. What Batman does is illegal too you know.
Sometimes there is such thing as the lesser of two evils and the greater good.
He harmed no one doing what he did.
Click to expand...
Click to collapse
If you don't want to share then Android is not for you.
And why the big deal about asking for donations. Its not free to run a site. And a donation is hardly mandatory, the clue is in the name, no-one was bent over and forced to do anything they never wanted to.
I have used Villain on and off since Feb and haven't donated a penny.
.... and Batman? Really? Yes he makes the decisions that no one else can, for the greater good, the bigger picture... he doesn't play hero just to boost his own ego.
Sent from my HTC Hero using XDA App

Hacre said:
EDIT: woah..
I missed this when I first read the OP. Hahaha no he wasn't. Battery life has to be one of the most done to death topics on these forums and do you know what? Your battery life is solely dependent on you the phone user, providing of course the developer or the cooker hasn't done something utterly retarded to the ROM that causes battery to run down.
Until Froyo was released, Cronos wasn't even a compiled ROM it was a precompiled Sense ROM and as such subject to all the whims of the HTC base that the rest of us were.
Oh and I don't owe him anything. Never used his ROM, never benefited from what he apparently gave back to the community (nothing). He owed me and whomever else asked him for it, source code, which happened to be the one thing he never once provided while being happy to make use of source code provided by others.
Click to expand...
Click to collapse
Ok, so you never used his rom. I did and it was leagues ahead of anything else at the time. It made our phones really usable with 2.1. I remember when it was first released it was in the top 5 threads for a week on the front page of xda so I'm sure I wasn't the only one to experience this.
Also, sometimes it's the way you ask for something. I never once saw you ask for the source code with a view to work with him on it, only to get access to it. I know you are going to spout GPL rules now but I would rather not provide them knowing they will be taken over and most likely I would not be included in development in a "team" way, and rather take the punishment when it came of being banned.

plonkersaurus said:
Also, sometimes it's the way you ask for something. I never once saw you ask for the source code with a view to work with him on it, only to get access to it. I know you are going to spout GPL rules now but I would rather not provide them knowing they will be taken over and most likely I would not be included in development in a "team" way, and rather take the punishment when it came of being banned.
Click to expand...
Click to collapse
My first four or five requests were incredibly polite. There were a plethora of polite request the first time he pulled this stunt too. My reason for asking was irrelevant. However my reason for asking for those particular sources, were twofold:
1: I didn't believe it.
2: If it was true then the community should damn well get access to it so we as a group can get it up to full working order so that EVERY ROM DEVELOPER can make use of it.
Taken over? What? I now don't believe that you're a developer, at least nothing outside pointing and clicking in a GUI based programming tool in some office somewhere, because you clearly have no idea of what collaborative development is. You cannot shut anyone, ANYONE, out of a GPL project, that's the whole frigging point. See my signature? Source code. Source code anyone can take and modify. Source code people are welcome to change, fix, port, patch and if they want to, submit a pull request so I can merge those fixes in.
Click the link. Follow the fork tree. Observe the magic as my changes move upstream to the original cyanogenmod + Hero kernel. Observe further magic as changes they make merge their way down into my kernel. Yeah I/we are really all about shutting people out.
Stop trolling.

plonkersaurus said:
Ok, so you never used his rom. I did and it was leagues ahead of anything else at the time. It made our phones really usable with 2.1. I remember when it was first released it was in the top 5 threads for a week on the front page of xda so I'm sure I wasn't the only one to experience this.
Also, sometimes it's the way you ask for something. I never once saw you ask for the source code with a view to work with him on it, only to get access to it. I know you are going to spout GPL rules now but I would rather not provide them knowing they will be taken over and most likely I would not be included in development in a "team" way, and rather take the punishment when it came of being banned.
Click to expand...
Click to collapse
You might be right, maybe they wouldn't have let him be in the team, maybe they would have. Who cares, they would have had to credit it to him either way, just as they credit help from other developers now.
The main point is that he wasn't willing to help push things forward. He wanted all the spotlight for himself.
Sent from my HTC Hero using XDA App

Hacre said:
Re check your history. Linus did not write Linux by himself. He wrote the first kernel by himself. Linux wasn't truly born until he released it along with the source code and people started fixing it, writing drivers for it and writing coreutils/toolchains around it. It didn't approach anything like popular until it got x86 support and the kernel reached a level of maturity in the 2.0.x releases. Collaborative development/debugging. It's an amazing thing. Stunted quickly by the "I will not share" attitude that you're defending and supporting.
I am genuinely curious as to how you can guarantee that people will receive donations for your work. Or why you'd even care. My kernel source tree is used by others, I don't lose a wink of sleep over whether they get donations for their finished ROM or not, it doesn't matter.
Donations are just that, donations. They are not a fee. They are not someone taking someone else's work and then charging for it. They're something that an individual feels that they want to give to someone out of the kindness of their hearts as a thank you as well as the fact that donations are quite a rarity.
I got my first donation today. It'll buy me a few beers. It won't make me rich. I got it for my work on the kernel and my work on the Villain 2.2 ROMs. Have a guess how many people at Villain are now pissy that I got a donation and not the project itself. None. Have a guess how many GNU developers are now hand wringing themselves with pure fret because some guy got bought a beer for some work he did on their code. None.
You didn't have to mention the GPL in your post. The GPL is why these ridiculous threads keep springing up, it was the GPL and the failure to adhere to it, that got Feeyo canned.
People with your attitude toward community development have no place on these forums. Kindly take the door that has a Feeyo shaped hole in it.
Click to expand...
Click to collapse
I think the problem here is your attitude, you seem to think you own the place. I am free to stay here as I wish as far as I know. I also don't believe you are reading my posts correctly as you seem to think I am against community programming which is further from the truth.
I never said I wouldn't share. I wouldn't share with you. I think community programming is great all things being equal. It seems to me that the hero community here is terrible right now and thus I wouldn't help it.
Getting people banned definitely isn't making you friends either. I honestly never saw you wanting to work with feeyo only to get at his work.
I would have no problem helping out trying to get android to work on the Xperia X1 and supplying my source code as that is a true example of people working together.

Hacre said:
My first four or five requests were incredibly polite. There were a plethora of polite request the first time he pulled this stunt too. My reason for asking was irrelevant. However my reason for asking for those particular sources, were twofold:
1: I didn't believe it.
2: If it was true then the community should damn well get access to it so we as a group can get it up to full working order so that EVERY ROM DEVELOPER can make use of it.
Taken over? What? I now don't believe that you're a developer, at least nothing outside pointing and clicking in a GUI based programming tool in some office somewhere, because you clearly have no idea of what collaborative development is. You cannot shut anyone, ANYONE, out of a GPL project, that's the whole frigging point. See my signature? Source code. Source code anyone can take and modify. Source code people are welcome to change, fix, port, patch and if they want to, submit a pull request so I can merge those fixes in.
Click the link. Follow the fork tree. Observe the magic as my changes move upstream to the original cyanogenmod + Hero kernel. Observe further magic as changes they make merge their way down into my kernel. Yeah I/we are really all about shutting people out.
Stop trolling.
Click to expand...
Click to collapse
That's not what I mean by shutting people out. I'm not trolling but replying to your false accusations.
You are also trying to personally discredit me by calling me a point and click GUI programmer which is below the belt. You know nothing about me.
What I mean is, working together as these roms are virtually the same project is about communicating. Something that would not have happened and does in a real collaborative effort.
I'm sick of this thread and having to defend myself because you fail to understand what working together really means. And no it's not just following rules. It's obvious you aren't a professional programmer. People skills and management are just as important as being able to program and that is the point I am trying to get at.

I think you've formed your opinion and regardless of how many times Hacre blows your point out of the water, your not going to be swayed are you. He shouldn't even have to explain himself to you, every point had been covered in the other fan threads already.
Sent from my HTC Hero using XDA App

Devs, Please don't hide your Known Issues

I really don't want this to come across wrong, but I just have to say it.
Developers, I appreciate all your hard work. I understand this is all beta/test/etc. I understand it is free of cost, even to those who did donate to one dev or another. You do it because you want to, not because you have to.
But please, for the love of all that's good - keep an updated list of Known Issues!
It sucks having to read 50 pages of posts to try to figure out if a particular release is reliable or not, to find out if there's a key feature broken or buggy. What makes it worse is you can't tell when reading these threads which users are on which release, because many still post issues after they've been resolved. Others post things that aren't really "issues" but user error.
You know what your issues are, you read the threads and you fix the issues. But trying to find a decent rom to flash is very, very difficult when your OP says "No known problems" and the thread that follows show that to be very untrue. It generates a lot of extra posts with people posting things you already know about, and it generates a lot of bad will when someone flashes something only to find that there are a number of game breaking issues.
All it takes is to update a post, say #2, in your thread, with KNOWN ISSUES. Once you confirm a bug, whether you intend to fix it on your next release or not, add it to that thread. It helps you, as a dev keep track of the bug, and it helps potential downloaders know what bugs have been confirmed and make an educated decision as to whether they want to install your release.
Hiding known issues is something I don't think anyone does intentionally, but it feels that way sometimes. It feels like devs are in a popularity contest, and any admission of flaws in their particular ROM is a weakness. Well, to tell the truth, I and many others are sick of installing something that was CLAIMED to be working perfectly, only to have glaring problems that have been there for many versions.
For a civil and productive development community. Please. Be honest with your known issues. It will go a long way in building trust with the people who you're providing ROMs to, and will mean fewer posts for YOU to wade through of users reporting known issues, without having read 500 posts first.

I have a hard time believing that most devs actively hide them. Most of the time it's probably just a bit of laziness. But, yes, it would be helpful when comparing roms if the descriptions had a well-maintained list of active bugs.

Since the developers here are NOT getting paid (NO your $20 donation is not sh*t for the time it takes to make one of these roms), yes WE will have to bear the brunt of testing these roms out and letting them know what bugs if any are in them
The other issue is the people flashing these roms, coming from Eugene's to Whiskey to the ASOP roms may generate some ghosts in the software that the developers cannot duplicate themselves. I know that when I went with the TW 2.2 roms I had plenty of issues, more issues than I have had even when I was stock. Odining back to stock and reflashing the 4.2 TW fixed ALL my problems. Dont know what caused it but since I have flashed a couple of roms prior to that (no problems), I will assume there were some ghosts in my system. This is an example that unless a TW team member is holding MY phone and working on it, they may not be able to duplicate

They don't care to list them. It's beneath some of them.

Maybe AirBus should list "midair exploding engines" as a known issue too...
kponti said:
Since the developers here are NOT getting paid (NO your $20 donation is not sh*t for the time it takes to make one of these roms), yes WE will have to bear the brunt of testing these roms out and letting them know what bugs if any are in them
Click to expand...
Click to collapse
+1. Hell, at work I run a $100,000.00+ software suite and even that company won't do what the OP suggests!

If you have a problem with them stop using their roms go back to stock and see how much better theirs is even with a few bugs, not one of you has any right to complain. They do damn good work for free with some donations that do not come close to what they should be paid for it but they do not whine at all.

The problem I find is the "spammy" and useless comments average and pretentious users make which is both hard for the developer and the end user to read the threads. A dev releases a ROM and there is a guaranteed "Oh I can't wait to flash this" comment that will pop up. And there are some issues that are minor and are sometimes not related to the release that are posted and some pretentious loser who extends his ego by trying to make simple matters complicated. This forum didn't much of this problem before and I could quickly flash ROMs easily since I could clearly grasp the status on the ROM project.

I wish they would start a new thread with new releases. It's a pain to try to read through a 500 page thread, and you comments about this or that, and you have no idea which version the person is talking about. I gave up on custom roms and just using the leaked tmo 2.2, thanks for that Eugene

kponti said:
Since the developers here are NOT getting paid (NO your $20 donation is not sh*t for the time it takes to make one of these roms), yes WE will have to bear the brunt of testing these roms out and letting them know what bugs if any are in them
The other issue is the people flashing these roms, coming from Eugene's to Whiskey to the ASOP roms may generate some ghosts in the software that the developers cannot duplicate themselves. I know that when I went with the TW 2.2 roms I had plenty of issues, more issues than I have had even when I was stock. Odining back to stock and reflashing the 4.2 TW fixed ALL my problems. Dont know what caused it but since I have flashed a couple of roms prior to that (no problems), I will assume there were some ghosts in my system. This is an example that unless a TW team member is holding MY phone and working on it, they may not be able to duplicate
Click to expand...
Click to collapse
A $20 donation is not worth the risk of bricking a $550 phone just because they got "lazy" and didn't notify donators/downloaders of [a] potentially show-stopping issue.

Posted a new Thread in Dev section for the purpose of reporting issues. So if you have an issue please shoot it to me and I will post it in that thread.
Update: Here is the link for the WIKI page.
http://forum.xda-developers.com/wiki/index.php?title=Samsung_Galaxy_S_SGH-T959#ROMs

swehes said:
Posted a new Thread in Dev section for the purpose of reporting issues. So if you have an issue please shoot it to me and I will post it in that thread.
Click to expand...
Click to collapse
You are in a heap of trouble, a lot of people don't read, and you are gonna get 1000000000000000000000000000000000000000000000 repeats of the same issue.
"OMG! MY SD CAR DONES"T MOUNT< HELP ME!11!!111"

chui101 said:
I have a hard time believing that most devs actively hide them. Most of the time it's probably just a bit of laziness. But, yes, it would be helpful when comparing roms if the descriptions had a well-maintained list of active bugs.
Click to expand...
Click to collapse
The issue here is really that a forum is not the ideal place to manage software releases. A list of bugs emerges from community testing, but there's nowhere to "post" that list of issues, or attach it to a specific release. Since there's no way for the community to add such documentation, it falls on the ROM builder, who probably has other priorities.
This kind of project could be well served by using a real software project management software solution, such as say google code, which has an issue tracker and other useful features. But XDA does already give us a better tool than the forum - the XDA wiki!
I wish people would use the XDA wiki more extensively. This would be a good place to keep updated documentation such as this, without requiring the OP to keep a forum post updated with the latest findings. All the OP needs to do is link to the wiki page, and other people can help maintain it.

OK. Looking into Google Code.
(Update) So looking into the Google Code. What Licensing agreement are the ROMs under? Is it GPL v2 or v3 or another license?

swehes said:
OK. Looking into Google Code.
(Update) So looking into the Google Code. What Licensing agreement are the ROMs under? Is it GPL v2 or v3 or another license?
Click to expand...
Click to collapse
Depends on the project. The Linux kernel is GPLv2, so any kernels fall under that license. AOSP as a whole uses both GPL and apache code.
The issue with ROMs is that unless they're AOSP derived (like cyanogenmod) they often include binaries for which the license situation is murky at best, so google code isn't really an ideal fit for a "ROM" that's only ever released as a binary.
Really I was throwing google code out there as a well known example, there are tons of other ways to track issues. There are dedicated issue tracking systems such as trac, bugzilla, etc, but they require hosting. Most of the freely available hosted services require that you're running an open source project, which isn't necessarily true for the ROMs here.
IMO a serious project could very well benefit from such tools, but just using an XDA wiki page which community members can freely update is a great first step.

So looked into the Wiki for the Vibrant and have updated some information. Let me know what you guys think. Is this the way to go?
http://forum.xda-developers.com/wiki/index.php?title=Samsung_Galaxy_S_SGH-T959#ROMs

swehes said:
So looked into the Wiki for the Vibrant and have updated some information. Let me know what you guys think. Is this the way to go?
http://forum.xda-developers.com/wiki/index.php?title=Samsung_Galaxy_S_SGH-T959#ROMs
Click to expand...
Click to collapse
Not to be the "Spelling Nazi", and I am not even sure if you can change it, but it is "Kernel" not "Kernal". Also, the Dev on Team Whiskey is Sombionix, not Symbionix.
Otherwise, that looks like a great idea, and possible way of tracking things!
EDIT - I guess I could go ahead and make those tweaks, with it being a wiki and all couldn't I....
EDIT EDIT - Fixed it.

Stargazer3777 said:
Not to be the "Spelling Nazi", and I am not even sure if you can change it, but it is "Kernel" not "Kernal". Also, the Dev on Team Whiskey is Sombionix, not Symbionix.
Otherwise, that looks like a great idea, and possible way of tracking things!
EDIT - I guess I could go ahead and make those tweaks, with it being a wiki and all couldn't I....
EDIT EDIT - Fixed it.
Click to expand...
Click to collapse
Thanks. On both accounts.

Maybe this should be a post to Microsoft
To quote "there are known, unknowns and unknown, knowns and and even sometimes unknown,unknowns............but.........
Developers ----develop they do not become a bookkeeper of their development.........that is coordinating work...........good luck getting any developer in ANY Specialty to do that............. reporting bugs........
---Maybe this should be a post to Microsoft---

N8ter said:
A $20 donation is not worth the risk of bricking a $550 phone just because they got "lazy" and didn't notify donators/downloaders of [a] potentially show-stopping issue.
Click to expand...
Click to collapse
I have yet to see a REAL (completely dead) "bricked" vibrant from flashing a released Rom alone. I have seen a lot of user error cause boot loops or "soft-bricks" & HWL phones become unflashable because the end user didn't take the time to research though. As far as devs being "lazy" I dont really see that when the developer is coming here for us to tell him what else we find wrong. They are coding, you flash, you report back with a logcat. This is how development is made to my understanding. If ppl are to lazy to JUST do this then why shouldn't the developer discount long winded post or something they are not experiencing? If they know there is a bug its in the OP.
If you guys can change the interwebz & how 500 post per update are made completely useless please feel free to do so....

swehes said:
So looked into the Wiki for the Vibrant and have updated some information. Let me know what you guys think. Is this the way to go?
http://forum.xda-developers.com/wiki/index.php?title=Samsung_Galaxy_S_SGH-T959#ROMs
Click to expand...
Click to collapse
I think it's a pretty awesome start for sure
As a matter of personal taste, I think having an individual wiki page per ROM (with the known issues and other detailed info) might be nice, although I'm not sure what the policy on new pages is with the XDA wiki.
Speaking from professional experience, the most challenging aspect of any documentation system is always convincing people to use it. It's great to compile the information, but unless ROM builders and devs post a link to the wiki in the forum threads nobody will ever see it. Having good, community based documentation is a benefit to everybody though, so hopefully people will recognize the utility of it and encourage its growth!

Cyanogenmod 7 Development Thread - Take 2

DEVS! Would it be possible to use a FroYo Kernel for CM7 like the Droid X Developers did?
DON'T TROLL! IF YOU DO, THE MODS WILL SEE IT AND BAN YOU!
As we all know, the last Thread that involved CM7 Development for the Epic was closed because people got Off-Topic, so I decided to start this one just so we know where developing is going. This is just for those people who don't know how to read Github or don't want to check it every 3 seconds, and are okay with waiting a week for getting an update.
Please PLEASE PLEASE, DO NOT ASK FOR ETA'S! I know that someone will ask, but seriously. DO NOT ASK. It's annoying as hell. If the developers know when a release would happen, they'd tell us. Trust me, they would. But developing for our phone is difficult.
They can't Port something from the Vibrant or the Captivate because their GSM Phones and we're CDMA, meaning we use different signals or some crap like that. But I think it means that 3G and Calls and all of that would be hard to work on, not to mention 4G.
4G is an issue because it's something not many phones have, especially in the Galaxy S line. Remember that we're one of the original Galaxy S Phones, so we have it, and the Captivate, Vibrant, and Fascinate don't. This makes stuff even harder because then the developers have one more thing on their list to work on, that they never had before.
From what I saw last time, nullghost was trying to port the Nexus S 4G .35 Kernel. This is a Gingerbread Kernel. Remember that the Nexus S 4G is a STOCK GINGERBREAD phone, with no TouchWiz. The Kernel is just the thing that connects the software with the hardware, so this might also be hard because we have a keyboard and most other phones don't (I don't know if this really effects it, but from my prior experiences from Android, it does).
Lets say the Kernel gets Ported. The NS4G has 4G (no kidding). Don't quote me, but I think that'd get the camera working because obviously the camera is a piece of hardware, that should get 4G working because the the NS4G has it. GPS should probably work, although I'm sure that works if you use the GPS Status Method, and I'm not too sure about MMS and what the issue is with that.
Now, when I check Github, it appears as if the developers have stopped working? I mean, props to them for all they've done for us, but if I'm reading github properly, it seems as if they've taken a break (please correct me if I'm wrong).
Really. The only big problem we have is with people who won't stop asking for ETA's. Please, just don't ask. You'll cause more problems then you will help if you do get a reply.
And if anybody has any questions about the CM7-A4, feel free to ask them here. You should however check the closed Thread. It might be locked, but there's a reason it's not deleted, you can still read it, so please do.
Remember, no asking for ETA's. Just don't do it. Any questions, check the older Thread and in a few days or weeks what should be this Thread. Also check Github. No ETA's. Keep this on task, no gangster stuff. Kthnxbye.

Original Android <3ers! said:
DON'T TROLL! IF YOU DO, THE MODS WILL SEE IT AND BAN YOU!
As we all know, the last Thread that involved CM7 Development for the Epic was closed because people got Off-Topic, so I decided to start this one just so we know where developing is going. This is just for those people who don't know how to read Github or don't want to check it every 3 seconds, and are okay with waiting a week for getting an update.
Please PLEASE PLEASE, DO NOT ASK FOR ETA'S! I know that someone will ask, but seriously. DO NOT ASK. It's annoying as hell. If the developers know when a release would happen, they'd tell us. Trust me, they would. But developing for our phone is difficult.
They can't Port something from the Vibrant or the Captivate because their GSM Phones and we're CDMA, meaning we use different signals or some crap like that. But I think it means that 3G and Calls and all of that would be hard to work on, not to mention 4G.
4G is an issue because it's something not many phones have, especially in the Galaxy S line. Remember that we're one of the original Galaxy S Phones, so we have it, and the Captivate, Vibrant, and Fascinate don't. This makes stuff even harder because then the developers have one more thing on their list to work on, that they never had before.
From what I saw last time, nullghost was trying to port the Nexus S 4G .35 Kernel. This is a Gingerbread Kernel. Remember that the Nexus S 4G is a STOCK GINGERBREAD phone, with no TouchWiz. The Kernel is just the thing that connects the software with the hardware, so this might also be hard because we have a keyboard and most other phones don't (I don't know if this really effects it, but from my prior experiences from Android, it does).
Lets say the Kernel gets Ported. The NS4G has 4G (no kidding). Don't quote me, but I think that'd get the camera working because obviously the camera is a piece of hardware, that should get 4G working because the the NS4G has it. GPS should probably work, although I'm sure that works if you use the GPS Status Method, and I'm not too sure about MMS and what the issue is with that.
Now, when I check Github, it appears as if the developers have stopped working? I mean, props to them for all they've done for us, but if I'm reading github properly, it seems as if they've taken a break (please correct me if I'm wrong).
Really. The only big problem we have is with people who won't stop asking for ETA's. Please, just don't ask. You'll cause more problems then you will help if you do get a reply.
And if anybody has any questions about the CM7-A4, feel free to ask them here. You should however check the closed Thread. It might be locked, but there's a reason it's not deleted, you can still read it, so please do.
Remember, no asking for ETA's. Just don't do it. Any questions, check the older Thread and in a few days or weeks what should be this Thread. Also check Github. No ETA's. Keep this on task, no gangster stuff. Kthnxbye.
Click to expand...
Click to collapse
i disagree with the dont ask about ETA.
I think that if you announce that you are working on something then people have a right to ask for an eta.
People should be informed as to what is going on both good and bad...
While it can get to be like are we their yet thing... but then i would say you should have never announced something to begin with.

There's a reason I made that rule. If you look at every other CM7 Thread for the Epic, their closed because of ETA's. Don't even attempt to question what I have posted, it's based on fact.

daddy_droid said:
i disagree with the dont ask about ETA.
I think that if you announce that you are working on something then people have a right to ask for an eta.
People should be informed as to what is going on both good and bad...
While it can get to be like are we their yet thing... but then i would say you should have never announced something to begin with.
Click to expand...
Click to collapse
In other news....
I heard the Droid X has Cyanogenmod mostly working with it's stock 2.2 kernel. I wonder what all the Droid X devs had to do to make it work.
With the 2.3 kernel source being so close to fruition, it probably isn't worth it to give their method a try but if samsung can't get gingerbread working in the next couple of months it might be worth a shot.

And queue take 3... omfg, when will people learn, this is not to debate ETA.

Original Android <3ers! said:
There's a reason I made that rule. If you look at every other CM7 Thread for the Epic, their closed because of ETA's. Don't even attempt to question what I have posted, it's based on fact.
Click to expand...
Click to collapse
really not allowed to talk about that? Since when can someone else take away my free speech rights to ask when something is gonna to be released? If you dont want to answer a question for eta then just dont reply to it. After all no one is making you reply to anything.

If you HAVE NOTHING TO SHARE DONT POST IN DEVELOPMENT.

I'm trying to be honest with you and save you from being flamed. Did you even read the first post? The devs don't have the kernel source for the Epic 2.3.3 or beyond, nor do they have it for the Nexus S 4G, so until then, they have to stop developing because they cannot do ANYTHING without it. So an answer to an ETA is never.

lynyrd65 said:
In other news....
I heard the Droid X has Cyanogenmod mostly working with it's stock 2.2 kernel. I wonder what all the Droid X devs had to do to make it work.
With the 2.3 kernel source being so close to fruition, it probably isn't worth it to give their method a try but if samsung can't get gingerbread working in the next couple of months it might be worth a shot.
Click to expand...
Click to collapse
I think this would be a good idea while we wait for the Kernel source actually...

nullghost mentioned that CM6 would be in the same state as CM 7. Idk why, but yea.

No no, we're saying use the FroYo Kernel for CM7!

Original Android <3ers! said:
No no, we're saying use the FroYo Kernel for CM7!
Click to expand...
Click to collapse
Oh damn it, reading comprehension! My bad, my bad, continue the thread. Devs: could this also be possible?

Darkshneider said:
Oh damn it, reading comprehension! My bad, my bad, continue the thread. Devs: could this also be possible?
Click to expand...
Click to collapse
No.
Sent from my SPH-D700 using XDA App

Original Android <3ers! said:
No no, we're saying use the FroYo Kernel for CM7!
Click to expand...
Click to collapse
Fail. We've attempted this. A lot of the updated proprietary modules from gb and necessary for gb require updated kernel drivers which are present in .35 and would require more work to backport than what we're doing now.
We also do have NS4G source, we kanged everything we could from it.
We are lacking proper regulator sauce along with the branched victory gpio assignments which we can only fire blanks at right now since they have a completely new naming scheme in the aries(.35) tree.
If you want to know why these threads are closed, it's because I send requests that they be closed.
Why?
Because the participants in the threads usually spend more time speculating about possible scenarios rather than reading or asking 'good' questions.
In short, we're waiting on .35 release; then we'll either A) merge the victory bits to the unified aries tree or B) merge cm specific bits from aries to our victory sauce.
That's that.

The reason being? I dont get how theres source for 2.2 and we cant get CM6, how would 2.3 source help us get CM7 working?
And I got my answer while typing because of Deca. Thnx!

Decad3nce said:
Fail. We've attempted this. A lot of the updated proprietary modules from gb and necessary for gb require updated kernel drivers which are present in .35 and would require more work to backport than what we're doing now.
We also do have NS4G source, we kanged everything we could from it.
We are lacking proper regulator sauce along with the branched victory gpio assignments which we can only fire blanks at right now since they have a completely new naming scheme in the aries(.35) tree.
If you want to know why these threads are closed, it's because I send requests that they be closed.
Why?
Because the participants in the threads usually spend more time speculating about possible scenarios rather than reading or asking 'good' questions.
In short, we're waiting on .35 release; then we'll either A) merge the victory bits to the unified aries tree or B) merge cm specific bits from aries to our victory sauce.
That's that.
Click to expand...
Click to collapse
So you don't like me?

Original Android <3ers! said:
So you don't like me?
Click to expand...
Click to collapse
I don't mind you, your motives are good, but this environment fosters redundant and pointless poo flingin'. Which usually leads to us responding with the same information, over and over.

Original Android <3ers! said:
So you don't like me?
Click to expand...
Click to collapse
Great way to lose another Dev.
Remember Konane? I really liked him. It's such a pitty.
Decadence, I appreciate your hard work. I'm sorry for causing this. I know you have done what you can and are working as hard as is possible, please don't be deterred by these threads. Some of us really do appreciate your work.

lynyrd65 said:
Great way to lose another Dev. Remember Konane? I really liked him. It's such a pitty.
Decadence, I appreciate your hard work. I'm sorry for causing this. I know you have done what you can and are working as hard as is possible, please don't be deterred by these threads. Some of us really do appreciate your work.
Click to expand...
Click to collapse
I'm not deterred. Far from it. Maybe bored since I only have one summer class and way too much free time to stare at proprietary bits :|

Decad3nce said:
I'm not deterred. Far from it. Maybe bored since I only have one summer class and way too much free time to stare at proprietary bits :|
Click to expand...
Click to collapse
Developers tend to support developers.
Sent from my SPH-D700 using XDA App

make DEVelopment Not War

Now that developing for our Acer Iconia is going like a fast train.
Pls DEVelopers work togheter and don t fight each other here at XDA we have to work togheter and make all off us users happy to use they great modifications you the allready known, Half gods, give us.
But don t fight please in the world around us there is place enough for all developing people do it doesn t matter if one or the other has made the basic stone to start building from.
I love the work and skills of you all.
I hope that we can keep this forum of ACER Iconia peacefull
sincerely PiXiEjOe:

+1 to that!!

+100 i would say

+1000 who's next D:

+ 999,999,999,999,999,999,999

+ infinity

+ (n+1)
'n' being the highest number posted on this thread....(countable or not)...
Sent from my XT720 using XDA App

i am glad that you people think te same way i do so thanks to you all.
keep up the good colaborating spirit

I have no skills at all for dev, so I rely on them and praise them for the amazing work they do. Please....I will beg....don't any of you go away. I will be lost. Thanks.
Sent from my SGH-T959 using XDA App

apl I can say is BONG +++++++++++++++++++++++++++++++++ 1

While I think that devs should all work together towards a common goal, I also think that people should understand what ExAcTlY is going on before making their decisions...
It should also be noted that concealing/altering and stealing work is a DISGRACE and against what XDA is all about (and sometimes illegal...)
This post sums up Perfectly what the deal is:
birkoffsjunk said:
Now I can't speak for m-deejay, or anyone else for that matter however... Thor is distributing a Kernel without releasing the source which is both a breach of the GPL license & XDA rules not to mention illegal. Now as MDJ has released his code under the GPL he is well within his right as one of the rights holders to tell Thor to cease and desist.
I can't say if anyone else reported the GPL violations, but I can say what I did.
I reported Thor for breach of the GPL (twice regarding his signature)
I reported vache for breach of the GPL (twice for bundling a Kernel without source)
I also reported another post for breach of the GPL (for providing a link to Thor's Kernel)​I give full permission to any moderator to come and verify I did do the above. I believe XDA moderators were acting on those reports by me and no one else.
Why did I report the Kernel? Because of repeated requests which were either ignored, spammed and/or laughed off.
Given what I have said above, you do realise you have accused a great ROM developer of multiple devices of doing something he probably didn't? An apology to MDJ sounds like in order
Just wanted to add I will not partake in any further discussion in regards to the above.
Click to expand...
Click to collapse

There is no place like home. There is no place like home........
Sent from my GT-P7500 using Tapatalk

grhand82 said:
apl I can say is BONG +++++++++++++++++++++++++++++++++ 1
Click to expand...
Click to collapse
HAHA I LOL'd!!!

No war but peace and development

we cannot understand what goes behind scenes for these developers apperantly they have issues with each other but I respect them so much, I appreciate the hard work they do no other developer wants to even conside doing developing on the iconia before they broke into the locked boot loader. So please developers (not mentioning names) lets continue with the great work you guys made the A500 an envy withing my friends when 6 months ago they thought xoom, Asus tf were the better choice.

Thanks to everybody

Just stumbled on to this and it is so funny. There will always be a bit on a competitive edge in these forums. Back in x1 forum it was all out war for donations, views and downloads. It may be a bit daunting to others chefs when they are all working on making Acer base better we have mdj releasing all kinda ports. Good for us I admit but maybe a bit daunting for others. I would like to see a few different takes on the ports we have right now as to me Acer base has been taken as far as it can go. It be nice to see a fusion rom with the best bits of galaxy, thrive, xoom etc thrown in. Will the devs come together and do that? Maybe not but its still a thought
Sent from my A500 using XDA Premium App

so what we got from this war?NOTHING.....now this iconia forum look like nothing activity and dead

abditerex said:
so what we got from this war?NOTHING.....now this iconia forum look like nothing activity and dead
Click to expand...
Click to collapse
Ae you reading the same forum as the rest of us? We have root for every version, a unlocked bootloader, more roms then you can throw a stick at - and new posts every day.

+1 too. No need to enter thousand to agree.

[Q] opinions about the best ROM

I'm thinking of using another ROM
but first I want to know ur opinions about the one you're using or u think is the best, which one is the unbugiest & fastest one for xoom (wifi only)?
& what really makes the difference in xoom ROMs, cause I didn't see any difference in screen shots, like how u see a big difference between Cyanogen & stock one (in android phones)

mehras1991 said:
I'm thinking of using another ROM
but first I want to know ur opinions about the one you're using or u think is the best, which one is the unbugiest & fastest one for xoom (wifi only)?
& what really makes the difference in xoom ROMs, cause I didn't see any difference in screen shots, like how u see a big difference between Cyanogen & stock one (in android phones)
Click to expand...
Click to collapse
There is really only one custom ROM for the Xoom, made by Team Tiamat, and one variation on that one.
Save for some specific tweaks and added features like overclocking, there is not a massive difference from the stock ROM since the HC source code has not and will not be released.
Therefore it is a little early to start the typical "I have no freaking idea what I am doing, please tell me what I should do and how I should feel so I don't need to think too much" posts, isn't it?

rschenck said:
There is really only one custom ROM for the Xoom, made by Team Tiamat, and one variation on that one.
Save for some specific tweaks and added features like overclocking, there is not a massive difference from the stock ROM since the HC source code has not and will not be released.
Therefore it is a little early to start the typical "I have no freaking idea what I am doing, please tell me what I should do and how I should feel so I don't need to think too much" posts, isn't it?
Click to expand...
Click to collapse
That was a good answer, but the last part was a tiny bit harsh, no?

Honestly... the post above hit the nail on the head. Tiamat is the only core ROM for the Xoom as of current because no other teams will want to create a ROM that you cannot do too much with since the Honeycomb source is not out, as the post above said, and it won't be released. Wait for Ice cream sandwich. That's when they will be ready to release the new source. So, ICS should be rooted and custom ROM heaven!

okantomi said:
That was a good answer, but the last part was a tiny bit harsh, no?
Click to expand...
Click to collapse
Perhaps, but if you look at other XDA forums such as the SGS forum, there are dozens of these posts a day. People who can't be bothered to read threads and do research but just keep asking what people think is the best, as if that has any real value.
Then when someone answers them, they will ask them to tell them how to flash the selected ROM, still seeing no need to educate themselves.
Next will be the frantic "I bricked my device...help me!" post.
A few days after someone walks them through getting back to stock, they will just post another "Which ROM is best" post.
It becomes an unending cycle. Sure I am probably being unfair to the OP to make a point, but they are being unfair to themselves by not doing their own investigation.

diablo2224 said:
Honestly... the post above hit the nail on the head. Tiamat is the only core ROM for the Xoom as of current because no other teams will want to create a ROM that you cannot do too much with since the Honeycomb source is not out, as the post above said, and it won't be released. Wait for Ice cream sandwich. That's when they will be ready to release the new source. So, ICS should be rooted and custom ROM heaven!
Click to expand...
Click to collapse
And to give all due props to Team Tiamat, most of the people with the skills to make a ROM for the Xoom are already part of that team...and they have done about the best anyone could do with without sources.
Even if there are other Devs out there familiar with the Xoom, I doubt any other team will make a ROM since what is there for them to do that isn't already in the Tiamat ROM?

rschenck said:
And to give all due props to Team Tiamat, most of the people with the skills to make a ROM for the Xoom are already part of that team...and they have done about the best anyone could do with without sources.
Even if there are other Devs out there familiar with the Xoom, I doubt any other team will make a ROM since what is there for them to do that isn't already in the Tiamat ROM?
Click to expand...
Click to collapse
My point exactly! What more would the devs be able to do or add without the source other than some themes?
Great point about all the best devs being on Team Tiamat. They are working together to make an awesome ROM!

rschenck said:
Perhaps, but if you look at other XDA forums such as the SGS forum, there are dozens of these posts a day. People who can't be bothered to read threads and do research but just keep asking what people think is the best, as if that has any real value.
Then when someone answers them, they will ask them to tell them how to flash the selected ROM, still seeing no need to educate themselves.
Next will be the frantic "I bricked my device...help me!" post.
A few days after someone walks them through getting back to stock, they will just post another "Which ROM is best" post.
It becomes an unending cycle. Sure I am probably being unfair to the OP to make a point, but they are being unfair to themselves by not doing their own investigation.
Click to expand...
Click to collapse
You are always so helpful, I'm sorry that you are feeling a bit burnt on all the help you've been giving. I know that I feel a bit frustrated when people clearly don't research before they leap, but I thought the OP was just looking for some opinions.
Anyway, your replies and diablo2224's pretty much wrapped up that topic!

rschenck said:
Perhaps, but if you look at other XDA forums such as the SGS forum, there are dozens of these posts a day. People who can't be bothered to read threads and do research but just keep asking what people think is the best, as if that has any real value.
Then when someone answers them, they will ask them to tell them how to flash the selected ROM, still seeing no need to educate themselves.
Next will be the frantic "I bricked my device...help me!" post.
A few days after someone walks them through getting back to stock, they will just post another "Which ROM is best" post.
It becomes an unending cycle. Sure I am probably being unfair to the OP to make a point, but they are being unfair to themselves by not doing their own investigation.
Click to expand...
Click to collapse
funny, but true answer, that's kind of what happened to me in the past month, but I finally broke the circle rules in the pas 3days, so now I'm on my own

diablo2224 said:
My point exactly! What more would the devs be able to do or add without the source other than some themes?
Great point about all the best devs being on Team Tiamat. They are working together to make an awesome ROM!
Click to expand...
Click to collapse
without source code,
so all those tablet optimized apps are made by devs by playing with the right resolution & graphic effects for the screen!!?
& since xoom & the others have (almost) the same screen size, it won't be so difficult for developers

anyway, what's wrong with google!!
I just read on wiki that they'll release the source code with ice "cream sandwich" source code, & that's because "cream sandwich" will become an android version both for phones & tablets....
don't u think it's waste of time with doing that? I'm imagining a very boring future for android, think of it, u'll see the same version on all the android smartphones & tablets!!!
seriously, what a boring choice for google

mehras1991 said:
without source code,
so all those tablet optimized apps are made by devs by playing with the right resolution & graphic effects for the screen!!?
& since xoom & the others have (almost) the same screen size, it won't be so difficult for developers
Click to expand...
Click to collapse
Umm... ok?
That my friend is for developing apps. Maybe you don't know anything about root or custom Roms? It doesn't work the same way when it comes to developing a custom Rom with special features such as system tweaks. Without the source, the Rom will not see things such as... every single tweak in CyanogenMod! No interface tweaks, multimedia tweaks, no tweaks of any kind! Check out CyanogenMod settings... there are a boat load of tweaks for everything you can think of. As of right now, nothing like that can happen with our Honeycomb tablets without the Honeycomb source code.
Without the source, you have a slighty modified stock Rom experience that can be themed pretty easily...

diablo2224 said:
Umm... ok?
That my friend is for developing apps. Maybe you don't know anything about root or custom Roms? It doesn't work the same way when it comes to developing a custom Rom with special features such as system tweaks. Without the source, the Rom will not see things such as... every single tweak in CyanogenMod! No interface tweaks, multimedia tweaks, no tweaks of any kind! Check out CyanogenMod settings... there are a boat load of tweaks for everything you can think of. As of right now, nothing like that can happen with our Honeycomb tablets without the Honeycomb source code.
Without the source, you have a slighty modified stock Rom experience that can be themed pretty easily...
Click to expand...
Click to collapse
useful info,
thnx
so, do you think we'll have chance to see & try some cool stuffs when "ice cream sandwich" being released!?!?!? orrrr our xoom will be old for that time & we'll have to think of buying something new???

mehras1991 said:
useful info,
thnx
so, do you think we'll have chance to see & try some cool stuffs when "ice cream sandwich" being released!?!?!? orrrr our xoom will be old for that time & we'll have to think of buying something new???
Click to expand...
Click to collapse
ICS will be ROM heaven for both root users and devs alike, no doubt about that. No one knows if it will make its way onto our current Xoom's though. Keeping in mind that at Google IO this year, they said something about a time frame for all new Android devices that will keep the selected devices up to date with the most current OS updates and releases. If that's the case, the Xoom was the first Honeycomb tablet/dev tablet... so one would think that the Xoom would be getting the ICS update according the what they said at IO. Again, no one really knows yet as it is still much too early for ICS to officially launch. We'll see if the OG Xoom gets it or else they will end up launching the Xoom 2 as the first ICS device no doubt, because by that time the Xoom will be nearing it's one year mark, meaning... time for a remodel!