Januari 2014

Home / Archives for Januari 2014

YouTube's Center-Aligned UI, Ready For Launch

Posted by muamar Jumat, 31 Januari 2014 0 komentar

YouTube continues to refine its center-aligned experimental interface, first spotted in July. The latest tweaks include a menu button placed next to the YouTube logo, a gear button placed next to the "upload" button and a sidebar that remembers the latest display state.

Just like in the previous iterations, the header is sticky and the layout is center-aligned.

The homepage uses carousels and shows contextual menus that let you customize the sections.

YouTube also shows a tour guide, which means that the updated interface is almost ready to be released for everyone.

Here's how you can enable the experimental interface. If you use Chrome, Firefox, Opera, Safari or Internet Explorer 8+:

1. open youtube.com in a new tab

2. load your browser's developer console:

* Chrome or Opera 15+ - press Ctrl+Shift+J for Windows/Linux/ChromeOS or Command-Option-J for Mac

* Firefox - press Ctrl+Shift+K for Windows/Linux or Command-Option-K for Mac

* Internet Explorer 8+ - press F12 and select the "Console" tab

* Safari 6+ - if you haven't enabled the Develop menu, open Preferences from the Safari menu, go to the Advanced tab and check "Show Develop menu in menu bar". Close Preferences and then press Command-Option-C to show the console.

* Opera 12 - press Ctrl+Shift+I for Windows/Linux or Command-Option-I for Mac, then click "Console".

3. paste the following code which changes a YouTube cookie:

document.cookie="VISITOR_INFO1_LIVE=LlWIQlLwL_Y; path=/; domain=.youtube.com";window.location.reload();

4. press Enter and close the console.

To go back to the regular interface, use the same instructions, but replace the code from step 3 with this one:

document.cookie="VISITOR_INFO1_LIVE=; path=/; domain=.youtube.com";window.location.reload();

{ Thanks, Rubén. }

Baca Selengkapnya ....

UNDER THE GUNN.....Nick's Take: Episode 3 "Red Carpet Showdown", My Inside DISH!

Posted by muamar 0 komentar

Comin' Around The Corner: Starline Hollywood Double-Decker Tour Bus pulling up in Downtown L.A. getting ready for the "Under The Gunn" Hollywood tour--"Under The Gunn" Episode 3 Lifetime TV

This week on Lifetime's "Under the Gunn"....the contestants face their FIRST
Challenge after we, the Mentors, picked our four designers, in other
words now the competition REALLY can begin. Being that we were in Los
Angeles, it was only inevitable that the first challenge was to create a look for the Red Carpet.

Waiting for the Tour Bus: (left to right) Mentors Mondo Guerra, Nick Verreos, Anya Ayoung-Chee--"Under The Gunn" Episode 3 Lifetime TV

I was really excited about this challenge, as a mentor. And after coming off the "designer picking process" and feeling a bit rejected, I was excited because I thought "this was right up my alley". In retrospect, my "Hands On" approach was probably me over-compensating and trying to prove to my designers (and myself) that I was a worthy mentor. And, I also should have known, that the minute I said that "I have this 'in the bag'" on camera is the minute I was going to be in trouble!

On The Bus: "Under the Gunn" designers and mentors (and Tim Gunn!) headed for the Hollywood Tour--designer Shan Keith Oliver (second row, left) is NOT trying to hear it by the way--LOL!)

Let's get to my inside dish "Nick's Take" on the Episode...

As I said before, this was THE FIRST "actual"
challenge-- not only for the designers but for us the Mentors. This
was going to be a test of sorts on how I should mentor for the first
time. Since I had no other guide on what I should do--mentoring-wise--I
went to my "Instructor Nick" mode when I taught at FIDM in my draping,
sewing, sketching and pattern classes. This began right away during the
bus ride when the designers were given their "sketching time".

Tim Is Worried: Tim Gunn and Nick Verreos--Workroom Visits "Under the Gunn" Episode 3 Lifetime TV

HANDS OFF, NICK!: Instead of letting them just sketch alone on
their own, I sat by them and began giving them suggestions and in fact
sketching for them. Now, some of the designers did ask me for
suggestions, since they knew I had knowledge in this "department" of red
carpet dressing. In hindsight, now I realize I should have just let
them figure it out on their own and I shouldn't have been so hand's on.
Then, after the sketching and designers went fabric shopping, I
made my visit to the workroom--along with Tim--and my "hand's on/Instructor Nick"
approach unfortunately continued. This was primarily focused on two of
my designers--Natalia and Stephanie. They were the only ones asking me
questions, asking for my help, etc., and I LOVED giving them my help
(Oscar and Isabelle were on their own and self-sufficient, for the most part).

Nick On The Floor: Nick Verreos helping Natalia with her gown pattern--"Under The Gunn" Episode 3 Lifetime TV

It all came to a crescendo when...Natalia had run out into the workroom hallway/lounge area asking me for help with her gown pattern and I found myself ON THE FLOOR truing her pattern/fixing a seam line. Tim, then ran to us and began (correctly so) yelling at me wondering WHAT THE HECK I was doing??!! It was not until then that a BIG ROCK hit me: What the heck was I doing??!! I completely lost myself in going back to being "Instructor Nick" and forgotten that these designers were NOT my students and realized that none of the other mentors were sketching and/or making patterns/draping for their designers and more importantly Tim would NEVER do any of those things either (Stupid me!). It was too late for me to realize that this manner of "mentoring" was not the right way and if it wasn't for Tim, I might have just kept on doing it (Thank You Tim). Again, I really thought I was helping my designers, but I wasn't.

