Related
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!
Ok, is this *normal* that one by one the devs (jac, kk, sombionix and the rest of tw, and now - eugene373) proclaimed, effectively, that are abandoning (at least to a certain degree) xda? Their personal conflicts (which are unlikely our business) aside, is there anything else that feeds this tendency? In particular, are the xda modes doing enough (or anything at all?) to diffuse and perhaps reverse the trend? Or am I wrong to assume that this would be their business? I witnessed that 90% of (sane) xda members are being as supportive as ever to devs. There are, of course, the challenged ones, but it's the internet. So I don't see anything that regular (sane) members did wrong. And yet the facts are... disturbing.
P.S. Oh, and, after a week of admiring 'wannaby modes' nonsense here, do you mind not telling me that this thread doesn't belong to general or is off-topic? The point of this is to discuss if anything can be done to prevent that many see as an unfortunate trend in *vibrant* section.
I don't know about JAC or KK, because they are the older developers who works on the I9000 model before I even get a chance to visit XDA.
I believe that Team Whiskey moved out because they want to have their own support forum, with dedicated Donator Section for their supporters. Also to provide more ROM specific support for their ROMS.
As for Eugene, I am not too sure, but it may be due to people no respecting his work?
P.S. When did Eugene said that he is 'leaving' XDA?
He never said this. But he explicitly said that he is abandoning specific xda threads (which is, obviously, his full right) and will be posting only on his site.
i can understand this. Its starting to turn into a business, if they want to post their work that they put time into on their own website, that is their full right, and it makes sense. And it shouldnt be that big of a deal, its not that hard to make an account on either of their websites to gain access to their forums. So if they want to make their ROM's a little more private, then i give permission haha
While it's unfortunate, it seems pretty necessary to me. It's impossible to continue to have all discussion on a particular ROM in a single thread. It makes it much harder to find bug reports, for example. So having your own forum and website dedicated to your own ROM makes sense.
Just because they're leaving XDA doesn't mean they're gonna stop coding. And all of the devs know quite well that XDA is the best place to inform people about their ROMs.
Oh well I hope team whiskey makes a mobile app for theyre site
Still flashing , thanks to odin
Just for your knowledge..
KK was banned
JAC well know one knows
But just because most of us are opening our own sites doesnt mean we are going to jump away from XDA.
XDA is a great way to get our names out there..
Our personal sites are just so you guys have all our work in one location & can ask more questions or request features there. (Or that is was I do)
Keeping it classy, o yeah.
XDA is the hub... their sites are the gold mines.
Keep supporting the developers as much as you can, and that Vibrant is going to always be in tip-top form.
Master™ said:
Just for your knowledge..
KK was banned
JAC well know one knows
But just because most of us are opening our own sites doesnt mean we are going to jump away from XDA.
XDA is a great way to get our names out there..
Our personal sites are just so you guys have all our work in one location & can ask more questions or request features there. (Or that is was I do)
Click to expand...
Click to collapse
I missed what kk was banned for possibly a little before my time here
Still flashing , thanks to odin
I try to keep the Wiki updated with information. Although it is not mine to house hold so if anyone else want to add their 2 cents to the wiki please do so. Eugene just want to post his stuff in his forum for what the other people mentioned. Which is his full right. And is still going to keep tabs on XDA as it is a good place to get together.
reuthermonkey said:
While it's unfortunate, it seems pretty necessary to me. It's impossible to continue to have all discussion on a particular ROM in a single thread. It makes it much harder to find bug reports, for example. So having your own forum and website dedicated to your own ROM makes sense.
Click to expand...
Click to collapse
Ok, so maybe the xda mods need to show a bit more flexibility to better accommodate devs needs? Check either TW or Eugene's forums. Essentially, they replicate (nearly 1:1) the structure of xda vibrant sections. I understand that devs want more control over their threads and better organization. But it seems to me that it wouldn’t be that hard to implement the same right here:
A) create a separate sticky for each developer’s project
B) give devs certain mod rights within their threads
Again, I am certainly not against personal web sites, etc. And in no way am I trying to critisize the devs here (obviously it's their right to do whatever they feel like doing!). I am just trying to understand if xda is adopting to the situation. Maybe some small changes at xda can help to prevent the further devs fragmentation. I think nobody would want to see xda becoming just a hub for links to personal sites. Discussion, exchange of ideas, healthy competition (ok, this one may need to be put on hold for a while), comparative reviews like the one that swehes is doing are SO MUCH better when devs are actively participating.
EDIT: Actually, I suspect that if devs had a right to edit their own threads, some (if not most) conflicts would have never become public at the first place.
And the thread was closed... (Dissent causes censure).
Fellow Community: Something going arawy in the Samsung I9100 (Galaxy S2) forums.
The purpose of me opening this thread is to ensure community discussion occurs.
With good intentions, our User Experinance Admin @sveitus has sliced apart The Samsung Galaxy S II Android Development, hiving off `the cream` into The Samsung Galaxy S II Original ROM development thread.
The idea being to Quoting (and please read @sveitus's post in case I'm selectively quoting) the explanitory thread
This forum is for ROMs that aren't an original creation by you in terms of the underlying software, meaning, they've been either 1. developed with assistance from a kitchen or are 2. a re-skinning/re-themeing/minor adjustment of a particular ROM developed by someone else.
Click to expand...
Click to collapse
The Original ROM's are now found within this subforum
Setting aside the lunacy of thinking that anything apart from ASOP and Samsung's stock ROM isn't derived from something else... or the difficulties in determining which belongs in one thread or another (just watch them bouncy from one to another), I find a two things contra XDA ethos.
This subdivision was done without community consultation.
When announced, there was rapid dissent and the response was to close the thread (for heavens sake).
In fairness, to quote @sveitus
P.S. This is a bit of an experiment. Should it make sense, we'll roll it out to other forums on XDA
Click to expand...
Click to collapse
, although my concern is that there is no criteria laid down for "success"
I believe this is a reaction, maybe considered, to two things:
I believe that proportion of the community would like to see forums divided (from what I can tell, divided into Kernels, ROMs and Modems), a proportion are comfortable (complacenty abiding with?) the current structure and a proportion who want to differentiate `original` with `derived`. As is also common in politics, the silent majority will be ignored in favour of the loud minority. I suspect that the democratic view is unknown in this instance.
I believe that this split is a knee jerk reaction to an unfortunate incident where someone released a ROM claiming their own work when (to be confirmed?) all bar part of a theme was taken raw from another source uncredited.
Personally speaking, for a mod to close a thread without explaination isn't easily forgiveable.
What say you?
p.s. (edit) We already have different classes of users based on number of postings, etc.
The forums are not going to be divided. What we did with Galaxy S II was just an experiment...an attempt to keep themes/derivative ROMs (that are based on other ROMs) separate from everything else. Never was this about separating "top tier" developers from everyone else.
As we are going to announce today, we're working on a long-term solution for this, through a ROM database.
Thanks for your feedback.
svetius said:
The forums are not going to be divided. What we did with Galaxy S II was just an experiment...an attempt to keep themes/derivative ROMs (that are based on other ROMs) separate from everything else. Never was this about separating "top tier" developers from everyone else.
As we are going to announce today, we're working on a long-term solution for this, through a ROM database.
Thanks for your feedback.
Click to expand...
Click to collapse
Thank you for the quick response. I guess the division of the Samsung S2 forum was an incredibly short lived experiment and I imagine they are being remerged as I type and that themes can live where always should have in their own `themes and apps` sub forum.
I do understand why it is desirable to identify deriviative ROMs (hint: Look at the HD2 Android Dev forum(s) rules to see a great example of useful identification tags in subjects).
Sending you a pm regarding the closure of the thread (for the purpose of me opening this thread was to offer awareness and give our community a voice.
I'm just a user and I wonder how many other user dont really care where there ROMS have come from and just want a category which just contains ROMS, no sitckies, no dev no "coming" soons, just fully flashable ROMS. Now if you could so this it would make this area much easier to use.
I have to say I just don't get this ROM theft rubbish, Android is supposed to be open source, if you don't want to share your ROM don't post it full stop. If donations are'nt good enough for you then don't post it. If someone uses your work then see it as a compliment and live with it. Adding rules and further layers of complexity to the ROM cooking process is just causing arguments that need not be there. Cooks have to accept that their work is going to used, DEVs also as long as it isn't actually an app.
Now if this attitude puts some people off then the ROMS posted will be fewer in number but populated with those lovingly crafted for the sake of it and not by those who simply want ego boosts to or to generate a profit, this isnt what open source or XDA is supposed to be about...!
discuss..
I think we need to be careful about open. If I was to take the post above, change a couple of words and claim as my own then you would be understandably upset that i plagiarised your work. However, if I reply, building upon your message and credit you then that's a positive thing.
Open source is the same.
With you on the rest of it.
Sent from my GT-I9100 using XDA Premium App
tomj777 said:
I think we need to be careful about open. If I was to take the post above, change a couple of words and claim as my own then you would be understandably upset that i plagiarised your work. However, if I reply, building upon your message and credit you then that's a positive thing.
Open source is the same.
With you on the rest of it.
Sent from my GT-I9100 using XDA Premium App
Click to expand...
Click to collapse
Not at all, I strongly believe open source should be just that and that alone, plagiarism should not even exist on here. There should be no rules for cooking or ingredients at all. If everyone worked this way then there would be no complaints, everyone would just be sharing everything, we may even see better roms even if we do loose a few players.
Best option is no rules, anything goes and rely on people to do the right thing, those that don't will soon come to light and be appropriately chastised I am sure, this should be good enough.
stoolzo said:
...Best option is no rules, anything goes and rely on people to do the right thing, those that don't will soon come to light and be appropriately chastised I am sure, this should be good enough.
Click to expand...
Click to collapse
In a perfect world, that would be ideal. Relying on people to do the right thing would unfortunately lead to chaos. Why? Should we get rid of police officers and courts and just rely on people to "do the right thing"? Nice idea, however the world you mention is fantasy.
stoolzo said:
I'm just a user and I wonder how many other user dont really care where there ROMS have come from
Click to expand...
Click to collapse
I for one, also don't care which came from which. Though I understand the devs' who want to protect their fame/donations, which I think the primary reason for these copying disputes.
tomj777 said:
I think we need to be careful about open. If I was to take the post above, change a couple of words and claim as my own then you would be understandably upset that i plagiarised your work. However, if I reply, building upon your message and credit you then that's a positive thing.
Open source is the same.
Click to expand...
Click to collapse
This is true especially if money is involve.
ROM DEV A created a GOOD ROM = donation of ROM DEV A = 100%
ROM DEV B, IMPROVED/CUSTOMIZED ROM OF DEV A = donation of ROM DEV B = xx% = donation of ROM DEV A = 100%-xx%
NOTE: Above is just an example.
I think "orig" ROM devs feels that the donations coming to "derivative" ROM devs should have been theirs.
stoolzo said:
Not at all, I strongly believe open source should be just that and that alone, plagiarism should not even exist on here. There should be no rules for cooking or ingredients at all. If everyone worked this way then there would be no complaints, everyone would just be sharing everything, we may even see better roms even if we do loose a few players.
Best option is no rules, anything goes and rely on people to do the right thing, those that don't will soon come to light and be appropriately chastised I am sure, this should be good enough.
Click to expand...
Click to collapse
Our society/community is far from the utopic concept that you talk about. I would love nothing more than to not have to enforce any rules in here, trusting that people would just do the right thing, but unfortunately this is far from over. Quite frankly matters got much worse after the introduction of Android. Back when xda was solely focused on Windows Mobile, plagiarism was something that was hardly ever seen around these areas. Everyone had work out in the open, work which they gladly shared with everyone just for the advancement of the platform (and partial resentment against Microsoft ). That work was always credited, any and all help was always acknowledged, and people were all working together towards the same goal. If you want a more utopic XDA, go back 4 years in time and you will find one. Funny enough, it wasn't until Android hit that I learned that this site had moderators. I knew about the administrators but not about moderators... that is how utopic this place was. And if you look at my join date, I have been active here for a very long time.
khein said:
I for one, also don't care which came from which. Though I understand the devs' who want to protect their fame/donations, which I think the primary reason for these copying disputes.
This is true especially if money is involve.
ROM DEV A created a GOOD ROM = donation of ROM DEV A = 100%
ROM DEV B, IMPROVED/CUSTOMIZED ROM OF DEV A = donation of ROM DEV B = xx% = donation of ROM DEV A = 100%-xx%
NOTE: Above is just an example.
I think "orig" ROM devs feels that the donations coming to "derivative" ROM devs should have been theirs.
Click to expand...
Click to collapse
No, you are missing the point completely. In your equation, simply replace the word "donation" with the word "feedback". What is dev B going to do with feedback that was meant to go for dev A? Or better yet, if all that dev B did was throw theme packages together and zipped them into a flashable rom, what can dev B do when feedback comes to him asking him to fix something? Dev A needs these feedback and bug reports to improve his work.
Something I think has been missed from these discussions is...
One of the objectives here is to make it easier for users to finds ROMs that just variants of one they already have; the same underlying code base, but with tweaks to improve the user experience; and ROMs with actual improvements - bug fixes, major improvements, etc.
I'm not trying to make a point here, just illustrate another reason for the changes.
Dave
egzthunder1 said:
Our society/community is far from the utopic concept that you talk about. I would love nothing more than to not have to enforce any rules in here, trusting that people would just do the right thing, but unfortunately this is far from over. Quite frankly matters got much worse after the introduction of Android. Back when xda was solely focused on Windows Mobile, plagiarism was something that was hardly ever seen around these areas. Everyone had work out in the open, work which they gladly shared with everyone just for the advancement of the platform (and partial resentment against Microsoft ). That work was always credited, any and all help was always acknowledged, and people were all working together towards the same goal. If you want a more utopic XDA, go back 4 years in time and you will find one. Funny enough, it wasn't until Android hit that I learned that this site had moderators. I knew about the administrators but not about moderators... that is how utopic this place was. And if you look at my join date, I have been active here for a very long time.
Click to expand...
Click to collapse
The anything goes really can only be the way forward here because what you are are suggesting in any form is a total nightmare for users which completely defeats the object of XDA, remove ease of use and usefulness and you have no XDA and people will start to leave in droves.
If you agree that 4 years ago was far more ideal than it is currently then why aren't you trying to pull things back to where it was then? All you have to do is to post new rules about XDA stepping back on moderation and leaving users to self moderate. Advise that you will still deal with complaints but on a case by case basis by email and not be thread posts, setup and [email protected] or something. Just moderate the legal and unpleasant stuff.
yes it would be nice to have a one fits all system were everyone would receive the exact amount praise or donations for the work done, in proportion to what effort was put in, this WILL NEVER HAPPEN, if you keep loading layer up layer of complexity on top then you will just break it altogether, plus when something is open source nobody has the right to anything, praise, donations, nothing, open source is about good will, not profit, not fame or fortune. I think XDA allows themselves to get to mixed up in this.
Sometimes you just got to sit back and say F*ck it and let things ride.
DaveShaw said:
Something I think has been missed from these discussions is...
One of the objectives here is to make it easier for users to finds ROMs that just variants of one they already have; the same underlying code base, but with tweaks to improve the user experience; and ROMs with actual improvements - bug fixes, major improvements, etc.
I'm not trying to make a point here, just illustrate another reason for the changes.
Dave
Click to expand...
Click to collapse
I see what you were trying to do but it was a huge fail, it was a nice thought but its better just to shove all the ROMS together and let people try them as just because a ROM says it has this, that or the other it doesn't mean it will work as reported and it may have something the flasher wont like. All XDA needs to do is present the information clearly and leave the user to make up their own mind.
I see no need to break down the subs further other than to put ROMS in their own folder, that would definitely make things easier as the current ROM/DEV folder is a total mess.
egzthunder1 said:
No, you are missing the point completely. In your equation, simply replace the word "donation" with the word "feedback". What is dev B going to do with feedback that was meant to go for dev A? Or better yet, if all that dev B did was throw theme packages together and zipped them into a flashable rom, what can dev B do when feedback comes to him asking him to fix something? Dev A needs these feedback and bug reports to improve his work.
Click to expand...
Click to collapse
I have yet to experience what your talking about. ROM B has a problem? Moved to ROM A..
Derived ROM Dev tells "ORIG" ROM Dev an issue? "ORIG" ROM Dev replies that his/her ROM users doesn't report issues, and tells he/she(derived ROM dev) must have done something wrong.
That is normally what happens, because most bugs/issues are found by the "ORIG" rom users.
What if I hosted a copy/modified/derived version of the XDA forums. And my so-called derived XDA forum managed to gain some fame/high activity, even managed to catch up with xda's status/market share. Then one day, a major issue occured, and I couldn't fix it as the problem seems to come from the "ORIG" xda source BUT the "ORIG" xda forum doesn't have this problem. Do you think the XDA admin, would even bother to help me fix my derived XDA forum seeing that his "ORIG" forum could replicate the problem?
stoolzo said:
The anything goes really can only be the way forward here because what you are are suggesting in any form is a total nightmare for users which completely defeats the object of XDA, remove ease of use and usefulness and you have no XDA and people will start to leave in droves.
If you agree that 4 years ago was far more ideal than it is currently then why aren't you trying to pull things back to where it was then? All you have to do is to post new rules about XDA stepping back on moderation and leaving users to self moderate. Advise that you will still deal with complaints but on a case by case basis by email and not be thread posts, setup and [email protected] or something. Just moderate the legal and unpleasant stuff.
yes it would be nice to have a one fits all system were everyone would receive the exact amount praise or donations for the work done, in proportion to what effort was put in, this WILL NEVER HAPPEN, if you keep loading layer up layer of complexity on top then you will just break it altogether, plus when something is open source nobody has the right to anything, praise, donations, nothing, open source is about good will, not profit, not fame or fortune. I think XDA allows themselves to get to mixed up in this.
Sometimes you just got to sit back and say F*ck it and let things ride.
Click to expand...
Click to collapse
Users did not self moderate 4+ years ago.... there was less need for moderation. You didn't see constant intervention by mods, not because the rules were not in place or because the mods were not around, but rather because there was no drama in the titanic proportions that we see it daily. It is very easy to speak from the regular member's stand point, but the amount of stuff that we (mods and admins) see going through this site day in and day out since the smartphone market exploded would make you want to jump out of a window!
You are suggesting, in essence, that we do away with our rules and let people "do the right thing." Why? Our rules have been in place since early 2003 when the site was founded. For over 5 years, these rules have made xda-developers the site that many regard today as the largest developer community on the web.
You speak of the objective of XDA, what do you think this is? Do you know what the true mission of this site is? XDA is a development and hacking community. It isn't end users that make this community, it is developers, hackers, and enthusiast that are the back-bone of this site. Do you want to know what XDA truly is about?
Read this
http://forum.xda-developers.com/showpost.php?p=2031989&postcount=45
I think what a lot of people forget is that this is not a "make my phone neat & kewl" place.
As implied by the name this is technically a Developers forum/community.
Now what does that mean? Well first off it means that there is an expectation that if you are here then you want to customize your device but rather than just installing something that someone packaged you want to understand how it works and maybe even enhance it yourself.
When I first came here with a Blue Angel it was a different environment. PDA Phones were not embraced by the general public because of the expense and complexity (I paid over $400 for my BA). A $400 phone 4 years ago was expensive, today the Tilt is $300 after rebates but with inflation & the rise in the cost of other devices and the fact that there are other sources out there giving them away for $150 our neat bit of kit has become popular with mainstream users.
Now we have a flood of new users who are asking not "How can I do this myself" but more like "Give me the quick fix" without caring to understand the process. See if you read the threads then you get to experience the learning process, you see how the issues were investigated and confirmed. Then you get to watch the different attempts at resolution and learn why some failed while others worked. That is called Development.
The NooB backlash is coming from users who have walked in the development shoes and is directed mainly at those who don't care for the journey but just want the end result or destination.
As a Development Forum we are just as much (if not more) about the journey. I've read so many comments like "I don't have time to read all of the threads" or "I don't care how it works, just that it does". These very statements are contrary to the heart & soul of XDA-Devs and that is why the backlash is so strong.
Let me be very clear on this: IF YOU DON'T CARE ABOUT UNDERSTANDING THE JOURNEY THEN YOU PROBABLY SHOULDN'T BE HERE IN THE FIRST PLACE.
XDA-Devs is about developers & hackers helping each other and working together to get the most out of our devices by understanding them better than most.
XDA-Devs is not about helping everyone who wants a "Kewl bit of kit" make their phone better than the guy next to him.
Now do we go kicking users off who never contribute anything, NO. We tolerate it to an extent. Where the toleration ends is when these users start diluting the usefulness of the forum by repeating the same questions over and over again.
You ask us to understand your position. Well if you want to benefit from our experience and time then I think it is only fair that you understand our position.
Click to expand...
Click to collapse
This is the true ethos of XDA. This is what our community and founding members believed and still do regarding how our site should work and what our members should do to "fit" here.
Hi, firstly I am not talking about XDA as a whole, I fully understand the need for general forum rules and regs, I am simply talking here about cooking for android, I am not trying to tell you how to run your shop. Cooking for Android is different I think as Android is supposed to open source, on one hand people should not be expecting anything in return for the work but on the other it is implied that they will as this is a good will based forum, it should remain that way (again for android only I cannot speak for other platforms)
I am simply of the opinion, regarding cooking and only cooking that trying to police this is impossible,
I certainly understand how frustrating it can be for genuine devs and people who put a lot of effort into customising a ROM but it is just impossible to weed out the good from the bad as you have clearly found, plenty has already been said on this so I dont really need to say any more.
Its is certainly true that XDA has changed, its grown into something completely different, perhaps its time for major rethink and not just sticking plasters
Have you thought about setting up a tier forum system?.
Tier one: would be invite only by MODs, this would be a completely seperate forum, laid out in the same way but on a different URL maybe. This would be mainly for devs and cooks, people on here could create, view and edits posts on here and also on the standard main forum as it is now.
Tier two: would be invite only or based on numbers of posts and / or numbers of thankyou's perhaps. (from different users). You would be able to view tier 1 but not post. YOu would be able to view and post the standard forum.
tier three: no access to view tier one, can edit and post on the main standard forum only much like a user can a the moment.
Tier 4: read only access to main form (until they join)
People on Tier 1 would then be able to disucss and share stuff without the background hum of zillions of noob questions and posts, this would also be a lot more decure as invite only would keep out the riff raff.
Tier two people would then have an incentive to contribute more to dev and so reach tier 1 status. You could also use this system as a punishment, people cold be denied access to higher levels if they infringe on rules.
Sounds a little eliteist doesnt it?, well it is a little but I probably wont ever make tier one but can understand the need for something like this.
khein said:
I have yet to experience what your talking about. ROM B has a problem? Moved to ROM A..
Derived ROM Dev tells "ORIG" ROM Dev an issue? "ORIG" ROM Dev replies that his/her ROM users doesn't report issues, and tells he/she(derived ROM dev) must have done something wrong.
That is normally what happens, because most bugs/issues are found by the "ORIG" rom users.
What if I hosted a copy/modified/derived version of the XDA forums. And my so-called derived XDA forum managed to gain some fame/high activity, even managed to catch up with xda's status/market share. Then one day, a major issue occured, and I couldn't fix it as the problem seems to come from the "ORIG" xda source BUT the "ORIG" xda forum doesn't have this problem. Do you think the XDA admin, would even bother to help me fix my derived XDA forum seeing that his "ORIG" forum could replicate the problem?
Click to expand...
Click to collapse
Tbh I think you miss the point. We aren't saying derivative roms aren't important. Of course they are. I even use them occasionally myself. If I'm having an issue with a rom I'm using, of course I will try and help fix the bug. What we are trying to do is aid developers by splitting the forums up into two clear sections
stoolzo said:
I see what you were trying to do but it was a huge fail, it was a nice thought but its better just to shove all the ROMS together and let people try them as just because a ROM says it has this, that or the other it doesn't mean it will work as reported and it may have something the flasher wont like. All XDA needs to do is present the information clearly and leave the user to make up their own mind.
I see no need to break down the subs further other than to put ROMS in their own folder, that would definitely make things easier as the current ROM/DEV folder is a total mess.
Click to expand...
Click to collapse
That wasn't the only reason you know. Just one of the consequences of the new idea that seems to have been overlooked thus far.
stoolzo said:
Hi, firstly I am not talking about XDA as a whole, I fully understand the need for general forum rules and regs, I am simply talking here about cooking for android, I am not trying to tell you how to run your shop. Cooking for Android is different I think as Android is supposed to open source, on one hand people should not be expecting anything in return for the work but on the other it is implied that they will as this is a good will based forum, it should remain that way (again for android only I cannot speak for other platforms)
I am simply of the opinion, regarding cooking and only cooking that trying to police this is impossible,
I certainly understand how frustrating it can be for genuine devs and people who put a lot of effort into customising a ROM but it is just impossible to weed out the good from the bad as you have clearly found, plenty has already been said on this so I dont really need to say any more.
Its is certainly true that XDA has changed, its grown into something completely different, perhaps its time for major rethink and not just sticking plasters
Have you thought about setting up a tier forum system?.
Tier one: would be invite only by MODs, this would be a completely seperate forum, laid out in the same way but on a different URL maybe. This would be mainly for devs and cooks, people on here could create, view and edits posts on here and also on the standard main forum as it is now.
Tier two: would be invite only or based on numbers of posts and / or numbers of thankyou's perhaps. (from different users). You would be able to view tier 1 but not post. YOu would be able to view and post the standard forum.
tier three: no access to view tier one, can edit and post on the main standard forum only much like a user can a the moment.
Tier 4: read only access to main form (until they join)
People on Tier 1 would then be able to disucss and share stuff without the background hum of zillions of noob questions and posts, this would also be a lot more decure as invite only would keep out the riff raff.
Tier two people would then have an incentive to contribute more to dev and so reach tier 1 status. You could also use this system as a punishment, people cold be denied access to higher levels if they infringe on rules.
Sounds a little eliteist doesnt it?, well it is a little but I probably wont ever make tier one but can understand the need for something like this.
Click to expand...
Click to collapse
Hey,
Tier 1 does sorta exist It's the recognized developer program, which has an area for this.
If I'm honest, what you describe sounds very much like the new system, with a "big stuff" section (the rec dev area), then a tier 2 area, where the "original" stuff goes, and a tier 3 area for the remainder?
well, not really, my way does not seeks to discourage people by singling out their work, however apparently trivial it may appear to be inferior to others - openly...
My idea was really about giving the more technical / coding minded people more of a say in how they work, somewhere more quiet to share and discuss stuff. If you say this already exists then why don't you extend it to encompass the more favoured cooks?, the more stuff worked on and completed at this level will leave less to fight over at my level.
I still think you should put all the ROMS back together in one category and kick out all the other dev stuff into to its own, if only to help us lowly users find out next ROM more easily, don't forget about us
Hey all.
I find myself wondering two things, and thought it best to post it here. Been lurking for some time, love it here.
My first question deals with all the ROMs that are posted here, it's possible questions like this already exists in another thread so please direct me there as my searches didn't turn up anything. For those of us who aren't tech savvy to the point of knowing every abbreviation, technical detail and such, and even for the sake of practicality, is it a good idea to require that developers post a few lines about what their ROM actually does and what sets it apart?
Some ROMs do this, others don't. ParanoidAndroid is the first that comes to mind here at the Note section, where the developers explain in detail what it actually does. Other ROMs, I find, take it for granted that people will understand what this rom does or is about, and so we have to look around or maybe visit their home page or even try it out before discovering if it suits our purposes. Any rules or regulations on this sort of thing already? There are plenty of ROMs here, and instead of flashing every single one it seems appropriate to be offered a short explanation instead-
Secondly, I just bought a Valentinus (by Spigen) case, and want to do a review - where do I post that?
Have a great weekend.
I agree with you !
I think that ROM Chefs should write a brief description on what makes their ROM differ from the rest, There are a lot of similar ROMs out there at the moment, Not that it bothers me as i like how the development is so big.
I usually read the threads and get peoples opinions before flashing, That gives me an insight on what to expect from that particular ROM, But as i just said, A little description wouldnt go a miss
Oh and as for your case review, That should be in the Accessories Section, Theres a thread all about cases in there, you may want to add it into that!
Greets.
I agree. A few lines should be plenty, a brief description so we don't have to go through the 50+ pages and scour thru user problems, queries and other trivial matters. When we have so many roms, it is essential to get an overview. One master thread, sort of like the huge review list they have over at head-fi, detailing contents and function.
Thanks for the tip on the reviews.
Cheers.
+1
A short description will do no harm to any
If the dev is busy, the dev should ask any of the community users sure there are a lot there to help,
Sent from my GT-N7000 using xda premium
We had a similar discussion in one of the threads. If you go to the note wiki page you can find the list of kernels and roms available and their features. Thou this is in its early stage,after updating that list it will be a lot helpful
Sent from my GT-N7000 using xda app-developers app
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