Related
Dear all,
Due to the proliferation of new ROM's, the Wizard forum is in need of a bit of housekeeping. The mods cannot do this alone, so we are asking for your help.
1) The four most used kitchens have been stickied for the moment and questions regarding any ROM's you cook based on these kitchens should be posted in the appropriate thread. Please do not start a separate thread. Anichillus Core Professional kitchen is also found in the Development and Hacking forum since it is used for multiple devices and is beyond the scope of many basic users. Users beware. I may de-sticky the kitchens upon further discussions with the mods, but right now the structure will stand as it is.
2) On the same note, I'm asking for kitchen authors to notify me or other mods concerning useless posts in these threads (e.g. Why didn't you include "x" application? or posts that are inflammatory or non-technical in nature). They will promptly be deleted as we shouldn't have to wade through 20 posts of BS to get to relevant tech info.
3) All of the kitchens stickied are based wholly or in part on Bepe's tools and are of the same basic architecture. Therefore no more kitchens will be stickied unless they are truly unique or offer a substantially more comprehensive interface.
4) Also, it's sometimes better for a lot of people to refine one ROM than for a few people to refine a lot of ROM's. I know there are a thousand aspiring cooks out there right now since the kitchens have been released. You may be tempted to release your own ROM to the masses either because you think it's a great ROM or because you want to be known around the board. Resist the temptation. Unless your ROM offers a very innovative user experience (e.g. Touch), it is not likely to get a huge following and might just cause more confusion for the non-developers on this board, you might do better to try to collaborate with some fellow developers in creating a very good ROM.
5) MOST IMPORTANTLY (and you know who I'm talking to). Some people have repeatedly posted in this forum despite the fact that their posts had nothing to do with Windows Mobile 6 specific issues on the Wizard (i.e "My Herald..." or ("Do you have this software from a Nokia?"). We will issue 3 warnings through PM's but after that you might be up for a temporary ban. This will only happen if you're a repeat offender. Heck we've all posted in the wrong place at one point or another. If possible we may move the post to a more appropriate location but it would save everyone a lot of work and aggravation if the posts are made in the correct forum.
I hope this helps a bit. If you have suggestions for how we can make this place better, please air them here. If you have a complaint with a mod, please PM me first. I don't like public conflict and most of you don't either.
jwzg said:
Dear all,
5) MOST IMPORTANTLY (and you know who I'm talking to)..
Click to expand...
Click to collapse
not nice.,...
btw.
upgrade forum to allow people REMOVE own posts/topics, first.
Users can manage, with proper USUAL forum options, too.
smells like we vs. THEM,again,.
"same architecture" - yup, yup, but why i can see potential with new user cook result, and i can't with older builds?
it is random novadays(lack of your knowledge + newbie enthusiasm can make miracles).
I agree that a strong hand is needed. For this i suggest that there should be a special part in the forum where to move threads that have no replies for hmm...30 days ...?
I don't know too much stuff about forums but i think that would mean a nasty job for you guys so...just a suggestion. Or better...delete them or move them to an sort of recycle bin.
Regarding switching to a new upgraded forum, i think that would be an immense hard work also and it will leave the community off line for few days. It may be needed to come to that soon but that's not a big problem.
But i agree that allowing people to delete their own posts would be nice. But on the other hand, considering hours i spent here reading, i kinda got used to this look
I will PM you with posts to delete but beware that i may be more strict than you and i don't want to waste your time...so i will filter myself.
And one more thing to add to this. The original "Wizard" forum has some sort of bug because whenever you open it, there arent more than two pages in it, so older posts are mysteriously made invisible though the front page at forums.xda-developers.com shows that number of threads in it are in thousands..maybe users dont post the general questions there because they think (or know) that if they dont get a reply within a day, their post is going to go into oblivion and not be answered...
nothin said:
not nice.,...
btw.
upgrade forum to allow people REMOVE own posts/topics, first.
Users can manage, with proper USUAL forum options, too.
smells like we vs. THEM,again,.
"same architecture" - yup, yup, but why i can see potential with new user cook result, and i can't with older builds?
it is random novadays(lack of your knowledge + newbie enthusiasm can make miracles).
Click to expand...
Click to collapse
You are reading this wrong. I had about four or five posters who after two or three moved threads and a couple of PM's continued to post totally irrelevant posts in the Wizard Mobile 6 thread. I this was aimed at repeat offenders and not at the occasional screwup. By they way, you can modify your post or ask a mod to move it if you like. Not a big deal.
I'm not trying to be a jerk at all, but I'm not trying to be nice either. I just see the same old builds with different package combo's that anyone could make with the kitchen and a little ingenuity. However, folks like Zoki and the-equinoxe have done some fine things with the touch software that are truly innovative and add substance to the user experience. I for one have partially adapted the T-Mobile wing OEM package to the Wizard (yes camera too, but the image is transposed and my-faves doesn't work). That's true ROM cooking and not just throwing a few packages into a cooker and presto.
It is not "us" against them. It's those who have a bit more experience actually doing our best to take this forum up another level instead of settling for ssdd.
shantzg001 said:
And one more thing to add to this. The original "Wizard" forum has some sort of bug because whenever you open it, there arent more than two pages in it, so older posts are mysteriously made invisible though the front page at forums.xda-developers.com shows that number of threads in it are in thousands..maybe users dont post the general questions there because they think (or know) that if they dont get a reply within a day, their post is going to go into oblivion and not be answered...
Click to expand...
Click to collapse
I'm working on this...
all the old versions of Roms should be deleted too...like the very first wm6 roms theres no need for them
shantzg001 said:
And one more thing to add to this. The original "Wizard" forum has some sort of bug because whenever you open it, there arent more than two pages in it, so older posts are mysteriously made invisible though the front page at forums.xda-developers.com shows that number of threads in it are in thousands..maybe users dont post the general questions there because they think (or know) that if they dont get a reply within a day, their post is going to go into oblivion and not be answered...
Click to expand...
Click to collapse
Fixed by admin. Thanks for the heads up.
ANTC said:
all the old versions of Roms should be deleted too...like the very first wm6 roms theres no need for them
Click to expand...
Click to collapse
I disagree. There is history and things that can be found in those threads... Unless XDA-Developers is hurting for space, what is actually removed needs to be really determined that it isn't something that may help. I just did a Google search (I've given up trying to use the search here, easier to use Google's advanced searching techniques in most cases) and found an answer in the original Crossbow thread from January. Just deleting stuff because its "Old" is a bad idea IMO... Getting rid of the hundreds of "Help, I bricked my phone!" threads is even questionable as I wonder how many people have fixed a phone due to those and never posted anything here...
Remember there area a LOT of people that read and never post here. Yeah, it gets old answering the same questions over and over again (so I've taken the route where I've quit answering some of those.
mfrazzz said:
I disagree. There is history and things that can be found in those threads... Unless XDA-Developers is hurting for space, what is actually removed needs to be really determined that it isn't something that may help. I just did a Google search (I've given up trying to use the search here, easier to use Google's advanced searching techniques in most cases) and found an answer in the original Crossbow thread from January. Just deleting stuff because its "Old" is a bad idea IMO... Getting rid of the hundreds of "Help, I bricked my phone!" threads is even questionable as I wonder how many people have fixed a phone due to those and never posted anything here...
Remember there area a LOT of people that read and never post here. Yeah, it gets old answering the same questions over and over again (so I've taken the route where I've quit answering some of those.
Click to expand...
Click to collapse
true i guess I worded my statement wrong I ment delete old Rom threads like the different versions of roms...i have no need for my version 1-3.5 beta threads you see what i mean...and I think we should have a bricked phone help thread I even wrote a quick tut on my other site to save a bricked MDA..you understand were im getting at
Gulp - I hope I didn't start something we will all regret with my post "Why all these new WM6 ROMs?" http://forum.xda-developers.com/showthread.php?t=313781
Let us not forget that apart from a very few idiots this is a great place to be. I have learnt a lot from this forum considering that I do not have a background in computing.
It has even stimulated my interest to the extent that I have assembled my own computer. Didn't save me money and my wife cannot understand it but I have ended up with exactly what I wanted which a store built machine could not have given me.
I hope you understand the analogy.
Let's just make sure that "We don't throw out the baby with the bath water".
No, you didn't start anything scotch whiskey that hadn't already been brewing a bit. I think my modified OP is a little nicer, but still gets the point across.
ANTC said:
true i guess I worded my statement wrong I ment delete old Rom threads like the different versions of roms...i have no need for my version 1-3.5 beta threads you see what i mean...and I think we should have a bricked phone help thread I even wrote a quick tut on my other site to save a bricked MDA..you understand were im getting at
Click to expand...
Click to collapse
I agree with both you and mfrazzz.
What if someone doesn't want to use the latest version of a ROM, they don't like some changes or whatever, they will need those older threads for reference material. Also I notice lots of people asking questions, only to be referred to older threads. There isn't any use reinventing the wheel so to speak.
I think a good idea would be for developers (or just real supportive people) to make kind of an FAQ for some of these older versions, a "best of" list of questions and answers. It can be posted in the forum, it can be on some website somewhere, or in the XDA FTP, whatever. Not only would it give people a good place to refer to, but it might also eventually lead to a cut-down of basically the same questions.
Only then would I think removing older threads be a good idea. I know that wasn't entirely the point of this thread, but hey, mr smart guy back there decided to take a shot so I am too. I for one am right in there with him, I think its THE MAN against US. Oh yes, yes it is. oh noes. <3
jonflow said:
Only then would I think removing older threads be a good idea. I know that wasn't entirely the point of this thread, but hey, mr smart guy back there decided to take a shot so I am too. I for one am right in there with him, I think its THE MAN against US. Oh yes, yes it is. oh noes. <3
Click to expand...
Click to collapse
Guys, it's NOT the man against anyone. We'd just like to get some real development going on here instead of everyone releasing slightly different versions of the same ROM.
I don't like this talk
Everybody should have the right to publish his work, no matter what hi did.
The rest will judge his work and he will learn something. Only those who didn't do anything can't understand this.
Old topics should remain, I like to jump back to learn something, for new members old topics is a must.
If you must do something to show us you're administrator rights, do something good, like option to close the thread.
Zoki, no one said members can't publish their work. I just honestly believe more of it should be along the lines of what you did with the touch stuff. I truly admire your work because it was bleeding edge (still may be) and that's developing which is why this board exists. I'm not trying to flatter you here to gain your support either. It's just when people throw your name all over a splash screen it doesn't really make it their work since most all of the ROM's here are cooked using kitchens from other authors with packages from other members and yes, even HTC. If that sounds big-brother-ish, it's not intended that way. Just make sure credit is given to the quite literally hundreds of people who've made this possible. We're already having problems in other forums right now with people asking for donations in return for tech support for ROM's they've cooked with other's tools. That is one of the many issues we're trying to be proactive about here.
Regarding closing threads, I'm not an administrator, and they have chosen not to give OP's the rights to close their threads. If you want your thread closed, please PM me and I have the rights close it quickly. If you want someone else's thread closed, well, you can request it, but it may or may not happen.
BTW, the old threads were not deleted, and I strongly believe they shouldn't be. Admin simply made a mistake in a setting, and all of the old threads are visible as per our request.
As a mod, I'm just trying to do my best to make sure that we have an orderly forum and we are developing, which is the forum's purpose.
hey jwzg we aren't really calling you a bad person, we know you're looking out for us I agree though, the roms are starting to look the same except for one or two programs, and the splash screens. It would be better for people to just explain what was in a new ROM scheme they came up with, and it would encourage more people to start learning how to make their own ROMs, therefore making them more intellectual in this particular field, which is a good thing. knowledge is power. But hey its just my opinion!
jwzg said:
Guys, it's NOT the man against anyone. We'd just like to get some real development going on here instead of everyone releasing slightly different versions of the same ROM.
Click to expand...
Click to collapse
just to let you know that the REAL develepor regrets now releasing the rom kitchen tools....
jonflow said:
the roms are starting to look the same except for one or two programs, and the splash screens.
Click to expand...
Click to collapse
sorry i am noone for you all, my "senior" member status sounds like joke but...
everything is the same imo now, also, theres no real help lately; only people that can have answers are like "how to flash my phoooone", "did i brickeeeeed?" etc.
there's no real customisation of "custom" builds.
seems like checking some oempacks' ticks is making these current OSes special...
i can't get an answer for my problems, despite i tend to help people someOM:
http://forum.xda-developers.com/showthread.php?t=322228
i spent MONTH to make this, and what?
nobody wants to help.
ok, clean this forum up, you may remove my babbling now....
everything i know bout wizard customisation is from that site...but now, in "touch" soft times, there's nothing that makes wizard better, just nothing.
it became playground for kids or what...
sorry for funny english, i cant do better...
i want to say thank you to:
Faria,
Anichillus,
mattk_r
jwzg
double_ofour
zoki
and many many more people that made me ..learning, not copying.
allright, time to watch another touch skin post...
Myself i've been reading most of the time, only lately did i start posting to test some bugs in builds. The issue at hand is a double edged sword. Yes i solved many problems wading through old posts. But i also solved a lot of issues just reading an entire thread. I will never be able to create a kitchen but it sure is nice knowing that when i want to i can build a rom entirely to my liking. But indeed to many Build threads these day are the same. And most of the issues handled, but then spread across multiple build threads, are mostly about the same problems. Mainly issues with specific base roms and aplication incompatibilities. I think a lot of the solving of these issues is slowed down because of the spread through topics. Maybe setting up a rule that Roms that get posted and aren't updated or have any fixes posted should not be taken seriously and can be deleted. This way less Rom versions circulate the thread and only higher quality builds by Chefs are available. Also a good rule might be to have the cooks post more info about the sources and tools used for their builds, like Kitchen used, Base used, Patches used oem packages used. So new users more easily understand that no Rom has no history. It also takes away the polish of parading with your ego. Maybe even changing the main wizard topics into
1. Kitchen Development
2. How To & Troubleshooting
3. Rom Builds testing
4. Custom Made Software & tweaks
5. Hardware and Accesoires
6. To be Deleted (either move topics or delete them when re/placed into new main topics)
Then indeed phase out unneeded old posts if the information is passed into new threads that accordingly aknowledge the sources.
What i'm trying to say is, to change the perception a bit more that this is not a Technical support site and more of a doing site.
I think the main topics can set an expectation and the current ones don't give the impression that flashing is not kids biznz.
Also it looks like there are to many uploads of the same home screens, software etc. (i think even i am quilty of that).
I'm all for a big clean up but with the focus on retaining the history and origin as much as possible even if it means loosing a few classic threads.
You as admin can set the tone and expectation and a clear message should be sent to junior cooks that collaboration is what drives this site.
While I haven't been on XDA as long as some other members, I have gone through the mammoth threads that are Dude's and Cyanogen's and its just flooded with spam or often un-useful information most of the time.
This is a development thread after all and for those running either experimental or unstable builds are beta-testing for everyone else. Now there's no harm in having a bit of chit-chat here and there to lighten things up but some issues seem to get lost amongst the ten's of posts just saying "Flashing now/issues after flashing a theme/etc".
They are experimental/unstable for a reason!
I was wondering though, if it would be beneficial to devs to have some sort of standardised form for bugs and issues. Yes I know we could probably use a wiki or support tickets offered on other sites, but generally many things get posted here on XDA first.
I was thinking of a simple list that users could copy and paste to make things easier to see at a glance and to improve on search hits. Something like this:
ROM Build:
Theme:
ROM Issue:
Issue Keywords:
Reproducible:
Wiped before install:
Re-installed/reflashed:
Logcat:
Searched for answer:
An example of a report as below...
ROM Build: Cyanogen 3.9.6
Theme: Stock
ROM Issue: Cannot run MyTracks (be specific as possible)
Issue Keywords: MyTracks ForceClose
Reproducible: Yes (put in steps)
Wiped before install: No
Re-installed/reflashed: Yes, re-installed MyTracks
Logcat: Attached/No
Searched for answer: Yes
It can be added to though so I'll leave it to you guys to offer up suggestions.
The "Issue Keywords" part should flag up easier during searches, so if you run a search for "Issue Keywords Mytracks Forceclose", technically speaking it should link to this thread.
What do you guys think? Its a longshot I know for most members to copy and paste before they reply but if it becomes a habit, maybe it will become easier for devs to track issues for themselves to prioritise or offer solutions.
FLASHING NOW
Kidding, I think a standardized form would be useful and I think any issue somone reports must have a logcat or it should be thrown out with the exception of phones that won't boot at all and a logcat can't be created. I think posts like "this don't work' are largely useless to developers.
lol I was reading through the Hero dev threads before and all I saw was one liners with FLASHING NOW/CAN'T WAIT/ROSIEEEE etc. While enthusiam is a fantastic thing, sadly more information is often needed to fix any issues that might pop up.
I don't expect, and neither should anyone else, a dev to read though 200+ pages of posts to only find that there are only a handful of issues that are actually ROM related and not solvable by other members with a little effort.
A general thread for a rom that's a little more open and a straight bug report thread would probably help all invovled maybe u can pm a few developers about this idea to see if there is any support for it.
Aso a moderator that can provide tight strict support of the bug thread to keep it on the striaght and narrow
I have suggested to the mods before about having a totally seperate section just for ROMs and that but it looks like it was debunked, along with having any new moderators for this place.
Which is a shame because a lot of threads and points do get lost amongst the often pointless posts that are made, which makes searching and reading them a chore.
I'm not sure what the moderator support is like for the Dream section, I've only seen Mikey being active in trying to establish any ground rules. Have offered my services though if required but will try to help out whenever I can.
I'll ask around though to see if devs would be interested in trying to standardise reports here on XDA and hopefully other members might follow suit before posting.
I really like this idea. It would be nice to have everyone on the same page. I would also like to see a feature where you HAVE to put your info in a sig. The hardest thing about helping people is lack of info. With this in place, everyone will be a lot happier to help then if you just said, "I have a problem" and expecting everyone to read your mind.
Good idea NeoBlade!
I second this idea.
Thanks! After all it just makes it easier for the people here, be it devs or helpful members, to diagnose and to figure out solutions when troubleshooting. Its the same process that I use when helping people with technical issues on computers - The more relevant info available, the easier it becomes to track.
Cuts out a lot of guesswork I find.
Enforcing it into your signature would be nice but from the looks of it, most people have put in the effort to display the latest info at least, not all though which can't be helped since its understandable.
At the end of the day, most of us are willing to help out others, as long as they put in a little effort too.
What about a bug tracker? Maybe not even something as formal as a bug tracker but something along those lines. We could set it up to force certain information before submitting a bug such as their current rom, a2sd setup, phone model, motherboard, etc. I am a web developer so if I get some extra time I could write something up pretty quick. Just a thought.
chuckhriczko said:
What about a bug tracker? Maybe not even something as formal as a bug tracker but something along those lines. We could set it up to force certain information before submitting a bug such as their current rom, a2sd setup, phone model, motherboard, etc. I am a web developer so if I get some extra time I could write something up pretty quick. Just a thought.
Click to expand...
Click to collapse
most of the devs are using googlecode which has a bugtracker with it
There's a link to this in Cyanogen's Experimental thread
I think this is a great idea, so don't get me wrong, I just think it's more complicated than bug hunting.
A lot of what gets discussed sometimes isn't directly related to the ROM, but things like best swap methods and battery ussage do end up incorporated into the ROMs. Most people who post on these things do know what they're talking about and do make a contribution to the ROM, and other ROMs, too, and it necessarily stems from the discussion about the ROM, in my experience, most of the time.
In general, if I post, I try to address some sort of work around or solution to a problem that not everyone is having with the ROM. The fora aren't just for the ROM Devs, the rest of us read them, too, and get a lot out of them, despite the occaisional inanity.
If you go through the HTC Wizard ROM Forum, you'll see the same thing, and a ton more heated arguments. What happens as the ROMs progress, is that fewer bugs come up, and the fora get cleaned up right along with them.
What I might suggest is that people title their posts (perhaps be required to do so) with [Bug Report], [Request], [Solution], [Work around], [Comment], [Question], [Discussion], maybe [Misc.] to help sort through the parts of a forum. All of these parts are important enough, and mostly do contribute somehow to the results, which is a great ROM, but the process is people being in the discussion, and that's what's really going on. Wiktionary: forum I imagine if people did this, at least they would have to identify what it is that they're posting, which is where I see the problem. If people were required to think before they post by taking some sort of labelling action, they might second-guess themselves and save the keyboard for something more useful to others. At the least it would let anyone, devs included, filter.
It also might be handy if I could delete my own threads & posts that were errantly posted. We all have them somewhere. And people who post thier feelings rather than their cohesive, relevant thoughts will only be eradicated by educating the masses, so, pay your property taxes and find out what's going on with your local schools (we may be stuck for now, but there's always hope.).
Yeah there is an active bug tracker at googlecode already, but I can't really see many people actively taking the time to actually post there and fill in the relevant information.
I have no issue though with discussions in a thread as it adds character and can provide a friendly environment for people to help each other. More often than not, when people see others helping out, they would chime in too with a contribution.
I think Cyanogen though has killed off any compcache/linux swap discussions earlier on as he mentioned in his post that he didn't want to hear anymore of it And it has actually remained as so - There are plenty of such threads that exist already.
I agree though Janis with a structured standard title in their posts. It only takes a couple of seconds but can help people skim through what is banter and what issues might need looking at. I'll do so from here on it too (if only fast reply supports post titles!).
Would be nice if there was a notes/announcements section put up on certain sub-forums too outlining some form of post structure like what was mentioned. I'm more familiar with IPB/phpBB personally but I'm sure vBulletin supports it too.
As a new Android user who is very familiar with the command line and with Linux/Unix environments, I still feel extremely overwhelmed with the amount of 'fixes' and 'root' hacks going around.
I've played with linux for 100's of hours and have broken the install and fixed it...
But this is a phone that bricks, not a computer. I don't like playing "oh I'll just try this and see what happens" with my $400 phone.
Plus I honestly can't determine which one is best for me.
I started this thread so that someone could assist me in creating a guide for what you want to do and what is best to do it.
For example, I want to upgrade to Froyo when it releases.
In the mean time I want to install a lag-fix/ custom rom.
mymansionisabox said:
As a new Android user who is very familiar with the command line and with Linux/Unix environments, I still feel extremely overwhelmed with the amount of 'fixes' and 'root' hacks going around.
I've played with linux for 100's of hours and have broken the install and fixed it...
But this is a phone that bricks, not a computer. I don't like playing "oh I'll just try this and see what happens" with my $400 phone.
Plus I honestly can't determine which one is best for me.
I started this thread so that someone could assist me in creating a guide for what you want to do and what is best to do it.
For example, I want to upgrade to Froyo when it releases.
In the mean time I want to install a lag-fix/ custom rom.
Click to expand...
Click to collapse
Do people not know how to read stickies? there are guides and how-to's in this section alone. There are more in the development section. If you don't know how to search a forum, I'm not entirely sure you should be messing with your phone's firmware.
Kaik541 said:
Do people not know how to read stickies? there are guides and how-to's in this section alone. There are more in the development section. If you don't know how to search a forum, I'm not entirely sure you should be messing with your phone's firmware.
Click to expand...
Click to collapse
I actually have read all of the stickies.
Im not asking 'how-to' do anything.
What I am saying is that this forum has an absolute overload of 'information' and 'solutions'
There should be a more concise sticky discussing the advantages/disadvantages of each rom/lag fix/flash/recovery/etc. (Or at least about the ones anyone cares about)
If this exists, I sure as hell don't see it.
mymansionisabox said:
I actually have read all of the stickies.
Im not asking 'how-to' do anything.
What I am saying is that this forum has an absolute overload of 'information' and 'solutions'
There should be a more concise sticky discussing the advantages/disadvantages of each rom/lag fix/flash/recovery/etc. (Or at least about the ones anyone cares about)
If this exists, I sure as hell don't see it.
Click to expand...
Click to collapse
I think you're in a wrong forum if you want someone to give you any kind of "distilled", spoon-fed info just because you're afraid to mess with your "$400" phone.
Again, to second the other reply, all the info is posted. Just RTFW/S.
mymansionisabox said:
I actually have read all of the stickies.
Im not asking 'how-to' do anything.
What I am saying is that this forum has an absolute overload of 'information' and 'solutions'
There should be a more concise sticky discussing the advantages/disadvantages of each rom/lag fix/flash/recovery/etc. (Or at least about the ones anyone cares about)
If this exists, I sure as hell don't see it.
Click to expand...
Click to collapse
there are tons of guides and they're all condensed. I have to agree with the other poster, if you aren't going to take the time to read and learn what you're doing, don't do it. each sticky offering to help you through all of these processes are there for a reason.
There's the "Pimp My Captivate" thread which is exactly what you say you want. And there have been comparisons of each lagfix by Zilch25, clockwork recovery by Koush is clearly explained in his thread, each ROM is discussed in their own thread.
Ironically, you're asking for a sticky so as to have less stickies. Finding out which ROM you want to use is up to you and if you're not going to take the time to figure out what each tool offers or what each base ROM means, then maybe flashing your phone is something you should steer clear of for now.
If you're afraid of bricking it, just do a Nandroid backup. If something goes wrong, then you can just flash back and it'll be A-OK. If you seriously brick your phone and it's 100% messed up, it's probably because you tried to mess it up.
Hydrocharged said:
If you're afraid of bricking it, just do a Nandroid backup. If something goes wrong, then you can just flash back and it'll be A-OK. If you seriously brick your phone and it's 100% messed up, it's probably because you tried to mess it up.
Click to expand...
Click to collapse
Even guys that intentionally tried to brick their phone can't do it. I don't have much to say as it already has. Just take the time to read. There is a condensed version of what you can do to your phone, the pimp my captivate. Otherwise there are many different ways of rooting, lax fixes, firmwares to flash etc...so there is not one thing that you can do that will make your decision easier.
flashman2002 said:
Even guys that intentionally tried to brick their phone can't do it. I don't have much to say as it already has. Just take the time to read. There is a condensed version of what you can do to your phone, the pimp my captivate. Otherwise there are many different ways of rooting, lax fixes, firmwares to flash etc...so there is not one thing that you can do that will make your decision easier.
Click to expand...
Click to collapse
don't say that. there have been several confirmed bricks from i9000's using the i897 one-click downloader. While there is no immediate, known, for-certain brick method for your phones... you never know who or what may be the first... always read as much as you can in the threads before you attempt to do anything
As someone who was new to the Captivate scene, but not XDA, just two weeks ago the best advice I can give you is start with the "Pimp my Captivate" PDF file. Read through that and then move forward to other stuff like flashing new firmware and using odin. Trust me you will catch on. I am no move on to working on friends phones for them without any worry of breaking (bricking) them.
Just read, read, read, and sometime read some more. If you have a question about a certain hack, fix, firmware...ect then just ask that question in that thread. Trust me there will be very useful helpful people to answer your questions.
I did what is probably the easiest method. I used unleash the beast and then one click lag fix. That's it and my phone is amazing now. I plan on sitting tight until froyo comes out and whatever the top rom happens to be.
I do appreciate everyone's answers.
Despite that, I really don't understand this particular forum's aversion of being more organized and concise. (imo)
I don't think any of you who told me to read actually understood my intentions of making this post since,although I didn't state it, I have already flashed mods to my Captivate and I have modded my previous phones.
I'm new to XDA so maybe this site is far more trustworthy than where I've been.
I'll check it out and read at least the last 10 pages of each thing that I install.
Thanks though.
Mod please close this thread.
mymansionisabox said:
I do appreciate everyone's answers.
Despite that, I really don't understand this particular forum's aversion of being more organized and concise. (imo)
I don't think any of you who told me to read actually understood my intentions of making this post since,although I didn't state it, I have already flashed mods to my Captivate and I have modded my previous phones.
I'm new to XDA so maybe this site is far more trustworthy than where I've been.
I'll check it out and read at least the last 10 pages of each thing that I install.
Thanks though.
Mod please close this thread.
Click to expand...
Click to collapse
we have nothing against being "organized," I just believe your definition of organization is far too complex. You want all the ROMs compared side by side, followed by the tools, and the rooting methods, and the lagfixes and to know which is "best."
Each thing is kept separate from the other because there would be an absolute and definite overload of information in each thread. Look at SRE (a fine example of how to do it properly), he details the result for the end-user and then provides links to where each part of what he did came from. The development section provides a thread on reverting to stock and just that because it should focus on that, rooting can be left for a thread on rooting. SRE shouldn't be tossed into a thread with UTB because they provide different effects.
If you were to compile everything into one big mega-thread, questions would never be answered because there would be far too much crossover. The Pimp My Captivate thread is as good as it gets in that regard, they provide optimizations and suggestions and where to find more information, which is good enough.
I understand.
After this post I am done though, because I'm getting no where with this.
Check out the web page below, this is really what I meant. I can't post links so just close the gap between http:// and ga..
http:// gadgets.boingboing.net/2008/12/17/osx-netbook-compatib.html
I belong to several forums that had been attempting to put mac osx on netbooks and on one of them a chart of compatibility was compiled, which is similar to what I was suggesting we needed.
Ignore the comments below the chart; that would be unnecessary.
All I was proposing to do was have a locked/stickied thread that only a moderator could change up as new changes/improvements occurred.
Each root/lagfix/rom would have a href connected to their actual thread.
So there would be no need to have comments/ questions asked on that particular page. ****.. it could just be a damn wiki page, but I digress..
If no one thinks that would be beneficial to the community, that is fine.
I don't care, I can easily figure it out myself.
Mod, please close thread.
1800 devices were sold this week, and I would expect that a good portion of those users will be headed here.
Again, this is just an early report from one user who just got their device, so it could be a one-off. But I would go on the assumption that they are all getting 4349, to play it safe.
To the moderators:
I would highly recommend that the development area be altered ASAP to break up the 1.1 and 1.2 ROMs. I would also recommend that a disclaimer be added to all 1.1 ROMs, including anything CM7 based, that specific steps need to be taken if a 4349 user attempts to use these ROMs. I have been asking for this since April, and I am respectively asking again.
Again, this could just be a one-off user with 4349. But given that one Woot! user has it, and new TigerDirect users have 4349 as well gives me the impression that this could be the norm for all new devices. And I think it's in XDA's best interests to prepare the development site accordingly, given what we know about 1.1 down-leveling.
To the 1.1 devs / modders:
Same request. From someone who had the opposite occur with TNT Lite 5, this is a potentially devastating situation if these users flash your 1.1 based ROM.
To new Woot! users:
You should read this first, please: http://forum.xda-developers.com/showthread.php?t=1035983 Don't jump into modding until you have confirmed what stock version you have, please.
I agree, If we can prevent a user from flashing the wrong ROM due to their bootloader, we will save many users from needless grief and reduce the number of posts for help to those who really need it.
Roebeet, sure glad to see you back posting and helping...
brookfield said:
I agree, If we can prevent a user from flashing the wrong ROM due to their bootloader, we will save many users from needless grief and reduce the number of posts for help to those who really need it.
Roebeet, sure glad to see you back posting and helping...
Click to expand...
Click to collapse
I think I picked the right week to do so.
This will be the role of the posters of the ROMs/MODs to delineate which bootloader is used, as well as to provide the appropriate disclaimers, etc.
At the end of the day, XDA is a developer site - and all action taken is at your own risk and decision. If users are not willing to fully research their choices the responsibility falls on them for whatever happens. There will be people who help out of the goodness of their heart - but not their responsibility if something fails like the user was warned it would.
Agreed. The SD development sections are much easier to navigate after being segregated into 1.1 and 1.2
jerdog said:
At the end of the day, XDA is a developer site - and all action taken is at your own risk and decision. If users are not willing to fully research their choices the responsibility falls on them for whatever happens. There will be people who help out of the goodness of their heart - but not their responsibility if something fails like the user was warned it would.
Click to expand...
Click to collapse
Isn't this a pretty basic usability issue? This would help new users, but more fundamentally it's just good organization, no?
jerdog said:
This will be the role of the posters of the ROMs/MODs to delineate which bootloader is used, as well as to provide the appropriate disclaimers, etc.
Click to expand...
Click to collapse
I kinda disagree with this statement. In other sub-forums on XDA, they require all posts in the dev section to follow guidelines on the title at the very least. Simply requiring that all posts in that section be classified the same way is all that is needed (with all the disclaimers and everything).
Example:
[Rom][1.2BL] Uber Fake Rom!!1?! (Now with extra frosted flakes) - [1.0 - 6/10/11)
Tostino said:
I kinda disagree with this statement. In other sub-forums on XDA, they require all posts in the dev section to follow guidelines on the title at the very least. Simply requiring that all posts in that section be classified the same way is all that is needed (with all the disclaimers and everything).
Example:
[Rom][1.2BL] Uber Fake Rom!!1?! (Now with extra frosted flakes) - [1.0 - 6/10/11)
Click to expand...
Click to collapse
And that's a good statement - if you notice those posting actual development ROMs/MODs already follow this as a rule of thumb. But it is not an XDA requirement. It has been suggested to Devs that they follow this anyways.
Clean up on "Isle 9" please. I think being structured by bootloader is a great idea. Especially since there are projects now other then Android being worked on. And in the future when Windows 8 is released.
jerdog said:
This will be the role of the posters of the ROMs/MODs to delineate which bootloader is used, as well as to provide the appropriate disclaimers, etc.
At the end of the day, XDA is a developer site - and all action taken is at your own risk and decision. If users are not willing to fully research their choices the responsibility falls on them for whatever happens. There will be people who help out of the goodness of their heart - but not their responsibility if something fails like the user was warned it would.
Click to expand...
Click to collapse
Why not simply break out the ROM section, rather than put more of the onus on the developers? The developers already have enough to do with developing and will in all likelihood already advise which bootloader to use. Make it a little easier for them.
We all know that what we do is at our own risk; all that is being asked is to break the ROM section into a 1.1 and 1.2 subforum.
jerdog said:
This will be the role of the posters of the ROMs/MODs to delineate which bootloader is used, as well as to provide the appropriate disclaimers, etc.
At the end of the day, XDA is a developer site - and all action taken is at your own risk and decision. If users are not willing to fully research their choices the responsibility falls on them for whatever happens. There will be people who help out of the goodness of their heart - but not their responsibility if something fails like the user was warned it would.
Click to expand...
Click to collapse
I disagree. The breaking into a 1.1 and a 1.2 sub-forum of the development section seems pretty much critical to avoid any unnecessary headache for XDA gTab users. Saying what you said above is like throwing a 10 year old behind the wheel of a car and saying: "You accept the risks of your own actions, so go ahead and start driving and we'll see where this leads us."
You wouldn't do that under any circumstance, so you provide "buffers" (training, mentorship, test driving, books, etc) which in our case would be the sub-forums separating boot loader types to attempt to put forth a friendly effort to help users avoid a headache.
The sub-forums would look something like this:
Android Development:
General Development (CWM, radios, tools, app dev, etc)
1.1 Bootloader Development (all 1.1 based kernels, ROMs, and misc.)
1.2 Bootloader Development (all 1.1 based kernels, ROMs, and misc.)
Not putting forth the effort to at least provide a somewhat protected atmosphere for the XDA gTab users is negligence. I have been a member of the XDA community in an observer/user fashion for much longer than my membership reflects. From my experience with XDA, I have noticed a trend on the gTab community in more recent times that is not reflected on the other device forums I have utilized (HD2, Tilt, Tilt2, G2, G1, MyTouch, and a few more that I cannot remember). The vast majority of those kept higher and more enforced standards than the gTab forums have lately, but still looked out for the users by putting certain "buffers" and preventative measures into place to try to keep users from messing up their pricey hardware due to negligence.
Yes, negligence on the user's part is their fault by not following some instructions laid out for them, but it doesn't mean that the leadership can't at a minimum provide some buffers out of a good faith gesture. I hope you don't take this in a disrespectful way or anything, just voicing my observation on things I've seen over the past few months and figured as the gTab moderator (even though you're selling yours), you'd probably want to know what the community members of your device forum are observing.
Thanks for your hard work, but this is something that's inevitable and should not be avoided or curtailed for a later date.
jerdog said:
This will be the role of the posters of the ROMs/MODs to delineate which bootloader is used, as well as to provide the appropriate disclaimers, etc.
At the end of the day, XDA is a developer site - and all action taken is at your own risk and decision. If users are not willing to fully research their choices the responsibility falls on them for whatever happens. There will be people who help out of the goodness of their heart - but not their responsibility if something fails like the user was warned it would.
Click to expand...
Click to collapse
No offense, but speaking as a non-1337 who's been dealing with 1337s for years, this post sounds like the typical 1337 attitude.
Dividing up the development section into 1.1 and 1.2 will save many headaches. Noone is here to stroke anyone's ego as a 1337. We're just trying to make the process go as smoothly as possible here.
flipovich said:
I disagree. The breaking into a 1.1 and a 1.2 sub-forum of the development section seems pretty much critical to avoid any unnecessary headache for XDA gTab users. Saying what you said above is like throwing a 10 year old behind the wheel of a car and saying: "You accept the risks of your own actions, so go ahead and start driving and we'll see where this leads us."
Click to expand...
Click to collapse
We're not talking about putting people behind a car. We're talking about people accessing a forum that is for development. Any usage of the forum and the developed solutions presented is at your own risk.
flipovich said:
You wouldn't do that under any circumstance, so you provide "buffers" (training, mentorship, test driving, books, etc) which in our case would be the sub-forums separating boot loader types to attempt to put forth a friendly effort to help users avoid a headache.
The sub-forums would look something like this:
Android Development:
General Development (CWM, radios, tools, app dev, etc)
1.1 Bootloader Development (all 1.1 based kernels, ROMs, and misc.)
1.2 Bootloader Development (all 1.1 based kernels, ROMs, and misc.)
Click to expand...
Click to collapse
This is not a precedent at XDA nor would it be approved. There is some segmentation under a device but that is by OS - not by a bootloader in an OS.
flipovich said:
Not putting forth the effort to at least provide a somewhat protected atmosphere for the XDA gTab users is negligence. I have been a member of the XDA community in an observer/user fashion for much longer than my membership reflects. From my experience with XDA, I have noticed a trend on the gTab community in more recent times that is not reflected on the other device forums I have utilized (HD2, Tilt, Tilt2, G2, G1, MyTouch, and a few more that I cannot remember). The vast majority of those kept higher and more enforced standards than the gTab forums have lately, but still looked out for the users by putting certain "buffers" and preventative measures into place to try to keep users from messing up their pricey hardware due to negligence.
Yes, negligence on the user's part is their fault by not following some instructions laid out for them, but it doesn't mean that the leadership can't at a minimum provide some buffers out of a good faith gesture. I hope you don't take this in a disrespectful way or anything, just voicing my observation on things I've seen over the past few months and figured as the gTab moderator (even though you're selling yours), you'd probably want to know what the community members of your device forum are observing.
Thanks for your hard work, but this is something that's inevitable and should not be avoided or curtailed for a later date.
Click to expand...
Click to collapse
Not taken as disrespectful at all. And whether or not I own the device has nothing to do with the level of effort put into the forum. It is not the role of a moderator to police the information and provide checks and balances for the users. It is the role of the developer or poster to do that. Moderators are here to keep threads on topic, keep users from trolling, cleanup spam, etc.
Developers should mark their projects as to the relevance for the user - i.e. [BL1.2] or whatever. It's important for users to be held responsible for their actions and we are a development community - not a hand-holding community.
It is also the role of users to report posts that they see as problematic to the OP and if the OP doesn't make changes then you can bring the moderators in to assist as appropriate. It's also the role of users to help keep things sorted by reporting posts that need moved elsewhere, etc. and to report those who are abusive so that they can be actioned.
My goal was not to ruffle feathers. I'm just stating my concerns and suggestions, whether they are feasible or not.
The newer 1.2 ROMs here on XDA seem to add these differences to their titles and first posts (as mentioned), but my concern is the older 1.1 ROMs, especially ones that were created before this new branch was released. For example, some of the CM7 based ROMs, and even CM7 itself, are not safe to use if you are flashing directly from 4349 stock. And I've also made suggestions in the Cyanagenmod forums, for the same reasons.
And I appreciate the suggestions and involvement. Thanks!
Thanks
I never heard of the g tablet before this week, but the TD Ebay deal was too good to pass up. I got one with 1.2-4349 on it. First thing I did was downgrade it thanks to the heads up info from this forum. With some reading was also able to put Veganginger on it. First attempt, it locked it up when rebooting after a successful install. But again, this forum was right on top of it. I followed the info for using nvflash and got back to a stock rom, ran clockwork again and installed Vegan no problem.
Not much to comment on the tablet itself yet, it just arrived yesterday, but so far its been fun just making the updates.
Just wanted to say thanks for all the info.
I've read through this thread and I do not believe a separate sub-forum is necessary. As such, I am closing this thread before the discussion becomes out of hand.
The differences between the Gtab versions lie in software alone. There is currently a method available to revert to 1.1 using nvflash in order to regain ROM compatibility with 1.1 ROMs. This, coupled with a simple warning as to which bootloader is compatible will ensure that everyone is satisfied.
In the past, we have only given separate development sub-forums for devices where a revision change is tied to a physical hardware change. As this is simply a (reversible) software difference, Jerdog has taken the correct approach by suggesting that the developers and moderators delineate which ROMs are compatible with which bootloaders.
Will Verduzco
XDA Senior Moderation Team
You've probably read the new Operation Iron Fist going on here: http://forum.xda-developers.com/announcement.php?f=1159
As of now, I will no longer stand for the way some things are going here. If I see ANY trolling, flaming, or disrespectful behaviour, you will receive an infraction on the spot. No more warnings.
Also, offtopic chatter on the development forums is exceptionally high here. This will stop, since I will also infract upon it.
Just one more thing: if you encounter ANY of above mentioned offences, let me know ASAP, instead of foulmouthing about it on the public forum. If I see that, you WILL get an infraction too.
I am sorry for acting this way, but you guys are forcing me to do this.
Sounds good to me, unless "iron fist" translates in reality to Naziism.
There's a difference in insulting people, and trying to contribute and being attacked. I tried to contribute by pointing out that there were several bugs that were fairly severe. If a user doesn't point them out, what's the point of ever releasing anything beyond 1.0 and then closing the thread?
However, there's a small group of users in the community who have resorted to fanaticism, and when someone goes that direction it shouldn't be tolerated. When I get criticized for bringing up a bug, and told I'm a "habitual complainer" how is that supposed to encourage anyone to want to participate in the DEVELOPMENT of anything for any phone? For some reason the Infuse 4G participants who I'm referring to seem really on edge, and speak out (often personally) about anyone who says anything aside from praise.
We're not here to be reassured that the world is 100% good, and that everything everyone says is amazing, we're here to participate in an active development community, be it as a developer, or as a contributing end user. The moment you criticize your user base is the moment you go from being an open community of developers and end users to a system of dictatorship, and closed platformism (yeah, it's a word now because I said so), lol.
To the people who squash anyone who's new, or doesn't know something, or volunteers that they're having a problem and need help, STOP. There's no need to make someone feel bad for asking a question a second time in a 3000+ post thread and then criticizing them for not reading the answer in post 2106 on page 291. There's no need to tell someone they are full of crap when they say they're having internet speed issues, and that since it works for you to your satisfaction that they're obviously less intelligent. There's no reason to tell someone they're wrong just because you disagree with them.
To make this a "community" everyone has to be understanding that everyone has their opinions, and that we're all here to make the phone in whatever thread a better phone.
Without developers, this site wouldn't exist. Without end users wanting mods, this site wouldn't exist. If you continue to alienate anyone who's new and turn this into a fanboy forum, it's just going to send them back to Apple iOS forums and devices. If that's how you want to help turn the mobile community, fine, but personally, I don't.
Bella
True to some extent. But the main problem is this:
NeoS2007 said:
Just one more thing: if you encounter ANY of above mentioned offences, let me know ASAP, instead of foulmouthing about it on the public forum. If I see that, you WILL get an infraction too.
Click to expand...
Click to collapse
Most people here think they can say ANYTHING to ANYONE. That's not what this forum is about. It's aimed at development and not discussion. If you feel you should debate in any way, move to another forum.
And you can call my method anything you like, I used to warn everyone before acting, but that's over. You of all people should know that.
I'm not about to take any sides, but Bella, you're completely out of line. Being part of the community is different than creating your own community. This is a group working together towards a common goal. To reach that goal, we must provide detailed, factual and documented information to the dev(s) so that we can enable them to create the best possible releases. I've seen no images, logcat, etc. that was provided by you. Granted, there are several others in the forum not providing these details, but there are several who have provided very specific and detailed information. It took far too long for you to provide this kind of information and it only turned the conversation south. You are not alone, so know I am not singing you out; there were several others who contributed to a negative environment. The reason for my posting this is because you were the only one to come here and plead your case.
That said, this is a community filled with individuals. We all have different personalities and will act and react differently to different scenarios. Hopefully this can be the beginning of a constructive and collaborative effort by us all to truly bring our Infuse to the next level.
I will not retort nor reply, I am simply sharing my views and experiences in this forum so far. The Captivate started off rough, but never reached this level. It won't be easy resurrecting this one from the ashes, but it can be done.
Right, you say I was unable to provide any factual data, yet I responded each time with factual and accurate data that was requested by GTG. I think some people get frustrated because often issues that come up are issues they just don't know how to solve, and often that leads to accusations that the end user is crazy, unintelligent, or just uncooperative, when the case is the opposite.
Clearly in the end I identified a data connectivity issue first (review thread if you like) that's been significant enough for him now to pull the ROM until he can resolve the issue. Rather than fellow members responding with productive comments, they responded in an attacking manor. My point was valid (as vetted by GTG at this point), and for those who weren't having the issue, why pipe in and say there's no problem? Do you take your car to the mechanic and tell him everything is working fine?
Initially I was called a complainer for bringing it to the attention. Unfortunately as a developer you can't expect that an end user is always going to be able to provide the detail you need. If I had the experience and desire to build a ROM I'd do it myself. It's kinda like building a house then expecting to know where to find a pipe junction inside a wall that only you know where it is. There's only so much expectation you can have of the end users.
Additionally, this is not the Google Developers Forum. This is not a forum of official Android releases, this is a hobbyist community of people who want to tinker with their phone. If a developer wants to be in an environment of developing for Google, maybe they ought to apply for a position at google.com/jobs. The ROMs that come out of XDA are great, but we have to realize there is nothing official about anything that comes from these forums.
I think the comment should be changed from "development, not discussion" to development and on-topic discussion. Because if you discourage discussion, it's like discouraging shopping in a mall. Discussion is what makes a forum like this great.
I'll certainly commit to staying on topic in the future.
Have at it neo. Thanks
Sent from my SAMSUNG-SGH-I997R using XDA App
Bella, you never provided the data requested. You just compared two modems - this was NOT what gtg asked for. He asked you to compare 2.0.1 to 2.0.2 performance. After looking through the thread, I'm fairly certain never provided this information, you just maintained that you had provided the requested data because of your modem comparison tests.
Perhaps you were under the mistaken impression that 2.0.1 to 2.0.2 was a modem firmware change - if you had opened the update zip to analyze the contents you would see that it was not. There's a reason gtg specifically asked you to compare 2.0.1 to 2.0.2 and not to compare UCKE3 vs UXKG3 modems, and the latter is what you did.
Also, the network connectivity issue was only one of the reasons gtg pulled the ROM. He was trying to be nice, but the poor attitude of many users in the thread was a MAJOR contribution to the ROM pull also. In addition to that, at least two developers have stated either in posts here or on IRC that they are extremely uneasy about releasing any ROM images on these forums because of the poor behavior on these threads. It is also why I currently have a "no support, don't PM me" policy for the kernel I released - it was the only solution to getting experienced users the build that many were asking for without subjecting myself to the painful experience gtg did.
PLEASE have at it! I haven't visited this forum in a few years (iPhone) and now that i'm back with an Infuse this place isn't anything like it use to be.
My 2cents.
Entropy512 said:
Bella, you never provided the data requested. You just compared two modems - this was NOT what gtg asked for. He asked you to compare 2.0.1 to 2.0.2 performance. After looking through the thread, I'm fairly certain never provided this information, you just maintained that you had provided the requested data because of your modem comparison tests.
Perhaps you were under the mistaken impression that 2.0.1 to 2.0.2 was a modem firmware change - if you had opened the update zip to analyze the contents you would see that it was not. There's a reason gtg specifically asked you to compare 2.0.1 to 2.0.2 and not to compare UCKE3 vs UXKG3 modems, and the latter is what you did.
Also, the network connectivity issue was only one of the reasons gtg pulled the ROM. He was trying to be nice, but the poor attitude of many users in the thread was a MAJOR contribution to the ROM pull also. In addition to that, at least two developers have stated either in posts here or on IRC that they are extremely uneasy about releasing any ROM images on these forums because of the poor behavior on these threads. It is also why I currently have a "no support, don't PM me" policy for the kernel I released - it was the only solution to getting experienced users the build that many were asking for without subjecting myself to the painful experience gtg did.
Click to expand...
Click to collapse
Understood. I provided what he asked to the best of my ability at the time ... I'd reference my post but I'm not digging through a 3000 message thread, sorry. :-(
Matt-Helm said:
PLEASE have at it! I haven't visited this forum in a few years (iPhone) and now that i'm back with an Infuse this place isn't anything like it use to be.
My 2cents.
Click to expand...
Click to collapse
The Inspire and Aria forums were much more friendly, it's not this site, it's just the Infuse forum in general. I had a very positive experience in the Inspire threads
I think it was not the fact that you raised an issue that bothered the developers, it was the manner in which it was raised.
Also, look at it from a developer's perspective - when the thread is filled with posts that clearly indicate that the poster didn't even read the first post of the thread in its entirety (not saying that you did this, but many others did), it gets massively frustrating.
I've never seen so many people completely fail to read/comprehend the first post of a thread as the Infused v2 thread. Even after it was put into the first post as a known issue, we still got reports of HDMI not working every 3-4 pages.
After what could be effectively described only as an all-weekend hack session two weekends ago, everyone's been a bit exhausted/burned out. But everyone keeps demanding MORE MORE MORE!
Entropy512 said:
Also, look at it from a developer's perspective - when the thread is filled with posts that clearly indicate that the poster didn't even read the first post of the thread in its entirety (not saying that you did this, but many others did), it gets massively frustrating.
I've never seen so many people completely fail to read/comprehend the first post of a thread as the Infused v2 thread. Even after it was put into the first post as a known issue, we still got reports of HDMI not working every 3-4 pages.
Click to expand...
Click to collapse
I agree 100% ... the only thing I can say is that remember that many people come from iphone, aka the dev team blog, which is much different. On theirs you read from the bottom up. I don't think that's an excuse since XDA uses the globally accepted standard in forums. But yeah, last night there were about 25 people in an hour asking why the links didn't work, lol.
Not really sure if this is on topic or not.... I just looked up "Iron Fisting" and this was the first result http://www.urbandictionary.com/define.php?term=iron fisting
Holy cow! The mods/admins mean business!
AdamOutler said:
Not really sure if this is on topic or not.... I just looked up "Iron Fisting" and this was the first result http://www.urbandictionary.com/define.php?term=iron fisting
Holy cow! The mods/admins mean business!
Click to expand...
Click to collapse
I know my mouth (and legs) will be shut going forward.
Bravo Neo. Bravoooooooooooooo.
Thank you!
Looking forward to seeing a cleaned up forum!
by the way? how do u become an admin?
i spend way to much time on here...even while im at work (because its my job relates highly to this)
AdamOutler said:
Not really sure if this is on topic or not.... I just looked up "Iron Fisting" and this was the first result http://www.urbandictionary.com/define.php?term=iron fisting
Holy cow! The mods/admins mean business!
Click to expand...
Click to collapse
(removed comment)
looking forward to clean and healthy forum.
I hope I'm not going to make any enemies by saying this, but I can't say I entirely agree with this being an iron fist. So far all that has been done is the Infused v2 ROM thread was locked. On any other forum I frequent they start with punishing the offenders individually, and only lock the thread as a last resort. I didn't see anybody get personally warned and I didn't see anybody get banned, and it really was only a handful that caused problems. I know there were a LOT of people that were posting the same questions over and over, but that can't be helped most of the time. The ones that were bickering and really ruining the thread are still posting happy as can be. I know it sounds like I'm questioning the mod(s) or being ungrateful, but I don't mean it that way. I just feel like we lost the ability to have an important and fun discussion before all the possible options were explored. Now if gtg asked for the thread to be locked then that is an entirely different matter, but I didn't get that impression from reading the last post.
I really do enjoy these forums and always have, and feel like this board is run very well. By this board, I mean the Infuse board. I just wanted to say that I don't know if I entirely agree with the way the infused thread was handled.
EDIT: I wanted to add that I know the mod(s) do this for free in their spare time, and I know that you can't police it 24/7. I really do appreciate your efforts at running this board, and the ONLY thing that I've seen that I take "issue" with is the handling of the Infused thread. Maybe there are things behind the scenes that I didn't see, and if that is the case then I apologize.
The Infused forum is only locked temporarily, as I asked the dev to contact me when his rom is finished.
Thanks for your support people. Just remember to report anything that's offensive/disrespectful/wrong/etc. and I'll take care of it.
NeoS2007 said:
The Infused forum is only locked temporarily, as I asked the dev to contact me when his rom is finished.
Thanks for your support people. Just remember to report anything that's offensive/disrespectful/wrong/etc. and I'll take care of it.
Click to expand...
Click to collapse
I did see where it was locked only temporarily. I just wanted to get that off my chest, so to speak. It wasn't REALLY bugging me, but I did get pretty frustrated with how people were acting. It was pretty ridiculous. Like I said before, I really do appreciate your efforts to keep our forums running smoothly. Thank you for your continued presence and work, and for not taking my post personally, (at least I don't think you did ).