• Masuk ke dalam dashboard.
• Klik "template".
• Scroll mouse ke bawah, maka akan tersedia beberapa template default yang disediakan oleh blogger yang dapat kita gunakan.
• Klik satu di antaranya kemudian klik terapkan.
• Maka template secara otomatis akan terganti dengan yang baru.

Mengganti Template Dari Penyedia Template Gratis

Masuk ke dalam dashboar blogger.
Klik "template".
Klik "Cadangkan/Pulihkan" yang berada di sebelah kanan atas.


Download/Unduh terlebih dahulu template lama apabila dibutuhkan.


Kemudian browse file xml template dari hardisk komputer.


Klik "Unggah".
Tunggu proses upload hingga selesai dan lihat hasilnya.

allo semua, balik lagi... Selasa kali ini tutorialnya adalah "Cara Menambahkan Feedjit ke Dalam Blog", please look my Blog! ada di paling bawah sebelah itu dia!!!! tapi karena aku baru bikin... jadinya aku baru sedikit, hehehe mau gak??? OK (Ikuti Step)

1. Kalian Buka www.feedjit.com

2. Klik "Choose Your Feedjit".


 3. Pilih yang itu aja, paling pinggir kiri, yang Free.


4. Atur dulu warna warnanya sesuai selera masing masing, atur width and height-nya yaitu luasnya, atur berapa jumlah visitor yang mau ditampilkan, jika sudah Klik GO.


5.  Klik Yang diberi Kotak itu.


6. Tulis nama blog kalian, judul yang mau ditulis, jika sudah Klik tambahkan widget, maka akan tertambah secara otomatis, kalian bisa melihatnya di Tata letak.


7. sekarang buka Blogger. ke tata letak.


8. look! sudah tertambah secara otomatis kan :D


9. Klik Simpan perubahan.

Making Android for everyone

---

Android 4.4 is designed to run fast, smooth, and responsively on a much broader range of devices than ever before — including on millions of entry-level devices around the world that have as little as 512MB RAM.
KitKat streamlines every major component to reduce memory use and introduces new APIs and tools to help you create innovative, responsive, memory-efficient applications.
OEMs building the next generation of Android devices can take advantage of targeted recommendations and options to run Android 4.4 efficiently, even on low-memory devices. Dalvik JIT code cache tuning, kernel samepage merging (KSM), swap to zRAM, and other optimizations help manage memory. New configuration options let OEMs tune out-of-memory levels for processes, set graphics cache sizes, control memory reclaim, and more.
In Android itself, changes across the system improve memory management and reduce memory footprint. Core system processes are trimmed to use less heap, and they now more aggressively protect system memory from apps consuming large amounts of RAM. When multiple services start at once — such as when network connectivity changes — Android now launches the services serially, in small groups, to avoid peak memory demands.
For developers, Android 4.4 helps you deliver apps that are efficient and responsive on all devices. A new API, ActivityManager.isLowRamDevice(), lets you tune your app's behavior to match the device's memory configuration. You can modify or disable large-memory features as needed, depending on the use-cases you want to support on entry-level devices. Learn more about optimizing your apps for low-memory devices here.
New tools give also give you powerful insight into your app's memory use. The procstats tool details memory use over time, with run times and memory footprint for foreground apps and background services. An on-device view is also available as a new developer option. The meminfo tool is enhanced to make it easier to spot memory trends and issues, and it reveals additional memory overhead that hasn't previously been visible.

New NFC capabilities through Host Card Emulation

---

Android 4.4 introduces new platform support for secure NFC-based transactions through Host Card Emulation (HCE), for payments, loyalty programs, card access, transit passes, and other custom services. With HCE, any app on an Android device can emulate an NFC smart card, letting users tap to initiate transactions with an app of their choice — no provisioned secure element (SE) in the device is needed. Apps can also use a new Reader Mode to act as readers for HCE cards and other NFC-based transactions.
Android HCE emulates ISO/IEC 7816 based smart cards that use the contactless ISO/IEC 14443-4 (ISO-DEP) protocol for transmission. These cards are used by many systems today, including the existing EMVCO NFC payment infrastructure. Android uses Application Identifiers (AIDs) as defined in ISO/IEC 7816-4 as the basis for routing transactions to the correct Android applications.
Apps declare the AIDs they support in their manifest files, along with a category identifier that indicates the type of support available (for example, "payments"). In cases where multiple apps support the same AID in the same category, Android displays a dialog that lets the user choose which app to use.
When the user taps to pay at a point-of-sale terminal, the system extracts the preferred AID and routes the transaction to the correct application. The app reads the transaction data and can use any local or network-based services to verify and then complete the transaction.
Android HCE requires an NFC controller to be present in the device. Support for HCE is already widely available on most NFC controllers, which offer dynamic support for both HCE and SE transactions. Android 4.4 devices that support NFC will include Tap & Pay for easy payments using HCE.

Printing framework

---

Android apps can now print any type of content over Wi-Fi or cloud-hosted services such as Google Cloud Print. In print-enabled apps, users can discover available printers, change paper sizes, choose specific pages to print, and print almost any kind of document, image, or file.
Android 4.4 introduces native platform support for printing, along with APIs for managing printing and adding new types of printer support. The platform provides a print manager that mediates between apps requesting printing and installed print services that handle print requests. The print manager provides shared services and a system UI for printing, giving users consistent control over printing from any app. The print manager also ensures the security of content as it's passed across processes, from an app to a print service.
Printer manufacturers can use new APIs to develop their own print services — pluggable components that add vendor-specific logic and services for communicating with specific types of printers. They can build print services and distribute them through Google Play, making it easy for users to find and install them on their devices. Just as with other apps, you can update print services over-the-air at any time.
Client apps can use new APIs to add printing capabilities to their apps with minimal code changes. In most cases, you would add a print action to your Action Bar and a UI for choosing items to print. You would also implement APIs to create print jobs, query the print manager for status, and cancel jobs. This lets you print nearly any type of content, from local images and documents to network data or a view rendered to a canvas.
For broadest compatibility, Android uses PDF as its primary file format for printing. Before printing, your app needs to generate a properly paginated PDF version of your content. For convenience, the printing API provides native and WebView helper classes to let you create PDFs using standard Android drawing APIs. If your app knows how to draw the content, it can quickly create a PDF for printing.
Most devices running Android 4.4 will include Google Cloud Print pre-installed as a print service, as well as several Google apps that support printing, including Chrome, Drive, Gallery, and QuickOffice.

