Related
Hi guys,
so, as there are some possibilities, and the question arised, here's a little poll for you.
It's about how developers and users/testers of Android should best communicate.
Quick overview:
This thread has 4k+ entries now, but many people are watching it. It's more like an IRC channel, though.
The Linux-To-Go site has 4 different trackers (bugs, patches, support, feature requests), and a news system and a little bit more. Sometimes it is quite slow, but since they've just got a new sponsor, I think they're working out how to distribute the load.
I have already asked whether we can have a subforum, and the site admin seemed positive about it, but wanted to see into which directions the Mod's discussions were.
If you have a better idea, please post!
Stefan
I prefer the googlecode bugtracker, since the most people dosnt need to create an new account, it is simple but powerfull. And the ui looks much better then the Linux-To-Go one.
Looks like guys here voting mostly for just subforum. May I suggest in this case that there would be few sticky topics for guides/overall discussion and the rest is topic per bug type-o-thing? Someone would be a moderator, of course.
it doesn't even matter what we / you think - the only votes that matter are the ones of the developers.
git seems to work quite well for developing - if ltg is too slow - it shouldn't be a problem to clone it to a faster repo elsewhere (afaik there's already a faster one in place - can't remember the address) - also after the initial setup it doesn't really matter how slow it is anymore (unless you don't know how to use git and constantly start over from scratch).
As for bugtracking - are there developers interested in bugtracking? I think they're well aware of what needs work.
(e.g. for Polaris it's documented in the wiki)
What we really need at the moment is kernel developers for various devices.
just my 2 ¢
Tip
I don't dislike the idea of a full thread as it was...but i feel we should split threats into 50 posts. After could be "Part II" , "Part III"...etc.
Hugs
excogitation said:
As for bugtracking - are there developers interested in bugtracking? I think they're well aware of what needs work.
(e.g. for Polaris it's documented in the wiki)
What we really need at the moment is kernel developers for various devices.
just my 2 ¢
Click to expand...
Click to collapse
Actually, I suggested a bug tracker, even for developers-internal use because then one can see what the other devs are working on and that one doesn't have to care about the problem...
More developers would be good, of course!!
Stefan
seidler2547 said:
Actually, I suggested a bug tracker, even for developers-internal use because then one can see what the other devs are working on and that one doesn't have to care about the problem...
Click to expand...
Click to collapse
There is more to it. First, more eyes will be able to find more bugs. Second, bug tracker allows instead of keeping all bugs in head, constantly trying to remember them all, keep in head only one on which working currently, while the rest is recorded in database according to their priority. No one has superhuman memory. Also, bugtracking important because people generally happier with product that is with not too many features but robust rather than product with whole bunch of awesomeness but also hosting whole hive of bugs. Here's good article on bugtracking.
Thanks MooNWalker. Seems we should try to push a bit more for a subforum, and use the bugtracker for the reasons you said. We should see if the LTG one can be extended so that people will not have to sign up in order to make contributions. The site itself seems fast right now.
Stefan
Ok, we will try with the bugtracker.
Go here to see the bugs and to enter new ones.
Stefan
@seidler2547: Can you change something there? It is currently not obvious that this is the bugtracker for Kaiser Android. You have to know that this is the right place there. If i was new here and i what to fast post a bug, i will be very confused if the bugtracker is the right one.
Hi lanwin, dzo set up the tracker name. Anyway, it is a bit cryptic because it is not only for Kaiser Android. It is for running Linux (and with it Android) on MSM7x00 devices, that is Kaiser, Nike, Polaris, Vogue and so on. We have a common hardware base, so we coordinate our development. You know you're on the right bug tracker because -> the link here says so, and -> this is the only one in mobile-linux you can report bugs without logging in
Having said that, we can think about the name nevertheless. What do you suggest?
Stefan
Hi Stefan, yep i know that but a non technical user wouldn't do. Even if it is ugly, i suggest "Android for Kaiser, Nike, Polaris, Vogue (MSM7x00)".
Anyway, thanks for bringing Android for this platforms forward!
new sub forum
i think a sub forum is good because it will allow for more specific threads.
it will also allow us to get an rss feed of all things android
finally, can't the current long thread just be moved into the sub-forum? no one will be forced to start or look at new threads, but it will be there.
Does it really affect anything in a negative way or preclude the other options?
Android development is only going to pickup, and i expect we will see a corresponding drop off in WM.
Lets think about what the development scene is going to look like in 2 years... even after we've all moved on from our current phones.
The question is: Can/Should/Will xda-devs be the place for android development too?
seidler2547 said:
Having said that, we can think about the name nevertheless. What do you suggest?
Click to expand...
Click to collapse
Put link to bugtracker in Android on HTC wiki. Might be helpfull to put it in first post on main thread.
I think this bugtracker was for the full Android port, but it seems that it is only for the kernel so all my bugs are closed with "This is not related to this project (Linux kernel for mobile devices) but to the google android user space and must hence be moved.".
Where to report user spaces related bugs?
That is a good question. I have seen the close, but I'm not too happy with it, although I understand the reasons. Maybe we need to make an extra google bugtracker, as someone suggested.
Stefan
I think the original android post has really become quite cumbersome, I voted for a subforum but I don't really care as long as I am able to see what is going on. The old post has become unorganized there are a bunch of different sites and stuff on that post to get builds and kernels and what not from and I have become somewhat confused with it all. I am curious though as to how many people are actually working on this at our end the only one I see actively posting is seidler is dzo or polypoly still working on it. I'm having problems getting some of the files required listed on source.android.com fiqured I would give it a wack, probly a short wack.
seidler2547 said:
That is a good question. I have seen the close, but I'm not too happy with it, although I understand the reasons. Maybe we need to make an extra google bugtracker, as someone suggested.
Stefan
Click to expand...
Click to collapse
This was me I am against a sub forum. Forums are very bad in cases of a bugtracking functionality because there is no bug management available and users tend to use one thread for bug reporting, questions and discussion where it is really hard to find out the bugs for the devs.
I think there should only be one bugtracker for the users because the most of them can not distinguish between user space and kernel space bugs and requests.
I suggest to open a user friendly google code bugtracker and some of the devs move bugs related to kernel space over to the other bugtracker.
Hi
These last days, and this is a joy, a few new/or not developers are beginning to create roms on ICS.
Each rom has a difference with others, and i noticed some roms has qualities that are not found on others, but need the advantages of some others.
A few users asked it before, i offer today with this thread (i hope this is not a mistake, and that it will remains clean), to vote. The target is to ask to our developers to create a sort of developing team, around a "unic" rom.
Their competences put in common should be awsome, don't you think?
If you want to help me to make this thread known by developers, do not hesitate to link it in your signature, by this way, dev in the development section could see the result of the vote, that i hope to be YES
Thx for your responses, and please take this thread clean
Want a good idea !
Google is doing this. Wait for the official release...
Sent from my Nexus S 4G using xda premium
It is called the CM team.... facepalm
FYI, Koush is an integral member of that team (not that they have been working on ICS as a team yet)
This is a terribly biased survey. Where's the option for "No, we'd like to see a diverse selection of Roms"
With all due respect, "Nope, i prefer lot of partially working roms" is a very suggestive option, that says you're critical of the current work, or just impatient.
Seriously dude, ics JUST CAME OUT. Teams will form, and work will get done in due time.
Patience, grasshopper.
Have you no humour?
If you say no, indeed it can be for other reasons..
In fact, the target is to reach an almost stable and fully functionnal BEFORE the official release...
after this, no need to have a team, on a official base, a dev can do something good alone.
As you like to call me grasshoper, and with all the due respect , i would like to call you embittered cod-fish.
Does it fit enough to you sir?
Dear All,
Excuse me if I start a new thread here but it is my understanding that certain questions are not to be made in the development section.
I know much has to do with personal taste, your own experience and research, but I am coming from an HTC Aria, and I am looking for a custom ROM for my Inspire.
There are many ROM's posted that I know and appreciate have a lot of hard work and dedication from developers and unconditional testers and followers, as for instance the specific ROM thread for BinDroid's ROM itself alone has close to 900 posts, so please don't be offended by my questions, as for what I have seen and managed to read it seems to be that this might be what I am looking for:
Is this a stable ROM for daily use?
Are there any trade-off's / sacrifices (camara, video, flash, sound, buttons, gps, etc? that don't work or have limitations?)
I can understand that for many long time users and followers there can be "known issues" , but please understand that for newcommers these are not, so your kind comments will be most welcome.
I thank you all for your support and look forward to your answers and any recomendations that you may have.
Cheers!
I would say this Rom is stable for a daily use. For awhile I was running this Rom for little over 2 months. It's very clean. Its one of the handful of roms out here that works form start to finish. The support from the inspire to the desire hd threads for this is very quick if you had any issue that you may come across. I couldn't remember the last time I.had any major issue when using this. Battery life is great if you do a lot of Pandora browsing uploads like to fb etc. Works for me with my inspire. So would differently say flash this sucker.. its worth it.
If I remember right the only thing I did was a different kernel and a uv script lite other then that bad ass.
Sent from my HTC Inspire 4G using XDA
Stormglider said:
Dear All,
Excuse me if I start a new thread here but it is my understanding that certain questions are not to be made in the development section.
I know much has to do with personal taste, your own experience and research, but I am coming from an HTC Aria, and I am looking for a custom ROM for my Inspire.
There are many ROM's posted that I know and appreciate have a lot of hard work and dedication from developers and unconditional testers and followers, as for instance the specific ROM thread for BinDroid's ROM itself alone has close to 900 posts, so please don't be offended by my questions, as for what I have seen and managed to read it seems to be that this might be what I am looking for:
Is this a stable ROM for daily use?
Are there any trade-off's / sacrifices (camara, video, flash, sound, buttons, gps, etc? that don't work or have limitations?)
I can understand that for many long time users and followers there can be "known issues" , but please understand that for newcommers these are not, so your kind comments will be most welcome.
I thank you all for your support and look forward to your answers and any recomendations that you may have.
Cheers!
Click to expand...
Click to collapse
Let's first start with, welcome! Secondly, while you're correct dev threads are typically (depends on the dev team or individual developing the ROM) are reserved for development, there are Q&A's for each respective ROM that you should use to ask questions regarding a specific ROM. If everyone created a separate thread about each question they had for each ROM they use you can see how chaotic the forums would get.
The best way to figure out what "issues" a ROM has is to read some of the recent posts in both the Q&A and Dev section, you'll see there what most people are dealing with. Most ROMs here are pretty stable and I would say fine for daily use (ICS has some minor bugs due to source issues but from what I'm seeing there are a couple of somewhat stable ICS builds).Remember this is a development site, so some independent searching and reading is expected on your part.
As for Bindroid, I used it way back when they firsant started with sense 3.5 and loved it. Danny and the team are real nice guys and do great work. I would say that ROM is more then capable of being a stable, daily driver. Just remember, only you can decide what you can live with and c live without. All ROMs come with trade offs, some users don't mind them and don't even consider them trade offs or issues which is why you need to decide for yourself. Goood luck man!
I am a computer science graduate that is looking to work on an existing ROM project in my spare time (ideally a popular one like CM10). How would I go about this? I don't mind starting small (doing code reviews and such), but I would like to be able to work up to actually submitting fixes and being part of a 'team'.
I don't have any specific Android development experience, but I know Java well and use it every day at my job. I am just not currently a part of any code projects in my spare time and would love to do something Android related now that I finally have one (even better if I could work on .
So...is this possible? What steps can I take towards this goal? Or is this a situation like 'you've got a lot to learn before you even think of joining a project'. Again, I have no Android-specific dev experience, but I learn quick and am eager to be a part of the Android development community. I want to be part of an existing team because I feel my strength lies in developing fixes and features, not in designing a ROM from the ground up.
Thanks in advance to anyone who replies and sorry If I shouldn't have posted this in a more specific Q&A forum as well.
Exoplanet25 said:
I am a computer science graduate that is looking to work on an existing ROM project in my spare time (ideally a popular one like CM10). How would I go about this? I don't mind starting small (doing code reviews and such), but I would like to be able to work up to actually submitting fixes and being part of a 'team'.
I don't have any specific Android development experience, but I know Java well and use it every day at my job. I am just not currently a part of any code projects in my spare time and would love to do something Android related now that I finally have one (even better if I could work on .
So...is this possible? What steps can I take towards this goal? Or is this a situation like 'you've got a lot to learn before you even think of joining a project'. Again, I have no Android-specific dev experience, but I learn quick and am eager to be a part of the Android development community. I want to be part of an existing team because I feel my strength lies in developing fixes and features, not in designing a ROM from the ground up.
Thanks in advance to anyone who replies and sorry If I shouldn't have posted this in a more specific Q&A forum as well.
Click to expand...
Click to collapse
Your best bet is to start by trying to build a CM rom from source, play with GIT and get used to building android from source, then look towards a device you own, if there already a CM verion for it? if so perhaps talk with the dev thats in charge of it and see what you can help with.
Okay, deferring to the wisdom of the elders on this question. I've been all over the place with ROMs, TW and AOSP, but I'm heading to college in a few weeks and I'm looking to "settle down" with a ROM and ride it out until my upgrade in November. Is there a clear winner out there right now in terms of stability/battery life that still has some cool features? I'm very minimalistic and I don't need to be able to customize every single facet of the UI, but rooted stock is a bit too dull for me! I'm on CleanRom 8.2 atm and it's good but not great, I'm really looking for the ultimate daily driver ROM and kernel, please advise a lowly serf such as myself.
I don't believe the rules of XDA allow a "what is the best ROM" thread, so you may not get a simple answer (and to be honest, people have different priorities in what they want or need from a ROM, so what may be best for them may not be best for you).
That said, perhaps the best approach would be to look through the Android Development and Original Android Development topics and look at both the early posts (the OP, plus a page or two after), and the last page or two to get an sense of the install, the features, and the level of support you might get with each ROM. You will also be able to eliminate ROM's that are no longer supported (eg, I believe Scott is no longer supporting CR, so even though it was/is a great ROM, perhaps not the best to consider).
Also google the ROMs to see if there are any YouTubes showing the install and use of the ROM. There are many good reviews of ROMs and seeing them in action is a big help.
Last, a number of ROMs are being discussed on Google+ so you may want to check out that resource too.
And, it may also be a good idea to actually try the ROMs on your phone. ROMs can act differently on your phone than they might on mine.
Hope this helps!!
My recommendation is read all the rom threads as much a you can and experiment by trying them out. "Best of" rom threads are frowned upon because it generally discourages people to read and learn. I am going to close this and trust you will be able to find what you are looking for with some diligence and have fun trying. Thats what makes this site great!:good: