Database Info

Possible new XDA feature set? Configuration Profiles per phone? (Ex: my T-mob Wing)

In my sigfile below, you can see what I am currently running on my T-Mobile Wing.
The XDA site, for a long time, has been incredible in terms of specific app development, ROMs, etc. But I am now looking for "the next step": Total configuration recommendations: specific recs on which apps to use together with which ROMs on a given device, to achieve a user's most important usability functions and requirements.
I am going to layout the current issues I have been having problems with, mention my priority requirements, and I'm seeking recs on a smart configuration suite that begins with the ROM, includes recs on the overall interface and app launcher, down to specific APP recommendations to best meet my needs.
I think it would be great to eventually create, for all phone models, a series of consumer-end-user "Configuration Profiles", so right now, this is a first request: Help me optimize my T-Mobile Wing for how I want to use it.
=================================
My current configuration:
ROM: OpenTouch 6.5 by ttran001
INTERFACE & APPLICATION LAUNCHER: iFonz 1.1.2 by ssj5trunks
BASIC PHONECALL FUNCTIONS:supbro's iDialer + iContact (via larna)
SOFT KEYBOARD: PCM Keyboard by tene w/ iPhone theme by 2manyphones /
PRIMARY BROWSER: Opera Mini (strengths: Speed, lightweight. Weakness: data input is 2-step process; no copy & paste of web content)
SECONDARY BROWSERS: Opera Mobile (but for some reason the SIP is always overriding my preference, and going back to Windows soft keyboard). Skyfire (great for Youtube; lacks setting your own startpage URL), NetFront (I think their zoom/context scroller is fantastic)
MUSIC PLAYER: A_C's s2p
VIDEO PLAYER: for YouTube videos I use Skyfire Browser; otherwise YouTubePlay by milesmowbray
PHOTO VIEWER/EDITOR/SLIDESHOW A_C's s2v and HTC Album
FILE EXPLORER: Total Commander (has drag & drop!)
==============================
I am having compatibility problems, and I can't seem to troubleshoot the conflict sources. So it's time for a new ROM install, and rebuild my suite of apps. I'm hoping I can get a few recs on ROMS, application launchers, dialers.
USABILITY REQUIREMENTS: I am a power user, but not a techie. I currently have been using iFonz, have liked it a lot. Large target areas for finger navigation is very impt to me, especially when driving. Any of the basic windows soft key areas, scrollbars, OK button, Top-bar icons are not big enough, creating for me constant flow of mistakes and "stalls" in completing just the baseline functions of "Speakerphone On/Off", Hide Keypad/Show keypad etc.
If I had my way I would never have to touch any aspect of the Windows Mobile Interface.. but alas, that is not yet a reality. But getting closer day by day, example: supbro just today released a "green button" app that ties his iDialer app to the windows default dialer. A major breakthrough in usability.
What's Impt to me and Not Impt to me: (for Recommendations' sake):
NOT IMPT: I never run games, don't care. Weather is nice, but not impt. SMS and MMS are lo priority for me, I rarely use them.
MOST IMPT:
1. Basic phone functions, that allow me to take the phone out of my pocket and not end up accidentally ending the call before even getting the phone to my ear. Similarly, not having something accidentally trigger DIALING A FRIEND's NUMBER, or last redial. Big large phone dialpad, with large phone number display, bullet-proof "speakerphone on/off", bullet-proof "SAVE TO CONTACTS" without all the windows mobile backflips of "select Save to Contacts" then do I press "NEW CONTACT" or what? Just terrible usability design. Easy to find REDIAL.
2. Contacts: Contact manager with THUMBNAIL PHOTOS list, jump to alphabet letter, LARGE target area for finger to tap-and-dial in 1-step, not going to a detail screen to select WHICH number, or do I want to send email or SMS.
3. MP3 player: big obvious target area for volume control, and timeline slider, next song, etc. Integration with hard keys for next song, pause, mute. (S2u2 already does this, but there are still some squirrely problems, which create that dreaded problem of wanting to turn it off asap but no, gotta do backflips to get to the interface.)
4. CLOSE ALL APPS: since the Wing has the crappy old processor of its predecessor (MDA), and limited RAM, there are always times when apps lock up, and you just want to close everthing
5. one-click WIFI ON/OFF -- I don't want to go through some cumbersome Communication Manager. When I get home to my network, or I am at a Starbucks and want to use Tmobile Hotspot, it should be a no-brainer: wifi is turned on, all available networks show by default, all in one step. Just as if I take my Macbook Pro to a cafe, click one icon, see all networks. To me it would be even greater if, when I was at a Tmobile Hotspot, 1 click would *turn on wifi, *launch Tmobile's hotspot utility
6. Voice Command, Handwriting SIP, and a bunch of other things.
=======================
I'm hoping someone will take me up on this big-picture request. Thank you