Storage access framework

---

A new storage access framework makes it simple for users to browse and open documents, images, and other files across all of their their preferred document storage providers. A standard, easy-to-use UI lets users browse files and access recents in a consistent way across apps and providers.
Cloud or local storage services can participate in this ecosystem by implementing a new document provider class that encapsulates their services. The provider class includes all of the APIs needed to register the provider with the system and manage browsing, reading, and writing documents in the provider. The document provider can give users access to any remote or local data that can be represented as files — from text, photos, and wallpapers to video, audio, and more.
If you build a document provider for a cloud or local service, you can deliver it to users as part of your existing Android app. After downloading and installing the app, users will have instant access to your service from any app that participates in the framework. This can help you gain exposure and user engagement, since users will find your services more easily.
If you develop a client app that manages files or documents, you can integrate with the storage access framework just by using new CREATE_DOCUMENT or OPEN_DOCUMENT intents to open or create files — the system automatically displays the standard UI for browsing documents, including all available document providers.
You can integrate your client app one time, for all providers, without any vendor-specific code. As users add or remove providers, they’ll continue to have access to their preferred services from your app, without changes or updates needed in your code.
The storage access framework is integrated with the existing GET_CONTENT intent, so users also have access to all of their previous content and data sources from the new system UI for browsing. Apps can continue using GET_CONTENT as a way to let users import data. The storage access framework and system UI for browsing make it easier for users to find and import their data from a wider range of sources.
Most devices running Android 4.4 will include Google Drive and local storage pre-integrated as document providers, and Google apps that work with files also use the new framework.

Low-power sensors

---

Sensor batching

Android 4.4 introduces platform support for hardware sensor batching, a new optimization that can dramatically reduce power consumed by ongoing sensor activities.
With sensor batching, Android works with the device hardware to collect and deliver sensor events efficiently in batches, rather than individually as they are detected. This lets the device's application processor remain in a low-power idle state until batches are delivered. You can request batched events from any sensor using a standard event listener, and you can control the interval at which you receive batches. You can also request immediate delivery of events between batch cycles.
Sensor batching is ideal for low-power, long-running use-cases such as fitness, location tracking, monitoring, and more. It can makes your app more efficient and it lets you track sensor events continuously — even while the screen is off and the system is asleep.
Sensor batching is currently available on Nexus 5, and we're working with our chipset partners to bring it to more devices as soon as possible.

Step Detector and Step Counter

Android 4.4 also adds platform support for two new composite sensors — step detector and step counter — that let your app track steps when the user is walking, running, or climbing stairs. These new sensors are implemented in hardware for low power consumption.
The step detector analyzes accelerometer input to recognize when the user has taken a step, then triggers an event with each step. The step counter tracks the total number of steps since the last device reboot and triggers an event with each change in the step count. Because the logic and sensor management is built into the platform and underlying hardware, you don't need to maintain your own detection algorithms in your app.
Step detector and counter sensors are available on Nexus 5, and we're working with our chipset partners to bring them to new devices as soon as possible.

SMS provider

---

If you develop a messaging app that uses SMS or MMS, you can now use a shared SMS provider and new APIs to manage your app's message storage and retrieval. The new SMS provider and APIs define a standardized interaction model for all apps that handle SMS or MMS messages.
Along with the new provider and APIs, Android 4.4 introduces new semantics for receiving messages and writing to the provider. When a message is received, the system routes it directly to the user's default messaging app using the new SMS_DELIVER intent. Other apps can still listen for incoming messages using the SMS_RECEIVED intent. Also, the system now allows only the default app to write message data to the provider, although other apps can read at any time. Apps that are not the user's default can still send messages — the system handles writing those messages to the provider on behalf of the app, so that users can see them in the default app.
The new provider and semantics help to improve the user's experience when multiple messaging apps are installed, and they help you to build new messaging features with fully-supported, forward-compatible APIs.

New ways to build beautiful apps

---

Full-screen Immersive mode

Now your apps can use every pixel on the device screen to showcase your content and capture touch events. Android 4.4 adds a new full-screen immersive mode that lets you create full-bleed UIs reaching from edge to edge on phones and tablets, hiding all system UI such as the status bar and navigation bar. It's ideal for rich visual content such as photos, videos, maps, books, and games.
In the new mode, the system UI stays hidden, even while users are interacting with your app or game — you can capture touch events from anywhere across the screen, even areas that would otherwise be occupied by the system bars. This gives you a great way to create a larger, richer, more immersive UI in your app or game and also reduce visual distraction.
To make sure that users always have easy, consistent access to system UI from full-screen immersive mode, Android 4.4 supports a new gesture — in immersive mode, an edge swipe from the top or bottom of the screen now reveals the system UI.
To return to immersive mode, users can touch the screen outside of the bar bounds or wait for a short period for the bars to auto-hide. For a consistent user experience, the new gesture also works with previous methods of hiding the status bar.

Transitions framework for animating scenes

Most apps structure their flows around several key UI states that expose different actions. Many apps also use animation to help users understand their progress through those states and the actions available in each. To make it easier to create high-quality animations in your app, Android 4.4 introduces a new transitions framework.
The transitions framework lets you define scenes, typically view hierarchies, and transitions, which describe how to animate or transform the scenes when the user enters or exits them. You can use several predefined transition types to animate your scenes based on specific properties, such as layout bounds, or visibility. There's also an auto-transition type that automatically fades, moves, and resizes views during a scene change. In addition, you can define custom transitions that animate the properties that matter most to your app, and you can plug in your own animation styles if needed.
With the transitions framework you can also animate changes to your UI on the fly, without needing to define scenes. For example, you can make a series of changes to a view hierarchy and then have the TransitionManager automatically run a delayed transition on those changes.
Once you've set up transitions, it's straightforward to invoke them from your app. For example, you can call a single method to begin a transition, make various changes in your view hierarchy, and on the next frame animations will automatically begin that animate the changes you specified.
For custom control over the transitions that run between specific scenes in your application flow, you can use the TransitionManager. The TransitionManager lets you define the relationship between scenes and the transitions that run for specific scene changes.

Translucent system UI styling

To get the most impact out of your content, you can now use new window styles and themes to request translucent system UI, including both the status bar and navigation bar. To ensure the legibility of navigation bar buttons or status bar information, subtle gradients is shown behind the system bars. A typical use-case would be an app that needs to show through to a wallpaper.

