Subforum or thread to discuss CM nightlies? - Nook Color Q&A, Help & Troubleshooting

Subforum or thread to discuss CM nightlies? - Nook Color Q&A, Help & Troubleshooting

Is there an xda thread that discusses CM releases nightlies & stable for the Nook color )Encore)? The forum on CM is not very active & I don't find many postings that say things like "Ok, I tried CM7 nightly #95 & I have encountered these problems." It would even be nice to have a running poll that rates the functionality of new releases. That way, those who don't have the time to deal with new bugs can judge whether or not to move to a new CM release & fix a bug they may have. I am trying to use my NC in a productive way, but I would like a few issues fixed, but need some of the "tools" to still work. Maybe the solution in my case is to install only stable releases, but the last stable was on 5/8 & I got impatient & installed some nightlies.
Cheers,
kev

bugeyed1 said:
can judge whether or not to move to a new CM release & fix a bug they may have. I am trying to use my NC in a productive way, but I would like a few issues fixed, but need some of the "tools" to still work.
Click to expand...
Click to collapse
A big issue is that the developers officially consider the nightlies to be a "use at your own risk" type situation. Since CM7 is a pure community project, the developers work on whatever bugs effect them directly or ones that are so egregious that they effect everyone (like SOD). There is no process for the community to decide which bugs gets fixed because that comes close to breaking the first rule of cyanogenmod.
Maybe the solution in my case is to install only stable releases, but the last stable was on 5/8 & I got impatient & installed some nightlies.
Click to expand...
Click to collapse
That is exactly what the answer is from developers that on this forum- stick to the stable releases if you want stable. Of course then the issue is that you miss out on some great improvements for a while (like working sleep), so in the end you have to chose:
A. A stable, non-fully functioning version.
B. A nonstable, functional-hopefully nightly.
For many of us used to open source development, this dichotomy between broken and stale is the norm.
If you are having real issues it is best to post them in the CM7 developers thread where they will be read, and hope that a kind developer chooses to work on that issue after you post it!

poofyhairguy said:
For many of us used to open source development, this dichotomy between broken and stale is the norm.
Click to expand...
Click to collapse
As a Debian Sid user, I would be bored if it were any other way.
The Nook has the great perk of booting off an sd card by default, which really diminished my reasons for not staying on top of the nightlies. (I grab one every few days instead of daily but that is more to conserve their bandwidth than a fear of what I will get.)

Related

Devs, Please don't hide your Known Issues

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Assemble Dev Team for an ICS ROM

As our device is dying in support I feel that we need to develop a large development team (10+ people) that will work on ICS for our gtablet. I mean after all our device is capable of running it ( Tegra 250). If you would like to be part of this team shoot an email to [email protected] explaining why you want to be part of this team and what you can contribute. Thank you.

You know that you need a new kernel for ICS to work properly right? Ch3vr0n5 and dpw13 are currently working on it over at slatedroid.

lol. i was gonna post something similar to this in the next couple days. I made the n1 ics port and started work today trying to get ics booting on my gtab. I think first order of business is to start a room on freenode.
#tegratab_ics_dev
all interested parties please join
btw im drewis

texasice said:
lol. i was gonna post something similar to this in the next couple days. I made the n1 ics port and started work today trying to get ics booting on my gtab. I think first order of business is to start a room on freenode.
#tegratab_ics_dev
all interested parties please join
btw im drewis
Click to expand...
Click to collapse
guys,
pm jazzruby, tek112 or fosser2, ch3vron..they are also over @ slatedroid viewsonic gtablet forum..
they have been working on a kernel with hw accel for HC3.2 and ICS. There are been some teaser pics by fosser with ics running on his gtablet.
I'm sure they could use your help...
kernel dev in the gtablet laboratory forum as well.

Cyanogen: Our goal is to provide continued support to all CM7 devices back to the QSD8250 series of devices such as the Nexus One. (12/2/2011)
Click to expand...
Click to collapse
The CyanogenMod team has also said they will continue to support our gTabs so I am looking forward to CM9 which hopefully will drop some time in January.