(reserved for photos/ videos of my current configuration)
saving this space to come back and add some photos and videos that demonstrate the problems I want to solve.

You've been a member long enough to know that "Recommend a Rom" threads usually get closed.
You've done a good job listing what exactly you're looking for but still the title is along the lines of a noobie swooping in and asking for the best rom.
Where you do differ is that you've obviously put a lot of thought into what you're looking for but alas the thread title doesnt accurately reflect the depth of your post.
Honestly this sounds like the idea that launched a project. The question is will you step up and coordinate the project?
If so I would recommend you retitle this thread and take the concept to the next step.

kyphur said:
You've been a member long enough to know that "Recommend a Rom" threads usually get closed.
Click to expand...
Click to collapse
Hey thanks for replying, kyphur. Honestly, I actually didn't know that... but hold on -- there are 2 reasons why is this. So I will explain, because my intention is not to break rules & protocols -- i have too much respect for this community:
(a) I'm actually not a regular here to see those patterns. I started with an MDA, learned how to use XDA-dev site to try to find answers, went through my initiation of asking dumb questions, getting slapped to "use search, damnit", found my way to understanding the cultuyre and rules.. but even after a year I was too scared to ever try a mod on my MDA. And it wasn't til I got my Wing that I finally jumped in to do the whole shebang -- from hardSPL, to ROM installation, etc. With great help from various members here, like papamopps. And once I get something working, I am not frequenting the site, other than for subscribed threads to Apps that are still in development that I am using -- like for example iContact and iDialer. Because I really rely upon my phone for work, and once it's doing what I need it to do, I generally am not cruising looking for "the next great thing".
I want to add, though, that inasmuch as it may sound as though I am merely a taker and not a giver, the way that I give is by donating to the app developers and ROM chefs whose products I have used. And if you ask A_C and ssj5trunks, for example, my donations are large -- as my best way to compensate back. Also, I volunteer to host websites, and for example A_C hosts part of his new site www.A2-s2.com with me -- and I am happy to be of service that way.
(b) The second reason I didn't explicitly know that was a rule here is because I tend to mostly be in the WING/Herald "silo" -- and there, the user Pureskillz is known for doing thorough Reviews of Roms -- which are amazing -- and I have asked before in threads in that section for recs on which ROM might be fastest for me to use to run iFonz, and I have gotten really helpful replies.
This is all quite different from a newbie parachuting in to say "hey guys, what should I use on my Wing, i want to have an iphone type of phone". So thank you for letting me know - i honestly did not know this was verboten
You've done a good job listing what exactly you're looking for but still the title is along the lines of a noobie swooping in and asking for the best rom.
Where you do differ is that you've obviously put a lot of thought into what you're looking for but alas the thread title doesnt accurately reflect the depth of your post.
Click to expand...
Click to collapse
Gotcha. Okay, I will go rename it: How would this sound?
Request: Suggested Apps for configuring my T-Mobile Wing for specific functions
I don't know if that's any better... but
Honestly this sounds like the idea that launched a project. The question is will you step up and coordinate the project?
Click to expand...
Click to collapse
Actually, this is exactly part of what I want to do, but on a "clean page" so as to give newbies an easier pathway IN to understanding what is even AVAILABLE to them. But my interest is in mainstream users, not so much in the tricked-out overclocked custom registry code-writing userbase. Because to me, the whole site in its entirety is geared for those users.
So yes, I am wanting to create a website that places a mainstream-friendly "front end" to this amazing knowledge-base. All links would be attributed and linked to the actual XDA threads. But I want to provide capsule summaries that help users understand where they are being sent, and how they should approach a "Release" thread... What they can expect, the protocols for asking for help, etc.
So yes, I have given a lot of thought to what I think, as a Usability and Information Designer, is a huge gap between mainstream phione users who are finding out about XDA for first time -- largely thru YouTube videos which kinda blow their minds -- because its functionality is so beyond what is marketed to them as possible via carriers like (in USA) T-Mobile, AT&T, etc -- and the ability to comprehend this site -- which is gargantuan in nature, and a maze of complexity for a newbie.
Let me give a very tangible example: I would bet you that probably less than 1% of the users of Windows Mobile in the USA, who are using for example, the T-Mobile Wing, have any idea at all that they can get for free GPS location tracking on their phones, right now, today, just by using Google Maps. It's not ever presented to users. So you have this huge population of people who have a truly awesome function available for their phones right now -- that they have no idea is the case.
I was just discussing this in San Francisco the other day with the Product Development Manager at Google for the Google Maps product line.
So: re stepping up to the plate: one of the parts I have in mind is to help facilitate the assembly of -- the creation of -- these "Configuration Profiles" which would seek to create common function-sets that certain types of users would likely say "YES, THAT ONE, that's matches the kinds of things I am looking for.
So, with that in mind, I wanted to try it out here, and see if this would be something users here would support as being worthwhile, or more of just a pain in the ass. And, the timing is such that I really have had more and more problems having my Wing function effectively, and I know from my own experiences that the selection of a ROM is really quite critical to building the suite of apps & functionality I desire.
If so I would recommend you retitle this thread and take the concept to the next step.
Click to expand...
Click to collapse
I am fine with your deleting the thread if it really isn't appropriate for the site. I was looking very carefully for where to post this, and this seemed like the best place. What are your thoughts?
thank you.

