Related
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! 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
finaly tiad8 testing team manage to make Tiadroid to run on the HTC touch HD not fully functioal rom but it dose run and i confirm that coz running it on my hd now
still trying to tweak the kernel coz almost nothing works properly
but we are getting closer and closer to a fully working nand build.
and oh its freaking fast yeahh!!!
Cool!
Have you any photos or videos of that?
Which version of Android is running on your Blackstone?
What is working? non-working?
android 2.2.2，many things include gsm is not working...waiting for tweak
All radio functions are missing and there are other bugs. But the phone is perfectly responsive, and never lags, which I haven't seen in any other ROM. It's even faster than my WinMo!!
We are trying to get tiad8 to make a git/repo so that all people could contribute. Hope to see some XDA devs there .
metamasterplay said:
All radio functions are missing and there are other bugs. But the phone is perfectly responsible, and never lags, which I haven't seen in any other ROM. It's even faster than my WinMo!!
We are trying to get tiad8 to make a git/repo so that all people could contribute. Hope to see some XDA devs there .
Click to expand...
Click to collapse
Why aren't you guys working on this working with actual devs?!? It seems this herrickwong character is doing all the heavy lifting (it seems he's the kernel dev behind this...) If he wants to actually get this working best for everyone, he should contact me (or the XDAndroid dev team)...
Git repo is a necessary step. All this stuff has no source as far as I can tell, which is a violation of the GPL. Good work on herrickwong's part, congrats guys! Let's try to make it available for everyone now...
arrrghhh said:
Why aren't you guys working on this working with actual devs?!? It seems this herrickwong character is doing all the heavy lifting (it seems he's the kernel dev behind this...) If he wants to actually get this working best for everyone, he should contact me (or the XDAndroid dev team)...
Git repo is a necessary step. All this stuff has no source as far as I can tell, which is a violation of the GPL. Good work on herrickwong's part, congrats guys! Let's try to make it available for everyone now...
Click to expand...
Click to collapse
You do not really believe this will happen, do you?
Available and transparent? With detailed informations what was used and changed?
Maybe herrickwong (great step) will do but for the rest?
ThaiDai said:
You do not really believe this will happen, do you?
Available and transparent? With detailed informations what was used and changed?
Maybe herrickwong (great step) will do but for the rest?
Click to expand...
Click to collapse
I hope that actual devs will realize that this is necessary. The only reason others are able to take XDAndroid's work so easily is because it's all openly available as source, and we are very transparent.
I want everyone to enjoy these phone's to their fullest ability. It would be a shame if he got Blackstone's to partially boot (it sounds like you guys are now where GSM RHOD's are - awesome!) and never released any of the stuff that got it to work in the first place... how can we merge back that work and have a unified system for all?
Again, I am really hoping that if he has some real devs in his clutches (seems herrickwong is a kernel dev!) then they should want to be transparent and work with other devs! Accelerate this project, gogogo!
I totally agree, it's really hard to give any kind of help while blindfolded
It's changing. Slowly, but it's changing.
For his new FRX07 builds tiad8 is giving credits to many people contributing to it.
A first step back into a bigger community working together for Blacky.
But we need source code. Without it we can't know why it works, integrate devices, etc
Sent from my HD2 using XDA App
Absolutly correct. I hope herrickwong will do because I doubt he will succeed in solving the problems alone. Until now the kernel and NAND is not really usable. Much work to do.
Hi xda developers,
I am using following source code and some modification. Any one know the owner? Who like to clone this project for continuous the project! I will tell him what i changed.
git://gitorious.org/~g3rm/linux-on-qualcomm-s-msm/linux-msm-blac-nand-tests.git
User g3rm0 here should be the owner.
herrickwong said:
Hi xda developers,
I am using following source code and some modification. Any one know the owner? Who like to clone this project for continuous the project! I will tell him what i changed.
git://gitorious.org/~g3rm/linux-on-qualcomm-s-msm/linux-msm-blac-nand-tests.git
Click to expand...
Click to collapse
g3rm0 is definitely the owner.
herrickwong, welcome! You should get in contact with ACL if you'd like some help getting GSM working - I'd bet it's the same issue holding up GSM RHOD's, so that would be a great breakthru!
As for you telling him what you changed... why not just submit merge requests to his repo? That way he can take the git-formatted patches and apply them... Just a suggestion, seems more efficient than telling him what you changed .
So we have it for the fascinate, the vibrant, the Nexus s and the galaxy s its self, where is ours? If we had Cyanogenmod all of this garbage about waiting for sprinsung to update our GB would be a non-issue. i have programming skills (java, python, c++, perl, bash, etc) and a lot of free time. Id be willing to put forth effort to get this out if some one were to decide to help out.
If OP really does have the knowledge to help out hes more than welcome to take a stab at it.. but be warned people have tried and tried but dont realise the level of development they are up against. the team working on it are very good, and if you think you have something to add.. then come to the cm7 epic irc channel and chit chat, but i wouldnt expect them to automatically assume you know what youre talking about...
Without GB source code, this is a dead end
Sent from my MIUI Powered device
krazyflipj said:
Without GB source code, this is a dead end
Sent from my MIUI Powered device
Click to expand...
Click to collapse
Not at all. Without Gingerbread Source Code Developers are capable of writing drivers themselves, it is just a lot easier to work with Samsung's drivers.
063_XOBX said:
Not at all. Without Gingerbread Source Code Developers are capable of writing drivers themselves, it is just a lot easier to work with Samsung's drivers.
Click to expand...
Click to collapse
Exactly...as everyone always asks "why do the other Galaxy S line of phones have CM7 but not us?" Well, since those models will probably never see official GB, the Devs in those communities took it upon themselves to build CM7 from scratch, from the bottom up. Just to point it out as well, they're Dev's are a lot higher in numbers compared to ours and therefore were able to split the work amongst themselves, which was still a challenge to say the least. We on the other hand, have a lot less Devs and us trying to follow the other Galaxy S communitie's footsteps would be impossible. The workload is just too much for our Devs. Luckily, we were the only US Galaxy S variant that will be receiving official GB, so, our Devs are waiting on Samsung to release source code, as this will make everything that much easier and smoother to complete CM7. I mean, why try and build from scratch when we have GB being released in a couple weeks? and just one last thing to clear up...everyone asks "why not just port a kernel or ROM from another Galaxy S phone?" Well, the Epic is the 'redheaded stepchild' of the Galaxy S family. Our hardware is different from the rest of the other variants. Decad3nce and the rest of the CM7 team have assured us that they've exhausted many different resources in attempts to get us CM7 before GB, but so far, they're still not near releasing a stable build.
Bottom line: GB source will help up immensely and is what we're currently waiting/looking forward to in order to advance with CM7 development.
*this is all common knowledge I have read/have been told by many high reguarded ppl within and around our community. If I'm wrong about something please point it out an correct me, just plz dnt start a flame war or anything of the like. I wrote this in hope of clearing up some questions/concerns. Also, feel free to add anything I might have missed*
Sent from my SPH-D700 using XDA App
metalblaster said:
So we have it for the fascinate, the vibrant, the Nexus s and the galaxy s its self, where is ours? If we had Cyanogenmod all of this garbage about waiting for sprinsung to update our GB would be a non-issue. i have programming skills (java, python, c++, perl, bash, etc) and a lot of free time. Id be willing to put forth effort to get this out if some one were to decide to help out.
Click to expand...
Click to collapse
i n00b teh pwns said:
Considering we have a team working on it, these threads aren't necessary. Making these threads just makes the Devs realize how ungrateful you people are. If I was them, I would've scrapped CM7 work a long time ago.
Sent from my Frozen over Epic.
Click to expand...
Click to collapse
chris41g said:
If OP really does have the knowledge to help out hes more than welcome to take a stab at it.. but be warned people have tried and tried but dont realise the level of development they are up against. the team working on it are very good, and if you think you have something to add.. then come to the cm7 epic irc channel and chit chat, but i wouldnt expect them to automatically assume you know what youre talking about...
Click to expand...
Click to collapse
All of you are right.
Coming from someone who has a lot of experience developing BSPs for the Linux kernel, this is something that can take a lot of time.
Some of it can be reverse engineered, but a lot of it only exists in binary form. Unfortunately, the interfaces to the binary parts can change.
It's not quite as simple as knowing C/C++. You have to know how the hardware works, or at least similar experience to know what's going on and how to reverse engineer it.
metalblaster said:
So we have it for the fascinate, the vibrant, the Nexus s and the galaxy s its self, where is ours? If we had Cyanogenmod all of this garbage about waiting for sprinsung to update our GB would be a non-issue. i have programming skills (java, python, c++, perl, bash, etc) and a lot of free time. Id be willing to put forth effort to get this out if some one were to decide to help out.
Click to expand...
Click to collapse
Everything should be current here: https://github.com/EpicCM
Otherwise, feel free to jump in #epic @ irc.fossnet.info
Hi guys, i'm an italian guy and forma this reason i don't undestend Hood the reasons why alla post of lollipop ROM will be closed. I understand that the problemi is the resources ot cyanogenmod. Thanks for all
Sent from my LG-D802 using XDA Free mobile app
Long story short: users steal early code releases from various sources and mash them together. Ultimately releasing half baked roms with their own name on it. A bunch of devices have been bricked, so the threads will be closed to avoid further damage.
Original devs are unhappy with the situation and do not like it therefore they complain and wanted the threads closed.
Sent from my LG-D802 - Powered by Dorimanx
Trixanity said:
Long story short: users steal early code releases from various sources and mash them together. Ultimately releasing half baked roms with their own name on it. A bunch of devices have been bricked, so the threads will be closed to avoid further damage.
Original devs are unhappy with the situation and do not like it therefore they complain and wanted the threads closed.
Sent from my LG-D802 - Powered by Dorimanx
Click to expand...
Click to collapse
Thanks a lot bro , and if the person who stole the code fix all bugs and release a stable rom, the thread will bel closed euqal?
Edoardo001 said:
Thanks a lot bro , and if the person who stole the code fix all bugs and release a stable rom, the thread will bel closed euqal?
Click to expand...
Click to collapse
if they fix all bugs they should fix it in the source and send it to gerrit by CM for reviewing and then pushing in to the source for all to build on.
Edoardo001 said:
Thanks a lot bro , and if the person who stole the code fix all bugs and release a stable rom, the thread will bel closed euqal?
Click to expand...
Click to collapse
Doubtful they would be able to fix it, or they wouldn't have kanged it to begin with, they would have built it using their own source.
Although i understand the mind set, and have no problem with the threads being closed, i do not agree with the choice of the word steal. Google released the source for anyone to build with, if someone doesnt want their code used github has private repos. Which in my mind defeats the point of open source. But isnt it about time we go back to personal responsibility? If you dont know the devs rep, and or you cant recover from a bad flash, then maybe, just maybe you shouldnt be rooted or playing fast and loose with your devices operating system.
Just sayin, resume doing as you plz.
Sent from my LG-VS985 using Tapatalk
wyrdtrtle said:
Although i understand the mind set, and have no problem with the threads being closed, i do not agree with the choice of the word steal. Google released the source for anyone to build with, if someone doesnt want their code used github has private repos. Which in my mind defeats the point of open source. But isnt it about time we go back to personal responsibility? If you dont know the devs rep, and or you cant recover from a bad flash, then maybe, just maybe you shouldnt be rooted or playing fast and loose with your devices operating system.
Just sayin, resume doing as you plz.
Sent from my LG-VS985 using Tapatalk
Click to expand...
Click to collapse
Absolutely agree with you. Open source is after all.. Open source. If you share your work, you must know that people are going to use it. It can be looked as your work is definitely something if others want to use it!
And yeah, if you have rooted your device and install roms, be ready for the risks it comes with. One cant blame a dev if they use devs stuff on their own risk.
I'll just leave this here
http://forum.xda-developers.com/showthread.php?t=2944269