Info Android Phone | The Android | What is Android | Androids | Android Market | App

CyanogenMOD 7.2.0 RC5.3 for galaxy mini

The Android | What is Android | Androids | Android Market | App for Android | Android Apps | Android Application | Download Android | Tablet Android | Tablet PC | Phone Android | Android 2.2 | Android 2.3 | Android Free | Games for Android | Android Samsung | Galaxy Android | Android Google | Games Android | アンドロイド | Android | Android 2 | Android PC | Google Android | Android Galaxy | Phones with Android | Which Android Phone | What is an Android Tablet | What is an Android Phone

baru aja mau posting cm7 rc5.2 udah muncul lagi cm7 rc5.3,y udh langsung aja deh saya share,tp custom rom ini blm smpet saya test karena blm smpet saya download. tapi klo mau coba silahkan aja,hehe

Download bahan2nya dimari :

1.Cyanogenmod 7.2.0 rc5.3

2.Update System for CyanogenMOD 7.2.0 RC5.3 ( MUST DOWNLOAD )

3.Update Tun and Cifs module for CyanogenMOD 7.2.0 RC5.3 ( OPTIONAL )

NEW !!!

4.Gapps for this custom rom. tinggal install lewat recovery aja setelah semua file di atas udah selesai di install di mininya kk

ini changelognya saya copas langsung dari threadnya mastah yanuar harry aka squadzone di xda :

added max length value SMS changeable into MMS ( configure this from MMS settings )
Fix FM radio for audio routing and seek support
added option to lock dock button into ADWLauncher ( enable this via ADW settings )
Fix rotation on Gallery3D, no more banding image, and better scan all image from sdcard ( if this still happen, just run dev tools app, and click media scan, wait until finish, and done )
use media service for MUSIC, for better scan all music from sdcard ( if this still happen, just run dev tools app, and click media scan, wait until finish, and done )
Rebased with cyanogenmod again and Rewriting all app to decrease whitespace on java
Fix user interface touch configuration, due to error appear from logcat while touching
Fix keyboard theme problem that came from 3rd party app
Fix system permission
Fix scroll cache option due to problem ( not apply ) when click force disable scroll cache
Fix camera colour capture image and video when using high or low setting, and force enable samsung service camera
Fix screenshot colour image ( no more blur ) when trying capture SS after animation stop
FIX DSP manager configuration, due to problem FC when apply some config
Improve lockscreen animation, due to some lag when scroll cache is force disable
Rewriting binary file, due to problem when execute with busybox or toolbox
Improve sensor service orientation, due to problem with ICS rotation animation
Rewriting and Recompile libaudio using CM-audio implementation ( Kanged from and Thanks to Psyke83 )
Improve HTML proccessing, to improve browser when trying to open full website not mobile website
Force enable static a2dp while using bluetooth headset or handsfree ( i hope, but my bluetooth headset is broken now, and i cant test, so please test this )
Readd Setup_fs for optimizing data and cache partition, ( i forgot to add this before )
Framework optimizing to decrease some error when booting, after apply from HDPI theme ( looks better now, but still need to find HDPI theme that compatible with our device )
Patch GLES android to not use software rendering, use Full gpu hardware rendering due to problem with some HD GAME ( i hope )

cara install :
-base : 2.3.4 (disarankan pake xxkpk,tapi kalo pake xxkpi atau yg lain silahkan aja,hehe)

-harus udah install clockworkmod recovery,caranya ada di postingan custom rom andro-id v3.2

-Pindahkan semua bahan yang sudah di sediakan di atas ke sdcard si mini

-install file no.1 lewat recovery,jangan lupa sebelumnya wipe data n cache dlu

-kalo udah selesai pilih reboot system now