@ quicksite
The concept sounds great. I agree with you in that many people want functionality but who dont have the technical knowledge, (or want it initially) but who wish to maximise their devices usefulness. They also may not want to risk damaging something they have just paid £500 for. How many times have i had my friends come upto me and say, how did you do that? can i have it? can you do it for me? haha....
Whilst some may say this is not in the spirit of xda as one should not venture into the depths of winmo without technical knowledge, i believe it adheres to its basic principles and that xda should continue in its evolvement (sorry my spelling is crap today); the more the members the greater the knowledge.
Whilst i only have a Polaris and Prophet, i would be interested in this dev project as it could encompass all devices. It would benefit xda in that noobies who dont or cant get to grasp with the technicalities have somewhere (one place) to "glorify" their device. I think once the new members have blinged their device, their interest and curiousity expands... "mm i wonder what else i can do". THis leads to further reading and learning and such new blood and knowledge can only be of benefit.
Count me in.

@quick site
Sounds like you want to either get into cooking your own rom, or should grab an ultralite rom and install everything you want.
You may want to try task facade for a task manager. everything pops up with a large screenshot and to close apps you just have to long hold them.
You can set task facade to a hardbutton (or if your hardbuttons are all full you can use hbutton which allows you to map several programs to one key)

An introductory video example: to orient a new user
timmymarsh said:
@ quicksite
The concept sounds great. I agree with you in that many people want functionality but who dont have the technical knowledge, (or want it initially) but who wish to maximise their devices usefulness. They also may not want to risk damaging something they have just paid £500 for. How many times have i had my friends come upto me and say, how did you do that? can i have it? can you do it for me? haha....
Click to expand...
Click to collapse
Thanks for replying. ... Here's the video I recently added to YouTube just to show in a non-technical way WHAT one could do on their T-Mobile Wing.
http://www.youtube.com/watch?v=ZSc0Qz8tf_c
As I told the Google Maps Mobile product manager, I don't think a tiny fraction of people know about the GPS functioning just via Google Maps usage. This video would not appeal to the vast majority of XDA Members, however, because it is meant to be a soft-introduction to "outsiders", vs an information-packed walk-through or installation guide.
{
"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"
}
http://www.youtube.com/watch?v=ZSc0Qz8tf_c
Whilst some may say this is not in the spirit of xda as one should not venture into the depths of winmo without technical knowledge, i believe it adheres to its basic principles and that xda should continue in its evolvement (sorry my spelling is crap today); the more the members the greater the knowledge.
Click to expand...
Click to collapse
My area of professional expertise is usability design, consumer content design, information design. I spent over a year getting the feel of XDA site before I jumped in to try to mod my Wing. I learned the culture, realized there were LOTS of preliminary things which I had no idea about, and had to first assemble a macro knowledge set up: what is Hardl SPL, what is an RUU, what is a radio rom, does a ROM have Windows Mobile OS in it? If so, Is it a legal license? what does "brick my phone" mean? ... I went to the Herald wiki, I saw guides for noobs to read, I read them, but then circular questions like: "Be sure to read XXXXX's great guide to flashing"... So I read this guide, many of them, and they'll say "be sure to make sure whether you have version x or version y; if X, never Hard SPL, if Y, it's okay; then a thread "Hard SPL working on WING!", then more guides how to Hard SPL your phone. Then you're supposed to pick a ROM.
If you ask for advice, you're told "start reading; everyone has different needs". SO you read up, use search, end up on a thread you think applies to ROMS for your phone, only to be 12 pages into the thread before you grasp the concept that this thread and this ROM is only for an HTC Himalaya. ANd it's completely irrelevant to my quest.
But senior people here would say "It's obvious, you were in the wrong area; look at the wiki, it has a list of phones, only search for ROMS for that phone"... but some ROMS are for many phones. Anyone, this is nothing new to those experienced with XDA. And I understand the frustration of senior members who keep posting stickies to help Newbies prep properly and not just dive in to ask "how do I get iphone on by HTC Touch?" etc.
But as can be seen very clearly from THIS SEMINAL THREAD, "Let People Ask Whatever They Like", that there is a culture "war" developing on XDA between those who feel adamantly: this site is for tinkerers, and if you've come just to get "kewl" stuff for your phone, you're in the wrong place. While other senior members are adamantly in the other corner of "why not help people? So what if they ask stupid questions? Just move on, ignore them, you don't need to chastise everyone."
Whilst i only have a Polaris and Prophet, i would be interested in this dev project as it could encompass all devices. It would benefit xda in that noobies who dont or cant get to grasp with the technicalities have somewhere (one place) to "glorify" their device. I think once the new members have blinged their device, their interest and curiousity expands... "mm i wonder what else i can do". THis leads to further reading and learning and such new blood and knowledge can only be of benefit.
Count me in.
Click to expand...
Click to collapse
This is nice to hear. The biggest problem with any knowledge base is in formation design. Despite the wiki, despite the sticky threads, despite the SIG LINES with links to Help Guides, despite the warnings, it is my professional opinion that this spectacular knowledge-base called XDA-Developers, is like a big tinker-toy project with new arms constantly being added, and nodes that even everyday users don't even know about, because they are specialized areas for particular phones etc. And now there is a whole new initiative ( A GREAT ONE!) to develop for the Android platform.
To me, creating some landing pages that help orient newcomers without overloading them with a huge maze of a dense site -- helps everyone:
* for sure helps the newbie
* helps the senior members (who will see yet another 100 threads open per day with same old new questions) from having to constantly look at "101" type questions.
* helps the software authors in getting donations for their works by more easily shuttling newcomers to the specific kinds of apps they have been looking for.
I think we are seeing a crossroads right now, with the launch of the Apple Apps store, the Android Apps store, Blackberry's store, and Windows' expected entry (what's it called, Skyapps ?)... Critical mass has now been reached in the marketplace for owners of toucscreen devices to now embrace specialized apps and functions that fit specific needs, and manufacturers and carriers are finally figuring this out. XDA sits is a very unusual place amongst all this, given the open-source spirited "knowledge-share & donate" philosophy of the site. I think there will be longtime veteran members here who will not be happy with influxes of even MORE news trying to get the latest & greatest. I just believe the dam has broken, and it might be good to filter newcomers and orient them (my interest), vs having them flood in and irritate the **** out of the people who built this community...
Sorry for the lenghts of these posts. I'm just wanting to be clear.

joel2009 said:
@quick site
Sounds like you want to either get into cooking your own rom, or should grab an ultralite rom and install everything you want.
Click to expand...
Click to collapse
Thanks. Yes, that's what I have done to date. I started with a PapaMopps ROM, then moved to an OpenTouch ROM, and now am trying to consider WHICH ultralite woud work best for my configuration. It's these snags like dialers that confound me. AND which topbar is overriding another -- for exmaple, when iFonz is in use, it overrides the top bar with access to windows start logo, etc.
You may want to try task facade for a task manager. everything pops up with a large screenshot and to close apps you just have to long hold them.
Click to expand...
Click to collapse
Thank you for the rec. i will search for Task Facade.
I also just found WkTask from a thread here at XDA -- and tried it out. Now THAT's what I'm looking for... but again, it's the conflcit with apps or interfaces that overlay that top bar so that it is not a constant.
You can set task facade to a hardbutton (or if your hardbuttons are all full you can use hbutton which allows you to map several programs to one key)
Click to expand...
Click to collapse
Ahh, I never new until now about Hbutton. That's exactly what I need! I will search for it too. I am guessing it is context sensitive -- and offers a different default action depending on which app is the one in use?
thanks very much.

@ quicksite
Assume you are going to set up your own site for this project or is this something you are going to do on xda? im interested in assisting in this in which ever direction you want this to go, so let me know and i will find some time and buy some more coffee....

I'm not sure quite what you want to achieve, but I think what you want is a less technical (i.e. suitable for normal people) way to access the information here.
This sub forum was brought about because it was decided that new users probably wouldn't have a huge technical knowledge, so it woul be better to let them ask about "what's x" somewhere where people want to help rather than hack. So in a sense, this sub forum goes part way to achieving that.

[GUIDE] How To Be A New Member, Not A NØØB

{
"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*

Custom/reliable rom/operating system

So I am going to post this here, because the development section is ferboten to people trying to offer useful suggestions. Geez, I hope this is the right section.
Let me set it up. ANDROID IS BASED ON THE LINUX KERNEL. Everything, and I mean everything after that fact becomes android and bloat. Given this as the basis of all things android, I have a simple set of guidelines that should be used to create a solid, reliable, bullet proof operating system for devices able to use the android operating system.
#1. Create the kernel boot section of the basic platform that supports the very basic hardware features, including touch screen, radios, power/charging/battery management, wifi, bluetooth, nearfield, audio, microphone, s-pen,etc. Basics only. Root access is standard and can be turnd on/off just like developwer functions. No special tricks or addon hoops to jump through.
#2 At this point STOP. Every single process or service to be run on the device from this point forward should be able to be individually selectable - or not. Yes, I understand that individual services or apps may have dependancies to other processes and that thouse need to be functional in order for a particular app to work. That is why, each additional service or app must list the dependencies and in the selection process, the installion will be required to verify you have the proper services installed and functioning, if not to list them and allow you to make the decision to proceed. Viola, we have NO MORE BLOAT WARE.
#3 Make selecting additional services/apps selection process a menu driven, tag selectable process. Make the unselection process smart to verify and identify the other apps dependant on the item you are killing/removing.
#4 Allow a built in snapshot option to capture the entire system as you have customized it for yourself and allow it to be backed up to external memory with the ability to bring it back, AT WILL. With no big hassles.
Those 4 items are a good start. By themselves alone, it would put all of us in the drivers seat of controlling and living with our devices.
I am aware that such a system is not for everyone. It does require some basic technical understanding of the process. But for the vast majority of users, I am certain, that an a la carte system is far superior to the bloated monstrosities being forced down our devices.
I would appreciate any refinements to my suggestions.

The silence is deafening. It has been days. Kind of says something, don't you think?

I am so very happy (not) that these boards a compartmentalized to the point where you can't get through.
Pretty much a waste of my valuable time, especially considering the fact that if my suggestions where applied, people would be clamoring for an installation with those features. I guess there is not much true "developer" in xdadevelopers anymore.
Funny guys, with the pay to remove ads spam here. Really? Why? For what.
I leave here disappointed. Not angry. Just sad.

I'm not a developer so I have nothing valuable to contribute to your suggestions in your original post but I can offer an observation regarding your perception of the level of contribution to your thread and that is the fact that is particular area of the forums probably isn't the ideal spot to have a discussion such as this. You figured that out already so sure you can call me Capt. Obvious if you wish but I'm just pointing out that yes the forums are compartmentalized (as you've stated) in such a way that development for each device is separated out. This development is centered around AOSP based ROMs or "stock" ROMs (using manufacturer released source) so if you're looking to have higher level discussions about what AOSP should look like then deep down at this device specific level probably isn't where you want to be. So there's that . . . then there's the fact that for this particular device you can basically hear a pin drop in the sub-forums as it is since nothing much is going on by way of development.
Where specifically such a discussion would see more input I'm not sure, perhaps the main general discussion section?

Thank you for your sobering reply. I get frustrated. Already had my post bounced out of "wrong" forum while trying to speak directly to "developers" (i wanted air quotes because the term does not accuratly describe its target) So I tried this. The note pro 12.0 is still the best hardware giving the ipad a run for its money. The problem its monkeyshines kiddie software running it, or not running, or barely running it. ANDROID, indian word for crappy wannabe software, developed by clueless kids.
Again, thanks for the gentle nudge. I appreciate someone willing to conduct a conversation

Are you looking for an Ubuntu or SUSE type of setup?
I think what you are looking for is similar to apt-get type of installs, I could be wrong of course. This might be helpful for many "users". I think one of the barriers is that there are slight differences between the models of tablets, and creating the logic to put in for the sub-dependencies might prove problematic. You might get more answers to this possibility by asking one of the developers directly and sharing with them. Not a developer myself.

An Issue with a ROM, a Kernel or an Application, etc.? A Few Things to Consider.

Background: Following some threads at XDA I’ve pretty early realised that quite a few bug reports, requests, and questions in regard to ROMs, kernels or applications are raised without sufficient information to allow (Recognised) Developers (RD), Recognised Contributors (RC), or other members to easily provide solid answers and recommendations or a possible fix. Everybody should remember even a highly professional member cannot read your mind.
Initially, I opened a thread with the same topic in regard to the device I use: The Samsung SGS3 LTE (GT-i9305). It’s accessible . If you already know that thread, I hope you don’t mind that I mostly copied and pasted.
Purpose: To provide some recommendations how to best phrase a request for support to possible ROM/kernel/applications issues in order to receive the most suitable answer and solution.
General recommendations:
Please read the XDA Forum Rules provided by @MikeChannon; a MUST READ for everybody who intends to post on XDA. Other MUST READ's I certainly recommend to everybody who wants to "breathe" what I believe the spirit of XDA is, are the following posts:
Forum Etiquette by @TheByteSmasher,
http://forum.xda-developers.com/show...postcount=2441 by @zelendel, and last but not least
http://forum.xda-developers.com/show...9&postcount=44 by @kyphur
Remember: Before you flash anything take a NANDROID backup or ensure you've an up-to-date one!
If you don’t know yet what’s hidden behind some of the expressions mentioned in the title of the following linked thread, just check it out: What is? Boot loader, custom ROMs, CWM, modem, kernel, flashing, rooting, ADB, baseband?? by @esimon311. Thanks to esimon311 for this great overview.
Guidance for useful modifications regarding some parts of your kernel can be obtained here: [GUIDE] Most up to date guide on CPU governors, I/O schedulers and more! by @Saber. Thanks to Saber for this great guide.
Before you post your issue or request, reboot at least once and try to replicate your problem. If it doesn't persist any longer the reboot might already have been the solution.
Read, read, and read again, read the OP (first post of each thread) and scan the respective thread. Use the search function of XDA. Remember: Make use of your friend – your favourite web-search engine. It does mean you have to read and study but I've no doubt you don't mind to do that for your device. Maybe, you'll find your required answer without having to post something.
A lot of OPs already contain hints how to solve commonly known issues.
Before you post in a ROM development thread, be sure not to run a custom kernel or Xposed. In case you use the latter, disable all Xposed modules and check if your issue still persists. Anyhow, if you’re using custom kernel or Xposed and you're convinced the issue is ROM related, you might post but mention the kernel and/or Xposed.
Last but not least: Don't ask what e.g. the best ROM, kernel or app is! All of them available at xda are great; however, each one of them has its different specification, capabilities, and pro's and con's depend on personal desire and expectations. The best one for you is the one, which meets your desire and expectation.
Before you post in a thread:
If you want to sell your car you probably achieve the better bargain the better (or more suitable) the portal is, in which you're offering it. I'm convinced you won't offer a car with the star at the bonnet on a webside covering military motorbikes.
Same applies to XDA. The more precise your post is going to fit into a thread or forum the faster and most likely better reply you're going to receive.
For this reason, I suggest you to exactly identify, in which of the 1000 fora or probably millions of threads to post. Prior to posting take you're time and study the following excellent guides and recommendations - all by @sd_shadow - to find the best and most reasonable place for your post.
[Guide] How and Where to Ask a Question on XDA
"Have Question about Posting?" in this post
[Index] of Help Threads (and Template)
When you post in a thread:
If available, post questions in Q&A threads (some threads have a dedicated Q&A section besides its development one) instead of the development thread. But if you have a solid bug report (never reported before, and your post is complying to all the required criteria provided below including all necessary info), you can post in a development thread.
Don't make a RD, RC or anybody else to read your mind. Don't have them to make assumptions – as soon as an assumption fails the whole solution is going to become void.
Please post your issue or request by using the English language as mentioned in the XDA rules to allow everybody to understand the post and hopefully to contribute, or at least to learn out of it. Don't be afraid if English isn't your native tongue – that's certainly the case for most of the xda users. A language barrier isn't an issue at XDA – as long as we all at least try to use the English language. Even if your English skills aren't too developed just use simple wording or a reasonable translator tool; nobody is going to blame you; however, try to be as precise and unambiguous as possible.
Always run a logging tool to be able to augment your post by a log file. Add the log as an attachment to your post or upload it into the cloud and provide the link in your post. Do not include the log into the text phrase of your post in order not to spam the thread. It doesn't matter, which logging tool you use but familiarise yourself with its use and where it saves the log. I'm personally e.g. using "Catlog" that saves logs to the internal storage. Alternatively use adb commands. Here is a [Tutorial] How To Logcat by @paxChristos. Thanks to paxChristos for this great tutorial.
If you're running (Ed)Xposed uninstall it, and take the log again (while Xposed is running, the log even states that it's useless because of Xposed).
Take screenshot(s) and attach them/it to your post. Don’t insert it/them into the “text box”. Before you take a screenshot, change your system language to English to allow everybody to understand the content of the screen.
Always provide exact and precise information about your issue. Write a description and, if possible, steps to allow for reproduction.
Unless the issue is only related to an application always provide exact and precise information about your device, the ROM, the kernel, your recovery, and specify the versions of the latter three. If you have issues with a theme, information regarding your ROM is certainly required. Occasionally information about your modem (or even bootloader) might also be helpful e.g. if you've problems with the RIL, mobile network or making phone calls. If you're on F2FS please mention.
If your issue or problem occurred immediately after you flashed a ROM* or kernel* or installed an application (incl. themes), please describe your installation procedure (clean, dirty, or describe when you wiped and/or formatted what).
*Please provide information, from which ROM or kernel you came.
Credits and many thanks to @woodman and @alias_ z3d in helping me to set up this OP.

