How can we help developing
 

how can everyone else on here help out the developers or help to develop a working build?

Re: How can we help developing
 

Good idea... I say next we try to get the audio working than start working on the inner tweaks "gps, messaging, ringtones, etc"...

However, i'll be pissed if Android gets video ringtones before us daily WinMo users get'm lol..

Re: How can we help developing
 

By answering other peoples questions so the devs don't have to and then they spend more time on fixing things.

Re: How can we help developing
 

Yeah alot of us sit hours a day answering pretty much the same stuff all day. I have learned alot so far though and it's been fun!! just glad we have our own home now!!!

Never thought I would prefer a phone without sound over Windows lol

Re: How can we help developing
 

wish i knew what was wrong with mine, was on the phone last night with my GF and android crashed and restarted the gui on me.

Re: How can we help developing
 

wsh i knew linux

Wirelessly posted (Opera/9.5 (Microsoft Windows; PPC; Opera Mobi/17992; U; en))

if you knew linux i doubt you would be here. you would hate anything windows.

Re: How can we help developing
 

Well, apart from answering questions, is there any other way we can help? Would the developers like us to create a list of problems that we come up with, or note things that work for us?
I feel like just answering questions isn't enough. But if that's what will help, I shall do my best.

Re: How can we help developing
 

Yeah all that will happen if you post what does or does not work will clutter this thread up even more so than it already is and we already have allot of people that do that. I am sure Pippy and Civic know what does or does not work with there builds and are working on fixing/ enabling the features. I think that the thing that everyone has to do before posting anything (really in any thread, not just this one) is take the time and read through the entire thread to catch up on what has or has not been mentioned already. I know it is allot of reading sometime, how ever if everyone does not take the time to catch up and read though the thread, its just going to get even longer and longer and really be ridiculous for anyone to even find anything that is actually relevant to getting this to work. I just think that if you want to help out and have knowledge that has not been posted already, go ahead and post it if you think it will really help with the Dev or troubleshooting possible problems, otherwise just help answer some of the noob questions that have been posted over and over and over (I would just say to ignore them but if we do that they will just continue to ask)

Wirelessly posted (Opera/9.5 (Microsoft Windows; PPC; Opera Mobi/17992; U; en))

The main goal is get everything working then go for the smaller things like bugs and making sure all the apps work. Basically hold off on reporting bugs till the devs ask for them and just play with what we have for now.

Re: How can we help developing
 

CDMA developers will to some degree follow the foot steps/footprints/blueprints of GSM developers. Just encase if everybody dont know GSM users (TMo TP2 & ATT Tilt2) are at 100-110% functionality on the AndroidOS. They had a head start due the mass base of GSM users WORLDWIDE...!!! We (CDMA users & developers) are playing catch up and learning from some of their trail and errors. And working hard behind the scene s with key players.

What we can do as ppcgeeks.com (largest CDMA WM site) members is tighten up on the noobish punch drunk posts and directly help by advising members to read alittle more. I'm not saying dont help other members but there is a thin line between helping and enabling.

The first date is over, we like the click (Android) and we want more than a one night stand. So lets court her, wine and dine this baby into long lasting relationship.

CDMA Android Development will reach 110% before we know it. To the all helpers keep helping and enablers stop enabling. XDA.Developers.com dont even play ring around the roses.

If you want to help Developing try some new stuffs. Like putting together your own Android package folder based on the information, software etc thats already out there on websites. And trying it on your own PHONE, like I did. There is no real way to Brick your device. Nothing a soft/hard reset or even flashing a custom thru the sdcard couldnt fix. I'm running a mix of things that I took my time and packaged up for me.




Only the born to win ppcgeekers will read this post and receive the positive.

Re: How can we help developing
 

+1 I agree the posts are out of control in some threads. I find when searching the forums I then have to search the thread and that still doesnt narrow down the garbage enough to make it mangeable to find specific answers and I think maybe that is why we have so many repeat thread posts that contain the same questions.

Re: How can we help developing
 

As I have suggested in other threads, update the wiki at http://androidonhtc.com.

This will cut down on clutter.

Read through the thread(s) and pick out questions and answers that are often asked and add them to the FAQ. Then promote its use as a resource for all the common questions and concerns. It really is the best way to organize all the data and hopefully cut down on the constant repeat questions. Threads reaching a 1000 posts a week are difficult and frustrating to keep up with.

This to me is one of the most basic ways to help, anyone can do it, and yet it is probably the most helpful next to developers working the code.

So pitch in, it only takes a rew minutes to update something.

Your contributions will be greatly appreciated by the community.

Re: How can we help developing
 

+1...Well said...!!!

Re: How can we help developing
 

