Develop Bugs

[NEW STICKY WIKI PAGES] - [Please Read]

***Due to popular request & in an attempt to clean up the Hero Forums, we have created several Sticky Wiki pages where you can find all current links to ROMS, GUIDES etc.***
HERO ROMS CLICK HERE
HERO GUIDES CLICK HERE
HERO THEMES CLICK HERE​
As is the nature of the Wiki please feel free to edit and place a link with a short description of your post. You can also edit the appearance of the page and how it is layed out.
Hopefully you will all add your relevant links to the Wiki and update them as required.
This will, in theory, provide a one stop Index page which should, if this works, be a useful resource to all.
This will of course only work if YOU, the users, keep it up to date and clean.
Sugestions and feedback are always welcome. This thread will be regularly cleaned, so dont be offended if your post disappears from here.

Wiki pages now up and running peeps. Please edit and update as necessary as some content has not been transfered or lost in cyber space

Where i can get WM6.5

Hi to all XDA Users!
Where i can get the latest WM6.5 Release for VGA? (for example the 21891)

It's in every Wallmart! Otherwise you can also use search function!

RAMMANN said:
It's in every Wallmart! Otherwise you can also use search function!
Click to expand...
Click to collapse
pls post me a link
i've tried to search but i didn't find anything

no I can't. you didn't even state if you just want to flash a custom ROM or build your own kitchen. and I have no clue what device you use. So just sum up this information for yourself and type it up in search field.

Please look in the relevant section of the forum for your device.
Otherwise, WinMo 6.5.x kitchens and dumps are available from: http://forum.xda-developers.com/showthread.php?t=544445

Help compiling a ROM please ?

I'm looking for a 2.2 Froyo rom, WITH HTC Sence UI.
pref, 720p recording, newest radio ect..
tried searching through the forum but can't seem to find one i like, most roms have been trimmed down..
couldn't understand the rom kitchen othervise i would compile my own..
any link for this kind of rom or if someone could compile it for me, would be highly aprishiated.
excuse my bad grammar.

Your kidding right?
I'd have a look again if I were you.

Please use search before posting! When you signed up to these forums you agreed to the forum rules, and the number 1 rule is:
1. Search before posting.
Use one of our search functions before posting, whether you have a question or something new to share, it's very likely someone already asked that question or shared that news.
Click to expand...
Click to collapse
Everything you need to know is here, but always search before asking.
Chef Central > Android http://forum.xda-developers.com/forumdisplay.php?f=613
Learn Android ROM development. For serious students only. This forum is monitored and moderated by seasoned developers.
http://forum.xda-developers.com/showthread.php?t=667298
cyanogen said:
Here's my advice for those looking to make their own Android ROMs.. Stop. Write an app or two first, learn how the system works from a developer standpoint. Learn some Java. Read the developer documentation. Learn how to use Git. Then learn how to build AOSP from source. Read the porting guides, and learn how the build system works (the links below have almost everything you could possibly want to know). Now try to put your new found skills to work on enhancing the platform by writing code or making theme overlays. And share! And put that **** on your resume. There is a *ton* of information out there but any kind of "step-by-step rom cooking guide" is going to be a complete fail- it's too broad of a subject.
Android Developer Guides: http://d.android.com
Working with AOSP source: http://source.android.com
Platform Developer Guide: http://pdk.android.com
Android Gitweb: http://android.git.kernel.org
Git Ready (Git tips and tricks): http://www.gitready.com/
Building CyanogenMod: http://wiki.cyanogenmod.com/index.php/Building_from_source
How Dexopt works and what are those odex files: http://android.git.kernel.org/?p=pl...bcd225e47b2cc7abb2a366112d3aeb45936;hb=master
The PDK site is absolutely vital if you are going to work on custom ROMs. Read every single page. Twice. Some of the info isn't up to date, but you'll get a really good idea about what goes into actually configuring Android to work on a real device.
Click to expand...
Click to collapse

Klutsh said:
Your kidding right?
I'd have a look again if I were you.
Click to expand...
Click to collapse
It's quite hilarious now when I read it again. How %&¤/"# some people can be

Expand the forum into a wiki

I've got to say that these directions on this website are some of the hardest to follow. I think that the xda-developer website should be maintained as a wiki rather than a forum (or at least the main section should be a wiki). When I go to wikipedia, I don't have to sift through twenty posts to find out the history of 'Nevada' or the chemical makeup of 'acetaminophen.'
I understand that this web site is made for experts, but I've got to say that I've found many others who have scoured the website for information specific to their particular situation and gotten lost because that information is sandwiched between two threads and then between two other posts. Then they start a new thread and get chastised for posting about an issue that has already been hammered out in another post.
Conversely, I find that the simple instructions--like those found on youtube--simplify the instructions too much. The instructions work great for a select few, but most people run into problems during the install and have to turn to xda-developer to find more information.
A wiki would solve both of these problems. First, it would eliminate the knee-jerk reaction of noobies to just post their problem without reading. They would only be allowed to post to the forum if their particular problem wasn't resolved in the wiki. And if a lot of noobies kept posting about a problem that's already been solved, it would be up to the editors of the wiki to tweak the article to minimize confusion.
Secondly, with a bunch of experts working together to simplify the complex information means that they could have simple instructions with specific links for the situations where those instructions would not work. Some of the forum posts are like this, but they are few and far between.
The wiki that currently exists is mainly for information about the phones, not detailing instructions for development.
The reason I decided to rant was that my wife asked me to root her NookColor 1.3.0 and I proceeded to gather data on this process. I went to this post http://forum.xda-developers.com/showthread.php?t=1054027 and started reading the instructions for 1.3. It stated "2. Copy onto your flashable CWM SD card using Windows Explorer." I asked myself "How do I get a flashable CWM SD Card?" After some snooping, I found the instructions above 1.3 (in 1.2) where it stated "CWM Bootable from SD Card: http://forum.xda-developers.com/showthread.php?t=987735"
I followed the link and it was this next page that got me. It has 6 different links to different versions of CWM, instructions regarding uRecImg and uImage files (I do not know what these are) and an admission in the first paragraph that the author will no long actively edit the thread. If this were a wiki, someone else could take the baton.
Please write back, as I'd love to hear from the community. I'm sure there's a plus to the forums; however, so far I haven't seen it.

