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

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.

Related

I Will Post Your Question In The Dev Thread IF...

Thread closed.
Don't bother complaining about the 10-post rule here. I will request regular thread cleaning as necessary. This is not a thread you can use to build up your post count.
1. There are other constructive threads with that topic in the About xda-developers.com forum. I will happily debate you on the matter there.
--- Better alternative to postcount limit in development forums
--- A possible simple solution for Dev thread "Spam"
2. It is not going away because it is (mostly) for spam control.
Fallen Spartan said:
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.
Click to expand...
Click to collapse
- Fallen Spartan - Moderator Committee
Getting 10 quality posts is not that difficult and doesn't take that long if someone puts in a little effort. However, I understand if someone doesn't feel like they have time to do that.
That being said, I promise to post your question and post any answers received back from the appropriate ROM thread.........IF
You are asking something development related or some technical question about the ROM itself.
You are producing a mod for the ROM.
You want to enter a bug report.
That is what the development threads are supposed to be used for. ​
Other types of questions generally belong in the device Q&A (Question and Answer) forums. Not the dev threads. That is why there is no post count limit on the Q&A forums. If you really want the best device specific help, try reading the stickied guides in your devices Q&A forum, then post there if necessary.
Each one of these questions will be evaluated individually. If your question is uniquely ROM-related, I will ask it.
Your post must include:
1. A detailed device configuration: ROM, kernel, firmware, radio, mods, etc...etc...
---- This info should be in your signature
2. A list of things you have searched, read, done, and tried.
---- Expecting to come in here and get a quick freebie? Nothing in life is free, you have to do a little work here.
3. Terms you have searched for and where you searched.
---- Which forums? Which websites? Exact terms and different combinations of terms tried?
4. Your agreement that you have read ALL of the dev's initial posts in said dev thread. TWICE.
---- I mean read, not just skimmed over. Good devs put a lot of work into their first page posts and keep them updated, many times with FAQs and other helpful troubleshooting tips.
5. Your agreement that you have read the stickied guides in your devices General, Q&A, and Development forums.
---- Many people have put in countless hours of their personal time to enter in this knowledge for you to learn it and apply it successfully to your XDA experience and phone, and the mods have put them at the top of the subforum pages so you don't have to work to find them. Please don't waste their time or yours.
6. If you are having a problem, what exact steps brought you to the point you are at?
---- Remember, the more details you can give means that it is more likely your question will get answered correctly.
7. What steps have you tried to resolve the problem on your own?
---- See points 2. and 6. above.
8. What logs do you have?
---- See point 6. above. And this: [GUIDE] How to give constructive feedback to developers And this: [Tutorial] How to Logcat
9. The exact question you want to post
If you do these things I honestly believe that you will not need to post your question as it will already have been answered, but if not, I will enter your questions on any dev thread you want to post in but cannot post in, and post any and all answers received back here.
Thanks mate!
Also for the newbies: Any other question must go to Q&A section and not in here in General, wrong section threads will be moved or closed.
{
"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"
}
Sent from my sending thing (copyright by domini99 )
I have a 100Mbps download and upload speed, the newest MIUI release ("miui_INC_2.8.10") has been uploaded to quite a few foreign websites that only allow download speeds of up to around 22.5KB/s.
I've taken it upon myself to download the ROM file, upload it to my personal DropBox but also, more importantly, my personal file hosting server, here. (Link will be LIVE/ACTIVE in ~30 seconds from this post.)
Please post both of these links (note that they're the full URL, I'm not trying to get any money out of them, just trying to supply download links) in [THIS] thread.
DrXThirst said:
I have a 100Mbps download and upload speed, the newest MIUI release ("miui_INC_2.8.10") has been uploaded to quite a few foreign websites that only allow download speeds of up to around 22.5KB/s.
I've taken it upon myself to download the ROM file, upload it to my personal DropBox but also, more importantly, my personal file hosting server, here. (Link will be LIVE/ACTIVE in ~30 seconds from this post.)
Please post both of these links (note that they're the full URL, I'm not trying to get any money out of them, just trying to supply download links) in [THIS] thread.
Click to expand...
Click to collapse
Welcome, thank you. I want to be clear on what you are trying to do first. You are trying to be a mirror site, correct? I see that the OP there set up a mirror on DevHost a few days ago, but if you want to offer secondary mirrors then I can post there and ask for his permission.
Yes, I am trying to supply two North American server mirrors. The DevHost is a nice mirror, but still their bandwidth only allocates maybe 150KB/s per download.
The DropBox mirror supports up to, at least, 3.5MB/s. (Yes, MegaBytes) while I've downloaded at a full 12.5MB/s (100Mbps) from my personal hosting site.
Thank you.
EDIT: And as a.. "complimentary gift" of sorts for supplying these two mirrors (of great quality), would it at all be possible to remove my posting restrictions even though I have yet to reach my "10 quality posts"?
See, I don't visit the website often enough to bother with posting in Off-Topic forums, or "General Discussion." If you've noticed, I'm intelligent, and what I have to post is relevant, and most of the time useful, to the thread.
I've also been a member of some other forums for years, one which I will soon be "celebrating" my 10 year anniversary. I'm a developer of many Windows-based programs and I have before had fixes for some of the bugs for the ROMs posted here, but was aggravated that I could not post due to lack of post count and decided to just not post (not like I really had a choice.)
All I ask is that you consider my request.
Regards,
DrXThirst said:
Yes, I am trying to supply two North American server mirrors. The DevHost is a nice mirror, but still their bandwidth only allocates maybe 150KB/s per download.
The DropBox mirror supports up to, at least, 3.5MB/s. (Yes, MegaBytes) while I've downloaded at a full 12.5MB/s (100Mbps) from my personal hosting site.
Thank you.
EDIT: And as a.. "complimentary gift" of sorts for supplying these two mirrors (of great quality), would it at all be possible to remove my posting restrictions even though I have yet to reach my "10 quality posts"?
See, I don't visit the website often enough to bother with posting in Off-Topic forums, or "General Discussion." If you've noticed, I'm intelligent, and what I have to post is relevant, and most of the time useful, to the thread.
I've also been a member of some other forums for years, one which I will soon be "celebrating" my 10 year anniversary. I'm a developer of many Windows-based programs and I have before had fixes for some of the bugs for the ROMs posted here, but was aggravated that I could not post due to lack of post count and decided to just not post (not like I really had a choice.)
All I ask is that you consider my request.
Regards,
Click to expand...
Click to collapse
I will be happy to post this in the dev thread for you as long as the OP is fine with it, I appreciate you taking time to do that work of getting everything set up. I will write to him right now to ask and I will copy you on the PM so he knows exactly what we are requesting.
I wish I could assist but I do not have any power with regards to the posting restrictions, that would have to be done by one of the moderators. You can feel free to write to one of them, but at this point given that you are just 4 posts away I think their answer would be to suggest to post a few more times.
Update: PM is sent to the OP and you, hopefully he will reply back soon with a yes answer and I will post your links.
samsung galaxy sl i9003
samsung galaxy sl i9003 REMICS rom please tell them to fixed the link because i cant download the rom
thanks
alldjubs said:
samsung galaxy sl i9003 REMICS rom please tell them to fixed the link because i cant download the rom
thanks
Click to expand...
Click to collapse
A link to the specific ROM thread would be helpful. There are two RemICS ROMs there.
[ROM][PORT][Android 4.0.4] RemICS v1.5.3 - SIII look [05-08-2012]
[ROM][PORT][ICS][4.0.4] RemICS v1.5.3 (FIXED) - SIII Look & Feel [20-08-2012]
Both of them appear to be using DevHost, but since I am not able to get to my files on DevHost right now either it seems to be a problem there. Typically they get it resolved in a few minutes so if you try again in a little while it should be ok. The first ROM above has a mirror here on RapidShare if that helps.
Meanrom 2.6 - Issue with Cam Mod and Beats Mod
http://forum.xda-developers.com/showthread.php?t=1645211
After following the specific instructions in the forum as how to install the cam mod and beats mod (specifically post #6171)
Beats still does not show up anywhere on the phone. Someone else had this problem as well, but it was not responded to.
How can we verify that we successfully installed the cam and the beats mods?
Thanks!
MANDROIDS said:
http://forum.xda-developers.com/showthread.php?t=1645211
After following the specific instructions in the forum as how to install the cam mod and beats mod (specifically post #6171)
Beats still does not show up anywhere on the phone. Someone else had this problem as well, but it was not responded to.
How can we verify that we successfully installed the cam and the beats mods?
Thanks!
Click to expand...
Click to collapse
I am at work right now and today is incredibly busier than normal so I can't dig into this at the moment, I am sorry. I will look more at it when I get home in a few hours. I don't see a specific way to test the camera but I would suggest taking some pictures and looking at the size. They should be significantly larger in size with the HQ mod. For Beats, I believe that you can start the stock music player up and plug headphones in and you should see a red "b" icon on the notification bar.
MANDROIDS said:
After following the specific instructions in the forum as how to install the cam mod and beats mod (specifically post #6171)
Beats still does not show up anywhere on the phone. Someone else had this problem as well, but it was not responded to.
How can we verify that we successfully installed the cam and the beats mods?
Thanks!
Click to expand...
Click to collapse
Here's the original post that post was based on, with links to the versions of the mods required. If the coolexe v3 music mod, which includes beats, is installed properly you should have an Beats Audio option in your settings menu and you will need to go into that and check off at least the wired headphones, and optionally bluetooth, before you will see the beats notifications when playing songs in HTC Music.
ramjet73
ramjet73 said:
Here's the original post that post was based on, with links to the versions of the mods required. If the coolexe v3 music mod, which includes beats, is installed properly you should have an Beats Audio option in your settings menu and you will need to go into that and check off at least the wired headphones, and optionally bluetooth, before you will see the beats notifications when playing songs in HTC Music.
ramjet73
Click to expand...
Click to collapse
Thank you!! Most appreciated sir.
Thank you for your help with getting it posted.
I didn't see a beats option in my settings, even though I followed those steps.
If you have any suggestions on how to get it working it would be greatly appreciated.
PS The rom is also missing the sprinttv app. Installing it from Google Play and running it says that the app needs an update and then crashes. Is there an APK for the sprinttv that will work with Meanrom 2.6?
Is there a zip of the missing apps that we can install through recovery?
DrXThirst said:
Yes, I am trying to supply two North American server mirrors. The DevHost is a nice mirror, but still their bandwidth only allocates maybe 150KB/s per download.
Click to expand...
Click to collapse
Well, I have to say this is the first time on this site that I have made several attempts to contact someone to convey an offer of free hosting/mirroring and been completely ignored. I have seen the guy online several times but no reply. I sent him a PM to ask him for at least the courtesy of a reply, but nothing. He is online now but appears to be ignoring it.
So my advice is to not waste your time and bandwidth any further on him or his ROM. I sincerely apologize to you, I was hoping to have a good positive demonstration here by doing it the right way and asking before simply posting mirror links as I have seen others do in the past, but to be ignored just demonstrates that someone does not wish to be helped, and therefore it is very likely that he will receive little help in the future when he does need it.
Badly need some assistance, Will be greatly appreciated. Thankyou
mf2112 said:
Your post must include:
1. A detailed device configuration: ROM, kernel, firmware, radio, mods, etc...etc...
---- This info should be in your signature -
2. A list of things you have searched, read, done, and tried.
---- Expecting to come in here and get a quick freebie? Nothing in life is free, you have to do a little work here.
3. Terms you have searched for and where you searched.
---- Which forums? Which websites? Exact terms and different combinations of terms tried?
4. Your agreement that you have read ALL of the dev's initial posts in said dev thread. TWICE.
---- I mean read, not just skimmed over. Good devs put a lot of work into their first page posts and keep them updated, many times with FAQs and other helpful troubleshooting tips.
5. Your agreement that you have read the stickied guides in your devices General, Q&A, and Development forums.
---- Many people have put in countless hours of their personal time to enter in this knowledge for you to learn it and apply it successfully to your XDA experience and phone, and the mods have put them at the top of the subforum pages so you don't have to work to find them. Please don't waste their time or yours.
6. If you are having a problem, what exact steps brought you to the point you are at?
---- Remember, the more details you can give means that it is more likely your question will get answered correctly.
7. What steps have you tried to resolve the problem on your own?
---- See points 2. and 6. above.
8. What logs do you have?
---- See point 6. above. And this: [GUIDE] How to give constructive feedback to developers And this: [Tutorial] How to Logcat
9. The exact question you want to post
If you do these things I honestly believe that you will not need to post your question as it will already have been answered, but if not, I will enter your questions on any dev thread you want to post in but cannot post in, and post any and all answers received back here.
Click to expand...
Click to collapse
Model Number : A501
Kernel Version: 2.6.36.3+
Build Number: Acer_A501_4.064.01_AAP_OPTUS
Aspect Ratio: 1280x800
Read, Searched, Done & Tried:
Google for a good few hours, Searching countless A501 root links to find 90% of sites were for the A500. YouTubing, wording it in multiple ways found a guy that claimed to be able to root the A501 and A500. Watched the vid and the more I watched the less I trusted him, Clicked the download links in his description and was redirected to sites that didn't look trustworthy.
I haven't physically tried anything to do with rooting yet until I know more about it or find a guide specifically for the A501.
Searched keywords in this site and just about every forum to do with android, found one or two things on here claiming to do the A501 root but I don't have ICS and I'm not exactly sure how to get it, I'm pretty sure my device came as 3.1 or 3.0.1 Honeycomb when I bought it (It's on a Plan) I THINK I updated it to 3.2.1 Honeycomb but can't remember.
Tried multiple apps to help me getting the controller to work for Modern Combat 3 but most of them are for Bluetooth or like the Joystick Center 6 & Joy2Touch (Which I downloaded here) they need rooting - (I'd like to be able to use Joy2Touch without rooting but it doesn't seem possible?)
Quite a few hours went into research and all I know about this is that I need to revert my tablet back to 3.0.1 or 3.1 to root it, I also seen a post saying something like Bootloader will make it difficult - I'm not sure if it's on my device or not.
I have not installed any roms or mods on my device yet.
Terms searched: "A501 root" "How-to root Acer Iconia A501" "How to setup xbox wired controller Modern Combat 3" "Modern Combat 3 Controller support?" I cant remember exactly every term I searched but it was all pretty much the same just worded differently and I used Google, Youtube, Posted questions on answers.yahoo.com and this site but nobody has replied.
Read Dev posts: http://forum.xda-developers.com/showthread.php?t=1370111
http://forum.xda-developers.com/forumdisplay.php?f=1236
http://forum.xda-developers.com/forumdisplay.php?f=565
http://forum.xda-developers.com/showthread.php?t=816994
Nothing that helps with the rooting of A501 - I just searched multiple times in the search bar.
Hey guys.
Looked around the forum a bit but didn't find my answer, trying to play Modern Combat 3 with my wired xbox controller, shoot, change weapon and zoom work. Just can't figure out how to get the analog sticks to aim and walk for me.
(Controller works fine for other games like Dead trigger)
I have the USB/BT Joystick center 6 app and the joy2touch but when i use joy2touch it just says "root access failed"
Is there an easy fix for this? What do I have to do to get this working, would love to play the game with my controller.
Thanks guys.
Kaotica said:
Model Number : A501
Kernel Version: 2.6.36.3+
Build Number: Acer_A501_4.064.01_AAP_OPTUS
Aspect Ratio: 1280x800
...
Click to expand...
Click to collapse
Hey, thank you for posting and including all the info. I am trying to look into this right now, but I am at work so it is a bit difficult to sneak in too much XDA time. I will spend time on it this evening if I am unable to find anything else. Just out of curiosity, did you post this in the A500 forums? I just PM'ed a mod there to see if A501 questions were also included in the A500 forums so hopefully he will be able to get back to me soon on that.
ramjet73 said:
Here's the original post that post was based on, with links to the versions of the mods required. If the coolexe v3 music mod, which includes beats, is installed properly you should have an Beats Audio option in your settings menu and you will need to go into that and check off at least the wired headphones, and optionally bluetooth, before you will see the beats notifications when playing songs in HTC Music.
ramjet73
Click to expand...
Click to collapse
Please let ramjet73 know as to the MeanRom 2.6 http://forum.xda-developers.com/showthread.php?t=1645211 his post 6171
works exactly as long as you first flash the RUU 2.89. If you don't flash the RUU and bring your phone 100% back to stock his method leads to continual white screen (HTC) or constant rebooting.
Kaotica said:
Model Number : A501
Kernel Version: 2.6.36.3+
Build Number: Acer_A501_4.064.01_AAP_OPTUS
Aspect Ratio: 1280x800
...
Click to expand...
Click to collapse
Hey, after checking around, I think your best bet is to post your question in the A500 Q&A forum as there are other questions I saw in there for the A501. You have it well written up and I think you well get help and replies there since you have really tried and people will see and respect that.
Well, first I have to admit, it took me some sticky reading digging to find this thread, but it's a very welcome idea.
I had made this original post here, probably against my better judgment and forum policy, but I'm hoping this can significantly help:
http://forum.xda-developers.com/showthread.php?t=1858551
That post also links to the discussion around lost IMEI's and being stuck on roaming on the Verizon GS3. If you read through the thread, you'll see that the developer is still attempting to ascertain root cause of the lost IMEI and/or stuck roaming. My post is an attempt to add a very specific circumstance to help guide in the debugging of that situation.
I would like to follow up with additional information around the ERI and post a conjecture around devices with non-matching MIN and device phone numbers, to see if any of that might have something to do with or might shed some light on the stuck in roaming mode.

[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*

Rom OP Format...DEVS READ PLEASE

Below is a format that should be used as an example of how a rom thread should look. It doesnt have to be exact. I suggest that you stay creative and use all the features in the advanced panel when creating a thread.
1. Name of rom, team, etc
2. Introduction
3. Changelog in code or php tags
4. What's included in the rom in the (apps, tweaks, scripts, addons, mods) in code of php tags
5. What works/what doesn't work in code or php tags
6. Credits (Users name-with link to (profile/github/or thread u got tweak from embedded), and what they did to help you)
7. Screenshots (2-10 different screenshots of different aspects of rom)
8. Kernel with either link to thread you got it from or github (if stock sense or cm please state that and that is enough)
9. Instructions on how to install the rom (also if special instruction for a2sd or beats audio...etc)
10. Do's and Don'ts of the rom
11. Questions & Answers section (I find this helpful to write out asked questions with solutions at the bottom of the op. I find that it cuts down on the question being asked a million times)
12. Finally the dl link
13. Additional add-ons (this can go into first post or reserved posts after)
I find the embedded link looks and feels better throughout the op if possible.
All sections should have a header with enlarged text and spaced out so people can read it easily.
I am hoping that this helps to make this section a little cleaner and easier. enjoy
The way I look at this is that it takes US weeks/days/hours to make these roms....we can take the time out to make sure that the op looks professional and clean
Also Make sure the op is fully ready before posting. I know we all get excited to release a rom but stating that half the stuff will be updated as time permits just shows that you are lazy and in a hurry which doesnt look good cause if thats the case then how does your rom run....
No posting a a rom thread without a DL link either
Thanks Papa Smurf151 i think everyone who is getting ready to post a rom should be redirected here!
sorry if im not allowed to post here, so please delete my comment if needed
i left this open for feedback
How about how stable it is like in the old days?
I remember last year everyone would label them as beta, RC, final etc.
bennyboy78 said:
How about how stable it is like in the old days?
I remember last year everyone would label them as beta, RC, final etc.
Click to expand...
Click to collapse
I think what Papa Smurf outlined in the OP is more then enough and it covers the basics while keeping the majority of the threads uniformed or at least try to
I also don't think we should start being over critical here and require individuals that start threads in the development section to add labels like Alpha, Beta, MC, RC or whatever.
I understand that having labels would make things a whole lot easier for the user BUT it also doesn't encourage the user to read about what he or she flashes onto their phone.
I don't know how many times I've seen a user complain and harass developers over something that was clearly their (the user) fault because they didn't read the OP. They saw fancy screenshots and saw the download link and either ended up bricking their phone or causing their phone to turn into a hot pocket...lol
Not trying to tell people how to do their job BUT I think we should encourage users to read/search more not shortcut things for users.
Mazda said:
I think what Papa Smurf outlined in the OP is more then enough and it covers the basics while keeping the majority of the threads uniformed or at least try to
I also don't think we should start being over critical here and require individuals that start threads in the development section to add labels like Alpha, Beta, MC, RC or whatever.
I understand that having labels would make things a whole lot easier for the user BUT it also doesn't encourage the user to read about what he or she flashes onto their phone.
I don't know how many times I've seen a user complain and harass developers over something that was clearly their (the user) fault because they didn't read the OP. They saw fancy screenshots and saw the download link and either ended up bricking their phone or causing their phone to turn into a hot pocket...lol
Not trying to tell people how to do their job BUT I think we should encourage users to read/search more not shortcut things for users.
Click to expand...
Click to collapse
Well said, couldn't agree any more.
MBQsniper said:
Well said, couldn't agree any more.
Click to expand...
Click to collapse
See I assumed this was common sense and ROMs that are missing a lot of these details, I don't give the time of day too so those ROMs don't matter to me. Because in my mind all the good ROM's out there already follow this in some way shape or form.
I appreciate what you did but I don't see why we need it is all.
As long as these are only guidelines and not enforceable rules, I agree with them. But I wouldn't agree with deleting/locking threads that fail to follow these guidelines; that would send the wrong message to developers.
v5HMeca said:
As long as these are only guidelines and not enforceable rules, I agree with them. But I wouldn't agree with deleting/locking threads that fail to follow these guidelines; that would send the wrong message to developers.
Click to expand...
Click to collapse
Rom threads will never be locked or deleted for not following these guidelines. I would hope devs would embrace them and if a fellow dev isn't then I would hope someone would point them here and try to help them. Most rom devs want to have a nice looking op. But some of them are new and don't know better or are very young and don't know better. This just helps to give structure that they can refer to and say oh yeah maybe I should have that or this.
XDA Moderator
Cherokee4Life said:
See I assumed this was common sense and ROMs that are missing a lot of these details, I don't give the time of day too so those ROMs don't matter to me. Because in my mind all the good ROM's out there already follow this in some way shape or form.
I appreciate what you did but I don't see why we need it is all.
Click to expand...
Click to collapse
What?

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! 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.

Categories

Resources