Related
Hi
I haven't been round these forums as long as many, but I noticed the wiki was a bit out of date and through searching found that there was some intention to move to Mediawiki in 2006: http://forum.xda-developers.com/showthread.php?t=267487
Unfortunately more searching only turned up 2 or 3 threads when users were asking how it was getting on. I think, with the nature of a wiki, we could open it up and run it like a community project when the scripts are there, to move pages from the existing wiki over rather than having one person do it all which could take a long time.
I'm no expert but anyone knows how wikipedia works so I think it's just a case of getting it done. Here's a brief guide http://www.siteground.com/tutorials/mediawiki/mediawiki_installation.htm
Anyway, to keep this thread concise:
- Where are we with the mediawiki (has it been shelved?)
- Would you be willing to open the project of migrating pages to the community to speed up the mediawiki
And errr, can't think of anything else, so I'll leave it there for now. If things do start moving along nicely, we could set up a thread to discuss specific areas that need work and get a team of editors together.
bumping for information
bumping to see if this is still alive?
Last update from Flar (site Admin) a few weeks ago when someone asked the same in the moderators forum was that moving from phpwiki to mediawiki is not as straight forward as they imagined initially, and also they first need to change the hosting server because of the extra added load from mediawiki (it's bit more server hungry than phpwiki).
Hi, I was wondering if there was any new development concerning this topic? I've been using the wiki more frequent lately, and it just lacks a lot of features and usability, which would be much improved by a move to MediaWiki.
p.s.: I've just donated a little something to help pay for additional hosting capacities.
Hey, I never knew this thread existed
I last PM'd Flar before I became a moderator at the back end of September with regards to this. I too would be very interested in see'ing an XDA MediaWiki.
She said that the person who is looking into is not always available, this is why there is a delay.
I will try and get and update on this, if I can.
Thanks
Dave
I HAVE AN POCKET PC == INVIEW == N911 (D-MEDIA) WM2003
AND I WANT TO UPGRADE THE SYSTEM TO WM5 OR WM6 IF ANY ONE KNOW WHAT VIRSION IS GOOD TO ME AND HOW TO UPGRADE
[email protected]
HELP ME PLEASE n911
no one can help me to get wm5 or wm6 for N911 PPC
Why you opened 2 threads??
http://forum.xda-developers.com/showthread.php?t=401113&highlight=N911
No One Answer To The First No One Can Help ?
Don't post the same thing twice!!!
With Virsion Is God To Mee And How Can I Upgrade Please
You are new so listen up!
Firstly, Welcome to XDA-DEVELOPERS!
This is not Craig's list. You are expected to read & learn here, not just type up wish lists like classified ads. This is a forum for Developers that has over the years become popular with the general public. As such, you are expected to read & learn. Know what you need & want before you post & be specific in the issues you're having.
Also, show respect. Use proper capitalization, use spaces, use paragraphs & punctuation. The easier you make it to read, the more likely someone will take their FREE time to actually read & help. Undestand, that if it appears that you've made NO effort, then those that have spent the time reading & learning will feel that you are unworthy of recieveing this sometimes hard earned info. Most of what you need is already available. Take some time & make an effort.
When looking for specific items, use the search button, or the "Search this Thread" tools for searches in specific areas.
I will give you a chance to edit & properly format your post. Do this & include some info you've looked up or searched for & have questions on. If you cannot do this, your post will be closed.
Thank you.
GSLEON3 said:
You are new so listen up!
Firstly, Welcome to XDA-DEVELOPERS!
This is not Craig's list. You are expected to read & learn here, not just type up wish lists like classified ads. This is a forum for Developers that has over the years become popular with the general public. As such, you are expected to read & learn. Know what you need & want before you post & be specific in the issues you're having.
Also, show respect. Use proper capitalization, use spaces, use paragraphs & punctuation. The easier you make it to read, the more likely someone will take their FREE time to actually read & help. Undestand, that if it appears that you've made NO effort, then those that have spent the time reading & learning will feel that you are unworthy of recieveing this sometimes hard earned info. Most of what you need is already available. Take some time & make an effort.
When looking for specific items, use the search button, or the "Search this Thread" tools for searches in specific areas.
I will give you a chance to edit & properly format your post. Do this & include some info you've looked up or searched for & have questions on. If you cannot do this, your post will be closed.
Thank you.
Click to expand...
Click to collapse
Congrats on becoming a Mod!
That's a great explanation of what to do!
As far as I know there is no WM5 or 6 for the In-View D-Media N911. I see that you have posted this on other forums as well. No means No regardess of where you hear it.
It seems to be getting a mess in the dev. section lately.
Put your idea on this thread and we'll look into it.
1. create sticky for official (samsung) firmware as easy downloads
2. create sticky for some basic guides
3. create sticky with pointers to roms for the in-house cooks (rotohammer etc.)
this is a start.
MOD EDIT: BEFORE POSTING ANY THREAD IN THE DEVELOPMENT SECTION, PLEASE READ THE FOLLOWING:
If you have developed a ROM, or are working with others to do so, the development forum is somewhere to discuss and share ideas, post useful feedback and logs or crash dumps, and to discuss a common goal developers are trying to achieve.
It is NOT the place to post your question because it gets higher traffic, or because more experienced users frequent it. Doing this just annoys those who are working on the device, and drives them away. Developers don't want to wade through 20 threads of "Help me urgently" to find their threads for porting and fixing camera issues etc. Similarly, if a thread is designated as discussion for developers say, porting a camera fix, please do not post in there asking "When will it be ready?", "Can I flash this yet?" etc. This is both completely disrespectful to those working on the project (you evidently haven't read the important posts in the thread), and also is making it harder for developers to find comments from other developers or testers when required.
Similarly, don't make loads of "Thanks for your work here" posts in an active development thread. It's just as annoying to developers as asking when something will be ready. If a ROM is complete, then go ahead and thank the developer if you wish, but don't go into threads for devs only, and interrupt it to post "thanks". It's basically spamming, and is treated as such.
If you are posting in development, you should have read every sticky and notice there, and should be actively developing or helping in the development of something. Developing isn't installing a ROM, or using a tweak, it's creating a ROM or other hack or tweak. If you haven't read for several days before starting out on XDA, you are likely about to ask something already solved. I registered on XDA when I first wanted to post, and that was to join in a discussion on something. Sure, join up and ask a question, but read the information available in General and Q&A first, as your question will have been asked before. Search is your friend here, become familiar with it.
Regarding when to post in development if you are not actually developing something, there is one occasion where it's acceptable. If you find a leak of a new ROM, which isn't already posted, and you verify it's legitimacy via either running it, or based on the source you obtained it from, then this is assisting in development, and should be posted in development. If you want to ask when a leak will be available use search first, then if not already in discussion, open a thread in general or Q&A.
If you have a problem flashing a ROM, this is NOT related to development. It's up to you to determine if it is specific to a particular ROM, and post useful information in that developer's existing thread for the ROM. If it happens on more than one ROM, and isn't a known issue (remember you should read several times more words than you post), then find out what you are doing wrong. Check guides written by others, try to repeat the problem and see if it happens every time. Something needs to be reproducible to be fixed effectively.
Once you have identified what you need help with go to the device Q&A forum (general if device lacks one), and make a clear, informative thread that explains the issue, and what you have tried doing to fix it. Did you re-download the ROM? Did you ask a friend to flash it for you, to reduce chance of user error? What steps (exactly) did you follow? What errors did you see (exact wording)? Did you double check all the steps? Did you do a wipe or hard reset?
If you make a clear, concise, yet detailed post, you will find help forthcoming, and should get the problem sorted very quickly. If someone suggests you try something, report back on what happened, did it work etc. Then, next time someone has this issue and searches, they will find this and have a verified and tested solution.
So remember... before you start a thread in development, ask yourself what you are developing. If you can't answer, then stop, step away from the post button, and think about where you are posting. Would it be better in General or Q&A, or is some more time with your best friend, search, required?
I'd have a set of stickies including:
Flashing Guide http://forum.xda-developers.com/showthread.php?t=895827
Unlocking Guide http://forum.xda-developers.com/showthread.php?t=843323
Rooting Guide http://forum.xda-developers.com/showthread.php?t=859712
A *HUGE OBNOXIOUS BLINKING* Readme http://forum.xda-developers.com/showthread.php?t=888071
I'm by no means a Dev myself, but I'd love to see y'know... development posts when I lurk here.
Ok, now that i'm un-retired, i'll ask some major cleanup on the dev section.
Starting today/tomorrow between flashing my dev Tab
Several people posted dumped stock firmwares, maybe this should be consolidated into one "Get back to stock" sticky?
T-Mobile stock firmware! http://forum.xda-developers.com/showthread.php?t=855851
[FIRMWARE] - AT&T stock firmware http://forum.xda-developers.com/showthread.php?t=847609
AT&T Production Stock Firmware (I987UCJK1) http://forum.xda-developers.com/showthread.php?t=857608
Also, rotobackup instructions http://forum.xda-developers.com/showthread.php?t=850359&highlight=rotobackup
Links to Open Source archives http://forum.xda-developers.com/showthread.php?t=844981
Good instructions on building cifs module http://forum.xda-developers.com/showpost.php?p=9470152&postcount=53
Also can be used to build tun.ko module for VPN.
I would recommend having tags for the different models of tablets. ( [VZW] [TMO] [AT&T] [SPNT] [EURO] etc...)
Just my .02
We really need to have them separated... This is getting bad. Take a vote and and promise everyone would be on board!!
Galaxy Tab Android Development (CDMA)
Galaxy Tab Android Development (GSM)
Galaxy Tab Android Development (...)
Please!!! lol
I agree that the Tab development needs to be split amongst compatibility.
GSM/EUR
CDMA
etc.
That will make the issues with possible flashing mistakes lower and also enable people to find the best build for them.
A third vote for at least something like a top level and sub forums for GSM and CDMA. There might be things that apply to both, but it seems like real development would be at least specific to one or the other, if not down to the carrier level (and I'm not suggesting per carrier forums).
A sticky for my directory(bible). This will be updated frequently. And will be useful for all noobs and pros alike.
Sent from my GT-P1000 using Tapatalk
What happened to this idea? The development forum is CRAP. I've spent the last three hours seaching for a stock ROM. Can we please, please get some mod action in here?
Sprint only section please! +100 to the splitting up compatible models.
williams37 said:
Sprint only section please! +100 to the splitting up compatible models.
Click to expand...
Click to collapse
+1000000 more for spliting up!
I agree and count my vote, this forum should be easier to find and read the info im searching for it took me days to find a rom and another day to find out how to mod my device using google we should also hav more dev's more porting
wingtytn said:
I agree and count my vote, this forum should be easier to find and read the info im searching for it took me days to find a rom and another day to find out how to mod my device using google we should also hav more dev's more porting
Click to expand...
Click to collapse
What we really need is a bigger community. The larger the user base, the larger the dev base. Especially in the states, it seems like no one is developing for our Tabs specifically. And from what I've found, ours are, just like the Galaxy S, different from the international version.
So do we even have a Mod ? Can they do this for us ? Its been like weeks since we asked to split it up.....
+1beeeeeeelion to split and have a CMDA and GSM and Intl section added....and then under those when people list just say [Sprint] or [VZW] in the title of the thread....
aal1 said:
So do we even have a Mod ? Can they do this for us ? Its been like weeks since we asked to split it up.....
+1beeeeeeelion to split and have a CMDA and GSM and Intl section added....and then under those when people list just say [Sprint] or [VZW] in the title of the thread....
Click to expand...
Click to collapse
Your official mod is taking a break, just busy with life lately. I'll be taking over until he comes back.
I've forwarded this thread on to the admins, being that after being here for 2 days I can already see how bad it is. Hopefully we can get the sections split up and I can start moving posts around.
Can we please also have teh same tagging as HD2 section has, ie the date at beginning of title..
example...
[19.MAR.2011][ROM] Rom Title Rom Version [KERNEL]
is it possible to get this "stickie" out of the developers section?
it would be more helpfull to get serious content into there. also the actual official thread is sticky and dead.
a sticky should be something important or something must read. this thread is not a "must read"
sorry, constructive critics
I agree we need some reorg. PLEASE look at my sig, and follow the HD2 url,
Seems the HD2 overall section has recently had a makeover. It is much easier to navigate, and the people whe are not devs can op in on the thread.
The devs, on the other hand, have their own section, that requires you be a dev in order to get into it and exchange ideas. This keeps the riff raff from convelouting the threads.
So, can you please look it over. What ever work is needed to be done, I will offer my assistance to reorg the threads and topics.
Thanks
StarLog said:
I agree we need some reorg. PLEASE look at my sig, and follow the HD2 url,
Seems the HD2 overall section has recently had a makeover. It is much easier to navigate, and the people whe are not devs can op in on the thread.
The devs, on the other hand, have their own section, that requires you be a dev in order to get into it and exchange ideas. This keeps the riff raff from convelouting the threads.
So, can you please look it over. What ever work is needed to be done, I will offer my assistance to reorg the threads and topics.
Thanks
Click to expand...
Click to collapse
I just looked at HD2 section, and theres nothing new there.
They have a section for NAND dev, and for SD Dev, thats it.
There are some plans in the works for the site in general that may do what you're referring to, but nothing is done yet for any of the fora.
If they give you guys the new sections, It will take me a day or so to move everything around. And I dont know tis section as well as I'd like so it may take a little longer as I'd have to go through every thread, but it would get done.
/IF/ that happens, it should clean up the sections a lot and make it easier to find everything. If not, I'm open to suggestions.
I would like to learn how to develop Roms like the major bigshots on the Epic forum, can some please give me some advice on where/how to get started with this, along with things I'll need to start developing.
Thanks
Simply AOSP 3.1.1
masaidjet said:
I would like to learn how to develop Roms like the major bigshots on the Epic forum, can some please give me some advice on where/how to get started with this, along with things I'll need to start developing.
Thanks
Simply AOSP 3.1.1
Click to expand...
Click to collapse
I have no idea, but I am glad to hear that you want to learn to build some ROMs for us.
Good luck!
Thanks for the support. I just hope a rom developer would provide me the answers I need soon
Simply AOSP 3.1.1
Read, read, and read some more. Then read again. The info is around just scattered all over the internet. cynagon has a good post about it in the android development section. I would start with going there
First of all, I would recommend buying a book that teaches Java development, there are several available from Amazon (I recommend the Lewis & Loftus 6th edition, it's the one used in my Intro CS classes). Once you have a decent understanding of that, you can go to developer(dot)android(dot)com/sdk/installing(dot)html (sorry, can't post links as a new user) to get set up with the Android SDK and linking it with Eclipse. At the very bottom of that page, they have some guides to starting programming, like a "Hello World" application. Also, I read that Samsung recently came out with a developer's section somewhere on their site, which has some tips for beginning programmers. Finally, take apart some .apks, and try and understand some of what's going on inside them, and look at the sample projects included in the Android SDK.
Best of luck, and welcome to the other side of the community.
If you're old enough, I suggest looking online for nearby classes where they can teach you directly so you can fully understand it all.
Otherwise, feel free to take some of the other's advice, and figure it out by reading =P
Nevertheless, welcome to Development.
There's a thread somewhere specifically for it... brb digging...
Dug: http://forum.xda-developers.com/showthread.php?t=667298
learn about linux.
themes and most ui changes are java - download a rom, unzip it, and check out /system/framework or /system/app
you can open .jar files by changing .jar to .zip and extracting them
Thanks for all the advice you guys, umm I'ma start off by learning how to theme then work my way up trying to understand my phone a lot more than I do now
> 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