Hi,
Next to making ROMs I want to try and work on the wiki some more to make it THE prophet information source on basic questions.
I made this thread for users to suggest stuff that they think should be covered.
This is NOT a thread for asking questions about your prophet.
Thanks
Hi Jester
Wiki forums has pros and cons. Reading 20 pages of mixed text is not by far the best way to learn anything, the main problem for me is to distingish good info from bad one.
The 'Expert Selection': For each thread I would like to see only what an expert/senior member has selected. This filter can be multiple and tematic; the same 'expert' can select only some posts an 'rename' the sub-thread; and of course the same thread could be filtered by two or more members.
This way i can have the same point of view of them, and this is important for me..
Hi Jester,
Thanks for the big support on the Prophet and releasing ROM versions!
In the Forums there are many questions about how to upgrade your (for example) Dutch ROM to a WWE, what to do, maybe this is also something to add to the Wiki.
The Wiki side sould be rich of information about how to upgrade the ROM, what are usefull programms, free or payed, where does ipl and SPL stand for, What are the latest versions.
Groet,
TheTeek
Hi Jesterz,
Thanks a ton for your ROMs and your efforts!
One of the most eagerly sought after info is ROM editing specifically for G4 roms (specially again for Prophet).
Can you help in consolidating the tools (along with usage tips) to modify ROMs to achieve the following:
1. Steps to upgrade only the OS to whichever ROM OS you want.
2. Steps to increase the pagepool to X [I understand the device runs faster on an increased pagepool], but I am not sure of the ideal size to be kept. I got some details from here: http://forum.xda-developers.com/showthread.php?t=283280&highlight=pagepool
4. Steps to remove MS Office, voice dial and other applications from the rom and add a few apps. Will also need help in adding few apps like resco explorer and some registry hacks into the ROM.
5. Steps to move some programs from programs to system (for e.g smsdeliveryfix)
Am sure others can also add to this request.
Thanks.
Hi Jesterz,
thanks for this thread, I beleve there are a lot of stupid questions because a lot of information in the wiki are too much generic and the people have fear to make some errors (IS NOT YOUR FAULT because the newbie are sometime very newbie).
My dream wiki is:
- more specific
- with new information
For example, if you check the main procedure to update the rom, there are some step not very clear:
1) ***
If it states: "Could not update itsutils.dll to the current version, maybe it is in use ?" Do the following :
Copy the cab's from the Utils folder in the Lokiwiz03a.zip file to your Prophet and execute them.
(There are two files : "Cert_SPCS.cab" and "EnableRapi.cab")
This is not clear. A lot of user wrote me in private asking if you need to do a soft reset (or no, or an hard reset) after that.
2) ***
Sometime after that the itsutils.dll error is still alive. What the people have to do?
3)***
In some rom, you don't have to unlock the cid... right? But this is not on the wiki.
4) ***
There are some question where there are not answer, like this one in the ROM DUMPT.
"if you want backup your own rom, you have to do the unlock cid procedure and update the rom with another one. But if you do that you lost your own rom!!! So, why there is a Dump rom procedure, if you can not do that with your original one?"
5) ***
I would lik see in the wiky a tread with the list of the BEST ROM and the update.
6) ***
There are some etc...
I think what would be a *very* good piece of info for newbies is what are all the tools you guys use (cert.cab, etc etc....) and what each does to some degree....
as a newb myself, I find it *very* daunting and very scary to see lots of stuff posted on the forums that say "How To: Copy fileA and fileB to device, run fileC.exe on computer, then execute fileD on device, then wait, and poof! you're done". I'd be nice to at least know that the heck each of the components are and the purpose (even if it's very technical) of each one.
Also, if it's possible, list off any interdependencies these tools have. There are too many "half-instructions" floating around and it's really difficult to determine whether the user needs to do anything before hand before following the instructions.
*lastely*, Can we get a guide that lists off all the pros and cons for each of the custom ROMs that are getting posted. It's a little tough for newbies to know what are all the pros and cons for each ROM. Yes, we know there are pros and cons and nothings perfect, but *what* are the bugs? and what are the features? At least that way we can decide for ourselves whether or not the ROM will work for us...
I'm only into day 2 of all of this so I apologize if what I'm suggesting sounds stupid.
Thanks
Hello all,
Jesterz, thanks you for your investisment in the forum.
Some suggestions about the wiki.
One of the main issues for upgrading a rom is to have a clear view of what is going on.
There are many threads discussing different roms.
It should be grateful to have one main page giving an overview of every live rom and a page for each rom where the author can put a link and also give the current status of his rom and known issues. So I join to Mr Yellow for this.
It should be something very basic, not as far as an Issue tracking page (ie http://jira.codehaus.org/browse/MPA)
By now, whenever I want to update a rom, I have to read the entire post...
One solution can be, for each cooking rom version, adding a text file that describe everything to know.
Of course, a howto for cooking rom and useful mistakes can be also interesting.
cheers
Andre
Hi Guys - and yes, thanks for all the time & investment made here.
I'm a fairly new member, and one thing I think would benefit the WIKI is an idiots guide or introduction.
I found the the wiki a bit tricky in so much that it starts at a fairly high level and misses the basics
Whats an AKU and why might I prefer a new one ?
What extra features can I get with a new rom ?
Why might I need newer radio drivers ?
Stuff like that.
Also, a glossary would go down reall well.
JJ
doublej said:
Hi Guys - and yes, thanks for all the time & investment made here.
I'm a fairly new member, and one thing I think would benefit the WIKI is an idiots guide or introduction.
I found the the wiki a bit tricky in so much that it starts at a fairly high level and misses the basics
Whats an AKU and why might I prefer a new one ?
What extra features can I get with a new rom ?
Why might I need newer radio drivers ?
Stuff like that.
Also, a glossary would go down reall well.
JJ
Click to expand...
Click to collapse
I agree with the above......more of a beginner area with more explaination
Not an idiot guide but something more for the leaner who want to be experts like most here
Get to it
I think these are all great suggestions. The Prophet wiki is looking pretty sparse at the moment. So why doesn't everyone start editing it, rather than just talking about it?
Cheers,
uayeb
Hello
read it !
agree!
Shall i make a tutorial for changing the case? I know there is one already in another forum(modaco). But i want one on xda-developers?
the more the merrier!
I think possibly the most useful thing would be 'How to recover Prophet stuck in Bootloader'. I seem to telling people how to do it most days and sometimes more than once a day...
I'll happily write a 'How To' if required.
l3v5y said:
I think possibly the most useful thing would be 'How to recover Prophet stuck in Bootloader'. I seem to telling people how to do it most days and sometimes more than once a day...
I'll happily write a 'How To' if required.
Click to expand...
Click to collapse
You know, that's what's awesome about the wiki... you *CAN* go ahead and write whatever you want. It only takes like 5-10 minutes to understand the syntax of wiki-code... create a new page, write your stuff down, and start formatting. Bam, you've created a wiki page that everyone can use. Announce to the fourm that you've done so and you're done!
Then you can start insulting newbies that complain about getting stuck in boot loader that they should search and read the wiki! It feels really good!
mr_yellow said:
You know, that's what's awesome about the wiki... you *CAN* go ahead and write whatever you want. It only takes like 5-10 minutes to understand the syntax of wiki-code... create a new page, write your stuff down, and start formatting. Bam, you've created a wiki page that everyone can use. Announce to the fourm that you've done so and you're done!
Then you can start insulting newbies that complain about getting stuck in boot loader that they should search and read the wiki! It feels really good!
Click to expand...
Click to collapse
But how can I get it uploaded?
l3v5y said:
But how can I get it uploaded?
Click to expand...
Click to collapse
You don't upload anything. You can edit each page like it was a forum post. there's special syntax for lists, bullet points, headlines, links etc... but if you want to create a page, all you need is a title and that's it. Everything is done on the serverside.
The easiest way to start is to pick a page, click the edit button at the bottom, then add a new link to a page using the syntax [new page title]. when you save it, "new page title" becomes a link to a new page where you can create a new page and add more content there.
Give it a shot. Don't be afraid to break stuff.. you can always look back on old versions of the page and reverse any changes.
Pallas said:
Shall i make a tutorial for changing the case? I know there is one already in another forum(modaco). But i want one on xda-developers?
Click to expand...
Click to collapse
I second this!!! I've been looking at the modaco 1, & feel we need to have 1 from xda dev & Pallas is the man... heheh
mr_yellow said:
You don't upload anything. You can edit each page like it was a forum post. there's special syntax for lists, bullet points, headlines, links etc... but if you want to create a page, all you need is a title and that's it. Everything is done on the serverside.
The easiest way to start is to pick a page, click the edit button at the bottom, then add a new link to a page using the syntax [new page title]. when you save it, "new page title" becomes a link to a new page where you can create a new page and add more content there.
Give it a shot. Don't be afraid to break stuff.. you can always look back on old versions of the page and reverse any changes.
Click to expand...
Click to collapse
Breaking stuff can be fun I'll give it a try now...
l3v5y said:
Breaking stuff can be fun I'll give it a try now...
Click to expand...
Click to collapse
Good Luck!
What I mean is, it seems to me that it would be more efficient to put any/all files that may be upgraded as packages and instead of flashing cooked roms, we could flash a generic rom and uninstall old/reinstall new packages
Am I making sense to anyone?
I understand you
I believe this is part of what chefs who create "lite" or "unbloated" or "clean" or "naked" (in Garmin's ROMs) are trying to achieve.
I personally like the idea, and hope we see more of them.
My personal favorite ROM of all time was the very first Hyperdragon III
mbarvian said:
I understand you
I believe this is part of what chefs who create "lite" or "unbloated" or "clean" or "naked" (in Garmin's ROMs) are trying to achieve.
I personally like the idea, and hope we see more of them.
My personal favorite ROM of all time was the very first Hyperdragon III
Click to expand...
Click to collapse
Up until recently the problem has been that cooks either created loaded ROMs with tons of stuff added to them, or lite ROMs, where they stripped this out.
The issue was however that it is quite easy to strip things out of a ROM. Making CAB packages out of those stripped out files however can be one of the more time consuming tasks and cooks didn't always offer those packages. In addition, CABs which were made available from other sources weren't always packaged in entirety and wouldn't always install.
Cooks have been getting better at this recently however. My new set of ROMS follows these concepts precisely:
http://forum.xda-developers.com/showthread.php?t=429117
I have been calling and advocating for this too basically since the dawn of UC
Previously I didn't post much under different nick, but I have "put up together" this concept in THIS thread finally, albeit with somewhat misleading "temporary" title, but it is good discussion if anyone is interested.
Granted, few apps have to be cooked-in in order to function properly, but those are really just very few. But as you can read there, most objections against this kind of "real lite" ROMs (where any "upgraedable apps" are NOT cooked-in) come from people who don't understand it, or don't know much about UC or Sashimi (BTW I'm for UC rather than Sashimi because UC is much easier for any newbies), or just don't know/have no clue how it works and are affraid it would make troubles to them if they don't have the same apps cooked-in.
Perhaps any of you could add your input there, since there isn't much sense in starting new thread about basically same thing.
Bengalih, I will test your ROMs with pleasure when I have bit m,ore time (or actually a second Kaiser would be great ).
But I can already give you my sincere congratulations now if you have created such ROMs
I have made ROM based on hang.tuah's ROMeOS (it was going to be an update, but ended in another ROM, LOL - not quite "lite" as I would want it, but I can't change the things that were "always there" now ). I try to steer its users into UC and use "extended packs" for things like dialers, comm managers etc. They'll have best proof that "cooked-in" is *worse* than "installed" soon, when they will have i.e. choice of Opal or Kaiser dialer in the extended pack - which obviously would be impossible if the dialer was cooked-in in the ROM...
@bengalih: your post is what got me to thinking about this again
I'm happy to see that you others share my attitude towards efficiency
I have not completely read thru both of your threads but I suppose what needs to be done is to create a universal standard
The way I see it, this type of system would be beneficial to cooks and end users alike. End users need a minimal variety of options to install these collections and a minimal variety of each basic rom release to install the collections to. Cooks need a simple system to adhere to that requires no more work to put together their collections than the current amount of work they do to create their roms.
Here is a sample proposal (what I'm thinking right now with a minimal knowledge of rom cooking )
A base rom of each flavor could be made available to download. By each flavor, I mean a different rom with each combination of files that must be cooked in to work. I haven't read anything like that before so if there are more than a couple combinations then no more than 4-5 with typcal combinations should be considered.
I need to do some reasearch to learn what benefits and/or caveats are associated with UC and Sashimi. I suppose cooks should be the ones to decide whether to make their collection(s) combatible one installer or the other.
selyb said:
@bengalih: your post is what got me to thinking about this again
Click to expand...
Click to collapse
In the future it might just be best to post in the thread about this then. As a topic that has been tread over several times putting additional input into an existing thread would be more effective.
selyb said:
I have not completely read thru both of your threads but I suppose what needs to be done is to create a universal standard
Click to expand...
Click to collapse
Perhaps you should read through the threads that are already out there before staring a new one that re-hashes the same information.
selyb said:
The way I see it, this type of system would be beneficial to cooks and end users alike. End users need a minimal variety of options to install these collections and a minimal variety of each basic rom release to install the collections to. Cooks need a simple system to adhere to that requires no more work to put together their collections than the current amount of work they do to create their roms.
Click to expand...
Click to collapse
Good luck trying to get cooks to follow anything you propose. Not that it might not be a brilliant idea, but cooks are going to do their own thing. I decided to take matters into my own hands and cook my own ROMs according to the principles I thought best. I put the ROMs and my principles out there in hopes others will adopt them, but that's the best you can do...
selyb said:
A base rom of each flavor could be made available to download. By each flavor, I mean a different rom with each combination of files that must be cooked in to work. I haven't read anything like that before so if there are more than a couple combinations then no more than 4-5 with typcal combinations should be considered.
Click to expand...
Click to collapse
Again, pretty much what I have done already with the HTC and AT&T official 6.1 releases. A base ROM for each with a set of CAB file to customize to your desires.
selyb said:
I need to do some reasearch to learn what benefits and/or caveats are associated with UC and Sashimi. I suppose cooks should be the ones to decide whether to make their collection(s) combatible one installer or the other.
Click to expand...
Click to collapse
No offense, because I realize I am coming off a bit gruff in this post, but you do need to do alot of research. I agree with alot of what you are saying, but it has been said before (by myself and others). Also, there is no reason that a collection of CAB files wouldn't work with SASHIMI instead of UC or vice-versa. To your own admission, you don't understand how these installers work, but when you do your research you'll see that in essence they are both just installing CAB and XML files (and with SASHIMI the capability for much more).
Again, please don't take anything here as a personal attack. I can see that you are coming off of inspiration from my posts and I don't disagree with your basic ideas. However you will get better reception from all if you do these things:
1) Research what is out there before posting so you don't retread old ground.
2) Don't just "propose" ideas, put them into action. Even the best ideas are unlikely to be adopted unless you put effort into implementing them youself.
I say these to you for your own protection before someone not as nice as me begins to bash you for not doing research
Ok, well, I will quit posting to this thread before someone not so nice does come along.
selyb said:
Ok, well, I will quit posting to this thread before someone not so nice does come along.
Click to expand...
Click to collapse
Heh... well seriously, take some time and learn more of what is currently out there and see where it is lacking.
I generally invite user feedback on my development projects. If you go back through the older threads, and take a look at what I am trying to do with my BRR ROMs, please feel free to comment in there about what additionally you would like to see and why.
Trust me, I very much welcome an open debate about what would be an effective way to do things. I just wanted to burst your bubble a little bit (seeing as you are a newer member) that your aspirations, although maybe valid, are most likely not going to get implemented by a majority of the cooks throughout the site.
I don't mean to shut down your thread, and you should continue posting if you see it as the best place to do so. I just feel that if you contribute to some existing projects that already have momentum then your ideas are more likely to get some attention.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
*If you find this Guide Thread helpful, feel free to hit the "thanks" button below!
Okay, so I know this has been done before, but I felt it helpful to plant the seed of knowledge and guidance for those new to xda who, rather than being subjected to flaming and accidental trolling here as result of their own inexperience, and more specifically, here within the ATRIX 2 forums could find an advantage by reading and understanding this guide. That said, the purpose of this and my intent (along with the Senior Members, Members, and others) is that this will be a 'must read' here in the General Section of our beloved ATRIX 2 community, and that the guidelines I am about to share will benefit those new to xda to learn how to be contributing, helpful, rule-abiding citizens who will one day -sooner, rather than later- become "New Members" (Junior Members) and who will evolve and grow to benefit the entire ATRIX 2 community.
Now, aside from a certain sliver of members here, we all started out as "n00bs", including myself. So, don't feel as though you are some kind of plague to the societal ecosystem that is xda, you are simply at your infant stage. However, this is not an excuse for not following the rules of xda, which I will reiterate again shortly, nor is it cause for you to come in here as if you own the place. This isn't my forum, or your forum, it is our forum, and many people such as myself have a certain affinity toward it, and regard it highly for both continuing education, fellowship with friends, and causative shared knowledge. You can learn a great deal here on xda about your phone, what possibilities you can reach in terms of customizations and so forth, and if interested, how you can do your own developmental work with Android. However, all of these have one very imperative precursory requirement: read, search, read, and search. Your best companion, besides the help you may receive in your journey here on xda, will be that of Google. Use it, use it some more, and when you think you've exhausted all of your own resources to find answers for any questions, concerns, or confusions, keep using it! You will only thank yourself (and have a certain sense of self accomplishment) when you can solve your own quandaries or quagmires. Trust me, you are not the first person to have the issue your may be faced with, or will face at some point down the line, so the probability that your problems have been addressed here or elsewhere within the nether-webs, is extremely high.
Before diving right in, let me overview the rules set by xda:
*Search Before Posting, Maintain Proper Member Conduct, Post Only Using A Clear Subject And Message, Use The English Language, Post A Message Only Once, Do Not Post Warez (I'll explain what this means later), Do Not Spam (again, more explanation to come regarding this), No Requests For Donations Up Front, Do Not Use Copyrighted Materials Or Anything That Does NOT Belong To You, Be Helpful To Others When You Are Able, Do Not Post With Intent To Sell Something, Using The Work Of Others MUST Be Approved, Do Not Post For Your Own Monetary Gain, Do NOT Create More Than One User Account, Keep On Topic In Threads And With Your Posts, and Do Not Bump A Thread More Than Once In A 24 Hour Period.
For a full description of rules for xda forums, please refer to THIS THREAD.
*STANDARD DISCLAIMER: I cannot be held responsible for any and all damage related to Hardware loss or Data or Software, which the user might cause while attempting any procedures or methods found on xda. Additionally, I am taking the liberty to assume that anyone who attempts these procedures understands the potential risks involved. This guide thread is intended for aiding new members so as to have a better user experience here, and no risks of any aforementioned damages will arise from following this guide, I am still exempting myself from any liability as result of anything anyone does to their device(s).
(You will see disclaimers such as these, which I myself employ, to indemnify one's own responsibilities for that which you or anyone else may do as result of following guides/ROM installations/theming/modding/rooting/etc.)
---Getting Started (With The Basics)---
So for the sake of everyone's time here, I have to assume that you (yeah, you!) have already registered and read the forum rules, as well as watched that lovely "You're A n00b On XDA" video, so I don't feel compelled to do the entire rundown of the full length version of rules. However, I will briefly recap them here. Please keep these in mind when within the forum, and exercise your own abilities before enlisting the help of others here. Granted, we are here to help you, but if it is apparent that you have not helped yourself, we will let you know in a way that *hopefully would eliminate the need to call you out on your lack of reading, searching, reading, and searching some more. Now that we have that out of the way, let's begin:
1) Reading Is Invaluable, Searching Is Imperative:
As I mentioned before, reading is your most powerful tool that will give you the advantage to avoid being called that "N" word and more of a "New Member". Along with this, is searching. I recommend you read ALL of the stickies in each of the sections of this forum. They have been 'stickied' by our forum moderators for reasons that prove advantageous to everyone, and those who wrote these 'stickied' threads put in their own time and efforts in compiling information to be used and/or observed by the entire community. Please refrain from posting new threads, unless undoubtedly necessary. Even if your questions or concerns are not exactly in line with what's being/been discussed within another thread, but is even remotely similar, start by posting in that exiting thread. This keeps our forum clean and free of clutter, as well as avoids wasting the time of others, along with your own. You should consider the question or concern you may have, and choose keywords when searching for answers. Try several times with different keywords if your answer(s) didn't magically appear from your first attempt with utilizing the search bar. If you are unclear as to what term or acronym you need assistance with, please refer to THIS THREAD by stempox for a better understanding of what it is you are looking for. Other useful threads for New Members are found here: New Member Guide-Get the most out of XDA!! and Search guide video.
2) Proper Posting Protocol:
Posting is something that you might find yourself doing a lot of, and is your privilege as New Member here on xda. However, you should avoid posting to drive your post count up, and refrain from re-posting what others have already posted by re-wording their statements. Excessive posting is annoying, especially when the above Rule #1 is neglected to be followed. You get no special treatment for the most posts in any forum, nor do you gain any respect if you prove yourself unable or unwilling to read, search, read and search some more on your own. The most important three aspects of your new user experience will be found by reading, and searching, and along with this is posting. These all go hand in hand, and if you think about it for a second or two, make absolute sense that these are all tied in with each other, relying on each other, and benefiting each other as well. Also, take your time when posting by giving every little strand of information you can possibly thing of. Example: your firmware, your current ROM, what procedures you used, what methods you've tried, what country you're in (sound silly, but sometimes extremely important), what you're trying to do, etc, etc, etc. The more information you give initially, the less time we have to take to fish for leads to track down your problem(s), and the less time you have to take responding to our requests for more info. Don't go into "panic mode", just read and post accordingly. Also, xda has some implementations for keeping our forums legitimate, and free of junk advertisement (SPAM), and in doing so you will find that for your first 7 posts will be accompanied by irritating CAPTCHA prompt entries. You will also see a 2 minute restriction from posting again or editing your existing posts. This all will end once you have reached 30 posts, making your evolution from Junior Member to Member. Remember, don't post rubbish just to quickly scoot through this process. We all see what you post, and we all pay attention to these things here. You don't want to make yourself look like a "Johnny Cutcorners" here, just do your part by abiding and respecting others, and for goodness sake, respect for yourself as well.
General Section: This section of the Atrix 2 forum should be used for all discussion regarding the Motorola Atrix 2 (general chat, tips & tricks, etc...)
Atrix 2 Q&A: This section should be used for all of your questions relating to the Motorola Atrix 2. Please refrain from posting questions in the General Section, as we now have the Q&A for this purpose.
3) The Question Posting Conundrum:
So, you've spent hours upon hours searching xda forums, Google'ing your fingers to the bones and typing all the different keywords you can possibly imagine in that handy little search bar at the top right found on each xda forum page you visit, and still come up empty handed. Now, where do you post your question or concern? If you've reached your 10 post minimum and feel your issue is of a 'development' nature, or more specifically regarding a certain ROM or mod or theme, post in that Rom or mod or theme's existing thread! Do yourself a favor and post in the appropriate sections for whatever your topic may be. If you still have doubts, post in the General Section, but only after what (?) :searching, reading, searching and reading some more! Also, give your new post some time to be read, thought over, and responded to. Don't be so impatient that you bump (Bring Up My Post) your own post for answers, and don't post frantically calling for -or expecting an immediate answer. There are thousands and thousands of members on xda who live all over the world, so exercise your placidity by affording your post to be read and addressed in a reasonable time. A good suggestion is to subscribe to your own threads that you may post, along with any that you feel you'd like to "keep up with" that you have posted to by clicking on the Thread Tools Button and receive email notifications once a member replies. This is your indication that you have someone who has responded, and hopefully helped you along your way (assuming you have given all the necessary information for them to be of help!)
4) Thanking Those That Talk You Through It:
You've seen each member's username and avatar, and below those are the member's "thanks meter". This was put in place as an easy to recognize indication of a member's useful posts here on xda. It is a way to see those who have contributed much of their own time and knowledge and/or talents or abilities with their own development with Android, or by simply being one who gives useful answers or tips to others. It is by no means a measure of superiority, but rather an identifiable way to distinguish those who are more apt to be someone to provide helpful insight. If you have been given such insight or helpful tips/solutions by anyone here, click that member's "thanks button". Please forgo the formalities of a written 'thank you', though is you feel you must, accompany it with a click of that mouse as well! It means more to us when you do, and as you see yourself becoming more fluent in your understanding of things, you will notice that it feels better when someone takes the time to click YOUR thanks button. This signifies that our work here is appreciated, and our answers or help is valued. After all, we do this on our own free time, and have no obligations to you. Again, the number of thanks a member has is no significant measure of their status or stature, and many of the more helpful ones here are those with fewer than expected thanks in their "thanks meter". You must have at least one post in order to give someone a "proper" thanking, and you can gain the first one in The Say "Hi" Thread. You are limited to only 8 thanks per day, but you can work around this if you have both the mobile app for xda developers and a PC.
Getting Thanks:
You will see that everyone here has a "Thanks Meter" above their avatar. Here are the thanks counts needed to get to the next bar:
1st bar - 26
2nd bar - 51
3rd bar - 101
4th bar - 201
5th bar - 501
(There's a a bug here, never gets to 5 bars)
6th bar - 1001
7th bar - 2001
8th bar - 5001
9th bar - 8001
Maxed! - 10000
5) Flaming Firestorms And Trolling Treacheries:
While many members here have quite the sense of humor, New Member, you need to take that into consideration. You may be referred to as that "N" word, but please don't take offense to it. Though you may find yourself posting something that has been discussed previously, you may also find your self seeing a barrage or comments that you may take personally. I advise you not to, as most -if not all- joking is done in a good nature. Let's face it, we're here because we like to play with our phones, right? If you can't have a sense of humor about things, maybe you need a different toy to play with. Sometimes, members will spout off something that can very easily be taken as an attack, in which case you need to understand that the reason for this is most likely due to the fact that the comments posted reflect something that has been posted a gazillion times before. If you sense frustration, it is wise not to engage in a childish battle of insults and name calling. This can get you reprimanded, up to, but not limited to a temporary ban of this site. Avoid confrontation with others, that may escalate to something which you may regret later. If you feel a member is unnecessarily flaming you or others, please do not hesitate to click that little triangle at the top right of that member's post and report this to the forum moderators. Albeit, this is a handy way to bring an end to conflict before it can really get full swing, this is by no means your personal badge to wear as a "pseudo forum cop".
6) Weeding Out The Warez:
If you understand what you've signed up for as a new user here on xda, you know that this site is primarily for the developers, their work, and their contributions. That being so, it is highly against xda forum rules to post anything that avoids the payment of a software. There will be zero tolerance for people trying to avoid paying for software by asking for or advertising cheats, cracks, serial codes, or other methods of skirting the purchase of software. This is a site made up of thousands upon thousands of developers from around the world, and when you try to cheat the system by not paying for something a developer has worked on and released for purchase, you end up cheating the entire xda community. Just don't do it!
7) Admission To The Development Section:
Noobs seem to have an uncanny inkling to want to jump right in and have access to posting in the development section right off the bat. Fact of the matter is this, you can't! This is not to try to ostracize or "haze" the new recruits for a while, this was put in place by xda if members who have joined xda on or after March 11, 2012. The real reason for this is that xda tries to keep from having the Development Sections of every forum from being flooded with inexperienced New Members, and allow the Development Section to be left for the 'real' work of our beloved devs (developers). For New Members who wish to say "thank you" for the awesome new ROM or mod or theme their using in its corresponding thread may make you feel like a nice guy, it does nothing but add necessary "junk posts" to the otherwise important threads, and adds no valuable conversation to them. Think about what you are wishing to express in the Development Sections, and if you feel it is important, think again. The devs here appreciate hearing bug reports about whatever they have released to the general community, but doing so by simply replying, "GPS don't work no more" or "Don't get no text notification on my fone" doesn't help. Unless you are able to provide useful information to go along with your post, such as a logcat output, kmsg, debug log, etc., don't bother. Remember what I said earlier about providing as much information as you possibly can? This holds true here in the Development Section as well. Here's a great thread regarding this, [GUIDE] How to give constructive feedback to developers. You can also show your appreciation by rating a dev's thread by clicking the dropdown at the top of each of these threads (same goes for any other section within these forums) or by making a donation to them. Still think we're being unfair? Here's a summarization by Fallen Spartan: "The 10 post rule was put in place to make new users think, and hopefully contribute and help others by making useful posts rather than the usual crap like "thanks", "kewl" etc or ask questions which have been asked countless times before. They still have access to dev forums, just cannot post in them. Its not a massive restriction and to provide 10 useful/helpful posts is not hard." Now, don't attempt to cheat the system here either by jumping your post count up with junk posts just to get to have the privilege of having the access to the Development Sections, because believe it or not, these sections are the most watched sections by the forum moderators, and if caught you could lose your post count. Just go out and participate in xda the "right" way, you and the forums will be better for it. Read this thread for more: 10 post count rule for Dev threads.
8) User Title Territory:
Ever wonder what it means when you see a member's "title" under their avatar? Well, I can explain this also -at least with the words of juzz86: "I'll sum it up for you (or try, anyway!) There are Junior Members, Members, Senior Members first. These make up the vast majority of XDAs userbase. Recognised Contributors are nominated by other users and/or Mods/Developers. They are recognised for their contributions which are not specifically Development, such as detailed guides, one-click utilities and other tools/mods. Recognised Themers are also nominated by users/Mods/Developers, for their work themeing custom ROMs and providing standalone themes for flashing. Recognised Developers are nominated and approved by the Developer Committee, for their work in Development whether it be ROMs, Root methods, bootloader unlocks etc. Elite Recognised Developers are again assessed by the Developer Committee, and are deemed to have gone above-and-beyond in providing knowledge/hacks/tools/apps/ROMs for the XDA community. Forum Moderators are appointed by the Moderator Committee, after submitting an application (see the 'sticky' at the top of this forum - currently applications are not open). They are the first-line of keeping the forums tidy, friendly and orderly. Senior Moderators are the next step up the ladder, providing site-wide support for Forum Mods and looking after the nitty-gritty issues, as well as areas of XDA not policed by FSMs, such as the Marketplace. Administrators are next. There are several Admins - each look after a specific part of XDA such as the Portal, the Members and the User Experience of XDA as a whole. At the top is Mike Channon, who is overall Forum Administrator. Other titles you may come across:
Moderator Committee - sits on the Mod Committee
Developer Committee - as above, but for Developer Committee
XDA News writer - publishes articles for the Portal (front page)
Retired xxxx - have since officially 'left' their XDA position
Hopefully that clears most of them up for you. Contrary to what a lot of people expect, the thanks-meter does not figure at all in determining a users tag."
0 to 29 posts - Junior Member
30 to 99 posts - Member
100 + posts - Senior Member
9) Sport A Spiffy Signature:
Having a nice signature helps identify you both in your geographic location (helpful, for many reasons), what type of device you are using, any modifications or current software versions you are running, which carrier you are with, and other important information that could alleviate the annoying need to ask you for further information. A signature should inform others about your phone when you post a question. A good signature will include information helpful to others beyond the direct target of the question/reply. A great signature will inform the community with important information and potentially answer questions which have not been asked yet, avoiding repetitive posts. Please click here to make a signature (5-8 posts minimum) It's cool and you will get more help and respect from us.
10) Other Helpful Links:
Chef Central
[Tutorial] How To Logcat
QUESTIONS BELONG IN Q&A!!!
[INFO]FXZ what? An explanation
[GUIDE] How to give constructive feedback to developers
[INFO] What you need to know about ICS and your Atrix 2
Brief synopsis on basic rules and how to help the community
[HELP THREAD] Any Question Answered Here (NØØB Friendly)
The Beginners Guide !!! (NOOBS)[ALL IN 1 RESOURCE GUIDE]
---Welcome To The ATRIX 2 Community---
Now that we have that out of the way, it's time to start getting out there and showing the community that though you may be a "Junior Member" in rank, you are by no means nothing but a New User because you understand the rules, follow them, and help other New Members to do the same! So, enjoy all that you can gain from xda, and give all you can. It is a great place to be, to learn, and to grow in your Android experience. If you have any problems or questions or concerns, you can always PM (Personal Message) any member here on xda, and they will gladly give you their time in reply. This may bode well for those how still feel a bit uncomfortable with creating new thread posts, or simply would rather not clutter up our forum with useless or repetitive posts (I thank you, as well as any member whom you chose to PM for help!).
An while I'm mentioning other Members here, I feel that it would benefit you all to get to know some of the more predominant Members here in the Atrix 2 community. There are many great people here, but I will list some for you that have a strong presence here, and so that you might have a nice directory to refer to. I will start by listing our forum's Moderators (those who help keep the forum clean, organized, and in order), then Developers (those responsible for releasing all those great ROMs, themes, mods, scripts, and so on) and then some of the key Senior Members (those that have been contemporaneous and well versed in the Atrix 2's basics, and more complex issues). Please take some time to get to know these folks, they will be as helpful and as patient with you as long as you are conducting yourself in a "New Member" fashion.
Atrix 2 Moderators:
Moscow Desire
Mr. Clown
prbassplayer
Atrix 2 Current Developers:
alteredlikeness
cogeary
farshad525hou
jimbridgman
JRW 28
lkrasner
lukensteinz
rdavisct
Atrix 2 Developers From Chinese Forums:
socialx
xmsh
Atrix 2 Developers: (Past)
lfaber06
Atrix 2 Senior Members:
Archmag3
CapnPez
daavvis
Deliberate
Deveshmanish
dicksteele
DX2Trip
Fall of Enosis
hankbizzo5
jboxer
jfrank1485
Jimmy273
KEB64
lilhaiti
mtnlion
nephillim
PhoenixNghi
PRichardson
shinydesert
souljaboy
tmease1
X-jo
And, just in case, here in the video of the rules of xda developers site. Doesn't hurt to watch it more than the obligatory first time for your registration process. Enjoy xda, and I welcome you to our community!
I hope this guide helps you make your experience on XDA a better one. While I appreciate you clicking the thanks button below, I appreciate it more if you take what I have written here and keep it in mind when visiting our forum, and pass it along whenever possible to help out others here who are New Members!
Thank you for reading, and happy forum'ing! :good:
Credits: mf2112, juzz86, Fallen Spartan
New Member's Guide To Android Terminologies
Also, here is a list of commonly used terminologies and lingo used here in the forum, and since you are a New Member here, you'll need to learn how to use them! In order to fully understand the lessons that are being taught here, you’ll to need to learn a few of the more popular terms that are used when discussing the Android OS. When someone tells you to add a widget to your home screen, I don’t want you to have that dazed look on your face. You can learn this stuff! It’s easy. The first thing you need to do is learn the popular terminology used to describe things in the Android world. So here we go…
ADK: Android Development Kit, What people use to develop anything for the droid such as ROM's
AOSP: Short for Android Open Source Project, and when the term is used in ROM descriptions, it usually indicates that the ROM in question is based on the Android source code provided by Google itself, and not on some other ROM project or a company’s firmware.
Baseband: In communications and signal processing, the baseband describes signals and systems whose range of the frequencies measured from close to 0 hertz to a cut-off frequency, a maximum bandwidth or highest signal frequency; it is sometimes used to describe frequencies starting close to zero
Boot Loader: Executes code before any operating system is launched. On Android devices, the bootloader is usually locked because manufacturers want you to use the version of Android they’ve provided. With a locked bootloader on Android phones, custom ROMs cannot be flashed.
Boot Loop: simply means something is preventing the phone from completing it's boot cycle and is stuck between the boot animation and the unlock screen, creating a looped animation. This is often fixed by either reloading a Nandroid, or Reflashing a rom from the Boot Loader.
Brick or Bricked: Jargon for a completely unrecoverable device, (no more than a brick or paperweight).
Bug or Software Bug: an Error or flaw in software that produces a failure or unexpected/unwanted result. Typically created from incorrect code, this is why some ROMs are better and smoother running than others because certain developers have taken the time to input "perfect" code
Busybox: An app on your phone that will give you access to additional Linux/Unix based commands. You may need BusyBox installed to perform some root level tasks, and some other apps that require root access may need BusyBox installed as well. BusyBox is self-dubbed “The Swiss Army Knife of Embedded Linux.”
ClockworkMod or CWM: A recovery program that is often used to apply updates, ROMs, or create a back up or restore a backup file
Dalvik: is the cryptic name of the virtual machine (VM) in Android, and it’s the basis for running apps (with the .apk filename extension) on the platform. Before Android apps are launched, they’re converted into the compact Dalvik Executable (.dex) format, which is designed to be suitable for systems that are constrained in terms of memory and processor speed. Dalvik was originally written by Dan Bornstein, who named it after the fishing village of Dalvík in Eyjafjörður, Iceland, where some of his ancestors lived.
Dalvik Cache: Simply put it is the cache used by Dalvik, and it’s the result of Dalvik doing optimizations of running apps. Some Android ROMs allow you to move the Dalvik cache to your SD card, in order to free up internal storage.
De-odex: Apk files have respective odexes that devs use to supposedly save space. Deodexing means you convert it back to a .dex file and put it back inside the apk. This allows you to easily replace files (not having to worry about odexes), but the main point was to deodex services.jar so that you can change all text to different colors (such as the clock color to white) and to deodex services.jar, you need to deodex everything.
What the heck does it mean, exactly? Well, it’s probably the hardest term to explain in this rooting dictionary...
When a ROM has been deodexed, it means that its apps have been prepared so they can be modified. Deodexed ROMs feature apps that have been repackaged in a certain way. Android applications (.apk's) contain .odex files that devs supposedly use to save space. These .odex files are extracted from the application packages and put in the /system/ folder on your phone, to speed up boot processes and to allow parts of applications to be preloaded.
However, this makes hacking and modifying those apps difficult because parts of the apps have been extracted to another location. Deodexing means that all pieces of an application package are put back together into one file, and it makes sure that a modified .apk won’t conflict with some separate odexed parts located somewhere else. Developers of custom ROMs choose to deodex their ROM packages, since it lets them modify various .APKs, and it also makes theming possible after the ROMs have been installed.
Dev. or Developer: An individual that creates, or alters a file in such a manner as to advance the program
Ext2/3/4: This refers to partitions on your SD card. They’re extended file systems for Linux that can be used by Android, usually in order to preserve internal storage space. Many custom Android ROMs require that you have an Ext2, Ext3 or Ext4 partition on your memory card. Ext2 is the oldest type of extended file system, and Ext4 is the newest.
So what exactly is a partition? It’s a part of a hard disk, or a SD card in this case, that’s separated from the other parts. Think of partitioning as dividing your SD card into two sections that have different purposes.
Firmware: A phone’s firmware is basically its operating system. A “firmware update” means that the operating system, the software that controls the phone, is updated. “Stock firmware” means that the firmware is unmodified: it’s the version of the operating system the phone’s manufacturer delivers.
Flash or Flash Memory: To flash a custom ROM, or a firmware, simply means that you install it. So, flashing is the process of installing a new version of the Android operating system, or just parts of it, like such as the radio and/or kernel. Flashing new ROMs is done via the Recovery Mode, usually with ClockworkMod Recovery.
FXZ: FXZ is an acronym for Full XML Zip file and is the format for most dual core Motorola firmware files. They are an archive of all of the stock partition images for a given device to be flashed in fastboot with either RSD lite or using adb and the fastboot binary.
Kernel: Central component of most operating systems: it’s a bridge between applications and the actual data processing done at the hardware level. Android kernels are often customized, optimized and modified for different purposes, such as over-clocking the processor or extending the battery life. Custom ROMs usually include a new kernel.
NanDroid or Nandroid Backup: Anyone with root access make a complete system backup. It lets you create a backup of every piece of information on your phone, and it can be restored later whenever you want. NANDroid backups are usually performed before flashing a new ROM, in case anything goes wrong with an update or when flashing, or if you want to return to your previous setup later. NANDroid backups are created from the Recovery Mode often found with CWM.
Odexed: See Deodexed
Radio: It’s the radio on your phone that handles communication, the radio that sends and receives voice and data. Flashing (installing) a new radio can improve your reception, and bring other benefits.
Root: Common word associated with giving a user "super user" access to their phones programming and other various aspects that would normaly not be possible, also known as "Jailbroken" for iPhones.
OS: Operating system, I.E. Windows, Mac, Ubuntu...and Android.
Overclocking: Speeding up the CPU past the factory presets to achieve a faster and more responsive device
ROM: Read Only Memory, a program used to make changes to anything from the look of the home screen, to icons to custom boot animation
RSD Lite: This stands for "Remote Software Download", and is Motorola’s own tool in flashing virtually any type of program, (so long as its in .sbf form) to the Android OS
SetCPU: This is a popular application for overclocking or underclocking your phone’s processor, making it faster or slower. It may require a special kernel in order to work.
Shell or SSH:secure shell or ssh is a network protocol that allows data to be exchanged using a secure channel between two networked devices
SPR or SPRecovery: A recovery program that is often used to apply updates, ROMs, or create a back up or restore a backup file
Stock:Simply means an unaltered state, such as when you first purchase your phone from Verizon, or when you do a factory reset to "go back to stock."
SU or Superuser: When you root your Android phone, you will get superuser access. The superuser or root user is sort of a special user account for system administration.
Terminal or Terminal Emulator: An app that lets users access Android’s built-in Linux command line shell. It’s useful for programmers and for those with root access. There are some Roms that have built in theme and/or tools that are accessed from Terminal.
Theme: A set of icons, backgrounds and app trays that change the aesthetics of the overall look of the droid and its applications
TUN/TAP: Refers to a network TUNnel, operates within layer 3 packets, or ip packets. Packets sent by a system via a TUN/TAP device are delivered to a user-space program that attaches itself to the device. A user space program may also pass packets into a TUN/TAP device. In this case TUN/TAP device delivers (or "injects") these packets to the operating system's network stack thus emulating their reception from an external source.
Underclocking: Slowing down the CPU mainly to limit battery usage
.sbf: Summation Briefcase File
.apk or APK's: An .apk file extension denotes an Android Package (APK) file, an .apk file can be opened and inspected using common archive tools
.tar: Similar to a zip file, a tar file archives multiple files into one file
.tgz: TGZ files are commonly used as install packages for Slackware Linux.
Reference source: droidforums.net
Credits: da2zoe, Sam Fisher
You sir are determined to get us out of the stupidity waves!! Thanks for the write up.
Edit: I should have screamed "Sticky" when I have seen something like this, but learnt the hard way that, people tend to ignore stickies
so better keep it this way and lets not let it get lost in the pile of other threads and make it floating, bumping and hope the n00bs read this.
Apex you're awesome. You should write for a living.
Edit:totally sarcastic. I've read his articles not too shabby.
mtnlion said:
Apex you're awesome. You should write for a living.
Click to expand...
Click to collapse
I think he does!
Edit: My bad I didnt recognize the sarcasm in it
Sent from my MB865 using xda app-developers app
Thanks guys! If I could forge a decent living being a writer, I'd quit my job in a second. And if I were to really have a wish cone true, I'd go at it HST style and buy myself a cabin in the mountains of Colorado and drink myself stupid while hammering out pieces on my typewriter. Though, in my case it would be a computer rather than typewriter, but the booze would still be in the equation. Oh, and the guns...
Sent from my SAMSUNG-SGH-I747 using xda premium
Maybe add to this a list who the dev team and the more Sr. members are in here, so that noobs recognize those immediately, and may see the value of those posters quicker in replies to new users quests for help.
If you want a list I can help with that through PM if you would like.
This is absolutely AWESOME!!!! Great job!!!
Sticky!!
jimbridgman said:
Maybe add to this a list who the dev team and the more Sr. members are in here, so that noobs recognize those immediately, and may see the value of those posters quicker in replies to new users quests for help.
If you want a list I can help with that through PM if you would like.
This is absolutely AWESOME!!!! Great job!!!
Sticky!!
Click to expand...
Click to collapse
Ah, great suggestion! I'll update the OP with this. Would you mind helping me out with a list? I'd be much appreciative. I tried to cover all the "basics" and am still running things through my thinker to make this as comprehensive as possible. Thanks Jim!
Sent from my SAMSUNG-SGH-I747 using xda premium
Good for everyone
I think everyone should be encouraged to read, including us senior members. We were all noob -er new users once, and I've seen more than a few senior members devolve into name calling and/or borderline posts in my short time in this forum as well as in other forums.
troycarpenter said:
I think everyone should be encouraged to read, including us senior members. We were all noob -er new users once, and I've seen more than a few senior members devolve into name calling and/or borderline posts in my short time in this forum as well as in other forums.
Click to expand...
Click to collapse
I can agree with this. We all get frustrated at times, irritated at others, and I myself have been inclusive to that. However, the simple things in life (such as the rules of this forum) are what keep us all from becoming a bunch of Mongoloids. It's true that recent events, though now becoming more of a minor speed bump in the rear view mirror, had many of us rather edgy. I'm sure I was one of them, and my apologies have been extended. Now, I'm just trying to make the forum a better place for us all, and for myself. Hopefully this will have some impact, if only just a small one...
Sent from my SAMSUNG-SGH-I747 using xda premium
I think I'm a pretty non-noobish new member lol
Sent from my locked MB865 on Ice Cream Sandwich.
Thanks for the great write up as usual. Consider yourself nominated and highly recommended for recognized contributor status.
If you agree with this put in a good word to our mods for Apex_Strider.
You should see if xda has any portal writing positions open. you would be great
lkrasner said:
Thanks for the great write up as usual. Consider yourself nominated and highly recommended for recognized contributor status.
If you agree with this put in a good word to our mods for Apex_Strider.
You should see if xda has any portal writing positions open. you would be great
Click to expand...
Click to collapse
+1 cant agree more..
Sent from my MB865 using xda app-developers app
lkrasner said:
Thanks for the great write up as usual. Consider yourself nominated and highly recommended for recognized contributor status.
If you agree with this put in a good word to our mods for Apex_Strider.
You should see if xda has any portal writing positions open. you would be great
Click to expand...
Click to collapse
Thanks, lkrasner! I appreciate that, and would be quite the honor and privilege to be a Recognized Contributor for the Atrix 2 community. And many thanks to Jim, and the others who have recommended me to our moderators as well, along anyone else who does so. You guys are great, and this is an awesome community here.
Sent from my SAMSUNG-SGH-I747 using xda premium
Lol I just noticed I'm a Senior Member? I thought I was still junior. Always on Mobile.
Great read. Everybody should follow these rules and it should be stickied!
Sent from my locked MB865 on Ice Cream Sandwich.
DemosZevasa said:
Lol I just noticed I'm a Senior Member? I thought I was still junior. Always on Mobile.
Great read. Everybody should follow these rules and it should be stickied!
Sent from my locked MB865 on Ice Cream Sandwich.
Click to expand...
Click to collapse
Well, congratulations on the ranking up! I'm going to be adding a "Get To Know Your Community" sub-section to the OP, inclusive to that will be a list of Moderators, Developers, and Senior Members, so as to be easily recognizable for new members. Your name can now be supplementary to said list...
Sent from my SAMSUNG-SGH-I747 using xda premium
Apex_Strider said:
...Reading Is Invaluable, Searching Is Imperative...
Click to expand...
Click to collapse
Perhaps the site should fix its search functionality. Currently, search does not honor quotes. So searching for "Encrypted APK" returns the phone book - everything with "encrypted" or "apk" (and not the union), when in realitly there are less than 3 threads on the topic.
Awe, I'm on the senior list. Thanks mate.
Sent from my MB865 using xda premium
Fall of Enosis said:
Awe, I'm on the senior list. Thanks mate.
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
Not just on the Senior Member list, but "key" Seniors list (paragraph just above explains). This, hopefully will help n00bs and nons to acknowledge the more prevalent ones.
Sent from my SAMSUNG-SGH-I747 Anti-Motorola Ballistic Missile
Fall of Enosis said:
Awe, I'm on the senior list. Thanks mate.
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
and i'm not *sniff*
First off, this is meant to be constructive criticism; I use Synergy ROM and look forward to flashing nightlies. My only issue is with the changelog. I'm sure many others would agree that the lack of any detail for each commit/build is a real turn off. This forum is for power users, and while a few words describing changes may suffice for some persons, detailed technical descriptions for each change would only serve to benefit this ROM's reputation and rate of adoption. It's simply good development practice to use detailed comments.
b0bj0e said:
First off, this is meant to be constructive criticism; I use Synergy ROM and look forward to flashing nightlies. My only issue is with the changelog. I'm sure many others would agree that the lack of any detail for each commit/build is a real turn off. This forum is for power users, and while a few words describing changes may suffice for some persons, detailed technical descriptions for each change would only serve to benefit this ROM's reputation and rate of adoption. It's simply good development practice to use detailed comments.
Click to expand...
Click to collapse
Well, first, these guys are doing this in their off time and are busy with the actual developing of their ROM....Second the CM10 changelog isn't much more detailed at all... granted they provide the code that's been changed but that doesn't do much for the every day flasher, only for other developers. It's nothing new is all Im getting too
I would say most if not all the commits shown are pretty detailed or detailed enough to be understood. Some of them are just minor little tweaks that would thrown into the category of "Speed improvements/tweaks" or "Tons more tweaks and enhancements" but with the change log you get to see what exactly is being added and when its added. That's a lot more than other roms give you.
they vary
I would agree with everyone in this thread so far
Some of the updates have been vague or couched in terms that many wouldn't understand. The developers are doing this on their own time and as a hobby (though they do get some donations - not really a commercial enterprise though). Most of the update descriptions are enough to get the message across and are certainly more than some developers give. Even the apps in Google Play have some vague "What's new" lines at times (if any).
That said, I think Eschelon has improved a bit, or at least is a bit more conscious of the need for clearer update info at times. The one that really stood out for me was "Revision 60: Volume hack" which raised a bunch of questions on the Synergy thread. With R68 that hack was removed as it caused some problems. With that update there was a clearer note "Revision 68: Remove 10 step volume hack".
I think that without writing a paragraph describing the feature as existed, the changes, and the resulting functionality, you will never satisfy everyone. Most people running the ROM are knowledgeable enough to get the meaning of short notes. The new users probably won't, but then it might be a good learning experience for them.
The only thing that might really help is starting a Synergy thread in the FAQ section (if there isn't one already) and pointing new users there to ask their questions (as users with less than 10 posts can't post to the Synergy ROM thread directly).
b0bj0e said:
First off, this is meant to be constructive criticism; I use Synergy ROM and look forward to flashing nightlies. My only issue is with the changelog. I'm sure many others would agree that the lack of any detail for each commit/build is a real turn off. This forum is for power users, and while a few words describing changes may suffice for some persons, detailed technical descriptions for each change would only serve to benefit this ROM's reputation and rate of adoption. It's simply good development practice to use detailed comments.
Click to expand...
Click to collapse
I think that synergy's changelog gives you much better info than most. There are details and there are too many details. Giving technical descriptions of changes opens the door for every person to start picking apart each and every change.
I think the amount of detail in synergy's changelog is spot-on.
While the changelog can be vague, it seems like most of the unclear commits end up getting discussed in the thread anyway. Making the commits a full sentence or so would nice, but it's pretty low on my wishlist, personally. On a side note, this discussion would probably be more appropriately held in the ROM thread itself.
I've tested most things that i use day to day without any issues.
Pete7ate said:
I've tested most things that i use day to day without any issues.
Click to expand...
Click to collapse
Overall I think the info given is acceptable, what I do not like is that I am flashing so many different things that I can forget what build I was on or liked. The "latest build here" link does just as it says (which inherently should be a good thing), but only lists the most current build for download unlike CM that has all recent builds there with description options on the same page. I actually downloaded and flashed r68 twice thinking I was adding the next nightly!
Also on a similar note, what is the smaller zip file that is posted under the larger most current build? Is that a flashable add on that has the most recent changes in a smaller file form? Unclear on that.
annoyingduck said:
Overall I think the info given is acceptable, what I do not like is that I am flashing so many different things that I can forget what build I was on or liked. The "latest build here" link does just as it says (which inherently should be a good thing), but only lists the most current build for download unlike CM that has all recent builds there with description options on the same page. I actually downloaded and flashed r68 twice thinking I was adding the next nightly!
Also on a similar note, what is the smaller zip file that is posted under the larger most current build? Is that a flashable add on that has the most recent changes in a smaller file form? Unclear on that.
Click to expand...
Click to collapse
You can click the "Old" link on the download page for the latest nightly and you will get a listing of all the nightly builds. The smaller zip is a MD5 key which the TWRP recovery uses to verify the ROM file to make sure it downloaded properly before flashing it to your phone.
Thanks for the info, as I have only used CWM and have not run into that before in my use. I really got to read up on TWRP and play around with it, from what I have read it seams like an overall better recovery with more options and UI.
annoyingduck said:
Thanks for the info, as I have only used CWM and have not run into that before in my use. I really got to read up on TWRP and play around with it, from what I have read it seams like an overall better recovery with more options and UI.
Click to expand...
Click to collapse
I really like TWRP over CWM, especially for the MD5 feature. I use this most when I download the ROM's directly from my phone. I don't really trust the phone's browser to download the file correctly every time (have had halting issues in the past).