Watch Tim tell me "HANDS OFF!" HERE...

The Runway:

Tim Gunn and Judges (left to right) stylist Jen Rade, Marie Claire Fashion Editor Zanna Roberts Rassi and designer Rachel Roy--"Under the Gunn" Episode 3 Lifetime TV

Designers and Mentor: Mentor Nick Verreos with designers (clockwise from top) Isabelle Donola Oscar Gracia-Lopez, Stephanie
Ohnmacht and Natalia Fedner--"Under The Gunn" Episode 3 Lifetime TV

Here are the looks from my Designers...

Isabelle Donola: Isabelle created a very fitted dress from a golden hued silk shantung. The dress featured a draped cowl front and mesh-like back.

Inside Dish--Isabelle had originally made the dress to be LONG but it ended up being TOO SHORT, she then added a piece at the bottom hem (to make it floor length). When I saw what she had done, I told her that the judges might see that and notice it as a mistake. I suggested that she should do away with that piece and just make the dress "tea-length"--below-the-knee cocktail. And she did, and I think the look was quite chic.

Natalia Fedner: Natalia's gown was of silk charmeuse--a fabric Natalia said she loved using in her own line and that it's one of her "signatures". The gown was one shoulder with gold straps.

Inside Dish: This is the dress that I was ON THE FLOOR trying to help Natalia with. Originally, however, this gown was going to have those gold straps and a gold piece in the front but both Tim and I suggested that under the time constraints, this might be too much work for her. She therefore kept it simple and made it a clean one shoulder plain front with asymmetrical side pleating.

Oscar Garcia-Lopez: I loved Oscar's hunter green gown. This was perfectly made and VERY red carpet. I thought that he would be on top.

Inside Dish: Oscar was done waaaaay before any of the other designers. In fact he had so much time, he began cleaning and sweeping the workroom as a result (bless his heart!). Also, this gown was going to have a keyhole front opening AND he wanted to add a BIG BOW at the back--right on her bootie, as well as give her a TURBAN and long gloves. Not kidding. I suggested that it might be "too mucheey" and to keep it simple. He did and it looked gorgeous.

Stephanie Ohnmacht: Stephanie created a strapless dress with this green taffeta.

Inside Dish: Two things happened to Stephanie that weren't good: her fabric choice and the fact that I tried to help. The concept of the design and dress was sweet--she was going for a dress for the young "Hollywood" girl but it ended up looking prom-a-licious. She wanted to do some interesting diagonal draping and make the dress not have side seams yet still achieve a fuller shape. And even with my "Too Hands-On" help (which didn't really help) the dress looked tortured. Seeing the dress on the runway really also brought it home to me to try and stay HANDS OFF. I was sure that my Stephanie would be going home. But she didn't! (thank goodness).

Out: Who did go home was Camilla Castillo. I actually LIKED this dress; it was simple, modern and a little bit "Raf Simons for Dior". I even liked the origami-like folding in the back. The dress, however, was a little too see-through in the front and the fabric was wrinkled. Camilla also made lots of excuses on the runway/judging which I think the judges did not like. She went home.

