Someone can explain why all lollipop ROM thread will be closed? - G2 Q&A, Help & Troubleshooting

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

Related

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

Kingxklick AOSP ROM!!!

King is almost done with his AOSP rom....looks incredible from what i can see...check out his site and go to the forums for more details......
Sent from my PC36100 using XDA App
Hmm... how long til this thread gets closed too?
Hey... This thing makes phone calls too!
JTNiggle said:
Hmm... how long til this thread gets closed too?
Hey... This thing makes phone calls too!
Click to expand...
Click to collapse
Yep this is the same guy posting garbage about getting update to GB on his Nexus. I recognize this fool by his exclamation marks.
kamasi36 said:
Yep this is the same guy posting garbage about getting update to GB on his Nexus. I recognize this fool by his exclamation marks.
Click to expand...
Click to collapse
Ok so the guy got banned. Does that mean anything related to his work is forbidden on XDA?
Sent while sitting on the toilet.
I'm sure he will charge people to use his work and get support because of course he made it from scratch with no help..
MrDSL said:
I'm sure he will charge people to use his work and get support because of course he made it from scratch with no help..
Click to expand...
Click to collapse
this ! <--- THIS !!
I sort of like sense, until the level of the android integration changes, as it's supposed to ˜32 for GB. Last I saw king was sorting it out and testing the wifi stuff.
The issue with all of android development is the "glue" which holds the pieces together. The changes in frameworks (new releases..) necessitates changes in the "glue". So whether it's changes to arguments, changes to calls, changes to tunnels / pipes, semaphores, locks, all these take work. Code does not compile and test itself, yet (lol). So a system integrator, which is what devs do, earns its (non-sexist) keep by using other peoples / coders stuff.
Vision is what all the devs have. Vision to see how the pieces should fit together. So I support his sorry ass, till this site comes to the same realization. I also support others. I fully appreciate their work and effort. How can people expect code for free? F off the devs are entitled to remuneration. Supporters fill the niche of testers, I almost wish the stuff was first given, then issued to supporters. As it is, we test, you benefit, back asswords...
So Kings AOSP rom is in his forum and he has done bunch of stuff to make it work. Decadence, Flipz, Birdman, Hill, Koush, Cyanogen, Amon_RA, Hero_over, KingX, and everybody else who "devs" should be names you remember at this start of a new genera of personal computing. Stories to tell your kids... "see that xxx on the TV, that's my software."
BTW if google is going to compete with MS, it had better start funding.
I am amazed that these people provide stuff, and people have the gall to comment on them, IT'S THE CODE, not the coder.
Amen.
Lotsa small minded folks... gotta coddle em', cajole' em, and hope that the code/Roms themselves take centerstage.. not they're drama.
The site in question requires registration for most downloads and requires donations as well for certain things (aka selling).
I am sorry, but I will have to close this thread.

Cyanogenmod 7 Development Thread - Take 2