-nah klo udah selesai install cm7 rc 5 nya masuk recovery lagi,lalu install file no.2 lalu file no.3 (tidak perlu wipe data n cache utk install file no.2 dan 3. klo ke 2 nya udah di install reboot system now lagi.

NOTE : Silahkan DWYOR,saya blm nyobain custom rom ini. nanti klo udah saya test langsung saya kasih screenshootnya

Sistem Reproduksi Manusia pada Pria

Android Developers on Google+

[This post is by Reto Meier, Android Developer Relations Tech Lead. — Tim Bray]

I’ve been fortunate enough to be involved with Android since the 0.9 preview SDK was released to developers back in 2007. A lot has changed since then, but one thing that hasn’t is the rapid pace at which new tools, resources, and information have become available for us Android developers. Just look at the last few months.

In December Android Training launched, with its first set of classes designed to demonstrate the best practices behind building great Android Apps.

Earlier this month, the Android design site went live — offering a place to learn about the principles, building blocks, and patterns you need to make good design decisions when creating your Android app interfaces.

We’ve got a lot more planned in the coming year, so to help you keep abreast of all the latest Android developer news we’re launching the +Android Developers page on Google+!

One of my favourite things about Google+ is the quality of conversation around posts, so +Android Developers will focus on being a place for the people behind the Android developer experience, and Android developers all around the world, to meet and discuss the latest in Android app development.

We’ll be posting development tips, discussing updates to the SDK and developer tools, highlighting new Android training classes, and posting video and pics from Android developer events around the world.

We’ll also be using Google+ Hangouts to help us all interact even more closely. Starting with weekly broadcast office-hours on Hangouts On Air to answer Android development questions. These will happen every Wednesday at 2pm Pacific Time (10pm UTS) in Mountain View—expect to see these hangouts in more time zones as our teams in London, Sydney, and Tokyo get involved. Each hangout will be recorded for YouTube, so if you can’t join us live you won’t miss out.

It turns out that hangouts are a lot of fun, so we’ll be doing more of these that feature interviews with Google engineers and 3rd party Android app developers willing to share their tips and experiences.

We’re looking forward to interacting with you even more closely, so add us to your circles, join the conversation by commenting on posts, and join the hangouts. We can't wait to hear what you have to say.

Cara Membuat dan Mendapatkan Cover Terbaik untuk TimeLine FB Anda

Untuk BeckGround anda harus menyediakan Foto minimal brukuran 851 berbanding 314
biar bisa menyesuekan posisi
...
Kunjungi link dibawah

facebook timeline banner background

Contoh Foto Dari FB saya

Game Perang Terbaik di Dunia

Ngegombal yux

MyTrans Digital Entertainment TV

CyanogenMOD 7.2.0 RC5.0.1 for galaxy mini

ini ada editan baru dari mastah yanuar untuk cm7. cm7 rc 5.0.1 ini menurut saya sudah sangat bagus dan lengkap. sudah banyak bug yg di fix di cm7 ini. beberapa review dari saya :

-file manager di hilangkan dan di ganti dengan total comander
-sudah ada dsp manager dr bawaan custom rom ini
-otomatis terinstall kernel 864mhz, jadi gk perlu capek2 install kernel lagi.hehe(di beberapa
-ada tombol backnya di bagian pojok kiri bawah di deretan statusbar.dll

Download bahan2nya dimari :

-CyanogenMOD 7.2.0 RC5.0.1

-update some APPS and module for CyanogenMOD 7.2.0 RC5.0.1

-Second update some APPS to fix incoming call style for CyanogenMOD 7.2.0 RC5.0.1

-Blackwhitemiui.apk

daripada penasaran mendingan langsung liat aja nih penampakanya. cekidot

note : screnshoot yang saya ambil akan berbeda dari bawaanya karena saya sudah menggunakan tema miui melalui theme chooser

Image Hosted by ImageShack.us

cara install :
-base : 2.3.4 (kalo saya pake xxkpk),seterah situ mau pake kpi atau kpk pkoknya saya testnya di kpk jadi jangan tanya lg bisa atau gk klo di kpi atau base yg lain

-harus udah install clockworkmod recovery,caranya ada di postingan custom rom andro-id v3.2

-Pindahkan semua bahan yang sudah di sediakan di atas ke sdcard si mini

-install file CyanogenMOD 7.2.0 RC5.0.1.zip lewat recovery,jangan lupa sebelumnya wipe data n cache dlu

-kalo udah selesai pilih reboot system now

-nah klo udah selesai install cm7 rc 5 nya masuk recovery lagi,lalu install ke dua update an app nya. untuk urutanya install yang updatean pertama baru yang ke dua atau sebaliknya kayanya gk masalah,hehe. gk usah wipe data n cache klo cuma mau install update an appnya. klo ke 2 nya udah di install reboot system now lagi.

*tambahan untuk mempercantik tampilan

-nah klo ke 3 file di atas udah di install lwt recovery sekarang tinggal install blackwhitemiui.apk nya lwt total comander ataupun file manager lainya.lalu masuk theme chooser dan pilih blackwhitemiui.apk

note :

-klo ada masalah silahkan wipe data n cache baru install ulang cr nya.

SUMBER

THX To : Mastah Yanuar dan agan amri untuk tema miui nya :-)

Say Goodbye to the Menu Button

[This post is by Scott Main, lead tech writer for developer.android.com. — Tim Bray]

Before Android 3.0 (Honeycomb), all Android-powered devices included a dedicated Menu button. As a developer, you could use the Menu button to display whatever options were relevant to the user, often using the activity’s built-in options menu. Honeycomb removed the reliance on physical buttons, and introduced the ActionBar class as the standard solution to make actions from the user options immediately visible and quick to invoke. In order to provide the most intuitive and consistent user experience in your apps, you should migrate your designs away from using the Menu button and toward using the action bar. This isn’t a new concept — the action bar pattern has been around on Android even before Honeycomb. As Ice Cream Sandwich rolls out to more devices, it’s important that you begin to migrate your designs to the action bar in order to promote a consistent Android user experience.

You might worry that it’s too much work to begin using the action bar, because you need to support versions of Android older than Honeycomb. However, it’s quite simple for most apps because you can continue to support the Menu button on pre-Honeycomb devices, but also provide the action bar on newer devices with only a few lines of code changes.

If I had to put this whole post into one sentence, it’d be: Set targetSdkVersion to 14 and, if you use the options menu, surface a few actions in the action bar with showAsAction="ifRoom".

Don’t call it a menu

Not only should your apps stop relying on the hardware Menu button, but you should stop thinking about your activities using a “menu button” at all. Your activities should provide buttons for important user actions directly in the action bar (or elsewhere on screen). Those that can’t fit in the action bar end up in the action overflow.

In the screenshot here, you can see an action button for Search and the action overflow on the right side of the action bar.

Even if your app is built to support versions of Android older than 3.0 (in which apps traditionally use the options menu panel to display user options/actions), when it runs on Android 3.0 and beyond, there’s no Menu button. The button that appears in the system/navigation bar represents the action overflow for legacy apps, which reveals actions and user options that have “overflowed off the screen.”

This might seem like splitting hairs over terminology, but the name action overflow promotes a different way of thinking. Instead of thinking about a menu that serves as a catch-all for various user options, you should think more about which user options you want to display on the screen as actions. Those that don't need to be on the screen can overflow off the screen. Users can reveal the overflow and other options by touching an overflow button that appears alongside the on-screen action buttons.

Action overflow button for legacy apps

If you’ve already developed an app to support Android 2.3 and lower, then you might have noticed that when it runs on a device without a hardware Menu button (such as a Honeycomb tablet or Galaxy Nexus), the system adds the action overflow button beside the system navigation.

This is a compatibility behavior for legacy apps designed to ensure that apps built to expect a Menu button remain functional. However, this button doesn’t provide an ideal user experience. In fact, in apps that don’t use an options menu anyway, this action overflow button does nothing and creates user confusion. So you should update your legacy apps to remove the action overflow from the navigation bar when running on Android 3.0+ and begin using the action bar if necessary. You can do so all while remaining backward compatible with the devices your apps currently support.

If your app runs on a device without a dedicated Menu button, the system decides whether to add the action overflow to the navigation bar based on which API levels you declare to support in the <uses-sdk> manifest element. The logic boils down to:

If you set either minSdkVersion or targetSdkVersion to 11 or higher, the system will not add the legacy overflow button.

Otherwise, the system will add the legacy overflow button when running on Android 3.0 or higher.

The only exception is that if you set minSdkVersion to 10 or lower, set targetSdkVersion to 11, 12, or 13, and you do not use ActionBar, the system will add the legacy overflow button when running your app on a handset with Android 4.0 or higher.

That exception might be a bit confusing, but it’s based on the belief that if you designed your app to support pre-Honeycomb handsets and Honeycomb tablets, it probably expects handset devices to include a Menu button (but it supports tablets that don’t have one).

So, to ensure that the overflow action button never appears beside the system navigation, you should set the targetSdkVersion to 14. (You can leave minSdkVersion at something much lower to continue supporting older devices.)

Migrating to the action bar

If you have activities that use the options menu (they implement onCreateOptionsMenu()), then once the legacy overflow button disappears from the system/navigation bar (because you’ve set targetSdkVersion to 14), you need to provide an alternative means for the user to access the activity’s actions and other options. Fortunately, the system provides such a means by default: the action bar.

Add showAsAction="ifRoom" to the <item> elements representing the activity’s most important actions to show them in the action bar when space is available. For help deciding how to prioritize which actions should appear in the action bar, see Android Design’s Action Bar guide.

To further provide a consistent user experience in the action bar, we suggest that you use action icons designed by the Android UX Team where appropriate. The available icons support common user actions such as Refresh, Delete, Attach, Star, Share and more, and are designed for the light and dark Holo themes; they’re available on the Android Design downloads page.

If these icons don’t accommodate your needs and you need to create your own, you should follow the Iconography design guide.

Removing the action bar

If you don’t need the action bar, you can remove it from your entire app or from individual activities. This is appropriate for apps that never used the options menu or for apps in which the action bar doesn’t meet design needs (such as games). You can remove the action bar using a theme such as Theme.Holo.NoActionBar or Theme.DeviceDefault.NoActionBar.

In order to use such a theme and remain backward compatible, you can use Android’s resource system to define different themes for different platform versions, as described by Adam Powell’s post, Holo Everywhere. All you need is your own theme, which you define to inherit different platform themes depending on the current platform version.

For example, here’s how you can declare a custom theme for your application:

<application android:theme="@style/NoActionBar">

Or you can instead declare the theme for individual <activity> elements.

For pre-Honeycomb devices, include the following theme in res/values/themes.xml that inherits the standard platform theme:

<resources>
    <style name="NoActionBar" parent="@android:style/Theme">
        <!-- Inherits the default theme for pre-HC (no action bar) -->
    </style>
</resources>

For Honeycomb and beyond, include the following theme in res/values-v11/themes.xml that inherits a NoActionBar theme:

<resources>
    <style name="NoActionBar" parent="@android:style/Theme.Holo.NoActionBar">
        <!-- Inherits the Holo theme with no action bar; no other styles needed. -->
    </style>
</resources>

At runtime, the system applies the appropriate version of the NoActionBar theme based on the system’s API version.

Summary

Android no longer requires a dedicated Menu button, some devices don’t have one, and you should migrate away from using it.

Set targetSdkVersion to 14, then test your app on Android 4.0.

Add showAsAction="ifRoom" to menu items you’d like to surface in the action bar.

If the ActionBar doesn’t work for your app, you can remove it with Theme.Holo.NoActionBar or Theme.DeviceDefault.NoActionBar.

For information about how you should design your action bar, see Android Design’s Action Bar guide. More information about implementing the action bar is also available in the Action Bar developer guide.