Database Info

Poll Suggestion

I've been reading your board for the last three days trying to identify which ROM would be best for me to install on my new AT&T Tilt.
While there's a lot of great information in these threads and user signatures, it would be helpful to me if some of this information was consolidated at the top of the board. For example, I'd like to know the number of users who currently used each ROM. One way to do this is with a sticky poll.
I suggest that the moderators include a sticky poll in the Kaiser ROM development board listing all available ROMs (cooked and OEM) for the Kaiser/Tilt/TYTN2 and asking users, inter alia: (1) which ROM they presently have on their machine and (2) which ROM is their favorite.
Of course choosing a ROM is a personal matter, but why not harness the power of collective preference to better inform our decisions, and give meaningful information to developers who could use the information to refine their recipes.
-DarthHammer

mmm..a suggestion like many, but unworkable to update this by Mod's.
Some people scream each 5 minutes that THIS one is their favorit.
And some chefs cook 5 roms in 10 days,
before this thread goes down by the mod Squad, read read read. And 3 days is nothing (except if you call it 72 hours)

ceevee369 said:
mmm..a suggestion like many, but unworkable to update this by Mod's.
Some people scream each 5 minutes that THIS one is their favorit.
And some chefs cook 5 roms in 10 days,
before this thread goes down by the mod Squad, read read read. And 3 days is nothing (except if you call it 72 hours)
Click to expand...
Click to collapse
Agreed. Reading is the only way. What works for some, may be terrible for others.
Read the first couple of pages for each rom to help you in your decision making.
Also, if you read a little deeper than the first couple of pages, you can find out if there are any issues related to the rom that might affect you.

ROM: Fastest Non-Buggiest ROM available?

I've spent countless hours going through the forums...

Out of all of the roms that I have tried I would claim eOS is the fastest non buggiest rom out there. It is very streamlined and fast, and I had 0 bugs when using it, if that is all that you are concerned with. It is lacking in some features by default, letting users personalize it as they wish.
Jason

How was responsiveness? Do you know if there are any benchmarks out there (I'm lazy, thought I'd ask for a direct link before looking it up...) for it?
Forgot to also ask; with any of the ROM's - which one's are most friendliest when it comes to adding new cabs? I guess my goal is utilize the processor and... add those things we all like to screw around with for a week or two and decide if its worth keeping. Usually in my case, if it causes my phone to freeze, it's off to the next choice...

hkjr said:
I've spent countless hours going through the forums and figured I'd ask. Please note, I'm asking not for your opinion, or what you're favorite ROM is, regardless what drives it or what extras are on it... I'm asking everyone for some facts - as of today, 12.13.2008, who has the fastest, non-buggiest ROM around? ROM's are buried everywhere and some include benchmarks, others don't. I'm on AT&T and a,s of last night, went back to the OEM 6.1 ROM.
Click to expand...
Click to collapse
There is no way to have software and not have bugs. NOTHING is going to perform EXACTLY as you want it to right out of the box.
To see what everyone WOULD respond to your message with if they wanted to - look at their signature - why would they use it if they thought it was buggy or bad?
You are going to have to configure your phone no matter what. You will get (if the mods let this thread stay open) many opinions (just like the zillions of other threads that ask this question) from people who have not gotten tired of answering it.
The only way to find out what you like and what is non-buggy in your opinon you are actually going to have to download and try each of the ROM's.
Sorry - I wish it were simpler than that - but it isn't.
Two posts and you have already violated a rule this is not going to go well obiwan!
The rule:
If you post a redundant thread, SPAM, flame or violate any rules. Your thread will be closed or deleted without warning. Useless threads like those that address an issue such as "Which ROM is the best," "Kaiser vs iPhone," or "Kaiser Killer" will be closed. You could also be banned for violating the rules.
To find a list of the rules:
http://forum.xda-developers.com/announcement.php?f=378
You state you have read a lot - I believe you - there is a lot to read. But - you are going to need to read even more to make yourself happy I am afraid.

Thanks for the input - that's why I was/am looking for stat's/results/screen shots of benchmarks, etc - just the facts.

The best way to find the answer to your question is to read the rom's threats, put the doubts about the rom's there and flashed then.
And you'll be a flash addicted like me.

This one screams...its the fastest one I have found yet......and the memory...oh the memory available is the best yet too. Give his one a try.

hkjr said:
I've spent countless hours going through the forums...
Click to expand...
Click to collapse
if u have spent countless hours reading the forums you should know that you should not be starting new threads, filling up our forum with questions like this!

gregaplummer said:
This one screams...its the fastest one I have found yet......and the memory...oh the memory available is the best yet too. Give his one a try.
Click to expand...
Click to collapse
When you say "this one" to which one are you referring too....

As posted in countless other places, all "best rom" threads will be closed.

