How to custom my own home screen?

by water » Fri, 13 Feb 2009 02:06:24 GMT


Sponsored Links
 Android phone has a default home screen,a clock in the middle,and four
icons in the bottom,
i want to change this layout,
May i develop a application,after i installed it,it replace the
default home screen?
Thanks~!

--~--~---------~--~----~------------~-------~--~----~



How to custom my own home screen?

by Scynasty » Fri, 13 Feb 2009 04:23:25 GMT


 add    <category android:name="android.intent.category.HOME" />  in
the intent-filter of the activity you want as the home screen. when
the home button is clicked it will ask which home screen you want to
run.



--~--~---------~--~----~------------~-------~--~----~


Sponsored Links


Other Threads

1. About Dynamic Voltage and Frequency Scaling In ADP2

Thank you for your suggestions. It's really very very helpfull. But the
current problem I am facing is how to customize the kernel for my phone. I
need to configure the CPU frequency of Android phone. However, the current
kernel doesn't support "userspace" governor. So I need to rebuild the kernel
and turn on the "userspace" or make it built as a module. At first I
followed the instruction  here "
http://source.android.com/documentation/building-for-dream" to build kernel
for Sapphire(my phone is ADP2). But I didn't find any approach like "make
menuconfig" to customize the kernel as I need. Then  I download the HTC
magic kernel ource code from the HTC developer website
http://developer.htc.com/ and try to rebuild that. But maybe, I need cross
compiler or something else. I am still trying. I'm really confused about the
various kinds of kernel source code and rebuild approaches from android
website or HTC or other website. Actually, I just need one that can work. Do
you have any suggestions about how to customize the kernel(Sapphire) for
ADP2? Thank you very much!
















> > >> >> > website:

2. Android 1.5 on CDMA phones and OEM non-conformance documentation...



Or you can target API level 4 and either support both CDMA/GSM or have
the appropriate <uses-feature> element to stipulate that you only
support GSM. This eliminates the problem entirely, with the side effect
of dropping support for those devices presently on Android 1.5.


FCC conformance is public but has nothing to do with Android API levels.


I'm not sure it's a "sign off on" so much as Google tests the devices
and withholds Android Market support if, in Google's estimation, the
device will inadequately support third-party applications. Certainly, we
have at least one documented report of that structure (the QVGA 1.5
device from last summer), and I have not seen a "sign off on" approach
described by the core Android team.

If you have evidence of such a "sign off" model in use, please point me
to it -- thanks!

-- 
Mark Murphy (a Commons Guy)
http://commonsware.com | http://twitter.com/commonsguy

Android App Developer Books: http://commonsware.com/books

-- 

3. problem in switching two activities

4. Align ImageView to the right

5. Could not get audio input for record source

6. Sound Processing

7. sizes of alternative markets?