I think you are doing a disservice to the intelligence of both Android
users and Iphone users... they're more sophisticated than THAT! "BWA
HA HA, your little Android has to have a special mode for what
everything else can do out of the box..." I don't think people are as
gullible as you do, lol.
{SNARK} And I seriously doubt that Google is going to suddenly acquire
a good marketing team... {/SNARK}
The "hack" comment is not to say "can't do it, users will know it's a
hack", it's more like "can't be done, the core team is too good to
throw in a hack." If they're like most programmers I know, they'd quit
before writing code they perceived as a hack. And this WOULD be a hack
of gigantic proportions.
On Mar 27, 8:38 am, Pd <lotusscr...@gmail.com> wrote:
> As you know the technical reasons you would think along those lines.
> Consumers don't know the ins and outs of the device so they probably
> wouldn't think the same as you or I. Turning a negative into a
> positive, a good marketing team would have a field day with this.
> Something along the lines of:
>
> T-Mobile / HTC / Android: True gaming experience with "Full Gaming
> Mode". No interruptions just complete gaming pleasure :-)
>
> Pd.
>
>
>
> Sundog wrote:
> > I call "hack" again. Imagine what the Android haters would say
> > IMMEDIATELY! "Your phone has to have a special mode to handle a simple
> > display smoothly? BWAHAHAHA...." etc. etc.
>
> > On Mar 27, 7:43 am, Pd <lotusscr...@gmail.com> wrote:
>
> >> I was thinking on the same lines. Maybe have a "Gaming Mode" where the
> >> user knowingly chooses to turn the device into a games machine for
> >> better performance.
>
> >> Pd.
>
> >> Markus Junginger wrote:
>
> >>> I strongly agree with the idea that foreground processes should be
> >>> preferred. Currently I develop a game, which - like most games -
> >>> relies on a constant high frame rate. At first, the game pretty sloppy
> >>> until I realized some background app was draining CPU resources. So I
> >>> uninstalled some of them until it ran smoothly. Clearly, this is
> >>> nothing you want to tell a user to do.
>
> >>> So, my first thought on how to solve this is a guaranteed CPU slice
> >>> for the foreground app. Let the foreground task constantly get 90-95%
> >>> of the CPU time if it needs it, no matter what's running in the
> >>> background. The remaining 5-10% should be enough for background tasks.
> >>> I think that's perfectly fine if, for example, emails are received a
> >>> little slower when the user plays a game. Of course, if the foreground
> >>> task does not use the CPU entirely, background tasks should be able to
> >>> get a bigger slice.
>
> >>> Oh, and by the way, what about a JIT or a hotspot compiler? If Android
> >>> apps would be running a factor ~10 the problem would be smaller by the
> >>> same factor. :)- Hide quoted text -
>
> >> - Show quoted text -- Hide quoted text -
>
> - Show quoted text -
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers-unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
-~----------~----~----~----~------~----~------~--~---