Enhanced notification access

Notification listener services can now see more information about incoming notifications that were constructed using the notification builder APIs. Listener services can access a notification's actions as well as new extras fields — text, icon, picture, progress, chronometer, and many others — to extract cleaner information about the notification and present the information in a different way.

Chromium WebView

Android 4.4 includes a completely new implementation of WebView that's based on Chromium. The new Chromium WebView gives you the latest in standards support, performance, and compatibility to build and display your web-based content.
Chromium WebView provides broad support for HTML5, CSS3, and JavaScript. It supports most of the HTML5 features available in Chrome for Android 30. It also brings an updated version of the JavaScript Engine (V8) that delivers dramatically improved JavaScript performance.
In addition, the new Chromium WebView supports remote debugging using Chrome DevTools. For example, you can use Chrome DevTools on your development machine to inspect, debug, and analyze your WebView content live on a mobile device.
The new Chromium WebView is included on all compatible devices running Android 4.4 and higher. You can take advantage of the new WebView right away, and with minimum modifications to existing apps and content. In most cases, your content will migrate to the new implementation seamlessly.

New media capabilities

---

Screen recording

Now it's easy to create high-quality video of your app, directly from your Android device. Android 4.4 adds support for screen recording and provides a screen recording utility that lets you start and stop recording on a device that's connected to your Android SDK environment over USB. It's a great new way to create walkthroughs and tutorials for your app, testing materials, marketing videos, and more.
With the screen recording utility, you can capture video of your device screen contents and store the video as an MP4 file on the device. You can record at any device-supported resolution and bitrate you want, and the output retains the aspect ratio of the display. By default, the utility selects a resolution equal or close to the device's display resolution in the current orientation. When you are done recording, you can share the video directly from your device or pull the MP4 file to your host computer for post-production.
If your app plays video or other protected content that you don’t want to be captured by the screen recorder, you can use SurfaceView.setSecure() to mark the content as secure.
You can access screen recording through the adb tool included in the Android SDK, using the command adb shell screenrecord. You can also launch it through the DDMS panel in Android Studio.

Resolution switching through adaptive playback

Android 4.4 brings formal support for adaptive playback into the Android media framework. Adaptive playback is an optional feature of video decoders for MPEG-DASH and other formats that enables seamless change in resolution during playback. The client can start to feed the decoder input video frames of a new resolution and the resolution of the output buffers change automatically, and without a significant gap.
Resolution switching in Android 4.4 lets media apps offer a significantly better streaming video experience. Apps can check for adaptive playback support at runtime using existing APIs and implement resolution-switching using new APIs introduced in Android 4.4.

Common Encryption for DASH

Android now supports the Common Encryption (CENC) for MPEG-DASH, providing a standard, multiplatform DRM scheme for managing protecting content. Apps can take advantage of CENC through Android's modular DRM framework and platform APIs for supporting DASH.

HTTP Live Streaming

Android 4.4 updates the platform's HTTP Live Streaming (HLS) support to a superset of version 7 of the HLS specification (version 4 of the protocol). See the IETF draft for details.

Audio Tunneling to DSP

For high-performance, lower-power audio playback, Android 4.4 adds platform support for audio tunneling to a digital signal processor (DSP) in the device chipset. With tunneling, audio decoding and output effects are off-loaded to the DSP, waking the application processor less often and using less battery.
Audio tunneling can dramatically improve battery life for use-cases such as listening to music over a headset with the screen off. For example, with audio tunneling, Nexus 5 offers a total off-network audio playback time of up to 60 hours, an increase of over 50% over non-tunneled audio.
Media applications can take advantage of audio tunneling on supported devices without needing to modify code. The system applies tunneling to optimize audio playback whenever it's available on the device.
Audio tunneling requires support in the device hardware. Currently audio tunneling is available on Nexus 5 and we're working with our chipset partners to make it available on more devices as soon as possible.

Audio monitoring

Apps can use new monitoring tools in the Visualizer effect to get updates on the peak and RMS levels of any currently playing audio on the device. For example, you could use this creatively in music visualizers or to implement playback metering in a media player.

Loudness enhancer

Media playback applications can increase the loudness of spoken content by using the new LoudnessEnhancer effect, which acts as compressor with time constants that are specifically tuned for speech.

Audio timestamps for improved AV sync

The audio framework can now report presentation timestamps from the audio output HAL to applications, for better audio-video synchronization. Audio timestamps let your app determine when a specific audio frame will be (or was) presented off-device to the user; you can use the timestamp information to more accurately synchronize audio with video frames.

Wi-Fi CERTIFIED Miracast™

Android 4.4 devices can now be certified to the Wi-Fi Alliance Wi-Fi Display Specification as Miracast compatible. To help with testing, a new Wireless Display developer option exposes advanced configuration controls and settings for Wireless Display certification. You can access the option at Settings > Developer options > Wireless display certification. Nexus 5 is a Miracast certified wireless display device.

RenderScript Compute

---

Ongoing performance improvements

When your apps use RenderScript, they'll benefit from ongoing performance tuning in the RenderScript runtime itself, without the need for recompilation. The chart at right shows performance gains in Android 4.4 on two popular chipsets.

GPU acceleration

Any app using RenderScript on a supported device benefits from GPU acceleration, without code changes or recompiling. Since the Nexus 10 first debuted RenderScript GPU acceleration, various other hardware partners have added support.
Now with Android 4.4, GPU acceleration is available on the Nexus 5, as well as the Nexus 4, Nexus 7 (2013), and Nexus 10, and we're working with our partners to bring it to more devices as soon as possible.

RenderScript in the Android NDK

Now you can take advantage of RenderScript directly from your native code. A new C++ API in the Android Native Development Kit (NDK) lets you access the same RenderScript functionality available through the framework APIs, including script intrinsics, custom kernels, and more.
If you have large, performance-intensive tasks to handle in native code, you can perform those tasks using RenderScript and integrate them with your native code. RenderScript offers great performance across a wide range of devices, with automatic support for multi-core CPUs, GPUs, and other processors.
When you build an app that uses the RenderScript through the NDK, you can distribute it to any device running Android 2.2 or or higher, just like with the RenderScript support library available for framework APIs.

Graphics

---

GLES2.0 SurfaceFlinger

Android 4.4 upgrades its SurfaceFlinger from OpenGL ES 1.0 to OpenGL ES 2.0.

New Hardware Composer support for virtual displays

