A message for the webmaster.
Have just joined today and am initially interested in reviewing all posts from Australia concerning hardware and software, sources and issues.
Is is possible to sort membership list by country (not location) to make this easier?
Related
Hi all,
i just bought my self a second hand MDA, and i want to use it as phone, but also play with it, and modify the OS. I've been reading these forums all night, and i was wondering if there isn't a FAQ for all this stuff.
Reading all the threads confused my about how to backup, how to upgrade to wm2003 .. what's the difference between O2 and T-Mobile ...
Maybe it should be better to include all frequently asked questions in a document. I'm willing to help to set this up ...
I also checked the #xda-developers on ircnet, but it was an empty channel, does anyone know where the channel is?
thx
If you want to help create FAQ documents, you're most definitely welcome to. We'll certainly give such documents a prominent spot on the site.
Be advised that ROM manipulation on these devices is a hairy and complex subject though.
With so many roms and software being developed and so many questions being asked over and over again, it occured to me that there is not (correct me if i am wrong) a public bug tracker for XDA.
Ideally integration with the user database and even possibly the threads (more than just a url link) would be great.
If we had a way of tracking and submitting bugs then i think each dev or cook could better manage the bugs in thier software and i think it will help reduce the duplicate requests and bug reports going on in each thread.
The bug tracker could split between software types, platform, then also have device sections with each rom under that, much like XDA is structured at the moment, in fact probably identical to reduce the confusion and help with the linking and integration.
What bug trackers could possibly be used that would integrate with XDA? Bugzilla?
I am more than willing to setup an instance for testing etc, who would be keen to see and help with this? Integration will be the biggest task.
Interesting Idea, I guess that would have to involve developer consent that they want their work to be tracked. Having people discuss in threads isnt bad as that is what the forum is for but a tracker type online utility may be good for huge projects which would cut down on posts saying "Hey whats the status of Bug X and Y?"
Good idea
I used my own tracker for a while, but for xda we would have the issue of how to assign users to what role.
Every time I made a rom, I would need to request a new category and get ten pepper added as project authors ...
Trouble with the tracker that I found was that it just got messed up like the forums. Trust me that nobody searched it.
I reverted to a dedicated subforum, eventually, as it was less work in managing. I had appointed a second bug system admin, yet still got heaps of stuff to do...
A tracker is a great idea, but would be misused, and there stupid "why is camera no work kthxbai" posts would continue by those not checking the tracker.
Integrating a attacker is pretty easy on a username perspective, but harder on a people perspective
Still, I like the idea, but can envisage huge amounts of work for svetius, making new categories every time a new rom appears etc ...
pulser_g2 said:
I used my own tracker for a while, but for xda we would have the issue of how to assign users to what role.
Every time I made a rom, I would need to request a new category and get ten pepper added as project authors ...
Trouble with the tracker that I found was that it just got messed up like the forums. Trust me that nobody searched it.
I reverted to a dedicated subforum, eventually, as it was less work in managing. I had appointed a second bug system admin, yet still got heaps of stuff to do...
A tracker is a great idea, but would be misused, and there stupid "why is camera no work kthxbai" posts would continue by those not checking the tracker.
Integrating a attacker is pretty easy on a username perspective, but harder on a people perspective
Still, I like the idea, but can envisage huge amounts of work for svetius, making new categories every time a new rom appears etc ...
Click to expand...
Click to collapse
yeah i agree with all of your points, i guess i was thinking that if it were somehow integrated into the forums then it'd be used more. as far as roles, a simple request to establish a project that would then be assigned to the dev in question. they could then choose to add extra people.
i just have no idea what tracker could and how fully integrated it would be with the forums.
it seems to me that if some of the noob "why is x not working" could be at least reduced by a bug tracker, hell we could even weed out the noobs by saying that unless you check and submit bugs no questions will be answered in the forum.
anyway, thought it was worth mentioning and getting the ball rolling. We could do some basic pilots of different trackers based on any known integration benefits.
Dear visitors and members,
This is my first post in XDA-Forums. I hope I am posting in the right sub-forum.
I want to share a technical article I have just posted in my blog. Perhaps the solution I am presenting has been already discussed here, and may be dejavu for some members and visitors.
HTC, Motorola, Samsung, and for that matter chinese clones with Android OS have mostly bluetooth problems. I have in a pratical manner shown how to hack into a free and excellent app available in Android market known as "BlueTerm".
My chinese HTC clone (A3 Star HD2 T8585 clone as is known) can now connect with my bluetooth module and I can send control commands that are processed by a microcontroller thorugh serial communication .
The article is at my blog and will share link to anyone who is interested by sending me PM
Tayeb
I have published for download a modified BlueTerm apk that will hopefully work in most Android devices including HTC, Motorola, Samsung and others with Bluettooth SPP connection issues. Anyone interested may ask me the direct link through PM.
Recognized Developer Code of ConductAs an XDA Developers member with special standing as part of our developer program, we obviously have some expectations of your conduct. We try to be friendly here, and while we understand that not everyone is going to get along, we would ask that you try to avoid getting into big arguments in threads. If you have an issue with another forum member, take it up with them politely in a private message. It’s the mature way to deal with things.
As a titled member on XDA, you are a representative of XDA’s ethos – “by developers, for developers.” As such your activity offsite in other public venues should be in the same vein. Any negative, derogatory, abusive talk or actions may be taken into account as to your status as a titled member. This would include any behavior which violates our site rules. This does not change your responsibility to be subject to the requirements for acceptance into the Recognized Developer program, both in their current and future states.
While all users should follow the site rules, we would ask that you take a quick look at them again, as they are occasionally updated. If you have any questions, please don’t hesitate to get in touch with any moderator.
In addition to the rules, we would highlight the importance of acknowledging the work of others. It’s not nice to see your work get ripped off—whether it’s a ROM, part of a ROM, an app, a theme, images, guide text, etc. If you’re familiar with the regulations in academic institutions, you should know the score. Just seek permission and acknowledge those whose work you use, and generally be reasonable about things.
We would also ask that if you have a dispute, you first try to resolve it in a reasonable and private way, such as through private message. It is in no one’s interest to see your dirty laundry aired in public, and it looks much better for you to avoid conflicts on the site.
Senior Recognized Developers of XDA, in additional to the above, are expected to be active on XDA regularly. While we all go away for vacation, exams, and other everyday life events; we would ask that if a Senior Recognized Developer intends to take a significant break from development, he or she stand down temporarily. You’re more than welcome back if and when you return, and we’d love to have you back, if a space becomes available. The reason for requesting this level of activity is because as a Senior Recognized Developer, you will be able to vote on the appointment of other Senior Recognized Developers in the future. If many Senior Developers disappeared, it would be troublesome gathering a sensible turnout. In addition, from time to time we will invite discussions on matters pertaining to the site, and it’s only fair that we try to ensure that the people most familiar with development and XDA have a chance at helping out.
Recognized Developer Minimum RequirementsTo be able to provide some transparency on how the reviews for RD are rated we’ve set up these minimum requirements. Please understand that the RD program is not just a reward for people that try hard on XDA, it is more than that. Accordingly, not just any project meets the standard of development. We will use these minimum requirements with enough room to budge if the circumstances require this, but please use a somewhat critical view of your projects, and only apply if you have at least met these requirements.
Make sure you uphold the RD code of conduct and the regular XDA rules. Should you have infractions on your account, contact the Developer Committee if you want to know if you are eligible to apply. As a general rule of thumb, wait one month per infraction point before applying, and can’t accept members with more than 10 points to their account. Of course, exceptions may be made but contact us if you have a question about this.
All Projects
Members must be actively involved in the community
Team accounts can’t receive the RD title. It’s a program that rewards developers for their individual work and team accounts don’t fit that idea.
A minimum of two full-fledged, markedly different projects are needed to apply for RD, only very special projects are considered otherwise
Any project needs to have at least three months of active development before it will be taken into account for the application
No history of bans and/or serious infractions
Changelogs must be readily available inside the thread, with updated information for each version
Feature lists and changelogs need to be free of blurry expressions like “tweaked ext4 performance” and other meaningless terms. Instead, it should be explained what was done in detail and why it was done
ROM
They started from an official manufacturer or source base (stock ROM or AOSP-like source).
Threads show a clear overview of changes made, in a way that DC can clearly see what has been developed by the user
The ROM isn’t the product of an online kitchen or otherwise derivative development (i.e. themed stock ROM)
ROMs need to identify what kernel they are using
If 100% stock then they must state that
If custom they must provide a link to the kernel on XDA (if available) or a link to the kernel source. To accomplish this there are two options:
Option 1: They provide links to suggested kernels but do not include them in the ROM
Option 2: They include the kernel but must provide a full, buildable source with all GPLv2 requirements met
Apps
Very simple applications may be excluded (very basic UI or functioning)
A free version of the application is available on XDA (no trials)
The developers are either active on XDA or really helpful in their support thread
Kernels
Sources must be posted and downloadable with build comments, toolchain used, and must compile
Sources must be released via forking + commits rather than “lump releases”
Link to the source must include which branch is in use
Guidelines:
In order to make sure the DC is able to find the information we need to make sure your threads hold all the information necessary. Here’s a list of things we like to see.
Threads should include:
Clear introduction
An overview of what the project does (i.e. its purpose) and what is included
2-8 screenshots that are posted alongside each other
A clear changelog in a
Code:
or tag, that shows the non-trivial updates to the project
Installation instructions and links to download and github (or like services) for source code, as applicable
Credits with links to the projects that have been built upon, or have been included, in this project
Provide a checksum if you can (md5, sha1 etc.)
The DC set up a template thread that highlights the important parts of a project. Try to follow this template to have an organized and clean thread. You can find the template thread here.
I was checking the list of holidays on the Achievements page. The current list comprises mainly of holidays in the US, with the odd holiday from other countries thrown in. For me as an Indian, a Thanksgiving would not be of much significance, but logging in on a Diwali means a lot. Diwali BTW is a national holiday across India. Similarly, there would be holidays for different countries which are important to XDA forum users from those countries.
My suggestion is to add holidays to the list based on countries from where there are most users. When XDA forum users log in on those holidays from that particular region, give them credit. Maybe a bit complicated to code as multiple factors will need to be checked for a logged-in user.
MOD ACTION:
Thread closed as duplicate of https://forum.xda-developers.com/t/...fic-holidays-to-the-achievement-list.4520037/
Please check Rule 5:
5. Create a thread topic or post a message only once, this includes external links & streaming media.
As a large forum, we don't need unnecessary clutter. You're free to edit your message as you like, so if you do not receive an answer, revisit your message and see if you can describe your problem better. Not everyone is online at the same time so it might take a while before you receive an answer.
You can bump your unanswered question once every 24 hours
Duplicate threads and posts will be removed
Always post in an existing thread if a topic already exists, before creating a new thread.
Use our search function to find the best forum for your device.
Links to an external source are only allowed if relevant to the topic in hand. A description must be included, no copy & pasting from the original source.
Self-promotion is forbidden, this includes blogs, social media and video channels etc. Random links will be removed.
Click to expand...
Click to collapse
If you need the other thread moved here or to any other forum, please use the Report button under your post and make the request.