I have seen many users, including me, asking if they should or should not keep their device encrypted and disable AVB across different threads. This thread aims at providing a better understanding of why and when the aforementioned options are needed to the newbies like me. I am calling on the experts (anyone actually) to give their opinions and explanations here and teach us so that we do not just follow guides blindly.
I hope this draws some attention. Thank you in advance for your time.
Related
Hello,
first thanks for this great place! I would have smashed my Touch HD if xda wouldnt exist
I have a suggestion regarding the ROM forums and threads:
As the cookers and chefs are mostly to busy to gather information from the thread and put them in the first(second...) post, it would be really nice if a threadstarter or moderator could assign a normal user as an "thread-specific" moderator (for only the first three posts for example). So volunteers, people very interested in this ROM, could maintain a buglist, tips and hints, fixes and other helpful stuff from the thousand and more pages and make the life for everybody easier.
Its sometimes really hard to find information in the thousand pages. I think a solution like this would help everybody and reduce the senseless spam questions in the ROM forums. All 1-2 pages new users ask the same as people before, and all are getting the answer "Read through the thread, its mentioned 10 pages before" for example.
Whats your opinion about this?
7Bit said:
Hello,
first thanks for this great place! I would have smashed my Touch HD if xda wouldnt exist
I have a suggestion regarding the ROM forums and threads:
As the cookers and chefs are mostly to busy to gather information from the thread and put them in the first(second...) post, it would be really nice if a threadstarter or moderator could assign a normal user as an "thread-specific" moderator (for only the first three posts for example). So volunteers, people very interested in this ROM, could maintain a buglist, tips and hints, fixes and other helpful stuff from the thousand and more pages and make the life for everybody easier.
Its sometimes really hard to find information in the thousand pages. I think a solution like this would help everybody and reduce the senseless spam questions in the ROM forums. All 1-2 pages new users ask the same as people before, and all are getting the answer "Read through the thread, its mentioned 10 pages before" for example.
Whats your opinion about this?
Click to expand...
Click to collapse
Hi,
1. I don't think this is possible with the standard vB software. And I know the webmasters are adversed to applying "patches" unless they really help.
2. There is a problem of trust. Moderators are selected on here to be trustworthy, not to carry out malicious activities and to always be fair. I've seen plenty of people on here become friends and then enimies as quick as they can. Giving many users complete control over a single thread could become problematic. If you're just speaking about allowing users to edit another users thread. I can't see that been too risky - but still Impractical with the forum software.
An alternative, If the ROM cook would like someone to help manage the thread, they should arange before hand to let someone bag a few posts on the thread when it's first started (I know its not practical to existing threads). Moderators can help add posts when needed and remove any
pesky "First" messages someone might inject in the way .
Just my thoughts
Ta
Dave
Yes you are absolutly right, good idea
It would be enough if the moderators could move a post of the "Useful thread stuff Collecter / Maintainer" at the second or third position of an existing ROM thread, or if the creator already plans it when creating the thread. That would be exact the same without editing the board software or applying hacks...
7Bit said:
Yes you are absolutly right, good idea
It would be enough if the moderators could move a post of the "Useful thread stuff Collecter / Maintainer" at the second or third position of an existing ROM thread, or if the creator already plans it when creating the thread. That would be exact the same without editing the board software or applying hacks...
Click to expand...
Click to collapse
Well if it's not possible to arrange this beforehand by timing a the time of thread creation, you could indeed ask on of the mods to help you out there. Don't look at me yet though, haven't figured that one out yet
Hi all,
I decided to root my phone and mod it a couple of weeks ago. Now, baring in mind I knew nothing about how to do it, I was pointed to this forum and have spent that time reading, learning, teaching myself. I have an HTC Desire with the common low system memory problem.
Well, after rooting, s-off'ing, partintioning etc i tried a number of different ROM's. I actually lost count how many i tried :-O In the end though, it came down to just one rom, which was LeeDrOiD. I now have this installed and the sense 3.0 addon pack and the keyboard mod with the arrow keys on it
Anyway, the point of this post is to thank this community and all the people who post their information on here. To the people that create guides to help us newbies out. I have learnt so much in such a small amount of time, which is due to the consise and easy to digest guides on here. This sit is the best
Now, not sure if I'm allowed to do this or not (you can remove the links if not) but, i wanted to put the main three pages i used to learn pretty much everything. This is purely to do with the my phone, the HTC desire but, can be used to teach.
Firstly, the newbie guide. This is so cool, so easy to understand.
http://forum.xda-developers.com/showthread.php?t=1016084
Secondly, the main LeeDrOiD page, containing everything you need to know and links to all the software needed.
http://forum.xda-developers.com/showthread.php?t=1170633
Thirdly, the FAQ, in particular the FAQ on the addons i.e. Sense 3.0. Once i read this, I realised why the addon hadn't worked and so when i followed these instructions, it all went perfectly. Used the same procedure too, to flash the new keyboard.
http://forum.xda-developers.com/showthread.php?p=16808961#post16808961on
Well, thans again XDA community and i hope anyone newbies that read this will find the three links informative.
I experienced early access for number of apps from Xda
Nice to see that not all newbies (myself included) are not unapreciative of all the hard work the mods devs and community here have provided to myself and many others. I would also like to thank everyone here for all there hard work and the thanks button will now become invaluble as appreciation and manners never cost nothink (bar 10 posts)
I am glad to join this thread. As my Desire S is the first Android based phone I own (switched from Symbian after the total dissapointment on it) and it was a complete black box to me, even after I had spent hundreds (not kidding) of hours reflashing my old Nokia.
So thanks to the devs and the advanced users here I am catching up quite quickly just following the guides (some of them are written in a pro manner but are pointing to the right tools and threads so it is not impossible to get things together)
So big thanks from me to everyone involved in this community.
Hi,
I like what the XDA Devs bring to us "users" in terms of modding phones, instructions, assistance and so on. I am wondering though how many of these devs actually get a chance to go through their own thread (rom post, suggestion, hack or whichever) and update their main post with the most common hurdles that users within the forum have posted and inquired about?
Not many would be my guess and I don't blame them.
I have also seen the comments of "search this thread" way too many times and have been caught out myself too.
My suggestion is that people with the issue contribute back to the thread if any answer helped them to the solution, or if they come up with the solution themselves.
To improve this concept further, keywords for questions and answers within the thread should be compulsory.
A list of possible keywords would be
[Q] Question
[A] Answer
Bug
Solution
and used in conjunction with each other. If you have both the bug and solutions, you'd post - yes i know what that looks like!
Benefits to this system would be when searching a thread you could filter the entire thread with [Q] and bits and then troll for the answers.
This is too long and will most likely be ignored, but if you've read this far, please let me know what you think.
> Abstract: I have been consolidating a complete, monolithic, and community editable guide for all mobile devices, to reform how XDA Developers works. Take a look, and edit or give suggestions... (Perhaps merge this with XDA University?)
## Rationale
XDA Developers is one of the largest and most important sites to mobile device development. We know all that; we've been here for years. And after staying here for a long time, it's hard to imagine anything different from the status quo; nor why the "new guy" is so frustrated and confused.
Unfortunately, owing to our messy evolution, the guides for most devices on XDA are, (quite honestly, no offense), outdated and disorganized, divided among tons of threads and maintained by OPs who may or may not be active. The XDA Wiki was built on the premise of consolidating the info from the forum, but the tendency to link to forum posts rather than bring in the full methods has made it utterly redundant, and therefore rarely edited or trafficked.
The reality is, forums are great for development and asking questions, but they are the wrong place for constantly fluctuating guides that demand united community support. The result is the status quo on XDA; a ceberus of information difficult to organize or sift through, resulting in newbies constantly asking supposedly "obvious" questions about methods and issues long since solved.
The question is, is it the noob's fault for not trusting or reading such disorganization, or could it be that we aren't making it clear how to proceed safely?
## Design Specifications
To rectify this situation, I have been compiling the Android Development Codex, a complete, monolithic, and community editable guide to the any device I could get my hands on, taking users all the way from unlocking to customization.
The codex will also give readers a few tips and tricks for troubleshooting common problems (so they don't have to wade through 900 posts to find the answer), and general guides to cool mods that can be made on the phone. Perhaps we could even teach people to create modifications to keep the community going.
The Android Development Codex is based on eight principles:
* Everything must be in the guide. We need customized "beginning to end" guides that give the user everything it takes to mod a device and deal with problems afterwards. As stated above, the XDA Wiki failed because it only linked to the forum, making it no more useful than a forum sticky.
* Mark or fix outdated information ASAP. Outdated information is the biggest issue with the status quo on XDA; at best, it won't work, and the new guy will come crying to the forums. At worst, devices will be bricked, leading to intense mobs of angry noobs. With a monolithic guide, as soon as new developments occur, we can post it in the Codex as a warning to all, and change the method if needed.
* No redundant information. There could be thousands of devices by the time we get to a finished state, and much of that info is exactly the same. This leads to duplication of work, and eventually outdated info. Examples are things like ClockworkMod instructions, Glossaries, and general OS mods. The Codex should consolidate as many mods as possible into general guides, and for things like glossaries and recovery instructions, Mediawiki-style templates should be used to pull them in.
* One customized guide for every device family. Every device is special in some way. The XDA Developers Book is great, but even the most general of rooting guides cannot tackle the thousands of unique circumstances that exist in every device. Rooting, Unlocking, Downgrading, and other unique things are under this umbrella.
* Always provide a manual method. Automatic "one-click" roots are great, but manufacturers are always out to patch the latest method. If we don't know how to do it by hand, we can't really find much of a solution.
* Ensure that all required files are accessible and stay accessible. Eventually, all good things must come to an end, and when people are no longer around to sweep the grounds, link rot sets in. This is very, very bad; one of the archives could contain a vital rooting program, and there would be no way to recover it. Just remember the fall of Megaupload. Always have multiple mirrors for every file, and perhaps archive everything into the Internet Archive when the community is gone.
* Give all sources for methods included. Credit must be given where credit is due, not only in deference to the original authors, but also to give the methods credibility.
* The ultimate goal is to transform a layman into a developer. For most people nowadays, modding mobile phones is their gateway into the workings of the computers that control our lives today, just like home computers were in the 80s. The Codex needs to clearly show how anyone can become an XDA-Developer and participate as enlightened individuals, rather than as mere participants.
## The Monolithic Guide
The Android Development Codex is here.
Currently, only the HTC HD2 and the HTC Droid Incredible have functionally complete guides at the moment.
The entire thing is stored on Github Wiki, so you can edit it if you have a github account. Hopefully, developers will all be able to come together once and for all, and work on one big guide, rather than tons of small, redundant, and outdated ones.
## The Android Development Codex is unfinished! Why are you releasing it now?
Originally, I was going to keep the Android Development Codex as a surprise until all the guides for the devices I owned were complete. However, a new project called "XDA University" is being started with similar goals, so am prematurely releasing my work to the community and awaiting further developments.
If anyone here has a hand in creating the XDA University, please contact me, because I have some great ideas on how to make it work, not to mention tons of data for us to start with.
You have a PM
TNSMANI said:
I also request all the users to use thumbnails instead if inline screenshots, if possible. Where it is required or unavoidable, you may use the inline images. You see, for those who use the mobile to view the threads, it is very tedious to scroll through such screenshots and most of the times important messages in posts also will be scrolled past.
So please understand and cooperate.
Thanks and cheers!
Click to expand...
Click to collapse
Doing it here to avoid detailing a non-related thread.
Thanks for removing posts that had nothing to do with the purpose of the thread in question. I would appreciate if you could also address the following queries:
1. Please explain the following:
"Where it is required or unavoidable, you may use the inline images."
WHAT determines whether it is required or unavoidable. And WHO determines whether it is required or unavoidable.
If the answer to the above isn't clear, please remove the inline screenshot feature itself, to remove conflicts/ confusion/ useless arguments over personal preference, OR let the poster choose how he wants to write his post, even if that means some of the members may choose to skip reading it.
2. You didn't address the more important issue of being impolite and using cuss words in the forum. Clearly, these are violations of forum rules, and rules apply to EVERYONE.
I do appreciate that people should co-operate with each other and make forum usage a pleasant experience to gain/ share knowledge, solve problems and help each other out, among others that are development related and focuses on the purpose of every thread.
Where people have a difference of opinion, for example, like how one wants to present an idea/ view (obviously in a respectful and dignified way), someone person's preference shouldn't override that of another. We should just leave that to the poster.
It is just a preference, and it should stay that way AS LONG AS IT DOESN'T VIOLATE ANY OF THE FORUM RULES.
Replied via PM.
TheMystic said:
Doing it here to avoid detailing a non-related thread.
Thanks for removing posts that had nothing to do with the purpose of the thread in question. I would appreciate if you could also address the following queries:
1. Please explain the following:
"Where it is required or unavoidable, you may use the inline images."
WHAT determines whether it is required or unavoidable. And WHO determines whether it is required or unavoidable.
If the answer to the above isn't clear, please remove the inline screenshot feature itself, to remove conflicts/ confusion/ useless arguments over personal preference, OR let the poster choose how he wants to write his post, even if that means some of the members may choose to skip reading it.
2. You didn't address the more important issue of being impolite and using cuss words in the forum. Clearly, these are violations of forum rules, and rules apply to EVERYONE.
I do appreciate that people should co-operate with each other and make forum usage a pleasant experience to gain/ share knowledge, solve problems and help each other out, among others that are development related and focuses on the purpose of every thread.
Where people have a difference of opinion, for example, like how one wants to present an idea/ view (obviously in a respectful and dignified way), someone person's preference shouldn't override that of another. We should just leave that to the poster.
It is just a preference, and it should stay that way AS LONG AS IT DOESN'T VIOLATE ANY OF THE FORUM RULES.
Click to expand...
Click to collapse
Hello sir, I just wanted to inform you in-line images are absolutely ok and we apologize for the misunderstanding. That’s our fault but will make sure the proper information is known to everyone on the moderation staff.
I’m not gonna respond to your second issue as that is something that is purely subjective in nature. But I can say we strive to be as impartial as possible and we absolutely do extend the forum rules to everyone. Just because it may not be publicly visible that doesn’t mean it wasn’t handled privately.
However, sometimes things get missed so the best thing to do is report whatever posts you think need to be reviewed. It’s a very large forum and we rely on members to point us in the direction of moderation needs.
If you have any other questions or concerns please feel free to PM me. I am happy to have a discussion with you about anything. I am gonna close this thread though as that the primary reason for it being opened has been addressed.