The latest version of Android Hardware Composer, HWComposer 1.3, supports hardware composition of one virtual display in addition to the primary, external (e.g. HDMI) display, and has improved OpenGL ES interoperability.

New Types of Connectivity

---

New Bluetooth profiles

Android 4.4 support for two new Bluetooth profiles to let apps support a broader range of low-power and media interactions. Bluetooth HID over GATT (HOGP) gives apps a low-latency link with low-power peripheral devices such as mice, joysticks, and keyboards. Bluetooth MAP lets your apps exchange messages with a nearby device, for example an automotive terminal for handsfree use or another mobile device. As an extension to Bluetooth AVRCP 1.3, users can now set absolute volume on the system from their Bluetooth devices.
Platform support for HOGP, MAP, and AVRCP is built on the Bluedroid Bluetooth stack introduced by Google and Broadcom in Android 4.2. Support is available right away on Nexus devices and other Android-compatible devices that offer compatible Bluetooth capabilities.

IR Blasters

Android 4.4 introduces platform support for built-in IR blasters, along with a new API and system service that let you create apps to take advantage them.
Using the new API, you can build apps that let users remotely control nearby TVs, tuners, switches, and other electronic devices. The API lets your app check whether the phone or tablet has an infrared emitter, query it's carrier frequencies, and then send infrared signals.
Because the API is standard across Android devices running Android 4.4 or higher, your app can support the broadest possible range of vendors without writing custom integration code.

Wi-Fi TDLS support

Android 4.4 introduces a seamless way to stream media and other data faster between devices already on the same Wi-Fi network by supporting Wi-Fi Tunneled Direct Link Setup (TDLS).

Accessibility

---

System-wide settings for closed captioning

Android 4.4 now supports a better accessibility experience across apps by adding system-wide preferences for Closed Captioning. Users can go to Settings > Accessibility > Captions to set global captioning preferences, such as whether to show captions and what language, text size, and text style to use.
Apps that use video can now access the user's captioning settings and adjust presentation to meet the user's preferences. A new captioning manager API lets you check and monitor the user's captioning preferences. The captioning manager provides you with the user's preferred captioning state as well as preferred locale, scaling factor, and text style. The text style includes foreground and background colors, edge properties, and typeface.
In addition, apps that use VideoView can use a new API to pass a captioning stream along with a video stream for rendering. The system automatically handles the display of the captions on video frames according to the user's systemwide settings. Currently, VideoView supports auto-display of captions in WebVTT format only.
All apps that show captions should make sure to check the user's systemwide captioning preferences and render captions as closely as possible to those preferences. For more insight into how specific combinations of settings should look, you can look at a preview of captions in different languages, sizes, and styles right in the Settings app.

Enhanced Accessibility APIs

Android 4.4 extends the accessibility APIs to support more precise structural and semantic description and observation of onscreen elements. With the new APIs, developers can improve the quality of accessible feedback by providing accessibility services with more information about on-screen elements.
In accessibility nodes, developers can now determine whether a node is a popup, get its input type, and more. You can also use new APIs to work with nodes that contain grid-like information, such as lists and tables. For example, you can now specify new supported actions, collection information, live region modes, and more.
New accessibility events let developers more closely follow the changes that are taking place in window content, and they can now listen for changes in the touch exploration mode on the device.

Support for international Users

---

Drawable mirroring for RTL locales

If your app is targeting users who use RTL scripts, you can use a new API to declare that a drawable should be auto-mirrored when the user's locale setting includes an RTL language.
Declaring a drawable as auto-mirrored helps you prevent duplication of assets in your app and reduces the the size of your APK. When you have drawables that are the reusable for both LTR and RTL presentations, you can declare the default versions as auto-mirrored and then omit those Drawables from your RTL resources.
You can declare various types of drawables as auto-mirrored in your application code, such as bitmap, nine-patch, layer, state list, and other drawables. You can also declare a drawable as auto-mirrored in your resource files by using a new attribute.

Force RTL Layout

To make it easier to test and debug layout mirroring issues without switching to an RTL language, Android includes a new developer option to force RTL layout direction in all apps.
The Force RTL layout option switches the device to RTL layout for all locales and displays text in your current language. This can help you find layout issues across your app, without having to display the app in an RTL language. You can access the option in Settings > Developer options > Force RTL layout direction.

Security enhancements

---

SELinux (enforcing mode)

Android 4.4 updates its SELinux configuration from "permissive" to "enforcing." This means potential policy violations within a SELinux domain that has an enforcing policy will be blocked.

Improved cryptographic algorithms

Android has improved its security further by adding support for two more cryptographic algorithms. Elliptic Curve Digital Signature Algorithm (ECDSA) support has been added to the keystore provider improving security of digital signing, applicable to scenarios such as signing of an application or a data connection. The Scrypt key derivation function is implemented to protect the cryptographic keys used for full-disk encryption.

Other enhancements

On multiuser devices, VPNs are now applied per user. This can allow a user to route all network traffic through a VPN without affecting other users on the device. Also, Android now supports FORTIFY_SOURCE level 2, and all code is compiled with those protections. FORTIFY_SOURCE has been enhanced to work with clang.

Tools for analyzing memory use

---

Procstats

A new tool called procstats helps you analyze the memory resources your app uses, as well as the resources used by other apps and services running on the system.
Procstats keeps track of how apps are running over time, providing data about their execution durations and memory use to help determine how efficiently they are performing. This is most important for apps that start services that run in the background, since it lets you monitor how long they are running and how much RAM they are using while doing so. Procstats will also collect data for foreground applications about memory use over time to determine the overall memory profile of the app.
Procstats can help you identify background services started by your app. You can keep track of how long those services continue running and how much RAM they use while doing so. Procstats also lets you profile your app while it's in the foreground, using its memory use over time to determine its overall memory profile.

On-device memory status and profiling