[Android] [POLL] Bugtracking/Communication system

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.

Which kernel for my Nexus S? suggestions...

I have been looking on the forums at several operating systems for the Nexus "s" and i really dont know which one is really good with battery and with a smooth snap performance, there's just so many to choose from and its confusing to me as im a new user to android and learning it all.
anyone have suggestion for a modern good working kernal which isnt in test form, thats great with battery and has snap smooth performance, iv seen good ones on the forum, but as i said im new and not certain and rather experienced user opinions.
Thank you.
oh, and i saw a thread, a user said he lost only 3% of battery on idle throughout the night using a certain operating system, but i cant remember the thread..

dinjc said:
I have been looking on the forums at several operating systems for the Nexus "s" and i really dont know which one is really good with battery and with a smooth snap performance, there's just so many to choose from and its confusing to me as im a new user to android and learning it all.
anyone have suggestion for a modern good working kernal which isnt in test form, thats great with battery and has snap smooth performance, iv seen good ones on the forum, but as i said im new and not certain and rather experienced user opinions.
Thank you.
Click to expand...
Click to collapse
I would go with the ICUP Kernel Edition (http://forum.xda-developers.com/showthread.php?t=1401455)
Good battery life and smooth performance.

Your best course of action is to not create a thread asking for people to do things for you.
Go sort the Android Development forum by Stats and find the most popular kernel. Read every word of the OP and however much you possibly can of the thread itself. It might take a day or two just to properly educate yourself and get some background. Flash the kernel, use it for several days, and then and only then make an assessment of battery life and performance. After you have done this, go back to the kernel's thread and make a post documenting your experience and what did and did not work for you.
You've registered this month, you have 5 posts, and you've created 2 threads that are completely pointless. Try to contribute something. What I outlined above is possible for anyone no matter what their knowledge level.

watch this https://docs.google.com/spreadsheet/ccc?key=0AntDDKv-lS6IdFZ6VDRQV0cxRXFVT2dKYm94bWJyQ0E#gid=0

crachel said:
Your best course of action is to not create a thread asking for people to do things for you.
Go sort the Android Development forum by Stats and find the most popular kernel. Read every word of the OP and however much you possibly can of the thread itself. It might take a day or two just to properly educate yourself and get some background. Flash the kernel, use it for several days, and then and only then make an assessment of battery life and performance. After you have done this, go back to the kernel's thread and make a post documenting your experience and what did and did not work for you.
You've registered this month, you have 5 posts, and you've created 2 threads that are completely pointless. Try to contribute something. What I outlined above is possible for anyone no matter what their knowledge level.
Click to expand...
Click to collapse
i understand what you said, but I'm extremely new to the whole android saga, thus why im asking around, and have been researching, i just thought ill ask the forum for some advice. sorry.

Floating battery temperature/% display for use with GPS/NAV (My first “App”)

As you guys know, we can experience rapid battery drain or rapid battery temp increases when using GPS and Navigation Apps.
So, I created an App that will put a transparent display "floating" on top of all other apps (mostly GPS and Nav) so we can easily keep an eye on those parameters (battery temp and %) without leaving our GPS/Nav/other application
Here’s the App page, including APK, discussion, and a screenshot:
http://forum.xda-developers.com/showthread.php?t=1890710
It works great for me.
I don’t know if others will find it useful....
But I’m interested to hear if you have any feedback good or bad.
Since it is not Infuse-specific, I decided I should not post in the Infuse Development forum. Hope you guys don't mind me posting here... just wanted to communicate about it with some of the friendly people I have come to "know" on these great Infuse forums. If this is a bad place to post this, let me know.

electricpete1 said:
As you guys know, we can experience rapid battery drain or rapid battery temp increases when using GPS and Navigation Apps.
So, I created an App that will put a transparent display "floating" on top of all other apps (mostly GPS and Nav) so we can easily keep an eye on those parameters (battery temp and %) without leaving our GPS/Nav/other application
Here’s the App page, including APK, discussion, and a screenshot:
http://forum.xda-developers.com/showthread.php?t=1890710
It works great for me.
I don’t know if others will find it useful....
But I’m interested to hear if you have any feedback good or bad.
Since it is not Infuse-specific, I decided I should not post in the Infuse Development forum. Hope you guys don't mind me posting here... just wanted to communicate about it with some of the friendly people I have come to "know" on these great Infuse forums. If this is a bad place to post this, let me know.
Click to expand...
Click to collapse
A link to a page on xda for an app you made? Yes I think this is a perfectly appropriate place. Good job.

Simple and useful app! I like it! =D
Thanks!

Memory impact of this App
Thanks for the feedback. I appreciate it.
In the App thread above, I added a discussion of possible negative impact of this App on your free memory, and how to work around it.