i was wondering if anyone could make a vid which shows how one would about installing android on a TP2 this would not only help me, because i wana know how to do it without breaking my phone haha, but like u guys have mentioned help by reducing the question developers have to answer

Wirelessly posted (Opera/9.5 (Microsoft Windows; PPC; Opera Mobi/17992; U; en))

It is 4 steps.

Download the package.

Open the folder and drag and drop everything to the SD card.

Take out sim card.

Start haret which is on your SD card.

You are not booting android. Congrats.

Re: How can we help developing
 

1. download and unzipp the package, copy and paste everything to the root of the sdcard. Root: meaning front and center of sdcard, not in a folder or anything. front page of the sdcard. click on haret.exe....BOOM

2. You cant damage your device doing this. Worst case soft/hard reset the phone. But I highly doubt it, this run from the sdcard and not the device.

Re: How can we help developing
 

How do I put this delicately? Ummmm, no. They aren't anywhere near 100% functionality

Wirelessly posted (Opera/9.7 (WindowsMobile; PPC; Opera Mobi/35267; U; en; Presto/2.1.1))

thx for the reply and gentle feedback on my post. i will check with my orginal resource plus a youtube vid on att tilt2 running android. to make sure i iron out my maybe suppose facts. but i know they being gsm users are so far ahead it may seem like 100 percent compared to us cdma users. will post more accurate info later tonight with links.

late,
ib1

Re: How can we help developing
 

70% I'd say but more than enough for many to switch to android
3d is not working fully nor are a few other things (speaker phone/ sound)
but its pretty stable battery life is about 6-8 hours and by in large development has been fast

Re: How can we help developing
 

Last I checked, CDMA and GSM are both missing the same features. MrPippy built his rootfs off the same gitorious codebase everyone else is using, plus we both use the same kernal and initramfs. So unless something happened in the last day, which I don't see in the rootfs changes, CDMA and GSM are pretty much the same

Re: How can we help developing
 

Like I said I will post what information I have sometime to tonight.. And if I stand corrected I stand as a Mann.

Re: How can we help developing
 

As promised whether its enough or not here it go:

Fact still stand that GSM users are ahead of the curve, by what percent I'll let you grade it . Keep in mind this video was made on 01/28/2010...enjoy

http://www.youtube.com/watch?v=xQUIC...eature=related

1. marketplace,browser, ability to make calls w/ working speaker etc was running on gsm _ 01/28/2010

2. marketplace,browser, ability to make calls w/ working speaker etc was running on cdma _ 03/xx/2010




late,
info[]box1

Re: How can we help developing
 

How so? Because I'm looking all over gitorious, and I see nothing that gives them any more features than we have already. What do they have that we don't that's putting them ahead of "the curve" right now? The fact is, with girourious, we share a common source. What they have, we have. What we have, they have

As far as the information you sourced, you couldn't be more wrong. I could make calls in Android with the builds I put together back in December. Plus, it doesn't really help validate your point when we're talking about the current state of things

Re: How can we help developing
 

Guys, the point of this thread is to determine how we as users can assist the developers in furthering the Android port. I am pretty sure that arguing over who is ahead on the development (CDMA/GSM) is not helpful. I am very interested in helping out and I have fairly high technical knowledge and would be willing to do anything possible to help out. It looks like the most we can do at this point is to help answer posts and I will do my best.

Re: How can we help developing
 

I was unaware of the ability to make calls with a working speaker in December. (Working speaker during a call) was brought to my attention in one of the later releases of March.

Bottom line... I stand corrected.


Agreed and thanks hit.

Re: How can we help developing
 

I'm a college student and I've been developing software in one way or another for about 7 years now and I was wondering if there is anything I could do on that end to help with the progress. I'm familiar with OS/Kernel development (though not neccessarily for phones), most common languages (C/C++/C#/Java/etc), and of course I have a TP2. Where do I begin?

Re: How can we help developing
 

I am giving this a bump. Is there any way that we can help the devs? I have quite a bit of knowledge about the *nix environments and have plenty of time to devote to this. If there is anything I can do please let me know.

Re: How can we help developing
 

If you are comfortable with the kernel, there's info on how to get your own build environment going at:

http://www.androidonhtc.com/wiki/Get_Involved

Then it's time to just start poring over the code in arch/arm/mach-msm/ and looking at the git logs to see what's getting worked on. To my eye, the two most glaring missing pieces right now are the device speaker and (passable) battery status. The battery stuff has come along a great deal in the last couple weeks and will probably take some more steps soon. Audio has gotten no attention.

Start looking at code, start lurking at #htc-linux on freenode, and wait for the clouds to part. That's how to help if you're not afraid of C.

If you are afraid of C, +1 to helping out with the wiki, making the project clearer for people who want to try it out (and may in turn want to get involved with helping themselves).