sjmoreno said:
The CyanogenMod team has also said they will continue to support our gTabs so I am looking forward to CM9 which hopefully will drop some time in January.
Click to expand...
Click to collapse
uhm based on what you quote nothing is said there we dont have qsd in our gtabs...

If anyone is interested and has dev experience shoot me a pm and i'll get you up to date. thanks

Yea upon further investigation there are already a few people working on this. In fact a quick google search will find you a booting cm9 for gtab. (i dont want to post the link since it is pre alpha and not my rom) but the gtab is not lacking devs by any means. (they just arent on xda)
oh and forget my post about the irc room there is already one. but again you must find it yourself
dont know why the pic is green but whatever

texasice said:
Yea upon further investigation there are already a few people working on this. In fact a quick google search will find you a booting cm9 for gtab. (i dont want to post the link since it is pre alpha and not my rom) but the gtab is not lacking devs by any means. (they just arent on xda)
oh and forget my post about the irc room there is already one. but again you must find it yourself
dont know why the pic is green but whatever
Click to expand...
Click to collapse
I appreciate that you didn't post the link to this, and please anyone else who "finds" this build (yes its out there) please do not post it anywhere either. It is extremely beta and has many problems (to the point where you would have to open your tablet to push the internal reset button). Thanks

i really don't appreciate this elitist dev crap. "yeah there's a place where you can talk about it, and a build you can get to try it, but i'm not going to tell you where." i completely understand that the devs are doing work that we (I) can't do and that they're entitled to a bit of leeway for that but if they're going to talk about their work in public and post shots, they're just doing it to get a rise out of people. there is no valid reason to restrict people from trying out alpha builds except to keep others out of their club.
of course, if you want to install something against the advice of someone who knows a lot more than you do, that's your perogative but you assume all responsibility. it does absolutely make sense that the devs want ZERO whining or "bug reporting" from alpha builds. ostensibly, the devs and those with technical acumen are trying to protect newbs who might fry their tabs. to my thinking however, nothing would make someone learn faster not to flash random **** than a $300 brick. we're all intelligent humans and not children, however, so
links:
cm9 alpha (install script edited)
gapps
original file
note: THIS IS NOT A DAILY DRIVER. i tested it on a 1.2BL tab. i had to turn off the getprop script asserts to get it to install, which is usually bad form. it boots, but we have no hw acceleration, no wifi, no camera, no sound, no usb storage or adb... etc. this is just a taste, proof that work is being done.
irc is freenode #gtab_kerneldev

Notion ink adam is getting official ICS, I suppose that will help a lot?

iammuze said:
i really don't appreciate this elitist dev crap. "yeah there's a place where you can talk about it, and a build you can get to try it, but i'm not going to tell you where." i completely understand that the devs are doing work that we (I) can't do and that they're entitled to a bit of leeway for that but if they're going to talk about their work in public and post shots, they're just doing it to get a rise out of people. there is no valid reason to restrict people from trying out alpha builds except to keep others out of their club.
of course, if you want to install something against the advice of someone who knows a lot more than you do, that's your perogative but you assume all responsibility. it does absolutely make sense that the devs want ZERO whining or "bug reporting" from alpha builds. ostensibly, the devs and those with technical acumen are trying to protect newbs who might fry their tabs. to my thinking however, nothing would make someone learn faster not to flash random **** than a $300 brick. we're all intelligent humans and not children, however, so
links:
cm9 alpha (install script edited)
gapps
original file
note: THIS IS NOT A DAILY DRIVER. i tested it on a 1.2BL tab. i had to turn off the getprop script asserts to get it to install, which is usually bad form. it boots, but we have no hw acceleration, no wifi, no camera, no sound, no usb storage or adb... etc. this is just a taste, proof that work is being done.
irc is freenode #gtab_kerneldev
Click to expand...
Click to collapse
Well aren't you cool, learning how to use google and ****.
EDIT: Ok now that I'm done fuming about this. The release that was posted is an early build of CM9. It is based off of Android 4.0.3. The kernel that is included with that release is linux 2.6.36. Since then, we have now moved onto 2.6.39. In no way is the "dev" group elitist. At any time anyone could have joined the IRC group and asked for a download link to the latest kernel/rom. The reason this has not been released yet is because of the "power button" script. When the power button is tripped at random times it causes the entire tablet to freeze up. The only way to "reset" the tablet is to open it up and press the internal reset button, thereby voiding any warranty from Viewsonic. Another issue that I have seen with using this kernel is possible damage to the camera. Just a few days ago I learned that while running this kernel the camera heats up and is hot to the touch, almost to the point of burning yourself. I have since then, unplugged the camera from the mainboard, to hopefully stop damage to the camera (I'm guessing that whoever has run this already without unplugging their camera, has potentially fried it). In short, installing this rom does give you some latest and greatest software to play with, but with it comes risks. DO NOT INSTALL THIS ROM/KERNEL IF YOU DO NOT WANT TO RISK DAMAGING YOUR TABLET.
ps. As a dev. team, we will be releasing HC with a .36 kernel that supports hw accel very soon. Keep your heads up for that release. Hopefully this release can hold people over until everything becomes more stable. Thank you all for patiently waiting.