Android 4.4 includes a new developer option to make it easier to analyze your app's memory profile while it's running on any device or emulator. It's especially useful to get a view of how your app uses memory and performs on devices with low RAM. You can access the option at Settings > Developer options > Process stats
The Process Stats option shows you a variety of high-level metrics on your app's memory use, based on data collected using the new procstats service. On the main screen you can see a summary of system memory status. Green indicates relative amount of time spent with low RAM usage, yellow indicates moderate RAM usage, and red indicates high (critical) RAM usage
Below the summary is a list summarizing each app's memory load on the system. For each app, a blue bar indicates the relative computed memory load (runtime x avg_pss) of its process, and a percentage number indicates the relative amount of time spent in the background. You can filter the list to show only foreground, background, or cached processes, and you can include or exclude system processes. You can also change the duration of the data collected to 3, 6, 12, or 24 hours, and you can include or exclude uss memory.
To take a closer look at a specific app's memory usage in isolation, tap the app. For each app, you can now see a summary of the memory consumed and the percentage of the collection interval that the app has been running. You can also see the average and maximum usage over the collection period, and below the app's services and the percentage of time they've been running.
Analyzing your app using the data in Process Stats can reveal issues and suggest possible optimizations for your app. For example, if your app is running longer than it should or using too much memory over a period of time, there could be bugs in your code that you can resolve to improve your app's performance, especially when running on a device with low RAM.

• widget dilengkapi dengan tombol sosial sepert facebook, twitter dan google+.
• menggunakan jQuery yang sederhana sehingga lebih cepat saat load
• mengapung sampai bagian komentar blog
• sebuah ikon link komentar yang akan mengarahkan pengunjung ke kotak komentar
  
  

LIVE DEMO

Menambahkan Horizontal Floating Share Bar di blog :

• Login ke Blogger Anda - klik Template dan pilih Edit HTML
• Cari tag </head>, gunakan Ctrl+F untuk mencari
• Selanjutnya salin kode dibawah ini tepat sebelum tag </head>

