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!

Tester

Just putting it out there that I would love to be a tester for the Galaxy SII, I have the original one, I have flash and went through 90% of every ROM up for it in both sections the original section and regular section, I just love flashing and going through Roms and would love to just help out someone with there Rom and do whatever it is they need me to do as far as testing, please hit me back. I hope I posted this is the right place if not, I will watch the Noob video 20 times in a row for punishment.

ah ok...... that's an idea

Original SGS II ? No kidding! :|

At first, I thought of this as just a pointless thread - but you got me thinking... What if we were to create a thread where people can nominate themselves as alpha/beta/etc. testers for ROM/Kernel developers? The difference lying in that to be eligible for a position, you'd have to prove that you have basic knowledge of how to recover from, for example, a bootloop, or a device that won't even boot, or constant FCs, etc. etc., along with again, pretty basic ADB knowledge, how to create and restore a NANDroid backup, and things like that. It'd come with the usual disclaimer stating that all responsibilities lie with the user, not the developer, and while the developer may be willing to provide support for bugs, etc., they are not liable for any damage resulting either directly or indirectly from the use of their software.
This would solve two things - it would satisfy those who just can't stand to wait for the release of something, who like to always live on the bleeding edge of development, and it would provide the developers a huge testing platform.
In review, though, this provides to main issues: 1) people would only be able to test one thing at a time, e.g. you're not going to be allowed to test a beta ROM with an alpha kernel, for example - it creates too many variables, and makes it harder for the developers to isolate and fix problems - but this shouldn't be an issue for people, just pick what you want and stick with it, and 2) people who leak the otherwise tester-restricted software for the masses - but this can be solved easily: maintain a list of official testers. Anyone who comes begging for support because they went ahead and flashed some leaked ROM/kernel/whatever, and ended up without a working device without being on the list, can be denied support for breaking the rules. Moreover, they, along with the leaker, could potentially face site-imposed bans?
I'll cut the rambling here, but I think it's a good idea?

As a ROM developer, its a great idea.
Sent from HydrOG3N MOD S2.
Technology Evolves, Android Evolves.
HydrOG3N is THE Revolution.

Thinking about it, not bad idea. But to back sceamworks up a bit, there should be a number of post limit, Some form of history for the dev`s to see who is a Noob (sorry Noobs) and who is not...

I'm in
Sent from my GT-I9100 using XDA App

I like the idea and I too would be glad to help people testing there ROMs.
It also seems nice to have a thread where people (like me or the OP) can set them self available for testing.

Most real developers pick their team from watching the threads and see how is willing to put the time in and know how to properly test as well as offer ideas on fixes. But not a bad idea I guess for new rom developers

lodger said:
Thinking about it, not bad idea. But to back sceamworks up a bit, there should be a number of post limit, Some form of history for the dev`s to see who is a Noob (sorry Noobs) and who is not...
Click to expand...
Click to collapse
I agree completely, I'd say 50-100 would be a fair starting point? I might PM some devs sometime soon with a proper proposal, and if I get a positive response from a majority of them, I might draft something, and get some official names on-board.
zelendel said:
Most real developers pick their team from watching the threads and see how is willing to put the time in and know how to properly test as well as offer ideas on fixes. But not a bad idea I guess for new rom developers
Click to expand...
Click to collapse
I considered this, and I think if anything brings the idea down, it'll be that - it's a hard sell to make, and I'd love to say that there's no harm in trying, but really, there is, so I guess execution is everything?

Good idea, im in....

ROM Release Rate

I understand, after 2+ years, that ROM development and the forums for the EVO are gonna slow down. Devs are going to move on to other devices, but there is a really disturbing trend here that is irritating the hell out of me.
ROMs used to be released as Aplha's Beta's RC's, final, etc. You could look at the OP and see everything about the ROM. Devs took their time crafting something unique.
Now, I'm seeing these ROMS come out at a rapid pace and I'm not liking it for several reasons.
1) Poorly written OP's that don't even list the Android base version or the kernel, etc.
2) The same ROM with different names and the only real differences are a few 3rd party apps, or a slight theme change.
3) ROMs released as finals, with a ton of bugs. I'm not talking about FFC, Netflix, 4G bugs on ICS/JB ROMS; I'm talking about ROMS with no Wifi, for example. The majority use WiFi. Why the HELL would you release something where one of the most important aspects doesn't even work?? It's like not paying attention to details is suddenly OK
Settings that don't stick. Sounds that don't stick. Constant System Process Errors. These are pre-release errors, and I don't see them getting fixed, because it's become like a race to port every other ROM from every other device and tweak to boot up on the Evo, then letting it go.
I REALLY wish I could take the time and learn how to properly cook up my own ROM. My OCD of paying attention to details would probably make it great.