fosser2 said:
Well aren't you cool, learning how to use google and
ps. As a dev. team, we will be releasing HC with a .36 kernel that supports hw accel very soon. Keep your heads up for that release. Hopefully this release can hold people over until everything becomes more stable. Thank you all for patiently waiting.
Click to expand...
Click to collapse
Kids.....they think they know everything! Haha, just kidding but hopefully maybe people understand why now. Im pumped about the HC release! Im tired of froyo and can't wait to play the THD games that required 2.3+. Thank you and the rest of the team so much for your hard work. Im not a programmer but im going to start digging for the technical info you need for the camera.

fosser2 said:
Well aren't you cool, learning how to use google and ****.
EDIT: Ok now that I'm done fuming about this. The release that was posted is an early build of CM9. It is based off of Android 4.0.3. The kernel that is included with that release is linux 2.6.36. Since then, we have now moved onto 2.6.39. In no way is the "dev" group elitist. At any time anyone could have joined the IRC group and asked for a download link to the latest kernel/rom. The reason this has not been released yet is because of the "power button" script. When the power button is tripped at random times it causes the entire tablet to freeze up. The only way to "reset" the tablet is to open it up and press the internal reset button, thereby voiding any warranty from Viewsonic. Another issue that I have seen with using this kernel is possible damage to the camera. Just a few days ago I learned that while running this kernel the camera heats up and is hot to the touch, almost to the point of burning yourself. I have since then, unplugged the camera from the mainboard, to hopefully stop damage to the camera (I'm guessing that whoever has run this already without unplugging their camera, has potentially fried it). In short, installing this rom does give you some latest and greatest software to play with, but with it comes risks. DO NOT INSTALL THIS ROM/KERNEL IF YOU DO NOT WANT TO RISK DAMAGING YOUR TABLET.
ps. As a dev. team, we will be releasing HC with a .36 kernel that supports hw accel very soon. Keep your heads up for that release. Hopefully this release can hold people over until everything becomes more stable. Thank you all for patiently waiting.
Click to expand...
Click to collapse
Thanks to all the Devs working on this stuff for us! That said if you guys need any testing done just shoot me a PM, I rarely use my tablet any more and have cracked it open plenty of times for other hardware testing. I don't have much time to work on software anymore, but am more than willing to test stuff for you if you don't wish to risk your tablets. Again thanks for all your work.
Sent from my Nexus S using XDA App

MOD EDIT:
FORUM RULES:
Encouraging members to participate in forum activities on other phone related sites is prohibited.
Off-site downloads are permitted if the site is non-commercial and does not require registration.

Closing this thread - this is just getting out of hand folks.

ROMs ROMs and more ROMs