<b:if cond='data:blog.pageType == &quot;item&quot;'>
<style type='text/css'>
/*<![CDATA[*/
　　　 .horizontalsocial .sharertitle{float: left; border-right: 1px solid #d2d2d2; padding: 3px 10px 2px 0px; margin: 0 0px 0 0; color: #b1a9a5; font-family:'Oswald', Arial, Helvetica, sans-serif;text-transform: uppercase; line-height: 25px; vertical-align: middle;　 font-size: 14px;}
　　　 .horizontalsocial .fb-like{width: 100px; float: left; border-right: 1px solid #d2d2d2; padding: 3px 0 2px;　 height: 25px; }
　　　 .horizontalsocial .sharertwitter{float: left; width: 115px; border-right: 1px solid #d2d2d2; margin: 0 15px 0 0; padding: 3px 0 2px; height: 25px;}
　　　 .horizontalsocial .sharergplus{float: left; width: 90px; margin: 0 15px 0 15px; padding: 3px 0 2px; border-right: 1px solid #d2d2d2; height: 25px;}
　　　 .horizontalsocial .sharerbubble{background: url(https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhk6VzKgb3hDkX6Aq20NrqpOlwjs91dgZ1QfX-SnZxKtrL7TmfPEV68cGgUPsEUuMoc_wQmenpd6HBmvmmL_X0ieJRrCbm1rdqJpbVp5WjJ8ZMjAcIr2_ghLUN5gnZehIeeYQoZyNDcydg/s1600/Commentz.png) no-repeat;　 height: 25px; min-width: 25px; float: left; margin: 7px 0 0; line-height: 18px; vertical-align: top;}
　　　 .horizontalsocial .sharerbubble a{color: #2d2520;　 padding: 0px 0 0px 30px; font-size: 18px !important; font-family: 'Lora', Arial, Helvetica, san-serif !important; }
　　　 .horizontalsocial.fixed{ position:fixed; top: -2px; z-index: 99999;}
　　　 #w2bSocialFloat {clear:both;padding: 6px 0;display:block;background:#FFFFFF;}
　　　 #w2bSocialFloat td{padding:4px;margin:0;border:none;}
　　　 #w2bSocialFloat td iframe{max-width:82px;width:82px !important;}
　　　 #w2bSocialFloat.w2bFloatSocial{position: fixed;top:0;z-index:9999999;border-bottom:1px solid #ccc;-webkit-box-shadow:0 1px 1px rgba(0,0,0,0.15);-moz-box-shadow:0 1px 1px rgba(0,0,0,0.15);box-shadow:0 1px 1px rgba(0,0,0,0.15);}
/*]]>*/
</style>
<script type="text/javascript">
/*<![CDATA[*/
// Set the Top Offset
$theOffset = 0;

jQuery(document).ready(function(b){var a=b("#w2bSocialFloat");a.wrap('<div id="w2bSocialPlaceholder"></div>').closest("#w2bSocialPlaceholder").height(a.outerHeight());a.width(a.outerWidth());e=a.offset().top-$theOffset;b("#w2bSocialFloat iframe[src*=plusone]").closest("div").css("max-width","82px");b(window).scroll(function(){d=b(this).scrollTop();d>=e?a.addClass("w2bFloatSocial"):a.removeClass("w2bFloatSocial");f=b(".post");if(f.length!=0){c=f.outerHeight()+f.offset().top;d>=c?a.stop().animate({top:"-150px"}):a.stop().animate({top:$theOffset+"px"})}else d>=e?a.css("top",$theOffset+"px"):a.css("top","0")})});
/*]]>*/
</script>
<script type="text/javascript" src="http://widgets.way2blogging.org/blogger-widgets/w2b-blogger-pinit.js"></script>
<script type="text/javascript">
/*<![CDATA[*/
　　　 // Twitter
　 　　 (function(a,b,c){var d=a.getElementsByTagName(b)[0];if(!a.getElementById(c)){a=a.createElement(b);a.id=c;a.src="//platform.twitter.com/widgets.js";d.parentNode.insertBefore(a,d)}})(document,"script","twitter-wjs");
　　　 // Google + (plus)
　　　 (function(){var a=document.createElement("script");a.type="text/javascript";a.async=true;a.src="https://apis.google.com/js/plusone.js";var b=document.getElementsByTagName("script")[0];b.parentNode.insertBefore(a,b)})();

/*]]>*/
</script>
</b:if>

• langkah selanjutnya cari kode dibawah ini, gunakan Ctrl+F :

<data:post.body/>

• kemudian salin script dibawah ini tepat diatas <data:post.body/> :

<b:if cond='data:blog.pageType == &quot;item&quot;'>
<div class='horizontalsocial social-buttons' id='horizontalsocial'>
<div class='w2bSocialFloat' id='w2bSocialFloat'>
<table class='w2bSocialFloat' width='100%'>
　　　 <tr>
<td><div class='sharertitle'>Socialize It &#8594;</div>
</td>
　　　 　　　 <td>
　　　 　　　 　　　 <div class='sharertwitter'><a class='twitter-share-button' expr:data-text='data:post.title' expr:data-url='data:post.url' href='https://twitter.com/share'>Tweet</a></div>
　　　 　　　 </td>

　　　 　　　 <td>
　　　 　　　 <div class='fb-like'>　　　 <iframe allowTransparency='true' expr:src='&quot;//www.facebook.com/plugins/like.php?href=&quot; + data:post.url + &quot;&amp;send=false&amp;layout=button_count&amp;width=80&amp;show_faces=false&amp;action=like&amp;colorscheme=light&amp;font&amp;height=21&quot;' frameborder='0' scrolling='no' style='border:none; overflow:hidden; width:80px; height:21px;'/></div>
　　　 　　　 </td>
　　　 　　　
　　　 　　　 <td>
　　　 　　　 <div class='sharergplus'>　　　 <div class='g-plusone' data-size='medium' expr:data-href='data:post.url'/></div>
　　　 　　　 </td>
　　　 　　　
　　　 　　　 <td>
<div class='sharerbubble'><span class='thecomments'>
<b:if cond='data:post.allowComments'>
<a class='comment-link' expr:href='data:post.addCommentUrl' expr:onclick='data:post.addCommentOnclick'><b:if cond='data:post.numComments == 1'>1 <b:else/><data:post.numComments/> </b:if></a>
</b:if>
</span></div>
</td>
　　　 </tr>
</table>
</div></div>
</b:if>

• Terakhir, klik Simpan template - selesai !

Tambahan :
Untuk menghilangkan fitur melayang, hapus script yang berwarna merah dan Anda juga bisa mengganti ikon komentar dengan ikon yang komentar yang Anda miliki cukup ganti link url yang berwarna kuning dengan link url ikon Anda.

Saya telah menambahkan Widget Horizontal Floating Share Bar ini diblog saya, bisa Anda lihat dibawah judul posting. Seperti biasa semoga artikel ini bermanfaat buat Anda semua dan bila Anda mengalami kesulitan tidak ada salahnya untuk berbagi dengan saya.

At the end of 2013 we saw Apple release pretty much every mobile device we'd been expecting, except for the iPhone 6. While that didn't come out, by seeing the iPad Air, iPad Mini with Retina Display, iPhone 5s and iOS 7, we at least got a great glimpse of what the company has been up to and where it will go in the future.
With the usual rumours starting to appear, we can start to build up a picture of what we can expect from the iPhone 6. In this article we're doing exactly that, looking at the best release date, price and specs information, filtering the rubbish to help build a clearer picture.

iPHONE 6 SCREEN

The one thing that everyone seems to be able to agree on is that the iPhone 6 will have a larger screen than any other iOS smartphone before it. There's a definite market for large-screen phones, as we've seen with the HTC One, Sony Xperia Z and Samsung Galaxy S4, so it makes sense for Apple to compete on screen size.
The question that has to be answered is, how big will the screen be? Early rumours suggested that there would be a 4.8in screen, but more recent rumours have suggested that the iPhone 6 could have a 5in screen.
According to Japanese tech publication MacFun, the 5in screen will have a Full HD resolution of 1,920x1,080. From a certain point of view this makes a lot of sense, as there are already a lot of Full HD phones out there. However, we think that the resolution could be wrong, mostly because of the way that Apple works.
Generally speaking Apple likes resolutions that scale easily from previous products, so it and developers know how apps will look on-screen. Full HD doesn't do this from the existing iPhone or iPads. We think that Apple could quadruple the existing iPhone 5S's screen resolution, giving an iPhone 6 with a resolution of 2,272x1,280 instead. We've covered why the iPhone 6 won't have a Full HD screen in more detail.
While Apple has not previously made a large-screen phone, upping the screen size for the iPhone 6 makes a lot of sense. It means it can compete with the large-screen phones from other manufacturers and keep the iPhone 5S as a smaller alternative, giving iPhone users more choice.

iPHONE 6 TWO SCREEN SIZES

Rumours that the iPhone 6 will come in two screen sizes simply won't go away. The most recent information comes from leaked information from Foxconn executives (unnamed, of course), reported by BGR.
According to this information, the iPhone 6 will ship in 4.7in and a phablet-sized 5.7in. This would be the first time that Apple has launched one mobile product in two sizes, but the company is apparently ready to make an exception this time around.
Even more fuel was poured on to the fire of this rumour, this time with information that a 4.7in iPhone 6 to be joined by 5.6in iPhone phablet.
According to Taiwan's Economic Daily News, Apple is set to launch a new phablet alongside the iPhone 6, with a 5.6in screen size. The site is reporting that Apple will not launch this product under the iPhone brand. There's no information as to what the product will be called, but it's possible that it could fall under the iPad category.
According to the reports, the new product is a result of Apple experimenting with screen sizes. In some ways it makes sense to have the larger product, as it gives consumers more choice and lets Apple compete with its competition at all screen sizes.
The new device will apparently have a sapphire glass screen, making it extremely tough and durable. Unfortunately, that's all the information that we have for the time being.
We're not entirely sure that we believe these rumours. We know that Apple was reportedly trying different screen sizes, but trying and releasing are two completely different things. With all of its existing mobile range, Apple has kept things simple by having just one screen size; complicating the line-up with two screen sizes doesn't feel like the kind of thing that the company would do.
Besides, Apple already has the smaller iPhone 5S, so we'd imagine that this will sit alongside the iPhone 6 as the smaller handset. We can't completely rule out this rumour, but given by past form, we'd say that the iPhone 6 available in one screen size seems more likely.

iPHONE 6 SIZE

ETNews has been reporting that the iPhone 6 will be the slimmest iPhone yet. In fact, at a reported 6mm thick, the iPhone 6 would shave 1.6mm off of the iPhone 5. It would also make the iPhone 6 half the thickness of the iPhone 3GS.
Making the iPhone slimmer also raises the question, will it be called the iPhone 6 at all? When Apple made the iPad slimmer and smaller, it went with iPad Air. Plenty of people believe that the iPhone 6 could be the iPhone Air instead.
It would make sense in a way, as Apple could continue to sell the iPhone 5S as the smaller screen version and have the iPhone Air as the slim, large-screen model

iPHONE 6 RELEASE DATE

The short version is that nobody really knows when the iPhone 6 is coming out. A lot of guesses have been made, but they're largely wrong. That said, here's what we can work out with a bit of logical thinking.
If Apple sticks to its usually release schedule, the iPhone 6 would follow a year after the iPhone 5S, which would mean that it would be out September 2014. However, with the iPhone 6 it feels more like something different and complementary, in some ways, to the iPhone 5S. In fact, we'd say that it was more like an addition to the line-up than a strict replacement of the iPhone 5S. We kind of see it replicating what Samsung has with the full-size Galaxy S4 and the Samsung Galaxy S4 Mini, with the exception that Apple's small phone, the 5S, is still really powerful.
If we had to be pushed on a date, we'd say that early this year, between March and May would make sense. This would give Apple enough distance from the iPhone 5S, and give it a chance to take the limelight away from Samsung, which will be looking to release its Galaxy S5 handset around the same time.
Some rumours point to a May 2014 launch of the iPhone 6 as the most likely. According to Digitimes and its supply chain sources, Apple is gearing up for a May launch of the new iPhone.
It reported that the new iPhone will use a "20nm processor manufactured by Taiwan Semiconductor Manufacturing Company (TSMC)", although the sources didn't mention any other specifications. However, from all of the other rumours out there, we've managed to cobble together some of the expected specifications, including a larger screen.
However, the phone may get released after that and, as we warned, there are many conflicting reports. First, Investor's Business Daily has reported on a market report by Susquehanna Financial Group analyst, Mehdi Hosseini.
In Hosseini's research, he reported that SanDisk is likely to be one of the prime beneficiaries of the iPhone 6, supplying flash memory to Apple. The site then reports that the iPhone is due to be launched in June or July 2014, with Hosseini reporting, "Although there is no color yet on the iPhone 6 specs, our recent checks in Taiwan and Korea suggest Apple has already begun negotiating with its memory suppliers to secure capacities."
More recent rumours suggest that the iPhone 6 could be released in June. According to Eldar Murtazin, the next iPhone is coming soon.

This kind of information is always hard to vet, but Murtazin has good form. He predicted the launch of the Galaxy S4 correctly and has said that the Samsung Galaxy S5 will launch on the 23 February.
According to Murtazin's Tweet, the iPhone 6 would go on sale in June. Realistically, this means that the official launch we be a few weeks ahead of this, so a May launch sounds quite plausible at this point.
Murtazin also said that this sees a move to shorter product cycles, meaning that we're likely to see new flagship handsets more frequently. There are several reasons why Apple might take this route, including competing more closely with Samsung, which is due to the launch the Galaxy S5 soon, and that the iPhone 6 will sit alongside, rather than replacing, the iPhone 5S.
We don't have too long to wait to find out if these rumours are true, and we'll bring you more release date rumours as we have them.

iPHONE 6 TOUGHER CONSTRUCTION

Although beautifully made, the iPhone is just as breakable as any other smartphone, with plenty of people walking around with cracked screens after a drop. Apple appears to be working on a solution to this problem, toughening up its products.
A new deal could signal a super-tough sapphire screen for the iPhone 6. According to reports, Apple has struck a deal with GT Advanced technologies to produce sapphire glass in a plant in Arizona.
The deal was announced by GT Advanced Technologies in a regulatory filing. "The sapphire glass that GT will make in the facility will be used to cover the camera lenses in Apple's phones and the fingerprint-reading devices in its latest products. GT's technology also can be used to make scratchproof glass covers for smartphones, although it is not used for that purpose by Apple today".
Apple is due to pay $578m, which GT Advanced Technologies will use to buy and operate sapphire production equipment in a new Arizona facility. GT Advanced Technologies will pay back the Apple over a five-year period.
While the deal should, in the short-term, provide Apple with the materials it needs for existing components, there's a long-term plan, too. As part of the deal, GT Advanced Technologies will "deliver low cost, high volume manufacturing of sapphire material" using a large-capacity furnace.
Synthetic sapphire glass gets its name because it's transparent, although it's not technically glass. However, sapphire's advantage over glass is its incredible durability and hardiness. Sapphire has a value of 9 on the Mohs scale of mineral hardness, putting it just behind diamond. This means that it's extremely difficult to break, resulting in fewer broken iPhones, saving money in repair costs.
As well as looking at the screen, Apple is also said to be looking at toughening up the case by investigating liquid metal for the iPhone 6. Liquid metal would encase the iPhone 6 is a super-tough metal, built up layer-by-layer, making it a lot hardier and more difficult to break. According to new information, Apple has put in five patents for liquid metal.
One describes how bulk metallic glasses (BMG, or liquid metal to give it the more familiar name) would be layered on top of each other to create components. The main focus on this invention is via 3D printing, allowing Apple to build components and cases from computer-generated designs.
What's more Patently Apple, which found the information, believes that Apple has already used liquid metals in the iPhone 5S, suggesting that the technology is already available. It's clear, then, that Apple is interested in liquid metal for the iPhone and iPad range, so it's now a matter of when.

Liquid metal could make the iPhone 6 a lot tougher than previous models

iPHONE 6 CAMERA

For the iPhone 5S Apple upped the physical size of its 8-megapixel sensor, meaning that each pixel gets more light. In addition, it upgraded the lens from an f/2.4 model to an f/2.2 model, increasing low-light performance again. Combined with the A7 SoC, the camera has a couple of neat modes, including a 10fps burst mode that goes on until the phone's memory is full, and a 120fps slow-motion mode.
It would make sense if Apple was to use this sensor in the iPhone 6, although, given it's a bigger phone, with more room inside for components, it could well up the pixel count, with a 12- or 13-megapixel on the cards.
Apple may also be considering going in a completely different direction, particularly if a new patent is to be used. This suggests that the iPhone 6 could get a refocus-able lightfield camera.
Reported by 9to5Mac, a patent has been granted to Apple for a lightfield camera, allowing people to refocus their shots after they've been taken.
The technology works by capturing light fields, rather than a single 2D capture of the moment. The net result is that a photo is no longer a fixed capture, but one where you can select a part of the picture to completely refocus the image.
We've already seen the technology in use with the Lytro Light Field camera. It's an interesting product, using software to let you choose the point of focus after the image has already been capture. You can see an example of this in the shot below.
Part of the problem with the system is that the Lytro camera only took low-resolution photos, which were no good for printing at a later date. Upping the resolution isn't that easy and, by the details of the patent, not something that Apple is going to do. Instead, the patent refers to a high-resolution and low-resolution mode, with the patent covering a "digital camera system configurable to operate in a low-resolution refocusable mode and a high-resolution non-refocusable mode".
From the sounds of this, the lightfield option would be an option in the camera mode, much as Slo-Mo is with the iPhone 5S. The Slo-Mo editing tools, which are easy-to-use and incredibly intuitive, so if Apple can bring the same approach to lightfield, it could offer a completely different smartphone photography experience.
The patent contains no information as to when or if Apple will use the technology, particularly as it could be hard to slim it down to fit into a smartphone. Still, we can just hope that it will be ready for use in the iPhone 6.
Something that seems a lot more likely is the iPhone 6 to get optical image stabilisation (OIS). This all stems from the rumours that Apple is keen to make the photography better on the iPhone 6, focusing on quality over specifications. While the sensor looks set to stay at 8-megapixels, OIS could help reduce shake and improve photography, particularly in low light.
The information comes from The China Post, quoting from Nomura Securities, stating that Apple "may adopt an 8 mega-pixel (MP) camera with improved optical image stabilization on its upcoming handset, instead of the 16 MP upgrade anticipated by industry observers".
This information follows an Apple patent for improved autofocus and OIS. Information in the patent shows that Apple plans to use a lens actuator module that contains an autofocus mechanism "capable of moving a lens according to at least three degrees of freedom" and an OIS mechanism ""capable of moving the lens according to at least two degrees of freedom".
If this information turns out to be true, we're pleased. We've long said that more megapixels doesn't lead to better quality (quite the opposite in many cases), so focusing on the core components and increasing quality is a much better idea.

iPHONE 6 STORAGE

In terms of storage, 64GB has been the top model for a couple of years, and continues to be so for the iPhone 5S. We're not expecting this to change for the iPhone 6, although we know that the Apple can make a 128GB model, thanks to the recent launch of a 128GB iPad 4.
The new model doubled the maximum capacity of the previous high-end iPad (64GB). This update was said to be about increasing the variety of uses for the tablet, with Apple stating that more storage was good for large files for use in applications such as CAD and music production. It's also a more useful amount of storage for photos and videos.

iPHONE 6 A7 SoC

At the moment, the Apple A7 system-on-a-chip (SoC) is the main focus for the company. This is the first 64-bit mobile chip and it's extremely fast. In fact, in our benchmarks on using the iPhone 5S, we found that the A7 is by far the fastest mobile processor. Apple has now used the A7 chip in both the iPad Air and iPad Mini with Retina Display.
Where as in the past Apple had to tweak the graphics part of the SoC to work on an iPad's screen by adding quad-core graphics (the latest chip with the A6X), with the A7 this isn't required. Instead, the A7 is fast enough as it is.
With that in mind we'd expect to see the same chip used in the iPhone 6. However, the only caveat is when the phone comes out. If it's early next year then we'd expect the A7 chip to be used as is; if the release date is closer to the end of next year, then we could see a tweaked version, perhaps even a quad-core variant.

iPHONE 6 PRICE

Apple typically releases its new models at the same price as the old ones. If that holds out, then, and assuming that the 16GB model is dropped, we'd expect the 32GB model to cost £529, the 64GB model £599 and the 128GB model £699. However, if the company continues to sell the iPhone 5S, we could be in for some new pricing, with the iPhone 6 a premium model that sits above it, in which case all bets are off and we have no idea how much it will be.
If Apple does decide to make an iPhone with a larger screen, there's also a good chance prices will increase too. Susquehanna analyst Chris Caso, speaking to AllThingsD, predicted that there could be a $50 to $100 premium for a larger iPhone 6, compared to the 4in iPhone 5s.
Although this goes against Apple's tradition of keeping prices the same across generations, it's not a rule the company is afraid to break every now and then. Last month's iPad Mini with Retina display launch introduced a $70 premium over the entry level model, so a price hike isn't out of the question.

iPHONE 6 MOBILE PAYMENTS SYSTEM

As the smartphone become more ubiquitous it makes sense for it to be at the heart of everything we do, including paying for goods. Now, Time Cook, Apple's CEO, has dropped a rather massive hint that Apple is looking at a mobile payments system, which could launch with the iPhone 6.
Reported by [a href="http://business.time.com/2014/01/30/apples-next-big-thing-could-be-allowing-you-to-easily-pay-for-stuff/"], Cook told investors on a recent earnings call, "You can tell by looking at the demographics of our customers and the amount of commerce that goes through iOS devices…that it’s a big opportunity on the platform."
The question is, how will Apple approach this. Current mobile payments systems rely on NFC. There are plenty of NFC readers in shops now, providing contactless payments via card and phone for transactions of up to £20. However, Apple has so far shunned NFC, refusing to introduce the technology in any of its smartphones or tablets.
Following this, we could assume that Apple will want to go its own way. On its side is the fact that Apple is actually already one of the biggest companies dealing with mobile payments, thanks to the collection of credit card details and payments it processes through iTunes and the App Store. It would make sense for Apple to find a way to open up its systems and start letting people pay for goods in stores.
One way it could do this is with iBeacon. This indoor positioning system uses Bluetooth Low Energy (BLE), letting low-cost transmitters advertise their presences to iOS 7 devices. For example, the system can be used to broadcast offers in a shop alongside a payment system. In fact, Apple already uses this technology in its stores to let customers pay for goods without having to approach a till.
Apple could roll out iBeacon to other shops, making it an addition, not replacement, to NFC terminals. The benefit of Apple's system, particularly if used with verification, such as through TouchID, is that it could allow transactions of any value, rather than the £20 limit of today.

BEWARE FAKE PHOTOS

The problem with reporting on a product that doesn't officially exist is working out which leaks are real and which ones are just made up. Sadly, the most recent iPhone 6 photos have proven to be fake.
Posted by a Twitter user, @mornray886, the photos purported to show the iPhone 6. However, closer inspection showed that things weren't quite as they appeared. For starters, the Twitter user was new and had only posted up these pictures.
Secondly, the phone was covered in protective plastic, but both the front and back had identical air bubbles. Finally, a Reddit user showed that the fingerprint smudges were lifted from an iPad render made by Martin Hajek. This proved that the iPhone 6 photos were just an artist's rendering.

Don't believe the hype, this isn't the iPhone 6
We're not against renders, as they can help visualise what a feature might look like. However, we are against renders being passed off as the real thing. As for the iPhone 6, we're going to have to wait a bit longer to find out what it will really look like.