The Best: (left to right) Designers Blake Smith (Anya's designer) and Sam Donovan (Mondo's) were the two best looks and rightly so. I loved these two designs and for being such polar opposites of what could be deemed as a "red carpet" look. One was a beautifully constructed va-va-voom of a gown (Blake's) and Sam's was a young, directional-looking jumpsuit for an up-and-coming Hollywood ingenue "It" girl. Sam won and Congrats to him!

Click HERE to watch Tim's take on the Episode and talk about my TOO HANDS ON approach (Oyyy Vey!)

Baca Selengkapnya ....

Process Stats: Understanding How Your App Uses RAM

Posted by muamar 0 komentar

Posted by Dianne Hackborn, Android framework team

Android 4.4 KitKat introduced a new system service called procstats that helps you better understand how your app is using the RAM resources on a device. Procstats makes it possible to see how your app is behaving over time — including how long it runs in the background and how much memory it uses during that time. It helps you quickly find inefficiencies and misbehaviors in your app that can affect how it performs, especially when running on low-RAM devices.

You can access procstats data using an adb shell command, but for convenience there is also a new Process Stats developer tool that provides a graphical front-end to that same data. You can find Process Stats in Settings > Developer options > Process Stats.

In this post we’ll first take a look at the Process Stats graphical tool, then dig into the details of the memory data behind it, how it's collected, and why it's so useful to you as you analyze your app.

Process Stats overview of memory used by background processes over time.

Looking at systemwide memory use and background processes

When you open Process Stats, you see a summary of systemwide memory conditions and details on how processes are using memory over time. The image at right gives you an example of what you might see on a typical device.

At the top of the screen we can see that:

We are looking at that data collected over the last ~3.5 hours.

Currently the device’s RAM is in good shape ("Device memory is currently normal").

During that entire time the memory state has been good — this is shown by the green bar. If device memory was getting low, you would see yellow and red regions on the left of the bar representing the amount of total time with low memory.

Below the green bar, we can see an overview of the processes running in the background and the memory load they've put on the system:

The percentage numbers on the right indicate the amount of time each process has spent running during the total duration.

The blue bars indicate the relative computed memory load of each process. (The memory load is runtime*avg_pss, which we will go into more detail on later.)

Some apps may be listed multiple times, since what is being shown is processes (for example, Google Play services runs in two processes). The memory load of these apps is the sum of the load of their individual processes.

There are a few processes at the top that have all been running for 100% of the time, but with different weights because of their relative memory use.

Analyzing memory for specific processes

The example shows some interesting data: we have a Clock app with a higher memory weight than Google Keyboard, even though it ran for less than half the time. We can dig into the details of these processes just by tapping on them:

Process Stats memory details for Clock and Keyboard processes over the past 3.5 hours.

The details for these two processes reveal that:

The reason that Clock has been running at all is because it is being used as the current screen saver when the device is idle.

Even though the Clock process ran for less than half the time of the Keyboard, its ram use was significantly larger (almost 3x), which is why its overall weight is larger.

Essentially, procstats provides a “memory use” gauge that's much like the storage use or data use gauges, showing how much RAM the apps running in the background are using. Unlike with storage or data, though, memory use is much harder to quantify and measure, and procstats uses some tricks to do so. To illustrate the complexity of measuring memory use, consider a related topic: task managers.

Understanding task managers and their memory info

We’ve had a long history of task managers on Android. Android has always deeply supported multitasking, which means the geeky of us will tend to want to have some kind of UI for seeing and controlling this multitasking like the traditional UI we are used to from the desktop. However, multitasking on Android is actually quite a bit more complicated and fundamentally different than on a traditional desktop operating system, as I previously covered in Multitasking the Android Way. This deeply impacts how we can show it to the user.

Multitasking and continuous process management

To get a feel for just how different process management is on Android, you can take a look at the output of an important system service, the activity manager, with adb shell dumpsys activity. The example below shows a snapshot of current application processes on Android 4.4, listing them from most important to least:

ACTIVITY MANAGER RUNNING PROCESSES (dumpsys activity processes)
Process LRU list (sorted by oom_adj, 22 total, non-act at 2, non-svc at 2):
  PERS #21: sys   F/ /P  trm: 0 23064:system/1000 (fixed)
  PERS #20: pers  F/ /P  trm: 0 23163:com.android.systemui/u0a12 (fixed)
  PERS #19: pers  F/ /P  trm: 0 23344:com.nuance.xt9.input/u0a77 (fixed)
  PERS #18: pers  F/ /P  trm: 0 23357:com.android.phone/1001 (fixed)
  PERS #17: pers  F/ /P  trm: 0 23371:com.android.nfc/1027 (fixed)
  Proc # 3: fore  F/ /IB trm: 0 13892:com.google.android.apps.magazines/u0a59 (service)
    com.google.android.apps.magazines/com.google.apps.dots.android.app.service.SyncService<=Proc{23064:system/1000}
  Proc # 2: fore  F/ /IB trm: 0 23513:com.google.process.gapps/u0a8 (provider)
    com.google.android.gsf/.gservices.GservicesProvider<=Proc{13892:com.google.android.apps.magazines/u0a59}
  Proc # 0: fore  F/A/T  trm: 0 24811:com.android.settings/1000 (top-activity)
  Proc # 4: vis   F/ /IF trm: 0 23472:com.google.process.location/u0a8 (service)
    com.google.android.backup/.BackupTransportService<=Proc{23064:system/1000}
  Proc #14: prcp  F/ /IF trm: 0 23298:com.google.android.inputmethod.latin/u0a57 (service)
    com.google.android.inputmethod.latin/com.android.inputmethod.latin.LatinIME<=Proc{23064:system/1000}
  Proc # 1: home  B/ /HO trm: 0 23395:com.android.launcher/u0a13 (home)
  Proc #16: cch   B/ /CA trm: 0 23966:com.google.android.deskclock/u0a36 (cch-act)
  Proc # 6: cch   B/ /CE trm: 0 7716:com.google.android.music:main/u0a62 (cch-empty)
  Proc # 5: cch   B/ /CE trm: 0 8644:com.google.android.apps.docs/u0a39 (cch-empty)
  Proc # 8: cch+2 B/ /CE trm: 0 5131:com.google.android.youtube/u0a78 (cch-empty)
  Proc # 7: cch+2 B/ /CE trm: 0 23338:com.google.android.gms/u0a8 (cch-empty)
  Proc #10: cch+4 B/ /CE trm: 0 8937:com.google.android.apps.walletnfcrel/u0a24 (cch-empty)
  Proc # 9: cch+4 B/ /CE trm: 0 24689:com.google.android.apps.plus/u0a70 (cch-empty)
  Proc #15: cch+6 B/ /S  trm: 0 23767:com.google.android.apps.currents/u0a35 (cch-started-services)
  Proc #13: cch+6 B/ /CE trm: 0 9115:com.google.android.gm/u0a44 (cch-empty)
  Proc #12: cch+6 B/ /S  trm: 0 7738:android.process.media/u0a6 (cch-started-services)
  Proc #11: cch+6 B/ /CE trm: 0 8922:com.google.android.setupwizard/u0a19 (cch-empty)

Example output of dumpsys activity command, showing all processes currently running.

There are a few major groups of processes here — persistent system processes, the foreground processes, background processes, and finally cached processes — and the category of a process is extremely important for understanding its impact on the system.

At the same time, processes on this list change all of the time. For example, in the snapshot above we can see that “com.google.android.gm” is currently an important process, but that is because it is doing a background sync, something the user would not generally be aware of or want to manage.

Snapshotting per-process RAM use

The traditional use of a task manager is closely tied to RAM use, and Android provides a tool called meminfo for looking at a snapshot of current per-process RAM use. You can access it with the command adb shell dumpsys meminfo. Here's an example of the output.

Total PSS by OOM adjustment:
    31841 kB: Native
               13173 kB: zygote (pid 23001)
                4372 kB: surfaceflinger (pid 23000)
                3721 kB: mediaserver (pid 126)
                3317 kB: glgps (pid 22993)
                1656 kB: drmserver (pid 125)
                 995 kB: wpa_supplicant (pid 23148)
                 786 kB: netd (pid 121)
                 518 kB: sdcard (pid 132)
                 475 kB: vold (pid 119)
                 458 kB: keystore (pid 128)
                 448 kB: /init (pid 1)
                 412 kB: adbd (pid 134)
                 254 kB: ueventd (pid 108)
                 238 kB: dhcpcd (pid 10617)
                 229 kB: tf_daemon (pid 130)
                 200 kB: installd (pid 127)
                 185 kB: dumpsys (pid 14207)
                 144 kB: healthd (pid 117)
                 139 kB: debuggerd (pid 122)
                 121 kB: servicemanager (pid 118)
    48217 kB: System
               48217 kB: system (pid 23064)
    49095 kB: Persistent
               34012 kB: com.android.systemui (pid 23163 / activities)
                7719 kB: com.android.phone (pid 23357)
                4676 kB: com.android.nfc (pid 23371)
                2688 kB: com.nuance.xt9.input (pid 23344)
    24945 kB: Foreground
               24945 kB: com.android.settings (pid 24811 / activities)
    17136 kB: Visible
               14026 kB: com.google.process.location (pid 23472)
                3110 kB: com.android.defcontainer (pid 13976)
     6911 kB: Perceptible
                6911 kB: com.google.android.inputmethod.latin (pid 23298)
    14277 kB: A Services
               14277 kB: com.google.process.gapps (pid 23513)
    26422 kB: Home
               26422 kB: com.android.launcher (pid 23395 / activities)
    21798 kB: B Services
               16242 kB: com.google.android.apps.currents (pid 23767)
                5556 kB: android.process.media (pid 7738)
   145869 kB: Cached
               41588 kB: com.google.android.apps.plus (pid 24689)
               21417 kB: com.google.android.deskclock (pid 23966 / activities)
               14463 kB: com.google.android.apps.docs (pid 8644)
               14303 kB: com.google.android.gm (pid 9115)
               11014 kB: com.google.android.music:main (pid 7716)
               10688 kB: com.google.android.apps.magazines (pid 13892)
               10240 kB: com.google.android.gms (pid 23338)
                9882 kB: com.google.android.youtube (pid 5131)
                8807 kB: com.google.android.apps.walletnfcrel (pid 8937)
                3467 kB: com.google.android.setupwizard (pid 8922)

Total RAM: 998096 kB
 Free RAM: 574945 kB (145869 cached pss + 393200 cached + 35876 free)
 Used RAM: 392334 kB (240642 used pss + 107196 buffers + 3856 shmem + 40640 slab)
 Lost RAM: 30817 kB
   Tuning: 64 (large 384), oom 122880 kB, restore limit 40960 kB (high-end-gfx)

Example output of dumpsys meminfo command, showing memory currently used by running processes.

We are now looking at the same processes as above, again organized by importance, but now with on their impact on RAM use.

Usually when we measure RAM use in Android, we do this with Linux’s PSS (Proportional Set Size) metric. This is the amount of RAM actually mapped into the process, but weighted by the amount it is shared across processes. So if there is a 4K page of RAM mapped in to two processes, its PSS amount for each process would be 2K.

The nice thing about using PSS is that you can add up this value across all processes to determine the actual total RAM use. This characteristic is used at the end of the meminfo report to compute how much RAM is in use (which comes in part from all non-cached processes), versus how much is "free" (which includes cached processes).

Task-manager style memory info, showing a snapshot of memory used by running apps.

Task manager UI based on PSS snapshot

Given the information we have so far, we can imagine various ways to present this in a somewhat traditional task manager UI. In fact, the UI you see in Settings > Apps > Running is derived from this information. It shows all processes running services (“svc” adjustment in the LRU list) and on behalf of the system (the processes with a “<=Proc{489:system/1000}” dependency), computing the PSS RAM for each of these and any other processes they have dependencies on.

The problem with visualizing memory use in this way is that it gives you the instantaneous state of the apps, without context over time. On Android, users don’t directly control the creation and removal of application processes — they may be kept for future use, removed when the system decides, or run in the background without the user explicitly launching them. So looking only at the instantaneous state of memory use only, you would be missing important information about what is actually going on over time.

For example, in our first look at the process state we see the com.google.android.apps.magazines process running for a sync, but when we collected the RAM use right after that it was no longer running in the background but just being kept around as an old cached process.

To address this problem, the new procstats tool continually monitors the state of all application processes over time, aggregating that information and collecting PSS samples from those processes while doing so. You can view the raw data being collected by procstats with the command adb shell dumpsys procstats.

Seeing memory use over time with procstats

Let’s now go back to procstats and take a look at the context it provides by showing memory use over time. We can use the command adb shell dumpsys procstats --hours 3 to output memory information collected over the last 3 hours. This is the same data as represented graphically in the first Process Stats example.

The output shows all of the processes that have run in the last 3 hours, sorted with the ones running the most first. (Processes in a cached state don’t count for the total time in this sort.) Like the initial graphical representation, we now clearly see a big group of processes that run all of the time, and then some that run occasionally — this includes the Magazines process, which we can now see ran for 3.6% of the time over the last 3 hours.

  * com.google.android.inputmethod.latin / u0a57:
           TOTAL: 100% (6.4MB-6.7MB-6.8MB/5.4MB-5.4MB-5.4MB over 21)
          Imp Fg: 100% (6.4MB-6.7MB-6.8MB/5.4MB-5.4MB-5.4MB over 21)
  * com.google.process.gapps / u0a8:
           TOTAL: 100% (12MB-13MB-14MB/10MB-11MB-12MB over 211)
          Imp Fg: 0.11%
          Imp Bg: 0.83% (13MB-13MB-13MB/11MB-11MB-11MB over 1)
         Service: 99% (12MB-13MB-14MB/10MB-11MB-12MB over 210)
  * com.android.systemui / u0a12:
           TOTAL: 100% (29MB-32MB-34MB/26MB-29MB-30MB over 21)
      Persistent: 100% (29MB-32MB-34MB/26MB-29MB-30MB over 21)
  * com.android.phone / 1001:
           TOTAL: 100% (6.5MB-7.1MB-7.6MB/5.4MB-5.9MB-6.4MB over 21)
      Persistent: 100% (6.5MB-7.1MB-7.6MB/5.4MB-5.9MB-6.4MB over 21)
  * com.nuance.xt9.input / u0a77:
           TOTAL: 100% (2.3MB-2.5MB-2.7MB/1.5MB-1.5MB-1.5MB over 21)
      Persistent: 100% (2.3MB-2.5MB-2.7MB/1.5MB-1.5MB-1.5MB over 21)
  * com.android.nfc / 1027:
           TOTAL: 100% (4.2MB-4.5MB-4.6MB/3.2MB-3.2MB-3.3MB over 21)
      Persistent: 100% (4.2MB-4.5MB-4.6MB/3.2MB-3.2MB-3.3MB over 21)
  * com.google.process.location / u0a8:
           TOTAL: 100% (13MB-13MB-14MB/10MB-11MB-11MB over 21)
          Imp Fg: 100% (13MB-13MB-14MB/10MB-11MB-11MB over 21)
  * system / 1000:
           TOTAL: 100% (42MB-46MB-56MB/39MB-42MB-48MB over 21)
      Persistent: 100% (42MB-46MB-56MB/39MB-42MB-48MB over 21)
  * com.google.android.apps.currents / u0a35:
           TOTAL: 100% (16MB-16MB-16MB/14MB-14MB-14MB over 17)
         Service: 100% (16MB-16MB-16MB/14MB-14MB-14MB over 17)
  * com.android.launcher / u0a13:
           TOTAL: 77% (25MB-26MB-27MB/22MB-23MB-24MB over 73)
             Top: 77% (25MB-26MB-27MB/22MB-23MB-24MB over 73)
          (Home): 23% (25MB-26MB-26MB/23MB-23MB-24MB over 12)
  * android.process.media / u0a6:
           TOTAL: 48% (5.0MB-5.3MB-5.5MB/4.0MB-4.2MB-4.2MB over 11)
          Imp Fg: 0.00%
          Imp Bg: 0.00%
         Service: 48% (5.0MB-5.3MB-5.5MB/4.0MB-4.2MB-4.2MB over 11)
        Receiver: 0.00%
        (Cached): 22% (4.1MB-4.5MB-4.8MB/3.0MB-3.5MB-3.8MB over 8)
  * com.google.android.deskclock / u0a36:
           TOTAL: 42% (20MB-21MB-21MB/18MB-19MB-19MB over 8)
          Imp Fg: 42% (20MB-21MB-21MB/18MB-19MB-19MB over 8)
         Service: 0.00%
        Receiver: 0.01%
        (Cached): 58% (17MB-20MB-21MB/16MB-18MB-19MB over 14)
  * com.android.settings / 1000:
           TOTAL: 23% (19MB-22MB-28MB/15MB-19MB-24MB over 31)
             Top: 23% (19MB-22MB-28MB/15MB-19MB-24MB over 31)
      (Last Act): 77% (9.7MB-14MB-20MB/7.5MB-11MB-18MB over 8)
        (Cached): 0.02%
  * com.google.android.apps.magazines / u0a59:
           TOTAL: 3.6% (10MB-10MB-10MB/8.7MB-9.0MB-9.0MB over 6)
          Imp Bg: 0.03%
         Service: 3.6% (10MB-10MB-10MB/8.7MB-9.0MB-9.0MB over 6)
        (Cached): 17% (9.9MB-10MB-10MB/8.7MB-8.9MB-9.0MB over 5)
  * com.android.defcontainer / u0a5:
           TOTAL: 1.4% (2.7MB-3.0MB-3.0MB/1.9MB-1.9MB-1.9MB over 7)
             Top: 1.2% (3.0MB-3.0MB-3.0MB/1.9MB-1.9MB-1.9MB over 6)
          Imp Fg: 0.19% (2.7MB-2.7MB-2.7MB/1.9MB-1.9MB-1.9MB over 1)
         Service: 0.00%
        (Cached): 15% (2.6MB-2.6MB-2.6MB/1.8MB-1.8MB-1.8MB over 1)
  * com.google.android.youtube / u0a78:
           TOTAL: 1.3% (9.0MB-9.0MB-9.0MB/7.8MB-7.8MB-7.8MB over 1)
          Imp Bg: 1.0% (9.0MB-9.0MB-9.0MB/7.8MB-7.8MB-7.8MB over 1)
         Service: 0.27%
      Service Rs: 0.01%
        Receiver: 0.00%
        (Cached): 99% (9.1MB-9.4MB-9.7MB/7.7MB-7.9MB-8.1MB over 24)
  * com.google.android.gms / u0a8:
           TOTAL: 0.91% (9.2MB-9.2MB-9.2MB/7.6MB-7.6MB-7.6MB over 1)
          Imp Bg: 0.79% (9.2MB-9.2MB-9.2MB/7.6MB-7.6MB-7.6MB over 1)
         Service: 0.11%
        Receiver: 0.00%
        (Cached): 99% (8.2MB-9.4MB-10MB/6.5MB-7.6MB-8.1MB over 25)
  * com.google.android.gm / u0a44:
           TOTAL: 0.56%
          Imp Bg: 0.55%
         Service: 0.01%
        Receiver: 0.00%
        (Cached): 99% (11MB-13MB-14MB/10MB-12MB-13MB over 24)
  * com.google.android.apps.plus / u0a70:
           TOTAL: 0.22%
          Imp Bg: 0.22%
         Service: 0.00%
        Receiver: 0.00%
        (Cached): 100% (38MB-40MB-41MB/36MB-38MB-39MB over 17)
  * com.google.android.apps.docs / u0a39:
           TOTAL: 0.15%
          Imp Bg: 0.09%
         Service: 0.06%
        (Cached): 54% (13MB-14MB-14MB/12MB-12MB-13MB over 17)
  * com.google.android.music:main / u0a62:
           TOTAL: 0.11%
          Imp Bg: 0.04%
         Service: 0.06%
        Receiver: 0.01%
        (Cached): 70% (7.7MB-10MB-11MB/6.4MB-9.0MB-9.3MB over 20)
  * com.google.android.apps.walletnfcrel / u0a24:
           TOTAL: 0.01%
        Receiver: 0.01%
        (Cached): 69% (8.1MB-8.4MB-8.6MB/7.0MB-7.1MB-7.1MB over 13)
  * com.google.android.setupwizard / u0a19:
           TOTAL: 0.00%
        Receiver: 0.00%
        (Cached): 69% (2.7MB-3.2MB-3.4MB/1.8MB-2.0MB-2.2MB over 13)

Run time Stats:
  SOff/Norm: +1h43m29s710ms
  SOn /Norm: +1h37m14s290ms
      TOTAL: +3h20m44s0ms

          Start time: 2013-11-06 07:24:27
  Total elapsed time: +3h42m23s56ms (partial) libdvm.so chromeview

Example output of dumpsys procstats --hours 3 command, showing memory details for processes running in the background over the past ~3 hours.

The percentages tell you how much of the overall time each process has spent in various key states. The memory numbers tell you about memory samples in those states, as minPss-avgPss-maxPss / minUss-avgUss-maxUss. The procstats tool also has a number of command line options to control its output — use adb shell dumpsys procstats -h to see a list of the available options.

Comparing this raw data from procstats with the visualization of its data we previously saw, we can see that it is showing only process run data from a subset of states: Imp Fg, Imp Bg, Service, Service Rs, and Receiver. These are the situations where the process is actively running in the background, for as long as it needs to complete the work it is doing. In terms of device memory use, these are the process states that tend to cause the most trouble: apps running in the background taking RAM from other things.

Getting started with procstats

We have already found the new procstats tool to be invaluable in better understanding the overall memory behavior of Android systems, and it has been a key part of the Project Svelte effort in Android 4.4.

As you develop your own applications, be sure to use procstats and the other tools mentioned here to help understand how your own app is behaving, especially how much it runs in the background and how much RAM it uses during that time.

More information about how to analyze and debug RAM use on Android is available on the developer page Investigating Your RAM Usage.

Join the discussion on

+Android Developers

Baca Selengkapnya ....

Google Sells Motorola to Lenovo

Posted by muamar Rabu, 29 Januari 2014 0 komentar

Google's decision to sell Motorola Mobility to Lenovo for $2.91 billion is even more surprising than Google's acquisition of Motorola Mobility for $12.5 billion in 2011.

"Lenovo will now acquire world-renowned Motorola Mobility, including the MOTOROLA brand and Motorola Mobility's portfolio of innovative smartphones like the Moto X and Moto G and the DROID™ Ultra series. In addition to current products, Lenovo will take ownership of the future Motorola Mobility product roadmap. Google will maintain ownership of the vast majority of the Motorola Mobility patent portfolio, including current patent applications and invention disclosures."

Motorola's patents weren't that valuable, Google didn't manage to make Motorola profitable, it started to compete with the other Android OEMs and sold Motorola at a loss. Still, why not try harder to make Motorola shine once again? Why admit defeat and show that your strategy was wrong?

I think the answer can be found in Google's licensing agreement with Samsung:

"Samsung Electronics and Google Inc. furthered their long-term cooperative partnership with a global patent cross-license agreement covering a broad range of technologies and business areas. The mutually beneficial agreement covers the two companies existing patents as well as those filed over the next 10 years."

Samsung is the biggest Android OEM and a switch from Android to Tizen would be a very bad news for Google. If Samsung used its dominant position and asked Google to get rid of Motorola, Google didn't have other options.

Motorola is a lost bet, Google showed that the health of the Android ecosystem is more important than owning Motorola.

"Lenovo has the expertise and track record to scale Motorola Mobility into a major player within the Android ecosystem. This move will enable Google to devote our energy to driving innovation across the Android ecosystem, for the benefit of smartphone users everywhere. As a side note, this does not signal a larger shift for our other hardware efforts. The dynamics and maturity of the wearable and home markets, for example, are very different from that of the mobile industry. We're excited by the opportunities to build amazing new products for users within these emerging ecosystems," said Larry Page, Google's CEO.

Apparently, Motorola's Advanced Technology Group will continue to work at Google. "That means the Ara modular smartphone concept, as well as sensors you swallow and passwords you tattoo on your skin. The Advanced Tech team is headed by one-time Defense Advanced Research Projects Agency director Regina Dugan, and has been behind some of the more sci-fi things that Google has demonstrated since acquiring Moto's mobile biz."

{ Thanks, Jérôme and Tolis . }

Baca Selengkapnya ....

Updated Stock Card in Google Search

Posted by muamar 0 komentar

Google's stock card that's displayed when you search for [GOOG], [TSLA], [Microsoft stock] and other similar queries is now a lot bigger. Tabs are placed above the chart and you can get the stock price at any time by mousing over the chart or tapping it.

Drag the dotted line to get the price variation.

Another change is that the links to Google Finance, Yahoo Finance and MSN Money have been removed.

{ Thanks, Jérôme. }

Baca Selengkapnya ....

OLYMPIC FASHION REPORT.....Sochi 2014 Winter Olympics Fashion From Around the World: Check Out These Uniforms!

Posted by muamar 0 komentar

Print-tastic: Norway's curling team could be the NEXT winner of the Eurovision Contest...in these "uniforms"

The Sochi 2014 Winter Olympics is a week away and well, I think it's time to discuss some of the Olympics Fashion From Around the World that we will be seeing on display from the athletes. Everyone knows all the much-discussed controversies surrounding the Sochi Olympics including terrorist threats as well as the anti-LGBT laws, but here, I want to discuss other controversies: The Fashion!

Colorful, Printed and a little bit of Fashion Cray-Cray vs. Subdued, Boring and Un-creative...these uniforms below run the gamut. So, without further ado...let's discuss the Olympics Fashion and I am giving each of them my own "Fashion Points" score--0 being NOT Fashionable and 10 being très CHIC...

Germany: Germany's uniforms are COLORFUL, to say the least. Multicolored puffy coats and THOSE psychedelic printed pants! How do you say "Wowza" in German? Well, at least the German Olympic team will be noticed form the "nose-bleed" seats for sure!I think it's A LOT. I appreciate the color and I might even wear that puffy parka but the pants...they look like pajamas a 12-year-old would wear. What do you guys think? Yeay or Nay on Germany?

Fashion Points: 6/10

Canada: Oh Canada. Canada's Olympic uniforms are a big YAWN compared to Germany's but then again, almost anybody's would be. They've incorporated the red, of course. And the country's name is boldly displayed. however, they seem pretty uncreative in terms of fashion. The red parka coat I could buy at an outlet mall like TOMORROW and the zip up sweaters, they seem a little like grandma knitted them...

Fashion Points: 4/10

But, I do kind of like this:

Canada's Snowboarder--Under Armour recently debuted its design of the winter Olympic uniform
for Canadian snowboarders who will be competing at Sochi 2014.The jacket and pants feature a maple leaf pattern, made up
of tiny little triangles. The pattern itself is thermo-conductive and
helps to lock in heat without additional bulk. As well, the outer jacket
is completely water-resistant, which makes it even more comfortable for
wear during winter sports. The uniforms are also kind of "Retro" in that they take
inspiration from the 1972 Summit Series, where the Canadian men’s hockey
team defeated the Soviet Union. I think this look is pretty cool (do the kids still say that??!!).

Fashion Points: 8.9/10

Czech Republic: These boys are happy for some reason. Not sure why. They look like moose-hunters in Alaska. I like the gold lettering in the hooded zip-up parka and the fur cap is kitschy (I'd take a faux fur one please!), but I think the entire look is a bit disjointed..it's like they're going to work out but yet have to brave below zero temperatures to do so. maybe that's the point.

Fashion Points: 3/10

Japan: Orange and blue? Are they from Holland or Japan? I'm confused. I do like the bold colors, but fashion-wise, these are pretty uninteresting.

Fashion Points: 2/10

USA: These uniforms--designed by Ralph Lauren--and all made in the good ol' US of A (Thank Goodness!) were met with lots of shock and awe and much polarized commentary form the web:

"Welcome to the ugly sweater party, America," the
San Francisco Chronicle wrote.

Deadspin chimed in too: "A
generous interpretation would say the patchwork stylings are reminiscent of
certain Russian folk dress. But it's totally just an ugly Christmas
sweater."

Ouch. I don't hate them but at the same time, I'm not super
excited about them. On the positive, I like the "retro" look it's giving
me--like 1960s ski instructors in the Swiss Alps. The navy and red pea coat is
elegant and VERY Ralph Lauren. It screams "Old Money Americana".

Fashion Points: 7/10

Moose Sweater Boy: I would buy this sweater. I would wear it with jeans and my YSL "Johnny Boots". But I am not sure of the white pants, especially in the winter and with all the snow (it will just blend in) and the slush (it will get filthy REALLY fast!).

Fashion Points: 8/10 (for the sweater!)

Patchwork Mess: As much as I liked the other sweater, I am not sure about this one. This sweater is just TOO MUCHEEY. He might as well have a button that you touch and all of sudden it's the National Anthem! It's a bit tacky and too in your face.

Fashion Points: 2/10

Medal Podium Outfits from Nike: Nike also designed the Medal podium looks for the US Olympic team and there are some good and not-so-good things about these looks. I like the sneakers with the bold neon soles; very on-trend. The silver fitted puffy jacket is also very Uniqlo and trendy. I like that it's fitted and sleeker but the silver and the quilting combined...it looks like a Jiffy Pop Popcorn maker. And the leggings are more Lulu Lemon and less Fashion Olympics. With all that said, I still think they're stylish. If I had a vision of what flight attendants on a Moon trip shuttle in the year 2100 would wear, these outfits would be it.

Fashion Points: 5.5/10

US Speedskating Uniform: Now this is HOT. Very Robocop meets hot swimmer. And seriously, look at those LEG MUSCLES! The only think that's a little jarring is the color-blocking focus on the inner thigh region. Just sayin'

Fashion Points: 8/10

Russia: There are a lot of things going on here. On the far right, you have very wearable puffy jackets and red pant combo (I likey!), then there are two Von Trapp kids from "The Sound of Music" for some reason, and then some fur trimmed ladies:

Miss Russia 1977: Part of me just wishes they were completely made of fur. The styling of these coats looks very 70s pimp...or something an old Russia woman would be wearing on her way to the the supermarket on a cold Winter's day.

Glove Boy--And PS: these gloves are SUPER GAY (and I can say that!).

Total Fashion Points for Russia: 5/10 (for the Good, the "Uh Oh" 70s fur coat and those gloves)

Sochi 2014 Volunteers Uniforms: These above are the uniforms that will be worn by the Sochi 2014 volunteers. The print in these zip-up parka coats/jackets are blindingly jarring. They remind me of a jacket one of the "Golden Girls" would have worn on a rainy Florida day! On a positive note: there's NO WAY one could miss a Sochi 2014 Winter Olympics volunteer, if you needed their assistance--they certainly do not blend in. My secret wish is to see one of the German Olympic team stand NEXT to one of these volunteers!!

Fashion Points: 3.8/10

Mariachi Olympic Prince: Mexican skier Hubertus von Hohenlohe is trying to go for being the "best Dressed" at the Sochi Winter Olympics. This above is what the 55-year-old will wear during the ski competition. In what will be his sixth trip to the Olympics, Hohenlohe will don a mariachi-themed race suit during competition. "Until I went to Mexico recently to make a documentary, I never
realized what a beautiful, amazing, rich past and culture they have and
what a proud people they are," he told NBC Olympics. "It actually moved
me to see how much they suffered and how much they fought for what they
have. The power to have your own identity is so strong and something I
believe in so I want to give it a go in a very cool, elegant way. I want
to celebrate who they are, but of course in my own style." Hohenlohe, also a prince of German descent, joked that being one of the most fashionable "is a medal I need so urgently."

Fashion Points: 9.5/10

Norway Curling Team: Finally, the Norway curling team and their suits/uniforms. I actually LOVE them! They're fun, kooky and attention-grabbing. Is the print loud? Yes! I would probably never ever wear a complete suit of this but I would certainly love a silk pocket scarf out of it. Watching grown men slide stones across the ice to a targeted area of concentric rings while wearing these get-ups will certainly be one of MY highlights of the Sochi 2014 Winter Olympics...Go Team Norway!

Fashion Points: 7/10

What do YOU guys think of these uniforms??? Cray-Cray Good or Cray-Cray "Uh Oh!"...Let me know!

Baca Selengkapnya ....