change framework assets with alternate home screen

by Andy Droid » Thu, 10 Sep 2009 06:57:09 GMT


Sponsored Links
 Could an alternate home screen app replace the assets such as s
"menu_item_background_pressed.9.png" or
"list_selector_background_focus.9.png", both found in  frameworks/base/
core/res/res/drawable in the open source project?  I have altered
those by changing out the assets and recompiling.

But can I make it so the installation of the home screen will open up
framework-res.apk, replace the asset, then re-package framework-
res.apk?  I realize this would then have broad ramifications, but just
wondering if it could be done.  thanks.

Also wondering if a alt home screen app, can replace icons of core
apps, such as Contacts, etc. thanks


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



Other Threads

1. NewBie asking

Hai all,

straight to thepoint... i already bought android dev phone and right
now i'm in indonesia using XL as Operator...for the beginning...call,
received sms, and also using data access 3G, i can..but i can't send
sms...do you know why that happen? right now i can't send sms using my
number .....but the strange is i can received sms....is there any
suggestion how i'm supposed to do? thanks for the help and support.

cheers,

Ryandi

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

2. G1 vs. Fedora Core (6+) vs. udev

Hi all,

I've finally figured out what was going wrong with the udev stuff on
Fedora Core 6
setting up the USB device for adb. The advice for Ubuntu may be correct, but it
doesn't work out of the box with Fedora Core 6 and probably higher. The reason
is because Fedora Core 6 has a rule in /etc/udev/rules.d/50-udev.rules
for all new
USB devices which sets modes, etc. The advice for Ubuntu is to make a
file called
50-android.rules and place it in the rules directory. Note that just
like init(1), udev
scans the rules directory in sorted order which means that 50-android
is executed
*before* 50-udev.

The net effect here is that 50-udev sets the permissions on the new device back
to 0644 which is to say, no write permission for userland adb and the subsequent
non-love (running adb's server as root ought to work). Here's the simple fix:

1) create a file to 51-android.rules in rules.d
2) put this incantation in it:

SUBSYSTEM=="usb_device",SYSFS{idVendor}=="0bb4",SYMLINK+="android_adb",MODE="0666"

3) as root after you've created the file, kick udev with: udevcontrol
reload_rules
4) plug in the device and enjoy!

It would be *really* nice if this or something like it found its way
back into the
documentation ::wink wink:: In fact, the advice for Ubuntu Dapper is the
exact same rule as Fedora, so most likely just changing the docs to create
51-android will work for both Fedora and Ubuntu Dapper.

Mike

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

3. support for encryption

4. New Screens (one per class)

5. ClassNotFoundException in Eclipse Layout tab when custom view references another project

6. Market paid-for apps

7. Pass state from Activity to Service