Can someone tell me whats up with the 50+ ICS ROMs? It's a bit concerning that all this effort seems to be put into reproducing the same exact thing. I think the community would benefit from cooperation rather than competition... But I feel like I must be missing something here, I am new to the Nexus S but not to Android, is there something about the Nexus S community that I'm not getting?
Not complaining at all, or should I say, I'm not trying to complain. I also want to point out that I appreciate the developers who pour their time and effort into our devices and help us to get the maximum value out of them.
(Want to note, I am running AOSP's ICS build and loving it.)

joenathane said:
Can someone tell me whats up with the 50+ ICS ROMs? It's a bit concerning that all this effort seems to be put into reproducing the same exact thing. I think the community would benefit from cooperation rather than competition... But I feel like I must be missing something here, I am new to the Nexus S but not to Android, is there something about the Nexus S community that I'm not getting?
Not complaining at all, or should I say, I'm not trying to complain. I also want to point out that I appreciate the developers who pour their time and effort into our devices and help us to get the maximum value out of them.
(Want to note, I am running AOSP's ICS build and loving it.)
Click to expand...
Click to collapse
Hey Man, I am much similar to where you are right now. I am not new to Nexus S or Android, but I feel that the abundance of ROMs is a good thing.
Having so many ROMs shows that the device is still running very strong: Something Android phones NEED to have behind them.
On the other hand I dislike it. To all the developers out there, I think you guys are amazing and genius no doubt. So take the following lightly...
What people don't like to see when browsing for a ROM is a dozen ROMs that are all identical. We need something new and fresh, hence why I like MIUI.
What I think should be done is as you said, have co-operation to make one master ROM because we have hundreds of people in the Nexus S community ready to help.
Speaking on my behalf I HATE SO MANY ROMs Because I simply cannot decide which is best because they are all similar in many ways, and I don't have time to try each one out as much as I want to. I do like having these ROMs but when it comes to choosing one its a big choice for me.
Any feedback on this?

I agree with a not so great abundance or ROMs. But most are not devs. They are simply "chefs" because they never actually developed anything. They just price and scrap things from source to mods. Cm9, ASOP, Peter A(because of his radios and kernal) are devs. We have lots of chefs.
I made brickROM just because of this situation. Its never been done, but the community wasn't ready for it yet.
Either way you can tell what rom has Is "real" I would say there's about only 5
And its sad for new Android users that come here get presided by a catching slogan and rob themselves from using a much better rom
Sent from my Nexus S 4G using XDA App. Developer of brickROM, and OP of XDA Thread of The Year 2011.

What would you do if you don't like any of the existing ROMs? May be one is missing a feature you need, another just has too many features you don't want? The answer is simple -- create your own ROM, or modify an existing one... I think most devs just make the ROM they want to use as their daily driver and simply share it here (i.e. what's going on is not about competition, at least from my point of view)
It sounds good to gather all devs to create a ROM that suits everyone's needs, but IMHO it is nearly impossible to do that

suksit said:
What would you do if you don't like any of the existing ROMs? May be one is missing a feature you need, another just has too many features you don't want? The answer is simple -- create your own ROM, or modify an existing one... I think most devs just make the ROM they want to use as their daily driver and simply share it here (i.e. what's going on is not about competition, at least from my point of view)
It sounds good to gather all devs to create a ROM that suits everyone's needs, but IMHO it is nearly impossible to do that
Click to expand...
Click to collapse
But these futures found in everyone's ROM are just mods that you can flash. I flash 8 zips with every rom update but I know that a personal mix so I have no need to share it.
I'm capiale of changing my waklppaer
I flash custom font, and inverted apps with some tyranny Widgets and kernal. With gnex sounds. No reason to "cook" it. This is not development.
Sent from my Nexus S 4G using XDA App. Developer of brickROM, and OP of XDA Thread of The Year 2011.

Reserved
Sent from my Nexus S 4G using XDA App. Developer of brickROM, and OP of XDA Thread of The Year 2011.

suksit said:
It sounds good to gather all devs to create a ROM that suits everyone's needs, but IMHO it is nearly impossible to do that
Click to expand...
Click to collapse
The CyanogenMod team pull it off quite well, all that is needed is a bug tracker and patch review system and boom! instant cooperation.
Maybe we have too many "chefs" in the kitchen

joenathane said:
The CyanogenMod team pull it off quite well, all that is needed is a bug tracker and patch review system and boom! instant cooperation.
Maybe we have too many "chefs" in the kitchen
Click to expand...
Click to collapse
I am agree with you CyanogenMod need a bug tracker for CM9.

Here is an interesting fact in case anyone didn't know but MR. Cyanogen himself is rocking a Nexus S http://twitter.com/#!/cyanogen/status/153353404159234049
I wonder what build of ICS he is running, probably from his own private reserve...

joenathane said:
The CyanogenMod team pull it off quite well, all that is needed is a bug tracker and patch review system and boom! instant cooperation.
Maybe we have too many "chefs" in the kitchen
Click to expand...
Click to collapse
I will be honest here and say that I personally dislike Cyanogen Mod for the most part. True that they are the gut best in performance, but if the only ROM I had was Cyanogen, I would not be very happy with it. I just think that for my favor, Cyanogen focus' so much on power, yet takes the look of the ROM as a after thought. The modified music on Cyanogen ROMs and the overall execution of his work lacks style and design, as if he first said "Make it fast, then maybe make it look ok" MIUI on the other hand has a great deal invested in how it looks which gives a very effective illusion of performance.
I think that the problem is we have so many chefs in that small kitchen and they have all made so many great dishes that sooner or later they will have eventually all used the same spices by some point, so we are beginning to lose that uniqueness in each one.

LGIQEXPO said:
I will be honest here and say that I personally dislike Cyanogen Mod for the most part. True that they are the gut best in performance, but if the only ROM I had was Cyanogen, I would not be very happy with it. I just think that for my favor, Cyanogen focus' so much on power, yet takes the look of the ROM as a after thought. The modified music on Cyanogen ROMs and the overall execution of his work lacks style and design, as if he first said "Make it fast, then maybe make it look ok" MIUI on the other hand has a great deal invested in how it looks which gives a very effective illusion of performance.
I think that the problem is we have so many chefs in that small kitchen and they have all made so many great dishes that sooner or later they will have eventually all used the same spices by some point, so we are beginning to lose that uniqueness in each one.
Click to expand...
Click to collapse
The only problem with that is Miui uses CyanogenMod code as a base(http://en.wikipedia.org/wiki/MIUI#Development) and CyanogenMod 7 has the theme chooser integrated for easy themeing(check the last three links in my signature to see some themes I created for it).
I don't think any mod team have contributed more to Android than the CyanogenMod Team, they certainly have my respect for that.
I agree about the spices, all these chefs cooking the same exact entree and now which on to choose...

joenathane said:
The only problem with that is Miui uses CyanogenMod code as a base(http://en.wikipedia.org/wiki/MIUI#Development)
Click to expand...
Click to collapse
It's a fact, not a problem.
Back on topic,
LGIQEXPO said:
I think that the problem is we have so many chefs in that small kitchen and they have all made so many great dishes that sooner or later they will have eventually all used the same spices by some point, so we are beginning to lose that uniqueness in each one.
Click to expand...
Click to collapse
I believe at some point the community will decide which dishes live and which will die. I don't think people will keep posting ROMs if nobody uses it.

suksit said:
It's a fact, not a problem.
Back on topic,
I believe at some point the community will decide which dishes live and which will die. I don't think people will keep posting ROMs if nobody uses it.
Click to expand...
Click to collapse
This^^ plus one thing, good all these chefs are popping up, that's showing a swell in number of people interested in development, in the end it can only have a positive outcome. Let em dev.
Sent from my Nexus S 4G using Tapatalk

suksit said:
It's a fact, not a problem.
Click to expand...
Click to collapse
I obviously didn't mean problem in that sense, I meant it as in the 'problem' with his argument not the problem with CyanogenMod or Miui, I'm not sure how you interpreted it the way you did...
suksit said:
I believe at some point the community will decide which dishes live and which will die. I don't think people will keep posting ROMs if nobody uses it.
Click to expand...
Click to collapse
what about the "noobs" who are instantly confronted with 20+ ICS ROMs and not a clue to which is worth its weight in salt?

joenathane said:
I obviously didn't mean problem in that sense, I meant it as in the 'problem' with his argument not the problem with CyanogenMod or Miui, I'm not sure how you interpreted it the way you did...
Click to expand...
Click to collapse
Sorry if I interpreted it wrong (English is not my native language anyway ) I thought you're trying to imply that "since MIUI is based on CM, @LGIQEXPO shouldn't compare them together" or "if you like MIUI, it means you already liked CM." Just wanted to say that it is not a problem if one wants to compare those two.
joenathane said:
what about the "noobs" who are instantly confronted with 20+ ICS ROMs and not a clue to which is worth its weight in salt?
Click to expand...
Click to collapse
Occasionally I'd see a thread titled "Help me decide which ROM is best" and the most popular answer would be "Why don't you try them all?" Yeah it would be madness to try all 20+ ROMs in a row, but I don't think anyone will do that.
Before flashing a ROM, I'd (suggest them to) read everything in the first few posts by the OP, and take a look at the screenshots (most of the time I can decide if I will like this ROM or not by these two factors) If those "noobs" are not too ignorant I believe they'll have a small list of ROM(s) they want to try (may be 4-5 choices, which is reasonable.)

I know it is on the same code, but I more so meant the apps that MIUI re-did for their ROMs, and how they offer a nice end user appeal.
What would be amazing is if all the known devs of these ROMs would just once come together to use their own strengths, and make a mast ROM out of it. MIUI Design and style, Cyanogen tweaks and speed, Peter A. stability, the overclocking everything! (I can't wait for that hahah )

you want fewer rom, get a ns4g. Although we only have a fraction of the roms found in the other forum, they all seem to have their own distinct character.

i was using an SII before this so i was a frequent on that part of xda.. they do have a separate page for original development and another one for development (being kitchen products)

Hey,
Just wanted to add my opinion in all of this that there are so many "equal" roms.
I as some mentioned on another thread am a chef to rom developing, and I don't mind.
Why I do this is because I don't have the time or knowledge to create Android source apps so I take what I think is the best from each rom and create my own.
For example for me CM9 is way to bloated with too many configurations and options I prefer a more real cleaner AOSP, something like Peter Alfonso (buglessBeast), but I do like the T9 dialer from CM9, so I cherry-pick that from CM9 and add it to a PA base.
Also for the notifications power menu I liked TeamKang one so I added that. That way I'm making my own custom rom to my liking and also I don't have to be flashing 20 zips every time there is a new update or wipe my phone
I just thought on sharing it just if some one has the same likes in roms I'm no asking for anything in return. Also I do this in my little free time.
Sent from my Nexus S 4G using XDA App

mandaman2k said:
Hey,
Just wanted to add my opinion in all of this that there are so many "equal" roms.
I as some mentioned on another thread am a chef to rom developing, and I don't mind.
Why I do this is because I don't have the time or knowledge to create Android source apps so I take what I think is the best from each rom and create my own.
For example for me CM9 is way to bloated with too many configurations and options I prefer a more real cleaner AOSP, something like Peter Alfonso (buglessBeast), but I do like the T9 dialer from CM9, so I cherry-pick that from CM9 and add it to a PA base.
Also for the notifications power menu I liked TeamKang one so I added that. That way I'm making my own custom rom to my liking and also I don't have to be flashing 20 zips every time there is a new update or wipe my phone
I just thought on sharing it just if some one has the same likes in roms I'm no asking for anything in return. Also I do this in my little free time.
Sent from my Nexus S 4G using XDA App
Click to expand...
Click to collapse
Thanks for adding your voice to the discourse.
If I was asked to offer an opinion on what you do, this is what I would say....
I think what you do is okay for you, but the problem is when you release it. There is a problem because as you state, you cherry pick features and/or "code" from other ROMs, and that can/will lead to issues for your user base. Lets take for example the T9 dialer, what happens when security bugs are found and fixed and optimizations make it into an update of the T9 dialer? Well that would mean you would need to update your ROM, but what if you're busy with your job or just with life and are too busy to get around to it? Well now your users of your ROM are without those security, bug fixes and optimizations, and multiply that by all the other pieces of the ROM that you cherry picked from other sources.
My point here to be clear is that due to the nature of your ROM, it will always lag in patches to security issues, bug fixes and optimizations and I think that is ultimately a disservice to your user base.
There is a value that you create, so I guess the question here is, does that value of bringing all these pieces into one convenient package outweigh the negatives of the lagging patches/fixes?
I mean no offense, and I hope this isn't taken as such, I just want to encourage some discourse on these things...

Our phone is not dead!!!!

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Phone is dead

[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

Database Users

welcome