DEVS! Would it be possible to use a FroYo Kernel for CM7 like the Droid X Developers did?
DON'T TROLL! IF YOU DO, THE MODS WILL SEE IT AND BAN YOU!
As we all know, the last Thread that involved CM7 Development for the Epic was closed because people got Off-Topic, so I decided to start this one just so we know where developing is going. This is just for those people who don't know how to read Github or don't want to check it every 3 seconds, and are okay with waiting a week for getting an update.
Please PLEASE PLEASE, DO NOT ASK FOR ETA'S! I know that someone will ask, but seriously. DO NOT ASK. It's annoying as hell. If the developers know when a release would happen, they'd tell us. Trust me, they would. But developing for our phone is difficult.
They can't Port something from the Vibrant or the Captivate because their GSM Phones and we're CDMA, meaning we use different signals or some crap like that. But I think it means that 3G and Calls and all of that would be hard to work on, not to mention 4G.
4G is an issue because it's something not many phones have, especially in the Galaxy S line. Remember that we're one of the original Galaxy S Phones, so we have it, and the Captivate, Vibrant, and Fascinate don't. This makes stuff even harder because then the developers have one more thing on their list to work on, that they never had before.
From what I saw last time, nullghost was trying to port the Nexus S 4G .35 Kernel. This is a Gingerbread Kernel. Remember that the Nexus S 4G is a STOCK GINGERBREAD phone, with no TouchWiz. The Kernel is just the thing that connects the software with the hardware, so this might also be hard because we have a keyboard and most other phones don't (I don't know if this really effects it, but from my prior experiences from Android, it does).
Lets say the Kernel gets Ported. The NS4G has 4G (no kidding). Don't quote me, but I think that'd get the camera working because obviously the camera is a piece of hardware, that should get 4G working because the the NS4G has it. GPS should probably work, although I'm sure that works if you use the GPS Status Method, and I'm not too sure about MMS and what the issue is with that.
Now, when I check Github, it appears as if the developers have stopped working? I mean, props to them for all they've done for us, but if I'm reading github properly, it seems as if they've taken a break (please correct me if I'm wrong).
Really. The only big problem we have is with people who won't stop asking for ETA's. Please, just don't ask. You'll cause more problems then you will help if you do get a reply.
And if anybody has any questions about the CM7-A4, feel free to ask them here. You should however check the closed Thread. It might be locked, but there's a reason it's not deleted, you can still read it, so please do.
Remember, no asking for ETA's. Just don't do it. Any questions, check the older Thread and in a few days or weeks what should be this Thread. Also check Github. No ETA's. Keep this on task, no gangster stuff. Kthnxbye.
Original Android <3ers! said:
DON'T TROLL! IF YOU DO, THE MODS WILL SEE IT AND BAN YOU!
As we all know, the last Thread that involved CM7 Development for the Epic was closed because people got Off-Topic, so I decided to start this one just so we know where developing is going. This is just for those people who don't know how to read Github or don't want to check it every 3 seconds, and are okay with waiting a week for getting an update.
Please PLEASE PLEASE, DO NOT ASK FOR ETA'S! I know that someone will ask, but seriously. DO NOT ASK. It's annoying as hell. If the developers know when a release would happen, they'd tell us. Trust me, they would. But developing for our phone is difficult.
They can't Port something from the Vibrant or the Captivate because their GSM Phones and we're CDMA, meaning we use different signals or some crap like that. But I think it means that 3G and Calls and all of that would be hard to work on, not to mention 4G.
4G is an issue because it's something not many phones have, especially in the Galaxy S line. Remember that we're one of the original Galaxy S Phones, so we have it, and the Captivate, Vibrant, and Fascinate don't. This makes stuff even harder because then the developers have one more thing on their list to work on, that they never had before.
From what I saw last time, nullghost was trying to port the Nexus S 4G .35 Kernel. This is a Gingerbread Kernel. Remember that the Nexus S 4G is a STOCK GINGERBREAD phone, with no TouchWiz. The Kernel is just the thing that connects the software with the hardware, so this might also be hard because we have a keyboard and most other phones don't (I don't know if this really effects it, but from my prior experiences from Android, it does).
Lets say the Kernel gets Ported. The NS4G has 4G (no kidding). Don't quote me, but I think that'd get the camera working because obviously the camera is a piece of hardware, that should get 4G working because the the NS4G has it. GPS should probably work, although I'm sure that works if you use the GPS Status Method, and I'm not too sure about MMS and what the issue is with that.
Now, when I check Github, it appears as if the developers have stopped working? I mean, props to them for all they've done for us, but if I'm reading github properly, it seems as if they've taken a break (please correct me if I'm wrong).
Really. The only big problem we have is with people who won't stop asking for ETA's. Please, just don't ask. You'll cause more problems then you will help if you do get a reply.
And if anybody has any questions about the CM7-A4, feel free to ask them here. You should however check the closed Thread. It might be locked, but there's a reason it's not deleted, you can still read it, so please do.
Remember, no asking for ETA's. Just don't do it. Any questions, check the older Thread and in a few days or weeks what should be this Thread. Also check Github. No ETA's. Keep this on task, no gangster stuff. Kthnxbye.
Click to expand...
Click to collapse
i disagree with the dont ask about ETA.
I think that if you announce that you are working on something then people have a right to ask for an eta.
People should be informed as to what is going on both good and bad...
While it can get to be like are we their yet thing... but then i would say you should have never announced something to begin with.
There's a reason I made that rule. If you look at every other CM7 Thread for the Epic, their closed because of ETA's. Don't even attempt to question what I have posted, it's based on fact.
daddy_droid said:
i disagree with the dont ask about ETA.
I think that if you announce that you are working on something then people have a right to ask for an eta.
People should be informed as to what is going on both good and bad...
While it can get to be like are we their yet thing... but then i would say you should have never announced something to begin with.
Click to expand...
Click to collapse
In other news....
I heard the Droid X has Cyanogenmod mostly working with it's stock 2.2 kernel. I wonder what all the Droid X devs had to do to make it work.
With the 2.3 kernel source being so close to fruition, it probably isn't worth it to give their method a try but if samsung can't get gingerbread working in the next couple of months it might be worth a shot.
And queue take 3... omfg, when will people learn, this is not to debate ETA.
Original Android <3ers! said:
There's a reason I made that rule. If you look at every other CM7 Thread for the Epic, their closed because of ETA's. Don't even attempt to question what I have posted, it's based on fact.
Click to expand...
Click to collapse
really not allowed to talk about that? Since when can someone else take away my free speech rights to ask when something is gonna to be released? If you dont want to answer a question for eta then just dont reply to it. After all no one is making you reply to anything.
If you HAVE NOTHING TO SHARE DONT POST IN DEVELOPMENT.
I'm trying to be honest with you and save you from being flamed. Did you even read the first post? The devs don't have the kernel source for the Epic 2.3.3 or beyond, nor do they have it for the Nexus S 4G, so until then, they have to stop developing because they cannot do ANYTHING without it. So an answer to an ETA is never.
lynyrd65 said:
In other news....
I heard the Droid X has Cyanogenmod mostly working with it's stock 2.2 kernel. I wonder what all the Droid X devs had to do to make it work.
With the 2.3 kernel source being so close to fruition, it probably isn't worth it to give their method a try but if samsung can't get gingerbread working in the next couple of months it might be worth a shot.
Click to expand...
Click to collapse
I think this would be a good idea while we wait for the Kernel source actually...
nullghost mentioned that CM6 would be in the same state as CM 7. Idk why, but yea.
No no, we're saying use the FroYo Kernel for CM7!
Original Android <3ers! said:
No no, we're saying use the FroYo Kernel for CM7!
Click to expand...
Click to collapse
Oh damn it, reading comprehension! My bad, my bad, continue the thread. Devs: could this also be possible?
Darkshneider said:
Oh damn it, reading comprehension! My bad, my bad, continue the thread. Devs: could this also be possible?
Click to expand...
Click to collapse
No.
Sent from my SPH-D700 using XDA App
Original Android <3ers! said:
No no, we're saying use the FroYo Kernel for CM7!
Click to expand...
Click to collapse
Fail. We've attempted this. A lot of the updated proprietary modules from gb and necessary for gb require updated kernel drivers which are present in .35 and would require more work to backport than what we're doing now.
We also do have NS4G source, we kanged everything we could from it.
We are lacking proper regulator sauce along with the branched victory gpio assignments which we can only fire blanks at right now since they have a completely new naming scheme in the aries(.35) tree.
If you want to know why these threads are closed, it's because I send requests that they be closed.
Why?
Because the participants in the threads usually spend more time speculating about possible scenarios rather than reading or asking 'good' questions.
In short, we're waiting on .35 release; then we'll either A) merge the victory bits to the unified aries tree or B) merge cm specific bits from aries to our victory sauce.
That's that.
The reason being? I dont get how theres source for 2.2 and we cant get CM6, how would 2.3 source help us get CM7 working?
And I got my answer while typing because of Deca. Thnx!
Decad3nce said:
Fail. We've attempted this. A lot of the updated proprietary modules from gb and necessary for gb require updated kernel drivers which are present in .35 and would require more work to backport than what we're doing now.
We also do have NS4G source, we kanged everything we could from it.
We are lacking proper regulator sauce along with the branched victory gpio assignments which we can only fire blanks at right now since they have a completely new naming scheme in the aries(.35) tree.
If you want to know why these threads are closed, it's because I send requests that they be closed.
Why?
Because the participants in the threads usually spend more time speculating about possible scenarios rather than reading or asking 'good' questions.
In short, we're waiting on .35 release; then we'll either A) merge the victory bits to the unified aries tree or B) merge cm specific bits from aries to our victory sauce.
That's that.
Click to expand...
Click to collapse
So you don't like me?
Original Android <3ers! said:
So you don't like me?
Click to expand...
Click to collapse
I don't mind you, your motives are good, but this environment fosters redundant and pointless poo flingin'. Which usually leads to us responding with the same information, over and over.
Original Android <3ers! said:
So you don't like me?
Click to expand...
Click to collapse
Great way to lose another Dev.
Remember Konane? I really liked him. It's such a pitty.
Decadence, I appreciate your hard work. I'm sorry for causing this. I know you have done what you can and are working as hard as is possible, please don't be deterred by these threads. Some of us really do appreciate your work.
lynyrd65 said:
Great way to lose another Dev. Remember Konane? I really liked him. It's such a pitty.
Decadence, I appreciate your hard work. I'm sorry for causing this. I know you have done what you can and are working as hard as is possible, please don't be deterred by these threads. Some of us really do appreciate your work.
Click to expand...
Click to collapse
I'm not deterred. Far from it. Maybe bored since I only have one summer class and way too much free time to stare at proprietary bits :|
Decad3nce said:
I'm not deterred. Far from it. Maybe bored since I only have one summer class and way too much free time to stare at proprietary bits :|
Click to expand...
Click to collapse
Developers tend to support developers.
Sent from my SPH-D700 using XDA App

