[inline] On Fri, Mar 27, 2009 at 2:02 PM, Stoyan Damov <[email protected]> wrote: > And *especially* when a background app is hurting a foreground app? I > can't find anyone would want a background service to get more cycles > than the currently executing UI in the foreground, because the UI pegs > the CPU and is thus "hurting" the background service, right? Right?
I said "in general". We do care much about the care where the UX isn't as smooth as it should be because of a background process, but we also probably don't want to turn the dial so far that background apps can't run at all. > Do these people read any of the android-* lists, and if yes, which > ones? If you don't know the answer to any of the 2 questions, how can > we make contact with these people? Those people are supposed to be on android-platform (user-space) and android-kernel (kernel-space). If not, that's a problem on our side that we need to fix. Those lists expect to have someone currently actively "driving" an implementation. > I don't want you to answer it either. I would love though, if you > could point us to someone who could, or would. Unfortunately, I don't know who has authority to say anything in that domain. > OK. We agree to disagree. I do want ideas and suggestions to be logged > for future reading. I mind the bug-tracking system. I would imagine > something like a web site, where people could post ideas and > suggestions, and others can vote, and comment on them, tag them, > search them easily, etc. http://code.google.com/p/android/issues/list > is simply not appropriate. I have to agree that the current public bug database isn't quite appropriate for a project as large as Android. It does support everything you mentioned, though. > So android-platform is the right list for this, ok, thanks. > >> About my example: I hadn't reached the implementation phase yet, that >> specific issue is still very firmly in the design phase. If you're willing to follow up on the issue throughout the discussion up to the point where it's implemented, that's perfectly fine. You don't need to have code ready to show before you post (in fact that's definitely not recommended). However, showing up and saying essentially "I want this fixed right now and I want someone else to do it" isn't going to get you the right kind of attention. Right now those lists are still a bit in a state of flux and tend to lack some focus, but we're trying to bring that a bit more under control. JBQ -- Jean-Baptiste M. "JBQ" Queru Android Engineer, Google. Questions sent directly to me that have no reason for being private will likely get ignored or forwarded to a public forum with no further warning. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