First!!!
Perfect noc.jfcbs! After the i930x world, now the general version of your nice thread. I'm sure it will be a great addition to the XDA community. I hope a lot of members will read and remember your advices.

An Issue with a ROM, a Kernel or an Application, etc.? A Few Things to Consider.

Background: Following some threads at XDA I’ve pretty early realised that quite a few bug reports, requests, and questions in regard to ROMs, kernels or applications are raised without sufficient information to allow (Recognised) Developers (RD), Recognised Contributors (RC), or other members to easily provide solid answers and recommendations or a possible fix. Everybody should remember even a highly professional member cannot read your mind.
Initially, I opened a thread with the same topic in regard to the device I use: The Samsung SGS3 LTE (GT-i9305). It’s accessible . If you already know that thread, I hope you don’t mind that I mostly copied and pasted.
Purpose: To provide some recommendations how to best phrase a request for support to possible ROM/kernel/applications issues in order to receive the most suitable answer and solution.
General recommendations:
Please read the XDA Forum Rules provided by @MikeChannon; a MUST READ for everybody who intends to post on XDA. Other MUST READ's I certainly recommend to everybody who wants to "breathe" what I believe the spirit of XDA is, are the following posts:
Forum Etiquette by @TheByteSmasher,
http://forum.xda-developers.com/show...postcount=2441 by @zelendel, and last but not least
http://forum.xda-developers.com/show...9&postcount=44 by @kyphur
Remember: Before you flash anything take a NANDROID backup or ensure you've an up-to-date one!
If you don’t know yet what’s hidden behind some of the expressions mentioned in the title of the following linked thread, just check it out: What is? Boot loader, custom ROMs, CWM, modem, kernel, flashing, rooting, ADB, baseband?? by @esimon311. Thanks to esimon311 for this great overview.
Guidance for useful modifications regarding some parts of your kernel can be obtained here: [GUIDE] Most up to date guide on CPU governors, I/O schedulers and more! by @Saber. Thanks to Saber for this great guide.
Before you post your issue or request, reboot at least once and try to replicate your problem. If it doesn't persist any longer the reboot might already have been the solution.
Read, read, and read again, read the OP (first post of each thread) and scan the respective thread. Use the search function of XDA. Remember: Make use of your friend – your favourite web-search engine. It does mean you have to read and study but I've no doubt you don't mind to do that for your device. Maybe, you'll find your required answer without having to post something.
A lot of OPs already contain hints how to solve commonly known issues.
Before you post in a ROM development thread, be sure not to run a custom kernel or Xposed. In case you use the latter, disable all Xposed modules and check if your issue still persists. Anyhow, if you’re using custom kernel or Xposed and you're convinced the issue is ROM related, you might post but mention the kernel and/or Xposed.
Last but not least: Don't ask what e.g. the best ROM, kernel or app is! All of them available at xda are great; however, each one of them has its different specification, capabilities, and pro's and con's depend on personal desire and expectations. The best one for you is the one, which meets your desire and expectation.
Before you post in a thread:
If you want to sell your car you probably achieve the better bargain the better (or more suitable) the portal is, in which you're offering it. I'm convinced you won't offer a car with the star at the bonnet on a webside covering military motorbikes.
Same applies to XDA. The more precise your post is going to fit into a thread or forum the faster and most likely better reply you're going to receive.
For this reason, I suggest you to exactly identify, in which of the 1000 fora or probably millions of threads to post. Prior to posting take you're time and study the following excellent guides and recommendations - all by @sd_shadow - to find the best and most reasonable place for your post.
[Guide] How and Where to Ask a Question on XDA
"Have Question about Posting?" in this post
[Index] of Help Threads (and Template)
When you post in a thread:
If available, post questions in Q&A threads (some threads have a dedicated Q&A section besides its development one) instead of the development thread. But if you have a solid bug report (never reported before, and your post is complying to all the required criteria provided below including all necessary info), you can post in a development thread.
Don't make a RD, RC or anybody else to read your mind. Don't have them to make assumptions – as soon as an assumption fails the whole solution is going to become void.
Please post your issue or request by using the English language as mentioned in the XDA rules to allow everybody to understand the post and hopefully to contribute, or at least to learn out of it. Don't be afraid if English isn't your native tongue – that's certainly the case for most of the xda users. A language barrier isn't an issue at XDA – as long as we all at least try to use the English language. Even if your English skills aren't too developed just use simple wording or a reasonable translator tool; nobody is going to blame you; however, try to be as precise and unambiguous as possible.
Always run a logging tool to be able to augment your post by a log file. Add the log as an attachment to your post or upload it into the cloud and provide the link in your post. Do not include the log into the text phrase of your post in order not to spam the thread. It doesn't matter, which logging tool you use but familiarise yourself with its use and where it saves the log. I'm personally e.g. using "Catlog" that saves logs to the internal storage. Alternatively use adb commands. Here is a [Tutorial] How To Logcat by @paxChristos. Thanks to paxChristos for this great tutorial.
If you're running (Ed)Xposed uninstall it, and take the log again (while Xposed is running, the log even states that it's useless because of Xposed).
Take screenshot(s) and attach them/it to your post. Don’t insert it/them into the “text box”. Before you take a screenshot, change your system language to English to allow everybody to understand the content of the screen.
Always provide exact and precise information about your issue. Write a description and, if possible, steps to allow for reproduction.
Unless the issue is only related to an application always provide exact and precise information about your device, the ROM, the kernel, your recovery, and specify the versions of the latter three. If you have issues with a theme, information regarding your ROM is certainly required. Occasionally information about your modem (or even bootloader) might also be helpful e.g. if you've problems with the RIL, mobile network or making phone calls. If you're on F2FS please mention.
If your issue or problem occurred immediately after you flashed a ROM* or kernel* or installed an application (incl. themes), please describe your installation procedure (clean, dirty, or describe when you wiped and/or formatted what).
*Please provide information, from which ROM or kernel you came.
Credits and many thanks to @woodman and @alias_ z3d in helping me to set up this OP.

First!!!
Perfect noc.jfcbs! After the i930x world, now the general version of your nice thread. I'm sure it will be a great addition to the XDA community. I hope a lot of members will read and remember your advices.