The issue is that if anyone can edit content, then it cannot be trusted or treated as reliable...
Trolls could easily adjust commands so they would break devices.
The only way to let people see how reliable content is, is to ensure it is only editable by the named author, with their profile showing previous details to help decide if they are reliable or not...

"How do I get a flashable CWM SD Card?"
Click to expand...
Click to collapse
If you come to a forum like XDA it should be to learn, which involves a lot of reading and depending what it is and on what device you wish to do it, a lot of practising. The answer to the question I've quoted is on the first page of your first link, which is why its always a good idea to read the first few pages of a thread, as certain things that aren't understood in the OP are answered in the first few pages.
Sent from my LT15i using XDA App

Why do ROM developers put BusyBox in their ROMs?

Why?

It is needed to have root on your device. Google it, to get more details
Sent from my HTC One X using xda premium

I myself dont know and it would be nice to have an explanation here as most of us are new to this rooting and bricking jargon simple explanations of these things will help "COMMUNITY" members hence why we have a section
HTC one X Q&A
It very easy to tell someone Google it
as Einstein said: "If you cannot explain it simply then you don't understand it well enough"
check this video out I found it, however I cannot view it due to Admins blocking Youtube http://www.google.co.za/url?sa=t&rc..._92TCg&usg=AFQjCNGRf354aisVBQXiO8jVypBAj91PLg
Edit:
Not my intention to be Rude but this is a Q&A and we need to be helpful as a Community not make people not want to ask questions

BusyBox is a package containing a whole range of "program commands" and/or "scripts" (tools). It is with these extra tools, specific tasks can be performed.
Once a custom ROM has BusyBox installed, it means that scripts on the ROM and apps in the ROM can use make use of the tools to perform their tasks.
For example "dd" is a known linux command/tool for block-by-block copying and dumping. However "dd" does not exist until BusyBox is installed. Other popular tools are "uname" to get the kernels name/details, and "ls" is to list the contents of a directory/folder (similar to "dir" in DOS). There are about 50 or more of these commands packaged inside "BusyBox". Whenever there are new versions of BusyBox installed (as you may see in the changelogs for some custom ROM's), this is simply because BusyBox has included either new versions of some of its tools, or perhaps added additional tools to the package.
Hope that helps answer your question. However to be honest, I found all that out by SEARCHing this forum.
- WizzKidd

wizzkidd said:
BusyBox is a package containing a whole range of "program commands" and/or "scripts" (tools). It is with these extra tools, specific tasks can be performed.
Once a custom ROM has BusyBox installed, it means that scripts on the ROM and apps in the ROM can use make use of the tools to perform their tasks.
For example "dd" is a known linux command/tool for block-by-block copying and dumping. However "dd" does not exist until BusyBox is installed. Other popular tools are "uname" to get the kernels name/details, and "ls" is to list the contents of a directory/folder (similar to "dir" in DOS). There are about 50 or more of these commands packaged inside "BusyBox". Whenever there are new versions of BusyBox installed (as you may see in the changelogs for some custom ROM's), this is simply because BusyBox has included either new versions of some of its tools, or perhaps added additional tools to the package.
Hope that helps answer your question. However to be honest, I found all that out by SEARCHing this forum.
- WizzKidd
Click to expand...
Click to collapse
^^ hit the nail on the head. That's not to say that busybox is the ONLY way to get those tools. It's just the slimmest. There are more robust gnu equivalents of the tools that it includes, but they're nowhere near its tiny footprint.
Busybox is a pretty neat application though, since all of the tools that it provides are housed in one binary (busybox). The other commands operate with symlinks named appropriately for their function (su, etc.). The binary detects the name of the symlink that invoked it and behaves appropriately. It's commonly used in environments where not much space is available (recovery environments, embedded systems, etc.)
--Matt

jinkira said:
I myself dont know and it would be nice to have an explanation here as most of us are new to this rooting and bricking jargon simple explanations of these things will help "COMMUNITY" members hence why we have a section
HTC one X Q&A
It very easy to tell someone Google it
as Einstein said: "If you cannot explain it simply then you don't understand it well enough"
check this video out I found it, however I cannot view it due to Admins blocking Youtube http://www.google.co.za/url?sa=t&rc..._92TCg&usg=AFQjCNGRf354aisVBQXiO8jVypBAj91PLg
Edit:
Not my intention to be Rude but this is a Q&A and we need to be helpful as a Community not make people not want to ask questions
Click to expand...
Click to collapse
The main reason people here get told to Google a problem is because more likely than not, the answer you'll get from the search engine will be a page from XDA...
There's also a search box within XDA too, I found these pages using it, they would have answered the OPs question, there wasn't really a need for this thread.
Not trying to be rude but the search is there for a reason and these questions have been asked hundreds of times before
http://busybox.net/FAQ.html#whatis

thank you all for the feedback it is much appreciated
oh and I did do a search but only on the HOX forum not the entire site, and Searching only th HOXX forum there were fragmented pieces of info, but anyways Thanks you guys