Hipkat thats the best thing ive heard in weeks,someone finally speaking out about the BS thats being posted now days and its like everyones in a race to see who can come out with the most borked roms,lol,like you said,they are all the same,except the apps and some themeing and half of them cant do that either,i'm sure this isnt meant to be a bashing session,its just getting rediculous with the drama some are causing and all the crappy ass roms being released,some guys do know what their doing,theres been 1 or 2 that i've put out that i shouldnt have,but come on guys at least take your time and try to do it right,only takes a little common sense and effort.If you havent noticed,over half the members and devs have left because of the BS,when i started doing roms,it was fun,nows its just a big joke,lol.
I dont care if anyone gets pissed about this and i'm sure they will,but oh well life goes on,you will eventually get over it.

It's definitely not a bashing, but a call for Devs to take a little more time and do it right

HipKat said:
It's definitely not a bashing, but a call for Devs to take a little more time and do it right
Click to expand...
Click to collapse
I don't Dev, Cook, Build, Port or whatever term is used so I have alot of respect for those that do. With that being said I would also state that I am in complete agreement with you and Diablo.
I look at damned near every topic started in the Dev forum just to see what is being made. I take weeks to look at a new ROM and follow the threads to see what comes of it (with the only exception being Mazda's new CAJB ROM. On that one I went with name recognition and am pleased that I did)
In regards to the mass influx of ROMs I'll say this: If you guys don't take the time to keep up with each item you produce, work on bugs, add new options, answer questions from the users then you'll soon find yourself out of favor. Your reputation here, just like in RL, is something of value. It takes very little to earn trust, respect and loyalty. Most people will always give you the benefit of the doubt. Do something to devalue that trust and it can be nearly impossible to regain.
I think some wisdom can be gleaned by the following quote:
jamieg71 said:
I've seen devs, chefs, hackers, w/e, that make statements like "I do this for myself and just choose to share" or things to that effect. I call BS. I won't speak for anyone else but myself when I say, I do this for the thrill of it, for the challenge, to learn, and to share. I'd be lying if I said I didn't care about d/l numbers or that seeing my thanks meter grow did not give me some juvenalalistic (is that a word?) thrill. The fact is, guys like me doing this stuff get off on it...
Click to expand...
Click to collapse
We know why you do it, and if you want to keep your junkies and not lose your rep, then make sure you take the time to Develop your craft and thereby make a better product for the masses...
Sorry for the rant

Well said, and nice quote from Jamie, who, btw, you notice took a lot of time with Reloaded

HipKat said:
Well said, and nice quote from Jamie, who, btw, you notice took a lot of time with Reloaded
Click to expand...
Click to collapse
...lol, 'nuff said!

I think everyone needs to remember the difference between Development and Port / Theme / Tweak / Mod. That simple labeling would be a start

Over in Evo LTE land, they have finally recognized this distinction by creating entirely separate forums for "HTC EVO 4G LTE Android Development" and "HTC EVO 4G LTE Original Android Development"
One is for tweaks or ports, and the other is for people who actually compile something.

I made a request for the same original dev section but got denied as our device is to old.
I agree that there are a ton of ports and not enough originality or bugs being fixed. What I would like to state us that the op is stating that a lot have some third party apps but that's like calling the kettle black. You yourself have a rerelease of a miui from where all you did was slap your team name in the thread. I believe the original thread still exists. I'm not calling you out at all but at the same time the work that goes into all these ports or mods or what not is a ton. I myself have my rom thread and some new stuff coming out but I don't call people out usually on their stuff unless its a pure kang(meaning an actual using of ur work with out permission) not a duplicate port.
Yeah some of the revs here could put a little more work in and for sure learn to organize their rom thread a whole hell of a lot better but at the same time who else do u see bringing the newest and best to a two year old device.
XDA Moderator

It's not that they have 3rd party apps, all ROMS do, it's that some ROMS are just the same ROM with a few different 3rd party apps, or a slight variation in theming, and I mean real slight, but tbh, my biggest beef was with the OP not even listing what kernel is in the ROM, or if it has A2SD or a way to get it working, or the version of Android it's based on, etc.
Add in bug reports that get ignored or the person posting the report gets demeaned for it.
Mostly, it's just the sloppiness that I see going on over the last few months. Too hasty to release something without really perfecting it first

HipKat said:
It's not that they have 3rd party apps, all ROMS do, it's that some ROMS are just the same ROM with a few different 3rd party apps, or a slight variation in theming, and I mean real slight, but tbh, my biggest beef was with the OP not even listing what kernel is in the ROM, or if it has A2SD or a way to get it working, or the version of Android it's based on, etc.
Add in bug reports that get ignored or the person posting the report gets demeaned for it.
Mostly, it's just the sloppiness that I see going on over the last few months. Too hasty to release something without really perfecting it first
Click to expand...
Click to collapse
I can agree with that there. sloppy op's without all the listings of what is added or taken out and what its running with a q & a section amoung other things.

I feel like we developers and porters alike should make a check list. Every time you want to post something, run through the list and then once everything is there, read again. If it seems like a business proposition (detailed, understandable, provocative and complete) then, that is the right moment to unleash it.

Thats exactly what i do,i make a list in notepad of what i want to do to the rom,then i go through and check it off as i go,wahla,i have a channelog,so to speak,then post it on the thread.Just like in my 4 Kornerz thread..... http://forum.xda-developers.com/showthread.php?t=1612933

Same thing I'm gonna do as I try and update this MIUI GB ROM

What's funny is that the main reason I always hated opening ROM threads is because I'm completely OCD and feel like the posts have to make perfect sense. I try for my thread to make a little bit of sense at least at this point. And I try to keep change logs, bug reports & FAQs up to date.
But then again, I only have one ROM thread in this device section.
----------------------
Current Device: HTC EVO 4G LTE | ROM: toasted-deck CM10 | Kernel: Stock

Kernel should be listed.
a2sd included/not included AND if a specific version is known to work/not work.
Gapps included/not included (you can usually tell from the size of the ROM, but still)
SuperSU vs. Superuser
Wifi and data working/not working
Boot animation audio (can lead to uncomfortable moments when flashing in restrooms, in bed, around family or in TSA security lines--- yes, all personal experiences)
Probably much more...
RootzWiki kinda sorta tried to standardize some of that in OP headers. Would be cool to see that concept expanded in a visually pleasing manner. But, I know people like sprucing up their OP to their liking. Example:
Source: https://github.com/s...mmc-ra-recovery
Mod Type: Recovery Difficulty: Moderate Mod Status: Kang Mod Base: Carrier:
Requires Root: Yes Apply In: Fastboot Optional: Themed Optional: Android Version:
I think ports are great. If the developer is planning on just bringing it over and leaving it alone I think that's fine, but they should be upfront and say "Hey, I did this. Probably won't do any more with it myself, but anyone is welcome to add to it. Otherwise, enjoy."
What I'd really like to see is the people who respond first after an OP + OP reserved do something with that slot besides planting their flag of happening to be online at the right time (e.g. "First. Looks cool!"). They could take the lead, especially for very active developers with many ROMs and threads, to follow that thread and maintain an updated ROM Cheat Sheet/Known Fixes post. How many times have you followed the development of a ROM and things like the new boot animation didn't make it into the next update because the developer forgot. Then people post, "Hey, what happened to the boot ani" five or six times. Then a nice person posts it on Dropbox. Then a few people say other things. Then people repeat the question. Then people point them to the Dropbox link two pages back. Repeat. Repeat. Probably wouldn't matter though since a lot of people never read the OP. They sure wouldn't read that. I'll shut up.

smelkus said:
Kernel should be listed.
a2sd included/not included AND if a specific version is known to work/not work.
Gapps included/not included (you can usually tell from the size of the ROM, but still)
SuperSU vs. Superuser
Wifi and data working/not working
Boot animation audio (can lead to uncomfortable moments when flashing in restrooms, in bed, around family or in TSA security lines--- yes, all personal experiences)
Probably much more...
RootzWiki kinda sorta tried to standardize some of that in OP headers. Would be cool to see that concept expanded in a visually pleasing manner. But, I know people like sprucing up their OP to their liking. Example:
Source: https://github.com/s...mmc-ra-recovery
Mod Type: Recovery Difficulty: Moderate Mod Status: Kang Mod Base: Carrier:
Requires Root: Yes Apply In: Fastboot Optional: Themed Optional: Android Version:
I think ports are great. If the developer is planning on just bringing it over and leaving it alone I think that's fine, but they should be upfront and say "Hey, I did this. Probably won't do any more with it myself, but anyone is welcome to add to it. Otherwise, enjoy."
What I'd really like to see is the people who respond first after an OP + OP reserved do something with that slot besides planting their flag of happening to be online at the right time (e.g. "First. Looks cool!"). They could take the lead, especially for very active developers with many ROMs and threads, to follow that thread and maintain an updated ROM Cheat Sheet/Known Fixes post. How many times have you followed the development of a ROM and things like the new boot animation didn't make it into the next update because the developer forgot. Then people post, "Hey, what happened to the boot ani" five or six times. Then a nice person posts it on Dropbox. Then a few people say other things. Then people repeat the question. Then people point them to the Dropbox link two pages back. Repeat. Repeat. Probably wouldn't matter though since a lot of people never read the OP. They sure wouldn't read that. I'll shut up.
Click to expand...
Click to collapse
LOL, you forgot 'Lather, Rinse...'
Who else clicked the link

While I agree with the OP 100%, I think at the end of the day there is NO rule that states that you need to do all that..... This is for FREE, and therefore we should be happy with we get on our EVO's nowadays..... I wish developers took their time to put a fully detail change log, bug list Q&A's section, but honestly if we don't like the way certain devs handle their threads, then just move on to the next Rom either way I don't develop, and I can figure out most stuff regarding a Rom by myself now, so I'm just thankful for all the roms out for the og EVO.
Edit: what I would like to know is what's going on with all the Rom teams flip flopping, what's up with that? Sorry to go off topic, lol.
Sent from my PC36100 using xda premium

Sorry, but while I appreciate the freeness of the work done and am grateful for it, there should still be enough info to identify exactly what you're getting into.
Perfect example. A lot of ICS/JB ROMS require the patched A2SD file. Good luck finding it. Why not add a link to the OP?? Same with GAPPS
And the date that it was released is much appreciated, although not as critical. The Android version if it's a Sense and/or GB ROM is definitely something that should be there, along with the kernel.

PHE-NOM said:
Edit: what I would like to know is what's going on with all the Rom teams flip flopping, what's up with that? Sorry to go off topic, lol.
Sent from my PC36100 using xda premium
Click to expand...
Click to collapse
Two teams merged. Some people have left teams. I myself left td to not look partial towards a certain group.
XDA Moderator

Our phone is not dead!!!!

*Please no one delete this thread! It is really important!*
Hi everyone!
I am here to tell you guys about our phone.
Yes, the title says everything; our phone is not dead!
What do you think? Just because Huawei is not supporting this phone anymore doesn't mean that our phone is dead!
Look! We have achieved great things with our knowledge! We have already have Android that wasn't given to us by Huawei:
- CM 7.2
- Aurora ICS
- MIUI
- Oxygen
- JokerROM
- and lots of others!
(Thanks to all those developers that have contributed their efforts for the sake of our phone!)
Huawei is not supporting us, but every person in our community is supporting each other.
I know we are lacking developers, but we still have great developers: DZO (he's a bit sleepy), forumber2, Blefish, MosTERRA, ezet, and anyone else I have missed!
We still have developers, but not once have I read anyone commenting anything positive about our phone. Not once anyone has told someone else that our phone is dying/dead. Always, everyone here has said our phone is finished.
Come on guys! Don't say this! Always try to say good things about our phone. By saying bad things about our phone, you are discouraging other people, and most importantly the Developers, from keeping the phone.
Please stop discouraging Developers and others! Instead, encourage others to gather knowledge and start building some ROMs!
Yes, I would encourage all of you here to start gathering knowledge about android and start building some MODs, Themes, ROMs, etc, for our phone!
NEVER AGAIN I WOULD WANT TO SEE A COMMENT THAT SAYS NEGATIVE THINGS ABOUT OUR PHONE!!!!

You're right and in general I agree with you but this sub-forum is only to post ROM's preferably tested and without bugs. You should move this to General section or ask to mods to do that. Blefish is working on CM 10 and we (non-developers) need to wait.
Cheers.

to say our phone is "dead" is not negative as i perceive it.. its just a plain fact..
in this fast-changing technology world, our phone already did its job very well..
my u8800 has just passed its 2-year mark, and though its just become my second-line support phone in this month, its still of great value to me..
(big compliment to our great developers!)
HOWEVER, the phones is already over 2 years old, and this is a very old age in technology world (and also considering its lack of official support)..
if everyone just refuses to proceed forward, we are probably still playing/flashing mods for our beloved transistor radio (if thats even possible)!
[edit]
with the above said, i do not mean to discourage any further development effort on this phone..
i actually welcome such activities very much honestly..
its just that ppl should also recognise those of us who try to move forward with newer and more powerful phones..

rqmok said:
*Please no one delete this thread! It is really important!*
Hi everyone!
I am here to tell you guys about our phone.
Yes, the title says everything; our phone is not dead!
What do you think? Just because Huawei is not supporting this phone anymore doesn't mean that our phone is dead!
Look! We have achieved great things with our knowledge! We have already have Android that wasn't given to us by Huawei:
- CM 7.2
- Aurora ICS
- MIUI
- Oxygen
- JokerROM
- and lots of others!
(Thanks to all those developers that have contributed their efforts for the sake of our phone!)
Huawei is not supporting us, but every person in our community is supporting each other.
I know we are lacking developers, but we still have great developers: DZO (he's a bit sleepy), forumber2, Blefish, MosTERRA ezet, possibly me, and anyone else I have missed!
We still have developers, but not once have I read anyone commenting anything positive about our phone. Not once anyone has told someone else that our phone is dying/dead. Always, everyone here has said our phone is finished.
Come on guys! Don't say this! Always try to say good things about our phone. By saying bad things about our phone, you are discouraging other people, and most importantly the Developers, from keeping the phone.
Please stop discouraging Developers and others! Instead, encourage others to gather knowledge and start building some ROMs!
Yes, I would encourage all of you here to start gathering knowledge about android and start building some MODs, Themes, ROMs, etc, for our phone!
NEVER AGAIN I WOULD WANT TO SEE A COMMENT THAT SAYS NEGATIVE THINGS ABOUT OUR PHONE!!!!
Click to expand...
Click to collapse
So why don't you make Jelly bean ?

iamelton said:
to say our phone is "dead" is not negative as i perceive it.. its just a plain fact..
in this fast-changing technology world, our phone already did its job very well..
my u8800 has just passed its 2-year mark, and though its just become my second-line support phone in this month, its still of great value to me..
(big compliment to our great developers!)
HOWEVER, the phones is already over 2 years old, and this is a very old age in technology world (and also considering its lack of official support)..
if everyone just refuses to proceed forward, we are probably still playing/flashing mods for our beloved transistor radio (if thats even possible)
Click to expand...
Click to collapse
Our main problem is the just the lack of developers as I already said before, because saying our phones is old fashioned it ain't true, for an example the Huawei Ascend G300, imo that phone is not that far away from our phone in hardware and capability (and also it was release in May of 2012), but still it already has CM9, CM10, CM10.1, thats my point of view, we can't all have the same opinion. I just don't have the skill to do such things in the Android area, if I had I would work on this awesome device.

It's not dead, but it's been on life support for a very long time, now. Blefish is the only active, transparent developer this device has going for, and even he doesn't have public releases yet and encounters numerous issues. There is no real Jellybean for this device, regardless of the fact that the hardware is capable, and so for all intents and purposes it is dead, for the time being. But that could change.
Regardless, this is a terrible thread and if you want to help you shouldn't spam this forum. There are specific forums for this sort of inane garbage.

I think it's dead anymore since we can't go through jellybean. There are only 2 person as i know who have coding knowledge;dzo and blefish.Besides we haven't seen a working wifi for jellybean both of them;so this makes the phone dead,in my view.

i think the points are quite clear now.. in android world, a phone is "dead" if there is not much active development/support for the latest updates going around (either officially or from individuals)..
[edit]
OP, just did a search and found out that u ported a xperia style rom to our phone, so that makes u a developer of this phone.. thx for the work..
(though another GB rom does not interest me that much.. )

I'd like to point out that just because I haven't released a rom does not mean I am not working on it. Just hang on as there is awesome stuff coming up!
I know I am not the fastest developer around, but I always try to do things "properly". Of which I mean I try to provide good code that would be reusable in the future.
Sent from my U8800

Would just like to clarify something
No. Our phone will never be dead, as long as we have devs working on it.
I would also like to point out something:
Just because I ported Xperia Style GB ROM, doesn't mean I have become a developer. BUT at least I am trying to build JB for our device. Yes, I have downloaded the CM10 source and have started building it. Since this is the first ever ROM I will build, which is why I am getting help from Blefish (thanks a lot Blefish. I really appreciate your efforts).
I am trying my best to keep this project going, but I have my studies and other important things (won't mention because they are personal). It is my second last year in High School, so I don't get much time (i'm sorry).
I WOULD STILL LIKE TO ENCOURAGE PEOPLE TO GATHER KNOWLEDGE AND START BUILDING FOR OUR DEVICE. WE NEED AS MUCH DEVELOPERS AS POSSIBLE WORKING ON THIS DEVICE!
I know gathering the knowledge is hard, but we have the Q&A section where you can ask something whenever you are stuck. Please step forward and start working!
Thanks for understanding.:good:

rqmok said:
No. Our phone will never be dead, as long as we have devs working on it.
I would also like to point out something:
Just because I ported Xperia Style GB ROM, doesn't mean I have become a developer. BUT at least I am trying to build JB for our device. Yes, I have downloaded the CM10 source and have started building it. Since this is the first ever ROM I will build, which is why I am getting help from Blefish (thanks a lot Blefish. I really appreciate your efforts).
I am trying my best to keep this project going, but I have my studies and other important things (won't mention because they are personal). It is my second last year in High School, so I don't get much time (i'm sorry).
I WOULD STILL LIKE TO ENCOURAGE PEOPLE TO GATHER KNOWLEDGE AND START BUILDING FOR OUR DEVICE. WE NEED AS MUCH DEVELOPERS AS POSSIBLE WORKING ON THIS DEVICE!
I know gathering the knowledge is hard, but we have the Q&A section where you can ask something whenever you are stuck. Please step forward and start working!
Thanks for understanding.:good:
Click to expand...
Click to collapse
HD2 is dead and it still has developers.
It's not developing, it's passed on. This phone is no more. It has ceased to be. It's expired and gone to meet its maker. This is a late phone. It's a stiff. Bereft of life, it rests in peace. If we haven't bought it , it would be pushing up the daisies. It's run down the curtain and joined the choir invisible. This is an ex-phone. Capisci?

rqmok said:
No. Our phone will never be dead, as long as we have devs working on it.
I would also like to point out something:
Just because I ported Xperia Style GB ROM, doesn't mean I have become a developer. BUT at least I am trying to build JB for our device. Yes, I have downloaded the CM10 source and have started building it. Since this is the first ever ROM I will build, which is why I am getting help from Blefish (thanks a lot Blefish. I really appreciate your efforts).
I am trying my best to keep this project going, but I have my studies and other important things (won't mention because they are personal). It is my second last year in High School, so I don't get much time (i'm sorry).
I WOULD STILL LIKE TO ENCOURAGE PEOPLE TO GATHER KNOWLEDGE AND START BUILDING FOR OUR DEVICE. WE NEED AS MUCH DEVELOPERS AS POSSIBLE WORKING ON THIS DEVICE!
I know gathering the knowledge is hard, but we have the Q&A section where you can ask something whenever you are stuck. Please step forward and start working!
Thanks for understanding.:good:
Click to expand...
Click to collapse
ok i take back my previous recognition of u as a developer.. now you are a developer-to-be for this great phone.. (honestly, no sarcasm attached.. )
and while i think u8800 is dead, u see it as a living pal.. no problem.. case closed.. (no sarcasm, again..)
now back to business.. i would very much be happy to see a jb rom created and surely would give it a try in my u8800..
i just hope u can keep this enthusiasm and keep working on this jb-rom-to-come..
honestly speaking, having enthusiasm on something and start working on it are not that difficult.. its the persistence and patience (in dealing with obstacles) that make the difference..
good luck and hope to hear from u soon.. :good:

Blefish said:
I'd like to point out that just because I haven't released a rom does not mean I am not working on it. Just hang on as there is awesome stuff coming up!
I know I am not the fastest developer around, but I always try to do things "properly". Of which I mean I try to provide good code that would be reusable in the future.
Sent from my U8800
Click to expand...
Click to collapse
Hey,
I just don't understand something so i want to ask you. I am following you on twitter and see that it is really not easy making kernel 3.4. I just want to know, wouldn't it be easier if you just use the 3.0.8 kernel that we already have and maybe tweak it a bit? 3.0.8 should work with CM10. I just don't see the point of triing so hard to make the new kernel for CM10. Let's look in the future and if you release your rom in 2 months for now there will not be so many people that would find it usefull because many of U8800 users are already switching to new devices. And in may there is coming KLP.
Thanks for clarification! :good:

rastek said:
Hey,
I just don't understand something so i want to ask you. I am following you on twitter and see that it is really not easy making kernel 3.4. I just want to know, wouldn't it be easier if you just use the 3.0.8 kernel that we already have and maybe tweak it a bit? 3.0.8 should work with CM10. I just don't see the point of triing so hard to make the new kernel for CM10. Let's look in the future and if you release your rom in 2 months for now there will not be so many people that would find it usefull because many of U8800 users are already switching to new devices. And in may there is coming KLP.
Thanks for clarification! :good:
Click to expand...
Click to collapse
I understand what you are trying to say to Blefish.
I'll tell you. May it be 3.0.8 or 3.1 kernel, the story is the same: no Bluetooth and no WiFi. The 3.0.8 will need to be made compatible with CM10, but making WiFi and Bluetooth work will still won't be easy. That's why it is better to work on 3.1 kernel when you know that both kernels have the same story.
I hope you understand.

My phone is not dead!!!!!!!!!!!

Ok i understand that wifi and bt do not work with 3.0.8 and cm10, but blefish said in one thread that it is just a matter of configuration and is not nearly as hard as making a new kernel. I think blefish could make it work with 3.0.8.
Sent from my Nexus 4 using xda app-developers app

alexmbra said:
My phone is not dead!!!!!!!!!!!
Click to expand...
Click to collapse
That's the spirit!!
rastek said:
Ok i understand that wifi and bt do not work with 3.0.8 and cm10, but blefish said in one thread that it is just a matter of configuration and is not nearly as hard as making a new kernel. I think blefish could make it work with 3.0.8.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Yes, it is a matter of configuration.
All we have right now are the drivers from Aurora and the drivers from official Huawei ROMs. To make CM10, the drivers need to be taken from an older ROM and put into CM10. Now, it is not just a matter of copy-pasting. Our current drivers are not compatible with JB. Blefish has made some things working. The biggest problem is the WiFi. The old WiFi drivers need to be made compatible with CM10, and this is the hardest part. This is why there has been no one, yet, who has been able to do this.
No matter what kernel it is, may it be 3.0.8 or 3.1, the WiFi drivers need to be made compatible with CM10.
I think oguzhan mobile was able to fix the WiFi to the extent where it actually turned on, but it wouldn't scan. I don't know why he stopped development. I am not sure what kernel oguzhan mobile was using, but I think it was 3.0.8. I think you might be right that it would be easier for our phone to use the 3.0.8 kernel, but I think the 3.1 kernel would run better with CM10.1.
If you really want to know why Blefish wouldn't use 3.0.8 kernel, then you would need to Blefish himself. I have already said what I think, but I am not sure if I am right.
I am going to give it a try with 3.0.8 kernel. It might be easier than 3.1 kernel. I'll just have to find out

I like the way you talk....
Waiting for JB...
Sent from my U8800 using Tapatalk 2

Just follow @rtammekivi on Twitter if you want to know what's going on.

Phone is dead