Minggu, 04 Oktober 2015
Asus A455LN-WX016D Laptop Gaming Murah Dengan GeForce GT840M 2GB
Sabtu, 03 Oktober 2015
Asus ROG GX500 Harga dan Spesifikasi Laptop Layar 4K Yang Seksi
Jumat, 02 Oktober 2015
Daftar Laptop Asus Harga 7 Jutaan Terbaru 2016
Daftar Laptop Harga 7 Jutaan
Tipe Laptop
|
Harga Laptop Asus
|
Asus A451LN-WX028D |
Rp 7,000,000
|
Asus Eee PC 1002HA |
Rp 7,075,000
|
Asus A455LD-WX184D |
Rp 7,099,000
|
Asus A455LN-WX004D |
Rp 7,120,000
|
Asus A46CM-WX091D |
Rp 7,150,000
|
Asus P450LDV-W0209D |
Rp 7,179,000
|
Asus A450LB-WX077D |
Rp 7,199,000
|
Asus A441LB-WX077D |
Rp 7,249,000
|
Asus A555LN-XX196D |
Rp 7,299,000
|
Asus X450LC-WX037H |
Rp 7,312,000
|
Asus X301A-RX015R |
Rp 7,356,600
|
Asus X550ZE-XX065D |
Rp 7,389,000
|
Asus A555LN-XX395D |
Rp 7,399,000
|
Asus U36SD-RX221D |
Rp 7,400,000
|
Asus Pro PU301LA-RO117D |
Rp 7,599,000
|
Asus U38N-C4010H |
Rp 7,659,000
|
Asus VivoBook S451LN-CA012H |
Rp 7,699,000
|
Asus U47VC-WO028V | Rp 7,920,000 |
Asus PU451LD-WO062G | Rp 7,990,000 |
Kamis, 01 Oktober 2015
How Google Cloud Messaging handles Doze in Android 6.0 Marshmallow
Android 6.0 Marshmallow introduces a new power saving feature called ‘Doze’. A device enters Doze when the user leaves it unplugged and stationary for a period of time and with the screen off. When this happens, the system defers application activity to save power. It will periodically and briefly resume normal operations, called an idle maintenance window, in order to perform app syncing and other pending operations.
If your app uses Google Cloud Messaging (GCM), you will need to take into account the following behaviors for users whose devices are in Doze.
GCM has two priority types for messages, called high priority and normal priority. When using high priority, GCM attempts to deliver messages immediately, waking a device in Doze, as needed. With Android Marshmallow, nothing changes here.
However, when using normal priority (the default priority), there are a number of different behaviors when the device is in Doze, including:
- The most important change is that messages will be batched for devices in Doze. When the device enters its idle maintenance window, the batch of messages will be received.
- We discard messages whose time_to_live expires while the device is in Doze (including TTL=0).
Despite this, it is recommended that, unless absolutely necessary, you keep your notifications as normal priority ones, as this will minimize battery impact. They will still sync during doze mode as described above, and of course once the device exits Doze.
High priority messages should only be used by applications that need to generate an immediate notification to the end user such as a chat app notification or an incoming phone call.
To learn more about Google Cloud Messaging message priorities, visit the Google Developers site.
Harga ASUS X553MA-XX826D dan Spesifikasi Lengkapnya
Rabu, 30 September 2015
Android Studio 1.4
Posted by, Jamal Eason, Product Manager, Android
Today we are releasing the 1.4 update to the Android Studio stable release channel. Most of the work and enhancements for Android Studio 1.4 are under the hood. However we have a handful of new features that we hope you enjoy and integrate into your workflow.
Note that some of new features (e.g. vector assets) require you to use Gradle Plugin 1.4 for your app project. The beta version of the Gradle plugin (1.4.0-beta3 ) is available today on jcenter with the final version coming in the next few weeks.
New Features in Android Studio 1.4
Design Tools
Vector AssetsStarting with API 21, you can use Vector Drawables for image assets. For most apps, using VectorDrawables decreases the amount of density dependent drawables you need to maintain, and will also give you sharp image assets regardless of the screen device densities your app supports.
With Android Studio 1.4, we are making the process of importing SVG images or Material icons much easier. If you update your Gradle Android plugin to 1.4.0-beta3 (or higher) in the project structure dialogue or your project
build.gradle
file ( 'com.android.tools.build:gradle:1.4.0-beta3'
), you can now use the new Vector Asset Studio by right-clicking the res/drawable folder in your project and selecting New → Vector Asset from the content menu.
We are also excited to offer backwards compatibility for your vector assets in Android Studio 1.4. Once you have a vectorDrawable image in your res/drawable, the Gradle plugin will automatically generate raster PNG images for API level 20 and below during build time. This means you only need to update and maintain your vector asset for your app project and Android Studio can take care of image conversion process. Note, it is still best practice to create density dependent launcher icons in your res/mipmap folder. Learn more by watching the DevByte video on the new Vector Asset Studio tool.
Theme EditorWe understand that managing your app theme and style can be a bit complex. With Android Studio 1.4, we are releasing a preview of the Theme Editor to help with this task. This first version of the Theme Editor is focused on editing and updating the material theme colors (
colors.xml
) in your app project. In future releases, we will cover more attributes of your app theme and styles files. To access the editor, navigate from top level menu Tools → Android → Theme Editor.
Project TemplatesWe know many of you use the New Project Wizard app templates to start a new app project or to quickly add an activity to an existing app. To help with the visual design of your apps, we updated the app templates to include the Android Design Support Library alongside the AppCompat Support library.
From the template wizard you can start projects with a basic blank template with a floating action button or start from a range of user interface components such as the navigation drawer, or AppBar with scrolling view. We also re-introduced the empty app template for those who want minimum code generation when adding an activity to your project.
With Android Studio 1.4, you can also validate your apps on the new Nexus 5X and Nexus 6P screen sizes.
Performance Monitors
GPU Rendering MonitorNow it is possible to quickly inspect the GPU rendering performance of your app. To enable GPU monitoring, make sure you turn on monitoring for your Android hardware device or emulator under Setting → Developer Options → Profile GPU rendering → In adb shell dumpsys gfxinfo . To learn more about the GPU rendering results, check out the developer documentation.
Network MonitorWith Android Studio 1.4, you can also monitor the network usage of your app. With the monitor you can track the transmit and receive rates of your app over time.
Developer Services
FirebaseIt is now even easier to add a Firebase mobile backend to your Android app. Firebase includes data storage, user authentication, static hosting, and more. To access the feature, navigate from the top level menu and select File → Project Structure → Cloud. Learn more about Firebase in this tutorial.
Whats Next
For current developers on Android Studio, you can check for updates from the navigation menu (Help → Check for Update [Windows/Linux] , Android Studio → Check for Updates [OS X]) . For new users, you can learn more about Android Studio on the product overview page or download the stable version from the Android Studio download site.
We welcome feedback on how we can help you. Connect with the Android developer tools team on Google+.
Selasa, 29 September 2015
Android 6.0 Marshmallow coming to devices soon
Posted by, Dave Burke, VP of Engineering, Android
Starting next week, Android 6.0 Marshmallow will begin rolling out to supported Nexus devices around the world, including Nexus 5, Nexus 6, Nexus 7 (2013), Nexus 9, Nexus Player, and Android One. At the same time, we’ll be pushing the Android 6.0 source to the Android Open Source Project (AOSP), which marks the official beginning of public availability.
Today we also introduced two great new Nexus devices that will be among the first to run the Android 6.0 Marshmallow platform. These devices let your apps use the latest platform features and take advantage of the latest hardware optimizations from our partners. Let’s take a look at how to make sure your apps look great on these new devices.
Introducing Nexus 5X and Nexus 6P
Nexus 5X | Nexus 6P |
The Nexus 5X is built in partnership with LG. It’s equipped with a 5.2-inch FHD LCD 1080p display, a Snapdragon™ 808 processor (1.8 GHz hexa-core, 64-bit), and a 12.3 MP rear camera. Offering top-line performance in a compact, lightweight device.
The Nexus 6P, built in partnership with Huawei, has a 5.7-inch WQHD AMOLED display, Snapdragon™ 810 v2.1 processor (2.0 GHz octa-core 64-bit), front-facing stereo speakers, and a 12.3 MP rear camera, all housed in a diamond-cut aluminum body.
Both devices have USB Type-C ports and fingerprint sensors, and include the latest hardware features for Android, such as: Android Sensor Hub, low-power Wi-Fi scanning with channel selection, batching, and BSSID hotlists, Bluetooth 4.2 with ultra low-power BLE notifications, and more.
Get your apps ready
Take some time to make sure your apps and games are ready to give your users the best mobile experience on these devices.
Check your assets
Resolution | Screen size | Density | |
---|---|---|---|
Nexus 5X | 1920 x 1080 px (730 x 410 dp) | normal | 420 dpi |
Nexus 6P | 2560 x 1440 px (730 x 410 dp) | normal | 560 dpi |
Nexus 5X has a quantized density of 420 dpi, which falls in between the xhdpi
and xxhdpi
primary density buckets. Nexus 6P has a density of 560 dpi, which falls in between the xxhdpi
and xxxhdpi
buckets. The platform will scale down any assets from a higher resolution bucket, but if those aren’t available, then it will scale up the assets from a lower-density bucket.
For best appearance in the launcher, we recommend that you provide at least an xxxhdpi
app icon because devices can display large app icons on the launcher.
For the rest of your assets, you can consider using vector assets or optionally add versions for the next-higher density bucket. This provides a sharper visual experience, but does increase apk size, so you should make an appropriate decision for your app.
Make sure you are not filtered on Google Play
If you are using the <compatible-screens>: element in your AndroidManifest.xml file, you should stop using it because it’s not scalable to re-compile and publish your app each time new devices come out. If you must use it, make sure to update your manifest to add a new configuration for Nexus 5X, since it uses a new density bucket (420). Otherwise, your app may be filtered from Google Play on these devices.
Wrapping up M Developer Preview
After three preview releases, and with the final OTA coming soon, it’s time to wrap up the Android M Developer Preview. The feedback you’ve provided has helped make Android 6.0 a great platform for apps and games. Developers in more than 200 countries have been using the Developer Preview to get their apps ready for Android 6.0 Marshmallow users everywhere.
More developer resources
If you haven’t taken a look at Android 6.0 Marshmallow yet, visit developer.android.com/mm for complete information about about what’s new for developers and important changes to plan for in your apps — runtime permissions, Doze and App Standby idle modes, Auto Backup for Apps, fingerprint support, and others.
We’ve also produced a playlist of developer videos to help you get the most out of all the new features in Android 6.0 Marshmallow. Check it out below.
Final testing and updates
Now is the time to finish up testing and prepare for publishing. You can use the Developer Preview 3 system images for final testing until early October. After the Android 6.0 public release, you’ll be able to download final images from the Nexus factory images page, and final emulator images from Android Studio.
Reminder: Devices flashed with an M Developer Preview build won’t receive the Android 6.0 update automatically. You’ll need to manually flash those devices to a public released image first.
Upload your apps to Google Play
When your apps are ready, you can update them to Google Play via the Developer Console on all release channels (Alpha, Beta & Production). For apps that target API level 23, Google Play will provide the new optimized download and autoupdate flow based on the runtime permissions model in Android 6.0. Give it a try!
To make sure that your updated app runs well on Android 6.0 Marshmallow and older versions, we recommend that you use the newly improved beta testing feature on Google Play to get early feedback. You can then do a staged rollout as you release the new version to all users.
What’s next?
In mid-October, we’ll be turning down the M Developer Preview community and the M Developer Preview issue tracker. If you've filed bugs against the preview, and you'd like to keep these open against the Android 6.0 final builds, you can file a new issue in the AOSP issue tracker.
Thanks to everyone who participated in the Android M Developer Preview. Let us know how this year’s preview met your needs by taking a short survey. Your feedback helps shape our future releases.
Senin, 28 September 2015
Daftar Laptop Asus Harga 6 Jutaan Terbaru 2016
Daftar Laptop Asus Harga 6 Jutaan
Laptop Asus Harga 6 Jutaan |
Tipe Laptop
|
Harga Laptop Asus
|
Asus H100TAM-DK022P |
Rp 6,019,000
|
Asus P450LDV-WO317D |
Rp 6,049,000
|
Asus EeeTop 2013IUKI-B071M |
Rp 6,099,000
|
Asus Transformer Book TP300LD-DW102D |
Rp 6,199,000
|
Asus VivoBook S300CA-C1040H |
Rp 6,237,000
|
Asus Transformer Book TP300LD-DW102H |
Rp 6,273,400
|
Asus A450LD-WX036D |
Rp 6,299,000
|
Asus X550ZE-XX033D |
Rp 6,330,000
|
Asus Pro PU301LA-RO116D |
Rp 6,399,000
|
Asus A46CB-WX024D |
Rp 6,543,000
|
Asus ZENBOOK UX32A-R3024H |
Rp 6,578,000
|
Asus Transformer Book TP300LD-DW010D |
Rp 6,599,000
|
Asus Eee PC VX6S-BLK040M Lamborghini |
Rp 6,600,000
|
Asus A455LB-WX001D |
Rp 6,699,000
|
Asus X450LD-WX025D |
Rp 6,699,000
|
Asus A43SD-VX748D |
Rp 6,700,000
|
Asus X551CA-HCL1201L |
Rp 6,803,600
|
Asus A451LB-WX077D | Rp 6,899,000 |
Asus VivoBook S300CA-C1041H | Rp 6,908,000 |
Asus S46CB-WX004H | Rp 6,787,000 |
Support for 100MB APKs on Google Play
Smartphones are powerful devices that can support diverse tasks from graphically intensive games to helping people get work done from anywhere. We understand that developers are challenged with delivering a delightful user experience that maximizes the hardware of the device, while also ensuring that their users can download, install, and open the app as quickly as possible. It’s a tough balance to strike, especially when you’re targeting diverse global audiences.
To support the growing number of developers who are building richer apps and games on Google Play, we are increasing the APK file size limit to 100MB from 50MB. This means developers can publish APKs up to 100MB in size, and users will see a warning only when the app exceeds the 100MB quota and makes use of Expansion Files. The default update setting for users will continue to be to auto-updating apps over Wi-Fi only, enabling users to access higher quality apps and games while conserving their data usage.
Even though you can make your app bigger, it doesn’t always mean you should. Remember to keep in mind the following factors:
- Mobile data connectivity: Users around the world have varying mobile data connectivity speeds. Particularly in developing countries, many people are coming online with connections slower than those of users in countries like the U.S. and Japan. Users on a slow connection are less likely to install an app or game that is going to take a long time to download.
- Mobile data caps: Many mobile networks around the world give users a limited number of MB that they can download each month without incurring additional charges. Users are often wary of downloading large files for fear of exceeding their limits.
- App performance: Mobile devices have limited RAM and storage space. The larger your app or game, the slower it may run, particularly on older devices.
- Install time: People want to start using your app or game as quickly as possible after tapping the install button. Longer wait times increase the risk they’ll give up.
We hope that, in certain circumstances, this file size increase is useful and enables you to build higher quality apps and games that users love.
Kamis, 24 September 2015
Android Development Patterns: A Series on Best Practices for Android Development
One of the benefits of Android development is the flexibility provided by the large number of APIs in the Android framework and Support Library, not even including the Google Play services APIs. However, that can be a lot to understand, particularly when confronted with multiple options or design decisions. Thankfully, things are about to get a lot clearer with a new series: Android Development Patterns.
The goal of Android Development Patterns is to focus on the fundamental components and best practices that can make the biggest difference in your app. We spend time talking about the why behind each API, so that you know exactly what is best for your situation.
Centered on Android framework APIs, the Android Support Library, and high level app structure and design, we’ll augment the many videos on the Android Developers YouTube channel to bring the focus back towards Android development at its core.
Android Development Patterns are more than just videos. You’ll find written pro-tips from in-house experts at Google, such as Joanna Smith and Ian Lake, every week through the Android Development Patterns Google+ Collection.
Watch all of Android Development Patterns!