BTW, anyone can contribute to such optimizations. Get an ADP1, grab the android source code, head over to the android-platform mailing list, and optimize away.
JBQ (trying hard to make sure that it's possible for anyone to contribute code to android). On Wed, Jan 14, 2009 at 10:47 PM, Al Sutton <[email protected]> wrote: > > Sounds like HTC used an MLC flash module... bummer :(. > > Tell the guy working on the Home screen to minimise writes wherever > possible. That includes stripping out logging, separate preference > settings, etc., etc., etc. > > Lets hope the next device uses something less focused on cost and more > focused on performance (especially since I was recently able to buy a > 1GB SLC flash based SD Card for about 10 USD a from Amazon, so it's not > a huge cost increase for a distinctly noticeable speed increase ). > > Al. > > Jean-Baptiste Queru wrote: >> I know that the author of Home has been under lots of pressure to make >> it start as quickly as he possibly could, because startup time has >> consistently been a visible issue. >> >> At this point, the only know option is... apps on SD card (no >> kidding), since the limiting factor when launching Home is the I/O >> speed, and the G1's internal flash is unbelievably slow. >> >> JBQ >> >> On Wed, Jan 14, 2009 at 2:29 PM, Disconnect <[email protected]> wrote: >> >>> Never said that was a good fix. But - unless i'm wrong? - there is little to >>> no pressure to make it work right now, and the way to get that is by making >>> tmob aware that their customers actually care. Or so R. told me (I'm not >>> going to throw him under the bus here, if he wants his name published as the >>> author thats up to him :) ..) >>> >>> On Wed, Jan 14, 2009 at 5:17 PM, Jean-Baptiste Queru <[email protected]> >>> wrote: >>> >>>> Of course, pinning Home in RAM will mean that the RAM in question >>>> won't be available to other apps (including the browser), so you'll >>>> see a lot more of "my background services got interrupted" and "my >>>> browser ran out of memory and closed". >>>> >>>> Home used to be pinned in RAM, and dogfooding found that the user >>>> experience was worse in that case. >>>> >>>> JBQ >>>> >>>> On Wed, Jan 14, 2009 at 2:04 PM, Disconnect <[email protected]> >>>> wrote: >>>> >>>>> Its not a race condition, unless by "race condition between two threads" >>>>> you >>>>> mean "the device gets low on memory and kills all the background apps, >>>>> then >>>>> home takes forever to start up again". >>>>> >>>>> If you are a tmob customer, you -need- to call 611 and ask/complain >>>>> about >>>>> this. Currently, its "behaving as expected" at 10 seconds (yes, its >>>>> proven >>>>> that 15 is not unusual, but I'm told the requirements were 10 or less) >>>>> and >>>>> until the carrier leans on google its going to stay that way. (And they >>>>> don't care about the lists, irc, etc. They care about calls into their >>>>> support center.) >>>>> >>>>> On Wed, Jan 14, 2009 at 12:40 PM, pilkro <[email protected]> wrote: >>>>> >>>>>> Have not. But I've just recently done a factory reset. >>>>>> >>>>>> I don't want to have to pull the battery every time I browse the web, >>>>>> though. >>>>>> >>>>>> >>>>>> >>>>>> On Jan 14, 12:34 pm, Al Sutton <[email protected]> wrote: >>>>>> >>>>>>> 62 that's heading for a record I think.... Have you done the battery >>>>>>> pull trick? >>>>>>> >>>>>>> >>>>>>> (http://groups.google.com/group/android-developers/browse_thread/threa... >>>>>>> >>>>>>> Al. >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> pilkro wrote: >>>>>>> >>>>>>>> Every time. >>>>>>>> >>>>>>>> FWIW, I have 62 installed Market Apps. >>>>>>>> >>>>>>>> On Jan 14, 12:27 pm, Mark Murphy <[email protected]> wrote: >>>>>>>> >>>>>>>>> David Turner wrote: >>>>>>>>> >>>>>>>>>> yes, this is a known issue. I believe that the problem has been >>>>>>>>>> identified (race condition between two threads) and that a fix in >>>>>>>>>> on >>>>>>>>>> the >>>>>>>>>> way. >>>>>>>>>> >>>>>>>>> Good to know...but race conditions usually aren't that consistent. >>>>>>>>> >>>>>>>>> pilkro: Do you get the 5-15 second delay *every* time or >>>>>>>>> occasionally? >>>>>>>>> >>>>>>>>> I don't see this problem on my G1, and if it were widespread, I'd >>>>>>>>> expect >>>>>>>>> there would be many more complaints about this. >>>>>>>>> >>>>>>>>> -- >>>>>>>>> Mark Murphy (a Commons Guy)http://commonsware.com >>>>>>>>> _The Busy Coder's Guide to Android Development_ Version 2.0 >>>>>>>>> Published! >>>>>>>>> >>>>>>> -- >>>>>>> ====== >>>>>>> Funky Android Limited is registered in England & Wales with the >>>>>>> company number 6741909. The registered head office is Kemp House, >>>>>>> 152-160 City Road, London, EC1V 2NX, UK. >>>>>>> >>>>>>> The views expressed in this email are those of the author and not >>>>>>> necessarily those of Funky Android Limited, it's associates, or it's >>>>>>> subsidiaries. >>>>>>> >>>>> >>>> >>>> -- >>>> Jean-Baptiste M. "JBQ" Queru >>>> Android Engineer, Google. >>>> >>>> >>>> >>> >> >> >> >> > > > -- > ====== > Funky Android Limited is registered in England & Wales with the > company number 6741909. The registered head office is Kemp House, > 152-160 City Road, London, EC1V 2NX, UK. > > The views expressed in this email are those of the author and not > necessarily those of Funky Android Limited, it's associates, or it's > subsidiaries. > > > > > -- Jean-Baptiste M. "JBQ" Queru Android Engineer, Google. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
