{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Google's operating system, unlike implemented in other platforms, is strongly oriented to the user, making it easy to perform tasks in other systems are complicated or completely impossible.
Such is the case of modification of applications developed by other users, for which there are tools that allow both the treated and recompiling, but of course, to modify the resulting code must have some computer knowledge.
However, any user can change the visual appearance of your applications without having prior knowledge and without being root, resulting, in general, extremely simple to modify the background of your widgets, for example.
To do this you simply need to know how Google organizes the information in an application.
Android applications are recognized for having the extent apk, English Package System Android. Apk files (like jar files, java standard derived) contain all the information on the application, ie the same code, resources used, the list of permissions required to run, and digital signature associated with it, which prevents a change, and is checked every time we make an update.
Although initially it may seem complicated, it really is not, as a apk file is organized internally as a zip container, so that stored data can be obtained with almost all the pressure reducers on the market, although it is recommended WinRar program use, which makes the whole process.
The images and descriptions of the various screens of Android are in res directory, which is structured as follows:
Subdirectories layout and layout-*: The files are of type xml, although they are compiled, so are not directly modifiable and need to decompile the application to change them. These files contain the description of the elements of the different screens of the application,
Xml subdirectory: this subdirectory files are also compiled xml type, and include information on the configuration screens of the application,
Drawable drawable-subdirectories and *: Depending on the programmer, you'll find both compiled xml files as images (usually png files 9.png type).
The png files are files 9.png extensible, and find more information here, while the png files are a type of images you can edit with any editor.
Image
Once all the changes, you only have to insert the apk files modified in the application, for which, if you use WinRar, keep in mind that graphics files should be inserted disabling compression, while for the rest file must indicate the type of normal compression.
To finish, you need to download a utility to sign the new application you can install once signed, but first uninstall the original application.
Related
You can use Active Sync as a kind of registry monitor.
Dont know what it monitors exactly. Perhaps someone can tell.
This is what you do.
On you PC create 2 values:
[HKCU\Software\Microsoft\Windows CE Services]
"RapiLogPath"="C:\TEMP"
"RapiVerbose"=dword:00000001 or 0 or 2
This creates WCESMgr.exe_XXXX.Log files in that directory
when connected through active sync.
Example of the output:
WCESMgr.exe,CeRapiInit[Ex],8413147,0,0,Start,
WCESMgr.exe,,8413147,0,0,CEAPI,1242324,1346454851,842083401,0x32333234
WCESMgr.exe,CeSyncTimeToPc,8414619,1472,1472,CEAPI,29425124,1346454851,959589449,0x31353234
WCESMgr.exe,CeProcessConfig,8415470,2323,821,CEAPI,25884384,1346454851,892480585,0x33343838
WCESMgr.exe,CeProcessConfig,8415811,2664,321,CEAPI,25884380,1346454851,892480585,0x33343838
WCESMgr.exe,CeProcessConfig,8415921,2774,110,CEAPI,25884476,1346454851,892480585,0x34343838
WCESMgr.exe,CeRegCreateKeyEx,8416071,2924,150,CEAPI,25882160,1346454851,892480585,0x31323838
Click to expand...
Click to collapse
Not very useful at the moment but perhaps someone can make sense of it?
Cheers
For $29, you can pick up TorchSoft Registry Workshop that can not only compare registries on your desktop PC, but also your Windows Mobile device via ActiveSync!
http://www.torchsoft.com/en/rw_information.html
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Multiple undo and redo. The undo history can be saved to disk and reloaded at startup.
Search and replace registry keys, values and data with super fast search algorithm. On a typical PC, you can search the entire registry in about ten seconds!
Compare registry between computers and/or REG files with super fast speed.
Connect mobile device (Pocket PC, SmartPhone, etc.) registry via ActiveSync. new!
Cut, copy and paste registry keys and values.
Drag and drop to move or copy registry keys and values.
Edit REG files in the same way as editing system registry.
Backup and restore registry (Windows NT4/2K/XP/2003 only).
Defragment registry with preview (Windows NT4/2K/XP/2003 only).
Easy and flexible Favorites management.
Quickly browse registry with address bar, bookmarks and visitation history.
Support of linkage aware ability. You can use context menu to navigate to referenced key, open containing folder or open URL if the key or value contains a ProgID, ClassID, folder, file path or URL.
Allow to open multiple local registry windows.
Allow to open secure registry keys when running under the administrator privilege.
Edit binary data in BYTE, WORD or DWORD format.
Support of version 5 REG files with Windows 98/ME/NT4.
tweakradje said:
Not very useful at the moment but perhaps someone can make sense of it?
Click to expand...
Click to collapse
It is just a log of RAPI functions with what looks like call parameters.
For the non programmers among us:
RAPI (Remote Application Programming Interface) is a set of functions ActiveSync provides that let you execute a set of functions (APIs) on the device from your PC.
As a registry monitor this has two major issues:
a) It only sees changes triggered from the PC, but any cab installation does changes internally.
b) Part of the log tweakradje quoted looked to me like a list of argument addresses instead of the parameters them selves, so unless there is another setting for logging, you can't actually see the strings being sent, so you don't know which keys and values were altered.
Still, it is an interesting discovery and someone will probably find a use for it.
Side note: On WM5 devices, phone edition in particular, security was tightened so registry access via RAPI is now blocked (except I think for reading certain keys).
I’ve just been asked in the Smartphone & PPC Mag VIP section (where I’m the lead helper) of how you can easily change your upper / lower / scrollbar colors on WM5+ (WM5, WM6, WM6.1 etc.) Windows Mobile devices with touchscreens (NOT models without them!), also often referred to as the “base hue”.
I’ve published a lot of system color-related information back in the pre-WM5 days (see for example THIS). In WM5, the situation has changed drastically with the introduction of the “base hue”. This means old utilities and Registry hacks no longer work under WM5+. Fortunately, there are a lot of tools to help the situation.
Probably the easiest (and free!) way of doing this is getting VJBaseHue from HERE. To do this, download the CAB file at the bottom and also download “Example themes by ZeBoxx”. Install the former to the built-in storage of your device (NOT to a storage card) so that you don’t need to modify the .lnk files in the latter, ZeBoxx file.
Now, uncompress the contents of the ZeBoxx file and copy the lnk files to anywhere on your Windows Mobile phone; I recommend \Windows\Start Menu\Programs or a subdirectory of them so that you can easily access them from the Start menu. Now, by just going to clicking Start / Programs (or the folder you’ve created) and clicking any of these links, the color of the upper/lower/scroll bars immediately change.
Just some examples:
A QVGA Pocket PC Phone Edition (Windows Mobile Professional in the new, WM6+ parlance) device with black base hue:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Now, clicking the “Magneta” link makes the base hue to magneta as can be seen in the following screenshot:
Note that you can use any color (not just the pre-defined ones in the ZeBoxx file) if you follow the tutorial on the homepage.
So I came across this early on in my research of theme porting, but was still learning and didn't fully understand the process. However, now that I have some experience under my belt I decided to take a look at it and see how it worked.
http://forum.xda-developers.com/showthread.php?t=591329
Basically by use of this app we can apply created .zip packages that contain themed image's for any .apk located in /system/. In short, we can theme individual pieces of our phone to our taste, by applying a specific .zip.
There is a very specific process to doing this, because there are certain requirements to inserting .png files into your phone. The files you have flashed may have changed XML values that point to specific images, if that XML points to 20 images then the .zip you create must contain different versions of those specific 20 images - in order for this to work properly. In other words, the images already have to be called in the code for this to work, so we have to be careful how we build these .zip's so they work right.
Basically what we need to do is just start creating addon packs for our existing theme's, that way we know it will work as long as that theme is installed (it has the XML to support the .png file addon packs)
That means, you get your little tweaks without us having to create entire new theme's or having to bother at all with the long process of making these edits, we just have to find the .png's you want changed and include them in the package.
Watch this video; http://www.youtube.com/watch?v=p9y3ooUZZrg
I've tested this once on just my battery (because the accurate battery xml is universal, it references 100~ images) I used the battery from my recent port A Splash of Color, i pulled the .png files of just the battery icon and transplanted them to the .zip i created (watch the video, it shows you how to do it) Pushed the .zip to the AndroidThemes directory on my phone (that the Metamorph app created) then loaded up the app. In the app, my test.zip showed up and everything worked great - at the end the phone vibrated as if it was force closing but it was just rebooting, when it was done the battery icon was changed, with no need to wipe dalvik or use recovery at all.
Go ahead and try for your self, here is my testing.zip (you must have at least pick and pack and a theme with the accurate battery mod installed for this to work);
http://www.megaupload.com/?d=QFLQDEGE
I have my EA11 dark froyo port that i'm working on, and you'll see i've changed the battery to the EA11 Splash of Color battery
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Then stay tuned for some updates on the theme's i've ported (customizations!)
looks awesome! I read something about this a while back, seems pretty useful.
Sent from my SCH-I500 using Tapatalk
Description
This widget downloads 2 images from the URLs you specify and displays them on your home screen. You can configure the refresh interval (15m, 30m, 1h or 2h) and you can also do manual updates whenever you want.
Purpose
It is a great tool for system administrators to keep an eye on their servers when ... they are not keeping an eye on the servers (not at work, or when at work and interested to see the stats of their own personal servers).
You need to know how to configure MRTG or other tools that are able to generate these updated images.
Screenshots
1. 480 x 854 phone screen, 2 Image Monitor Widgets running:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
2. from 240x320 resolution
Details
Home page contains more details of the application (screenshots, instructions to configure MRTG, image sizes, license, etc).
Widget listens for network connectivity events and downloads automatically the images every time a network connection is established.
It is by design, as I usually want to check the home screen widgets when I exit areas of no signal, and I don't like to manually update the things.
It comes in 4x1 size (for bigger screens) and in 3x3 for smaller screens (wildfire, x10 mini, etc).
I wrote an identical app for WM 6.1 (http://forum.xda-developers.com/showthread.php?t=1025076) and now I've decided to rewrite it also for Android (since I also have an Android phone now).
Download:
Image Monitor Widget.apk – version 1.1(116)
Permissions:
* Storage (modify/delete SD card contents) – needed to be able to save logs (into /sdcard/Android/data folder) and also to allow settings backup.
* Network (full internet access / network state) – so that images can be downloaded and to get access to the network state change trigger.
Running
You need to be an administrator of a server which you can configure to generate the small graphs.
To read about how to configure MRTG to generate the small images please check here.
There's no security for now - the images will have to be made available on your sever on a URL path that only you know and then add those URLs into the widget settings.
I'm using it for a while now and I've decided to share it with the community.
UR Image Widget
Hi,
I've written a similar android widget app that is multi purpose and should also be able to display MRTG-images:
URL Image Widget
Just search for it on google play
Have fun
Leif
Hi guys, this is just a simple Tutorial to setup your own icon for your Android applications.
- So, first you have to create/find a 48 x 48 PNG image and place the image inside your Project folder under res/drawable. You can name the icon as of your choice, but remember to use same name in every folders like drawable-hdpi or drawable-mdpi etc..
- Open AndroidManifest.xml
- Inside the XML file, you should see an <application> tag, and the android:icon attribute. Add the below line to that attribute.
Code:
android:icon="@drawable/icon"
Note that, I named my icon as icon.png since the name icon. PNG extension is not needed in the XML file. Just only have to specify the icon name.
So, now you have successfully set your icon to your app.
But the thing is, Android Phones comes in variety of Screen resolutions. So your app icon must also support the different screen sizes/resolution. For this, inside your Project you will find many folders like drawable-hdpi, drawable-ldpi, drawable-mdpi and drawable-xhdpi under the /res folder. Add those images inside the respected folders by the resolution specified in the below table.
1. Low Density (~120dpi)
Folder Path: res/drawable-ldpi
Image resolution must be 36 x 36 PNG file.
2. Medium Density (~160dpi)
Folder Path: res/drawable-mdpi
Image resolution must be 48 x 48 PNG file.
3. High Density (~240dpi)
Folder Path: res/drawable-hdpi
Image resolution must be 72 x 72 PNG file.
4. Extra High Density (~320dpi)
Folder Path: res/drawable-xhdpi
Image resolution must be 96 x 96 PNG file.
Click to expand...
Click to collapse
Anyways as an example, I have set an icon for this Application, and the before/after setting the icon is showed in the below pics.
BEFORE :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
AFTER :
So, that's it. And its not that hard thing to set an icon for your Android apps. I have used XDA logo of various resolutions for the icon. You can download the one's I used from here, or you can design your own and set as mentioned in the Tutorial. Also, you may need to check the Icon Design Guidelines specified by Google for reference.
Reserved.