[DEV] Finding a devs team

Hey guys and girlz,
as many of you know, the developement for our device is not that great and fast because everybody (except from ivendor and arco and maybe some others) is working alone on a ROM/kernel. We could speed this up by building a dev team where all devs for our device and maybe from galaxy w can work together and improve ROM for ROM instead of doing each ROM alone.
Hope we can do this :good:
If anybody is interested, post it here or PM me
Greets and regards,
markey
AW: [DEV] Finding a devs team
markey97 said:
Hey guys and girlz,
as many of you know, the developement for our device is not that great and fast because everybody (except from ivendor and arco and maybe some others) is working alone on a ROM/kernel. We could speed this up by building a dev team where all devs for our device and maybe from galaxy w can work together and improve ROM for ROM instead of doing each ROM alone.
Hope we can do this :good:
If anybody is interested, post it here or PM me
Greets and regards,
markey
Click to expand...
Click to collapse
Hm. Mate are you blind? Look at this forum. We have a lot of roms, some are even twice there from 2 different developers.
For me, personally its perfect like it is. Arco and Ivendor as lead developers for CM10. Other devs can contribute or take their work and make a new rom out of it.
Especially for a almost 2 years old device our forum is really awesome and you should be happy for what weve got here.
Just my 2 cents.
P.s: This is the development section. You should ask things like that on the General section, in the i9001 thread.
Sent from my GT-I9001 using xda app-developers app
XeLLaR* said:
Hm. Mate are you blind? Look at this forum. We have a lot of roms, some are even twice there from 2 different developers.
For me, personally its perfect like it is. Arco and Ivendor as lead developers for CM10. Other devs can contribute or take their work and make a new rom out of it.
Especially for a almost 2 years old device our forum is really awesome and you should be happy for what weve got here.
Just my 2 cents.
P.s: This is the development section. You should ask things like that on the General section, in the i9001 thread.
Sent from my GT-I9001 using xda app-developers app
Click to expand...
Click to collapse
First of all, i appreciate all the work of ivendor , skywalker, brood, xistance and arco and others who did an amazing job of porting major roms to our device. But i must honestly say, i agree on some points with the OP. It is amazing with what we achieved on our small but awesome community, but our phone is getting old and eventually we will be left behind. So now it is the best time to combine all of the knowledge that is hidden in our i9001 section to ensure the future.
In the past year i have been in this section i saw a lot of stuff that could be fixed faster if people would communicate more, like the well known cm9 camera problem (i dont know for sure there was miscommunication as i dont know what happened in the background). A dev team would be awesome.
But i am afraid that this won't work anymore. The glorious days of the i9001 are over. Many good devs left us.
But is is worth the shot. Would be so awesome! If you have any android knowledge, please join.
(I am to stupid. I cant join. I know how qtADB works but that is all).
Also i like the idea of combining the two devices and make a giant dev team for both so we can benefit from there knowledge and they from ours!
Verstuurd van mijn GT-I9001 met Tapatalk
XeLLaR* said:
Hm. Mate are you blind? Look at this forum. We have a lot of roms, some are even twice there from 2 different developers.
For me, personally its perfect like it is. Arco and Ivendor as lead developers for CM10. Other devs can contribute or take their work and make a new rom out of it.
Especially for a almost 2 years old device our forum is really awesome and you should be happy for what weve got here.
Just my 2 cents.
P.s: This is the development section. You should ask things like that on the General section, in the i9001 thread.
Sent from my GT-I9001 using xda app-developers app
Click to expand...
Click to collapse
No i'm not, otherwise I couldn't have read the forum and written this here
(Just joking)
I know that we have a lot of ROMs, but there are some from 2 different developers because one of them hasn't updated very long or stopped the project and then a new dev took the work.
Thats your personal opinion and I accept it.
I mean this all because of the bugs that have to be fixed.
No its not that awesome, look at the dhd, they have a big dev team who solves most of the bugs there and they have fully functional Android 4.2 and MANY more ROMs than we have also have a look at some other 2 or more year old devices, most of them have big dev teams who do fast and great work.
I really appreciate the work of all our developers (!!we have a 3.4 kernel which even much newer and better devices don't have!!) but we can make this even better and faster.
Thanks i know this but in general section we couldn't get a team together and i also forgot about this section because i mostly (nearly only) use the developement section
Greets and regards,
markey
I seem to agree with xellar's view. Our I9001 forum is great as it is for a two year old device and development seems to be moving forward at a well-placed pace. I dont see any point in creating a ''dev team'' . Dont get me wrong , I'd love to see it happen. But Im comfortable with the pace here .
AW: [DEV] Finding a devs team
I would also apreciate a dev. BUT the developement of the last 2 years was that good, that i can't comlpain on anything. It works very well the way it goes now. Maybe in the near future (~6 moths) when more importent (doesn't mean the other are unimportant) devs leave the s+ and 5.0 will be roll out, maybe then we need a dev-team.
But we have already s.t. like dev-teams:
Arco and Ivendor (CM9/10)
The kernel devs (Erik, castagna, Biagio, Christopher, ...)
Xistance and Doom (CM10.1)
They all share allready there knowledge and function.
So... No need to hurry in my opinion :beer:
"...nothing is more powerful than a young boy's wish. Except an Apache helicopter..." -Ted
i think we have a lack of devs contributing to really port the newer versions of android. its only arco and ivendor who are doing this and since arco wanted to concentrate more on his own device its only ivendor (arco is yet still involved with our phone). everyone else is "just" forking from ivendor, aokp, aosp and paranoid which is great and which is not necessarily easy. without them there would be nothing else but the cm rom. still its not comparable to ivendors or arcos work. i dont want to diminish the importance of the work of others (sadly i have to always mention it when saying things like that...). i just didn't see them commit to ivendors github and ivendors credits concede my point.
AW: [DEV] Finding a devs team
I'd love to be in the team
Sent from my GT-I9001 using xda app-developers app
dr.wtf said:
i think we have a lack of devs contributing to really port the newer versions of android. its only arco and ivendor who are doing this and since arco wanted to concentrate more on his own device its only ivendor (arco is yet still involved with our phone). everyone else is "just" forking from ivendor, aokp, aosp and paranoid which is great and which is not necessarily easy. without them there would be nothing else but the cm rom. still its not comparable to ivendors or arcos work. i dont want to diminish the importance of the work of others (sadly i have to always mention it when saying things like that...). i just didn't see them commit to ivendors github and ivendors credits concede my point.
Click to expand...
Click to collapse
As true as this is, I still don't like the fact that you say we just fork their work. Both arco and ivendor haven't even started doing any real work on 4.2, forget giving us anything. Camcory and I have brought 4.2 by ourselves, just using arco's kernel source(which is REALLY important so I'm saying nothing to arco).
you probably saw what a mess the "perfectly working cm7" was even though mazen said hes not a real developer. when the 3.4 kernel came up it turned out to be not properly ported. no offense to both of those guys since cm7 actually was usable and the kernel had its right to exist (educk, if you read this, no need to defend yourself, i've read the whole thread).
but you must understand that im kind of suspicious with new things since i don't know if you know what youre doing. im not judging, i really don't know because i'm not qualified. also i dont see anything else going on on your github but your 4.2 porting. so i cant see any references. i also dont see any commits from camcory. thats another thing i cant get an opinion about.
but arco and ivendor have proven to be pretty skilled. i remember someone saying we would never have a 3.x kernel because someone who wanted to port it would be insane...
im still thankful for what youre doing since if ivendor quits its all on you
and im sorry you got in the "just forking" cathegory and everybody else who doesn't feel he belongs there. im just generalizing...
just actually saw your sig. still doesn't change much
dr.wtf said:
you probably saw what a mess the "perfectly working cm7" was even though mazen said hes not a real developer. when the 3.4 kernel came up it turned out to be not properly ported. no offense to both of those guys since cm7 actually was usable and the kernel had its right to exist (educk, if you read this, no need to defend yourself, i've read the whole thread).
but you must understand that im kind of suspicious with new things since i don't know if you know what youre doing. im not judging, i really don't know because i'm not qualified. also i dont see anything else going on on your github but your 4.2 porting. so i cant see any references. i also dont see any commits from camcory. thats another thing i cant get an opinion about.
but arco and ivendor have proven to be pretty skilled. i remember someone saying we would never have a 3.x kernel because someone who wanted to port it would be insane...
im still thankful for what youre doing since if ivendor quits its all on you
and im sorry you got in the "just forking" cathegory and everybody else who doesn't feel he belongs there. im just generalizing...
just actually saw your sig. still doesn't change much
Click to expand...
Click to collapse
Only one thing to say:: does not make any sense at all...
What op asked is on team..wats happening here is just nonsense..if somebody interested to work with him pls do it..if u are not interested get the f** k out of here...its not must that each and everyone has to put their point of view..if u are ready to help then help..otherwise leave from this thread...simple....
Sent from my GT-I9001 using xda app-developers app
AW: [DEV] Finding a devs team
This thread needs to be closed. Its like a slap in the face for all of our developers. Shame on you! Show some respect to them. They sacrifiy a lot time to give us a better user experience for our phones but well, everyone is like "hurrdhurr dat fone is not even like a galaxy s3 now brah after flasching tis rom my fone suks bad ass".. Instead of saying thanks to the developers or donate some buck to them for a fresh beer or something.
Always remember this is a single core device, with a midrange chipset and it cant handle even close as much as a S3 or S2.
We have a fully working (vsync and tripple buffer are working and all ither stuff) Jellybean cm10. Not even the s2 or s3 have this because of the lack of sources for their exynos cpus.
I hate this unrepectless behavior.
Be happy with what you got here FOR FREE. And for a Non-flagship device like our i9001, we have A HELL OF A LOT roms and kernels!
Get your **** together people.
Sent from my GT-I9001 using xda app-developers app
Disrespectfull: YES understandeble: YES.
At our forum/development we got 1-person teams. Some ROMS are made with someone on the background (CM9/CM10/CM10.1).. But the other ROMS that are based on these are made and maintained by 1 person.
I got the feeling that some of us dont have PATIENCE..
And that is something what is very stupid.
Teams are working faster and fixing faster and better bugs in ROMS, that is true.
If the OP want to make a team just ask some developers for godssake. These topic are as disrespectfull as saying WHEN ARE YOU GOING TO UPDATE OR FIXING THIS OR THAT in every goddamm topic.
Just my opnion..
dr.wtf said:
you probably saw what a mess the "perfectly working cm7" was even though mazen said hes not a real developer. when the 3.4 kernel came up it turned out to be not properly ported. no offense to both of those guys since cm7 actually was usable and the kernel had its right to exist (educk, if you read this, no need to defend yourself, i've read the whole thread).
but you must understand that im kind of suspicious with new things since i don't know if you know what youre doing. im not judging, i really don't know because i'm not qualified. also i dont see anything else going on on your github but your 4.2 porting. so i cant see any references. i also dont see any commits from camcory. thats another thing i cant get an opinion about.
but arco and ivendor have proven to be pretty skilled. i remember someone saying we would never have a 3.x kernel because someone who wanted to port it would be insane...
im still thankful for what youre doing since if ivendor quits its all on you
and im sorry you got in the "just forking" cathegory and everybody else who doesn't feel he belongs there. im just generalizing...
just actually saw your sig. still doesn't change much
Click to expand...
Click to collapse
Alright, even through, I shouldn't have any comments here as you already screw things up really bad, I feel like I must do it to clear things up a bit around here.
First of all, you said yourself that you don't have any knowledge related to software development, so why are you messing with people that actually devote time to do it? If you have no ideea what development is, why are you talking about it in this manner? I mean, it is ok to ask or to make mistakes, everybody does, nobody is perfect but I consider this post offensive and I must defend myself here.
Second, as far as I'm consern, my GitHub is MINE and I and only I will decide when to push something there. I cannot be forced by anyone to do anything. So, your sentece "I didn's see anything going on on your github" so what?!? Tell me, why should I post anything just for you to see it? Ah, you think I lack activity? Again, so what? I or any other Open Source developer cannot be forced by anyone to publish something. We do this because we like it, we are not paid for it. Maybe if you would pay me to do these things, yeah you could have the right to judge my activity. This is open source, this is Android, the developers are bringing stuff to the end user but the end user is free to choose if he wants to use that piece of software or if he doesn't want to use that software. Same applies to you, you don't have to flash anything on your phone just because it's there online, if you don't like it, don't use it .
About my 3.4 kernel. I mentioned in the OP of the thread that it is an early "alpha" nothing more. I even used the word "preview". If the end user doesn't like the way the kernel is, than he wont use it.
Oh, and I'm not supposed to say this but I'll take this opportunity just for you to see that I'm not lacking activity and actually I want to develop that 3.4 kernel, also I'll explain why I didn't update anything on github.
I worked locally, and everytime I fixed something, 2 other errors came up, after I fixed those 2, another 3 came up and so on. That's why I choosed not to push anything to git until I get something concret. I said this a million times actually: I have no ideea when that kernel will be ready and if it will be ready, I am going to decide if it will be published to git and XDA or not. This is my personal decision, you can't influence me in any way to do anything.
Also, I'm not a full time developer, I'm still a beginer, I'm still learning things here and I choosed to share my work with others, here on XDA because I thought that my work could be usefull. If you or anyone else don't find it usefull, as I said, don't use it .
Also, ivendor won't quit either and there is nothing on me...again, you are trying to push me...this is hilarious...I choosed to start the 3.4 kernel project but that doesn't mean that I must finish it... I really hope you understood something from this post, if not please, just let it go and ignore it. Also, there is no need to apologise, you were wrong by trying to put pressure on me but I ignored it, as you probaly noticed.
Cheers,
Erik
Topic reported.
Argument:
Insulting to our developers an absolutly not development related..
Cheers
Thread Closed:
This topic has turned to a flame war and no longer serves a purpose.
Appreciate the work the devs do, as they aren't required to do anything...
~ The-Captain

[Great News] [Official] [CM12.1][Coming Soon]

Hello Everyone
I have come across device tree for Hima M9/CyanogenMod 12.1 with a custom Kernel. (If I'll tell you the name of either , you'd Google in a second)
The developer is a genius and trust me you'd see both of these within a month. Stay tuned for updates.
I can attach screenshots but I'd not post links as previous experiences that I had meant that people started troubling the developer and he quit the project all together. Respect the developers and read in my signature about development process and what it is actually like to be one.
This is just a confirmation and I can actually prove it to everyone who are interested.
I see many device tree updates every day so I am sure once CM12.1 is available officially, it'd open gates for all sorts of custom ROMs!
Attachments coming in few hours as I'm heading out
wow that would be awesome! cant wait to run a pure android rom on this beast
*all f***** fingers crossed*
Yay!
Sent from my LG-H811 using Tapatalk
Hnk1 said:
Hello Everyone
I have come across device tree for Hima M9/CyanogenMod 12.1 with a custom Kernel. (If I'll tell you the name of either , you'd Google in a second)
The developer is a genius and trust me you'd see both of these within a month. Stay tuned for updates.
I can attach screenshots but I'd not post links as previous experiences that I had meant that people started troubling the developer and he quit the project all together. Respect the developers and read in my signature about development process and what it is actually like to be one.
This is just a confirmation and I can actually prove it to everyone who are interested.
I see many device tree updates every day so I am sure once CM12.1 is available officially, it'd open gates for all sorts of custom ROMs!
Attachments coming in few hours as I'm heading out
Click to expand...
Click to collapse
The link below is to the thread which its being discussed in within m9 Q&A section. Rashid97 is the dev working on the project
http://forum.xda-developers.com/one-m9/help/cyanogenmod-12-12-1-htc-one-m9-t3069920
v1rk said:
The link below is to the thread which its being discussed in within m9 Q&A section. Rashid97 is the dev working on the project
http://forum.xda-developers.com/one-m9/help/cyanogenmod-12-12-1-htc-one-m9-t3069920
Click to expand...
Click to collapse
aaronrw said:
Yay!
Sent from my LG-H811 using Tapatalk
Click to expand...
Click to collapse
sweetrobot said:
about ****ing time!!! so sick of the nonSense...
cm / aosp / aokp ftw.
paperweight for the last couple of months. tried a bunch of the existing roms, just not my cup of tea.
Click to expand...
Click to collapse
k1moe said:
wow that would be awesome! cant wait to run a pure android rom on this beast
*all f***** fingers crossed*
Click to expand...
Click to collapse
I am afraid that is not it what you are pointing out.
Here are the screenshots.
You can clearly see that how much commits are posted daily and it is going on at a very brisk rate. Cheer up everyone!
Request :
Just please do not trouble the developer if you find out who is he.
READ THIS HERE
Alternatively you can see more information in my signature!
Hnk1 said:
DEVELOPMENT PROCESS
INTRODUCTION
I am starting this forum in hope of educating my readers about ROM development according to my experiences. Further, I will highlight what is the usual developers' thought process before they decide to build a ROM for a specific device. The reasons why they usually choose a certain device or why they prefer one device over another would also be stated briefly. I also have intention of looking into ways how we can speed up ROM productions for any device and what you can do to play your part.
I UNDERSTAND YOUR FRUSTRATION FOR NO CUSTOM ROMS EVEN AFTER SOME MONTHS BUT THIS DOESNOT GIVE YOU THE RIGHT TO SPAM
I am sure many of you must be really disappointed by the lack of development for your device and I know this must be frustrating when we see other devices are getting ROMS so quickly. I know many are too excited when they find a little about any OTA/ Custom ROM and sharing such news is fully justified. However, it's beyond my logic & thinking why the forums are SPAMMED for any little information they might find anywhere regardless of their sources or if it has been ALREADY POSTED. I reckon many of these threads could have been avoided by simply searching in the forum.
ROM DEVELOPMENT
I can assure you that many develoeprs are working very hard to PORT and develop different ROMS for a device. However, the reason we can not see any CUSTOM roms till yet is due to complicated nature of a device itself.
Usually developers prefer a device which is :
1. Easy to work with, less complicated to code with or in other terms DEVELOPER friendly. For example, for a while I had a real issue with HTC phones as they have too many things to work with like Bootloader, S Lock, Radios, Hboot version etc while in Nexus devices you only need to unlock your device with one fastboot command. That's all and you are ready to flash ROMs.
2. Personal preference of Device. This simply means that we all have different tastes and thus we choose different devices. A certain developer might only work for a certain brand while other might work with few brands. This has nothing to do with anything but a personal choice.
3. A device that promises reward in terms of money/self satisfaction. Developers usually go for devices which have most active users so if their intention is also to get some money out of it in terms of donation, this will work well with devices which are more in number.
4. Knowledge about a certain brand more than another.
5. MONEY TO BUY A CERTAIN DEVICE/DEVICES. Suppose a developer wants to make ROMS for Xperia L/ SP/Z and Xperia U. Yet he only has 500 dollars to choose from. He then will have to make a choice between devices and this will eventually mean that not all of the devices get the same treatment. Money is the most decisive factor why a developer doesnot chose your device but rather another. For example purpose only, if I have to choose between devices, I might prefer SP over Xperia L as I can see more future of SP than Xperia L(I might be wrong).
6. Simply he bought a device or it is gifted/donated to him
SOME REQUESTS
Please STOP bugging developers by trivial questions. Just think how many other people ask the same question and it gets very frustrating to actually work on the device itself.
Every developer has a LIFE apart from developing ROMs. They also have a family, school, work, hobbies, bad days and so much like us. So they will do it when they feel like doing it. Just sit back and relax. Enjoy your device until developer releases the ROM for your device. Asking a REASONABLE question seems plausible but asking same questions/useless questions without using brains is just STUPID. Kindly refrain from that.
If you have seen a developer who has taken the initiative to work on your device , the best thing to do is to be patient. Let him concentrate. Spamming and spamming again won't help really.Yet some users start SPAMMING developers, their twitters, blogs and accounts. That's really sad. You can discuss on the forum what you think about it but IRKING developers isnot really cool.
WHAT CAN YOU DO TO HELP DEVELOPERS AND SEE CUSTOM ROMS.
1. Search the form first and look for answers. DON'T start new posts/questions/threads when it is ALREADY mentioned in some other section.
2. STOP PMing/SPAMING developers but rather ask a question WHICH havenot been asked before in the forum. Do not engage in the habit of making a new forum for everything. Try to keep threads as little as possible.
3. Follow developers and see what they have updated about on their official twitter,facebook,etc rather than bugging them on different forums/social websites.
4 DONATE THEM. DONATE THEM . DONATE THEM!
The amount of efforts they put, sitting for hours in front of their PCs and I know how frustrating it gets when you try to run commands and everything seems to work yet you can not boot up your ROM. And worse, you can not find WHY really. Just a change in line in build.prop results in failure of ROM to boot up and specially working from source to build ROM is really really tough. The best thing you can do is being supportive and patient !
A ROM development requires not just EXCESSIVE amount of hardwork, time, energy and dedication but also they need MONEY to actually buy devices and try it on. They are happy and encouraged to keep on developing ROMs when they see their efforts are not wasted and they are rewarded and respected for what they do.
SOME BASICS OF ROM DEVELOPMENT
Usually this is required to make a full custom ROM
Blobs which contain hardware information which comes from hardware manufacturer like Qualcomm in case of Snapdragon processors
A fully functional device tree
Latest Android source (Or the android version source you want to build for)
Specific Custom ROM coding which is based on Android Source
Usually a device tree and kernel tree is needed before custom roms can be made available. This is a long trial and error process in which every component of hardware is made functional as usually manufacturers do not provide any code for their devices and thus new code is to be written which is very frustrating and long process!
Click to expand...
Click to collapse
Hnk1 said:
I am afraid that is not it what you are pointing out.
Here are the screenshots.
You can clearly see that how much commits are posted daily and it is going on at a very brisk rate. Cheer up everyone!
Request :
Just please do not trouble the developer if you find out who is he.
READ THIS HERE
Alternatively you can see more information in my signature!
Click to expand...
Click to collapse
What i pointed is where the developer actually mentioned he his working on it and the link can be sourced by anyone, and people in that thread have been checking the github as mentioned. Theres now two threads on the discussion of cm12.1 which talk similar. All you are doing is not mentioning the dev based someone who used his work without his permission. Also to add the dev replied that thread to have to say they having working booting img just some features aren't working.
Link to his github for the current work
https://github.com/Hima-Dev/android_device_htc_hima-common
Thank GOD
---------- Post added at 01:33 PM ---------- Previous post was at 01:32 PM ----------
I'll be happy to donate
I'm really excited about this, because the person doing this is making amazing progress and at last count I want to say it was only Wi-Fi and one other thing not working with said developer already pretty certain that they know how to change that, it's just a lot of trial and error (any dev knows how frustrating it can be having to compile the source all over again to test a tiny change)
What this means for me, personally, is that I can do what I've done on past htc devices and knock out a fairly complete port of miui (some default miui stuff doesn't play nice during flash, like the camera app, so I'll likely include the stock m9 camera app as packaged for other phones so it doesn't rely on sense)
Anyway... ?
v1rk said:
What i pointed is where the developer actually mentioned he his working on it and the link can be sourced by anyone, and people in that thread have been checking the github as mentioned. Theres now two threads on the discussion of cm12.1 which talk similar. All you are doing is not mentioning the dev based someone who used his work without his permission. Also to add the dev replied that thread to have to say they having working booting img just some features aren't working.
Link to his github for the current work
https://github.com/Hima-Dev/android_device_htc_hima-common
Click to expand...
Click to collapse
Cheers for side information. I know the developer and I'm pretty sure you'd get a kernel and Cm12.1 pretty soon.
Actually I Would let the developers sort out their differences themselves, for me it is Cm12.1 coming pretty soon.
agentfusion said:
I'm really excited about this, because the person doing this is making amazing progress and at last count I want to say it was only Wi-Fi and one other thing not working with said developer already pretty certain that they know how to change that, it's just a lot of trial and error (any dev knows how frustrating it can be having to compile the source all over again to test a tiny change)
What this means for me, personally, is that I can do what I've done on past htc devices and knock out a fairly complete port of miui (some default miui stuff doesn't play nice during flash, like the camera app, so I'll likely include the stock m9 camera app as packaged for other phones so it doesn't rely on sense)
Anyway... ?
Click to expand...
Click to collapse
Whhhaaatttttt?!?!?! Miui?!?!?
Wait
Galaxysm said:
Whhhaaatttttt?!?!?! Miui?!?!?
Click to expand...
Click to collapse
Yeah. Once we have a reliable port of CM12, then porting other stuff is pretty easy. All I have to do is find a device that already has miui with the same resolution and dpi/ppi and port the assets over to the m9.
Preferably I'd like to port the miui patchrom so I can setup an automated build system to build a fresh copy every time aosp and miui are updated, but I don't have anywhere near enough time for that.
agentfusion said:
Yeah. Once we have a reliable port of CM12, then porting other stuff is pretty easy. All I have to do is find a device that already has miui with the same resolution and dpi/ppi and port the assets over to the m9.
Preferably I'd like to port the miui patchrom so I can setup an automated build system to build a fresh copy every time aosp and miui are updated, but I don't have anywhere near enough time for that.
Click to expand...
Click to collapse
Nice I can't wait!!
Nice to see this coming ... And for MIUI I haven't been able to use it since I change my original EVO ... It would be great to have it as an option ...
Great news
Daily reminder that CM12 is a desperately needed and coveted thingy for the m8+1.
Is it lollipop 5.1?
Sent from my HTC One M9 using XDA Free mobile app
vegetaleb said:
Is it lollipop 5.1?
Sent from my HTC One M9 using XDA Free mobile app
Click to expand...
Click to collapse
Cm12.1 is lolipop 5.1
Anyone knows the progress on this...
epedrosa said:
Anyone knows the progress on this...
Click to expand...
Click to collapse
Be patient. The OP says "within a month" and it has only been roughly 2 weeks

Categories

Resources